Internet Engineering Task Force                            S. Hollenbeck
Internet-Draft                                            VeriSign, Inc.
August 17, 2001                               Expires: February 17, 2002

         Extensible Provisioning Protocol E.164 Number Mapping
                   <draft-hollenbeck-epp-e164-00.txt>

Status of this Memo

  This document is an Internet-Draft and is in full conformance with all
  provisions of Section 10 of RFC2026.

  Internet-Drafts are working documents of the Internet Engineering Task
  Force (IETF), its areas, and its working groups.  Note that other
  groups may also distribute working documents as Internet-Drafts.

  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".

  The list of current Internet-Drafts can be accessed at
  http://www.ietf.org/ietf/1id-abstracts.txt

  The list of Internet-Draft Shadow Directories can be accessed at
  http://www.ietf.org/shadow.html.

Abstract

  This document describes an Extensible Provisioning Protocol (EPP)
  mapping for the provisioning and management of E.164 numbers stored in
  a shared central repository.  Specified in XML, the mapping defines
  EPP command syntax and semantics as applied to E.164 numbers.

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 in
  examples is provided only to illustrate element relationships and is
  not a REQUIRED feature of this protocol.







Hollenbeck             Expires February 17, 2002                [Page 1]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


Table of Contents

  1. Introduction .................................................    3
  2. Object Attributes ............................................    4
  2.1 E.164 Domain Names ..........................................    4
  2.2 NAPTR Fields ................................................    4
  2.3 Contact and Client Identifiers ..............................    5
  2.4 Status Values ...............................................    5
  2.5 Dates and Times .............................................    6
  2.6 Validity Periods ............................................    7
  2.7 Authorization Information ...................................    7
  3. EPP Command Mapping ..........................................    8
  3.1 EPP Query Commands ..........................................    8
  3.1.1 EPP <check> Command .......................................    8
  3.1.2 EPP <info> Command ........................................    9
  3.1.3 EPP <transfer> Command ....................................   13
  3.2 EPP Transform Commands ......................................   15
  3.2.1 EPP <create> Command ......................................   15
  3.2.2 EPP <delete> Command ......................................   18
  3.2.3 EPP <renew> Command .......................................   19
  3.2.4 EPP <transfer> Command ....................................   21
  3.2.5 EPP <update> Command ......................................   23
  4. Formal Syntax ................................................   27
  5. Internationalization Considerations ..........................   35
  6. IANA Considerations ..........................................   35
  7. Security Considerations ......................................   35
  8. Acknowledgements .............................................   36
  9. References ...................................................   36
  10. Author's Address ............................................   37
  A. Revisions From Previous Version ..............................   38
  B. Full Copyright Statement .....................................   39




















Hollenbeck             Expires February 17, 2002                [Page 2]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


1. Introduction

  This document describes an E.164 number mapping for version 1.0 of the
  Extensible Provisioning Protocol (EPP).  This mapping is specified
  using the Extensible Markup Language (XML) 1.0 as described in [XML]
  and XML Schema notation as described in [XMLS-1] and [XMLS-2].

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

  [RFC2916] describes how the Domain Name System (DNS) can be used to
  identify services associated with an E.164 number.  The EPP mapping
  described in this document specifies a mechanism for the provisioning
  and management of E.164 numbers stored in a shared central repository.
  Information exchanged via this mapping can be extracted from the
  repository and used to publish DNS resource records as described in
  [RFC2916].  Examples used in this document were chosen specifically to
  illustrate provisioning concepts for the example resource records
  described in [RFC2916].

  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.


























Hollenbeck             Expires February 17, 2002                [Page 3]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


2. Object Attributes

  An EPP E.164 object has attributes and associated values that may be
  viewed and modified by the sponsoring client or the server.  This
  section describes each attribute type in detail.

2.1 E.164 Domain Names

  An E.164 domain name is a representation of an E.164 number that has
  been translated to conform to domain name syntax as described in
  [RFC2916].  The labels used to describe the name space of an E.164
  domain name are a policy matter that is beyond the scope of this
  document.

2.2 NAPTR Fields

  According to [RFC2916], Naming Authority Pointer (NAPTR) resource
  records are used to identify available ways of contacting a specific
  node identified by a domain name created from the translation of an
  E.164 number.  The format and processing rules for NAPTR records is
  described in [RFC2915].

2.2.1 Order

  The NAPTR order field is represented in this mapping using a 16-bit
  unsigned integer.

2.2.2 Preference

  The NAPTR preference field is represented in this mapping using a 16-
  bit unsigned integer.

2.2.3 Flags

  The NAPTR flags field is represented in this mapping using a single
  character from the set [uU].  NAPTR defines additional flags, but only
  the "u" flag is currently used in the context of E.164 numbers.  The
  case of the flag character is not significant.

2.2.4 Service

  The NAPTR service field is represented in this mapping using a
  character string with a minimum length of zero characters and a
  maximum length of 65 characters.

2.2.5 Regular Expression

  The NAPTR regexp field is represented in this mapping using a



Hollenbeck             Expires February 17, 2002                [Page 4]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


  character string with a minimum length of 0 characters and an
  unspecified maximum length.  This field can contain numerous
  backslashes and should thus be treated with care.

2.2.6 Replacement

  The NAPTR replacement field is not currently used in the context of
  E.164 numbers.

2.3 Contact and Client Identifiers

  All EPP contacts are identified by a server-unique identifier.
  Contact identifiers are character strings with a specified minimum
  length, a specified maximum length, and a specified format.  Contact
  identifiers use the "clIDType" client identifier syntax described in
  [EPP].

2.4 Status Values

  An E.164 object MUST always have at least one associated status value.
  Status values MAY be set only by the client that sponsors an E.164
  object and by the server on which the object resides.  A client MAY
  change the status of an E.164 object using the EPP <update> command.
  Each status value MAY be accompanied by a string of human-readable
  text that describes the rationale for the status applied to the
  object.

  A client MUST NOT alter status values set by the server.  A server MAY
  alter or override status values set by a client subject to local
  server policies.

  Status values that may be added or removed by a client are prefixed
  with "client".  Corresponding status values that may be added or
  removed by a server are prefixed with "server".  Status values that do
  not begin with either "client" or "server" are server-managed.

  Status Value Descriptions:

  clientDeleteProhibited, serverDeleteProhibited

  Requests to delete the object MUST be rejected.

  clientHold, serverHold

  Delegation information MUST be withheld from publication in the
  object's nominal zone.

  clientRenewProhibited, serverRenewProhibited



