Opened 10 years ago

Closed 10 years ago

#188 closed design (fixed)

pick IANA policy (RFC5226) for Transfer Coding / Content Coding

Reported by: julian.reschke@… Owned by: julian.reschke@…
Priority: urgent Milestone: 08
Component: non-specific Severity: Active WG Document
Keywords: Cc:

Description

The updated IANA registration procedures should pick an RFC5226-defined policy.

Change History (6)

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

  • Priority changed from normal to urgent

Proposal: expert review & specification required.

comment:2 Changed 10 years ago by mnot@…

General agreement in room at Stockholm WG meeting that expert review / spec required is appropriate for most registries, including this (while some like method and status code may need a higher bar).

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

  • Owner set to julian.reschke@…
  • Status changed from new to assigned

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

From [670]:

Rephrase registration procedures for Transfer/Content? Codings in terms of RFC5226, requiring Expert Review & Specification (see #188)

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

From [671]:

Use consistent names in IANA registration tables (see #188)

comment:6 Changed 10 years ago by mnot@…

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.