Rightside Group, Ltd.

matt@conundrum.com

OPS dnssec operator procedures Section 4.3.5.1 of "DNSSEC Operational Practices, version 2" describes a procedure for transitioning a DNSSEC signed zone from one (cooperative) operator to another. The procedure works well in many situations, but makes the assumption that it is feasible for the two operators to simultaneously publish slightly different versions of the zone being transferred. In some cases, such as with TLD registries, operational considerations require both operators to publish identical versions of the zone for the duration of the transition. This document describes a modified transition procedure which can be used in these cases.

The process described in "DNSSEC Operational Practices, version 2" (), section 4.3.5.1 for cooperating DNS operators to move a DNSSEC signed zone cannot be followed in all cases. When operators are moving a zone that is automatically published and/or changes rapidly, such as with a TLD or any other zone published from a registration database, it may not be feasible for the operators to publish different versions of the same zone. In these cases, it would be necessary for one or both operators to have the capability to add, remove, or alter arbitrary records inline along the zone transfer path (such as modifying the NSSet, and stripping RRSIGs). It cannot be assumed that this capability exists, since few (if any) common DNS implementations include these functions, and many custom implementations exist whose feature sets cannot be predicted. As a result, it must be assumed that operators moving an automatically generated or frequently updated zone must be able to publish an identical zone while transitioning it from one operator to another.

In this scenario, it is assumed that the operators will not exchange any private key material, but are otherwise fully cooperative. It is also assumed that the zone publishing process will be transferred between operators independently of the DNS operations. The simplest case is to transition the publishing process after the DNS operations move has been completed, and is the order that is assumed in this document, although the reverse order is possible. During the transition, the losing operator will provide the zone contents to the gaining operator by some automatic means (typically zone transfer). The transition of the publishing process is out of scope of this document. The DNS operations transition uses a modified pre-publish KSK and ZSK rollover, whereby the losing operator pre-publishes the public KSK and ZSK of the gaining operator. Partway through the transition, the losing operator stops signing the zone and begins providing an unsecure zone to the gaining operator, who begins signing. Once that is done, the gaining operator continues to post-publish the public keys of the losing operator until the TTLs of the original RRSIGs expire. In the timeline below, the losing operator is operator A, and the gaining operator is operator B. Records representig data generated by each operator are appended with the operator letter. DNSKEY_Z is a ZSK, and DNSKEY_K is a KSK. RRSIG_K is the RRSIG generated with DNSKEY_K.

---------------------------------------------------------------- | initial | pre-publish | re-delegation I | ---------------------------------------------------------------- | Parent: | Parent: | Parent: | | NS_A | NS_A | | | | | NS_B | | DS_A | DS_A | DS_A | | | | DS_B | ---------------------------------------------------------------- | Child: | Child: | Child: | | Published by A | Published by A | Published by A | | Signed by A | Signed by A | Signed by A | | SOA_A0 | SOA_A1 | SOA_A1 | | RRSIG_Z_A(SOA) | RRSIG_Z_A(SOA) | RRSIG_Z_A(SOA) | | | | | | NS_A | | | | | NS_B | NS_B | | RRSIG_Z_A(NS) | RRSIG_Z_A(NS) | RRSIG_Z_A(NS) | | | | | | DNSKEY_Z_A | DNSKEY_Z_A | DNSKEY_Z_A | | | DNSKEY_Z_B | DNSKEY_Z_B | | DNSKEY_K_A | DNSKEY_K_A | DNSKEY_K_A | | | DNSKEY_K_B | DNSKEY_K_B | | RRSIG_K_A(DNSKEY) | RRSIG_K_A(DNSKEY) | RRSIG_K_A(DNSKEY) | ----------------------------------------------------------------

---------------------------------------------------------------- | signing-migration | re-delegation II | post-migration | ---------------------------------------------------------------- | Parent: | Parent: | Parent: | | | | | | NS_B | NS_B | NS_B | | DS_A | | | | DS_B | DS_B | DS_B | ---------------------------------------------------------------- | Child: | Child: | Child: | | Published by A | Published by A | Published by B | | Signed by B | Signed by B | Signed by B | | SOA_A2 | SOA_A2 | SOA_B0 | | RRSIG_Z_B(SOA) | RRSIG_Z_B(SOA) | RRSIG_Z_B(SOA) | | | | | | | | | | NS_B | NS_B | NS_B | | RRSIG_Z_B(NS) | RRSIG_Z_B(NS) | RRSIG_Z_B(NS) | | | | | | DNSKEY_Z_A | DNSKEY_Z_A | | | DNSKEY_Z_B | DNSKEY_Z_B | DNSKEY_Z_B | | DNSKEY_K_A | DNSKEY_K_A | | | DNSKEY_K_B | DNSKEY_K_B | DNSKEY_K_B | | RRSIG_K_B(DNSKEY) | RRSIG_K_B(DNSKEY) | RRSIG_K_B(DNSKEY) | ----------------------------------------------------------------

This document raises no new security considerations. Please see Section 6 of .

This document has no actions for IANA.

[RFC Editor: Please remove this section before publication.] This document is maintained at Github at . Issue reports and pull requests are gratefully accepted here. The XML and TXT versions of this document are generated from Markdown using mmark by Miek Gieben. mmark is available at .

[RFC Editor: Please remove this section before publication.]

grammar and spelling nits added Security Considerations section added IANA Considerations section added Document Source and Changelist call out publishing migration as out of scope

Initial Submission