Network Working Group F. Neves Internet-Draft H. Kobayashi Intended status: Informational Registro.br Expires: July 5, 2009 January 2009 Autonomous System Number Mapping for the Extensible Provisioning Protocol (EPP) draft-neves-epp-asn-00.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. 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. This Internet-Draft will expire on July 5, 2009. Abstract This document describes an Extensible Provisioning Protocol (EPP) mapping for the provisioning and management of Autonomous Systems Numbers stored in a shared central repository. Specified in XML, this mapping defines EPP command syntax and semantics as applied to Autonomous Systems. Neves & Kobayashi Expires July 5, 2009 [Page 1] Internet-Draft EPP ASN Mapping January 2009 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Conventions Used In This Document . . . . . . . . . . . . 3 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Autonomous System Number (ASN) . . . . . . . . . . . . . . 3 2.2. Organization Identifier . . . . . . . . . . . . . . . . . 3 2.3. Contact Identifiers . . . . . . . . . . . . . . . . . . . 4 2.4. Validity Periods . . . . . . . . . . . . . . . . . . . . . 4 3. EPP command mapping . . . . . . . . . . . . . . . . . . . . . 4 3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . . 4 3.1.1. EPP Command . . . . . . . . . . . . . . . . . 4 3.1.2. EPP Command . . . . . . . . . . . . . . . . . . 6 3.1.3. EPP Command . . . . . . . . . . . . . . . . 9 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . . 10 3.2.1. EPP Command . . . . . . . . . . . . . . . . . 11 3.2.2. EPP Command . . . . . . . . . . . . . . . . . 13 3.2.3. EPP Command . . . . . . . . . . . . . . . . . 14 3.2.4. EPP Command . . . . . . . . . . . . . . . . 16 3.2.5. EPP Command . . . . . . . . . . . . . . . . . 18 3.3. Offline Review of Requested Actions . . . . . . . . . . . 20 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 20 5. Internationalization Considerations . . . . . . . . . . . . . 26 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 7. Security Considerations . . . . . . . . . . . . . . . . . . . 27 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 27 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 28 9.1. Normative References . . . . . . . . . . . . . . . . . . . 28 9.2. Informative References . . . . . . . . . . . . . . . . . . 28 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 29 Intellectual Property and Copyright Statements . . . . . . . . . . 30 Neves & Kobayashi Expires July 5, 2009 [Page 2] Internet-Draft EPP ASN Mapping January 2009 1. Introduction This document describes an Autonomous System 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 [W3C.REC-xml-20040204], and XML Schema notation, as described in [W3C.REC-xmlschema-1-20041028] and [W3C.REC-xmlschema-2-20041028]. The EPP core protocol specification [RFC4930] 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. 1.1. 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 and white spaces in examples is provided only to ilustrate element relationships and is not a REQUIRED feature of this protocol. 2. Object Attributes 2.1. Autonomous System Number (ASN) The syntax for Autonomous System Numbers described in this document MUST conform to [I-D.ietf-idr-as-representation]. 2.2. Organization Identifier Organization identifiers are unique internal or external to the repository identifiers represented by character strings with a specified minimum length, and a specified maximum length. Organization identifiers use the "orgIDType" syntax described in [I-D.neves-epp-brorg]. Neves & Kobayashi Expires July 5, 2009 [Page 3] Internet-Draft EPP ASN Mapping January 2009 2.3. Contact 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 [RFC4930]. 2.4. Validity Periods An Autonomous System Number MAY have a specified validity period. If server policy supports ASN validity periods, the validity period is defined when an ASN object is created, and it MAY be extended by the EPP command. As a matter of server policy, this specification does not define actions to be taken upon expiration of an ASN object's validity period. Validity periods are measured in years or months with the appropriate units specified using the "unit" attribute. Valid values for the "unit" attribute are "y" for years and "m" for months. The minimum allowable period value is one (1). The maximum allowable value is ninety-nine decimal (99). A server MAY support a lower maximum value. 3. EPP command mapping A detailed description of the EPP syntax and semantics can be found in [RFC4930]. The command mappings described here are specifically for use in provisioning and managing Autonomous System Numbers via EPP. 3.1. EPP Query Commands EPP provides three commands to retrieve domain information: to determine if a domain object can be provisioned within a repository, to retrieve detailed information associated with a domain object, and to retrieve domain object transfer status information. 3.1.1. EPP Command The EPP command is used to determine if an object can be provisioned within a repository. It provides a hint that allows a client to anticipate the success or failure of provisioning an object using the command as object provisioning requirements are ultimately a matter of server policy. Neves & Kobayashi Expires July 5, 2009 [Page 4] Internet-Draft EPP ASN Mapping January 2009 In addition to the standard EPP command elements, the command MUST contain an element that identifies the AS namespace. The element contains the following child elements: - One or more elements that contain the textual representation of the AS object (ASN) to be queried. Example command: C: C: C: C: C: C: 64500 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 AS namespace and the location of the AS schema. The element contains one or more elements that contain the following child elements: - An element that contains the textual representation of the queried AS object. This element MUST contain an "avail" attribute whose value indicates object availability (can it be provisioned or not) at the moment the command was completed. A value of "1" or "true" means that the object can be provisioned. A value of "0" or "false" means that the object cannot be provisioned. - An OPTIONAL element that MAY be provided when an object cannot be provisioned. If present, this element contains server-specific text to help explain why the object can not be provisioned. This text MUST be represented in the response language previously negotiated with the client; an OPTIONAL "lang" attribute MAY be present to identify the language if the negotiated value is something other than the default value of "en" (English). Neves & Kobayashi Expires July 5, 2009 [Page 5] Internet-Draft EPP ASN Mapping January 2009 Example response: S: S: S: S: S: Command completed successfully S: S: S: S: S: 64500 S: In use S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: An EPP error response MUST be returned if a command cannot be processed for any reason. 3.1.2. EPP Command The EPP command is used to retrieve information associated with an AS object. In addition to the standard EPP command elements, the command MUST contain an element that identifies the AS namespace. The element contains the following child elements: - An element that contains the textual representation of the AS object to be queried. Neves & Kobayashi Expires July 5, 2009 [Page 6] Internet-Draft EPP ASN Mapping January 2009 Example command: C: C: C: C: C: C: 64500 C: C: C: ABC-12345 C: C: When an command has been processed successfully, the EPP element MUST contain a child element that identifies the AS namespace. The element contains the following child elements: - An element that contains the textual representation of the queried AS object (ASN). - An element that contains the Repository Object IDentifier assigned to the AS object when the it was created. - An element that contains the identifier for the organization object associated with the AS object as the AS manager. The EPP mapping for organization objects is described in [I-D.neves-epp-brorg]. - One or more elements that contain the identifiers for contact objects associated with the AS object. - A element that contains the identifier of the sponsoring client. - An OPTIONAL element that contains the identifier of the client that created the AS object. - An OPTIONAL element that contains the date and time of AS object creation. - An OPTIONAL element that contains the date and time identifying the end of the AS object registration period. Neves & Kobayashi Expires July 5, 2009 [Page 7] Internet-Draft EPP ASN Mapping January 2009 - An OPTIONAL element that contains the identifier of the client that last updated the AS object. This element MUST NOT be present if the AS has never been modified. - An OPTIONAL element that contains the date and time of the most recent AS object modification. This element MUST NOT be present if the AS object has never been modified. - An OPTIONAL element that contains the date and time of the most recent successful AS object transfer. This element MUST NOT be provided if the AS object has never been transferred. Example response: S: S: S: S: S: Command completed successfully S: S: S: S: 64500 S: 64500-REP S: BR-ABCD-LACNIC S: fan S: hkk S: ClientY S: ClientX S: 1999-04-03T22:00:00.0Z S: ClientX S: 2005-12-03T09:00:00.0Z S: 2004-04-08T09:00:00.0Z S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: An EPP error response MUST be returned if an command cannot be processed for any reason. Neves & Kobayashi Expires July 5, 2009 [Page 8] Internet-Draft EPP ASN Mapping January 2009 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 an element that identifies the AS namespace. The element MUST contain the following child elements: - An element that contains the textual representation of the AS object to be queried. Example query command: C: C: C: C: C: C: 64500 C: C: C: ABC-12345 C: C: When a query command has been processed successfully, the EPP element MUST contain a child element that identifies the AS namespace. The element contains the following child elements: - An element that contains the textual representation for the queried AS object. - An element that contains the state of the most recent transfer request. - An element that contains the identifier of the client that requested the object transfer. - An element that contains the date and time that the transfer was requested. Neves & Kobayashi Expires July 5, 2009 [Page 9] Internet-Draft EPP ASN Mapping January 2009 - An element that contains the identifier of the client that SHOULD act upon a pending 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 will 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: 64500 S: pending S: ClientX S: 2000-06-06T22:00:00.0Z S: ClientY S: 2000-06-11T22:00:00.0Z S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: An EPP error response MUST be returned if a query command cannot be processed for any reason. 3.2. EPP Transform Commands EPP provides five commands to transform AS objects: to create an instance of an AS object, to delete an instance of an AS object, to extend the validity period of an AS object, to manage AS object sponsorship changes, and to change information associated with an AS object. Transform commands are typically processed and completed in real Neves & Kobayashi Expires July 5, 2009 [Page 10] Internet-Draft EPP ASN Mapping January 2009 time. Server operators MAY receive and process transform commands, but defer completing the requested action if human or third-party review is required before the requested action can be completed. In such situations the server MUST return a 1001 response code to the client to note that the command has been received and processed, but the requested action is pending. The server MUST also manage the status of the object that is the subject of the command to reflect the initiation and completion of the requested action. Once the action has been completed, all clients involved in the transaction MUST be notified using a service message that the action has been completed and that the status of the object has changed. 3.2.1. EPP Command The EPP command provides a transform operation that allows a client to create an AS object. In addition to the standard EPP command elements, the command MUST contain an element that identifies the AS namespace. The element contains the following child elements: - An element that contains the textual representation of the Autonomous System object to be created. - An element that contains the identifier for the organization object to be associated with the AS object as the AS manager. This identifier MUST be known to the server before the AS object can be associated with this organization object. The EPP mapping for organization objects is described in [I-D.neves-epp-brorg]. - One or more elements that contain the identifiers for contact objects to be associated with the AS object. Contact object identifiers MUST be known to the server before the contact object can be associated with the AS object. Neves & Kobayashi Expires July 5, 2009 [Page 11] Internet-Draft EPP ASN Mapping January 2009 Example command: C: C: C: C: C: C: 64500 C: BR-ABCD-LACNIC C: fan C: hkk 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 AS namespace. The element contains the following child elements: - An element that contains the textual representation of the created AS. - An element that contains the Repository Object IDentifier assigned to the AS object. - An element that contains the date and time of AS object creation. - An OPTIONAL element that contains the date and time identifying the end of the AS object's registration period. Neves & Kobayashi Expires July 5, 2009 [Page 12] Internet-Draft EPP ASN Mapping January 2009 Example response: S: S: S: S: S: Command completed successfully S: S: S: S: 64500 S: 64500-REP S: 1999-04-03T22:00:00.0Z S: S: S: S: ABC-12345 S: 54321-XYZ S: S: S: An EPP error response MUST be returned if a command cannot be processed for any reason. 3.2.2. EPP Command The EPP command provides a transform operation that allows a client to delete an AS object. In addition to the standard EPP command elements, the command MUST contain an element that identifies the AS namespace. The element MUST contain the following child element: - A element that contains the textual representation of the AS object (ASN) to be deleted. Neves & Kobayashi Expires July 5, 2009 [Page 13] Internet-Draft EPP ASN Mapping January 2009 Example command: C: C: C: C: C: C: 64500 C: C: C: ABC-12345 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: ABC-12345 S: 54321-XYZ S: S: S: An EPP error response MUST be returned if a command cannot be processed for any reason. 3.2.3. EPP Command The EPP command provides a transform operation that allows a client to extend the validity period of an AS object. In addition to the standard EPP command elements, the command MUST contain an element that identifies the AS namespace. The element contains the following child elements: Neves & Kobayashi Expires July 5, 2009 [Page 14] Internet-Draft EPP ASN Mapping January 2009 - An element that contains the textual representation of the AS object (ASN) whose validity period is to be extended. - An element that contains the date on which the current validity period ends. This value ensures that repeated commands do not result in multiple unanticipated successful renewals. - An OPTIONAL element that contains the number of units to be added to the registration period of the AS object. The number of units available MAY be subject to limits imposed by the server. Example command: C: C: C: C: C: C: 64500 C: 2008-04-03T00:00:00.0Z C: 3 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 AS namespace. The element contains the following child elements: - A element that contains the textual representation of the AS object (ASN). - An OPTIONAL element that contains the date and time identifying the end of the AS object's registration period. Neves & Kobayashi Expires July 5, 2009 [Page 15] Internet-Draft EPP ASN Mapping January 2009 Example response: S: S: S: S: S: Command completed successfully S: S: S: S: 64500 S: 2011-04-03T00:00:00.0Z S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: An EPP error response MUST be returned if a command cannot 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 an AS object. In addition to the standard EPP command elements, the command MUST contain an element that identifies the AS namespace. The element contains the following child elements: - An element that contains the textual representation of the AS object (ASN) 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 [RFC4930]. Neves & Kobayashi Expires July 5, 2009 [Page 16] Internet-Draft EPP ASN Mapping January 2009 Example command: C: C: C: C: C: C: 64500 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 AS namespace. The element contains the same child elements defined for a transfer query response. Example response: S: S: S: S: S: Command completed successfully S: S: S: S: 64500 S: pending S: ClientX S: 2000-06-08T22:00:00.0Z S: ClientY S: 2000-06-13T22:00:00.0Z S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: An EPP error response MUST be returned if a command cannot be processed for any reason. Neves & Kobayashi Expires July 5, 2009 [Page 17] Internet-Draft EPP ASN Mapping January 2009 3.2.5. EPP Command The EPP command provides a transform operation that allows a client to modify the attributes of an AS object. In addition to the standard EPP command elements, the update command MUST contain an element that identifies the AS namespace and the location of the AS schema. The element contains the following child elements: - An element that contains the textual representation of the AS object (ASN) to be updated. - An OPTIONAL element that contains attribute values to be added to the object. - An OPTIONAL element that contains attribute values to be removed from the object. - An OPTIONAL element that contains object attribute values to be changed. At least one , , or element MUST be provided. The and elements contain the following child elements: - Zero or more elements that contain the identifiers for contact objects to be associated with or removed from the AS object. Contact object identifiers MUST be known to the server before the contact object can be associated with the AS object. A element contains the following child element: - A element that contains the identifier for the organization object to be associated with the AS object as the AS manager. This identifier MUST be known to the server before the AS object can be associated with this organization object. The EPP mapping for organization objects is described in [I-D.neves-epp-brorg]. Neves & Kobayashi Expires July 5, 2009 [Page 18] Internet-Draft EPP ASN Mapping January 2009 Example command: C: C: C: C: C: C: 64500 C: C: fan C: C: C: hkk C: C: C: BR-XYZW-LACNIC> C: C: C: C: ABC-12345 C: C: When an 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: ABC-12345 S: 54321-XYZ S: S: S: An EPP error response MUST be returned if an command cannot be processed for any reason. Neves & Kobayashi Expires July 5, 2009 [Page 19] Internet-Draft EPP ASN Mapping January 2009 3.3. Offline Review of Requested Actions Commands are processed by a server in the order they are received from a client. Though an immediate response confirming receipt and processing of the command is produced by the server, a server operator MAY perform an offline review of requested transform commands before completing the requested action. In such situations, the response from the server MUST clearly note that the transform command has been received and processed, but the requested action is pending. The status of the corresponding object MUST clearly reflect processing of the pending action. The server MUST notify the client when offline processing of the action has been completed. TBD: Example of pending request + example "review completed" service message 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. The BEGIN and END tags are not part of the schema; they are used to note the beginning and ending of the schema for URI registration purposes. BEGIN Neves & Kobayashi Expires July 5, 2009 [Page 20] Internet-Draft EPP ASN Mapping January 2009 Extensible Provisioning Protocol v1.0 Autonomous System Number schema. Neves & Kobayashi Expires July 5, 2009 [Page 21] Internet-Draft EPP ASN Mapping January 2009 Neves & Kobayashi Expires July 5, 2009 [Page 23] Internet-Draft EPP ASN Mapping January 2009 Neves & Kobayashi Expires July 5, 2009 [Page 24] Internet-Draft EPP ASN Mapping January 2009 Neves & Kobayashi Expires July 5, 2009 [Page 25] Internet-Draft EPP ASN Mapping January 2009 END 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. Conformant XML processors recognize both UTF-8 and UTF-16 [RFC2781]. Though XML includes provisions to identify and use other character encodings through use of an "encoding" attribute in an declaration, use of UTF-8 is Neves & Kobayashi Expires July 5, 2009 [Page 26] Internet-Draft EPP ASN Mapping January 2009 RECOMMENDED in environments where parser encoding support incompatibility exists. 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. The extended date-time form using upper case "T" and "Z" characters defined in [W3C.REC-xmlschema-2-20041028] MUST be used to represent date-time values as XML Schema does not support truncated date-time forms or lower case "T" and "Z" characters. 6. IANA Considerations This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in [RFC3688]. Two URI assignments have been requested to IANA: Registration request for the extension namespace: URI: urn:ietf:params:xml:ns:asn-1.0 Registrant Contact: See the "Author's Address" section of this document. XML: None. Namespace URIs do not represent an XML specification. Registration request for the extension XML schema: URI: urn:ietf:params:xml:schema:asn-1.0 Registrant Contact: See the "Author's Address" section of this document. XML: See the "Formal Syntax" section of this document. 7. Security Considerations The object mapping described in this document does not provide any other security services or introduce any additional considerations beyond those described by [RFC4930] and protocol layers used by EPP. 8. Acknowledgements Neves & Kobayashi Expires July 5, 2009 [Page 27] Internet-Draft EPP ASN Mapping January 2009 9. References 9.1. Normative References [I-D.ietf-idr-as-representation] Huston, G. and G. Michaelson, "Textual Representation of AS Numbers", draft-ietf-idr-as-representation-01 (work in progress), September 2008. [I-D.neves-epp-brorg] Neves, F. and H. Kobayashi, "BR Organization Mapping for the Extensible Provisioning Protocol (EPP)", draft-neves-epp-brorg-04 (work in progress), June 2007. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004. [RFC4930] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", RFC 4930, May 2007. [W3C.REC-xml-20040204] Maler, E., Yergeau, F., Sperberg-McQueen, C., Paoli, J., and T. Bray, "Extensible Markup Language (XML) 1.0 (Third Edition)", World Wide Web Consortium FirstEdition REC-xml- 20040204, February 2004, . [W3C.REC-xmlschema-1-20041028] Thompson, H., Maloney, M., Mendelsohn, N., and D. Beech, "XML Schema Part 1: Structures Second Edition", World Wide Web Consortium Recommendation REC-xmlschema-1-20041028, October 2004, . [W3C.REC-xmlschema-2-20041028] Malhotra, A. and P. Biron, "XML Schema Part 2: Datatypes Second Edition", World Wide Web Consortium Recommendation REC-xmlschema-2-20041028, October 2004, . 9.2. Informative References [RFC2781] Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO 10646", RFC 2781, February 2000. Neves & Kobayashi Expires July 5, 2009 [Page 28] Internet-Draft EPP ASN Mapping January 2009 Authors' Addresses Frederico A. C. Neves NIC.br / Registro.br Av. das Nacoes Unidas, 11541, 7 Sao Paulo, SP 04578-000 BR Phone: +55 11 5509 3511 Email: fneves@registro.br URI: http://registro.br/ Hugo Koji Kobayashi NIC.br / Registro.br Av. das Nacoes Unidas, 11541, 7 Sao Paulo, SP 04578-000 BR Phone: +55 11 5509 3511 Email: koji@registro.br URI: http://registro.br/ Neves & Kobayashi Expires July 5, 2009 [Page 29] Internet-Draft EPP ASN Mapping January 2009 Full Copyright Statement Copyright (C) The IETF Trust (2009). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Neves & Kobayashi Expires July 5, 2009 [Page 30]