• E
• Selected RFCs
• Where and How to Get New RFCs
• Primary Repositories
• ds.internic.net—InterNIC Directory and Database Services
• nis.nsf.net
• nisc.jvnc.net
• ftp.isi.edu
• wuarchive.wustl.edu
• doc.ic.ac.uk
• ftp.ncren.net
• ftp.sesqui.net
• nis.garr.it
• Secondary Repositories
• UUNET Archive
• RFC INDEX

E

Selected RFCs

RFCs, or Request for Comments, are the official standards in the Internet community. Contained in this index is a partial list of relevant RFCs. A complete list of effective RFCs, as well as the RFCs themselves, is available online in various places throughout the Internet. Sending e-mail to rfc-info@isi.edu with a subject, getting rfcs, and help, ways_to_get_rfcs, in the body of the message will return a list containing current methods for obtaining RFCs. At the time of printing, that e-mail message returned the following material in this appendix.

Where and How to Get New RFCs

RFCs may be obtained via e-mail or FTP from many RFC repositories. The primary repositories will have the RFC available when it is first announced, as will many secondary repositories. Some secondary repositories might take a few days to make available the most recent RFCs.

Primary Repositories

RFCs can be obtained via FTP from ds.internic.net, nis.nsf.net, nisc.jvnc.net, ftp.isi.edu, wuarchive.wustl.edu, src.doc.ic.ac.uk, ftp.ncren.net, ftp.sesqui.net, or nis.garr.it.

ds.internic.net—InterNIC Directory and Database Services

RFCs can be obtained from ds.internic.net via FTP, WAIS, and electronic mail. Through FTP, RFCs are stored as rfc/rfcnnnn.txt or rfc/rfcnnnn.ps where nnnn is the RFC number. Log in as anonymous and provide your e-mail address as the password. Through WAIS, you can use either your local WAIS client or Telnet to ds.internic.net and log in as wais (no password required) to access a WAIS client. Help information and a tutorial for using WAIS are available online. The WAIS database to search is rfcs.

Directory and Database Services also provides a mail server interface. Send a mail message to mailserv@ds.internic.net and include any of the following commands in the message body:

• document-by-name rfcnnnn, where nnnn is the RFC number. The text version is sent.
  
  
• file /ftp/rfc/rfcnnnn.yyy, where nnnn is the RFC number and yyy is txt or ps.
  
  
• help to get information on how to use the mailserver.
  
  

The InterNIC Directory and Database Services Collection of Resource Listings, Internet Documents such as RFCs, FYIs, STDs, and Internet Drafts, and Publically Accessible Databases are also now available via Gopher. All our collections are waisindexed and can be searched from the Gopher menu.

To access the InterNIC Gopher Servers, connect to internic.net, port 70.

admin@dsinternic.net

nis.nsf.net

To obtain RFCs from nis.nsf.net via FTP, log in with username anonymous and password guest; then connect to the directory of RFCs with cd /internet/documents/rfc. The filename is of the form rfcnnnn.txt (where nnnn refers to the RFC number).

For sites without FTP capability, electronic mail query is available from nis.nsf.net. Address the request to nis-info@nis.nsf.net and leave the subject field of the message blank. The first text line of the message must be send rfcnnnn.txt, where nnnn is the RFC number.

rfc-mgr@merit.edu

nisc.jvnc.net

RFCs can also be obtained via FTP from nisc.jvnc.net, with the pathname rfc/rfcnnnn.txt (where nnnn refers to the number of the RFC). An index can be obtained with the pathname rfc/rfc-index.txt. JvNCnet also provides a mail service for those sites that cannot use FTP. Address the request to sendrfc@nisc.jvnc.net. In the Subject: field of the message, indicate the RFC number, as in Subject: rfcnnnn (where nnnn is the RFC number). RFCs whose numbers are less than 1000 need not place a leading 0. (For example, RFC932 is fine.) For a complete index to the RFC library, enter rfc-index in the Subject: field, as in Subject: rfc-index. No text in the body of the message is needed.

