Datasets:
magZHL
/
RFCtry

Dataset card Data Studio Files
xet
 Community
1
text
stringlengths
0
79
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
RFC INDEX
-------------
(CREATED ON: 06/05/2024.)
This file contains citations for all RFCs in numeric order.
RFC citations appear in this format:
#### Title of RFC. Author 1, Author 2, Author 3. Issue date.
(Format: ASCII) (Obsoletes xxx) (Obsoleted by xxx) (Updates xxx)
(Updated by xxx) (Also FYI ####) (Status: ssssss) (DOI: ddd)
or
#### Not Issued.
For example:
1129 Internet Time Synchronization: The Network Time Protocol. D.L.
Mills. October 1989. (Format: TXT, PS, PDF, HTML) (Also RFC1119)
(Status: INFORMATIONAL) (DOI: 10.17487/RFC1129)
Key to citations:
#### is the RFC number.
Following the RFC number are the title, the author(s), and the
publication date of the RFC. Each of these is terminated by a period.
Following the number are the title (terminated with a period), the
author, or list of authors (terminated with a period), and the date
(terminated with a period).
The format follows in parentheses. One or more of the following formats
are listed: text (TXT), PostScript (PS), Portable Document Format
(PDF), HTML, XML.
Obsoletes xxxx refers to other RFCs that this one replaces;
Obsoleted by xxxx refers to RFCs that have replaced this one.
Updates xxxx refers to other RFCs that this one merely updates (but
does not replace); Updated by xxxx refers to RFCs that have updated
(but not replaced) this one. Generally, only immediately succeeding
and/or preceding RFCs are indicated, not the entire history of each
related earlier or later RFC in a related series.
The (Also FYI ##) or (Also STD ##) or (Also BCP ##) phrase gives the
equivalent FYI, STD, or BCP number if the RFC is also in those
document sub-series. The Status field gives the document's
current status (see RFC 2026). The (DOI ddd) field gives the
Digital Object Identifier.
RFCs may be obtained in a number of ways, using HTTP, FTP, or email.
See the RFC Editor Web page http://www.rfc-editor.org
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
RFC INDEX
---------
0001 Host Software. S. Crocker. April 1969. (Format: TXT, HTML) (Status:
UNKNOWN) (DOI: 10.17487/RFC0001)
0002 Host software. B. Duvall. April 1969. (Format: TXT, PDF, HTML)
(Status: UNKNOWN) (DOI: 10.17487/RFC0002)
0003 Documentation conventions. S.D. Crocker. April 1969. (Format: TXT,
HTML) (Obsoleted by RFC0010) (Status: UNKNOWN) (DOI:
10.17487/RFC0003)
0004 Network timetable. E.B. Shapiro. March 1969. (Format: TXT, HTML)
(Status: UNKNOWN) (DOI: 10.17487/RFC0004)
0005 Decode Encode Language (DEL). J. Rulifson. June 1969. (Format: TXT,
HTML) (Status: UNKNOWN) (DOI: 10.17487/RFC0005)
0006 Conversation with Bob Kahn. S.D. Crocker. April 1969. (Format: TXT,
HTML) (Status: UNKNOWN) (DOI: 10.17487/RFC0006)
0007 Host-IMP interface. G. Deloche. May 1969. (Format: TXT, HTML)
(Status: UNKNOWN) (DOI: 10.17487/RFC0007)
0008 ARPA Network Functional Specifications. G. Deloche. May 1969.
(Format: PDF) (Status: UNKNOWN) (DOI: 10.17487/RFC0008)
0009 Host Software. G. Deloche. May 1969. (Format: PDF) (Status: UNKNOWN)
(DOI: 10.17487/RFC0009)
0010 Documentation conventions. S.D. Crocker. July 1969. (Format: TXT,
HTML) (Obsoletes RFC0003) (Obsoleted by RFC0016) (Updated by
RFC0024, RFC0027, RFC0030) (Status: UNKNOWN) (DOI: 10.17487/RFC0010)
0011 Implementation of the Host - Host Software Procedures in GORDO. G.
Deloche. August 1969. (Format: TXT, PDF, HTML) (Obsoleted by