[openpgp] Re: I-D Action: draft-ietf-openpgp-hkp-01.txt

--===============3550542179489835773==
Content-Type: multipart/alternative; boundary="00000000000011d702065390a627"

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

Hi Andrew, all,

Thanks, good to see -01 and the test instance.

I=E2=80=99ll take another pass through the draft and the test deployment. T=
he two
places I=E2=80=99ll focus on are:

   - the JSON schema once it is added, especially keeping it aligned with
   the response examples and any backward-compatible fields;
   - whether the static-serving / discovery behavior is clear enough for
   implementers who do not run a traditional synchronizing keyserver.

A small non-normative checklist of =E2=80=9Cwhat a simple implementation sh=
ould
serve and what clients should tolerate=E2=80=9D might be useful if the WG t=
hinks
that fits.

Best,
Songbo Bu

On Fri, 5 Jun 2026 16:23:44 +0100, Andrew Gallagher
[email protected] wrote:

Hi, all.

I=E2=80=99ve published a new HKP draft that contains (almost!) all the chan=
ges
discussed on the list. The only caveat is that there is not yet a formal
JSON schema in the document.

The corresponding hockeypuck PR has been merged and is running on
test.pgpkeys.eu now.

Thanks,
A

On 05/06/2026 16:00, [email protected] wrote:

Internet-Draft draft-ietf-openpgp-hkp-01.txt is now available. It is a work
item of the Open Specification for Pretty Good Privacy (OPENPGP) WG of the
IETF.

Title: OpenPGP HTTP Keyserver Protocol
Authors: Daphne Shaw
Andrew Gallagher
Daniel Huigens
Name: draft-ietf-openpgp-hkp-01.txt
Pages: 51
Dates: 2026-06-05

Abstract:

This document specifies a series of conventions to implement an
OpenPGP keyserver using the Hypertext Transfer Protocol (HTTP). As
this document is a codification and extension of a protocol that is
already in wide use, strict attention is paid to backward
compatibility with these existing implementations.

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

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

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

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]

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

<div dir=3D"ltr"><p>Hi Andrew, all,</p>
<p>Thanks, good to see -01 and the test instance.</p>
<p>I=E2=80=99ll take another pass through the draft and the test deployment=
. The two places I=E2=80=99ll focus on are:</p>
<ul>
<li>the JSON schema once it is added, especially keeping it aligned with th=
e response examples and any backward-compatible fields;</li>
<li>whether the static-serving / discovery behavior is clear enough for imp=
lementers who do not run a traditional synchronizing keyserver.</li>
</ul>
<p>A small non-normative checklist of =E2=80=9Cwhat a simple implementation=
 should serve and what clients should tolerate=E2=80=9D might be useful if =
the WG thinks that fits.</p>
<p>Best,<br>
Songbo Bu</p>
<p>On Fri, 5 Jun 2026 16:23:44 +0100, Andrew Gallagher <a href=3D"mailto:an=
[email protected]" target=3D"_blank">andrewg=3D40andrewg=
[email protected]</a> wrote:</p>
<blockquote>
<p>Hi, all.</p>
<p>I=E2=80=99ve published a new HKP draft that contains (almost!) all the c=
hanges<br>
discussed on the list. The only caveat is that there is not yet a formal<br=
>
JSON schema in the document.</p>
<p>The corresponding hockeypuck PR has been merged and is running on<br>
<a href=3D"http://test.pgpkeys.eu" target=3D"_blank">test.pgpkeys.eu</a> no=
w.</p>
<p>Thanks,<br>
A</p>
<p>On 05/06/2026 16:00, <a href=3D"mailto:[email protected]" target=
=3D"_blank">[email protected]</a> wrote:</p>
<blockquote>
<p>Internet-Draft draft-ietf-openpgp-hkp-01.txt is now available. It is a w=
ork<br>
item of the Open Specification for Pretty Good Privacy (OPENPGP) WG of the<=
br>
IETF.</p>
<p>Title: OpenPGP HTTP Keyserver Protocol<br>
Authors: Daphne Shaw<br>
Andrew Gallagher<br>
Daniel Huigens<br>
Name: draft-ietf-openpgp-hkp-01.txt<br>
Pages: 51<br>
Dates: 2026-06-05</p>
<p>Abstract:</p>
<p>This document specifies a series of conventions to implement an<br>
OpenPGP keyserver using the Hypertext Transfer Protocol (HTTP). As<br>
this document is a codification and extension of a protocol that is<br>
already in wide use, strict attention is paid to backward<br>
compatibility with these existing implementations.</p>
<p>The IETF datatracker status page for this Internet-Draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-openpgp-hkp/" target=
=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-openpgp-hkp/</a></p=
>
<p>There is also an HTMLized version available at:<br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-openpgp-hkp-01"=
 target=3D"_blank">https://datatracker.ietf.org/doc/html/draft-ietf-openpgp=
-hkp-01</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-h=
kp-01" target=3D"_blank">https://author-tools.ietf.org/iddiff?url2=3Ddraft-=
ietf-openpgp-hkp-01</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>

--00000000000011d702065390a627--


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

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18Kb3BlbnBncCBt
YWlsaW5nIGxpc3QgLS0gb3BlbnBncEBpZXRmLm9yZwpUbyB1bnN1YnNjcmliZSBzZW5kIGFuIGVt
YWlsIHRvIG9wZW5wZ3AtbGVhdmVAaWV0Zi5vcmcK

--===============3550542179489835773==--