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
|
<pre>Internet Engineering Task Force (IETF) S. Hollenbeck
Request for Comments: 8605 Verisign Labs
Category: Informational R. Carney
ISSN: 2070-1721 GoDaddy Inc.
May 2019
<span class="h1">vCard Format Extensions:</span>
<span class="h1">ICANN Extensions for the Registration Data Access Protocol (RDAP)</span>
Abstract
This document defines extensions to the vCard data format for
representing and exchanging contact information used to implement the
Internet Corporation for Assigned Names and Numbers (ICANN)
operational profile for the Registration Data Access Protocol (RDAP).
The property and parameter defined here are used to add values to
RDAP responses that are consistent with ICANN policies.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are candidates for any level of Internet
Standard; see <a href="./rfc7841#section-2">Section 2 of RFC 7841</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="https://www.rfc-editor.org/info/rfc8605">https://www.rfc-editor.org/info/rfc8605</a>.
<span class="grey">Hollenbeck & Carney Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc8605">RFC 8605</a> ICANN RDAP vCard Extensions May 2019</span>
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-1.1">1.1</a>. Terminology Used in This Document . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2">2</a>. vCard Extensions: Properties . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2.1">2.1</a>. Property: CONTACT-URI . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3">3</a>. vCard Extensions: Parameters . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3.1">3.1</a>. Parameter: CC . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-4">4</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-5">5</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-6">6</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-6.1">6.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-6.2">6.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The "Temporary Specification for gTLD Registration Data" available at
<<a href="https://www.icann.org/resources/pages/gtld-registration-data-specs-en">https://www.icann.org/resources/pages/gtld-registration-data-specs-</a>
<a href="https://www.icann.org/resources/pages/gtld-registration-data-specs-en">en</a>> was published by the Internet Corporation for Assigned Named and
Numbers (ICANN) in 2018. The Temporary Specification includes
requirements that cannot currently be met by the Registration Data
Access Protocol (RDAP, [<a href="./rfc7483" title=""JSON Responses for the Registration Data Access Protocol (RDAP)"">RFC7483</a>]) without extending the underlying
vCard [<a href="./rfc6350" title=""vCard Format Specification"">RFC6350</a>] specification used to represent RDAP entity objects.
This document includes specifications for an additional vCard
property and an additional vCard parameter to meet the requirements
of the Temporary Specification.
<span class="grey">Hollenbeck & Carney Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc8605">RFC 8605</a> ICANN RDAP vCard Extensions May 2019</span>
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Terminology Used in This Document</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "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" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>] [<a href="./rfc8174" title=""Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"">RFC8174</a>] when, and only when, they appear in all
capitals, as shown here.
Syntax specifications shown here use the augmented Backus-Naur Form
(ABNF) as described in [<a href="./rfc5234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC5234</a>] and are specified as in the base
vCard specification [<a href="./rfc6350" title=""vCard Format Specification"">RFC6350</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. vCard Extensions: Properties</span>
This document describes one new vCard extension property.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Property: CONTACT-URI</span>
Namespace:
Property name: CONTACT-URI
Purpose: RDAP entity information can be redacted under certain
circumstances (e.g., privacy). The Temporary Specification requires
that RDAP entity objects representing "Registrant", "Admin", and
"Tech" contacts contain an email address or a location for a web form
to facilitate email communication with the relevant contact in a way
that does not identify the associated individual. The CONTACT-URI
property can be used to include URIs representing an email address or
a location for a web form.
Value type: A single URI value.
Cardinality: *
Property parameters: PREF
Description: At least one "mailto", "http", or "https" URI value MUST
be provided. Additional CONTACT-URI properties MAY be provided to
describe other contact methods. If multiple CONTACT-URI properties
are used, the vCard PREF parameter MUST be used to describe the most
preferred property as described in <a href="./rfc6350#section-5.3">Section 5.3 of RFC 6350</a> [<a href="./rfc6350" title=""vCard Format Specification"">RFC6350</a>].
<span class="grey">Hollenbeck & Carney Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc8605">RFC 8605</a> ICANN RDAP vCard Extensions May 2019</span>
Format definition:
CONTACT-URI-param = "VALUE=uri" / pref-param ; pref-param from
[<a href="./rfc6350" title=""vCard Format Specification"">RFC6350</a>]
CONTACT-URI-value = uri ; uri from [<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>]
Examples:
CONTACT-URI:https://contact.example.com
CONTACT-URI;PREF=1:mailto:contact@example.com
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. vCard Extensions: Parameters</span>
This document describes one new vCard extension parameter.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Parameter: CC</span>
Namespace:
Parameter name: CC
Purpose: ICANN requires the use of ISO 3166 [<a href="#ref-ISO.3166.1988">ISO.3166.1988</a>] two-
letter codes, not "country names", in RDAP entity responses. This
parameter is used to extend the ADR property described in
<a href="./rfc6350#section-6.3.1">Section 6.3.1 of RFC 6350</a> [<a href="./rfc6350" title=""vCard Format Specification"">RFC6350</a>].
Description: This parameter contains the ISO 3166 [<a href="#ref-ISO.3166.1988">ISO.3166.1988</a>]
two-character country code associated with the "country name" ADR
component described in <a href="./rfc6350#section-6.3.1">Section 6.3.1 of RFC 6350</a> [<a href="./rfc6350" title=""vCard Format Specification"">RFC6350</a>].
Format definition:
CC-param = "CC=" 2ALPHA
Examples:
ADR;TYPE=work;CC=US:;;54321 Oak St;Reston;VA;20190;USA
ADR;TYPE=home;CC=US:;;12345 Elm St;Reston;VA;20190;USA
<span class="grey">Hollenbeck & Carney Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc8605">RFC 8605</a> ICANN RDAP vCard Extensions May 2019</span>
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IANA Considerations</span>
IANA has added the following entry to the "vCard Properties" registry
defined in <a href="./rfc6350#section-10.3.1">Section 10.3.1 of RFC 6350</a> [<a href="./rfc6350" title=""vCard Format Specification"">RFC6350</a>].
Namespace:
Property: CONTACT-URI
Reference: <a href="./rfc8605#section-2.1">Section 2.1 of RFC 8605</a> (this RFC)
IANA is requested to add the following entry to the vCard Parameters
registry defined in <a href="./rfc6350#section-10.3.2">Section 10.3.2 of RFC 6350</a> [<a href="./rfc6350" title=""vCard Format Specification"">RFC6350</a>].
Namespace:
Property: CC
Reference: <a href="./rfc8605#section-3.1">Section 3.1 of RFC 8605</a> (this RFC)
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
The CONTACT-URI value is purposefully intended to be a publicly
visible contact reference; as such, it cannot require confidentiality
protection. There are, however, privacy implications in the choice
of a URI scheme for the web form contact method. An "https" URI
value can be used to indicate support for confidentiality protection
for connections to the server that publishes the web form. This
document presents no other security considerations beyond those
described in <a href="#section-9">Section 9</a> of the base vCard specification [<a href="./rfc6350" title=""vCard Format Specification"">RFC6350</a>].
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Normative References</span>
[<a id="ref-ISO.3166.1988">ISO.3166.1988</a>]
International Organization for Standardization, "Codes for
the representation of names of countries, 3rd edition",
ISO Standard 3166, August 1988.
[<a id="ref-RFC2119">RFC2119</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>,
DOI 10.17487/RFC2119, March 1997,
<<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>>.
<span class="grey">Hollenbeck & Carney Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc8605">RFC 8605</a> ICANN RDAP vCard Extensions May 2019</span>
[<a id="ref-RFC3986">RFC3986</a>] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66,
<a href="./rfc3986">RFC 3986</a>, DOI 10.17487/RFC3986, January 2005,
<<a href="https://www.rfc-editor.org/info/rfc3986">https://www.rfc-editor.org/info/rfc3986</a>>.
[<a id="ref-RFC5234">RFC5234</a>] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, <a href="./rfc5234">RFC 5234</a>,
DOI 10.17487/RFC5234, January 2008,
<<a href="https://www.rfc-editor.org/info/rfc5234">https://www.rfc-editor.org/info/rfc5234</a>>.
[<a id="ref-RFC6350">RFC6350</a>] Perreault, S., "vCard Format Specification", <a href="./rfc6350">RFC 6350</a>,
DOI 10.17487/RFC6350, August 2011,
<<a href="https://www.rfc-editor.org/info/rfc6350">https://www.rfc-editor.org/info/rfc6350</a>>.
[<a id="ref-RFC8174">RFC8174</a>] Leiba, B., "Ambiguity of Uppercase vs Lowercase in <a href="./rfc2119">RFC</a>
<a href="./rfc2119">2119</a> Key Words", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc8174">RFC 8174</a>, DOI 10.17487/RFC8174,
May 2017, <<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>>.
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative References</span>
[<a id="ref-RFC7483">RFC7483</a>] Newton, A. and S. Hollenbeck, "JSON Responses for the
Registration Data Access Protocol (RDAP)", <a href="./rfc7483">RFC 7483</a>,
DOI 10.17487/RFC7483, March 2015,
<<a href="https://www.rfc-editor.org/info/rfc7483">https://www.rfc-editor.org/info/rfc7483</a>>.
Acknowledgements
The author would like to acknowledge the following individuals for
their contributions to the development of this document: Rick
Wilhelm.
<span class="grey">Hollenbeck & Carney Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc8605">RFC 8605</a> ICANN RDAP vCard Extensions May 2019</span>
Authors' Addresses
Scott Hollenbeck
Verisign Labs
12061 Bluemont Way
Reston, VA 20190
United States of America
Email: shollenbeck@verisign.com
URI: <a href="https://www.verisignlabs.com/">https://www.verisignlabs.com/</a>
Roger Carney
GoDaddy Inc.
14455 N. Hayden Rd. #219
Scottsdale, AZ 85260
United States of America
Email: rcarney@godaddy.com
URI: <a href="http://www.godaddy.com">http://www.godaddy.com</a>
Hollenbeck & Carney Informational [Page 7]
</pre>
|
