--- 1/draft-ietf-regext-launchphase-04.txt 2017-06-22 15:13:08.978166468 -0700 +++ 2/draft-ietf-regext-launchphase-05.txt 2017-06-22 15:13:09.086169053 -0700 @@ -1,21 +1,21 @@ Internet Engineering Task Force J. Gould Internet-Draft VeriSign, Inc. Intended status: Standards Track W. Tan -Expires: October 29, 2017 Cloud Registry +Expires: December 24, 2017 Cloud Registry G. Brown CentralNic Ltd - April 27, 2017 + June 22, 2017 Launch Phase Mapping for the Extensible Provisioning Protocol (EPP) - draft-ietf-regext-launchphase-04 + draft-ietf-regext-launchphase-05 Abstract This document describes an Extensible Provisioning Protocol (EPP) extension mapping for the provisioning and management of domain name registrations and applications during the launch of a domain name registry. Status of This Memo @@ -25,21 +25,21 @@ 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 http://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 October 29, 2017. + This Internet-Draft will expire on December 24, 2017. Copyright Notice Copyright (c) 2017 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 (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -50,21 +50,21 @@ described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Conventions Used in This Document . . . . . . . . . . . . 4 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 5 2.1. Application Identifier . . . . . . . . . . . . . . . . . 5 2.2. Validator Identifier . . . . . . . . . . . . . . . . . . 5 2.3. Launch Phases . . . . . . . . . . . . . . . . . . . . . . 6 - 2.3.1. Trademark Claims Phase . . . . . . . . . . . . . . . 6 + 2.3.1. Trademark Claims Phase . . . . . . . . . . . . . . . 7 2.4. Status Values . . . . . . . . . . . . . . . . . . . . . . 9 2.4.1. State Transition . . . . . . . . . . . . . . . . . . 10 2.5. Poll Messaging . . . . . . . . . . . . . . . . . . . . . 11 2.6. Mark Validation Models . . . . . . . . . . . . . . . . . 14 2.6.1. element . . . . . . . . . . . . . . 15 2.6.2. element . . . . . . . . . . . . . . . . . 16 2.6.3. Digital Signature . . . . . . . . . . . . . . . . . . 16 2.6.3.1. element . . . . . . . . . . . . 16 2.6.3.2. element . . . . . . . . . 16 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 16 @@ -91,48 +91,51 @@ 6. Implementation Status . . . . . . . . . . . . . . . . . . . . 52 6.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 53 6.2. Verisign Consolidated Top Level Domain (CTLD) SRS . . . . 53 6.3. Verisign .COM / .NET SRS . . . . . . . . . . . . . . . . 54 6.4. REngin v3.7 . . . . . . . . . . . . . . . . . . . . . . . 54 6.5. RegistryEngine EPP Service . . . . . . . . . . . . . . . 54 6.6. Neustar EPP SDK . . . . . . . . . . . . . . . . . . . . . 55 6.7. gTLD Shared Registry System . . . . . . . . . . . . . . . 55 7. Security Considerations . . . . . . . . . . . . . . . . . . . 56 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 56 - 9. Normative References . . . . . . . . . . . . . . . . . . . . 57 + 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 57 + 9.1. Normative References . . . . . . . . . . . . . . . . . . 57 + 9.2. Informative References . . . . . . . . . . . . . . . . . 57 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 57 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 57 - A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 57 + A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 58 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 58 A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 58 A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 58 A.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 59 A.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 59 A.8. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 59 A.9. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 59 A.10. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 60 A.11. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 61 A.12. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 61 A.13. Change from 12 to EPPEXT 00 . . . . . . . . . . . . . . . 61 A.14. Change EPPEXT 00 to EPPEXT 01 . . . . . . . . . . . . . . 61 - A.15. Change EPPEXT 01 to EPPEXT 02 . . . . . . . . . . . . . . 61 + A.15. Change EPPEXT 01 to EPPEXT 02 . . . . . . . . . . . . . . 62 A.16. Change EPPEXT 02 to EPPEXT 03 . . . . . . . . . . . . . . 62 A.17. Change EPPEXT 03 to EPPEXT 04 . . . . . . . . . . . . . . 62 A.18. Change EPPEXT 04 to EPPEXT 05 . . . . . . . . . . . . . . 62 A.19. Change EPPEXT 05 to EPPEXT 06 . . . . . . . . . . . . . . 62 - A.20. Change EPPEXT 06 to EPPEXT 07 . . . . . . . . . . . . . . 62 + A.20. Change EPPEXT 06 to EPPEXT 07 . . . . . . . . . . . . . . 63 A.21. Change from EPPEXT 07 to REGEXT 00 . . . . . . . . . . . 63 A.22. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 63 A.23. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 63 A.24. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 63 A.25. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 63 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 63 + A.26. Change from REGEXT 04 to REGEXT 05 . . . . . . . . . . . 64 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 64 1. Introduction This document describes an extension mapping for version 1.0 of the Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping specifies a flexible schema that can be used to implement several common use cases related to the provisioning and management of domain name registrations and applications during the launch of a domain name registry. @@ -2118,36 +2121,36 @@ IPR Disclosure: None Status: Active Notes: None 6. Implementation Status Note to RFC Editor: Please remove this section and the reference to - RFC 6982 [RFC6982] before publication. + RFC 7942 [RFC7942] before publication. This section records the status of known implementations of the protocol defined by this specification at the time of posting of this - Internet-Draft, and is based on a proposal described in RFC 6982 - [RFC6982]. The description of implementations in this section is + Internet-Draft, and is based on a proposal described in RFC 7942 + [RFC7942]. The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs. Please note that the listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist. - According to RFC 6982 [RFC6982], "this will allow reviewers and + According to RFC 7942 [RFC7942], "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit". 6.1. Verisign EPP SDK Organization: Verisign Inc. @@ -2325,53 +2328,57 @@ were provided by Jothan Frakes, Keith Gaughan, Seth Goldman, Scott Hollenbeck, Michael Holloway, Jan Jansen, Rubens Kuhl, Ben Levac, Gustavo Lozano, Klaus Malorny, Alexander Mayrhofer, Patrick Mevzek, James Mitchell, Francisco Obispo, Mike O'Connell, Bernhard Reutner- Fischer, Trung Tran, Ulrich Wisser and Sharon Wodjenski. Some of the description of the Trademark Claims Phase was based on the work done by Gustavo Lozano in the ICANN TMCH functional specifications. -9. Normative References +9. References + +9.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, . [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, . [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Domain Name Mapping", STD 69, RFC 5731, DOI 10.17487/RFC5731, August 2009, . - [RFC6982] Sheffer, Y. and A. Farrel, "Improving Awareness of Running - Code: The Implementation Status Section", RFC 6982, - DOI 10.17487/RFC6982, July 2013, - . + [RFC7848] Lozano, G., "Mark and Signed Mark Objects Mapping", + RFC 7848, DOI 10.17487/RFC7848, June 2016, + . + + [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running + Code: The Implementation Status Section", BCP 205, + RFC 7942, DOI 10.17487/RFC7942, July 2016, + . + +9.2. Informative References [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, February 2015, . - [RFC7848] Lozano, G., "Mark and Signed Mark Objects Mapping", - RFC 7848, DOI 10.17487/RFC7848, June 2016, - . - Appendix A. Change History A.1. Change from 00 to 01 1. Changed to use camel case for the XML elements. 2. Replaced "cancelled" status to "rejected" status. 3. Added the child elements of the element. 4. Removed the XML schema and replaced with "[TBD]". A.2. Change from 01 to 02 @@ -2651,21 +2657,29 @@ 3. Removed the second paragraph of section 2.1 describing the option of creating an application identifier for a Launch Registration. 4. Provided clarification in section 2.2 on the responsibility of the server to ensure that the supported validator identifiers are unique. 5. Updated the text in section 2.5 referencing the domain name object in RFC 5731. 6. Updated the copyright to 2017 in section 4.1. +A.26. Change from REGEXT 04 to REGEXT 05 + + 1. Updates based on feedback from Ulrich Wisser that include: + + 1. Updated reference to obsoleted RFC 6982 with RFC 7942. + 2. Moved RFC 7451 reference from normative to informative. + Authors' Addresses + James Gould VeriSign, Inc. 12061 Bluemont Way Reston, VA 20190 US Email: jgould@verisign.com URI: http://www.verisigninc.com Wil Tan