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

Guillem Jover <guillem@hadrons.org> Thu, 11 February 2021 15:51 UTC

Return-Path: <guillem@hadrons.org>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E61A93A16D8 for <openpgp@ietfa.amsl.com>; Thu, 11 Feb 2021 07:51:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.116
X-Spam-Level:
X-Spam-Status: No, score=-1.116 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, PDS_RDNS_DYNAMIC_FP=0.001, RCVD_IN_SORBS_DUL=0.001, RDNS_DYNAMIC=0.982, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hadrons.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zv2v6d1PwRqL for <openpgp@ietfa.amsl.com>; Thu, 11 Feb 2021 07:51:14 -0800 (PST)
Received: from pulsar.hadrons.org (2.152.178.181.dyn.user.ono.com [2.152.178.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8190F3A16D7 for <openpgp@ietf.org>; Thu, 11 Feb 2021 07:51:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=hadrons.org ; s=201908; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:From:Reply-To:Subject:Content-Transfer-Encoding: Content-ID:Content-Description:X-Debbugs-Cc; bh=fgfPSRenZWQGlBoCIRz+3Y5a8dbr0/V2J8KzMOM4Bqo=; b=AdXfi2+tKWdLQY368tPLqi7Qti 4h8l3MBtza31pbRX9nKND7WHcj1cdwp7iIbknU5M92n0mAWlxVVuxEc/qTAPV5QU2nshV/pOrvS+R EJEJhAFzXPsRrU7cbXBCqHCpjf+xllKIHCMqbvveeisot/dop3paRoTwQXG8wnSgACc6P/Ylq9Ml3 ZydAzjyZUDsAeM0QUkLSP9hNddWbERPLI+GKw15NIOmfSlOEOYihSz4+J5cFNSxzN05dp+fUgwaEy I1D/HjyVVB0qGlW+vo67ysu76TScDaYXbmW1rylw6IF0Gw2oLea1QtTvGwoaX7xjO9xRxClpq78tn jiSxNjDw==;
Received: from guillem by pulsar.hadrons.org with local (Exim 4.92) (envelope-from <guillem@hadrons.org>) id 1lAEFI-00076U-8h; Thu, 11 Feb 2021 16:51:08 +0100
Date: Thu, 11 Feb 2021 16:51:07 +0100
From: Guillem Jover <guillem@hadrons.org>
To: Andrew Gallagher <andrewg@andrewg.com>
Cc: openpgp@ietf.org
Message-ID: <YCVSa3CWuRIV17ry@thunder.hadrons.org>
References: <161254580617.29620.7114088127291075805@ietfa.amsl.com> <76fe41fc-f14e-fe3c-db02-7e5b7629dc8a@gmx.net> <1612693541055.92697@cs.auckland.ac.nz> <fe95a37d-7853-fa7b-f8ce-49b60928206b@andrewg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <fe95a37d-7853-fa7b-f8ce-49b60928206b@andrewg.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/5gRrCP8IJWapmMrAzFCqf2m1kOY>
Subject: Re: [openpgp] I-D Action: draft-ietf-openpgp-crypto-refresh-01.txt
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2021 15:51:17 -0000

On Mon, 2021-02-08 at 10:50:02 +0000, Andrew Gallagher wrote:
> On 07/02/2021 10:25, Peter Gutmann wrote:
> > Heiko Stamer <HeikoStamer@gmx.net> 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