Re: [openpgp] a new draft overlapping the WG draft

Kai Engert <kaie@kuix.de> Fri, 07 October 2022 17:43 UTC

Return-Path: <kaie@kuix.de>
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 F1782C14CF14 for <openpgp@ietfa.amsl.com>; Fri, 7 Oct 2022 10:43:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 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, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kuix.de
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yacy_qyozZK2 for <openpgp@ietfa.amsl.com>; Fri, 7 Oct 2022 10:43:50 -0700 (PDT)
Received: from cloud.kuix.de (cloud.kuix.de [93.90.207.85]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ECCE3C14CF04 for <openpgp@ietf.org>; Fri, 7 Oct 2022 10:43:49 -0700 (PDT)
Received: from [IPV6:2003:c8:af08:6600:1faa:9ae1:9207:1d8a] (p200300c8af0866001faa9ae192071d8a.dip0.t-ipconnect.de [IPv6:2003:c8:af08:6600:1faa:9ae1:9207:1d8a]) by cloud.kuix.de (Postfix) with ESMTPSA id 6A39C184AFF; Fri, 7 Oct 2022 17:43:46 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kuix.de; s=2018; t=1665164626; bh=UIcCR+rg2Asw1JOfuOVtDdgUq2yqduO43y73OGmvKAM=; h=Date:To:Cc:References:From:Subject:In-Reply-To:From; b=KAa0Fj9CDLOB1kHErtsVOFSsNagQrx6wkRZoqOXfiNrN8SnZ3MqLnTDgzrDqX2Q0p U4ggeS2LxgRsY2SPAhUEnzvCEdLOkZOFXX1RM1LC51ka/aSkMKNJxHyMhQ1e5NfKWv bK13YaARfMUxtZ3j/ync7va3m1xIh2D+AEl/VwXfg6n9ApoR9pmBhKyiCMpZKJYZal hawDPaIllJia1TvKUYziBQHC4qQ5bSxL4cpF3G2IsqZJTFS9BL3p+0mlW/UzEDvVUW LS/nVF+uvva56TowlRamnHLYJm8LmfT2nKl923PG7wV+hjiApOUjvsN7QHhhX9sLcY xC7i7qaZur8DQ==
Message-ID: <71ba533f-120e-2a6a-8519-37efbc7a5fcb@kuix.de>
Date: Fri, 07 Oct 2022 19:43:46 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.3.1
Content-Language: en-US
To: "Neal H. Walfield" <neal@walfield.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: "openpgp@ietf.org" <openpgp@ietf.org>
References: <b8ddeb1e-fdbb-edab-3693-722c9e14f3d8@cs.tcd.ie> <878rlsc6oe.wl-neal@walfield.org>
From: Kai Engert <kaie@kuix.de>
In-Reply-To: <878rlsc6oe.wl-neal@walfield.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/VL8mdX2HHQuTvv2fYeF6KiR4jho>
Subject: Re: [openpgp] a new draft overlapping the WG draft
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 07 Oct 2022 17:43:54 -0000

On 07.10.22 11:41, Neal H. Walfield wrote:
>    - At the same I'd like the DT to review concessions that were made
>      to Werner.  In particular, my understanding is that keeping AEAD's
>      flexible chunk size parameter was a compromise with Werner.  I'd
>      like to repropose removing the chunk size parameter, and fixing it
>      to a single value.

If you avoid introducing deliberate conflicts, the GnuPG developers 
could more easily reconsider their position at a future time, and decide 
to implement crypto-refresh despite their today's concerns.

Kai