DHCPv6 Extension Practices and Considerations
draft-rhl-dhc-dhcpv6-extensions-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ren Gang , Lin He , Ying Liu | ||
| Last updated | 2023-12-31 (Latest revision 2023-06-29) | ||
| Replaces | draft-ietf-dhc-problem-statement-of-mredhcpv6 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Reviews |
OPSDIR Last Call review
(of
draft-ietf-dhc-problem-statement-of-mredhcpv6
-05)
by Nagendra Nainar
Has issues
|
||
| 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
IP addresses assume an increasing number of attributes as communication identifiers to meet different requirements. Privacy protection, accountability, security, and manageability of networks can be supported by extending the DHCPv6 protocol as required. This document provides current extension practices and typical DHCPv6 server software in terms of extensions, defines a general model of DHCPv6, discusses some extension points, and presents extension cases.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)