rfc-admin@nisc.jvnc.net

ftp.isi.edu

RFCs can be obtained via FTP from ftp.isi.edu, with the pathname in-notes/rfcnnnn.txt (where nnnn refers to the number of the RFC). Log in with FTP username anonymous and password guest.

RFCs can also be obtained via electronic mail from isi.edu by using the RFC-INFO service. Address the request to rfc-info@isi.edu with a message body of

Retrieve: RFC

Doc-ID: RFCnnnn

where nnnn refers to the number of the RFC. (Always use four digits; the DOC-ID of RFC 822 is RFC0822.) The rfc-info@isi.edu server provides other ways of selecting RFCs based on keywords and such; for more information, send a message to rfc-info@isi.edu with the message body help: help.

RFC-Manager@ISI.EDU

wuarchive.wustl.edu

RFCs can also be obtained via FTP from wuarchive.wustl.edu, with the pathname info/rfc/rfcnnnn.txt.Z (where nnnn refers to the number of the RFC and U indicates that the document is in compressed form).

At wuarchive.wustl.edu, the RFCs are in an archive file system, and various archives can be mounted as part of an NFS file system. Contact Chris Myers (chris@wugate.wustl.edu) if you want to mount this file system in your NFS.

chris@wugate.wustl.edu

doc.ic.ac.uk

RFCs can be obtained via FTP from src.doc.ic.ac.uk with the pathname rfc/rfcnnnn.txt.Z or rfc/rfcnnnn.ps.Z (where nnnn refers to the number of the RFC). Log in with FTP username anonymous and password your-email-address. To obtain the RFC Index, use the pathname rfc/rfc-index.txt.Z. (The trailing .Z indicates that the document is in compressed form.)

src.doc.ic.ac.uk also provides an automatic mail service for those sites in the UK that cannot use FTP. Address the request to info-server@doc.ic.ac.uk with a Subject: line of wanted and a message body of

request sources

topic path rfc/rfcnnnn.txt.Z

request end

where nnnn refers to the number of the RFC. Multiple requests may be included in the same message by giving multiple topic path commands on separate lines. To request the RFC Index, the command should read

topic path rfc/rfc-index.txt.Z

The archive is also available using NIFTP and the ISO FTAM system.

ukuug-soft@doc.ic.ac.uk

ftp.ncren.net

To obtain RFCs from ftp.ncren.net via FTP, log in with username anonymous and your internet e-mail address as the password. The RFCs can be found in the directory /rfc, with filenames of the form: rfcnnnn.txt or rfcnnnn.ps, where nnnn refers to the RFC number.

This repository is also accessible via WAIS and the Internet Gopher.

rfc-mgr@ncren.net

ftp.sesqui.net

RFCs can be obtained via FTP from ftp.sesqui.net, with the pathname pub/rfc/rfcnnnn.xxx (where nnnn refers to the number of the RFC and xxx indicates the document form, txt for ASCII and ps for PostScript).

At ftp.sesqui.net, the RFCs are in an archive file system, and various archives can be mounted as part of an NFS file system. Please contact RFC-maintainer (rfc-maint@sesqui.net) if you want to mount this file system in your NFS.

rfc-maint@sesqui.net

nis.garr.it

RFCs can be obtained from nis.garr.it FTP archive with the pathname mirrors/RFC/rfcnnnn.txt (where nnnn refers to the number of the RFC). Log in with FTP, username anonymous and password guest.

The following is a summary of ways to get RFC from GARR-NIS FTP archive:

Via FTP: ftp.nis.garr.it directory mirrors/RFC

Via Gopher: gopher.nis.garr.it, folders GARR-NIS; anonymous FTP: ftp.nis.garr.it mirrors RFC

Via WWW: ftp://ftp.nis.garr.it/mirrors/RFC

Via e-mail: dbserv@nis.garr.it whose body contains get mirrors/RFC/rfc<number>..

