Where and how to get new RFCs ============================= RFCs may be obtained via EMAIL 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 may take a few days to make available the most recent RFCs. Many of these repositories also now have World Wide Web servers. Try the following URL as a starting point: http://www.isi.edu/rfc-editor/ 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, NIS.GARR.IT, or FTP.IMAG.FR. 1. DS.INTERNIC.NET - InterNIC Directory and Database Services RFC's may be obtained from DS.INTERNIC.NET via FTP, WAIS, and electronic mail. Through FTP, RFC's are stored as rfc/rfcnnnn.txt or rfc/rfcnnnn.ps where 'nnnn' is the RFC number. Login as "anonymous" and provide your e-mail address as the password. Through WAIS, you may use either your local WAIS client or telnet to DS.INTERNIC.NET and login 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, please connect to "internic.net" port 70. contact: admin@ds.internic.net 2. NIS.NSF.NET To obtain RFCs from NIS.NSF.NET via FTP, login with username "anonymous" and password "guest"; then connect to the directory of RFCs with cd /internet/documents/rfc. The file name 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" with nnnn the RFC number. contact: rfc-mgr@merit.edu 3. 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 which cannot use FTP. Address the request to "SENDRFC@NISC.JVNC.NET" and in the "Subject:" field of the message indicate the RFC number, as in "Subject: rfcNNNN" (where NNNN is the RFC number). Please note that 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. contact: rfc-admin@nisc.jvnc.net 4. 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). Login 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 4 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". contact: RFC-Manager@ISI.EDU 5. 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 "Z" 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. Please contact Chris Myers (chris@wugate.wustl.edu) if you want to mount this file system in your NFS. contact: chris@wugate.wustl.edu 6. SRC.DOC.IC.AC.UK RFCs can be obtained via FTP from SRC.DOC.IC.AC.UK with the pathname rfc/rfcnnnn.txt.gz or rfc/rfcnnnn.ps.gz (where "nnnn" refers to the number of the RFC). Login with FTP username "anonymous" and password "your-email-address". To obtain the RFC Index, use the pathname rfc/rfc-index.txt.gz. (The trailing .gz 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 which 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.gz 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.gz The archive is also available using NIFTP and the ISO FTAM system. contact: ukuug-soft@doc.ic.ac.uk 7. FTP.NCREN.NET To obtain RFCs from FTP.NCREN.NET via FTP, login with username "anonymous" and your internet e-mail address as password. The RFCs can be found in the directory /rfc, with file names 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. contact: rfc-mgr@ncren.net 8. 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. contact: rfc-maint@sesqui.net 9. 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). Login with FTP, username "anonymous" and password "guest". 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: send a mail to dbserv@nis.garr.it whose body contains "get mirrors/RFC/rfc.[txt,ps]". To get via electronic mail a file in the ftp archive, put the get command either in the subject or as a mail body line of a mail message sent to dbserv@nis.garr.it. must be the concatenation of two strings, the directory path and the filename. Remember: use uppercase and lowercase exactly! The directory path is listed at the beginning of each block of files. Example: to get RFC1004...the command should be: get mirrors/RFC/rfc1004.txt. 10. FTP.IMAG.FR RFCs can be obtained via FTP from ftp.imag.fr with the pathname /pub/archive/IETF/rfc/rfcnnnn.txt (where "nnnn" refers to the number of the RFC). Login with FTP username "anonymous" and password "your-email-address". To obtain the RFC Index, use the pathname /pub/archive/IETF/rfc/rfc-index.txt Internet drafts & other IETF related documents are also mirrored in the /pub/archive/IETF directory. Contact: rfc-adm@imag.fr ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Secondary Repositories: Australia and Pacific Rim ------------------------- Site: munnari Contact: Robert Elz Host: munnari.oz.au Directory: rfc rfc's in compressed format rfcNNNN.Z postscript rfc's rfcNNNN.ps.Z Site: The Programmers' Society University of Technology, Sydney Contact: ftp@progsoc.uts.edu.au Host: ftp.progsoc.uts.edu.au Directory: rfc (or std). Both are stored uncompressed. Denmark ------- Site: University of Copenhagen Host: ftp.denet.dk Directory: rfc Finland ------- Site: FUNET Host: nic.funet.fi Directory: index/RFC Directory: /pub/netinfo/rfc Notes: RFCs in compressed format. Also provides email access by sending mail to archive-server@nic.funet.fi. France ------ Site: Centre d'Informatique Scientifique et Medicale (CISM) Contact: ftpmaint@univ-lyon1.fr Host: ftp.univ-lyon1.fr Directories: pub/rfc/* Classified by hundreds pub/mirrors/rfc Mirror of Internic Notes: Files compressed with gzip. Online decompression done by the FTP server. France ------ Site: Institut National de la Recherche en Informatique et Automatique (INRIA) Address: info-server@inria.fr Notes: RFCs are available via email to the above address. Info Server manager is Mireille Yamajako (yamajako@inria.fr). Germany ------- Site: EUnet Germany Host: ftp.Germany.EU.net Directory: pub/documents/rfc Netherlands ----------- Site: EUnet Host: mcsun.eu.net Directory: rfc Notes: RFCs in compressed format. Norway ------ Host: ugle.unit.no Directory: pub/rfc South Africa ------------ Site: The Internet Solution Contact: ftp-admin@is.co.za Host: ftp.is.co.za Directory: internet/in-notes/rfc Sweden ------ Host: sunic.sunet.se Directory: rfc Host: chalmers.se Directory: rfc United States ------------- Site: cerfnet Contact: help@cerf.net Host: nic.cerf.net Directory: netinfo/rfc Site: NASA NAIC Contact: rfc-updates@naic.nasa.gov Host: naic.nasa.gov Directory: files/rfc Site: NIC.DDN.MIL (DOD users only) Contact: NIC@nic.ddn.mil Host: NIC.DDN.MIL Directory: rfc/rfcnnnn.txt Note: DOD users only may obtain RFC's via FTP from NIC.DDN.MIL. Internet users should NOT use this source due to inadequate connectivity. Site: uunet Contact: James Revell Host: ftp.uu.net Directory: inet/rfc UUNET Archive ------------- UUNET archive, which includes the RFC's, various IETF documents, and other information regarding the internet, is available to the public via anonymous ftp (to ftp.uu.net) and anonymous uucp, and will be available via an anonymous kermit server soon. Get the file /archive/inet/ls-lR.Z for a listing of these documents. Any site in the US 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 only works from within the US. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Requests for special distribution of RFCs should be addressed to either the author of the RFC in question or to RFC-Manager@ISI.EDU. 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@ISI.EDU. Users with .MIL addresses may send a request to MAJORDOMO@NIC.DDN.MIL with an empty Subject: line and a message: subscribe rfc [your email address]. Changes to this file "rfc-retrieval.txt" should be sent to RFC-MANAGER@ISI.EDU. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~