[openpgp] Re: openpgp - New Meeting Session Request for IETF 126

--===============8828980647845958474==
Content-Type: multipart/alternative; boundary="0000000000009cda9906536cf2c5"

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

Hi Andrew, Stephen, all,

+1. Grouping draft-psks and draft-replacementkey under a short =E2=80=9Cdoc=
uments
approaching WGLC=E2=80=9D agenda item seems useful.

For each, the session could cover roughly the same questions: current
implementation status, interop-test coverage, remaining test-vector gaps,
and any issues that would block WGLC. That would keep the discussion
concrete while giving remote reviewers a clearer checklist.

Best,
Songbo Bu

On Thu, 4 Jun 2026 09:59:52 +0100, Andrew Gallagher
[email protected] wrote:

Hi Stephen, Songbo.

I think draft-replacementkey is fairly close behind draft-psks in
maturity, and would benefit from a similar session.

A

On 04/06/2026 02:20, Songbo Bu wrote:

Hi Stephen, all,

One possible agenda item: a short status / interoperability slot for
draft-ietf-openpgp-persistent-symmetric-keys.

Daniel=E2=80=99s note says the spec text is close, experimental implementat=
ions
exist in OpenPGP.js, go-crypto and rpgp branches, and local interop
tests have run. It might be useful to use the session to agree what
evidence the WG wants before WGLC: prerelease availability, online
interop-test coverage, and any remaining test-vector or edge-case gaps.

Even a 10-minute slot would make the path to WGLC clearer for remote
reviewers.

Best,
Songbo Bu

On Wed, 03 Jun 2026 05:13:09 -0700, IETF Meeting Session Request Tool
[email protected] [email protected] wrote:

A new meeting session request has just been submitted by Stephen
Farrell, a
Chair of the OPENPGP Working Group.

Working Group Name: Open Specification for Pretty Good Privacy
Area Name: Security Area
Session Requester: Stephen Farrell

Number of Sessions: 1
Length of Session(s): 1 Hour
Number of Attendees: 40
Conflicts to Avoid:
Chair conflict: ufmrg sshm
Technology overlap: lamps pquip tls cfrg

Participants who must be present:

Resources Requested:

Special Requests:

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

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

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

<div dir=3D"ltr"><p>Hi Andrew, Stephen, all,</p>
<p>+1. Grouping draft-psks and draft-replacementkey under a short =E2=80=9C=
documents approaching WGLC=E2=80=9D agenda item seems useful.</p>
<p>For each, the session could cover roughly the same questions: current im=
plementation status, interop-test coverage, remaining test-vector gaps, and=
 any issues that would block WGLC. That would keep the discussion concrete =
while giving remote reviewers a clearer checklist.</p>
<p>Best,<br>
Songbo Bu</p>
<p>On Thu, 4 Jun 2026 09:59:52 +0100, Andrew Gallagher <a href=3D"mailto:an=
[email protected]" target=3D"_blank">andrewg=3D40andrewg=
[email protected]</a> wrote:</p>
<blockquote>
<p>Hi Stephen, Songbo.</p>
<p>I think draft-replacementkey is fairly close behind draft-psks in<br>
maturity, and would benefit from a similar session.</p>
<p>A</p>
<p>On 04/06/2026 02:20, Songbo Bu wrote:</p>
<blockquote>
<p>Hi Stephen, all,</p>
<p>One possible agenda item: a short status / interoperability slot for<br>
draft-ietf-openpgp-persistent-symmetric-keys.</p>
<p>Daniel=E2=80=99s note says the spec text is close, experimental implemen=
tations<br>
exist in OpenPGP.js, go-crypto and rpgp branches, and local interop<br>
tests have run. It might be useful to use the session to agree what<br>
evidence the WG wants before WGLC: prerelease availability, online<br>
interop-test coverage, and any remaining test-vector or edge-case gaps.</p>
<p>Even a 10-minute slot would make the path to WGLC clearer for remote<br>
reviewers.</p>
<p>Best,<br>
Songbo Bu</p>
<p>On Wed, 03 Jun 2026 05:13:09 -0700, IETF Meeting Session Request Tool<br=
>
<a href=3D"mailto:[email protected]" target=3D"_blank">session-reque=
[email protected]</a> <a href=3D"mailto:[email protected]" target=3D"_blan=
k">[email protected]</a> wrote:</p>
<p>A new meeting session request has just been submitted by Stephen<br>
Farrell, a<br>
Chair of the OPENPGP Working Group.</p>
<p>Working Group Name: Open Specification for Pretty Good Privacy<br>
Area Name: Security Area<br>
Session Requester: Stephen Farrell</p>
<p>Number of Sessions: 1<br>
Length of Session(s): 1 Hour<br>
Number of Attendees: 40<br>
Conflicts to Avoid:<br>
Chair conflict: ufmrg sshm<br>
Technology overlap: lamps pquip tls cfrg</p>
<p>Participants who must be present:</p>
<p>Resources Requested:</p>
<p>Special Requests:</p>
<p>openpgp mailing list =E2=80=93 <a href=3D"mailto:[email protected]" targe=
t=3D"_blank">[email protected]</a> <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><br>
<a href=3D"mailto:[email protected]" target=3D"_blank">openpgp-leave@i=
etf.org</a></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>

--0000000000009cda9906536cf2c5--


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

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18Kb3BlbnBncCBt
YWlsaW5nIGxpc3QgLS0gb3BlbnBncEBpZXRmLm9yZwpUbyB1bnN1YnNjcmliZSBzZW5kIGFuIGVt
YWlsIHRvIG9wZW5wZ3AtbGVhdmVAaWV0Zi5vcmcK

--===============8828980647845958474==--