FYI. Regards, Thomas Trede -----Original Message----- From: RFC Editor (by way of Bob Hinden <hinden@iprg.nokia.com>) <rfc-ed@ISI.EDU> To: ipng@sunroof.Eng.Sun.COM <ipng@sunroof.Eng.Sun.COM> Date: Donnerstag, 3. Dezember 1998 19:00 Subject: (IPng 6825) RFC 2462 on IPv6 Stateless Address Autoconfiguration
A new Request for Comments is now available in online RFC libraries.
RFC 2462:
Title: IPv6 Stateless Address Autoconfiguration Author(s): S. Thomson, T. Narten Status: Draft Standard Date: December 1998 Mailbox: set@thumper.bellcore.com, narten@raleigh.ibm.com Pages: 25 Characters: 61210 Obsoletes: 1971 I-D Tag: draft-ietf-ipngwg-addrconf-v2-02.txt
URL: ftp://ftp.isi.edu/in-notes/rfc2462.txt
This document specifies the steps a host takes in deciding how to autoconfigure its interfaces in IP version 6. The autoconfiguration process includes creating a link-local address and verifying its uniqueness on a link, determining what information should be autoconfigured (addresses, other information, or both), and in the case of addresses, whether they should be obtained through the stateless mechanism, the stateful mechanism, or both. This document defines the process for generating a link-local address, the process for generating site-local and global addresses via stateless address autoconfiguration, and the Duplicate Address Detection procedure. The details of autoconfiguration using the stateful protocol are specified elsewhere.
This document is a product of the IPNG Working Group of the IETF.
This is now a Draft 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. Content-Type: text/plain Content-ID: <981202153022.RFC@RFC-EDITOR.ORG>
RETRIEVE: rfc DOC-ID: rfc2462
<ftp://ftp.isi.edu/in-notes/rfc2462.txt>
-------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to majordomo@sunroof.eng.sun.com --------------------------------------------------------------------