- From: Alexey Melnikov <alexey.melnikov@isode.com>
- Date: Wed, 14 Dec 2016 09:59:52 +0000
- To: Poul-Henning Kamp <phk@phk.freebsd.dk>, Matthew Kerwin <matthew@kerwin.net.au>
- Cc: Kari Hurtta <hurtta-ietf@elmme-mailer.org>, Ilari Liusvaara <ilariliusvaara@welho.com>, HTTP working group mailing list <ietf-http-wg@w3.org>, Poul-Henning Kamp <phk@varnish-cache.org>
On 14/12/2016 09:21, Poul-Henning Kamp wrote: > -------- > In message <CACweHNDKgWQewZHb=Kz3_2=41M58sY5472Q5OwpqPLxorvkzHQ@mail.gmail.com> > , Matthew Kerwin writes: > >> If we're looking for inspiration elsewhere, why not C99? >> >> "\" %x75 1*4HEXDIG >> / "\" %x55 1*6HEXDIG ; C99 accepts 1*8 > The variable length means these run into the mess of "what if the > next character is a hex digit?". > > That's a much bigger issue when we're talking about code spitting > out strings than when it is programmers typing them in. > > I would prefer to make them fixed length: > > "\" "u" 4HEXDIG > "\" "U" 6HEXDIG IETF has published BCP 137, which should be followed, unless there is a very good reason not to: https://www.rfc-editor.org/bcp/bcp137.txt See section 5.1.
Received on Wednesday, 14 December 2016 10:00:43 UTC