Debian Codegraph @

rfc5105.html

raw
1 <pre>Network Working Group O. Lendl
2 Request for Comments: 5105 enum.at
3 Category: Standards Track December 2007
4
5
6 <span class="h1">ENUM Validation Token Format Definition</span>
7
8 Status of This Memo
9
10 This document specifies an Internet standards track protocol for the
11 Internet community, and requests discussion and suggestions for
12 improvements. Please refer to the current edition of the "Internet
13 Official Protocol Standards" (STD 1) for the standardization state
14 and status of this protocol. Distribution of this memo is unlimited.
15
16 Abstract
17
18 An ENUM domain name is tightly coupled with the underlying E.164
19 number. The process of verifying whether the Registrant of an ENUM
20 domain name is identical to the Assignee of the corresponding E.164
21 number is commonly called "validation". This document describes a
22 signed XML data format -- the Validation Token -- with which
23 Validation Entities can convey successful completion of a validation
24 procedure in a secure fashion.
25
26 Table of Contents
27
28 <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
29 <a href="#section-2">2</a>. Data Requirements ...............................................<a href="#page-2">2</a>
30 <a href="#section-3">3</a>. Digital Signature ...............................................<a href="#page-3">3</a>
31 <a href="#section-4">4</a>. Field Descriptions ..............................................<a href="#page-4">4</a>
32 <a href="#section-4.1">4.1</a>. The &lt;validation&gt; Element ...................................<a href="#page-4">4</a>
33 <a href="#section-4.2">4.2</a>. The &lt;tokendata&gt; Element ....................................<a href="#page-5">5</a>
34 <a href="#section-5">5</a>. Examples ........................................................<a href="#page-6">6</a>
35 <a href="#section-5.1">5.1</a>. Unsigned Token without Registrant Information ..............<a href="#page-6">6</a>
36 <a href="#section-5.2">5.2</a>. Signed Token ...............................................<a href="#page-6">6</a>
37 <a href="#section-6">6</a>. Formal Syntax ...................................................<a href="#page-8">8</a>
38 <a href="#section-6.1">6.1</a>. Token Core Schema ..........................................<a href="#page-9">9</a>
39 <a href="#section-6.2">6.2</a>. Token Data Schema .........................................<a href="#page-10">10</a>
40 <a href="#section-7">7</a>. Other Applications of the Token Concept ........................<a href="#page-12">12</a>
41 <a href="#section-8">8</a>. IANA Considerations ............................................<a href="#page-12">12</a>
42 <a href="#section-9">9</a>. Security Considerations ........................................<a href="#page-13">13</a>
43 <a href="#section-10">10</a>. Acknowledgements ..............................................<a href="#page-14">14</a>
44 <a href="#section-11">11</a>. References ....................................................<a href="#page-14">14</a>
45 <a href="#section-11.1">11.1</a>. Normative References .....................................<a href="#page-14">14</a>
46 <a href="#section-11.2">11.2</a>. Informative References ...................................<a href="#page-15">15</a>
47
48
49
50
51
52 <span class="grey">Lendl Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc5105">RFC 5105</a> ENUM Validation Token December 2007</span>
55
56
57 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
58
59 In the case where an ENUM (E.164 Number Mapping [<a href="#ref-1" title="&quot;The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)&quot;">1</a>]) domain name
60 corresponds to an existing E.164 number [<a href="#ref-2" title="&quot;The international public telecommunication numbering plan&quot;">2</a>], the delegation of this
61 domain needs to be authorized by the Assignee of the corresponding
62 E.164 number. In the role model described in [<a href="#ref-15" title="&quot;ENUM Validation Architecture&quot;">15</a>], the entity that
63 performs this check is called the Validation Entity (VE).
64
65 By conveying an ENUM Validation Token -- a signed XML document -- to
66 the Registry, a VE certifies that delegation requirements have been
67 met and are current.
68
69 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
70 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
71 document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="#ref-3" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">3</a>].
72
73 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Data Requirements</span>
74
75 In this model, the Token is the only piece of data passed from the VE
76 to the Registry. Therefore, the Token needs to contain at least as
77 much information as the Registry requires to grant the delegation of
78 the requested ENUM domain according to its registration policy. As
79 such, the Registry will need confirmation that:
80
81 o the Token was created by an accredited VE,
82
83 o the Token's duration of validity conforms to the policy,
84
85 o the validation procedure employed has met minimum requirements as
86 set forth by policy,
87
88 o and that the Token is protected against tampering and replay
89 attacks.
90
91 Beyond such mandatory information, the Token may optionally include
92 number holder information, in particular, to simplify future
93 revalidations.
94
95 For example, if initial validation requires the steps "Check the
96 identity of the Registrant" and "Check the ownership of an E.164
97 number", then a later revalidation only needs to re-check the
98 ownership as the identity of the Registrant does not change.
99
100 As the Token will be included (see e.g., [<a href="#ref-16" title="&quot;ENUM Validation Information Mapping for the Extensible Provisioning Protocol&quot;">16</a>]) in XML-based Registry/
101 Registrar protocols like the Extensible Provisioning Protocol (EPP)
102 [<a href="#ref-13" title="&quot;Extensible Provisioning Protocol (EPP)&quot;">13</a>], it is a natural choice to use XML to encode Validation Tokens.
103
104
105
106
107
108 <span class="grey">Lendl Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc5105">RFC 5105</a> ENUM Validation Token December 2007</span>
111
112
113 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Digital Signature</span>
114
115 According to the architecture model the propriety of an ENUM
116 delegation depends on the trust relationship between the Registry and
117 the VE. In general, an untrusted link between the Registry and VE
118 should be assumed (for instance, the Token is passed along with the
119 registration request by a Registrar, who might have no role in
120 asserting the right-to-use). Therefore, the Token must be protected
121 against forgery, tampering, and replay-attacks.
122
123 A digital signature on the token:
124
125 o asserts that the token was indeed generated by the indicated VE
126 (authenticity).
127
128 o guarantees that the token was not tampered with in transit
129 (integrity).
130
131 o enables auditing the validation process (non-repudiation).
132
133 The cryptographic signature on the token follows <a href="./rfc3275">RFC 3275</a> (XML-DSIG
134 [<a href="#ref-4" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">4</a>]). As tokens might be transmitted as part of an already XML based
135 protocol, the exclusive XML canonicalization [<a href="#ref-9" title="&quot;Exclusive XML Canonicalization Version 1.0&quot;">9</a>] MUST be used. This
136 transform guarantees that namespace declarations inherited from the
137 surrounding XML do not invalidate the signature. In order to make
138 the signature an integral part of the token, the
139 "enveloped"-signature mode is employed. The signature covers all
140 information contained in the Token.
141
142 XML-DSIG offers a number of cryptographic algorithms for digesting
143 and signing documents and recommends SHA1/RSA-SHA1. Recent advances
144 in cryptanalysis have cast doubt on the security of SHA1, thus
145 rendering this recommendation obsolete (see e.g., the Security
146 Considerations of [<a href="#ref-14" title="&quot;Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile&quot;">14</a>]). <a href="./rfc4051">RFC 4051</a> [<a href="#ref-5" title="&quot;Additional XML Security Uniform Resource Identifiers (URIs)&quot;">5</a>] defines how additional
147 algorithms can be used with XML-DSIG.
148
149 Validation Entities MUST be able to sign tokens according to
150 XML-DSIG, MUST support RSA-SHA1 and RSA-SHA256 [<a href="#ref-5" title="&quot;Additional XML Security Uniform Resource Identifiers (URIs)&quot;">5</a>], MUST support RSA
151 key sizes of 1024 and 2048 bits, and MUST be able to embed X.509 [<a href="#ref-10" title="&quot;Information technology - Open Systems Interconnection - The Directory: Public-key and attribute certificate frameworks&quot;">10</a>]
152 certificates. The Registry MUST define which signature algorithms
153 and key sizes it will accept in Validation Tokens as part of its
154 local policy.
155
156 The choice of a RSA-based signature does not require a public key
157 infrastructure. Whether the Registry acts as a certification
158 authority, accepts certs from a public certification authority, or
159 only accepts pre-registered keys is a local policy choice.
160
161
162
163
164 <span class="grey">Lendl Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc5105">RFC 5105</a> ENUM Validation Token December 2007</span>
167
168
169 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Field Descriptions</span>
170
171 The Validation Token is structured into three parts: the basic
172 validation information, additional information about the Registrant,
173 and the digital signature. The XML schema can be found in <a href="#section-6">Section 6</a>.
174
175 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. The &lt;validation&gt; Element</span>
176
177 A token MUST contain a &lt;validation&gt; element that contains the
178 following:
179
180 o A single validation "serial" attribute identifying a validation
181 token for a certain VE. It must be unique per VE.
182
183 o A single &lt;E164Number&gt; element containing the underlying E.164
184 number in fully qualified (international) format.
185
186 o An optional &lt;lastE164Number&gt; element. If present, it indicates
187 that the whole number block starting with &lt;E164Number&gt; up to and
188 including &lt;lastE164Number&gt; has been validated. To avoid
189 ambiguity, both numbers MUST be of the same length.
190
191 o A single &lt;validationEntityID&gt; element identifying the VE.
192
193 o A single &lt;registrarID&gt; element identifying the Registrar on whose
194 behalf the validation was performed.
195
196 o A single &lt;methodID&gt; element identifying the method used by the VE
197 for validation.
198
199 o A single &lt;executionDate&gt; attribute containing the date of
200 validation formatted as "full-date" according to <a href="./rfc3339">RFC 3339</a> [<a href="#ref-6" title="&quot;Date and Time on the Internet: Timestamps&quot;">6</a>].
201
202 o An optional &lt;expirationDate&gt; attribute marking the expiration date
203 of the validation token formatted as "full-date" according to <a href="./rfc3339">RFC</a>
204 <a href="./rfc3339">3339</a>. The Registry will automatically revoke the delegation at
205 this date unless a new Token has been submitted that extends the
206 lifetime of the validation. A missing &lt;expirationDate&gt; indicates
207 infinite validity of the Token.
208
209 The format and the uniqueness-constraints of these IDs is left to the
210 local policy of the Registry.
211
212
213
214
215
216
217
218
219
220 <span class="grey">Lendl Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc5105">RFC 5105</a> ENUM Validation Token December 2007</span>
223
224
225 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. The &lt;tokendata&gt; Element</span>
226
227 A token may contain a &lt;tokendata&gt; section containing information
228 about the number holder, consisting of the following elements:
229
230 o A single &lt;organization&gt; element containing the full name of the
231 organization to which the Registrant is affiliated.
232
233 o A single &lt;commercialregisternumber&gt; element. If the Registrant is
234 a company, then this field can be used to uniquely identify this
235 company by its official registration number within the local
236 country. The interpretation of this field is thus
237 country-specific.
238
239 o A single &lt;title&gt; element.
240
241 o A single &lt;firstname&gt; element.
242
243 o A single &lt;lastname&gt; element.
244
245 o A single &lt;address&gt; section containing the following elements:
246 * A single optional &lt;streetName&gt;
247 * A single optional &lt;houseNumber&gt;
248 * A single optional &lt;postalCode&gt;
249 * A single optional &lt;locality&gt;
250 * A single optional &lt;countyStateOrProvince&gt;
251 * A single optional &lt;ISOcountryCode&gt;
252
253 o Up to 10 &lt;phone&gt; elements containing full E.164 numbers.
254
255 o Up to 10 &lt;fax&gt; elements containing full E.164 numbers.
256
257 o Up to 10 &lt;email&gt; elements.
258
259 All elements directly under &lt;tokendata&gt; are optional. The
260 &lt;ISOcountryCode&gt; element specifies the country using the alpha-2
261 country code from ISO 3166-1:2006 [<a href="#ref-11" title="&quot;Codes for the representation of names of countries and their subdivisions -- Part 1: Country codes, 2nd edition&quot;">11</a>] (including updates published
262 by the 3166 Maintenance Agency). The definition of the first five
263 elements within the &lt;address&gt; element conforms to the second version
264 of the E.115 Computerized Directory Assistance [<a href="#ref-17" title="&quot;Computerized Directory Assistance Version 2&quot;">17</a>].
265
266
267
268
269
270
271
272
273
274
275
276 <span class="grey">Lendl Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc5105">RFC 5105</a> ENUM Validation Token December 2007</span>
279
280
281 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Examples</span>
282
283 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Unsigned Token without Registrant Information</span>
284
285 This basic Token without any information about the Registrant and
286 without the cryptographic signature shows the basic layout of the
287 Token.
288
289 &lt;?xml version="1.0" encoding="utf-8" standalone="no" ?&gt;
290 &lt;token xmlns="urn:ietf:params:xml:ns:enum-token-1.0" Id="TOKEN"
291 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
292 xsi:schemaLocation=
293 "urn:ietf:params:xml:ns:enum-token-1.0 enum-token-1.0.xsd"&gt;
294 &lt;validation serial="acmeve-000002"&gt;
295 &lt;E164Number&gt;+442079460200&lt;/E164Number&gt;
296 &lt;lastE164Number&gt;+442079460499&lt;/lastE164Number&gt;
297 &lt;validationEntityID&gt;ACME-VE&lt;/validationEntityID&gt;
298 &lt;registrarID&gt;reg-4711&lt;/registrarID&gt;
299 &lt;methodID&gt;42&lt;/methodID&gt;
300 &lt;executionDate&gt;2007-05-08&lt;/executionDate&gt;
301 &lt;expirationDate&gt;2007-11-01&lt;/expirationDate&gt;
302 &lt;/validation&gt;
303 &lt;/token&gt;
304
305 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Signed Token</span>
306
307 This example uses an X.509 based signature that includes the
308 certificate of the signing validation entity. Thus, the validity of
309 the signature can be verified without the need for a key-server. A
310 valid signature is a necessary, but not sufficient, condition for a
311 valid Token. Any entity evaluating a Token needs to check other
312 factors as well, e.g., the certificate and the XML schema.
313
314 &lt;?xml version="1.0" encoding="utf-8" standalone="no" ?&gt;
315 &lt;token xmlns="urn:ietf:params:xml:ns:enum-token-1.0" Id="TOKEN"
316 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
317 xsi:schemaLocation=
318 "urn:ietf:params:xml:ns:enum-token-1.0 enum-token-1.0.xsd"&gt;
319 &lt;validation serial="acmeve-000001"&gt;
320 &lt;E164Number&gt;+442079460123&lt;/E164Number&gt;
321 &lt;validationEntityID&gt;ACME-VE&lt;/validationEntityID&gt;
322 &lt;registrarID&gt;reg-4711&lt;/registrarID&gt;
323 &lt;methodID&gt;42&lt;/methodID&gt;
324 &lt;executionDate&gt;2007-05-08&lt;/executionDate&gt;
325 &lt;/validation&gt;
326 &lt;tokendata xmlns="urn:ietf:params:xml:ns:enum-tokendata-1.0"
327 xsi:schemaLocation=
328 "urn:ietf:params:xml:ns:enum-tokendata-1.0 enum-tokendata-1.0.xsd"&gt;
329
330
331
332 <span class="grey">Lendl Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc5105">RFC 5105</a> ENUM Validation Token December 2007</span>
335
336
337 &lt;contact&gt;
338 &lt;organisation&gt;Example Inc.&lt;/organisation&gt;
339 &lt;commercialregisternumber&gt;4711&lt;/commercialregisternumber&gt;
340 &lt;title&gt;Dr.&lt;/title&gt;
341 &lt;firstname&gt;Max&lt;/firstname&gt;
342 &lt;lastname&gt;Mustermann&lt;/lastname&gt;
343 &lt;address&gt;
344 &lt;streetName&gt;Main&lt;/streetName&gt;
345 &lt;houseNumber&gt;10&lt;/houseNumber&gt;
346 &lt;postalCode&gt;1010&lt;/postalCode&gt;
347 &lt;locality&gt;London&lt;/locality&gt;
348 &lt;countyStateOrProvince&gt;London&lt;/countyStateOrProvince&gt;
349 &lt;ISOcountryCode&gt;GB&lt;/ISOcountryCode&gt;
350 &lt;/address&gt;
351 &lt;phone&gt;+442079460123&lt;/phone&gt;
352 &lt;email&gt;[email protected]&lt;/email&gt;
353 &lt;/contact&gt;
354 &lt;/tokendata&gt;
355 &lt;Signature xmlns="http://www.w3.org/2000/09/xmldsig#"&gt;
356 &lt;SignedInfo&gt;
357 &lt;CanonicalizationMethod
358 Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/&gt;
359 &lt;SignatureMethod
360 Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/&gt;
361 &lt;Reference URI="#TOKEN"&gt;
362 &lt;Transforms&gt;
363 &lt;Transform Algorithm=
364 "<a href="http://www.w3.org/2000/09/xmldsig#enveloped-signature">http://www.w3.org/2000/09/xmldsig#enveloped-signature</a>"/&gt;
365 &lt;Transform
366 Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"&gt;
367 &lt;InclusiveNamespaces
368 xmlns="http://www.w3.org/2001/10/xml-exc-c14n#"
369 PrefixList="enum-token enum-tokendata"/&gt;
370 &lt;/Transform&gt;
371 &lt;/Transforms&gt;
372 &lt;DigestMethod
373 Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/&gt;
374 &lt;DigestValue
375 &gt;VxqsBxSNPFwPAUlCHts3g3DehcexnB1dqUz+GypLZ0k=&lt;/DigestValue&gt;
376 &lt;/Reference&gt;
377 &lt;/SignedInfo&gt;
378 &lt;SignatureValue&gt;
379 QKqphKRNPokVZFbenje+HZZV+RLrNweGnlWBw7ngAtH+rtuslR8LhMLmC4DlBb9V
380 HvKItl+7zLGm3VgYsqfHH8q3jCl1mFxUIuLlIPqtpJs+xAHAJDzZ+vmsF/q2IgrS
381 K0uMmKuU5V1gydDBOvIipcJx+PrPYyXYZSjQXkWknK8=&lt;/SignatureValue&gt;
382 &lt;KeyInfo&gt;
383 &lt;X509Data&gt;
384 &lt;X509Certificate&gt;
385
386
387
388 <span class="grey">Lendl Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc5105">RFC 5105</a> ENUM Validation Token December 2007</span>
391
392
393 MIIDZjCCAs+gAwIBAgIBBDANBgkqhkiG9w0BAQQFADB0MQswCQYDVQQGEwJBVDEP
394 MA0GA1UEBxMGVmllbm5hMRQwEgYDVQQKEwtCT0ZIIENlcnRzLjEbMBkGA1UEAxMS
395 Q0VSVFMuYm9maC5wcml2LmF0MSEwHwYJKoZIhvcNAQkBFhJjZXJ0c0Bib2ZoLnBy
396 aXYuYXQwHhcNMDQwNzIwMTMxNTA5WhcNMDUwNzIwMTMxNTA5WjB/MQswCQYDVQQG
397 EwJBVDEKMAgGA1UECBMBLTEPMA0GA1UEBxMGVmllbm5hMR0wGwYDVQQKExRBY21l
398 IEVOVU0gVmFsaWRhdGlvbjEQMA4GA1UEAxMHYWNtZS1WRTEiMCAGCSqGSIb3DQEJ
399 ARYTbm9ib2R5QGVudW0tYWNtZS5hdDCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkC
400 gYEArJPcjMFc54/zwztSdQXGxUtodJT9r1qGI2lQPNjLvtPJg93+7o5SIOsZGSpg
401 zWbztDAV5qc7PHZWUVIyf6MbM5qSgQDVrjNRhTosNtyqmwi23BH52SKkX3P7eGit
402 LmqEkiUZRxZhZ6upRbtcqvKSwmXitvW4zXZhkVHYJZ2HuMcCAwEAAaOB/DCB+TAJ
403 BgNVHRMEAjAAMCwGCWCGSAGG+EIBDQQfFh1PcGVuU1NMIEdlbmVyYXRlZCBDZXJ0
404 aWZpY2F0ZTAdBgNVHQ4EFgQUyK4otTQtvv6KdSlMBOPT5Ve18JgwgZ4GA1UdIwSB
405 ljCBk4AUvfPadpm0HhmZx2iAVumQTwgnG2eheKR2MHQxCzAJBgNVBAYTAkFUMQ8w
406 DQYDVQQHEwZWaWVubmExFDASBgNVBAoTC0JPRkggQ2VydHMuMRswGQYDVQQDExJD
407 RVJUUy5ib2ZoLnByaXYuYXQxITAfBgkqhkiG9w0BCQEWEmNlcnRzQGJvZmgucHJp
408 di5hdIIBADANBgkqhkiG9w0BAQQFAAOBgQCB9CHBnIUhrdic4h5Ar4hdxjHSQkDH
409 sJWd+MYrNcuSrv3TIOsUkUgNpNNhmkZPtiXqfy3388IRdJtJiLWXSOb/XlZHOM9I
410 MvwKYwhcpQ9UdM/w7VpXQqf+CEj0XSyqxGw65UsHIOijgiG/WyhSj+Lzriw7CTge
411 P2iAJkJVC4t2XA==
412 &lt;/X509Certificate&gt;
413 &lt;/X509Data&gt;
414 &lt;/KeyInfo&gt;
415 &lt;/Signature&gt;
416 &lt;/token&gt;
417
418 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Formal Syntax</span>
419
420 The formal syntax of the validation token is specified using XML
421 schema notation [<a href="#ref-7" title="&quot;XML Schema Part 1: Structures&quot;">7</a>] [<a href="#ref-8" title="&quot;XML Schema Part 2: Datatypes&quot;">8</a>]. Two schemas are defined: The "token core
422 schema" contains mandatory attribute definitions, and the "token data
423 schema" defines the format of the optional "tokendata" section. The
424 BEGIN and END tags are not part of the schema; they are used to note
425 the beginning and ending of the schema for URI registration purposes.
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444 <span class="grey">Lendl Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc5105">RFC 5105</a> ENUM Validation Token December 2007</span>
447
448
449 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Token Core Schema</span>
450
451 BEGIN
452 &lt;?xml version="1.0" encoding="UTF-8"?&gt;
453
454 &lt;schema targetNamespace="urn:ietf:params:xml:ns:enum-token-1.0"
455 xmlns:enum-token="urn:ietf:params:xml:ns:enum-token-1.0"
456 xmlns:enum-tokendata="urn:ietf:params:xml:ns:enum-tokendata-1.0"
457 xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
458 xmlns="http://www.w3.org/2001/XMLSchema"
459 elementFormDefault="qualified"&gt;
460
461 &lt;!-- Import common element types. --&gt;
462
463 &lt;import namespace="http://www.w3.org/2000/09/xmldsig#"
464 schemaLocation="xmldsig-core-schema.xsd"/&gt;
465 &lt;import namespace="urn:ietf:params:xml:ns:enum-tokendata-1.0"
466 schemaLocation="enum-tokendata-1.0.xsd"/&gt;
467
468 &lt;annotation&gt;
469 &lt;documentation&gt;
470 Validation Token core schema
471 &lt;/documentation&gt;
472 &lt;/annotation&gt;
473
474 &lt;element name="token" type="enum-token:tokenBaseType"/&gt;
475
476 &lt;simpleType name="shortTokenType"&gt;
477 &lt;restriction base="token"&gt;
478 &lt;minLength value="1"/&gt;
479 &lt;maxLength value="20"/&gt;
480 &lt;/restriction&gt;
481 &lt;/simpleType&gt;
482
483 &lt;simpleType name="e164numberType"&gt;
484 &lt;restriction base="token"&gt;
485 &lt;maxLength value="20"/&gt;
486 &lt;pattern value="\+\d\d*"/&gt;
487 &lt;/restriction&gt;
488 &lt;/simpleType&gt;
489
490 &lt;complexType name="validationDataType"&gt;
491 &lt;sequence&gt;
492 &lt;element name="E164Number"
493 type="enum-token:e164numberType"/&gt;
494 &lt;element name="lastE164Number" minOccurs="0"
495 type="enum-token:e164numberType"/&gt;
496 &lt;element name="validationEntityID"
497
498
499
500 <span class="grey">Lendl Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc5105">RFC 5105</a> ENUM Validation Token December 2007</span>
503
504
505 type="enum-token:shortTokenType"/&gt;
506 &lt;element name="registrarID"
507 type="enum-token:shortTokenType"/&gt;
508 &lt;element name="methodID"
509 type="enum-token:shortTokenType"/&gt;
510 &lt;element name="executionDate" type="date"/&gt;
511 &lt;element name="expirationDate"
512 type="date" minOccurs="0"/&gt;
513 &lt;/sequence&gt;
514 &lt;attribute name="serial" type="enum-token:shortTokenType"
515 use="required"/&gt;
516 &lt;/complexType&gt;
517
518 &lt;complexType name="tokenBaseType"&gt;
519 &lt;sequence&gt;
520 &lt;element name="validation"
521 type="enum-token:validationDataType"/&gt;
522 &lt;any namespace="urn:ietf:params:xml:ns:enum-tokendata-1.0"
523 minOccurs="0"/&gt;
524 &lt;any namespace="http://www.w3.org/2000/09/xmldsig#"/&gt;
525 &lt;/sequence&gt;
526 &lt;attribute name="Id" type="ID" use="required"/&gt;
527 &lt;/complexType&gt;
528 &lt;/schema&gt;
529 END
530
531 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Token Data Schema</span>
532
533 BEGIN
534 &lt;?xml version="1.0" encoding="UTF-8"?&gt;
535
536 &lt;schema targetNamespace="urn:ietf:params:xml:ns:enum-tokendata-1.0"
537 xmlns:enum-tokendata="urn:ietf:params:xml:ns:enum-tokendata-1.0"
538 xmlns="http://www.w3.org/2001/XMLSchema"
539 elementFormDefault="qualified"&gt;
540
541 &lt;element name="tokendata" type="enum-tokendata:tokenDataType"/&gt;
542
543 &lt;simpleType name="E115String"&gt;
544 &lt;restriction base="string"&gt;
545 &lt;pattern value="[&amp;#x20;-&amp;#x7A;&amp;#xA0;-&amp;#xD7FF;&amp;#xE000;-&amp;#xFFFD;]*"/&gt;
546 &lt;/restriction&gt;
547 &lt;/simpleType&gt;
548
549 &lt;simpleType name="E115StringUb256"&gt;
550 &lt;restriction base="enum-tokendata:E115String"&gt;
551 &lt;minLength value="1"/&gt;
552 &lt;maxLength value="256"/&gt;
553
554
555
556 <span class="grey">Lendl Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc5105">RFC 5105</a> ENUM Validation Token December 2007</span>
559
560
561 &lt;/restriction&gt;
562 &lt;/simpleType&gt;
563
564 &lt;simpleType name="countryCodeType"&gt;
565 &lt;restriction base="token"&gt;
566 &lt;minLength value="2"/&gt;
567 &lt;maxLength value="2"/&gt;
568 &lt;/restriction&gt;
569 &lt;/simpleType&gt;
570
571 &lt;simpleType name="TokenType"&gt;
572 &lt;restriction base="token"&gt;
573 &lt;minLength value="1"/&gt;
574 &lt;maxLength value="64"/&gt;
575 &lt;/restriction&gt;
576 &lt;/simpleType&gt;
577
578 &lt;complexType name="addressType"&gt;
579 &lt;all&gt;
580 &lt;element name="streetName" minOccurs="0"
581 type="enum-tokendata:E115StringUb256" /&gt;
582 &lt;element name="houseNumber" minOccurs="0"
583 type="enum-tokendata:E115StringUb256"/&gt;
584 &lt;element name="postalCode" minOccurs="0"
585 type="enum-tokendata:E115StringUb256"/&gt;
586 &lt;element name="locality" minOccurs="0"
587 type="enum-tokendata:E115StringUb256"/&gt;
588 &lt;element name="countyStateOrProvince" minOccurs="0"
589 type="enum-tokendata:E115StringUb256"/&gt;
590 &lt;element name="ISOcountryCode" minOccurs="0"
591 type="enum-tokendata:countryCodeType"/&gt;
592 &lt;/all&gt;
593 &lt;/complexType&gt;
594
595 &lt;group name="tokenContactBaseGroup"&gt;
596 &lt;sequence&gt;
597 &lt;element name="organisation" minOccurs="0"
598 type="enum-tokendata:E115StringUb256"/&gt;
599 &lt;element name="commercialregisternumber" minOccurs="0"
600 type="enum-tokendata:TokenType"/&gt;
601 &lt;element name="title" minOccurs="0"
602 type="enum-tokendata:TokenType"/&gt;
603 &lt;element name="firstname" minOccurs="0"
604 type="enum-tokendata:E115StringUb256"/&gt;
605 &lt;element name="lastname" minOccurs="0"
606 type="enum-tokendata:E115StringUb256"/&gt;
607 &lt;element name="address" minOccurs="0"
608 type="enum-tokendata:addressType"/&gt;
609
610
611
612 <span class="grey">Lendl Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc5105">RFC 5105</a> ENUM Validation Token December 2007</span>
615
616
617 &lt;element name="phone" type="enum-tokendata:TokenType"
618 minOccurs="0" maxOccurs="10" /&gt;
619 &lt;element name="fax" type="enum-tokendata:TokenType"
620 minOccurs="0" maxOccurs="10" /&gt;
621 &lt;element name="email" type="enum-tokendata:TokenType"
622 minOccurs="0" maxOccurs="10" /&gt;
623 &lt;/sequence&gt;
624 &lt;/group&gt;
625
626 &lt;complexType name="contactType"&gt;
627 &lt;sequence&gt;
628 &lt;group ref="enum-tokendata:tokenContactBaseGroup"/&gt;
629 &lt;/sequence&gt;
630 &lt;/complexType&gt;
631
632 &lt;complexType name="tokenDataType"&gt;
633 &lt;sequence&gt;
634 &lt;element name="contact" type="enum-tokendata:contactType"/&gt;
635 &lt;/sequence&gt;
636 &lt;/complexType&gt;
637
638 &lt;/schema&gt;
639 END
640
641 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Other Applications of the Token Concept</span>
642
643 The concept of the validation token may be useful in other
644 registry-type applications where the proof of an underlying right is
645 a condition for a valid registration.
646
647 An example is a Top Level Domain (TLD) where registration is subject
648 to proof of some precondition, like a trade mark or the right in a
649 name. Such situations often arise during the introduction of a new
650 TLD, e.g., during a "sunrise" phase.
651
652 A Number Portability (NP) database faces very similar verification
653 issues. An NP system based on the Token concept could potentially be
654 superior to current methods, and aid in the convergence of NP and
655 ENUM.
656
657 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. IANA Considerations</span>
658
659 This document uses Uniform Resource Names (URNs) to describe XML
660 namespaces and XML schemas conforming to a registry mechanism
661 described in <a href="./rfc3688">RFC 3688</a> [<a href="#ref-12" title="&quot;The IETF XML Registry&quot;">12</a>]. IANA has made the following four URI
662 assignments.
663
664
665
666
667
668 <span class="grey">Lendl Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc5105">RFC 5105</a> ENUM Validation Token December 2007</span>
671
672
673 1. Registration for the Token namespace:
674 * URI: urn:ietf:params:xml:ns:enum-token-1.0
675 * Registrant Contact: See the "Author's Address" section of this
676 document.
677 * XML: None. Namespace URIs do not represent an XML
678 specification.
679
680 2. Registration for the Token XML schema:
681 * URI: urn:ietf:params:xml:schema:enum-token-1.0
682 * Registrant Contact: See the "Author's Address" section of this
683 document.
684 * XML: See <a href="#section-6.1">Section 6.1</a> of this document.
685
686 3. Registration for the Token Data namespace:
687 * URI: urn:ietf:params:xml:ns:enum-tokendata-1.0
688 * Registrant Contact: See the "Author's Address" section of this
689 document.
690 * XML: None. Namespace URIs do not represent an XML
691 specification.
692
693 4. Registration for the Token Data XML schema:
694 * URI: urn:ietf:params:xml:schema:enum-tokendata-1.0
695 * Registrant Contact: See the "Author's Address" section of this
696 document.
697 * XML: See <a href="#section-6.2">Section 6.2</a> of this document.
698
699 The IDs used in the validationEntityID, RegistrarID, and methodID
700 elements are subject to local policy and thus do not require IANA
701 registration.
702
703 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Security Considerations</span>
704
705 The security of the Validation Token depends on the security of the
706 underlying XML DSIG algorithms. As such, all the security
707 considerations from [<a href="#ref-4" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">4</a>] apply here as well. Two points from [<a href="#ref-4" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">4</a>]
708 merit repetition:
709
710 Transforms are used to select the relevant data for signing and
711 discarding irrelevant information (e.g., pretty-printing and
712 name-space local names).
713
714 The &lt;Reference URI="#TOKEN"&gt; element and attribute combined with the
715 Id="TOKEN" attribute in &lt;token&gt; specifies that the signature should
716 cover the complete token. Moving the Id="TOKEN" attribute to e.g.,
717 the &lt;tokendata&gt; element would make the signature worthless.
718
719
720
721
722
723
724 <span class="grey">Lendl Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc5105">RFC 5105</a> ENUM Validation Token December 2007</span>
727
728
729 It is thus critical that the Registry not only checks whether the
730 Token passes a generic XML-DSIG signature check, but also that:
731
732 1. the signature uses approved transforms and cryptographic
733 algorithms.
734 2. the signature references the &lt;token&gt; element.
735 3. the key used in the signature belongs to an accredited VE.
736
737 The Token content is not encrypted. If local policy dictates that
738 the information contained within the token should be confidential,
739 then this has to be handled through a different mechanism.
740
741 When processing a delegation request, the Registry MUST verify that
742 the information contained in the Token matches the delegation
743 request. The &lt;registrarID&gt; element in the Token prevents a malicious
744 second Registrar from using an eavesdropped Token to register a
745 domain in his name. The Registry MUST verify that the
746 &lt;expirationDate&gt; given (including the case of no given expiration
747 date) conforms to the Registry's policy. To avert replay attacks,
748 local policy MUST specify how long after &lt;executionDate&gt; the Token
749 can be used to authorize a delegation.
750
751 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Acknowledgements</span>
752
753 The author would like to thank the following persons for their
754 valuable suggestions and contributions: Michael Haberler, Alexander
755 Mayrhofer, Bernie Hoeneisen, Michael Braunoeder, Staffan Hagnell,
756 Lawrence Conroy, and Tony Rutkowski.
757
758 <span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. References</span>
759
760 <span class="h3"><a class="selflink" id="section-11.1" href="#section-11.1">11.1</a>. Normative References</span>
761
762 [<a id="ref-1">1</a>] Faltstrom, P. and M. Mealling, "The E.164 to Uniform Resource
763 Identifiers (URI) Dynamic Delegation Discovery System (DDDS)
764 Application (ENUM)", <a href="./rfc3761">RFC 3761</a>, April 2004.
765
766 [<a id="ref-2">2</a>] ITU-T, "The international public telecommunication numbering
767 plan", Recommendation E.164, May 1997.
768
769 [<a id="ref-3">3</a>] Bradner, S., "Key words for use in RFCs to Indicate Requirement
770 Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
771
772 [<a id="ref-4">4</a>] Eastlake 3rd, D., Reagle, J., and D. Solo, "(Extensible Markup
773 Language) XML-Signature Syntax and Processing", <a href="./rfc3275">RFC 3275</a>, March
774 2002.
775
776
777
778
779
780 <span class="grey">Lendl Standards Track [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc5105">RFC 5105</a> ENUM Validation Token December 2007</span>
783
784
785 [<a id="ref-5">5</a>] Eastlake 3rd, D., "Additional XML Security Uniform Resource
786 Identifiers (URIs)", <a href="./rfc4051">RFC 4051</a>, April 2005.
787
788 [<a id="ref-6">6</a>] Klyne, G. and C. Newman, "Date and Time on the Internet:
789 Timestamps", <a href="./rfc3339">RFC 3339</a>, July 2002.
790
791 [<a id="ref-7">7</a>] Maloney, M., Beech, D., Mendelsohn, N., and H. Thompson, "XML
792 Schema Part 1: Structures", W3C REC REC-xmlschema-1-20010502,
793 May 2001.
794
795 [<a id="ref-8">8</a>] Malhotra, A. and P. Biron, "XML Schema Part 2: Datatypes", W3C
796 REC REC-xmlschema-2-20010502, May 2001.
797
798 [<a id="ref-9">9</a>] Eastlake, D., Boyer, J., and J. Reagle, "Exclusive XML
799 Canonicalization Version 1.0", W3C REC REC-xml-exc-c14n-
800 20020718, July 2002.
801
802 [<a id="ref-10">10</a>] International Telecommunications Union, "Information technology
803 - Open Systems Interconnection - The Directory: Public-key and
804 attribute certificate frameworks", ITU-T Recommendation X.509,
805 ISO Standard 9594-8, March 2000.
806
807 [<a id="ref-11">11</a>] International Organization for Standardization, "Codes for the
808 representation of names of countries and their subdivisions --
809 Part 1: Country codes, 2nd edition", ISO Standard 3166,
810 November 2006.
811
812 [<a id="ref-12">12</a>] Mealling, M., "The IETF XML Registry", <a href="https://www.rfc-editor.org/bcp/bcp81">BCP 81</a>, <a href="./rfc3688">RFC 3688</a>,
813 January 2004.
814
815 <span class="h3"><a class="selflink" id="section-11.2" href="#section-11.2">11.2</a>. Informative References</span>
816
817 [<a id="ref-13">13</a>] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", <a href="./rfc4930">RFC</a>
818 <a href="./rfc4930">4930</a>, May 2007.
819
820 [<a id="ref-14">14</a>] Schaad, J., Kaliski, B., and R. Housley, "Additional Algorithms
821 and Identifiers for RSA Cryptography for use in the Internet
822 X.509 Public Key Infrastructure Certificate and Certificate
823 Revocation List (CRL) Profile", <a href="./rfc4055">RFC 4055</a>, June 2005.
824
825 [<a id="ref-15">15</a>] Mayrhofer, A. and B. Hoeneisen, "ENUM Validation
826 Architecture", <a href="./rfc4725">RFC 4725</a>, November 2006.
827
828 [<a id="ref-16">16</a>] Hoeneisen, B., "ENUM Validation Information Mapping for the
829 Extensible Provisioning Protocol", <a href="./rfc5076">RFC 5076</a>, December 2007.
830
831 [<a id="ref-17">17</a>] ITU-T, "Computerized Directory Assistance Version 2",
832 Recommendation E.115v2, October 2005.
833
834
835
836 <span class="grey">Lendl Standards Track [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc5105">RFC 5105</a> ENUM Validation Token December 2007</span>
839
840
841 Author's Address
842
843 Otmar Lendl
844 enum.at GmbH
845 Karlsplatz 1/2/9
846 Wien A-1010
847 Austria
848
849 Phone: +43 1 5056416 33
850 EMail: [email protected]
851 URI: <a href="http://www.enum.at/">http://www.enum.at/</a>
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892 <span class="grey">Lendl Standards Track [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc5105">RFC 5105</a> ENUM Validation Token December 2007</span>
895
896
897 Full Copyright Statement
898
899 Copyright (C) The IETF Trust (2007).
900
901 This document is subject to the rights, licenses and restrictions
902 contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
903 retain all their rights.
904
905 This document and the information contained herein are provided on an
906 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
907 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
908 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
909 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
910 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
911 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
912
913 Intellectual Property
914
915 The IETF takes no position regarding the validity or scope of any
916 Intellectual Property Rights or other rights that might be claimed to
917 pertain to the implementation or use of the technology described in
918 this document or the extent to which any license under such rights
919 might or might not be available; nor does it represent that it has
920 made any independent effort to identify any such rights. Information
921 on the procedures with respect to rights in RFC documents can be
922 found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
923
924 Copies of IPR disclosures made to the IETF Secretariat and any
925 assurances of licenses to be made available, or the result of an
926 attempt made to obtain a general license or permission for the use of
927 such proprietary rights by implementers or users of this
928 specification can be obtained from the IETF on-line IPR repository at
929 <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
930
931 The IETF invites any interested party to bring to its attention any
932 copyrights, patents or patent applications, or other proprietary
933 rights that may cover technology that may be required to implement
934 this standard. Please address the information to the IETF at
935 [email protected].
936
937
938
939
940
941
942
943
944
945
946
947
948 Lendl Standards Track [Page 17]
949 </pre>