To have an RFC from the FTP archive e-mailed to you, put the get <fullpathname> command either in the subject or as a mail body line of a mail message sent to dbserv@nis.garr.it. <fullpathname> must be the concatenation of two strings: the directory path and the filename. Remember to use upper- and lowercase exactly. The directory path is listed at the beginning of each block of files.

For example, to get RFC1004, the command is get mirrors/RFC/rfc1004.txt.

Secondary Repositories

Here are other sites that contain the RFC documents.

UUNET Archive

UUNET archive, which includes RFCs, various IETF documents, and other information regarding the Internet, is available to the public via anonymous FTP (to ftp.uu.net), anonymous UUCP, and soon via an anonymous kermit server. Get the file /archive/inet/ls-lR.Z for a listing of these documents. Any site in the USA running UUCP may call +1 900 GOT SRCS and use the login uucp. There is no password. The phone company will bill you at $0.50 per minute for the call. The 900 number works only from within the USA.

Requests for special distribution of RFCs should be addressed to either the author of the RFC in question or to nic@internic.net.

Submissions for Requests for Comments should be sent to rfc-editor@isi.edu. Please consult "Instructions to RFC Authors," RFC 1543, for further information.

Requests to be added to or deleted from the RFC distribution list should be sent to RFC-request@nic.ddn.mil.

Changes to this file rfc-retrieval.txt should be sent to rfc-manager@isi.edu.

RFC INDEX

1812 Baker, F.,ed. Requirements for IP Version 4 Routers. 1995 June; 175p. (Obsoletes 1716, 1009)

1808 Fielding, R. Relative Uniform Resource Locators. 1995 June; 16p.

1789 Yang, C. INETPhone: Telephone Services and Servers on Internet. 1995 April; 6p.

1788 Simpson, W. ICMP Domain Name Messages. 1995 April; 7p.

1780 Postel, J.,ed. INTERNET OFFICIAL PROTOCOL STANDARDS. 1995 March; 39p. (Obsoletes RFC 1720, RFC 1610, RFC 1540, RFC 1500, RFC 1410, RFC 1360 RFC 1280, RFC 1250, RFC 1200, RFC 1140, RFC 1130)

1772 Rekhter, Y.; Gross, P.,eds. Application of the Border Gateway Protocol in the Internet. 1995 March; 19p. (Obsoletes RFC 1655)

1771 Rekhter, Y.; Li, T.,eds. A Border Gateway Protocol 4 (BGP-4). 1995 March; 57p. (Obsoletes RFC 1654)

1769 Mills, D. Simple Network Time Protocol (SNTP). 1995 March; 14p. (Obsoletes RFC 1361)

1760 Haller, N. The S/KEY One-Time Password System. 1995 February; 12P.

1757 Waldbusser, S. Remote Network Monitoring Management Information Base. 1995 February; 91p. (Obsoletes RFC 1271)

1752 Bradner, S.; Mankin, A. The Recommendation for the IP Next Generation Protocol. January 1995; 52p.

1744 Huston, G. Observations on the Management of the Internet Address Space. December 1994; 12p.

1741 Faltstrom, P.; Crocker, D.; Fair, E. MIME Content Type for BinHex Encoded Files. 1994 December; 6 p.

1739 Kessler, G.; Shepard, S. A Primer On Internet and TCP/IP Tools. 1994 December; 46 p.

1738 Berners-Lee, T.; Masinter, L.; McCahill, M.,eds. Uniform Resource Locators (URL). 1994 December; 25 p.

1737 Sollins, K.; Masinter, L. Functional Requirements for Uniform Resource Names. 1994 December; 7 p.

1736 Kunze, J. Functional Recommendations for Internet Resource Locators. 1995 February; 10p.

1734 Myers, J. POP3 AUTHentication command. 1994 December; 5 p. (Format: TXT=8499 bytes)

1725 Myers, J.; Rose, M. Post Office Protocol, Version 3. 1994 November; 18 p. (Obsoletes RFC 1460)

1717 Sklower, K.; Lloyd, B.; McGregor, G.; Carr, D. The PPP Multilink Protocol (MP). 1994 November; 21 p.

