Re: Structured Fields: whitespace in binary content

On Wed, Oct 28, 2020 at 6:28 PM Mark Nottingham <mnot@mnot.net> wrote:

>
> So, the obvious fix is to allow whitespace inside binary content.
> Delimitation won't be lost, because it's ":" on both ends. The base64
> parsers I checked already swallow whitespace in input (not surprising since
> the motivating use case for base64 was line-wrapped MIME).
>
> The question is whether it's too late to do this. Personally I think it's
> worth it; otherwise we're going to have some pretty confusing specs, and
> that's likely to lead to problems. Also, the delta to the spec and
> implementations is very small. Also, if there's some implementation lag I
> think that's workable, because this is less likely to be seen on the wire,
> and there aren't too many adopters of binary content yet.
>
> What do folks think? I'll start a PR to show what it'd be like, but I
> wanted to get early impressions ASAP.
>
> Thanks (and sorry for not seeing this earlier),
>
> --
> Mark Nottingham   https://www.mnot.net/
>
>
>
My instinct is that it's too substantial to skip both last-calls, but I'm
interested to see the diff anyway.

Cheers
-- 
  Matthew Kerwin
  https://matthew.kerwin.net.au/