RFC 9526: Simple Provisioning of Public Names for Residential Networks
In plain English — editorial summary, not part of the RFC
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 outside of the home network). Home networks are increasingly numbered using IPv6 addresses, which in principle makes this access simpler, but accessing home networks from the Internet requires the names and IP addresses of these devices and services to be made available in the public DNS. This document describes how a Home Naming Authority (NHA) instructs the outsourced infrastructure to publish these pieces of information in the public DNS. The names and IP addresses of the home network are set in the Public Homenet Zone by the Homenet Naming Authority (HNA), which in turn instructs an outsourced infrastructure to publish the zone on behalf of the home network owner.
Document record
- Document ID
- RFC9526
- Published
- January 2024
- Authors
- D. Migault; R. Weber; M. Richardson; R. Hunter
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- int
- Pages
- 35
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6168Requirements for Management of Name Servers for the DNSCurrent
May 2011
- RFC 9527DHCPv6 Options for the Homenet Naming AuthorityCurrent
January 2024
- RFC 9539Unilateral Opportunistic Deployment of Encrypted Recursive-to-Authoritative DNSCurrent
February 2024
- RFC 9463DHCP and Router Advertisement Options for the Discovery of Network-designated Resolvers (DNR)Current
November 2023
- RFC 9462Discovery of Designated ResolversCurrent
November 2023
- RFC 9250DNS over Dedicated QUIC ConnectionsCurrent
May 2022
- RFC 9243A YANG Data Model for DHCPv6 ConfigurationCurrent
June 2022
- RFC 9103DNS Zone Transfer over TLSCurrent
August 2021
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?