Managing the Use of Privacy Extensions for Stateless Address Autoconfiguration in IPv6
draft-gont-6man-managing-privacy-extensions-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Fernando Gont , Ron Broersma | ||
| Last updated | 2011-03-12 (Latest revision 2011-03-07) | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes an operational problem that arises due to the impossibility of managing the use of "Privacy Extensions" for IPv6 Stateless Address Autoconfiguration (SLAAC) in network scenarios that employ SLAAC. Additionally, this document specifies new flag in the Prefix Information option of Router Advertisement messages, such that routers can advertise, for each network prefix to be used for SLAAC, whether the aforementioned "Privacy Extensions" should be used.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)