1713 Romao, A. Tools for DNS debugging. 1994 November; 13 p.

1700 Reynolds, J.; Postel, J. ASSIGNED NUMBERS. 1994 October; 230 p. (Obsoletes RFC 1340)

1663 Rand, D. PPP Reliable Transmission. 1994 July; 8 p.

1661 Simpson, W.,ed. The Point-to-Point Protocol (PPP). 1994 July; 52 p. (Obsoletes RFC 1548)

1651 Freed, N.,ed.; Klensin, J.; Rose, M.; Stefferud, E.; Crocker, D. SMTP Service Extensions. 1994 July; 11 p. (Obsoletes RFC 1425)

1645 Gwinn, A. Simple Network Paging Protocol, Version 2. 1994 July; 15 p. (Obsoletes RFC 1568)

1636 Braden, R.; Clark, D.; Crocker, S.; Huitema, C. Report of IAB Workshop on Security in the Internet Architecture February 8-10, 1994. 1994 June; 52 p.

1635 Deutsch, P.; Emtage, A.; Marine, A. How to Use Anonymous FTP. 1994 May; 13 p.

1630 Berners-Lee, T. Universal Resource Identifiers in WWW. 1994 June; 28 p.

1618 Simpson, W. PPP over ISDN. 1994 May; 6 p.

1602 Internet Architecture Board; Internet Engineering Steering Group The Internet Standards Process—Revision 2. 1994 March; 37 p.

1601 Huitema, C. Charter of the Internet Architecture Board (IAB). 1994 March; 6 p.

1591 Postel, J. Domain Name System Structure and Delegation. 1994 March; 7 p.

1550 Bradner, S.; Mankin, S. IP: Next Generation (IPng) White Paper Solicitation. 1993 December; 6 p.

1547 Perkins, D. Requirements for an Internet Standard Point-to-Point Protocol. 1993 December; 21 p.

1541 Droms, R. Dynamic Host Configuration Protocol. 1993 October; 39 p. (Obsoletes RFC 1531)

1522 Moore, K. MIME (Multipurpose Internet Mail Extensions) Part Two: Message Header Extensions for Non-ASCII Text. 1993 September; 10 p. (Obsoletes 1342)

1490 Bradley, T.; Brown, C.; Malis, A. Multiprotocol Interconnect over Frame Relay. 1993 July; 35 p.(Obsoletes RFC 1294)

1459 Oikarinen, J.; Reed, D. Internet Relay Chat Protocol. 1993 May; 65 p.

1436 Anklesaria, F.; McCahill, M.; Lindner, P.; Johnson, D.; Torrey, D.; Alberti, B. The Internet Gopher Protocol (a distributed document search and retrieval protocol). 1993 March; 16 p.

1334 Lloyd, B.; Simpson, W. PPP Authentication Protocols. 1992 October; 16 p.

1333 Simpson, W. PPP Link Quality Monitoring. 1992 May; 15 p.

1332 McGregor, G. The PPP Internet Protocol Control Protocol (IPCP). 1992 May; 12 p. (Obsoletes RFC 1172)

1305 Mills, D. Network Time Protocol (Version 3) Specification, Implementation and Analysis. 1992 March; 120. (Obsoletes RFC 1119, RFC 1059, RFC 958)

1303 McCloghrie, K.; Rose, M. A Convention for Describing SNMP-based Agents. 1992 February; 12 p.

1301 Armstrong, S.; Freier, A.; Marzullo, K. Multicast Transport Protocol. February 1992; 38 p.

1296 Lottor, M. Internet Growth (1981-1991). 1992 January; 9 p.

1293 Brown, C. Inverse Address Resolution Protocol. 1992 January; 6 p.

1291 Aggarwal, V. Mid-Level Networks - Potential Technical Services. 1991 December; 10 p.

1288 Zimmerman, D. The Finger User Information Protocol. 1991 December; 12 p. (Obsoletes RFC 1196, RFC 1194, RFC 742)

