idnits 2.17.1 draft-hollenbeck-rfc2832bis-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 2 instances of lines with non-RFC3849-compliant IPv6 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 24, 2002) is 7976 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Downref: Normative reference to an Informational RFC: RFC 2832 (ref. '2') ** Obsolete normative reference: RFC 2373 (ref. '3') (Obsoleted by RFC 3513) Summary: 3 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group S. Hollenbeck 3 Internet-Draft S. Veeramachaneni 4 Expires: December 23, 2002 S. Yalamanchilli 5 VeriSign, Inc. 6 June 24, 2002 8 VeriSign Registry Registrar Protocol (RRP) Version 2.0.0 9 draft-hollenbeck-rfc2832bis-02.txt 11 Status of this Memo 13 This document is an Internet-Draft and is in full conformance with 14 all provisions of Section 10 of RFC2026. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at http:// 27 www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on December 23, 2002. 34 Copyright Notice 36 Copyright (C) The Internet Society (2002). All Rights Reserved. 38 Abstract 40 This document updates version 1.1.0 of the NSI Registry Registrar 41 Protocol specified in RFC 2832. The changes described in this 42 document combined with the base specification documented in RFC 2832 43 specify version 2.0.0 of the VeriSign Registry Registrar Protocol. 45 Conventions Used In This Document 47 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 48 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 49 document are to be interpreted as described in RFC 2119 [1]. 51 In examples, "C:" represents lines sent by a protocol client and "S:" 52 represents lines returned by a protocol server. 54 Discussion Venue 56 The authors welcome discussion and comments relating to the topics 57 presented in this document. Though direct comments to the authors 58 are welcome, public discussion is taking place on the "rrp@verisign- 59 grs.com" mailing list. To join the list, send a message to 60 "majordomo@verisign-grs.com" with the words "subscribe rrp" in the 61 body of the message. List archives [4] are available on the World 62 Wide Web. 64 Table of Contents 66 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 67 2. Protocol Updates . . . . . . . . . . . . . . . . . . . . . . . 3 68 2.1 Response Codes . . . . . . . . . . . . . . . . . . . . . . . . 3 69 2.2 TRANSFER Command Update . . . . . . . . . . . . . . . . . . . 4 70 2.3 IPv6 Name Server Addresses . . . . . . . . . . . . . . . . . . 5 71 3. Internationalization Considerations . . . . . . . . . . . . . 6 72 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 73 5. Security Considerations . . . . . . . . . . . . . . . . . . . 7 74 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 75 Normative References . . . . . . . . . . . . . . . . . . . . . 7 76 Informative References . . . . . . . . . . . . . . . . . . . . 7 77 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 7 78 A. Appendix A: Change History . . . . . . . . . . . . . . . . . . 8 79 Full Copyright Statement . . . . . . . . . . . . . . . . . . . 9 81 1. Introduction 83 The Network Solutions, Inc. (NSI) Registry Registrar Protocol (RRP) 84 was developed by NSI in 1998 and 1999 to allow multiple registrars to 85 provide second level Internet domain name registration services in 86 the top level domains (TLDs) administered by the NSI TLD registry. 87 Version 1.1.0 of the NSI RRP was published as Informational RFC 2832 88 [2] in May 2000. This document describes changes to RFC 2832 that 89 specify version 2.0.0 of the protocol. 91 2. Protocol Updates 93 This specification describes several modifications to RFC 2832 [2]: 94 two new response codes have been added, domain TRANSFER command 95 processing is updated to allow a client to cancel a requested domain 96 transfer, and support for IPv6 name server addresses is added. 98 2.1 Response Codes 100 Section 5.1 of RFC 2832 [2] is updated to include two additional 101 error response codes. 103 510 Invalid encoding 105 The value of a domain name or name server entity contains an invalid 106 ASCII compatible encoding used to represent an internationalized 107 domain or host name. The encoding is checked and verified in two 108 situations: when registering an internationalized domain name or name 109 server name, and when changing the name of a name server and the new 110 name of the server is internationalized. 112 Section 5.2 of RFC 2832 [2] is updated to include the addition of 113 response code 510 to the possible error values returned from the ADD 114 command: 116 Command: ADD 117 Success: 200, 220 118 Failure: 420, 421, 500, 502, 503, 504, 505, 507, 508, 510, 520, 531, 119 535, 540, 541, 545, 546, 547, 549, 550, 554 121 557 Name server locked 123 An attempt has been made to modify or delete a name server that is 124 hosting a TLD in the root zone. Modifications to the root zone can 125 only be made with the approval of the U.S. Department of Commerce 126 and IANA, so if the registrar absolutely needs to modify or delete 127 such a name server the action needs to be coordinated through the 128 registry operator using an out-of-band communications channel. 130 Section 5.2 of RFC 2832 [2] is updated to include the addition of 131 response code 557 to the possible error values returned from the DEL 132 and MOD commands: 134 Command: DEL 135 Success: 200, 220 136 Failure: 420, 421, 500, 502, 503, 504, 505, 507, 508, 520, 531, 532, 137 533, 541, 544, 545, 547, 549, 551, 552, 553, 557 139 Command: MOD 140 Success: 200, 220 141 Failure: 420, 421, 500, 502, 503, 504, 505, 507, 508, 510, 520, 531, 142 535, 540, 541, 542, 543, 544, 545, 547, 549, 550, 551, 552, 553, 557 144 2.2 TRANSFER Command Update 146 Section 4.3.10 of RFC 2832 [2] is updated to include an additional 147 TRANSFER command processing option. 149 Old text: 151 Authorized User: All registrars MAY use the TRANSFER command to 152 request transfer of registration service authority to the requesting 153 registrar. Only the current sponsoring registrar of a domain name 154 may explicitly approve or reject a requested transfer. The registry 155 MAY implicitly approve or reject requested transfers after a fixed 156 amount of time. 158 New text: 160 Authorized User: All registrars MAY use the TRANSFER command to 161 request transfer of registration service authority to the requesting 162 registrar. Only the current sponsoring registrar of a domain name 163 may explicitly approve a requested transfer. The current sponsoring 164 registrar MAY explicitly reject a requested transfer. The registry 165 MAY implicitly approve or reject requested transfers after a fixed 166 amount of time. The requesting registrar MAY cancel a pending 167 request, but the request to cancel the transfer MUST be sent before 168 it has been explicitly approved or rejected by the current sponsoring 169 registrar or it has been implicitly approved or rejected by the 170 registry. 172 Example: 174 A registrar cancels a previously requested domain transfer: 176 C:transfer 177 C:-Approve:No 178 C:EntityName:Domain 179 C:DomainName:example.com 180 C:. 181 S:200 Command completed successfully 182 S:. 184 2.3 IPv6 Name Server Addresses 186 Section 7 of RFC 2832 [2] is updated to include support for name 187 servers using IPv6 addresses. IPv6 addressing architecture is 188 described in RFC 2373 [3]. This ABNF grammar supplements the grammar 189 defined in RFC 2832. 191 ; Lexical Tokens 193 hexdigit = digit / %X41-46 / %x61-66 ; 0-9 / A-F / a-f 195 doubleoctet = 1*4hexdigit 197 docolon = doubleoctet colon 199 colondo = colon doubleoctet 201 ip-address = ip-address-v4 / ip-address-v6 203 ; ipv4 addresses 204 ip-address-v4 = 1*3digit dot 1*3digit dot 1*3digit dot 1*3digit 206 ip-address-v6 = ip-address-v6-standard / ip-address-v6-compressed 207 ; Standard form of IPv6 addresses 208 ; 8 hexdigit strings of length 1-4 separated by colons 209 ; 210 ; Eg: 10AA:0:0:00:8:800:200C:417A 212 ip-address-v6-standard = doubleoctet 7colondo 214 ; Compressed form of IPv6 addresses 215 ; Runs of zero-value octets are represented by '::' 216 ; 217 ; Examples: 218 ; :: ==> 0:0:0:0:0:0:0:0 219 ; 220 ; 1:: ==> 1:0:0:0:0:0:0:0 221 ; 2:2:: ==> 2:2:0:0:0:0:0:0 222 ; 7:7:7:7:7:7:7:: ==> 7:7:7:7:7:7:7:0 223 ; 224 ; ::1 ==> 0:0:0:0:0:0:0:1 225 ; ::2:2 ==> 0:0:0:0:0:0:2:2 226 ; ::7:7:7:7:7:7:7 ==> 0:7:7:7:7:7:7:7 227 ; 228 ; E::1 ==> E:0:0:0:0:0:0:1 229 ; E::2:2 ==> E:0:0:0:0:0:2:2 230 ; E::6:6:6:6:6:6 ==> E:0:6:6:6:6:6:6 231 ; 232 ; E:E::1 ==> E:E:0:0:0:0:0:1 233 ; E:E::2:2 ==> E:E:0:0:0:0:2:2 234 ; E:E::5:5:5:5:5 ==> E:E:0:5:5:5:5:5 235 ; 236 ; E:E:E::1 ==> E:E:E:0:0:0:0:1 237 ; E:E:E::2:2 ==> E:E:E:0:0:0:2:2 238 ; E:E:E::4:4:4:4 ==> E:E:E:0:4:4:4:4 239 ; 240 ; E:E:E:E::1 ==> E:E:E:E:0:0:0:1 241 ; E:E:E:E::2:2 ==> E:E:E:E:0:0:2:2 242 ; E:E:E:E::3:3:3 ==> E:E:E:E:0:3:3:3 243 ; 244 ; E:E:E:E:E::1 ==> E:E:E:E:E:0:0:1 245 ; E:E:E:E:E::2:2 ==> E:E:E:E:E:0:2:2 246 ; 247 ; E:E:E:E:E:E::1 ==> E:E:E:E:E:E:0:1 249 ip-address-v6-compressed = colon colon 250 ip-address-v6-compressed =/ 1*7docolon colon 251 ip-address-v6-compressed =/ colon 1*7colondo 252 ip-address-v6-compressed =/ docolon 1*6colondo 253 ip-address-v6-compressed =/ 2docolon 1*5colondo 254 ip-address-v6-compressed =/ 3docolon 1*4colondo 255 ip-address-v6-compressed =/ 4docolon 1*3colondo 256 ip-address-v6-compressed =/ 5docolon 1*2colondo 257 ip-address-v6-compressed =/ 6docolon colondo 259 3. Internationalization Considerations 261 This document does not introduce any new internationalization 262 considerations that are not already documented in RFC 2832 [2]. 264 4. IANA Considerations 266 This document does not introduce any new IANA considerations that are 267 not already documented in RFC 2832 [2]. 269 5. Security Considerations 271 This document does not introduce any new security considerations that 272 are not already documented in RFC 2832 [2]. 274 6. Acknowledgements 276 The authors graciously acknowledge the contributions of John Brady, 277 Matt Larson, Bill Manning, Erik Nordmark, and Steve Mahlstedt. 279 Normative References 281 [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement 282 Levels", BCP 14, RFC 2119, March 1997. 284 [2] Hollenbeck, S. and M. Srivastava, "NSI Registry Registrar 285 Protocol (RRP) Version 1.1.0", RFC 2832, May 2000. 287 [3] Hinden, R. and S. Deering, "IP Version 6 Addressing 288 Architecture", RFC 2373, July 1998. 290 Informative References 292 URIs 294 [4] 296 Authors' Addresses 298 Scott Hollenbeck 299 VeriSign, Inc. 300 21345 Ridgetop Circle 301 Dulles, VA 20166-6503 302 US 304 EMail: shollenbeck@verisign.com 306 Srikanth Veeramachaneni 307 VeriSign, Inc. 308 21345 Ridgetop Circle 309 Dulles, VA 20166-6503 310 US 312 EMail: sveerama@verisign.com 313 Suresh Yalamanchilli 314 VeriSign, Inc. 315 21345 Ridgetop Circle 316 Dulles, VA 20166-6503 317 US 319 EMail: syalamanchilli@verisign.com 321 Appendix A. Appendix A: Change History 323 (Note to RFC editor: please remove this section completely before 324 publication as an RFC.) 326 The following changes were made to produce version -02 from -01: 328 o Removed entity status section 2.1 and references it contained. 330 o Changed the description of response code 557 and removed updated 331 descriptions of codes 551, 552, and 533. 333 Full Copyright Statement 335 Copyright (C) The Internet Society (2002). All Rights Reserved. 337 This document and translations of it may be copied and furnished to 338 others, and derivative works that comment on or otherwise explain it 339 or assist in its implementation may be prepared, copied, published 340 and distributed, in whole or in part, without restriction of any 341 kind, provided that the above copyright notice and this paragraph are 342 included on all such copies and derivative works. However, this 343 document itself may not be modified in any way, such as by removing 344 the copyright notice or references to the Internet Society or other 345 Internet organizations, except as needed for the purpose of 346 developing Internet standards in which case the procedures for 347 copyrights defined in the Internet Standards process must be 348 followed, or as required to translate it into languages other than 349 English. 351 The limited permissions granted above are perpetual and will not be 352 revoked by the Internet Society or its successors or assigns. 354 This document and the information contained herein is provided on an 355 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 356 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 357 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 358 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 359 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 361 Acknowledgement 363 Funding for the RFC Editor function is currently provided by the 364 Internet Society.