Internet Engineering Task Force S. Hollenbeck Internet-Draft VeriSign, Inc. June 29, 2001 Expires: December 29, 2001 Extensible Provisioning Protocol Domain Name Mapping 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 Internet domain names stored in a shared central repository. Specified in XML, the mapping defines EPP command syntax and semantics as applied to domain names. 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 December 29, 2001 [Page 1] Internet-Draft EPP Domain Name Mapping June 29, 2001 Table of Contents 1. Introduction ................................................. 3 2. Object Attributes ............................................ 4 2.1 Domain Name and Host Names .................................. 4 2.2 Contact and Client Identifiers .............................. 4 2.3 Status Values ............................................... 4 2.4 Dates and Times ............................................. 6 2.5 Validity Periods ............................................ 6 2.6 Authorization Information ................................... 6 3. EPP Command Mapping .......................................... 7 3.1 EPP Query Commands .......................................... 7 3.1.1 EPP Command ....................................... 7 3.1.2 EPP Command ........................................ 8 3.1.3 EPP Command .................................... 11 3.2 EPP Transform Commands ...................................... 14 3.2.1 EPP Command ...................................... 14 3.2.2 EPP Command ...................................... 16 3.2.3 EPP Command ....................................... 17 3.2.4 EPP Command .................................... 19 3.2.5 EPP Command ...................................... 21 4. Formal Syntax ................................................ 25 5. Internationalization Considerations .......................... 32 6. IANA Considerations .......................................... 32 7. Security Considerations ...................................... 32 8. Acknowledgements ............................................. 33 9. References ................................................... 34 10. Author's Address ............................................ 35 A. Revisions From Previous Version .............................. 36 B. Full Copyright Statement ..................................... 37 Hollenbeck Expires December 29, 2001 [Page 2] Internet-Draft EPP Domain Name Mapping June 29, 2001 1. Introduction This document describes an internet domain name 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. 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. This document is being discussed on the "ietf-provreg" mailing list. To join the list, send a message to with the words "subscribe ietf-provreg" in the body of the message. There is a web site for the list archives at http://www.cafax.se/ietf-provreg. Hollenbeck Expires December 29, 2001 [Page 3] Internet-Draft EPP Domain Name Mapping June 29, 2001 2. Object Attributes An EPP domain 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 Domain Name and Host Names The syntax for domain and host names described in this document MUST conform to [RFC952] as updated by [RFC1123]. These conformance requirements MAY change as a result of progressing work in developing standards for internationalized domain names. A server MAY restrict allowable domain names to a particular top level domain, second level domain, or other domain for which the server is authoritative. 2.2 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.3 Status Values A domain object MUST always have at least one associated status value. Status values MAY be set only by the client that sponsors a domain object and by the server on which the object resides. A client MAY change the status of a domain object using the EPP 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. Hollenbeck Expires December 29, 2001 [Page 4] Internet-Draft EPP Domain Name Mapping June 29, 2001 clientHold, serverHold Delegation information MUST be withheld from publication in the object's nominal zone. clientRenewProhibited, serverRenewProhibited 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 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 Hollenbeck Expires December 29, 2001 [Page 5] Internet-Draft EPP Domain Name Mapping June 29, 2001 other status value combinations are valid. 2.4 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 a server SHOULD use one form or the other consistently. 2.5 Validity Periods A domain name object MAY have a specified validity period. If server policy supports domain object validity periods, the validity period is defined when a domain object is created, and it MAY be extended by the EPP or commands. As a matter of server policy, this specification does not define actions to be taken upon expiration of a domain 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.6 Authorization Information Authorization information is associated with domain objects to facilitate transfer operations. Authorization information is assigned when a domain 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 December 29, 2001 [Page 6] Internet-Draft EPP Domain Name Mapping June 29, 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 internet domain names via EPP. 3.1 EPP Query Commands EPP provides three commands to retrieve domain information: to determine if a domain object is known to the server, and to retrieve detailed information associated with a domain object, and to retrieve domain object transfer status information. 3.1.1 EPP Command The EPP command is used to determine if a domain object is known to the server. In addition to the standard EPP command elements, the command MUST contain a element that identifies the domain namespace and the location of the domain schema. The element contains the following child elements: - One or more elements that contain the fully qualified names of the domain objects to be queried. Example command: C: C: C: C: C: C: example1.com C: example2.com C: example3.com C: C: C: C: ABC-12346 C: C: When a command has been processed successfully, the EPP element MUST contain a child element that Hollenbeck Expires December 29, 2001 [Page 7] Internet-Draft EPP Domain Name Mapping June 29, 2001 identifies the domain namespace and the location of the domain schema. The element contains the following child elements: - One or more elements that contain the fully qualified names for the queried domain objects and an "x" attribute whose value identifies the object as either "+" for a known object or "-" for an unknown object. Example response: S: S: S: S: S: Command completed successfully S: S: S: S: example1.com S: example2.com S: example3.com S: S: S: S: S: ABC-12346 S: 54322-XYZ S: S: S: An EPP error response MUST be returned if a command can not be processed for any reason. 3.1.2 EPP Command The EPP command is used to retrieve information associated with a domain object. In addition to the standard EPP command elements, the command MUST contain a element that identifies the domain namespace and the location of the domain schema. The element contains the following child elements: - A element that contains the fully qualified name of the domain object to be queried. Hollenbeck Expires December 29, 2001 [Page 8] Internet-Draft EPP Domain Name Mapping June 29, 2001 Example command: C: C: C: C: C: C: example.com C: C: C: C: ABC-12346 C: C: When an command has been processed successfully, the EPP element MUST contain a child element that identifies the domain namespace and the location of the domain schema. The element contains the following child elements: - A element that contains the fully qualified name of the domain object. - A element that contains the Repository Object IDentifier assigned to the domain object when the object was created. - One or more elements that contain the current status descriptors associated with the domain. - If supported by the server, one element and one or more elements that contain identifiers for the human or organizational social information objects associated with the domain object. - Zero or more elements that contain the fully qualified names of the name server objects associated with the domain object. - Zero or more elements that contain the fully qualified names of the host objects created under this superordinate domain object. - A element that contains the identifier of the sponsoring client. Hollenbeck Expires December 29, 2001 [Page 9] Internet-Draft EPP Domain Name Mapping June 29, 2001 - A element that contains the identifier of the client that created the domain object. - A element that contains the date and time of domain object creation. - A element that contains the date and time identifying the end of the domain object's registration period. - A element that contains the identifier of the client that last updated the domain object. This element MUST NOT be present if the domain has never been modified. - A element that contains the date and time of the most recent domain object modification. This element MUST NOT be present if the domain object has never been modified. - A elements that contains the date and time of the most recent successful domain object transfer. This element MUST NOT be provided if the domain object has never been transferred. - A element that contains authorization information associated with the domain object. This element MUST NOT be provided if the querying client is not the current sponsoring client. Hollenbeck Expires December 29, 2001 [Page 10] Internet-Draft EPP Domain Name Mapping June 29, 2001 Example response: S: S: S: S: S: Command completed successfully S: S: S: S: example.com S: EXAMPLE1-VRSN S: S: jd1234 S: sh8013 S: sh8013 S: ns1.example.com S: ns2.example.com S: ns1.example.com S: ns2.example.com S: ClientX S: ClientY S: 1999-04-03T22:00:00.0Z S: ClientX S: 1999-12-03T09:00:00.0Z S: 2005-04-03T22:00:00.0Z S: 2000-04-08T09:00:00.0Z S: 2fooBAR S: S: S: S: S: ABC-12346 S: 54322-XYZ S: S: S: An EPP error response MUST be returned if an command can not be processed for any reason. 3.1.3 EPP Command Hollenbeck Expires December 29, 2001 [Page 11] Internet-Draft EPP Domain Name Mapping June 29, 2001 The EPP 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 command MUST contain an "op" attribute with value "query", and a element that identifies the domain namespace and the location of the domain schema. The element contains the following child elements: - A element that contains the fully qualified name of the domain object to be queried. Example query command: C: C: C: C: C: C: example.com C: C: C: C: ABC-12346 C: C: When a query command has been processed successfully, the EPP element MUST contain a child element that identifies the domain namespace and the location of the domain schema. The element contains the following child elements: - A element that contains the fully qualified name of the domain object. - A element that contains the state of the most recent transfer request. - A element that contains the identifier of the client that requested the object transfer. - A element that contains the date and time that the transfer was requested. Hollenbeck Expires December 29, 2001 [Page 12] Internet-Draft EPP Domain Name Mapping June 29, 2001 - A element that contains the identifier of the client that SHOULD act upon the transfer request. - A 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 element that contains the end of the domain object's validity period if the command caused or causes a change in the validity period. Example query response: S: S: S: S: S: Command completed successfully S: S: S: S: example.com S: pending S: ClientX S: 2000-06-06T22:00:00.0Z S: ClientY S: 2000-06-11T22:00:00.0Z S: 2002-09-08T22:00:00.0Z S: S: S: S: S: ABC-12346 S: 54322-XYZ S: S: S: An EPP error response MUST be returned if a query command can not be processed for any reason. Hollenbeck Expires December 29, 2001 [Page 13] Internet-Draft EPP Domain Name Mapping June 29, 2001 3.2 EPP Transform Commands EPP provides five commands to transform domain objects: to create an instance of a domain object, to delete an instance of a domain object, to extend the validity period of a domain object, to manage domain object sponsorship changes, and to change information associated with a domain object. 3.2.1 EPP Command The EPP command provides a transform operation that allows a client to create a domain object. In addition to the standard EPP command elements, the command MUST contain a element that identifies the domain namespace and the location of the domain schema. The element contains the following child elements: - A element that contains the fully qualified name of the domain object to be created. - An OPTIONAL element that contains the initial registration period of the domain object. A server MAY define a default initial registration period if not specified by the client. - Zero or more elements that contain the fully qualified name of a known host object to provide resolution services for the domain. A host object MUST be known to the server before the host object can be associated with a domain object. A server MUST provide host object services to provide domain name services. The EPP mapping for host objects is described in [EPP-H]. - An OPTIONAL element that contains the identifier for the human or organizational social information (contact) object to be associated with the domain object as the object registrant. This object identifier MUST be known to the server before the contact object can be associated with the domain object. The EPP mapping for contact objects is described in [EPP-C]. - Zero or more OPTIONAL elements that contain the identifiers for other contact objects to be associated with the domain object. Contact object identifiers MUST be known to the server before the contact object can be associated with the domain object. - A element that contains authorization information to be associated with the domain object. Hollenbeck Expires December 29, 2001 [Page 14] Internet-Draft EPP Domain Name Mapping June 29, 2001 Example command: C: C: C: C: C: C: example.com C: 2 C: ns1.example.com C: ns2.example.com C: jd1234 C: sh8013 C: sh8013 C: 2fooBAR C: C: C: C: ABC-12345 C: C: When a command has been processed successfully, the EPP element MUST contain a child element that identifies the domain namespace and the location of the domain schema. The element contains the following child elements: - A element that contains the fully qualified name of the domain object. - An OPTIONAL element that contains the date and time identifying the end of the domain object's registration period. Hollenbeck Expires December 29, 2001 [Page 15] Internet-Draft EPP Domain Name Mapping June 29, 2001 Example response: S: S: S: S: S: Command completed successfully S: S: S: S: example.com S: 2002-06-08T22:00:00.0Z S: S: S: S: S: ABC-12345 S: 54321-XYZ S: S: S: An EPP error response MUST be returned if a command can not be processed for any reason. 3.2.2 EPP Command The EPP command provides a transform operation that allows a client to delete a domain object. In addition to the standard EPP command elements, the command MUST contain a element that identifies the domain namespace and the location of the domain schema. The element contains the following child elements: - A element that contains the fully qualified name of the domain object to be deleted. A domain object SHOULD NOT be deleted if subordinate host objects are associated with the domain object. For example, if domain "example.com" exists, and host object "ns1.example.com" also exists, then domain "example.com" SHOULD NOT be deleted until host "ns1.example.com" has been either deleted or renamed to exist in a different superordinate domain. Hollenbeck Expires December 29, 2001 [Page 16] Internet-Draft EPP Domain Name Mapping June 29, 2001 Example command: C: C: C: C: C: C: example.com C: C: C: C: ABC-12346 C: C: When a command has been processed successfully, a server MUST respond with an EPP response with no element. Example response: S: S: S: S: S: Command completed successfully S: S: S: S: ABC-12346 S: 54322-XYZ S: S: S: An EPP error response MUST be returned if a command can not be processed for any reason. 3.2.3 EPP Command The EPP command provides a transform operation that allows a client to extend the validity period of a domain object. In addition Hollenbeck Expires December 29, 2001 [Page 17] Internet-Draft EPP Domain Name Mapping June 29, 2001 to the standard EPP command elements, the command MUST contain a element that identifies the domain namespace and the location of the domain schema. The element contains the following child elements: - A element that contains the fully qualified name of the domain object whose validity period is to be extended. - A element that contains the date on which the current validity period ends. This value ensures that repeated commands do not result in multiple unanticipated successful renewals. - An OPTIONAL element that contains the number of units to be added to the registration period of the domain object. Example command: C: C: C: C: C: C: example.com C: 2000-04-03 C: 5 C: C: C: C: ABC-12346 C: C: When a command has been processed successfully, the EPP element MUST contain a child element that identifies the domain namespace and the location of the domain schema. The element contains the following child elements: - A element that contains the fully qualified name of the domain object. - A element that contains the date and time identifying the end of the domain object's registration period. Hollenbeck Expires December 29, 2001 [Page 18] Internet-Draft EPP Domain Name Mapping June 29, 2001 Example response: S: S: S: S: S: Command completed successfully S: S: S: S: example.com S: 2005-04-03T22:00:00.0Z S: S: S: S: S: ABC-12346 S: 54322-XYZ S: S: S: An EPP error response MUST be returned if a command can not be processed for any reason. 3.2.4 EPP Command The EPP command provides a transform operation that allows a client to manage requests to transfer the sponsorship of a domain object. In addition to the standard EPP command elements, the command MUST contain a element that identifies the domain namespace and the location of the domain schema. The element contains the following child elements: - A element that contains the fully qualified name of the domain object for which a transfer request is to be created, approved, rejected, or cancelled. - An OPTIONAL element that contains the number of units to be added to the registration period of the domain object at 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 December 29, 2001 [Page 19] Internet-Draft EPP Domain Name Mapping June 29, 2001 - A element that contains authorization information associated with the domain object or authorization information associated with the domain 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 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]. Transfer of a domain object MUST implicitly transfer all host objects that are subordinate to the domain object. For example, if domain object "example.com" is transferred and host object "ns1.example.com" exists, the host object MUST be transferred as part of the "example.com" transfer process. Host objects that are subject to transfer when transferring a domain object are listed in the response to an EPP command performed on the domain object. Example request command: C: C: C: C: C: C: example.com C: 1 C: C: 2fooBAR C: C: C: C: C: ABC-12346 C: C: When a command has been processed successfully, the EPP element MUST contain a child element that identifies the domain namespace and the location of the domain schema. The element contains the same child elements defined for a transfer query response. Hollenbeck Expires December 29, 2001 [Page 20] Internet-Draft EPP Domain Name Mapping June 29, 2001 Example response: S: S: S: S: S: Command completed successfully S: S: S: S: example.com S: pending S: ClientX S: 2000-06-08T22:00:00.0Z S: ClientY S: 2000-06-13T22:00:00.0Z S: 2002-09-08T22:00:00.0Z S: S: S: S: S: ABC-12346 S: 54322-XYZ S: S: S: An EPP error response MUST be returned if a command can not be processed for any reason. 3.2.5 EPP Command The EPP command provides a transform operation that allows a client to modify the attributes of a domain object. In addition to the standard EPP command elements, the command MUST contain a element that identifies the domain namespace and the location of the domain schema. The element contains the following child elements: - A element that contains the fully qualified name of the domain object to be updated. - An OPTIONAL element that contains attribute values to Hollenbeck Expires December 29, 2001 [Page 21] Internet-Draft EPP Domain Name Mapping June 29, 2001 be added to the object. - An OPTIONAL element that contains attribute values to be removed from the object. - An OPTIONAL element that contains object attribute values to be changed. At least one , , or element MUST be provided. The and elements contain the following child elements: - Zero or more elements that contain the fully qualified name of a known host object. A host object MUST be known to the server before a server attribute can be added or removed from a domain object. The EPP mapping for host objects is described in [EPP-H]. - Zero or more elements that contain the identifiers for contact objects to be associated with or removed from the domain object. Contact object identifiers MUST be known to the server before the contact object can be associated with the domain object. - Zero or more 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. A element contains the following child elements: - A element that contains the identifier for the human or organizational social information (contact) object to be associated with the domain object as the object registrant. This object identifier MUST be known to the server before the contact object can be associated with the domain object. - A element that contains authorization information associated with the domain object. Hollenbeck Expires December 29, 2001 [Page 22] Internet-Draft EPP Domain Name Mapping June 29, 2001 Example command: C: C: C: C: C: C: example.com C: C: ns1.example2.com C: mak21 C: C: Payment overdue. C: C: C: C: ns2.example.com C: sh8013 C: C: C: C: sh8013 C: 2BARfoo C: C: C: C: C: ABC-12346 C: C: When an command has been processed successfully, a server MUST respond with an EPP response with no element. Hollenbeck Expires December 29, 2001 [Page 23] Internet-Draft EPP Domain Name Mapping June 29, 2001 Example response: S: S: S: S: S: Command completed successfully S: S: S: S: ABC-12346 S: 54322-XYZ S: S: S: An EPP error response MUST be returned if an command can not be processed for any reason. Hollenbeck Expires December 29, 2001 [Page 24] Internet-Draft EPP Domain Name Mapping June 29, 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. Extensible Provisioning Protocol v1.0 domain provisioning schema. Hollenbeck Expires December 29, 2001 [Page 26] Internet-Draft EPP Domain Name Mapping June 29, 2001 Hollenbeck Expires December 29, 2001 [Page 29] Internet-Draft EPP Domain Name Mapping June 29, 2001 Hollenbeck Expires December 29, 2001 [Page 30] Internet-Draft EPP Domain Name Mapping June 29, 2001 Hollenbeck Expires December 29, 2001 [Page 31] Internet-Draft EPP Domain Name Mapping June 29, 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 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. This document requires domain and host name syntax as specified in [RFC952] as updated by [RFC1123]. These conformance requirements MAY change as a result of progressing work in developing standards for internationalized domain names. 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:domain-1.0: The namespace URI for this EPP mapping. urn:iana:xml:schema:domain-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 December 29, 2001 [Page 32] Internet-Draft EPP Domain Name Mapping June 29, 2001 8. Acknowledgements This document was originally written as an individual submission Internet-Draft. The provreg working group later adopted it as a working group document and provided many invaluable comments and suggested improvements. Hollenbeck Expires December 29, 2001 [Page 33] Internet-Draft EPP Domain Name Mapping June 29, 2001 9. References [EPP] S. Hollenbeck: "Extensible Provisioning Protocol", work in progress. [EPP-C] S. Hollenbeck: "Extensible Provisioning Protocol Contact Mapping", work in progress. [EPP-H] S. Hollenbeck: "Extensible Provisioning Protocol Host Mapping", work in progress. [IANA-XML] M. Mealling: "The IANA XML Registry", work in progress. [ISO8601] ISO 8601:1988 (E): "Data elements and interchange formats - Information interchange - Representation of dates and times - The International Organization for Standardization". [RFC952] K. Harrenstien et al.: "DOD Internet Host Table Specification", RFC 952, October 1985. [RFC1123] R. Braden: "Requirements for Internet Hosts -- Application and Support", RFC 1123, October 1989. [RFC2119] S. Bradner: "Key Words for Use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [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 December 29, 2001 [Page 34] Internet-Draft EPP Domain Name Mapping June 29, 2001 10. Author's Address Scott Hollenbeck VeriSign Global Registry Services 21345 Ridgetop Circle Dulles, VA 20166-6503 USA shollenbeck@verisign.com Hollenbeck Expires December 29, 2001 [Page 35] Internet-Draft EPP Domain Name Mapping June 29, 2001 A. Revisions From Previous Version -01 to -02: Added an Acknowledgements section. Modified namespace and schema URNs to incorporate version numbers. Added ROID return to response. Added description of to description. Hollenbeck Expires December 29, 2001 [Page 36] Internet-Draft EPP Domain Name Mapping June 29, 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 December 29, 2001 [Page 37]