![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Opened 9 years ago
Closed 7 years ago
#274 closed design (fixed)
warn-code registry
| Reported by: | mnot@… | Owned by: | mnot@… |
|---|---|---|---|
| Priority: | normal | Milestone: | 18 |
| Component: | p6-cache | Severity: | Active WG Document |
| Keywords: | Cc: |
Description
Do we need to establish an IANA registry for warn-codes? Note that they are no longer required to be implemented.
Change History (5)
comment:1 Changed 8 years ago by mnot@…
- Owner set to mnot@…
comment:2 Changed 8 years ago by mnot@…
- Milestone changed from unassigned to 18
- Resolution set to incorporated
- Status changed from new to closed
comment:3 Changed 8 years ago by julian.reschke@…
comment:4 Changed 7 years ago by mnot@…
- Resolution incorporated deleted
- Status changed from closed to reopened
comment:5 Changed 7 years ago by mnot@…
- Resolution set to fixed
- Status changed from reopened to closed
Note: See
TracTickets for help on using
tickets.
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)