123 results ( Show 25 | All )
| Number | Files | Title | Authors | Date | More Info | Status |
|---|---|---|---|---|---|---|
| RFC 479 | ASCII, PDF, HTML | Use of FTP by the NIC Journal | J.E. White | March 1973 | Unknown | |
| RFC 543 | ASCII, PDF, HTML | Network journal submission and delivery | N.D. Meyer | July 1973 | Unknown | |
| RFC 628 | ASCII, PDF, HTML | Status of RFC numbers and a note on pre-assigned journal numbers | M.L. Keeney | March 1974 | Unknown | |
| RFC 629 | ASCII, PDF, HTML | Scenario for using the Network Journal | J.B. North | March 1974 | Unknown | |
| RFC 652 | ASCII, PDF, HTML | Telnet output carriage-return disposition option | D. Crocker | October 1974 | Historic (changed from Proposed Standard August 1998) | |
| RFC 1917 a.k.a. BCP 4 | ASCII, PDF, HTML | An Appeal to the Internet Community to Return Unused IP Networks (Prefixes) to the IANA | P. Nesser II | February 1996 | Best Current Practice | |
| RFC 2034 | ASCII, PDF, HTML | SMTP Service Extension for Returning Enhanced Error Codes | N. Freed | October 1996 | Proposed Standard | |
| RFC 2141 | ASCII, PDF, HTML, HTML with inline errata | URN Syntax | R. Moats | May 1997 | Errata, Obsoleted by RFC 8141 | Proposed Standard |
| RFC 2169 | ASCII, PDF, HTML | A Trivial Convention for using HTTP in URN Resolution | R. Daniel | June 1997 | Historic (changed from Experimental December 2021) | |
| RFC 2276 | ASCII, PDF, HTML | Architectural Principles of Uniform Resource Name Resolution | K. Sollins | January 1998 | Updated by RFC 3401 | Informational |
| RFC 2288 | ASCII, PDF, HTML | Using Existing Bibliographic Identifiers as Uniform Resource Names | C. Lynch, C. Preston, R. Daniel | February 1998 | Errata | Informational |
| RFC 2388 | ASCII, PDF, HTML, HTML with inline errata | Returning Values from Forms: multipart/form-data | L. Masinter | August 1998 | Errata, Obsoleted by RFC 7578 | Proposed Standard |
| RFC 2446 | ASCII, PDF, HTML | iCalendar Transport-Independent Interoperability Protocol (iTIP) Scheduling Events, BusyTime, To-dos and Journal Entries | S. Silverberg, S. Mansour, F. Dawson, R. Hopson | November 1998 | Errata, Obsoleted by RFC 5546 | Proposed Standard |
| RFC 2483 | ASCII, PDF, HTML | URI Resolution Services Necessary for URN Resolution | M. Mealling, R. Daniel | January 1999 | Experimental | |
| RFC 2611 a.k.a. BCP 33 | ASCII, PDF, HTML | URN Namespace Definition Mechanisms | L. Daigle, D. van Gulik, R. Iannella, P. Faltstrom | June 1999 | Obsoleted by RFC 3406 | Best Current Practice |
| RFC 2648 | ASCII, PDF, HTML, HTML with inline errata | A URN Namespace for IETF Documents | R. Moats | August 1999 | Errata, Updated by RFC 6924, RFC 9141 | Informational |
| RFC 3001 | ASCII, PDF, HTML | A URN Namespace of Object Identifiers | M. Mealling | November 2000 | Obsoleted by RFC 3061 | Informational |
| RFC 3043 | ASCII, PDF, HTML | The Network Solutions Personal Internet Name (PIN): A URN Namespace for People and Organizations | M. Mealling | January 2001 | Informational | |
| RFC 3044 | ASCII, PDF, HTML | Using The ISSN (International Serial Standard Number) as URN (Uniform Resource Names) within an ISSN-URN Namespace | S. Rozenfeld | January 2001 | Obsoleted by RFC 8254 | Historic (changed from Informational October 2017) |
| RFC 3061 | ASCII, PDF, HTML, HTML with inline errata | A URN Namespace of Object Identifiers | M. Mealling | February 2001 | Errata, Obsoletes RFC 3001 | Informational |
| RFC 3085 | ASCII, PDF, HTML | URN Namespace for NewsML Resources | A. Coates, D. Allen, D. Rivers-Moore | March 2001 | Informational | |
| RFC 3120 | ASCII, PDF, HTML | A URN Namespace for XML.org | K. Best, N. Walsh | June 2001 | Informational | |
| RFC 3121 | ASCII, PDF, HTML | A URN Namespace for OASIS | K. Best, N. Walsh | June 2001 | Informational | |
| RFC 3151 | ASCII, PDF, HTML | A URN Namespace for Public Identifiers | N. Walsh, J. Cowan, P. Grosso | August 2001 | Informational | |
| RFC 3187 | ASCII, PDF, HTML | Using International Standard Book Numbers as Uniform Resource Names | J. Hakala, H. Walravens | October 2001 | Obsoleted by RFC 8254 | Historic (changed from Informational October 2017) |