jkrey@ISI.EDU (Joyce K. Reynolds) (05/14/91)
Archive-name: internet/route/advance-nsfnet-routing-rfc/1991-05-08 Archive: ftp.nisc.sri.com:/rfc/rfc1122.txt [192.33.33.22] Original-posting-by: jkrey@ISI.EDU (Joyce K. Reynolds) Original-subject: RFC1222 on Advancing the NSFNET Routing Architecture Reposted-by: emv@msen.com (Edward Vielmetti, MSEN) A new Request for Comments is now available from the Network Information Center in the online library at NIC.DDN.MIL. RFC 1222: Title: Advancing the NSFNET Routing Architecture Author: H-W. Braun and Y. Rekhter Mailbox: HWB@SDSC.EDU, Yakov@Watson.IBM.COM Pages: 6 Characters: 14,729 Obsoletes/Updates: none pathname: RFC:RFC1222.TXT This RFC suggests improvements in the NSFNET routing architecture to accommodate a more flexible interface to the Backbone clients. This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. RFCs can be obtained via FTP from FTP.NISC.SRI.COM, NIS.NSF.NET, or NISC.JVNC.NET. RFCs can be obtained via FTP from FTP.NISC.SRI.COM, with the pathname rfc/rfcNNNN.txt (where "NNNN" refers to the number of the RFC). Login with FTP, username "anonymous" and password "guest". SRI also provides an automatic mail service for those sites which cannot use FTP. Address the request to MAIL-SERVER@NISC.SRI.COM and in the body of the message indicate the RFC to be sent: "send rfcNNNN" where NNNN is the RFC number. Multiple requests may be included in the same message. To obtain RFCs from NIS.NSF.NET via FTP, login with username "anonymous" and password "guest"; then connect to the RFC directory ("cd RFC"). The file name is of the form RFCnnnn.TXT-1 (where "nnnn" refers to the number of the RFC). The NIS also provides an automatic mail service for those sites which cannot use FTP. Address the request to NIS-INFO@NIS.NSF.NET and leave the subject field of the message blank. The first line of the text of the message must be "SEND RFCnnnn.TXT-1", where nnnn is replaced by the RFC number. RFCs can also be obtained via FTP from NISC.JVNC.NET, with the pathname rfc/RFCnnnn.TXT.v.Z (where "nnnn" refers to the number of the RFC and "v" refers to the version number of the RFC). There are a number of RFCs available in postscript format. Those RFCs have modifiers of .PS instead of .TXT. Login with FTP, username "anonymous" and your e-mail address as your password. JvNCnet also provides a mail service for those sites which cannot use FTP. Address the request to NISC@JVNC.NET and in the subject field of the message indicate the RFC number, as in "Subject: RFC nnnn". Requests for special distribution should be addressed to either the author of the RFC in question, or to NIC@NIC.DDN.MIL. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to POSTEL@ISI.EDU. Please consult RFC 1111, "Instructions to RFC Authors", for further information. Requests to be added to or deleted from this distribution list should be sent to RFC-REQUEST@NIC.DDN.MIL. Joyce K. Reynolds USC/Information Sciences Institute -- comp.archives file verification ftp.nisc.sri.com -rw-r--r-- 1 root ftp 289148 Apr 21 06:40 /rfc/rfc1122.txt found advance-nsfnet-routing-rfc ok ftp.nisc.sri.com:/rfc/rfc1122.txt