RFC1504 on Appletalk Update-Based Routing Protocol

"Joyce K. Reynolds" <jkrey@isi.edu> Fri, 27 August 1993 20:52 UTC

Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa10075; 27 Aug 93 16:52 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa29892; 27 Aug 93 16:52 EDT
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa10063; 27 Aug 93 16:52 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa10034; 27 Aug 93 16:50 EDT
Received: from zephyr.isi.edu by CNRI.Reston.VA.US id aa29817; 27 Aug 93 16:51 EDT
Received: from akamai.isi.edu by zephyr.isi.edu (5.65c/5.61+local-13) id <AA15432>; Fri, 27 Aug 1993 13:51:25 -0700
Message-Id: <199308272051.AA15432@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC1504 on Appletalk Update-Based Routing Protocol
Cc: jkrey@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 27 Aug 1993 13:51:16 -0700
Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US
From: "Joyce K. Reynolds" <jkrey@isi.edu>

A new Request for Comments is now available in online RFC libraries.


        RFC 1504:

        Title:      Appletalk Update-Based Routing Protocol:
                    Enhanced Appletalk Routing
        Author:     A. Oppenheimer
        Mailbox:    Oppenheime1@applelink.apple.com
        Pages:      82
        Characters: 20,1553
        Updates/Obsoletes:  none


This RFC provides detailed information about the AppleTalk
Update-based Routing Protocol (AURP) and wide area routing.  AURP
provides wide area routing enhancements to the AppleTalk routing
protocols and is fully compatible with AppleTalk Phase 2.  This memo
is being distributed to members of the Internet community to fully
document an Apple protocol that may be running over the Internet.
While the issues discussed may not be directly relevant to the
research problems of the Internet, they may be interesting to a number
of researchers and implementers.

This memo provides information for the Internet community.  It does
not specify an Internet standard.  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.INTERNIC.NET.  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.
ftp://ds.internic.net/rfc/rfc1504.txt"><ftp://ds.internic.net/rfc/rfc1504.txt>