Hollenbeck             Expires February 17, 2002                [Page 5]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


  Requests to renew the object MUST be rejected.

  clientTransferProhibited, serverTransferProhibited

  Requests to transfer the object MUST be rejected.

  clientUpdateProhibited, serverUpdateProhibited

  Requests to update the object (other than to remove this status) MUST
  be rejected.

  inactive

  Delegation information has not been associated with the object.

  ok

  This is the nominal status value for an object that has no pending
  operations or prohibitions.

  pendingDelete

  A delete request has been received for the object, but the object has
  not yet been purged from the server database.

  pendingTransfer

  A transfer request has been received for the object, and completion of
  the request is pending.  Transform commands other than <transfer> MUST
  be rejected while an object is in this state.

  pendingVerification

  A create request has been received for the object, and completion of
  the request is pending.

  "ok" status MUST NOT be combined with any other status.
  "pendingDelete" status MUST NOT be combined with either
  "clientDeleteProhibited" or "serverDeleteProhibited" status.
  "pendingTransfer" status MUST NOT be combined with either
  "clientTransferProhibited" or "serverTransferProhibited" status.  All
  other status value combinations are valid.

2.5 Dates and Times

  Date and time attribute values MUST be represented in Universal
  Coordinated Time (UTC) using the Gregorian calendar. Both extended and
  truncated date and time forms defined in [ISO8601] MAY be used, though



Hollenbeck             Expires February 17, 2002                [Page 6]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


  a server SHOULD use one form or the other consistently.

2.6 Validity Periods

  An E.164 object MAY have a specified validity period.  If server
  policy supports E.164 object validity periods, the validity period is
  defined when an E.164 object is created, and it MAY be extended by the
  EPP <renew> or <transfer> commands.  As a matter of server policy,
  this specification does not define actions to be taken upon expiration
  of an E.164 object's validity period.

  Validity periods are measured in years or months with the appropriate
  units specified using the "unit" attribute.  Valid values for the
  "unit" attribute are "y" for years and "m" for months.  The minimum
  allowable period value is one decimal (1).  The maximum allowable
  value is ninety-nine decimal (99).  A server MAY support a lower
  maximum value.

2.7 Authorization Information

  Authorization information is associated with E.164 objects to
  facilitate transfer operations.  Authorization information is assigned
  when an E.164 object is created, and it MAY be updated in the future.
  This specification describes password-based authorization information,
  though other mechanisms are possible.


























Hollenbeck             Expires February 17, 2002                [Page 7]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


3. EPP Command Mapping

  A detailed description of the EPP syntax and semantics can be found in
  [EPP].  The command mappings described here are specifically for use
  in provisioning and managing E.164 numbers via EPP.

3.1 EPP Query Commands

  EPP provides three commands to retrieve E.164 object information:
  <check> to determine if an E.164 object is known to the server, <info>
  to retrieve detailed information associated with an E.164 object, and
  <transfer> to retrieve E.164 object transfer status information.

3.1.1 EPP <check> Command

  The EPP <check> command is used to determine if an E.164 object is
  known to the server.  In addition to the standard EPP command
  elements, the <check> command MUST contain a <e164:check> element that
  identifies the e164 namespace and the location of the e164 schema.
  The <e164:check> element contains the following child elements:

  - One or more <e164:name> elements that contain the fully qualified
  names of the objects to be queried.

  Example <check> command:

  C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
  C:<epp xmlns="urn:iana:xml:ns:epp-1.0"
  C:     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  C:     xsi:schemaLocation="urn:iana:xml:ns:epp-1.0 epp-1.0.xsd">
  C:  <command>
  C:    <check>
  C:      <e164:check xmlns:e164="urn:iana:xml:ns:e164-1.0"
  C:       xsi:schemaLocation="urn:iana:xml:ns:e164-1.0 e164-1.0.xsd">
  C:        <e164:dn>4.3.2.1.6.7.9.8.6.4.e164.arpa</e164:dn>
  C:      </e164:check>
  C:    </check>
  C:    <unspec/>
  C:    <clTRID>ABC-12346</clTRID>
  C:  </command>
  C:</epp>

  When a <check> command has been processed successfully, the EPP
  <resData> element MUST contain a child <e164:chkData> element that
  identifies the e164 namespace and the location of the e164 schema.
  The <e164:chkData> element contains the following child elements:

  - One or more <e164:cd> elements that contain the fully qualified



Hollenbeck             Expires February 17, 2002                [Page 8]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


  names for the queried objects and an "x" attribute whose value
  identifies the object as either "+" for a known object or "-" for an
  unknown object.

  Example <check> response:

  S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
  S:<epp xmlns="urn:iana:xml:ns:epp-1.0"
  S:     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  S:     xsi:schemaLocation="urn:iana:xml:ns:epp-1.0 epp-1.0.xsd">
  S:  <response>
  S:    <result code="1000">
  S:      <msg>Command completed successfully</msg>
  S:    </result>
  S:    <resData>
  S:      <e164:chkData xmlns:e164="urn:iana:xml:ns:e164-1.0"
  S:       xsi:schemaLocation="urn:iana:xml:ns:e164-1.0 e164-1.0.xsd">
  S:        <e164:cd x="+">4.3.2.1.6.7.9.8.6.4.e164.arpa</e164:cd>
  S:      </e164:chkData>
  S:    </resData>
  S:    <unspec/>
  S:    <trID>
  S:      <clTRID>ABC-12346</clTRID>
  S:      <svTRID>54322-XYZ</svTRID>
  S:    </trID>
  S:  </response>
  S:</epp>

  An EPP error response MUST be returned if a <check> command can not be
  processed for any reason.

3.1.2 EPP <info> Command

  The EPP <info> command is used to retrieve information associated with
  an E.164 object.  In addition to the standard EPP command elements,
  the <info> command MUST contain a <e164:info> element that identifies
  the e164 namespace and the location of the e164 schema.  The
  <e164:info> element contains the following child elements:

  - An <e164:name> element that contains the fully qualified name of the
  object to be queried.










Hollenbeck             Expires February 17, 2002                [Page 9]

Internet-Draft             EPP E.164 Mapping             August 17, 2001



  Example <info> command:

  C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
  C:<epp xmlns="urn:iana:xml:ns:epp-1.0"
  C:     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  C:     xsi:schemaLocation="urn:iana:xml:ns:epp-1.0 epp-1.0.xsd">
  C:  <command>
  C:    <info>
  C:      <e164:info xmlns:e164="urn:iana:xml:ns:e164-1.0"
  C:       xsi:schemaLocation="urn:iana:xml:ns:e164-1.0 e164-1.0.xsd">
  C:        <e164:dn>4.3.2.1.6.7.9.8.6.4.e164.arpa</e164:dn>
  C:      </e164:info>
  C:    </info>
  C:    <unspec/>
  C:    <clTRID>ABC-12346</clTRID>
  C:  </command>
  C:</epp>

  When an <info> command has been processed successfully, the EPP
  <resData> element MUST contain a child <e164:infData> element that
  identifies the e164 namespace and the location of the e164 schema.
  The <e164:infData> element contains the following child elements:

  - An <e164:dn> element that contains the fully qualified name of the
  object.

  - An <e164:roid> element that contains the Repository Object
  IDentifier assigned to the object when the object was created.

  - One or more <e164:naptr> elements.  Each <e164:naptr> element
  contains the following child elements:

    - An <e164:order> element that contains a NAPTR order value.

    - An <e164:pref> element that contains a NAPTR preference value.

    - An <e164:flags> element that contains a NAPTR flags value.

    - An <e164:svc> element that contains a NAPTR service value.

    - An <e164:regex> element that contains a NAPTR regular expression
    value.

  - One or more <e164:status> elements that contain the current status
  descriptors associated with the object.

  - If supported by the server, one <e164:registrant> element and one or



