idnits 2.17.1 draft-hollenbeck-rfc2832bis-03.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. == The 'Updates: ' line in the draft header should list only the _numbers_ of the RFCs which will be updated by this document (if approved); it should not include the word 'RFC' in the list. -- The draft header indicates that this document updates RFC2832, but the abstract doesn't seem to directly say this. It does mention RFC2832 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year (Using the creation date from RFC2832, updated by this document, for RFC5378 checks: 1999-12-21) -- 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 (September 18, 2002) is 7884 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) ** Obsolete normative reference: RFC 2234 (ref. '4') (Obsoleted by RFC 4234) Summary: 4 errors (**), 0 flaws (~~), 4 warnings (==), 3 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 Updates: RFC 2832 S. Yalamanchilli 5 Expires: March 19, 2003 VeriSign, Inc. 6 September 18, 2002 8 VeriSign Registry Registrar Protocol (RRP) Version 2.0.0 9 draft-hollenbeck-rfc2832bis-03.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 March 19, 2003. 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 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 2. Protocol Updates . . . . . . . . . . . . . . . . . . . . . . . 3 58 2.1 Response Codes . . . . . . . . . . . . . . . . . . . . . . . . 3 59 2.2 TRANSFER Command Update . . . . . . . . . . . . . . . . . . . 4 60 2.3 IPv6 Name Server Addresses . . . . . . . . . . . . . . . . . . 5 61 3. Internationalization Considerations . . . . . . . . . . . . . 6 62 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 63 5. Security Considerations . . . . . . . . . . . . . . . . . . . 7 64 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 65 Normative References . . . . . . . . . . . . . . . . . . . . . 7 66 Informative References . . . . . . . . . . . . . . . . . . . . 7 67 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 7 68 Full Copyright Statement . . . . . . . . . . . . . . . . . . . 9 70 1. Introduction 72 The Network Solutions, Inc. (NSI) Registry Registrar Protocol (RRP) 73 was developed by NSI in 1998 and 1999 to allow multiple registrars to 74 provide second level Internet domain name registration services in 75 the top level domains (TLDs) administered by the NSI TLD registry. 76 Version 1.1.0 of the NSI RRP was published as Informational RFC 2832 77 [2] in May 2000. This document describes changes to RFC 2832 that 78 specify version 2.0.0 of the protocol. 80 2. Protocol Updates 82 This specification describes several modifications to RFC 2832 [2]: 83 two new response codes have been added, domain TRANSFER command 84 processing is updated to allow a client to cancel a requested domain 85 transfer, and support for IPv6 name server addresses is added. 87 2.1 Response Codes 89 Section 5.1 of RFC 2832 [2] is updated to include two additional 90 error response codes. 92 510 Invalid encoding 94 The value of a domain name or name server entity contains an invalid 95 ASCII compatible encoding used to represent an internationalized 96 domain or host name. The encoding is checked and verified in two 97 situations: when registering an internationalized domain name or name 98 server name, and when changing the name of a name server and the new 99 name of the server is internationalized. 101 Section 5.2 of RFC 2832 [2] is updated to include the addition of 102 response code 510 to the possible error values returned from the ADD 103 command: 105 Command: ADD 106 Success: 200, 220 107 Failure: 420, 421, 500, 502, 503, 504, 505, 507, 508, 510, 520, 531, 108 535, 540, 541, 545, 546, 547, 549, 550, 554 110 557 Name server locked 112 An attempt has been made to modify or delete a name server that is 113 hosting a TLD in the root zone. Modifications to the root zone can 114 only be made with the approval of the U.S. Department of Commerce 115 and IANA, so if the registrar absolutely needs to modify or delete 116 such a name server the action needs to be coordinated through the 117 registry operator using an out-of-band communications channel. 119 Section 5.2 of RFC 2832 [2] is updated to include the addition of 120 response code 557 to the possible error values returned from the DEL 121 and MOD commands: 123 Command: DEL 124 Success: 200, 220 125 Failure: 420, 421, 500, 502, 503, 504, 505, 507, 508, 520, 531, 532, 126 533, 541, 544, 545, 547, 549, 551, 552, 553, 557 128 Command: MOD 129 Success: 200, 220 130 Failure: 420, 421, 500, 502, 503, 504, 505, 507, 508, 510, 520, 531, 131 535, 540, 541, 542, 543, 544, 545, 547, 549, 550, 551, 552, 553, 557 133 2.2 TRANSFER Command Update 135 Section 4.3.10 of RFC 2832 [2] is updated to include an additional 136 TRANSFER command processing option. 138 Old text: 140 Authorized User: All registrars MAY use the TRANSFER command to 141 request transfer of registration service authority to the requesting 142 registrar. Only the current sponsoring registrar of a domain name 143 may explicitly approve or reject a requested transfer. The registry 144 MAY implicitly approve or reject requested transfers after a fixed 145 amount of time. 147 New text: 149 Authorized User: All registrars MAY use the TRANSFER command to 150 request transfer of registration service authority to the requesting 151 registrar. Only the current sponsoring registrar of a domain name 152 may explicitly approve a requested transfer. The current sponsoring 153 registrar MAY explicitly reject a requested transfer. The registry 154 MAY implicitly approve or reject requested transfers after a fixed 155 amount of time. The requesting registrar MAY cancel a pending 156 request, but the request to cancel the transfer MUST be sent before 157 it has been explicitly approved or rejected by the current sponsoring 158 registrar or it has been implicitly approved or rejected by the 159 registry. 161 Example: 163 A registrar cancels a previously requested domain transfer: 165 C:transfer 166 C:-Approve:No 167 C:EntityName:Domain 168 C:DomainName:example.com 169 C:. 170 S:200 Command completed successfully 171 S:. 173 2.3 IPv6 Name Server Addresses 175 Section 7 of RFC 2832 [2] is updated to include support for name 176 servers using IPv6 addresses. IPv6 addressing architecture is 177 described in RFC 2373 [3]. This ABNF [4] grammar supplements the 178 grammar defined in RFC 2832. 180 ; Lexical Tokens 182 hexdigit = digit / %X41-46 / %x61-66 ; 0-9 / A-F / a-f 184 doubleoctet = 1*4hexdigit 186 docolon = doubleoctet colon 188 colondo = colon doubleoctet 190 ip-address = ip-address-v4 / ip-address-v6 192 ; ipv4 addresses 193 ip-address-v4 = 1*3digit dot 1*3digit dot 1*3digit dot 1*3digit 195 ip-address-v6 = ip-address-v6-standard / ip-address-v6-compressed 196 ; Standard form of IPv6 addresses 197 ; 8 hexdigit strings of length 1-4 separated by colons 198 ; 199 ; Eg: 10AA:0:0:00:8:800:200C:417A 201 ip-address-v6-standard = doubleoctet 7colondo 203 ; Compressed form of IPv6 addresses 204 ; Runs of zero-value octets are represented by '::' 205 ; 206 ; Examples: 207 ; :: ==> 0:0:0:0:0:0:0:0 208 ; 209 ; 1:: ==> 1:0:0:0:0:0:0:0 210 ; 2:2:: ==> 2:2:0:0:0:0:0:0 211 ; 7:7:7:7:7:7:7:: ==> 7:7:7:7:7:7:7:0 212 ; 213 ; ::1 ==> 0:0:0:0:0:0:0:1 214 ; ::2:2 ==> 0:0:0:0:0:0:2:2 215 ; ::7:7:7:7:7:7:7 ==> 0:7:7:7:7:7:7:7 216 ; 217 ; E::1 ==> E:0:0:0:0:0:0:1 218 ; E::2:2 ==> E:0:0:0:0:0:2:2 219 ; E::6:6:6:6:6:6 ==> E:0:6:6:6:6:6:6 220 ; 221 ; E:E::1 ==> E:E:0:0:0:0:0:1 222 ; E:E::2:2 ==> E:E:0:0:0:0:2:2 223 ; E:E::5:5:5:5:5 ==> E:E:0:5:5:5:5:5 224 ; 225 ; E:E:E::1 ==> E:E:E:0:0:0:0:1 226 ; E:E:E::2:2 ==> E:E:E:0:0:0:2:2 227 ; E:E:E::4:4:4:4 ==> E:E:E:0:4:4:4:4 228 ; 229 ; E:E:E:E::1 ==> E:E:E:E:0:0:0:1 230 ; E:E:E:E::2:2 ==> E:E:E:E:0:0:2:2 231 ; E:E:E:E::3:3:3 ==> E:E:E:E:0:3:3:3 232 ; 233 ; E:E:E:E:E::1 ==> E:E:E:E:E:0:0:1 234 ; E:E:E:E:E::2:2 ==> E:E:E:E:E:0:2:2 235 ; 236 ; E:E:E:E:E:E::1 ==> E:E:E:E:E:E:0:1 238 ip-address-v6-compressed = colon colon 239 ip-address-v6-compressed =/ 1*7docolon colon 240 ip-address-v6-compressed =/ colon 1*7colondo 241 ip-address-v6-compressed =/ docolon 1*6colondo 242 ip-address-v6-compressed =/ 2docolon 1*5colondo 243 ip-address-v6-compressed =/ 3docolon 1*4colondo 244 ip-address-v6-compressed =/ 4docolon 1*3colondo 245 ip-address-v6-compressed =/ 5docolon 1*2colondo 246 ip-address-v6-compressed =/ 6docolon colondo 248 3. Internationalization Considerations 250 This document does not introduce any new internationalization 251 considerations that are not already documented in RFC 2832 [2]. 253 4. IANA Considerations 255 This document does not introduce any new IANA considerations that are 256 not already documented in RFC 2832 [2]. 258 5. Security Considerations 260 This document does not introduce any new security considerations that 261 are not already documented in RFC 2832 [2]. 263 6. Acknowledgements 265 The authors graciously acknowledge the contributions of John Brady, 266 Matt Larson, Bill Manning, Erik Nordmark, and Steve Mahlstedt. 268 Normative References 270 [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement 271 Levels", BCP 14, RFC 2119, March 1997. 273 [2] Hollenbeck, S. and M. Srivastava, "NSI Registry Registrar 274 Protocol (RRP) Version 1.1.0", RFC 2832, May 2000. 276 [3] Hinden, R. and S. Deering, "IP Version 6 Addressing 277 Architecture", RFC 2373, July 1998. 279 [4] Crocker, D. and P. Overell, "Augmented BNF for Syntax 280 Specifications: ABNF", RFC 2234, November 1997. 282 Informative References 284 Authors' Addresses 286 Scott Hollenbeck 287 VeriSign, Inc. 288 21345 Ridgetop Circle 289 Dulles, VA 20166-6503 290 US 292 EMail: shollenbeck@verisign.com 294 Srikanth Veeramachaneni 295 VeriSign, Inc. 296 21345 Ridgetop Circle 297 Dulles, VA 20166-6503 298 US 300 EMail: sveerama@verisign.com 301 Suresh Yalamanchilli 302 VeriSign, Inc. 303 21345 Ridgetop Circle 304 Dulles, VA 20166-6503 305 US 307 EMail: syalamanchilli@verisign.com 309 Full Copyright Statement 311 Copyright (C) The Internet Society (2002). All Rights Reserved. 313 This document and translations of it may be copied and furnished to 314 others, and derivative works that comment on or otherwise explain it 315 or assist in its implementation may be prepared, copied, published 316 and distributed, in whole or in part, without restriction of any 317 kind, provided that the above copyright notice and this paragraph are 318 included on all such copies and derivative works. However, this 319 document itself may not be modified in any way, such as by removing 320 the copyright notice or references to the Internet Society or other 321 Internet organizations, except as needed for the purpose of 322 developing Internet standards in which case the procedures for 323 copyrights defined in the Internet Standards process must be 324 followed, or as required to translate it into languages other than 325 English. 327 The limited permissions granted above are perpetual and will not be 328 revoked by the Internet Society or its successors or assigns. 330 This document and the information contained herein is provided on an 331 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 332 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 333 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 334 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 335 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 337 Acknowledgement 339 Funding for the RFC Editor function is currently provided by the 340 Internet Society.