Opened 12 years ago

Closed 11 years ago

Last modified 11 years ago

#97 closed editorial (fixed)

Move registrations and registry information to IANA Considerations

Reported by: fielding@… Owned by: julian.reschke@…
Priority: Milestone: 04
Component: p1-messaging Severity:
Keywords: Cc:

Description

Since we are required to have an IANA Considerations section, it should be used to house the type registrations and other documented registries (as opposed to leaving them in appendices).

This should be done during the next set of reorg changes.

Change History (5)

comment:1 Changed 11 years ago by julian.reschke@…

Can we make this a bit more specific?

We didn't have registrations for headers (#40) and status codes (#59) so far; they have been added now ([253] and [255]).

The method registry is still a TODO (#72).

So is this just about the MIME type registrations (Part1, Appendix A, and Part5, Appendix A)?

comment:2 Changed 11 years ago by julian.reschke@…

  • Milestone changed from 03 to 04

comment:3 Changed 11 years ago by julian.reschke@…

  • Component changed from non-specific to p1-messaging
  • Owner set to julian.reschke@…

Move Appendix A into the IANA considerations.

comment:4 Changed 11 years ago by julian.reschke@…

  • Resolution set to fixed
  • Status changed from new to closed

Fixed in [296]:

Resolve #97: Move media type registrations into IANA considerations section (closes #97).

comment:5 Changed 11 years ago by julian.reschke@…

From [299]:

Re-gen HTML due to reference target having been moved (related to #97).

Note: See TracTickets for help on using tickets.