Hollenbeck             Expires February 17, 2002               [Page 10]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


  more <e164:contact> elements that contain identifiers for the human or
  organizational social information objects associated with the E.164
  object.

  - A <e164:clID> element that contains the identifier of the sponsoring
  client.

  - A <e164:crID> element that contains the identifier of the client
  that created the object.

  - A <e164:crDate> element that contains the date and time of object
  creation.

  - A <e164:exDate> element that contains the date and time identifying
  the end of the object's registration period.

  - A <e164:upID> element that contains the identifier of the client
  that last updated the object.  This element MUST NOT be present if the
  object has never been modified.

  - A <e164:upDate> element that contains the date and time of the most
  recent object modification.  This element MUST NOT be present if the
  object has never been modified.

  - A <e164:trDate> elements that contains the date and time of the most
  recent successful object transfer.  This element MUST NOT be provided
  if the object has never been transferred.

  - A <e164:authInfo> element that contains authorization information
  associated with the object.  This element MUST NOT be provided if the
  querying client is not the current sponsoring client.




















Hollenbeck             Expires February 17, 2002               [Page 11]

Internet-Draft             EPP E.164 Mapping             August 17, 2001



  Example <info> response:

  S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
  S:<epp xmlns="urn:iana:xml:ns:epp-1.0"
  S:     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  S:     xsi:schemaLocation="urn:iana:xml:ns:epp-1.0 epp-1.0.xsd">
  S:  <response>
  S:    <result code="1000">
  S:      <msg>Command completed successfully</msg>
  S:    </result>
  S:    <resData>
  S:      <e164:infData xmlns:e164="urn:iana:xml:ns:e164-1.0"
  S:       xsi:schemaLocation="urn:iana:xml:ns:e164-1.0
  S:       e164-1.0.xsd">
  S:        <e164:dn>4.3.2.1.6.7.9.8.6.4.e164.arpa</e164:dn>
  S:        <e164:roid>EXAMPLE1-FOO</e164:roid>
  S:        <e164:naptr>
  S:          <e164:order>100</e164:order>
  S:          <e164:pref>10</e164:pref>
  S:          <e164:flags>u</e164:flags>
  S:          <e164:svc>sip+E2U</e164:svc>
  S:          <e164:regex>!^.*$!sip:info@tele2.se!</e164:regex>
  S:        </e164:naptr>
  S:        <e164:naptr>
  S:          <e164:order>102</e164:order>
  S:          <e164:pref>10</e164:pref>
  S:          <e164:flags>u</e164:flags>
  S:          <e164:svc>mailto+E2U</e164:svc>
  S:          <e164:regex>!^.*$!mailto:info@tele2.se!</e164:regex>
  S:        </e164:naptr>
  S:        <e164:status s="ok"/>
  S:        <e164:registrant>jd1234</e164:registrant>
  S:        <e164:contact type="admin">sh8013</e164:contact>
  S:        <e164:contact type="tech">sh8013</e164:contact>
  S:        <e164:clID>ClientX</e164:clID>
  S:        <e164:crID>ClientY</e164:crID>
  S:        <e164:crDate>1999-04-03T22:00:00.0Z</e164:crDate>
  S:        <e164:upID>ClientX</e164:upID>
  S:        <e164:upDate>1999-12-03T09:00:00.0Z</e164:upDate>
  S:        <e164:exDate>2005-04-03T22:00:00.0Z</e164:exDate>
  S:        <e164:trDate>2000-04-08T09:00:00.0Z</e164:trDate>
  S:        <e164:authInfo type="pw">2fooBAR</e164:authInfo>
  S:      </e164:infData>
  S:    </resData>
  S:    <unspec/>
  S:    <trID>
  S:      <clTRID>ABC-12346</clTRID>



Hollenbeck             Expires February 17, 2002               [Page 12]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


  S:      <svTRID>54322-XYZ</svTRID>
  S:    </trID>
  S:  </response>
  S:</epp>

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

3.1.3 EPP <transfer> Command

  The EPP <transfer> command provides a query operation that allows a
  client to determine real-time status of pending and completed transfer
  requests.  In addition to the standard EPP command elements, the
  <transfer> command MUST contain an "op" attribute with value "query",
  and a <e164:transfer> element that identifies the e164 namespace and
  the location of the e164 schema.  The <e164:transfer> element contains
  the following child elements:

  - A <e164:dn> element that contains the fully qualified name of the
  object to be queried.

  Example <transfer> query command:

  C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
  C:<epp xmlns="urn:iana:xml:ns:epp-1.0"
  C:     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  C:     xsi:schemaLocation="urn:iana:xml:ns:epp-1.0 epp-1.0.xsd">
  C:  <command>
  C:    <transfer op="query">
  C:      <e164:transfer xmlns:e164="urn:iana:xml:ns:e164-1.0"
  C:       xsi:schemaLocation="urn:iana:xml:ns:e164-1.0
  C:       e164-1.0.xsd">
  C:        <e164:dn>4.3.2.1.6.7.9.8.6.4.e164.arpa</e164:dn>
  C:      </e164:transfer>
  C:    </transfer>
  C:    <unspec/>
  C:    <clTRID>ABC-12346</clTRID>
  C:  </command>
  C:</epp>

  When a <transfer> query command has been processed successfully, the
  EPP <resData> element MUST contain a child <e164:trnData> element that
  identifies the e164 namespace and the location of the e164 schema. The
  <e164:trnData> element contains the following child elements:

  - A <e164:dn> element that contains the fully qualified name of the
  object.




Hollenbeck             Expires February 17, 2002               [Page 13]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


  - A <e164:trStatus> element that contains the state of the most recent
  transfer request.

  - A <e164:reID> element that contains the identifier of the client
  that requested the object transfer.

  - A <e164:reDate> element that contains the date and time that the
  transfer was requested.

  - A <e164:acID> element that contains the identifier of the client
  that SHOULD act upon the transfer request.

  - A <e164:acDate> element that contains the date and time of a
  required or completed response.  For a PENDING request, the value
  identifies the date and time by which a response is required before an
  automated response action MUST be taken by the server.  For all other
  status types, the value identifies the date and time when the request
  was completed.

  - An OPTIONAL <e164:exDate> element that contains the end of the
  object's validity period if the <transfer> command caused or causes a
  change in the validity period.





























Hollenbeck             Expires February 17, 2002               [Page 14]

