What would be the preferred way to provide a mixed list of IPv4 and IPv6
addresses, in a DHCPv6 option? IPv4-mapped addresses?
Or, is it assumed that any service which can be reached over IPv4 or
IPv6 by any given (dual-stack) client would use DNS FQDNs exclusively,
rather than addresses?
By the way, the list of RFCs enumerated in Section 5.1 includes both
4075 and 5908, but since 5908 deprecates 4075, it seems like only 1 of
them should be in any given (normative) list, not both.
- Kevin
On 9/19/2013 5:54 PM, The IESG wrote:
The IESG has received a request from the Dynamic Host Configuration WG
(dhc) to consider the following document:
- 'Guidelines for Creating New DHCPv6 Options'
<draft-ietf-dhc-option-guidelines-14.txt> as Best Current Practice
The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2013-10-03. Exceptionally, comments may be
sent to i...@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.
Abstract
This document provides guidance to prospective DHCPv6 Option
developers to help them creating option formats that are easily
adoptable by existing DHCPv6 software. This document updates
RFC3315.
The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-dhc-option-guidelines/
IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-dhc-option-guidelines/ballot/
No IPR declarations have been submitted directly on this I-D.
_______________________________________________
dhcwg mailing list
dh...@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg
