Opened 15 years ago
Closed 15 years ago
#59 closed editorial (fixed)
Status Code Registry
Reported by: | mnot@… | Owned by: | julian.reschke@… |
---|---|---|---|
Priority: | Milestone: | 03 | |
Component: | p2-semantics | Severity: | |
Keywords: | Cc: |
Description
The IANA status code registry should be referred to.
Attachments (2)
Change History (10)
comment:1 Changed 15 years ago by mnot@…
- Component set to non-specific
- Milestone set to unassigned
comment:2 Changed 15 years ago by fielding@…
- Milestone changed from unassigned to 02
comment:3 Changed 15 years ago by mnot@…
- Milestone changed from 02 to 03
comment:4 Changed 15 years ago by julian.reschke@…
- Component changed from non-specific to p2-semantics
- Owner set to julian.reschke@…
comment:5 Changed 15 years ago by julian.reschke@…
comment:6 Changed 15 years ago by julian.reschke@…
I think we should also take over the registration procedure, obsoleting RFC2817, Section 7.1.
comment:7 Changed 15 years ago by julian.reschke@…
Note: See
TracTickets for help on using
tickets.
From [255]:
Add IANA re-registration of status codes, referencing RFC 2817; todo: consider taking over the registry procedure (related to #59)