idnits 2.17.1 draft-snell-atompub-feature-04.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 577. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 588. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 595. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 601. 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 (May 23, 2007) is 6176 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 May 23, 2007 4 Intended status: Standards Track 5 Expires: November 24, 2007 7 Atom Publishing Protocol Features Extension 8 draft-snell-atompub-feature-04.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 November 24, 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. The 'f:feature' element . . . . . . . . . . . . . . . . . . . 3 51 3.1. Example . . . . . . . . . . . . . . . . . . . . . . . . . 5 52 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 53 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 54 5.1. Registry of Atom Publishing Features . . . . . . . . . . . 5 55 5.1.1. Initial Assignments . . . . . . . . . . . . . . . . . 6 56 6. Normative References . . . . . . . . . . . . . . . . . . . . . 12 57 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 13 58 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 13 59 Intellectual Property and Copyright Statements . . . . . . . . . . 14 61 1. Introduction 63 This document introduces extensions for the Atom Publishing Protocol 64 service document format for expressing metadata about the behaviors, 65 functions and capabilities supported by an Atom Publishing Protocol 66 server implementation. 68 2. Notational Conventions 70 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 71 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 72 document are to be interpreted as described in BCP 14, [RFC2119]. 74 This specification uses XML Namespaces [W3C.REC-xml-names-19990114] 75 to uniquely identify XML element names. It uses the following 76 namespace prefix for the indicated namespace URI; 78 "f": "http://purl.org/atompub/features/1.0" 80 This specification uses terms from the XML Infoset 81 [W3C.REC-xml-infoset-20040204]. However, this specification uses a 82 shorthand; the phrase "Information Item" is omitted when naming 83 Element Information Items. Therefore, when this specification uses 84 the terms "element" and "attribute" it is referring, respectively, to 85 the Element and Attribute Information Items in Infoset terms. 87 This specification uses the terms "atomUri" and 88 "atomCommonAttributes" from the non-normative RELAX NG Compact schema 89 included in [RFC4287]. Where used, these serve the same purpose and 90 have the same meaning as their use in [RFC4287]. 92 3. The 'f:feature' element 94 A feature is an abstract behavior, function and capability supported 95 by an Atom Publishing Protocol server. Examples of features that 96 might be supported by an APP server include support for draft 97 entries, scheduled publication of entries, use of a particular set of 98 Atom format extensions, use of a particular authentication scheme, 99 and so on. The presence of a f:feature element in an app:collection 100 element is an indication that the collection supports the feature 101 specified and may require that a client wishing to use the endpoint 102 use that feature. Features are identified using permanent, 103 universally unique IRI's. 105 feature = element f:feature { 106 atomCommonAttributes, 107 attribute ref { atomUri }, 108 attribute required { 'yes' | 'no' }?, 109 attribute href { atomUri }?, 110 attribute label { text }?, 111 (anyElement)* 112 } 114 anyElement = element * - f:* { 115 (attribute * { text } 116 | text 117 | anyElement)* 118 } 120 The "ref" attribute specifies a globally unique IRI identifying a 121 feature supported by a collection. The value of the ref attribute 122 MUST be compared on a case-sensitive, character-by-character basis. 123 Relative references MUST NOT be used. 125 A 'required' attribute value of "yes" indicates that clients MUST 126 utilize the identified feature when interacting with the collection. 127 A server MAY reject requests from clients that do not support or use 128 the feature. If not specified, the value is assumed to be "no". 130 An optional 'href' attribute MAY be used to specify the URI of a 131 human-readable description of the feature. Relative references MAY 132 be used. 134 The optional 'label' attribute MAY be used to specify a human- 135 readable label for the feature. The value of the 'label' attribute 136 is Language-Sensitive as defined by Section 2 of [RFC4287]. 138 The f:feature element MAY contain child elements and attributes other 139 than those defined in this specification. Such "foreign markup" are 140 considered to be metadata applicable to the feature identified by the 141 f:feature element. Software agents MUST NOT stop processing or 142 signal an error or change their behavior as a result of encountering 143 such foreign markup. 145 An app:collection element MAY contain zero or more f:feature elements 146 but MUST NOT contain more than one with the same ref attribute value. 147 The order in which f:feature elements appear within the app: 148 collection element is insignificant. 150 The f:feature element MAY contain attributes included as part of the 151 atomCommonAttributes production defined by Section 2 of [RFC4287] or 152 any update thereof. When used on an f:feature element, such 153 attributes serve the same purpose described in [RFC4287] or their 154 corresponding specifications. 156 3.1. Example 158 The following is an example of a collection supporting one 159 hypothetical required feature and a number of optional features. 161 162 163 164 ... 165 166 167 168 169 173 174 175 177 4. Security Considerations 179 Specific features supported by a collection may introduce security 180 considerations and concerns beyond those discussed by the Atom 181 Publishing Protocol and Atom Syndication Format specifications. 182 Implementors must refer to the specifications and description of each 183 feature to determine the security considerations relevant to each. 185 5. IANA Considerations 187 5.1. Registry of Atom Publishing Features 189 The Registry of Atom Publishing Features is maintained by IANA and 190 contains information about known features that can be supported by 191 Atom Publishing Protocol implementations. New assignments are 192 subject to IESG approval, as outlined in [RFC2434]. Requests should 193 be made by email to IANA, which will then forward the request to the 194 IESG, requesting approval. The request should use the following 195 template: 197 o Ref: (A globally unique IRI identifying the feature) 198 o Label: (A human-readable label for the feature) 199 o Description: (A human-readable description of the feature) 200 o Href: (A URI referencing a document containing a detailed 201 definition of the feature) 202 o Security Considerations: 204 5.1.1. Initial Assignments 206 The Registry of Features initially contains the following 207 assignments: 209 5.1.1.1. Drafts - http://purl.org/atom/app/drafts 211 o Ref: http://purl.org/atom/app/drafts 212 o Label: Drafts 213 o Description: The "Drafts" feature indicates that a collection 214 supports the use of the app:draft control element as defined in 215 section 13.1.1 of [I-D.ietf-atompub-protocol]. 216 o Href: http://www.ietf.org/internet-drafts/ 217 draft-ietf-atompub-protocol-14.txt 218 o Security Considerations: 220 5.1.1.2. Preserve Entries - http://purl.org/atom/app/preserve-entry 222 o Ref: http://purl.org/atom/app/preserve-entry 223 o Label: Preserve Entries 224 o Description: The "Preserve Entries" feature indicates that a 225 server will preserve the semantic content of entries POST and PUT 226 to the collection without making any modifications. 227 o Href: http://www.ietf.org/internet-drafts/ 228 draft-ietf-atompub-protocol-14.txt 229 o Security Considerations: 231 5.1.1.3. Preserve IDs - http://purl.org/atom/app/preserve-id 233 o Ref: http://purl.org/atom/app/preserve-id 234 o Label: Preserve IDs 235 o Description: The "Preserve IDs" feature indicates that a server 236 will preserve the atom:id of entries added to a collection. 237 o Href: http://www.ietf.org/internet-drafts/ 238 draft-ietf-atompub-protocol-14.txt 239 o Security Considerations: 241 5.1.1.4. XHTML Content - http://purl.org/atom/app/xhtml-content 242 o Ref: http://purl.org/atom/app/xhtml-content 243 o Label: XHTML Content 244 o Description: The "XHTML Content" feature indicates that a server 245 will accept XHTML within the atom:content element. 246 o Href: http://www.ietf.org/internet-drafts/ 247 draft-ietf-atompub-protocol-14.txt 248 o Security Considerations: 250 5.1.1.5. HTML Content - http://purl.org/atom/app/html-content 252 o Ref: http://purl.org/atom/app/html-content 253 o Label: HTML Content 254 o Description: The "HTML Content" feature indicates that a server 255 will accept escaped HTML within the atom:content element. 256 o Href: http://www.ietf.org/internet-drafts/ 257 draft-ietf-atompub-protocol-14.txt 258 o Security Considerations: 260 5.1.1.6. Text Content - http://purl.org/atom/app/text-content 262 o Ref: http://purl.org/atom/app/text-content 263 o Label: Text Content 264 o Description: The "Text Content" feature indicates that a server 265 will accept plain text within the atom:content element. 266 o Href: http://www.ietf.org/internet-drafts/ 267 draft-ietf-atompub-protocol-14.txt 268 o Security Considerations: 270 5.1.1.7. XML Content - http://purl.org/atom/app/xml-content 272 o Ref: http://purl.org/atom/app/xml-content 273 o Label: XML Content 274 o Description: The "XML Content" feature indicates that a server 275 will accept well-formed XML content within the atom:content 276 element. 277 o Href: http://www.ietf.org/internet-drafts/ 278 draft-ietf-atompub-protocol-14.txt 279 o Security Considerations: 281 5.1.1.8. Binary Content - http://purl.org/atom/app/binary-content 283 o Ref: http://purl.org/atom/app/xhtml-content 284 o Label: Binary Content 285 o Description: The "Binary Content" feature indicates that a server 286 will accept Base-64 encoded binary data within the atom:content 287 element. 289 o Href: http://www.ietf.org/internet-drafts/ 290 draft-ietf-atompub-protocol-14.txt 291 o Security Considerations: 293 5.1.1.9. Referenced Content - http://purl.org/atom/app/src-content 295 o Ref: http://purl.org/atom/app/ref-content 296 o Label: XHTML Content 297 o Description: The "Referenced Content" feature indicates that a 298 server will accept atom:content elements that use the src 299 attribute to reference external content resources. 300 o Href: http://www.ietf.org/internet-drafts/ 301 draft-ietf-atompub-protocol-14.txt 302 o Security Considerations: 304 5.1.1.10. XHTML Title - http://purl.org/atom/app/xhtml-title 306 o Ref: http://purl.org/atom/app/xhtml-title 307 o Label: XHTML Title 308 o Description: The "XHTML Title" feature indicates that a server 309 will accept XHTML within the atom:title element. 310 o Href: http://www.ietf.org/internet-drafts/ 311 draft-ietf-atompub-protocol-14.txt 312 o Security Considerations: 314 5.1.1.11. HTML Title - http://purl.org/atom/app/html-title 316 o Ref: http://purl.org/atom/app/html-title 317 o Label: HTML Title 318 o Description: The "HTML Content" feature indicates that a server 319 will accept escaped HTML within the atom:title element. 320 o Href: http://www.ietf.org/internet-drafts/ 321 draft-ietf-atompub-protocol-14.txt 322 o Security Considerations: 324 5.1.1.12. Text Title - http://purl.org/atom/app/text-title 326 o Ref: http://purl.org/atom/app/text-title 327 o Label: Text Title 328 o Description: The "Text Content" feature indicates that a server 329 will accept plain text within the atom:title element. 330 o Href: http://www.ietf.org/internet-drafts/ 331 draft-ietf-atompub-protocol-14.txt 332 o Security Considerations: 334 5.1.1.13. XHTML Summary - http://purl.org/atom/app/xhtml-summary 336 o Ref: http://purl.org/atom/app/xhtml-summary 337 o Label: XHTML Summary 338 o Description: The "XHTML Summary" feature indicates that a server 339 will accept XHTML within the atom:summary element. 340 o Href: http://www.ietf.org/internet-drafts/ 341 draft-ietf-atompub-protocol-14.txt 342 o Security Considerations: 344 5.1.1.14. HTML Summary - http://purl.org/atom/app/html-summary 346 o Ref: http://purl.org/atom/app/html-summary 347 o Label: HTML Summary 348 o Description: The "HTML Summary" feature indicates that a server 349 will accept escaped HTML within the atom:summary element. 350 o Href: http://www.ietf.org/internet-drafts/ 351 draft-ietf-atompub-protocol-14.txt 352 o Security Considerations: 354 5.1.1.15. Text Summary - http://purl.org/atom/app/text-summary 356 o Ref: http://purl.org/atom/app/text-summary 357 o Label: Text Summary 358 o Description: The "Text Summary" feature indicates that a server 359 will accept plain text within the atom:summary element. 360 o Href: http://www.ietf.org/internet-drafts/ 361 draft-ietf-atompub-protocol-14.txt 362 o Security Considerations: 364 5.1.1.16. Auto Summary - http://purl.org/atom/app/auto-summary 366 o Ref: http://purl.org/atom/app/auto-summary 367 o Label: Auto Summary 368 o Description: The "Auto Summary" feature indicates that a server 369 will autogenerate the value of the atom:summary element and will 370 either reject or ignore attempts by the client to modify the value 371 of atom:summary. 372 o Href: http://www.ietf.org/internet-drafts/ 373 draft-ietf-atompub-protocol-14.txt 374 o Security Considerations: 376 5.1.1.17. XHTML Rights - http://purl.org/atom/app/xhtml-rights 378 o Ref: http://purl.org/atom/app/xhtml-rights 379 o Label: XHTML Rights 380 o Description: The "XHTML Rights" feature indicates that a server 381 will accept XHTML within the atom:rights element. 382 o Href: http://www.ietf.org/internet-drafts/ 383 draft-ietf-atompub-protocol-14.txt 384 o Security Considerations: 386 5.1.1.18. HTML Rights - http://purl.org/atom/app/html-rights 388 o Ref: http://purl.org/atom/app/html-rights 389 o Label: HTML Rights 390 o Description: The "HTML Rights" feature indicates that a server 391 will accept escaped HTML within the atom:rights element. 392 o Href: http://www.ietf.org/internet-drafts/ 393 draft-ietf-atompub-protocol-14.txt 394 o Security Considerations: 396 5.1.1.19. Text Rights - http://purl.org/atom/app/text-rights 398 o Ref: http://purl.org/atom/app/text-rights 399 o Label: Text Rights 400 o Description: The "Text Rights" feature indicates that a server 401 will accept plain text within the atom:rights element. 402 o Href: http://www.ietf.org/internet-drafts/ 403 draft-ietf-atompub-protocol-14.txt 404 o Security Considerations: 406 5.1.1.20. Authenticated Author - http://purl.org/atom/app/auth-author 408 o Ref: http://purl.org/atom/app/auth-author 409 o Label: Authenticated Author 410 o Description: The "Authenticated Author" feature indicates that a 411 server will use the authenticated identity of the client to 412 determine the values to use within the atom:author element. 413 Attempts by a client to manually set or modify the author 414 information will either be rejected or ignored by the server. 415 o Href: http://www.ietf.org/internet-drafts/ 416 draft-ietf-atompub-protocol-14.txt 417 o Security Considerations: 419 5.1.1.21. Preserve Updated - http://purl.org/atom/app/preserve-updated 421 o Ref: http://purl.org/atom/app/preserve-updated 422 o Label: Preserve Updated 423 o Description: The "Preserve Updated" feature indicates that a 424 server will preserve the value of the atom:updated element 425 provided by a client. 427 o Href: http://www.ietf.org/internet-drafts/ 428 draft-ietf-atompub-protocol-14.txt 429 o Security Considerations: 431 5.1.1.22. Preserve Extensions - 432 http://purl.org/atom/app/preserve-extensions 434 o Ref: http://purl.org/atom/app/preserve-extensions 435 o Label: Preserve Extensions 436 o Description: The "Preserve Extensions" feature indicates that a 437 server will preserve arbitrary unknown foreign markup contained 438 within an entry. 439 o Href: http://www.ietf.org/internet-drafts/ 440 draft-ietf-atompub-protocol-14.txt 441 o Security Considerations: 443 5.1.1.23. Preserve Links - http://purl.org/atom/app/preserve-links 445 o Ref: http://purl.org/atom/app/preserve-links 446 o Label: Preserve Links 447 o Description: The "Preserve Links" feature indicates that a server 448 will preserve all atom:link elements contained within an entry. 449 o Href: http://www.ietf.org/internet-drafts/ 450 draft-ietf-atompub-protocol-14.txt 451 o Security Considerations: 453 5.1.1.24. Preserve Links - http://purl.org/atom/app/preserve-rights 455 o Ref: http://purl.org/atom/app/preserve-rights 456 o Label: Preserve Rights 457 o Description: The "Preserve Rights" feature indicates that a server 458 will preserve all atom:rights elements contained within an entry. 459 o Href: http://www.ietf.org/internet-drafts/ 460 draft-ietf-atompub-protocol-14.txt 461 o Security Considerations: 463 5.1.1.25. Slug - http://purl.org/atom/app/slug 465 o Ref: http://purl.org/atom/app/slug 466 o Label: Slug 467 o Description: The "Slug" feature indicates that a server will use 468 the Slug request header defined in section 9.7 of 469 [I-D.ietf-atompub-protocol] to set the URI of newly created 470 resources. 471 o Security Considerations: 473 5.1.1.26. Multiple Categories - 474 http://purl.org/atom/app/multiple-categories 476 o Ref: http://purl.org/atom/app/multiple-categories 477 o Label: Multiple Categories 478 o Description: The "Multiple Categories" feature indicates that a 479 server will accept entries that contain multiple atom:category 480 elements. 481 o Href: http://www.ietf.org/internet-drafts/ 482 draft-ietf-atompub-protocol-14.txt 483 o Security Considerations: 485 5.1.1.27. Contributors - http://purl.org/atom/app/contributors 487 o Ref: http://purl.org/atom/app/contributors 488 o Label: Contributors 489 o Description: The "Contributors" feature indicates that a server 490 will accept and preserve atom:contributor elements contained by an 491 entry. 492 o Href: http://www.ietf.org/internet-drafts/ 493 draft-ietf-atompub-protocol-14.txt 494 o Security Considerations: 496 5.1.1.28. Multiple Authors - http://purl.org/atom/app/multiple-authors 498 o Ref: http://purl.org/atom/app/multiple-authors 499 o Label: Multiple Authors 500 o Description: The "Multiple Authors" feature indicates that a 501 server will accept and preserve multiple atom:author elements 502 contained by an entry. 503 o Href: http://www.ietf.org/internet-drafts/ 504 draft-ietf-atompub-protocol-14.txt 505 o Security Considerations: 507 5.1.1.29. Feed Thread - http://purl.org/syndication/thread/1.0 509 o Ref: http://purl.org/syndication/thread/1.0 510 o Label: Feed Thread 511 o Description: The Feed Thread feature indicates that the APP server 512 accepts entries that contain the in-reply-to element as defined by 513 [RFC4685]. 514 o Security Considerations: 516 6. Normative References 518 [I-D.ietf-atompub-protocol] 519 Hora, B. and J. Gregorio, "The Atom Publishing Protocol", 520 draft-ietf-atompub-protocol-14 (work in progress), 521 March 2007. 523 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 524 Requirement Levels", BCP 14, RFC 2119, March 1997. 526 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an 527 IANA Considerations Section in RFCs", BCP 26, RFC 2434, 528 October 1998. 530 [RFC4287] Nottingham, M., Ed. and R. Sayre, Ed., "The Atom 531 Syndication Format", RFC 4287, December 2005. 533 [RFC4685] Snell, J., "Atom Threading Extensions", RFC 4685, 534 September 2006. 536 [W3C.REC-xml-infoset-20040204] 537 Cowan, J. and R. Tobin, "XML Information Set (Second 538 Edition)", World Wide Web Consortium Recommendation REC- 539 xml-infoset-20040204, February 2004, 540 . 542 [W3C.REC-xml-names-19990114] 543 Bray, T., Hollander, D., and A. Layman, "Namespaces in 544 XML", World Wide Web Consortium FirstEdition REC-xml- 545 names-19990114, January 1999, 546 . 548 Appendix A. Acknowledgements 550 The author acknowledges the feedback from Elias Torres, Robert Yates, 551 David Johnson, Byrne Reese, Joe Gregorio, Bill de hO`ra and the other 552 members of the IETF Atom Publishing working group during the 553 development of this specification. 555 Author's Address 557 James M Snell 559 Phone: 560 Email: jasnell@gmail.com 561 URI: http://snellspace.com 563 Full Copyright Statement 565 Copyright (C) The IETF Trust (2007). 567 This document is subject to the rights, licenses and restrictions 568 contained in BCP 78, and except as set forth therein, the authors 569 retain all their rights. 571 This document and the information contained herein are provided on an 572 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 573 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 574 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 575 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 576 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 577 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 579 Intellectual Property 581 The IETF takes no position regarding the validity or scope of any 582 Intellectual Property Rights or other rights that might be claimed to 583 pertain to the implementation or use of the technology described in 584 this document or the extent to which any license under such rights 585 might or might not be available; nor does it represent that it has 586 made any independent effort to identify any such rights. Information 587 on the procedures with respect to rights in RFC documents can be 588 found in BCP 78 and BCP 79. 590 Copies of IPR disclosures made to the IETF Secretariat and any 591 assurances of licenses to be made available, or the result of an 592 attempt made to obtain a general license or permission for the use of 593 such proprietary rights by implementers or users of this 594 specification can be obtained from the IETF on-line IPR repository at 595 http://www.ietf.org/ipr. 597 The IETF invites any interested party to bring to its attention any 598 copyrights, patents or patent applications, or other proprietary 599 rights that may cover technology that may be required to implement 600 this standard. Please address the information to the IETF at 601 ietf-ipr@ietf.org. 603 Acknowledgment 605 Funding for the RFC Editor function is provided by the IETF 606 Administrative Support Activity (IASA).