Re: [openpgp] I-D Action: draft-ietf-openpgp-crypto-refresh-01.txt

[Guillem Jover <[e-mail]>]

On Mon, 2021-02-08 at 10:50:02 +0000, Andrew Gallagher wrote:
> On 07/02/2021 10:25, Peter Gutmann wrote:
> > Heiko Stamer <[e-mail]> writes:
> > 
> > > For spaces and tabs the intention is clear for me, however, I am not sure
> > > about carriage returns in general. According to Unicode Character Database
> > > there are some other whitespace characters, e.g., form feed (0x0c). Should
> > > such characters be included, too?
> > 
> > That also just seems wrong in general, the last major OS type I know of that
> > used CR delimiters was Mac OS from 1984.  Shouldn't this be LF or CRLF?
> > Wherever this came from, it's not in 4880, or any other common RFC that
> > defines a format for blank lines.
> 
> It reads to me like this change is intended to cover a "blank line" of
> assorted spaces and tabs, with an optional trailing carriage return before
> the line feed delimiter. The admission of carriage returns elsewhere in the
> whitespace sequence is surely unintentional.

Yes this was the intention, as prompted by:

  <https://git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=aea291e3db1ac0414dcf005a0a607e78bdd77a5e>

The original MR:

  <https://gitlab.com/openpgp-wg/rfc4880bis/-/merge_requests/6>

> Note that the similar definition of "trailing white space" on line 69 should
> be kept consistent with that of "blank line".

Ah probably missed that one.

Thanks,
Guillem