idnits 2.17.1 draft-ietf-dnsop-dns-catalog-zones-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There are 2 instances of too long lines in the document, the longest one being 7 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (7 March 2022) is 778 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 DNSOP Working Group P. van Dijk 3 Internet-Draft PowerDNS 4 Intended status: Standards Track L. Peltan 5 Expires: 8 September 2022 CZ.NIC 6 O. Sury 7 Internet Systems Consortium 8 W. Toorop 9 NLnet Labs 10 K. Monshouwer 12 P. Thomassen 13 deSEC, SSE - Secure Systems Engineering 14 7 March 2022 16 DNS Catalog Zones 17 draft-ietf-dnsop-dns-catalog-zones-05 19 Abstract 21 This document describes a method for automatic DNS zone provisioning 22 among DNS primary and secondary nameservers by storing and 23 transferring the catalog of zones to be provisioned as one or more 24 regular DNS zones. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at https://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on 8 September 2022. 43 Copyright Notice 45 Copyright (c) 2022 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 50 license-info) in effect on the date of publication of this document. 51 Please review these documents carefully, as they describe your rights 52 and restrictions with respect to this document. Code Components 53 extracted from this document must include Revised BSD License text as 54 described in Section 4.e of the Trust Legal Provisions and are 55 provided without warranty as described in the Revised BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 60 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 3. Description . . . . . . . . . . . . . . . . . . . . . . . . . 4 62 4. Catalog Zone Structure . . . . . . . . . . . . . . . . . . . 4 63 4.1. SOA and NS Records . . . . . . . . . . . . . . . . . . . 4 64 4.2. Member Zones . . . . . . . . . . . . . . . . . . . . . . 4 65 4.3. Global Properties . . . . . . . . . . . . . . . . . . . . 5 66 4.3.1. Schema Version (version property) . . . . . . . . . . 6 67 4.4. Member Zone Properties . . . . . . . . . . . . . . . . . 6 68 4.4.1. Change of Ownership (coo property) . . . . . . . . . 6 69 4.4.2. Groups (group property) . . . . . . . . . . . . . . . 7 70 4.5. Custom Properties (*.ext properties) . . . . . . . . . . 8 71 5. Nameserver Behavior . . . . . . . . . . . . . . . . . . . . . 9 72 5.1. General Requirements . . . . . . . . . . . . . . . . . . 9 73 5.2. Member zone name clash . . . . . . . . . . . . . . . . . 9 74 5.3. Member zone removal . . . . . . . . . . . . . . . . . . . 10 75 5.4. Member node name change . . . . . . . . . . . . . . . . . 10 76 5.5. Migrating member zones between catalogs . . . . . . . . . 10 77 5.6. Zone associated state reset . . . . . . . . . . . . . . . 11 78 6. Implementation Notes . . . . . . . . . . . . . . . . . . . . 11 79 7. Security Considerations . . . . . . . . . . . . . . . . . . . 11 80 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 81 9. Normative References . . . . . . . . . . . . . . . . . . . . 12 82 10. Informative References . . . . . . . . . . . . . . . . . . . 13 83 Appendix A. Implementation Status . . . . . . . . . . . . . . . 14 84 Appendix B. Change History (to be removed before final 85 publication) . . . . . . . . . . . . . . . . . . . . . . 14 86 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 88 1. Introduction 90 The content of a DNS zone is synchronized amongst its primary and 91 secondary nameservers using AXFR and IXFR. However, the list of 92 zones served by the primary (called a catalog in [RFC1035]) is not 93 automatically synchronized with the secondaries. To add or remove a 94 zone, the administrator of a DNS nameserver farm not only has to add 95 or remove the zone from the primary, they must also add/remove the 96 zone from all secondaries, either manually or via an external 97 application. This can be both inconvenient and error-prone; it is 98 also dependent on the nameserver implementation. 100 This document describes a method in which the catalog is represented 101 as a regular DNS zone (called a "catalog zone" here), and transferred 102 using DNS zone transfers. As zones are added to or removed from the 103 catalog zone, these changes are distributed to the secondary 104 nameservers in the normal way. The secondary nameservers then 105 add/remove/modify the zones they serve in accordance with the changes 106 to the catalog zone. Other use-cases of nameserver remote 107 configuration by catalog zones are possible, where the catalog 108 consumer might not be a secondary. 110 2. Terminology 112 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 113 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 114 "OPTIONAL" in this document are to be interpreted as described in BCP 115 14 [RFC2119] [RFC8174] when, and only when, they appear in all 116 capitals, as shown here. 118 Catalog zone A DNS zone containing a DNS catalog, that is, a list of 119 DNS zones and associated properties. 121 Member zone A DNS zone whose configuration is published inside a 122 catalog zone. 124 Member node The DNS name in the Catalog zone representing a Member 125 zone. 127 $CATZ Used in examples as a placeholder to represent the domain name 128 of the catalog zone itself. $OLDCATZ and $NEWCATZ are used to 129 discuss migration a member zone from one catalog zone $OLDCATZ to 130 another catalog zone $NEWCATZ. 132 Catalog producer An entity that generates and is responsible for the 133 contents of the catalog zone. 135 Catalog consumer An entity that extracts information from the 136 catalog zone (such as a DNS server that configures itself 137 according to the catalog zone's contents). 139 3. Description 141 A catalog zone is a DNS zone whose contents are specially crafted. 142 Its records primarily constitute a list of PTR records referencing 143 other DNS zones (so-called "member zones"). The catalog zone may 144 contain other records indicating additional metadata (so-called 145 "properties") associated with these member zones. 147 Catalog consumers SHOULD ignore any RR in the catalog zone which is 148 meaningless or useless to the implementation. 150 Authoritative servers may be preconfigured with multiple catalog 151 zones, each associated with a different set of configurations. 153 Although the contents of a catalog zone are interpreted and acted 154 upon by nameservers, a catalog zone is a regular DNS zone and so must 155 adhere to the standards for such zones. 157 A catalog zone is primarily intended for the management of a farm of 158 authoritative nameservers. The content of catalog zones may not be 159 accessible from any recursive nameserver. 161 4. Catalog Zone Structure 163 4.1. SOA and NS Records 165 As with any other DNS zone, a catalog zone MUST have a syntactically 166 correct SOA record and at least one NS record at its apex. 168 The SOA record's SERIAL, REFRESH, RETRY and EXPIRE fields [RFC1035] 169 are used during zone transfer. A catalog zone's SOA SERIAL field 170 MUST increase when an update is made to the catalog zone's contents 171 as per serial number arithmetic defined in [RFC1982]. Otherwise, 172 catalog consumers might not notice updates to the catalog zone's 173 contents. 175 There is no requirement to be able to query the catalog zone via 176 recursive nameservers. Catalog consumers MUST ignore and MUST NOT 177 assume or require NS records at the apex. However, at least one is 178 still required so that catalog zones are syntactically correct DNS 179 zones. A single NS RR with a NSDNAME field containing the absolute 180 name "invalid." is RECOMMENDED [RFC2606]. 182 4.2. Member Zones 184 The list of member zones is specified as a collection of member 185 nodes, represented by domain names under the owner name "zones" where 186 "zones" is a direct child domain of the catalog zone. 188 The names of member zones are represented on the RDATA side (instead 189 of as a part of owner names) of a PTR record, so that all valid 190 domain names may be represented regardless of their length [RFC1035]. 191 This PTR record MUST be the only record in the PTR RRset with the 192 same name. More than one record in the RRset denotes a broken 193 catalog zone which MUST NOT be processed (see Section 5.1). 195 For example, if a catalog zone lists three zones "example.com.", 196 "example.net." and "example.org.", the member node RRs would appear 197 as follows: 199 .zones.$CATZ 0 IN PTR example.com. 200 .zones.$CATZ 0 IN PTR example.net. 201 .zones.$CATZ 0 IN PTR example.org. 203 where is a label that tags each record in the collection. 204 has an unique value in the collection. 206 Member node labels carry no informational meaning beyond labeling 207 member zones. A changed label may indicate that the state for a zone 208 needs to be reset (see Section 5.6). 210 Having the zones uniquely tagged with the label ensures 211 that additional RRs can be added below the member node (see 212 Section 4.4). 214 The CLASS field of every RR in a catalog zone MUST be IN (1). 216 The TTL field's value is not defined by this memo. Catalog zones are 217 for authoritative nameserver management only and are not intended for 218 general querying via recursive resolvers. 220 4.3. Global Properties 222 Apart from catalog zone metadata stored at the apex (NS, SOA and the 223 like), catalog zone information is stored in the form of 224 "properties". Catalog consumers SHOULD ignore properties they do not 225 understand. 227 This specification defines a number of so-called properties, as well 228 as a mechanism to allow implementers to store additional information 229 in the catalog zone with Custom properties, see Section 4.5. The 230 meaning of such custom properties is determined by the implementation 231 in question. 233 Some properties are defined at the global level; others are scoped to 234 apply only to a specific member zone. This document defines a single 235 mandatory global property in Section 4.3.1. Member-specific 236 properties are described in Section 4.4. 238 More properties may be defined in future documents. 240 4.3.1. Schema Version (version property) 242 The catalog zone schema version is specified by an integer value 243 embedded in a TXT RR named version.$CATZ. All catalog zones MUST 244 have a TXT RRset named version.$CATZ with exactly one RR. Catalog 245 consumers MUST NOT apply catalog zone processing to zones without the 246 expected value in the version.$CATZ TXT RR, but they may be 247 transferred as ordinary zones. For this memo, the value of the 248 version.CATZ TXT RR MUST be set to "2", i.e.: 250 version.$CATZ 0 IN TXT "2" 252 NB: Version 1 was used in a draft version of this memo and reflected 253 the implementation first found in BIND 9.11. 255 4.4. Member Zone Properties 257 Each member zone MAY have one or more additional properties, 258 described in this chapter. These properties are completely optional 259 and catalog consumers SHOULD ignore those it does not understand. 260 Member zone properties are represented by RRsets below the 261 corresponding member node. 263 4.4.1. Change of Ownership (coo property) 265 The coo property facilitates controlled migration of a member zone 266 from one catalog to another. 268 A Change Of Ownership is signaled by the coo property in the catalog 269 zone currently "owning" the zone. The name of the new catalog is in 270 the value of a PTR record in the old catalog. For example if member 271 "example.com." will migrate from catalog zone $OLDCATZ to catalog 272 zone $NEWCATZ, this appears in the $OLDCATZ catalog zone as follows: 274 .zones.$OLDCATZ 0 IN PTR example.com. 275 coo..zones.$OLDCATZ 0 IN PTR $NEWCATZ 277 The PTR RRset MUST consist of a single PTR record. More than one 278 record in the RRset denotes a broken catalog zone which MUST NOT be 279 processed (see Section 5.1). 281 When a consumer of catalog zone $OLDCATZ receives an update which 282 adds or changes a coo property for a member zone in $OLDCATZ 283 signalling a new owner $NEWCATZ, it does _not_ migrate the member 284 zone immediately. 286 This is because the catalog consumer may not have the 287 identifier associated with the member zone in $NEWCATZ and because 288 name servers do not index Resource Records by RDATA, it may not know 289 whether or not the member zone is configured in $NEWCATZ at all. It 290 may have to wait for an update of $NEWCATZ adding or changing that 291 member zone. When a consumer of catalog zone $NEWCATZ receives an 292 update of $NEWCATZ which adds or changes a member zone, _and_ that 293 consumer had the member zone associated with $OLDCATZ, _and_ there is 294 a coo property of the member zone in $OLDCATZ pointing to $NEWCATZ, 295 _only then_ it will reconfigure the member zone with the for $NEWCATZ 296 preconfigured settings. 298 Unless the member node label (i.e. ) for the member is the 299 same in $NEWCATZ, all associated state for a just migrated zone MUST 300 be reset (see Section 5.6). Note that the owner of $OLDCATZ allows 301 for the zone associated state to be taken over by the owner of 302 $NEWCATZ by default. To prevent the takeover, the owner of $OLDCATZ 303 has to enforce a zone state reset by changing the member node label 304 (see Section 5.6) before or simultaneous with adding the coo 305 property. (see also Section 7) 307 The old owner may remove the member zone containing the coo property 308 from $OLDCATZ once it has been established that all its consumers 309 have processed the Change of Ownership. 311 4.4.2. Groups (group property) 313 With a group property, consumer(s) can be signalled to treat some 314 member zones within the catalog zone differently. 316 The consumer MAY apply different configuration options when 317 processing member zones, based on the value of the group property. 318 The exact handling of configuration referred to by the group property 319 value is left to the consumer's implementation and configuration. 320 The property is defined by a TXT record in the sub-node labelled 321 group. 323 The producer MAY assign a group property to all, some, or none of the 324 member zones within a catalog zone. The producer MUST NOT assign 325 more than one group property to one member zone. 327 The consumer MUST ignore either all or none of the group properties 328 in a catalog zone. 330 The value of the TXT record MUST be at most 255 octets long and MUST 331 NOT contain whitespace characters. The consumer MUST interpret the 332 value case-sensitively. 334 4.4.2.1. Example 336 .zones.$CATZ 0 IN PTR example.com. 337 group..zones.$CATZ 0 IN TXT sign-with-nsec3 338 .zones.$CATZ 0 IN PTR example.net. 339 group..zones.$CATZ 0 IN TXT nodnssec 341 In this case, the consumer might be implemented and configured in the 342 way that the member zones with "nodnssec" group assigned will not be 343 signed with DNSSEC, and the zones with "sign-with-nsec3" group 344 assigned will be signed with DNSSEC with NSEC3 chain. 346 By generating the catalog zone (snippet) above, the producer signals 347 how the consumer shall treat DNSSEC for the zones example.net. and 348 example.com., respectively. 350 4.5. Custom Properties (*.ext properties) 352 Implementations and operators of catalog zones may choose to provide 353 their own properties. Custom properties can occur both globally, or 354 for a specific member zone. To prevent a name clash with future 355 properties, such properties should be represented below the label 356 ext. 358 ext is not a placeholder, so a custom property would have domains 359 names as follows: 361 .ext.$CATZ # for a global custom property 362 .ext..zones.$CATZ # for a member zone custom property 364 may consist of one or more labels. 366 Implementations MAY use such properties on the member zone level to 367 store additional information about member zones, for example to flag 368 them for specific treatment (such as ...). 370 Further, implementations MAY use custom properties on the global 371 level to store additional information about the catalog zone itself. 372 While there may be many use cases for this, a plausible one is to 373 store default values for custom properties on the global level, then 374 overriding them using a property of the same name on the member level 375 (= under the ext label of the member node) if so desired. A property 376 description should clearly say what semantics apply, and whether a 377 property is global, member, or both. 379 The meaning of the custom properties described in this section is 380 determined by the implementation alone, without expectation of 381 interoperability. A catalog consumer SHOULD ignore custom properties 382 it does not understand. 384 5. Nameserver Behavior 386 5.1. General Requirements 388 As it is a regular DNS zone, a catalog zone can be transferred using 389 DNS zone transfers among nameservers. 391 Although they are regular DNS zones, catalog zones contain only 392 information for the management of a set of authoritative nameservers. 393 For this reason, operators may want to limit the systems able to 394 query these zones. It may be inconvenient to serve some contents of 395 catalog zones via DNS queries anyway due to the nature of their 396 representation. A separate method of querying entries inside the 397 catalog zone may be made available by nameserver implementations (see 398 Section 6). 400 Catalog updates should be automatic, i.e., when a nameserver that 401 supports catalog zones completes a zone transfer for a catalog zone, 402 it SHOULD apply changes to the catalog within the running nameserver 403 automatically without any manual intervention. 405 As with regular zones, primary and secondary nameservers for a 406 catalog zone may be operated by different administrators. The 407 secondary nameservers may be configured as catalog consumer to 408 synchronize catalog zones from the primary, but the primary's 409 administrators may not have any administrative access to the 410 secondaries. 412 Nameservers MAY allow loading and transfer of broken zones with 413 incorrect catalog zone syntax (as they are treated as regular zones), 414 but catalog consumers MUST NOT process such broken zones as catalog 415 zones. For the purpose of catalog processing, the broken catalogs 416 MUST be ignored. 418 5.2. Member zone name clash 420 If there is a clash between an existing zone's name (either from an 421 existing member zone or otherwise configured zone) and an incoming 422 member zone's name (via transfer or update), the new instance of the 423 zone MUST be ignored and an error SHOULD be logged. 425 A clash between an existing member zone's name and an incoming member 426 zone's name (via transfer or update), may be an attempt to migrate a 427 zone to a different catalog, but should not be treated as one except 428 as described in {#cooproperty}. 430 5.3. Member zone removal 432 When a member zone is removed from a specific catalog zone, an 433 authoritative server MUST NOT remove the zone and associated state 434 data if the zone was not configured from that specific catalog zone. 435 Only when the zone was configured from a specific catalog zone, and 436 the zone is removed as a member from that specific catalog zone, the 437 zone and associated state (such as zone data and DNSSEC keys) MUST be 438 removed. 440 5.4. Member node name change 442 When via a single update or transfer, the member node's label value 443 () changes, catalog consumers MUST process this as a member 444 zone removal including all the zone's associated state (as described 445 in Section 5.3), immediately followed by processing the member as a 446 newly to be configured zone in the same catalog. 448 5.5. Migrating member zones between catalogs 450 If all consumers of the catalog zones involved support the coo 451 property, it is RECOMMENDED to perform migration of a member zone by 452 following the procedure described in Section 4.4.1. Otherwise a 453 migration of member zone from a catalog zone $OLDCATZ to a catalog 454 zone $NEWCATZ has to be done by: first removing the member zone from 455 $OLDCATZ; second adding the member zone to $NEWCATZ. 457 If in the process of a migration some consumers of the involved 458 catalog zones did not catch the removal of the member zone from 459 $OLDCATZ yet (because of a lost packet or down time or otherwise), 460 but did already see the update of $NEWCATZ, they may consider the 461 update adding the member zone in $NEWCATZ to be a name clash (see 462 Section 5.2) and as a consequence the member is not migrated to 463 $NEWCATZ. This possibility needs to be anticipated with a member 464 zone migration. Recovery from such a situation is out of the scope 465 of this document. It may for example entail a manually forced 466 retransfer of $NEWCATZ to consumers after they have been detected to 467 have received and processed the removal of the member zone from 468 $OLDCATZ. 470 5.6. Zone associated state reset 472 It may be desirable to reset state (such as zone data and DNSSEC 473 keys) associated with a member zone. 475 A zone state reset may be performed by a change of the member node's 476 name (see Section 5.4). 478 6. Implementation Notes 480 Catalog zones on secondary nameservers would have to be setup 481 manually, perhaps as static configuration, similar to how ordinary 482 DNS zones are configured. The secondary additionally needs to be 483 configured as a catalog consumer for the catalog zone to enable 484 processing of the member zones in the catalog, such as automatic 485 synchronized of the member zones for secondary service. 487 An administrator may want to look at data inside a catalog zone. 488 Typical queries might include dumping the list of member zones, 489 dumping a member zone's effective configuration, querying a specific 490 property value of a member zone, etc. Because of the structure of 491 catalog zones, it may not be possible to perform these queries 492 intuitively, or in some cases, at all, using DNS QUERY. For example, 493 it is not possible to enumerate the contents of a multi-valued 494 property (such as the list of member zones) with a single QUERY. 495 Implementations are therefore advised to provide a tool that uses 496 either the output of AXFR or an out-of-band method to perform queries 497 on catalog zones. 499 7. Security Considerations 501 As catalog zones are transmitted using DNS zone transfers, it is 502 RECOMMENDED that catalog zone transfer are protected from unexpected 503 modifications by way of authentication, for example by using TSIG 504 [RFC8945], or Strict or Mutual TLS authentication with DNS Zone 505 transfer over TLS [RFC9103]. 507 Use of DNS UPDATE [RFC2136] to modify the content of catalog zones 508 SHOULD similarly be authenticated. 510 Zone transfers of member zones SHOULD similarly be authenticated. 511 TSIG shared secrets used for member zones SHOULD NOT be mentioned in 512 the catalog zone data. However, key identifiers may be shared within 513 catalog zones. 515 Catalog zones reveal the zones served by the consumers of the catalog 516 zone. It is RECOMMENDED to limit the systems able to query these 517 zones. It is RECOMMENDED to transfer catalog zones confidentially 518 [RFC9103]. 520 Administrative control over what zones are served from the configured 521 name servers shifts completely from the server operator (consumer) to 522 the "owner" (producer) of the catalog zone content. 524 With migration of member zones between catalogs using the coo 525 property, it is possible for the owner of the target catalog (i.e. 526 $NEWCATZ) to take over all associated state with the zone from the 527 original owner (i.e. $OLDCATZ) by maintaining the same member node 528 label (i.e. ). To prevent the takeover of the zone 529 associated state, the original owner has to enforce a zone state 530 reset by changing the member node label (see Section 5.6) before or 531 simultaneously with adding the coo property. 533 8. Acknowledgements 535 Our deepest thanks and appreciation go to Stephen Morris, Ray Bellis 536 and Witold Krecicki who initiated this draft and did the bulk of the 537 work. 539 Catalog zones originated as the chosen method among various proposals 540 that were evaluated at ISC for easy zone management. The chosen 541 method of storing the catalog as a regular DNS zone was proposed by 542 Stephen Morris. 544 The initial authors discovered that Paul Vixie's earlier [Metazones] 545 proposal implemented a similar approach and reviewed it. Catalog 546 zones borrows some syntax ideas from Metazones, as both share this 547 scheme of representing the catalog as a regular DNS zone. 549 Thanks to Leo Vandewoestijne. Leo's presentation in the DNS devroom 550 at the FOSDEM'20 [FOSDEM20] was one of the motivations to take up and 551 continue the effort of standardizing catalog zones. 553 Thanks to Brian Conry, Klaus Darilion, Brian Dickson, Tony Finch, 554 Evan Hunt, Shane Kerr, Patrik Lundin, Victoria Risk, Petr Spacek and 555 Carsten Strotmann for reviewing draft proposals and offering comments 556 and suggestions. 558 9. Normative References 560 [RFC1035] Mockapetris, P., "Domain names - implementation and 561 specification", STD 13, RFC 1035, DOI 10.17487/RFC1035, 562 November 1987, . 564 [RFC1982] Elz, R. and R. Bush, "Serial Number Arithmetic", RFC 1982, 565 DOI 10.17487/RFC1982, August 1996, 566 . 568 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 569 Requirement Levels", BCP 14, RFC 2119, 570 DOI 10.17487/RFC2119, March 1997, 571 . 573 [RFC2136] Vixie, P., Ed., Thomson, S., Rekhter, Y., and J. Bound, 574 "Dynamic Updates in the Domain Name System (DNS UPDATE)", 575 RFC 2136, DOI 10.17487/RFC2136, April 1997, 576 . 578 [RFC2606] Eastlake 3rd, D. and A. Panitz, "Reserved Top Level DNS 579 Names", BCP 32, RFC 2606, DOI 10.17487/RFC2606, June 1999, 580 . 582 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 583 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 584 May 2017, . 586 [RFC8945] Dupont, F., Morris, S., Vixie, P., Eastlake 3rd, D., 587 Gudmundsson, O., and B. Wellington, "Secret Key 588 Transaction Authentication for DNS (TSIG)", STD 93, 589 RFC 8945, DOI 10.17487/RFC8945, November 2020, 590 . 592 [RFC9103] Toorop, W., Dickinson, S., Sahib, S., Aras, P., and A. 593 Mankin, "DNS Zone Transfer over TLS", RFC 9103, 594 DOI 10.17487/RFC9103, August 2021, 595 . 597 10. Informative References 599 [FOSDEM20] Vandewoestijne, L., "Extending Catalog zones - another 600 approach in automating maintenance", 2020, 601 . 604 [Metazones] 605 Vixie, P., "Federated Domain Name Service Using DNS 606 Metazones", 2005, 607 . 609 Appendix A. Implementation Status 611 *Note to the RFC Editor*: please remove this entire section before 612 publication. 614 In the following implementation status descriptions, "DNS Catalog 615 Zones" refers to DNS Catalog Zones as described in this document. 617 * Knot DNS 3.1 (released August 2, 2021) supports full producing and 618 consuming of catalog zones, including the group property. 620 * PowerDNS has a proof of concept external program called PowerCATZ 621 (https://github.com/PowerDNS/powercatz/), that can process DNS 622 Catalog Zones. 624 * Proof of concept python scripts (https://github.com/IETF- 625 Hackathon/NSDCatZ) that can be used for both generating and 626 consuming DNS Catalog Zones with NSD have been developed during 627 the hackathon at the IETF-109. 629 Interoperability between the above implementations has been tested 630 during the hackathon at the IETF-109. 632 Appendix B. Change History (to be removed before final publication) 634 * draft-muks-dnsop-dns-catalog-zones-00 636 | Initial public draft. 638 * draft-muks-dnsop-dns-catalog-zones-01 640 | Added Witold, Ray as authors. Fixed typos, consistency issues. 641 | Fixed references. Updated Area. Removed newly introduced custom 642 | RR TYPEs. Changed schema version to 1. Changed TSIG requirement 643 | from MUST to SHOULD. Removed restrictive language about use of 644 | DNS QUERY. When zones are introduced into a catalog zone, a 645 | primary SHOULD first make the new zones available for transfers 646 | first (instead of MUST). Updated examples, esp. use IPv6 in 647 | examples per Fred Baker. Add catalog zone example. 649 * draft-muks-dnsop-dns-catalog-zones-02 651 | Addressed some review comments by Patrik Lundin. 653 * draft-muks-dnsop-dns-catalog-zones-03 655 | Revision bump. 657 * draft-muks-dnsop-dns-catalog-zones-04 659 | Reordering of sections into more logical order. Separation of 660 | multi-valued properties into their own category. 662 * draft-toorop-dnsop-dns-catalog-zones-00 664 | New authors to pickup the editor pen on this draft 665 | 666 | Remove data type definitions for zone properties Removing 667 | configuration of member zones through zone properties altogether 668 | 669 | Remove Open issues and discussion Appendix, which was about zone 670 | options (including primary/secondary relationships) only. 672 * draft-toorop-dnsop-dns-catalog-zones-01 674 | Added a new section "The Serial Property", introducing a new 675 | mechanism which can help with disseminating zones from the primary 676 | to the secondary nameservers in a timely fashion more reliably. 677 | 678 | Three different ways to provide a "serial" property with a member 679 | zone are offered to or the workgroup for discussion. 680 | 681 | Added a new section "Implementation Status", listing production 682 | ready, upcoming and Proof of Concept implementations, and 683 | reporting on interoperability of the different implementations. 685 * draft-toorop-dnsop-dns-catalog-zones-02 687 | Adding the coo property for zone migration in a controlled fashion 688 | 689 | Adding the group property for reconfigure settings of member zones 690 | in an atomic update 691 | 692 | Adding the epoch property to reset zone associated state in a 693 | controlled fashion 695 * draft-toorop-dnsop-dns-catalog-zones-03 697 | Big cleanup! 698 | 699 | Introducing the terms catalog consumer and catalog producer 700 | 701 | Reorganized topics to create a more coherent whole 702 | 703 | Properties all have consistent format now 704 | 705 | Try to assume the least possible from implementations w.r.t.: 706 | 707 | 1) Predictability of the IDs of member zones 708 | 709 | 2) Whether or not fallback catalog zones can be found for a member 710 | 711 | 3) Whether or not a catalog consumer can maintain state 713 * draft-toorop-dnsop-dns-catalog-zones-04 715 | Move Implementation status to appendix 716 | 717 | Miscellaneous textual improvements 718 | 719 | coo property points to $NEWCATZ (and not zones.$NEWCATZ) 720 | 721 | Remove suggestion to increase serial and remove member zone from 722 | $OLDCATZ after migration 723 | 724 | More consistent usage of the terms catalog consumer and catalog 725 | producer throughout the document 726 | 727 | Better (safer) description of resetting refresh timers of member 728 | zones with the serial property 729 | 730 | Removing a member MUST remove zone associated state 731 | 732 | Make authentication requirements a bit less prescriptive in 733 | security considerations 734 | 735 | Updated implementation status for KnotDNS 736 | 737 | Describe member node name changes and update "Zone associated 738 | state reset" to use that as the mechanism for it. 739 | 740 | Add Peter Thomassen as co-author 741 | 742 | Complete removal of the epoch property. We consider consumer 743 | optimizations with predictable member node labels (for example 744 | based on a hash) out of the scope of this document. 745 | 746 | Miscellaneous editorial improvements 748 * draft-toorop-dnsop-dns-catalog-zones-05 750 | Add Kees Monshouwer as co-author 751 | 752 | Removed the "serial" property 753 | 754 | Allow custom properties on the global level 756 Authors' Addresses 758 Peter van Dijk 759 PowerDNS 760 Den Haag 761 Netherlands 762 Email: peter.van.dijk@powerdns.com 764 Libor Peltan 765 CZ.NIC 766 Czechia 767 Email: libor.peltan@nic.cz 769 Ondrej Sury 770 Internet Systems Consortium 771 Czechia 772 Email: ondrej@isc.org 774 Willem Toorop 775 NLnet Labs 776 Science Park 400 777 1098 XH Amsterdam 778 Netherlands 779 Email: willem@nlnetlabs.nl 781 Kees Monshouwer 782 Netherlands 783 Email: mind@monshouwer.eu 785 Peter Thomassen 786 deSEC, SSE - Secure Systems Engineering 787 Berlin 788 Germany 789 Email: peter@desec.io