Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa19359; 16 Jun 93 18:37 EDT Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa19278; 16 Jun 93 18:36 EDT Received: from zephyr.isi.edu by CNRI.Reston.VA.US id aa24475; 16 Jun 93 18:36 EDT Received: from akamai.isi.edu by zephyr.isi.edu (5.65c/5.61+local-13) id ; Wed, 16 Jun 1993 15:36:45 -0700 Message-Id: <199306162236.AA15528@zephyr.isi.edu> To: IETF-Announce: ; Subject: RFC1476 on RAP Cc: jkrey@isi.edu Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" Date: Wed, 16 Jun 93 15:36:42 PDT Sender:ietf-announce-request@IETF.CNRI.Reston.VA.US From: "Joyce K. Reynolds" --NextPart A new Request for Comments is now available in online RFC libraries. RFC 1476: Title: RAP: Internet Route Access Protocol Author: R. Ullmann Mailbox: Ariel@Process.COM Pages: 20 Characters: 45,560 Updates/Obsoletes: none This RFC describes an open distance vector routing protocol for use at all levels of the internet, from isolated LANs to the major routers of an international commercial network provider. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. Discussion and suggestions for improvement are requested. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@CNRI.RESTON.VA.US. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-REQUEST@NIC.DDN.MIL. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to "rfc-info@ISI.EDU" with the message body "help: ways_to_get_rfcs". For example: To: rfc-info@ISI.EDU Subject: getting rfcs help: ways_to_get_rfcs 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 RFC-EDITOR@ISI.EDU. Please consult RFC 1111, "Instructions to RFC Authors", for further information. Joyce K. Reynolds USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mail-server@nisc.sri.com" Content-Type: text/plain SEND rfc1476.txt --OtherAccess Content-Type: Message/External-body; name="rfc1476.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="rfc" Content-Type: text/plain --OtherAccess-- --NextPart--