[Docs] [txt|pdf] [Tracker] [Email] [Diff1] [Diff2] [Nits]
Versions: 00 01 02

    Internet Engineering Task Force                                  L. Zhou
    Internet-Draft                                                   N. Kong
    Intended status: Standards Track                                   CNNIC
    Expires: April 14, 2016                                            C. Qi
                                                                    Teleinfo
                                                                      X. Lee
                                                                       CNNIC
                                                                    J. Gould
                                                              VeriSign, Inc.
                                                            October 12, 2015

       Reseller Extension for the Extensible Provisioning Protocol (EPP)
                         draft-zhou-eppext-reseller-02

    Abstract

       This mapping, an extension to EPP object mappings like the EPP domain
       name mapping [RFC5731], to support assigning a reseller to any
       existing object (domain, host, contact) as well as any future
       objects.  Specified in Extensible Markup Language (XML), this
       extended mapping is applied to provide additional features required
       for the provisioning of resellers.

    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 April 14, 2016.

    Copyright Notice

       Copyright (c) 2015 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

    Zhou, et al.             Expires April 14, 2016                 [Page 1]

    Internet-Draft       Reseller Extension for the EPP         October 2015

       (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
       described in the Simplified BSD License.

       This document may contain material from IETF Documents or IETF
       Contributions published or made publicly available before November
       10, 2008.  The person(s) controlling the copyright in some of this
       material may not have granted the IETF Trust the right to allow
       modifications of such material outside the IETF Standards Process.
       Without obtaining an adequate license from the person(s) controlling
       the copyright in such materials, this document may not be modified
       outside the IETF Standards Process, and derivative works of it may
       not be created outside the IETF Standards Process, except to format
       it for publication as an RFC or to translate it into languages other
       than English.

    Table of Contents

       1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
       2.  Conventions Used in This Document . . . . . . . . . . . . . .   3
       3.  Object Attributes . . . . . . . . . . . . . . . . . . . . . .   4
         3.1.  Reseller Identifier . . . . . . . . . . . . . . . . . . .   4
         3.2.  Reseller Name . . . . . . . . . . . . . . . . . . . . . .   4
       4.  EPP Command Mapping . . . . . . . . . . . . . . . . . . . . .   4
         4.1.  EPP Query Commands  . . . . . . . . . . . . . . . . . . .   4
           4.1.1.  EPP <check> Command . . . . . . . . . . . . . . . . .   4
           4.1.2.  EPP <info> Command  . . . . . . . . . . . . . . . . .   4
           4.1.3.  EPP <transfer> Command  . . . . . . . . . . . . . . .   7
         4.2.  EPP Transform Commands  . . . . . . . . . . . . . . . . .   7
           4.2.1.  EPP <create> Command  . . . . . . . . . . . . . . . .   7
           4.2.2.  EPP <delete> Command  . . . . . . . . . . . . . . . .   8
           4.2.3.  EPP <renew> Command . . . . . . . . . . . . . . . . .   8
           4.2.4.  EPP <transfer> Command  . . . . . . . . . . . . . . .   9
           4.2.5.  EPP <update> Command  . . . . . . . . . . . . . . . .   9
       5.  Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . .  11
       6.  Internationalization Considerations . . . . . . . . . . . . .  13
       7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
         7.1.  XML Namespace . . . . . . . . . . . . . . . . . . . . . .  13
         7.2.  EPP Extension Registry  . . . . . . . . . . . . . . . . .  14
       8.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
       9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
         9.1.  Normative References  . . . . . . . . . . . . . . . . . .  14
         9.2.  Informative References  . . . . . . . . . . . . . . . . .  16
       Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . .  16

    Zhou, et al.             Expires April 14, 2016                 [Page 2]

    Internet-Draft       Reseller Extension for the EPP         October 2015

       Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16

    1.  Introduction

       Domain resellers are the individuals or companies act as agents for
       ICANN accredited registrars.  A domain name registrar may have
       several resellers to help them sell domain names to end users.

       Generally speaking, resellers provide domain registration information
       via registrar's EPP client without reseller information.  On one
       hand, registrars are concerned about how to identify resellers.  On
       the other hand, end users would also be confused by the WHOIS service
       without corresponding reseller information.  This requirement imposes
       a challenge for the domain registries since there is no definition of
       resellers in the existing EPP domain name mapping.  Out of band
       method could solve this problem but may increase extra cost.

       In order to facilitate provisioning and management of reseller
       information in a shared central repository, this document proposes a
       reseller extension of [RFC5731], [RFC5732] and [RFC5733].  The
       examples provided in this document are used for the domain object for
       illustration purposes.  The host and contact object could be extended
       in the same way with the domain object.

       A reseller mapping object defined in
       [ID.draft-zhou-eppext-reseller-mapping] SHOULD be created first.  The
       reseller information specified in this document SHOULD reference the
       existing reseller identifier and reseller name.

       This document is specified using the XML 1.0 as described in
       [W3C.REC-xml-20040204] and XML Schema notation as described in
       [W3C.REC-xmlschema-1-20041028] and [W3C.REC-xmlschema-2-20041028].

    2.  Conventions Used in This Document

       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 [RFC2119].

       In examples, "C:" represents lines sent by a protocol client and "S:"
       represents lines returned by a protocol server.  Indentation and
       white space in examples are provided only to illustrate element
       relationships and are not a REQUIRED feature of this specification.

       XML is case sensitive.  Unless stated otherwise, XML specifications
       and examples provided in this document MUST be interpreted in the
       character case presented to develop a conforming implementation.

    Zhou, et al.             Expires April 14, 2016                 [Page 3]

    Internet-Draft       Reseller Extension for the EPP         October 2015

       resellerext-1.0 in this document is used as an abbreviation for
       urn:ietf:params:xml:ns:resellerext-1.0.

    3.  Object Attributes

       This extension adds additional elements to the EPP domain name
       mapping [RFC5731].  Only the new elements are described here.

    3.1.  Reseller Identifier

       Reseller identifier provides the ID of the reseller of a sponsoring
       registrar.  Its corresponding element is <resellerext:id> which
       refers to the <resellerext:id> element defined in
       [ID.draft-zhou-eppext-reseller-mapping].

    3.2.  Reseller Name

       Reseller name provides the name of the reseller of a sponsoring
       registrar.  Its corresponding element is <resellerext:name> which
       refers to the <resellerext:name> element defined in
       [ID.draft-zhou-eppext-reseller-mapping].

    4.  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 reseller information via EPP.

    4.1.  EPP Query Commands

       EPP provides three commands to retrieve domain information: <check>
       to determine if a domain object can be provisioned within a
       repository, <info> to retrieve detailed information associated with a
       domain object, and <transfer> to retrieve domain-object transfer
       status information.

    4.1.1.  EPP <check> Command

       This extension does not add any elements to the EPP <check> command
       or <check> response described in the EPP domain name mapping
       [RFC5731], host mapping [RFC5732] and contact mapping [RFC5733].

    4.1.2.  EPP <info> Command

       This extension does not add any element to the EPP <info> command
       described in the EPP domain mapping [RFC5731], host mapping [RFC5732]

    Zhou, et al.             Expires April 14, 2016                 [Page 4]

    Internet-Draft       Reseller Extension for the EPP         October 2015

       and contact mapping [RFC5733].  However, additional elements are
       defined for the <info> response.

       Example <info> command:

      C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
      C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
      C:  <command>
      C:    <info>
      C:      <domain:info xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
      C:        <domain:name>example.com</domain:name>
      C:        <domain:authInfo>
      C:          <domain:pw>fooBAR</domain:pw>
      C:        </domain:authInfo>
      C:      </domain:info>
      C:    </info>
      C:    <clTRID>ngcl-mIFICBNP</clTRID>
      C:  </command>
      C:</epp>

       When an <info> command has been processed successfully, the EPP
       <resData> element MUST contain child elements as described in the EPP
       domain mapping [RFC5731], host mapping [RFC5732] and contact mapping
       [RFC5733].  In addition, the EPP <extension> element SHOULD contain a
       child <resellerext:infData> element that identifies the extension
       namespace if the domain object has data associated with this
       extension and based on its service policy.  The <resellerext:infData>
       element contains the following child elements:

       o  A <resellerext:id> element that contains the identifier of the
          reseller of a sponsoring registrar.

       o  An OPTIONAL <resellerext:name> element that contains the name of
          the reseller of a sponsoring registrar.

       Example <info> response for an authorized client:

    Zhou, et al.             Expires April 14, 2016                 [Page 5]

    Internet-Draft       Reseller Extension for the EPP         October 2015

    S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
    S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
    S:  <response>
    S:    <result code="1000">
    S:      <msg lang="en-US">Command completed successfully</msg>
    S:    </result>
    S:    <resData>
    S:      <domain:infData xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
    S:        <domain:name>example.com</domain:name>
    S:        <domain:roid>EXAMPLE1-REP</domain:roid>
    S:        <domain:status s="ok"/>
    S:        <domain:registrant>jd1234</domain:registrant>
    S:        <domain:contact type="admin">sh8013</domain:contact>
    S:        <domain:contact type="billing">sh8013</domain:contact>
    S:        <domain:contact type="tech">sh8013</domain:contact>
    S:        <domain:ns>
    S:          <domain:hostObj>ns1.example.com</domain:hostObj>
    S:        </domain:ns>
    S:        <domain:clID>ClientX</domain:clID>
    S:        <domain:crID>ClientY</domain:crID>
    S:        <domain:crDate>2015-02-06T04:01:21.0Z</domain:crDate>
    S:        <domain:exDate>2018-02-06T04:01:21.0Z</domain:exDate>
    S:        <domain:authInfo>
    S:          <domain:pw>2fooBAR</domain:pw>
    S:        </domain:authInfo>
    S:      </domain:infData>
    S:    </resData>
    S:    <extension>
    S:      <rgp:infData xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0">
    S:        <rgp:rgpStatus s="addPeriod"/>
    S:      </rgp:infData>
    S:      <resellerext:infData xmlns:resellerext="urn:ietf:params:xml:ns:resellerext-1.0">
    S:        <resellerext:id>myreseller</resellerext:id>
    S:        <resellerext:name>example</resellerext:name>
    S:      </resellerext:infData>
    S:    </extension>
    S:    <trID>
    S:      <clTRID>ngcl-IvJjzMZc</clTRID>
    S:      <svTRID>test142AWQONJZ</svTRID>
    S:    </trID>
    S:  </response>
    S:</epp>

       <info> response for the unauthorized client has not been changed, see
       [RFC5731], [RFC5732] and [RFC5733]for detail.

    Zhou, et al.             Expires April 14, 2016                 [Page 6]

    Internet-Draft       Reseller Extension for the EPP         October 2015

       An EPP error response MUST be returned if an <info> command cannot be
       processed for any reason.

    4.1.3.  EPP <transfer> Command

       This extension does not add any elements to the EPP <transfer>
       command or <transfer> response described in the EPP domain name
       mapping [RFC5731], host mapping [RFC5732] and contact mapping
       [RFC5733].

    4.2.  EPP Transform Commands

       EPP provides five commands to transform domain objects: <create> to
       create an instance of a domain object, <delete> to delete an instance
       of a domain object, <renew> to extend the validity period of a domain
       object, <transfer> to manage domain object sponsorship changes, and
       <update> to change information associated with a domain object.

    4.2.1.  EPP <create> Command

       This extension defines additional elements for the EPP <create>
       command described in the EPP domain mapping [RFC5731], host mapping
       [RFC5732] and contact mapping [RFC5733].  No additional elements are
       defined for the EPP <create> response.

       The EPP <create> command provides a transform operation that allows a
       client to create a domain object.  In addition to the EPP command
       elements described in the EPP domain mapping [RFC5731], host mapping
       [RFC5732] and contact mapping [RFC5733], the command MUST contain an
       <extension> element, and the <extension> element MUST contain a child
       <resellerext:create> element that identifies the extension namespace
       if the client wants to associate data defined in this extension to
       the domain object.  The <resellerext:create> element contains the
       following child elements:

       o  A <resellerext:id> element that contains the identifier of the
          reseller of a sponsoring registrar.

       Example <create> Command:

    Zhou, et al.             Expires April 14, 2016                 [Page 7]

    Internet-Draft       Reseller Extension for the EPP         October 2015

    C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
    C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
    C:  <command>
    C:    <create>
    C:      <domain:create xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
    C:        <domain:name>example.com</domain:name>
    C:        <domain:period unit="y">3</domain:period>
    C:        <domain:ns>
    C:          <domain:hostObj>ns1.example.com</domain:hostObj>
    C:        </domain:ns>
    C:        <domain:registrant>jd1234</domain:registrant>
    C:        <domain:contact type="tech">sh8013</domain:contact>
    C:        <domain:contact type="billing">sh8013</domain:contact>
    C:        <domain:contact type="admin">sh8013</domain:contact>
    C:        <domain:authInfo>
    C:           <domain:pw roid="ddddd-dddd">fooBAR</domain:pw>
    C:        </domain:authInfo>
    C:      </domain:create>
    C:    </create>
    C:    <extension>
    C:      <resellerext:create xmlns:resellerext="urn:ietf:params:xml:ns:resellerext-1.0">
    C:        <resellerext:id>myreseller</resellerext:id>
    C:      </resellerext:create>
    C:    </extension>
    C:    <clTRID>ABC-12345</clTRID>
    C:  </command>
    C:</epp>

       When a <create> command has been processed successfully, the EPP
       response is as described in the EPP domain mapping [RFC5731], host
       mapping [RFC5732] and contact mapping [RFC5733].

       An EPP error response MUST be returned if a <create> command cannot
       be processed for any reason.

    4.2.2.  EPP <delete> Command

       This extension does not add any elements to the EPP <delete> command
       or <delete> response described in the EPP domain mapping [RFC5731],
       host mapping [RFC5732] and contact mapping [RFC5733].

    4.2.3.  EPP <renew> Command

       This extension does not add any elements to the EPP <renew> command
       or <renew> response described in the EPP domain mapping [RFC5731],
       host mapping [RFC5732] and contact mapping [RFC5733].

    Zhou, et al.             Expires April 14, 2016                 [Page 8]

    Internet-Draft       Reseller Extension for the EPP         October 2015

    4.2.4.  EPP <transfer> Command

       This extension does not add any elements to the EPP <transfer>
       command or <transfer> response described in the EPP domain mapping
       [RFC5731], host mapping [RFC5732] and contact mapping [RFC5733], but
       after a successful transfer of an object with an assigned reseller,
       the server SHOULD clear the assigned reseller value.

    4.2.5.  EPP <update> Command

       This extension defines additional elements for the EPP <update>
       command described in the EPP domain mapping [RFC5731], host mapping
       [RFC5732] and contact mapping [RFC5733].  No additional elements are
       defined for the EPP <update> response.

       The EPP <update> command provides a transform operation that allows a
       client to modify the attributes of a domain object.  In addition to
       the EPP command elements described in the EPP domain mapping, the
       command MUST contain an <extension> element, and the <extension>
       element MUST contain a child <resellerext:update> element that
       identifies the extension namespace if the client wants to update the
       domain object with data defined in this extension.  The
       <resellerext:update> element contains the following child elements:

       o  An OPTIONAL <resellerext:add> element that contains attribute
          values to be added to the object.

       o  An OPTIONAL <resellerext:rem> element that contains attribute
          values to be removed from the object.

       o  An OPTIONAL <resellerext:chg> element that contains attribute
          values to be changed.

       At least one and only one <resellerext:add>, <resellerext:rem> or
       <resellerext:rem> element MUST be provided.  The <resellerext:add>,
       <resellerext:rem> and <resellerext:rem> elements contain the
       following child element:

       o  A <resellerext:id> element that contains the identifier of the
          reseller of a sponsoring registrar.

       Example <update> command, adding a reseller:

    Zhou, et al.             Expires April 14, 2016                 [Page 9]

    Internet-Draft       Reseller Extension for the EPP         October 2015

    C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
    C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
    C:  <command>
    C:    <update>
    C:      <domain:update xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
    C:        <domain:name>example.com</domain:name>
    C:      </domain:update>
    C:    </update>
    C:    <extension>
    C:      <resellerext:update xmlns:resellerext="urn:ietf:params:xml:ns:resellerext-1.0">
    C:        <resellerext:add>
    C:          <resellerext:id>myreseller</resellerext:id>
    C:        </resellerext:add>
    C:      </resellerext:update>
    C:    </extension>
    C:    <clTRID>ABC-12345</clTRID>
    C:  </command>
    C:</epp>

       Example <update> command, removing a reseller:

    C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
    C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
    C:  <command>
    C:    <update>
    C:      <domain:update xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
    C:        <domain:name>example.com</domain:name>
    C:      </domain:update>
    C:    </update>
    C:    <extension>
    C:      <resellerext:update xmlns:resellerext="urn:ietf:params:xml:ns:resellerext-1.0">
    C:        <resellerext:rem>
    C:          <resellerext:id>myreseller</resellerext:id>
    C:        </resellerext:rem>
    C:      </resellerext:update>
    C:    </extension>
    C:    <clTRID>ABC-12345</clTRID>
    C:  </command>
    C:</epp>

       Example <update> command, updating reseller identifier:

    Zhou, et al.             Expires April 14, 2016                [Page 10]

    Internet-Draft       Reseller Extension for the EPP         October 2015

    C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
    C:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
    C:  <command>
    C:    <update>
    C:      <domain:update xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
    C:        <domain:name>example.com</domain:name>
    C:      </domain:update>
    C:    </update>
    C:    <extension>
    C:      <resellerext:update xmlns:resellerext="urn:ietf:params:xml:ns:resellerext-1.0">
    C:        <resellerext:chg>
    C:          <resellerext:id>myreseller</resellerext:id>
    C:        </resellerext:chg>
    C:      </resellerext:update>
    C:    </extension>
    C:    <clTRID>ABC-12345</clTRID>
    C:  </command>
    C:</epp>

       When an extended <update> command has been processed successfully,
       the EPP response is as described in the EPP domain name mapping
       [RFC5731], host mapping [RFC5732] and contact mapping [RFC5733].

    5.  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.  The BEGIN and END tags are not part of the schema; they
       are used to note the beginning and ending of the schema for URI
       registration purposes.

    BEGIN
    <?xml version="1.0" encoding="UTF-8"?>

    <schema targetNamespace="urn:ietf:params:xml:ns:resellerext-1.0"
            xmlns:resellerr="urn:ietf:params:xml:ns:resellerext-1.0"
            xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
            xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
            xmlns="http://www.w3.org/2001/XMLSchema"
            elementFormDefault="qualified">

    <!--
    Import common element types.
    -->

    Zhou, et al.             Expires April 14, 2016                [Page 11]

    Internet-Draft       Reseller Extension for the EPP         October 2015

      <import namespace="urn:ietf:params:xml:ns:eppcom-1.0"
              schemaLocation="eppcom-1.0.xsd"/>
      <import namespace="urn:ietf:params:xml:ns:epp-1.0"
              schemaLocation="epp-1.0.xsd"/>

      <annotation>
        <documentation>
          Extensible Provisioning Protocol v1.0
          Domain Reseller Extension Schema v1.0
        </documentation>
      </annotation>

    <!-- Child elements found in EPP commands. -->
      <element name="create" type="resellerext:createType"/>
      <element name="update" type="resellerext:updateType"/>

    <!-- reseller name type-->
      <simpleType name="resNameType">
         <restriction base="normalizedString">
           <minLength value="1"/>
           <maxLength value="255"/>
         </restriction>
      </simpleType>

    <!-- Child elements of the <resellerext:create> command
    All elements must be present at time of creation
    -->
      <complexType name="createType">
        <sequence>
          <!-- agent identifier that sells the domain, e.g. registrar, reseller -->
          <element name="id" type="eppcom:clIDType"/>
        </sequence>
      </complexType>

    <!--
    Child elements of <resellerext:update> command
    -->

      <complexType name="updateType">
        <sequence>
          <element name="add" type="resellerext:addRemChgType" minOccurs="0"/>
          <element name="rem" type="resellerext:addRemChgType" minOccurs="0"/>
          <element name="chg" type="resellerext:addRemChgType" minOccurs="0"/>
        </sequence>
      </complexType>

      <complexType name="addRemChgType">
        <sequence>

    Zhou, et al.             Expires April 14, 2016                [Page 12]

    Internet-Draft       Reseller Extension for the EPP         October 2015

          <!-- agent identifier that sells the domain, e.g. registrar, reseller -->
          <element name="id" type="eppcom:clIDType" minOccurs="0"/>
        </sequence>
      </complexType>

    <!-- Child response element -->

      <element name="infData" type="resellerext:infDataType"/>

    <!-- <resellerext:infData> response elements -->

      <complexType name="infDataType">
        <sequence>
          <!-- agent identifier that sells the domain, e.g. registrar, reseller -->
          <element name="id" type="eppcom:clIDType" minOccurs="0"/>
          <!-- agent name that sells the domain, e.g. registrar, reseller -->
          <element name="name" type="resellerext:resNameType" minOccurs="0"/>
        </sequence>
      </complexType>

    <!-- End of schema. -->
    </schema>
    END

    6.  Internationalization Considerations

       EPP is represented in XML, which provides native support for encoding
       information using the Unicode character set and its more compact
       representations including UTF-8.  Conformant XML processors recognize
       both UTF-8 and UTF-16.  Though XML includes provisions to identify
       and use other character encodings through use of an "encoding"
       attribute in an <?xml?> declaration, use of UTF-8 is RECOMMENDED.

       As an extension of the EPP domain name mapping, the elements, element
       content described in this document MUST inherit the
       internationalization conventions used to represent higher-layer
       domain and core protocol structures present in an XML instance that
       includes this extension.

    7.  IANA Considerations

    7.1.  XML Namespace

       This document uses URNs to describe XML namespaces and XML schemas
       conforming to a registry mechanism described in [RFC3688].  IANA is
       requested to assignment the following URI.

    Zhou, et al.             Expires April 14, 2016                [Page 13]

    Internet-Draft       Reseller Extension for the EPP         October 2015

       Registration request for the reseller namespace:

       o  URI: urn:ietf:params:xml:ns:reseller-1.0

       o  Registrant Contact: See the "Author's Address" section of this
          document.

       o  XML: See the "Formal Syntax" section of this document.

    7.2.  EPP Extension Registry

       The EPP extension described in this document should be registered by
       the IANA in the EPP Extension Registry described in [RFC7451].  The
       details of the registration are as follows:

       Name of Extension: Domain Reseller Extension

       Document status: Standards Track

       Reference: (insert reference to RFC version of this document)

       Registrant Name and Email Address: See the "Author's Address" section
       of this document.

       TLDs: any

       IPR Disclosure: none

       Status: active

       Notes: none

    8.  Security Considerations

       The object mapping extension described in this document does not
       provide any other security services or introduce any additional
       considerations beyond those described by [RFC5730], [RFC5731],
       [RFC5732] and [RFC5733] or those caused by the protocol layers used
       by EPP.

    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,
                  <http://www.rfc-editor.org/info/rfc2119>.

    Zhou, et al.             Expires April 14, 2016                [Page 14]

    Internet-Draft       Reseller Extension for the EPP         October 2015

       [RFC3688]  Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
                  DOI 10.17487/RFC3688, January 2004,
                  <http://www.rfc-editor.org/info/rfc3688>.

       [RFC5730]  Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
                  STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009,
                  <http://www.rfc-editor.org/info/rfc5730>.

       [RFC5731]  Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
                  Domain Name Mapping", STD 69, RFC 5731,
                  DOI 10.17487/RFC5731, August 2009,
                  <http://www.rfc-editor.org/info/rfc5731>.

       [RFC5732]  Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
                  Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732,
                  August 2009, <http://www.rfc-editor.org/info/rfc5732>.

       [RFC5733]  Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
                  Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733,
                  August 2009, <http://www.rfc-editor.org/info/rfc5733>.

       [RFC7451]  Hollenbeck, S., "Extension Registry for the Extensible
                  Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451,
                  February 2015, <http://www.rfc-editor.org/info/rfc7451>.

       [W3C.REC-xml-20040204]
                  Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and
                  F. Yergeau, ""Extensible Markup Language (XML) 1.0 (Third
                  Edition)", World Wide Web Consortium FirstEdition REC-xml-
                  20040204", February 2004,
                  <http://www.w3.org/TR/2004/REC-xml-20040204>.

       [W3C.REC-xmlschema-1-20041028]
                  Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn,
                  ""XML Schema Part 1: Structures Second Edition", World
                  Wide Web Consortium Recommendation REC-xmlschema-
                  1-20041028", October 2004,
                  <http://www.w3.org/TR/2004/REC-xmlschema-1-20041028>.

       [W3C.REC-xmlschema-2-20041028]
                  Biron, P. and A. Malhotra, ""XML Schema Part 2: Datatypes
                  Second Edition", World Wide Web Consortium Recommendation
                  REC-xmlschema-2-20041028", October 2004,
                  <http://www.w3.org/TR/2004/REC-xmlschema-2-20041028>.

    Zhou, et al.             Expires April 14, 2016                [Page 15]

    Internet-Draft       Reseller Extension for the EPP         October 2015

    9.2.  Informative References

       [ID.draft-zhou-eppext-reseller-mapping]
                  Zhou, L., Kong, N., Qi, C., Lee, X., and J. Gould,
                  "Extensible Provisioning Protocol (EPP) Reseller Mapping",
                  Oct 2015, <http://tools.ietf.org/html/
                  draft-zhou-eppext-reseller-mapping>.

    Appendix A.  Change Log

       Initial -00:  Individual document submitted.

       -01:

          *  Updated abstract and introduction.

          *  Revised typos in info response.

          *  Added explanations on how to process reseller extension after
             successful transfer operation.

          *  Modified <update> explanation.

          *  Deleted reseller name element in <create> and <update>
             commands.

          *  Removed some inaccurate comments from xml schema.

          *  Modified the element name of reseller id and reseller name.

       -02:

          *  Changed author information.

          *  Updated xml typos <reseller:infData> to <resellerext:infData>
             in <info> response.

    Authors' Addresses

       Linlin Zhou
       CNNIC
       4 South 4th Street, Zhongguancun, Haidian District
       Beijing, Beijing  100190
       China

       Phone: +86 10 5881 2677
       Email: zhoulinlin@cnnic.cn

    Zhou, et al.             Expires April 14, 2016                [Page 16]

    Internet-Draft       Reseller Extension for the EPP         October 2015

       Ning Kong
       CNNIC
       4 South 4th Street, Zhongguancun, Haidian District
       Beijing, Beijing  100190
       China

       Phone: +86 10 5881 3147
       Email: nkong@cnnic.cn

       Chao Qi
       Teleinfo

       Email: qichao911@163.com

       Xiaodong Lee
       CNNIC
       4 South 4th Street, Zhongguancun, Haidian District
       Beijing, Beijing  100190
       China

       Phone: +86 10 5881 3020
       Email: xl@cnnic.cn

       James Gould
       VeriSign, Inc.
       12061 Bluemont Way
       Reston, VA  20190
       US

       Email: jgould@verisign.com

    Zhou, et al.             Expires April 14, 2016                [Page 17]

Html markup produced by rfcmarkup 1.115, available from https://tools.ietf.org/tools/rfcmarkup/