Changeset 1567 for draft-ietf-httpbis/latest/p1-messaging.xml
- Timestamp:
- 08/03/12 10:01:34 (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.xml
r1566 r1567 2392 2392 </t> 2393 2393 <t> 2394 Values to be added to this name space require a specification2395 (see "Specification Required" in<xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST;2394 Values to be added to this name space require IETF Review (see 2395 <xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST; 2396 2396 conform to the purpose of transfer coding defined in this section. 2397 2397 </t> … … 3322 3322 </t> 3323 3323 <t> 3324 Registrations are allowed on a First Come First Served basis as 3325 described in <xref target="RFC5226" x:sec="4.1" x:fmt="of"/>. The 3326 specifications need not be IETF documents or be subject to IESG review. 3327 Registrations are subject to the following rules: 3324 Registrations require IETF Review (see 3325 <xref target="RFC5226" x:sec="4.1" x:fmt="of"/>) and are subject to the 3326 following rules: 3328 3327 <list style="numbers"> 3329 3328 <t>A protocol-name token, once registered, stays registered forever.</t> … … 5007 5006 </t> 5008 5007 <t> 5008 Registration of Transfer Codings now requires IETF Review 5009 (<xref target="transfer.coding.registry"/>) 5010 </t> 5011 <t> 5009 5012 Remove hard limit of two connections per server. 5010 5013 Remove requirement to retry a sequence of requests as long it was idempotent. … … 5030 5033 101 (this was incorporated from <xref target="RFC2817"/>). 5031 5034 (<xref target="header.upgrade"/>) 5035 </t> 5036 </section> 5037 5038 <section title="Changes from RFC 2817" anchor="changes.from.rfc.2817"> 5039 <t> 5040 Registration of Upgrade tokens now requires IETF Review 5041 (<xref target="upgrade.token.registry"/>) 5032 5042 </t> 5033 5043 </section> … … 5937 5947 "chunk-extensions" 5938 5948 </t> 5949 <t> 5950 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/346"/>: 5951 "make IANA policy definitions consistent" 5952 </t> 5939 5953 </list> 5940 5954 </t>
Note: See TracChangeset
for help on using the changeset viewer.