Internet-Draft             EPP E.164 Mapping             August 17, 2001



  Example <transfer> query response:

  S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
  S:<epp xmlns="urn:iana:xml:ns:epp-1.0"
  S:     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  S:     xsi:schemaLocation="urn:iana:xml:ns:epp-1.0 epp-1.0.xsd">
  S:  <response>
  S:    <result code="1000">
  S:      <msg>Command completed successfully</msg>
  S:    </result>
  S:    <resData>
  S:      <e164:trnData xmlns:e164="urn:iana:xml:ns:e164-1.0"
  S:       xsi:schemaLocation="urn:iana:xml:ns:e164-1.0
  S:       e164-1.0.xsd">
  S:        <e164:dn>4.3.2.1.6.7.9.8.6.4.e164.arpa</e164:dn>
  S:        <e164:trStatus>pending</e164:trStatus>
  S:        <e164:reID>ClientX</e164:reID>
  S:        <e164:reDate>2000-06-06T22:00:00.0Z</e164:reDate>
  S:        <e164:acID>ClientY</e164:acID>
  S:        <e164:acDate>2000-06-11T22:00:00.0Z</e164:acDate>
  S:        <e164:exDate>2002-09-08T22:00:00.0Z</e164:exDate>
  S:      </e164:trnData>
  S:    </resData>
  S:    <unspec/>
  S:    <trID>
  S:      <clTRID>ABC-12346</clTRID>
  S:      <svTRID>54322-XYZ</svTRID>
  S:    </trID>
  S:  </response>
  S:</epp>

  An EPP error response MUST be returned if a <transfer> query command
  can not be processed for any reason.

3.2 EPP Transform Commands

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

3.2.1 EPP <create> Command

  The EPP <create> command provides a transform operation that allows a
  client to create an E.164 object.  In addition to the standard EPP
  command elements, the <create> command MUST contain an <e164:create>



Hollenbeck             Expires February 17, 2002               [Page 15]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


  element that identifies the e164 namespace and the location of the
  e164 schema.  The <e164:create> element contains the following child
  elements:

  - An <e164:dn> element that contains the fully qualified name of the
  object to be created.

  - An OPTIONAL <e164:period> element that contains the initial
  registration period of the object.  A server MAY define a default
  initial registration period if not specified by the client.

  - One or more <e164:naptr> elements.  Structure of the <164:naptr>
  element is described as part of the information returned from the
  <info> command.

  - An OPTIONAL <e164:registrant> element that contains the identifier
  for the human or organizational social information (contact) object to
  be associated with the object as the object registrant.  This object
  identifier MUST be known to the server before the contact object can
  be associated with the E.164 object.  The EPP mapping for contact
  objects is described in [EPP-C].

  - Zero or more OPTIONAL <e164:contact> elements that contain the
  identifiers for other contact objects to be associated with the E.164
  object.  Contact object identifiers MUST be known to the server before
  the contact object can be associated with the E.164 object.

  - An <e164:authInfo> element that contains authorization information
  to be associated with the E.164 object.






















Hollenbeck             Expires February 17, 2002               [Page 16]

Internet-Draft             EPP E.164 Mapping             August 17, 2001



  Example <create> command:

  C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
  C:<epp xmlns="urn:iana:xml:ns:epp-1.0"
  C:     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  C:     xsi:schemaLocation="urn:iana:xml:ns:epp-1.0 epp-1.0.xsd">
  C:  <command>
  C:    <create>
  C:      <e164:create
  C:       xmlns:e164="urn:iana:xml:ns:e164-1.0"
  C:       xsi:schemaLocation="urn:iana:xml:ns:e164-1.0 e164-1.0.xsd">
  C:        <e164:dn>4.3.2.1.6.7.9.8.6.4.e164.arpa</e164:dn>
  C:        <e164:naptr>
  C:          <e164:order>100</e164:order>
  C:          <e164:pref>10</e164:pref>
  C:          <e164:flags>u</e164:flags>
  C:          <e164:svc>sip+E2U</e164:svc>
  C:          <e164:regex>!^.*$!sip:info@tele2.se!</e164:regex>
  C:        </e164:naptr>
  C:        <e164:naptr>
  C:          <e164:order>102</e164:order>
  C:          <e164:pref>10</e164:pref>
  C:          <e164:flags>u</e164:flags>
  C:          <e164:svc>mailto+E2U</e164:svc>
  C:          <e164:regex>!^.*$!mailto:info@tele2.se!</e164:regex>
  C:        </e164:naptr>
  C:        <e164:period unit="y">2</e164:period>
  C:        <e164:registrant>jd1234</e164:registrant>
  C:        <e164:contact type="admin">sh8013</e164:contact>
  C:        <e164:contact type="tech">sh8013</e164:contact>
  C:        <e164:authInfo type="pw">2fooBAR</e164:authInfo>
  C:      </e164:create>
  C:    </create>
  C:    <clTRID>ABC-12345</clTRID>
  C:  </command>
  C:</epp>

  When a <create> command has been processed successfully, the EPP
  <resData> element MUST contain a child <e164:creData> element that
  identifies the e164 namespace and the location of the e164 schema.
  The <e164:creData> element contains the following child elements:

  - A <e164:dn> element that contains the fully qualified name of the
  object.

  - An OPTIONAL <e164:exDate> element that contains the date and time
  identifying the end of the object's registration period.



Hollenbeck             Expires February 17, 2002               [Page 17]

Internet-Draft             EPP E.164 Mapping             August 17, 2001



  Example <create> response:

  S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
  S:<epp xmlns="urn:iana:xml:ns:epp-1.0"
  S:     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  S:     xsi:schemaLocation="urn:iana:xml:ns:epp-1.0 epp-1.0.xsd">
  S:  <response>
  S:    <result code="1000">
  S:      <msg>Command completed successfully</msg>
  S:    </result>
  S:    <resData>
  S:      <e164:creData xmlns:e164="urn:iana:xml:ns:e164-1.0"
  S:       xsi:schemaLocation="urn:iana:xml:ns:e164-1.0 e164-1.0.xsd">
  S:        <e164:dn>4.3.2.1.6.7.9.8.6.4.e164.arpa</e164:dn>
  S:        <e164:exDate>2003-08-27T22:00:00.0Z</e164:exDate>
  S:      </e164:creData>
  S:    </resData>
  S:    <unspec/>
  S:    <trID>
  S:      <clTRID>ABC-12345</clTRID>
  S:      <svTRID>54321-XYZ</svTRID>
  S:    </trID>
  S:  </response>
  S:</epp>

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

3.2.2 EPP <delete> Command

  The EPP <delete> command provides a transform operation that allows a
  client to delete an E.164 object.  In addition to the standard EPP
  command elements, the <delete> command MUST contain an <e164:delete>
  element that identifies the e164 namespace and the location of the
  e164 schema.  The <e164:delete> element contains the following child
  elements:

  - An <e164:dn> element that contains the fully qualified name of the
  object to be deleted.











Hollenbeck             Expires February 17, 2002               [Page 18]

