[ipv6hackers] IPv6 temporary addresses (Fwd: New Version Notification for draft-ietf-6man-rfc4941bis-03.txt)

Fernando Gont fgont at si6networks.com
Thu Sep 5 14:50:50 CEST 2019


We are working in a revision of RFC4941, to address issues found in such

The current version of the revised spec is available at:

We'd really like to hear your comments and double-check if we got
everything right.

If possible, please post your feedback on the 6man list
(https://www.ietf.org/mailman/listinfo/ipv6). In any case, feedback
posted on this list or sent unicast to me is also welcome.



-------- Forwarded Message --------
Subject: New Version Notification for draft-ietf-6man-rfc4941bis-03.txt
Date: Thu, 05 Sep 2019 05:42:29 -0700
From: internet-drafts at ietf.org
To: Fernando Gont <fgont at si6networks.com>, Suresh Krishnan
<suresh.krishnan at ericsson.com>, Richard Draves <richdr at microsoft.com>,
Thomas Narten <narten at us.ibm.com>

A new version of I-D, draft-ietf-6man-rfc4941bis-03.txt
has been successfully submitted by Fernando Gont and posted to the
IETF repository.

Name:		draft-ietf-6man-rfc4941bis
Revision:	03
Title:		Privacy Extensions for Stateless Address Autoconfiguration in IPv6
Document date:	2019-09-05
Group:		6man
Pages:		21
Status:         https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4941bis/
Htmlized:       https://tools.ietf.org/html/draft-ietf-6man-rfc4941bis-03

   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.  This document
   describes an extension that causes nodes to generate global scope
   addresses with randomized interface identifiers that change over
   time.  Changing global scope addresses 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.  This document formally
   obsoletes RFC4941.

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

More information about the Ipv6hackers mailing list