rfc9526v4.txt		rfc9526.txt
	Internet Engineering Task Force (IETF) D. Migault		Internet Engineering Task Force (IETF) D. Migault
	Request for Comments: 9526 Ericsson		Request for Comments: 9526 Ericsson
	Category: Experimental R. Weber		Category: Experimental R. Weber
	ISSN: 2070-1721 Nominum		ISSN: 2070-1721 Nominum
	M. Richardson		M. Richardson
	Sandelman Software Works		Sandelman Software Works
	R. Hunter		R. Hunter
	Globis Consulting BV		Globis Consulting BV
	December 2023		January 2024
	Simple Provisioning of Public Names for Residential Networks		Simple Provisioning of Public Names for Residential Networks
	Abstract		Abstract
	Home network owners may have devices or services hosted on their home		Home network owners may have devices or services hosted on their home
	network that they wish to access from the Internet (i.e., from a		network that they wish to access from the Internet (i.e., from a
	network outside of the home network). Home networks are increasingly		network outside of the home network). Home networks are increasingly
	numbered using IPv6 addresses, which in principle makes this access		numbered using IPv6 addresses, which in principle makes this access
	simpler, but accessing home networks from the Internet requires the		simpler, but accessing home networks from the Internet requires the
	skipping to change at line 51 ¶		skipping to change at line 51 ¶
	publication by the Internet Engineering Steering Group (IESG). Not		publication by the Internet Engineering Steering Group (IESG). Not
	all documents approved by the IESG are candidates for any level of		all documents approved by the IESG are candidates for any level of
	Internet Standard; see Section 2 of RFC 7841.		Internet Standard; see Section 2 of RFC 7841.
	Information about the current status of this document, any errata,		Information about the current status of this document, any errata,
	and how to provide feedback on it may be obtained at		and how to provide feedback on it may be obtained at
	https://www.rfc-editor.org/info/rfc9526.		https://www.rfc-editor.org/info/rfc9526.
	Copyright Notice		Copyright Notice
	Copyright (c) 2023 IETF Trust and the persons identified as the		Copyright (c) 2024 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
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Revised BSD License text as described in Section 4.e of the		include Revised BSD License text as described in Section 4.e of the
	Trust Legal Provisions and are provided without warranty as described		Trust Legal Provisions and are provided without warranty as described
	skipping to change at line 925 ¶		skipping to change at line 925 ¶
	* a service provided by the HNA at port 853.		* a service provided by the HNA at port 853.
	As a result, even though the same pair of IP addresses may be		As a result, even though the same pair of IP addresses may be
	involved, the Control Channel and the Synchronization Channel are		involved, the Control Channel and the Synchronization Channel are
	always distinct channels.		always distinct channels.
	Uploading and dynamically updating the zone file on the DM can be		Uploading and dynamically updating the zone file on the DM can be
	seen as zone provisioning between the HNA (hidden primary server) and		seen as zone provisioning between the HNA (hidden primary server) and
	the DM (secondary server). This is handled using the normal zone		the DM (secondary server). This is handled using the normal zone
	transfer mechanism involving the AXFR and IXFR.		transfer mechanism involving the AXFR and Incremental Zone Transfer
			(IXFR).
	Part of the process to update the zone involves the owner of the zone		Part of the process to update the zone involves the owner of the zone
	(the hidden primary server, the HNA) sending a DNS Notify to the		(the hidden primary server, the HNA) sending a DNS Notify to the
	secondaries. In this situation, the only destination that is known		secondaries. In this situation, the only destination that is known
	by the HNA is the DM's Control Channel, so DNS Notifies are sent over		by the HNA is the DM's Control Channel, so DNS Notifies are sent over
	the Control Channel, secured by a mutually authenticated TLS.		the Control Channel, secured by a mutually authenticated TLS.
	Please note that DNS Notifies are not critical to normal operation,		Please note that DNS Notifies are not critical to normal operation,
	as the DM will be checking the zone regularly based upon SOA record		as the DM will be checking the zone regularly based upon SOA record
	comments. DNS Notifies do speed things up as they cause the DM to		comments. DNS Notifies do speed things up as they cause the DM to
	skipping to change at line 1068 ¶		skipping to change at line 1069 ¶
	WAN interface (by DHCPv6 or PPP with Router Advertisement (RA)), then		WAN interface (by DHCPv6 or PPP with Router Advertisement (RA)), then
	the HNA should originate Synchronization Channel updates from, for		the HNA should originate Synchronization Channel updates from, for
	example, 2001:db8:f00d:1234::2.		example, 2001:db8:f00d:1234::2.
	If an ISP has delegated 2001:db8:aeae::/56 to the HNA via DHCPv6-PD,		If an ISP has delegated 2001:db8:aeae::/56 to the HNA via DHCPv6-PD,
	then the HNA should originate Synchronization Channel updates to an		then the HNA should originate Synchronization Channel updates to an
	IP address within that subnet, such as 2001:db8:aeae:1::2.		IP address within that subnet, such as 2001:db8:aeae:1::2.
	With this relation automatically configured, the synchronization		With this relation automatically configured, the synchronization
	between the Home network and the DOI happens in a similar way to the		between the Home network and the DOI happens in a similar way to the
	synchronziation of the Public Homenet Zone described earlier in this		synchronization of the Public Homenet Zone described earlier in this
	document.		document.
	Note that for home networks connected to multiple ISPs, each ISP		Note that for home networks connected to multiple ISPs, each ISP
	provides only the DOI of the reverse zones associated with the		provides only the DOI of the reverse zones associated with the
	delegated prefix. It is also likely that the DNS exchanges will need		delegated prefix. It is also likely that the DNS exchanges will need
	to be performed on dedicated interfaces to be accepted by the ISP.		to be performed on dedicated interfaces to be accepted by the ISP.
	More specifically, the reverse zone update associated with prefix 1		More specifically, the reverse zone update associated with prefix 1
	cannot be performed by the HNA using an IP address that belongs to		cannot be performed by the HNA using an IP address that belongs to
	prefix 2. Such constraints do not raise major concerns for hot		prefix 2. Such constraints do not raise major concerns for hot
	standby or load-sharing configuration.		standby or load-sharing configuration.
	skipping to change at line 1640 ¶		skipping to change at line 1641 ¶
	Dedicated QUIC Connections", RFC 9250,		Dedicated QUIC Connections", RFC 9250,
	DOI 10.17487/RFC9250, May 2022,		DOI 10.17487/RFC9250, May 2022,
	<https://www.rfc-editor.org/info/rfc9250>.		<https://www.rfc-editor.org/info/rfc9250>.
	[RFC9276] Hardaker, W. and V. Dukhovni, "Guidance for NSEC3		[RFC9276] Hardaker, W. and V. Dukhovni, "Guidance for NSEC3
	Parameter Settings", BCP 236, RFC 9276,		Parameter Settings", BCP 236, RFC 9276,
	DOI 10.17487/RFC9276, August 2022,		DOI 10.17487/RFC9276, August 2022,
	<https://www.rfc-editor.org/info/rfc9276>.		<https://www.rfc-editor.org/info/rfc9276>.
	[RFC9527] Migault, D., Weber, R., and T. Mrugalski, "DHCPv6 Options		[RFC9527] Migault, D., Weber, R., and T. Mrugalski, "DHCPv6 Options
	for Home Network Naming Authority", RFC 9527,		for the Homenet Naming Authority", RFC 9527,
	DOI 10.17487/RFC9527, December 2023,		DOI 10.17487/RFC9527, January 2024,
	<https://www.rfc-editor.org/info/rfc9527>.		<https://www.rfc-editor.org/info/rfc9527>.
	[ZONEENUM] Wang, Z., Xiao, L., and R. Wang, "An efficient DNSSEC zone		[ZONEENUM] Wang, Z., Xiao, L., and R. Wang, "An efficient DNSSEC zone
	enumeration algorithm", DOI 10.2495/MIIT130591, April		enumeration algorithm", DOI 10.2495/MIIT130591, April
	2014, <https://doi.org/10.2495/MIIT130591>.		2014, <https://doi.org/10.2495/MIIT130591>.
	Appendix A. HNA Channel Configurations		Appendix A. HNA Channel Configurations
	A.1. Public Homenet Zone		A.1. Public Homenet Zone
End of changes. 5 change blocks.
	6 lines changed or deleted		7 lines changed or added
This html diff was produced by rfcdiff 1.48.