Internet Draft Tomek Zygmuntowicz draft-bartosiewicz-enum-48tld-00.txt Patrycja Wegrzynowicz October 17, 2003 Kuba Laszkiewicz Expires in six months Juliusz Brzostek Intended status: Informational Witold Zarowski Krzysztof Olesik Andrzej Bartosiewicz NASK (+48 ENUM Registry) EPP parameters for 8.4.e164.arpa Registry Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet- Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Abstract This document is a proposed description of the cooperation protocol between NASK and its Partners. The proposal can be replaced with the new document or can be invalidated. The content of this proposal relates to the documents: , , , , RFC 3375 published by Internet Engineering Task Force. 1. Introduction The Extensible Provisioning Protocol (EPP, [2]) describes an application layer client-server protocol for the provisioning and management of objects stored in a shared central repository. Specified in XML, EPP defines generic object management operations and an extensible framework that maps protocol operations to objects. The intent of this document is to specify the protocol elements in EPP extensions in order to accomodate additional information required for a registrar to interconnect with the 8.4.e164.arpa registry via an EPP-compatible interface. This document is based on the protocol for .PL domain names registrations. Readers should take document "EPP parameters for .pl ccTLD" (draft-zygmuntowicz-epp-pltld-00.txt) into consideration. 2. EPP modifications 2.1. The individual element The individual element has been added to commands: , and . It specifies whether the contact represents a private person. 2.2. The consentForPublishing element The consentForPublishing element has been added to commands: , and . It specifies for a contact representing a private person whether this person has given its assent for publishing personal details in WHOIS database. The consentForPublishing element has no meaning for a contact which does not represent a private person. 2.3. A transfer of a domain or a contact does not require a confirmation of sponsoring client of that object. A result of a transfer command is returned directly in response to or command with option op=request (status serverApproved is set in case of successful processing of transfer command). Options of the and commands other than request are not supported. 2.4. It is possible to delete a host using the command, even if there are domains delegated to that host, on the condition that the host is not configured for any domain which is delegated to this host. A side effect of a removal of a host is removal of all delegations to that host. 2.5. Using the command it is possible to create a host which belongs to a zone maintained by Registry (NASK) and for which no superordinate domain exists. Such created host has the pendingCreate status. It will be removed from the system if the superordinate domain is not reserved or registered before expiration of a period determined by the system parameters. 2.6. A change of a host's name is forbidden. A providing of the element in the element causes failure of the command. 2.7. The command returns full set of information only for sponsoring client, for other clients operation fails. 2.8. The command returns full set of information only for sponsoring client of a domain and client which provided a correct authorization information in the element. In other cases command fails. 2.9. The command returns full set of information only to sponsoring client of a domain and to client who provided a correct authorization information of domain in the element. Furthermore, if contact represents a private person (individual=1) who consents to publish his/her personal details (consentForPublishing=1) then information is returned to the others clients. In other cases command fails. 3. Examples Example 1: command 0.7.5.1.4.2.6.0.6.8.4.e164.arpa 2 ns1.example.tld ns1.example2.tld jd1234 2fooBAR nice name ABC-12345 Example 2: Processing of the command ns1.example.tld 192.1.2.3 198.1.2.3 1080:0:0:0:8:800:200417A ABC-12345 Example 3: System answer to the command Command completed successfully ns1.example.tld 1999-04-03T22:00:00.0Z ABC-12345 54322-XYZ Example 4: Processing of the command ns1.example.tld ABC-12345 Example 5: System answer to the command Command completed successfully ns1.example.tld NS1_EXAMPLE1-REP 192.1.2.3 198.1.2.3 1080:0:0:0:8:800:200417A ClientY ClientX 1999-04-03T22:00:00.0Z ClientX 1999-12-03T09:00:00.0Z 2000-04-08T09:00:00.0Z ABC-12345 54322-XYZ Example 6: Processing of the command ns1.example.tld 192.3.2.1 1080:0:0:0:8:800:200417A ns2.example.tld ABC-12345 Example 7: System answer to the command Command completed successfully ABC-12345 54321-XYZ Example 8: Processing of the command sh8013 11John Doe Example Inc. 123 Example Dr. Suite 100 Dulles VA 20166-6503 US +1.7035555555 +1.7035555556 jdoe@example.tld 2fooBAR 1 1 ABC-12345 Example 9: System answer to the command Command completed successfully sh8013 1999-04-03T22:00:00.0Z ABC-12345 54321-XYZ Example 10: Processing of the command 666666 2fooBAR ABC-12345 Example 11: System answer to the command Command completed successfully sh8013 SH8013-REP John Doe Example Inc. 123 Example Dr. Suite 100 Dulles VA 20166-6503 US +1.7035555555 +1.7035555556 jdoe@example.tld ClientY ClientX 1999-04-03T22:00:00.0Z ClientX 1999-12-03T09:00:00.0Z 2000-04-08T09:00:00.0Z 2fooBAR ABC-12345 54322-XYZ Example 12: Processing of the command sh8013 124 Example Dr. Suite 200 Dulles VA 20166-6503 US +1.7034444444 1 ABC-12345 Example 13: System answer to the command Command completed successfully ABC-12345 54321-XYZ 4. Formal syntax Extdom-1.0.xsd: NASK Extensible Provisioning Protocol v1.0 domain extension. Extcon-1.0.xsd: NASK Extensible Provisioning Protocol v1.0 contact extension. 5. Security Considerations This document does not require any special security considerations except those mentioned in documents [1], [2], [3], [4], [5], [6], [7]. 6. References [1] S. Hollenbeck "Generic Registry-Registrar Protocol Requirements", September 2002, RFC 3375. [2] S. Hollenbeck "Extensible Provisioning Protocol", August 2002, Internet-Draft. [3] S. Hollenbeck "Extensible Provisioning Protocol Contact Mapping", August 2002, Internet-Draft. [4] S. Hollenbeck "Extensible Provisioning Protocol Domain Name Mapping", August 2002, Internet-Draft. [5] S. Hollenbeck "Extensible Provisioning Protocol Host Mapping", August 2002, Internet-Draft. [6] S. Hollenbeck "Extensible Provisioning Protocol Transport Over TCP", August 2002, Internet-Draft. [7] S. Hollenbeck "Guidelines for Extending the Extensible Provisioning Protocol", October 2002, Internet-Draft. [8] T. Zygmuntowicz, P. Wegrzynowicz "EPP parameters for .pl ccTLD" May 2003, Internet-Draft. 7. Authors' Addresses Patrycja Wegrzynowicz NASK ul. Wawozowa 18 02-796 Warszawa Poland Email: patrycjaw@nask.pl Kuba Laszkiewicz NASK ul. Wawozowa 18 02-796 Warszawa Poland Email: jakubl@nask.pl Juliusz Brzostek NASK ul. Wawozowa 18 02-796 Warszawa Poland Email: juliuszb@nask.pl Tomek Zygmuntowicz NASK ul. Wawozowa 18 02-796 Warszawa Poland Email: tomekz@nask.pl Witold Zarowski NASK ul. Wawozowa 18 02-796 Warszawa Poland Email: witzar@nask.pl Krzysztof Olesik NASK ul. Wawozowa 18 02-796 Warszawa Poland Email: kolesik@nask.pl Andrzej Bartosiewicz NASK ul. Wawozowa 18 02-796 Warszawa Poland Email: andrzejb@nask.pl