@techreport{ietf-regext-dnsoperator-to-rrr-protocol-05,
    number =    {draft-ietf-regext-dnsoperator-to-rrr-protocol-05},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-regext-dnsoperator-to-rrr-protocol/05/},
    author =    {Jacques Latour and Ólafur Guðmundsson and Paul Wouters and Matthew Pounsett},
    title =     {{Third Party DNS operator to Registrars/Registries Protocol}},
    pagetotal = 15,
    year =      2018,
    month =     may,
    day =       4,
    abstract =  {There are several problems that arise in the standard Registrant/Registrar/Registry model when the operator of a zone is neither the Registrant nor the Registrar for the delegation. Historically the issues have been minor, and limited to difficulty guiding the Registrant through the initial changes to the NS records for the delegation. As this is usually a one time activity when the operator first takes charge of the zone it has not been treated as a serious issue. When the domain uses DNSSEC it necessary to make regular (sometimes annual) changes to the delegation, updating DS record(s) in order to track KSK rollover. Under the current model this is prone to delays and errors, as the Registrant must participate in updates to DS records. This document describes a simple protocol that allows a third party DNS operator to: establish the initial chain of trust (bootstrap DNSSEC) for a delegation; update DS records for a delegation; and, remove DS records from a secure delegation. The DNS operator may do these things in a trusted manner, without involving the Registrant for each operation. This same protocol can be used by Registrants to maintain their own domains if they wish.},
}