Changeset 2047 for draft-ietf-httpbis/latest/p2-semantics.xml
- Timestamp:
- 09/12/12 16:54:07 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r2046 r2047 380 380 </artwork></figure> 381 381 <t> 382 Media-type values are registered with the Internet Assigned Number 383 Authority (IANA). The media type registration process is 384 outlined in <xref target="BCP13"/>. Use of non-registered media types is 385 discouraged. 382 Internet media types ought to be registered with IANA according to the 383 procedures defined in <xref target="BCP13"/>. 386 384 </t> 387 385 </section> … … 398 396 </artwork></figure> 399 397 <t> 400 TheIANA Character Set registry398 Charset names ought to be registered in IANA Character Set registry 401 399 (<eref target="http://www.iana.org/assignments/character-sets"/>) 402 maintains the set of tokens registered for use on the Internet as 403 charset names <xref target="RFC2978"/>. 400 according to the procedures defined in <xref target="RFC2978"/>. 404 401 </t> 405 402 </section> … … 526 523 used to allow a representation to be compressed or otherwise usefully 527 524 transformed without losing the identity of its underlying media type 528 and without loss of information. Frequently, the representation is stored in529 coded form, transmitted directly, and only decoded by the recipient.525 and without loss of information. Frequently, the representation is stored 526 in coded form, transmitted directly, and only decoded by the recipient. 530 527 </t> 531 528 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="content-coding"/> … … 533 530 </artwork></figure> 534 531 <t> 535 All content-coding values are case-insensitive and &SHOULD;be registered532 All content-coding values are case-insensitive and ought to be registered 536 533 within the HTTP Content Coding registry, as defined in 537 534 <xref target="content.coding.registry"/>. They are used in the … … 1174 1171 <t> 1175 1172 Additional methods &MAY; be used in HTTP; many have already been 1176 standardized outside the scope of this specification and registered1177 within the HTTP Method Registry maintained by IANA, as defined in1178 <xref target="method.registry"/>.1173 standardized outside the scope of this specification and ought to be 1174 registered within the HTTP Method Registry maintained by IANA, as defined 1175 in <xref target="method.registry"/>. 1179 1176 </t> 1180 1177 <t> … … 4345 4342 <t> 4346 4343 The requirements for header field names are defined in 4347 <xref target="BCP90"/>. Authors of specifications 4348 defining new fields are advised to keep the name as short as practical, and 4349 not to prefix them with "X-" if they are to be registered (either 4350 immediately or in the future). 4344 <xref target="BCP90"/>. Authors of specifications defining new fields are 4345 advised to keep the name as short as practical and to not prefix the name 4346 with "X-" unless the header field will never be used on the Internet. 4347 (The "x-" prefix idiom has been extensively misused in practice; it was 4348 intended to only be used as a mechanism for avoiding name collisions inside 4349 proprietary software or intranet processing, since the prefix would ensure 4350 that private names never collide with a newly registered Internet name.) 4351 4351 </t> 4352 4352 <t>
Note: See TracChangeset
for help on using the changeset viewer.