[openpgp] Re: Call for adoption: draft-dkg-openpgp-external-secrets-03 (Ends 2026-09-18)
Heiko Schäfer <heiko.schaefer@posteo.de> Sat, 05 September 2026 12:08 UTC
Return-Path: <heiko.schaefer@posteo.de>
X-Original-To: openpgp@mail2.ietf.org
Delivered-To: openpgp@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 68859135F7C91 for <openpgp@mail2.ietf.org>; Sat, 5 Sep 2026 05:08:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1788610109; bh=Cyasa/FisxJSARocij34xFYC+cEX9cjW2lv4fVoxCPM=; h=Date:Subject:To:References:From:In-Reply-To; b=lV+CDh3oC4uSY5wtAMUH8A07dS0mW73WHTxQ4QjeDPYG1wNcLQibtaVW4SKCUW0ev ylOE5AtIOI6spWxqyANbXJIrLQG1mKI6NM9e7ypTaa90aCi3OZYEkgQNdnnL7z1pTW ivxabhmRPHfH6Ck9eyOra41DYjAKSIaqKE/ztibU=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.397
X-Spam-Level:
X-Spam-Status: No, score=-4.397 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_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=posteo.de
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AY4DsOwjwBzL for <openpgp@mail2.ietf.org>; Sat, 5 Sep 2026 05:08:28 -0700 (PDT)
Received: from mout01.posteo.de (mout01.posteo.de [185.67.36.65]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 15A0A135F7C85 for <openpgp@ietf.org>; Sat, 5 Sep 2026 05:08:28 -0700 (PDT)
Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 22E17240028 for <openpgp@ietf.org>; Sat, 5 Sep 2026 14:08:27 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=posteo.de; s=1984.8680eb; t=1788610107; bh=FHy2zeukMZZzKHP89De/UmIBJmhFlI9Vnynu/CtOF3U=; h=Message-ID:Date:MIME-Version:Subject:To:From:Content-Type: Content-Transfer-Encoding:From; b=hoauedFDJJYwDlX7QyJAjz85eFj5w3YgI2komnhyV6piVnkyTI1k+b8H81xHGq3kz oBGuPP9RBhKzZNe6Q23JFFMIpb0JkA7u38bVT5IE4EG6c1sZ6gYUy4bTmN0ddBsZZf KZQ2xr4yXdZiCA+MQFSKbUm7GCMbs52BID3ZTJUdCjMM8lVAixN8qxdXbnktLDzXsO jqFE8sqU0GpnTZ5OO8NmC3iAWrWBhnTRNCrB2ccQeryaw3V6AUtm36dWOhfwrAI6+A t1pvmp/wMqM1PM+rGna7km8+OGm79tvHdA2auaMLll3wHFRnOMwN5fTrdB1BJWco/N v07bglLolCRpQ==
Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4hcXDB4rdMz6tsb; Sat, 5 Sep 2026 14:08:26 +0200 (CEST)
Received: from services.empire.hs (services.foundation.hs [192.168.21.4]) by mail.foundation.hs (Postfix) with ESMTP id 28848705C5; Sat, 5 Sep 2026 14:08:26 +0200 (CEST)
Received: from [192.168.30.220] (p5dd422e8.dip0.t-ipconnect.de [93.212.34.232]) by services.empire.hs (Postfix) with ESMTPSA id B19C9C1BDF5; Sat, 5 Sep 2026 14:08:25 +0200 (CEST)
Message-ID: <a358dedd-75c8-4cde-8be0-a7cef8e63f7e@posteo.de>
Date: Sat, 05 Sep 2026 12:08:26 +0000
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, openpgp@ietf.org, openpgp-chairs@ietf.org, draft-dkg-openpgp-external-secrets@ietf.org
References: <178852887840.96242.13353437834122751025@dt-datatracker-9769b79f-xztnc>
Content-Language: en-US
From: Heiko Schäfer <heiko.schaefer@posteo.de>
In-Reply-To: <178852887840.96242.13353437834122751025@dt-datatracker-9769b79f-xztnc>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID-Hash: YWAOSUGH35D5MCKBYU33UJ7KDZ5JUVNZ
X-Message-ID-Hash: YWAOSUGH35D5MCKBYU33UJ7KDZ5JUVNZ
X-MailFrom: heiko.schaefer@posteo.de
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-openpgp.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [openpgp] Re: Call for adoption: draft-dkg-openpgp-external-secrets-03 (Ends 2026-09-18)
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/P6WkgeFf_HpUKP9yLdcAltVK2Xo>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Owner: <mailto:openpgp-owner@ietf.org>
List-Post: <mailto:openpgp@ietf.org>
List-Subscribe: <mailto:openpgp-join@ietf.org>
List-Unsubscribe: <mailto:openpgp-leave@ietf.org>
Hello all, dkg, first, thank you dkg for your work on external-secrets (and for entrusting the text to my editorship). Of course, hardware-backed keys are a trade-off, and not ideal in all situations. Still, they are effectively necessary in some contexts. For example, Let's Encrypt use hardware backed key material. As they should, and really must. Thus I think it's useful to standardize use of hardware backed keys in OpenPGP. I support adoption of this draft, which specifies such a standardized mechanism. And I'm happy to report that Paul Schaub has agreed to co-edit the draft with me. Thanks, Heiko On 9/4/26 3:34 PM, Stephen Farrell via Datatracker wrote: > Asd discussed at ITF-126, this message starts a openpgp WG Call for Adoption of: > draft-dkg-openpgp-external-secrets-03 > > This Working Group Call for Adoption ends on 2026-09-18 > > Abstract: > This document defines a standard wire format for indicating that the > secret component of an OpenPGP asymmetric key is stored externally, > for example on a hardware device or other comparable subsystem. > > Please reply to this message and indicate whether or not you support adoption > of this Internet-Draft by the openpgp WG. Comments to explain your preference > are greatly appreciated. Please reply to all recipients of this message and > include this message in your response. > > Authors, and WG participants in general, are reminded of the Intellectual > Property Rights (IPR) disclosure obligations described in BCP 79 [2]. > Appropriate IPR disclosures required for full conformance with the provisions > of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any. > Sanctions available for application to violators of IETF IPR Policy can be > found at [3]. > > Thank you. > [1] https://datatracker.ietf.org/doc/bcp78/ > [2] https://datatracker.ietf.org/doc/bcp79/ > [3] https://datatracker.ietf.org/doc/rfc6701/ > > The IETF datatracker status page for this Internet-Draft is: > https://datatracker.ietf.org/doc/draft-dkg-openpgp-external-secrets/ > > There is also an HTMLized version available at: > https://datatracker.ietf.org/doc/html/draft-dkg-openpgp-external-secrets-03 > > A diff from the previous version is available at: > https://author-tools.ietf.org/iddiff?url2=draft-dkg-openpgp-external-secrets-03 > > _______________________________________________ > openpgp mailing list -- openpgp@ietf.org > To unsubscribe send an email to openpgp-leave@ietf.org
- [openpgp] Call for adoption: draft-dkg-openpgp-ex… Stephen Farrell via Datatracker
- [openpgp] Re: Call for adoption: draft-dkg-openpg… Daniel Kahn Gillmor
- [openpgp] Re: Call for adoption: draft-dkg-openpg… Andrew Gallagher
- [openpgp] Re: Call for adoption: draft-dkg-openpg… Heiko Schäfer
- [openpgp] Re: Call for adoption: draft-dkg-openpg… Heiko Schäfer
- [openpgp] Re: Call for adoption: draft-dkg-openpg… Paul Schaub
- [openpgp] Re: Call for adoption: draft-dkg-openpg… Stephen Farrell
- [openpgp] Re: Call for adoption: draft-dkg-openpg… Heiko Schäfer