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

Ticket #274 (closed design: fixed)

Opened 4 years ago

Last modified 3 years ago

warn-code registry

Reported by: mnot@pobox.com Owned by: mnot@pobox.com
Priority: normal Milestone: 18
Component: p6-cache Severity: Active WG Document
Keywords: Cc:
Origin: draft-yevstifeyev-httpbis-http-warning-registry

Description

Do we need to establish an IANA registry for warn-codes? Note that they are no longer required to be implemented.

Change History

comment:1 Changed 3 years ago by mnot@pobox.com

  • Owner set to mnot@pobox.com

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

  • Status changed from new to closed
  • Resolution set to incorporated
  • Milestone changed from unassigned to 18

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

From [1487]:

Editorial: make IANA table handling consistent between warn codes and status codes (this includes giving each warn code a subsection to be referenced) (see #274)

comment:4 Changed 3 years ago by mnot@pobox.com

  • Status changed from closed to reopened
  • Resolution incorporated deleted

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

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