Moving RFC7238 (308 Status Code) to Proposed Standard

In Toronto, we discussed moving RFC7238 <http://tools.ietf.org/html/rfc7238> from Experimental to Proposed Standard, now that it is implemented in most browsers.

The WG in the room seemed to think that doing so is a good idea; anyone here have a reason to believe otherwise?

See also:
  https://datatracker.ietf.org/doc/status-change-http-status-code-308-ps/

Cheers,

--
Mark Nottingham   https://www.mnot.net/

Received on Monday, 28 July 2014 02:40:43 UTC

Follow Lee on X/Twitter - Father, Husband, Serial builder creating AI, crypto, games & web tools. We are friends :) AI Will Come To Life!

Check out: eBank.nz (Art Generator) | Netwrck.com (AI Tools) | Text-Generator.io (AI API) | BitBank.nz (Crypto AI) | ReadingTime (Kids Reading) | RewordGame | BigMultiplayerChess | WebFiddle | How.nz | Helix AI Assistant