< draft-ietf-homenet-naming-architecture-dhc-options-12.txt		draft-ietf-homenet-naming-architecture-dhc-options-13.txt >
	Homenet D. Migault		Homenet D. Migault
	Internet-Draft Ericsson		Internet-Draft Ericsson
	Intended status: Standards Track R. Weber		Intended status: Standards Track R. Weber
	Expires: October 30, 2021 Akamai		Expires: November 14, 2021 Akamai
	T. Mrugalski		T. Mrugalski
	Internet Systems Consortium, Inc.		Internet Systems Consortium, Inc.
	April 28, 2021		May 13, 2021
	DHCPv6 Options for Home Network Naming Authority		DHCPv6 Options for Home Network Naming Authority
	draft-ietf-homenet-naming-architecture-dhc-options-12		draft-ietf-homenet-naming-architecture-dhc-options-13
	Abstract		Abstract
	This document defines DHCPv6 options so an agnostic Homenet Naming		This document defines DHCPv6 options so an agnostic Homenet Naming
	Authority (HNA) can automatically proceed to the appropriate		Authority (HNA) can automatically proceed to the appropriate
	configuration and outsource the authoritative naming service for the		configuration and outsource the authoritative naming service for the
	home network. In most cases, the outsourcing mechanism is		home network. In most cases, the outsourcing mechanism is
	transparent for the end user.		transparent for the end user.
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 37 ¶		skipping to change at page 1, line 37 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at https://datatracker.ietf.org/drafts/current/.		Drafts is at https://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on October 30, 2021.		This Internet-Draft will expire on November 14, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 IETF Trust and the persons identified as the		Copyright (c) 2021 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 2, line 15 ¶		skipping to change at page 2, line 15 ¶
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3		2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
	3. Protocol Overview . . . . . . . . . . . . . . . . . . . . . . 3		3. Protocol Overview . . . . . . . . . . . . . . . . . . . . . . 3
	4. Payload Description . . . . . . . . . . . . . . . . . . . . . 4		4. Payload Description . . . . . . . . . . . . . . . . . . . . . 4
	4.1. Registered Homenet Domain Option . . . . . . . . . . . . 4		4.1. Registered Homenet Domain Option . . . . . . . . . . . . 4
	4.2. Distribution Master Option . . . . . . . . . . . . . . . 5		4.2. Distribution Manager Option . . . . . . . . . . . . . . . 5
	4.2.1. Supported Transport . . . . . . . . . . . . . . . . . 6		4.2.1. Supported Transport . . . . . . . . . . . . . . . . . 6
	4.3. Reverse Distribution Master Server Option . . . . . . . . 6		4.3. Reverse Distribution Manager Server Option . . . . . . . 6
	5. DHCP Behavior . . . . . . . . . . . . . . . . . . . . . . . . 7		5. DHCP Behavior . . . . . . . . . . . . . . . . . . . . . . . . 7
	5.1. DHCPv6 Server Behavior . . . . . . . . . . . . . . . . . 7		5.1. DHCPv6 Server Behavior . . . . . . . . . . . . . . . . . 7
	5.2. DHCPv6 Client Behavior . . . . . . . . . . . . . . . . . 7		5.2. DHCPv6 Client Behavior . . . . . . . . . . . . . . . . . 7
	5.3. DHCPv6 Relay Agent Behavior . . . . . . . . . . . . . . . 7		5.3. DHCPv6 Relay Agent Behavior . . . . . . . . . . . . . . . 7
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 8		7. Security Considerations . . . . . . . . . . . . . . . . . . . 8
	8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8		8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
	9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 8		9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 8
	10. References . . . . . . . . . . . . . . . . . . . . . . . . . 8		10. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
	10.1. Normative References . . . . . . . . . . . . . . . . . . 8		10.1. Normative References . . . . . . . . . . . . . . . . . . 8
	skipping to change at page 3, line 20 ¶		skipping to change at page 3, line 20 ¶
	This document shows how an ISP can provision automatically the HNA		This document shows how an ISP can provision automatically the HNA
	with a specific DOI. Most likely the DOI will be - at least partly		with a specific DOI. Most likely the DOI will be - at least partly
	be - managed or provided by its ISP, but other cases may envision the		be - managed or provided by its ISP, but other cases may envision the
	ISP storing some configuration so the homenet becomes resilient to		ISP storing some configuration so the homenet becomes resilient to
	HNA replacement.		HNA replacement.
	The ISP delegates the home network an IP prefix it owns as well as		The ISP delegates the home network an IP prefix it owns as well as
	the associated reverse zone. The ISP is well aware of the owner of		the associated reverse zone. The ISP is well aware of the owner of
	that prefix, and as such becomes a natural candidate for hosting the		that prefix, and as such becomes a natural candidate for hosting the
	Homenet Reverse Zone - that is the Reverse Distribution Master (RDM)		Homenet Reverse Zone - that is the Reverse Distribution Manager (RDM)
	and potentially the Reverse Public Authoritative Servers.		and potentially the Reverse Public Authoritative Servers.
	In addition, the ISP often identifies the home network with a name.		In addition, the ISP often identifies the home network with a name.
	In most cases, the name is used by the ISP for its internal network		In most cases, the name is used by the ISP for its internal network
	management operations and is not a name the home network owner has		management operations and is not a name the home network owner has
	registered to. The ISP may thus leverage such infrastructure and		registered to. The ISP may thus leverage such infrastructure and
	provide the homenet a specific domain name designated as per		provide the homenet a specific domain name designated as per
	[I-D.ietf-homenet-front-end-naming-delegation] a Homenet Registered		[I-D.ietf-homenet-front-end-naming-delegation] a Homenet Registered
	Domain. Similarly to the reverse zone, the ISP is well aware of who		Domain. Similarly to the reverse zone, the ISP is well aware of who
	owns that domain name and may become a natural candidate for hosting		owns that domain name and may become a natural candidate for hosting
	the Homenet Zone - that is the Distribution Master (DM) and the		the Homenet Zone - that is the Distribution Manager (DM) and the
	Public Authoritative Servers.		Public Authoritative Servers.
	This document describes DHCPv6 options that enables the ISP to		This document describes DHCPv6 options that enables the ISP to
	provide the necessary parameters to the HNA, to proceed. More		provide the necessary parameters to the HNA, to proceed. More
	specifically, the ISP provides the Registered Homenet Domain,		specifically, the ISP provides the Registered Homenet Domain,
	necessary information on the DM and the RDM so the HNA can manage and		necessary information on the DM and the RDM so the HNA can manage and
	upload the Public Homenet Zone and the Reverse Public Homenet Zone as		upload the Public Homenet Zone and the Reverse Public Homenet Zone as
	described in [I-D.ietf-homenet-front-end-naming-delegation].		described in [I-D.ietf-homenet-front-end-naming-delegation].
	The use of DHCPv6 options makes the configuration completely		The use of DHCPv6 options makes the configuration completely
	skipping to change at page 4, line 22 ¶		skipping to change at page 4, line 22 ¶
	DHCP Server does not have privileged relations with the DM or RDM.		DHCP Server does not have privileged relations with the DM or RDM.
	These cases are discussed latter in Appendix A. Such scenarios do		These cases are discussed latter in Appendix A. Such scenarios do
	not necessarily require configuration for the end user and can also		not necessarily require configuration for the end user and can also
	be zero-config.		be zero-config.
	The scenario considered in this section is as follows:		The scenario considered in this section is as follows:
	1. The HNA is willing to outsource the Public Homenet Zone or		1. The HNA is willing to outsource the Public Homenet Zone or
	Homenet Reverse Zone and configures its DHCP Client to include in		Homenet Reverse Zone and configures its DHCP Client to include in
	its Option Request Option (ORO) the Registered Homenet Domain		its Option Request Option (ORO) the Registered Homenet Domain
	Option (OPTION_REGISTERED_DOMAIN), the Distribution Master Option		Option (OPTION_REGISTERED_DOMAIN), the Distribution Manager
	(OPTION_DIST_MASTER) and the Reverse Distribution Master Option		Option (OPTION_DIST_MANAGER) and the Reverse Distribution Manager
	(OPTION_REVERSE_DIST_MASTER) option codes.		Option (OPTION_REVERSE_DIST_MANAGER) option codes.
	2. The DHCP Server responds to the HNA with the requested DHCPv6		2. The DHCP Server responds to the HNA with the requested DHCPv6
	options based on the identified homenet. The DHCP Client		options based on the identified homenet. The DHCP Client
	transmits the information to the HNA.		transmits the information to the HNA.
	3. The HNA is able to get authenticated by the DM and the RDM. The		3. The HNA is able to get authenticated by the DM and the RDM. The
	HNA builds the Homenet Zone ( resp. the Homenet Reverse Zone) and		HNA builds the Homenet Zone ( resp. the Homenet Reverse Zone) and
	proceed as described in		proceed as described in
	[I-D.ietf-homenet-front-end-naming-delegation]. The DHCPv6		[I-D.ietf-homenet-front-end-naming-delegation]. The DHCPv6
	options provide the necessary and non optional parameters		options provide the necessary and non optional parameters
	skipping to change at page 5, line 26 ¶		skipping to change at page 5, line 26 ¶
	o option-code (16 bits): OPTION_REGISTERED_DOMAIN, the option code		o option-code (16 bits): OPTION_REGISTERED_DOMAIN, the option code
	for the Registered Homenet Domain (TBD2).		for the Registered Homenet Domain (TBD2).
	o option-len (16 bits): length in octets of the option-data field as		o option-len (16 bits): length in octets of the option-data field as
	described in [RFC8415].		described in [RFC8415].
	o Registered Homenet Domain (variable): the FQDN registered for the		o Registered Homenet Domain (variable): the FQDN registered for the
	homenet encoded as described in section 10 of [RFC8415].		homenet encoded as described in section 10 of [RFC8415].
	4.2. Distribution Master Option		4.2. Distribution Manager Option
	The Distributed Master Option (OPTION_DIST_MASTER) provides the HNA		The Distributed Manager Option (OPTION_DIST_MANAGER) provides the HNA
	to FQDN of the DM as well as the transport protocol for the		to FQDN of the DM as well as the transport protocol for the
	transaction between the HNA and the DM.		transaction between the HNA and the DM.
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| OPTION_DIST_MASTER | option-len |		| OPTION_DIST_MANAGER | option-len |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Supported Transport | |		| Supported Transport | |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
	| |		| |
	/ Distribution Master FQDN /		/ Distribution Manager FQDN /
	| |		| |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 2: Distribution Master Option		Figure 2: Distribution Manager Option
	o option-code (16 bits): OPTION_DIST_MASTER, the option code for the		o option-code (16 bits): OPTION_DIST_MANAGER, the option code for
	DM Option (TBD3).		the Distribution Manager Option (TBD2).
	o option-len (16 bits): length in octets of the option-data field as		o option-len (16 bits): length in octets of the option-data field as
	described in [RFC8415].		described in [RFC8415].
	o Supported Transport (16 bits): defines the supported transport by		o Supported Transport (16 bits): defines the supported transport by
	the DM. Each bit represents a supported transport, and a DM MAY		the DM. Each bit represents a supported transport, and a DM MAY
	indicate the support of multiple modes. The bit for DNS over TLS		indicate the support of multiple modes. The bit for DNS over TLS
	[RFC7858] MUST be set.		[RFC7858] MUST be set.
	o Distribution Master FQDN (variable): the FQDN of the DM encoded as		o Distribution Manager FQDN (variable): the FQDN of the DM encoded
	described in section 10 of [RFC8415].		as described in section 10 of [RFC8415].
	4.2.1. Supported Transport		4.2.1. Supported Transport
	The Supported Transport filed of the DHCPv6 option indicates the		The Supported Transport filed of the DHCPv6 option indicates the
	supported transport protocol. Each bit represents a specific		supported transport protocol. Each bit represents a specific
	transport mechanism. The bit sets to 1 indicates the associated		transport mechanism. The bit sets to 1 indicates the associated
	transport protocol is supported. The corresponding bits are assigned		transport protocol is supported. The corresponding bits are assigned
	as described in Figure 3.		as described in Figure 3.
	Bit | Transport Protocol | Reference		Bit | Transport Protocol | Reference
	----+--------------------+-----------		----+--------------------+-----------
	0 | DNS over TLS | This-RFC		0 | DNS over TLS | This-RFC
	1-15| unallocated |		1-15| unallocated |
	Figure 3: Supported Transport		Figure 3: Supported Transport
	o DNS over TLS: indicates the support of DNS over TLS as described		o DNS over TLS: indicates the support of DNS over TLS as described
	in [RFC7858].		in [RFC7858].
	4.3. Reverse Distribution Master Server Option		4.3. Reverse Distribution Manager Server Option
	The Reverse Distribution Master Server Option		The Reverse Distribution Manager Server Option
	(OPTION_REVERSE_DIST_MASTER) provides the HNA to FQDN of the DM as		(OPTION_REVERSE_DIST_MANAGER) provides the HNA to FQDN of the DM as
	well as the transport protocol for the transaction between the HNA		well as the transport protocol for the transaction between the HNA
	and the DM.		and the DM.
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| OPTION_REVERSE_DIST_MASTER | option-len |		| OPTION_REVERSE_DIST_MANAGER | option-len |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Supported Transport | |		| Supported Transport | |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
	| |		| |
	/ Reverse Distribution Master FQDN /		/ Reverse Distribution Manager FQDN /
	| |		| |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 4: Reverse Distribution Master Option		Figure 4: Reverse Distribution Manager Option
	o option-code (16 bits): OPTION_REVERSE_DIST_MASTER, the option code		o option-code (16 bits): OPTION_REVERSE_DIST_MANAGER, the option
	for the Reverse Distribution Master Option (TBD4).		code for the Reverse Distribution Manager Option (TBD3).
	o option-len (16 bits): length in octets of the option-data field as		o option-len (16 bits): length in octets of the option-data field as
	described in [RFC8415].		described in [RFC8415].
	o Supported Transport (16 bits): defines the supported transport by		o Supported Transport (16 bits): defines the supported transport by
	the DM. Each bit represents a supported transport, and a DM MAY		the RDM. Each bit represents a supported transport, and a DM MAY
	indicate the support of multiple modes. The bit for DoT MUST be		indicate the support of multiple modes. The bit for DoT MUST be
	set.		set.
	o Reverse Distribution Master FQDN (variable): the FQDN of the RDM		o Reverse Distribution Manager FQDN (variable): the FQDN of the RDM
	encoded as described in section 10 of [RFC8415].		encoded as described in section 10 of [RFC8415].
	5. DHCP Behavior		5. DHCP Behavior
	5.1. DHCPv6 Server Behavior		5.1. DHCPv6 Server Behavior
	Sections 17.2.2 and 18.2 of [RFC8415] govern server operation in		Sections 17.2.2 and 18.2 of [RFC8415] govern server operation in
	regards to option assignment. As a convenience to the reader, we		regards to option assignment. As a convenience to the reader, we
	mention here that the server will send option foo only if configured		mention here that the server will send option foo only if configured
	with specific values for foo and if the client requested it. In		with specific values for foo and if the client requested it. In
	particular, when configured the DHCP Server sends the Registered		particular, when configured the DHCP Server sends the Registered
	Homenet Domain Option, Distribution Master Option, the Reverse		Homenet Domain Option, Distribution Manager Option, the Reverse
	Distribution Master Option when requested by the DHCPv6 client by		Distribution Manager Option when requested by the DHCPv6 client by
	including necessary option codes in its ORO.		including necessary option codes in its ORO.
	5.2. DHCPv6 Client Behavior		5.2. DHCPv6 Client Behavior
	The DHCPv6 client sends a ORO with the necessary option codes:		The DHCPv6 client sends a ORO with the necessary option codes:
	Registered Homenet Domain Option, Distribution Master Option, the		Registered Homenet Domain Option, Distribution Manager Option, the
	Reverse Distribution Master Option.		Reverse Distribution Manager Option.
	Upon receiving a DHCP option described in this document in the Reply		Upon receiving a DHCP option described in this document in the Reply
	message, the HNA SHOULD proceed as described in		message, the HNA SHOULD proceed as described in
	[I-D.ietf-homenet-front-end-naming-delegation].		[I-D.ietf-homenet-front-end-naming-delegation].
	5.3. DHCPv6 Relay Agent Behavior		5.3. DHCPv6 Relay Agent Behavior
	There are no additional requirements for the DHCP Relay agents.		There are no additional requirements for the DHCP Relay agents.
	6. IANA Considerations		6. IANA Considerations
	IANA is requested to assign the following new DHCPv6 Option Codes in		IANA is requested to assign the following new DHCPv6 Option Codes in
	the registry maintained in: https://www.iana.org/assignments/dhcpv6-		the registry maintained in: https://www.iana.org/assignments/dhcpv6-
	parameters/dhcpv6-parameters.xhtml#dhcpv6-parameters-2.		parameters/dhcpv6-parameters.xhtml#dhcpv6-parameters-2.
	Value Description Client ORO Singleton Option		Value Description Client ORO Singleton Option
	TBD1 OPTION_REGISTERED_DOMAIN Yes Yes		TBD1 OPTION_REGISTERED_DOMAIN Yes Yes
	TBD2 OPTION_DIST_MASTER Yes Yes		TBD2 OPTION_DIST_MANAGER Yes Yes
	TBD3 OPTION_REVERSE_DIST_MASTER Yes Yes		TBD3 OPTION_REVERSE_DIST_MANAGER Yes Yes
	IANA is requested to maintain a new number space of Supported		IANA is requested to maintain a new number space of Supported
	Transport parameter in the Distributed Master Option		Transport parameter in the Distributed Manager Option
	(OPTION_DIST_MASTER) or the Reverse Distribution Master Server Option		(OPTION_DIST_MANAGER) or the Reverse Distribution Manager Server
	(OPTION_REVERSE_DIST_MASTER). The different parameters are defined		Option (OPTION_REVERSE_DIST_MANAGER). The different parameters are
	in Figure 3 in Section 4.2.1. Future code points are assigned under		defined in Figure 3 in Section 4.2.1. Future code points are
	Specification Required as per [RFC8126].		assigned under Specification Required as per [RFC8126].
	7. Security Considerations		7. Security Considerations
	The security considerations in [RFC2131] and [RFC8415] are to be		The security considerations in [RFC2131] and [RFC8415] are to be
	considered. The use of DHCPv6 options provides a similar level of		considered. The use of DHCPv6 options provides a similar level of
	trust as the one used to provide the IP prefix. The link between the		trust as the one used to provide the IP prefix. The link between the
	HNA and the DHCPv6 server may benefit from additional security for		HNA and the DHCPv6 server may benefit from additional security for
	example by using [I-D.ietf-dhc-sedhcpv6].		example by using [I-D.ietf-dhc-sedhcpv6].
	8. Acknowledgments		8. Acknowledgments
	skipping to change at page 10, line 6 ¶		skipping to change at page 10, line 6 ¶
	Andrews, M., "Automated Delegation of IP6.ARPA reverse		Andrews, M., "Automated Delegation of IP6.ARPA reverse
	zones with Prefix Delegation", draft-andrews-dnsop-pd-		zones with Prefix Delegation", draft-andrews-dnsop-pd-
	reverse-02 (work in progress), November 2013.		reverse-02 (work in progress), November 2013.
	[I-D.ietf-dhc-sedhcpv6]		[I-D.ietf-dhc-sedhcpv6]
	Li, L., Jiang, S., Cui, Y., Jinmei, T., Lemon, T., and D.		Li, L., Jiang, S., Cui, Y., Jinmei, T., Lemon, T., and D.
	Zhang, "Secure DHCPv6", draft-ietf-dhc-sedhcpv6-21 (work		Zhang, "Secure DHCPv6", draft-ietf-dhc-sedhcpv6-21 (work
	in progress), February 2017.		in progress), February 2017.
	[I-D.ietf-homenet-front-end-naming-delegation]		[I-D.ietf-homenet-front-end-naming-delegation]
	Migault, D., Weber, R., Richardson, M., Hunter, R.,		Migault, D., Weber, R., Richardson, M., and R. Hunter,
	Griffiths, C., and W. Cloetens, "Simple Provisioning of		"Simple Provisioning of Public Names for Residential
	Public Names for Residential Networks", draft-ietf-		Networks", draft-ietf-homenet-front-end-naming-
	homenet-front-end-naming-delegation-13 (work in progress),		delegation-14 (work in progress), April 2021.
	March 2021.
	[I-D.sury-dnsext-cname-dname]		[I-D.sury-dnsext-cname-dname]
	Sury, O., "CNAME+DNAME Name Redirection", draft-sury-		Sury, O., "CNAME+DNAME Name Redirection", draft-sury-
	dnsext-cname-dname-00 (work in progress), April 2010.		dnsext-cname-dname-00 (work in progress), April 2010.
	Appendix A. Scenarios and impact on the End User		Appendix A. Scenarios and impact on the End User
	This section details various scenarios and discuss their impact on		This section details various scenarios and discuss their impact on
	the end user. This section is not normative and limits the		the end user. This section is not normative and limits the
	description of a limited scope of scenarios that are assumed to be		description of a limited scope of scenarios that are assumed to be
End of changes. 29 change blocks.
	47 lines changed or deleted		46 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/