[rfc-dist] RFC 4941 on Privacy Extensions for Stateless Address Autoconfiguration in IPv6

[rfc-editor@rfc-editor.org]

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

        
        RFC 4941

        Title:      Privacy Extensions for Stateless Address 
                    Autoconfiguration in IPv6 
        Author:     T. Narten, R. Draves,
                    S. Krishnan
        Status:     Standards Track
        Date:       September 2007
        Mailbox:    narten at us.ibm.com, 
                    richdr at microsoft.com, 
                    suresh.krishnan at ericsson.com
        Pages:      23
        Characters: 56699
        Obsoletes:  RFC3041
        See-Also:   

        I-D Tag:    draft-ietf-ipv6-privacy-addrs-v2-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4941.txt

Nodes use IPv6 stateless address autoconfiguration to generate
addresses using a combination of locally available information and
information advertised by routers.  Addresses are formed by combining
network prefixes with an interface identifier.  On an interface that
contains an embedded IEEE Identifier, the interface identifier is
typically derived from it.  On other interface types, the interface
identifier is generated through other means, for example, via random
number generation.  This document describes an extension to IPv6
stateless address autoconfiguration for interfaces whose interface
identifier is derived from an IEEE identifier.  Use of the extension
causes nodes to generate global scope addresses from interface
identifiers that change over time, even in cases where the interface
contains an embedded IEEE identifier.  Changing the interface
identifier (and the global scope addresses generated from it) over
time makes it more difficult for eavesdroppers and other information
collectors to identify when different addresses used in different
transactions actually correspond to the same node.  [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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at 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 at 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 at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...