Jan 11, 2008, 6:21:34 PM (12 years ago)

editorial: write preliminary introduction to p3 noting future reorg

1 edited


  • draft-ietf-httpbis/latest/p3-payload.html

    r157 r161  
    565565      </ul>
    566566      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
    567       <p id="rfc.section.1.p.1">This document will define aspects of HTTP related to the payload of messages (message content), including metadata and media
    568          types, along with HTTP content negotiation. Right now it only includes the extracted relevant sections of RFC 2616 without
    569          edit.
     567      <p id="rfc.section.1.p.1">This document defines HTTP message payloads (a.k.a., content), the associated metadata header fields that define how the payload
     568         is intended to be interpreted by a recipient, the request header fields that may influence content selection, and the various
     569         selection algorithms that are collectively referred to as HTTP content negotiation.
     570      </p>
     571      <p id="rfc.section.1.p.2">This document is currently disorganized in order to minimize the changes between drafts and enable reviewers to see the smaller
     572         errata changes. The next draft will reorganize the sections to better reflect the content. In particular, the sections on
     573         entities will be renamed payload and moved to the first half of the document, while the sections on content negotiation and
     574         associated request header fields will be moved to the second half. The current mess reflects how widely dispersed these topics
     575         and associated requirements had become in <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
    570576      </p>
    571577      <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="intro.requirements" href="#intro.requirements">Requirements</a></h2>
    14771483      <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;Since RFC2616
    14781484      </h2>
    1479       <p id="rfc.section.D.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
     1485      <p id="rfc.section.D.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
    14801486      </p>
    14811487      <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a>&nbsp;Since draft-ietf-httpbis-p3-payload-00
    16941700                  <li class="indline1"><em>RFC2388</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2388.1">2.3.2</a>, <a class="iref" href="#RFC2388"><b>9.2</b></a></li>
    16951701                  <li class="indline1"><em>RFC2557</em>&nbsp;&nbsp;<a class="iref" href="#RFC2557"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2557.1">A.6</a>, <a class="iref" href="#rfc.xref.RFC2557.2">C.1</a></li>
    1696                   <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#RFC2616"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.1">D.1</a></li>
     1702                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#RFC2616"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2">D.1</a></li>
    16971703                  <li class="indline1"><em>RFC2822</em>&nbsp;&nbsp;<a class="iref" href="#RFC2822"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2822.1">A</a></li>
    16981704                  <li class="indline1"><em>RFC3629</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3629.1">2.1</a>, <a class="iref" href="#RFC3629"><b>9.2</b></a></li>
Note: See TracChangeset for help on using the changeset viewer.