Moving RFC7238 (308 Status Code) to Proposed Standard

In Toronto, we discussed moving 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:


Mark Nottingham

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