On the Dynamic/Automatic Configuration of IPv6 Hosts
draft-gont-v6ops-host-configuration-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2017-09-14 (latest revision 2017-03-13) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-gont-v6ops-host-configuration-01.txt
Abstract
IPv6 has two different mechanisms for dynamic/automatic host configuration: SLAAC and DHCPv6. These two mechanisms allow for the configuration of IPv6 addresses and a number of network parameters. While there is overlap in the parameters that can be configured via these two protocols, different implementations support only subsets of such parameters with either mechanism, or have no support for DHCPv6 at all. This document analyzes a problem that arises from this situation, and mandates that all host implementations support RFC 6105 (DNS options for SLAAC) and the stateless DHCPv6 functionality in RFC 3315.
Authors
Fernando Gont
(fgont@si6networks.com)
Gert Doering
(gert@space.net)
Madelen Corbo
(madelen.garcia16@gmail.com)
Guillermo Gont
(ggont@si6networks.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)