1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
|
<pre>Network Working Group S. Hollenbeck
Request for Comments: 3632 S. Veeramachaneni
Updates: <a href="./rfc2832">2832</a> S. Yalamanchilli
Category: Informational VeriSign, Inc.
November 2003
<span class="h1">VeriSign Registry Registrar Protocol (RRP) Version 2.0.0</span>
Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract
This document updates version 1.1.0 of the Network Solutions Inc.
(NSI) Registry Registrar Protocol (RRP) specified in <a href="./rfc2832">RFC 2832</a>. The
changes described in this document combined with the base
specification documented in <a href="./rfc2832">RFC 2832</a> specify version 2.0.0 of the
VeriSign Registry Registrar Protocol.
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a>. Protocol Updates . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2.1">2.1</a>. Response Codes . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2.2">2.2</a>. TRANSFER Command Update . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2.3">2.3</a>. IPv6 Name Server Addresses . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3">3</a>. Internationalization Considerations . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-4">4</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-5">5</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-6">6</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-7">7</a>. Normative References . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-8">8</a>. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-9">9</a>. Full Copyright Statement . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<span class="grey">Hollenbeck, et al. Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc3632">RFC 3632</a> VeriSign RRP v2.0.0 November 2003</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
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 <a href="./rfc2832">RFC 2832</a>
[<a href="#ref-2" title=""NSI Registry Registrar Protocol (RRP) Version 1.1.0"">2</a>] in May 2000. This document describes changes to <a href="./rfc2832">RFC 2832</a> that
specify version 2.0.0 of the 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 <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC</a>
<a href="./rfc2119">2119</a> [<a href="#ref-1" title=""Key words for use in RFCs to Indicate Requirement Levels"">1</a>].
In examples, "C:" represents lines sent by a protocol client and
"S:" represents lines returned by a protocol server.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Protocol Updates</span>
This specification describes several modifications to <a href="./rfc2832">RFC 2832</a> [<a href="#ref-2" title=""NSI Registry Registrar Protocol (RRP) Version 1.1.0"">2</a>]:
two new response codes have been added, domain TRANSFER command
processing has been updated to allow a client to cancel a requested
domain transfer, and support for IPv6 name server addresses has been
added.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Response Codes</span>
<a href="./rfc2832#section-5.1">Section 5.1 of RFC 2832</a> [<a href="#ref-2" title=""NSI Registry Registrar Protocol (RRP) Version 1.1.0"">2</a>] has been updated to include two
additional error response codes.
510 Invalid encoding
The value of a domain name or name server entity contains invalid
ASCII compatible encoding used to represent an internationalized
domain or host name. The encoding is checked and verified in two
situations: when registering an internationalized domain name or name
server name, and when changing the name of a name server and the new
name of the server is internationalized.
<span class="grey">Hollenbeck, et al. Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc3632">RFC 3632</a> VeriSign RRP v2.0.0 November 2003</span>
<a href="./rfc2832#section-5.2">Section 5.2 of RFC 2832</a> [<a href="#ref-2" title=""NSI Registry Registrar Protocol (RRP) Version 1.1.0"">2</a>] has been updated to include response code
510 as a possible error value returned from the ADD command:
Command: ADD
Success: 200, 220
Failure: 420, 421, 500, 502, 503, 504, 505, 507, 508, 510, 520, 531,
535, 540, 541, 545, 546, 547, 549, 550, 554
557 Name server locked
An attempt has been made to modify or delete a name server that is
hosting a TLD in the root zone. Modifications to the root zone can
only be made with the approval of the U.S. Department of Commerce and
IANA, so if the registrar absolutely needs to modify or delete such a
name server, the action needs to be coordinated through the registry
operator using an out-of-band communications channel.
<a href="./rfc2832#section-5.2">Section 5.2 of RFC 2832</a> [<a href="#ref-2" title=""NSI Registry Registrar Protocol (RRP) Version 1.1.0"">2</a>] has been updated to include response code
557 as a possible error value 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, 510, 520, 531,
535, 540, 541, 542, 543, 544, 545, 547, 549, 550, 551, 552, 553, 557
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. TRANSFER Command Update</span>
<a href="./rfc2832#section-4.3.10">Section 4.3.10 of RFC 2832</a> [<a href="#ref-2" title=""NSI Registry Registrar Protocol (RRP) Version 1.1.0"">2</a>] has been updated to include an
additional TRANSFER command processing option.
Old text:
Authorized User: All registrars MAY use the TRANSFER command to
request the 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.
<span class="grey">Hollenbeck, et al. Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc3632">RFC 3632</a> VeriSign RRP v2.0.0 November 2003</span>
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<crlf>
C:-Approve:No<crlf>
C:EntityName:Domain<crlf>
C:DomainName:example.com<crlf>
C:.<crlf>
S:200 Command completed successfully<crlf>
S:.<crlf>
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. IPv6 Name Server Addresses</span>
<a href="./rfc2832#section-7">Section 7 of RFC 2832</a> [<a href="#ref-2" title=""NSI Registry Registrar Protocol (RRP) Version 1.1.0"">2</a>] has been updated to include support for
name servers using IPv6 addresses. IPv6 addressing architecture is
described in <a href="./rfc3513">RFC 3513</a> [<a href="#ref-3" title=""Internet Protocol Version 6 (IPv6) Addressing Architecture"">3</a>]. This ABNF [<a href="#ref-4" title=""Augmented BNF for Syntax Specifications: ABNF"">4</a>] grammar supplements the
grammar defined in <a href="./rfc2832">RFC 2832</a>.
; 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
<span class="grey">Hollenbeck, et al. Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc3632">RFC 3632</a> VeriSign RRP v2.0.0 November 2003</span>
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 '::'
;
; Examples:
; :: ==> 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:1
; 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
;
; 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:0:0:1
; E:E:E:E:E::2:2 ==> E:E:E:E:E:0:2:2
;
; 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
<span class="grey">Hollenbeck, et al. Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc3632">RFC 3632</a> VeriSign RRP v2.0.0 November 2003</span>
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
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Internationalization Considerations</span>
This document does not introduce any internationalization
considerations that are not already documented in <a href="./rfc2832">RFC 2832</a> [<a href="#ref-2" title=""NSI Registry Registrar Protocol (RRP) Version 1.1.0"">2</a>].
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IANA Considerations</span>
This document does not introduce any IANA considerations that are not
already documented in <a href="./rfc2832">RFC 2832</a> [<a href="#ref-2" title=""NSI Registry Registrar Protocol (RRP) Version 1.1.0"">2</a>].
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
This document does not introduce any security considerations that are
not already documented in <a href="./rfc2832">RFC 2832</a> [<a href="#ref-2" title=""NSI Registry Registrar Protocol (RRP) Version 1.1.0"">2</a>].
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgements</span>
The authors graciously acknowledge the contributions of John Brady,
Matt Larson, Bill Manning, Erik Nordmark, and Steve Mahlstedt.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Normative References</span>
[<a id="ref-1">1</a>] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-2">2</a>] Hollenbeck, S. and M. Srivastava, "NSI Registry Registrar
Protocol (RRP) Version 1.1.0", <a href="./rfc2832">RFC 2832</a>, May 2000.
[<a id="ref-3">3</a>] Hinden, R. and S. Deering, "Internet Protocol Version 6 (IPv6)
Addressing Architecture", <a href="./rfc3513">RFC 3513</a>, April 2003.
[<a id="ref-4">4</a>] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", <a href="./rfc2234">RFC 2234</a>, November 1997.
<span class="grey">Hollenbeck, et al. Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc3632">RFC 3632</a> VeriSign RRP v2.0.0 November 2003</span>
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Authors' Addresses</span>
Scott Hollenbeck
VeriSign, Inc.
21345 Ridgetop Circle
Dulles, VA 20166-6503
US
EMail: shollenbeck@verisign.com
Srikanth Veeramachaneni
VeriSign, Inc.
21345 Ridgetop Circle
Dulles, VA 20166-6503
US
EMail: sveerama@verisign.com
Suresh Yalamanchilli
VeriSign, Inc.
21345 Ridgetop Circle
Dulles, VA 20166-6503
US
EMail: syalamanchilli@verisign.com
<span class="grey">Hollenbeck, et al. Informational [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc3632">RFC 3632</a> VeriSign RRP v2.0.0 November 2003</span>
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Full Copyright Statement</span>
Copyright (C) The Internet Society (2003). 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 assignees.
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, et al. Informational [Page 8]
</pre>
|