Internet-Draft             EPP E.164 Mapping             August 17, 2001



  Example <delete> command:

  C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
  C:<epp xmlns="urn:iana:xml:ns:epp-1.0"
  C:     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  C:     xsi:schemaLocation="urn:iana:xml:ns:epp-1.0 epp-1.0.xsd">
  C:  <command>
  C:    <delete>
  C:      <e164:delete xmlns:e164="urn:iana:xml:ns:e164-1.0"
  C:       xsi:schemaLocation="urn:iana:xml:ns:e164-1.0 e164-1.0.xsd">
  C:        <e164:dn>4.3.2.1.6.7.9.8.6.4.e164.arpa</e164:dn>
  C:      </e164:delete>
  C:    </delete>
  C:    <unspec/>
  C:    <clTRID>ABC-12346</clTRID>
  C:  </command>
  C:</epp>

  When a <delete> command has been processed successfully, a server MUST
  respond with an EPP response with no <resData> element.

  Example <delete> response:

  S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
  S:<epp xmlns="urn:iana:xml:ns:epp-1.0"
  S:     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  S:     xsi:schemaLocation="urn:iana:xml:ns:epp-1.0 epp-1.0.xsd">
  S:  <response>
  S:    <result code="1000">
  S:      <msg>Command completed successfully</msg>
  S:    </result>
  S:    <unspec/>
  S:    <trID>
  S:      <clTRID>ABC-12346</clTRID>
  S:      <svTRID>54322-XYZ</svTRID>
  S:    </trID>
  S:  </response>
  S:</epp>

  An EPP error response MUST be returned if a <delete> command can not
  be processed for any reason.

3.2.3 EPP <renew> Command

  The EPP <renew> command provides a transform operation that allows a
  client to extend the validity period of an E.164 object.  In addition
  to the standard EPP command elements, the <renew> command MUST contain



Hollenbeck             Expires February 17, 2002               [Page 19]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


  an <e164:renew> element that identifies the e164 namespace and the
  location of the e164 schema.  The <e164:renew> element contains the
  following child elements:

  - An <e164:dn> element that contains the fully qualified name of the
  object whose validity period is to be extended.

  - An <e164:curExpDate> element that contains the date on which the
  current validity period ends.  This value ensures that repeated
  <renew> commands do not result in multiple unanticipated successful
  renewals.

  - An OPTIONAL <e164:period> element that contains the number of units
  to be added to the registration period of the object.

  Example <renew> command:

  C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
  C:<epp xmlns="urn:iana:xml:ns:epp-1.0"
  C:     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  C:     xsi:schemaLocation="urn:iana:xml:ns:epp-1.0 epp-1.0.xsd">
  C:  <command>
  C:    <renew>
  C:      <e164:renew xmlns:e164="urn:iana:xml:ns:e164-1.0"
  C:       xsi:schemaLocation="urn:iana:xml:ns:e164-1.0
  C:       e164-1.0.xsd">
  C:        <e164:dn>4.3.2.1.6.7.9.8.6.4.e164.arpa</e164:dn>
  C:        <e164:curExpDate>2000-04-03</e164:curExpDate>
  C:        <e164:period unit="y">1</e164:period>
  C:      </e164:renew>
  C:    </renew>
  C:    <unspec/>
  C:    <clTRID>ABC-12346</clTRID>
  C:  </command>
  C:</epp>

  When a <renew> command has been processed successfully, the EPP
  <resData> element MUST contain a child <e164:creData> element that
  identifies the e164 namespace and the location of the e164 schema.
  The <e164:creData> element contains the following child elements:

  - An <e164:dn> element that contains the fully qualified name of the
  object.

  - An <e164:exDate> element that contains the date and time identifying
  the end of the object's registration period.





Hollenbeck             Expires February 17, 2002               [Page 20]

Internet-Draft             EPP E.164 Mapping             August 17, 2001



  Example <renew> response:

  S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
  S:<epp xmlns="urn:iana:xml:ns:epp-1.0"
  S:     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  S:     xsi:schemaLocation="urn:iana:xml:ns:epp-1.0 epp-1.0.xsd">
  S:  <response>
  S:    <result code="1000">
  S:      <msg>Command completed successfully</msg>
  S:    </result>
  S:    <resData>
  S:      <e164:creData xmlns:e164="urn:iana:xml:ns:e164-1.0"
  S:       xsi:schemaLocation="urn:iana:xml:ns:e164-1.0
  S:       e164-1.0.xsd">
  S:        <e164:dn>4.3.2.1.6.7.9.8.6.4.e164.arpa</e164:dn>
  S:        <e164:exDate>2001-04-03T22:00:00.0Z</e164:exDate>
  S:      </e164:creData>
  S:    </resData>
  S:    <unspec/>
  S:    <trID>
  S:      <clTRID>ABC-12346</clTRID>
  S:      <svTRID>54322-XYZ</svTRID>
  S:    </trID>
  S:  </response>
  S:</epp>

  An EPP error response MUST be returned if a <renew> command can not be
  processed for any reason.

3.2.4 EPP <transfer> Command

  The EPP <transfer> command provides a transform operation that allows
  a client to manage requests to transfer the sponsorship of an E.164
  object.  In addition to the standard EPP command elements, the
  <transfer> command MUST contain a <e164:transfer> element that
  identifies the e164 namespace and the location of the e164 schema.
  The <e164:transfer> element contains the following child elements:

  - An <e164:dn> element that contains the fully qualified name of the
  object for which a transfer request is to be created, approved,
  rejected, or cancelled.

  - An OPTIONAL <e164:period> element that contains the number of units
  to be added to the registration period of the object upon completion
  of the transfer process.  This element MAY only be used when a
  transfer is requested, and it MUST be ignored if used otherwise.




Hollenbeck             Expires February 17, 2002               [Page 21]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


  - An <e164:authInfo> element that contains authorization information
  associated with the object or authorization information associated
  with the object's registrant or associated contacts.  This element is
  REQUIRED only when a transfer is requested, and it MUST be ignored if
  used otherwise.

  Every EPP <transfer> command MUST contain an "op" attribute that
  identifies the transfer operation to be performed.  Valid values,
  definitions, and authorizations for all attribute values are defined
  in [EPP].

  Example <transfer> request command:

  C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
  C:<epp xmlns="urn:iana:xml:ns:epp-1.0"
  C:     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  C:     xsi:schemaLocation="urn:iana:xml:ns:epp-1.0 epp-1.0.xsd">
  C:  <command>
  C:    <transfer op="request">
  C:      <e164:transfer xmlns:e164="urn:iana:xml:ns:e164-1.0"
  C:       xsi:schemaLocation="urn:iana:xml:ns:e164-1.0
  C:       e164-1.0.xsd">
  C:        <e164:dn>4.3.2.1.6.7.9.8.6.4.e164.arpa</e164:dn>
  C:        <e164:period unit="y">1</e164:period>
  C:        <e164:authInfo type="pw">2fooBAR</e164:authInfo>
  C:      </e164:transfer>
  C:    </transfer>
  C:    <unspec/>
  C:    <clTRID>ABC-12346</clTRID>
  C:  </command>
  C:</epp>

  When a <transfer> command has been processed successfully, the EPP
  <resData> element MUST contain a child <e164:trnData> element that
  identifies the e164 namespace and the location of the e164 schema.
  The <e164:trnData> element contains the same child elements defined
  for a transfer query response.














