Opened 14 years ago
Closed 13 years ago
#149 closed editorial (fixed)
update IANA requirements wrt Content-Coding values
Reported by: | julian.reschke@… | Owned by: | julian.reschke@… |
---|---|---|---|
Priority: | urgent | Milestone: | 10 |
Component: | p3-payload | Severity: | Active WG Document |
Keywords: | Cc: |
Description
We should clarify the exact registration requirements for Content-Codings (in terms of RFC5226), and add a section to the IANA Considerations section updating the existing registry.
Change History (9)
comment:1 Changed 14 years ago by julian.reschke@…
- Type changed from design to editorial
comment:2 Changed 14 years ago by julian.reschke@…
- Owner set to julian.reschke@…
- Priority set to normal
- Status changed from new to assigned
comment:3 Changed 14 years ago by julian.reschke@…
comment:4 Changed 13 years ago by julian.reschke@…
- Milestone changed from unassigned to 08
comment:5 Changed 13 years ago by julian.reschke@…
- Milestone changed from 08 to 09
comment:6 Changed 13 years ago by julian.reschke@…
- Milestone changed from 09 to 10
comment:7 Changed 13 years ago by julian.reschke@…
- Priority changed from normal to urgent
comment:8 Changed 13 years ago by julian.reschke@…
This ticket can be closed; both changes have been implemented a few drafts ago.
comment:9 Changed 13 years ago by julian.reschke@…
- Resolution set to fixed
- Status changed from assigned to closed
Note: See
TracTickets for help on using
tickets.
From [668]:
Add IANA considerations sub section for content codings (see #149)