Ticket #180 (closed editorial: fixed)
Note special status of Content-* prefix in header field registration procedures
|Reported by:||firstname.lastname@example.org||Owned by:|
|Component:||non-specific||Severity:||Active WG Document|
As per #103, header fields whose name starts with 'content-' have special meaning, placing additional requirements upon implementations. This needs to be noted in the registration procedures, for the information of IANA, the IESG and any expert reviewer.
Note that the resolution of #104 may obviate this.
- Priority set to normal
- Status changed from new to closed
- Resolution set to fixed
- Milestone changed from unassigned to 11