Changeset 1103
- Timestamp:
- 01/02/11 09:13:55 (11 years ago)
- Files:
-
- 68 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis-authscheme-registrations/latest/draft-ietf-httpbis-authscheme-registrations.html
r1099 r1103 314 314 } 315 315 @top-right { 316 content: " January 2011";316 content: "February 2011"; 317 317 } 318 318 @top-center { … … 323 323 } 324 324 @bottom-center { 325 content: " Informational";325 content: "Expires August 5, 2011"; 326 326 } 327 327 @bottom-right { … … 350 350 <link rel="Appendix" title="A Initial Registry Contents" href="#rfc.section.A"> 351 351 <link rel="Appendix" title="B Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.B"> 352 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.5 37, 2010-12-30 14:21:59, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">352 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.540, 2011-01-10 09:27:20, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 353 353 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 354 354 <meta name="dct.creator" content="Reschke, J. F."> 355 355 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-authscheme-registrations-latest"> 356 <meta name="dct.issued" scheme="ISO8601" content="2011-0 1-01">356 <meta name="dct.issued" scheme="ISO8601" content="2011-02-01"> 357 357 <meta name="dct.abstract" content="This document registers Hypertext Transfer Protocol (HTTP) authentication schemes which have been defined in standards-track RFCs before the IANA HTTP Authentication Scheme Registry was established."> 358 358 <meta name="description" content="This document registers Hypertext Transfer Protocol (HTTP) authentication schemes which have been defined in standards-track RFCs before the IANA HTTP Authentication Scheme Registry was established."> … … 371 371 <tr> 372 372 <td class="left">Intended status: Informational</td> 373 <td class="right"> January 1, 2011</td>373 <td class="right">February 1, 2011</td> 374 374 </tr> 375 375 <tr> 376 <td class="left">Expires: July5, 2011</td>376 <td class="left">Expires: August 5, 2011</td> 377 377 <td class="right"></td> 378 378 </tr> … … 399 399 in progress”. 400 400 </p> 401 <p>This Internet-Draft will expire on July5, 2011.</p>401 <p>This Internet-Draft will expire on August 5, 2011.</p> 402 402 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 403 403 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis-authscheme-registrations/latest/draft-ietf-httpbis-authscheme-registrations.xml
r1099 r1103 41 41 </author> 42 42 43 <date month=" January" year="2011"/>43 <date month="February" year="2011"/> 44 44 <workgroup>HTTPbis Working Group</workgroup> 45 45 -
draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.html
r1099 r1103 356 356 } 357 357 @top-right { 358 content: " January 2011";358 content: "February 2011"; 359 359 } 360 360 @top-center { … … 365 365 } 366 366 @bottom-center { 367 content: " Standards Track";367 content: "Expires August 5, 2011"; 368 368 } 369 369 @bottom-right { … … 400 400 <link rel="Appendix" title="C Alternative Approaches to Internationalization" href="#rfc.section.C"> 401 401 <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D"> 402 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.5 37, 2010-12-30 14:21:59, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">402 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.540, 2011-01-10 09:27:20, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 403 403 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 404 404 <meta name="dct.creator" content="Reschke, J. F."> 405 405 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-content-disp-latest"> 406 <meta name="dct.issued" scheme="ISO8601" content="2011-0 1-01">406 <meta name="dct.issued" scheme="ISO8601" content="2011-02-01"> 407 407 <meta name="dct.abstract" content="HTTP/1.1 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard. This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization aspects."> 408 408 <meta name="description" content="HTTP/1.1 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard. This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization aspects."> … … 422 422 <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved) 423 423 </td> 424 <td class="right"> January 1, 2011</td>424 <td class="right">February 1, 2011</td> 425 425 </tr> 426 426 <tr> … … 429 429 </tr> 430 430 <tr> 431 <td class="left">Expires: July5, 2011</td>431 <td class="left">Expires: August 5, 2011</td> 432 432 <td class="right"></td> 433 433 </tr> … … 458 458 in progress”. 459 459 </p> 460 <p>This Internet-Draft will expire on July5, 2011.</p>460 <p>This Internet-Draft will expire on August 5, 2011.</p> 461 461 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 462 462 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 657 657 filename="EURO rates"; 658 658 filename*=utf-8''<b>%e2%82%ac</b>%20rates 659 </pre> <p>Note: as of January 2011, those user agents that do not support the RFC 5987 encoding ignore "filename*" when it occurs after659 </pre> <p>Note: as of February 2011, those user agents that do not support the RFC 5987 encoding ignore "filename*" when it occurs after 660 660 "filename". Unfortunately, some user agents that do support RFC 5987 do pick the "filename" rather than the "filename*" parameter 661 661 when it occurs first; it is expected that this situation is going to improve soon. … … 824 824 <p id="rfc.section.C.3.p.2">As with the approaches above, this is not interoperable and furthermore risks misinterpreting the actual value.</p> 825 825 <h2 id="rfc.section.C.4"><a href="#rfc.section.C.4">C.4</a> <a id="alternatives.implementations" href="#alternatives.implementations">Implementations (to be removed by RFC Editor before publication)</a></h2> 826 <p id="rfc.section.C.4.p.1">Unfortunately, as of January 2011, neither the encoding defined in RFCs 2231 and 5987, nor any of the alternate approaches826 <p id="rfc.section.C.4.p.1">Unfortunately, as of February 2011, neither the encoding defined in RFCs 2231 and 5987, nor any of the alternate approaches 827 827 discussed above was implemented interoperably. Thus, this specification recommends the approach defined in RFC 5987, which 828 828 at least has the advantage of actually being specified properly. -
draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml
r1099 r1103 42 42 </author> 43 43 44 <date month=" January" year="2011"/>44 <date month="February" year="2011"/> 45 45 <workgroup>HTTPbis Working Group</workgroup> 46 46 … … 328 328 </artwork> 329 329 <postamble> 330 Note: as of January 2011, those user agents that do not support the RFC 5987330 Note: as of February 2011, those user agents that do not support the RFC 5987 331 331 encoding ignore "filename*" when it occurs after "filename". Unfortunately, 332 332 some user agents that do support RFC 5987 do pick the "filename" rather … … 742 742 <section title="Implementations (to be removed by RFC Editor before publication)" anchor="alternatives.implementations"> 743 743 <t> 744 Unfortunately, as of January 2011, neither the encoding defined in RFCs 2231744 Unfortunately, as of February 2011, neither the encoding defined in RFCs 2231 745 745 and 5987, nor any of the alternate approaches discussed above was 746 746 implemented interoperably. Thus, this specification recommends the approach -
draft-ietf-httpbis-method-registrations/latest/draft-ietf-httpbis-method-registrations.html
r1100 r1103 314 314 } 315 315 @top-right { 316 content: " January 2011";316 content: "February 2011"; 317 317 } 318 318 @top-center { … … 323 323 } 324 324 @bottom-center { 325 content: " Informational";325 content: "Expires August 5, 2011"; 326 326 } 327 327 @bottom-right { … … 350 350 <link rel="Appendix" title="A Initial Registry Contents" href="#rfc.section.A"> 351 351 <link rel="Appendix" title="B Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.B"> 352 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.5 37, 2010-12-30 14:21:59, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">352 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.540, 2011-01-10 09:27:20, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 353 353 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 354 354 <meta name="dct.creator" content="Reschke, J. F."> 355 355 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-method-registrations-latest"> 356 <meta name="dct.issued" scheme="ISO8601" content="2011-0 1-06">356 <meta name="dct.issued" scheme="ISO8601" content="2011-02-01"> 357 357 <meta name="dct.abstract" content="This document registers those Hypertext Transfer Protocol (HTTP) methods which have been defined in standards-track RFCs before the IANA HTTP Method Registry was established."> 358 358 <meta name="description" content="This document registers those Hypertext Transfer Protocol (HTTP) methods which have been defined in standards-track RFCs before the IANA HTTP Method Registry was established."> … … 371 371 <tr> 372 372 <td class="left">Intended status: Informational</td> 373 <td class="right"> January 6, 2011</td>373 <td class="right">February 1, 2011</td> 374 374 </tr> 375 375 <tr> 376 <td class="left">Expires: July 10, 2011</td>376 <td class="left">Expires: August 5, 2011</td> 377 377 <td class="right"></td> 378 378 </tr> … … 399 399 in progress”. 400 400 </p> 401 <p>This Internet-Draft will expire on July 10, 2011.</p>401 <p>This Internet-Draft will expire on August 5, 2011.</p> 402 402 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 403 403 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis-method-registrations/latest/draft-ietf-httpbis-method-registrations.xml
r1100 r1103 41 41 </author> 42 42 43 <date month=" January" year="2011"/>43 <date month="February" year="2011"/> 44 44 <workgroup>HTTPbis Working Group</workgroup> 45 45 -
draft-ietf-httpbis/latest/p1-messaging.html
r1101 r1103 344 344 } 345 345 @top-right { 346 content: " January 2011";346 content: "February 2011"; 347 347 } 348 348 @top-center { … … 353 353 } 354 354 @bottom-center { 355 content: " Standards Track";355 content: "Expires August 5, 2011"; 356 356 } 357 357 @bottom-right { … … 392 392 <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C"> 393 393 <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D"> 394 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.5 37, 2010-12-30 14:21:59, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">394 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.540, 2011-01-10 09:27:20, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 395 395 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 396 396 <meta name="dct.creator" content="Fielding, R."> … … 404 404 <meta name="dct.creator" content="Reschke, J. F."> 405 405 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 406 <meta name="dct.issued" scheme="ISO8601" content="2011-0 1-08">406 <meta name="dct.issued" scheme="ISO8601" content="2011-02-01"> 407 407 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 408 408 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 1 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the "http" and "https" Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations."> … … 435 435 </tr> 436 436 <tr> 437 <td class="left">Expires: July 12, 2011</td>437 <td class="left">Expires: August 5, 2011</td> 438 438 <td class="right">HP</td> 439 439 </tr> … … 488 488 <tr> 489 489 <td class="left"></td> 490 <td class="right"> January 8, 2011</td>490 <td class="right">February 1, 2011</td> 491 491 </tr> 492 492 </tbody> … … 516 516 in progress”. 517 517 </p> 518 <p>This Internet-Draft will expire on July 12, 2011.</p>518 <p>This Internet-Draft will expire on August 5, 2011.</p> 519 519 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 520 520 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 712 712 MIME-like message payloads for flexible interaction with network-based hypertext information systems. HTTP relies upon the 713 713 Uniform Resource Identifier (URI) standard <a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a> to indicate request targets and relationships between resources. Messages are passed in a format similar to that used by Internet 714 mail <a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a> and the Multipurpose Internet Mail Extensions (MIME) <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a> (see <a href="p3-payload.html#differences.between.http.and.mime" title=" ERROR: Anchor 'differences.between.http.and.mime' not found in p3-payload.xml.">Appendix ERROR: Anchor 'differences.between.http.and.mime' in Part3 not found in source file 'p3-payload.xml'.</a> of <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a> for the differences between HTTP and MIME messages).714 mail <a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a> and the Multipurpose Internet Mail Extensions (MIME) <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a> (see <a href="p3-payload.html#differences.between.http.and.mime" title="Differences between HTTP and MIME">Appendix A</a> of <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a> for the differences between HTTP and MIME messages). 715 715 </p> 716 716 <p id="rfc.section.1.p.2">HTTP is a generic interface protocol for information systems. It is designed to hide the details of how a service is implemented … … 860 860 <div id="rfc.figure.u.12"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">request-header</a> = <request-header, defined in <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 3</a>> 861 861 <a href="#abnf.dependencies" class="smpl">response-header</a> = <response-header, defined in <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 5</a>> 862 </pre><div id="rfc.figure.u.13"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">MIME-Version</a> = <MIME-Version, defined in <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#mime-version" title=" ERROR: Anchor 'mime-version' not found in p3-payload.xml.">Appendix ERROR: Anchor 'mime-version' in Part3 not found in source file 'p3-payload.xml'.</a>>862 </pre><div id="rfc.figure.u.13"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">MIME-Version</a> = <MIME-Version, defined in <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#mime-version" title="MIME-Version">Appendix A.1</a>> 863 863 </pre><div id="rfc.figure.u.14"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">Cache-Control</a> = <Cache-Control, defined in <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.pragma" title="Pragma">Section 3.4</a>> 864 864 <a href="#abnf.dependencies" class="smpl">Pragma</a> = <Pragma, defined in <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.pragma" title="Pragma">Section 3.4</a>> … … 1313 1313 / <a href="#header.via" class="smpl">Via</a> ; <a href="#header.via" id="rfc.xref.header.via.1" title="Via">Section 9.9</a> 1314 1314 / <a href="#abnf.dependencies" class="smpl">Warning</a> ; <a href="#Part6" id="rfc.xref.Part6.8"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.warning" title="Warning">Section 3.6</a> 1315 / <a href="#abnf.dependencies" class="smpl">MIME-Version</a> ; <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#mime-version" title=" ERROR: Anchor 'mime-version' not found in p3-payload.xml.">Appendix ERROR: Anchor 'mime-version' in Part3 not found in source file 'p3-payload.xml'.</a>1315 / <a href="#abnf.dependencies" class="smpl">MIME-Version</a> ; <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#mime-version" title="MIME-Version">Appendix A.1</a> 1316 1316 </pre><p id="rfc.section.3.4.p.3">General-header field names can be extended reliably only in combination with a change in the protocol version. However, new 1317 1317 or experimental header fields might be given the semantics of general header fields if all parties in the communication recognize … … 1707 1707 <li>Pointer to specification text</li> 1708 1708 </ul> 1709 <p id="rfc.section.6.2.3.p.3">Names of transfer codings <em class="bcp14">MUST NOT</em> overlap with names of content codings (<a href="p3-payload.html#content.codings" title=" ERROR: Anchor 'content.codings' not found in p3-payload.xml.">Appendix ERROR: Anchor 'content.codings' in Part3 not found in source file 'p3-payload.xml'.</a> of <a href="#Part3" id="rfc.xref.Part3.4"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>), unless the encoding transformation is identical (as it is the case for the compression codings defined in <a href="#compression.codings" title="Compression Codings">Section 6.2.2</a>).1709 <p id="rfc.section.6.2.3.p.3">Names of transfer codings <em class="bcp14">MUST NOT</em> overlap with names of content codings (<a href="p3-payload.html#content.codings" title="Content Codings">Section 2.2</a> of <a href="#Part3" id="rfc.xref.Part3.4"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>), unless the encoding transformation is identical (as it is the case for the compression codings defined in <a href="#compression.codings" title="Compression Codings">Section 6.2.2</a>). 1710 1710 </p> 1711 1711 <p id="rfc.section.6.2.3.p.4">Values to be added to this name space require a specification (see "Specification Required" in <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of transfer coding defined in this section. … … 1726 1726 </p> 1727 1727 <h2 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a> <a id="quality.values" href="#quality.values">Quality Values</a></h2> 1728 <p id="rfc.section.6.4.p.1">Both transfer codings (TE request header field, <a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section 9.5</a>) and content negotiation (<a href="p3-payload.html#content.negotiation" title=" ERROR: Anchor 'content.negotiation' not found in p3-payload.xml.">Appendix ERROR: Anchor 'content.negotiation' in Part3 not found in source file 'p3-payload.xml'.</a> of <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) use short "floating point" numbers to indicate the relative importance ("weight") of various negotiable parameters. A weight1728 <p id="rfc.section.6.4.p.1">Both transfer codings (TE request header field, <a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section 9.5</a>) and content negotiation (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) use short "floating point" numbers to indicate the relative importance ("weight") of various negotiable parameters. A weight 1729 1729 is normalized to a real number in the range 0 through 1, where 0 is the minimum and 1 the maximum value. If a parameter has 1730 1730 a quality value of 0, then content with this parameter is "not acceptable" for the client. HTTP/1.1 applications <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values <em class="bcp14">SHOULD</em> also be limited in this fashion. … … 2183 2183 <h2 id="rfc.section.9.7"><a href="#rfc.section.9.7">9.7</a> <a id="header.transfer-encoding" href="#header.transfer-encoding">Transfer-Encoding</a></h2> 2184 2184 <p id="rfc.section.9.7.p.1">The "Transfer-Encoding" general-header field indicates what transfer-codings (if any) have been applied to the message body. 2185 It differs from Content-Encoding (<a href="p3-payload.html#content.codings" title=" ERROR: Anchor 'content.codings' not found in p3-payload.xml.">Appendix ERROR: Anchor 'content.codings' in Part3 not found in source file 'p3-payload.xml'.</a> of <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) in that transfer-codings are a property of the message (and therefore are removed by intermediaries), whereas content-codings2185 It differs from Content-Encoding (<a href="p3-payload.html#content.codings" title="Content Codings">Section 2.2</a> of <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) in that transfer-codings are a property of the message (and therefore are removed by intermediaries), whereas content-codings 2186 2186 are not. 2187 2187 </p> … … 2670 2670 <tr> 2671 2671 <td class="reference"><b id="Part2">[Part2]</b></td> 2672 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), January 2011.2672 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), February 2011. 2673 2673 </td> 2674 2674 </tr> 2675 2675 <tr> 2676 2676 <td class="reference"><b id="Part3">[Part3]</b></td> 2677 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-latest">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft draft-ietf-httpbis-p3-payload-latest (work in progress), January 2011.2677 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-latest">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft draft-ietf-httpbis-p3-payload-latest (work in progress), February 2011. 2678 2678 </td> 2679 2679 </tr> 2680 2680 <tr> 2681 2681 <td class="reference"><b id="Part6">[Part6]</b></td> 2682 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, <a href="mailto:mnot@mnot.net">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), January 2011.2682 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, <a href="mailto:mnot@mnot.net">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), February 2011. 2683 2683 </td> 2684 2684 </tr> … … 3725 3725 </li> 3726 3726 <li><em>Part3</em> <a href="#rfc.xref.Part3.1">1</a>, <a href="#rfc.xref.Part3.2">1.2.3</a>, <a href="#rfc.xref.Part3.3">3.4</a>, <a href="#rfc.xref.Part3.4">6.2.3</a>, <a href="#rfc.xref.Part3.5">6.4</a>, <a href="#rfc.xref.Part3.6">7.1.3.2</a>, <a href="#rfc.xref.Part3.7">9.7</a>, <a href="#Part3"><b>13.1</b></a>, <a href="#rfc.xref.Part3.8">A</a><ul> 3727 <li><em> Appendix </em> <a href="#rfc.xref.Part3.1">1</a></li>3728 <li><em> Appendix </em> <a href="#rfc.xref.Part3.2">1.2.3</a>, <a href="#rfc.xref.Part3.3">3.4</a></li>3729 <li><em>Appendix </em> <a href="#rfc.xref.Part3.4">6.2.3</a>, <a href="#rfc.xref.Part3.7">9.7</a></li>3730 <li><em>Appendix </em> <a href="#rfc.xref.Part3.5">6.4</a></li>3727 <li><em>Section 2.2</em> <a href="#rfc.xref.Part3.4">6.2.3</a>, <a href="#rfc.xref.Part3.7">9.7</a></li> 3728 <li><em>Section 5</em> <a href="#rfc.xref.Part3.5">6.4</a></li> 3729 <li><em>Appendix A</em> <a href="#rfc.xref.Part3.1">1</a></li> 3730 <li><em>Appendix A.1</em> <a href="#rfc.xref.Part3.2">1.2.3</a>, <a href="#rfc.xref.Part3.3">3.4</a></li> 3731 3731 </ul> 3732 3732 </li> -
draft-ietf-httpbis/latest/p1-messaging.xml
r1101 r1103 13 13 <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>"> 14 14 <!ENTITY ID-VERSION "latest"> 15 <!ENTITY ID-MONTH " January">15 <!ENTITY ID-MONTH "February"> 16 16 <!ENTITY ID-YEAR "2011"> 17 17 <!ENTITY mdash "—"> -
draft-ietf-httpbis/latest/p2-semantics.html
r1101 r1103 344 344 } 345 345 @top-right { 346 content: " January 2011";346 content: "February 2011"; 347 347 } 348 348 @top-center { … … 353 353 } 354 354 @bottom-center { 355 content: " Standards Track";355 content: "Expires August 5, 2011"; 356 356 } 357 357 @bottom-right { … … 391 391 <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B"> 392 392 <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C"> 393 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.5 37, 2010-12-30 14:21:59, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">393 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.540, 2011-01-10 09:27:20, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 394 394 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 395 395 <meta name="dct.creator" content="Fielding, R."> … … 403 403 <meta name="dct.creator" content="Reschke, J. F."> 404 404 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 405 <meta name="dct.issued" scheme="ISO8601" content="2011-0 1-08">405 <meta name="dct.issued" scheme="ISO8601" content="2011-02-01"> 406 406 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 407 407 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request-header fields, response status codes, and response-header fields."> … … 434 434 </tr> 435 435 <tr> 436 <td class="left">Expires: July 12, 2011</td>436 <td class="left">Expires: August 5, 2011</td> 437 437 <td class="right">HP</td> 438 438 </tr> … … 487 487 <tr> 488 488 <td class="left"></td> 489 <td class="right"> January 8, 2011</td>489 <td class="right">February 1, 2011</td> 490 490 </tr> 491 491 </tbody> … … 514 514 in progress”. 515 515 </p> 516 <p>This Internet-Draft will expire on July 12, 2011.</p>516 <p>This Internet-Draft will expire on August 5, 2011.</p> 517 517 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 518 518 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 2253 2253 <tr> 2254 2254 <td class="reference"><b id="Part1">[Part1]</b></td> 2255 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), January 2011.2255 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), February 2011. 2256 2256 </td> 2257 2257 </tr> 2258 2258 <tr> 2259 2259 <td class="reference"><b id="Part3">[Part3]</b></td> 2260 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-latest">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft draft-ietf-httpbis-p3-payload-latest (work in progress), January 2011.2260 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-latest">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft draft-ietf-httpbis-p3-payload-latest (work in progress), February 2011. 2261 2261 </td> 2262 2262 </tr> 2263 2263 <tr> 2264 2264 <td class="reference"><b id="Part4">[Part4]</b></td> 2265 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), January 2011.2265 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), February 2011. 2266 2266 </td> 2267 2267 </tr> 2268 2268 <tr> 2269 2269 <td class="reference"><b id="Part5">[Part5]</b></td> 2270 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), January 2011.2270 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), February 2011. 2271 2271 </td> 2272 2272 </tr> 2273 2273 <tr> 2274 2274 <td class="reference"><b id="Part6">[Part6]</b></td> 2275 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, <a href="mailto:mnot@mnot.net">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), January 2011.2275 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, <a href="mailto:mnot@mnot.net">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), February 2011. 2276 2276 </td> 2277 2277 </tr> 2278 2278 <tr> 2279 2279 <td class="reference"><b id="Part7">[Part7]</b></td> 2280 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">HTTP/1.1, part 7: Authentication</a>”, Internet-Draft draft-ietf-httpbis-p7-auth-latest (work in progress), January 2011.2280 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">HTTP/1.1, part 7: Authentication</a>”, Internet-Draft draft-ietf-httpbis-p7-auth-latest (work in progress), February 2011. 2281 2281 </td> 2282 2282 </tr> -
draft-ietf-httpbis/latest/p2-semantics.xml
r1101 r1103 13 13 <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>"> 14 14 <!ENTITY ID-VERSION "latest"> 15 <!ENTITY ID-MONTH " January">15 <!ENTITY ID-MONTH "February"> 16 16 <!ENTITY ID-YEAR "2011"> 17 17 <!ENTITY mdash "—"> -
draft-ietf-httpbis/latest/p3-payload.html
r1102 r1103 344 344 } 345 345 @top-right { 346 content: " January 2011";346 content: "February 2011"; 347 347 } 348 348 @top-center { … … 353 353 } 354 354 @bottom-center { 355 content: " Standards Track";355 content: "Expires August 5, 2011"; 356 356 } 357 357 @bottom-right { … … 390 390 <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D"> 391 391 <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E"> 392 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.5 37, 2010-12-30 14:21:59, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">392 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.540, 2011-01-10 09:27:20, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 393 393 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 394 394 <meta name="dct.creator" content="Fielding, R."> … … 402 402 <meta name="dct.creator" content="Reschke, J. F."> 403 403 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest"> 404 <meta name="dct.issued" scheme="ISO8601" content="2011-0 1-25">404 <meta name="dct.issued" scheme="ISO8601" content="2011-02-01"> 405 405 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 406 406 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation."> … … 428 428 </tr> 429 429 <tr> 430 <td class="left">Expires: July 29, 2011</td>430 <td class="left">Expires: August 5, 2011</td> 431 431 <td class="right">J. Mogul</td> 432 432 </tr> … … 485 485 <tr> 486 486 <td class="left"></td> 487 <td class="right"> January 25, 2011</td>487 <td class="right">February 1, 2011</td> 488 488 </tr> 489 489 </tbody> … … 511 511 in progress”. 512 512 </p> 513 <p>This Internet-Draft will expire on July 29, 2011.</p>513 <p>This Internet-Draft will expire on August 5, 2011.</p> 514 514 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 515 515 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1519 1519 <tr> 1520 1520 <td class="reference"><b id="Part1">[Part1]</b></td> 1521 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), January 2011.1521 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), February 2011. 1522 1522 </td> 1523 1523 </tr> 1524 1524 <tr> 1525 1525 <td class="reference"><b id="Part2">[Part2]</b></td> 1526 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), January 2011.1526 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), February 2011. 1527 1527 </td> 1528 1528 </tr> 1529 1529 <tr> 1530 1530 <td class="reference"><b id="Part4">[Part4]</b></td> 1531 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), January 2011.1531 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), February 2011. 1532 1532 </td> 1533 1533 </tr> 1534 1534 <tr> 1535 1535 <td class="reference"><b id="Part5">[Part5]</b></td> 1536 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), January 2011.1536 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), February 2011. 1537 1537 </td> 1538 1538 </tr> 1539 1539 <tr> 1540 1540 <td class="reference"><b id="Part6">[Part6]</b></td> 1541 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, <a href="mailto:mnot@mnot.net">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), January 2011.1541 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, <a href="mailto:mnot@mnot.net">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), February 2011. 1542 1542 </td> 1543 1543 </tr> -
draft-ietf-httpbis/latest/p3-payload.xml
r1102 r1103 13 13 <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>"> 14 14 <!ENTITY ID-VERSION "latest"> 15 <!ENTITY ID-MONTH " January">15 <!ENTITY ID-MONTH "February"> 16 16 <!ENTITY ID-YEAR "2011"> 17 17 <!ENTITY mdash "—"> -
draft-ietf-httpbis/latest/p4-conditional.html
r1101 r1103 344 344 } 345 345 @top-right { 346 content: " January 2011";346 content: "February 2011"; 347 347 } 348 348 @top-center { … … 353 353 } 354 354 @bottom-center { 355 content: " Standards Track";355 content: "Expires August 5, 2011"; 356 356 } 357 357 @bottom-right { … … 388 388 <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B"> 389 389 <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C"> 390 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.5 37, 2010-12-30 14:21:59, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">390 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.540, 2011-01-10 09:27:20, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 391 391 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 392 392 <meta name="dct.creator" content="Fielding, R."> … … 400 400 <meta name="dct.creator" content="Reschke, J. F."> 401 401 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest"> 402 <meta name="dct.issued" scheme="ISO8601" content="2011-0 1-08">402 <meta name="dct.issued" scheme="ISO8601" content="2011-02-01"> 403 403 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 404 404 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 4 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests."> … … 426 426 </tr> 427 427 <tr> 428 <td class="left">Expires: July 12, 2011</td>428 <td class="left">Expires: August 5, 2011</td> 429 429 <td class="right">J. Mogul</td> 430 430 </tr> … … 483 483 <tr> 484 484 <td class="left"></td> 485 <td class="right"> January 8, 2011</td>485 <td class="right">February 1, 2011</td> 486 486 </tr> 487 487 </tbody> … … 509 509 in progress”. 510 510 </p> 511 <p>This Internet-Draft will expire on July 12, 2011.</p>511 <p>This Internet-Draft will expire on August 5, 2011.</p> 512 512 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 513 513 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1187 1187 <tr> 1188 1188 <td class="reference"><b id="Part1">[Part1]</b></td> 1189 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), January 2011.1189 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), February 2011. 1190 1190 </td> 1191 1191 </tr> 1192 1192 <tr> 1193 1193 <td class="reference"><b id="Part3">[Part3]</b></td> 1194 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-latest">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft draft-ietf-httpbis-p3-payload-latest (work in progress), January 2011.1194 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-latest">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft draft-ietf-httpbis-p3-payload-latest (work in progress), February 2011. 1195 1195 </td> 1196 1196 </tr> 1197 1197 <tr> 1198 1198 <td class="reference"><b id="Part5">[Part5]</b></td> 1199 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), January 2011.1199 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), February 2011. 1200 1200 </td> 1201 1201 </tr> 1202 1202 <tr> 1203 1203 <td class="reference"><b id="Part6">[Part6]</b></td> 1204 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, <a href="mailto:mnot@mnot.net">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), January 2011.1204 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, <a href="mailto:mnot@mnot.net">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), February 2011. 1205 1205 </td> 1206 1206 </tr> -
draft-ietf-httpbis/latest/p4-conditional.xml
r1099 r1103 13 13 <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>"> 14 14 <!ENTITY ID-VERSION "latest"> 15 <!ENTITY ID-MONTH " January">15 <!ENTITY ID-MONTH "February"> 16 16 <!ENTITY ID-YEAR "2011"> 17 17 <!ENTITY notation "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> -
draft-ietf-httpbis/latest/p5-range.html
r1101 r1103 344 344 } 345 345 @top-right { 346 content: " January 2011";346 content: "February 2011"; 347 347 } 348 348 @top-center { … … 353 353 } 354 354 @bottom-center { 355 content: " Standards Track";355 content: "Expires August 5, 2011"; 356 356 } 357 357 @bottom-right { … … 388 388 <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C"> 389 389 <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D"> 390 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.5 37, 2010-12-30 14:21:59, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">390 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.540, 2011-01-10 09:27:20, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 391 391 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 392 392 <meta name="dct.creator" content="Fielding, R."> … … 400 400 <meta name="dct.creator" content="Reschke, J. F."> 401 401 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 402 <meta name="dct.issued" scheme="ISO8601" content="2011-0 1-08">402 <meta name="dct.issued" scheme="ISO8601" content="2011-02-01"> 403 403 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 404 404 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests."> … … 426 426 </tr> 427 427 <tr> 428 <td class="left">Expires: July 12, 2011</td>428 <td class="left">Expires: August 5, 2011</td> 429 429 <td class="right">J. Mogul</td> 430 430 </tr> … … 483 483 <tr> 484 484 <td class="left"></td> 485 <td class="right"> January 8, 2011</td>485 <td class="right">February 1, 2011</td> 486 486 </tr> 487 487 </tbody> … … 509 509 in progress”. 510 510 </p> 511 <p>This Internet-Draft will expire on July 12, 2011.</p>511 <p>This Internet-Draft will expire on August 5, 2011.</p> 512 512 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 513 513 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1035 1035 <tr> 1036 1036 <td class="reference"><b id="Part1">[Part1]</b></td> 1037 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), January 2011.1037 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), February 2011. 1038 1038 </td> 1039 1039 </tr> 1040 1040 <tr> 1041 1041 <td class="reference"><b id="Part4">[Part4]</b></td> 1042 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), January 2011.1042 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), February 2011. 1043 1043 </td> 1044 1044 </tr> -
draft-ietf-httpbis/latest/p5-range.xml
r1099 r1103 13 13 <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>"> 14 14 <!ENTITY ID-VERSION "latest"> 15 <!ENTITY ID-MONTH " January">15 <!ENTITY ID-MONTH "February"> 16 16 <!ENTITY ID-YEAR "2011"> 17 17 <!ENTITY notation "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> -
draft-ietf-httpbis/latest/p6-cache.html
r1101 r1103 347 347 } 348 348 @top-right { 349 content: " January 2011";349 content: "February 2011"; 350 350 } 351 351 @top-center { … … 356 356 } 357 357 @bottom-center { 358 content: " Standards Track";358 content: "Expires August 5, 2011"; 359 359 } 360 360 @bottom-right { … … 389 389 <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B"> 390 390 <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C"> 391 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.5 37, 2010-12-30 14:21:59, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">391 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.540, 2011-01-10 09:27:20, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 392 392 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 393 393 <meta name="dct.creator" content="Fielding, R."> … … 402 402 <meta name="dct.creator" content="Reschke, J. F."> 403 403 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 404 <meta name="dct.issued" scheme="ISO8601" content="2011-0 1-08">404 <meta name="dct.issued" scheme="ISO8601" content="2011-02-01"> 405 405 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 406 406 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. This document is Part 6 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages."> … … 428 428 </tr> 429 429 <tr> 430 <td class="left">Expires: July 12, 2011</td>430 <td class="left">Expires: August 5, 2011</td> 431 431 <td class="right">J. Mogul</td> 432 432 </tr> … … 489 489 <tr> 490 490 <td class="left"></td> 491 <td class="right"> January 8, 2011</td>491 <td class="right">February 1, 2011</td> 492 492 </tr> 493 493 </tbody> … … 515 515 in progress”. 516 516 </p> 517 <p>This Internet-Draft will expire on July 12, 2011.</p>517 <p>This Internet-Draft will expire on August 5, 2011.</p> 518 518 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 519 519 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1590 1590 <tr> 1591 1591 <td class="reference"><b id="Part1">[Part1]</b></td> 1592 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), January 2011.1592 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), February 2011. 1593 1593 </td> 1594 1594 </tr> 1595 1595 <tr> 1596 1596 <td class="reference"><b id="Part2">[Part2]</b></td> 1597 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), January 2011.1597 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), February 2011. 1598 1598 </td> 1599 1599 </tr> 1600 1600 <tr> 1601 1601 <td class="reference"><b id="Part4">[Part4]</b></td> 1602 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), January 2011.1602 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), February 2011. 1603 1603 </td> 1604 1604 </tr> 1605 1605 <tr> 1606 1606 <td class="reference"><b id="Part5">[Part5]</b></td> 1607 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), January 2011.1607 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), February 2011. 1608 1608 </td> 1609 1609 </tr> 1610 1610 <tr> 1611 1611 <td class="reference"><b id="Part7">[Part7]</b></td> 1612 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">HTTP/1.1, part 7: Authentication</a>”, Internet-Draft draft-ietf-httpbis-p7-auth-latest (work in progress), January 2011.1612 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">HTTP/1.1, part 7: Authentication</a>”, Internet-Draft draft-ietf-httpbis-p7-auth-latest (work in progress), February 2011. 1613 1613 </td> 1614 1614 </tr> -
draft-ietf-httpbis/latest/p6-cache.xml
r1099 r1103 13 13 <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>"> 14 14 <!ENTITY ID-VERSION "latest"> 15 <!ENTITY ID-MONTH " January">15 <!ENTITY ID-MONTH "February"> 16 16 <!ENTITY ID-YEAR "2011"> 17 17 <!ENTITY notation "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> -
draft-ietf-httpbis/latest/p7-auth.html
r1101 r1103 344 344 } 345 345 @top-right { 346 content: " January 2011";346 content: "February 2011"; 347 347 } 348 348 @top-center { … … 353 353 } 354 354 @bottom-center { 355 content: " Standards Track";355 content: "Expires August 5, 2011"; 356 356 } 357 357 @bottom-right { … … 385 385 <link rel="Appendix" title="A Collected ABNF" href="#rfc.section.A"> 386 386 <link rel="Appendix" title="B Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.B"> 387 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.5 37, 2010-12-30 14:21:59, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">387 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.540, 2011-01-10 09:27:20, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 388 388 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 389 389 <meta name="dct.creator" content="Fielding, R."> … … 397 397 <meta name="dct.creator" content="Reschke, J. F."> 398 398 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest"> 399 <meta name="dct.issued" scheme="ISO8601" content="2011-0 1-08">399 <meta name="dct.issued" scheme="ISO8601" content="2011-02-01"> 400 400 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 401 401 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 7 defines HTTP Authentication."> … … 428 428 </tr> 429 429 <tr> 430 <td class="left">Expires: July 12, 2011</td>430 <td class="left">Expires: August 5, 2011</td> 431 431 <td class="right">HP</td> 432 432 </tr> … … 481 481 <tr> 482 482 <td class="left"></td> 483 <td class="right"> January 8, 2011</td>483 <td class="right">February 1, 2011</td> 484 484 </tr> 485 485 </tbody> … … 507 507 in progress”. 508 508 </p> 509 <p>This Internet-Draft will expire on July 12, 2011.</p>509 <p>This Internet-Draft will expire on August 5, 2011.</p> 510 510 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 511 511 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 886 886 <tr> 887 887 <td class="reference"><b id="Part1">[Part1]</b></td> 888 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), January 2011.888 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), February 2011. 889 889 </td> 890 890 </tr> 891 891 <tr> 892 892 <td class="reference"><b id="Part6">[Part6]</b></td> 893 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, <a href="mailto:mnot@mnot.net">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), January 2011.893 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, <a href="mailto:mnot@mnot.net">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), February 2011. 894 894 </td> 895 895 </tr> -
draft-ietf-httpbis/latest/p7-auth.xml
r1101 r1103 13 13 <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>"> 14 14 <!ENTITY ID-VERSION "latest"> 15 <!ENTITY ID-MONTH " January">15 <!ENTITY ID-MONTH "February"> 16 16 <!ENTITY ID-YEAR "2011"> 17 17 <!ENTITY mdash "—"> -
rfc2629xslt/rfc2629.dtd
r799 r1103 105 105 category (std|bcp|info|exp|historic) 106 106 #IMPLIED 107 consensus (no|yes) #IMPLIED 107 108 seriesNo %NUMBER; #IMPLIED 108 109 ipr (full2026|noDerivativeWorks2026|none -
rfc2629xslt/rfc2629.rnc
r799 r1103 67 67 [ a:defaultValue = "" ] attribute updates { NUMBERS }?, 68 68 attribute category { "std" | "bcp" | "info" | "exp" | "historic" }?, 69 attribute consensus { "no" | "yes" }?, 69 70 attribute seriesNo { NUMBER }?, 70 71 attribute ipr { -
rfc2629xslt/rfc2629.xslt
r1099 r1103 2 2 XSLT transformation from RFC2629 XML format to HTML 3 3 4 Copyright (c) 2006-201 0, Julian Reschke (julian.reschke@greenbytes.de)4 Copyright (c) 2006-2011, Julian Reschke (julian.reschke@greenbytes.de) 5 5 All rights reserved. 6 6 … … 2667 2667 2668 2668 <xsl:template name="collectLeftHeaderColumn"> 2669 <xsl:param name="mode" />2670 2669 <!-- default case --> 2671 2670 <xsl:if test="$xml2rfc-private=''"> … … 3656 3655 } 3657 3656 @bottom-center { 3658 content: "<xsl:call-template name="get- category-long"/>";3657 content: "<xsl:call-template name="get-bottom-center"/>"; 3659 3658 } 3660 3659 @bottom-right { … … 3676 3675 } 3677 3676 @bottom-center { 3678 content: "<xsl:call-template name="get- category-long"/>";3677 content: "<xsl:call-template name="get-bottom-center"/>"; 3679 3678 } 3680 3679 @bottom-right { … … 3697 3696 } 3698 3697 @bottom-center { 3699 content: "<xsl:call-template name="get- category-long"/>";3698 content: "<xsl:call-template name="get-bottom-center"/>"; 3700 3699 } 3701 3700 @bottom-right { … … 6056 6055 <xsl:attribute name="title"> 6057 6056 <xsl:if test="@source"><xsl:value-of select="@source"/>: </xsl:if> 6058 <xsl:apply-templates select="text()|eref|xref"/> 6057 <xsl:variable name="content"> 6058 <xsl:apply-templates select="text()|eref|xref"/> 6059 </xsl:variable> 6060 <xsl:value-of select="$content"/> 6059 6061 </xsl:attribute> 6060 6062 <xsl:text>[</xsl:text> … … 6173 6175 </xsl:template> 6174 6176 6177 <xsl:template name="get-bottom-center"> 6178 <xsl:choose> 6179 <xsl:when test="/rfc/@docName"> 6180 <!-- for IDs, use the expiry date --> 6181 <xsl:text>Expires </xsl:text><xsl:call-template name="expirydate" /> 6182 </xsl:when> 6183 <xsl:otherwise> 6184 <xsl:call-template name="get-category-long"/> 6185 </xsl:otherwise> 6186 </xsl:choose> 6187 </xsl:template> 6188 6175 6189 <xsl:template name="get-category-long"> 6176 6190 <xsl:choose> … … 6210 6224 <xsl:text>http://greenbytes.de/tech/webdav/rfc2629.xslt, </xsl:text> 6211 6225 <!-- when RCS keyword substitution in place, add version info --> 6212 <xsl:if test="contains('$Revision: 1.5 37$',':')">6213 <xsl:value-of select="concat('Revision ',normalize-space(translate(substring-after('$Revision: 1.5 37$', 'Revision: '),'$','')),', ')" />6226 <xsl:if test="contains('$Revision: 1.540 $',':')"> 6227 <xsl:value-of select="concat('Revision ',normalize-space(translate(substring-after('$Revision: 1.540 $', 'Revision: '),'$','')),', ')" /> 6214 6228 </xsl:if> 6215 <xsl:if test="contains('$Date: 201 0-12-30 14:21:59$',':')">6216 <xsl:value-of select="concat(normalize-space(translate(substring-after('$Date: 201 0-12-30 14:21:59$', 'Date: '),'$','')),', ')" />6229 <xsl:if test="contains('$Date: 2011-01-10 09:27:20 $',':')"> 6230 <xsl:value-of select="concat(normalize-space(translate(substring-after('$Date: 2011-01-10 09:27:20 $', 'Date: '),'$','')),', ')" /> 6217 6231 </xsl:if> 6218 6232 <xsl:value-of select="concat('XSLT vendor: ',system-property('xsl:vendor'),' ',system-property('xsl:vendor-url'))" /> -
rfc2629xslt/rfc2629toFO.xslt
r981 r1103 2 2 XSLT transformation from RFC2629 XML format to XSL-FO 3 3 4 Copyright (c) 2006-201 0, Julian Reschke (julian.reschke@greenbytes.de)4 Copyright (c) 2006-2011, Julian Reschke (julian.reschke@greenbytes.de) 5 5 All rights reserved. 6 6 … … 2075 2075 </xsl:variable> 2076 2076 <xsl:variable name="center"> 2077 <xsl:call-template name="get- category-long" />2077 <xsl:call-template name="get-bottom-center" /> 2078 2078 </xsl:variable> 2079 2079 <xsl:variable name="right">[Page 999]</xsl:variable> -
rfc2629xslt/rfc2629toXHTML.xslt
r1099 r1103 2535 2535 2536 2536 <xsl:template name="collectLeftHeaderColumn"> 2537 <xsl:param name="mode"/>2538 2537 <!-- default case --> 2539 2538 <xsl:if test="$xml2rfc-private=''"> … … 3524 3523 } 3525 3524 @bottom-center { 3526 content: "<xsl:call-template name="get- category-long"/>";3525 content: "<xsl:call-template name="get-bottom-center"/>"; 3527 3526 } 3528 3527 @bottom-right { … … 3544 3543 } 3545 3544 @bottom-center { 3546 content: "<xsl:call-template name="get- category-long"/>";3545 content: "<xsl:call-template name="get-bottom-center"/>"; 3547 3546 } 3548 3547 @bottom-right { … … 3565 3564 } 3566 3565 @bottom-center { 3567 content: "<xsl:call-template name="get- category-long"/>";3566 content: "<xsl:call-template name="get-bottom-center"/>"; 3568 3567 } 3569 3568 @bottom-right { … … 5914 5913 <xsl:attribute name="title"> 5915 5914 <xsl:if test="@source"><xsl:value-of select="@source"/>: </xsl:if> 5916 <xsl:apply-templates select="text()|eref|xref"/> 5915 <xsl:variable name="content"> 5916 <xsl:apply-templates select="text()|eref|xref"/> 5917 </xsl:variable> 5918 <xsl:value-of select="$content"/> 5917 5919 </xsl:attribute> 5918 5920 <xsl:text>[</xsl:text> … … 6031 6033 </xsl:template> 6032 6034 6035 <xsl:template name="get-bottom-center"> 6036 <xsl:choose> 6037 <xsl:when test="/rfc/@docName"> 6038 <!-- for IDs, use the expiry date --> 6039 <xsl:text>Expires </xsl:text><xsl:call-template name="expirydate"/> 6040 </xsl:when> 6041 <xsl:otherwise> 6042 <xsl:call-template name="get-category-long"/> 6043 </xsl:otherwise> 6044 </xsl:choose> 6045 </xsl:template> 6046 6033 6047 <xsl:template name="get-category-long"> 6034 6048 <xsl:choose> … … 6068 6082 <xsl:text>http://greenbytes.de/tech/webdav/rfc2629.xslt, </xsl:text> 6069 6083 <!-- when RCS keyword substitution in place, add version info --> 6070 <xsl:if test="contains('$Revision: 1.5 37$',':')">6071 <xsl:value-of select="concat('Revision ',normalize-space(translate(substring-after('$Revision: 1.5 37$', 'Revision: '),'$','')),', ')"/>6084 <xsl:if test="contains('$Revision: 1.540 $',':')"> 6085 <xsl:value-of select="concat('Revision ',normalize-space(translate(substring-after('$Revision: 1.540 $', 'Revision: '),'$','')),', ')"/> 6072 6086 </xsl:if> 6073 <xsl:if test="contains('$Date: 201 0-12-30 14:21:59$',':')">6074 <xsl:value-of select="concat(normalize-space(translate(substring-after('$Date: 201 0-12-30 14:21:59$', 'Date: '),'$','')),', ')"/>6087 <xsl:if test="contains('$Date: 2011-01-10 09:27:20 $',':')"> 6088 <xsl:value-of select="concat(normalize-space(translate(substring-after('$Date: 2011-01-10 09:27:20 $', 'Date: '),'$','')),', ')"/> 6075 6089 </xsl:if> 6076 6090 <xsl:value-of select="concat('XSLT vendor: ',system-property('xsl:vendor'),' ',system-property('xsl:vendor-url'))"/> -
rfc2629xslt/rfc2629xslt.html
r1099 r1103 350 350 } 351 351 @top-right { 352 content: " November 2010";352 content: "January 2011"; 353 353 } 354 354 @top-center { … … 377 377 } 378 378 } 379 </style><link rel="Contents" href="#rfc.toc"><link rel="Author" href="#rfc.authors"><link rel="Index" href="#rfc.index"><link rel="Chapter" title="1 Introduction" href="#rfc.section.1"><link rel="Chapter" title="2 Supported RFC2629 elements" href="#rfc.section.2"><link rel="Chapter" title="3 Processing Instructions" href="#rfc.section.3"><link rel="Chapter" title="4 Anchors" href="#rfc.section.4"><link rel="Chapter" title="5 Supported XSLT engines" href="#rfc.section.5"><link rel="Chapter" title="6 Transforming to HTML" href="#rfc.section.6"><link rel="Chapter" title="7 Transforming to XHTML" href="#rfc.section.7"><link rel="Chapter" title="8 Transforming to CHM (Microsoft Compiled Help)" href="#rfc.section.8"><link rel="Chapter" title="9 Transforming to PDF" href="#rfc.section.9"><link rel="Chapter" title="10 Transforming to ePub" href="#rfc.section.10"><link rel="Chapter" title="11 Generic Extensions" href="#rfc.section.11"><link rel="Chapter" title="12 Utilities" href="#rfc.section.12"><link rel="Chapter" href="#rfc.section.13" title="13 Informative References"><link rel="Appendix" title="A RELAX NG Compact Schema" href="#rfc.section.A"><link rel="Appendix" title="B Implementation Notes" href="#rfc.section.B"><link rel="Appendix" title="C Examples" href="#rfc.section.C"><link rel="Appendix" title="D Producing the IETF 'Boilerplate'" href="#rfc.section.D"><link rel="Appendix" title="E License" href="#rfc.section.E"><link rel="Appendix" title="F Change Logs" href="#rfc.section.F"><meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.5 37, 2010-12-30 14:21:59, XSLT vendor: SAXON 6.5.5 from Michael Kay http://saxon.sf.net/"><meta name="keywords" content="RFC2629, xml2rfc, XSLT, hCard, XSL-FO, PDF, GRDDL, epub, Dublin Core"><link rel="schema.dct" href="http://purl.org/dc/terms/"><meta name="dct.creator" content="Reschke, J. F."></head><body><table class="header"><tbody><tr><td class="left">RFC2629 through XSLT</td><td class="right">J. Reschke</td></tr><tr><td class="left"></td><td class="right">greenbytes</td></tr><tr><td class="left"></td><td class="right">November 2010</td></tr></tbody></table><p class="title">Transforming RFC2629-formatted XML through XSLT</p><hr class="noprint"><h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1><ul class="toc"><li>1. <a href="#rfc.section.1">Introduction</a></li><li>2. <a href="#supported.elements">Supported RFC2629 elements</a><ul><li>2.1 <a href="#rfc.section.2.1">Extension elements</a></li></ul></li><li>3. <a href="#processing.instructions">Processing Instructions</a><ul><li>3.1 <a href="#rfc.section.3.1">Supported xml2rfc-compatible PIs</a></li><li>3.2 <a href="#rfc.section.3.2">Unsupported xml2rfc-compatible PIs</a></li><li>3.3 <a href="#rfc.section.3.3">Extension PIs</a></li></ul></li><li>4. <a href="#anchors">Anchors</a></li><li>5. <a href="#xslt.engines">Supported XSLT engines</a><ul><li>5.1 <a href="#rfc.section.5.1">Standalone Engines</a></li><li>5.2 <a href="#xslt.engines.browser">In-Browser Engines</a></li></ul></li><li>6. <a href="#output.html">Transforming to HTML</a><ul><li>6.1 <a href="#rfc.section.6.1">HTML compliance</a></li><li>6.2 <a href="#html.link">Standard HTML LINK elements</a></li><li>6.3 <a href="#rfc.section.6.3">Standard HTML metadata</a></li><li>6.4 <a href="#rfc2731.properties">Dublin Core (RFC2731) metadata</a></li><li>6.5 <a href="#hcard">Experimental hCard support</a></li></ul></li><li>7. <a href="#output.xhtml">Transforming to XHTML</a></li><li>8. <a href="#output.chm">Transforming to CHM (Microsoft Compiled Help)</a></li><li>9. <a href="#output.pdf">Transforming to PDF</a><ul><li>9.1 <a href="#output.pdf.fop">Via XSL-FO</a><ul><li>9.1.1 <a href="#rfc.section.9.1.1">Extension feature matrix</a></li><li>9.1.2 <a href="#rfc.section.9.1.2">Example: producing output for Apache FOP</a></li></ul></li><li>9.2 <a href="#output.pdf.html">Via X(HTML)</a></li></ul></li><li>10. <a href="#output.epub">Transforming to ePub</a></li><li>11. <a href="#extensions">Generic Extensions</a><ul><li>11.1 <a href="#ext.element.abnf-char-sequence"><abnf-char-sequence> element</a></li><li>11.2 <a href="#ext.element.anchor-alias"><anchor-alias> element</a></li><li>11.3 <a href="#ext.element.bcp14"><bcp14> element</a></li><li>11.4 <a href="#ext.element.bb"><bb> element</a></li><li>11.5 <a href="#ext.element.bc"><bc> element</a></li><li>11.6 <a href="#ext.element.blockquote"><blockquote> element</a></li><li>11.7 <a href="#ext.element.boilerplate"><boilerplate> element</a></li><li>11.8 <a href="#ext.element.bt"><bt> element</a></li><li>11.9 <a href="#ext.element.dfn"><dfn> element</a></li><li>11.10 <a href="#ext.element.h"><h> element</a></li><li>11.11 <a href="#ext.element.highlight"><highlight> element</a></li><li>11.12 <a href="#ext.element.length-of"><length-of> element</a></li><li>11.13 <a href="#ext.element.link"><link> element</a></li><li>11.14 <a href="#ext.element.lt"><lt> element</a></li><li>11.15 <a href="#ext.element.note"><note> element</a></li><li>11.16 <a href="#ext.element.parse-xml"><parse-xml> element</a></li><li>11.17 <a href="#ext.element.prose"><prose> element</a></li><li>11.18 <a href="#ext.element.q"><q> element</a></li><li>11.19 <a href="#ext.element.ref"><ref> element</a></li><li>11.20 <a href="#ext.element.source"><source> element</a></li><li>11.21 <a href="#ext.element.sup"><sup> element</a></li><li>11.22 <a href="#ext-rfc2629.artwork">Extensions to Xml2rfc <artwork> element</a></li><li>11.23 <a href="#ext-rfc2629.iref">Extensions to Xml2rfc <iref> element</a></li><li>11.24 <a href="#ext-rfc2629.list">Extensions to Xml2rfc <list> element</a></li><li>11.25 <a href="#ext-rfc2629.rfc">Extensions to Xml2rfc <rfc> element</a></li><li>11.26 <a href="#ext-rfc2629.section">Extensions to Xml2rfc <section> element</a></li><li>11.27 <a href="#ext-rfc2629.xref">Extensions to Xml2rfc <xref> element</a></li></ul></li><li>12. <a href="#utilities">Utilities</a><ul><li>12.1 <a href="#checking-references">Checking References</a></li><li>12.2 <a href="#rfc.section.12.2">Generating Graphs from References</a></li><li>12.3 <a href="#rfc.section.12.3">Producing reference entries for books</a></li><li>12.4 <a href="#clean-for-dtd">Down-converting to RFC2629bis DTD</a></li><li>12.5 <a href="#extract-artwork">Extracting artwork</a></li><li>12.6 <a href="#grddl">GRRDL</a></li></ul></li><li>13. <a href="#rfc.references">Informative References</a></li><li><a href="#rfc.authors">Author's Address</a></li><li>A. <a href="#grammar">RELAX NG Compact Schema</a></li><li>B. <a href="#rfc.section.B">Implementation Notes</a><ul><li>B.1 <a href="#rfc.section.B.1">Recognized type attributes for <artwork> element</a></li></ul></li><li>C. <a href="#examples">Examples</a><ul><li>C.1 <a href="#examples.internalsubset">Using the 'Internal Subset'</a></li><li>C.2 <a href="#examples.customizing">Customization</a></li></ul></li><li>D. <a href="#boilerplate">Producing the IETF 'Boilerplate'</a><ul><li>D.1 <a href="#attribute-ipr">The /rfc/@ipr Attribute</a><ul><li>D.1.1 <a href="#attribute-ipr-current">Current Values: '*trust200902'</a><ul><li>D.1.1.1 <a href="#attribute-ipr-trust200902">trust200902</a></li><li>D.1.1.2 <a href="#attribute-ipr-noModificationTrust200902">noModificationTrust200902</a></li><li>D.1.1.3 <a href="#attribute-ipr-noDerivativesTrust200902">noDerivativesTrust200902</a></li><li>D.1.1.4 <a href="#attribute-ipr-pre5378Trust200902">pre5378Trust200902</a></li></ul></li><li>D.1.2 <a href="#attribute-ipr-historic">Historic Values</a><ul><li>D.1.2.1 <a href="#attribute-ipr-200811">Historic Values: '*trust200811'</a></li><li>D.1.2.2 <a href="#attribute-ipr-3978">Historic Values: '*3978'</a></li><li>D.1.2.3 <a href="#attribute-ipr-3667">Historic Values: '*3667'</a></li><li>D.1.2.4 <a href="#attribute-ipr-2026">Historic Values: '*2026'</a></li></ul></li></ul></li><li>D.2 <a href="#attribute-category">The /rfc/@category Attribute</a></li><li>D.3 <a href="#attribute-submissiontype">The /rfc/@submissionType Attribute</a></li><li>D.4 <a href="#attribute-consensus">The /rfc/@consensus Attribute</a></li><li>D.5 <a href="#attribute-number">The /rfc/@number Attribute</a></li><li>D.6 <a href="#attribute-docname">The /rfc/@docName Attribute</a></li><li>D.7 <a href="#attribute-obsoletes">The /rfc/@obsoletes Attribute</a></li><li>D.8 <a href="#attribute-updates">The /rfc/@updates Attribute</a></li></ul></li><li>E. <a href="#license">License</a></li><li>F. <a href="#rfc.section.F">Change Logs</a><ul><li>F.1 <a href="#rfc.section.F.1">Package</a></li><li>F.2 <a href="#rfc.section.F.2">amazon-asin.xslt</a></li><li>F.3 <a href="#rfc.section.F.3">check-references.xslt</a></li><li>F.4 <a href="#rfc.section.F.4">gen-reference-graph.xslt</a></li><li>F.5 <a href="#rfc.section.F.5">rfc2629.xslt</a></li><li>F.6 <a href="#rfc.section.F.6">rfc2629toFO.xslt</a></li><li>F.7 <a href="#rfc.section.F.7">xsl11toAn.xslt</a></li><li>F.8 <a href="#rfc.section.F.8">xsl11toFop.xslt</a></li><li>F.9 <a href="#rfc.section.F.9">xsl11toXep.xslt</a></li></ul></li><li><a href="#rfc.index">Index</a></li></ul><hr class="noprint"><h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a> Introduction</h1><p id="rfc.section.1.p.1">This document describes a set of XSLT transformations that can be used to transform RFC2629-compliant XML (see <a href="#RFC2629" id="rfc.xref.RFC2629.1"><cite title="Writing I-Ds and RFCs using XML">[RFC2629]</cite></a>) to various output formats, such as HTML and PDF. The main topics are </p><ul><li>compliance to the xml2rfc XML element set (<a href="#supported.elements" title="Supported RFC2629 elements">Section 2</a>),</li><li>support for xml2rfc processing instructions (<a href="#processing.instructions" title="Processing Instructions">Section 3</a>),</li><li>the names of anchor elements generated in HTML and PDF output (<a href="#anchors" title="Anchors">Section 4</a>),</li><li>various XSLT engines that can be used (<a href="#xslt.engines" title="Supported XSLT engines">Section 5</a>),</li><li>outputting HTML (<a href="#output.html" title="Transforming to HTML">Section 6</a>) and XHTML (<a href="#output.xhtml" title="Transforming to XHTML">Section 7</a>),</li><li>outputting CHM (Compiled Microsoft Help, <a href="#output.chm" title="Transforming to CHM (Microsoft Compiled Help)">Section 8</a>),</li><li>outputting PDF (<a href="#output.pdf" title="Transforming to PDF">Section 9</a>),</li><li>extensions to the xml2rfc vocabulary (<a href="#extensions" title="Generic Extensions">Section 11</a>).</li><li>various utilities (<a href="#utilities" title="Utilities">Section 12</a>).</li></ul><p id="rfc.section.1.p.2">The full distribution is available at <<a href="http://greenbytes.de/tech/webdav/rfc2629xslt.zip">http://greenbytes.de/tech/webdav/rfc2629xslt.zip</a>>.</p><hr class="noprint"><h1 id="rfc.section.2" class="np"><a href="#rfc.section.2">2.</a> <a id="supported.elements" href="#supported.elements">Supported RFC2629 elements</a></h1><p id="rfc.section.2.p.1"> <samp>rfc2629.xslt</samp> supports both all RFC2629 grammar elements and the extensions implemented in xml2rfc 1.33.</p><h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a> Extension elements</h2><p id="rfc.section.2.1.p.1"> <samp>rfc2629.xslt</samp> supports two kind of extension elements, using different XML namespaces.</p><p id="rfc.section.2.1.p.2">The first set contains (hopefully) generally useful extensions, see <a href="#extensions" title="Generic Extensions">Section 11</a>.</p><p id="rfc.section.2.1.p.3">The second set is used for change and issue tracking and currently is not documented here. Please email the author in case you're interested in using these extensions.</p><hr class="noprint"><h1 id="rfc.section.3" class="np"><a href="#rfc.section.3">3.</a> <a id="processing.instructions" href="#processing.instructions">Processing Instructions</a></h1><p id="rfc.section.3.p.1">All PIs can be set as XSLT parameter as well, overriding any value that is found in the source file to be transformed.</p><div id="rfc.figure.u.1"></div> <p>Using processing instructions:</p> <pre class="text"><?rfc toc="yes"?>379 </style><link rel="Contents" href="#rfc.toc"><link rel="Author" href="#rfc.authors"><link rel="Index" href="#rfc.index"><link rel="Chapter" title="1 Introduction" href="#rfc.section.1"><link rel="Chapter" title="2 Supported RFC2629 elements" href="#rfc.section.2"><link rel="Chapter" title="3 Processing Instructions" href="#rfc.section.3"><link rel="Chapter" title="4 Anchors" href="#rfc.section.4"><link rel="Chapter" title="5 Supported XSLT engines" href="#rfc.section.5"><link rel="Chapter" title="6 Transforming to HTML" href="#rfc.section.6"><link rel="Chapter" title="7 Transforming to XHTML" href="#rfc.section.7"><link rel="Chapter" title="8 Transforming to CHM (Microsoft Compiled Help)" href="#rfc.section.8"><link rel="Chapter" title="9 Transforming to PDF" href="#rfc.section.9"><link rel="Chapter" title="10 Transforming to ePub" href="#rfc.section.10"><link rel="Chapter" title="11 Generic Extensions" href="#rfc.section.11"><link rel="Chapter" title="12 Utilities" href="#rfc.section.12"><link rel="Chapter" href="#rfc.section.13" title="13 Informative References"><link rel="Appendix" title="A RELAX NG Compact Schema" href="#rfc.section.A"><link rel="Appendix" title="B Implementation Notes" href="#rfc.section.B"><link rel="Appendix" title="C Examples" href="#rfc.section.C"><link rel="Appendix" title="D Producing the IETF 'Boilerplate'" href="#rfc.section.D"><link rel="Appendix" title="E License" href="#rfc.section.E"><link rel="Appendix" title="F Change Logs" href="#rfc.section.F"><meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.540, 2011-01-10 09:27:20, XSLT vendor: SAXON 6.5.5 from Michael Kay http://saxon.sf.net/"><meta name="keywords" content="RFC2629, xml2rfc, XSLT, hCard, XSL-FO, PDF, GRDDL, epub, Dublin Core"><link rel="schema.dct" href="http://purl.org/dc/terms/"><meta name="dct.creator" content="Reschke, J. F."></head><body><table class="header"><tbody><tr><td class="left">RFC2629 through XSLT</td><td class="right">J. Reschke</td></tr><tr><td class="left"></td><td class="right">greenbytes</td></tr><tr><td class="left"></td><td class="right">January 2011</td></tr></tbody></table><p class="title">Transforming RFC2629-formatted XML through XSLT</p><hr class="noprint"><h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1><ul class="toc"><li>1. <a href="#rfc.section.1">Introduction</a></li><li>2. <a href="#supported.elements">Supported RFC2629 elements</a><ul><li>2.1 <a href="#rfc.section.2.1">Extension elements</a></li></ul></li><li>3. <a href="#processing.instructions">Processing Instructions</a><ul><li>3.1 <a href="#rfc.section.3.1">Supported xml2rfc-compatible PIs</a></li><li>3.2 <a href="#rfc.section.3.2">Unsupported xml2rfc-compatible PIs</a></li><li>3.3 <a href="#rfc.section.3.3">Extension PIs</a></li></ul></li><li>4. <a href="#anchors">Anchors</a></li><li>5. <a href="#xslt.engines">Supported XSLT engines</a><ul><li>5.1 <a href="#rfc.section.5.1">Standalone Engines</a></li><li>5.2 <a href="#xslt.engines.browser">In-Browser Engines</a></li></ul></li><li>6. <a href="#output.html">Transforming to HTML</a><ul><li>6.1 <a href="#rfc.section.6.1">HTML compliance</a></li><li>6.2 <a href="#html.link">Standard HTML LINK elements</a></li><li>6.3 <a href="#rfc.section.6.3">Standard HTML metadata</a></li><li>6.4 <a href="#rfc2731.properties">Dublin Core (RFC2731) metadata</a></li><li>6.5 <a href="#hcard">Experimental hCard support</a></li></ul></li><li>7. <a href="#output.xhtml">Transforming to XHTML</a></li><li>8. <a href="#output.chm">Transforming to CHM (Microsoft Compiled Help)</a></li><li>9. <a href="#output.pdf">Transforming to PDF</a><ul><li>9.1 <a href="#output.pdf.fop">Via XSL-FO</a><ul><li>9.1.1 <a href="#rfc.section.9.1.1">Extension feature matrix</a></li><li>9.1.2 <a href="#rfc.section.9.1.2">Example: producing output for Apache FOP</a></li></ul></li><li>9.2 <a href="#output.pdf.html">Via X(HTML)</a></li></ul></li><li>10. <a href="#output.epub">Transforming to ePub</a></li><li>11. <a href="#extensions">Generic Extensions</a><ul><li>11.1 <a href="#ext.element.abnf-char-sequence"><abnf-char-sequence> element</a></li><li>11.2 <a href="#ext.element.anchor-alias"><anchor-alias> element</a></li><li>11.3 <a href="#ext.element.bcp14"><bcp14> element</a></li><li>11.4 <a href="#ext.element.bb"><bb> element</a></li><li>11.5 <a href="#ext.element.bc"><bc> element</a></li><li>11.6 <a href="#ext.element.blockquote"><blockquote> element</a></li><li>11.7 <a href="#ext.element.boilerplate"><boilerplate> element</a></li><li>11.8 <a href="#ext.element.bt"><bt> element</a></li><li>11.9 <a href="#ext.element.dfn"><dfn> element</a></li><li>11.10 <a href="#ext.element.h"><h> element</a></li><li>11.11 <a href="#ext.element.highlight"><highlight> element</a></li><li>11.12 <a href="#ext.element.length-of"><length-of> element</a></li><li>11.13 <a href="#ext.element.link"><link> element</a></li><li>11.14 <a href="#ext.element.lt"><lt> element</a></li><li>11.15 <a href="#ext.element.note"><note> element</a></li><li>11.16 <a href="#ext.element.parse-xml"><parse-xml> element</a></li><li>11.17 <a href="#ext.element.prose"><prose> element</a></li><li>11.18 <a href="#ext.element.q"><q> element</a></li><li>11.19 <a href="#ext.element.ref"><ref> element</a></li><li>11.20 <a href="#ext.element.source"><source> element</a></li><li>11.21 <a href="#ext.element.sup"><sup> element</a></li><li>11.22 <a href="#ext-rfc2629.artwork">Extensions to Xml2rfc <artwork> element</a></li><li>11.23 <a href="#ext-rfc2629.iref">Extensions to Xml2rfc <iref> element</a></li><li>11.24 <a href="#ext-rfc2629.list">Extensions to Xml2rfc <list> element</a></li><li>11.25 <a href="#ext-rfc2629.rfc">Extensions to Xml2rfc <rfc> element</a></li><li>11.26 <a href="#ext-rfc2629.section">Extensions to Xml2rfc <section> element</a></li><li>11.27 <a href="#ext-rfc2629.xref">Extensions to Xml2rfc <xref> element</a></li></ul></li><li>12. <a href="#utilities">Utilities</a><ul><li>12.1 <a href="#checking-references">Checking References</a></li><li>12.2 <a href="#rfc.section.12.2">Generating Graphs from References</a></li><li>12.3 <a href="#rfc.section.12.3">Producing reference entries for books</a></li><li>12.4 <a href="#clean-for-dtd">Down-converting to RFC2629bis DTD</a></li><li>12.5 <a href="#extract-artwork">Extracting artwork</a></li><li>12.6 <a href="#grddl">GRRDL</a></li></ul></li><li>13. <a href="#rfc.references">Informative References</a></li><li><a href="#rfc.authors">Author's Address</a></li><li>A. <a href="#grammar">RELAX NG Compact Schema</a></li><li>B. <a href="#rfc.section.B">Implementation Notes</a><ul><li>B.1 <a href="#rfc.section.B.1">Recognized type attributes for <artwork> element</a></li></ul></li><li>C. <a href="#examples">Examples</a><ul><li>C.1 <a href="#examples.internalsubset">Using the 'Internal Subset'</a></li><li>C.2 <a href="#examples.customizing">Customization</a></li></ul></li><li>D. <a href="#boilerplate">Producing the IETF 'Boilerplate'</a><ul><li>D.1 <a href="#attribute-ipr">The /rfc/@ipr Attribute</a><ul><li>D.1.1 <a href="#attribute-ipr-current">Current Values: '*trust200902'</a><ul><li>D.1.1.1 <a href="#attribute-ipr-trust200902">trust200902</a></li><li>D.1.1.2 <a href="#attribute-ipr-noModificationTrust200902">noModificationTrust200902</a></li><li>D.1.1.3 <a href="#attribute-ipr-noDerivativesTrust200902">noDerivativesTrust200902</a></li><li>D.1.1.4 <a href="#attribute-ipr-pre5378Trust200902">pre5378Trust200902</a></li></ul></li><li>D.1.2 <a href="#attribute-ipr-historic">Historic Values</a><ul><li>D.1.2.1 <a href="#attribute-ipr-200811">Historic Values: '*trust200811'</a></li><li>D.1.2.2 <a href="#attribute-ipr-3978">Historic Values: '*3978'</a></li><li>D.1.2.3 <a href="#attribute-ipr-3667">Historic Values: '*3667'</a></li><li>D.1.2.4 <a href="#attribute-ipr-2026">Historic Values: '*2026'</a></li></ul></li></ul></li><li>D.2 <a href="#attribute-category">The /rfc/@category Attribute</a></li><li>D.3 <a href="#attribute-submissiontype">The /rfc/@submissionType Attribute</a></li><li>D.4 <a href="#attribute-consensus">The /rfc/@consensus Attribute</a></li><li>D.5 <a href="#attribute-number">The /rfc/@number Attribute</a></li><li>D.6 <a href="#attribute-docname">The /rfc/@docName Attribute</a></li><li>D.7 <a href="#attribute-obsoletes">The /rfc/@obsoletes Attribute</a></li><li>D.8 <a href="#attribute-updates">The /rfc/@updates Attribute</a></li></ul></li><li>E. <a href="#license">License</a></li><li>F. <a href="#rfc.section.F">Change Logs</a><ul><li>F.1 <a href="#rfc.section.F.1">Package</a></li><li>F.2 <a href="#rfc.section.F.2">amazon-asin.xslt</a></li><li>F.3 <a href="#rfc.section.F.3">check-references.xslt</a></li><li>F.4 <a href="#rfc.section.F.4">gen-reference-graph.xslt</a></li><li>F.5 <a href="#rfc.section.F.5">rfc2629.xslt</a></li><li>F.6 <a href="#rfc.section.F.6">rfc2629toFO.xslt</a></li><li>F.7 <a href="#rfc.section.F.7">xsl11toAn.xslt</a></li><li>F.8 <a href="#rfc.section.F.8">xsl11toFop.xslt</a></li><li>F.9 <a href="#rfc.section.F.9">xsl11toXep.xslt</a></li></ul></li><li><a href="#rfc.index">Index</a></li></ul><hr class="noprint"><h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a> Introduction</h1><p id="rfc.section.1.p.1">This document describes a set of XSLT transformations that can be used to transform RFC2629-compliant XML (see <a href="#RFC2629" id="rfc.xref.RFC2629.1"><cite title="Writing I-Ds and RFCs using XML">[RFC2629]</cite></a>) to various output formats, such as HTML and PDF. The main topics are </p><ul><li>compliance to the xml2rfc XML element set (<a href="#supported.elements" title="Supported RFC2629 elements">Section 2</a>),</li><li>support for xml2rfc processing instructions (<a href="#processing.instructions" title="Processing Instructions">Section 3</a>),</li><li>the names of anchor elements generated in HTML and PDF output (<a href="#anchors" title="Anchors">Section 4</a>),</li><li>various XSLT engines that can be used (<a href="#xslt.engines" title="Supported XSLT engines">Section 5</a>),</li><li>outputting HTML (<a href="#output.html" title="Transforming to HTML">Section 6</a>) and XHTML (<a href="#output.xhtml" title="Transforming to XHTML">Section 7</a>),</li><li>outputting CHM (Compiled Microsoft Help, <a href="#output.chm" title="Transforming to CHM (Microsoft Compiled Help)">Section 8</a>),</li><li>outputting PDF (<a href="#output.pdf" title="Transforming to PDF">Section 9</a>),</li><li>extensions to the xml2rfc vocabulary (<a href="#extensions" title="Generic Extensions">Section 11</a>).</li><li>various utilities (<a href="#utilities" title="Utilities">Section 12</a>).</li></ul><p id="rfc.section.1.p.2">The full distribution is available at <<a href="http://greenbytes.de/tech/webdav/rfc2629xslt.zip">http://greenbytes.de/tech/webdav/rfc2629xslt.zip</a>>.</p><hr class="noprint"><h1 id="rfc.section.2" class="np"><a href="#rfc.section.2">2.</a> <a id="supported.elements" href="#supported.elements">Supported RFC2629 elements</a></h1><p id="rfc.section.2.p.1"> <samp>rfc2629.xslt</samp> supports both all RFC2629 grammar elements and the extensions implemented in xml2rfc 1.33.</p><h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a> Extension elements</h2><p id="rfc.section.2.1.p.1"> <samp>rfc2629.xslt</samp> supports two kind of extension elements, using different XML namespaces.</p><p id="rfc.section.2.1.p.2">The first set contains (hopefully) generally useful extensions, see <a href="#extensions" title="Generic Extensions">Section 11</a>.</p><p id="rfc.section.2.1.p.3">The second set is used for change and issue tracking and currently is not documented here. Please email the author in case you're interested in using these extensions.</p><hr class="noprint"><h1 id="rfc.section.3" class="np"><a href="#rfc.section.3">3.</a> <a id="processing.instructions" href="#processing.instructions">Processing Instructions</a></h1><p id="rfc.section.3.p.1">All PIs can be set as XSLT parameter as well, overriding any value that is found in the source file to be transformed.</p><div id="rfc.figure.u.1"></div> <p>Using processing instructions:</p> <pre class="text"><?rfc toc="yes"?> 380 380 <?rfc-ext support-rfc2731="no"?> 381 381 </pre> <div id="rfc.figure.u.2"></div> <p>Using XSLT parameters (Saxon):</p> <pre class="text">java -cp saxon.jar com.icl.saxon.StyleSheet source.xml rfc2629.xslt \ … … 955 955 956 956 <!-- <em>allow later RFC2616 reference using "&rfc2616;"</em> --> 957 <!-- <em>the data will be fetched from xml.resource.org</em> --> 957 958 <!ENTITY rfc2616 PUBLIC 958 959 "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2616.xml"> 959 960 961 <!-- <em>allow a custom reference using "&mydraft;"</em> --> 962 <!-- <em>the data will be fetched from the same location as the 963 source file</em> --> 964 <!ENTITY mydraft PUBLIC "reference.mydraft.xml"> 960 965 ]> 961 966 </pre> <p>Note: including entities from a remote site will not work in Firefox, see <<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=22942">https://bugzilla.mozilla.org/show_bug.cgi?id=22942</a>>.</p> <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a> <a id="examples.customizing" href="#examples.customizing">Customization</a></h2><p id="rfc.section.C.2.p.1">The XSLT code can be customized by creating a custom XSLT file that uses <xsl:import> to include the original code, and just overrides particular rules.</p><div id="rfc.figure.u.25"></div> <p>For instance, the code below overrides several attributes in <samp>rfc2629toFO.xslt</samp>, changing the color, spacing and font family for headers.</p> <pre class="text"><xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" … … 985 990 986 991 </xsl:transform> 987 </pre><div class="note" id="rfc.section.C.2.p.3"> <p> <b>Note:</b> the name for the attribute sets may change in the future as more working is done with respect to customizability. In any case, overriding the settings in a separate file will be easier to maintain. Please contact the author if you find yourself trying to override style definitions that currently do not use attribute sets.</p> <p> <b>Note:</b> the CSS style information used in <samp>rfc2629.xslt</samp> can be overriden in a similar (but less granular) way: just overwrite the template called "insertCss". As for XSL-FO, the class names may change in future.</p> </div><hr class="noprint"><h1 id="rfc.section.D" class="np"><a href="#rfc.section.D">D.</a> <a id="boilerplate" href="#boilerplate">Producing the IETF 'Boilerplate'</a></h1><p id="rfc.section.D.p.1">Various attributes of the <samp><rfc></samp> element plus some child elements of <samp><front></samp> affect the automatically generated parts of the front page, such as the tabular information at the beginning, the "Status Of This Memo", and the "Copyright Notice".</p><p id="rfc.section.D.p.2">When submitting an Internet Draft, this "boilerplate" is checked by "Idnits" (<<a href="http://tools.ietf.org/tools/idnits/">http://tools.ietf.org/tools/idnits/</a>>) for compliance with the current Intellectual Property rules, and thus it is important to set the correct values.</p><p id="rfc.section.D.p.3">Furthermore, the RFC Production Center uses RFC2629-based tools to generate the final RFC text, so the more accurate the supplied information is, the less additional work is left, and the risk for errors in producing the final (and immutable!) document is reduced.</p><div class="note" id="rfc.section.D.p.4"> <p> <b>Note:</b> this only applies to the case when IETF documents are produced. The "private" processing instruction <span id="rfc.iref.p.64"></span><span id="rfc.iref.p.65"></span> allows to switch off most of the autogeneration logic.</p> </div><h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a> <a id="attribute-ipr" href="#attribute-ipr">The /rfc/@ipr Attribute</a></h2><p id="rfc.section.D.1.p.1">As of the time of this writing, this attribute value can take a long list of values. As frequently, this is not the result of a grand plan, but simply for historic reasons. Of these values, only a few are currently in use; all others are supported by the various tools for backwards compatibility with old source files.</p><div class="note" id="rfc.section.D.1.p.2"> <p> <b>Note:</b> some variations of the boilerplate are selected based on the document's date; therefore it is important to specify the "year", "month" and "day" attributes of the <samp><date></samp> element when archiving the XML source of an Internet Draft on the day of submission.</p> </div><p id="rfc.section.D.1.p.3"> <em>Disclaimer: THIS ONLY PROVIDES IMPLEMENTATION INFORMATION. IF YOU NEED LEGAL ADVICE, PLEASE CONTACT A LAWYER.</em> For further information, refer to <<a href="http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf">http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf</a>>.</p><p id="rfc.section.D.1.p.4">Finally, for the current "Status Of This Memo" text, the <samp>submissionType</samp> attribute determines whether a statement about "Code Components" is inserted (this is the case for the value "IETF", which also happens to be the default). Other values, such as "independent", suppress this part of the text.</p><h3 id="rfc.section.D.1.1"><a href="#rfc.section.D.1.1">D.1.1</a> <a id="attribute-ipr-current" href="#attribute-ipr-current">Current Values: '*trust200902'</a></h3><p id="rfc.section.D.1.1.p.1">The name for these values refers to the "TLP" ("IETF TRUST Legal Provisions Relating to IETF Documents"), on effect February 15, 2009 (see <<a href="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090215.pdf">http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090215.pdf</a>>). Updates to this document were published on September 12, 2009 (TLP 3.0, <<a href="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090912.pdf">http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090912.pdf</a>>) and on December 28, 2009 (TLP 4.0, <<a href="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20091228.pdf">http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20091228.pdf</a>>), modifying the license for code components. The actual text is located in Section 6 ("Text To Be Included in IETF Documents") of these documents.</p><p id="rfc.section.D.1.1.p.2">The tools will automatically produce the "right" text depending on the document's date information (see above):</p><div id="rfc.table.u.10"><table class="tt full left" cellpadding="3" cellspacing="0"><thead><tr><th>TLP</th><th>URI</th><th>starting with publication date</th></tr></thead><tbody><tr><td class="left">3.0</td><td class="left"><<a href="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090912.pdf">http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090912.pdf</a>></td><td class="left">2009-11-01</td></tr><tr><td class="left">4.0</td><td class="left"><<a href="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20091228.pdf">http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20091228.pdf</a>></td><td class="left">2010-04-01</td></tr></tbody></table></div><h4 id="rfc.section.D.1.1.1"><a href="#rfc.section.D.1.1.1">D.1.1.1</a> <a id="attribute-ipr-trust200902" href="#attribute-ipr-trust200902">trust200902</a></h4><p id="rfc.section.D.1.1.1.p.1">This should be the default, unless one of the more specific '*trust200902' values is a better fit. It produces the text in Sections 6.a and 6.b of the TLP.</p><h4 id="rfc.section.D.1.1.2"><a href="#rfc.section.D.1.1.2">D.1.1.2</a> <a id="attribute-ipr-noModificationTrust200902" href="#attribute-ipr-noModificationTrust200902">noModificationTrust200902</a></h4><p id="rfc.section.D.1.1.2.p.1">This produces the additional text from Section 6.c.i of the TLP:</p><blockquote id="rfc.section.D.1.1.2.p.2"> <p>This document may not be modified, and derivative works of it may not be created, except to format it for publication as an RFC or to translate it into languages other than English.</p> </blockquote><h4 id="rfc.section.D.1.1.3"><a href="#rfc.section.D.1.1.3">D.1.1.3</a> <a id="attribute-ipr-noDerivativesTrust200902" href="#attribute-ipr-noDerivativesTrust200902">noDerivativesTrust200902</a></h4><p id="rfc.section.D.1.1.3.p.1">This produces the additional text from Section 6.c.ii of the TLP:</p><blockquote id="rfc.section.D.1.1.3.p.2"> <p>This document may not be modified, and derivative works of it may not be created, and it may not be published except as an Internet-Draft.</p> </blockquote><h4 id="rfc.section.D.1.1.4"><a href="#rfc.section.D.1.1.4">D.1.1.4</a> <a id="attribute-ipr-pre5378Trust200902" href="#attribute-ipr-pre5378Trust200902">pre5378Trust200902</a></h4><p id="rfc.section.D.1.1.4.p.1">This produces the additional text from Section 6.c.iii of the TLP, frequently called the "pre-5378 escape clause":</p><blockquote id="rfc.section.D.1.1.4.p.2"> <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.</p> </blockquote><p id="rfc.section.D.1.1.4.p.3">See Section 4 of <<a href="http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf">http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf</a>> for further information about when to use this value.</p><div class="note" id="rfc.section.D.1.1.4.p.4"> <p> <b>Note:</b> this text appears under "Copyright Notice", unless the document was published before November 2009, in which case it appears under "Status Of This Memo".</p> </div><h3 id="rfc.section.D.1.2"><a href="#rfc.section.D.1.2">D.1.2</a> <a id="attribute-ipr-historic" href="#attribute-ipr-historic">Historic Values</a></h3><h4 id="rfc.section.D.1.2.1"><a href="#rfc.section.D.1.2.1">D.1.2.1</a> <a id="attribute-ipr-200811" href="#attribute-ipr-200811">Historic Values: '*trust200811'</a></h4><p id="rfc.section.D.1.2.1.p.1">The attribute values "<span id="attribute-ipr-trust200811">trust200811</span>", "<span id="attribute-ipr-noModificationTrust200811">noModificationTrust200811</span>" and "<span id="attribute-ipr-noDerivativesTrust200811">noDerivativesTrust200811</span>" are similar to their "trust200902" counterparts, except that they use text specified in <<a href="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy_11-10-08.pdf">http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy_11-10-08.pdf</a>>.</p><h4 id="rfc.section.D.1.2.2"><a href="#rfc.section.D.1.2.2">D.1.2.2</a> <a id="attribute-ipr-3978" href="#attribute-ipr-3978">Historic Values: '*3978'</a></h4><p id="rfc.section.D.1.2.2.p.1">The attribute values "<span id="attribute-ipr-full3978">full3978</span>", "<span id="attribute-ipr-noModification3978">noModification3978</span>" and "<span id="attribute-ipr-noDerivatives3978">noDerivatives3978</span>" are similar to their counterparts above, except that they use text specified in RFC 3978 (March 2005).</p><h4 id="rfc.section.D.1.2.3"><a href="#rfc.section.D.1.2.3">D.1.2.3</a> <a id="attribute-ipr-3667" href="#attribute-ipr-3667">Historic Values: '*3667'</a></h4><p id="rfc.section.D.1.2.3.p.1">The attribute values "<span id="attribute-ipr-full3667">full3667</span>", "<span id="attribute-ipr-noModification3667">noModification3667</span>" and "<span id="attribute-ipr-noDerivatives3667">noDerivatives3667</span>" are similar to their counterparts above, except that they use text specified in RFC 3667 (February 2004).</p><h4 id="rfc.section.D.1.2.4"><a href="#rfc.section.D.1.2.4">D.1.2.4</a> <a id="attribute-ipr-2026" href="#attribute-ipr-2026">Historic Values: '*2026'</a></h4><p id="rfc.section.D.1.2.4.p.1">The attribute values "<span id="attribute-ipr-full2026">full2026</span>" and "<span id="attribute-ipr-noDerivativeWorks2026">noDerivativeWorks2026</span>" are similar to their counterparts above, except that they use text specified in RFC 2026 (October 1996).</p><p id="rfc.section.D.1.2.4.p.2">The special value "<span id="attribute-ipr-none">none</span>" was also used back then, and denied the IETF any rights beyond publication as Internet Draft.</p><h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a> <a id="attribute-category" href="#attribute-category">The /rfc/@category Attribute</a></h2><p id="rfc.section.D.2.p.1">For RFCs, the <samp>category</samp> determines the "maturity level" (see <a href="http://tools.ietf.org/html/rfc2026#section-4">Section 4</a> of <a href="#RFC2026" id="rfc.xref.RFC2026.2"><cite title="The Internet Standards Process -- Revision 3">[RFC2026]</cite></a>). The allowed values are "std" for "Standards Track", "bcp" for "BCP", "info" for "Informational", "exp" for "Experimental", and "historic" for - surprise - "Historic".</p><p id="rfc.section.D.2.p.2">For Internet Drafts, the category attribute is not needed, but <em>will</em> appear on the front page ("Intended Status"). Supplying this information can be useful, because reviewers may want to know.</p><div class="note" id="rfc.section.D.2.p.3"> <p> <b>Note:</b> the Standards Track consists of "Proposed Standard", "Draft Standards", and "Internet Standard". These do not appear in the boilerplate, thus the category attribute doesn't handle them. However, this information can be useful for validity checkers, and thus <samp>rfc2629.xslt</samp> supports an extension attribute for that purpose (see <a href="#ext-rfc2629.rfc" title="Extensions to Xml2rfc <rfc> element">Section 11.25</a> for details).</p> </div><h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a> <a id="attribute-submissiontype" href="#attribute-submissiontype">The /rfc/@submissionType Attribute</a></h2><p id="rfc.section.D.3.p.1">The RFC Editor publishes documents from different "document streams", of which the "IETF stream" of course is the most prominent one. Other streams are the "independent stream" (used for things like administrative information or April 1st RFCs), the "IAB stream" (Internet Architecture Board) and the "IRTF stream" (Internet Research Task Force).</p><p id="rfc.section.D.3.p.2">Not surprisingly, the values for the attribute are "IETF" (the default value), "independent", "IAB", and "IRTF".</p><p id="rfc.section.D.3.p.3"> <em>The values "IAB" and "IRTF" are supported by rfc2629.xslt, but not yet allowed by the DTD (waiting for release 1.36 of xml2rfc).</em> </p><p id="rfc.section.D.3.p.4">Historically, this did not affect the final appearance of RFCs, except for subtle differences in Copyright notices. Nowadays (as of <a href="#RFC5741" id="rfc.xref.RFC5741.1"><cite title="RFC Streams, Headers, and Boilerplates">[RFC5741]</cite></a>), the stream name appears in the first line of the front page, and it also affects the text in the "Status Of This Memo" section.</p><p id="rfc.section.D.3.p.5">For current documents, setting <samp>submissionType</samp> attribute will have the following effect: </p><ul><li>For RFCs, the stream name appears in the upper left corner of the first page (in Internet Drafts, this is either "Network Working Group", or the value of the <samp><workgroup></samp> element).</li><li>For RFCs, if affects the whole "Status Of This Memo" section (see <a href="http://tools.ietf.org/html/rfc5741#section-3.2.2">Section 3.2.2</a> of <a href="#RFC5741" id="rfc.xref.RFC5741.2"><cite title="RFC Streams, Headers, and Boilerplates">[RFC5741]</cite></a>).</li><li>For all RFCs and Internet Drafts, it determines whether the "Copyright Notice" mentions the Copyright on Code Components (see TLP, Section "Text To Be Included in IETF Documents").</li></ul><div class="note" id="rfc.section.D.3.p.6"> <p> <b>Note:</b> as of Version 1.35, <samp>xml2rfc</samp> (as opposed to <samp>rfc2629.xslt</samp>) does <em>not</em> implement support values other than "IETF" or "independent".</p> </div><h2 id="rfc.section.D.4"><a href="#rfc.section.D.4">D.4</a> <a id="attribute-consensus" href="#attribute-consensus">The /rfc/@consensus Attribute</a></h2><p id="rfc.section.D.4.p.1"> <em>Supported by rfc2629.xslt, but not yet allowed by the DTD (waiting for release 1.36 of xml2rfc).</em> </p><p id="rfc.section.D.4.p.2">For some of the publication streams (see <a href="#attribute-submissiontype" title="The /rfc/@submissionType Attribute">Appendix D.3</a>), the "Status Of This Memo" section depends on whether there was a consensus to publish (again, see <a href="http://tools.ietf.org/html/rfc5741#section-3.2.2">Section 3.2.2</a> of <a href="#RFC5741" id="rfc.xref.RFC5741.3"><cite title="RFC Streams, Headers, and Boilerplates">[RFC5741]</cite></a>).</p><p id="rfc.section.D.4.p.3">The <samp>consensus</samp> attribute ("yes"/"no", defaulting to "yes") can be used to supply this information. The effect for the various streams is: </p><ul><li>"independent" and "IAB": none.</li><li>"IETF": mention that there was an IETF consensus.</li><li>"IRTF": mention that there was a research group consensus (where the name of the research group is extracted from the <samp><workgroup></samp> element).</li></ul><h2 id="rfc.section.D.5"><a href="#rfc.section.D.5">D.5</a> <a id="attribute-number" href="#attribute-number">The /rfc/@number Attribute</a></h2><p id="rfc.section.D.5.p.1">For RFCs, this attribute supplies the RFC number.</p><h2 id="rfc.section.D.6"><a href="#rfc.section.D.6">D.6</a> <a id="attribute-docname" href="#attribute-docname">The /rfc/@docName Attribute</a></h2><p id="rfc.section.D.6.p.1">For Internet Drafts, this specifies the draft name (which appears below the title). The file extension is <em>not</em> part of the draft, so in general it should end with the current draft number ("-", plus two digits).</p><div class="note" id="rfc.section.D.6.p.2"> <p> <b>Note:</b> "Idnits" (<<a href="http://tools.ietf.org/tools/idnits/">http://tools.ietf.org/tools/idnits/</a>>) checks the in-document draft name for consistency with the filename of the submitted document.</p> </div><h2 id="rfc.section.D.7"><a href="#rfc.section.D.7">D.7</a> <a id="attribute-obsoletes" href="#attribute-obsoletes">The /rfc/@obsoletes Attribute</a></h2><p id="rfc.section.D.7.p.1">The RFC Editor maintains a database (<<a href="http://www.rfc-editor.org/rfc.html">http://www.rfc-editor.org/rfc.html</a>>) of all RFCs, including information about which one obsoletes which. Upon publication of an RFC, this database is updated from the data on the front page.</p><p id="rfc.section.D.7.p.2">This attribute takes a list of comma-separated RFC <em>numbers</em>. Do <em>not</em> put the string "RFC" here.</p><h2 id="rfc.section.D.8"><a href="#rfc.section.D.8">D.8</a> <a id="attribute-updates" href="#attribute-updates">The /rfc/@updates Attribute</a></h2><p id="rfc.section.D.8.p.1">This is like <samp>obsoletes</samp>, but for the "updates" relation.</p><hr class="noprint"><h1 id="rfc.section.E" class="np"><a href="#rfc.section.E">E.</a> <a id="license" href="#license">License</a></h1><p id="rfc.section.E.p.1">Copyright (c) 2006-2010, Julian Reschke (julian.reschke@greenbytes.de)</p><p id="rfc.section.E.p.2">All rights reserved.</p><p id="rfc.section.E.p.3">Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: </p><ul><li>Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.</li><li>Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.</li><li>Neither the name of Julian Reschke nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.</li></ul><p id="rfc.section.E.p.4">THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.</p><hr class="noprint"><h1 id="rfc.section.F" class="np"><a href="#rfc.section.F">F.</a> Change Logs</h1><h2 id="rfc.section.F.1"><a href="#rfc.section.F.1">F.1</a> Package</h2><dl><dt>2006-01-01</dt><dd>Switch to BSD License.</dd><dt>2007-01-12</dt><dd>Update to xml2rfc v1.33pre2.</dd><dt>2007-03-31</dt><dd>Update to xml2rfc v1.33pre3.</dd><dt>2007-05-01</dt><dd>Add XSLT test cases.</dd><dt>2008-07-18</dt><dd>Experimental support for inlined rdf:Description elements (ignored by the formatter, extracted by rfc2629grddl).</dd><dt>2008-12-04</dt><dd>Update to xml2rfc v1.34pre2.</dd><dt>2009-02-24</dt><dd>Experimental support for February 2009 boilerplate changes, and for the x:boilerplate element.</dd><dt>2009-07-08</dt><dd>Support new boilerplate ordering in RFCs published since July 2009. Fix problems with one-column text tables.</dd><dt>2009-07-19</dt><dd>When possible, calculate the actual Expiry date for Internet Drafts (full date must be available).</dd><dt>2009-08-01</dt><dd>For '$xml2rfc-ext-authors-section='end'", move the index in front of the authors section.</dd><dt>2009-08-04</dt><dd>Consider /rfc/@ipr="pre5378Trust200902" when producing RFCs, not IDs.</dd><dt>2009-08-29</dt><dd>Support alignment for artwork containing images (as opposed to, well, artwork).</dd><dt>2009-09-01</dt><dd>Allow xref in cref (as extension).</dd><dt>2009-09-14</dt><dd>Refactor handling of processing instructions.</dd><dt>2009-09-24</dt><dd>Fix typo in Status Of This Memo, present since November 2008. Fix formatting of iprExtract attribute. Starting with Internet Draft publication dates after 2009-11-30: use new Trust Legal Provisions text; for Internet Drafts: move Abstract up, and move "pre5378" escape clause to the Copyright Notice. Add support for refparent PI. For RFCs: use new TLP text as of September 2009. Incorporate xml2rfc v1.34pre4.</dd><dt>2009-10-06</dt><dd>Starting with Internet Draft publication dates after 2009-10-31: use new Trust Legal Provisions text; for Internet Drafts: move Abstract up, and move "pre5378" escape clause to the Copyright Notice. Incorporate xml2rfc v1.34pre5.</dd><dt>2009-10-27</dt><dd>Upgrade to xml2rfc v1.34.</dd><dt>2010-01-08</dt><dd>For RFC generation (not IDs), experimentally support RFC 5741 headers and boilerplate and Trust Legal Provisions 4.0.</dd><dt>2010-03-31</dt><dd>Upgrade to xml2rfc v1.35.</dd><dt>2010-06-27</dt><dd>Be consistent with xml2rfc.tcl in formatting initials (truncate after the first); see <<a href="http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/10">http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/10</a>>.</dd><dt>2010-08-31</dt><dd>Experimental support for prose in references.</dd>< /dl><h2 id="rfc.section.F.2"><a href="#rfc.section.F.2">F.2</a> amazon-asin.xslt</h2><dl><dt>2003-11-16</dt><dd>Initial release.</dd><dt>2005-04-02</dt><dd>Fix two DTD issues.</dd></dl><h2 id="rfc.section.F.3"><a href="#rfc.section.F.3">F.3</a> check-references.xslt</h2><dl><dt>2003-11-16</dt><dd>Initial release.</dd><dt>2004-05-11</dt><dd>Add document status; print references type.</dd><dt>2005-01-01</dt><dd>Add experimental check for ID status.</dd><dt>2005-04-01</dt><dd>Add fixes from Bill Fenner.</dd><dt>2005-12-03</dt><dd>Add checks against local copy of <<a href="http://www.w3.org/2002/01/tr-automation/tr.rdf">http://www.w3.org/2002/01/tr-automation/tr.rdf</a>>.</dd><dt>2006-07-22</dt><dd>Add checks for standards levels.</dd><dt>2006-08-06</dt><dd>"check-ietf-references.xslt" replaced by "check-references.xslt".</dd><dt>2007-01-04</dt><dd>Use information online at <<a href="http://tools.ietf.org/">http://tools.ietf.org/</a>> to retrieve Internet-Draft status information.</dd><dt>2007-06-16</dt><dd>Fix bug looking up ref type when inside change markup.</dd><dt>2008-06-14</dt><dd>Enhance output when draft was updated, and then published as RFC.</dd><dt>2008-07-12</dt><dd>Add XSLT2-based link target checking.</dd><dt>2008-08-10</dt><dd>Change keywords for "intended-level" to proposed/draft/internet, optionally extract intended level from /rfc/@x:maturity-level attribute.</dd></dl><h2 id="rfc.section.F.4"><a href="#rfc.section.F.4">F.4</a> gen-reference-graph.xslt</h2><dl><dt>2006-09-03</dt><dd>New.</dd><dt>2007-06-07</dt><dd>Use <a href="http://dpcarlisle.blogspot.com/2007/05/exslt-node-set-function.html">Carlisle method</a> to define exslt:node-set in msxsml (which means that the stylesheet can now be used with MSXML as well).</dd><dt>2007-10-15</dt><dd>Use W3C data from tr.rdf as well (experimental).</dd></dl><h2 id="rfc.section.F.5"><a href="#rfc.section.F.5">F.5</a> rfc2629.xslt</h2><dl><dt>2001-03-28</dt><dd>Code rearranged, generate numbered section anchors for paragraphs (t) as well. Fixes in index handling.</dd><dt>2001-04-12</dt><dd>Moved HTML output into XHTML namespace.</dd><dt>2001-10-02</dt><dd>Fixed default location for RFCs and numbering of section references. Support ?rfc editing processing instruction.</dd><dt>2001-10-07</dt><dd>Made telephone number links active.</dd><dt>2001-10-08</dt><dd>Support for vspace element.</dd><dt>2001-10-09</dt><dd>Experimental support for rfc-issue PI.</dd><dt>2001-11-11</dt><dd>Support rfc private PI. Removed bogus code reporting the WG in the header.</dd><dt>2001-11-11</dt><dd>Support rfc private PI. Removed bogus code reporting the WG in the header.</dd><dt>2001-12-17</dt><dd>Support title attribute on references element</dd><dt>2002-01-05</dt><dd>Support for list/@style="@format"</dd><dt>2002-01-09</dt><dd>Display "closed" RFC issues as deleted</dd><dt>2002-01-14</dt><dd>Experimentally and optionally parse XML encountered in artwork elements (requires MSXSL).</dd><dt>2002-01-27</dt><dd>Some cleanup. Moved RFC issues from PIs into namespaced elements.</dd><dt>2002-01-29</dt><dd>Added support for sortrefs PI. Added support for figure names.</dd><dt>2002-02-07</dt><dd>Highlight parts of artwork which are too wide (72 characters).</dd><dt>2002-02-12</dt><dd>Code rearrangement for static texts. Fixes for section numbering. TOC generation rewritten.</dd><dt>2002-02-15</dt><dd>Support for irefs in sections; support iref @primary=true</dd><dt>2002-03-03</dt><dd>Moved anchor prefix into a constant. Added sanity checks on user anchor names.</dd><dt>2002-03-23</dt><dd>Bugfix in detection of matching org names when creating the header. Fixed sorting in subitems.</dd><dt>2002-04-02</dt><dd>Fix TOC link HTML generation when no TOC is generated (created broken HTML table code).</dd><dt>2002-04-03</dt><dd>Made rendering of references more tolerant re: missing parts.</dd><dt>2002-04-08</dt><dd>Fixed reference numbering when references are split into separate sections.</dd><dt>2002-04-16</dt><dd>Fix default namespace (shouldn't be set for HTML output method).</dd><dt>2002-04-19</dt><dd>Lowercase internal CSS selectors for Mozilla compliance. Do not put TOC into ul element.</dd><dt>2002-04-21</dt><dd>Make numbered list inside numbered lists use alphanumeric numbering.</dd><dt>2002-05-05</dt><dd>Updated issue/editing support.</dd><dt>2002-05-15</dt><dd>Bugfix for section numbering after introduction of ed:replace</dd><dt>2002-06-21</dt><dd>When producing private documents, do not include document status, copyright etc.</dd><dt>2002-07-08</dt><dd>Fix xrefs to Appendices.</dd><dt>2002-07-19</dt><dd>Make artwork lightyellow for easier reading. (fielding)</dd><dt>2002-10-09</dt><dd>Translate references title to anchor name to avoid non-uri characters. (fielding)</dd><dt>2002-10-13</dt><dd>Support for tocdepth PI.</dd><dt>2002-11-03</dt><dd>Added temporariry workaround for Mozilla/Transformiix result tree fragment problem. (search for 'http://bugzilla.mozilla.org/show_bug.cgi?id=143668')</dd><dt>2002-12-25</dt><dd>xref code: attempt to uppercase "section" and "appendix" when at the start of a sentence.</dd><dt>2003-02-02</dt><dd>fixed code for vspace blankLines="0", enhanced display for list with "format" style, got rid of HTML blockquote elements, added support for "hangIndent"</dd><dt>2003-04-10</dt><dd>experimental support for appendix and spanx elements</dd><dt>2003-04-19</dt><dd>fixed counting of list numbers in "format %" styles (one counter per unique format string). Added more spanx styles.</dd><dt>2003-05-02</dt><dd>experimental texttable support</dd><dt>2003-05-02</dt><dd>Make mailto links optional (default = none) (jre: default and PI name changed) (fielding)</dd><dt>2003-05-04</dt><dd>experimental support for HTML link elements; fix default for table header alignment default</dd><dt>2003-05-06</dt><dd>support for "background" PI.</dd><dt>2003-05-11</dt><dd>change %c format to lowercase alphabetic. add support for keyword elements (generate META tag). fix various HTML conformance problems. added experimental support for role attribute. do not number paragraphs in unnumbered sections. update boilerplate texts. support for "iprnotified" PI. bugfix list numbering. strip whitespace when building tel: URIs.</dd><dt>2003-05-12</dt><dd>more conformance fixes (layout moved into CSS, move lists and figures out of para content, do not use tables for list formatting)</dd><dt>2003-05-13</dt><dd>add DC.Creator meta tag, refactoring</dd><dt>2003-05-16</dt><dd>put nbsps between "section" and section number (xref).</dd><dt>2003-05-18</dt><dd>author summary: add missing comma.</dd><dt>2003-06-06</dt><dd>fix index generation bug (transposed characters in key generation). Enhance sentence start detection (xref starting a section was using lowercase "section").</dd><dt>2003-06-22</dt><dd>exp. support for xref/@format. Add missing support for eref w/o content. exp. support for annotations in reference elements. Code cleanup reference table formatting.</dd><dt>2003-07-09</dt><dd>Another fix for DC.Creator meta tag creation based on RFC2731</dd><dt>2003-07-24</dt><dd>Fix namespace name for DC.Creator.</dd><dt>2003-08-06</dt><dd>Cleanup node-set support (only use exslt (saxon, xalan, libxslt) extension functions; remove Transformix workarounds that stopped to work in Moz 1.4)</dd><dt>2003-08-09</dt><dd>Generate HTML lang tag.</dd><dt>2003-08-10</dt><dd>Map spanx/verb to HTML "samp" element. Fix author name display in references (reverse surname/initials for last author), add "Ed.". Fix internal bookmark generation.</dd><dt>2003-08-17</dt><dd>Add DCMI dates, identifiers and abstract. Add PI to suppress DCMI generation. Do not add TOC entry to Copyright Statement when there is none. Align RFC2629 PI names and parameter names. Change style for inline URIs generated by eref. Add header and footer support. Enhance CSS paging properties. Support topblock PI. Added hooks for proper XHTML generation through separate XSLT. Enhance warning and error messages. Add support for artwork image display. Table formatting fixes (borders, thead continuation).</dd><dt>2003-08-18</dt><dd>Add workaround for MSXML4 node-set and Mozilla node-set issues (fallback just displays are warning).</dd><dt>2003-10-06</dt><dd>Add workaround for broken pre/ins handling in Mozilla (see <<a href="http://bugzilla.mozilla.org/show_bug.cgi?id=204401">http://bugzilla.mozilla.org/show_bug.cgi?id=204401</a>>). Make use of cite attribute on ed:replace. CSS cleanup.</dd><dt>2003-10-08</dt><dd>Fix minor issue detecting the same org for the header (caused by IE's non-standard whitespace handling). Fix default handling for /rfc/@category.</dd><dt>2003-11-09</dt><dd>Inherit ed:entered-by from ancestor elements. Change CSS color for inserted text to green. Generate issues-list anchor. Do not complain about missing targets when the xref element is below ed:del. Remove code that attempted to distinguish section/Section when producing links - always use uppercase. Fix date rendering for issue resolutions.</dd><dt>2003-11-29</dt><dd>Fix color values for table backgrounds for issue rendering. Change rendering of issue links to use inline-styles. Add colored issue markers to issues.</dd><dt>2003-12-13</dt><dd>Fix inheritance of ed:entered-by attribute. Display note elements inside change tracking as well.</dd><dt>2004-01-18</dt><dd>When PI compact = 'yes', make most CSS print page breaks conditional.</dd><dt>2004-02-20</dt><dd>Support for RFC3667 IPR changes (xml2rfc 1.22); see <<a href="http://lists.xml.resource.org/pipermail/xml2rfc/2004-February/001088.html">http://lists.xml.resource.org/pipermail/xml2rfc/2004-February/001088.html</a>>.</dd><dt>2004-03-11</dt><dd>Add "(if approved)" to "updates" and "obsoletes" unless the document has an RFC number.</dd><dt>2004-04-01</dt><dd>Fix RFC3667 output, see <<a href="http://lists.xml.resource.org/pipermail/xml2rfc/2004-April/001208.html">http://lists.xml.resource.org/pipermail/xml2rfc/2004-April/001208.html</a>>.</dd><dt>2004-04-04</dt><dd>Add support for section/top attribute. Move references into plain section container.</dd><dt>2004-04-06</dt><dd>Do not emit identical para anchors for deleted content.</dd><dt>2004-04-14</dt><dd>Fix references TOC generation when there are no references.</dd><dt>2004-04-24</dt><dd>Fix RFC3667 output, see <<a href="http://xml.resource.org/pipermail/xml2rfc/2004-April/001246.html">http://xml.resource.org/pipermail/xml2rfc/2004-April/001246.html</a>>.</dd><dt>2004-05-09</dt><dd>Add custom support for generating compound index documents. Add anchors for each Index letter. Add experimental cref support. Fix conditional page breaks before References section.</dd><dt>2004-05-16</dt><dd>Refactor external index generation.</dd><dt>2004-05-20</dt><dd>Rewrite anchor generation for comments.</dd><dt>2004-05-22</dt><dd>Enhance issues rendering (add links to changes).</dd><dt>2004-05-30</dt><dd>Allow single quote as delimiter in processing instructions as well. Move block-level issue pointers to floats. Disable issue pointers for print media. Add "purple numbers". Add hrefs to section headings. Add non-printing index key letter list to start of index.</dd><dt>2004-06-01</dt><dd>Use &#xb6; instead of # for PNs.</dd><dt>2004-07-18</dt><dd>Add support for list style=letters (thanks Roy F.). Make PNs optional; add new PI.</dd><dt>2004-09-05</dt><dd>Fix index links into unnumbered sections. Bring IPR boilerplate in-line with xml2rfc 1.25. Add experimental CSS3 paged media support. Various HTML fixes.</dd><dt>2004-09-21</dt><dd>Enhance checking of artwork width.</dd><dt>2004-09-26</dt><dd>Add check for unused references. Uppercase letters in list style letters when nested into another list.</dd><dt>2004-10-10</dt><dd>Fix internal change track pointers.</dd><dt>2004-11-01</dt><dd>Allow change tracking on references (as a whole). Rewrite artwork handling so that it allows change tracking inside artwork. Also allow a subset of text markup inside artwork, such as xrefs (note this requires post-processing the source to make it compliant to RFC2629bis).</dd><dt>2004-11-03</dt><dd>Enhanced placement of iref anchors.</dd><dt>2004-11-06</dt><dd>Index: display irefs that appeared (with primary=true) inside artwork elements in a monospaced font.</dd><dt>2004-11-14</dt><dd>Add special code so that changes in section titles can be change-tracked.</dd><dt>2005-01-14</dt><dd>Bugfixes for HtmlToXhtml converter.</dd><dt>2005-01-22</dt><dd>Enhance generation of HTML h* elements (for Mozilla Outliner).</dd><dt>2005-01-31</dt><dd>Put vertical space around top-level TOC entries in TOC. Switch to pt-based CSS. Re-arrange top section. Make hr elements reflect new-page settings in TXT output (compact-PI). Fix page number in footer (CSS print) and add some more experimental support for paged media (tested with Prince 4.1 alpha). Rewrite TOC and Index generation to generate HTML lists. Cleanup id generation for paragraphs. Reduce whitespace in output. Fix vspace implementation. Use right/left dqoutes and copyright sign where appropriate.</dd><dt>2005-02-04</dt><dd>Add <link> element to references section. Fix newly introduced bug in references processing.</dd><dt>2005-02-05</dt><dd>Integrate various fixes/enhancements by Roy Fielding: spelling of "Authors' Addresses", comma setting in references, position of "Authors" section, optionally place authors addresses at end (PI), trailing dots in section numbers, switch to verdana default font in CSS. Add experimental support for centered artwork.</dd><dt>2005-02-09</dt><dd>Fixes in spacing and links of references section titles. Enhance sorting in references when change tracking is in place. Re-add figure centering support. Add missing 2nd part of "Author's Adresses" fix.</dd><dt>2005-02-25</dt><dd>Align section number format with xml2rfc1.29.</dd><dt>2005-03-28</dt><dd>Get rid of table elements in Author's section. Add experimental hCard (<<a href="http://developers.technorati.com/wiki/hCard">http://developers.technorati.com/wiki/hCard</a>>) support.</dd><dt>2005-04-03</dt><dd>Add RFC3978-style IPR statement support. (fenner@research.att.com)</dd><dt>2005-04-11</dt><dd>Cleanup author display. hCard related fixes.</dd><dt>2005-05-07</dt><dd>Minor fixes to allow change tracking in doc title. Add experimental support for table border styles. CSS cleanup.</dd><dt>2005-06-18</dt><dd>Implement missing support for references to texttables.</dd><dt>2005-09-25</dt><dd>Use (-moz-)column-count when printing the index.</dd><dt>2005-10-04</dt><dd>Report missing element templates with xsl:message.</dd><dt>2005-10-15</dt><dd>Process t/@anchor.</dd><dt>2005-10-23</dt><dd>More workarounds for Mozilla's broken del/ins handling (this time for figures).</dd><dt>2005-10-27</dt><dd>lowercase hCard class names</dd><dt>2005-11-22</dt><dd>Enhance diagnostics for XML-in-artwork extension</dd><dt>2005-11-26</dt><dd>Fix formatting of section numbers for sections inserted into <back>.</dd><dt>2005-12-12</dt><dd>Fix some validity problems when change tracking occured inside lists.</dd><dt>2005-12-18</dt><dd>Add change tracking inside the index.</dd><dt>2006-02-04</dt><dd>Add prev/next links to highlighted changes (change tracking extension).</dd><dt>2006-02-10</dt><dd>Catch errors instantiating MSXML component.</dd><dt>2006-02-11</dt><dd>References: add "work in progress" for Internet Drafts.</dd><dt>2006-02-27</dt><dd>Fix front matter (lowercase Internet-Draft, say "Intended status" for non-RFC documents). Start work on experimental extension for simplified internal links.</dd><dt>2006-03-19</dt><dd>Tweaks to IESG Copyright stuff; support submissionType attribute. Fix duplicate reference anchors in HTML output. Reduce HTML Tidy warnings. Fix reference to normative ASCII version (now requires trailing ".txt"). Tweaks to hCard generation. Started to move non-issue-tracking extensions into namespace "http://purl.org/net/xml2rfc/ext".</dd><dt>2006-03-27</dt><dd>Moved "simple reference" extension into namespace "http://purl.org/net/xml2rfc/ext" and add documentation. HTML conformance enhancements.</dd><dt>2006-04-02</dt><dd>Cleanup special code for automated XHTML XSLT generation.</dd><dt>2006-04-21</dt><dd>Generate <CITE> elements where appropiate. Introduce x:blockquote, x:dfn, x:h and x:q elements.</dd><dt>2006-05-06</dt><dd>Introduce x:bcp14 element.</dd><dt>2006-05-14</dt><dd>Fix content model for x:blockquote.</dd><dt>2006-06-18</dt><dd>Add box drawing support (x:bt, x:bc, x:bb).</dd><dt>2006-06-20</dt><dd>HTML validity fixes (legal chars in anchors in index).</dd><dt>2006-06-24</dt><dd>Reduce leading empty lines in artwork. Move <dt> style info into CSS.</dd><dt>2006-07-14</dt><dd>Fix rendering of multiple street address entries (missing line break).</dd><dt>2006-07-24</dt><dd>Add extension for deep linking into RFCs, do not generate empty list items in TOC output, avoid empty <dt> elements for list items without hangText attribute.</dd><dt>2006-08-01</dt><dd>Allow @anchor on more elements; start work on Relax NG grammar for extensions. Reduce generated style elements (use CSS classes instead). Consistently use "id" instead of "name". Change default target for RFC links to "http://tools.ietf.org/html/rfcNNNN".</dd><dt>2006-08-06</dt><dd>Include appendices defined in <appendix> elements in TOC (please consider them deprecated anyhow!). Generate links to "http://tools.ietf.org/html/draft-*" for Internet Drafts. Replace x:frag by x:rel, allowing any kind of relative reference instead of just fragments.</dd><dt>2006-08-30</dt><dd>Reduce textual differences between HTML output and what xml2rfc produces in TXT output mode (section refs/reference targets). Add small workaround for Opera 9.0.1's problem with node-set().</dd><dt>2006-10-29</dt><dd>Fix problem generating internal links to change markup within references section. Enhancements when generating numbered references for deleted references. Allow inclusion of references into the index (through include-references-in-index extension). Fix a bug that caused the newer version of the IETF boilerplate to be produced rather than the pre-RFC3667 one. Update to RFC4287 boilerplate.</dd><dt>2006-11-11</dt><dd>Add extension attribute x:for-anchor to <iref> handling.</dd><dt>2006-11-26</dt><dd>Experimental (and limited) support for <x:lt>.</dd><dt>2006-12-04</dt><dd>Fix bugs in processing documents that have both the ipr and the number attribute set on the rfc root element. Add support for x:fmt='none' on xrefs. Add different pre style based on artwork type attributes (experimental).</dd><dt>2006-12-13</dt><dd>Add x:fmt='anchor' for xref elements.</dd><dt>2007-01-07</dt><dd>Fix root template for compatibility for the exslt:node-set implementation in Firefox3.</dd><dt>2007-01-29</dt><dd>Avoid empty table entry in front matter when organization is not specified for an author.</dd><dt>2007-02-10</dt><dd>Allow change tracking in table rows.</dd><dt>2007-03-09</dt><dd>Add hcard profile URI (<<a href="http://www.w3.org/2006/03/hcard">http://www.w3.org/2006/03/hcard</a>>) to head element. Add warning for misplaced <t> elements (after section).</dd><dt>2007-03-21</dt><dd>Fix internal linking from reference entries in index for some xref types. Minor CSS tweaks contributed by MTR. Allow turning on text justification through a PI. Improve iref anchor generation to generate less instable anchors.</dd><dt>2007-03-28</dt><dd>Fixes for numbering of ed:inserted references sections.</dd><dt>2007-05-04</dt><dd>Do not generate anchors for edits in deleted sections. Enhance HTML conformance.</dd><dt>2007-05-19</dt><dd>Enhance diagnostics when using Saxon (needs Saxon's "-l" command line parameter to keep line number information). Add warning when symref PI is missing (default will change in the future). Add support for overriding computed section numbers (when formatting historic documents).</dd><dt>2007-06-07</dt><dd>Change default for symrefs PI to "yes" (see change in xml2rfc 1.33pre4). Warn about docName attributes that appear to contain a file extension.</dd><dt>2007-06-26</dt><dd>Workaround author/@initials values without trailing dot, as in xml2rfc.tcl.</dd><dt>2007-07-14</dt><dd>Enhance index generation for references that use @x:sec attribute.</dd><dt>2007-09-09</dt><dd>Fix: sortrefs is a nop when symrefs=no.</dd><dt>2007-10-17</dt><dd>Work in progress: add support for referencing sections in sibling documents by anchor name.</dd><dt>2007-10-17</dt><dd>Work in progress (continued): support for referencing sections in sibling documents by anchor name.</dd><dt>2007-12-31</dt><dd>Emit warning when updating/obsoleting stuff that's not referenced.</dd><dt>2008-02-03</dt><dd>Support xml2rfc-1.33pre5's suppress-title attribute on texttable and figure.</dd><dt>2008-02-06</dt><dd>Extension: allow <eref> below <cref>.</dd><dt>2008-02-17</dt><dd>Extensions: add x:span and x:length-of.</dd><dt>2008-02-20</dt><dd>Add new RFC boilerplate (as changed in 2007-08).</dd><dt>2008-02-27</dt><dd>Improve diagnostics for artwork width problems; add defaulting of publication dates (requires XSLT processor supporting exslt:date, or msxml).</dd><dt>2008-02-29</dt><dd>Enhance CSS for link elements in the front header, update rules for generating "Acknowledgment" statement.</dd><dt>2008-03-01</dt><dd>Use line numbers in diagnostics in Saxon8/9 as well.</dd><dt>2008-03-02</dt><dd>Fix a bug in the logic choosing the boilerplate, resulting in obsolete text being inserted into IDs.</dd><dt>2008-04-01</dt><dd>Add support for superscript element.</dd><dt>2008-06-28</dt><dd>Add sanity checks for email addresses, allow multiple email elements.</dd><dt>2008-07-06</dt><dd>Add x:abnf-char-sequence.</dd><dt>2008-08-21</dt><dd>Add x:note.</dd><dt>2008-09-06</dt><dd>Add experimental support for SVG images.</dd><dt>2008-09-17</dt><dd>Add experimental support for x:author. Fix xref/@format=none.</dd><dt>2008-10-10</dt><dd>Fix a huge bug, causing text content after an XML comment to be ignored.</dd><dt>2009-02-24</dt><dd>Use table/caption when needed.</dd><dt>2009-03-07</dt><dd>Fix bug that caused text to disappear in the output in presence of processing instructions.</dd><dt>2009-03-12</dt><dd>Make inlined comments bookmarkable.</dd><dt>2009-04-09</dt><dd>Upgrade to DC-HTML from RFC 2731 (affects head/@profile).</dd><dt>2009-07-08</dt><dd>Remove table/@summary in output; the value getting inserted was just repeating stuff that appeared in the preamble.</dd><dt>2009-08-01</dt><dd>Implement table alignment (HTML output only for now).</dd><dt>2009-08-18</dt><dd>Replicate Dublin Core "abstract" metadata into meta/@name=description (search engines do use it).</dd><dt>2009-09-02</dt><dd>Fix default/left alignment of table columns, remove silly table summmary attributes.</dd><dt>2009-09-24</dt><dd>Support double-sided layout using CSS page:left/right selectors.</dd><dt>2009-11-27</dt><dd>Generate unordered lists instead of broken definition lists for list style empty.</dd></dl><h2 id="rfc.section.F.6"><a href="#rfc.section.F.6">F.6</a> rfc2629toFO.xslt</h2><dl><dt>2003-11-16</dt><dd>Initial release.</dd><dt>2003-11-29</dt><dd>Enhance handling of unknown list styles.</dd><dt>2004-04-04</dt><dd>Update reference section handling.</dd><dt>2004-04-17</dt><dd>Use XSL-WD-1.1-style fo:bookmark and index handling and add postprocessors for existing implementations. Unify PDF info generation by using XEP (postprocessors) will convert.</dd><dt>2004-04-20</dt><dd>Add experimental cref support.</dd><dt>2004-06-14</dt><dd>Set correct index-item defaults.</dd><dt>2004-07-18</dt><dd>Add list style=letters.</dd><dt>2004-09-03</dt><dd>Make URLs in text break where they are allowed to break by inserting zero-width spaces.</dd><dt>2004-09-26</dt><dd>Fix letter-style inside nested lists.</dd><dt>2004-10-31</dt><dd>Update handling of artwork.</dd><dt>2004-11-13</dt><dd>Fix handling of references inside ed:* markup. Fix whitespace handling in artwork.</dd><dt>2004-11-27</dt><dd>Irefs in artwork generate monospaced entries in index.</dd><dt>2005-01-31</dt><dd>Fix TOC generation that was broken after changes in main XSLT.</dd><dt>2005-02-05</dt><dd>Bring in sync with cosmetic changes in rfc2629.xslt.</dd><dt>2005-05-07</dt><dd>Minor fix for change tracking in document title. Support for table styles.</dd><dt>2005-06-18</dt><dd>Fix references to tables.</dd><dt>2005-10-15</dt><dd>Process t/@anchor.</dd><dt>2006-02-11</dt><dd>References: add "work in progress" for Internet Drafts.</dd><dt>2006-06-02</dt><dd>Use XSL 1.1 WD Feb 2006.</dd><dt>2007-03-21</dt><dd>Support optional text justification.</dd><dt>2007-05-19</dt><dd>Various improvements in spacing; also allow overriding the automatic list indentation via list/x:indent.</dd><dt>2009-04-08</dt><dd>Fix spacing in headers; add support for formatting for double-sided printing.</dd><dt>2009-08-01</dt><dd>Remove surplus empty pages when not generating double-sided output.</dd></dl><h2 id="rfc.section.F.7"><a href="#rfc.section.F.7">F.7</a> xsl11toAn.xslt</h2><dl><dt>2004-05-17</dt><dd>Initial release.</dd><dt>2006-06-02</dt><dd>Use XSL 1.1 WD Feb 2006.</dd></dl><h2 id="rfc.section.F.8"><a href="#rfc.section.F.8">F.8</a> xsl11toFop.xslt</h2><dl><dt>2010-08-25</dt><dd>Switch to Apache FOP 1.0.</dd><dt>2009-09-12</dt><dd>Support for FOP 0.20.5 and FOP 0.93 removed. Please use FOP 0.95.</dd><dt>2008-03-15</dt><dd>Add a workaround to the fo:inline workaround (sigh).</dd></dl><h2 id="rfc.section.F.9"><a href="#rfc.section.F.9">F.9</a> xsl11toXep.xslt</h2><dl><dt>2004-05-17</dt><dd>Initial release.</dd><dt>2004-09-04</dt><dd>Fix xep:index-item attributes.</dd><dt>2006-06-02</dt><dd>Use XSL 1.1 WD Feb 2006.</dd></dl><hr class="noprint"><h1 id="rfc.index" class="np"><a href="#rfc.index">Index</a></h1><p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.F">F</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.J">J</a> <a href="#rfc.index.K">K</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.Q">Q</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.X">X</a> </p><div class="print2col"><ul class="ind"><li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul><li>abnf-char-sequence Extension Element <a href="#rfc.iref.a.27"><b>11.1</b></a>, <a href="#rfc.iref.a.29">A</a></li><li>allow-markup-in-artwork PI pseudo-attribute <a href="#rfc.iref.a.1">3.3</a></li><li>alternate HTML LINK element <a href="#rfc.iref.a.22">6.2</a></li><li>anchor-alias Extension Element <a href="#rfc.iref.a.28"><b>11.2</b></a>, <a href="#rfc.iref.a.30">A</a></li><li>Anchors <ul><li>rfc.abstract <a href="#rfc.iref.a.3">4</a></li><li>rfc.authors <a href="#rfc.iref.a.4">4</a></li><li>rfc.copyright <a href="#rfc.iref.a.5">4</a></li><li>rfc.copyrightnotice <a href="#rfc.iref.a.6">4</a></li><li>rfc.figure.n <a href="#rfc.iref.a.7">4</a>, <a href="#rfc.iref.a.18">4</a></li><li>rfc.figure.u.n <a href="#rfc.iref.a.8">4</a>, <a href="#rfc.iref.a.19">4</a></li><li>rfc.index <a href="#rfc.iref.a.9">4</a></li><li>rfc.ipr <a href="#rfc.iref.a.10">4</a></li><li>rfc.iref.n <a href="#rfc.iref.a.11">4</a></li><li>rfc.note.n <a href="#rfc.iref.a.12">4</a></li><li>rfc.references <a href="#rfc.iref.a.13">4</a>, <a href="#rfc.iref.a.14">4</a></li><li>rfc.section.n <a href="#rfc.iref.a.15">4</a></li><li>rfc.section.n.p.m <a href="#rfc.iref.a.16">4</a></li><li>rfc.status <a href="#rfc.iref.a.17">4</a></li><li>rfc.toc <a href="#rfc.iref.a.20">4</a></li><li>rfc.xref.name.n <a href="#rfc.iref.a.21">4</a></li></ul></li><li>AntennaHouse XSL Formatter <a href="#rfc.iref.a.26">9.1</a></li><li>Apache FOP <a href="#rfc.iref.a.25">9.1</a></li><li>appendix HTML LINK element <a href="#rfc.iref.a.23">6.2</a></li><li>assign-section-number Extension Element <a href="#rfc.iref.a.31">A</a></li><li>author HTML LINK element <a href="#rfc.iref.a.24">6.2</a></li><li>authors-section PI pseudo-attribute <a href="#rfc.iref.a.2">3.3</a></li></ul></li><li><a id="rfc.index.B" href="#rfc.index.B"><b>B</b></a><ul><li>background PI pseudo-attribute <a href="#rfc.iref.b.1">3.1</a></li><li>bb Extension Element <a href="#rfc.iref.b.3"><b>11.4</b></a>, <a href="#rfc.iref.b.8">A</a></li><li>bc Extension Element <a href="#rfc.iref.b.4"><b>11.5</b></a>, <a href="#rfc.iref.b.9">A</a></li><li>bcp14 Extension Element <a href="#rfc.iref.b.2"><b>11.3</b></a>, <a href="#rfc.iref.b.10">A</a></li><li><em>BCP97</em> <a href="#rfc.xref.BCP97.1">12.1</a>, <a href="#BCP97"><b>13</b></a></li><li>blockquote Extension Element <a href="#rfc.iref.b.5"><b>11.6</b></a>, <a href="#rfc.iref.b.11">A</a></li><li>boilerplate Extension Element <a href="#rfc.iref.b.6"><b>11.7</b></a>, <a href="#rfc.iref.b.12">A</a></li><li>bt Extension Element <a href="#rfc.iref.b.7"><b>11.8</b></a>, <a href="#rfc.iref.b.13">A</a></li></ul></li><li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul><li>chapter HTML LINK element <a href="#rfc.iref.c.3">6.2</a></li><li>CHM format <a href="#rfc.iref.c.7">8</a></li><li>comments PI pseudo-attribute <a href="#rfc.iref.c.2">3.1</a></li><li>compact PI pseudo-attribute <a href="#rfc.iref.c.1">3.1</a></li><li>contents HTML LINK element <a href="#rfc.iref.c.4">6.2</a></li><li>copyright HTML LINK element <a href="#rfc.iref.c.5">6.2</a></li><li>Creator DCMI property <a href="#rfc.iref.c.6">6.4</a></li></ul></li><li><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul><li>Date.Issued DCMI property <a href="#rfc.iref.d.3">6.4</a></li><li><em>DC-HTML</em> <a href="#rfc.xref.DC-HTML.1">6.4</a>, <a href="#DC-HTML"><b>13</b></a></li><li>DCMI properties <ul><li>Creator <a href="#rfc.iref.d.2">6.4</a></li><li>Date.Issued <a href="#rfc.iref.d.4">6.4</a></li><li>Description.Abstract <a href="#rfc.iref.d.6">6.4</a></li><li>Identifier <a href="#rfc.iref.d.7">6.4</a></li><li>isPartOf <a href="#rfc.iref.d.8">6.4</a></li><li>Relation.Replaces <a href="#rfc.iref.d.9">6.4</a></li></ul></li><li>Description.Abstract DCMI property <a href="#rfc.iref.d.5">6.4</a></li><li>dfn Extension Element <a href="#rfc.iref.d.10"><b>11.9</b></a>, <a href="#rfc.iref.d.11">A</a></li><li>duplex PI pseudo-attribute <a href="#rfc.iref.d.1">3.3</a></li></ul></li><li><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul><li>editing PI pseudo-attribute <a href="#rfc.iref.e.1">3.1</a></li><li>Extension Elements <ul><li>abnf-char-sequence <a href="#rfc.iref.e.2"><b>11.1</b></a>, <a href="#rfc.iref.e.23">A</a></li><li>anchor-alias <a href="#rfc.iref.e.3"><b>11.2</b></a>, <a href="#rfc.iref.e.24">A</a></li><li>assign-section-number <a href="#rfc.iref.e.26">A</a></li><li>bb <a href="#rfc.iref.e.5"><b>11.4</b></a>, <a href="#rfc.iref.e.27">A</a></li><li>bc <a href="#rfc.iref.e.6"><b>11.5</b></a>, <a href="#rfc.iref.e.28">A</a></li><li>bcp14 <a href="#rfc.iref.e.4"><b>11.3</b></a>, <a href="#rfc.iref.e.29">A</a></li><li>blockquote <a href="#rfc.iref.e.7"><b>11.6</b></a>, <a href="#rfc.iref.e.30">A</a></li><li>boilerplate <a href="#rfc.iref.e.8"><b>11.7</b></a>, <a href="#rfc.iref.e.31">A</a></li><li>bt <a href="#rfc.iref.e.9"><b>11.8</b></a>, <a href="#rfc.iref.e.32">A</a></li><li>dfn <a href="#rfc.iref.e.10"><b>11.9</b></a>, <a href="#rfc.iref.e.33">A</a></li><li>h <a href="#rfc.iref.e.11"><b>11.10</b></a>, <a href="#rfc.iref.e.34">A</a></li><li>highlight <a href="#rfc.iref.e.12"><b>11.11</b></a>, <a href="#rfc.iref.e.35">A</a></li><li>include-author <a href="#rfc.iref.e.25">A</a></li><li>length-of <a href="#rfc.iref.e.13"><b>11.12</b></a>, <a href="#rfc.iref.e.36">A</a></li><li>link <a href="#rfc.iref.e.14"><b>11.13</b></a>, <a href="#rfc.iref.e.37">A</a></li><li>lt <a href="#rfc.iref.e.15"><b>11.14</b></a>, <a href="#rfc.iref.e.38">A</a></li><li>note <a href="#rfc.iref.e.16"><b>11.15</b></a>, <a href="#rfc.iref.e.39">A</a></li><li>parse-xml <a href="#rfc.iref.e.17"><b>11.16</b></a>, <a href="#rfc.iref.e.40">A</a></li><li>prose <a href="#rfc.iref.e.18"><b>11.17</b></a>, <a href="#rfc.iref.e.41">A</a></li><li>q <a href="#rfc.iref.e.19"><b>11.18</b></a>, <a href="#rfc.iref.e.42">A</a></li><li>rdf:Description <a href="#rfc.iref.e.48">A</a></li><li>ref <a href="#rfc.iref.e.20"><b>11.19</b></a>, <a href="#rfc.iref.e.43">A</a></li><li>source <a href="#rfc.iref.e.21"><b>11.20</b></a>, <a href="#rfc.iref.e.44">A</a></li><li>span <a href="#rfc.iref.e.46">A</a></li><li>sup <a href="#rfc.iref.e.22"><b>11.21</b></a>, <a href="#rfc.iref.e.45">A</a></li><li>x <a href="#rfc.iref.e.47">A</a></li></ul></li></ul></li><li><a id="rfc.index.F" href="#rfc.index.F"><b>F</b></a><ul><li>Firefox <ul><li>1.*/2.* <a href="#rfc.iref.f.3">5.2</a></li><li>3.* <a href="#rfc.iref.f.2">5.2</a></li></ul></li><li>footer PI pseudo-attribute <a href="#rfc.iref.f.1">3.1</a></li></ul></li><li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul><li>generator HTML META element <a href="#rfc.iref.g.2">6.3</a></li><li>Google Chrome <a href="#rfc.iref.g.1">5.2</a></li><li>Grammar <a href="#rfc.iref.g.3"><b>A</b></a></li></ul></li><li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul><li>h Extension Element <a href="#rfc.iref.h.12"><b>11.10</b></a>, <a href="#rfc.iref.h.14">A</a></li><li>header PI pseudo-attribute <a href="#rfc.iref.h.1">3.1</a></li><li>highlight Extension Element <a href="#rfc.iref.h.13"><b>11.11</b></a>, <a href="#rfc.iref.h.15">A</a></li><li><em>HTML</em> <a href="#rfc.xref.HTML.1">6.1</a>, <a href="#rfc.xref.HTML.2">11.6</a>, <a href="#rfc.xref.HTML.3">11.9</a>, <a href="#rfc.xref.HTML.4">11.18</a>, <a href="#rfc.xref.HTML.5">11.21</a>, <a href="#HTML"><b>13</b></a></li><li>HTML compliance <a href="#rfc.iref.h.2">6.1</a></li><li>HTML LINK elements <ul><li>alternate <a href="#rfc.iref.h.3">6.2</a></li><li>appendix <a href="#rfc.iref.h.4">6.2</a></li><li>author <a href="#rfc.iref.h.5">6.2</a></li><li>chapter <a href="#rfc.iref.h.6">6.2</a></li><li>contents <a href="#rfc.iref.h.7">6.2</a></li><li>copyright <a href="#rfc.iref.h.8">6.2</a></li><li>index <a href="#rfc.iref.h.9">6.2</a></li></ul></li><li>HTML META elements <ul><li>generator <a href="#rfc.iref.h.10">6.3</a></li><li>keywords <a href="#rfc.iref.h.11">6.3</a></li></ul></li></ul></li><li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul><li>Identifier DCMI property <a href="#rfc.iref.i.10">6.4</a></li><li>include PI pseudo-attribute <a href="#rfc.iref.i.3">3.2</a></li><li>include-author Extension Element <a href="#rfc.iref.i.12">A</a></li><li>include-references-in-index PI pseudo-attribute <a href="#rfc.iref.i.4">3.3</a></li><li>index HTML LINK element <a href="#rfc.iref.i.9">6.2</a></li><li>inline PI pseudo-attribute <a href="#rfc.iref.i.1">3.1</a></li><li>Internet Explorer 5.5 <a href="#rfc.iref.i.5">5.2</a></li><li>Internet Explorer 6 <a href="#rfc.iref.i.6">5.2</a></li><li>Internet Explorer 7 <a href="#rfc.iref.i.7">5.2</a></li><li>Internet Explorer 8 <a href="#rfc.iref.i.8">5.2</a></li><li>iprnotified PI pseudo-attribute <a href="#rfc.iref.i.2">3.1</a></li><li>isPartOf DCMI property <a href="#rfc.iref.i.11">6.4</a></li></ul></li><li><a id="rfc.index.J" href="#rfc.index.J"><b>J</b></a><ul><li>justification PI pseudo-attribute <a href="#rfc.iref.j.1">3.3</a></li></ul></li><li><a id="rfc.index.K" href="#rfc.index.K"><b>K</b></a><ul><li>keywords HTML META element <a href="#rfc.iref.k.1">6.3</a></li></ul></li><li><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul><li>length-of Extension Element <a href="#rfc.iref.l.2"><b>11.12</b></a>, <a href="#rfc.iref.l.5">A</a></li><li>link Extension Element <a href="#rfc.iref.l.3"><b>11.13</b></a>, <a href="#rfc.iref.l.6">A</a></li><li>linkmailto PI pseudo-attribute <a href="#rfc.iref.l.1">3.1</a></li><li>lt Extension Element <a href="#rfc.iref.l.4"><b>11.14</b></a>, <a href="#rfc.iref.l.7">A</a></li></ul></li><li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul><li>Microsoft Help <a href="#rfc.iref.m.5">8</a></li><li>Mozilla <a href="#rfc.iref.m.3">5.2</a>, <a href="#rfc.iref.m.4">5.2</a></li><li>MSXML3 <a href="#rfc.iref.m.1">5.1</a></li><li>MSXML4 <a href="#rfc.iref.m.2">5.1</a></li></ul></li><li><a id="rfc.index.N" href="#rfc.index.N"><b>N</b></a><ul><li>needLines PI pseudo-attribute <a href="#rfc.iref.n.1">3.2</a></li><li>NoScript <a href="#rfc.iref.n.2">5.2</a></li><li>note Extension Element <a href="#rfc.iref.n.3"><b>11.15</b></a>, <a href="#rfc.iref.n.4">A</a></li></ul></li><li><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul><li>Opera <a href="#rfc.iref.o.1">5.2</a>, <a href="#rfc.iref.o.2">5.2</a></li></ul></li><li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul><li>Parameters <ul><li>xml2rfc-background <a href="#rfc.iref.p.2">3.1</a></li><li>xml2rfc-comments <a href="#rfc.iref.p.6">3.1</a></li><li>xml2rfc-compact <a href="#rfc.iref.p.4">3.1</a></li><li>xml2rfc-editing <a href="#rfc.iref.p.8">3.1</a></li><li>xml2rfc-ext-allow-markup-in-artwork <a href="#rfc.iref.p.44">3.3</a></li><li>xml2rfc-ext-authors-section <a href="#rfc.iref.p.46">3.3</a></li><li>xml2rfc-ext-duplex <a href="#rfc.iref.p.48">3.3</a></li><li>xml2rfc-ext-include-references-in-index <a href="#rfc.iref.p.50">3.3</a></li><li>xml2rfc-ext-justification <a href="#rfc.iref.p.52">3.3</a></li><li>xml2rfc-ext-parse-xml-in-artwork <a href="#rfc.iref.p.55">3.3</a></li><li>xml2rfc-ext-sec-no-trailing-dots <a href="#rfc.iref.p.59">3.3</a></li><li>xml2rfc-ext-support-rfc2731 <a href="#rfc.iref.p.57">3.3</a></li><li>xml2rfc-footer <a href="#rfc.iref.p.10">3.1</a></li><li>xml2rfc-header <a href="#rfc.iref.p.12">3.1</a></li><li>xml2rfc-inline <a href="#rfc.iref.p.14">3.1</a></li><li>xml2rfc-iprnotified <a href="#rfc.iref.p.16">3.1</a></li><li>xml2rfc-linkmailto <a href="#rfc.iref.p.18">3.1</a></li><li>xml2rfc-private <a href="#rfc.iref.p.21">3.1</a></li><li>xml2rfc-refparent <a href="#rfc.iref.p.23">3.1</a></li><li>xml2rfc-rfcedstyle <a href="#rfc.iref.p.25">3.1</a></li><li>xml2rfc-sortrefs <a href="#rfc.iref.p.27">3.1</a></li><li>xml2rfc-symrefs <a href="#rfc.iref.p.29">3.1</a></li><li>xml2rfc-toc <a href="#rfc.iref.p.31">3.1</a></li><li>xml2rfc-tocdepth <a href="#rfc.iref.p.33">3.1</a></li><li>xml2rfc-topblock <a href="#rfc.iref.p.35">3.1</a></li></ul></li><li>parse-xml Extension Element <a href="#rfc.iref.p.60"><b>11.16</b></a>, <a href="#rfc.iref.p.62">A</a></li><li>parse-xml-in-artwork PI pseudo-attribute <a href="#rfc.iref.p.53">3.3</a></li><li>private PI pseudo-attribute <a href="#rfc.iref.p.19">3.1</a>, <a href="#rfc.iref.p.64">D</a></li><li>Processing Instruction pseudo attributes <ul><li>allow-markup-in-artwork <a href="#rfc.iref.p.43">3.3</a></li><li>authors-section <a href="#rfc.iref.p.45">3.3</a></li><li>background <a href="#rfc.iref.p.1">3.1</a></li><li>comments <a href="#rfc.iref.p.5">3.1</a></li><li>compact <a href="#rfc.iref.p.3">3.1</a></li><li>duplex <a href="#rfc.iref.p.47">3.3</a></li><li>editing <a href="#rfc.iref.p.7">3.1</a></li><li>footer <a href="#rfc.iref.p.9">3.1</a></li><li>header <a href="#rfc.iref.p.11">3.1</a></li><li>ijustification <a href="#rfc.iref.p.51">3.3</a></li><li>include <a href="#rfc.iref.p.36">3.2</a></li><li>include-references-in-index <a href="#rfc.iref.p.49">3.3</a></li><li>inline <a href="#rfc.iref.p.13">3.1</a></li><li>iprnotified <a href="#rfc.iref.p.15">3.1</a></li><li>linkmailto <a href="#rfc.iref.p.17">3.1</a></li><li>needLines <a href="#rfc.iref.p.37">3.2</a></li><li>parse-xml-in-artwork <a href="#rfc.iref.p.54">3.3</a></li><li>private <a href="#rfc.iref.p.20">3.1</a>, <a href="#rfc.iref.p.65">D</a></li><li>refparent <a href="#rfc.iref.p.22">3.1</a></li><li>rfcedstyle <a href="#rfc.iref.p.24">3.1</a></li><li>sec-no-trailing-dots <a href="#rfc.iref.p.58">3.3</a></li><li>slides <a href="#rfc.iref.p.38">3.2</a></li><li>sortrefs <a href="#rfc.iref.p.26">3.1</a></li><li>strict <a href="#rfc.iref.p.39">3.2</a></li><li>subcompact <a href="#rfc.iref.p.40">3.2</a></li><li>support-rfc2731 <a href="#rfc.iref.p.56">3.3</a></li><li>symrefs <a href="#rfc.iref.p.28">3.1</a></li><li>toc <a href="#rfc.iref.p.30">3.1</a></li><li>tocdepth <a href="#rfc.iref.p.32">3.1</a></li><li>tocindent <a href="#rfc.iref.p.41">3.2</a></li><li>tocompact <a href="#rfc.iref.p.42">3.2</a></li><li>topblock <a href="#rfc.iref.p.34">3.1</a></li></ul></li><li>prose Extension Element <a href="#rfc.iref.p.61"><b>11.17</b></a>, <a href="#rfc.iref.p.63">A</a></li></ul></li><li><a id="rfc.index.Q" href="#rfc.index.Q"><b>Q</b></a><ul><li>q Extension Element <a href="#rfc.iref.q.1"><b>11.18</b></a>, <a href="#rfc.iref.q.2">A</a></li></ul></li><li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul><li>rdf:Description Extension Element <a href="#rfc.iref.r.26">A</a></li><li>ref Extension Element <a href="#rfc.iref.r.23"><b>11.19</b></a>, <a href="#rfc.iref.r.25">A</a></li><li>refparent PI pseudo-attribute <a href="#rfc.iref.r.1">3.1</a></li><li>Relation.Replaces DCMI property <a href="#rfc.iref.r.22">6.4</a></li><li>RELAX NG Compact Schema <a href="#rfc.iref.r.24"><b>A</b></a></li><li>rfc.abstract anchor <a href="#rfc.iref.r.3">4</a></li><li>rfc.authors anchor <a href="#rfc.iref.r.4">4</a></li><li>rfc.copyright anchor <a href="#rfc.iref.r.5">4</a></li><li>rfc.copyrightnotice anchor <a href="#rfc.iref.r.6">4</a></li><li>rfc.figure.n anchor <a href="#rfc.iref.r.7">4</a>, <a href="#rfc.iref.r.18">4</a></li><li>rfc.figure.u.n anchor <a href="#rfc.iref.r.8">4</a>, <a href="#rfc.iref.r.19">4</a></li><li>rfc.index anchor <a href="#rfc.iref.r.9">4</a></li><li>rfc.ipr anchor <a href="#rfc.iref.r.10">4</a></li><li>rfc.iref.n anchor <a href="#rfc.iref.r.11">4</a></li><li>rfc.note.n anchor <a href="#rfc.iref.r.12">4</a></li><li>rfc.references anchor <a href="#rfc.iref.r.13">4</a></li><li>rfc.references.n anchor <a href="#rfc.iref.r.14">4</a></li><li>rfc.section.n anchor <a href="#rfc.iref.r.15">4</a></li><li>rfc.section.n.p.m anchor <a href="#rfc.iref.r.16">4</a></li><li>rfc.status anchor <a href="#rfc.iref.r.17">4</a></li><li>rfc.toc anchor <a href="#rfc.iref.r.20">4</a></li><li>rfc.xref.name.n anchor <a href="#rfc.iref.r.21">4</a></li><li><em>RFC2026</em> <a href="#rfc.xref.RFC2026.1">11.25</a>, <a href="#RFC2026"><b>13</b></a>, <a href="#rfc.xref.RFC2026.2">D.2</a><ul><li><em>Section 4</em> <a href="#rfc.xref.RFC2026.2">D.2</a></li><li><em>Section 4.1</em> <a href="#rfc.xref.RFC2026.1">11.25</a></li></ul></li><li><em>RFC2119</em> <a href="#rfc.xref.RFC2119.1">11.3</a>, <a href="#rfc.xref.RFC2119.2">11.27</a>, <a href="#RFC2119"><b>13</b></a><ul><li><em>Section 5</em> <a href="#rfc.xref.RFC2119.2">11.27</a></li></ul></li><li><em>RFC2616</em> <a href="#RFC2616"><b>13</b></a>, <a href="#rfc.xref.RFC2616.1">B.1</a>, <a href="#rfc.xref.RFC2616.2">B.1</a>, <a href="#rfc.xref.RFC2616.3">B.1</a><ul><li><em>Section 2.1</em> <a href="#rfc.xref.RFC2616.1">B.1</a></li><li><em>Section 19.1</em> <a href="#rfc.xref.RFC2616.2">B.1</a>, <a href="#rfc.xref.RFC2616.3">B.1</a></li></ul></li><li><em>RFC2629</em> <a href="#rfc.xref.RFC2629.1">1</a>, <a href="#RFC2629"><b>13</b></a></li><li><em>RFC2648</em> <a href="#rfc.xref.RFC2648.1">6.4</a>, <a href="#RFC2648"><b>13</b></a></li><li><em>RFC2731</em> <a href="#rfc.xref.RFC2731.1">6.4</a>, <a href="#RFC2731"><b>13</b></a></li><li><em>RFC5234</em> <a href="#RFC5234"><b>13</b></a>, <a href="#rfc.xref.RFC5234.1">B.1</a></li><li><em>RFC5741</em> <a href="#RFC5741"><b>13</b></a>, <a href="#rfc.xref.RFC5741.1">D.3</a>, <a href="#rfc.xref.RFC5741.2">D.3</a>, <a href="#rfc.xref.RFC5741.3">D.4</a><ul><li><em>Section 3.2.2</em> <a href="#rfc.xref.RFC5741.2">D.3</a>, <a href="#rfc.xref.RFC5741.3">D.4</a></li></ul></li><li>rfcedstyle PI pseudo-attribute <a href="#rfc.iref.r.2">3.1</a></li><li><em>RNC</em> <a href="#RNC"><b>13</b></a>, <a href="#rfc.xref.RNC.1">A</a>, <a href="#rfc.xref.RNC.2">B.1</a></li></ul></li><li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul><li>Safari <a href="#rfc.iref.s.9">5.2</a>, <a href="#rfc.iref.s.11">5.2</a><ul><li>3.* <a href="#rfc.iref.s.10">5.2</a></li></ul></li><li>Saxon <a href="#rfc.iref.s.8">5.1</a></li><li>Schema <a href="#rfc.iref.s.14"><b>A</b></a></li><li>sec-no-trailing-dots PI pseudo-attribute <a href="#rfc.iref.s.7">3.3</a></li><li>slides PI pseudo-attribute <a href="#rfc.iref.s.3">3.2</a></li><li>sortrefs PI pseudo-attribute <a href="#rfc.iref.s.1">3.1</a></li><li>source Extension Element <a href="#rfc.iref.s.12"><b>11.20</b></a>, <a href="#rfc.iref.s.15">A</a></li><li>span Extension Element <a href="#rfc.iref.s.17">A</a></li><li>strict PI pseudo-attribute <a href="#rfc.iref.s.4">3.2</a></li><li>subcompact PI pseudo-attribute <a href="#rfc.iref.s.5">3.2</a></li><li>sup Extension Element <a href="#rfc.iref.s.13"><b>11.21</b></a>, <a href="#rfc.iref.s.16">A</a></li><li>support-rfc2731 PI pseudo-attribute <a href="#rfc.iref.s.6">3.3</a></li><li>symrefs PI pseudo-attribute <a href="#rfc.iref.s.2">3.1</a></li></ul></li><li><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul><li>toc PI pseudo-attribute <a href="#rfc.iref.t.1">3.1</a></li><li>tocdepth PI pseudo-attribute <a href="#rfc.iref.t.2">3.1</a></li><li>tocindent PI pseudo-attribute <a href="#rfc.iref.t.4">3.2</a></li><li>tocompact PI pseudo-attribute <a href="#rfc.iref.t.5">3.2</a></li><li>topblock PI pseudo-attribute <a href="#rfc.iref.t.3">3.1</a></li></ul></li><li><a id="rfc.index.X" href="#rfc.index.X"><b>X</b></a><ul><li>x Extension Element <a href="#rfc.iref.x.30">A</a></li><li>Xalan <a href="#rfc.iref.x.27">5.1</a></li><li><em>XHTML2</em> <a href="#rfc.xref.XHTML2.1">11.10</a>, <a href="#XHTML2"><b>13</b></a></li><li><em>XML</em> <a href="#XML"><b>13</b></a>, <a href="#rfc.xref.XML.1">C.1</a><ul><li><em>Section 2.8</em> <a href="#rfc.xref.XML.1">C.1</a></li></ul></li><li>xml-stylesheet PI <a href="#rfc.iref.x.29">6</a></li><li>xml2rfc-background parameter <a href="#rfc.iref.x.2">3.1</a></li><li>xml2rfc-comments parameter <a href="#rfc.iref.x.4">3.1</a></li><li>xml2rfc-editing parameter <a href="#rfc.iref.x.3">3.1</a>, <a href="#rfc.iref.x.5">3.1</a></li><li>xml2rfc-ext-allow-markup-in-artwork parameter <a href="#rfc.iref.x.19">3.3</a></li><li>xml2rfc-ext-authors-section parameter <a href="#rfc.iref.x.20">3.3</a></li><li>xml2rfc-ext-duplex <a href="#rfc.iref.x.21">3.3</a></li><li>xml2rfc-ext-include-references-in-index parameter <a href="#rfc.iref.x.22">3.3</a></li><li>xml2rfc-ext-justification parameter <a href="#rfc.iref.x.23">3.3</a></li><li>xml2rfc-ext-parse-xml-in-artwork parameter <a href="#rfc.iref.x.24">3.3</a></li><li>xml2rfc-ext-sec-no-trailing-dots parameter <a href="#rfc.iref.x.26">3.3</a></li><li>xml2rfc-ext-support-rfc2731 parameter <a href="#rfc.iref.x.25">3.3</a></li><li>xml2rfc-footer parameter <a href="#rfc.iref.x.6">3.1</a></li><li>xml2rfc-header parameter <a href="#rfc.iref.x.7">3.1</a></li><li>xml2rfc-inline parameter <a href="#rfc.iref.x.8">3.1</a></li><li>xml2rfc-iprnotified parameter <a href="#rfc.iref.x.9">3.1</a></li><li>xml2rfc-linkmailto parameter <a href="#rfc.iref.x.10">3.1</a></li><li>xml2rfc-private parameter <a href="#rfc.iref.x.11">3.1</a></li><li>xml2rfc-refparent parameter <a href="#rfc.iref.x.12">3.1</a></li><li>xml2rfc-rfcedstyle parameter <a href="#rfc.iref.x.13">3.1</a></li><li>xml2rfc-sortrefs parameter <a href="#rfc.iref.x.14">3.1</a></li><li>xml2rfc-symrefs parameter <a href="#rfc.iref.x.15">3.1</a></li><li>xml2rfc-toc parameter <a href="#rfc.iref.x.16">3.1</a></li><li>xml2rfc-tocdepth parameter <a href="#rfc.iref.x.17">3.1</a></li><li>xml2rfc-topblock parameter <a href="#rfc.iref.x.18">3.1</a></li><li><em>XSL-FO</em> <a href="#rfc.xref.XSL-FO.1">9.1</a>, <a href="#rfc.xref.XSL-FO.2">9.1</a>, <a href="#XSL-FO"><b>13</b></a></li><li>xsltproc <a href="#rfc.iref.x.28">5.1</a><ul><li>passing parameters <a href="#rfc.iref.x.1">3</a></li></ul></li></ul></li></ul></div></body></html>992 </pre><div class="note" id="rfc.section.C.2.p.3"> <p> <b>Note:</b> the name for the attribute sets may change in the future as more working is done with respect to customizability. In any case, overriding the settings in a separate file will be easier to maintain. Please contact the author if you find yourself trying to override style definitions that currently do not use attribute sets.</p> <p> <b>Note:</b> the CSS style information used in <samp>rfc2629.xslt</samp> can be overriden in a similar (but less granular) way: just overwrite the template called "insertCss". As for XSL-FO, the class names may change in future.</p> </div><hr class="noprint"><h1 id="rfc.section.D" class="np"><a href="#rfc.section.D">D.</a> <a id="boilerplate" href="#boilerplate">Producing the IETF 'Boilerplate'</a></h1><p id="rfc.section.D.p.1">Various attributes of the <samp><rfc></samp> element plus some child elements of <samp><front></samp> affect the automatically generated parts of the front page, such as the tabular information at the beginning, the "Status Of This Memo", and the "Copyright Notice".</p><p id="rfc.section.D.p.2">When submitting an Internet Draft, this "boilerplate" is checked by "Idnits" (<<a href="http://tools.ietf.org/tools/idnits/">http://tools.ietf.org/tools/idnits/</a>>) for compliance with the current Intellectual Property rules, and thus it is important to set the correct values.</p><p id="rfc.section.D.p.3">Furthermore, the RFC Production Center uses RFC2629-based tools to generate the final RFC text, so the more accurate the supplied information is, the less additional work is left, and the risk for errors in producing the final (and immutable!) document is reduced.</p><div class="note" id="rfc.section.D.p.4"> <p> <b>Note:</b> this only applies to the case when IETF documents are produced. The "private" processing instruction <span id="rfc.iref.p.64"></span><span id="rfc.iref.p.65"></span> allows to switch off most of the autogeneration logic.</p> </div><h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a> <a id="attribute-ipr" href="#attribute-ipr">The /rfc/@ipr Attribute</a></h2><p id="rfc.section.D.1.p.1">As of the time of this writing, this attribute value can take a long list of values. As frequently, this is not the result of a grand plan, but simply for historic reasons. Of these values, only a few are currently in use; all others are supported by the various tools for backwards compatibility with old source files.</p><div class="note" id="rfc.section.D.1.p.2"> <p> <b>Note:</b> some variations of the boilerplate are selected based on the document's date; therefore it is important to specify the "year", "month" and "day" attributes of the <samp><date></samp> element when archiving the XML source of an Internet Draft on the day of submission.</p> </div><p id="rfc.section.D.1.p.3"> <em>Disclaimer: THIS ONLY PROVIDES IMPLEMENTATION INFORMATION. IF YOU NEED LEGAL ADVICE, PLEASE CONTACT A LAWYER.</em> For further information, refer to <<a href="http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf">http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf</a>>.</p><p id="rfc.section.D.1.p.4">Finally, for the current "Status Of This Memo" text, the <samp>submissionType</samp> attribute determines whether a statement about "Code Components" is inserted (this is the case for the value "IETF", which also happens to be the default). Other values, such as "independent", suppress this part of the text.</p><h3 id="rfc.section.D.1.1"><a href="#rfc.section.D.1.1">D.1.1</a> <a id="attribute-ipr-current" href="#attribute-ipr-current">Current Values: '*trust200902'</a></h3><p id="rfc.section.D.1.1.p.1">The name for these values refers to the "TLP" ("IETF TRUST Legal Provisions Relating to IETF Documents"), on effect February 15, 2009 (see <<a href="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090215.pdf">http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090215.pdf</a>>). Updates to this document were published on September 12, 2009 (TLP 3.0, <<a href="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090912.pdf">http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090912.pdf</a>>) and on December 28, 2009 (TLP 4.0, <<a href="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20091228.pdf">http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20091228.pdf</a>>), modifying the license for code components. The actual text is located in Section 6 ("Text To Be Included in IETF Documents") of these documents.</p><p id="rfc.section.D.1.1.p.2">The tools will automatically produce the "right" text depending on the document's date information (see above):</p><div id="rfc.table.u.10"><table class="tt full left" cellpadding="3" cellspacing="0"><thead><tr><th>TLP</th><th>URI</th><th>starting with publication date</th></tr></thead><tbody><tr><td class="left">3.0</td><td class="left"><<a href="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090912.pdf">http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20090912.pdf</a>></td><td class="left">2009-11-01</td></tr><tr><td class="left">4.0</td><td class="left"><<a href="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20091228.pdf">http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy-20091228.pdf</a>></td><td class="left">2010-04-01</td></tr></tbody></table></div><h4 id="rfc.section.D.1.1.1"><a href="#rfc.section.D.1.1.1">D.1.1.1</a> <a id="attribute-ipr-trust200902" href="#attribute-ipr-trust200902">trust200902</a></h4><p id="rfc.section.D.1.1.1.p.1">This should be the default, unless one of the more specific '*trust200902' values is a better fit. It produces the text in Sections 6.a and 6.b of the TLP.</p><h4 id="rfc.section.D.1.1.2"><a href="#rfc.section.D.1.1.2">D.1.1.2</a> <a id="attribute-ipr-noModificationTrust200902" href="#attribute-ipr-noModificationTrust200902">noModificationTrust200902</a></h4><p id="rfc.section.D.1.1.2.p.1">This produces the additional text from Section 6.c.i of the TLP:</p><blockquote id="rfc.section.D.1.1.2.p.2"> <p>This document may not be modified, and derivative works of it may not be created, except to format it for publication as an RFC or to translate it into languages other than English.</p> </blockquote><h4 id="rfc.section.D.1.1.3"><a href="#rfc.section.D.1.1.3">D.1.1.3</a> <a id="attribute-ipr-noDerivativesTrust200902" href="#attribute-ipr-noDerivativesTrust200902">noDerivativesTrust200902</a></h4><p id="rfc.section.D.1.1.3.p.1">This produces the additional text from Section 6.c.ii of the TLP:</p><blockquote id="rfc.section.D.1.1.3.p.2"> <p>This document may not be modified, and derivative works of it may not be created, and it may not be published except as an Internet-Draft.</p> </blockquote><h4 id="rfc.section.D.1.1.4"><a href="#rfc.section.D.1.1.4">D.1.1.4</a> <a id="attribute-ipr-pre5378Trust200902" href="#attribute-ipr-pre5378Trust200902">pre5378Trust200902</a></h4><p id="rfc.section.D.1.1.4.p.1">This produces the additional text from Section 6.c.iii of the TLP, frequently called the "pre-5378 escape clause":</p><blockquote id="rfc.section.D.1.1.4.p.2"> <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.</p> </blockquote><p id="rfc.section.D.1.1.4.p.3">See Section 4 of <<a href="http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf">http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf</a>> for further information about when to use this value.</p><div class="note" id="rfc.section.D.1.1.4.p.4"> <p> <b>Note:</b> this text appears under "Copyright Notice", unless the document was published before November 2009, in which case it appears under "Status Of This Memo".</p> </div><h3 id="rfc.section.D.1.2"><a href="#rfc.section.D.1.2">D.1.2</a> <a id="attribute-ipr-historic" href="#attribute-ipr-historic">Historic Values</a></h3><h4 id="rfc.section.D.1.2.1"><a href="#rfc.section.D.1.2.1">D.1.2.1</a> <a id="attribute-ipr-200811" href="#attribute-ipr-200811">Historic Values: '*trust200811'</a></h4><p id="rfc.section.D.1.2.1.p.1">The attribute values "<span id="attribute-ipr-trust200811">trust200811</span>", "<span id="attribute-ipr-noModificationTrust200811">noModificationTrust200811</span>" and "<span id="attribute-ipr-noDerivativesTrust200811">noDerivativesTrust200811</span>" are similar to their "trust200902" counterparts, except that they use text specified in <<a href="http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy_11-10-08.pdf">http://trustee.ietf.org/license-info/archive/IETF-Trust-License-Policy_11-10-08.pdf</a>>.</p><h4 id="rfc.section.D.1.2.2"><a href="#rfc.section.D.1.2.2">D.1.2.2</a> <a id="attribute-ipr-3978" href="#attribute-ipr-3978">Historic Values: '*3978'</a></h4><p id="rfc.section.D.1.2.2.p.1">The attribute values "<span id="attribute-ipr-full3978">full3978</span>", "<span id="attribute-ipr-noModification3978">noModification3978</span>" and "<span id="attribute-ipr-noDerivatives3978">noDerivatives3978</span>" are similar to their counterparts above, except that they use text specified in RFC 3978 (March 2005).</p><h4 id="rfc.section.D.1.2.3"><a href="#rfc.section.D.1.2.3">D.1.2.3</a> <a id="attribute-ipr-3667" href="#attribute-ipr-3667">Historic Values: '*3667'</a></h4><p id="rfc.section.D.1.2.3.p.1">The attribute values "<span id="attribute-ipr-full3667">full3667</span>", "<span id="attribute-ipr-noModification3667">noModification3667</span>" and "<span id="attribute-ipr-noDerivatives3667">noDerivatives3667</span>" are similar to their counterparts above, except that they use text specified in RFC 3667 (February 2004).</p><h4 id="rfc.section.D.1.2.4"><a href="#rfc.section.D.1.2.4">D.1.2.4</a> <a id="attribute-ipr-2026" href="#attribute-ipr-2026">Historic Values: '*2026'</a></h4><p id="rfc.section.D.1.2.4.p.1">The attribute values "<span id="attribute-ipr-full2026">full2026</span>" and "<span id="attribute-ipr-noDerivativeWorks2026">noDerivativeWorks2026</span>" are similar to their counterparts above, except that they use text specified in RFC 2026 (October 1996).</p><p id="rfc.section.D.1.2.4.p.2">The special value "<span id="attribute-ipr-none">none</span>" was also used back then, and denied the IETF any rights beyond publication as Internet Draft.</p><h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a> <a id="attribute-category" href="#attribute-category">The /rfc/@category Attribute</a></h2><p id="rfc.section.D.2.p.1">For RFCs, the <samp>category</samp> determines the "maturity level" (see <a href="http://tools.ietf.org/html/rfc2026#section-4">Section 4</a> of <a href="#RFC2026" id="rfc.xref.RFC2026.2"><cite title="The Internet Standards Process -- Revision 3">[RFC2026]</cite></a>). The allowed values are "std" for "Standards Track", "bcp" for "BCP", "info" for "Informational", "exp" for "Experimental", and "historic" for - surprise - "Historic".</p><p id="rfc.section.D.2.p.2">For Internet Drafts, the category attribute is not needed, but <em>will</em> appear on the front page ("Intended Status"). Supplying this information can be useful, because reviewers may want to know.</p><div class="note" id="rfc.section.D.2.p.3"> <p> <b>Note:</b> the Standards Track consists of "Proposed Standard", "Draft Standards", and "Internet Standard". These do not appear in the boilerplate, thus the category attribute doesn't handle them. However, this information can be useful for validity checkers, and thus <samp>rfc2629.xslt</samp> supports an extension attribute for that purpose (see <a href="#ext-rfc2629.rfc" title="Extensions to Xml2rfc <rfc> element">Section 11.25</a> for details).</p> </div><h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a> <a id="attribute-submissiontype" href="#attribute-submissiontype">The /rfc/@submissionType Attribute</a></h2><p id="rfc.section.D.3.p.1">The RFC Editor publishes documents from different "document streams", of which the "IETF stream" of course is the most prominent one. Other streams are the "independent stream" (used for things like administrative information or April 1st RFCs), the "IAB stream" (Internet Architecture Board) and the "IRTF stream" (Internet Research Task Force).</p><p id="rfc.section.D.3.p.2">Not surprisingly, the values for the attribute are "IETF" (the default value), "independent", "IAB", and "IRTF".</p><p id="rfc.section.D.3.p.3"> <em>The values "IAB" and "IRTF" are supported by rfc2629.xslt, but not yet allowed by the DTD (waiting for release 1.36 of xml2rfc).</em> </p><p id="rfc.section.D.3.p.4">Historically, this did not affect the final appearance of RFCs, except for subtle differences in Copyright notices. Nowadays (as of <a href="#RFC5741" id="rfc.xref.RFC5741.1"><cite title="RFC Streams, Headers, and Boilerplates">[RFC5741]</cite></a>), the stream name appears in the first line of the front page, and it also affects the text in the "Status Of This Memo" section.</p><p id="rfc.section.D.3.p.5">For current documents, setting <samp>submissionType</samp> attribute will have the following effect: </p><ul><li>For RFCs, the stream name appears in the upper left corner of the first page (in Internet Drafts, this is either "Network Working Group", or the value of the <samp><workgroup></samp> element).</li><li>For RFCs, if affects the whole "Status Of This Memo" section (see <a href="http://tools.ietf.org/html/rfc5741#section-3.2.2">Section 3.2.2</a> of <a href="#RFC5741" id="rfc.xref.RFC5741.2"><cite title="RFC Streams, Headers, and Boilerplates">[RFC5741]</cite></a>).</li><li>For all RFCs and Internet Drafts, it determines whether the "Copyright Notice" mentions the Copyright on Code Components (see TLP, Section "Text To Be Included in IETF Documents").</li></ul><div class="note" id="rfc.section.D.3.p.6"> <p> <b>Note:</b> as of Version 1.35, <samp>xml2rfc</samp> (as opposed to <samp>rfc2629.xslt</samp>) does <em>not</em> implement support values other than "IETF" or "independent".</p> </div><h2 id="rfc.section.D.4"><a href="#rfc.section.D.4">D.4</a> <a id="attribute-consensus" href="#attribute-consensus">The /rfc/@consensus Attribute</a></h2><p id="rfc.section.D.4.p.1"> <em>Supported by rfc2629.xslt, but not yet allowed by the DTD (waiting for release 1.36 of xml2rfc).</em> </p><p id="rfc.section.D.4.p.2">For some of the publication streams (see <a href="#attribute-submissiontype" title="The /rfc/@submissionType Attribute">Appendix D.3</a>), the "Status Of This Memo" section depends on whether there was a consensus to publish (again, see <a href="http://tools.ietf.org/html/rfc5741#section-3.2.2">Section 3.2.2</a> of <a href="#RFC5741" id="rfc.xref.RFC5741.3"><cite title="RFC Streams, Headers, and Boilerplates">[RFC5741]</cite></a>).</p><p id="rfc.section.D.4.p.3">The <samp>consensus</samp> attribute ("yes"/"no", defaulting to "yes") can be used to supply this information. The effect for the various streams is: </p><ul><li>"independent" and "IAB": none.</li><li>"IETF": mention that there was an IETF consensus.</li><li>"IRTF": mention that there was a research group consensus (where the name of the research group is extracted from the <samp><workgroup></samp> element).</li></ul><h2 id="rfc.section.D.5"><a href="#rfc.section.D.5">D.5</a> <a id="attribute-number" href="#attribute-number">The /rfc/@number Attribute</a></h2><p id="rfc.section.D.5.p.1">For RFCs, this attribute supplies the RFC number.</p><h2 id="rfc.section.D.6"><a href="#rfc.section.D.6">D.6</a> <a id="attribute-docname" href="#attribute-docname">The /rfc/@docName Attribute</a></h2><p id="rfc.section.D.6.p.1">For Internet Drafts, this specifies the draft name (which appears below the title). The file extension is <em>not</em> part of the draft, so in general it should end with the current draft number ("-", plus two digits).</p><div class="note" id="rfc.section.D.6.p.2"> <p> <b>Note:</b> "Idnits" (<<a href="http://tools.ietf.org/tools/idnits/">http://tools.ietf.org/tools/idnits/</a>>) checks the in-document draft name for consistency with the filename of the submitted document.</p> </div><h2 id="rfc.section.D.7"><a href="#rfc.section.D.7">D.7</a> <a id="attribute-obsoletes" href="#attribute-obsoletes">The /rfc/@obsoletes Attribute</a></h2><p id="rfc.section.D.7.p.1">The RFC Editor maintains a database (<<a href="http://www.rfc-editor.org/rfc.html">http://www.rfc-editor.org/rfc.html</a>>) of all RFCs, including information about which one obsoletes which. Upon publication of an RFC, this database is updated from the data on the front page.</p><p id="rfc.section.D.7.p.2">This attribute takes a list of comma-separated RFC <em>numbers</em>. Do <em>not</em> put the string "RFC" here.</p><h2 id="rfc.section.D.8"><a href="#rfc.section.D.8">D.8</a> <a id="attribute-updates" href="#attribute-updates">The /rfc/@updates Attribute</a></h2><p id="rfc.section.D.8.p.1">This is like <samp>obsoletes</samp>, but for the "updates" relation.</p><hr class="noprint"><h1 id="rfc.section.E" class="np"><a href="#rfc.section.E">E.</a> <a id="license" href="#license">License</a></h1><p id="rfc.section.E.p.1">Copyright (c) 2006-2010, Julian Reschke (julian.reschke@greenbytes.de)</p><p id="rfc.section.E.p.2">All rights reserved.</p><p id="rfc.section.E.p.3">Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: </p><ul><li>Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.</li><li>Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.</li><li>Neither the name of Julian Reschke nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.</li></ul><p id="rfc.section.E.p.4">THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.</p><hr class="noprint"><h1 id="rfc.section.F" class="np"><a href="#rfc.section.F">F.</a> Change Logs</h1><h2 id="rfc.section.F.1"><a href="#rfc.section.F.1">F.1</a> Package</h2><dl><dt>2006-01-01</dt><dd>Switch to BSD License.</dd><dt>2007-01-12</dt><dd>Update to xml2rfc v1.33pre2.</dd><dt>2007-03-31</dt><dd>Update to xml2rfc v1.33pre3.</dd><dt>2007-05-01</dt><dd>Add XSLT test cases.</dd><dt>2008-07-18</dt><dd>Experimental support for inlined rdf:Description elements (ignored by the formatter, extracted by rfc2629grddl).</dd><dt>2008-12-04</dt><dd>Update to xml2rfc v1.34pre2.</dd><dt>2009-02-24</dt><dd>Experimental support for February 2009 boilerplate changes, and for the x:boilerplate element.</dd><dt>2009-07-08</dt><dd>Support new boilerplate ordering in RFCs published since July 2009. Fix problems with one-column text tables.</dd><dt>2009-07-19</dt><dd>When possible, calculate the actual Expiry date for Internet Drafts (full date must be available).</dd><dt>2009-08-01</dt><dd>For '$xml2rfc-ext-authors-section='end'", move the index in front of the authors section.</dd><dt>2009-08-04</dt><dd>Consider /rfc/@ipr="pre5378Trust200902" when producing RFCs, not IDs.</dd><dt>2009-08-29</dt><dd>Support alignment for artwork containing images (as opposed to, well, artwork).</dd><dt>2009-09-01</dt><dd>Allow xref in cref (as extension).</dd><dt>2009-09-14</dt><dd>Refactor handling of processing instructions.</dd><dt>2009-09-24</dt><dd>Fix typo in Status Of This Memo, present since November 2008. Fix formatting of iprExtract attribute. Starting with Internet Draft publication dates after 2009-11-30: use new Trust Legal Provisions text; for Internet Drafts: move Abstract up, and move "pre5378" escape clause to the Copyright Notice. Add support for refparent PI. For RFCs: use new TLP text as of September 2009. Incorporate xml2rfc v1.34pre4.</dd><dt>2009-10-06</dt><dd>Starting with Internet Draft publication dates after 2009-10-31: use new Trust Legal Provisions text; for Internet Drafts: move Abstract up, and move "pre5378" escape clause to the Copyright Notice. Incorporate xml2rfc v1.34pre5.</dd><dt>2009-10-27</dt><dd>Upgrade to xml2rfc v1.34.</dd><dt>2010-01-08</dt><dd>For RFC generation (not IDs), experimentally support RFC 5741 headers and boilerplate and Trust Legal Provisions 4.0.</dd><dt>2010-03-31</dt><dd>Upgrade to xml2rfc v1.35.</dd><dt>2010-06-27</dt><dd>Be consistent with xml2rfc.tcl in formatting initials (truncate after the first); see <<a href="http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/10">http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/10</a>>.</dd><dt>2010-08-31</dt><dd>Experimental support for prose in references.</dd><dt>2011-01-27</dt><dd>Update to xml2rfc v1.36pre1.</dd></dl><h2 id="rfc.section.F.2"><a href="#rfc.section.F.2">F.2</a> amazon-asin.xslt</h2><dl><dt>2003-11-16</dt><dd>Initial release.</dd><dt>2005-04-02</dt><dd>Fix two DTD issues.</dd></dl><h2 id="rfc.section.F.3"><a href="#rfc.section.F.3">F.3</a> check-references.xslt</h2><dl><dt>2003-11-16</dt><dd>Initial release.</dd><dt>2004-05-11</dt><dd>Add document status; print references type.</dd><dt>2005-01-01</dt><dd>Add experimental check for ID status.</dd><dt>2005-04-01</dt><dd>Add fixes from Bill Fenner.</dd><dt>2005-12-03</dt><dd>Add checks against local copy of <<a href="http://www.w3.org/2002/01/tr-automation/tr.rdf">http://www.w3.org/2002/01/tr-automation/tr.rdf</a>>.</dd><dt>2006-07-22</dt><dd>Add checks for standards levels.</dd><dt>2006-08-06</dt><dd>"check-ietf-references.xslt" replaced by "check-references.xslt".</dd><dt>2007-01-04</dt><dd>Use information online at <<a href="http://tools.ietf.org/">http://tools.ietf.org/</a>> to retrieve Internet-Draft status information.</dd><dt>2007-06-16</dt><dd>Fix bug looking up ref type when inside change markup.</dd><dt>2008-06-14</dt><dd>Enhance output when draft was updated, and then published as RFC.</dd><dt>2008-07-12</dt><dd>Add XSLT2-based link target checking.</dd><dt>2008-08-10</dt><dd>Change keywords for "intended-level" to proposed/draft/internet, optionally extract intended level from /rfc/@x:maturity-level attribute.</dd></dl><h2 id="rfc.section.F.4"><a href="#rfc.section.F.4">F.4</a> gen-reference-graph.xslt</h2><dl><dt>2006-09-03</dt><dd>New.</dd><dt>2007-06-07</dt><dd>Use <a href="http://dpcarlisle.blogspot.com/2007/05/exslt-node-set-function.html">Carlisle method</a> to define exslt:node-set in msxsml (which means that the stylesheet can now be used with MSXML as well).</dd><dt>2007-10-15</dt><dd>Use W3C data from tr.rdf as well (experimental).</dd></dl><h2 id="rfc.section.F.5"><a href="#rfc.section.F.5">F.5</a> rfc2629.xslt</h2><dl><dt>2001-03-28</dt><dd>Code rearranged, generate numbered section anchors for paragraphs (t) as well. Fixes in index handling.</dd><dt>2001-04-12</dt><dd>Moved HTML output into XHTML namespace.</dd><dt>2001-10-02</dt><dd>Fixed default location for RFCs and numbering of section references. Support ?rfc editing processing instruction.</dd><dt>2001-10-07</dt><dd>Made telephone number links active.</dd><dt>2001-10-08</dt><dd>Support for vspace element.</dd><dt>2001-10-09</dt><dd>Experimental support for rfc-issue PI.</dd><dt>2001-11-11</dt><dd>Support rfc private PI. Removed bogus code reporting the WG in the header.</dd><dt>2001-11-11</dt><dd>Support rfc private PI. Removed bogus code reporting the WG in the header.</dd><dt>2001-12-17</dt><dd>Support title attribute on references element</dd><dt>2002-01-05</dt><dd>Support for list/@style="@format"</dd><dt>2002-01-09</dt><dd>Display "closed" RFC issues as deleted</dd><dt>2002-01-14</dt><dd>Experimentally and optionally parse XML encountered in artwork elements (requires MSXSL).</dd><dt>2002-01-27</dt><dd>Some cleanup. Moved RFC issues from PIs into namespaced elements.</dd><dt>2002-01-29</dt><dd>Added support for sortrefs PI. Added support for figure names.</dd><dt>2002-02-07</dt><dd>Highlight parts of artwork which are too wide (72 characters).</dd><dt>2002-02-12</dt><dd>Code rearrangement for static texts. Fixes for section numbering. TOC generation rewritten.</dd><dt>2002-02-15</dt><dd>Support for irefs in sections; support iref @primary=true</dd><dt>2002-03-03</dt><dd>Moved anchor prefix into a constant. Added sanity checks on user anchor names.</dd><dt>2002-03-23</dt><dd>Bugfix in detection of matching org names when creating the header. Fixed sorting in subitems.</dd><dt>2002-04-02</dt><dd>Fix TOC link HTML generation when no TOC is generated (created broken HTML table code).</dd><dt>2002-04-03</dt><dd>Made rendering of references more tolerant re: missing parts.</dd><dt>2002-04-08</dt><dd>Fixed reference numbering when references are split into separate sections.</dd><dt>2002-04-16</dt><dd>Fix default namespace (shouldn't be set for HTML output method).</dd><dt>2002-04-19</dt><dd>Lowercase internal CSS selectors for Mozilla compliance. Do not put TOC into ul element.</dd><dt>2002-04-21</dt><dd>Make numbered list inside numbered lists use alphanumeric numbering.</dd><dt>2002-05-05</dt><dd>Updated issue/editing support.</dd><dt>2002-05-15</dt><dd>Bugfix for section numbering after introduction of ed:replace</dd><dt>2002-06-21</dt><dd>When producing private documents, do not include document status, copyright etc.</dd><dt>2002-07-08</dt><dd>Fix xrefs to Appendices.</dd><dt>2002-07-19</dt><dd>Make artwork lightyellow for easier reading. (fielding)</dd><dt>2002-10-09</dt><dd>Translate references title to anchor name to avoid non-uri characters. (fielding)</dd><dt>2002-10-13</dt><dd>Support for tocdepth PI.</dd><dt>2002-11-03</dt><dd>Added temporariry workaround for Mozilla/Transformiix result tree fragment problem. (search for 'http://bugzilla.mozilla.org/show_bug.cgi?id=143668')</dd><dt>2002-12-25</dt><dd>xref code: attempt to uppercase "section" and "appendix" when at the start of a sentence.</dd><dt>2003-02-02</dt><dd>fixed code for vspace blankLines="0", enhanced display for list with "format" style, got rid of HTML blockquote elements, added support for "hangIndent"</dd><dt>2003-04-10</dt><dd>experimental support for appendix and spanx elements</dd><dt>2003-04-19</dt><dd>fixed counting of list numbers in "format %" styles (one counter per unique format string). Added more spanx styles.</dd><dt>2003-05-02</dt><dd>experimental texttable support</dd><dt>2003-05-02</dt><dd>Make mailto links optional (default = none) (jre: default and PI name changed) (fielding)</dd><dt>2003-05-04</dt><dd>experimental support for HTML link elements; fix default for table header alignment default</dd><dt>2003-05-06</dt><dd>support for "background" PI.</dd><dt>2003-05-11</dt><dd>change %c format to lowercase alphabetic. add support for keyword elements (generate META tag). fix various HTML conformance problems. added experimental support for role attribute. do not number paragraphs in unnumbered sections. update boilerplate texts. support for "iprnotified" PI. bugfix list numbering. strip whitespace when building tel: URIs.</dd><dt>2003-05-12</dt><dd>more conformance fixes (layout moved into CSS, move lists and figures out of para content, do not use tables for list formatting)</dd><dt>2003-05-13</dt><dd>add DC.Creator meta tag, refactoring</dd><dt>2003-05-16</dt><dd>put nbsps between "section" and section number (xref).</dd><dt>2003-05-18</dt><dd>author summary: add missing comma.</dd><dt>2003-06-06</dt><dd>fix index generation bug (transposed characters in key generation). Enhance sentence start detection (xref starting a section was using lowercase "section").</dd><dt>2003-06-22</dt><dd>exp. support for xref/@format. Add missing support for eref w/o content. exp. support for annotations in reference elements. Code cleanup reference table formatting.</dd><dt>2003-07-09</dt><dd>Another fix for DC.Creator meta tag creation based on RFC2731</dd><dt>2003-07-24</dt><dd>Fix namespace name for DC.Creator.</dd><dt>2003-08-06</dt><dd>Cleanup node-set support (only use exslt (saxon, xalan, libxslt) extension functions; remove Transformix workarounds that stopped to work in Moz 1.4)</dd><dt>2003-08-09</dt><dd>Generate HTML lang tag.</dd><dt>2003-08-10</dt><dd>Map spanx/verb to HTML "samp" element. Fix author name display in references (reverse surname/initials for last author), add "Ed.". Fix internal bookmark generation.</dd><dt>2003-08-17</dt><dd>Add DCMI dates, identifiers and abstract. Add PI to suppress DCMI generation. Do not add TOC entry to Copyright Statement when there is none. Align RFC2629 PI names and parameter names. Change style for inline URIs generated by eref. Add header and footer support. Enhance CSS paging properties. Support topblock PI. Added hooks for proper XHTML generation through separate XSLT. Enhance warning and error messages. Add support for artwork image display. Table formatting fixes (borders, thead continuation).</dd><dt>2003-08-18</dt><dd>Add workaround for MSXML4 node-set and Mozilla node-set issues (fallback just displays are warning).</dd><dt>2003-10-06</dt><dd>Add workaround for broken pre/ins handling in Mozilla (see <<a href="http://bugzilla.mozilla.org/show_bug.cgi?id=204401">http://bugzilla.mozilla.org/show_bug.cgi?id=204401</a>>). Make use of cite attribute on ed:replace. CSS cleanup.</dd><dt>2003-10-08</dt><dd>Fix minor issue detecting the same org for the header (caused by IE's non-standard whitespace handling). Fix default handling for /rfc/@category.</dd><dt>2003-11-09</dt><dd>Inherit ed:entered-by from ancestor elements. Change CSS color for inserted text to green. Generate issues-list anchor. Do not complain about missing targets when the xref element is below ed:del. Remove code that attempted to distinguish section/Section when producing links - always use uppercase. Fix date rendering for issue resolutions.</dd><dt>2003-11-29</dt><dd>Fix color values for table backgrounds for issue rendering. Change rendering of issue links to use inline-styles. Add colored issue markers to issues.</dd><dt>2003-12-13</dt><dd>Fix inheritance of ed:entered-by attribute. Display note elements inside change tracking as well.</dd><dt>2004-01-18</dt><dd>When PI compact = 'yes', make most CSS print page breaks conditional.</dd><dt>2004-02-20</dt><dd>Support for RFC3667 IPR changes (xml2rfc 1.22); see <<a href="http://lists.xml.resource.org/pipermail/xml2rfc/2004-February/001088.html">http://lists.xml.resource.org/pipermail/xml2rfc/2004-February/001088.html</a>>.</dd><dt>2004-03-11</dt><dd>Add "(if approved)" to "updates" and "obsoletes" unless the document has an RFC number.</dd><dt>2004-04-01</dt><dd>Fix RFC3667 output, see <<a href="http://lists.xml.resource.org/pipermail/xml2rfc/2004-April/001208.html">http://lists.xml.resource.org/pipermail/xml2rfc/2004-April/001208.html</a>>.</dd><dt>2004-04-04</dt><dd>Add support for section/top attribute. Move references into plain section container.</dd><dt>2004-04-06</dt><dd>Do not emit identical para anchors for deleted content.</dd><dt>2004-04-14</dt><dd>Fix references TOC generation when there are no references.</dd><dt>2004-04-24</dt><dd>Fix RFC3667 output, see <<a href="http://xml.resource.org/pipermail/xml2rfc/2004-April/001246.html">http://xml.resource.org/pipermail/xml2rfc/2004-April/001246.html</a>>.</dd><dt>2004-05-09</dt><dd>Add custom support for generating compound index documents. Add anchors for each Index letter. Add experimental cref support. Fix conditional page breaks before References section.</dd><dt>2004-05-16</dt><dd>Refactor external index generation.</dd><dt>2004-05-20</dt><dd>Rewrite anchor generation for comments.</dd><dt>2004-05-22</dt><dd>Enhance issues rendering (add links to changes).</dd><dt>2004-05-30</dt><dd>Allow single quote as delimiter in processing instructions as well. Move block-level issue pointers to floats. Disable issue pointers for print media. Add "purple numbers". Add hrefs to section headings. Add non-printing index key letter list to start of index.</dd><dt>2004-06-01</dt><dd>Use &#xb6; instead of # for PNs.</dd><dt>2004-07-18</dt><dd>Add support for list style=letters (thanks Roy F.). Make PNs optional; add new PI.</dd><dt>2004-09-05</dt><dd>Fix index links into unnumbered sections. Bring IPR boilerplate in-line with xml2rfc 1.25. Add experimental CSS3 paged media support. Various HTML fixes.</dd><dt>2004-09-21</dt><dd>Enhance checking of artwork width.</dd><dt>2004-09-26</dt><dd>Add check for unused references. Uppercase letters in list style letters when nested into another list.</dd><dt>2004-10-10</dt><dd>Fix internal change track pointers.</dd><dt>2004-11-01</dt><dd>Allow change tracking on references (as a whole). Rewrite artwork handling so that it allows change tracking inside artwork. Also allow a subset of text markup inside artwork, such as xrefs (note this requires post-processing the source to make it compliant to RFC2629bis).</dd><dt>2004-11-03</dt><dd>Enhanced placement of iref anchors.</dd><dt>2004-11-06</dt><dd>Index: display irefs that appeared (with primary=true) inside artwork elements in a monospaced font.</dd><dt>2004-11-14</dt><dd>Add special code so that changes in section titles can be change-tracked.</dd><dt>2005-01-14</dt><dd>Bugfixes for HtmlToXhtml converter.</dd><dt>2005-01-22</dt><dd>Enhance generation of HTML h* elements (for Mozilla Outliner).</dd><dt>2005-01-31</dt><dd>Put vertical space around top-level TOC entries in TOC. Switch to pt-based CSS. Re-arrange top section. Make hr elements reflect new-page settings in TXT output (compact-PI). Fix page number in footer (CSS print) and add some more experimental support for paged media (tested with Prince 4.1 alpha). Rewrite TOC and Index generation to generate HTML lists. Cleanup id generation for paragraphs. Reduce whitespace in output. Fix vspace implementation. Use right/left dqoutes and copyright sign where appropriate.</dd><dt>2005-02-04</dt><dd>Add <link> element to references section. Fix newly introduced bug in references processing.</dd><dt>2005-02-05</dt><dd>Integrate various fixes/enhancements by Roy Fielding: spelling of "Authors' Addresses", comma setting in references, position of "Authors" section, optionally place authors addresses at end (PI), trailing dots in section numbers, switch to verdana default font in CSS. Add experimental support for centered artwork.</dd><dt>2005-02-09</dt><dd>Fixes in spacing and links of references section titles. Enhance sorting in references when change tracking is in place. Re-add figure centering support. Add missing 2nd part of "Author's Adresses" fix.</dd><dt>2005-02-25</dt><dd>Align section number format with xml2rfc1.29.</dd><dt>2005-03-28</dt><dd>Get rid of table elements in Author's section. Add experimental hCard (<<a href="http://developers.technorati.com/wiki/hCard">http://developers.technorati.com/wiki/hCard</a>>) support.</dd><dt>2005-04-03</dt><dd>Add RFC3978-style IPR statement support. (fenner@research.att.com)</dd><dt>2005-04-11</dt><dd>Cleanup author display. hCard related fixes.</dd><dt>2005-05-07</dt><dd>Minor fixes to allow change tracking in doc title. Add experimental support for table border styles. CSS cleanup.</dd><dt>2005-06-18</dt><dd>Implement missing support for references to texttables.</dd><dt>2005-09-25</dt><dd>Use (-moz-)column-count when printing the index.</dd><dt>2005-10-04</dt><dd>Report missing element templates with xsl:message.</dd><dt>2005-10-15</dt><dd>Process t/@anchor.</dd><dt>2005-10-23</dt><dd>More workarounds for Mozilla's broken del/ins handling (this time for figures).</dd><dt>2005-10-27</dt><dd>lowercase hCard class names</dd><dt>2005-11-22</dt><dd>Enhance diagnostics for XML-in-artwork extension</dd><dt>2005-11-26</dt><dd>Fix formatting of section numbers for sections inserted into <back>.</dd><dt>2005-12-12</dt><dd>Fix some validity problems when change tracking occured inside lists.</dd><dt>2005-12-18</dt><dd>Add change tracking inside the index.</dd><dt>2006-02-04</dt><dd>Add prev/next links to highlighted changes (change tracking extension).</dd><dt>2006-02-10</dt><dd>Catch errors instantiating MSXML component.</dd><dt>2006-02-11</dt><dd>References: add "work in progress" for Internet Drafts.</dd><dt>2006-02-27</dt><dd>Fix front matter (lowercase Internet-Draft, say "Intended status" for non-RFC documents). Start work on experimental extension for simplified internal links.</dd><dt>2006-03-19</dt><dd>Tweaks to IESG Copyright stuff; support submissionType attribute. Fix duplicate reference anchors in HTML output. Reduce HTML Tidy warnings. Fix reference to normative ASCII version (now requires trailing ".txt"). Tweaks to hCard generation. Started to move non-issue-tracking extensions into namespace "http://purl.org/net/xml2rfc/ext".</dd><dt>2006-03-27</dt><dd>Moved "simple reference" extension into namespace "http://purl.org/net/xml2rfc/ext" and add documentation. HTML conformance enhancements.</dd><dt>2006-04-02</dt><dd>Cleanup special code for automated XHTML XSLT generation.</dd><dt>2006-04-21</dt><dd>Generate <CITE> elements where appropiate. Introduce x:blockquote, x:dfn, x:h and x:q elements.</dd><dt>2006-05-06</dt><dd>Introduce x:bcp14 element.</dd><dt>2006-05-14</dt><dd>Fix content model for x:blockquote.</dd><dt>2006-06-18</dt><dd>Add box drawing support (x:bt, x:bc, x:bb).</dd><dt>2006-06-20</dt><dd>HTML validity fixes (legal chars in anchors in index).</dd><dt>2006-06-24</dt><dd>Reduce leading empty lines in artwork. Move <dt> style info into CSS.</dd><dt>2006-07-14</dt><dd>Fix rendering of multiple street address entries (missing line break).</dd><dt>2006-07-24</dt><dd>Add extension for deep linking into RFCs, do not generate empty list items in TOC output, avoid empty <dt> elements for list items without hangText attribute.</dd><dt>2006-08-01</dt><dd>Allow @anchor on more elements; start work on Relax NG grammar for extensions. Reduce generated style elements (use CSS classes instead). Consistently use "id" instead of "name". Change default target for RFC links to "http://tools.ietf.org/html/rfcNNNN".</dd><dt>2006-08-06</dt><dd>Include appendices defined in <appendix> elements in TOC (please consider them deprecated anyhow!). Generate links to "http://tools.ietf.org/html/draft-*" for Internet Drafts. Replace x:frag by x:rel, allowing any kind of relative reference instead of just fragments.</dd><dt>2006-08-30</dt><dd>Reduce textual differences between HTML output and what xml2rfc produces in TXT output mode (section refs/reference targets). Add small workaround for Opera 9.0.1's problem with node-set().</dd><dt>2006-10-29</dt><dd>Fix problem generating internal links to change markup within references section. Enhancements when generating numbered references for deleted references. Allow inclusion of references into the index (through include-references-in-index extension). Fix a bug that caused the newer version of the IETF boilerplate to be produced rather than the pre-RFC3667 one. Update to RFC4287 boilerplate.</dd><dt>2006-11-11</dt><dd>Add extension attribute x:for-anchor to <iref> handling.</dd><dt>2006-11-26</dt><dd>Experimental (and limited) support for <x:lt>.</dd><dt>2006-12-04</dt><dd>Fix bugs in processing documents that have both the ipr and the number attribute set on the rfc root element. Add support for x:fmt='none' on xrefs. Add different pre style based on artwork type attributes (experimental).</dd><dt>2006-12-13</dt><dd>Add x:fmt='anchor' for xref elements.</dd><dt>2007-01-07</dt><dd>Fix root template for compatibility for the exslt:node-set implementation in Firefox3.</dd><dt>2007-01-29</dt><dd>Avoid empty table entry in front matter when organization is not specified for an author.</dd><dt>2007-02-10</dt><dd>Allow change tracking in table rows.</dd><dt>2007-03-09</dt><dd>Add hcard profile URI (<<a href="http://www.w3.org/2006/03/hcard">http://www.w3.org/2006/03/hcard</a>>) to head element. Add warning for misplaced <t> elements (after section).</dd><dt>2007-03-21</dt><dd>Fix internal linking from reference entries in index for some xref types. Minor CSS tweaks contributed by MTR. Allow turning on text justification through a PI. Improve iref anchor generation to generate less instable anchors.</dd><dt>2007-03-28</dt><dd>Fixes for numbering of ed:inserted references sections.</dd><dt>2007-05-04</dt><dd>Do not generate anchors for edits in deleted sections. Enhance HTML conformance.</dd><dt>2007-05-19</dt><dd>Enhance diagnostics when using Saxon (needs Saxon's "-l" command line parameter to keep line number information). Add warning when symref PI is missing (default will change in the future). Add support for overriding computed section numbers (when formatting historic documents).</dd><dt>2007-06-07</dt><dd>Change default for symrefs PI to "yes" (see change in xml2rfc 1.33pre4). Warn about docName attributes that appear to contain a file extension.</dd><dt>2007-06-26</dt><dd>Workaround author/@initials values without trailing dot, as in xml2rfc.tcl.</dd><dt>2007-07-14</dt><dd>Enhance index generation for references that use @x:sec attribute.</dd><dt>2007-09-09</dt><dd>Fix: sortrefs is a nop when symrefs=no.</dd><dt>2007-10-17</dt><dd>Work in progress: add support for referencing sections in sibling documents by anchor name.</dd><dt>2007-10-17</dt><dd>Work in progress (continued): support for referencing sections in sibling documents by anchor name.</dd><dt>2007-12-31</dt><dd>Emit warning when updating/obsoleting stuff that's not referenced.</dd><dt>2008-02-03</dt><dd>Support xml2rfc-1.33pre5's suppress-title attribute on texttable and figure.</dd><dt>2008-02-06</dt><dd>Extension: allow <eref> below <cref>.</dd><dt>2008-02-17</dt><dd>Extensions: add x:span and x:length-of.</dd><dt>2008-02-20</dt><dd>Add new RFC boilerplate (as changed in 2007-08).</dd><dt>2008-02-27</dt><dd>Improve diagnostics for artwork width problems; add defaulting of publication dates (requires XSLT processor supporting exslt:date, or msxml).</dd><dt>2008-02-29</dt><dd>Enhance CSS for link elements in the front header, update rules for generating "Acknowledgment" statement.</dd><dt>2008-03-01</dt><dd>Use line numbers in diagnostics in Saxon8/9 as well.</dd><dt>2008-03-02</dt><dd>Fix a bug in the logic choosing the boilerplate, resulting in obsolete text being inserted into IDs.</dd><dt>2008-04-01</dt><dd>Add support for superscript element.</dd><dt>2008-06-28</dt><dd>Add sanity checks for email addresses, allow multiple email elements.</dd><dt>2008-07-06</dt><dd>Add x:abnf-char-sequence.</dd><dt>2008-08-21</dt><dd>Add x:note.</dd><dt>2008-09-06</dt><dd>Add experimental support for SVG images.</dd><dt>2008-09-17</dt><dd>Add experimental support for x:author. Fix xref/@format=none.</dd><dt>2008-10-10</dt><dd>Fix a huge bug, causing text content after an XML comment to be ignored.</dd><dt>2009-02-24</dt><dd>Use table/caption when needed.</dd><dt>2009-03-07</dt><dd>Fix bug that caused text to disappear in the output in presence of processing instructions.</dd><dt>2009-03-12</dt><dd>Make inlined comments bookmarkable.</dd><dt>2009-04-09</dt><dd>Upgrade to DC-HTML from RFC 2731 (affects head/@profile).</dd><dt>2009-07-08</dt><dd>Remove table/@summary in output; the value getting inserted was just repeating stuff that appeared in the preamble.</dd><dt>2009-08-01</dt><dd>Implement table alignment (HTML output only for now).</dd><dt>2009-08-18</dt><dd>Replicate Dublin Core "abstract" metadata into meta/@name=description (search engines do use it).</dd><dt>2009-09-02</dt><dd>Fix default/left alignment of table columns, remove silly table summmary attributes.</dd><dt>2009-09-24</dt><dd>Support double-sided layout using CSS page:left/right selectors.</dd><dt>2009-11-27</dt><dd>Generate unordered lists instead of broken definition lists for list style empty.</dd></dl><h2 id="rfc.section.F.6"><a href="#rfc.section.F.6">F.6</a> rfc2629toFO.xslt</h2><dl><dt>2003-11-16</dt><dd>Initial release.</dd><dt>2003-11-29</dt><dd>Enhance handling of unknown list styles.</dd><dt>2004-04-04</dt><dd>Update reference section handling.</dd><dt>2004-04-17</dt><dd>Use XSL-WD-1.1-style fo:bookmark and index handling and add postprocessors for existing implementations. Unify PDF info generation by using XEP (postprocessors) will convert.</dd><dt>2004-04-20</dt><dd>Add experimental cref support.</dd><dt>2004-06-14</dt><dd>Set correct index-item defaults.</dd><dt>2004-07-18</dt><dd>Add list style=letters.</dd><dt>2004-09-03</dt><dd>Make URLs in text break where they are allowed to break by inserting zero-width spaces.</dd><dt>2004-09-26</dt><dd>Fix letter-style inside nested lists.</dd><dt>2004-10-31</dt><dd>Update handling of artwork.</dd><dt>2004-11-13</dt><dd>Fix handling of references inside ed:* markup. Fix whitespace handling in artwork.</dd><dt>2004-11-27</dt><dd>Irefs in artwork generate monospaced entries in index.</dd><dt>2005-01-31</dt><dd>Fix TOC generation that was broken after changes in main XSLT.</dd><dt>2005-02-05</dt><dd>Bring in sync with cosmetic changes in rfc2629.xslt.</dd><dt>2005-05-07</dt><dd>Minor fix for change tracking in document title. Support for table styles.</dd><dt>2005-06-18</dt><dd>Fix references to tables.</dd><dt>2005-10-15</dt><dd>Process t/@anchor.</dd><dt>2006-02-11</dt><dd>References: add "work in progress" for Internet Drafts.</dd><dt>2006-06-02</dt><dd>Use XSL 1.1 WD Feb 2006.</dd><dt>2007-03-21</dt><dd>Support optional text justification.</dd><dt>2007-05-19</dt><dd>Various improvements in spacing; also allow overriding the automatic list indentation via list/x:indent.</dd><dt>2009-04-08</dt><dd>Fix spacing in headers; add support for formatting for double-sided printing.</dd><dt>2009-08-01</dt><dd>Remove surplus empty pages when not generating double-sided output.</dd></dl><h2 id="rfc.section.F.7"><a href="#rfc.section.F.7">F.7</a> xsl11toAn.xslt</h2><dl><dt>2004-05-17</dt><dd>Initial release.</dd><dt>2006-06-02</dt><dd>Use XSL 1.1 WD Feb 2006.</dd></dl><h2 id="rfc.section.F.8"><a href="#rfc.section.F.8">F.8</a> xsl11toFop.xslt</h2><dl><dt>2010-08-25</dt><dd>Switch to Apache FOP 1.0.</dd><dt>2009-09-12</dt><dd>Support for FOP 0.20.5 and FOP 0.93 removed. Please use FOP 0.95.</dd><dt>2008-03-15</dt><dd>Add a workaround to the fo:inline workaround (sigh).</dd></dl><h2 id="rfc.section.F.9"><a href="#rfc.section.F.9">F.9</a> xsl11toXep.xslt</h2><dl><dt>2004-05-17</dt><dd>Initial release.</dd><dt>2004-09-04</dt><dd>Fix xep:index-item attributes.</dd><dt>2006-06-02</dt><dd>Use XSL 1.1 WD Feb 2006.</dd></dl><hr class="noprint"><h1 id="rfc.index" class="np"><a href="#rfc.index">Index</a></h1><p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.F">F</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.J">J</a> <a href="#rfc.index.K">K</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.Q">Q</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.X">X</a> </p><div class="print2col"><ul class="ind"><li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul><li>abnf-char-sequence Extension Element <a href="#rfc.iref.a.27"><b>11.1</b></a>, <a href="#rfc.iref.a.29">A</a></li><li>allow-markup-in-artwork PI pseudo-attribute <a href="#rfc.iref.a.1">3.3</a></li><li>alternate HTML LINK element <a href="#rfc.iref.a.22">6.2</a></li><li>anchor-alias Extension Element <a href="#rfc.iref.a.28"><b>11.2</b></a>, <a href="#rfc.iref.a.30">A</a></li><li>Anchors <ul><li>rfc.abstract <a href="#rfc.iref.a.3">4</a></li><li>rfc.authors <a href="#rfc.iref.a.4">4</a></li><li>rfc.copyright <a href="#rfc.iref.a.5">4</a></li><li>rfc.copyrightnotice <a href="#rfc.iref.a.6">4</a></li><li>rfc.figure.n <a href="#rfc.iref.a.7">4</a>, <a href="#rfc.iref.a.18">4</a></li><li>rfc.figure.u.n <a href="#rfc.iref.a.8">4</a>, <a href="#rfc.iref.a.19">4</a></li><li>rfc.index <a href="#rfc.iref.a.9">4</a></li><li>rfc.ipr <a href="#rfc.iref.a.10">4</a></li><li>rfc.iref.n <a href="#rfc.iref.a.11">4</a></li><li>rfc.note.n <a href="#rfc.iref.a.12">4</a></li><li>rfc.references <a href="#rfc.iref.a.13">4</a>, <a href="#rfc.iref.a.14">4</a></li><li>rfc.section.n <a href="#rfc.iref.a.15">4</a></li><li>rfc.section.n.p.m <a href="#rfc.iref.a.16">4</a></li><li>rfc.status <a href="#rfc.iref.a.17">4</a></li><li>rfc.toc <a href="#rfc.iref.a.20">4</a></li><li>rfc.xref.name.n <a href="#rfc.iref.a.21">4</a></li></ul></li><li>AntennaHouse XSL Formatter <a href="#rfc.iref.a.26">9.1</a></li><li>Apache FOP <a href="#rfc.iref.a.25">9.1</a></li><li>appendix HTML LINK element <a href="#rfc.iref.a.23">6.2</a></li><li>assign-section-number Extension Element <a href="#rfc.iref.a.31">A</a></li><li>author HTML LINK element <a href="#rfc.iref.a.24">6.2</a></li><li>authors-section PI pseudo-attribute <a href="#rfc.iref.a.2">3.3</a></li></ul></li><li><a id="rfc.index.B" href="#rfc.index.B"><b>B</b></a><ul><li>background PI pseudo-attribute <a href="#rfc.iref.b.1">3.1</a></li><li>bb Extension Element <a href="#rfc.iref.b.3"><b>11.4</b></a>, <a href="#rfc.iref.b.8">A</a></li><li>bc Extension Element <a href="#rfc.iref.b.4"><b>11.5</b></a>, <a href="#rfc.iref.b.9">A</a></li><li>bcp14 Extension Element <a href="#rfc.iref.b.2"><b>11.3</b></a>, <a href="#rfc.iref.b.10">A</a></li><li><em>BCP97</em> <a href="#rfc.xref.BCP97.1">12.1</a>, <a href="#BCP97"><b>13</b></a></li><li>blockquote Extension Element <a href="#rfc.iref.b.5"><b>11.6</b></a>, <a href="#rfc.iref.b.11">A</a></li><li>boilerplate Extension Element <a href="#rfc.iref.b.6"><b>11.7</b></a>, <a href="#rfc.iref.b.12">A</a></li><li>bt Extension Element <a href="#rfc.iref.b.7"><b>11.8</b></a>, <a href="#rfc.iref.b.13">A</a></li></ul></li><li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul><li>chapter HTML LINK element <a href="#rfc.iref.c.3">6.2</a></li><li>CHM format <a href="#rfc.iref.c.7">8</a></li><li>comments PI pseudo-attribute <a href="#rfc.iref.c.2">3.1</a></li><li>compact PI pseudo-attribute <a href="#rfc.iref.c.1">3.1</a></li><li>contents HTML LINK element <a href="#rfc.iref.c.4">6.2</a></li><li>copyright HTML LINK element <a href="#rfc.iref.c.5">6.2</a></li><li>Creator DCMI property <a href="#rfc.iref.c.6">6.4</a></li></ul></li><li><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul><li>Date.Issued DCMI property <a href="#rfc.iref.d.3">6.4</a></li><li><em>DC-HTML</em> <a href="#rfc.xref.DC-HTML.1">6.4</a>, <a href="#DC-HTML"><b>13</b></a></li><li>DCMI properties <ul><li>Creator <a href="#rfc.iref.d.2">6.4</a></li><li>Date.Issued <a href="#rfc.iref.d.4">6.4</a></li><li>Description.Abstract <a href="#rfc.iref.d.6">6.4</a></li><li>Identifier <a href="#rfc.iref.d.7">6.4</a></li><li>isPartOf <a href="#rfc.iref.d.8">6.4</a></li><li>Relation.Replaces <a href="#rfc.iref.d.9">6.4</a></li></ul></li><li>Description.Abstract DCMI property <a href="#rfc.iref.d.5">6.4</a></li><li>dfn Extension Element <a href="#rfc.iref.d.10"><b>11.9</b></a>, <a href="#rfc.iref.d.11">A</a></li><li>duplex PI pseudo-attribute <a href="#rfc.iref.d.1">3.3</a></li></ul></li><li><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul><li>editing PI pseudo-attribute <a href="#rfc.iref.e.1">3.1</a></li><li>Extension Elements <ul><li>abnf-char-sequence <a href="#rfc.iref.e.2"><b>11.1</b></a>, <a href="#rfc.iref.e.23">A</a></li><li>anchor-alias <a href="#rfc.iref.e.3"><b>11.2</b></a>, <a href="#rfc.iref.e.24">A</a></li><li>assign-section-number <a href="#rfc.iref.e.26">A</a></li><li>bb <a href="#rfc.iref.e.5"><b>11.4</b></a>, <a href="#rfc.iref.e.27">A</a></li><li>bc <a href="#rfc.iref.e.6"><b>11.5</b></a>, <a href="#rfc.iref.e.28">A</a></li><li>bcp14 <a href="#rfc.iref.e.4"><b>11.3</b></a>, <a href="#rfc.iref.e.29">A</a></li><li>blockquote <a href="#rfc.iref.e.7"><b>11.6</b></a>, <a href="#rfc.iref.e.30">A</a></li><li>boilerplate <a href="#rfc.iref.e.8"><b>11.7</b></a>, <a href="#rfc.iref.e.31">A</a></li><li>bt <a href="#rfc.iref.e.9"><b>11.8</b></a>, <a href="#rfc.iref.e.32">A</a></li><li>dfn <a href="#rfc.iref.e.10"><b>11.9</b></a>, <a href="#rfc.iref.e.33">A</a></li><li>h <a href="#rfc.iref.e.11"><b>11.10</b></a>, <a href="#rfc.iref.e.34">A</a></li><li>highlight <a href="#rfc.iref.e.12"><b>11.11</b></a>, <a href="#rfc.iref.e.35">A</a></li><li>include-author <a href="#rfc.iref.e.25">A</a></li><li>length-of <a href="#rfc.iref.e.13"><b>11.12</b></a>, <a href="#rfc.iref.e.36">A</a></li><li>link <a href="#rfc.iref.e.14"><b>11.13</b></a>, <a href="#rfc.iref.e.37">A</a></li><li>lt <a href="#rfc.iref.e.15"><b>11.14</b></a>, <a href="#rfc.iref.e.38">A</a></li><li>note <a href="#rfc.iref.e.16"><b>11.15</b></a>, <a href="#rfc.iref.e.39">A</a></li><li>parse-xml <a href="#rfc.iref.e.17"><b>11.16</b></a>, <a href="#rfc.iref.e.40">A</a></li><li>prose <a href="#rfc.iref.e.18"><b>11.17</b></a>, <a href="#rfc.iref.e.41">A</a></li><li>q <a href="#rfc.iref.e.19"><b>11.18</b></a>, <a href="#rfc.iref.e.42">A</a></li><li>rdf:Description <a href="#rfc.iref.e.48">A</a></li><li>ref <a href="#rfc.iref.e.20"><b>11.19</b></a>, <a href="#rfc.iref.e.43">A</a></li><li>source <a href="#rfc.iref.e.21"><b>11.20</b></a>, <a href="#rfc.iref.e.44">A</a></li><li>span <a href="#rfc.iref.e.46">A</a></li><li>sup <a href="#rfc.iref.e.22"><b>11.21</b></a>, <a href="#rfc.iref.e.45">A</a></li><li>x <a href="#rfc.iref.e.47">A</a></li></ul></li></ul></li><li><a id="rfc.index.F" href="#rfc.index.F"><b>F</b></a><ul><li>Firefox <ul><li>1.*/2.* <a href="#rfc.iref.f.3">5.2</a></li><li>3.* <a href="#rfc.iref.f.2">5.2</a></li></ul></li><li>footer PI pseudo-attribute <a href="#rfc.iref.f.1">3.1</a></li></ul></li><li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul><li>generator HTML META element <a href="#rfc.iref.g.2">6.3</a></li><li>Google Chrome <a href="#rfc.iref.g.1">5.2</a></li><li>Grammar <a href="#rfc.iref.g.3"><b>A</b></a></li></ul></li><li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul><li>h Extension Element <a href="#rfc.iref.h.12"><b>11.10</b></a>, <a href="#rfc.iref.h.14">A</a></li><li>header PI pseudo-attribute <a href="#rfc.iref.h.1">3.1</a></li><li>highlight Extension Element <a href="#rfc.iref.h.13"><b>11.11</b></a>, <a href="#rfc.iref.h.15">A</a></li><li><em>HTML</em> <a href="#rfc.xref.HTML.1">6.1</a>, <a href="#rfc.xref.HTML.2">11.6</a>, <a href="#rfc.xref.HTML.3">11.9</a>, <a href="#rfc.xref.HTML.4">11.18</a>, <a href="#rfc.xref.HTML.5">11.21</a>, <a href="#HTML"><b>13</b></a></li><li>HTML compliance <a href="#rfc.iref.h.2">6.1</a></li><li>HTML LINK elements <ul><li>alternate <a href="#rfc.iref.h.3">6.2</a></li><li>appendix <a href="#rfc.iref.h.4">6.2</a></li><li>author <a href="#rfc.iref.h.5">6.2</a></li><li>chapter <a href="#rfc.iref.h.6">6.2</a></li><li>contents <a href="#rfc.iref.h.7">6.2</a></li><li>copyright <a href="#rfc.iref.h.8">6.2</a></li><li>index <a href="#rfc.iref.h.9">6.2</a></li></ul></li><li>HTML META elements <ul><li>generator <a href="#rfc.iref.h.10">6.3</a></li><li>keywords <a href="#rfc.iref.h.11">6.3</a></li></ul></li></ul></li><li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul><li>Identifier DCMI property <a href="#rfc.iref.i.10">6.4</a></li><li>include PI pseudo-attribute <a href="#rfc.iref.i.3">3.2</a></li><li>include-author Extension Element <a href="#rfc.iref.i.12">A</a></li><li>include-references-in-index PI pseudo-attribute <a href="#rfc.iref.i.4">3.3</a></li><li>index HTML LINK element <a href="#rfc.iref.i.9">6.2</a></li><li>inline PI pseudo-attribute <a href="#rfc.iref.i.1">3.1</a></li><li>Internet Explorer 5.5 <a href="#rfc.iref.i.5">5.2</a></li><li>Internet Explorer 6 <a href="#rfc.iref.i.6">5.2</a></li><li>Internet Explorer 7 <a href="#rfc.iref.i.7">5.2</a></li><li>Internet Explorer 8 <a href="#rfc.iref.i.8">5.2</a></li><li>iprnotified PI pseudo-attribute <a href="#rfc.iref.i.2">3.1</a></li><li>isPartOf DCMI property <a href="#rfc.iref.i.11">6.4</a></li></ul></li><li><a id="rfc.index.J" href="#rfc.index.J"><b>J</b></a><ul><li>justification PI pseudo-attribute <a href="#rfc.iref.j.1">3.3</a></li></ul></li><li><a id="rfc.index.K" href="#rfc.index.K"><b>K</b></a><ul><li>keywords HTML META element <a href="#rfc.iref.k.1">6.3</a></li></ul></li><li><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul><li>length-of Extension Element <a href="#rfc.iref.l.2"><b>11.12</b></a>, <a href="#rfc.iref.l.5">A</a></li><li>link Extension Element <a href="#rfc.iref.l.3"><b>11.13</b></a>, <a href="#rfc.iref.l.6">A</a></li><li>linkmailto PI pseudo-attribute <a href="#rfc.iref.l.1">3.1</a></li><li>lt Extension Element <a href="#rfc.iref.l.4"><b>11.14</b></a>, <a href="#rfc.iref.l.7">A</a></li></ul></li><li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul><li>Microsoft Help <a href="#rfc.iref.m.5">8</a></li><li>Mozilla <a href="#rfc.iref.m.3">5.2</a>, <a href="#rfc.iref.m.4">5.2</a></li><li>MSXML3 <a href="#rfc.iref.m.1">5.1</a></li><li>MSXML4 <a href="#rfc.iref.m.2">5.1</a></li></ul></li><li><a id="rfc.index.N" href="#rfc.index.N"><b>N</b></a><ul><li>needLines PI pseudo-attribute <a href="#rfc.iref.n.1">3.2</a></li><li>NoScript <a href="#rfc.iref.n.2">5.2</a></li><li>note Extension Element <a href="#rfc.iref.n.3"><b>11.15</b></a>, <a href="#rfc.iref.n.4">A</a></li></ul></li><li><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul><li>Opera <a href="#rfc.iref.o.1">5.2</a>, <a href="#rfc.iref.o.2">5.2</a></li></ul></li><li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul><li>Parameters <ul><li>xml2rfc-background <a href="#rfc.iref.p.2">3.1</a></li><li>xml2rfc-comments <a href="#rfc.iref.p.6">3.1</a></li><li>xml2rfc-compact <a href="#rfc.iref.p.4">3.1</a></li><li>xml2rfc-editing <a href="#rfc.iref.p.8">3.1</a></li><li>xml2rfc-ext-allow-markup-in-artwork <a href="#rfc.iref.p.44">3.3</a></li><li>xml2rfc-ext-authors-section <a href="#rfc.iref.p.46">3.3</a></li><li>xml2rfc-ext-duplex <a href="#rfc.iref.p.48">3.3</a></li><li>xml2rfc-ext-include-references-in-index <a href="#rfc.iref.p.50">3.3</a></li><li>xml2rfc-ext-justification <a href="#rfc.iref.p.52">3.3</a></li><li>xml2rfc-ext-parse-xml-in-artwork <a href="#rfc.iref.p.55">3.3</a></li><li>xml2rfc-ext-sec-no-trailing-dots <a href="#rfc.iref.p.59">3.3</a></li><li>xml2rfc-ext-support-rfc2731 <a href="#rfc.iref.p.57">3.3</a></li><li>xml2rfc-footer <a href="#rfc.iref.p.10">3.1</a></li><li>xml2rfc-header <a href="#rfc.iref.p.12">3.1</a></li><li>xml2rfc-inline <a href="#rfc.iref.p.14">3.1</a></li><li>xml2rfc-iprnotified <a href="#rfc.iref.p.16">3.1</a></li><li>xml2rfc-linkmailto <a href="#rfc.iref.p.18">3.1</a></li><li>xml2rfc-private <a href="#rfc.iref.p.21">3.1</a></li><li>xml2rfc-refparent <a href="#rfc.iref.p.23">3.1</a></li><li>xml2rfc-rfcedstyle <a href="#rfc.iref.p.25">3.1</a></li><li>xml2rfc-sortrefs <a href="#rfc.iref.p.27">3.1</a></li><li>xml2rfc-symrefs <a href="#rfc.iref.p.29">3.1</a></li><li>xml2rfc-toc <a href="#rfc.iref.p.31">3.1</a></li><li>xml2rfc-tocdepth <a href="#rfc.iref.p.33">3.1</a></li><li>xml2rfc-topblock <a href="#rfc.iref.p.35">3.1</a></li></ul></li><li>parse-xml Extension Element <a href="#rfc.iref.p.60"><b>11.16</b></a>, <a href="#rfc.iref.p.62">A</a></li><li>parse-xml-in-artwork PI pseudo-attribute <a href="#rfc.iref.p.53">3.3</a></li><li>private PI pseudo-attribute <a href="#rfc.iref.p.19">3.1</a>, <a href="#rfc.iref.p.64">D</a></li><li>Processing Instruction pseudo attributes <ul><li>allow-markup-in-artwork <a href="#rfc.iref.p.43">3.3</a></li><li>authors-section <a href="#rfc.iref.p.45">3.3</a></li><li>background <a href="#rfc.iref.p.1">3.1</a></li><li>comments <a href="#rfc.iref.p.5">3.1</a></li><li>compact <a href="#rfc.iref.p.3">3.1</a></li><li>duplex <a href="#rfc.iref.p.47">3.3</a></li><li>editing <a href="#rfc.iref.p.7">3.1</a></li><li>footer <a href="#rfc.iref.p.9">3.1</a></li><li>header <a href="#rfc.iref.p.11">3.1</a></li><li>ijustification <a href="#rfc.iref.p.51">3.3</a></li><li>include <a href="#rfc.iref.p.36">3.2</a></li><li>include-references-in-index <a href="#rfc.iref.p.49">3.3</a></li><li>inline <a href="#rfc.iref.p.13">3.1</a></li><li>iprnotified <a href="#rfc.iref.p.15">3.1</a></li><li>linkmailto <a href="#rfc.iref.p.17">3.1</a></li><li>needLines <a href="#rfc.iref.p.37">3.2</a></li><li>parse-xml-in-artwork <a href="#rfc.iref.p.54">3.3</a></li><li>private <a href="#rfc.iref.p.20">3.1</a>, <a href="#rfc.iref.p.65">D</a></li><li>refparent <a href="#rfc.iref.p.22">3.1</a></li><li>rfcedstyle <a href="#rfc.iref.p.24">3.1</a></li><li>sec-no-trailing-dots <a href="#rfc.iref.p.58">3.3</a></li><li>slides <a href="#rfc.iref.p.38">3.2</a></li><li>sortrefs <a href="#rfc.iref.p.26">3.1</a></li><li>strict <a href="#rfc.iref.p.39">3.2</a></li><li>subcompact <a href="#rfc.iref.p.40">3.2</a></li><li>support-rfc2731 <a href="#rfc.iref.p.56">3.3</a></li><li>symrefs <a href="#rfc.iref.p.28">3.1</a></li><li>toc <a href="#rfc.iref.p.30">3.1</a></li><li>tocdepth <a href="#rfc.iref.p.32">3.1</a></li><li>tocindent <a href="#rfc.iref.p.41">3.2</a></li><li>tocompact <a href="#rfc.iref.p.42">3.2</a></li><li>topblock <a href="#rfc.iref.p.34">3.1</a></li></ul></li><li>prose Extension Element <a href="#rfc.iref.p.61"><b>11.17</b></a>, <a href="#rfc.iref.p.63">A</a></li></ul></li><li><a id="rfc.index.Q" href="#rfc.index.Q"><b>Q</b></a><ul><li>q Extension Element <a href="#rfc.iref.q.1"><b>11.18</b></a>, <a href="#rfc.iref.q.2">A</a></li></ul></li><li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul><li>rdf:Description Extension Element <a href="#rfc.iref.r.26">A</a></li><li>ref Extension Element <a href="#rfc.iref.r.23"><b>11.19</b></a>, <a href="#rfc.iref.r.25">A</a></li><li>refparent PI pseudo-attribute <a href="#rfc.iref.r.1">3.1</a></li><li>Relation.Replaces DCMI property <a href="#rfc.iref.r.22">6.4</a></li><li>RELAX NG Compact Schema <a href="#rfc.iref.r.24"><b>A</b></a></li><li>rfc.abstract anchor <a href="#rfc.iref.r.3">4</a></li><li>rfc.authors anchor <a href="#rfc.iref.r.4">4</a></li><li>rfc.copyright anchor <a href="#rfc.iref.r.5">4</a></li><li>rfc.copyrightnotice anchor <a href="#rfc.iref.r.6">4</a></li><li>rfc.figure.n anchor <a href="#rfc.iref.r.7">4</a>, <a href="#rfc.iref.r.18">4</a></li><li>rfc.figure.u.n anchor <a href="#rfc.iref.r.8">4</a>, <a href="#rfc.iref.r.19">4</a></li><li>rfc.index anchor <a href="#rfc.iref.r.9">4</a></li><li>rfc.ipr anchor <a href="#rfc.iref.r.10">4</a></li><li>rfc.iref.n anchor <a href="#rfc.iref.r.11">4</a></li><li>rfc.note.n anchor <a href="#rfc.iref.r.12">4</a></li><li>rfc.references anchor <a href="#rfc.iref.r.13">4</a></li><li>rfc.references.n anchor <a href="#rfc.iref.r.14">4</a></li><li>rfc.section.n anchor <a href="#rfc.iref.r.15">4</a></li><li>rfc.section.n.p.m anchor <a href="#rfc.iref.r.16">4</a></li><li>rfc.status anchor <a href="#rfc.iref.r.17">4</a></li><li>rfc.toc anchor <a href="#rfc.iref.r.20">4</a></li><li>rfc.xref.name.n anchor <a href="#rfc.iref.r.21">4</a></li><li><em>RFC2026</em> <a href="#rfc.xref.RFC2026.1">11.25</a>, <a href="#RFC2026"><b>13</b></a>, <a href="#rfc.xref.RFC2026.2">D.2</a><ul><li><em>Section 4</em> <a href="#rfc.xref.RFC2026.2">D.2</a></li><li><em>Section 4.1</em> <a href="#rfc.xref.RFC2026.1">11.25</a></li></ul></li><li><em>RFC2119</em> <a href="#rfc.xref.RFC2119.1">11.3</a>, <a href="#rfc.xref.RFC2119.2">11.27</a>, <a href="#RFC2119"><b>13</b></a><ul><li><em>Section 5</em> <a href="#rfc.xref.RFC2119.2">11.27</a></li></ul></li><li><em>RFC2616</em> <a href="#RFC2616"><b>13</b></a>, <a href="#rfc.xref.RFC2616.1">B.1</a>, <a href="#rfc.xref.RFC2616.2">B.1</a>, <a href="#rfc.xref.RFC2616.3">B.1</a><ul><li><em>Section 2.1</em> <a href="#rfc.xref.RFC2616.1">B.1</a></li><li><em>Section 19.1</em> <a href="#rfc.xref.RFC2616.2">B.1</a>, <a href="#rfc.xref.RFC2616.3">B.1</a></li></ul></li><li><em>RFC2629</em> <a href="#rfc.xref.RFC2629.1">1</a>, <a href="#RFC2629"><b>13</b></a></li><li><em>RFC2648</em> <a href="#rfc.xref.RFC2648.1">6.4</a>, <a href="#RFC2648"><b>13</b></a></li><li><em>RFC2731</em> <a href="#rfc.xref.RFC2731.1">6.4</a>, <a href="#RFC2731"><b>13</b></a></li><li><em>RFC5234</em> <a href="#RFC5234"><b>13</b></a>, <a href="#rfc.xref.RFC5234.1">B.1</a></li><li><em>RFC5741</em> <a href="#RFC5741"><b>13</b></a>, <a href="#rfc.xref.RFC5741.1">D.3</a>, <a href="#rfc.xref.RFC5741.2">D.3</a>, <a href="#rfc.xref.RFC5741.3">D.4</a><ul><li><em>Section 3.2.2</em> <a href="#rfc.xref.RFC5741.2">D.3</a>, <a href="#rfc.xref.RFC5741.3">D.4</a></li></ul></li><li>rfcedstyle PI pseudo-attribute <a href="#rfc.iref.r.2">3.1</a></li><li><em>RNC</em> <a href="#RNC"><b>13</b></a>, <a href="#rfc.xref.RNC.1">A</a>, <a href="#rfc.xref.RNC.2">B.1</a></li></ul></li><li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul><li>Safari <a href="#rfc.iref.s.9">5.2</a>, <a href="#rfc.iref.s.11">5.2</a><ul><li>3.* <a href="#rfc.iref.s.10">5.2</a></li></ul></li><li>Saxon <a href="#rfc.iref.s.8">5.1</a></li><li>Schema <a href="#rfc.iref.s.14"><b>A</b></a></li><li>sec-no-trailing-dots PI pseudo-attribute <a href="#rfc.iref.s.7">3.3</a></li><li>slides PI pseudo-attribute <a href="#rfc.iref.s.3">3.2</a></li><li>sortrefs PI pseudo-attribute <a href="#rfc.iref.s.1">3.1</a></li><li>source Extension Element <a href="#rfc.iref.s.12"><b>11.20</b></a>, <a href="#rfc.iref.s.15">A</a></li><li>span Extension Element <a href="#rfc.iref.s.17">A</a></li><li>strict PI pseudo-attribute <a href="#rfc.iref.s.4">3.2</a></li><li>subcompact PI pseudo-attribute <a href="#rfc.iref.s.5">3.2</a></li><li>sup Extension Element <a href="#rfc.iref.s.13"><b>11.21</b></a>, <a href="#rfc.iref.s.16">A</a></li><li>support-rfc2731 PI pseudo-attribute <a href="#rfc.iref.s.6">3.3</a></li><li>symrefs PI pseudo-attribute <a href="#rfc.iref.s.2">3.1</a></li></ul></li><li><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul><li>toc PI pseudo-attribute <a href="#rfc.iref.t.1">3.1</a></li><li>tocdepth PI pseudo-attribute <a href="#rfc.iref.t.2">3.1</a></li><li>tocindent PI pseudo-attribute <a href="#rfc.iref.t.4">3.2</a></li><li>tocompact PI pseudo-attribute <a href="#rfc.iref.t.5">3.2</a></li><li>topblock PI pseudo-attribute <a href="#rfc.iref.t.3">3.1</a></li></ul></li><li><a id="rfc.index.X" href="#rfc.index.X"><b>X</b></a><ul><li>x Extension Element <a href="#rfc.iref.x.30">A</a></li><li>Xalan <a href="#rfc.iref.x.27">5.1</a></li><li><em>XHTML2</em> <a href="#rfc.xref.XHTML2.1">11.10</a>, <a href="#XHTML2"><b>13</b></a></li><li><em>XML</em> <a href="#XML"><b>13</b></a>, <a href="#rfc.xref.XML.1">C.1</a><ul><li><em>Section 2.8</em> <a href="#rfc.xref.XML.1">C.1</a></li></ul></li><li>xml-stylesheet PI <a href="#rfc.iref.x.29">6</a></li><li>xml2rfc-background parameter <a href="#rfc.iref.x.2">3.1</a></li><li>xml2rfc-comments parameter <a href="#rfc.iref.x.4">3.1</a></li><li>xml2rfc-editing parameter <a href="#rfc.iref.x.3">3.1</a>, <a href="#rfc.iref.x.5">3.1</a></li><li>xml2rfc-ext-allow-markup-in-artwork parameter <a href="#rfc.iref.x.19">3.3</a></li><li>xml2rfc-ext-authors-section parameter <a href="#rfc.iref.x.20">3.3</a></li><li>xml2rfc-ext-duplex <a href="#rfc.iref.x.21">3.3</a></li><li>xml2rfc-ext-include-references-in-index parameter <a href="#rfc.iref.x.22">3.3</a></li><li>xml2rfc-ext-justification parameter <a href="#rfc.iref.x.23">3.3</a></li><li>xml2rfc-ext-parse-xml-in-artwork parameter <a href="#rfc.iref.x.24">3.3</a></li><li>xml2rfc-ext-sec-no-trailing-dots parameter <a href="#rfc.iref.x.26">3.3</a></li><li>xml2rfc-ext-support-rfc2731 parameter <a href="#rfc.iref.x.25">3.3</a></li><li>xml2rfc-footer parameter <a href="#rfc.iref.x.6">3.1</a></li><li>xml2rfc-header parameter <a href="#rfc.iref.x.7">3.1</a></li><li>xml2rfc-inline parameter <a href="#rfc.iref.x.8">3.1</a></li><li>xml2rfc-iprnotified parameter <a href="#rfc.iref.x.9">3.1</a></li><li>xml2rfc-linkmailto parameter <a href="#rfc.iref.x.10">3.1</a></li><li>xml2rfc-private parameter <a href="#rfc.iref.x.11">3.1</a></li><li>xml2rfc-refparent parameter <a href="#rfc.iref.x.12">3.1</a></li><li>xml2rfc-rfcedstyle parameter <a href="#rfc.iref.x.13">3.1</a></li><li>xml2rfc-sortrefs parameter <a href="#rfc.iref.x.14">3.1</a></li><li>xml2rfc-symrefs parameter <a href="#rfc.iref.x.15">3.1</a></li><li>xml2rfc-toc parameter <a href="#rfc.iref.x.16">3.1</a></li><li>xml2rfc-tocdepth parameter <a href="#rfc.iref.x.17">3.1</a></li><li>xml2rfc-topblock parameter <a href="#rfc.iref.x.18">3.1</a></li><li><em>XSL-FO</em> <a href="#rfc.xref.XSL-FO.1">9.1</a>, <a href="#rfc.xref.XSL-FO.2">9.1</a>, <a href="#XSL-FO"><b>13</b></a></li><li>xsltproc <a href="#rfc.iref.x.28">5.1</a><ul><li>passing parameters <a href="#rfc.iref.x.1">3</a></li></ul></li></ul></li></ul></div></body></html> -
rfc2629xslt/rfc2629xslt.txt
r1099 r1103 4 4 RFC2629 through XSLT J. Reschke 5 5 greenbytes 6 November 20106 January 27, 2011 7 7 8 8 … … 56 56 57 57 58 Documentation RFC2629 through XSLT November 201058 Documentation RFC2629 through XSLT January 2011 59 59 60 60 … … 113 113 114 114 115 Documentation RFC2629 through XSLT November 2010115 Documentation RFC2629 through XSLT January 2011 116 116 117 117 … … 170 170 171 171 172 Documentation RFC2629 through XSLT November 2010172 Documentation RFC2629 through XSLT January 2011 173 173 174 174 … … 227 227 228 228 229 Documentation RFC2629 through XSLT November 2010229 Documentation RFC2629 through XSLT January 2011 230 230 231 231 … … 284 284 285 285 286 Documentation RFC2629 through XSLT November 2010286 Documentation RFC2629 through XSLT January 2011 287 287 288 288 … … 341 341 342 342 343 Documentation RFC2629 through XSLT November 2010343 Documentation RFC2629 through XSLT January 2011 344 344 345 345 … … 398 398 399 399 400 Documentation RFC2629 through XSLT November 2010400 Documentation RFC2629 through XSLT January 2011 401 401 402 402 … … 455 455 456 456 457 Documentation RFC2629 through XSLT November 2010457 Documentation RFC2629 through XSLT January 2011 458 458 459 459 … … 512 512 513 513 514 Documentation RFC2629 through XSLT November 2010514 Documentation RFC2629 through XSLT January 2011 515 515 516 516 … … 569 569 570 570 571 Documentation RFC2629 through XSLT November 2010571 Documentation RFC2629 through XSLT January 2011 572 572 573 573 … … 626 626 627 627 628 Documentation RFC2629 through XSLT November 2010628 Documentation RFC2629 through XSLT January 2011 629 629 630 630 … … 683 683 684 684 685 Documentation RFC2629 through XSLT November 2010685 Documentation RFC2629 through XSLT January 2011 686 686 687 687 … … 740 740 741 741 742 Documentation RFC2629 through XSLT November 2010742 Documentation RFC2629 through XSLT January 2011 743 743 744 744 … … 797 797 798 798 799 Documentation RFC2629 through XSLT November 2010799 Documentation RFC2629 through XSLT January 2011 800 800 801 801 … … 854 854 855 855 856 Documentation RFC2629 through XSLT November 2010856 Documentation RFC2629 through XSLT January 2011 857 857 858 858 … … 911 911 912 912 913 Documentation RFC2629 through XSLT November 2010913 Documentation RFC2629 through XSLT January 2011 914 914 915 915 … … 968 968 969 969 970 Documentation RFC2629 through XSLT November 2010970 Documentation RFC2629 through XSLT January 2011 971 971 972 972 … … 1025 1025 1026 1026 1027 Documentation RFC2629 through XSLT November 20101027 Documentation RFC2629 through XSLT January 2011 1028 1028 1029 1029 … … 1082 1082 1083 1083 1084 Documentation RFC2629 through XSLT November 20101084 Documentation RFC2629 through XSLT January 2011 1085 1085 1086 1086 … … 1139 1139 1140 1140 1141 Documentation RFC2629 through XSLT November 20101141 Documentation RFC2629 through XSLT January 2011 1142 1142 1143 1143 … … 1196 1196 1197 1197 1198 Documentation RFC2629 through XSLT November 20101198 Documentation RFC2629 through XSLT January 2011 1199 1199 1200 1200 … … 1253 1253 1254 1254 1255 Documentation RFC2629 through XSLT November 20101255 Documentation RFC2629 through XSLT January 2011 1256 1256 1257 1257 … … 1310 1310 1311 1311 1312 Documentation RFC2629 through XSLT November 20101312 Documentation RFC2629 through XSLT January 2011 1313 1313 1314 1314 … … 1367 1367 1368 1368 1369 Documentation RFC2629 through XSLT November 20101369 Documentation RFC2629 through XSLT January 2011 1370 1370 1371 1371 … … 1424 1424 1425 1425 1426 Documentation RFC2629 through XSLT November 20101426 Documentation RFC2629 through XSLT January 2011 1427 1427 1428 1428 … … 1481 1481 1482 1482 1483 Documentation RFC2629 through XSLT November 20101483 Documentation RFC2629 through XSLT January 2011 1484 1484 1485 1485 … … 1538 1538 1539 1539 1540 Documentation RFC2629 through XSLT November 20101540 Documentation RFC2629 through XSLT January 2011 1541 1541 1542 1542 … … 1595 1595 1596 1596 1597 Documentation RFC2629 through XSLT November 20101597 Documentation RFC2629 through XSLT January 2011 1598 1598 1599 1599 … … 1652 1652 1653 1653 1654 Documentation RFC2629 through XSLT November 20101654 Documentation RFC2629 through XSLT January 2011 1655 1655 1656 1656 … … 1709 1709 1710 1710 1711 Documentation RFC2629 through XSLT November 20101711 Documentation RFC2629 through XSLT January 2011 1712 1712 1713 1713 … … 1766 1766 1767 1767 1768 Documentation RFC2629 through XSLT November 20101768 Documentation RFC2629 through XSLT January 2011 1769 1769 1770 1770 … … 1823 1823 1824 1824 1825 Documentation RFC2629 through XSLT November 20101825 Documentation RFC2629 through XSLT January 2011 1826 1826 1827 1827 … … 1880 1880 1881 1881 1882 Documentation RFC2629 through XSLT November 20101882 Documentation RFC2629 through XSLT January 2011 1883 1883 1884 1884 … … 1937 1937 1938 1938 1939 Documentation RFC2629 through XSLT November 20101939 Documentation RFC2629 through XSLT January 2011 1940 1940 1941 1941 … … 1994 1994 1995 1995 1996 Documentation RFC2629 through XSLT November 20101996 Documentation RFC2629 through XSLT January 2011 1997 1997 1998 1998 … … 2051 2051 2052 2052 2053 Documentation RFC2629 through XSLT November 20102053 Documentation RFC2629 through XSLT January 2011 2054 2054 2055 2055 … … 2108 2108 2109 2109 2110 Documentation RFC2629 through XSLT November 20102110 Documentation RFC2629 through XSLT January 2011 2111 2111 2112 2112 … … 2165 2165 2166 2166 2167 Documentation RFC2629 through XSLT November 20102167 Documentation RFC2629 through XSLT January 2011 2168 2168 2169 2169 … … 2222 2222 2223 2223 2224 Documentation RFC2629 through XSLT November 20102224 Documentation RFC2629 through XSLT January 2011 2225 2225 2226 2226 … … 2279 2279 2280 2280 2281 Documentation RFC2629 through XSLT November 20102281 Documentation RFC2629 through XSLT January 2011 2282 2282 2283 2283 … … 2336 2336 2337 2337 2338 Documentation RFC2629 through XSLT November 20102338 Documentation RFC2629 through XSLT January 2011 2339 2339 2340 2340 … … 2393 2393 2394 2394 2395 Documentation RFC2629 through XSLT November 20102395 Documentation RFC2629 through XSLT January 2011 2396 2396 2397 2397 … … 2450 2450 2451 2451 2452 Documentation RFC2629 through XSLT November 20102452 Documentation RFC2629 through XSLT January 2011 2453 2453 2454 2454 … … 2507 2507 2508 2508 2509 Documentation RFC2629 through XSLT November 20102509 Documentation RFC2629 through XSLT January 2011 2510 2510 2511 2511 … … 2564 2564 2565 2565 2566 Documentation RFC2629 through XSLT November 20102566 Documentation RFC2629 through XSLT January 2011 2567 2567 2568 2568 … … 2621 2621 2622 2622 2623 Documentation RFC2629 through XSLT November 20102623 Documentation RFC2629 through XSLT January 2011 2624 2624 2625 2625 … … 2678 2678 2679 2679 2680 Documentation RFC2629 through XSLT November 20102680 Documentation RFC2629 through XSLT January 2011 2681 2681 2682 2682 … … 2735 2735 2736 2736 2737 Documentation RFC2629 through XSLT November 20102737 Documentation RFC2629 through XSLT January 2011 2738 2738 2739 2739 … … 2761 2761 2762 2762 <!-- allow later RFC2616 reference using "&rfc2616;" --> 2763 <!-- the data will be fetched from xml.resource.org --> 2763 2764 <!ENTITY rfc2616 PUBLIC 2764 2765 "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2616.xml"> 2765 2766 2767 <!-- allow a custom reference using "&mydraft;" --> 2768 <!-- the data will be fetched from the same location as the 2769 source file --> 2770 <!ENTITY mydraft PUBLIC "reference.mydraft.xml"> 2766 2771 ]> 2767 2772 … … 2784 2789 2785 2790 2786 2787 2788 2789 2790 2791 2791 Reschke [Page 49] 2792 2792 2793 2793 2794 Documentation RFC2629 through XSLT November 20102794 Documentation RFC2629 through XSLT January 2011 2795 2795 2796 2796 … … 2849 2849 2850 2850 2851 Documentation RFC2629 through XSLT November 20102851 Documentation RFC2629 through XSLT January 2011 2852 2852 2853 2853 … … 2906 2906 2907 2907 2908 Documentation RFC2629 through XSLT November 20102908 Documentation RFC2629 through XSLT January 2011 2909 2909 2910 2910 … … 2963 2963 2964 2964 2965 Documentation RFC2629 through XSLT November 20102965 Documentation RFC2629 through XSLT January 2011 2966 2966 2967 2967 … … 3020 3020 3021 3021 3022 Documentation RFC2629 through XSLT November 20103022 Documentation RFC2629 through XSLT January 2011 3023 3023 3024 3024 … … 3077 3077 3078 3078 3079 Documentation RFC2629 through XSLT November 20103079 Documentation RFC2629 through XSLT January 2011 3080 3080 3081 3081 … … 3134 3134 3135 3135 3136 Documentation RFC2629 through XSLT November 20103136 Documentation RFC2629 through XSLT January 2011 3137 3137 3138 3138 … … 3191 3191 3192 3192 3193 Documentation RFC2629 through XSLT November 20103193 Documentation RFC2629 through XSLT January 2011 3194 3194 3195 3195 … … 3248 3248 3249 3249 3250 Documentation RFC2629 through XSLT November 20103250 Documentation RFC2629 through XSLT January 2011 3251 3251 3252 3252 … … 3305 3305 3306 3306 3307 Documentation RFC2629 through XSLT November 20103307 Documentation RFC2629 through XSLT January 2011 3308 3308 3309 3309 … … 3326 3326 2010-08-31 Experimental support for prose in references. 3327 3327 3328 2011-01-27 Update to xml2rfc v1.36pre1. 3329 3328 3330 F.2. amazon-asin.xslt 3329 3331 … … 3357 3359 3358 3360 3359 3360 3361 3361 Reschke [Page 59] 3362 3362 3363 3363 3364 Documentation RFC2629 through XSLT November 20103364 Documentation RFC2629 through XSLT January 2011 3365 3365 3366 3366 … … 3419 3419 3420 3420 3421 Documentation RFC2629 through XSLT November 20103421 Documentation RFC2629 through XSLT January 2011 3422 3422 3423 3423 … … 3476 3476 3477 3477 3478 Documentation RFC2629 through XSLT November 20103478 Documentation RFC2629 through XSLT January 2011 3479 3479 3480 3480 … … 3533 3533 3534 3534 3535 Documentation RFC2629 through XSLT November 20103535 Documentation RFC2629 through XSLT January 2011 3536 3536 3537 3537 … … 3590 3590 3591 3591 3592 Documentation RFC2629 through XSLT November 20103592 Documentation RFC2629 through XSLT January 2011 3593 3593 3594 3594 … … 3647 3647 3648 3648 3649 Documentation RFC2629 through XSLT November 20103649 Documentation RFC2629 through XSLT January 2011 3650 3650 3651 3651 … … 3704 3704 3705 3705 3706 Documentation RFC2629 through XSLT November 20103706 Documentation RFC2629 through XSLT January 2011 3707 3707 3708 3708 … … 3761 3761 3762 3762 3763 Documentation RFC2629 through XSLT November 20103763 Documentation RFC2629 through XSLT January 2011 3764 3764 3765 3765 … … 3818 3818 3819 3819 3820 Documentation RFC2629 through XSLT November 20103820 Documentation RFC2629 through XSLT January 2011 3821 3821 3822 3822 … … 3875 3875 3876 3876 3877 Documentation RFC2629 through XSLT November 20103877 Documentation RFC2629 through XSLT January 2011 3878 3878 3879 3879 … … 3932 3932 3933 3933 3934 Documentation RFC2629 through XSLT November 20103934 Documentation RFC2629 through XSLT January 2011 3935 3935 3936 3936 … … 3989 3989 3990 3990 3991 Documentation RFC2629 through XSLT November 20103991 Documentation RFC2629 through XSLT January 2011 3992 3992 3993 3993 … … 4046 4046 4047 4047 4048 Documentation RFC2629 through XSLT November 20104048 Documentation RFC2629 through XSLT January 2011 4049 4049 4050 4050 … … 4103 4103 4104 4104 4105 Documentation RFC2629 through XSLT November 20104105 Documentation RFC2629 through XSLT January 2011 4106 4106 4107 4107 … … 4160 4160 4161 4161 4162 Documentation RFC2629 through XSLT November 20104162 Documentation RFC2629 through XSLT January 2011 4163 4163 4164 4164 … … 4217 4217 4218 4218 4219 Documentation RFC2629 through XSLT November 20104219 Documentation RFC2629 through XSLT January 2011 4220 4220 4221 4221 … … 4274 4274 4275 4275 4276 Documentation RFC2629 through XSLT November 20104276 Documentation RFC2629 through XSLT January 2011 4277 4277 4278 4278 … … 4331 4331 4332 4332 4333 Documentation RFC2629 through XSLT November 20104333 Documentation RFC2629 through XSLT January 2011 4334 4334 4335 4335 … … 4388 4388 4389 4389 4390 Documentation RFC2629 through XSLT November 20104390 Documentation RFC2629 through XSLT January 2011 4391 4391 4392 4392 … … 4445 4445 4446 4446 4447 Documentation RFC2629 through XSLT November 20104447 Documentation RFC2629 through XSLT January 2011 4448 4448 4449 4449 … … 4502 4502 4503 4503 4504 Documentation RFC2629 through XSLT November 20104504 Documentation RFC2629 through XSLT January 2011 4505 4505 4506 4506 … … 4559 4559 4560 4560 4561 Documentation RFC2629 through XSLT November 20104561 Documentation RFC2629 through XSLT January 2011 4562 4562 4563 4563 -
rfc2629xslt/rfc2629xslt.xml
r1095 r1103 30 30 </author> 31 31 32 <date month=" November" year="2010"/>32 <date month="January" year="2011"/> 33 33 34 34 <keyword>RFC2629</keyword> … … 2342 2342 2343 2343 <!-- <spanx>allow later RFC2616 reference using "&rfc2616;"</spanx> --> 2344 <!-- <spanx>the data will be fetched from xml.resource.org</spanx> --> 2344 2345 <!ENTITY rfc2616 PUBLIC 2345 2346 "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2616.xml"> 2346 2347 2348 <!-- <spanx>allow a custom reference using "&mydraft;"</spanx> --> 2349 <!-- <spanx>the data will be fetched from the same location as the 2350 source file</spanx> --> 2351 <!ENTITY mydraft PUBLIC "reference.mydraft.xml"> 2347 2352 ]> 2348 2353 </artwork> … … 2851 2856 Experimental support for prose in references. 2852 2857 </t> 2858 <t hangText="2011-01-27"> 2859 Update to xml2rfc v1.36pre1. 2860 </t> 2853 2861 </list></t> 2854 2862 </section> -
rfc2629xslt/samples/rfc2629.xslt
r1099 r1103 2 2 XSLT transformation from RFC2629 XML format to HTML 3 3 4 Copyright (c) 2006-201 0, Julian Reschke (julian.reschke@greenbytes.de)4 Copyright (c) 2006-2011, Julian Reschke (julian.reschke@greenbytes.de) 5 5 All rights reserved. 6 6 … … 2667 2667 2668 2668 <xsl:template name="collectLeftHeaderColumn"> 2669 <xsl:param name="mode" />2670 2669 <!-- default case --> 2671 2670 <xsl:if test="$xml2rfc-private=''"> … … 3656 3655 } 3657 3656 @bottom-center { 3658 content: "<xsl:call-template name="get- category-long"/>";3657 content: "<xsl:call-template name="get-bottom-center"/>"; 3659 3658 } 3660 3659 @bottom-right { … … 3676 3675 } 3677 3676 @bottom-center { 3678 content: "<xsl:call-template name="get- category-long"/>";3677 content: "<xsl:call-template name="get-bottom-center"/>"; 3679 3678 } 3680 3679 @bottom-right { … … 3697 3696 } 3698 3697 @bottom-center { 3699 content: "<xsl:call-template name="get- category-long"/>";3698 content: "<xsl:call-template name="get-bottom-center"/>"; 3700 3699 } 3701 3700 @bottom-right { … … 6056 6055 <xsl:attribute name="title"> 6057 6056 <xsl:if test="@source"><xsl:value-of select="@source"/>: </xsl:if> 6058 <xsl:apply-templates select="text()|eref|xref"/> 6057 <xsl:variable name="content"> 6058 <xsl:apply-templates select="text()|eref|xref"/> 6059 </xsl:variable> 6060 <xsl:value-of select="$content"/> 6059 6061 </xsl:attribute> 6060 6062 <xsl:text>[</xsl:text> … … 6173 6175 </xsl:template> 6174 6176 6177 <xsl:template name="get-bottom-center"> 6178 <xsl:choose> 6179 <xsl:when test="/rfc/@docName"> 6180 <!-- for IDs, use the expiry date --> 6181 <xsl:text>Expires </xsl:text><xsl:call-template name="expirydate" /> 6182 </xsl:when> 6183 <xsl:otherwise> 6184 <xsl:call-template name="get-category-long"/> 6185 </xsl:otherwise> 6186 </xsl:choose> 6187 </xsl:template> 6188 6175 6189 <xsl:template name="get-category-long"> 6176 6190 <xsl:choose> … … 6210 6224 <xsl:text>http://greenbytes.de/tech/webdav/rfc2629.xslt, </xsl:text> 6211 6225 <!-- when RCS keyword substitution in place, add version info --> 6212 <xsl:if test="contains('$Revision: 1.5 37$',':')">6213 <xsl:value-of select="concat('Revision ',normalize-space(translate(substring-after('$Revision: 1.5 37$', 'Revision: '),'$','')),', ')" />6226 <xsl:if test="contains('$Revision: 1.540 $',':')"> 6227 <xsl:value-of select="concat('Revision ',normalize-space(translate(substring-after('$Revision: 1.540 $', 'Revision: '),'$','')),', ')" /> 6214 6228 </xsl:if> 6215 <xsl:if test="contains('$Date: 201 0-12-30 14:21:59$',':')">6216 <xsl:value-of select="concat(normalize-space(translate(substring-after('$Date: 201 0-12-30 14:21:59$', 'Date: '),'$','')),', ')" />6229 <xsl:if test="contains('$Date: 2011-01-10 09:27:20 $',':')"> 6230 <xsl:value-of select="concat(normalize-space(translate(substring-after('$Date: 2011-01-10 09:27:20 $', 'Date: '),'$','')),', ')" /> 6217 6231 </xsl:if> 6218 6232 <xsl:value-of select="concat('XSLT vendor: ',system-property('xsl:vendor'),' ',system-property('xsl:vendor-url'))" /> -
rfc2629xslt/samples/sample.ipr.id.noDerivativesTrust200902.200909.test.xhtml
r1072 r1103 277 277 } 278 278 @bottom-center { 279 content: " Informational";279 content: "Expires March 5, 2010"; 280 280 } 281 281 @bottom-right { -
rfc2629xslt/samples/sample.ipr.id.noModification3978.200606.test.xhtml
r1072 r1103 277 277 } 278 278 @bottom-center { 279 content: " Informational";279 content: "Expires December 3, 2006"; 280 280 } 281 281 @bottom-right { -
rfc2629xslt/samples/sample.ipr.id.noModificationTrust200902.200909.test.xhtml
r1072 r1103 277 277 } 278 278 @bottom-center { 279 content: " Informational";279 content: "Expires March 5, 2010"; 280 280 } 281 281 @bottom-right { -
rfc2629xslt/samples/sample.ipr.id.pre5378Trust200902.200909.test.xhtml
r1072 r1103 277 277 } 278 278 @bottom-center { 279 content: " Informational";279 content: "Expires March 5, 2010"; 280 280 } 281 281 @bottom-right { -
rfc2629xslt/samples/sample.ipr.id.pre5378Trust200902.200912.test.xhtml
r1072 r1103 277 277 } 278 278 @bottom-center { 279 content: " Informational";279 content: "Expires June 4, 2010"; 280 280 } 281 281 @bottom-right { -
rfc2629xslt/samples/sample.ipr.id.pre5378Trust200902.201011.test.xhtml
r1095 r1103 277 277 } 278 278 @bottom-center { 279 content: " Informational";279 content: "Expires May 5, 2011"; 280 280 } 281 281 @bottom-right { -
rfc2629xslt/samples/sample.ipr.id.trust200902.200909.test.xhtml
r1072 r1103 277 277 } 278 278 @bottom-center { 279 content: " Informational";279 content: "Expires March 5, 2010"; 280 280 } 281 281 @bottom-right { -
rfc2629xslt/samples/sample.ipr.id.trust200902.200911.test.xhtml
r1072 r1103 277 277 } 278 278 @bottom-center { 279 content: " Informational";279 content: "Expires May 5, 2010"; 280 280 } 281 281 @bottom-right { -
rfc2629xslt/samples/sample.ipr.id.trust200902.201006.iab.test.xhtml
r1072 r1103 277 277 } 278 278 @bottom-center { 279 content: " Informational";279 content: "Expires December 3, 2010"; 280 280 } 281 281 @bottom-right { -
rfc2629xslt/samples/sample.ipr.id.trust200902.201006.ietf.test.xhtml
r1072 r1103 277 277 } 278 278 @bottom-center { 279 content: " Informational";279 content: "Expires December 3, 2010"; 280 280 } 281 281 @bottom-right { -
rfc2629xslt/samples/sample.ipr.id.trust200902.201006.ind.test.xhtml
r1072 r1103 277 277 } 278 278 @bottom-center { 279 content: " Informational";279 content: "Expires December 3, 2010"; 280 280 } 281 281 @bottom-right { -
rfc2629xslt/samples/sample.ipr.id.trust200902.201006.irtf.test.xhtml
r1072 r1103 277 277 } 278 278 @bottom-center { 279 content: " Informational";279 content: "Expires December 3, 2010"; 280 280 } 281 281 @bottom-right { -
rfc2629xslt/samples/sample.ipr.id.trust200902.201006.test.xhtml
r1072 r1103 277 277 } 278 278 @bottom-center { 279 content: " Informational";279 content: "Expires December 3, 2010"; 280 280 } 281 281 @bottom-right { -
rfc2629xslt/samples/sample.ipr.rfc.201001.iab.exp.txt
r1095 r1103 2 2 3 3 4 Network Working GroupJ. Doe4 Internet Architecture Board (IAB) J. Doe 5 5 Request for Comments: 9999 January 2010 6 6 Category: Experimental 7 ISSN: 2070-1721 7 8 8 9 … … 15 16 Status of This Memo 16 17 17 This memo defines an Experimental Protocol for the Internet 18 community. It does not specify an Internet standard of any kind. 19 Discussion and suggestions for improvement are requested. 20 Distribution of this memo is unlimited. 18 This document is not an Internet Standards Track specification; it is 19 published for examination, experimental implementation, and 20 evaluation. 21 22 This document defines an Experimental Protocol for the Internet 23 community. This document is a product of the Internet Architecture 24 Board (IAB) and represents information that the IAB has deemed 25 valuable to provide for permanent record. Documents approved for 26 publication by the IAB are not a candidate for any level of Internet 27 Standard; see Section 2 of RFC 5741. 28 29 Information about the current status of this document, any errata, 30 and how to provide feedback on it may be obtained at 31 http://www.rfc-editor.org/info/rfc9999. 21 32 22 33 Copyright Notice … … 35 46 36 47 Dummy Section. 48 49 50 51 52 53 54 55 Doe Experimental [Page 1] 56 57 58 RFC 9999 IAB Experimental January 2010 59 37 60 38 61 Author's Address … … 53 76 54 77 55 Doe Experimental [Page 1]56 78 57 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 Doe Experimental [Page 2] 113 114 -
rfc2629xslt/samples/sample.ipr.rfc.201001.iab.hist.txt
r1095 r1103 2 2 3 3 4 Network Working GroupJ. Doe4 Internet Architecture Board (IAB) J. Doe 5 5 Request for Comments: 9999 January 2010 6 6 Category: Historic 7 ISSN: 2070-1721 7 8 8 9 … … 15 16 Status of This Memo 16 17 17 This memo describes a historic protocol for the Internet community. 18 It does not specify an Internet standard of any kind. Distribution 19 of this memo is unlimited. 18 This document is not an Internet Standards Track specification; it is 19 published for the historical record. 20 21 This document defines a Historic Document for the Internet community. 22 This document is a product of the Internet Architecture Board (IAB) 23 and represents information that the IAB has deemed valuable to 24 provide for permanent record. Documents approved for publication by 25 the IAB are not a candidate for any level of Internet Standard; see 26 Section 2 of RFC 5741. 27 28 Information about the current status of this document, any errata, 29 and how to provide feedback on it may be obtained at 30 http://www.rfc-editor.org/info/rfc9999. 20 31 21 32 Copyright Notice … … 34 45 35 46 Dummy Section. 47 48 49 50 51 52 53 54 55 Doe Historic [Page 1] 56 57 58 RFC 9999 IAB Historic January 2010 59 36 60 37 61 Author's Address … … 53 77 54 78 55 Doe Historic [Page 1]56 79 57 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 Doe Historic [Page 2] 113 114 -
rfc2629xslt/samples/sample.ipr.rfc.201001.iab.inf.txt
r1095 r1103 2 2 3 3 4 Network Working GroupJ. Doe4 Internet Architecture Board (IAB) J. Doe 5 5 Request for Comments: 9999 January 2010 6 6 Category: Informational 7 ISSN: 2070-1721 7 8 8 9 … … 15 16 Status of This Memo 16 17 17 This memo provides information for the Internet community. It does 18 not specify an Internet standard of any kind. Distribution of this 19 memo is unlimited. 18 This document is not an Internet Standards Track specification; it is 19 published for informational purposes. 20 21 This document is a product of the Internet Architecture Board (IAB) 22 and represents information that the IAB has deemed valuable to 23 provide for permanent record. Documents approved for publication by 24 the IAB are not a candidate for any level of Internet Standard; see 25 Section 2 of RFC 5741. 26 27 Information about the current status of this document, any errata, 28 and how to provide feedback on it may be obtained at 29 http://www.rfc-editor.org/info/rfc9999. 20 30 21 31 Copyright Notice … … 43 53 44 54 45 46 47 48 49 50 51 52 53 54 55 55 Doe Informational [Page 1] 56 56 -
rfc2629xslt/samples/sample.ipr.rfc.201001.ietf.bcp.c.txt
r1095 r1103 2 2 3 3 4 Network Working GroupJ. Doe4 Internet Engineering Task Force (IETF) J. Doe 5 5 Request for Comments: 9999 January 2010 6 6 Category: Best Current Practice 7 ISSN: 2070-1721 7 8 8 9 … … 15 16 Status of This Memo 16 17 17 This document specifies an Internet Best Current Practices for the 18 Internet Community, and requests discussion and suggestions for 19 improvements. Distribution of this memo is unlimited. 18 This memo documents an Internet Best Current Practice. 19 20 This document is a product of the Internet Engineering Task Force 21 (IETF). It represents the consensus of the IETF community. It has 22 received public review and has been approved for publication by the 23 Internet Engineering Steering Group (IESG). Further information on 24 BCPs is available in Section 2 of RFC 5741. 25 26 Information about the current status of this document, any errata, 27 and how to provide feedback on it may be obtained at 28 http://www.rfc-editor.org/info/rfc9999. 20 29 21 30 Copyright Notice … … 38 47 Dummy Section. 39 48 49 50 51 52 53 54 55 Doe Best Current Practice [Page 1] 56 57 58 RFC 9999 IETF Best Current Practice w/ consensus January 2010 59 60 40 61 Author's Address 41 62 … … 53 74 54 75 55 Doe Best Current Practice [Page 1]56 76 57 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 Doe Best Current Practice [Page 2] 113 114 -
rfc2629xslt/samples/sample.ipr.rfc.201001.ietf.exp.c.txt
r1095 r1103 2 2 3 3 4 Network Working GroupJ. Doe4 Internet Engineering Task Force (IETF) J. Doe 5 5 Request for Comments: 9999 January 2010 6 6 Category: Experimental 7 ISSN: 2070-1721 7 8 8 9 … … 15 16 Status of This Memo 16 17 17 This memo defines an Experimental Protocol for the Internet 18 community. It does not specify an Internet standard of any kind. 19 Discussion and suggestions for improvement are requested. 20 Distribution of this memo is unlimited. 18 This document is not an Internet Standards Track specification; it is 19 published for examination, experimental implementation, and 20 evaluation. 21 22 This document defines an Experimental Protocol for the Internet 23 community. This document is a product of the Internet Engineering 24 Task Force (IETF). It represents the consensus of the IETF 25 community. It has received public review and has been approved for 26 publication by the Internet Engineering Steering Group (IESG). Not 27 all documents approved by the IESG are a candidate for any level of 28 Internet Standard; see Section 2 of RFC 5741. 29 30 Information about the current status of this document, any errata, 31 and how to provide feedback on it may be obtained at 32 http://www.rfc-editor.org/info/rfc9999. 21 33 22 34 Copyright Notice … … 34 46 the Trust Legal Provisions and are provided without warranty as 35 47 described in the Simplified BSD License. 48 49 50 51 52 53 54 55 Doe Experimental [Page 1] 56 57 58 RFC 9999 IETF Experimental w/ consensus January 2010 59 36 60 37 61 1. Dummy Section … … 53 77 54 78 55 Doe Experimental [Page 1]56 79 57 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 Doe Experimental [Page 2] 113 114 -
rfc2629xslt/samples/sample.ipr.rfc.201001.ietf.exp.nc.txt
r1095 r1103 2 2 3 3 4 Network Working GroupJ. Doe4 Internet Engineering Task Force (IETF) J. Doe 5 5 Request for Comments: 9999 January 2010 6 6 Category: Experimental 7 ISSN: 2070-1721 7 8 8 9 … … 15 16 Status of This Memo 16 17 17 This memo defines an Experimental Protocol for the Internet 18 community. It does not specify an Internet standard of any kind. 19 Discussion and suggestions for improvement are requested. 20 Distribution of this memo is unlimited. 18 This document is not an Internet Standards Track specification; it is 19 published for examination, experimental implementation, and 20 evaluation. 21 22 This document defines an Experimental Protocol for the Internet 23 community. This document is a product of the Internet Engineering 24 Task Force (IETF). It has been approved for publication by the 25 Internet Engineering Steering Group (IESG). Not all documents 26 approved by the IESG are a candidate for any level of Internet 27 Standard; see Section 2 of RFC 5741. 28 29 Information about the current status of this document, any errata, 30 and how to provide feedback on it may be obtained at 31 http://www.rfc-editor.org/info/rfc9999. 21 32 22 33 Copyright Notice … … 39 50 Dummy Section. 40 51 52 53 54 55 Doe Experimental [Page 1] 56 57 58 RFC 9999 IETF Experimental w/o consensus January 2010 59 60 41 61 Author's Address 42 62 … … 53 73 54 74 55 Doe Experimental [Page 1]56 75 57 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 Doe Experimental [Page 2] 113 114 -
rfc2629xslt/samples/sample.ipr.rfc.201001.ietf.hist.c.txt
r1095 r1103 2 2 3 3 4 Network Working GroupJ. Doe4 Internet Engineering Task Force (IETF) J. Doe 5 5 Request for Comments: 9999 January 2010 6 6 Category: Historic 7 ISSN: 2070-1721 7 8 8 9 … … 15 16 Status of This Memo 16 17 17 This memo describes a historic protocol for the Internet community. 18 It does not specify an Internet standard of any kind. Distribution 19 of this memo is unlimited. 18 This document is not an Internet Standards Track specification; it is 19 published for the historical record. 20 21 This document defines a Historic Document for the Internet community. 22 This document is a product of the Internet Engineering Task Force 23 (IETF). It represents the consensus of the IETF community. It has 24 received public review and has been approved for publication by the 25 Internet Engineering Steering Group (IESG). Not all documents 26 approved by the IESG are a candidate for any level of Internet 27 Standard; see Section 2 of RFC 5741. 28 29 Information about the current status of this document, any errata, 30 and how to provide feedback on it may be obtained at 31 http://www.rfc-editor.org/info/rfc9999. 20 32 21 33 Copyright Notice … … 38 50 Dummy Section. 39 51 52 53 54 55 Doe Historic [Page 1] 56 57 58 RFC 9999 IETF Historic w/ consensus January 2010 59 60 40 61 Author's Address 41 62 … … 53 74 54 75 55 Doe Historic [Page 1]56 76 57 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 Doe Historic [Page 2] 113 114 -
rfc2629xslt/samples/sample.ipr.rfc.201001.ietf.hist.nc.txt
r1095 r1103 2 2 3 3 4 Network Working GroupJ. Doe4 Internet Engineering Task Force (IETF) J. Doe 5 5 Request for Comments: 9999 January 2010 6 6 Category: Historic 7 ISSN: 2070-1721 7 8 8 9 … … 15 16 Status of This Memo 16 17 17 This memo describes a historic protocol for the Internet community. 18 It does not specify an Internet standard of any kind. Distribution 19 of this memo is unlimited. 18 This document is not an Internet Standards Track specification; it is 19 published for the historical record. 20 21 This document defines a Historic Document for the Internet community. 22 This document is a product of the Internet Engineering Task Force 23 (IETF). It has been approved for publication by the Internet 24 Engineering Steering Group (IESG). Not all documents approved by the 25 IESG are a candidate for any level of Internet Standard; see Section 26 2 of RFC 5741. 27 28 Information about the current status of this document, any errata, 29 and how to provide feedback on it may be obtained at 30 http://www.rfc-editor.org/info/rfc9999. 20 31 21 32 Copyright Notice … … 38 49 Dummy Section. 39 50 51 52 53 54 55 Doe Historic [Page 1] 56 57 58 RFC 9999 IETF Historic w/o consensus January 2010 59 60 40 61 Author's Address 41 62 … … 53 74 54 75 55 Doe Historic [Page 1]56 76 57 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 Doe Historic [Page 2] 113 114 -
rfc2629xslt/samples/sample.ipr.rfc.201001.ietf.inf.c.txt
r1095 r1103 2 2 3 3 4 Network Working GroupJ. Doe4 Internet Engineering Task Force (IETF) J. Doe 5 5 Request for Comments: 9999 January 2010 6 6 Category: Informational 7 ISSN: 2070-1721 7 8 8 9 … … 15 16 Status of This Memo 16 17 17 This memo provides information for the Internet community. It does 18 not specify an Internet standard of any kind. Distribution of this 19 memo is unlimited. 18 This document is not an Internet Standards Track specification; it is 19 published for informational purposes. 20 21 This document is a product of the Internet Engineering Task Force 22 (IETF). It represents the consensus of the IETF community. It has 23 received public review and has been approved for publication by the 24 Internet Engineering Steering Group (IESG). Not all documents 25 approved by the IESG are a candidate for any level of Internet 26 Standard; see Section 2 of RFC 5741. 27 28 Information about the current status of this document, any errata, 29 and how to provide feedback on it may be obtained at 30 http://www.rfc-editor.org/info/rfc9999. 20 31 21 32 Copyright Notice … … 38 49 Dummy Section. 39 50 51 52 53 54 55 Doe Informational [Page 1] 56 57 58 RFC 9999 IETF Informational w/ consensus January 2010 59 60 40 61 Author's Address 41 62 … … 53 74 54 75 55 Doe Informational [Page 1]56 76 57 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 Doe Informational [Page 2] 113 114 -
rfc2629xslt/samples/sample.ipr.rfc.201001.ietf.inf.nc.txt
r1095 r1103 2 2 3 3 4 Network Working GroupJ. Doe4 Internet Engineering Task Force (IETF) J. Doe 5 5 Request for Comments: 9999 January 2010 6 6 Category: Informational 7 ISSN: 2070-1721 7 8 8 9 … … 15 16 Status of This Memo 16 17 17 This memo provides information for the Internet community. It does 18 not specify an Internet standard of any kind. Distribution of this 19 memo is unlimited. 18 This document is not an Internet Standards Track specification; it is 19 published for informational purposes. 20 21 This document is a product of the Internet Engineering Task Force 22 (IETF). It has been approved for publication by the Internet 23 Engineering Steering Group (IESG). Not all documents approved by the 24 IESG are a candidate for any level of Internet Standard; see Section 25 2 of RFC 5741. 26 27 Information about the current status of this document, any errata, 28 and how to provide feedback on it may be obtained at 29 http://www.rfc-editor.org/info/rfc9999. 20 30 21 31 Copyright Notice … … 38 48 Dummy Section. 39 49 50 51 52 53 54 55 Doe Informational [Page 1] 56 57 58 RFC 9999 IETF Informational w/o consensus January 2010 59 60 40 61 Author's Address 41 62 … … 53 74 54 75 55 Doe Informational [Page 1]56 76 57 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 Doe Informational [Page 2] 113 114 -
rfc2629xslt/samples/sample.ipr.rfc.201001.ietf.std.c.txt
r1095 r1103 2 2 3 3 4 Network Working GroupJ. Doe4 Internet Engineering Task Force (IETF) J. Doe 5 5 Request for Comments: 9999 January 2010 6 6 Category: Standards Track 7 ISSN: 2070-1721 7 8 8 9 … … 15 16 Status of This Memo 16 17 17 This document specifies an Internet standards track protocol for the 18 Internet community, and requests discussion and suggestions for 19 improvements. Please refer to the current edition of the "Internet 20 Official Protocol Standards" (STD 1) for the standardization state 21 and status of this protocol. Distribution of this memo is unlimited. 18 This is an Internet Standards Track document. 19 20 This document is a product of the Internet Engineering Task Force 21 (IETF). It represents the consensus of the IETF community. It has 22 received public review and has been approved for publication by the 23 Internet Engineering Steering Group (IESG). Further information on 24 Internet Standards is available in Section 2 of RFC 5741. 25 26 Information about the current status of this document, any errata, 27 and how to provide feedback on it may be obtained at 28 http://www.rfc-editor.org/info/rfc9999. 22 29 23 30 Copyright Notice … … 40 47 Dummy Section. 41 48 49 50 51 52 53 54 55 Doe Standards Track [Page 1] 56 57 58 RFC 9999 IETF Standards Track w/ consensus January 2010 59 60 42 61 Author's Address 43 62 … … 53 72 54 73 55 Doe Standards Track [Page 1]56 74 57 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 Doe Standards Track [Page 2] 113 114 -
rfc2629xslt/samples/sample.ipr.rfc.201001.ind.exp.txt
r1095 r1103 2 2 3 3 4 Network Working GroupJ. Doe4 Independent Submission J. Doe 5 5 Request for Comments: 9999 January 2010 6 6 Category: Experimental 7 ISSN: 2070-1721 7 8 8 9 … … 15 16 Status of This Memo 16 17 17 This memo defines an Experimental Protocol for the Internet 18 community. It does not specify an Internet standard of any kind. 19 Discussion and suggestions for improvement are requested. 20 Distribution of this memo is unlimited. 18 This document is not an Internet Standards Track specification; it is 19 published for examination, experimental implementation, and 20 evaluation. 21 22 This document defines an Experimental Protocol for the Internet 23 community. This is a contribution to the RFC Series, independently 24 of any other RFC stream. The RFC Editor has chosen to publish this 25 document at its discretion and makes no statement about its value for 26 implementation or deployment. Documents approved for publication by 27 the RFC Editor are not a candidate for any level of Internet 28 Standard; see Section 2 of RFC 5741. 29 30 Information about the current status of this document, any errata, 31 and how to provide feedback on it may be obtained at 32 http://www.rfc-editor.org/info/rfc9999. 21 33 22 34 Copyright Notice … … 35 47 36 48 Dummy Section. 49 50 51 52 53 54 55 Doe Experimental [Page 1] 56 57 58 RFC 9999 Independent Submission Experimental January 2010 59 37 60 38 61 Author's Address … … 53 76 54 77 55 Doe Experimental [Page 1]56 78 57 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 Doe Experimental [Page 2] 113 114 -
rfc2629xslt/samples/sample.ipr.rfc.201001.ind.hist.txt
r1095 r1103 2 2 3 3 4 Network Working GroupJ. Doe4 Independent Submission J. Doe 5 5 Request for Comments: 9999 January 2010 6 6 Category: Historic 7 ISSN: 2070-1721 7 8 8 9 … … 15 16 Status of This Memo 16 17 17 This memo describes a historic protocol for the Internet community. 18 It does not specify an Internet standard of any kind. Distribution 19 of this memo is unlimited. 18 This document is not an Internet Standards Track specification; it is 19 published for the historical record. 20 21 This document defines a Historic Document for the Internet community. 22 This is a contribution to the RFC Series, independently of any other 23 RFC stream. The RFC Editor has chosen to publish this document at 24 its discretion and makes no statement about its value for 25 implementation or deployment. Documents approved for publication by 26 the RFC Editor are not a candidate for any level of Internet 27 Standard; see Section 2 of RFC 5741. 28 29 Information about the current status of this document, any errata, 30 and how to provide feedback on it may be obtained at 31 http://www.rfc-editor.org/info/rfc9999. 20 32 21 33 Copyright Notice … … 34 46 35 47 Dummy Section. 48 49 50 51 52 53 54 55 Doe Historic [Page 1] 56 57 58 RFC 9999 Independent Submission Historic January 2010 59 36 60 37 61 Author's Address … … 53 77 54 78 55 Doe Historic [Page 1]56 79 57 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 Doe Historic [Page 2] 113 114 -
rfc2629xslt/samples/sample.ipr.rfc.201001.ind.inf.txt
r799 r1103 2 2 3 3 4 Network Working GroupJ. Doe4 Independent Submission J. Doe 5 5 Request for Comments: 9999 January 2010 6 6 Category: Informational 7 ISSN: 2070-1721 7 8 8 9 … … 15 16 Status of This Memo 16 17 17 This memo provides information for the Internet community. It does 18 not specify an Internet standard of any kind. Distribution of this 19 memo is unlimited. 18 This document is not an Internet Standards Track specification; it is 19 published for informational purposes. 20 21 This is a contribution to the RFC Series, independently of any other 22 RFC stream. The RFC Editor has chosen to publish this document at 23 its discretion and makes no statement about its value for 24 implementation or deployment. Documents approved for publication by 25 the RFC Editor are not a candidate for any level of Internet 26 Standard; see Section 2 of RFC 5741. 27 28 Information about the current status of this document, any errata, 29 and how to provide feedback on it may be obtained at 30 http://www.rfc-editor.org/info/rfc9999. 20 31 21 32 Copyright Notice … … 34 45 35 46 Dummy Section. 47 48 49 50 51 52 53 54 55 Doe Informational [Page 1] 56 57 58 RFC 9999 Independent Submission Informational January 2010 59 36 60 37 61 Author's Address … … 53 77 54 78 55 Doe Informational [Page 1]56 79 57 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 Doe Informational [Page 2] 113 114 -
rfc2629xslt/samples/sample.ipr.rfc.201001.irtf.exp.c.txt
r1095 r1103 2 2 3 3 4 Network Working GroupJ. Doe4 Internet Research Task Force (IRTF) J. Doe 5 5 Request for Comments: 9999 January 2010 6 6 Category: Experimental 7 ISSN: 2070-1721 7 8 8 9 … … 15 16 Status of This Memo 16 17 17 This memo defines an Experimental Protocol for the Internet 18 community. It does not specify an Internet standard of any kind. 19 Discussion and suggestions for improvement are requested. 20 Distribution of this memo is unlimited. 18 This document is not an Internet Standards Track specification; it is 19 published for examination, experimental implementation, and 20 evaluation. 21 22 This document defines an Experimental Protocol for the Internet 23 community. This document is a product of the Internet Research Task 24 Force (IRTF). The IRTF publishes the results of Internet-related 25 research and development activities. These results might not be 26 suitable for deployment. This RFC represents the consensus of the 27 {insert_name} Research Group of the Internet Research Task Force 28 (IRTF). Documents approved for publication by the IRSG are not a 29 candidate for any level of Internet Standard; see Section 2 of RFC 30 5741. 31 32 Information about the current status of this document, any errata, 33 and how to provide feedback on it may be obtained at 34 http://www.rfc-editor.org/info/rfc9999. 21 35 22 36 Copyright Notice … … 35 49 36 50 Dummy Section. 51 52 53 54 55 Doe Experimental [Page 1] 56 57 58 RFC 9999 IRTF Experimental w/ RG consensus January 2010 59 37 60 38 61 Author's Address … … 53 76 54 77 55 Doe Experimental [Page 1]56 78 57 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 Doe Experimental [Page 2] 113 114 -
rfc2629xslt/samples/sample.ipr.rfc.201001.irtf.exp.nc.txt
r1095 r1103 2 2 3 3 4 Network Working GroupJ. Doe4 Internet Research Task Force (IRTF) J. Doe 5 5 Request for Comments: 9999 January 2010 6 6 Category: Experimental 7 ISSN: 2070-1721 7 8 8 9 … … 15 16 Status of This Memo 16 17 17 This memo defines an Experimental Protocol for the Internet 18 community. It does not specify an Internet standard of any kind. 19 Discussion and suggestions for improvement are requested. 20 Distribution of this memo is unlimited. 18 This document is not an Internet Standards Track specification; it is 19 published for examination, experimental implementation, and 20 evaluation. 21 22 This document defines an Experimental Protocol for the Internet 23 community. This document is a product of the Internet Research Task 24 Force (IRTF). The IRTF publishes the results of Internet-related 25 research and development activities. These results might not be 26 suitable for deployment. This RFC represents the individual 27 opinion(s) of one or more members of the {insert_name} Research Group 28 of the Internet Research Task Force (IRTF). Documents approved for 29 publication by the IRSG are not a candidate for any level of Internet 30 Standard; see Section 2 of RFC 5741. 31 32 Information about the current status of this document, any errata, 33 and how to provide feedback on it may be obtained at 34 http://www.rfc-editor.org/info/rfc9999. 21 35 22 36 Copyright Notice … … 35 49 36 50 Dummy Section. 51 52 53 54 55 Doe Experimental [Page 1] 56 57 58 RFC 9999 IRTF Experimental w/o RG consensus January 2010 59 37 60 38 61 Author's Address … … 53 76 54 77 55 Doe Experimental [Page 1]56 78 57 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 Doe Experimental [Page 2] 113 114 -
rfc2629xslt/samples/sample.ipr.rfc.201001.irtf.exp.norg.txt
r1095 r1103 2 2 3 3 4 Network Working GroupJ. Doe4 Internet Research Task Force (IRTF) J. Doe 5 5 Request for Comments: 9999 January 2010 6 6 Category: Experimental 7 ISSN: 2070-1721 7 8 8 9 … … 15 16 Status of This Memo 16 17 17 This memo defines an Experimental Protocol for the Internet 18 community. It does not specify an Internet standard of any kind. 19 Discussion and suggestions for improvement are requested. 20 Distribution of this memo is unlimited. 18 This document is not an Internet Standards Track specification; it is 19 published for examination, experimental implementation, and 20 evaluation. 21 22 This document defines an Experimental Protocol for the Internet 23 community. This document is a product of the Internet Research Task 24 Force (IRTF). The IRTF publishes the results of Internet-related 25 research and development activities. These results might not be 26 suitable for deployment. Documents approved for publication by the 27 IRSG are not a candidate for any level of Internet Standard; see 28 Section 2 of RFC 5741. 29 30 Information about the current status of this document, any errata, 31 and how to provide feedback on it may be obtained at 32 http://www.rfc-editor.org/info/rfc9999. 21 33 22 34 Copyright Notice … … 35 47 36 48 Dummy Section. 49 50 51 52 53 54 55 Doe Experimental [Page 1] 56 57 58 RFC 9999 IRTF Experimental (no RG) January 2010 59 37 60 38 61 Author's Address … … 53 76 54 77 55 Doe Experimental [Page 1]56 78 57 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 <