RFC 4862 on IPv6 Stateless Address Autoconfiguration
rfc-editor@rfc-editor.org Mon, 24 September 2007 22:37 UTC
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IZwY0-0004KG-L0; Mon, 24 Sep 2007 18:37:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IZwXx-0004GH-R7; Mon, 24 Sep 2007 18:36:57 -0400
Received: from bosco.isi.edu ([128.9.168.207]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IZwXr-0007na-LX; Mon, 24 Sep 2007 18:36:57 -0400
Received: by bosco.isi.edu (Postfix, from userid 70) id B19C9E43CD; Mon, 24 Sep 2007 15:32:57 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20070924223257.B19C9E43CD@bosco.isi.edu>
Date: Mon, 24 Sep 2007 15:32:57 -0700
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: ipv6@ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 4862 on IPv6 Stateless Address Autoconfiguration
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org
A new Request for Comments is now available in online RFC libraries. RFC 4862 Title: IPv6 Stateless Address Autoconfiguration Author: S. Thomson, T. Narten, T. Jinmei Status: Standards Track Date: September 2007 Mailbox: sethomso@cisco.com, narten@us.ibm.com, jinmei@isl.rdc.toshiba.co.jp Pages: 30 Characters: 72482 Obsoletes: RFC2462 See-Also: I-D Tag: draft-ietf-ipv6-rfc2462bis-08.txt URL: http://www.rfc-editor.org/rfc/rfc4862.txt This document specifies the steps a host takes in deciding how to autoconfigure its interfaces in IP version 6. The autoconfiguration process includes generating a link-local address, generating global addresses via stateless address autoconfiguration, and the Duplicate Address Detection procedure to verify the uniqueness of the addresses on a link. [STANDARDS TRACK] This document is a product of the IP Version 6 Working Group Working Group of the IETF. This is now a Draft Standard Protocol. STANDARDS TRACK: 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. 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. The RFC Editor Team USC/Information Sciences Institute ... -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------