Hollenbeck             Expires February 17, 2002               [Page 22]

Internet-Draft             EPP E.164 Mapping             August 17, 2001



  Example <transfer> response:

  S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
  S:<epp xmlns="urn:iana:xml:ns:epp-1.0"
  S:     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  S:     xsi:schemaLocation="urn:iana:xml:ns:epp-1.0 epp-1.0.xsd">
  S:  <response>
  S:    <result code="1000">
  S:      <msg>Command completed successfully</msg>
  S:    </result>
  S:    <resData>
  S:      <e164:trnData xmlns:e164="urn:iana:xml:ns:e164-1.0"
  S:       xsi:schemaLocation="urn:iana:xml:ns:e164-1.0
  S:       e164-1.0.xsd">
  S:        <e164:dn>example.com</e164:dn>
  S:        <e164:trStatus>pending</e164:trStatus>
  S:        <e164:reID>ClientX</e164:reID>
  S:        <e164:reDate>2000-06-08T22:00:00.0Z</e164:reDate>
  S:        <e164:acID>ClientY</e164:acID>
  S:        <e164:acDate>2000-06-13T22:00:00.0Z</e164:acDate>
  S:        <e164:exDate>2002-09-08T22:00:00.0Z</e164:exDate>
  S:      </e164:trnData>
  S:    </resData>
  S:    <unspec/>
  S:    <trID>
  S:      <clTRID>ABC-12346</clTRID>
  S:      <svTRID>54322-XYZ</svTRID>
  S:    </trID>
  S:  </response>
  S:</epp>

  An EPP error response MUST be returned if a <transfer> command can not
  be processed for any reason.

3.2.5 EPP <update> Command

  The EPP <update> command provides a transform operation that allows a
  client to modify the attributes of an E.164 object.  In addition to
  the standard EPP command elements, the <update> command MUST contain
  an <e164:update> element that identifies the e164 namespace and the
  location of the e164 schema. The <e164:update> element contains the
  following child elements:

  - An <e164:dn> element that contains the fully qualified name of the
  object to be updated.

  - An OPTIONAL <e164:add> element that contains attribute values to be



Hollenbeck             Expires February 17, 2002               [Page 23]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


  added to the object.

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

  - An OPTIONAL <e164:chg> element that contains object attribute values
  to be changed.

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

  - Zero or more <e164:naptr> elements.  Structure of the <164:naptr>
  element is described as part of the information returned from the
  <info> command.  Remove operations MUST NOT remove all of the
  <e164:naptr> elements associated with an object without adding at
  least one new element.

  - Zero or more <e164:contact> elements that contain the identifiers
  for contact objects to be associated with or removed from the E.164
  object.  Contact object identifiers MUST be known to the server before
  the contact object can be associated with the E.164 object.

  - Zero or more <e164:status> elements that contain status values to be
  applied to or removed from the object.  When specifying a value to be
  removed, only the attribute value is significant; element text is not
  required to match a value for removal.

  An <e164:chg> element contains the following child elements:

  - An <e164:registrant> element that contains the identifier for the
  human or organizational social information (contact) object to be
  associated with the object as the object registrant.  This object
  identifier MUST be known to the server before the contact object can
  be associated with the E.164 object.

  - An <e164:authInfo> element that contains authorization information
  associated with the E.164 object.













Hollenbeck             Expires February 17, 2002               [Page 24]

Internet-Draft             EPP E.164 Mapping             August 17, 2001



  Example <update> command:

  C:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
  C:<epp xmlns="urn:iana:xml:ns:epp-1.0"
  C:     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  C:     xsi:schemaLocation="urn:iana:xml:ns:epp-1.0 epp-1.0.xsd">
  C:  <command>
  C:    <update>
  C:      <e164:update xmlns:e164="urn:iana:xml:ns:e164-1.0"
  C:       xsi:schemaLocation="urn:iana:xml:ns:e164-1.0
  C:       e164-1.0.xsd">
  C:        <e164:dn>4.3.2.1.6.7.9.8.6.4.e164.arpa</e164:dn>
  C:        <e164:add>
  C:          <e164:contact type="tech">mak21</e164:contact>
  C:          <e164:status s="clientHold" lang="en">
  C:            Payment overdue.
  C:          </e164:status>
  C:        </e164:add>
  C:        <e164:rem>
  C:          <e164:naptr>
  C:            <e164:order>102</e164:order>
  C:            <e164:pref>10</e164:pref>
  C:            <e164:flags>u</e164:flags>
  C:            <e164:svc>mailto+E2U</e164:svc>
  C:            <e164:regex>!^.*$!mailto:info@tele2.se!</e164:regex>
  C:          </e164:naptr>
  C:          <e164:contact type="tech">sh8013</e164:contact>
  C:          <e164:status s="clientTransferProhibited"/>
  C:        </e164:rem>
  C:        <e164:chg>
  C:          <e164:registrant>sh8013</e164:registrant>
  C:          <e164:authInfo type="pw">2BARfoo</e164:authInfo>
  C:        </e164:chg>
  C:      </e164:update>
  C:    </update>
  C:    <unspec/>
  C:    <clTRID>ABC-12346</clTRID>
  C:  </command>
  C:</epp>

  When an <update> command has been processed successfully, a server
  MUST respond with an EPP response with no <resData> element.








Hollenbeck             Expires February 17, 2002               [Page 25]

Internet-Draft             EPP E.164 Mapping             August 17, 2001



  Example <update> response:

  S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
  S:<epp xmlns="urn:iana:xml:ns:epp-1.0"
  S:     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  S:     xsi:schemaLocation="urn:iana:xml:ns:epp-1.0 epp-1.0.xsd">
  S:  <response>
  S:    <result code="1000">
  S:      <msg>Command completed successfully</msg>
  S:    </result>
  S:    <unspec/>
  S:    <trID>
  S:      <clTRID>ABC-12346</clTRID>
  S:      <svTRID>54322-XYZ</svTRID>
  S:    </trID>
  S:  </response>
  S:</epp>

  An EPP error response MUST be returned if an <update> command can not
  be processed for any reason.






























Hollenbeck             Expires February 17, 2002               [Page 26]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


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.

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

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

  <!--
  Import common element types.
  -->
    <import namespace="urn:iana:xml:ns:eppcom-1.0"
            schemaLocation="eppcom-1.0.xsd"/>
    <import namespace="urn:iana:xml:ns:epp-1.0"
            schemaLocation="epp-1.0.xsd"/>

    <annotation>
      <documentation>
        Extensible Provisioning Protocol v1.0
        E.164 number provisioning schema.
      </documentation>
    </annotation>

  <!--
  Types used within an EPP greeting.
  -->
    <element name="svc"/>

  <!--
  Child elements found in EPP commands.
  -->
    <element name="check" type="e164:mNameType"/>
    <element name="create" type="e164:createType"/>
    <element name="delete" type="e164:sNameType"/>
    <element name="info" type="e164:sNameType"/>
    <element name="renew" type="e164:renewType"/>
    <element name="transfer" type="e164:transferType"/>
    <element name="update" type="e164:updateType"/>

  <!--
  Child elements of the <create> command.



