@techreport{pounsett-transferring-automated-dnssec-zones-03,
    number =    {draft-pounsett-transferring-automated-dnssec-zones-03},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-pounsett-transferring-automated-dnssec-zones/03/},
    author =    {Matthew Pounsett},
    title =     {{Change of Operator Procedures for Automatically Published DNSSEC Zones}},
    pagetotal = 8,
    year =      2017,
    month =     sep,
    day =       13,
    abstract =  {Section 4.3.5.1 of {[}RFC6781{]} "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.},
}