* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #188 (closed design: fixed)

Opened 5 years ago

Last modified 5 years ago

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

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

Description

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

Change History

comment:1 Changed 5 years ago by julian.reschke@gmx.de

  • Priority changed from normal to urgent

Proposal: expert review & specification required.

comment:2 Changed 5 years ago by mnot@pobox.com

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 5 years ago by julian.reschke@gmx.de

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

comment:4 Changed 5 years ago by julian.reschke@gmx.de

From [670]:

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

comment:5 Changed 5 years ago by julian.reschke@gmx.de

From [671]:

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

comment:6 Changed 5 years ago by mnot@pobox.com

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