RFC Number (or Subseries Number):
Title/Keyword:    
Show Abstract  Show Keywords






Any
Standards Track :: 
Best Current Practice
Informational
Experimental
Historic
Unknown
WG Acronym:
Author (surname):
Abstract contains:

114 results ( Show  25 | All )

NumberFilesTitleAuthorsDateMore InfoStatus
RFC 479ASCII, PDF Use of FTP by the NIC Journal J.E. WhiteMarch 1973    Unknown
RFC 543ASCII, PDF Network journal submission and delivery N.D. MeyerJuly 1973    Unknown
RFC 628ASCII, PDF Status of RFC numbers and a note on pre-assigned journal numbers M.L. KeeneyMarch 1974    Unknown
RFC 629ASCII, PDF Scenario for using the Network Journal J.B. NorthMarch 1974    Unknown
RFC 652ASCII, PDF Telnet output carriage-return disposition option D. CrockerOctober 1974    Historic (changed from Proposed Standard August 1998)
RFC 1917 a.k.a. BCP 4

ASCII, PDF An Appeal to the Internet Community to Return Unused IP Networks (Prefixes) to the IANA P. Nesser IIFebruary 1996    Best Current Practice
RFC 2034ASCII, PDF SMTP Service Extension for Returning Enhanced Error Codes N. FreedOctober 1996    Proposed Standard
RFC 2141ASCII, PDF URN Syntax R. MoatsMay 1997Obsoleted by RFC 8141, ErrataProposed Standard
RFC 2169ASCII, PDF A Trivial Convention for using HTTP in URN Resolution R. DanielJune 1997    Experimental
RFC 2276ASCII, PDF Architectural Principles of Uniform Resource Name Resolution K. SollinsJanuary 1998Updated by RFC 3401Informational
RFC 2288ASCII, PDF Using Existing Bibliographic Identifiers as Uniform Resource Names C. Lynch, C. Preston, R. DanielFebruary 1998ErrataInformational
RFC 2388ASCII, PDF Returning Values from Forms: multipart/form-data L. MasinterAugust 1998Obsoleted by RFC 7578, ErrataProposed Standard
RFC 2446ASCII, PDF iCalendar Transport-Independent Interoperability Protocol (iTIP) Scheduling Events, BusyTime, To-dos and Journal Entries S. Silverberg, S. Mansour, F. Dawson, R. HopsonNovember 1998Obsoleted by RFC 5546, ErrataProposed Standard
RFC 2483ASCII, PDF URI Resolution Services Necessary for URN Resolution M. Mealling, R. DanielJanuary 1999    Experimental
RFC 2611 a.k.a. BCP 33

ASCII, PDF URN Namespace Definition Mechanisms L. Daigle, D. van Gulik, R. Iannella, P. FaltstromJune 1999Obsoleted by RFC 3406Best Current Practice
RFC 2648ASCII, PDF A URN Namespace for IETF Documents R. MoatsAugust 1999Updated by RFC 6924, ErrataInformational
RFC 3001ASCII, PDF A URN Namespace of Object Identifiers M. MeallingNovember 2000Obsoleted by RFC 3061Informational
RFC 3043ASCII, PDF The Network Solutions Personal Internet Name (PIN): A URN Namespace for People and Organizations M. MeallingJanuary 2001    Informational
RFC 3044ASCII, PDFUsing The ISSN (International Serial Standard Number) as URN (Uniform Resource Names) within an ISSN-URN Namespace S. RozenfeldJanuary 2001Obsoleted by RFC 8254Historic (changed from Informational October 2017)
RFC 3061ASCII, PDF A URN Namespace of Object Identifiers M. MeallingFebruary 2001Obsoletes RFC 3001, ErrataInformational
RFC 3085ASCII, PDF URN Namespace for NewsML Resources A. Coates, D. Allen, D. Rivers-MooreMarch 2001    Informational
RFC 3120ASCII, PDF A URN Namespace for XML.org K. Best, N. WalshJune 2001    Informational
RFC 3121ASCII, PDF A URN Namespace for OASIS K. Best, N. WalshJune 2001    Informational
RFC 3151ASCII, PDF A URN Namespace for Public Identifiers N. Walsh, J. Cowan, P. GrossoAugust 2001    Informational
RFC 3187ASCII, PDF Using International Standard Book Numbers as Uniform Resource Names J. Hakala, H. WalravensOctober 2001Obsoleted by RFC 8254Historic (changed from Informational October 2017)