Opened 7 years ago

Closed 6 years ago

#404 closed design (fixed)

Tentative Status Codes

Reported by: mnot@… Owned by:
Priority: normal Milestone: 22
Component: p2-semantics Severity: In WG Last Call
Keywords: Cc:

Description

One of the things that has bothered me for a while is that status codes are a scarce resource, and making a "I have an idea" proposal effectively consumes one, at least for a while.

E.g., my proposal for 430 Would Block in draft-nottingham-http-pipeline had us using 431 for Request Header Fields Too Large, even though 430 might not see the light of day.

I think we might improve this by adding something like:

""" Proposals for new status codes that are not yet widely deployed SHOULD NOT specify a specific code until there is clear consensus to register it; instead, early drafts can use notation such as "4xx" to indicate the class of the proposed status code, without consuming one prematurely. """

to <https://svn.tools.ietf.org/svn/wg/httpbis/draft-ietf-httpbis/latest/p2-semantics.html#considerations.for.new.status.codes>.

Change History (6)

comment:1 Changed 7 years ago by mnot@…

  • Milestone changed from unassigned to 22

Didn't seem to be any pushback on-list; marking for -22.

comment:2 Changed 7 years ago by mnot@…

  • Owner draft-ietf-httpbis-p2-semantics@… deleted

comment:3 Changed 7 years ago by fielding@…

From [2085]:

(editorial) Suggest that proposals for new status codes use a pseudonym like 4NN until there is consensus for registration; addresses #404

comment:4 Changed 7 years ago by fielding@…

  • Resolution set to incorporated
  • Status changed from new to closed

comment:5 Changed 6 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:6 Changed 6 years ago by mnot@…

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