--- 1/draft-ietf-regext-dnsoperator-to-rrr-protocol-04.txt 2018-05-04 09:14:27.102437069 -0700 +++ 2/draft-ietf-regext-dnsoperator-to-rrr-protocol-05.txt 2018-05-04 09:14:27.314442121 -0700 @@ -1,23 +1,23 @@ regext J. Latour Internet-Draft CIRA Intended status: Standards Track O. Gudmundsson -Expires: March 16, 2018 Cloudflare, Inc. +Expires: November 5, 2018 Cloudflare, Inc. P. Wouters Red Hat M. Pounsett - Rightside Group, Ltd. - September 12, 2017 + Nimbus Operations Inc. + May 4, 2018 Third Party DNS operator to Registrars/Registries Protocol - draft-ietf-regext-dnsoperator-to-rrr-protocol-04 + draft-ietf-regext-dnsoperator-to-rrr-protocol-05 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 @@ -45,25 +45,25 @@ 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 March 16, 2018. + This Internet-Draft will expire on November 5, 2018. Copyright Notice - Copyright (c) 2017 IETF Trust and the persons identified as the + Copyright (c) 2018 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 Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as @@ -83,33 +83,34 @@ 3.5. Bootstrapping DNSSEC . . . . . . . . . . . . . . . . . . 6 4. API Definition . . . . . . . . . . . . . . . . . . . . . . . 7 4.1. Authentication . . . . . . . . . . . . . . . . . . . . . 7 4.2. RESTful Resources . . . . . . . . . . . . . . . . . . . . 8 4.2.1. CDS resource . . . . . . . . . . . . . . . . . . . . 8 4.2.2. Token resource . . . . . . . . . . . . . . . . . . . 10 4.3. Customized Error Messages . . . . . . . . . . . . . . . . 11 5. Security considerations . . . . . . . . . . . . . . . . . . . 11 6. IANA Actions . . . . . . . . . . . . . . . . . . . . . . . . 11 7. Internationalization Considerations . . . . . . . . . . . . . 11 - 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 - 8.1. Normative References . . . . . . . . . . . . . . . . . . 11 + 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 + 8.1. Normative References . . . . . . . . . . . . . . . . . . 12 8.2. Informative References . . . . . . . . . . . . . . . . . 12 Appendix A. Document History . . . . . . . . . . . . . . . . . . 13 - A.1. regext Version 04 . . . . . . . . . . . . . . . . . . . . 13 - A.2. regext Version 03 . . . . . . . . . . . . . . . . . . . . 13 - A.3. regext Version 02 . . . . . . . . . . . . . . . . . . . . 13 - A.4. regext Version 01 . . . . . . . . . . . . . . . . . . . . 14 - A.5. regext Version 00 . . . . . . . . . . . . . . . . . . . . 14 - A.6. Version 03 . . . . . . . . . . . . . . . . . . . . . . . 14 - A.7. Version 02 . . . . . . . . . . . . . . . . . . . . . . . 14 - A.8. Version 01 . . . . . . . . . . . . . . . . . . . . . . . 14 - A.9. Version 00 . . . . . . . . . . . . . . . . . . . . . . . 14 + A.1. regext Version 05 . . . . . . . . . . . . . . . . . . . . 13 + A.2. regext Version 04 . . . . . . . . . . . . . . . . . . . . 13 + A.3. regext Version 03 . . . . . . . . . . . . . . . . . . . . 13 + A.4. regext Version 02 . . . . . . . . . . . . . . . . . . . . 14 + A.5. regext Version 01 . . . . . . . . . . . . . . . . . . . . 14 + A.6. regext Version 00 . . . . . . . . . . . . . . . . . . . . 14 + A.7. Version 03 . . . . . . . . . . . . . . . . . . . . . . . 14 + A.8. Version 02 . . . . . . . . . . . . . . . . . . . . . . . 14 + A.9. Version 01 . . . . . . . . . . . . . . . . . . . . . . . 14 + A.10. Version 00 . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 1. Introduction After a domain has been registered, one of three parties will maintain the DNS zone loaded on the "primary" DNS servers: the Registrant, the Registrar, or a third party DNS operator. DNS registration systems were originally designed around making registrations easy and fast, however after registration the complexity of making changes to the delegation differs for each of @@ -538,22 +539,22 @@ [RFC8078] Gudmundsson, O. and P. Wouters, "Managing DS Records from the Parent via CDS/CDNSKEY", RFC 8078, DOI 10.17487/RFC8078, March 2017, . 8.2. Informative References [I-D.ietf-dnsop-terminology-bis] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS - Terminology", draft-ietf-dnsop-terminology-bis-06 (work in - progress), July 2017. + Terminology", draft-ietf-dnsop-terminology-bis-10 (work in + progress), April 2018. [I-D.wallstrom-dnsop-dns-delegation-requirements] Wallstrom, P. and J. Schlyter, "DNS Delegation Requirements", draft-wallstrom-dnsop-dns-delegation- requirements-03 (work in progress), October 2016. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . @@ -570,34 +571,40 @@ Registration Data Access Protocol (RDAP)", RFC 7480, DOI 10.17487/RFC7480, March 2015, . [RFC7719] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS Terminology", RFC 7719, DOI 10.17487/RFC7719, December 2015, . Appendix A. Document History -A.1. regext Version 04 +A.1. regext Version 05 + + o new version to keep the draft alive + + o updating author organization + +A.2. regext Version 04 o changed uses of Registrar to Registration Entity and updated definitions to improve clarity o adding note about CDS/CDNSKEY interchangability in this document o added advice to scan all delegations (including insecure delegations) for CDS in order to bootstrap or update DNSSEC o removed "Other Delegation Maintenance" section, since we decided a while ago not to use this to update NS -A.2. regext Version 03 +A.3. regext Version 03 o simplify abstract o move all justification text to Intro o added HTTP response codes for rate limiting (429), missing DS RRsets (412) o expanded on Internationalization Considerations @@ -601,65 +608,63 @@ o expanded on Internationalization Considerations o corrected informative/normative document references o clarify parent/Registrar references in the draft o general spelling/grammar/style cleanup o removed references to NS and glue maintenance - o clarify content of POST body for 'cds' resource o change verb for obtaining a 'token' to GET o Updated reference to RFC8078 -A.3. regext Version 02 +A.4. regext Version 02 o Clarified based on comments and questions from early implementors (JL) o Text edits and clarifications. -A.4. regext Version 01 +A.5. regext Version 01 o Rewrote Abstract and Into (MP) o Introduced code 401 when changes are not allowed o Text edits and clarifications. -A.5. regext Version 00 +A.6. regext Version 00 o Working group document same as 03, just track changed to standard -A.6. Version 03 +A.7. Version 03 o Clarified based on comments and questions from early implementors -A.7. Version 02 +A.8. Version 02 o Reflected comments on mailing lists -A.8. Version 01 +A.9. Version 01 o This version adds a full REST definition this is based on suggestions from Jakob Schlyter. -A.9. Version 00 +A.10. Version 00 o First rough version Authors' Addresses - Jacques Latour CIRA Ottawa, ON Email: jacques.latour@cira.ca Olafur Gudmundsson Cloudflare, Inc. San Francisco, CA @@ -657,21 +662,22 @@ CIRA Ottawa, ON Email: jacques.latour@cira.ca Olafur Gudmundsson Cloudflare, Inc. San Francisco, CA Email: olafur+ietf@cloudflare.com + Paul Wouters Red Hat Toronto, ON Email: paul@nohats.ca Matthew Pounsett - Rightside Group, Ltd. + Nimbus Operations Inc. Toronto, ON Email: matt@conundrum.com