Re: Issue 271 of 5987bis - Proposed Standard or Internet Standard?

[Mark Nottingham <[e-mail]>]

Personal hat -

I'd prefer Proposed Standard; I don't think we want to overly promote the use of this encoding in new header fields, so calling it an Internet Standard sends the wrong message. 

In particular, if we do come up with a better solution, there will be that awkward phase (perhaps years) when this one will be full standard, and the "better" one will be only Proposed.

Finally, I don't think it meets the criteria in 2026.

I'm not lie-down-in-the-road against this (they're just words, after all); just a preference.

Cheers,


> On 13 Jan 2017, at 9:10 am, Patrick McManus <[e-mail]> wrote:
> 
> Gentlefolk of the HTTPbis WG -
> 
> I need to direct your attention to one of just two open issues with the 5987bis document (Indicating Character Encoding and Language for HTTP Header Field Parameters), which deals with the intended status of the eventual RFC. The consensus of the WG is sought.
> 
> https://github.com/httpwg/http-extensions/issues/271
> The intended status of this document is currently listed as "Internet Standard" ( https://datatracker.ietf.org/doc/draft-ietf-httpbis-rfc5987bis/ )
> 
> The other practical status for standards track documents is proposed standard  - its laid out here https://www.ietf.org/rfc/rfc2026.txt and also in https://www.rfc-editor.org/rfc/rfc6410.txt
> 
> The basic guidance is:
> 
>       An Internet Standard is characterized by a high degree of
>       technical maturity and by a generally held belief that the
>       specified protocol or service provides significant benefit to the
>       Internet community.
> 
> A list of the ~100 active documents currently bearing STD status can be found here https://www.rfc-editor.org/standards#IS
> I apologize to Julian for not starting this thread earlier, I procrastinated long enough that we got into the holiday season and then I decided to defer until everyone's attention returned to work.
> 
> Thanks for your input.
> -Patrick, chair-hat on

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