Internet Engineering Task Force S. Hollenbeck Internet-Draft VeriSign, Inc. November 10, 2000 Expires: May 10, 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 identifiers representing individuals or organizations (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. XML protocol elements are case sensitive. Hollenbeck Expires May 10, 2001 [Page 1] Internet-Draft EPP Contact Mapping November 10, 2000 Table of Contents 1. Introduction ................................................. 3 2. Object Attributes ............................................ 4 2.1 Contact and Client Identifiers .............................. 4 2.2 Individual and Organizational Names ......................... 4 2.3 Address ..................................................... 4 2.3.1 Street, City, and State or Province ....................... 4 2.3.2 Postal Code ............................................... 4 2.3.3 Country ................................................... 5 2.4 Telephone Numbers ........................................... 5 2.5 E-Mail Addresses ............................................ 5 2.6 Dates and Times ............................................. 5 2.7 Authorization Identifiers ................................... 5 3. EPP Command Mapping .......................................... 6 3.1 EPP Query Commands .......................................... 6 3.1.1 EPP Command ........................................ 6 3.1.2 EPP Command ........................................ 10 3.1.3 EPP Command .................................... 11 3.2 EPP Transform Commands ...................................... 13 3.2.1 EPP Command ...................................... 14 3.2.2 EPP Command ...................................... 16 3.2.3 EPP Command ....................................... 17 3.2.4 EPP Command .................................... 18 3.2.5 EPP Command ...................................... 20 4. Formal Syntax ................................................ 23 5. Internationalization Considerations .......................... 29 6. IANA Considerations .......................................... 29 7. Security Considerations ...................................... 29 8. References ................................................... 30 9. Author's Address ............................................. 31 10. Full Copyright Statement .................................... 32 Hollenbeck Expires May 10, 2001 [Page 2] Internet-Draft EPP Contact Mapping November 10, 2000 1. Introduction This document describes a person and organization 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 [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 Contact Mapping November 10, 2000 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 clients and contacts are identified by a server-unique identifier. Client and contact identifiers are character strings with a specified minimum length, a specified maximum length, and a specified set of characters from which these identifiers can be formed. The syntax used to represent both client and contact identifiers MUST be consistent; the contact identifier format specified in this document is consistent with the client identifier format specified in [EPP]. An EPP server MUST support contact objects to provide management facilities for client identifiers. Servers that provide only this level of support, and not support for client creation of contact objects, MUST NOT advertise contact object support in the EPP greeting and session creation process. 2.2 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. 2.3 Address Every contact has associated postal address information. A postal address contains street information, city information, OPTIONAL state/province information, a postal code, and a country identifier. 2.3.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.3.2 Postal Code Contact postal codes are represented using character strings. These strings have a specified minimum length and a specified maximum length. Hollenbeck Expires May 10, 2001 [Page 4] Internet-Draft EPP Contact Mapping November 10, 2000 2.3.3 Country Contact country identifiers are represented using two-character identifiers specified in [ISO3166]. 2.4 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. 2.5 E-Mail Addresses E-mail address syntax is defined in [RFC822]. This mapping does not prescribe minimum or maximum lengths for character strings used to represent e-mail addresses. 2.6 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. 2.7 Authorization Identifiers Authorization identifiers are associated with contact objects to facilitate authorization of transfer requests. Authorization identifiers use the transaction identifier syntax described in [EPP]. Hollenbeck Expires May 10, 2001 [Page 5] Internet-Draft EPP Contact 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 contact objects via EPP. 3.1 EPP Query Commands EPP provides three commands to retrieve contact information: to retrieve detailed information associated with a contact, to determine if a contact is known to the server, and to retrieve contact transfer status information. 3.1.1 EPP Command The EPP command is used to retrieve information associated with a contact. 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 for the queried contact. Example command: C: C: C: C: C: C: SH0000 C: C: C: C: 2000-06-08 C: ClientX C: ABC-12345-XYZ C: 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 Hollenbeck Expires May 10, 2001 [Page 6] Internet-Draft EPP Contact Mapping November 10, 2000 contact schema. The element SHALL contain the following child elements: - A element that contains the server-unique identifier for the queried contact. - A element that contains the identifier of the sponsoring client. The sponsoring client is the client that has administrative privileges to manage the object. - A element that contains the name of the individual or role represented by the contact. Each element MUST also contain a "type" attribute with a value of either "individual" (that identifies the name as belonging to an individual) or "role" (that identifies the name as belonging to an abstract entity). - A element that contains the name of the organization with which the contact is affiliated. This element is OPTIONAL. - A element that contains address information associated with the contact. A element SHALL contain the following child elements: - One or two 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. This element is OPTIONAL for addressing schemes that do not require a state or province name. - A element that contains the contact's postal code. - A element that contains the two-character identifier representing with the contact's country. - A element that contains the contact's telephone number. - A element that contain's the contacts facsimile telephone number. This element is OPTIONAL. - A element that contains the contact's e-mail address. Hollenbeck Expires May 10, 2001 [Page 7] Internet-Draft EPP Contact Mapping November 10, 2000 - A element that contains the identifier of the client that created the contact name. - A element that contains the date and time of contact creation. - A element that contains the date and time identifying the end of the contact's registration period. - A element that contains the identifier of the client that last updated the contact name. 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 modification. 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 successful transfer. This element MUST NOT be provided if the contact has never been transferred. - A element 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 Contact Mapping November 10, 2000 Example response: S: S: S: S: S: Command completed successfully S: S: S: S: SH0000 S: ClientY S: John Doe S: Example Corporation, Inc. S: S: 123 Example Dr. S: Suite 100 S: Dulles S: VA S: 20166-6503 S: US S: S: +1.7035555555 S: +1.7035555556 S: jdoe@example.com S: ClientX S: 1999-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: ClientY S: ABC-98765-XYZ S: S: S: S: S: 2000-06-08 S: ClientX S: ABC-12345-XYZ Hollenbeck Expires May 10, 2001 [Page 9] Internet-Draft EPP Contact Mapping November 10, 2000 S: S: 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 contact identifier 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 MUST contain the following child elements: - One or more (up to a maximum of sixteen) elements that contain the server-unique identifier for the queried contacts. Example command: C: C: C: C: C: C: SH0000 C: SH0001 C: SH0002 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 contact namespace and the location of the contact schema. The element SHALL contain the following child elements: Hollenbeck Expires May 10, 2001 [Page 10] Internet-Draft EPP Contact Mapping November 10, 2000 - One or more (up to a maximum of sixteen) elements that contain the server-unique identifier for the queried contacts and a "result" attribute whose value identifies the object as either "known" or "unknown". Example response: S: S: S: S: S: Command completed successfully S: S: S: S: SH0000 S: SH0001 S: SH0002 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 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 for the queried contact. Hollenbeck Expires May 10, 2001 [Page 11] Internet-Draft EPP Contact Mapping November 10, 2000 Example query command: C: C: C: C: C: C: SH0000 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 contact namespace and the location of the contact schema. The element SHALL contain the following child elements: - A element that contains the server-unique identifier for the queried contact. - 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". Hollenbeck Expires May 10, 2001 [Page 12] Internet-Draft EPP Contact Mapping November 10, 2000 - A element that contains the date and time that 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 SHALL 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: SH0000 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: S: S: 2000-06-08 S: ClientX S: ABC-12345-XYZ S: S: S: An EPP error response MUST be returned if a query command could not be processed for any reason. 3.2 EPP Transform Commands Hollenbeck Expires May 10, 2001 [Page 13] Internet-Draft EPP Contact Mapping November 10, 2000 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 SHALL contain the following child elements: - A element that contains the server-unique identifier for the contact to be created. - A element that contains the name of the individual or role represented by the contact. Each element MUST also contain a "type" attribute with a value of either "individual" (that identifies the name as belonging to an individual) or "role" (that identifies the name as belonging to an abstract entity). - A element that contains the name of the organization with which the contact is affiliated. This element is OPTIONAL. - A element that contains address information associated with the contact. A element SHALL contain the following child elements: - One or two 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. This element is OPTIONAL for addressing schemes that do not require a state or province name. - A element that contains the contact's postal code. - A element that contains the two-character identifier representing with the contact's country. - A element that contains the contact's telephone Hollenbeck Expires May 10, 2001 [Page 14] Internet-Draft EPP Contact Mapping November 10, 2000 number. - A element that contains the contact's facsimile telephone number. This element is OPTIONAL. - A element that contains the contact's e-mail address. Example command: C: C: C: C: C: C: SH0000 C: John Doe C: Example Corporation, Inc. C: C: C: 123 Example Dr. C: Suite 100 C: Dulles C: VA C: 20166-6503 C: US C: C: +1.7035555555 C: +1.7035555556 C: jdoe@example.com C: C: C: C: 2000-06-08 C: ExampleCo 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. Hollenbeck Expires May 10, 2001 [Page 15] Internet-Draft EPP Contact 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 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 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 for the contact to be deleted. A contact MUST NOT be deleted if it is associated with other known objects. Such a contact MUST NOT be deleted until the association with other known objects has been broken. Hollenbeck Expires May 10, 2001 [Page 16] Internet-Draft EPP Contact Mapping November 10, 2000 Example command: C: C: C: C: C: 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 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 Contact Mapping November 10, 2000 Renewal semantics do not apply to contact objects, so there is no mapping defined for the EPP command. 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 MUST contain the following child elements: - A element that contains the server-unique identifier for the contact for which a transfer request is to be created, approved, rejected, or cancelled. 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 contact object becomes the authorization identifier required to authorize subsequent transfers of sponsorship of the contact object. A client MUST retain all transaction identifiers associated with successful contact object transfers and protect them from disclosure. A client MUST provide a copy of the transaction identifier information to the contact registrant, who will need this information to request a contact transfer through a different client. Hollenbeck Expires May 10, 2001 [Page 18] Internet-Draft EPP Contact Mapping November 10, 2000 Example request command: C: C: C: C: C: C: SH0000 C: C: C: 1999-06-08 C: ClientY 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 contact namespace and the location of the contact schema. The element SHALL contain the same child elements defined for a transfer query response. Hollenbeck Expires May 10, 2001 [Page 19] Internet-Draft EPP Contact Mapping November 10, 2000 Example response: S: S: S: S: S: Command completed successfully S: S: S: S: SH0000 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: 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 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 SHALL contain the following child elements: - A element that contains the server-unique identifier for the contact to be updated. Hollenbeck Expires May 10, 2001 [Page 20] Internet-Draft EPP Contact Mapping November 10, 2000 The element SHALL contain at least one of the following child elements: - A element that contains content object attribute values to be added or changed. A element SHALL contain at least one of the following child elements: - A element that contains the name of the individual or role represented by the contact. Each element MUST also contain a "type" attribute with a value of either "individual" (that identifies the name as belonging to an individual) or "role" (that identifies the name as belonging to an abstract entity). - A element that contains the name of the organization with which the contact is affiliated. This element is OPTIONAL. - A element that contains address information associated with the contact. A element SHALL contain the following child elements: - One or two elements that contain the contact's street address. - A element that contains the contact's city. - A element that identifies the contact's state, province, or other local identifier. This element is OPTIONAL for addressing schemes that do not require a state or province name. - A element that contains the contact's postal code. - A element that contains the two-character identifier representing with the contact's country. - A element that contains the contact's telephone number. - A element that contain's the contacts facsimile telephone number. This element is OPTIONAL. - A element that contains the contact's e-mail address. - A element that identifies OPTIONAL elements to be removed from the content object. A element SHALL contain at least one of the following child elements: Hollenbeck Expires May 10, 2001 [Page 21] Internet-Draft EPP Contact Mapping November 10, 2000 - A element that contains the name of the organization to be removed. - A element that contain's the facsimile telephone number to be removed. Example command: C: C: C: C: C: C: SH0000 C: C: John Doe C: Example Corporation, Inc. C: C: 124 Example Dr. C: Suite 200 C: Dulles C: VA C: 20166-6503 C: US C: C: +1.7034444444 C: jdoe@example.com C: C: C: +1.7035555556 C: C: C: C: C: 2000-06-08 C: ExampleCo 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 22] Internet-Draft EPP Contact 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 contact provisioning schema. Hollenbeck Expires May 10, 2001 [Page 23] Internet-Draft EPP Contact Mapping November 10, 2000 Hollenbeck Expires May 10, 2001 [Page 24] Internet-Draft EPP Contact Mapping November 10, 2000 Hollenbeck Expires May 10, 2001 [Page 27] Internet-Draft EPP Contact Mapping November 10, 2000 Hollenbeck Expires May 10, 2001 [Page 28] Internet-Draft EPP Contact 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. 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 29] Internet-Draft EPP Contact Mapping November 10, 2000 8. References [CHARSET] ftp://ftp.isi.edu/in-notes/iana/assignments/character-sets [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", draft- hollenbeck-epp-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. [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 - The International Organization for Standardization". [RFC822] D. Crocker: "Standard for the Format Of ARPA Internet Text Messages", RFC 822, August 1982. [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 30] Internet-Draft EPP Contact 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 31] Internet-Draft EPP Contact 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 32]