Network Working Group F. Neves Internet-Draft H. Kobayashi Intended status: Informational Registro.br Expires: February 12, 2011 August 11, 2010 IP Network Mapping for the Extensible Provisioning Protocol (EPP) draft-neves-epp-ipnetwork-01.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 February 12, 2011. Abstract This document describes an Extensible Provisioning Protocol (EPP) mapping for the provisioning and management of IP Networks stored in a shared central repository. Specified in XML, this mapping defines EPP command syntax and semantics as applied to IP Networks. Neves & Kobayashi Expires February 12, 2011 [Page 1] Internet-Draft EPP IP Network Mapping August 2010 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Conventions Used In This Document . . . . . . . . . . . . 3 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 3 2.1. IP Network Identifiers . . . . . . . . . . . . . . . . . . 3 2.2. Organization Identifier . . . . . . . . . . . . . . . . . 4 2.3. Contact Identifiers . . . . . . . . . . . . . . . . . . . 4 2.4. IP Network Allocation Type . . . . . . . . . . . . . . . . 4 2.5. ASN . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.6. Validity Periods . . . . . . . . . . . . . . . . . . . . . 5 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 5 3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . . 5 3.1.1. EPP Command . . . . . . . . . . . . . . . . . 5 3.1.2. EPP Command . . . . . . . . . . . . . . . . . . 8 3.1.3. EPP Command . . . . . . . . . . . . . . . . 13 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . . 15 3.2.1. EPP Command . . . . . . . . . . . . . . . . . 16 3.2.2. EPP Command . . . . . . . . . . . . . . . . . 19 3.2.3. EPP Command . . . . . . . . . . . . . . . . . 20 3.2.4. EPP Command . . . . . . . . . . . . . . . . 22 3.2.5. EPP Command . . . . . . . . . . . . . . . . . 24 3.3. Offline Review of Requested Actions . . . . . . . . . . . 26 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 26 5. Internationalization Considerations . . . . . . . . . . . . . 33 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34 7. Security Considerations . . . . . . . . . . . . . . . . . . . 34 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 35 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 35 9.1. Normative References . . . . . . . . . . . . . . . . . . . 35 9.2. Informative References . . . . . . . . . . . . . . . . . . 36 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 36 Intellectual Property and Copyright Statements . . . . . . . . . . 37 Neves & Kobayashi Expires February 12, 2011 [Page 2] Internet-Draft EPP IP Network Mapping August 2010 1. Introduction This document describes an IP Network 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 [RFC5730] 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. IP Network Identifiers All EPP IP Networks are identified by a server-unique identifier. IP Network identifiers are tokens with a specified format. IP Network identifiers use the "roidType" (Repository Object IDentifier type) described in [RFC5730]. All EPP IP Networks are also identified by a pair of addresses: the start and end addresses, which is the range of addresses of the IP network. However, this range of addresses is not a server-unique identifier as it is possible to have a parent and child network with the same start and end address. Each IP range contains a "version" attribute to identify the IP address version. Attribute value "v4" is used to denote IPv4 address format. Attribute value "v6" is used to denote IPv6 address format. If the "version" attribute is not specified, "v4" is the default Neves & Kobayashi Expires February 12, 2011 [Page 3] Internet-Draft EPP IP Network Mapping August 2010 attribute value. 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]. 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 [RFC5730]. 2.4. IP Network Allocation Type An IP Network object MUST always have one associated allocation type value. Allocation types are mutually exclusive, which means that a network object can only have one allocation type at a time. Allocation type values can be set by the server on which the IP network resides or by the client that sponsors an IP network object, subject to server policy. A client can change the IP network allocation type using the EPP command. Allocation Type Descriptions: - Assignment IP network delegation to an end user, for specific use within the Internet infrastructure the assignee operates. - Allocation IP network delegation to an Internet Service Provider (ISP) for the purpose of subsequent distribution to its clients. - Reservation IP network reserved for future delegation to an ISP or end user. 2.5. ASN If supported by the server, an IP network MAY be associated to an Autonomous System. The syntax for Autonomous System Numbers Neves & Kobayashi Expires February 12, 2011 [Page 4] Internet-Draft EPP IP Network Mapping August 2010 described in this document MUST conform to [I-D.ietf-idr-as-representation]. 2.6. Validity Periods An IP network object MAY have a specified validity period. If server policy supports IP network validity periods, the validity period is defined when an IP network 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 IP network 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 the EPP core protocol specification [RFC5730]. The command mappings described here are specifically for use in provisioning and managing IP networks via EPP. 3.1. EPP Query Commands EPP provides three commands to retrieve object information: to determine if an object is known to the server, to retrieve detailed information associated with an object, and to retrieve 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. In addition to the standard EPP command elements, the command MUST contain an element that identifies the IP network namespace. The element contains the following child elements: Neves & Kobayashi Expires February 12, 2011 [Page 5] Internet-Draft EPP IP Network Mapping August 2010 - One or more elements that contain the range of IP addresses of the network to be queried. This element contains an OPTIONAL "version" attribute that identifies the IP version. Attribute value "v4" is used to denote IPv4 address format. Attribute value "v6" is used to denote IPv6 address format. If not specified, "v4" is the default attribute value. Each element contains the following child elements: - One element that contains the first IP address of the network. - One element that contains the last IP address of the network. Example command: C: C: C: C: C: C: C: 192.168.0.0 C: 192.168.0.255 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 IP network namespace. The element contains one or more elements that contain the following child elements: - One element that contains the range of IP addresses of the network to be queried. In addition to the OPTIONAL "version" attribute, 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. Each element contains the following child elements: Neves & Kobayashi Expires February 12, 2011 [Page 6] Internet-Draft EPP IP Network Mapping August 2010 - One element that contains the first IP address of the network. - One element that contains the last IP address of the network. - 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 cannot 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). Example response: S: S: S: S: S: Command completed successfully S: S: S: S: S: S: 192.168.0.0 S: 192.168.0.255 S: 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. Neves & Kobayashi Expires February 12, 2011 [Page 7] Internet-Draft EPP IP Network Mapping August 2010 3.1.2. EPP Command The EPP command is used to retrieve information associated with an IP network object. In addition to the standard EPP command elements, the command MUST contain an element that identifies the IP network namespace. The element contains the following child elements: - An element that contains the range of IP addresses of the network to be queried. This element contains an OPTIONAL "version" attribute that identifies the IP version. Attribute value "v4" is used to denote IPv4 address format. Attribute value "v6" is used to denote IPv6 address format. If not specified, "v4" is the default attribute value. Each element contains the following child elements: - One element that contains the first IP address of the network. - One element that contains the last IP address of the network. - An OPTIONAL element that contains the Repository Object IDentifier assigned to the IP network referenced in the element. Example command: C: C: C: C: C: C: C: 192.168.0.0 C: 192.168.15.255 C: C: b_123456-LACNIC 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 IP network namespace. The Neves & Kobayashi Expires February 12, 2011 [Page 8] Internet-Draft EPP IP Network Mapping August 2010 element contains the following child elements: - An element that contains the range of IP addresses of the network to be queried. This element contains an OPTIONAL "version" attribute that identifies the IP version. Attribute value "v4" is used to denote IPv4 address format. Attribute value "v6" is used to denote IPv6 address format. If not specified, "v4" is the default attribute value. Each element contains the following child elements: - One element that contains the first IP address of the network. - One element that contains the last IP address of the network. - One or more elements that contains the following child elements: - An element that contains the Repository Object IDentifier assigned to the network object when the object was created. There are possibly more than one id per iprange because iprange is not a server-unique identifier. - An element that contains the IP network allocation type. - An element that contains the organization identifier that manages the IP network. - One or more elements that contain indentifiers for contact objects associated with the IP network. - An OPTIONAL that contains the Autonomous System Number that manages the network. - Zero or more OPTIONAL elements that contain DNS delegation information for the IP network. Each has the following child elements: - An element that contains the range of IP addresses that has reverse DNS delegation information. This element contains an OPTIONAL "version" attribute that identifies the IP version. Attribute value "v4" is used to denote IPv4 address format. Attribute value "v6" is used to denote IPv6 address format. If not specified, "v4" is the default attribute value. Each element Neves & Kobayashi Expires February 12, 2011 [Page 9] Internet-Draft EPP IP Network Mapping August 2010 contains the following child elements: - One element that contains the first IP address of the network. - One element that contains the last IP address of the network. The range of IP addresses of the element MUST be a subset of the IP address range described in the element of the queried IP network. - One or more elements that contains the fully qualified names of the delegated host attributes associated with this element. - One OPTIONAL element that contains the range of IP addresses and roid of the parent IP network. Each element has the following child elements: - An element that contains the range of IP addresses of the parent IP network. This element contains an OPTIONAL "version" attribute that identifies the IP version. Attribute value "v4" is used to denote IPv4 address format. Attribute value "v6" is used to denote IPv6 address format. If not specified, "v4" is the default attribute value. Each element contains the following child elements: - One element that contains the first IP address of the network. - One element that contains the last IP address of the network. The range of IP addresses of the element of the queried IP network MUST be a subset of the IP address range described for this element. - An OPTIONAL element that contains the Repository Object IDentifier assigned to this parent IP network object. Neves & Kobayashi Expires February 12, 2011 [Page 10] Internet-Draft EPP IP Network Mapping August 2010 - One or more OPTIONAL element that contains the range of IP addresses and roids of allocated or assigned subnetworks of the IP network. Each element has the following same child elements: - An element that contains the range of IP addresses of this child IP network. This element contains an OPTIONAL "version" attribute that identifies the IP version. Attribute value "v4" is used to denote IPv4 address format. Attribute value "v6" is used to denote IPv6 address format. If not specified, "v4" is the default attribute value. Each element contains the following child elements: - One element that contains the first IP address of the network. - One element that contains the last IP address of the network. The range of IP addresses of the element MUST be a subset of the IP address range described in the element of the queried IP network. - An OPTIONAL element that contains the Repository Object IDentifier assigned to this child IP network object. - An element that contains the identifier of the sponsoring client. - An OPTIONAL element that contains the identifier of the client that created the IP network object. - An OPTIONAL element that contains the date and time of the IP network object creation. - An OPTIONAL element that contains the date and time identifying the end of the IP network object registration period. - An OPTIONAL element that contains the identifier of the client that last updated the network object. This element MUST NOT be present if the network has never been modified. Neves & Kobayashi Expires February 12, 2011 [Page 11] Internet-Draft EPP IP Network Mapping August 2010 - An OPTIONAL element that contains the date and time of the most recent network object modification. This element MUST NOT be present if the network object has never been modified. - An OPTIONAL element that contains the most recent successful IP network object transfer. This element MUST NOT be provided if the IP network object has never been transferred. Example response: S: S: S: S: S: Command completed successfully S: S: S: S: S: 192.168.0.0 S: 192.168.15.255 S: S: S: b_123456-LACNIC S: allocation S: BR-ABC-LACNIC S: HKK S: S: S: 192.168.0.0 S: 192.168.0.255 S: S: a.example.com S: b.example.com S: S: S: S: 192.168.2.0 S: 192.168.2.255 S: S: d.example.com S: e.example.com S: S: Neves & Kobayashi Expires February 12, 2011 [Page 12] Internet-Draft EPP IP Network Mapping August 2010 S: S: 192.168.0.0 S: 192.168.255.255 S: S: b_12345-LACNIC S: S: S: S: 192.168.0.0 S: 192.168.0.127 S: S: b_234567-LACNIC S: S: ClientY S: ClientX S: 1999-04-03T22:00:00.0Z S: ClientX S: 1999-12-03T09:00:00.0Z S: 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. 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 network namespace. The element MUST contain the following child elements: - An element that contains the server-unique identifier of the IP network object to be queried. Neves & Kobayashi Expires February 12, 2011 [Page 13] Internet-Draft EPP IP Network Mapping August 2010 Example query command: C: C: C: C: C: C: b_123456-LACNIC 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 IP network namespace. The element contains the following child elements: - An element that contains the server-unique identifier for the queried network. - 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. - An element that contains the identifier of the client that SHOULD act upon the transfer request. - An 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. Neves & Kobayashi Expires February 12, 2011 [Page 14] Internet-Draft EPP IP Network Mapping August 2010 Example query response: S: S: S: S: S: Command completed successfully S: S: S: S: b_123456-LACNIC 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 IP network objects: to create an instance of an IP network object, to delete an instance of an IP network object, to extend the validity period of an IP network object, to manage IP network object sponsorship changes, and to change information associated with an IP network object. Transform commands are typically processed and completed in real 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 Neves & Kobayashi Expires February 12, 2011 [Page 15] Internet-Draft EPP IP Network Mapping August 2010 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 IP network object. In addition to the standard EPP command elements, the command MUST contain an element that identifies the IP network namespace. The element contains the following child elements: - An element that contains the range of IP addresses of the network object to be created. This element contains an OPTIONAL "version" attribute that identifies the IP version. Attribute value "v4" is used to denote IPv4 address format. Attribute value "v6" is used to denote IPv6 address format. If not specified, "v4" is the default attribute value. Each element contains the following child elements: - One element that contains the first IP address of the network. - One element that contains the last IP address of the network. - An element that contains identifier for the organization object to be associated with the IP network. This identifier MUST be known to the server before the IP network object can be associated with this organization object. The EPP mapping for organization objects is described in [I-D.neves-epp-brorg]. - An OPTIONAL element that contains the IP network allocation type. - An OPTIONAL that contains the Autonomous System Number that manages the network. - Zero or more OPTIONAL elements that contain indentifiers for contact objects to be associated with the IP network. - Zero or more OPTIONAL elements that contain DNS delegation information for the IP network. Each has the following child elements: Neves & Kobayashi Expires February 12, 2011 [Page 16] Internet-Draft EPP IP Network Mapping August 2010 - An element that contains the range of IP addresses of the network that has reverse DNS information. This element contains an OPTIONAL "version" attribute that identifies the IP version. Attribute value "v4" is used to denote IPv4 address format. Attribute value "v6" is used to denote IPv6 address format. If not specified, "v4" is the default attribute value. Each element contains the following child elements: - One element that contains the first IP address of the network. - One element that contains the last IP address of the network. The range of IP addresses of the element MUST be a subset of the IP address range described in the element of the IP network to be created. - One or more elements that contains the fully qualified names of the delegated host attributes associated with this element. Neves & Kobayashi Expires February 12, 2011 [Page 17] Internet-Draft EPP IP Network Mapping August 2010 Example command: C: C: C: C: C: C: C: 192.168.16.0 C: 192.168.31.255 C: C: BR-ABC-LACNIC C: assignment C: ABC123 C: C: C: 192.168.16.0 C: 192.168.17.255 C: C: a.example.com C: b.example.com 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 IP network namespace. The element contains the following child elements: - An element that contains the range of IP addresses of the created network object. This element contains an OPTIONAL "version" attribute that identifies the IP version. Attribute value "v4" is used to denote IPv4 address format. Attribute value "v6" is used to denote IPv6 address format. If not specified, "v4" is the default attribute value. Each element contains the following child elements: - One element that contains the first IP address of the network. Neves & Kobayashi Expires February 12, 2011 [Page 18] Internet-Draft EPP IP Network Mapping August 2010 - One element that contains the last IP address of the network. - An element that contains the server-unique identifier for the created IP network. - An element that contains the date and time of IP network object creation. - An OPTIONAL element that contains the date identifying the end of the IP network object's registration period. Example response: S: S: S: S: S: Command completed successfully S: S: S: S: S: 192.168.16.0 S: 192.168.31.255 S: S: b_123456-LACNIC 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 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 an IP network object. In addition to the standard EPP command elements, the command MUST contain an Neves & Kobayashi Expires February 12, 2011 [Page 19] Internet-Draft EPP IP Network Mapping August 2010 element that identifies the IP network namespace. The element MUST contain the following child element: - An element that contains the server-unique identifier of the network object to be deleted. Example command: C: C: C: C: C: C: b_123456-LACNIC 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 can not be processed for any reason. 3.2.3. EPP Command The EPP command provides a transform operation that allows a client to extend the validity period of an IP network object. In addition to the standard EPP command elements, the command Neves & Kobayashi Expires February 12, 2011 [Page 20] Internet-Draft EPP IP Network Mapping August 2010 MUST contain an element that identifies the IP network namespace. The element contains the following child elements: - An element that contains the server-unique identifier of the IP network 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 IP network object. The number of units available MAY be subject to limits imposed by the server. Example command: C: C: C: C: C: C: b_12345-LACNIC C: C: 2008-04-03T00:00:00.0Z C: 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 IP network namespace. The element contains the following child elements: - An element that contains the server-unique identifier of the IP network. Neves & Kobayashi Expires February 12, 2011 [Page 21] Internet-Draft EPP IP Network Mapping August 2010 - An OPTIONAL element that contains the date and time identifying the end of the IP network object's registration period. Example response: S: S: S: S: S: Command completed successfully S: S: S: S: b_12345-LACNIC 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 IP network object. In addition to the standard EPP command elements, the command MUST contain an element that identifies the IP network namespace. The element contains the following child elements: - An element that contains the server-unique identifier of the IP network 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 [RFC5730]. Neves & Kobayashi Expires February 12, 2011 [Page 22] Internet-Draft EPP IP Network Mapping August 2010 Example command: C: C: C: C: C: C: b_12345-LACNIC 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 IP network 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: b_12345-LACNIC 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 Neves & Kobayashi Expires February 12, 2011 [Page 23] Internet-Draft EPP IP Network Mapping August 2010 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 an IP network object. In addition to the standard EPP command elements, the command MUST contain an element that identifies the IP network namespace. The element contains the following child elements: - An element that contains the server-unique identifier of the IP network object 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: - One or more elements that contain DNS delegation information for the IP network. Each has the following child elements: - An element that contains the range of IP addresses of the network that has reverse DNS information. This element contains an OPTIONAL "version" attribute that identifies the IP version. Attribute value "v4" is used to denote IPv4 address format. Attribute value "v6" is used to denote IPv6 address format. If not specified, "v4" is the default attribute value. Each element contains the following child elements: - One element that contains the first IP address of the network. - One element that contains the last IP address of the network. Neves & Kobayashi Expires February 12, 2011 [Page 24] Internet-Draft EPP IP Network Mapping August 2010 - One or more elements that contains the fully qualified names of the delegated host attributes associated with this element. - One or more elements that contain indentifiers for contact objects to be associated with the IP Network. An element contains the following OPTIONAL child elements. At least one child element MUST be present: - An element that contains the identifier for the organization object to be associated with the IP network. - An element that contains the IP network allocation type. Example command: C: C: C: C: C: C: b_123456-LACNIC C: C: AAA1 C: C: C: BR-DEF-LACNIC C: assignment C: 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. Neves & Kobayashi Expires February 12, 2011 [Page 25] Internet-Draft EPP IP Network Mapping August 2010 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 can not be processed for any reason. 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 Extensible Provisioning Protocol v1.0 IP range provisioning schema. Neves & Kobayashi Expires February 12, 2011 [Page 27] Internet-Draft EPP IP Network Mapping August 2010 Neves & Kobayashi Expires February 12, 2011 [Page 28] Internet-Draft EPP IP Network Mapping August 2010 Neves & Kobayashi Expires February 12, 2011 [Page 30] Internet-Draft EPP IP Network Mapping August 2010 Neves & Kobayashi Expires February 12, 2011 [Page 31] Internet-Draft EPP IP Network Mapping August 2010 Neves & Kobayashi Expires February 12, 2011 [Page 32] Internet-Draft EPP IP Network Mapping August 2010 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 Neves & Kobayashi Expires February 12, 2011 [Page 33] Internet-Draft EPP IP Network Mapping August 2010 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 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:ipnetwork-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:ipnetwork-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 [RFC5730] and protocol layers used by EPP. Neves & Kobayashi Expires February 12, 2011 [Page 34] Internet-Draft EPP IP Network Mapping August 2010 8. Acknowledgements 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. [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", STD 69, RFC 5730, August 2009. [W3C.REC-xml-20040204] Paoli, J., Maler, E., Yergeau, F., Sperberg-McQueen, C., 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] Mendelsohn, N., Thompson, H., Beech, D., and M. Maloney, "XML Schema Part 1: Structures Second Edition", World Wide Web Consortium Recommendation REC-xmlschema-1-20041028, October 2004, . [W3C.REC-xmlschema-2-20041028] Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes Second Edition", World Wide Web Consortium Recommendation REC-xmlschema-2-20041028, October 2004, . Neves & Kobayashi Expires February 12, 2011 [Page 35] Internet-Draft EPP IP Network Mapping August 2010 9.2. Informative References [RFC2781] Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO 10646", RFC 2781, February 2000. 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 February 12, 2011 [Page 36] Internet-Draft EPP IP Network Mapping August 2010 Full Copyright Statement Copyright (C) The IETF Trust (2010). 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 February 12, 2011 [Page 37]