| rfc9527v4.txt | rfc9527.txt | |||
|---|---|---|---|---|
| Internet Engineering Task Force (IETF) D. Migault | Internet Engineering Task Force (IETF) D. Migault | |||
| Request for Comments: 9527 Ericsson | Request for Comments: 9527 Ericsson | |||
| Category: Standards Track R. Weber | Category: Standards Track R. Weber | |||
| ISSN: 2070-1721 Akamai | ISSN: 2070-1721 Akamai | |||
| T. Mrugalski | T. Mrugalski | |||
| ISC | ISC | |||
| December 2023 | January 2024 | |||
| DHCPv6 Options for the Homenet Naming Authority | DHCPv6 Options for the Homenet Naming Authority | |||
| Abstract | Abstract | |||
| This document defines DHCPv6 options so that a Homenet Naming | This document defines DHCPv6 options so that a Homenet Naming | |||
| Authority (HNA) can automatically set the appropriate configuration | Authority (HNA) can automatically set the appropriate configuration | |||
| and outsource the authoritative naming service for the home network. | and outsource the authoritative naming service for the home network. | |||
| In most cases, the outsourcing mechanism is transparent for the end | In most cases, the outsourcing mechanism is transparent for the end | |||
| user. | user. | |||
| skipping to change at line 36 ¶ | skipping to change at line 36 ¶ | |||
| received public review and has been approved for publication by the | received public review and has been approved for publication by the | |||
| Internet Engineering Steering Group (IESG). Further information on | Internet Engineering Steering Group (IESG). Further information on | |||
| Internet Standards is available in Section 2 of RFC 7841. | Internet Standards is available in 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/rfc9527. | https://www.rfc-editor.org/info/rfc9527. | |||
| 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 398 ¶ | skipping to change at line 398 ¶ | |||
| New entries MUST specify the bit position, the transport protocol | New entries MUST specify the bit position, the transport protocol | |||
| description, a mnemonic, and a reference as shown in Table 2. | description, a mnemonic, and a reference as shown in Table 2. | |||
| Changes to the format or policies of the registry are managed by the | Changes to the format or policies of the registry are managed by the | |||
| IETF via the IESG. | IETF via the IESG. | |||
| Future code points are assigned under RFC Required per [RFC8126]. | Future code points are assigned under RFC Required per [RFC8126]. | |||
| The initial registry is as specified in Table 2 below. | The initial registry is as specified in Table 2 below. | |||
| +======================+====================+==========+===========+ | +======================+====================+==========+===========+ | |||
| | Bit Position (Least | Transport Protocol | Mnemonic | Reference | | | Bit Position (least | Transport Protocol | Mnemonic | Reference | | |||
| | to most significant) | Description | | | | | to most significant) | Description | | | | |||
| +======================+====================+==========+===========+ | +======================+====================+==========+===========+ | |||
| | 0 | DNS over mutually | DomTLS | RFC 9527 | | | 0 | DNS over mutually | DomTLS | RFC 9527 | | |||
| | | authenticated TLS | | | | | | authenticated TLS | | | | |||
| +----------------------+--------------------+----------+-----------+ | +----------------------+--------------------+----------+-----------+ | |||
| | 1-15 | Unassigned | | | | | 1-15 | Unassigned | | | | |||
| +----------------------+--------------------+----------+-----------+ | +----------------------+--------------------+----------+-----------+ | |||
| Table 2: Supported Transport Registry | Table 2: Supported Transport Registry | |||
| skipping to change at line 458 ¶ | skipping to change at line 458 ¶ | |||
| RFC 8415, DOI 10.17487/RFC8415, November 2018, | RFC 8415, DOI 10.17487/RFC8415, November 2018, | |||
| <https://www.rfc-editor.org/info/rfc8415>. | <https://www.rfc-editor.org/info/rfc8415>. | |||
| [RFC9103] Toorop, W., Dickinson, S., Sahib, S., Aras, P., and A. | [RFC9103] Toorop, W., Dickinson, S., Sahib, S., Aras, P., and A. | |||
| Mankin, "DNS Zone Transfer over TLS", RFC 9103, | Mankin, "DNS Zone Transfer over TLS", RFC 9103, | |||
| DOI 10.17487/RFC9103, August 2021, | DOI 10.17487/RFC9103, August 2021, | |||
| <https://www.rfc-editor.org/info/rfc9103>. | <https://www.rfc-editor.org/info/rfc9103>. | |||
| [RFC9526] Migault, D., Weber, R., Richardson, M., and R. Hunter, | [RFC9526] Migault, D., Weber, R., Richardson, M., and R. Hunter, | |||
| "Simple Provisioning of Public Names for Residential | "Simple Provisioning of Public Names for Residential | |||
| Networks", RFC 9526, DOI 10.17487/RFC9526, December 2023, | Networks", RFC 9526, DOI 10.17487/RFC9526, January 2024, | |||
| <https://www.rfc-editor.org/info/rfc9526>. | <https://www.rfc-editor.org/info/rfc9526>. | |||
| 8.2. Informative References | 8.2. Informative References | |||
| [CNAME-PLUS-DNAME] | [CNAME-PLUS-DNAME] | |||
| Surý, O., "CNAME+DNAME Name Redirection", Work in | Surý, O., "CNAME+DNAME Name Redirection", Work in | |||
| Progress, Internet-Draft, draft-sury-dnsop-cname-plus- | Progress, Internet-Draft, draft-sury-dnsop-cname-plus- | |||
| dname-01, 15 July 2018, | dname-01, 15 July 2018, | |||
| <https://datatracker.ietf.org/doc/html/draft-sury-dnsop- | <https://datatracker.ietf.org/doc/html/draft-sury-dnsop- | |||
| cname-plus-dname-01>. | cname-plus-dname-01>. | |||
| End of changes. 4 change blocks. | ||||
| 4 lines changed or deleted | 4 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. | ||||