Internet Engineering Task Force G. Lozano Internet-Draft ICANN Intended status: Standards Track June 16, 2016 Expires: December 18, 2016 Registrar Registration Expiration Date Extension Mapping for the Extensible Provisioning Protocol (EPP) draft-lozano-ietf-eppext-registrar-expiration-date-01 Abstract This document describes an Extensible Provisioning Protocol (EPP) extension mapping for the provisioning and management of the registrar registration expiration date for domain names stored in a shared central repository. Specified in XML, this mapping extends the EPP domain name mapping. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. 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 December 18, 2016. Copyright Notice Copyright (c) 2016 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 Lozano Expires December 18, 2016 [Page 1] Internet-Draft Registrar Registration Expiration Date June 2016 the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 2. Object Elements . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Synchronize Registry and Registrar Expiration Date . . . 3 2.2. Registrar Registration Expiration Date . . . . . . . . . 4 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 4 3.1. EPP Query commands . . . . . . . . . . . . . . . . . . . 4 3.2. EPP Transform commands . . . . . . . . . . . . . . . . . 6 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 12 4.1. rrExDate Schema . . . . . . . . . . . . . . . . . . . . . 12 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 7. Internationalization Considerations . . . . . . . . . . . . . 14 8. Security Considerations . . . . . . . . . . . . . . . . . . . 14 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 9.1. Normative References . . . . . . . . . . . . . . . . . . 14 9.2. Informative References . . . . . . . . . . . . . . . . . 15 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 15 1. Introduction This document describes an extension mapping for version 1.0 of the Extensible Provisioning Protocol (EPP) described in RFC [RFC5730]. This mapping, an extension of the domain name mapping described in RFC [RFC5731], is specified using the Extensible Markup Language (XML) 1.0 [W3C.REC-xml] and XML Schema notation ([W3C.REC-xmlschema-1] [W3C.REC-xmlschema-2]). The EPP core protocol specification [RFC5730] provides a complete description of EPP command and response structures. A thorough understanding of the base protocol specification is necessary to understand the mapping described in this document. This document is written following the Guidelines for Extending the Extensible Provisioning Protocol as defined in [RFC3735]. This extension is defined in order to support the Internet Corporation for Assigned Names and Numbers (ICANN) Thick Whois Policy Recommendation [ThickWhoisPolicy] that allows gTLD domain name registries to display the registrar registration expiration date in the Registration Data Directory Service (e.g. Whois, RDAP). Lozano Expires December 18, 2016 [Page 2] Internet-Draft Registrar Registration Expiration Date June 2016 1.1. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. In examples, "C:" represents lines sent by a protocol client, and "S:" represents lines returned by a protocol server. "////" is used to note element values that have been shortened to better fit page boundaries. Indentation and white space in examples is provided only to illustrate element relationships and is not a mandatory feature of this protocol. XML is case sensitive. Unless stated otherwise, XML specifications and examples provided in this document MUST be interpreted in the character case presented in order to develop a conforming implementation. rrExDate-1.0 is used as an abbreviation for urn:ietf:params:xml:ns:rrExDate-1.0. The XML namespace prefix "rrExDate" is used, but implementations MUST NOT depend on it and instead employ a proper namespace-aware XML parser and serializer to interpret and output the XML documents. 2. Object Elements This extension adds additional elements to the EPP domain name mapping [RFC5731]. Only those new elements are described here. 2.1. Synchronize Registry and Registrar Expiration Date A element MUST contain a "flag" attribute. The "flag" attribute contains an XML Schema boolean value. A value of "true" or "1" (one) indicates that the registrar registration expiration date shall have the same value as the registry expiration date of the domain object () at all times. A value of "false" or "0" (zero) indicates that the registrar registration expiration date is defined in . A value of "false" or "0" (zero) without an element indicates that the registrar registration expiration date is not defined, or shall be removed, as the case may be. Lozano Expires December 18, 2016 [Page 3] Internet-Draft Registrar Registration Expiration Date June 2016 2.2. Registrar Registration Expiration Date An OPTIONAL element is used by the registrar to specify the value of the registrar registration expiration date. The element MUST NOT be included, if the "flag" attribute in is set to "true" or "1" (one). 3. EPP Command Mapping A detailed description of the EPP syntax and semantics can be found in the EPP core protocol specification [RFC5730]. The command mappings described here are specifically for use in provisioning and managing of the registrar registration expiration date via EPP. 3.1. EPP Query commands EPP provides three commands to retrieve object information: to determine if an object is known to the server, to retrieve detailed information associated with an object, and to retrieve object transfer status information. 3.1.1. EPP command This extension does not add any elements to the EPP command or response described in the EPP domain mapping [RFC5731]. 3.1.2. EPP command This extension does not add any elements to the EPP command, but does include elements in the response. After an info command has been processed successfully, the server MUST include a object in the section of the EPP response. Example response for a domain object: Lozano Expires December 18, 2016 [Page 4] Internet-Draft Registrar Registration Expiration Date June 2016 S: S: S: S: S: Command completed successfully S: S: S: S: example.com S: EXAMPLE1-REP S: S: jd1234 S: sh8013 S: sh8013 S: S: ns1.example.com S: ns1.example.net S: S: ClientX S: ClientY S: 1999-04-03T22:00:00.0Z S: ClientX S: 1999-12-03T09:00:00.0Z S: 2005-04-03T22:00:00.0Z S: 2000-04-08T09:00:00.0Z S: S: 2fooBAR S: S: S: S: S: S: S: S: 2004-04-03T22:00:00.0Z S: S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: Lozano Expires December 18, 2016 [Page 5] Internet-Draft Registrar Registration Expiration Date June 2016 3.1.3. EPP command This extension does not add any elements to the EPP command, but does include elements in the response. A response to a query command MUST include a object in the section of the EPP response. Example query response: S: S: S: S: S: Command completed successfully S: S: S: S: example.com S: pending S: ClientX S: 2000-06-06T22:00:00.0Z S: ClientY S: 2000-06-11T22:00:00.0Z S: 2002-09-08T22:00:00.0Z S: S: S: S: S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: 3.2. EPP Transform commands The following general requirements apply to the , , , and commands: Lozano Expires December 18, 2016 [Page 6] Internet-Draft Registrar Registration Expiration Date June 2016 A server MUST return a 2004 response code when receiving an EPP transform command that includes this extension with a value in the element that precedes the creation date of the domain object (). A server MUST return a 2002 response code when receiving an EPP transform command that includes this extension with a element, and a value of "true" or "1" (one) in the "flag" attribute in the element. 3.2.1. EPP command This extension defines additional elements for the EPP command. The general requirements for EPP transform commands described above apply to the EPP command. This extension does not add any elements to the EPP response described in the EPP domain mapping [RFC5731]. Example command: Lozano Expires December 18, 2016 [Page 7] Internet-Draft Registrar Registration Expiration Date June 2016 C: C: C: C: C: C: example.com C: 2 C: C: ns1.example.net C: ns2.example.net C: C: jd1234 C: sh8013 C: sh8013 C: C: 2fooBAR C: C: C: C: C: C: C: C: 2004-04-03T22:00:00.0Z C: C: C: C: C: ABC-12345 C: C: Example command that sets the registrar registration expiration date to the expiration date of the domain object (), if the domain is successfully created: Lozano Expires December 18, 2016 [Page 8] Internet-Draft Registrar Registration Expiration Date June 2016 C: C: C: C: C: C: example.com C: 2 C: C: ns1.example.net C: ns2.example.net C: C: jd1234 C: sh8013 C: sh8013 C: C: 2fooBAR C: C: C: C: C: C: C: C: C: ABC-12345 C: C: 3.2.2. EPP command This extension does not add any elements to the EPP command or response described in the EPP domain mapping [RFC5731]. 3.2.3. EPP command This extension defines additional elements for the EPP command. The general requirements for EPP transform commands described above apply to the EPP command. This extension does not add any elements to the EPP response described in the EPP domain mapping [RFC5731]. Example command: Lozano Expires December 18, 2016 [Page 9] Internet-Draft Registrar Registration Expiration Date June 2016 C: C: C: C: C: C: example.com C: 2000-04-03 C: 5 C: C: C: C: C: C: C: 2005-04-03T22:00:00.0Z C: C: C: C: C: ABC-12345 C: C: 3.2.4. EPP command This extension defines additional elements for the EPP command. The general requirements for EPP transform commands described above apply to the EPP command. This extension does not add any elements to the EPP response described in the EPP domain mapping [RFC5731]. Example command: Lozano Expires December 18, 2016 [Page 10] Internet-Draft Registrar Registration Expiration Date June 2016 C: C: C: C: C: C: example.com C: 1 C: C: 2fooBAR C: C: C: C: C: C: C: C: 2004-04-03T22:00:00.0Z C: C: C: C: C: ABC-12345 C: C: 3.2.5. EPP command This extension defines additional elements for the EPP command. The general requirements for EPP transform commands described above apply to the EPP command. This extension does not add any elements to the EPP response described in the EPP domain mapping [RFC5731]. Example command: Lozano Expires December 18, 2016 [Page 11] Internet-Draft Registrar Registration Expiration Date June 2016 C: C: C: C: C: C: example.com C: C: C: C: C: C: C: 2006-04-03T22:00:00.0Z C: C: C: C: C: ABC-12345 C: C: 4. Formal Syntax An EPP object mapping is specified in XML Schema notation. The formal syntax presented here is a complete schema representation of the object mapping suitable for automated validation of EPP XML instances. 4.1. rrExDate Schema Copyright (c) 2016 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). Lozano Expires December 18, 2016 [Page 12] Internet-Draft Registrar Registration Expiration Date June 2016 BEGIN Extensible Provisioning Protocol v1.0 domain name extension schema for implementing the ICANN thick whois policy. END 5. Acknowledgements The author would like to acknowledge the following individuals for their contributions to this document: Patrick Mevzek. 6. IANA Considerations This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in [RFC3688]. Two URI assignments have been registered by the IANA. Registration request for the rrExDate namespace: URI: urn:ietf:params:xml:ns:rrExDate-1.0" Registrant Contact: IESG XML: None. Namespace URIs do not represent an XML specification. Lozano Expires December 18, 2016 [Page 13] Internet-Draft Registrar Registration Expiration Date June 2016 Registration request for the rrExDate schema: URI: urn:ietf:params:xml:schema:rrExDate-1.0" Registrant Contact: IESG XML: See the "Formal Syntax" section of this document. 7. Internationalization Considerations The internationalization considerations of EPP described in [RFC5730] apply to this specification as well. 8. Security Considerations The mapping extensions described in this document do not provide any security services beyond those described by EPP [RFC5730], the EPP domain name mapping [RFC5731], and protocol layers used by EPP. The security considerations described in these other specifications apply to this specification as well. 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, . [RFC3735] Hollenbeck, S., "Guidelines for Extending the Extensible Provisioning Protocol (EPP)", RFC 3735, DOI 10.17487/RFC3735, March 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, . Lozano Expires December 18, 2016 [Page 14] Internet-Draft Registrar Registration Expiration Date June 2016 [W3C.REC-xml] W3C, "Extensible Markup Language (XML) 1.0 (Second Edition)", Oct 2000, . [W3C.REC-xmlschema-1] W3C, "XML Schema Part 1: Structures Second Edition", Oct 2004, . [W3C.REC-xmlschema-2] W3C, "XML Schema Part 2: Structures Second Edition", Oct 2004, . 9.2. Informative References [ThickWhoisPolicy] ICANN, "GNSO Council Policy Recommendations for a new Consensus Policy on Thick Whois", Oct 2013, . Author's Address Gustavo Lozano ICANN 12025 Waterfront Drive, Suite 300 Los Angeles 90292 US Phone: +1.3103015800 Email: gustavo.lozano@icann.org Lozano Expires December 18, 2016 [Page 15]