1282 Kantor, B. BSD Rlogin. 1991 December; 5 p. (Format: TXT=10704 bytes) (Obsoletes RFC 1258)

1281 Pethia, R.; Crocker, S.; Fraser, B. Guidelines for the Secure Operation of the Internet. 1991 November; 10 p.

1277 Hardcastle-Kille, S. Encoding Network Addresses to support operation over non-OSI lower layers. 1991 November; 12 p.

1270 Kastenholz, F.,ed. SNMP communications services. 1991 October; 11 p.

1269 Willis, S.; Burruss, J. Definitions of Managed Objects for the Border Gateway Protocol (version 3). 1991 October; 13 p.

1267 Lougheed, K.; Rekhter, Y. A Border Gateway Protocol 3 (BGP-3). 1991 October; 35 p. (Obsoletes RFC 1105, RFC 1163)

1266 Rekhter, Y.,ed. Experience with the BGP protocol. 1991 Ocober; 9 p.

1265 Rekhter, Y.,ed. BGP protocol analysis. 1991 October; 8 p.

1264 Hinden, R. Internet routing protocol standardization criteria. 1991 October; 8 p.

1261 Williamson, S.; Nobile, L. Transition of NIC services. 1991 September; 3 p.

1256 Deering, S.,ed. ICMP router discovery messages. 1991 September; 19 p.

1254 Mankin, A.; Ramakrishnan, K.,eds. Gateway congestion control survey. 1991 August; 25 p.

1244 Holbrook, J.; Reynolds, J.,eds. Site Security Handbook. 1991 July; 101 p.

1242 Bradner, S.,ed. Benchmarking terminology for network interconnection devices. 1991 July; 12 p.

1240 Shue, C.; Haggerty, W.; Dobbins, K. OSI connectionless transport services on top of UDP: Version 1. 1991 June; 8 p.

1234 Provan, D. Tunneling IPX traffic through IP networks. 1991 June; 6 p.

1221 Edmond, W. Host Access Protocol (HAP) specification: Version 2. 1991 April; 68 p. (Updates RFC 907)

1220 Baker, F.,ed. Point-to-Point Protocol extensions for bridging. 1991 April; 18 p.

1219 Tsuchiya, P. On the assignment of subnet numbers. 1991 April; 13 p.

1215 Rose, M.,ed. Convention for defining traps for use with the SNMP. 1991 March; 9 p.

1211 Westine, A.; Postel, J. Problems with the maintenance of large mailing lists. 1991 March; 54 p.

1209 Piscitello, D.; Lawrence, J. Transmission of IP datagrams over the SMDS Service. 1991 March; 11 p. (Format: TXT=25280 bytes)

1208 Jacobsen, O.; Lynch, D. Glossary of networking terms. 1991 March; 18 p.

1207 Malkin, G.; Marine, A.; Reynolds, J. FYI on Questions and Answers: Answers to commonly asked "experienced Internet user" questions. 1991 February; 15 p.

1205 Chmielewski, P. 5250 Telnet interface. 1991 February; 12 p.

1203 Rice, J. Interactive Mail Access Protocol: Version 3. 1991 February; 49 p. (Obsoletes RFC 1064)

1201 Provan, D. Transmitting IP traffic over ARCNET networks. 1991 February; 7 p. (Obsoletes RFC 1051)

1192 Kahin, B.,ed. Commercialization of the Internet summary report. 1990 November; 13 p.

1191 Mogul, J.; Deering, S. Path MTU discovery. 1990 November; 19 p. (Obsoletes RFC 1063)

1188 Katz, D. Proposed standard for the transmission of IP datagrams over FDDI networks. 1990 October; 11 p. (Obsoletes RFC 1103)

1183 Everhart, C.; Mamakos, L.; Ullmann, R.; Mockapetris, P. New DNS RR definitions. 1990 October; 11 p. (Updates RFC 1034, RFC 1035)

1180 Socolofsky, T.; Kale, C. TCP/IP tutorial. 1991 January; 28 p.