Hollenbeck             Expires February 17, 2002               [Page 27]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


  -->
    <complexType name="createType">
      <sequence>
        <element name="dn" type="eppcom:labelType"/>
        <element name="naptr" type="e164:naptrType"
         maxOccurs="unbounded"/>
        <element name="period" type="e164:periodType"
         minOccurs="0"/>
        <element name="registrant" type="eppcom:clIDType"
         minOccurs="0"/>
        <element name="contact" type="e164:contactType"
         minOccurs="0" maxOccurs="unbounded"/>
        <element name="authInfo" type="eppcom:authInfoType"/>
      </sequence>
    </complexType>

    <complexType name="naptrType">
      <sequence>
        <element name="order" type="unsignedShort"/>
        <element name="pref" type="unsignedShort"/>
        <element name="flags" type="e164:flagsType"/>
        <element name="svc" type="e164:svcType"
         minOccurs="0"/>
        <element name="regex" type="e164:regexType"
         minOccurs="0"/>
      </sequence>
    </complexType>

    <simpleType name="flagsType">
      <restriction base="token">
        <minLength value="1"/>
      </restriction>
    </simpleType>

    <simpleType name="svcType">
      <restriction base="token">
        <minLength value="0"/>
        <maxLength value="65"/>
      </restriction>
    </simpleType>

    <simpleType name="regexType">
      <restriction base="token">
        <minLength value="0"/>
      </restriction>
    </simpleType>

    <complexType name="periodType">



Hollenbeck             Expires February 17, 2002               [Page 28]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


      <simpleContent>
        <extension base="e164:pLimitType">
          <attribute name="unit" type="e164:pUnitType"
           use="required"/>
        </extension>
      </simpleContent>
    </complexType>

    <simpleType name="pLimitType">
      <restriction base="unsignedShort">
        <minInclusive value="1"/>
        <maxInclusive value="99"/>
      </restriction>
    </simpleType>

    <simpleType name="pUnitType">
      <restriction base="token">
        <enumeration value="y"/>
        <enumeration value="m"/>
      </restriction>
    </simpleType>

    <complexType name="contactType">
      <simpleContent>
        <extension base="eppcom:clIDType">
          <attribute name="type" type="e164:contactAttrType"
           use="optional"/>
        </extension>
      </simpleContent>
    </complexType>

    <simpleType name="contactAttrType">
      <restriction base="token">
        <enumeration value="admin"/>
        <enumeration value="billing"/>
        <enumeration value="tech"/>
      </restriction>
    </simpleType>

  <!--
  Child element of commands that require a single name.
  -->
    <complexType name="sNameType">
      <sequence>
        <element name="dn" type="eppcom:labelType"/>
      </sequence>
    </complexType>




Hollenbeck             Expires February 17, 2002               [Page 29]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


  <!--
  Child element of commands that accept multiple names.
  -->
    <complexType name="mNameType">
      <sequence>
        <element name="dn" type="eppcom:labelType"
         maxOccurs="unbounded"/>
      </sequence>
    </complexType>

  <!--
  Child elements of the <renew> command.
  -->
    <complexType name="renewType">
      <sequence>
        <element name="dn" type="eppcom:labelType"/>
        <element name="curExpDate" type="date"/>
        <element name="period" type="e164:periodType"
         minOccurs="0"/>
      </sequence>
    </complexType>

  <!--
  Child elements of the <transfer> command.
  -->
    <complexType name="transferType">
      <sequence>
        <element name="dn" type="eppcom:labelType"/>
        <element name="period" type="e164:periodType"
         minOccurs="0"/>
        <element name="authInfo" type="eppcom:authInfoType"
         minOccurs="0"/>
      </sequence>
    </complexType>

  <!--
  Child elements of the <update> command.
  -->
    <complexType name="updateType">
      <sequence>
        <element name="dn" type="eppcom:labelType"/>
        <choice minOccurs="1" maxOccurs="3">
          <element name="add" type="e164:addRemType"
           minOccurs="0"/>
          <element name="rem" type="e164:addRemType"
           minOccurs="0"/>
          <element name="chg" type="e164:chgType"
           minOccurs="0"/>



Hollenbeck             Expires February 17, 2002               [Page 30]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


         </choice>
      </sequence>
    </complexType>

  <!--
  Data elements that can be added or removed.
  -->
    <complexType name="addRemType">
      <choice minOccurs="1" maxOccurs="3">
        <element name="naptr" type="e164:naptrType"
         minOccurs="0" maxOccurs="unbounded"/>
        <element name="contact" type="e164:contactType"
         minOccurs="0" maxOccurs="unbounded"/>
        <element name="status" type="e164:statusType"
         minOccurs="0" maxOccurs="14"/>
      </choice>
    </complexType>

  <!--
  Data elements that can be changed.
  -->
    <complexType name="chgType">
      <sequence>
        <element name="registrant" type="eppcom:clIDType"
         minOccurs="0"/>
        <element name="authInfo" type="eppcom:authInfoType"
         minOccurs="0"/>
      </sequence>
    </complexType>

  <!--
  Child response elements.
  -->
    <element name="chkData" type="e164:chkDataType"/>
    <element name="creData" type="e164:creDataType"/>
    <element name="infData" type="e164:infDataType"/>
    <element name="trnData" type="e164:trnDataType"/>

  <!--
  <check> response elements.
  -->
    <complexType name="chkDataType">
      <sequence>
        <element name="cd" type="e164:checkType"
         maxOccurs="unbounded"/>
      </sequence>
    </complexType>




Hollenbeck             Expires February 17, 2002               [Page 31]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


    <complexType name="checkType">
      <simpleContent>
        <extension base = "eppcom:labelType">
          <attribute name="x" type="eppcom:checkType"
           use="required"/>
        </extension>
      </simpleContent>
    </complexType>

  <!--
  <create> and <renew> response elements.
  -->
    <complexType name="creDataType">
      <sequence>
        <element name="dn" type="eppcom:labelType"/>
        <element name="exDate" type="dateTime"
         minOccurs="0"/>
      </sequence>
    </complexType>

  <!--
  <info> response elements.
  -->
    <complexType name="infDataType">
      <sequence>
        <element name="dn" type="eppcom:labelType"/>
        <element name="roid" type="eppcom:roidType"/>
        <element name="naptr" type="e164:naptrType"
         maxOccurs="unbounded"/>
        <element name="status" type="e164:statusType"
         maxOccurs="14"/>
        <element name="registrant" type="e164:contactType"
         minOccurs="0"/>
        <element name="contact" type="e164:contactType"
         minOccurs="0" maxOccurs="unbounded"/>
        <element name="clID" type="eppcom:clIDType"/>
        <element name="crID" type="eppcom:clIDType"/>
        <element name="crDate" type="dateTime"/>
        <element name="upID" type="eppcom:clIDType"
         minOccurs="0"/>
        <element name="upDate" type="dateTime"
         minOccurs="0"/>
        <element name="exDate" type="dateTime"
         minOccurs="0"/>
        <element name="trDate" type="dateTime"
         minOccurs="0"/>
        <element name="authInfo" type="eppcom:authInfoType"/>
      </sequence>



