The Routing Over Large Clouds Mailing List Archive by date

[Andy Malis <malis@maelstrom.timeplex.com>]

You can all toss your copies of the NARP internet draft - the RFC is
You can all toss your copies of the NARP internet draft - the RFC is
now available.  As noted below, this is an experimental protocol that
now available.  As noted below, this is an experimental protocol that
was developed on the road to NHRP.

I am not aware of any completed and tested implementations.

Regards,
Andy
Andy
__________________________________________________________________________
Andrew G. Malis   malis@maelstrom.timeplex.com             +1 508 266-4522
Andrew G. Malis   malis@maelstrom.timeplex.com             +1 508 266-4522
Ascom Timeplex    289 Great Rd., Acton MA 01720 USA   FAX: +1 508 264-4999
Ascom Timeplex    289 Great Rd., Acton MA 01720 USA   FAX: +1 508 264-4999

------- Forwarded Message

To: IETF-Announce:;
To: IETF-Announce:;
Subject: RFC1735 on NBMA ARP (NARP)
Subject: RFC1735 on NBMA ARP (NARP)
Cc: jkrey@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Wed, 14 Dec 94 16:20:51 PST
Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US
Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US
From: "Joyce K. Reynolds" <jkrey@isi.edu>


- --NextPart


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


        RFC 1735:

        Title:      NBMA Address Resolution Protocol (NARP)
        Title:      NBMA Address Resolution Protocol (NARP)
        Author:     J. Heinanen & R. Govindan
        Author:     J. Heinanen & R. Govindan
        Mailbox:    Juha.Heinanen@datanet.tele.fi, govindan@isi.edu
        Pages:      11   
        Characters: 24,485
        Updates/Obsoletes:  none


This document describes the NBMA Address Resolution Protocol (NARP).
This document describes the NBMA Address Resolution Protocol (NARP).
NARP can be used by a source terminal (host or router) connected to a
NARP can be used by a source terminal (host or router) connected to a
Non-Broadcast, Multi-Access link layer (NBMA) network to find out the
Non-Broadcast, Multi-Access link layer (NBMA) network to find out the
NBMA addresses of the a destination terminal provided that the
NBMA addresses of the a destination terminal provided that the
destination terminal is connected to the same NBMA network.  Although
destination terminal is connected to the same NBMA network.  Although
this document focuses on NARP in the context of IP, the technique is
this document focuses on NARP in the context of IP, the technique is
applicable to other network layer protocols as well.  This RFC is a
product of the Routing over Large Clouds Working Group of the IETF.

IESG Note: Note that the work contained in this memo does not describe
an Internet standard.  This work represents an early stage in the
ongoing efforts to resolve direct communication over NBMA subnets.  It
ongoing efforts to resolve direct communication over NBMA subnets.  It
is a suitable experimental protocol for early deployment.  It is
expect that it will be superceded by other work being developed within
the IETF.

This memo defines an Experimental Protocol for the Internet community.
This memo does not specify an Internet standard of any kind.
Discussion and suggestions for improvement are requested.
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
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
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 
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 admin@DS.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 1543, Instructions to RFC
Authors, for further information.
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
implementation to automatically retrieve the ASCII version
of the RFCs.

- --NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

- --OtherAccess
- --OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="mailserv@ds.internic.net"

Content-Type: text/plain
Content-ID: <941214161807.RFC@ISI.EDU>

SEND /rfc/rfc1735.txt

- --OtherAccess
- --OtherAccess
Content-Type:   Message/External-body;
        name="rfc1735.txt";
        site="ds.internic.net";
        access-type="anon-ftp";
        directory="rfc"

Content-Type: text/plain
Content-ID: <941214161807.RFC@ISI.EDU>

- --OtherAccess--
- --OtherAccess--
- --NextPart--

------- End of Forwarded Message