IETF Logo Mail Archive

[openpgp] Marker packet for OpenPGP-NG (was: Confirming open questions discussed at IETF 114)

Werner Koch <wk@gnupg.org> Wed, 12 October 2022 15:02 UTC

Return-Path: <wk@gnupg.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 737ACC14CF15 for <openpgp@ietfa.amsl.com>; Wed, 12 Oct 2022 08:02:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 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, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gnupg.org
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 MOUTiUptdAAq for <openpgp@ietfa.amsl.com>; Wed, 12 Oct 2022 08:02:11 -0700 (PDT)
Received: from kerckhoffs.g10code.com (kerckhoffs.g10code.com [IPv6:2001:aa8:fff1:100::22]) (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 3314FC1522AE for <openpgp@ietf.org>; Wed, 12 Oct 2022 08:02:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnupg.org; s=20181017; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:To:From:Sender:Reply-To:Cc:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=g+8tlqdU9fUmQpF5OlIU1kyQP/VVadQyuHLH5Qn9Rro=; b=bjZiBdJkpH8jKuTLJZObDRi4gw 9bhNs1YaKKPm8B+VrFplX77NmRu6NUDNVVwzGhF68GgfGaC9++zkLtGdqz2Gj15cSg1sL67mKNZtR Ugxfk0iAxz2hKGulnDDVbT+WK9mVgGlFTiVPpfFJLq5PXhCGRqT3RulOVyDsUCLsLGwk=;
Received: from uucp by kerckhoffs.g10code.com with local-rmail (Exim 4.89 #1 (Debian)) id 1oidFI-0003Jv-8L for <openpgp@ietf.org>; Wed, 12 Oct 2022 17:02:08 +0200
Received: from wk by wheatstone.g10code.de with local (Exim 4.92 #5 (Debian)) id 1oidDz-00069D-7C for <openpgp@ietf.org>; Wed, 12 Oct 2022 17:00:47 +0200
From: Werner Koch <wk@gnupg.org>
To: openpgp@ietf.org
References: <87tu6wneqh.fsf@fifthhorseman.net> <87y1tm635e.fsf@fifthhorseman.net> <bc30b65f-3dc7-fa1a-e3a9-9b7171192d92@cs.tcd.ie>
X-message-flag: Mails containing HTML will not be read! Please send only plain text.
Jabber-ID: wk@jabber.gnupg.org
Mail-Followup-To: openpgp@ietf.org
Date: Wed, 12 Oct 2022 17:00:40 +0200
In-Reply-To: <bc30b65f-3dc7-fa1a-e3a9-9b7171192d92@cs.tcd.ie> (Stephen Farrell's message of "Tue, 11 Oct 2022 12:35:07 +0100")
Message-ID: <87sfjtdr3b.fsf_-_@wheatstone.g10code.de>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=Cyber_attack_Semtex_SISMI_Federal_Bureau_of_Investigation_racal_War_"; micalg="pgp-sha256"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/s8VvJwaY_iwpOz7lhrDsCeI1O9U>
Subject: [openpgp] Marker packet for OpenPGP-NG (was: Confirming open questions discussed at IETF 114)
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: Wed, 12 Oct 2022 15:02:16 -0000

Hi!

Given that the crypto-refresh I-D heavily deviates from OpenPGP as
specified in RFC-2440 and RFC-4880 and deployed practise I have two
suggestions to avoid confusion:

1. All data including key packets shall make use of a marker packet

   5.8.  Marker Packet (Tag 10)

   This packet was used by certain PGP versions and flagged as obsolete
   in RFC-4880.  With this specification it is repurposed to mark the
   data and keys constructed as specified by this specification and its
   successors.

   The body of this packet consists of:

     - The three octets 0x60, 0x67, 0x70  (which spell "pgp" in UTF-8).

   Implementations SHALL use this packet to indicate packet formats
   described by this specification.  It SHALL be the first packet of
   each OpenPGP Message or sets of OpenPGP Keys.  Note that the old
   marker packet used three different octets.


2. Clearly identify the new specification as a new version of OpenPGP
   with only limited backward compatibility.  For example
     OpenPGP-NG or OpenPGP/2 or ModernPGP or IETFPGP
   or maybe just PGP (if Broadcom allows for such a use)



Salam-Shalom,

   Werner


-- 
The pioneers of a warless world are the youth that
refuse military service.             - A. Einstein

v2.23.0 | Report a Bug | By Email