Mark Nottingham wrote: >> B. Status Codes: <http://www.tools.ietf.org/wg/httpbis/trac/ticket/40> >> >> I have added instructions to update the status code registry in P2. >> >> Question: >> >> 3) The current status code registration procedure is hiding in a >> really obscure place >> (<http://tools.ietf.org/html/rfc2817#section-7.1>), should Part 2 take >> over (me thinks yes). Should we keep the registration requirements >> (IETF standards track)? > > Yes and yes. > ... Proposed patch: <http://www3.tools.ietf.org/wg/httpbis/trac/attachment/ticket/59/i59.diff>. This copies RFC2817's reg. procedure into P2, Section 5 ("Status Code and Reason Phrase"), and updates the IANA Considerations and the Change Log accordingly. BR, JulianReceived on Monday, 9 June 2008 16:33:18 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:38:31 GMT