Internet Engineering Task Force S. Hollenbeck Internet-Draft VeriSign, Inc. June 29, 2001 Expires: December 29, 2001 Extensible Provisioning Protocol Contact 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 individual or organizational social information identifiers (known as "contacts") stored in a shared central repository. Specified in XML, the mapping defines EPP command syntax and semantics as applied to contacts. 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 Contact mapping June 29, 2001 Table of Contents 1. Introduction ................................................. 3 2. Object Attributes ............................................ 4 2.1 Contact and Client Identifiers .............................. 4 2.2 Status Values ............................................... 4 2.3 Individual and Organizational Names ......................... 5 2.4 Address ..................................................... 5 2.4.1 Street, City, and State or Province ....................... 6 2.4.2 Postal Code ............................................... 6 2.4.3 Country ................................................... 6 2.5 Telephone Numbers ........................................... 6 2.6 E-Mail Addresses ............................................ 6 2.7 Dates and Times ............................................. 6 2.8 Authorization Information ................................... 6 3. EPP Command mapping .......................................... 8 3.1 EPP Query Commands .......................................... 8 3.1.1 EPP Command ....................................... 8 3.1.2 EPP Command ........................................ 9 3.1.3 EPP Command .................................... 14 3.2 EPP Transform Commands ...................................... 16 3.2.1 EPP Command ...................................... 16 3.2.2 EPP Command ...................................... 19 3.2.3 EPP Command ....................................... 20 3.2.4 EPP Command .................................... 21 3.2.5 EPP Command ...................................... 22 4. Formal Syntax ................................................ 27 5. Internationalization Considerations .......................... 34 6. IANA Considerations .......................................... 34 7. Security Considerations ...................................... 34 8. Acknowledgements ............................................. 35 9. References ................................................... 36 10. Author's Address ............................................ 37 A. Revisions From Previous Version .............................. 38 B. Full Copyright Statement ..................................... 39 Hollenbeck Expires December 29, 2001 [Page 2] Internet-Draft EPP Contact mapping June 29, 2001 1. Introduction This document describes a personal and organizational identifier 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 Contact mapping June 29, 2001 2. Object Attributes An EPP contact 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. The formal syntax for the attribute values described here can be found in the "Formal Syntax" section of this document. 2.1 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.2 Status Values A contact object MUST always have at least one associated status value. Status values MAY be set only by the client that sponsors a contact object and by the server on which the object resides. A client MAY change the status of a contact 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. clientTransferProhibited, serverTransferProhibited Requests to transfer the object MUST be rejected. clientUpdateProhibited, serverUpdateProhibited Requests to update the object (other than to remove this status) MUST Hollenbeck Expires December 29, 2001 [Page 4] Internet-Draft EPP Contact mapping June 29, 2001 be rejected. linked The contact object has at least one active association with another object, such as a domain object. Servers SHOULD provide services to determine existing object associations. 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. "ok" status MAY only be combined with "linked" status. "linked" status MAY be combined with any 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.3 Individual and Organizational Names Individual and organizational names associated with a contact are represented using character strings. These strings have a specified minimum length and a specified maximum length. Individual and organizational names MAY be provided in both a subset of UTF-8 [RFC2279] that can be represented in 7-bit ASCII [US-ASCII] and unrestricted UTF-8. 2.4 Address Every contact has associated postal address information. A postal address contains street information, city information, OPTIONAL state/province information, an OPTIONAL postal code, and a country identifier as described in [ISO11180]. Address information MAY be provided in both a subset of UTF-8 [RFC2279] that can be represented Hollenbeck Expires December 29, 2001 [Page 5] Internet-Draft EPP Contact mapping June 29, 2001 in 7-bit ASCII [US-ASCII] and unrestricted UTF-8. Address elements MUST be exchanged in the order described in the protocol schema, but display order MAY be altered to reflect local preferences. 2.4.1 Street, City, and State or Province Contact street, city, and state or province information is represented using character strings. These strings have a specified minimum length and a specified maximum length. 2.4.2 Postal Code Contact postal codes are represented using character strings. These strings have a specified minimum length and a specified maximum length. 2.4.3 Country Contact country identifiers are represented using two-character identifiers specified in [ISO3166]. 2.5 Telephone Numbers Contact telephone number structure requirements are defined in [E164a]. Telephone numbers described in this mapping are character strings that MUST begin with a plus sign ("+", ASCII value 0x002B), followed by a country code defined in [E164b], followed by a dot (".", ASCII value 0x002E), followed by a sequence of digits representing the telephone number. An optional "x" attribute is provided to note telephone extension information. 2.6 E-Mail Addresses E-mail address syntax is defined in [RFC2822]. This mapping does not prescribe minimum or maximum lengths for character strings used to represent e-mail addresses. 2.7 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.8 Authorization Information Authorization information is associated with domain objects to facilitate transfer operations. Authorization information is assigned Hollenbeck Expires December 29, 2001 [Page 6] Internet-Draft EPP Contact mapping June 29, 2001 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 7] Internet-Draft EPP Contact 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 contact objects via EPP. 3.1 EPP Query Commands EPP provides three commands to retrieve contact information: to determine if a contact object is known to the server, to retrieve detailed information associated with a contact object, and to retrieve contact object transfer status information. 3.1.1 EPP Command The EPP command is used to determine if a contact object is known to the server. In addition to the standard EPP command elements, the command MUST contain a element that identifies the contact namespace and the location of the contact schema. The element contains the following child elements: - One or more elements that contain the server-unique identifier of the contact objects to be queried. Example command: C: C: C: C: C: C: sh8013 C: sah8013 C: 8013sah 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 8] Internet-Draft EPP Contact mapping June 29, 2001 identifies the contact namespace and the location of the contact schema. The element contains the following child elements: - One or more elements that contain the repository object identifier for the queried contact 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: sh8013 S: sah8013 S: 8013sah 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 contact object. In addition to the standard EPP command elements, the command MUST contain a element that identifies the contact namespace and the location of the contact schema. The element contains the following child elements: Hollenbeck Expires December 29, 2001 [Page 9] Internet-Draft EPP Contact mapping June 29, 2001 - A element that contains the server-unique identifier of the contact object to be queried. Example command: C: C: C: C: C: C: sh8013 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 contact namespace and the location of the contact schema. The element contains the following child elements: - A element that contains the server-unique identifier of the contact object. - A element that contains the Repository Object IDentifier assigned to the contact object when the object was created. - One or more elements that describe the status of the contact object. - A element that contains child elements whose content MUST be represented in a subset of UTF-8 that can be represented in the 7-bit US-ASCII character set. - An OPTIONAL ("i15d" is short for "internationalized") element that contains child elements whose content MAY be represented in unrestricted UTF-8. The and elements contain the following child elements: - A element that contains the name of the individual or role represented by the contact. Hollenbeck Expires December 29, 2001 [Page 10] Internet-Draft EPP Contact mapping June 29, 2001 - An OPTIONAL element that contains the name of the organization with which the contact is affiliated. - A element that contains address information associated with the contact. A element contains the following child elements: - One, two, or three elements that contain the contact's street address. - A element that contains the contact's city. - An OPTIONAL element that contains the contact's state or province. - An OPTIONAL element that contains the contact's postal code. - A element that contains the contact's country code. - An OPTIONAL element that contains the contact's voice telephone number. - An OPTIONAL element that contains the contact's facsimile telephone number. - A element that contains the contact's e-mail address. - A element that contains the identifier of the sponsoring client. - A element that contains the identifier of the client that created the contact object. - A element that contains the date and time of contact object creation. - A element that contains the identifier of the client that last updated the contact object. This element MUST NOT be present if the contact has never been modified. - A element that contains the date and time of the most recent contact object modification. This element MUST NOT be present if the contact object has never been modified. - A elements that contains the date and time of the most recent successful contact object transfer. This element MUST NOT Hollenbeck Expires December 29, 2001 [Page 11] Internet-Draft EPP Contact mapping June 29, 2001 be provided if the contact object has never been transferred. - A element that contains authorization information associated with the contact object. This element MUST NOT be provided if the querying client is not the current sponsoring client. Hollenbeck Expires December 29, 2001 [Page 12] Internet-Draft EPP Contact mapping June 29, 2001 Example response: S: S: S: S: S: Command completed successfully S: S: S: S: sh8013 S: SH8013-VRSN S: S: S: S: John Doe S: Example Inc. S: S: 123 Example Dr. S: Suite 100 S: Dulles S: VA S: 20166-6503 S: US S: S: S: +1.7035555555 S: +1.7035555556 S: jdoe@example.com S: ClientY S: ClientX S: 1999-04-03T22:00:00.0Z S: ClientX S: 1999-12-03T09:00:00.0Z S: 2000-04-08T09:00:00.0Z S: 2fooBAR S: S: S: S: S: ABC-12346 S: 54322-XYZ S: Hollenbeck Expires December 29, 2001 [Page 13] Internet-Draft EPP Contact mapping June 29, 2001 S: S: An EPP error response MUST be returned if an command can 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 contact namespace and the location of the contact schema. The element MUST contain the following child elements: - A element that contains the server-unique identifier of the contact object to be queried. Example query command: C: C: C: C: C: C: sh8013 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 contact namespace and the location of the contact schema. The element contains the following child elements: - A element that contains the server-unique identifier for the queried contact. - A element that contains the state of the most Hollenbeck Expires December 29, 2001 [Page 14] Internet-Draft EPP Contact mapping June 29, 2001 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. - 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 SHOULD be taken by the server. For all other status types, the value identifies the date and time when the request was completed. Example query response: S: S: S: S: S: Command completed successfully S: S: S: S: sh8013 S: pending S: ClientX S: 2000-06-06T22:00:00.0Z S: ClientY S: 2000-06-11T22:00:00.0Z S: S: S: S: S: ABC-12346 S: 54322-XYZ S: S: S: Hollenbeck Expires December 29, 2001 [Page 15] Internet-Draft EPP Contact mapping June 29, 2001 An EPP error response MUST be returned if a query command can not be processed for any reason. 3.2 EPP Transform Commands EPP provides four commands to transform contact object information: to create an instance of a contact object, to delete an instance of a contact object, to manage contact object sponsorship changes, and to change information associated with a contact object. This document does not define a mapping for the EPP command. 3.2.1 EPP Command The EPP command provides a transform operation that allows a client to create a contact object. In addition to the standard EPP command elements, the command MUST contain a element that identifies the contact namespace and the location of the contact schema. The element contains the following child elements: - A element that contains the desired server-unique identifier for the contact to be created. - A element that contains child elements whose content MUST be represented in a subset of UTF-8 that can be represented in the 7-bit US-ASCII character set. - An OPTIONAL ("i15d" is short for "internationalized") element that contains child elements whose content MAY be represented in unrestricted UTF-8. The and elements contain the following child elements: - A element that contains the name of the individual or role represented by the contact. - An OPTIONAL element that contains the name of the organization with which the contact is affiliated. - A element that contains address information associated with the contact. A element contains the following child elements: - One, two, or three elements that contain the contact's street address. - A element that contains the contact's city. Hollenbeck Expires December 29, 2001 [Page 16] Internet-Draft EPP Contact mapping June 29, 2001 - An OPTIONAL element that contains the contact's state or province. - An OPTIONAL element that contains the contact's postal code. - A element that contains the contact's country code. - An OPTIONAL element that contains the contact's voice telephone number. - An OPTIONAL element that contains the contact's facsimile telephone number. - A element that contains the contact's e-mail address. - A element that contains authorization information to be associated with the contact object. Hollenbeck Expires December 29, 2001 [Page 17] Internet-Draft EPP Contact mapping June 29, 2001 Example command: C: C: C: C: C: C: sh8013 C: C: John Doe C: Example Inc. C: C: 123 Example Dr. C: Suite 100 C: Dulles C: VA C: 20166-6503 C: US C: C: C: +1.7035555555 C: +1.7035555556 C: jdoe@example.com 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 contact namespace and the location of the contact schema. The element contains the following child elements: - A element that contains the server-unique identifier for the created contact. Hollenbeck Expires December 29, 2001 [Page 18] Internet-Draft EPP Contact mapping June 29, 2001 Example response: S: S: S: S: S: Command completed successfully S: S: S: S: sh8013 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 contact object. In addition to the standard EPP command elements, the command MUST contain a element that identifies the contact namespace and the location of the contact schema. The element MUST contain the following child elements: - A element that contains the server-unique identifier of the contact object to be deleted. A contact object SHOULD NOT be deleted if it is associated with other known objects. An associated contact SHOULD NOT be deleted until associations with other known objects have been broken. Hollenbeck Expires December 29, 2001 [Page 19] Internet-Draft EPP Contact mapping June 29, 2001 Example command: C: C: C: C: C: C: sh8013 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 Renewal semantics do not apply to contact objects, so there is no mapping defined for the EPP command. Hollenbeck Expires December 29, 2001 [Page 20] Internet-Draft EPP Contact mapping June 29, 2001 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 contact object. In addition to the standard EPP command elements, the command MUST contain a element that identifies the contact namespace and the location of the contact schema. The element contains the following child elements: - A element that contains the server-unique identifier of the contact object for which a transfer request is to be created, approved, rejected, or cancelled. - A element that contains authorization information associated with the contact object. 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 as defined in [EPP]. Example request command: C: C: C: C: C: C: sh8013 C: 2fooBAR 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 contact namespace and the location of the contact schema. The element contains the same child elements defined for a transfer query response. Hollenbeck Expires December 29, 2001 [Page 21] Internet-Draft EPP Contact mapping June 29, 2001 Example response: S: S: S: S: S: Command completed successfully S: S: S: S: sh8013 S: pending S: ClientX S: 2000-06-08T22:00:00.0Z S: ClientY S: 2000-06-13T22: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 contact object. In addition to the standard EPP command elements, the command MUST contain a element that identifies the contact namespace and the location of the contact schema. The element contains the following child elements: - A element that contains the server-unique identifier of the contact object to be updated. - An OPTIONAL element that contains attribute values to be added to the object. Hollenbeck Expires December 29, 2001 [Page 22] Internet-Draft EPP Contact mapping June 29, 2001 - 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: - One or more elements that contain status values to be associated with 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 OPTIONAL child elements. At least one child element MUST be present: - A element that contains child elements whose content MUST be represented in a subset of UTF-8 that can be represented in the 7-bit US-ASCII character set. - A ("i15d" is short for "internationalized") element that contains child elements whose content MAY be represented in unrestricted UTF-8. The and elements contain the following OPTIONAL child elements: - A element that contains the name of the individual or role represented by the contact. - A element that contains the name of the organization with which the contact is affiliated. - A element that contains address information associated with the contact. A element contains the following OPTIONAL child elements: - One, two, or three elements that contain the contact's street address. - A element that contains the contact's city. - A element that contains the contact's state or province. - A element that contains the contact's postal code. - A element that contains the contact's country code. Hollenbeck Expires December 29, 2001 [Page 23] Internet-Draft EPP Contact mapping June 29, 2001 - A element that contains the contact's voice telephone number. - A element that contains the contact's facsimile telephone number. - A element that contains the contact's e-mail address. - A element that contains authorization information associated with the contact object. Hollenbeck Expires December 29, 2001 [Page 24] Internet-Draft EPP Contact mapping June 29, 2001 Example command: C: C: C: C: C: C: sh8013 C: C: C: C: C: C: C: C: 124 Example Dr. C: Suite 200 C: Dulles C: VA C: 20166-6503 C: US C: C: C: +1.7034444444 C: 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 25] Internet-Draft EPP Contact 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 26] Internet-Draft EPP Contact 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 contact provisioning schema. Hollenbeck Expires December 29, 2001 [Page 27] Internet-Draft EPP Contact mapping June 29, 2001 Hollenbeck Expires December 29, 2001 [Page 28] Internet-Draft EPP Contact mapping June 29, 2001 Hollenbeck Expires December 29, 2001 [Page 29] Internet-Draft EPP Contact mapping June 29, 2001 Hollenbeck Expires December 29, 2001 [Page 31] Internet-Draft EPP Contact mapping June 29, 2001 Hollenbeck Expires December 29, 2001 [Page 32] Internet-Draft EPP Contact mapping June 29, 2001 Hollenbeck Expires December 29, 2001 [Page 33] Internet-Draft EPP Contact 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. Humans, organizations, and other entities often need to represent social information in both a commonly understood character set and a locally optimized character set. This specification provides features allowing representation of social information in both a subset of UTF-8 for broad readability and unrestricted UTF-8 for local optimization. 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:contact-1.0: The namespace URI for this EPP mapping. urn:iana:xml:schema:contact-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 34] Internet-Draft EPP Contact 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 35] Internet-Draft EPP Contact mapping June 29, 2001 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. [IANA-XML] M. Mealling: "The IANA XML Registry", work in progress. [ISO3166] ISO 3166-1: "Codes for the representation of names of countries and their subdivisions - Part 1: Country codes", October 1997. [ISO8601] ISO 8601:1988 (E): "Data elements and interchange formats - Information interchange - Representation of dates and times", June 1988. [ISO11180] ISO 11180:1993 (E): "Postal addressing", March 1993. [RFC2119] S. Bradner: "Key Words for Use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2279] F. Yergeau: "UTF-8, a transformation format of ISO 10646", RFC 2279, January 1998. [RFC2822] P. Resnick: "Internet Message Format", RFC 2822, April 2001. [US-ASCII] Coded Character Set -- 7-bit American Standard Code for Information Interchange, ANSI X3.4-1986; also: ISO/IEC 646 (IRV). [XML] Editor 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 36] Internet-Draft EPP Contact 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 37] Internet-Draft EPP Contact 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 38] Internet-Draft EPP Contact 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 39]