Debian Codegraph @

rfc4991.html

raw
1 <pre>Network Working Group A. Newton
2 Request for Comments: 4991 VeriSign, Inc.
3 Category: Standards Track August 2007
4
5
6 <span class="h1">A Common Schema for Internet Registry Information Service</span>
7 <span class="h1">Transfer Protocols</span>
8
9 Status of This Memo
10
11 This document specifies an Internet standards track protocol for the
12 Internet community, and requests discussion and suggestions for
13 improvements. Please refer to the current edition of the "Internet
14 Official Protocol Standards" (STD 1) for the standardization state
15 and status of this protocol. Distribution of this memo is unlimited.
16
17 Copyright Notice
18
19 Copyright (C) The IETF Trust (2007).
20
21 Abstract
22
23 This document describes an XML Schema for use by Internet Registry
24 Information Service (IRIS) application transfer protocols that share
25 common characteristics. It describes common information about the
26 transfer protocol, such as version, supported extensions, and
27 supported security mechanisms.
28
29 Table of Contents
30
31 <a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
32 <a href="#section-2">2</a>. Document Terminology . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
33 <a href="#section-3">3</a>. Formal XML Syntax . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
34 <a href="#section-4">4</a>. Version Information . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
35 <a href="#section-5">5</a>. Size Information . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
36 <a href="#section-6">6</a>. Authentication Success Information . . . . . . . . . . . . . . <a href="#page-8">8</a>
37 <a href="#section-7">7</a>. Authentication Failure Information . . . . . . . . . . . . . . <a href="#page-8">8</a>
38 <a href="#section-8">8</a>. Other Information . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
39 <a href="#section-9">9</a>. Internationalization Considerations . . . . . . . . . . . . . <a href="#page-9">9</a>
40 <a href="#section-10">10</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
41 <a href="#section-10.1">10.1</a>. XML Namespace URN Registration . . . . . . . . . . . . . <a href="#page-10">10</a>
42 <a href="#section-11">11</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
43 <a href="#section-12">12</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
44 <a href="#section-12.1">12.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
45 <a href="#section-12.2">12.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
46 <a href="#appendix-A">Appendix A</a>. Contributors . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
47
48
49
50
51
52 <span class="grey">Newton 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="./rfc4991">RFC 4991</a> Common Schema for IRIS Transfer Protocols August 2007</span>
55
56
57 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
58
59 IRIS [<a href="#ref-8" title="&quot;IRIS: The Internet Registry Information Service (IRIS) Core Protocol&quot;">8</a>] has two transfer protocols, LWZ (lightweight using
60 compression) [<a href="#ref-9" title="&quot;A Lightweight UDP Transfer Protocol for the Internet Registry Information Service&quot;">9</a>] and XPC (XML pipelining with chunks) [<a href="#ref-10" title="&quot;XML Pipelining with Chunks for the Internet Registry Information Service&quot;">10</a>], that
61 share common negotiation mechanisms. Both transfer protocols have a
62 need for the server to provide rich status information to clients
63 during protocol negotiation. In many cases, this status information
64 would be too complex to describe using simple bit fields and length-
65 specified octet sequences. This document defines an XML Schema for
66 this rich status information and describes the usage of conformant
67 XML for conveying this status information.
68
69 This document defines five types of information used in the
70 negotiation of protocol capabilities: version, size, authentication
71 success, authentication failure, and other information. The version
72 information is used to negotiate the versions and extensions to the
73 transfer protocol, the application operations protocol, and data
74 models used by the application operations. Size information is used
75 to indicate request and response size capabilities and errors.
76 Authentication success and failure information is used to indicate
77 the outcome of an authentication action. Other types of information
78 may also be conveyed that is generally a result of an error but
79 cannot be corrected through defined protocol behavior.
80
81 As an example, upon initiation of a connection, a server may send
82 version information informing the client of the data models supported
83 by the server and the security mechanisms supported by the server.
84 The client may then respond appropriately. For example, the client
85 may not recognize any of the data models supported by the server, and
86 therefore close the connection. On the other hand, the client may
87 recognize the data models and the security mechanisms and begin the
88 procedure to initialize a security mechanism with the server before
89 proceeding to query data according to a recognized data model.
90
91 Both LWZ [<a href="#ref-9" title="&quot;A Lightweight UDP Transfer Protocol for the Internet Registry Information Service&quot;">9</a>] and XPC [<a href="#ref-10" title="&quot;XML Pipelining with Chunks for the Internet Registry Information Service&quot;">10</a>] provide examples of the usage of the XML
92 Schema defined in this document.
93
94 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Document Terminology</span>
95
96 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
97 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
98 document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="#ref-6" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">6</a>].
99
100
101
102
103
104
105
106
107
108 <span class="grey">Newton 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="./rfc4991">RFC 4991</a> Common Schema for IRIS Transfer Protocols August 2007</span>
111
112
113 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Formal XML Syntax</span>
114
115 The following is the XML Schema used to define transfer protocol
116 status information. See the following specifications: [<a href="#ref-2" title="&quot;Extensible Markup Language (XML) 1.0&quot;">2</a>], [<a href="#ref-3" title="&quot;Namespaces in XML&quot;">3</a>], [<a href="#ref-4" title="&quot;XML Schema Part 2: Datatypes&quot;">4</a>],
117 [<a href="#ref-5" title="&quot;XML Schema Part 1: Structures&quot;">5</a>]. Updates or changes to this schema require a document that
118 UPDATES or OBSOLETES this document.
119
120 &lt;?xml version="1.0"?&gt;
121 &lt;schema xmlns="http://www.w3.org/2001/XMLSchema"
122 xmlns:iristrans="urn:ietf:params:xml:ns:iris-transport"
123 targetNamespace="urn:ietf:params:xml:ns:iris-transport"
124 elementFormDefault="qualified" &gt;
125
126 &lt;annotation&gt;
127 &lt;documentation&gt;
128 A schema for describing status information
129 for use by multiple transfer protocols.
130 &lt;/documentation&gt;
131 &lt;/annotation&gt;
132
133 &lt;element name="versions"&gt;
134 &lt;complexType&gt;
135 &lt;sequence&gt;
136 &lt;element name="transferProtocol" maxOccurs="unbounded"&gt;
137 &lt;complexType&gt;
138 &lt;sequence&gt;
139 &lt;element name="application" minOccurs="0"
140 maxOccurs="unbounded"&gt;
141 &lt;complexType&gt;
142 &lt;sequence&gt;
143 &lt;element name="dataModel" minOccurs="0"
144 maxOccurs="unbounded"&gt;
145 &lt;complexType&gt;
146 &lt;attribute name="protocolId" type="token"
147 use="required" /&gt;
148 &lt;attribute name="extensionIds"
149 type="normalizedString" /&gt;
150 &lt;/complexType&gt;
151 &lt;/element&gt;
152 &lt;/sequence&gt;
153 &lt;attribute name="protocolId" type="token"
154 use="required" /&gt;
155 &lt;attribute name="extensionIds"
156 type="normalizedString" /&gt;
157 &lt;/complexType&gt;
158 &lt;/element&gt;
159 &lt;/sequence&gt;
160 &lt;attribute name="protocolId" type="token" use="required"
161
162
163
164 <span class="grey">Newton 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="./rfc4991">RFC 4991</a> Common Schema for IRIS Transfer Protocols August 2007</span>
167
168
169 /&gt;
170 &lt;attribute name="extensionIds" type="normalizedString" /&gt;
171 &lt;attribute name="authenticationIds"
172 type="normalizedString" /&gt;
173 &lt;attribute name="responseSizeOctets"
174 type="positiveInteger" /&gt;
175 &lt;attribute name="requestSizeOctets"
176 type="positiveInteger" /&gt;
177 &lt;/complexType&gt;
178 &lt;/element&gt;
179 &lt;/sequence&gt;
180 &lt;/complexType&gt;
181 &lt;/element&gt;
182
183 &lt;element name="size"&gt;
184 &lt;complexType&gt;
185 &lt;sequence&gt;
186 &lt;element name="request"
187 minOccurs="0"
188 type="iristrans:octetsType" /&gt;
189 &lt;element name="response"
190 minOccurs="0"
191 type="iristrans:octetsType" /&gt;
192 &lt;/sequence&gt;
193 &lt;/complexType&gt;
194 &lt;/element&gt;
195
196 &lt;complexType name="octetsType"&gt;
197 &lt;choice&gt;
198 &lt;element name="exceedsMaximum"&gt;
199 &lt;complexType/&gt;
200 &lt;/element&gt;
201 &lt;element name="octets" type="positiveInteger" /&gt;
202 &lt;/choice&gt;
203 &lt;/complexType&gt;
204
205 &lt;element name="authenticationSuccess"&gt;
206 &lt;complexType&gt;
207 &lt;sequence&gt;
208 &lt;element name="description" minOccurs="0"
209 maxOccurs="unbounded"&gt;
210 &lt;complexType&gt;
211 &lt;simpleContent&gt;
212 &lt;extension base="string"&gt;
213 &lt;attribute name="language" type="language"
214 use="required"/&gt;
215 &lt;/extension&gt;
216 &lt;/simpleContent&gt;
217
218
219
220 <span class="grey">Newton 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="./rfc4991">RFC 4991</a> Common Schema for IRIS Transfer Protocols August 2007</span>
223
224
225 &lt;/complexType&gt;
226 &lt;/element&gt;
227 &lt;element name="data" minOccurs="0" maxOccurs="1"
228 type="base64Binary"/&gt;
229 &lt;/sequence&gt;
230 &lt;/complexType&gt;
231 &lt;/element&gt;
232
233 &lt;element name="authenticationFailure"&gt;
234 &lt;complexType&gt;
235 &lt;sequence&gt;
236 &lt;element name="description" minOccurs="0"
237 maxOccurs="unbounded"&gt;
238 &lt;complexType&gt;
239 &lt;simpleContent&gt;
240 &lt;extension base="string"&gt;
241 &lt;attribute name="language" type="language"
242 use="required"/&gt;
243 &lt;/extension&gt;
244 &lt;/simpleContent&gt;
245 &lt;/complexType&gt;
246 &lt;/element&gt;
247 &lt;/sequence&gt;
248 &lt;/complexType&gt;
249 &lt;/element&gt;
250
251 &lt;element name="other"&gt;
252 &lt;complexType&gt;
253 &lt;sequence&gt;
254 &lt;element name="description" minOccurs="0"
255 maxOccurs="unbounded"&gt;
256 &lt;complexType&gt;
257 &lt;simpleContent&gt;
258 &lt;extension base="string"&gt;
259 &lt;attribute name="language" type="language"
260 use="required"/&gt;
261 &lt;/extension&gt;
262 &lt;/simpleContent&gt;
263 &lt;/complexType&gt;
264 &lt;/element&gt;
265 &lt;/sequence&gt;
266 &lt;attribute type="token" name="type" use="required"/&gt;
267 &lt;/complexType&gt;
268 &lt;/element&gt;
269
270 &lt;/schema&gt;
271
272
273
274
275
276 <span class="grey">Newton 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="./rfc4991">RFC 4991</a> Common Schema for IRIS Transfer Protocols August 2007</span>
279
280
281 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Version Information</span>
282
283 The &lt;versions&gt; element is used to describe version information about
284 the transfer protocol, the application protocol, and data models used
285 by the application protocol.
286
287 The &lt;versions&gt; element has one or more &lt;transferProtocol&gt; child
288 elements. &lt;transferProtocol&gt; elements have zero or more &lt;application&gt;
289 child elements. And &lt;application&gt; elements have zero or more
290 &lt;dataModel&gt; elements. Each of these element types has a 'protocolId'
291 attribute identifying the protocol they represent and an optional
292 'extensionIds' attribute identifying the protocol extensions they
293 support.
294
295 During capabilities negotiation, it is expected that both sides of
296 the negotiation recognize the 'protocolId' value of the
297 &lt;transferProtocol&gt; element and at least one of the &lt;application&gt; and
298 &lt;dataModel&gt; elements. If the negotiation produces a situation where
299 this is not possible, an error SHOULD be given and communication
300 ended. It is not expected that each side must recognize the
301 'extensionIds' values, and unrecognized 'extensionIds' values MUST be
302 ignored.
303
304 Additionally, the &lt;transferProtocol&gt; element has optional
305 'authenticationIds', 'responseSizeOctets', and 'requestSizeOctets'
306 attributes. The 'authenticationIds' attribute identifies
307 authentication mechanisms supported by the associated transfer
308 protocol. The 'responseSizeOctets' attribute describes the maximum
309 response size in octets the server will give. The
310 'requestSizeOctets' attribute describes the maximum request size in
311 octets the server will accept.
312
313 The protocol, extension, and authentication mechanism identifiers are
314 of no specific type, and this document defines none. Specifications
315 using this XML Schema MUST define the identifiers for use with the
316 &lt;versions&gt; element and its children.
317
318 The meaning of octets for the transfer of data is counted in
319 different ways for different transfer protocols. Some transfer
320 protocols need only to specify the octets of the data being
321 transferred, while other transfer protocols need to account for
322 additional octets used to transfer the data. Specifications using
323 this XML Schema MUST describe how these octet counts are calculated.
324
325
326
327
328
329
330
331
332 <span class="grey">Newton 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="./rfc4991">RFC 4991</a> Common Schema for IRIS Transfer Protocols August 2007</span>
335
336
337 The following is example XML describing version information.
338
339 &lt;versions xmlns="urn:ietf:params:xml:ns:iris-transport"&gt;
340 &lt;transferProtocol protocolId="iris.lwz"
341 authenticationIds="PLAIN EXTERNAL"&gt;
342 &lt;application protocolId="urn:ietf:params:xml:ns:iris1"
343 extensionIds="http://example.com/SIMPLEBAG"&gt;
344 &lt;dataModel protocolId="urn:ietf:params:xml:ns:dchk1"/&gt;
345 &lt;dataModel protocolId="urn:ietf:params:xml:ns:dreg1"/&gt;
346 &lt;/application&gt;
347 &lt;/transferProtocol&gt;
348 &lt;/versions&gt;
349
350 Version Information Example
351
352 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Size Information</span>
353
354 The &lt;size&gt; element provides a means for a server to communicate to a
355 client that a given request has exceeded a negotiated size
356 (&lt;request&gt;) or that a response to a given request will exceed a
357 negotiated size (&lt;response&gt;).
358
359 A server may indicate one of two size conditions by specifying the
360 following child elements:
361
362 &lt;exceedsMaximum&gt; - this child element simply indicates that the
363 size exceeded the negotiated size.
364
365 &lt;octets&gt; - this child element indicates that the size exceeded the
366 negotiated size and conveys the number of octets that is the
367 maximum for a request if the parent element is a &lt;request&gt; element
368 or the number of octets needed to provide the response if the
369 parent element is a &lt;response&gt; element.
370
371 The meaning of octets for the transfer of data is counted in
372 different ways for different transfer protocols. Some transfer
373 protocols need only to specify the octets of the data being
374 transferred, while other transfer protocols need to account for
375 additional octets used to transfer the data. Specifications using
376 this XML Schema MUST describe how these octet counts are calculated.
377
378 The following is example XML describing size information.
379
380 &lt;size xmlns="urn:ietf:params:xml:ns:iris-transport"&gt;
381 &lt;response&gt;
382 &lt;octets&gt;1211&lt;/octets&gt;
383 &lt;/response&gt;
384 &lt;/size&gt;
385
386
387
388 <span class="grey">Newton 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="./rfc4991">RFC 4991</a> Common Schema for IRIS Transfer Protocols August 2007</span>
391
392
393 Size Information Example
394
395 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Authentication Success Information</span>
396
397 The &lt;authenticationSuccess&gt; element indicates that a client has
398 successfully authenticated to a server. Along with this indication,
399 it can provide text that may be presented to a user with regard to
400 this successful authentication using child &lt;description&gt; elements.
401
402 Each &lt;description&gt; element MUST have a 'language' attribute
403 describing the language of the content of the &lt;description&gt; element.
404 Clients are not expected to concatenate multiple descriptions;
405 therefore, servers MUST NOT provide multiple &lt;description&gt; elements
406 with the same language descriptor.
407
408 Finally, additional security data may be sent back with the
409 authentication success message using the &lt;data&gt; element. The content
410 of this element is of the base64Binary simple type.
411
412 The following is example XML describing authentication success
413 information.
414
415 &lt;authenticationSuccess
416 xmlns="urn:ietf:params:xml:ns:iris-transport"&gt;
417 &lt;description language="en"&gt;
418 user 'bob' authenticates via password
419 &lt;/description&gt;
420 &lt;/authenticationSuccess&gt;
421
422 Authentication Success Example
423
424 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Authentication Failure Information</span>
425
426 The &lt;authenticationFailure&gt; element indicates that a client has
427 failed to properly authenticate to a server. Along with this
428 indication, it can provide text that may be presented to a user with
429 regard to this authentication failure using child &lt;description&gt;
430 elements.
431
432 Each &lt;description&gt; element MUST have a 'language' attribute
433 describing the language of the content of the &lt;description&gt; element.
434 Clients are not expected to concatenate multiple descriptions;
435 therefore, servers MUST NOT provide multiple &lt;description&gt; elements
436 with the same language descriptor.
437
438 The following is example XML describing authentication failure
439 information.
440
441
442
443
444 <span class="grey">Newton 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="./rfc4991">RFC 4991</a> Common Schema for IRIS Transfer Protocols August 2007</span>
447
448
449 &lt;authenticationFailure
450 xmlns="urn:ietf:params:xml:ns:iris-transport"&gt;
451 &lt;description language="en"&gt;
452 please consult your admin if you have forgotten your password
453 &lt;/description&gt;
454 &lt;/authenticationFailure&gt;
455
456 Authentication Failure Example
457
458 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Other Information</span>
459
460 The &lt;other&gt; element conveys status information that may require
461 interpretation by a human to be meaningful. This element has a
462 required 'type' attribute, which contains an identifier regarding the
463 nature of the information. This document does not define any
464 identifiers for use in this attribute, but the intent is that these
465 identifiers are well-known so that clients may take different classes
466 of action based on the content of this attribute. Therefore,
467 specifications making use of this XML Schema MUST define these
468 identifiers.
469
470 The &lt;other&gt; element may have zero or more &lt;description&gt; elements.
471 Each &lt;description&gt; element MUST have a 'language' attribute
472 describing the language of the content of the &lt;description&gt; element.
473 Servers may use these child elements to convey textual information to
474 clients regarding the class (or type) of status information being
475 specified by the &lt;other&gt; element. Clients are not expected to
476 concatenate multiple descriptions; therefore, servers MUST NOT
477 provide multiple &lt;description&gt; elements with the same language
478 descriptor.
479
480 The following is example XML describing other information.
481
482 &lt;other xmlns="urn:ietf:params:xml:ns:iris-transport" type="system"&gt;
483 &lt;description language="en"&gt;unavailable, come back
484 later&lt;/description&gt;
485 &lt;/other&gt;
486
487 Other Information Example
488
489 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Internationalization Considerations</span>
490
491 XML processors are obliged to recognize both UTF-8 and UTF-16 [<a href="#ref-1" title="&quot;The Unicode Standard, Version 3&quot;">1</a>]
492 encodings. XML provides for mechanisms to identify and use other
493 character encodings. Application transfer protocols MUST define
494 which additional character encodings, if any, are to be allowed in
495 the use of the XML defined in this document.
496
497
498
499
500 <span class="grey">Newton 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="./rfc4991">RFC 4991</a> Common Schema for IRIS Transfer Protocols August 2007</span>
503
504
505 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. IANA Considerations</span>
506
507 <span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. XML Namespace URN Registration</span>
508
509 This document makes use of the XML namespace and schema registry
510 specified in XML_URN [<a href="#ref-7" title="&quot;The IETF XML Registry&quot;">7</a>]. Accordingly, the following registrations
511 have been made by IANA:
512
513 o XML Namespace URN/URI:
514
515 * urn:ietf:params:xml:ns:iris-transport
516
517 o Contact:
518
519 * Andrew Newton &lt;[email protected]&gt;
520
521 o XML:
522
523 * None
524
525 o XML Schema URN/URI:
526
527 * urn:ietf:params:xml:schema:iris-transport
528
529 o Contact:
530
531 * Andrew Newton &lt;[email protected]&gt;
532
533 o XML:
534
535 * The XML Schema specified in <a href="#section-3">Section 3</a>
536
537 <span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Security Considerations</span>
538
539 Transfer protocols using XML conformant to the XML Schema in this
540 document and offering security properties such as authentication and
541 confidentiality SHOULD offer an initial message from the server to
542 the client using the &lt;versions&gt; element. This &lt;versions&gt; element
543 SHOULD contain all relevant authentication identifiers in its
544 'authenticationId' attribute. The purpose of providing this initial
545 message is to help thwart downgrade attacks.
546
547
548
549
550
551
552
553
554
555
556 <span class="grey">Newton 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="./rfc4991">RFC 4991</a> Common Schema for IRIS Transfer Protocols August 2007</span>
559
560
561 <span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. References</span>
562
563 <span class="h3"><a class="selflink" id="section-12.1" href="#section-12.1">12.1</a>. Normative References</span>
564
565 [<a id="ref-1">1</a>] The Unicode Consortium, "The Unicode Standard, Version 3", ISBN
566 0-201-61633-5, 2000, &lt;The Unicode Standard, Version 3&gt;.
567
568 [<a id="ref-2">2</a>] World Wide Web Consortium, "Extensible Markup Language (XML)
569 1.0", W3C XML, February 1998, &lt;<a href="http://www.w3.org/TR/1998/REC-xml-19980210">http://www.w3.org/TR/1998/REC-</a>
570 <a href="http://www.w3.org/TR/1998/REC-xml-19980210">xml-19980210</a>&gt;.
571
572 [<a id="ref-3">3</a>] World Wide Web Consortium, "Namespaces in XML", W3C XML
573 Namespaces, January 1999, &lt;<a href="http://www.w3.org/TR/1999/REC-xml-names-19990114">http://www.w3.org/TR/1999/REC-xml-</a>
574 <a href="http://www.w3.org/TR/1999/REC-xml-names-19990114">names-19990114</a>&gt;.
575
576 [<a id="ref-4">4</a>] World Wide Web Consortium, "XML Schema Part 2: Datatypes", W3C
577 XML Schema, October 2004, &lt;<a href="http://www.w3.org/TR/xmlschema-2/">http://www.w3.org/TR/xmlschema-2/</a>&gt;.
578
579 [<a id="ref-5">5</a>] World Wide Web Consortium, "XML Schema Part 1: Structures", W3C
580 XML Schema, October 2004, &lt;<a href="http://www.w3.org/TR/xmlschema-1/">http://www.w3.org/TR/xmlschema-1/</a>&gt;.
581
582 [<a id="ref-6">6</a>] Bradner, S., "Key words for use in RFCs to Indicate Requirement
583 Levels", <a href="./rfc2119">RFC 2119</a>, <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, March 1997.
584
585 [<a id="ref-7">7</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>,
586 January 2004.
587
588 <span class="h3"><a class="selflink" id="section-12.2" href="#section-12.2">12.2</a>. Informative References</span>
589
590 [<a id="ref-8">8</a>] Newton, A. and M. Sanz, "IRIS: The Internet Registry
591 Information Service (IRIS) Core Protocol", <a href="./rfc3981">RFC 3981</a>, January
592 2005.
593
594 [<a id="ref-9">9</a>] Newton, A., "A Lightweight UDP Transfer Protocol for the
595 Internet Registry Information Service", <a href="./rfc4993">RFC 4993</a>, August 2007.
596
597 [<a id="ref-10">10</a>] Newton, A., "XML Pipelining with Chunks for the Internet
598 Registry Information Service", <a href="./rfc4992">RFC 4992</a>, August 2007.
599
600
601
602
603
604
605
606
607
608
609
610
611
612 <span class="grey">Newton 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="./rfc4991">RFC 4991</a> Common Schema for IRIS Transfer Protocols August 2007</span>
615
616
617 <span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Contributors</span>
618
619 Substantive contributions to this document have been provided by the
620 members of the IETF's CRISP Working Group, especially Robert
621 Martin-Legene, Milena Caires, and David Blacka.
622
623 Author's Address
624
625 Andrew L. Newton
626 VeriSign, Inc.
627 21345 Ridgetop Circle
628 Sterling, VA 20166
629 USA
630
631 Phone: +1 703 948 3382
632 EMail: [email protected]
633 URI: <a href="http://www.verisignlabs.com/">http://www.verisignlabs.com/</a>
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668 <span class="grey">Newton 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="./rfc4991">RFC 4991</a> Common Schema for IRIS Transfer Protocols August 2007</span>
671
672
673 Full Copyright Statement
674
675 Copyright (C) The IETF Trust (2007).
676
677 This document is subject to the rights, licenses and restrictions
678 contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
679 retain all their rights.
680
681 This document and the information contained herein are provided on an
682 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
683 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
684 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
685 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
686 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
687 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
688
689 Intellectual Property
690
691 The IETF takes no position regarding the validity or scope of any
692 Intellectual Property Rights or other rights that might be claimed to
693 pertain to the implementation or use of the technology described in
694 this document or the extent to which any license under such rights
695 might or might not be available; nor does it represent that it has
696 made any independent effort to identify any such rights. Information
697 on the procedures with respect to rights in RFC documents can be
698 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>.
699
700 Copies of IPR disclosures made to the IETF Secretariat and any
701 assurances of licenses to be made available, or the result of an
702 attempt made to obtain a general license or permission for the use of
703 such proprietary rights by implementers or users of this
704 specification can be obtained from the IETF on-line IPR repository at
705 <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
706
707 The IETF invites any interested party to bring to its attention any
708 copyrights, patents or patent applications, or other proprietary
709 rights that may cover technology that may be required to implement
710 this standard. Please address the information to the IETF at
711 [email protected].
712
713 Acknowledgement
714
715 Funding for the RFC Editor function is currently provided by the
716 Internet Society.
717
718
719
720
721
722
723
724 Newton Standards Track [Page 13]
725 </pre>