1173 VanBokkelen, J. Responsibilities of host and network managers: A summary of the "oral tradition" of the Internet. 1990 August; 5 p.

1170 Fougner, R. Public key standards and licenses. 1991 January; 2 p.

1166 Kirkpatrick, S.; Stahl, M.; Recker, M. Internet numbers. 1990 July; 182 p. (Obsoletes RFC 1117, RFC 1062, RFC 1020)

1165 Crowcroft, J.; Onions, J. Network Time Protocol (NTP) over the OSI Remote Operations Service. 1990 June; 10 p.

1157 Case, J.; Fedor, M.; Schoffstall, M.; Davin, C. Simple Network Management Protocol (SNMP). 1990 May; 36 p.(Obsoletes RFC 1098)

1144 Jacobson, V. Compressing TCP/IP headers for low-speed serial links. 1990 February; 43 p.

1132 McLaughlin, L. Standard for the transmission of 802.2 packets over IPX networks. 1989 November; 4 p. (Format: TXT=8128 bytes)

1129 Mills, D. Internet time synchronization: The Network Time Protocol. 1989 October; 29 p.

1128 Mills, D. Measured performance of the Network Time Protocol in the Internet system. 1989 October; 20 p.

1125 Estrin, D. Policy requirements for inter Administrative Domain routing. 1989 November; 18 p.

1124 Leiner, B. Policy issues in interconnecting networks. 1989 September; 54 p.

1118 Krol, E. Hitchhikers guide to the Internet. 1989 September; 24 p.

1112 Deering, S. Host extensions for IP multicasting. 1989 August; 17 p. (Obsoletes RFC 988, RFC 1054)

1108 Kent, S. Security Options for the Internet Protocol. 1991 November; 17 p. (Obsoletes RFC 1038)

1101 Mockapetris, P. DNS encoding of network names and other types. 1989 April; 14 p.(Updates RFC 1034, RFC 1035)

1092 Rekhter, J. EGP and policy based routing in the new NSFNET backbone. 1989 February; 5 p.

1089 Schoffstall, M.; Davin, C.; Fedor, M.; Case, J. SNMP over Ethernet. 1989 February; 3 p.

1088 McLaughlin, L. Standard for the transmission of IP datagrams over NetBIOS networks. 1989 February; 3 p.

1087 Defense Advanced Research Projects Agency, Internet Activities Board; DARPA IAB Ethics and the Internet. 1989 January; 2 p.

1082 Rose, M. Post Office Protocol: Version 3: Extended service offerings. 1988 November; 11 p.

1077 Leiner, B.,ed. Critical issues in high-bandwidth networking. 1988 November; 46 p.

1074 Rekhter, J. NSFNET backbone SPF based Interior Gateway Protocol. 1988 October; 5 p.

1056 Lambert, M. PCMAIL: A distributed mail system for personal computers. 1988 June; 38 p. (Obsoletes RFC 993)

1055 Romkey, J. Nonstandard for transmission of IP datagrams over serial lines: SLIP. 1988 June; 6 p.

1049 Sirbu, M. Content-type header field for Internet messages. 1988 March; 8 p.

1042 Postel, J.; Reynolds, J. Standard for the transmission of IP datagrams over IEEE 802 networks. 1988 February; 15 p. (Obsoletes RFC 948)

1033 Lottor, M. Domain administrators operations guide. 1987 November; 22 p.

1032 Stahl, M. Domain administrators guide. 1987 November; 14 p.

1027 Carl-Mitchell, S.; Quarterman, J. Using ARP to implement transparent subnet gateways. 1987 October; 8 p.

1008 McCoy, W. Implementation guide for the ISO Transport Protocol. 1987 June; 73 p.

1007 McCoy, W. Military supplement to the ISO Transport Protocol. 1987 June; 23 p.

1006 Rose, M.; Cass, D. ISO transport services on top of the TCP: Version 3. 1987 May; 17 p. (Obsoletes RFC 983)