Internet Engineering Task Force S. Hollenbeck Internet-Draft S. Veeramachaneni VeriSign, Inc. January 25, 2002 Expires: July 25, 2002 VeriSign Registry Registrar Protocol (RRP) Version 2.0.0 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 updates version 1.1.0 of the NSI Registry Registrar Protocol specified in RFC 2832. The changes described in this document combined with the base specification documented in RFC 2832 specify version 2.0.0 of the VeriSign Registry Registrar Protocol. 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. Hollenbeck & Veeramachaneni Informational [Page 1] Internet-Draft VeriSign RRP v2.0.0 January 25, 2002 Table of Contents 1. Introduction ................................................. 3 2. Protocol Updates ............................................. 4 2.1 Response Code Update ........................................ 4 2.2 TRANSFER Command Update ..................................... 5 2.3 Name Server IP Address Update ............................... 6 3. IANA Considerations .......................................... 8 4. Internationalization Considerations .......................... 8 5. Security Considerations ...................................... 8 6. Acknowledgements ............................................. 8 7. References ................................................... 8 8. Author's Address ............................................. 9 A. Revisions From Previous Version .............................. 9 B. Full Copyright Statement ..................................... 10 Hollenbeck & Veeramachaneni Informational [Page 2] Internet-Draft VeriSign RRP v2.0.0 January 25, 2002 1. Introduction The Network Solutions, Inc. (NSI) Registry Registrar Protocol (RRP) was developed by NSI in 1998 and 1999 to allow multiple registrars to provide second level Internet domain name registration services in the top level domains (TLDs) administered by the NSI TLD registry. Version 1.1.0 of the NSI RRP was published as Informational RFC 2832 [RFC2832] in May 2000. This document describes changes to RFC 2832 that specify version 2.0.0 of the protocol. NSI was acquired by VeriSign, Inc. in June 2000. The protocol name change from "NSI RRP" to "VeriSign RRP" is a reflection of that acquisition. Hollenbeck & Veeramachaneni Informational [Page 3] Internet-Draft VeriSign RRP v2.0.0 January 25, 2002 2. Protocol Updates This specification describes three modifications to [RFC2832]: a new error response code is defined, domain TRANSFER command processing is updated to allow a client to cancel a requested domain transfer, and support for IPv6 name server addresses is added. 2.1 Response Code Update Section 5.1 of [RFC2832] is updated to include an additional error response code: 557 Name server locked This response indicates that a name server has been locked by the registry. A name server cannot be modified or deleted while it is locked. Section 5.2 of [RFC2832] is updated to include the addition of response code 557 to the possible error values returned from the DEL and MOD commands: Command: DEL Success: 200, 220 Failure: 420, 421, 500, 502, 503, 504, 505, 507, 508, 520, 531, 532, 533, 541, 544, 545, 547, 549, 551, 552, 553, 557 Command: MOD Success: 200, 220 Failure: 420, 421, 500, 502, 503, 504, 505, 507, 508, 520, 531, 535, 540, 541, 542, 543, 544, 545, 547, 549, 550, 551, 552, 553, 557 Hollenbeck & Veeramachaneni Informational [Page 4] Internet-Draft VeriSign RRP v2.0.0 January 25, 2002 2.2 TRANSFER Command Update Section 4.3.10 of [RFC2832] is updated to include an additional TRANSFER command processing option. Old text: Authorized User: All registrars MAY use the TRANSFER command to request transfer of registration service authority to the requesting registrar. Only the current sponsoring registrar of a domain name may explicitly approve or reject a requested transfer. The registry MAY implicitly approve or reject requested transfers after a fixed amount of time. New text: Authorized User: All registrars MAY use the TRANSFER command to request transfer of registration service authority to the requesting registrar. Only the current sponsoring registrar of a domain name may explicitly approve a requested transfer. The current sponsoring registrar MAY explicitly reject a requested transfer. The registry MAY implicitly approve or reject requested transfers after a fixed amount of time. The requesting registrar MAY cancel a pending request, but the request to cancel the transfer MUST be sent before it has been explicitly approved or rejected by the current sponsoring registrar or it has been implicitly approved or rejected by the registry. Example: A registrar cancels a previously requested domain transfer: C:transfer C:-Approve:No C:EntityName:Domain C:DomainName:example.com C:. S:200 Command completed successfully S:. Hollenbeck & Veeramachaneni Informational [Page 5] Internet-Draft VeriSign RRP v2.0.0 January 25, 2002 2.3 Name Server IP Address Update Section 7 of [RFC2832] is updated to include support for name servers using IPv6 addresses. IPv6 addressing architecture is described in [IPv6]. This ABNF grammar supplements the grammar defined in RFC 2832. ; Lexical Tokens hexdigit = digit / %X41-46 / %x61-66 ; 0-9 / A-F / a-f doubleoctet = 1*4hexdigit docolon = doubleoctet colon colondo = colon doubleoctet ip-address = ip-address-v4 / ip-address-v6 ; ipv4 addresses ip-address-v4 = 1*3digit dot 1*3digit dot 1*3digit dot 1*3digit ip-address-v6 = ip-address-v6-standard / ip-address-v6-compressed ; Standard form of IPv6 addresses ; 8 hexdigit strings of length 1-4 separated by colons ; ; Eg: 10AA:0:0:00:8:800:200C:417A ip-address-v6-standard = doubleoctet 7colondo ; Compressed form of IPv6 addresses ; Runs of zero-value octets are represented by '::' ; ; Eg: ; :: ==> 0:0:0:0:0:0:0:0 ; ; 1:: ==> 1:0:0:0:0:0:0:0 ; 2:2:: ==> 2:2:0:0:0:0:0:0 ; 7:7:7:7:7:7:7:: ==> 7:7:7:7:7:7:7:0 ; ; ::1 ==> 0:0:0:0:0:0:0:1 ; ::2:2 ==> 0:0:0:0:0:0:2:2 ; ::7:7:7:7:7:7:7 ==> 0:7:7:7:7:7:7:7 ; ; E::1 ==> E:0:0:0:0:0:0:2 ; E::2:2 ==> E:0:0:0:0:0:2:2 ; E::6:6:6:6:6:6 ==> E:0:6:6:6:6:6:6 Hollenbeck & Veeramachaneni Informational [Page 6] Internet-Draft VeriSign RRP v2.0.0 January 25, 2002 ; ; E:E::1 ==> E:E:0:0:0:0:0:1 ; E:E::2:2 ==> E:E:0:0:0:0:2:2 ; E:E::5:5:5:5:5 ==> E:E:0:5:5:5:5:5 ; ; E:E:E::1 ==> E:E:E:0:0:0:0:1 ; E:E:E::2:2 ==> E:E:E:0:0:0:2:2 ; E:E:E::4:4:4:4 ==> E:E:E:0:4:4:4:4 ; ; E:E:E:E::1 ==> E:E:E:E:0:0:0:1 ; E:E:E:E::2:2 ==> E:E:E:E:0:0:2:2 ; E:E:E:E::3:3:3 ==> E:E:E:E:0:3:3:3 ; ; E:E:E:E:E::1 ==> E:E:E:E:E:E:0:6 ; E:E:E:E:E::2:2 ==> E:E:E:E:E:E:1:6 ; ; E:E:E:E:E:E::1 ==> E:E:E:E:E:E:0:1 ip-address-v6-compressed = colon colon ip-address-v6-compressed =/ 1*7docolon colon ip-address-v6-compressed =/ colon 1*7colondo ip-address-v6-compressed =/ docolon 1*6colondo ip-address-v6-compressed =/ 2docolon 1*5colondo ip-address-v6-compressed =/ 3docolon 1*4colondo ip-address-v6-compressed =/ 4docolon 1*3colondo ip-address-v6-compressed =/ 5docolon 1*2colondo ip-address-v6-compressed =/ 6docolon colondo Hollenbeck & Veeramachaneni Informational [Page 7] Internet-Draft VeriSign RRP v2.0.0 January 25, 2002 3. IANA Considerations This document does not introduce any new IANA considerations that are not already documented in [RFC2832]. 4. Internationalization Considerations This document does not introduce any new internationalization considerations that are not already documented in [RFC2832]. 5. Security Considerations This document does not introduce any new security considerations that are not already documented in [RFC2832]. 6. Acknowledgements The authors graciously acknowledge the contributions of John Brady, Matt Larson, Bill Manning, Erik Nordmark, and Steve Mahlstedt. 7. References Normative References: [IPv6] R. Hinden, S. Deering: "IP Version 6 Addressing Architecture", work in progress. [RFC2119] S. Bradner: "Key Words for Use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. Informative References: [RFC2832] S. Hollenbeck, M. Srivastava: "NSI Registry Registrar Protocol (RRP) Version 1.1.0", RFC 2832, May 2000. Hollenbeck & Veeramachaneni Informational [Page 8] Internet-Draft VeriSign RRP v2.0.0 January 25, 2002 8. Author's Address Scott Hollenbeck VeriSign Global Registry Services 21345 Ridgetop Circle Dulles, VA 20166-6503 USA shollenbeck@verisign.com Srikanth Veeramachaneni VeriSign Global Registry Services 21345 Ridgetop Circle Dulles, VA 20166-6503 USA sveerama@verisign.com A. Revisions From Previous Version (Note to RFC editor: please remove this section completely before publication as an RFC.) None, this is the initial version. Hollenbeck & Veeramachaneni Informational [Page 9] Internet-Draft VeriSign RRP v2.0.0 January 25, 2002 B. Full Copyright Statement Copyright (C) The Internet Society 2002. All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society. Hollenbeck & Veeramachaneni Informational [Page 10]