Network Working Group F. Neves Internet-Draft H. Kobayashi Intended status: Informational Registro.br Expires: February 17, 2012 August 16, 2011 BR Domain Mapping for the Extensible Provisioning Protocol (EPP) draft-neves-epp-brdomain-05.txt Abstract This document describes an Extensible Provisioning Protocol (EPP) extension mapping for the provisioning and management of .br Internet domain names stored in a shared central repository. Specified in XML, this mapping extends the EPP domain name mapping to provide additional features required for the provisioning of .br domain names. 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). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. 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." This Internet-Draft will expire on February 17, 2012. Neves & Kobayashi Expires February 17, 2012 [Page 1] Internet-Draft EPP BR Domain Mapping August 2011 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Conventions Used In This Document . . . . . . . . . . . . 3 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Ticket Number . . . . . . . . . . . . . . . . . . . . . . 3 2.2. Organization Identifier . . . . . . . . . . . . . . . . . 4 2.3. Release Process . . . . . . . . . . . . . . . . . . . . . 4 2.3.1. Flags . . . . . . . . . . . . . . . . . . . . . . . . 4 2.4. Host Status . . . . . . . . . . . . . . . . . . . . . . . 4 2.5. Pending . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.5.1. Documentation Pending . . . . . . . . . . . . . . . . 4 2.5.2. DNS Pending . . . . . . . . . . . . . . . . . . . . . 5 2.5.3. Release Process Pending . . . . . . . . . . . . . . . 5 2.6. Domain Equivalence . . . . . . . . . . . . . . . . . . . . 5 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 5 3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . . 5 3.1.1. EPP Command . . . . . . . . . . . . . . . . . 5 3.1.2. EPP Command . . . . . . . . . . . . . . . . . . 9 3.1.3. EPP Command . . . . . . . . . . . . . . . . 14 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . . 15 3.2.1. EPP Command . . . . . . . . . . . . . . . . . 15 3.2.2. EPP Command . . . . . . . . . . . . . . . . . 19 3.2.3. EPP Command . . . . . . . . . . . . . . . . . 19 3.2.4. EPP Command . . . . . . . . . . . . . . . . 20 3.2.5. EPP Command . . . . . . . . . . . . . . . . . 20 3.3. Offline Review of Requested Actions . . . . . . . . . . . 27 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 31 5. Internationalization Considerations . . . . . . . . . . . . . 38 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38 7. Security Considerations . . . . . . . . . . . . . . . . . . . 39 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 39 8.1. Normative References . . . . . . . . . . . . . . . . . . . 39 8.2. Informative References . . . . . . . . . . . . . . . . . . 40 Appendix A. Changes from version 03 . . . . . . . . . . . . . . . 40 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 40 Intellectual Property and Copyright Statements . . . . . . . . . . 42 Neves & Kobayashi Expires February 17, 2012 [Page 2] Internet-Draft EPP BR Domain Mapping August 2011 1. Introduction This document describes a .br Internet domain name mapping for version 1.0 of the Extensible Provisioning Protocol (EPP). This mapping, an extension of the domain name mapping described in [RFC5731], 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. 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 illustrate element relationships and is not a REQUIRED feature of this protocol. 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. 2. Object Attributes This extension adds elements to the EPP domain name mapping [RFC5731]. Only new element descriptions are described here. 2.1. Ticket Number A ticket is the unique sequential identifier that represents and guarantees the principle of first come first served operations for a .br domain name registration. A ticket represents a .br domain name registration request that has a "pendingCreate" status. Multiple concurrent tickets for the same or equivalent domain object, representing requests made by different organizations, MAY be active at the same time. Neves & Kobayashi Expires February 17, 2012 [Page 3] Internet-Draft EPP BR Domain Mapping August 2011 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. Release Process When a domain name is deleted it does not return to the free name space. It need to pass a so called "Release Process", that offers these names for a fixed period of time to the public. Depending on the number of interested parties for each domain name and the demonstration of specific rights to it, at the end of the process, a name could be assigned to an interested party, return to the free name space, or return to a list to be offered again in a future release process. 2.3.1. Flags This document defines 3 generic flags to be used during the release process. The semantics of these flags are announced before the beginning of each process. The purpose of these flags is to signal specific rights of an organization on a requested domain name. 2.4. Host Status Before a name server is accepted as a delegated server for a given .br domain name, it MUST be configured to answer DNS queries authoritatively for this domain name. The status of a name server is checked by the server upon receipt of a command that add new name servers to a domain object. 2.5. Pending Registration requests MAY have their status set as "pendingCreate" due to some off-line procedures. There are 3 kinds of pending that may require off-line procedures by the registrant, the sponsoring client or the registry. 2.5.1. Documentation Pending Depending on the category of the domain name, some proof of eligibility MAY be required. In this case, a doc pending will be set until the list of documents is sent by the registrant. Neves & Kobayashi Expires February 17, 2012 [Page 4] Internet-Draft EPP BR Domain Mapping August 2011 2.5.2. DNS Pending Authoritative servers MUST be provided to complete the domain registration. If the delegated servers does not answer authoritatively at registration time, a dns pending will be set until problem is solved. 2.5.3. Release Process Pending This pending signals the end and the result of the release process. 2.6. Domain Equivalence For registration purposes, an equivalence mapping for the comparison of domain names is established. The mapping is carried through changing the accented characters and "c" cedilla, respectively, for their not accented versions and the "c" character, and discarding hyphens. The valid characters table for IDNA [RFC5890], [RFC5891] in the .br registry is describe in [BR-Portuguese-Table]. A given domain name X is considered equivalent to another domain name Y if, after applying the equivalence mapping, the resulting domain names X' and Y' are equal. 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 .br Internet domain names 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 This extension defines additional elements to the EPP command and EPP response described in the EPP domain mapping [RFC5731]. The EPP command is used to determine if an object can be provisioned within a repository. In addition to the EPP command elements described in the EPP domain mapping [RFC5731], the Neves & Kobayashi Expires February 17, 2012 [Page 5] Internet-Draft EPP BR Domain Mapping August 2011 command MAY contain an element. The element MUST contain a child element element that identifies the extension namespace and the location of the extension schema. The element contains the following child element: - A element that contains the identifier for the organization object that MAY be associated with the domain object as the object registrant. The EPP mapping for organization objects is described in [I-D.neves-epp-brorg]. Example command with organization object: C: C: C: C: C: C: example.com.br C: example.net.br C: example.org.br C: C: C: C: C: C: 005.506.560/0001-36 C: C: C: C: ABC-12345 C: C: When a command has been processed successfully, the EPP element MUST contain child elements as described in the EPP domain mapping [RFC5731]. In addition, the EPP element MAY contain a child element. The element MUST contain a child element that identifies the extension namespace and the location of the extension schema. The Neves & Kobayashi Expires February 17, 2012 [Page 6] Internet-Draft EPP BR Domain Mapping August 2011 element contains one or more of the following child element: - One or more elements. Each element contains OPTIONAL hasConcurrent and inReleaseProcess attributes to indicate if there is any request for this domain name registration or if the domain name is being offered in the release process, respectively. The element contains the following child elements: - A element that contains the fully qualified name of the queried domain object. - An OPTIONAL element that contains the fully qualified name of the equivalent domain object that is restricting the availability of the queried domain object. This element MUST NOT be present if the exact queried object is unavailable. - An OPTIONAL element that contains the identifier for the organization object that is associated with the queried or equivalent domain object. The EPP mapping for organization objects is described in [I-D.neves-epp-brorg]. - Zero or more elements that contain the identifiers of existing domain registration requests for equivalent domain name objects. Example response with element: S: S: S: S: S: Command completed successfully S: S: S: S: S: e-xample.net.br S: In use S: Neves & Kobayashi Expires February 17, 2012 [Page 7] Internet-Draft EPP BR Domain Mapping August 2011 S: S: example.org.br S: S: S: example.com.br S: S: S: example.ind.br S: S: S: S: S: S: S: e-xample.net.br S: S: example.net.br S: S: S: 043.828.151/0001-45 S: S: S: S: example.org.br S: S: 043.828.151/0001-45 S: S: S: S: example.com.br S: 123456 S: S: S: example.ind.br S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: An EPP error response MUST be returned if an extended command Neves & Kobayashi Expires February 17, 2012 [Page 8] Internet-Draft EPP BR Domain Mapping August 2011 can not be processed for any reason. 3.1.2. EPP Command This extension defines additional elements to the EPP command and EPP response described in the EPP domain mapping [RFC5731]. The EPP command is used to retrieve information associated with a domain object. In addition to the EPP command elements described in the EPP domain mapping [RFC5731], the command MAY contain an element. The element MUST contain a child element element that identifies the extension namespace and the location of the extension schema. The element contains the following child element: - A element that contains the identifier of the domain registration request. Example command with ticket number: C: C: C: C: C: C: example.com.br C: C: C: C: C: 123456 C: C: C: ABC-12345 C: C: The element MUST only be used for domain objects with the Neves & Kobayashi Expires February 17, 2012 [Page 9] Internet-Draft EPP BR Domain Mapping August 2011 "pendingCreate" status. When an command has been processed successfully, the EPP element MUST contain child elements as described in the EPP domain mapping [RFC5731]. In addition, the EPP element MUST contain a child element. The element MUST contain a child element that identifies the extension namespace and the location of the extension schema. The element contains the following child elements: - An OPTIONAL element that contains the identifier of the domain registration request. This element MUST be present if the command contains this element. - An element that contains the identifier for the organization object associated with the domain object as the object registrant. The EPP mapping for organization objects is described in [I-D.neves-epp-brorg]. - An OPTIONAL element that contains flags for the release process. This element MUST NOT be present if the request does not contain a element. At least one of its attributes flag1, flag2, or flag3 MUST be provided. - An OPTIONAL element that contains pending information to be resolved before the registration request can be completed. This element MUST NOT be present if the request does not contain a element. The element contains the following child elements: - Zero or more elements that contains information about documents that MUST be sent by an off-line procedure. Each element MUST contain a status attribute. A element contains the following child elements: - A element that contains the type of document. - A element that contains the date and time limit of this pending. - A element that has a description of the required document in human readable format. Neves & Kobayashi Expires February 17, 2012 [Page 10] Internet-Draft EPP BR Domain Mapping August 2011 - Zero or more elements that contains DNS pending information. Each element MUST contain a status attribute. A element contains the following child elements: - A element that contains the fully qualified name of a host. - A element that contains the date and time limit of this pending. - An OPTIONAL element. This element MUST contain a status attribute. A element contains the following child elements: - A element that contains the date and time limit of this pending. - Zero or more elements that contain the identifiers of concurrent domain registration requests for equivalent domain objects. This element MUST NOT be present if the request does not contain a element. - An OPTIONAL element that contains the domain object publication status. This element MUST NOT be present if the request contains a element. The element MUST contain a publicationFlag attribute and MAY contain the following child element: - Zero or more elements that contain the reason for not publishing the domain name. This element MUST be present if the domain publicationFlag is set to "onHold" or "waitingWithdrawal". - An OPTIONAL element that contains a REQUIRED "active" attribute. A positive boolean value indicates that the validity period of the domain name is automatically extended by the Registry. Example response of a command with ticket number: S: S: S: Neves & Kobayashi Expires February 17, 2012 [Page 11] Internet-Draft EPP BR Domain Mapping August 2011 S: S: Command completed successfully S: S: S: S: example.com.br S: EXAMPLE1-REP S: S: fan S: fan S: fan S: S: S: ns1.example.com.br S: 192.0.2.1 S: S: S: ns1.example.net.br S: S: S: ClientX S: ClientX S: 2006-01-30T22:00:00.0Z S: ClientX S: 2006-01-31T09:00:00.0Z S: S: S: S: S: 123456 S: S: 005.506.560/0001-36 S: S: S: S: S: S: ns1.example.com.br S: S: 2006-02-13T22:00:00.0Z S: S: Neves & Kobayashi Expires February 17, 2012 [Page 12] Internet-Draft EPP BR Domain Mapping August 2011 S: CNPJ S: 2006-03-01T22:00:00.0Z S: S: Cadastro Nacional da Pessoa Juridica S: S: S: S: 2006-02-01T22:00:00.0Z S: S: S: S: 123451 S: S: S: 123455 S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: Example response of a command without ticket number: S: S: S: S: S: Command completed successfully S: S: S: S: example.com.br S: EXAMPLE1-REP S: S: fan S: fan S: fan S: Neves & Kobayashi Expires February 17, 2012 [Page 13] Internet-Draft EPP BR Domain Mapping August 2011 S: S: ns1.example.com.br S: 192.0.2.1 S: S: S: ns1.example.net.br S: S: S: ClientX S: ClientX S: 2006-02-03T12:00:00.0Z S: ClientX S: 2006-02-03T12:00:00.0Z S: S: S: S: S: S: 005.506.560/0001-36 S: S: S: billing S: S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: An EPP error response MUST be returned if an extended command can not be processed for any reason. 3.1.3. EPP Command This extension does not add any elements to the EPP command or response described in the EPP domain mapping [RFC5731]. Neves & Kobayashi Expires February 17, 2012 [Page 14] Internet-Draft EPP BR Domain Mapping August 2011 3.2. EPP Transform Commands EPP provides five commands to transform objects: to create an instance of an object, to delete an instance of an object, to extend the validity period of an object, to manage object sponsorship changes, and to change information associated with an object. 3.2.1. EPP Command This extension defines additional elements to the EPP command and EPP response described in the EPP domain mapping [RFC5731]. The EPP command provides a transform operation that allows a client to create a domain object. In addition to the EPP command elements described in the EPP domain mapping [RFC5731], the command MUST contain an element. The element MUST contain a child element that identifies the extension namespace and the location of the extension schema. The element contains the following child elements: - A element that contains the identifier for the organization object that the domain object will be associated. This object identifier MUST be known to the server before the domain object can be associated with the organization object. The EPP mapping for organization objects is described in [I-D.neves-epp-brorg]. - An OPTIONAL element that contains flags for the release process. At least one of its attributes flag1, flag2, or flag3 MUST be provided. - An OPTIONAL element that contains a REQUIRED "active" attribute. A positive boolean value indicates that the validity period of the domain name is automatically extended by the Registry. Neves & Kobayashi Expires February 17, 2012 [Page 15] Internet-Draft EPP BR Domain Mapping August 2011 Example command: C: C: C: C: C: C: example.com.br C: C: C: ns1.example.com.br C: 192.0.2.1 C: C: C: ns1.example.net.br C: C: C: fan C: fan C: fan C: C: 2fooBAR C: C: C: C: C: C: C: 005.506.560/0001-36 C: C: C: C: C: C: ABC-12345 C: C: When a command has been processed successfully, the EPP Neves & Kobayashi Expires February 17, 2012 [Page 16] Internet-Draft EPP BR Domain Mapping August 2011 element MUST contain child elements as described in the EPP domain mapping [RFC5731]. In addition, the EPP element MUST contain a child element. The element MUST contain a child element that identifies the extension namespace and the location of the extension schema. The element contains the following child elements: - A element that contains the identifier of the domain registration request. - An OPTIONAL element that contains pending information to be resolved before the registration request can be completed. The element contains the following child elements: - Zero or more elements that contains information about documents that MUST be sent by an off-line procedure. Each element MUST contain a status attribute. A element contains the following child elements: - a element that contains the type of document. - a element that contains the date and time limit of this pending. - a element that has a description of the required document in human readable format. - Zero or more elements that contains DNS pending information. Each element MUST contain a status attribute. A element contains the following child elements: - a element that contains the fully qualified name of a host. - a element that contains the date and time limit of this pending. - an OPTIONAL element. This element MUST contain a status attribute. A element contains the following child elements: - a element that contains the date and time limit of this pending. Neves & Kobayashi Expires February 17, 2012 [Page 17] Internet-Draft EPP BR Domain Mapping August 2011 - Zero or more elements that contain the identifiers of concurrent domain registration requests for equivalent domain objects. Example response: S: S: S: S: S: Command completed successfully; action pending S: S: S: S: example.com.br S: 2006-01-30T22:00:00.0Z S: S: S: S: S: 123456 S: S: S: S: ns1.example.com.br S: S: 2006-02-13T22:00:00.0Z S: S: S: CNPJ S: 2006-03-01T22:00:00.0Z S: S: Cadastro Nacional da Pessoa Juridica S: S: S: S: S: 123451 S: Neves & Kobayashi Expires February 17, 2012 [Page 18] Internet-Draft EPP BR Domain Mapping August 2011 S: S: 123455 S: S: S: S: S: ABC-12345 S: 54321-XYZ S: S: S: An EPP error response MUST be returned if an extended command can not be processed for any reason. 3.2.2. EPP Command This extension does not add any elements to the EPP command or response described in the EPP domain mapping [RFC5731]. 3.2.3. EPP Command This extension defines additional elements for the EPP response described in the EPP domain mapping [RFC5731]. When a command has been processed successfully, the EPP element MUST contain child elements as described in the EPP domain mapping [RFC5731]. In addition, the EPP element MUST contain a child element. The element MUST contain a child element that identifies the extension namespace and the location of the extension schema. The element contains the following child element: - A element that contains the domain object publication status. The element MUST contain a publicationFlag attribute and MAY contain the following child element: - Zero or more elements that contain the reason for not publishing the domain name. This element MUST be present if the domain publicationFlag is set to "onHold" or "waitingWithdrawal". Neves & Kobayashi Expires February 17, 2012 [Page 19] Internet-Draft EPP BR Domain Mapping August 2011 Example response with element: S: S: S: S: S: Command completed successfully S: S: S: S: example.com.br S: 2007-04-03T00:00:00.0Z S: S: S: S: S: S: S: S: S: ABC-12345 S: 54322-XYZ S: S: S: 3.2.4. EPP Command This extension does not add any elements to the EPP command or response described in the EPP domain mapping [RFC5731]. 3.2.5. EPP Command This extension defines additional elements for the EPP command and EPP response described in the EPP domain mapping [RFC5731]. The EPP command provides a transform operation that allows a Neves & Kobayashi Expires February 17, 2012 [Page 20] Internet-Draft EPP BR Domain Mapping August 2011 client to change the state of a domain object. In addition to the EPP command elements described in the EPP domain mapping [RFC5731], the command MAY contain a child element. The element MUST contain a child element that identifies the extension namespace and the location of the extension schema. The element contains the following child elements: - An OPTIONAL element that contains the identifier of the domain registration request. - An OPTIONAL element that contains object attribute values to be changed. A element contains the following child elements: - An OPTIONAL element that contains flags for the release process. At least one of its attributes flag1, flag2, or flag3 MUST be provided. - An OPTIONAL element that contains a REQUIRED "active" attribute. A positive boolean value indicates that the validity period of the domain name is automatically extended by the Registry. - An OPTIONAL element that contains the domain object publication status. The publication status can be "published" or "onHold". - An OPTIONAL element that contains the identifier for the new organization object that the domain object will be associated. This object identifier MUST be known to the server before the domain object can be associated with the organization object. The EPP mapping for organization objects is described in [I-D.neves-epp-brorg]. Example command with an element: Neves & Kobayashi Expires February 17, 2012 [Page 21] Internet-Draft EPP BR Domain Mapping August 2011 C: C: C: C: C: C: example.com.br C: C: C: C: ns2.example.com C: C: C: hkk C: C: C: C: C: ns1.example.com.br C: C: C: fan C: C: C: C: C: C: 123456 C: C: C: C: C: published C: C: C: C: C: ABC-12345 C: C: Neves & Kobayashi Expires February 17, 2012 [Page 22] Internet-Draft EPP BR Domain Mapping August 2011 Example command with no element: C: C: C: C: C: C: example.com.br C: C: C: C: ns2.example.com C: C: C: hkk C: C: C: C: C: ns1.example.com.br C: C: C: fan C: C: C: C: ABC-12345 C: C: When an command has been processed successfully, the EPP element MUST contain child elements as described in the EPP domain mapping [RFC5731]. In addition, the response MAY contain a child EPP element. The EPP element MUST contain a child element that identifies the extension namespace and the location of the extension schema. The element contains the following child elements: Neves & Kobayashi Expires February 17, 2012 [Page 23] Internet-Draft EPP BR Domain Mapping August 2011 - An OPTIONAL element that contains the identifier of the domain registration request. This element MAY be present only if the command contains an element. - An OPTIONAL element that contains pending information to be resolved before the registration request can be completed. This element MAY be present only if the command contains an element. The element contains the following child elements: - Zero or more elements that contains information about documents that MUST be sent by an off-line procedure. Each element MUST contain a status attribute. A element contains the following child elements: - A element that contains the type of document. - A element that contains the date and time limit of this pending. - A element that has a description of the required document in human readable format. - Zero or more elements that contains DNS pending information. Each element MUST contain a status attribute. A element contains the following child elements: - A element that contains the fully qualified name of a host. - A element that contains the date and time limit of this pending. - An OPTIONAL element. This element MUST contain a status attribute. A element contains the following child elements: - a element that contains the date and time limit of this pending. - Zero or more element that contains information on DNS queries made to the hosts been modified. This element MAY be present only if the command does not contain an element. Neves & Kobayashi Expires February 17, 2012 [Page 24] Internet-Draft EPP BR Domain Mapping August 2011 - An OPTIONAL element that contains the domain object publication status. This element MUST NOT be present if the request contains a element. The element MUST contain a publicationFlag attribute and MAY contain the following child element: - Zero or more elements that contain the reason for not publishing the domain name. This element MUST be present if the domain publicationFlag is set to "onHold" or "waitingWithdrawal". Example response of a command with element: S: S: S: S: S: Command completed successfully S: S: S: S: 123456 S: S: S: CNPJ S: 2006-03-01T22:00:00.0Z S: S: Cadastro Nacional da Pessoa Juridica S: S: S: S: S: S: S: ABC-12345 S: 54321-XYZ S: S: S: Neves & Kobayashi Expires February 17, 2012 [Page 25] Internet-Draft EPP BR Domain Mapping August 2011 Example response of a command with no element: S: S: S: S: S: Data management policy violation S: S: S: S: S: ns2.example.com S: Query refused S: S: S: S: S: ABC-12345 S: 54321-XYZ S: S: S: Neves & Kobayashi Expires February 17, 2012 [Page 26] Internet-Draft EPP BR Domain Mapping August 2011 Another example response of a command with no element: S: S: S: S: S: Command completed successfully S: S: S: S: S: S: S: S: ABC-12345 S: 54321-XYZ S: S: S: An EPP error response MUST be returned if an extended 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. An example describing a command that requires offline review is included here. Note the result code and message returned in response to the command. Neves & Kobayashi Expires February 17, 2012 [Page 27] Internet-Draft EPP BR Domain Mapping August 2011 S: S: S: S: S: Command completed successfully; action pending S: S: S: S: example.com.br S: 2006-01-30T22:00:00.0Z S: S: S: S: S: 123456 S: S: S: S: ns1.example.com.br S: S: 2006-02-13T22:00:00.0Z S: S: S: S: S: S: ABC-12345 S: 54321-XYZ S: S: S: The status of the domain object after returning this response MUST include "pendingCreate". The server operator reviews the request offline, and informs the client of the outcome of the review by either queuing a service message for retrieval via the command or by using an out-of-band mechanism to inform the client of the request. Neves & Kobayashi Expires February 17, 2012 [Page 28] Internet-Draft EPP BR Domain Mapping August 2011 In addition to the EPP elements described in the EPP domain mapping [RFC5731], the command element MUST contain a child element. The element MUST contain a child element that identifies the extension namespace and the location of the extension schema. The element contains the following child element: - A element that contains the identifier of the domain registration request. - An OPTIONAL element containing a human-readable message that describes the reason for denying the request. The language of the response is identified via an OPTIONAL "lang" attribute. If not specified, the default attribute value MUST be "en" (English). Neves & Kobayashi Expires February 17, 2012 [Page 29] Internet-Draft EPP BR Domain Mapping August 2011 Example "review completed" service message: S: S: S: S: S: Command completed successfully; ack to dequeue S: S: S: 1999-04-04T22:01:00.0Z S: Pending action completed successfully. S: S: S: S: example.com.br S: S: ABC-12345 S: 54321-XYZ S: S: 2006-02-13T22:30:00.0Z S: S: S: S: S: 123456 S: S: Nao obtivemos uma resposta adequada durante o prazo S: fixado do servidor de DNS (ns1.example.com.br) para o S: presente dominio. S: S: S: S: S: BCD-23456 S: 65432-WXY S: S: S: Neves & Kobayashi Expires February 17, 2012 [Page 30] Internet-Draft EPP BR Domain Mapping August 2011 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 domain name extension schema for .br domain provisioning. Neves & Kobayashi Expires February 17, 2012 [Page 31] Internet-Draft EPP BR Domain Mapping August 2011 Neves & Kobayashi Expires February 17, 2012 [Page 32] Internet-Draft EPP BR Domain Mapping August 2011 Neves & Kobayashi Expires February 17, 2012 [Page 33] Internet-Draft EPP BR Domain Mapping August 2011 Neves & Kobayashi Expires February 17, 2012 [Page 34] Internet-Draft EPP BR Domain Mapping August 2011 Neves & Kobayashi Expires February 17, 2012 [Page 35] Internet-Draft EPP BR Domain Mapping August 2011 Neves & Kobayashi Expires February 17, 2012 [Page 36] Internet-Draft EPP BR Domain Mapping August 2011 Neves & Kobayashi Expires February 17, 2012 [Page 37] Internet-Draft EPP BR Domain Mapping August 2011 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 [RFC3629]. 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 RECOMMENDED in environments where parser encoding support incompatibility exists. As an extension of the EPP domain mapping [RFC5731], the elements, element content, attributes, and attribute values described in this document MUST inherit the internationalization conventions used to represent higher-layer domain and core protocol structures present in an XML instance that includes this extension. 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: Neves & Kobayashi Expires February 17, 2012 [Page 38] Internet-Draft EPP BR Domain Mapping August 2011 URI: urn:ietf:params:xml:ns:brdomain-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:brdomain-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 mapping extensions described in this document do not provided any security services beyond those described by EPP [RFC5730], the EPP domain name mapping [RFC5731], and protocol layers used by EPP. 8. References 8.1. Normative References [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), January 2009. [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. [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Domain Name Mapping", STD 69, RFC 5731, August 2009. [W3C.REC-xml-20040204] Bray, T., Maler, E., Sperberg-McQueen, C., Paoli, J., and F. Yergeau, "Extensible Markup Language (XML) 1.0 (Third Neves & Kobayashi Expires February 17, 2012 [Page 39] Internet-Draft EPP BR Domain Mapping August 2011 Edition)", World Wide Web Consortium FirstEdition REC-xml- 20040204, February 2004, . [W3C.REC-xmlschema-1-20041028] Beech, D., Thompson, H., Maloney, M., and N. Mendelsohn, "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, . 8.2. Informative References [BR-Portuguese-Table] Neves, F., "BR Portuguese Language Table", August 2005, . [RFC2781] Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO 10646", RFC 2781, February 2000. [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, November 2003. [RFC5890] Klensin, J., "Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework", RFC 5890, August 2010. [RFC5891] Klensin, J., "Internationalized Domain Names in Applications (IDNA): Protocol", RFC 5891, August 2010. Appendix A. Changes from version 03 1. Fixed example command in section 3.1.2 2. References of EPP drafts updated to RFCs 3. pDnsStatusType new enumeration values Neves & Kobayashi Expires February 17, 2012 [Page 40] Internet-Draft EPP BR Domain Mapping August 2011 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 17, 2012 [Page 41] Internet-Draft EPP BR Domain Mapping August 2011 Full Copyright Statement Copyright (C) The IETF Trust (2011). 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 17, 2012 [Page 42]