Re: Consensus call to include Display Strings in draft-ietf-httpbis-sfbis

["Martin J. Dürst" <[e-mail]>]

I support this proposal, with or without minor or medium changes (e.g. 
according to the lines proposed by Roy).

The possibility for HTTP headers to include non-ASCII characters, e.g. 
in what's now called display strings, has been envisioned from the start 
of HTTP; the only problem is that at that very early time, ISO-8859-1 
was available but Unicode/UTF-8 was not.

In my work at the W3C Team and in my participation in the IETF, I have 
come across then need for something like display strings occasionally, 
but consistently. This need does not go away by denying it.

If there were another batch of additions planned for structured field 
values, it might be possible to move this addition to that batch, but as 
far as I'm aware of, there is not really any such batch, and therefore, 
it is highly advisable to include this addition now.

There are several technical details I plan to comment on, but I will do 
that in separate mails.

Regards,   Martin.

On 2023-05-25 11:26, Tommy Pauly wrote:
> Hello HTTP WG,
> 
> As part of the WGLC for draft-ietf-httpbis-sfbis, we’ve been discussing the inclusion of "Display Strings” (strings that allow Unicode content).
> 
> While not part of the initial scope of this -bis effort, this addition has had significant discussion and support expressed for inclusion.
> 
> This email starts a formal consensus call to determine if the working group would like to expand the scope of draft-ietf-httpbis-sfbis to include Display Strings, specifically to merge in the following pull request (modulo any editorial changes that are needed):
> 
> https://github.com/httpwg/http-extensions/pull/2494
> 
> Please reply to this email to express your opinion on this issue by Wednesday, June 7.
> 
> Thanks,
> Tommy
> 
>