[openpgp] Re: I-D Action: draft-ietf-openpgp-replacementke y-08.txt

Songbo Bu <[email protected]> Sun, 31 May 2026 11:48:56 +0800
Newsgroups gmane.ietf.openpgp
Message-ID <CAK08nYZ5=3Vw47-vuaOg7cy_Y2p0PTFToEKyiK6Jp6yXLP+AEQ@mail.gmail.com>
--===============1787370482921104096==
Content-Type: multipart/alternative; boundary="000000000000c3fd41065314f511"

--000000000000c3fd41065314f511
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Andrew,

Thanks for posting -08. The implementation-status and test-vector
appendices are useful additions, especially if the document is moving
toward wider review.

One small test-vector suggestion after a quick scan: it may help
implementers if each vector explicitly states the expected processing
outcome near the armored block, for example which primary key is
deprecated, which key is the expected replacement, whether an
identity-equivalence binding is present, and whether the vector should be
accepted or rejected.

The current descriptive text is readable, but explicit expected results
would make it easier to turn the appendix into automated tests across
implementations.

Best,
Songbo Bu

On Fri, 29 May 2026 19:19:19 +0100, Andrew Gallagher
[email protected] wrote:

Hi, all.

Please find below for your delectation a fresh Key Replacement draft-08.
There are no normative changes since the previous version, however there
are two new appendices:

   -

   RFC7942 Implementation Status (with two implementations)
   -

   Test Vectors

Basic interop testing between protonmail/go-crypto and rpgp(ie) has been
successful. Other implementations are encouraged to join in! :-)

Thanks,
Andrew.

On 29/05/2026 19:14, [email protected] wrote:

Internet-Draft draft-ietf-openpgp-replacementkey-08.txt is now available. I=
t
is a work item of the Open Specification for Pretty Good Privacy (OPENPGP)
WG
of the IETF.

Title: OpenPGP Key Replacement
Authors: Daphne Shaw
Andrew Gallagher
Name: draft-ietf-openpgp-replacementkey-08.txt
Pages: 31
Dates: 2026-05-29

Abstract:

This document specifies a method in OpenPGP to suggest a replacement
for an expired, revoked, or deprecated primary key.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-openpgp-replacementkey/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-openpgp-replacementkey-08

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=3Ddraft-ietf-openpgp-replacementk=
ey-08

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts

openpgp mailing list =E2=80=93 [email protected]
To unsubscribe send an email to [email protected]

--000000000000c3fd41065314f511
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><p>Hi Andrew,</p>
<p>Thanks for posting -08. The implementation-status and test-vector append=
ices are useful additions, especially if the document is moving toward wide=
r review.</p>
<p>One small test-vector suggestion after a quick scan: it may help impleme=
nters if each vector explicitly states the expected processing outcome near=
 the armored block, for example which primary key is deprecated, which key =
is the expected replacement, whether an identity-equivalence binding is pre=
sent, and whether the vector should be accepted or rejected.</p>
<p>The current descriptive text is readable, but explicit expected results =
would make it easier to turn the appendix into automated tests across imple=
mentations.</p>
<p>Best,<br>
Songbo Bu</p>
<p>On Fri, 29 May 2026 19:19:19 +0100, Andrew Gallagher <a href=3D"mailto:a=
[email protected]" target=3D"_blank">andrewg=3D40andrew=
[email protected]</a> wrote:</p>
<blockquote>
<p>Hi, all.</p>
<p>Please find below for your delectation a fresh Key Replacement draft-08.=
<br>
There are no normative changes since the previous version, however there<br=
>
are two new appendices:</p>
<ul>
<li>
<p>RFC7942 Implementation Status (with two implementations)</p>
</li>
<li>
<p>Test Vectors</p>
</li>
</ul>
<p>Basic interop testing between protonmail/go-crypto and rpgp(ie) has been=
<br>
successful. Other implementations are encouraged to join in! :-)</p>
<p>Thanks,<br>
Andrew.</p>
<p>On 29/05/2026 19:14, <a href=3D"mailto:[email protected]" target=
=3D"_blank">[email protected]</a> wrote:</p>
<blockquote>
<p>Internet-Draft draft-ietf-openpgp-replacementkey-08.txt is now available=
. It<br>
is a work item of the Open Specification for Pretty Good Privacy (OPENPGP) =
WG<br>
of the IETF.</p>
<p>Title: OpenPGP Key Replacement<br>
Authors: Daphne Shaw<br>
Andrew Gallagher<br>
Name: draft-ietf-openpgp-replacementkey-08.txt<br>
Pages: 31<br>
Dates: 2026-05-29</p>
<p>Abstract:</p>
<p>This document specifies a method in OpenPGP to suggest a replacement<br>
for an expired, revoked, or deprecated primary key.</p>
<p>The IETF datatracker status page for this Internet-Draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-openpgp-replacementk=
ey/" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-openpgp-=
replacementkey/</a></p>
<p>There is also an HTMLized version available at:<br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-openpgp-replace=
mentkey-08" target=3D"_blank">https://datatracker.ietf.org/doc/html/draft-i=
etf-openpgp-replacementkey-08</a></p>
<p>A diff from the previous version is available at:<br>
<a href=3D"https://author-tools.ietf.org/iddiff?url2=3Ddraft-ietf-openpgp-r=
eplacementkey-08" target=3D"_blank">https://author-tools.ietf.org/iddiff?ur=
l2=3Ddraft-ietf-openpgp-replacementkey-08</a></p>
<p>Internet-Drafts are also available by rsync at:<br>
rsync.ietf.org::internet-drafts</p>


<p>openpgp mailing list =E2=80=93 <a href=3D"mailto:[email protected]" targe=
t=3D"_blank">[email protected]</a><br>
To unsubscribe send an email to <a href=3D"mailto:[email protected]" t=
arget=3D"_blank">[email protected]</a></p>
</blockquote>
</blockquote>
</div>

--000000000000c3fd41065314f511--


--===============1787370482921104096==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18Kb3BlbnBncCBt
YWlsaW5nIGxpc3QgLS0gb3BlbnBncEBpZXRmLm9yZwpUbyB1bnN1YnNjcmliZSBzZW5kIGFuIGVt
YWlsIHRvIG9wZW5wZ3AtbGVhdmVAaWV0Zi5vcmcK

--===============1787370482921104096==--