Changeset 1212

Mar 25, 2011, 2:20:13 AM (8 years ago)

less verbose ticket links

2 edited


  • wg_materials/ietf80/ietf-80-httpbis-changes.xhtml

    r1210 r1212  
    5757    <p><a href="">RFC 2145</a> (Use and Interpretation of HTTP Version Numbers)</p>
    5858    <ul>
    59     <li>RFC2145 Normative (<a href=""></a>)</li>
     59    <li>RFC2145 Normative (<a href="">Ticket 75</a>)</li>
    6060    </ul>
    6161    <p>-> Part 1 now obsoletes RFC 2145</p>
    6363    <p><a href="">RFC 2617</a> (HTTP Authentication: Basic and Digest Access Authentication)</p>
    6464    <ul>
    65     <li>should we have an auth scheme registry (<a href=""></a>)</li>
    66     <li>absorbing the auth framework from 2617 (<a href=""></a>)</li>
     65    <li>should we have an auth scheme registry (<a href="">Ticket 141</a>)</li>
     66    <li>absorbing the auth framework from 2617 (<a href="">Ticket 237</a>)</li>
    6767    </ul>
    6868    <p>-> Part 7 now updates RFC 2617 with respect to the authentication framework,
    7373    <p><a href="">RFC 2817</a> (Upgrading to TLS Within HTTP/1.1)</p>
    7474    <ul>
    75     <li>Migrate Upgrade details from RFC2817 (<a href=""></a>)</li>
    76     <li>Migrate CONNECT from RFC2817 to p2 (<a href=""></a>)</li>
     75    <li>Migrate Upgrade details from RFC2817 (<a href="">Ticket 240</a>)</li>
     76    <li>Migrate CONNECT from RFC2817 to p2 (<a href="">Ticket 239</a>)</li>
    7777    </ul>
    7878    <p>-> Part 1 and 2 now update RFC 2817 (defining CONNECT, and updating the Upgrade header field)</p>
    8080    <h2 class="break">Changes: terminology and ABNF</h2>
    8181    <ul>
    82     <li>Clarify "Requested Variant" (<a href=""></a>)</li>
    83     <li>Clarify entity / representation / variant terminology (<a href=""></a>)</li>
    84     <li>duplicate ABNF for Reason-Phrase (<a href=""></a>) (editorial)</li>
    85     <li>define "transparent" proxy (<a href=""></a>) (editorial)</li>
    86     <li>duplicate ABNF for "Method" (<a href=""></a>) (editorial)</li>
    87     <li>untangle ABNFs for header fields (<a href=""></a>) (editorial)</li>
     82    <li>Clarify "Requested Variant" (<a href="">Ticket 69</a>)</li>
     83    <li>Clarify entity / representation / variant terminology (<a href="">Ticket 109</a>)</li>
     84    <li>duplicate ABNF for Reason-Phrase (<a href="">Ticket 137</a>) (editorial)</li>
     85    <li>define "transparent" proxy (<a href="">Ticket 210</a>) (editorial)</li>
     86    <li>duplicate ABNF for "Method" (<a href="">Ticket 275</a>) (editorial)</li>
     87    <li>untangle ABNFs for header fields (<a href="">Ticket 276</a>) (editorial)</li>
    8888    </ul>
    8989    <p>-> We now create an aggregated ABNF from the source code of the specs</p>
    9191    <h2 class="break">Changes: extension points</h2>
    9292    <ul>
    93     <li>Custom Ranges (<a href=""></a>)</li>
    94     <li>Max-Forwards vs extension methods (<a href=""></a>)</li>
    95     <li>Allowing heuristic caching for new status codes (<a href=""></a>)</li>
    96     <li>proxies not supporting certain methods (<a href=""></a>) (editorial)</li>
    97     <li>Considerations for new status codes (<a href=""></a>)</li>
    98     <li>Considerations for new methods (<a href=""></a>)</li>
    99     <li>Is * usable as a request-uri for new methods? (<a href=""></a>)</li>
     93    <li>Custom Ranges (<a href="">Ticket 85</a>)</li>
     94    <li>Max-Forwards vs extension methods (<a href="">Ticket 203</a>)</li>
     95    <li>Allowing heuristic caching for new status codes (<a href="">Ticket 223</a>)</li>
     96    <li>proxies not supporting certain methods (<a href="">Ticket 226</a>) (editorial)</li>
     97    <li>Considerations for new status codes (<a href="">Ticket 229</a>)</li>
     98    <li>Considerations for new methods (<a href="">Ticket 230</a>)</li>
     99    <li>Is * usable as a request-uri for new methods? (<a href="">Ticket 233</a>)</li>
    100100    </ul>
    102     <h2 class="break">Other Changes (1/6)</h2>
     102    <h2 class="break">Other Changes (1/5)</h2>
    104104    <p>non-specific</p>
    105105    <ul>
    106     <li>205 Bodies (<a href=""></a>)</li>
    107     <li>HTTP(s) URI scheme definitions (<a href=""></a>)</li>
    108     <li>Note special status of Content-* prefix in header registration procedures (<a href=""></a>) (editorial)</li>
    109     <li>Status codes and caching (<a href=""></a>)</li>
    110     <li>Header Classification (<a href=""></a>)</li>
     106    <li>205 Bodies (<a href="">Ticket 88</a>)</li>
     107    <li>HTTP(s) URI scheme definitions (<a href="">Ticket 159</a>)</li>
     108    <li>Note special status of Content-* prefix in header registration procedures (<a href="">Ticket 180</a>) (editorial)</li>
     109    <li>Status codes and caching (<a href="">Ticket 199</a>)</li>
     110    <li>Header Classification (<a href="">Ticket 224</a>)</li>
    111111    </ul>
    113     <h2 class="break">Other Changes (2/6)</h2>
     113    <h2 class="break">Other Changes (2/5)</h2>
    115115    <p>Part 1 (Messaging)</p>
    116116    <ul>
    117     <li>Delimiting messages with multipart/byteranges (<a href=""></a>)</li>
    118     <li>Trailer requirements (<a href=""></a>)</li>
    119     <li>What is the value space of HTTP status codes? (<a href=""></a>)</li>
    120     <li>confusing Date requirements for clients (<a href=""></a>)</li>
     117    <li>Delimiting messages with multipart/byteranges (<a href="">Ticket 90</a>)</li>
     118    <li>Trailer requirements (<a href="">Ticket 193</a>)</li>
     119    <li>What is the value space of HTTP status codes? (<a href="">Ticket 213</a>)</li>
     120    <li>confusing Date requirements for clients (<a href="">Ticket 248</a>)</li>
    121121    </ul>
    123     <h2 class="break">Other Changes (3/6)</h2>
     123    <h2 class="break">Other Changes (3/5)</h2>
    125125    <p>Part 2 (Semantics)</p>
    126126    <ul>
    127     <li>Connection closing (<a href=""></a>) (editorial)</li>
    128     <li>Fragment combination / precedence during redirects (<a href=""></a>)</li>
    129     <li>Content-* vs. PUT (<a href=""></a>)</li>
    130     <li>Understanding Content-* on non-PUT requests (<a href=""></a>)</li>
    131     <li>Monitoring connections (<a href=""></a>) (editorial)</li>
    132     <li>Methods and Caching (<a href=""></a>)</li>
     127    <li>Connection closing (<a href="">Ticket 28</a>) (editorial)</li>
     128    <li>Fragment combination / precedence during redirects (<a href="">Ticket 43</a>)</li>
     129    <li>Content-* vs. PUT (<a href="">Ticket 79</a>)</li>
     130    <li>Understanding Content-* on non-PUT requests (<a href="">Ticket 102</a>)</li>
     131    <li>Monitoring connections (<a href="">Ticket 108</a>) (editorial)</li>
     132    <li>Methods and Caching (<a href="">Ticket 139</a>)</li>
     133    <li>Are OPTIONS and TRACE safe? (<a href="">Ticket 171</a>)</li>
     134    <li>User-Agent guidelines (<a href="">Ticket 232</a>)</li>
     135    <li>clarify PUT semantics (<a href="">Ticket 267</a>)</li>
    133136    </ul>
    135     <h2 class="break">Other Changes (4/6)</h2>
    137     <p>Part 2 (Semantics)</p>
    138     <ul>
    139     <li>Are OPTIONS and TRACE safe? (<a href=""></a>)</li>
    140     <li>User-Agent guidelines (<a href=""></a>)</li>
    141     <li>clarify PUT semantics (<a href=""></a>)</li>
    142     </ul>
     138    <h2 class="break">Other Changes (4/5)</h2>
    144140    <p>Part 3 (Payload)</p>
    145141    <ul>
    146     <li>confusing req. language for Content-Location (<a href=""></a>) (editorial)</li>
    147     <li>"requested resource" in content-encoding definition (<a href=""></a>)</li>
     142    <li>confusing req. language for Content-Location (<a href="">Ticket 136</a>) (editorial)</li>
     143    <li>"requested resource" in content-encoding definition (<a href="">Ticket 183</a>)</li>
    148144    </ul>
    150     <h2 class="break">Other Changes (5/6)</h2>
    152146    <p>Part 5 (Range)</p>
    153147    <ul>
    154     <li>Caches can't be required to serve ranges (<a href=""></a>)</li>
     148    <li>Caches can't be required to serve ranges (<a href="">Ticket 217</a>)</li>
    155149    </ul>
     151    <h2 class="break">Other Changes (5/5)</h2>
    157153    <p>Part 6 (Cache)</p>
    158154    <ul>
    159     <li>No-cache definition (<a href=""></a>)</li>
    160     <li>Does no-store in request imply no-cache? (<a href=""></a>)</li>
    161     <li>Clarify "public" (<a href=""></a>)</li>
     155    <li>No-cache definition (<a href="">Ticket 216</a>)</li>
     156    <li>Does no-store in request imply no-cache? (<a href="">Ticket 249</a>)</li>
     157    <li>Clarify "public" (<a href="">Ticket 268</a>)</li>
    162158    </ul>
    164     <h2 class="break">Other Changes (6/6)</h2>
    166160    <p>Part 7 (Auth)</p>
    167161    <ul>
    168     <li>auth-param syntax (<a href=""></a>)</li>
     162    <li>auth-param syntax (<a href="">Ticket 195</a>)</li>
    169163    </ul>
    171165    <h2 class="break">Changes: housekeeping</h2>
    172166    <ul>
    173     <li>MIME-Version not listed in P1, general header fields (<a href=""></a>) (editorial)</li>
    174     <li>Factor out Content-Disposition (<a href=""></a>)</li>
    175     <li>introduction to part 7 is work-in-progress (<a href=""></a>) (editorial)</li>
    176     <li>consider removing the "changes from 2068" sections (<a href=""></a>) (editorial)</li>
    177     <li>update RFC 2109 reference (<a href=""></a>) (editorial)</li>
     167    <li>MIME-Version not listed in P1, general header fields (<a href="">Ticket 122</a>) (editorial)</li>
     168    <li>Factor out Content-Disposition (<a href="">Ticket 123</a>)</li>
     169    <li>introduction to part 7 is work-in-progress (<a href="">Ticket 130</a>) (editorial)</li>
     170    <li>consider removing the "changes from 2068" sections (<a href="">Ticket 220</a>) (editorial)</li>
     171    <li>update RFC 2109 reference (<a href="">Ticket 279</a>) (editorial)</li>
    178172    </ul>
Note: See TracChangeset for help on using the changeset viewer.