idnits 2.17.1 draft-hollenbeck-rfc2832bis-00.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 : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. == 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.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. 'IPv6' ** Downref: Normative reference to an Informational RFC: RFC 2832 Summary: 3 errors (**), 0 flaws (~~), 3 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force S. Hollenbeck 3 Internet-Draft S. Veeramachaneni 4 VeriSign, Inc. 5 January 25, 2002 Expires: July 25, 2002 7 VeriSign Registry Registrar Protocol (RRP) Version 2.0.0 8 10 Status of this Memo 12 This document is an Internet-Draft and is in full conformance with all 13 provisions of Section 10 of RFC2026. 15 Internet-Drafts are working documents of the Internet Engineering Task 16 Force (IETF), its areas, and its working groups. Note that other 17 groups may also distribute working documents as Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet-Drafts as reference 22 material or to cite them other than as "work in progress". 24 The list of current Internet-Drafts can be accessed at 25 http://www.ietf.org/ietf/1id-abstracts.txt 27 The list of Internet-Draft Shadow Directories can be accessed at 28 http://www.ietf.org/shadow.html. 30 Abstract 32 This document updates version 1.1.0 of the NSI Registry Registrar 33 Protocol specified in RFC 2832. The changes described in this 34 document combined with the base specification documented in RFC 2832 35 specify version 2.0.0 of the VeriSign Registry Registrar Protocol. 37 Conventions Used In This Document 39 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 40 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 41 document are to be interpreted as described in [RFC2119]. 43 In examples, "C:" represents lines sent by a protocol client and "S:" 44 represents lines returned by a protocol server. 46 Table of Contents 48 1. Introduction ................................................. 3 49 2. Protocol Updates ............................................. 4 50 2.1 Response Code Update ........................................ 4 51 2.2 TRANSFER Command Update ..................................... 5 52 2.3 Name Server IP Address Update ............................... 6 53 3. IANA Considerations .......................................... 8 54 4. Internationalization Considerations .......................... 8 55 5. Security Considerations ...................................... 8 56 6. Acknowledgements ............................................. 8 57 7. References ................................................... 8 58 8. Author's Address ............................................. 9 59 A. Revisions From Previous Version .............................. 9 60 B. Full Copyright Statement ..................................... 10 62 1. Introduction 64 The Network Solutions, Inc. (NSI) Registry Registrar Protocol (RRP) 65 was developed by NSI in 1998 and 1999 to allow multiple registrars to 66 provide second level Internet domain name registration services in the 67 top level domains (TLDs) administered by the NSI TLD registry. 68 Version 1.1.0 of the NSI RRP was published as Informational RFC 2832 69 [RFC2832] in May 2000. This document describes changes to RFC 2832 70 that specify version 2.0.0 of the protocol. 72 NSI was acquired by VeriSign, Inc. in June 2000. The protocol name 73 change from "NSI RRP" to "VeriSign RRP" is a reflection of that 74 acquisition. 76 2. Protocol Updates 78 This specification describes three modifications to [RFC2832]: a new 79 error response code is defined, domain TRANSFER command processing is 80 updated to allow a client to cancel a requested domain transfer, and 81 support for IPv6 name server addresses is added. 83 2.1 Response Code Update 85 Section 5.1 of [RFC2832] is updated to include an additional error 86 response code: 88 557 Name server locked 90 This response indicates that a name server has been locked by the 91 registry. A name server cannot be modified or deleted while it is 92 locked. 94 Section 5.2 of [RFC2832] is updated to include the addition of 95 response code 557 to the possible error values returned from the DEL 96 and MOD commands: 98 Command: DEL 99 Success: 200, 220 100 Failure: 420, 421, 500, 502, 503, 504, 505, 507, 508, 520, 531, 532, 101 533, 541, 544, 545, 547, 549, 551, 552, 553, 557 103 Command: MOD 104 Success: 200, 220 105 Failure: 420, 421, 500, 502, 503, 504, 505, 507, 508, 520, 531, 535, 106 540, 541, 542, 543, 544, 545, 547, 549, 550, 551, 552, 553, 557 108 2.2 TRANSFER Command Update 110 Section 4.3.10 of [RFC2832] is updated to include an additional 111 TRANSFER command processing option. 113 Old text: 115 Authorized User: All registrars MAY use the TRANSFER command to 116 request transfer of registration service authority to the requesting 117 registrar. Only the current sponsoring registrar of a domain name may 118 explicitly approve or reject a requested transfer. The registry MAY 119 implicitly approve or reject requested transfers after a fixed amount 120 of time. 122 New text: 124 Authorized User: All registrars MAY use the TRANSFER command to 125 request transfer of registration service authority to the requesting 126 registrar. Only the current sponsoring registrar of a domain name may 127 explicitly approve a requested transfer. The current sponsoring 128 registrar MAY explicitly reject a requested transfer. The registry MAY 129 implicitly approve or reject requested transfers after a fixed amount 130 of time. The requesting registrar MAY cancel a pending request, but 131 the request to cancel the transfer MUST be sent before it has been 132 explicitly approved or rejected by the current sponsoring registrar or 133 it has been implicitly approved or rejected by the registry. 135 Example: 137 A registrar cancels a previously requested domain transfer: 139 C:transfer 140 C:-Approve:No 141 C:EntityName:Domain 142 C:DomainName:example.com 143 C:. 144 S:200 Command completed successfully 145 S:. 147 2.3 Name Server IP Address Update 149 Section 7 of [RFC2832] is updated to include support for name servers 150 using IPv6 addresses. IPv6 addressing architecture is described in 151 [IPv6]. This ABNF grammar supplements the grammar defined in RFC 152 2832. 154 ; Lexical Tokens 156 hexdigit = digit / %X41-46 / %x61-66 ; 0-9 / A-F / a-f 158 doubleoctet = 1*4hexdigit 160 docolon = doubleoctet colon 162 colondo = colon doubleoctet 164 ip-address = ip-address-v4 / ip-address-v6 166 ; ipv4 addresses 167 ip-address-v4 = 1*3digit dot 1*3digit dot 1*3digit dot 1*3digit 169 ip-address-v6 = ip-address-v6-standard / ip-address-v6-compressed 171 ; Standard form of IPv6 addresses 172 ; 8 hexdigit strings of length 1-4 separated by colons 173 ; 174 ; Eg: 10AA:0:0:00:8:800:200C:417A 176 ip-address-v6-standard = doubleoctet 7colondo 178 ; Compressed form of IPv6 addresses 179 ; Runs of zero-value octets are represented by '::' 180 ; 181 ; Eg: 182 ; :: ==> 0:0:0:0:0:0:0:0 183 ; 184 ; 1:: ==> 1:0:0:0:0:0:0:0 185 ; 2:2:: ==> 2:2:0:0:0:0:0:0 186 ; 7:7:7:7:7:7:7:: ==> 7:7:7:7:7:7:7:0 187 ; 188 ; ::1 ==> 0:0:0:0:0:0:0:1 189 ; ::2:2 ==> 0:0:0:0:0:0:2:2 190 ; ::7:7:7:7:7:7:7 ==> 0:7:7:7:7:7:7:7 191 ; 192 ; E::1 ==> E:0:0:0:0:0:0:2 193 ; E::2:2 ==> E:0:0:0:0:0:2:2 194 ; E::6:6:6:6:6:6 ==> E:0:6:6:6:6:6:6 195 ; 196 ; E:E::1 ==> E:E:0:0:0:0:0:1 197 ; E:E::2:2 ==> E:E:0:0:0:0:2:2 198 ; E:E::5:5:5:5:5 ==> E:E:0:5:5:5:5:5 199 ; 200 ; E:E:E::1 ==> E:E:E:0:0:0:0:1 201 ; E:E:E::2:2 ==> E:E:E:0:0:0:2:2 202 ; E:E:E::4:4:4:4 ==> E:E:E:0:4:4:4:4 203 ; 204 ; E:E:E:E::1 ==> E:E:E:E:0:0:0:1 205 ; E:E:E:E::2:2 ==> E:E:E:E:0:0:2:2 206 ; E:E:E:E::3:3:3 ==> E:E:E:E:0:3:3:3 207 ; 208 ; E:E:E:E:E::1 ==> E:E:E:E:E:E:0:6 209 ; E:E:E:E:E::2:2 ==> E:E:E:E:E:E:1:6 210 ; 211 ; E:E:E:E:E:E::1 ==> E:E:E:E:E:E:0:1 213 ip-address-v6-compressed = colon colon 214 ip-address-v6-compressed =/ 1*7docolon colon 215 ip-address-v6-compressed =/ colon 1*7colondo 216 ip-address-v6-compressed =/ docolon 1*6colondo 217 ip-address-v6-compressed =/ 2docolon 1*5colondo 218 ip-address-v6-compressed =/ 3docolon 1*4colondo 219 ip-address-v6-compressed =/ 4docolon 1*3colondo 220 ip-address-v6-compressed =/ 5docolon 1*2colondo 221 ip-address-v6-compressed =/ 6docolon colondo 223 3. IANA Considerations 225 This document does not introduce any new IANA considerations that are 226 not already documented in [RFC2832]. 228 4. Internationalization Considerations 230 This document does not introduce any new internationalization 231 considerations that are not already documented in [RFC2832]. 233 5. Security Considerations 235 This document does not introduce any new security considerations that 236 are not already documented in [RFC2832]. 238 6. Acknowledgements 240 The authors graciously acknowledge the contributions of John Brady, 241 Matt Larson, Bill Manning, Erik Nordmark, and Steve Mahlstedt. 243 7. References 245 Normative References: 247 [IPv6] R. Hinden, S. Deering: "IP Version 6 Addressing Architecture", 248 work in progress. 250 [RFC2119] S. Bradner: "Key Words for Use in RFCs to Indicate 251 Requirement Levels", BCP 14, RFC 2119, March 1997. 253 Informative References: 255 [RFC2832] S. Hollenbeck, M. Srivastava: "NSI Registry Registrar 256 Protocol (RRP) Version 1.1.0", RFC 2832, May 2000. 258 8. Author's Address 260 Scott Hollenbeck 261 VeriSign Global Registry Services 262 21345 Ridgetop Circle 263 Dulles, VA 20166-6503 264 USA 265 shollenbeck@verisign.com 267 Srikanth Veeramachaneni 268 VeriSign Global Registry Services 269 21345 Ridgetop Circle 270 Dulles, VA 20166-6503 271 USA 272 sveerama@verisign.com 274 A. Revisions From Previous Version 276 (Note to RFC editor: please remove this section completely before 277 publication as an RFC.) 279 None, this is the initial version. 281 B. Full Copyright Statement 283 Copyright (C) The Internet Society 2002. All Rights Reserved. 285 This document and translations of it may be copied and furnished to 286 others, and derivative works that comment on or otherwise explain it 287 or assist in its implementation may be prepared, copied, published and 288 distributed, in whole or in part, without restriction of any kind, 289 provided that the above copyright notice and this paragraph are 290 included on all such copies and derivative works. However, this 291 document itself may not be modified in any way, such as by removing 292 the copyright notice or references to the Internet Society or other 293 Internet organizations, except as needed for the purpose of developing 294 Internet standards in which case the procedures for copyrights defined 295 in the Internet Standards process must be followed, or as required to 296 translate it into languages other than English. 298 The limited permissions granted above are perpetual and will not be 299 revoked by the Internet Society or its successors or assigns. 301 This document and the information contained herein is provided on an 302 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 303 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 304 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN 305 WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 306 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 308 Acknowledgement 310 Funding for the RFC Editor function is currently provided by the 311 Internet Society.