draft-ietf-ion-ipv6-ind

Last Version:	draft-ietf-ion-ipv6-ind-05.txt		Tracker Entry
Date:	29-Mar-2004
Disposition:	non-current
Previous Versions:	draft-ietf-ion-ipv6-ind-05.txt (diff)    - 03-Dec-2001
	draft-ietf-ion-ipv6-ind-05.txt (diff)    - 15-Jun-2001
	draft-ietf-ion-ipv6-ind-04.txt (diff)    - 23-Nov-2000
	draft-ietf-ion-ipv6-ind-03.txt (diff)    - 19-Jul-2000
	draft-ietf-ion-ipv6-ind-02.txt (diff)    - 29-Oct-1999
	draft-ietf-ion-ipv6-ind-01.txt (diff)    - 01-Jul-1999
	draft-ietf-ion-ipv6-ind-00.txt (diff)    - 09-Apr-2002

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


        RFC 3122

        Title:      Extensions to IPv6 Neighbor Discovery for Inverse
                    Discovery Specification
        Author(s):  A. Conta
        Status:     Standards Track
        Date:       June 2001
        Mailbox:    aconta@txc.com
        Pages:      21
        Characters: 40416
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ion-ipv6-ind-05.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3122.txt


This memo describes extensions to the IPv6 Neighbor Discovery that
allow a node to determine and advertise an IPv6 address corresponding
to a given link-layer address.  These extensions are called Inverse
Neighbor Discovery.  The Inverse Neighbor Discovery (IND) was
originally developed for Frame Relay networks, but may also apply to
other networks with similar behavior.

This document is a product of the IPng 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.