#517 closed editorial (incorporated)
move IANA registrations to correct draft
Reported by: | julian.reschke@… | Owned by: | draft-ietf-httpbis-p2-semantics@… |
---|---|---|---|
Priority: | normal | Milestone: | 25 |
Component: | non-specific | Severity: | In IETF LC |
Keywords: | Cc: |
Description
IANA about <http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p2-semantics-24.html#content.coding.registry>:
"NOTE: several entries that are part of the fourth action (Content-Coding registrations) have draft-ietf-httpbis-p1-messaging as their reference. If we're to update those entries with an RFC number once draft-ietf-httpbis-p1-messaging has been assigned one, these entries need to be requested in the IANA Considerations section for draft-ietf-httpbis-p1-messaging, rather than this document. We have no other mechanism to ensure that reference updates aren't overlooked."
Change History (3)
comment:1 Changed 9 years ago by julian.reschke@…
comment:2 Changed 9 years ago by julian.reschke@…
- Component changed from p2-semantics to non-specific
- Milestone changed from unassigned to 25
- Resolution set to incorporated
- Status changed from new to closed
comment:3 Changed 9 years ago by julian.reschke@…
- Severity changed from In WG Last Call to In IETF LC
Note: See
TracTickets for help on using
tickets.
From [2462]:
move most content coding registrations to part 1 (see #517)