RFC 2603 on ILMI-Based Server Discovery for NHRP

RFC Editor <rfc-ed@ISI.EDU> Wed, 09 June 1999 23:16 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05458; Wed, 9 Jun 1999 19:16:59 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id TAA25453 for ietf-123-outbound.10@ietf.org; Wed, 9 Jun 1999 19:15:03 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id SAA25206 for <all-ietf@loki.ietf.org>; Wed, 9 Jun 1999 18:16:03 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04716 for <all-ietf@ietf.org>; Wed, 9 Jun 1999 18:12:22 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id PAA29543; Wed, 9 Jun 1999 15:12:24 -0700 (PDT)
Message-Id: <199906092212.PAA29543@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2603 on ILMI-Based Server Discovery for NHRP
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 09 Jun 1999 15:12:24 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 2603:

        Title:	    ILMI-Based Server Discovery for NHRP
	Author(s):  M. Davison
        Status:     Proposed Standard
	Date:       June 1999
        Mailbox:    mike.davison@cisco.com
        Pages:      6
        Characters: 11865
        Updates/Obsoletes/See Also: None  
        I-D Tag:    draft-ietf-ion-discov-nhrp-05.txt


        URL:        ftp://ftp.isi.edu/in-notes/rfc2603.txt


This memo defines how ILMI-based Server Discovery, which provides a
method for ATM-attached hosts and routers to dynamically determine the
ATM addresses of servers, shall be used to locate NHRP servers.

This document is a product of the Internetworking Over NBMA Working
Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) 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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        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 RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
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://ftp.isi.edu/in-notes/rfc2603.txt"><ftp://ftp.isi.edu/in-notes/rfc2603.txt>