idnits 2.17.1 draft-ietf-enum-epp-e164-08.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1.a on line 15. -- Found old boilerplate from RFC 3978, Section 5.5 on line 758. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 735. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 742. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 748. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: This document is an Internet-Draft and is subject to all provisions of Section 3 of RFC 3667. By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (December 1, 2004) is 7079 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 3731 (ref. '1') (Obsoleted by RFC 4931) -- Possible downref: Non-RFC (?) normative reference: ref. '2' -- Possible downref: Non-RFC (?) normative reference: ref. '3' -- Possible downref: Non-RFC (?) normative reference: ref. '4' ** Obsolete normative reference: RFC 3730 (ref. '5') (Obsoleted by RFC 4930) ** Obsolete normative reference: RFC 3761 (ref. '6') (Obsoleted by RFC 6116, RFC 6117) Summary: 8 errors (**), 0 flaws (~~), 3 warnings (==), 10 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group S. Hollenbeck 2 Internet-Draft VeriSign, Inc. 3 Expires: June 1, 2005 December 1, 2004 5 E.164 Number Mapping for the Extensible Provisioning Protocol 6 draft-ietf-enum-epp-e164-08.txt 8 Status of this Memo 10 This document is an Internet-Draft and is subject to all provisions 11 of section 3 of RFC 3667. By submitting this Internet-Draft, each 12 author represents that any applicable patent or other IPR claims of 13 which he or she is aware have been or will be disclosed, and any of 14 which he or she become aware will be disclosed, in accordance with 15 RFC 3668. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as 20 Internet-Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on June 1, 2005. 35 Copyright Notice 37 Copyright (C) The Internet Society (2004). 39 Abstract 41 This document describes an Extensible Provisioning Protocol (EPP) 42 extension mapping for the provisioning and management of E.164 43 numbers representing domain names stored in a shared central 44 repository. Specified in XML, this mapping extends the EPP domain 45 name mapping to provide additional features required for the 46 provisioning of E.164 numbers. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 1.1 Conventions Used In This Document . . . . . . . . . . . . 3 52 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 3 53 2.1 E.164 Domain Names . . . . . . . . . . . . . . . . . . . . 3 54 2.2 NAPTR Fields . . . . . . . . . . . . . . . . . . . . . . . 4 55 2.2.1 Order . . . . . . . . . . . . . . . . . . . . . . . . 4 56 2.2.2 Preference . . . . . . . . . . . . . . . . . . . . . . 4 57 2.2.3 Flags . . . . . . . . . . . . . . . . . . . . . . . . 4 58 2.2.4 Service . . . . . . . . . . . . . . . . . . . . . . . 4 59 2.2.5 Regular Expression . . . . . . . . . . . . . . . . . . 4 60 2.2.6 Replacement . . . . . . . . . . . . . . . . . . . . . 4 61 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 5 62 3.1 EPP Query Commands . . . . . . . . . . . . . . . . . . . . 5 63 3.1.1 EPP Command . . . . . . . . . . . . . . . . . 5 64 3.1.2 EPP Command . . . . . . . . . . . . . . . . . . 5 65 3.1.3 EPP Command . . . . . . . . . . . . . . . . 7 66 3.2 EPP Transform Commands . . . . . . . . . . . . . . . . . . 7 67 3.2.1 EPP Command . . . . . . . . . . . . . . . . . 7 68 3.2.2 EPP Command . . . . . . . . . . . . . . . . . 9 69 3.2.3 EPP Command . . . . . . . . . . . . . . . . . 9 70 3.2.4 EPP Command . . . . . . . . . . . . . . . . 9 71 3.2.5 EPP Command . . . . . . . . . . . . . . . . . 9 72 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 11 73 5. Internationalization Considerations . . . . . . . . . . . . . 14 74 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 75 7. Security Considerations . . . . . . . . . . . . . . . . . . . 15 76 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15 77 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 78 9.1 Normative References . . . . . . . . . . . . . . . . . . . . 15 79 9.2 Informative References . . . . . . . . . . . . . . . . . . . 16 80 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 16 81 Intellectual Property and Copyright Statements . . . . . . . . 17 83 1. Introduction 85 This document describes an E.164 number mapping for version 1.0 of 86 the Extensible Provisioning Protocol (EPP). This mapping, an 87 extension of the domain name mapping described in [1], is specified 88 using the Extensible Markup Language (XML) 1.0 as described in [2] 89 and XML Schema notation as described in [3] and [4]. 91 The EPP core protocol specification [5] provides a complete 92 description of EPP command and response structures. A thorough 93 understanding of the base protocol specification is necessary to 94 understand the mapping described in this document. 96 ENUM [6] describes how the Domain Name System (DNS) can be used to 97 identify services associated with an E.164 number. The EPP mapping 98 described in this document specifies a mechanism for the provisioning 99 and management of E.164 numbers stored in a shared central 100 repository. Information exchanged via this mapping can be extracted 101 from the repository and used to publish DNS resource records as 102 described in ENUM [6]. Examples used in this document were chosen 103 specifically to illustrate provisioning concepts for the example 104 resource records described in the ENUM specification. 106 1.1 Conventions Used In This Document 108 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 109 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 110 document are to be interpreted as described in RFC 2119 [7]. 112 In examples, "C:" represents lines sent by a protocol client and "S:" 113 represents lines returned by a protocol server. Indentation and 114 white space in examples is provided only to illustrate element 115 relationships and is not a REQUIRED feature of this specification. 117 XML is case sensitive. Unless stated otherwise, XML specifications 118 and examples provided in this document MUST be interpreted in the 119 character case presented to develop a conforming implementation. 121 2. Object Attributes 123 This extension adds additional elements to the EPP domain name 124 mapping [1]. Only new element descriptions are described here. 126 2.1 E.164 Domain Names 128 An E.164 domain name is a representation of an E.164 number that has 129 been translated to conform to domain name syntax as described in the 130 ENUM specification [6]. The labels used to describe the name space 131 of an E.164 domain name are a policy matter that is beyond the scope 132 of this document. 134 2.2 NAPTR Fields 136 According to ENUM [6], Naming Authority Pointer (NAPTR) resource 137 records are used to identify available ways of contacting a specific 138 node identified by a domain name created from the translation of an 139 E.164 number. The basic NAPTR record format is described in RFC 3403 140 [8]. Rules for structuring and using NAPTR records for use with ENUM 141 are described in RFC 3761 [6]. 143 Several NAPTR field values are optional per RFC 3403. RFC 3761 144 describes processing rules that require the presence of certain NAPTR 145 field values. This document describes field value requirements that 146 correspond to RFC 3761. 148 2.2.1 Order 150 The NAPTR order field, a 16-bit unsigned integer, is represented in 151 this mapping using the XML Schema "unsignedShort" data type. 153 2.2.2 Preference 155 The NAPTR preference field, a 16-bit unsigned integer, is represented 156 in this mapping using the XML Schema "unsignedShort" data type. 158 2.2.3 Flags 160 The NAPTR flags field is represented in this mapping using a single 161 character. The case of the flag character is not significant. 163 2.2.4 Service 165 The NAPTR service field is represented in this mapping using a 166 character string with an unspecified maximum length. Valid values 167 are application-dependent. 169 2.2.5 Regular Expression 171 The NAPTR regexp field is represented in this mapping using a 172 character string with an unspecified maximum length. This field can 173 contain numerous backslashes and should thus be treated with care. 175 2.2.6 Replacement 177 The NAPTR replacement field, whose value is a domain name, is 178 represented in this mapping using a character string with a maximum 179 length of 255 characters. 181 3. EPP Command Mapping 183 A detailed description of the EPP syntax and semantics can be found 184 in the EPP core protocol specification [5]. The command mappings 185 described here are specifically for use in implementing ENUM 186 provisioning processes via EPP. 188 3.1 EPP Query Commands 190 EPP provides three commands to retrieve object information: 191 to determine if an object is known to the server, to retrieve 192 detailed information associated with an object, and to 193 retrieve object transfer status information. 195 3.1.1 EPP Command 197 This extension does not add any elements to the EPP command 198 or response described in the EPP domain mapping [1]. 200 3.1.2 EPP Command 202 This extension does not add any elements to the EPP command 203 described in the EPP domain mapping [1]. Additional elements are 204 defined for the response. 206 When an command has been processed successfully, the EPP 207 element MUST contain child elements as described in the EPP 208 domain mapping [1]. In addition, the EPP element MUST 209 contain a child element that identifies the extension 210 namespace and the location of the extension schema. The 211 element contains one or more elements 212 that contain the following child elements: 214 - An element that contains a NAPTR order value. 216 - An element that contains a NAPTR preference value. 218 - An OPTIONAL element that contains a NAPTR flags 219 value. 221 - An element that contains a NAPTR service value. 223 - An OPTIONAL element that contains a NAPTR regular 224 expression value. 226 - An OPTIONAL element that contains a NAPTR 227 replacement value. 229 Example response: 231 S: 232 S: 236 S: 237 S: 238 S: Command completed successfully 239 S: 240 S: 241 S: 245 S: 3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa 246 S: EXAMPLE1-REP 247 S: 248 S: jd1234 249 S: sh8013 250 S: sh8013 251 S: 252 S: ns1.example.com 253 S: ns2.example.com 254 S: 255 S: ns1.example.com 256 S: ns2.example.com 257 S: ClientX 258 S: ClientY 259 S: 1999-04-03T22:00:00.0Z 260 S: ClientX 261 S: 1999-12-03T09:00:00.0Z 262 S: 2005-04-03T22:00:00.0Z 263 S: 2000-04-08T09:00:00.0Z 264 S: 265 S: 2fooBAR 266 S: 267 S: 268 S: 269 S: 270 S: 273 S: 274 S: 10 275 S: 100 276 S: u 277 S: E2U+sip 278 S: "!^.*$!sip:info@example.com!" 279 S: 280 S: 281 S: 10 282 S: 102 283 S: u 284 S: E2U+msg 285 S: "!^.*$!mailto:info@example.com!" 286 S: 287 S: 288 S: 289 S: 290 S: ABC-12345 291 S: 54322-XYZ 292 S: 293 S: 294 S: 296 An EPP error response MUST be returned if an extended command 297 can not be processed for any reason. 299 3.1.3 EPP Command 301 This extension does not add any elements to the EPP 302 command or response described in the EPP domain mapping 303 [1]. 305 3.2 EPP Transform Commands 307 EPP provides five commands to transform objects: to create 308 an instance of an object, to delete an instance of an 309 object, to extend the validity period of an object, 310 to manage object sponsorship changes, and to 311 change information associated with an object. 313 3.2.1 EPP Command 315 This extension defines additional elements for the EPP 316 command described in the EPP domain mapping [1]. No additional 317 elements are defined for the EPP response. 319 The EPP command provides a transform operation that allows a 320 client to create a domain object. In addition to the EPP command 321 elements described in the EPP domain mapping [1], the command MUST 322 contain an element. The element MUST contain 323 a child element that identifies the extension namespace 324 and the location of the extension schema. The element 325 contains one or more elements that contain the following 326 child elements: 328 - An element that contains a NAPTR order value. 330 - An element that contains a NAPTR preference value. 332 - An OPTIONAL element that contains a NAPTR flags 333 value. 335 - An element that contains a NAPTR service value. 337 - An OPTIONAL element that contains a NAPTR regular 338 expression value. 340 - An OPTIONAL element that contains a NAPTR 341 replacement value. 343 Example command: 345 C: 346 C: 350 C: 351 C: 352 C: 356 C: 3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa 357 C: 2 358 C: 359 C: ns1.example.com 360 C: ns2.example.com 361 C: 362 C: jd1234 363 C: sh8013 364 C: sh8013 365 C: 366 C: 2fooBAR 367 C: 368 C: 369 C: 370 C: 371 C: 375 C: 376 C: 10 377 C: 100 378 C: u 379 C: E2U+sip 380 C: "!^.*$!sip:info@example.com!" 381 C: 382 C: 383 C: 10 384 C: 102 385 C: u 386 C: E2U+msg 387 C: "!^.*$!mailto:info@example.com!" 388 C: 389 C: 390 C: 391 C: ABC-12345 392 C: 393 C: 395 When an extended command has been processed successfully, 396 the EPP response is as described in the EPP domain mapping [1]. 398 3.2.2 EPP Command 400 This extension does not add any elements to the EPP command 401 or response described in the EPP domain mapping [1]. 403 3.2.3 EPP Command 405 This extension does not add any elements to the EPP command 406 or response described in the EPP domain mapping [1]. 408 3.2.4 EPP Command 410 This extension does not add any elements to the EPP 411 command or response described in the EPP domain mapping 412 [1]. 414 3.2.5 EPP Command 416 This extension defines additional elements for the EPP 417 command described in the EPP domain mapping [1]. No additional 418 elements are defined for the EPP response. 420 The EPP command provides a transform operation that allows a 421 client to change the state of a domain object. In addition to the 422 EPP command elements described in the EPP domain mapping [1], the 423 command MUST contain an element. The 424 element MUST contain a child element that 425 identifies the extension namespace and the location of the extension 426 schema. The element contains one or more or 427 elements. Each and element contains 428 an element that contains the following child elements: 430 - An element that contains a NAPTR order value. 432 - An element that contains a NAPTR preference value. 434 - An OPTIONAL element that contains a NAPTR flags 435 value. 437 - An element that contains a NAPTR service value. 439 - An OPTIONAL element that contains a NAPTR regular 440 expression value. 442 - An OPTIONAL element that contains a NAPTR 443 replacement value. 445 Example command: 447 C: 448 C: 452 C: 453 C: 454 C: 458 C: 3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa 459 C: 460 C: 461 C: 462 C: 465 C: 466 C: 467 C: 10 468 C: 102 469 C: u 470 C: E2U+msg 471 C: "!^.*$!mailto:info@example.com!" 472 C: 473 C: 474 C: 475 C: 476 C: ABC-12345 477 C: 478 C: 480 When an extended command has been processed successfully, 481 the EPP response is as described in the EPP domain mapping [1]. 483 4. Formal Syntax 485 An EPP object mapping is specified in XML Schema notation. The 486 formal syntax presented here is a complete schema representation of 487 the object mapping suitable for automated validation of EPP XML 488 instances. The BEGIN and END tags are not part of the schema; they 489 are used to note the beginning and ending of the schema for URI 490 registration purposes. 492 BEGIN 493 494 499 500 501 Extensible Provisioning Protocol v1.0 502 domain name extension schema for E.164 number provisioning. 503 504 506 509 510 512 515 517 520 521 522 523 524 526 527 528 529 530 532 533 535 537 538 540 541 542 543 544 545 547 548 549 550 551 553 554 555 556 557 559 560 561 562 563 564 566 569 570 571 573 575 576 578 581 582 583 584 585 587 590 592 595 596 597 598 599 601 604 605 END 607 5. Internationalization Considerations 609 EPP is represented in XML, which provides native support for encoding 610 information using the Unicode character set and its more compact 611 representations including UTF-8 [10]. Conformant XML processors 612 recognize both UTF-8 and UTF-16 [11]. Though XML includes provisions 613 to identify and use other character encodings through use of an 614 "encoding" attribute in an declaration, use of UTF-8 is 615 RECOMMENDED in environments where parser encoding support 616 incompatibility exists. 618 As an extension of the EPP domain mapping [1], the elements, element 619 content, attributes, and attribute values described in this document 620 MUST inherit the internationalization conventions used to represent 621 higher-layer domain and core protocol structures present in an XML 622 instance that includes this extension. 624 6. IANA Considerations 626 This document uses URNs to describe XML namespaces and XML schemas 627 conforming to a registry mechanism described in RFC 3688 [9]. Two 628 URI assignments are requested. 630 Registration request for the extension namespace: 632 URI: urn:ietf:params:xml:ns:e164epp-1.0 634 Registrant Contact: IESG 636 XML: None. Namespace URIs do not represent an XML specification. 638 Registration request for the extension XML schema: 640 URI: urn:ietf:params:xml:schema:e164epp-1.0 642 Registrant Contact: IESG 644 XML: See the "Formal Syntax" section of this document. 646 7. Security Considerations 648 The mapping extensions described in this document do not provide any 649 security services beyond those described by EPP [5], the EPP domain 650 name mapping [1], and protocol layers used by EPP. Security 651 considerations related to ENUM are described in the "Security 652 Considerations" section of the ENUM specification [6]; security 653 considerations related to the Dynamic Delegation Discovery System and 654 NAPTR records are described in the "Security Considerations" section 655 of RFC 3403 [8]. The security considerations described in these 656 other specifications apply to this specification as well. 658 As with other domain object transforms, the EPP transform operations 659 described in this document MUST be restricted to the sponsoring 660 client as authenticated using the mechanisms described in sections 661 2.9.1.1 and 7 of RFC 3730 [5]. Any attempt to perform a transform 662 operation on a domain object by any client other than the sponsoring 663 client MUST be rejected with an appropriate EPP authorization error. 665 8. Acknowledgements 667 The author would like to thank the following people who have provided 668 significant contributions to the development of this document: 670 Lawrence Conroy, Edward Lewis, Michael Mealling, Allison Mankin, Chip 671 Sharp, and James Yu. 673 9. References 675 9.1 Normative References 677 [1] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Domain 678 Name Mapping", RFC 3731, March 2004. 680 [2] Paoli, J., Sperberg-McQueen, C., Bray, T. and E. Maler, 681 "Extensible Markup Language (XML) 1.0 (Second Edition)", W3C 682 FirstEdition REC-xml-20001006, October 2000. 684 [3] Maloney, M., Beech, D., Mendelsohn, N. and H. Thompson, "XML 685 Schema Part 1: Structures", W3C REC REC-xmlschema-1-20010502, 686 May 2001. 688 [4] Malhotra, A. and P. Biron, "XML Schema Part 2: Datatypes", W3C 689 REC REC-xmlschema-2-20010502, May 2001. 691 [5] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", RFC 692 3730, March 2004. 694 [6] Faltstrom, P. and M. Mealling, "The E.164 to Uniform Resource 695 Identifiers (URI) Dynamic Delegation Discovery System (DDDS) 696 Application (ENUM)", RFC 3761, April 2004. 698 [7] Bradner, S., "Key words for use in RFCs to Indicate Requirement 699 Levels", BCP 14, RFC 2119, March 1997. 701 [8] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part 702 Three: The Domain Name System (DNS) Database", RFC 3403, October 703 2002. 705 [9] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 706 2004. 708 9.2 Informative References 710 [10] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 711 63, RFC 3629, November 2003. 713 [11] Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO 10646", 714 RFC 2781, February 2000. 716 Author's Address 718 Scott Hollenbeck 719 VeriSign, Inc. 720 21345 Ridgetop Circle 721 Dulles, VA 20166-6503 722 US 724 EMail: shollenbeck@verisign.com 726 Intellectual Property Statement 728 The IETF takes no position regarding the validity or scope of any 729 Intellectual Property Rights or other rights that might be claimed to 730 pertain to the implementation or use of the technology described in 731 this document or the extent to which any license under such rights 732 might or might not be available; nor does it represent that it has 733 made any independent effort to identify any such rights. Information 734 on the procedures with respect to rights in RFC documents can be 735 found in BCP 78 and BCP 79. 737 Copies of IPR disclosures made to the IETF Secretariat and any 738 assurances of licenses to be made available, or the result of an 739 attempt made to obtain a general license or permission for the use of 740 such proprietary rights by implementers or users of this 741 specification can be obtained from the IETF on-line IPR repository at 742 http://www.ietf.org/ipr. 744 The IETF invites any interested party to bring to its attention any 745 copyrights, patents or patent applications, or other proprietary 746 rights that may cover technology that may be required to implement 747 this standard. Please address the information to the IETF at 748 ietf-ipr@ietf.org. 750 Disclaimer of Validity 752 This document and the information contained herein are provided on an 753 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 754 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 755 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 756 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 757 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 758 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 760 Copyright Statement 762 Copyright (C) The Internet Society (2004). This document is subject 763 to the rights, licenses and restrictions contained in BCP 78, and 764 except as set forth therein, the authors retain all their rights. 766 Acknowledgment 768 Funding for the RFC Editor function is currently provided by the 769 Internet Society.