.au Registry Q. Pham Internet-Draft C. Wright Intended status: Informational AusRegistry Expires: January 2, 2016 July 2015 .au Extensions to the Extensible Provisioning Protocol au-extensions-1.2 Abstract This document describes application layer client-server protocol extensions for the Extensible Provisioning Protocol as needed for the management of domain objects stored in the .au Registry. Specified in XML, the protocol defines specific object management operations and an extensible framework that maps the protocol extensions to the relevant objects. This document includes a protocol specification, an object mapping template, and an XML media type registration. This document obsoletes the .au Extensions version 1.1. Status of this Memo This document is an Internet-Draft and is NOT offered in accordance with Section 10 of RFC 2026, and the author does not provide the IETF with any rights other than to publish as an Internet-Draft. 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 January 2, 2016. Pham & Wright Expires January 2, 2016 [Page 1] Internet-Draft .au Extensions to EPP July 2015 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. EPP . . . . . . . . . . . . . . . . . . . . . . . . 3 3. EPP . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.1. EPP Command . . . . . . . . . . . . . . . . . . . 4 3.2. EPP Response . . . . . . . . . . . . . . . . . . . 5 4. EPP . . . . . . . . . . . . . . . . . . . . . . 5 4.1. EPP Command . . . . . . . . . . . . . . . . 5 4.2. EPP Response . . . . . . . . . . . . . . . . 5 5. EPP . . . . . . . . . . . . . . . . . . . . . 8 5.1. EPP Command . . . . . . . . . . . . . . . 8 5.2. EPP Response . . . . . . . . . . . . . . . 11 6. EPP . . . . . . . . . . . . . . . . . . . . . 11 6.1. EPP Command . . . . . . . . . . . . . . . 11 6.2. EPP Response . . . . . . . . . . . . . . . 14 7. au Extensions . . . . . . . . . . . 14 7.1. au Extensions Command . . . . . 14 7.2. au Extensions Response . . . . 17 8. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 18 8.1. XML Schema [urn:X-au:params:xml:ns:auext-1.2] . . . . . . 18 8.2. XML Schema [urn:X-au:params:xml:ns:audomain-1.1] . . . . . 21 9. Security Considerations . . . . . . . . . . . . . . . . . . . 23 10. Normative References . . . . . . . . . . . . . . . . . . . . . 23 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 24 Pham & Wright Expires January 2, 2016 [Page 2] Internet-Draft .au Extensions to EPP July 2015 1. Introduction This document contains explanations of the relevant commands from the EPP RFCs that are affected by the inclusion of the au extensions. The use of these extensions by the client/server will be identified in the following commands as explained in the relevant sections below: o o EPP's command response extension framework [EPP RFC4930 2.7.3] is used to extend the following commands: o o And the following responses: o The following additional Protocol Extensions (object/operation extension) [EPP RFC4930 2.7.1] are defined: o 2. EPP All standard EPP elements apply plus: o A element that contains a element that includes the namespace URI representing the .au EPP extensions. Pham & Wright Expires January 2, 2016 [Page 3] Internet-Draft .au Extensions to EPP July 2015 Example with .au extensions specified: AusRegistry EPP Server 2006-02-09T15:42:29.0Z 1.0 en urn:ietf:params:xml:ns:domain-1.0 urn:ietf:params:xml:ns:contact-1.0 urn:ietf:params:xml:ns:host-1.0 urn:X-au:params:xml:ns:auext-1.2 urn:X-au:params:xml:ns:audomain-1.1 3. EPP The login command is not "extended" however the au extensions uri must be specified at time of login. 3.1. EPP Command In addition to the standard EPP elements, an EPP command must also include: o A element that contains a element that includes the namespace URI representing the .au EPP extensions Pham & Wright Expires January 2, 2016 [Page 4] Internet-Draft .au Extensions to EPP July 2015 Example EPP Login command with .au extensions specified: REGISTRAR p4ssw0rd! 1.0 en urn:ietf:params:xml:ns:contact-1.0 urn:ietf:params:xml:ns:domain-1.0 urn:ietf:params:xml:ns:host-1.0 urn:X-au:params:xml:ns:auext-1.2 urn:X-au:params:xml:ns:audomain-1.1 3.2. EPP Response No modifications are required. 4. EPP Extensions are provided to support the ability to view the current .au information associated with a particular domain stored within the registry system. 4.1. EPP Command No modifications required. 4.2. EPP Response In addition to the standard EPP elements found in a response a response should also conform to the following using an element that contains the extensions information specific to the domain. Pham & Wright Expires January 2, 2016 [Page 5] Internet-Draft .au Extensions to EPP July 2015 o An element which contains the .au extension information. * An element which contains the following elements: + An element that contains the name of the Registrant of the registered domain object. + An OPTIONAL element that contains the identifier for the Registrant's eligibility type. - Every element contains a "type" which identifies the type of the Registrant ID specified for the element. + An element that contains the Registrant's eligibility type. + An OPTIONAL element that contains the name of the individual or organisation that represents the Registrant which the eligibility is based on. + An OPTIONAL element that contains the identifier for the eligibility name. - Every element that contains a "type" which identifies the type of the eligibility ID specified for the element. + A element that contains the policy reason for which the domain object is registered under. Example response for an authorized client: Command completed successfully Pham & Wright Expires January 2, 2016 [Page 6] Internet-Draft .au Extensions to EPP July 2015 example.com.au D0000003-AR EXAMPLE EXAMPLE ns1.example.com.au ns2.example.com.au ns1.example.com.au ns2.exmaple.com.au Registrar Registrar 2006-02-09T15:44:58.0Z 2008-02-10T00:00:00.0Z 0192pqow RegistrantName Pty. Ltd. 123456789 Other Registrant Eligibility 987654321 2 ABC-12345 805 Pham & Wright Expires January 2, 2016 [Page 7] Internet-Draft .au Extensions to EPP July 2015 This .au Extension information is only returned to the sponsoring Registrar, all others will receive the response as below: Example response for an unauthorized client: Command completed successfully example.com.au D0000003-AR Registrar ABC-12345 805 5. EPP The EPP domain create command is extended to enable the client to supply the required .au information at time of registration. 5.1. EPP Command In addition to the standard EPP elements found in a command a command should also conform to the following using the element that contains the extension information specific to the domain being created. Pham & Wright Expires January 2, 2016 [Page 8] Internet-Draft .au Extensions to EPP July 2015 o A element which contains a number of elements that hold the information which is specific to the .au name space. * A element which contains the following child elements: + A element that contains the name of the Registrant of the requested domain object. + An OPTIONAL element that contains the identifier for the Registrant. - Every element MUST contain a "type" attribute that identifies the type of the Registrant ID specified by the element. + An element that contains the Registrant's eligibility type. + An OPTIONAL element that contains the name of the individual or organisation that represents the Registrant which the eligibility is based on. + An OPTIONAL element that contains the identifier for the eligibility name. - Every element MUST have a "type" attribute that identifies the type of the eligibility ID specified for the element. + A element that contains the policy reason for which the domain object registered under. Example command: Pham & Wright Expires January 2, 2016 [Page 9] Internet-Draft .au Extensions to EPP July 2015 example.com.au Registrant Tech2 0192pqow RegistrantName Pty. Ltd. 123456789 Other Registrant Eligibility 987654321 2 ABC-12345 Pham & Wright Expires January 2, 2016 [Page 10] Internet-Draft .au Extensions to EPP July 2015 5.2. EPP Response No modifications neccessary 6. EPP Extensions are provided to enable a client to make "corrections" to domain name .au information as required. 6.1. EPP Command In addition to the standard EPP elements found in a command a command can also conform to the following using the element that contains the extension information to be updated specific to the domain being updated. Note: these elements are equivilent to an EPP "chg" element, meaning that all information will be replaced with the new .au extension information supplied I.E. the entire .au extension unit is one atomic unit. o A element which contains a number of elements that hold the information which is specific to the .au name space: * A element which contains the following child elements: + A element that contains the name of the Registrant of the requested domain object. + An OPTIONAL element that contains the identifier for the Registrant. - Every element MUST contain a "type" attribute that identifies the type of the Registrant ID specified by the element. + An element that contains the Registrant's eligibility type. + An OPTIONAL element that contains the name of the individual or organisation that represents the Registrant which the eligibility is based on. + An OPTIONAL element that contains the identifier for the eligibility name. Pham & Wright Expires January 2, 2016 [Page 11] Internet-Draft .au Extensions to EPP July 2015 - Every element MUST have a "type" attribute that identifies the type of the eligibility ID specified for the element. + A element that contains the policy reason for which the domain object registered under. * A element MUST be provided. This element must contain an explanation as to the purpose of the update. For example a correction of a spelling mistake. It should be noted that these explanations are reviewed by the regulator and this update mechanism is NOT provided to facilitate transfer of Registrant. Example command: Pham & Wright Expires January 2, 2016 [Page 12] Internet-Draft .au Extensions to EPP July 2015 example.com.au Tech2 New Name 123456789 Other Registrant Eligibility 987654321 2 Registrant made spelling mistake during registration. ABC-12345 Pham & Wright Expires January 2, 2016 [Page 13] Internet-Draft .au Extensions to EPP July 2015 6.2. EPP Response No modifications necessary 7. au Extensions With this version of the .au extensions an additional command is added to allow a client to request a "transfer of domain registrant". 7.1. au Extensions Command This command is used to initiate a transfer of registrant of a domain name. A transfer of domain name from one registrant to another also results in a new license period for the domain name. An command is defined as follows: o An element which contains the following child elements: * An element which contains the following child elements: + An element which contains the following child elements: - An element MUST be provided which specifies the fully qualifed name of the domain of which the registrant should be transfered. - An element MUST be provided which specifies the current expiry date of the domain. - An element that specifies the period for which the new registrant wants the name to be registered - A element that contains the following child elements: o A element MUST be provided. This element MUST contain an english readable string for the Registrant's name. o An OPTIONAL element that represents the identifier for the Registrant. Pham & Wright Expires January 2, 2016 [Page 14] Internet-Draft .au Extensions to EPP July 2015 * Every element MUST contain a "type" attribute that identifies the type of the Registrant ID specified by the element. o An element that contains the Registrant's eligibility type. o An OPTIONAL element that contains the name of the individual or organisation that represents the Registrant which the eligibility is based on. o An OPTIONAL element that contains the identifier for the eligibility name. * Every element MUST have a "type" attribute that identifies the type of the eligibility ID specified for the element. o A element that contains the policy reason for which the domain object registered under. - A element MUST be provided. This element must contain an explanation as to the purpose of the update For example a correction of a spelling mistake. It should be noted that these explanations are reviewed by the regulator and this update mechanism is NOT provided to facilitate transfer of registrant. * An OPTIONAL element which contains the client supplied identifier for the transaction. Pham & Wright Expires January 2, 2016 [Page 15] Internet-Draft .au Extensions to EPP July 2015 Example command: domain.com.au 2000-04-03 2 New Name 123456789 Other Registrant Eligibility 987654321 2 Previous registrant has sold the business ABC-12345 Pham & Wright Expires January 2, 2016 [Page 16] Internet-Draft .au Extensions to EPP July 2015 7.2. au Extensions Response The following response will be returned from the au extensions command: o An element that contains the same child elements as the epp:response type does (see EPP RFC). The resData section of this response contains the following: o An element that contains the following child elements: * A element that contains the fully qualified name of the domain to which the registrant transfer was applied. * A element that contains the new expiry date of the domain after the registrant transfer. Pham & Wright Expires January 2, 2016 [Page 17] Internet-Draft .au Extensions to EPP July 2015 Example response: Command completed successfully domain.com.au 2005-04-03T22:00:00.0Z ABC-12345 2389742981742 8. Formal Syntax 8.1. XML Schema [urn:X-au:params:xml:ns:auext-1.2] .au Extensions to the Extensible Provisioning Protocol v1.2 schema. Pham & Wright Expires January 2, 2016 [Page 20] Internet-Draft .au Extensions to EPP July 2015 8.2. XML Schema [urn:X-au:params:xml:ns:audomain-1.1] .au Domain Extensions to the Extensible Provisioning Protocol v1.0. schema. 9. 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. 10. Normative References [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, . Pham & Wright Expires January 2, 2016 [Page 23] Internet-Draft .au Extensions to EPP July 2015 Authors' Addresses Quoc Pham AusRegistry 8/10 Queens Road Melbourne, Victoria 3004 AU Email: quoc.pham@ausregistry.com.au URI: www.ausregistry.com Chris Wright AusRegistry 8/10 Queens Road Melbourne, Victoria 3004 AU Email: chris@ausregistry.com URI: www.ausregistry.com Pham & Wright Expires January 2, 2016 [Page 24]