[homenet] RFC 9526 on Simple Provisioning of Public Names for Residential Networks
rfc-editor@rfc-editor.org Mon, 29 January 2024 05:36 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 589FCC14F6B9; Sun, 28 Jan 2024 21:36:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.658
X-Spam-Level:
X-Spam-Status: No, score=-6.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EwhKDJtUaimm; Sun, 28 Jan 2024 21:36:44 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C868C14F6AB; Sun, 28 Jan 2024 21:36:44 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id EEE191F35FB0; Sun, 28 Jan 2024 21:36:43 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, homenet@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240129053643.EEE191F35FB0@rfcpa.amsl.com>
Date: Sun, 28 Jan 2024 21:36:43 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/SnpT5KjImanE3XY5yLIxwL6b088>
Subject: [homenet] RFC 9526 on Simple Provisioning of Public Names for Residential Networks
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jan 2024 05:36:48 -0000
A new Request for Comments is now available in online RFC libraries. RFC 9526 Title: Simple Provisioning of Public Names for Residential Networks Author: D. Migault, R. Weber, M. Richardson, R. Hunter Status: Experimental Stream: IETF Date: January 2024 Mailbox: daniel.migault@ericsson.com, ralf.weber@nominum.com, mcr+ietf@sandelman.ca, v6ops@globis.net Pages: 35 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-homenet-front-end-naming-delegation-27.txt URL: https://www.rfc-editor.org/info/rfc9526 DOI: 10.17487/RFC9526 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. This document is a product of the Home Networking Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC