--- 1/draft-ietf-regext-launchphase-02.txt 2017-04-24 06:13:29.730287068 -0700 +++ 2/draft-ietf-regext-launchphase-03.txt 2017-04-24 06:13:29.838289647 -0700 @@ -1,21 +1,21 @@ Internet Engineering Task Force J. Gould Internet-Draft VeriSign, Inc. Intended status: Standards Track W. Tan -Expires: April 30, 2017 Cloud Registry +Expires: October 26, 2017 Cloud Registry G. Brown CentralNic Ltd - October 27, 2016 + April 24, 2017 Launch Phase Mapping for the Extensible Provisioning Protocol (EPP) - draft-ietf-regext-launchphase-02 + draft-ietf-regext-launchphase-03 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,25 +25,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 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 April 30, 2017. + This Internet-Draft will expire on October 26, 2017. Copyright Notice - Copyright (c) 2016 IETF Trust and the persons identified as the + 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 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 @@ -98,38 +98,39 @@ 6.7. gTLD Shared Registry System . . . . . . . . . . . . . . . 55 7. Security Considerations . . . . . . . . . . . . . . . . . . . 56 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 56 9. Normative References . . . . . . . . . . . . . . . . . . . . 57 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 57 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 57 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 57 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 . . . . . . . . . . . . . . . . . . 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.16. Change EPPEXT 02 to EPPEXT 03 . . . . . . . . . . . . . . 61 + 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.21. Change from EPPEXT 07 to REGEXT 00 . . . . . . . . . . . 62 + 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 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 63 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. @@ -2327,40 +2328,48 @@ 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 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate - Requirement Levels", BCP 14, RFC 2119, March 1997. + Requirement Levels", BCP 14, RFC 2119, + DOI 10.17487/RFC2119, March 1997, + . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, - January 2004. + DOI 10.17487/RFC3688, January 2004, + . [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", - STD 69, RFC 5730, August 2009. + STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, + . [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) - Domain Name Mapping", STD 69, RFC 5731, August 2009. + 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, July - 2013. + Code: The Implementation Status Section", RFC 6982, + DOI 10.17487/RFC6982, July 2013, + . [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible - Provisioning Protocol", RFC 7451, February 2015. + 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, + [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]". @@ -2622,20 +2630,24 @@ 1. Fixed reference of Claims Check Command to Trademark Check Command in the Trademark Check Form section. 2. Replaced reference of draft-ietf-eppext-tmch-smd to RFC 7848. A.23. Change from REGEXT 01 to REGEXT 02 1. Removed the reference to ietf-regext-tmch-func-spec and briefly described the trademark claims phase that is relavent to draft- ietf-regext-launchphase. +A.24. Change from REGEXT 02 to REGEXT 03 + + 1. Ping update. + Authors' Addresses James Gould VeriSign, Inc. 12061 Bluemont Way Reston, VA 20190 US Email: jgould@verisign.com URI: http://www.verisigninc.com