Internet Engineering Task Force S. Hollenbeck Internet-Draft VeriSign, Inc. November 10, 2000 Expires: May 10, 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. XML protocol elements are case sensitive. Hollenbeck Expires May 10, 2001 [Page 1] Internet-Draft EPP Domain Name Mapping November 10, 2000 Table of Contents 1. Introduction ................................................. 3 2. Object Attributes ............................................ 4 2.1 Domain Name and Host Names .................................. 4 2.2 Client Identifiers .......................................... 4 2.3 Status Values ............................................... 4 2.4 Domain Contacts ............................................. 5 2.5 Dates and Times ............................................. 5 2.6 Authorization Identifiers ................................... 6 3. EPP Command Mapping .......................................... 7 3.1 EPP Query Commands .......................................... 7 3.1.1 EPP Command ........................................ 7 3.1.2 EPP Command ........................................ 10 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 ...................................... 22 4. Formal Syntax ................................................ 25 5. Internationalization Considerations .......................... 31 6. IANA Considerations .......................................... 31 7. Security Considerations ...................................... 31 8. References ................................................... 32 9. Author's Address ............................................. 33 10. Full Copyright Statement .................................... 34 Hollenbeck Expires May 10, 2001 [Page 2] Internet-Draft EPP Domain Name Mapping November 10, 2000 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 [XML-SD] and [XML- SS]. The referenced XML Schema documents recently progressed from Working Draft status to Candidate Recommendation status. The references to these documents and the URIs used to refer to XML Schema namespaces MUST be changed once XML parsers that support the updated specifications are available. [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. It is important to note that XML is case sensitive. XML specifications and examples provided in this document MUST be interpreted in the exact character case presented to develop a conforming implementation. This document is being discussed on the "rrp" mailing list. To join the list, send a message to with the words "subscribe rrp" in the body of the message. There is a web site for the list archives at . Hollenbeck Expires May 10, 2001 [Page 3] Internet-Draft EPP Domain Name Mapping November 10, 2000 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 Client Identifiers All EPP clients are identified by a server-unique identifier. Client identifiers use the contact identifier syntax described in [EPP-C]. 2.3 Status Values A domain name always has at least one associated status indicator. Status indicators MAY be set only by the client that sponsors a known 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. Client-Managed Status Values: CLIENT-HOLD The domain MUST NOT be published in a zone for DNS resolution. CLIENT-LOCK The domain MUST NOT be modified through any action of the EPP , , or commands, though the command MAY be used to change the status value. The command MAY be applied to avoid exceeding the end of the domain validity period. Child objects MUST NOT be added or removed. Server-Managed Status Values: NEW The domain has been delegated, can be modified, and has not been published in a zone. Hollenbeck Expires May 10, 2001 [Page 4] Internet-Draft EPP Domain Name Mapping November 10, 2000 ACTIVE The domain has been delegated, can be modified, and appears in a zone. INACTIVE The domain has not been delegated, can be modified, and does not appear in a zone. HOLD The domain MUST NOT be published in a zone for DNS resolution. LOCK The domain MUST NOT be modified through any action of the EPP , , or commands, though the command MAY be used to change the status value. The command MAY be applied to avoid exceeding the end of the domain validity period. Child objects MUST NOT be added or removed. PENDING-TRANSFER A transfer request has been received for the domain, and processing of the request is pending. PENDING-DELETE A delete request has been received for this domain. The domain has been removed from the zone, but has not yet been purged from the server database. 2.4 Domain Contacts The syntax for domain contact identifiers is described in [EPP-C]. A server MAY support a contact object service to allow contact objects to be associated with domain objects. 2.5 Dates and Times Date and time attribute values MUST be represented in Universal Coordinated Time (UTC). Both extended and truncated date and time forms defined in [ISO8601] MAY be used. Every domain name has an associated validity period. The validity period is determined when a domain object is created, and it MAY be extended by the action of the EPP and commands. If the end of the validity period is reached without explicit client Hollenbeck Expires May 10, 2001 [Page 5] Internet-Draft EPP Domain Name Mapping November 10, 2000 action to extend the period, a server MAY extend the period automatically for one additional year or it MAY place the domain on HOLD status. A domain name MUST NOT be deleted automatically upon expiration of the validity period. 2.6 Authorization Identifiers Authorization identifiers are associated with domain name objects to facilitate authorization of transfer requests. Authorization identifiers use the transaction identifier syntax described in [EPP]. Hollenbeck Expires May 10, 2001 [Page 6] Internet-Draft EPP Domain Name Mapping November 10, 2000 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 retrieve detailed information associated with a domain, to determine if a domain is known to the server, and to retrieve domain transfer status information. 3.1.1 EPP Command The EPP command is used to retrieve information associated with a domain. 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 MUST contain the following child elements: - A element that contains the fully qualified domain name for which information is requested. Example command: C: C: C: C: C: C: example.com C: C: C: C: 2000-06-08 C: ClientX C: ABC-12345-XYZ C: C: C: If the domain is known to the server, the EPP element MUST contain a child element that identifies the domain namespace and the location of the domain schema. The Hollenbeck Expires May 10, 2001 [Page 7] Internet-Draft EPP Domain Name Mapping November 10, 2000 element SHALL contain the following child elements: - A element that contains the fully qualified name of the domain. - A element that contains the identifier of the sponsoring client. - One or more elements that contain the current status descriptors associated with the domain. See the command description for a list of valid status values. - If supported by the server, one or more elements that contain identifiers for the registrant, administrative, technical, and billing contacts. - Zero or more elements that contain the fully qualified names of the name servers to which the domain is delegated. - Zero or more elements that contain the fully qualified names of the child name servers known under this parent domain. - A element that contains the identifier of the client that created the domain name. - A element that contains the date and time of domain creation. - A element that contains the date and time identifying the end of the domain's registration period. - A element that contains the identifier of the client that last updated the domain name. 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 modification. This element MUST NOT be present if the domain has never been modified. - A elements that contains the date and time of the most recent successful transfer. This element MUST NOT be provided if the domain has never been transferred. - A elements derived from either the original creation transaction or the most recent successful transfer transaction. This element MUST NOT be provided if the querying client is not the current sponsoring client. Hollenbeck Expires May 10, 2001 [Page 8] Internet-Draft EPP Domain Name Mapping November 10, 2000 Example response: S: S: S: S: S: Command completed successfully S: S: S: S: example.com S: ClientX S: ACTIVE S: SH0000 S: SH0000 S: SH0000 S: SH0000 S: ns1.example.com S: ns2.example.com S: ns1.example.com S: ns2.example.com S: ClientY S: 1999-04-03T22:00:00.0Z S: S: 2005-04-03T22:00:00.0Z S: S: ClientX S: 1999-12-03T09:00:00.0Z S: S: 2000-04-08T09:00:00.0Z S: S: S: 2000-04-08 S: ClientX S: ABC-98765-XYZ S: S: S: S: S: 2000-06-08 S: ClientX S: ABC-12345-XYZ S: S: Hollenbeck Expires May 10, 2001 [Page 9] Internet-Draft EPP Domain Name Mapping November 10, 2000 S: An EPP error response MUST be returned if an command could not be processed for any reason. 3.1.2 EPP Command The EPP command is used to determine if a domain name 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 MUST contain the following child elements: - One or more (up to a maximum of sixteen) elements that contain the fully qualified name of the queried domains. Example command: C: C: C: C: C: C: example1.com C: example2.com C: example3.com C: C: C: C: 2000-06-08 C: ClientX C: ABC-12345-XYZ C: 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 SHALL contain the following child elements: - One or more (up to a maximum of sixteen) elements that contain the fully qualified name of the queried domains and a "result" attribute whose value identifies the object as either "known" or Hollenbeck Expires May 10, 2001 [Page 10] Internet-Draft EPP Domain Name Mapping November 10, 2000 "unknown". 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: 2000-06-08 S: ClientX S: ABC-12345-XYZ S: S: S: An EPP error response MUST be returned if a command could not be processed for any reason. 3.1.3 EPP Command 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 MUST contain the following child elements: - A element that contains the fully qualified name of the domain. Hollenbeck Expires May 10, 2001 [Page 11] Internet-Draft EPP Domain Name Mapping November 10, 2000 Example query command: C: C: C: C: C: C: example.com C: C: C: 1999-06-08 C: ClientX C: ABC-98765-XYZ C: C: C: C: 2000-06-08 C: ClientX C: ABC-12345-XYZ C: C: C: When a command has been processed successfully, a server MUST respond with an EPP element that MUST contain a child element that identifies the domain namespace and the location of the domain schema. The element SHALL contain the following child elements: - A element that contains the fully qualified domain name used in the query. - A element that contains the identifier of the client that initiated the transfer request. - A element that contains the identifier of the client that SHOULD respond to the transfer request. - A element that contains the state of the most recent transfer request. Valid values are "PENDING", "APPROVED", "REJECTED", "AUTO-APPROVED", "AUTO-REJECTED", and "CANCELLED". - A element that contains the date and time that Hollenbeck Expires May 10, 2001 [Page 12] Internet-Draft EPP Domain Name Mapping November 10, 2000 the transfer was requested. - 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'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: ClientX S: ClientY S: PENDING S: S: 2000-06-06T22:00:00.0Z S: S: S: 2000-06-11T22:00:00.0Z S: S: S: 2002-09-08T22:00:00.0Z S: S: S: S: S: 2000-06-08 S: ClientX S: ABC-12345-XYZ S: S: S: Hollenbeck Expires May 10, 2001 [Page 13] Internet-Draft EPP Domain Name Mapping November 10, 2000 An EPP error response MUST be returned if a query command could not be processed for any reason. 3.2 EPP Transform Commands EPP provides five commands to transform domain object information: 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 MUST contain the following child elements: - A element that contains the fully qualified domain name of the object to be created. - An OPTIONAL element that contains the initial registration period of the domain, measured in years. If not specified, the initial registration period MUST be one year. The minimum allowable value is one (1) year. The maximum allowable value is ninety-nine (99) years. A server MAY support a lower maximum value. - Zero or more (up to a maximum of thirteen) elements that contain the fully qualified host name of a known host object to provide resolution services for the domain. A host object MUST be known to the server before a domain can be delegated to the host. A server MUST provide host object services to provide domain name services. The EPP mapping for host objects is described in [EPP-H]. - Zero or more (up to a maximum of four) elements that contain the registrant, administrative, technical, and billing contact identifiers to be associated with the domain. A contact identifier MUST be known to the server before the contact can be associated with the domain. Only one contact identifier of each type MAY be specified. A server MAY provide contact object services when providing domain name object services. The EPP mapping for contact objects is described in [EPP-C]. It is important to note that the transaction identifier associated Hollenbeck Expires May 10, 2001 [Page 14] Internet-Draft EPP Domain Name Mapping November 10, 2000 with successful creation of a domain object becomes the authorization identifier required to transfer sponsorship of the domain object. A client MUST retain all transaction identifiers associated with domain object creation and protect them from disclosure. A client MUST also provide a copy of the transaction identifier information to the domain registrant, who will need this information to request a domain transfer through a different client. Example command: C: C: C: C: C: C: example.com C: 2 C: ns1.example.com C: ns2.example.com C: SH0000 C: SH0000 C: SH0000 C: SH0000 C: C: C: C: 2000-06-08 C: ClientX C: ABC-12345-XYZ C: C: C: When a command has been processed successfully, a server MUST respond with an EPP element that MUST contain a child element that identifies the domain namespace and the location of the domain schema. The element SHALL contain the following child elements: - A element that contains the fully qualified domain name that has been created. - A element that contains the end of the domain's validity period. Hollenbeck Expires May 10, 2001 [Page 15] Internet-Draft EPP Domain Name Mapping November 10, 2000 Example response: S: S: S: S: S: Command completed successfully S: S: S: S: example.com S: S: 2002-06-08T22:00:00.0Z S: S: S: S: S: 2000-06-08 S: ClientX S: ABC-12345-XYZ S: S: S: An EPP error response MUST be returned if a command could 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 SHALL contain the following child elements: - A element that contains the fully qualified domain name of the object to be deleted. A domain name MUST NOT be deleted if the domain is associated with child name servers. For example, if domain "example.com" is known, and name server "ns1.example.com" is also known, then domain "example.com" MUST NOT be deleted until server "ns1.example.com" has been either deleted or renamed to exist in a different parent domain. Hollenbeck Expires May 10, 2001 [Page 16] Internet-Draft EPP Domain Name Mapping November 10, 2000 Example command: C: C: C: C: C: C: example.com C: C: C: C: 2000-06-08 C: ClientX C: ABC-12345-XYZ C: 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: 2000-06-08 S: ClientX S: ABC-12345-XYZ S: S: S: An EPP error response MUST be returned if a command could not be processed for any reason. 3.2.3 EPP Command Hollenbeck Expires May 10, 2001 [Page 17] Internet-Draft EPP Domain Name Mapping November 10, 2000 The EPP command provides a transform operation that allows a client to extend the validity period 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 SHALL contain the following child elements: - A element that contains the fully qualified domain name of the object whose validity period is to be extended. - A element that contains the year in which the current validity period ends. This value ensures that repeated commands do not result in multiple unanticipated successful renewals. - A element that contains the number of years to be added to the validity period of the domain. The minimum allowable value is one (1) year. The maximum allowable value is ninety-nine (99) years. A server MAY support a lower maximum value. Example command: C: C: C: C: C: C: example.com C: 2000 C: C: 5 C: C: C: C: 2000-06-08 C: ClientX C: ABC-12345-XYZ C: C: C: When a command has been processed successfully, a server MUST respond with an EPP element that MUST contain a child element that identifies the domain namespace and the location of the domain schema. The element Hollenbeck Expires May 10, 2001 [Page 18] Internet-Draft EPP Domain Name Mapping November 10, 2000 SHALL contain the following child elements: - A element that contains the fully qualified domain name whose validity period has been extended. - A element that contains the end of the domain's validity period. Example response: S: S: S: S: S: Command completed successfully S: S: S: S: example.com S: S: 2005-04-03T22:00:00.0Z S: S: S: S: S: 2000-06-08 S: ClientX S: ABC-12345-XYZ S: S: S: An EPP error response MUST be returned if a command could 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 SHALL contain the following child elements: Hollenbeck Expires May 10, 2001 [Page 19] Internet-Draft EPP Domain Name Mapping November 10, 2000 - A element that contains the fully qualified domain name of the object for which a transfer request is to be created, approved, rejected, or cancelled. - An OPTIONAL element that contains a number of years to be added to the registration period of the domain if the transfer is successful. If not specified, the registration period MUST NOT be changed as a result of the transfer. The minimum allowable value is one (1) year. The maximum allowable value is ninety-nine (99) years. A server MAY support a lower maximum value. This element MUST be consistently present or absent for all associated request, approval, rejection, or cancellation operations. 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]. Every EPP command MUST also contain an authorization identifier as described in [EPP]. It is important to note that the transaction identifier associated with successful transfer of a domain object becomes the authorization identifier required to authorize subsequent transfers of sponsorship of the domain object. A client MUST retain all transaction identifiers associated with successful domain object transfers and protect them from disclosure. A client MUST provide a copy of the transaction identifier information to the domain registrant, who will need this information to request a domain transfer through a different client. Hollenbeck Expires May 10, 2001 [Page 20] Internet-Draft EPP Domain Name Mapping November 10, 2000 Example request command: C: C: C: C: C: C: example.com C: 1 C: C: C: 1999-06-08 C: ClientX C: ABC-98765-XYZ C: C: C: C: 2000-06-08 C: ClientY C: ABC-12345-XYZ C: C: C: When a command has been processed successfully, a server MUST respond with an EPP element that MUST contain a child element that identifies the domain namespace and the location of the domain schema. The element SHALL contain the same child elements defined for a transfer query response. Hollenbeck Expires May 10, 2001 [Page 21] Internet-Draft EPP Domain Name Mapping November 10, 2000 Example response: S: S: S: S: S: Command completed successfully S: S: S: S: example.com S: ClientX S: ClientY S: PENDING S: S: 2000-06-08T22:00:00.0Z S: S: S: 2000-06-13T22:00:00.0Z S: S: S: 2002-09-08T22:00:00.0Z S: S: S: S: S: 2000-06-08 S: ClientX S: ABC-12345-XYZ S: S: S: An EPP error response MUST be returned if a command could 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 SHALL contain the following child elements: Hollenbeck Expires May 10, 2001 [Page 22] Internet-Draft EPP Domain Name Mapping November 10, 2000 - A element that contains the fully qualified domain name of the object to be updated. - An OPTIONAL element that contains attribute values to be added to the domain object. - An OPTIONAL element that contains attribute values to be removed from the domain object. Either a element or a element MUST be provided. The and elements SHALL contain the following child elements: - Zero or more elements that contain the fully qualified host 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 (up to a maximum of four) elements that contain the registrant, administrative, technical, and billing contact identifiers to be associated with the domain. A contact identifier MUST be known to the server before the contact can be associated with the domain. Only one contact identifier of each type MAY be specified. A server MAY provide contact object services when providing domain name object services. The EPP mapping for contact objects is described in [EPP-C]. - One or two elements that contain status values to be applied to or removed from the domain object. It is important to note that the maximum number of domain attribute elements is subject to the number of values currently associated with the domain object. For example, if a domain object currently has "n" server attribute elements, the maximum number of server attribute elements that can be added is 13 - "n". Likewise, the maximum number of contact elements that can be added is 4 - "n", with the added restriction that only one contact of each type (registrant, administrative, technical, or billing) MAY be associated with a domain object. Hollenbeck Expires May 10, 2001 [Page 23] Internet-Draft EPP Domain Name Mapping November 10, 2000 Example command: C: C: C: C: C: C: example.com C: C: ns1.example.com C: SH0000 C: CLIENT-HOLD C: C: C: ns2.example.com C: SH0000 C: CLIENT-LOCK C: C: C: C: C: 2000-06-08 C: ClientX C: ABC-12345-XYZ C: C: C: When an command has been processed successfully, a server MUST respond with an EPP response with no element. Hollenbeck Expires May 10, 2001 [Page 24] Internet-Draft EPP Domain Name Mapping November 10, 2000 Example response: S: S: S: S: S: Command completed successfully S: S: S: 2000-06-08 S: ClientX S: ABC-12345-XYZ S: S: S: An EPP error response MUST be returned if an command could not be processed for any reason. 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 May 10, 2001 [Page 25] Internet-Draft EPP Domain Name Mapping November 10, 2000 Hollenbeck Expires May 10, 2001 [Page 26] Internet-Draft EPP Domain Name Mapping November 10, 2000 Hollenbeck Expires May 10, 2001 [Page 27] Internet-Draft EPP Domain Name Mapping November 10, 2000 Hollenbeck Expires May 10, 2001 [Page 28] Internet-Draft EPP Domain Name Mapping November 10, 2000 Hollenbeck Expires May 10, 2001 [Page 29] Internet-Draft EPP Domain Name Mapping November 10, 2000 Hollenbeck Expires May 10, 2001 [Page 30] Internet-Draft EPP Domain Name Mapping November 10, 2000 5. Internationalization Considerations EPP is represented in XML, which provides native support for encoding information using the double-byte Unicode character set and its more compact representations including UTF-8. Compliant XML processors are required to understand both UTF-8 and raw Unicode character sets; XML also includes a provision for identifying other character sets through use of an "encoding" attribute in an processing instruction. The complete list of character set encoding identifiers is maintained by IANA and is described in [CHARSET] and [RFC1700]. All date-time values presented via EPP MUST be expressed in Universal Coordinated Time. The XML Schema "date" format allows use of time zone identifiers to indicate offsets from the zero meridian, but this option MUST NOT be used within EPP. Both extended and truncated date and time forms defined in [ISO8601] MAY be used. 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. IANA SHOULD maintain a registry of XML namespace and schema URI assignments. Per policies described in [IANA], 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. 7. Security Considerations The object mapping described in this document does not provide any security services beyond those specified by [EPP]. Hollenbeck Expires May 10, 2001 [Page 31] Internet-Draft EPP Domain Name Mapping November 10, 2000 8. References [CHARSET] ftp://ftp.isi.edu/in-notes/iana/assignments/character-sets [EPP] S. Hollenbeck: "Extensible Provisioning Protocol", draft- hollenbeck-epp-00.txt, work in progress. [EPP-C] S. Hollenbeck: "Extensible Provisioning Protocol Contact Mapping", draft-hollenbeck-epp-contact-00.txt, work in progress. [EPP-H] S. Hollenbeck: "Extensible Provisioning Protocol Host Mapping", draft-hollenbeck-epp-host-00.txt, work in progress. [IANA] T. Narten, H. Alvestrand: "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998. [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. [RFC1700] J. Reynolds, J. Postel: "Assigned Numbers", STD 2, RFC 1700, October 1994. [RFC2119] S. Bradner: "Key Words for Use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [XML] Editor T. Bray et al.: "Extensible Markup Language (XML) 1.0", http://www.w3.org/TR/REC-xml, W3C Recommendation February 1998 [XML-SD] Editors P. Biron and A. Malhotra: "XML Schema Part 2: Datatypes", http://www.w3.org/TR/xmlschema-2/, W3C Working Draft April 2000 [XML-SS] Editor H. Thompson et al.: "XML Schema Part 1: Structures", http://www.w3.org/TR/xmlschema-1/, W3C Working Draft April 2000 Hollenbeck Expires May 10, 2001 [Page 32] Internet-Draft EPP Domain Name Mapping November 10, 2000 9. Author's Address Scott Hollenbeck VeriSign Global Registry Services 21345 Ridgetop Circle Dulles, VA 20166-6503 USA shollenbeck@verisign.com Hollenbeck Expires May 10, 2001 [Page 33] Internet-Draft EPP Domain Name Mapping November 10, 2000 10. Full Copyright Statement Copyright (C) The Internet Society 2000. 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 May 10, 2001 [Page 34]