Internet-Draft | catalog-zone-xfr-properties | March 2025 |
Suhonen, et al. | Expires 27 September 2025 | [Page] |
This document specifies DNS Catalog Zones Properties that define the primary name servers from which specific or all member zones can transfer their associated zone, as well as properties for access control for those transfers.¶
This note is to be removed before publishing as an RFC.¶
Status information for this document may be found at https://datatracker.ietf.org/doc/draft-axu-dnsop-catalog-zone-xfr-properties/.¶
Discussion of this document takes place on the dnsop Working Group mailing list (mailto:dnsop@iets.org), which is archived at https://mailarchive.ietf.org/arch/browse/dnsop/.¶
Source for this draft and an issue tracker can be found at https://github.com/https://github.com/DNS-Hackathon/catalog-extensions-draft.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 27 September 2025.¶
Copyright (c) 2025 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
DNS Catalog Zones [RFC9432] described a method for automatic DNS zone provisioning among DNS name servers by the catalog of zones to be provisioned as one or more regular DNS zones. Configuration associated with the member zones, such as from which primary name servers and with which TSIG keys [RFC8945] to transfer the zones, and from which IP addresses and with which TSIG keys DNS notifies [RFC1996] are allowed, were assumed to be preprovisioned at the catalog consumer.¶
This document specifies DNS Catalog Zones Properties to specify primary name servers and TSIG keys to use to transfer the member zones in a catalog, as well as properties to specify which IP addresses, using which TSIG keys, are allowed to notify [RFC1996] the secondary name server serving the member zones, in order to remove the need to preprovision those at the catalog consumers.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
Body text [REPLACE]¶
These new properties can be at the top of the catalog zone, where they will affect all member zones, or under a member zone label, where they will affect just that member zone.¶
Body text [REPLACE]¶
Body text [REPLACE]¶
Body text [REPLACE]¶
Body text [REPLACE]¶
Body text [REPLACE]¶
Body text [REPLACE]¶
IANA is requested to add the following entries to the "DNS Catalog Zones Properties" registry under the "Domain Name System (DNS) Parameters" page:¶
Property Prefix | Description | Status | Reference |
---|---|---|---|
primaries | Primary name servers | Standards Track | [this document] |
allow-notify | Allow NOTIFY from | Standards track | [this document] |
allow-transfer | Allow zone transfer from | Standards track | [this document] |
allow-query | Allow queries from | Standards track | [this document] |
[NOTE to the RFC Editor: Please remove this section before publication]¶
This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft [RFC7942].¶
Security and Privacy Considerations¶
Example Catalog with One of Everything¶
Thanks everybody who helped making this work possible.¶
Thanks to all of the contributors.¶