idnits 2.17.1 draft-snell-atompub-feature-02.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 on line 15. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 648. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 659. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 666. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 672. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust 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 (March 19, 2007) is 6247 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) == Outdated reference: A later version (-17) exists of draft-ietf-atompub-protocol-14 ** Obsolete normative reference: RFC 2434 (Obsoleted by RFC 5226) Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Snell 3 Internet-Draft March 19, 2007 4 Intended status: Standards Track 5 Expires: September 20, 2007 7 Atom Publishing Protocol Features Extension 8 draft-snell-atompub-feature-02.txt 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 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 Internet- 20 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 September 20, 2007. 35 Copyright Notice 37 Copyright (C) The IETF Trust (2007). 39 Abstract 41 This document introduces extensions to the Atom Publishing Protocol 42 introspection format for expressing metadata about the behaviors, 43 functions and capabilities supported by an Atom Publishing Protocol 44 server implementation. 46 Table of Contents 48 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 49 2. Notational Conventions . . . . . . . . . . . . . . . . . . . . 3 50 3. Feature Introspection and the 'f:feature' element . . . . . . 3 51 3.1. Example . . . . . . . . . . . . . . . . . . . . . . . . . 5 52 4. Publishing Controls and the 'f:control' element . . . . . . . 5 53 4.1. Example . . . . . . . . . . . . . . . . . . . . . . . . . 7 54 5. Security Considerations . . . . . . . . . . . . . . . . . . . 7 55 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 56 6.1. Registry of Features and Controls . . . . . . . . . . . . 8 57 6.1.1. Initial Assignments . . . . . . . . . . . . . . . . . 8 58 7. Normative References . . . . . . . . . . . . . . . . . . . . . 15 59 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 15 60 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 15 61 Intellectual Property and Copyright Statements . . . . . . . . . . 17 63 1. Introduction 65 This document introduces extensions for the Atom Publishing Protocol 66 introspection format for expressing metadata about the behaviors, 67 functions and capabilities supported by an Atom Publishing Protocol 68 server implementation. 70 2. Notational Conventions 72 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 73 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 74 document are to be interpreted as described in BCP 14, [RFC2119]. 76 This specification uses XML Namespaces [W3C.REC-xml-names-19990114] 77 to uniquely identify XML element names. It uses the following 78 namespace prefix for the indicated namespace URI; 80 "f": "http://purl.org/atompub/features/1.0" 82 This specification uses terms from the XML Infoset 83 [W3C.REC-xml-infoset-20040204]. However, this specification uses a 84 shorthand; the phrase "Information Item" is omitted when naming 85 Element Information Items. Therefore, when this specification uses 86 the terms "element" and "attribute" it is referring, respectively, to 87 the Element and Attribute Information Items in Infoset terms. 89 3. Feature Introspection and the 'f:feature' element 91 A feature is an abstract behavior, function and capability supported 92 by an Atom Publishing Protocol server. Examples of features that 93 might be supported by an APP server include support for draft 94 entries, scheduled publication of entries, use of a particular set of 95 Atom format extensions, use of a particular authentication scheme, 96 and so on. The presence of a f:feature element in an app:collection 97 element is an indication that the collection supports the feature 98 specified and may require that a client wishing to use the endpoint 99 use that feature. Features are identified using permanent, 100 universally unique IRI's. 102 feature = element f:feature { 103 atomCommonAttributes, 104 attribute ref { atomUri }, 105 attribute required { 'yes' | 'no' }?, 106 attribute href { atomURI }?, 107 attribute label { text }?, 108 (extensionElement*) 110 } 112 The "ref" attribute specifies an globally unique IRI identifying a 113 feature supported by a collection. The value of the ref attribute 114 MUST be compared on a case-sensitive, character-by-character basis. 115 Relative references MUST NOT be used. 117 A 'required' attribute value of "yes" indicates that clients MUST 118 utilize the identified feature when interacting with the collection. 119 A server MAY reject requests from clients that do not support or use 120 the feature. If not specified, the value is assumed to be "no". 122 An optional 'href' attribute MAY be used to specify the URI of a 123 human-readable description of the feature. Relative references MAY 124 be used. 126 The optional 'label' attribute MAY be used to specify a human- 127 readable label for the feature. The value of the 'label' attribute 128 is Language-Sensitive as defined by Section 2 of [RFC4287]. 130 The f:feature element MAY contain child elements and attributes other 131 than those defined in this specification. Such "foreign markup" are 132 considered to be metadata applicable to the feature identified by the 133 f:feature element. Software agents MUST NOT stop processing or 134 signal an error or change their behavior as a result of encountering 135 such foreign markup. 137 An app:collection element MAY contain zero or more f:feature elements 138 but MUST NOT contain more than one with the same ref attribute value. 139 The order in which f:feature elements appears is insignificant. 141 3.1. Example 143 The following is an example of a collection supporting one required 144 and one optional feature. 146 147 148 149 ... 150 151 154 155 156 160 161 162 164 4. Publishing Controls and the 'f:control' element 166 Publishing Controls are a mechanism provided by the Atom Publishing 167 Protocol to embed metadata within atom:entry elements designed to 168 influence the way a server processes the entry. The app:control 169 element is provided as a convenient container for this metadata 170 within an atom:entry. The Atom Publishing Protocol does not define a 171 mechanism by which clients can discover which publishing controls a 172 server supports. 174 The presence of a f:control element in an app:collection element is 175 an indication that the collection supports the control and may 176 require that a client wishing to use the endpoint use that control. 177 Controls are identified using permanent, universally unique IRI's. 179 control = element f:control { 180 atomCommonAttributes, 181 attribute ref { atomUri }, 182 attribute required { 'yes' | 'no' }?, 183 attribute href { atomURI }?, 184 attribute label { text }?, 185 (extensionElement*) 186 } 188 The "ref" attribute specifies an globally unique IRI identifying a 189 control supported by a collection. The value of the ref attribute 190 MUST be compared on a case-sensitive, character-by-character basis. 191 Relative references MUST NOT be used. 193 A 'required' attribute value of "yes" indicates that clients MUST 194 utilize the identified control when interacting with the collection. 195 A server MAY reject requests from clients that do not support or use 196 the control. If not specified, the value is assumed to be "no". 198 An optional 'href' attribute MAY be used to specify the URI of a 199 human-readable description of the control. Relative references MAY 200 be used. 202 The optional 'label' attribute MAY be used to specify a human- 203 readable label for the control. The value of the 'label' attribute 204 is Language-Sensitive as defined by Section 2 of [RFC4287]. 206 The f:control element MAY contain child elements and attributes other 207 than those defined in this specification. Such "foreign markup" are 208 considered to be metadata applicable to the control identified by the 209 f:control element. Software agents MUST NOT stop processing or 210 signal an error or change their behavior as a result of encountering 211 such foreign markup. 213 An app:collection element MAY contain zero or more f:control elements 214 but MUST NOT contain more than one with the same ref attribute value. 215 The order in which f:control elements appear is insignificant. 217 4.1. Example 219 The following is an example of a collection supporting one required 220 and one optional control. 222 223 224 225 ... 226 228 230 231 markdown 232 wiki 233 line-breaks 234 235 236 237 238 239 241 An example atom:entry using the listed controls could appear as: 243 244 ... 245 246 yes 247 markdown 248 line-breaks 249 250 ... 251 253 5. Security Considerations 255 Specific features and controls supported by a collection may 256 introduce security considerations and concerns beyond those discussed 257 by the Atom Publishing Protocol and Atom Syndication Format 258 specifications. Implementors must refer to the specifications and 259 description of each feature and control to determine the security 260 considerations relevant to each. 262 6. IANA Considerations 264 6.1. Registry of Features and Controls 266 The Registry of Features and Controls is maintained by IANA and 267 contains information about known features and controls that can be 268 supported by Atom Publishing Protocol implementations. New 269 assignments are subject to IESG approval, as outlined in [RFC2434]. 270 Requests should be made by email to IANA, which will then forward the 271 request to the IESG, requesting approval. The request should use the 272 following template: 274 o Type: ("Control" or "Feature") 275 o Ref: (A globally unique IRI identifying the control or feature) 276 o Label: (A human-readable label for the feature) 277 o Description: 278 o Href: (A URI referencing a document containing a detailed 279 definition of the control or feature) 280 o Security Considerations: 282 6.1.1. Initial Assignments 284 The Registry of Features and Controls initially contains the 285 following assignments: 287 6.1.1.1. Drafts - http://purl.org/atom/app#drafts 289 o Type: Feature 290 o Ref: http://purl.org/atom/app#drafts 291 o Label: Drafts 292 o Description: The "Drafts" feature indicates that a collection 293 supports the use of the app:draft control element as defined in 294 section 13.1.1 of [I-D.ietf-atompub-protocol]. 295 o Href: http://www.ietf.org/internet-drafts/ 296 draft-ietf-atompub-protocol-14.txt 297 o Security Considerations: 299 6.1.1.2. Preserve Entries - http://purl.org/atom/app#preserve-entry 301 o Type: Feature 302 o Ref: http://purl.org/atom/app#preserve-entry 303 o Label: Preserve Entries 304 o Description: The "Preserve Entries" feature indicates that a 305 server will preserve the semantic content of entries POST and PUT 306 to the collection without modification. 307 o Href: http://www.ietf.org/internet-drafts/ 308 draft-ietf-atompub-protocol-14.txt 310 o Security Considerations: 312 6.1.1.3. Preserve IDs - http://purl.org/atom/app#preserve-id 314 o Type: Feature 315 o Ref: http://purl.org/atom/app#preserve-id 316 o Label: Preserve IDs 317 o Description: The "Preserve IDs" feature indicates that a server 318 will preserve the atom:id of entries POSTed to a collection. 319 o Href: http://www.ietf.org/internet-drafts/ 320 draft-ietf-atompub-protocol-14.txt 321 o Security Considerations: 323 6.1.1.4. XHTML Content - http://purl.org/atom/app#xhtml-content 325 o Type: Feature 326 o Ref: http://purl.org/atom/app#xhtml-content 327 o Label: XHTML Content 328 o Description: The "XHTML Content" feature indicates that a server 329 will accept XHTML within the atom:content element. 330 o Href: http://www.ietf.org/internet-drafts/ 331 draft-ietf-atompub-protocol-14.txt 332 o Security Considerations: 334 6.1.1.5. HTML Content - http://purl.org/atom/app#html-content 336 o Type: Feature 337 o Ref: http://purl.org/atom/app#html-content 338 o Label: HTML Content 339 o Description: The "HTML Content" feature indicates that a server 340 will accept escaped HTML within the atom:content element. 341 o Href: http://www.ietf.org/internet-drafts/ 342 draft-ietf-atompub-protocol-14.txt 343 o Security Considerations: 345 6.1.1.6. Text Content - http://purl.org/atom/app#text-content 347 o Type: Feature 348 o Ref: http://purl.org/atom/app#text-content 349 o Label: Text Content 350 o Description: The "Text Content" feature indicates that a server 351 will accept plain text within the atom:content element. 352 o Href: http://www.ietf.org/internet-drafts/ 353 draft-ietf-atompub-protocol-14.txt 354 o Security Considerations: 356 6.1.1.7. Binary Content - http://purl.org/atom/app#binary-content 358 o Type: Feature 359 o Ref: http://purl.org/atom/app#xhtml-content 360 o Label: Binary Content 361 o Description: The "Binary Content" feature indicates that a server 362 will accept Base-64 encoded binary data within the atom:content 363 element. 364 o Href: http://www.ietf.org/internet-drafts/ 365 draft-ietf-atompub-protocol-14.txt 366 o Security Considerations: 368 6.1.1.8. Referenced Content - http://purl.org/atom/app#ref-content 370 o Type: Feature 371 o Ref: http://purl.org/atom/app#ref-content 372 o Label: XHTML Content 373 o Description: The "Referenced Content" feature indicates that a 374 server will accept atom:content elements that use the src 375 attribute to reference external content resources. 376 o Href: http://www.ietf.org/internet-drafts/ 377 draft-ietf-atompub-protocol-14.txt 378 o Security Considerations: 380 6.1.1.9. XHTML Title - http://purl.org/atom/app#xhtml-title 382 o Type: Feature 383 o Ref: http://purl.org/atom/app#xhtml-title 384 o Label: XHTML Title 385 o Description: The "XHTML Title" feature indicates that a server 386 will accept XHTML within the atom:title element. 387 o Href: http://www.ietf.org/internet-drafts/ 388 draft-ietf-atompub-protocol-14.txt 389 o Security Considerations: 391 6.1.1.10. HTML Title - http://purl.org/atom/app#html-title 393 o Type: Feature 394 o Ref: http://purl.org/atom/app#html-title 395 o Label: HTML Title 396 o Description: The "HTML Content" feature indicates that a server 397 will accept escaped HTML within the atom:title element. 398 o Href: http://www.ietf.org/internet-drafts/ 399 draft-ietf-atompub-protocol-14.txt 400 o Security Considerations: 402 6.1.1.11. Text Title - http://purl.org/atom/app#text-title 404 o Type: Feature 405 o Ref: http://purl.org/atom/app#text-title 406 o Label: Text Title 407 o Description: The "Text Content" feature indicates that a server 408 will accept plain text within the atom:title element. 409 o Href: http://www.ietf.org/internet-drafts/ 410 draft-ietf-atompub-protocol-14.txt 411 o Security Considerations: 413 6.1.1.12. XHTML Summary - http://purl.org/atom/app#xhtml-summary 415 o Type: Feature 416 o Ref: http://purl.org/atom/app#xhtml-summary 417 o Label: XHTML Summary 418 o Description: The "XHTML Summary" feature indicates that a server 419 will accept XHTML within the atom:summary element. 420 o Href: http://www.ietf.org/internet-drafts/ 421 draft-ietf-atompub-protocol-14.txt 422 o Security Considerations: 424 6.1.1.13. HTML Summary - http://purl.org/atom/app#html-summary 426 o Type: Feature 427 o Ref: http://purl.org/atom/app#html-summary 428 o Label: HTML Summary 429 o Description: The "HTML Summary" feature indicates that a server 430 will accept escaped HTML within the atom:summary element. 431 o Href: http://www.ietf.org/internet-drafts/ 432 draft-ietf-atompub-protocol-14.txt 433 o Security Considerations: 435 6.1.1.14. Text Summary - http://purl.org/atom/app#text-summary 437 o Type: Feature 438 o Ref: http://purl.org/atom/app#text-summary 439 o Label: Text Summary 440 o Description: The "Text Summary" feature indicates that a server 441 will accept plain text within the atom:summary element. 442 o Href: http://www.ietf.org/internet-drafts/ 443 draft-ietf-atompub-protocol-14.txt 444 o Security Considerations: 446 6.1.1.15. Auto Summary - http://purl.org/atom/app#auto-summary 447 o Type: Feature 448 o Ref: http://purl.org/atom/app#auto-summary 449 o Label: Auto Summary 450 o Description: The "Auto Summary" feature indicates that a server 451 will autogenerate the value of the atom:summary element and will 452 either reject or ignore attempts by the client to modify the value 453 of atom:summary. 454 o Href: http://www.ietf.org/internet-drafts/ 455 draft-ietf-atompub-protocol-14.txt 456 o Security Considerations: 458 6.1.1.16. XHTML Rights - http://purl.org/atom/app#xhtml-rights 460 o Type: Feature 461 o Ref: http://purl.org/atom/app#xhtml-rights 462 o Label: XHTML Rights 463 o Description: The "XHTML Rights" feature indicates that a server 464 will accept XHTML within the atom:rights element. 465 o Href: http://www.ietf.org/internet-drafts/ 466 draft-ietf-atompub-protocol-14.txt 467 o Security Considerations: 469 6.1.1.17. HTML Rights - http://purl.org/atom/app#html-rights 471 o Type: Feature 472 o Ref: http://purl.org/atom/app#html-rights 473 o Label: HTML Rights 474 o Description: The "HTML Rights" feature indicates that a server 475 will accept escaped HTML within the atom:rights element. 476 o Href: http://www.ietf.org/internet-drafts/ 477 draft-ietf-atompub-protocol-14.txt 478 o Security Considerations: 480 6.1.1.18. Text Rights - http://purl.org/atom/app#text-rights 482 o Type: Feature 483 o Ref: http://purl.org/atom/app#text-rights 484 o Label: Text Rights 485 o Description: The "Text Rights" feature indicates that a server 486 will accept plain text within the atom:rights element. 487 o Href: http://www.ietf.org/internet-drafts/ 488 draft-ietf-atompub-protocol-14.txt 489 o Security Considerations: 491 6.1.1.19. Authenticated Author - http://purl.org/atom/app#auth-author 492 o Type: Feature 493 o Ref: http://purl.org/atom/app#auth-author 494 o Label: Authenticated Author 495 o Description: The "Authenticated Author" feature indicates that a 496 server will use the authenticated identity of the client to 497 determine the values to use within the atom:author element. 498 Attempts by a client to manually set or modify the author 499 information will either be rejected or ignored by the server. 500 o Href: http://www.ietf.org/internet-drafts/ 501 draft-ietf-atompub-protocol-14.txt 502 o Security Considerations: 504 6.1.1.20. Preserve Updated - http://purl.org/atom/app#preserve-updated 506 o Type: Feature 507 o Ref: http://purl.org/atom/app#preserve-updated 508 o Label: Preserve Updated 509 o Description: The "Preserve Updated" feature indicates that a 510 server will preserve the value of the atom:updated element 511 provided by a client. 512 o Href: http://www.ietf.org/internet-drafts/ 513 draft-ietf-atompub-protocol-14.txt 514 o Security Considerations: 516 6.1.1.21. Preserve Extensions - 517 http://purl.org/atom/app#preserve-extensions 519 o Type: Feature 520 o Ref: http://purl.org/atom/app#preserve-extensions 521 o Label: Preserve Extensions 522 o Description: The "Preserve Extensions" feature indicates that a 523 server will preserve arbitrary unknown foreign markup contained 524 within an entry. 525 o Href: http://www.ietf.org/internet-drafts/ 526 draft-ietf-atompub-protocol-14.txt 527 o Security Considerations: 529 6.1.1.22. Preserve Links - http://purl.org/atom/app#preserve-links 531 o Type: Feature 532 o Ref: http://purl.org/atom/app#preserve-links 533 o Label: Preserve Links 534 o Description: The "Preserve Links" feature indicates that a server 535 will preserve all atom:link elements contained within an entry. 536 o Href: http://www.ietf.org/internet-drafts/ 537 draft-ietf-atompub-protocol-14.txt 539 o Security Considerations: 541 6.1.1.23. Slug - http://purl.org/atom/app#slug 543 o Type: Feature 544 o Ref: http://purl.org/atom/app#slug 545 o Label: Slug 546 o Description: The "Slug" feature indicates that a server will use 547 the Slug request header defined in section 9.7 of 548 [I-D.ietf-atompub-protocol] to set the URI of newly created 549 resources. 550 o Security Considerations: 552 6.1.1.24. Multiple Categories - 553 http://purl.org/atom/app#multiple-categories 555 o Type: Feature 556 o Ref: http://purl.org/atom/app#multiple-categories 557 o Label: Multiple Categories 558 o Description: The "Multiple Categories" feature indicates that a 559 server will accept entries that contain multiple atom:category 560 elements. 561 o Href: http://www.ietf.org/internet-drafts/ 562 draft-ietf-atompub-protocol-14.txt 563 o Security Considerations: 565 6.1.1.25. Contributors - http://purl.org/atom/app#contributors 567 o Type: Feature 568 o Ref: http://purl.org/atom/app#contributors 569 o Label: Contributors 570 o Description: The "Contributors" feature indicates that a server 571 will accept and preserve atom:contributor elements contained by an 572 entry. 573 o Href: http://www.ietf.org/internet-drafts/ 574 draft-ietf-atompub-protocol-14.txt 575 o Security Considerations: 577 6.1.1.26. Multiple Authors - http://purl.org/atom/app#multiple-authors 579 o Type: Feature 580 o Ref: http://purl.org/atom/app#multiple-authors 581 o Label: Multiple Authors 582 o Description: The "Multiple Authors" feature indicates that a 583 server will accept and preserve multiple atom:author elements 584 contained by an entry. 586 o Href: http://www.ietf.org/internet-drafts/ 587 draft-ietf-atompub-protocol-14.txt 588 o Security Considerations: 590 7. Normative References 592 [I-D.ietf-atompub-protocol] 593 Hora, B. and J. Gregorio, "The Atom Publishing Protocol", 594 draft-ietf-atompub-protocol-14 (work in progress), 595 March 2007. 597 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 598 Requirement Levels", BCP 14, RFC 2119, March 1997. 600 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an 601 IANA Considerations Section in RFCs", BCP 26, RFC 2434, 602 October 1998. 604 [RFC4287] Nottingham, M., Ed. and R. Sayre, Ed., "The Atom 605 Syndication Format", RFC 4287, December 2005. 607 [W3C.REC-xml-infoset-20040204] 608 Cowan, J. and R. Tobin, "XML Information Set (Second 609 Edition)", World Wide Web Consortium Recommendation REC- 610 xml-infoset-20040204, February 2004, 611 . 613 [W3C.REC-xml-names-19990114] 614 Layman, A., Hollander, D., and T. Bray, "Namespaces in 615 XML", World Wide Web Consortium FirstEdition REC-xml- 616 names-19990114, January 1999, 617 . 619 Appendix A. Acknowledgements 621 The author acknowledges the feedback from Elias Torres, Robert Yates, 622 David Johnson, Byrne Reese, Joe Gregorio and the other members of the 623 IETF Atom Publishing working group during the development of this 624 specification. 626 Author's Address 628 James M Snell 630 Phone: 631 Email: jasnell@gmail.com 632 URI: http://snellspace.com 634 Full Copyright Statement 636 Copyright (C) The IETF Trust (2007). 638 This document is subject to the rights, licenses and restrictions 639 contained in BCP 78, and except as set forth therein, the authors 640 retain all their rights. 642 This document and the information contained herein are provided on an 643 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 644 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 645 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 646 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 647 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 648 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 650 Intellectual Property 652 The IETF takes no position regarding the validity or scope of any 653 Intellectual Property Rights or other rights that might be claimed to 654 pertain to the implementation or use of the technology described in 655 this document or the extent to which any license under such rights 656 might or might not be available; nor does it represent that it has 657 made any independent effort to identify any such rights. Information 658 on the procedures with respect to rights in RFC documents can be 659 found in BCP 78 and BCP 79. 661 Copies of IPR disclosures made to the IETF Secretariat and any 662 assurances of licenses to be made available, or the result of an 663 attempt made to obtain a general license or permission for the use of 664 such proprietary rights by implementers or users of this 665 specification can be obtained from the IETF on-line IPR repository at 666 http://www.ietf.org/ipr. 668 The IETF invites any interested party to bring to its attention any 669 copyrights, patents or patent applications, or other proprietary 670 rights that may cover technology that may be required to implement 671 this standard. Please address the information to the IETF at 672 ietf-ipr@ietf.org. 674 Acknowledgment 676 Funding for the RFC Editor function is provided by the IETF 677 Administrative Support Activity (IASA).