Hollenbeck             Expires February 17, 2002               [Page 32]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


    </complexType>

  <!--
  Status is a combination of attributes and an optional human-readable
  message that may be expressed in languages other than English.
  -->
    <complexType name="statusType">
      <simpleContent>
        <extension base="normalizedString">
          <attribute name="s" type="e164:statusValueType"
           use="required"/>
          <attribute name="lang" type="language"
           use="optional" default="en"/>
        </extension>
      </simpleContent>
    </complexType>

    <simpleType name="statusValueType">
      <restriction base="token">
        <enumeration value="clientDeleteProhibited"/>
        <enumeration value="clientHold"/>
        <enumeration value="clientRenewProhibited"/>
        <enumeration value="clientTransferProhibited"/>
        <enumeration value="clientUpdateProhibited"/>
        <enumeration value="inactive"/>
        <enumeration value="ok"/>
        <enumeration value="pendingDelete"/>
        <enumeration value="pendingTransfer"/>
        <enumeration value="pendingVerification"/>
        <enumeration value="serverDeleteProhibited"/>
        <enumeration value="serverHold"/>
        <enumeration value="serverRenewProhibited"/>
        <enumeration value="serverTransferProhibited"/>
        <enumeration value="serverUpdateProhibited"/>
      </restriction>
    </simpleType>

  <!--
  <transfer> response elements.
  -->
    <complexType name="trnDataType">
      <sequence>
        <element name="dn" type="eppcom:labelType"/>
        <element name="trStatus" type="eppcom:trStatusType"/>
        <element name="reID" type="eppcom:clIDType"/>
        <element name="reDate" type="dateTime"/>
        <element name="acID" type="eppcom:clIDType"/>
        <element name="acDate" type="dateTime"/>



Hollenbeck             Expires February 17, 2002               [Page 33]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


        <element name="exDate" type="dateTime"
         minOccurs="0"/>
      </sequence>
    </complexType>

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










































Hollenbeck             Expires February 17, 2002               [Page 34]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


5. 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.  Compliant XML processors are
  REQUIRED to understand both UTF-8 and UTF-16.  Though XML includes
  provisions to identify other character set encodings through use of an
  "encoding" attribute in an <?xml?> declaration, EPP use with character
  sets other than UTF-8 is NOT RECOMMENDED.

  All date-time values presented via EPP MUST be expressed in Universal
  Coordinated Time using the Gregorian calendar.  XML Schema allows use
  of time zone identifiers to indicate offsets from the zero meridian,
  but this option MUST NOT be used with EPP.  Both extended and
  truncated date and time forms defined in [ISO8601] MAY be used, though
  a server SHOULD use one form or the other consistently.

6. IANA Considerations

  XML schemas require a URI for unique identification.  Schemas MUST be
  registered to ensure URI uniqueness, but the IETF does not currently
  have a recommended repository for the registration of XML schemas.
  This document uses URNs to describe XML namespaces and XML schemas
  conforming to a registry mechanism described in [IANA-XML].

  IANA SHOULD maintain a registry of XML namespace and schema URI
  assignments.  URI assignment requests SHOULD be reviewed by a
  designated expert, and values SHOULD be assigned only as a result of
  standards action taken by the IESG.

  This document requests assignment of the following URIs:

  urn:iana:xml:ns:e164-1.0: The namespace URI for this EPP mapping.

  urn:iana:xml:schema:e164-1.0: The schema URI for this EPP mapping.

7. Security Considerations

  The object mapping described in this document does not provide any
  security services beyond those specified by [EPP] and protocol layers
  used by EPP.










Hollenbeck             Expires February 17, 2002               [Page 35]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


8. Acknowledgements

  TBD.

9. References

  [E164a] ITU-T Recommendation E.164: "The International Public
  Telecommunication Numbering Plan", May 1997.

  [E164b] Complement To ITU-T Recommendation E.164 (05/1997):  "List of
  ITU-T Recommendation E.164 assigned country codes", June 2000.

  [EPP] S. Hollenbeck: "Extensible Provisioning Protocol", work in
  progress.

  [EPP-C] S. Hollenbeck: "Extensible Provisioning Protocol Contact
  Mapping", work in progress.

  [IANA-XML] M. Mealling: "The IANA XML Registry", work in progress.

  [RFC2119] S. Bradner: "Key Words for Use in RFCs to Indicate
  Requirement Levels", BCP 14, RFC 2119, March 1997.

  [RFC2915] M. Mealling, R. Daniel: "The Naming Authority Pointer
  (NAPTR) DNS Resource Record", RFC 2915, September 2000.

  [RFC2916] P. Faltstrom: "E.164 number and DNS", RFC 2916, September
  2000.

  [XML] Editors T. Bray et al.: "Extensible Markup Language (XML) 1.0
  (Second Edition)", W3C Recommendation 6 October 2000.

  [XMLS-1] Editors H. Thompson et al.: "XML Schema Part 1: Structures",
  W3C Recommendation 2 May 2001.

  [XMLS-2] Editors P. Biron, A. Malhotra: "XML Schema Part 2:
  Datatypes", W3C Recommendation 2 May 2001.














Hollenbeck             Expires February 17, 2002               [Page 36]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


10. Author's Address

  Scott Hollenbeck
  VeriSign Global Registry Services
  21345 Ridgetop Circle
  Dulles, VA 20166-6503
  USA
  shollenbeck@verisign.com











































Hollenbeck             Expires February 17, 2002               [Page 37]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


A. Revisions From Previous Version

  None; this is the initial version.
















































Hollenbeck             Expires February 17, 2002               [Page 38]

Internet-Draft             EPP E.164 Mapping             August 17, 2001


B. Full Copyright Statement

  Copyright (C) The Internet Society 2001.  All Rights Reserved.

  This document and translations of it may be copied and furnished to
  others, and derivative works that comment on or otherwise explain it
  or assist in its implementation may be prepared, copied, published and
  distributed, in whole or in part, without restriction of any kind,
  provided that the above copyright notice and this paragraph are
  included on all such copies and derivative works.  However, this
  document itself may not be modified in any way, such as by removing
  the copyright notice or references to the Internet Society or other
  Internet organizations, except as needed for the purpose of developing
  Internet standards in which case the procedures for copyrights defined
  in the Internet Standards process must be followed, or as required to
  translate it into languages other than English.

  The limited permissions granted above are perpetual and will not be
  revoked by the Internet Society or its successors or assigns.

  This document and the information contained herein is provided on an
  "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
  TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT
  NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN
  WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
  MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

  Funding for the RFC Editor function is currently provided by the
  Internet Society.




















Hollenbeck             Expires February 17, 2002               [Page 39]