[openpgp] Re: Fwd: New Version Notification for draft-gall agher-openpgp-signatures-03.txt

--===============8036108708116734633==
Content-Type: multipart/alternative; boundary="000000000000963e4b0653779e3d"

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

Hi Andrew, all,

The split looks useful to me. Having signatures, certificates, and messages
separated should make the review easier, especially for readers who want to
focus on certificate/revocation behavior without also carrying all message
grammar details.

One small reviewability point: because certificate semantics now depend on
the signature draft, and draft-certificates also imports material from
draft-revocation, it may help to add a short =E2=80=9Cdocument map=E2=80=9D=
 or dependency
paragraph near the front of each draft. Something as simple as =E2=80=9Cthi=
s
document owns certificate grammar; signature packet/subpacket semantics are
in draft-signatures; message grammar is in draft-messages=E2=80=9D would re=
duce
cross-draft confusion.

I can take a closer read of draft-certificates and draft-signatures, with
an eye toward the certificate/signature boundary and revocation text.

Best,
Songbo Bu

On Thu, 4 Jun 2026 23:49:35 +0100, Andrew Gallagher
[email protected] wrote:

Hi, all.

I have just uploaded a new version of draft-gallagher-openpgp-signatures
with a reduced scope. I have also uploaded two new drafts that cover the
material now removed from draft-signatures:

   -

   draft-gallagher-openpgp-certificates - This covers the grammar and
   semantics of certificates, including revocations. It contains a
   significant chunk of dkg=E2=80=99s draft-revocation, and dkg is therefor=
e listed
   as co-author.
   -

   draft-gallagher-openpgp-messages - This covers the grammar of
   messages, and is by far the smallest of the three drafts (currently!).

draft-signatures is now focused specifically on the construction,
classification and semantics of signature packets and subpackets. I hope
this restructuring will make the document(s) more digestible.

Thanks,
A

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

<div dir=3D"ltr"><p>Hi Andrew, all,</p>
<p>The split looks useful to me. Having signatures, certificates, and messa=
ges separated should make the review easier, especially for readers who wan=
t to focus on certificate/revocation behavior without also carrying all mes=
sage grammar details.</p>
<p>One small reviewability point: because certificate semantics now depend =
on the signature draft, and draft-certificates also imports material from d=
raft-revocation, it may help to add a short =E2=80=9Cdocument map=E2=80=9D =
or dependency paragraph near the front of each draft. Something as simple a=
s =E2=80=9Cthis document owns certificate grammar; signature packet/subpack=
et semantics are in draft-signatures; message grammar is in draft-messages=
=E2=80=9D would reduce cross-draft confusion.</p>
<p>I can take a closer read of draft-certificates and draft-signatures, wit=
h an eye toward the certificate/signature boundary and revocation text.</p>
<p>Best,<br>
Songbo Bu</p>
<p>On Thu, 4 Jun 2026 23:49:35 +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 have just uploaded a new version of draft-gallagher-openpgp-signatures=
<br>
with a reduced scope. I have also uploaded two new drafts that cover the<br=
>
material now removed from draft-signatures:</p>
<ul>
<li>
<p>draft-gallagher-openpgp-certificates - This covers the grammar and<br>
semantics of certificates, including revocations. It contains a<br>
significant chunk of dkg=E2=80=99s draft-revocation, and dkg is therefore l=
isted<br>
as co-author.</p>
</li>
<li>
<p>draft-gallagher-openpgp-messages - This covers the grammar of<br>
messages, and is by far the smallest of the three drafts (currently!).</p>
</li>
</ul>
<p>draft-signatures is now focused specifically on the construction,<br>
classification and semantics of signature packets and subpackets. I hope<br=
>
this restructuring will make the document(s) more digestible.</p>
<p>Thanks,<br>
A</p>
</blockquote>
</div>

--000000000000963e4b0653779e3d--


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

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18Kb3BlbnBncCBt
YWlsaW5nIGxpc3QgLS0gb3BlbnBncEBpZXRmLm9yZwpUbyB1bnN1YnNjcmliZSBzZW5kIGFuIGVt
YWlsIHRvIG9wZW5wZ3AtbGVhdmVAaWV0Zi5vcmcK

--===============8036108708116734633==--