DHCPv6/SLAAC Interaction Implementation Guidance
draft-liu-6man-dhcpv6-slaac-implementation-guide-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Bing Liu , Ron Bonica | ||
| Last updated | 2014-08-18 (Latest revision 2014-02-14) | ||
| RFC stream | (None) | ||
| Intended RFC status | (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
ND and DHCPv6 protocols could have some interaction on address provisioning with the A, M, and O flags defined in ND protocol. But the relevant standard definitions of the flags contain ambiguity, so that current implementations in operating systems have varied on interpreting the flags. The variation might impact real network operations, so this document aims to provide some guidance on what should be the proper implementation on the interaction behavior.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)