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

Hi Andrew,

Am 18.08.25 um 12:51 schrieb Andrew Gallagher:
> Hi, Falko.
>
> On 18 Aug 2025, at 08:14, Falko Strenzke<[email protected]> wrote:
>> - The beginning of Section 4.2 seems to imply that since there may be only one RKS in one signature, there can only be a single RKSP in the whole certificate. That doesn't seem to work out since according to RFC 9580, v6 keys can have any number of Direct Key Signatures. Later, under Section 5.1, something is said about RKSPs "new" Direct Key Signatures overriding the "older" ones, here I think the clarity could be enhanced as to whether this covers multiple Direct Key Signatures to be present simultaneously or not. Also already Section 4.2 should clarify this aspect.
> Yes, RFC9580 is silent about the cumulation rules for signatures. But it’s actually more confusing than that again, because the subpacket can also appear in a revocation signature. We should make clear that a subpacket in a revocation takes precedence over any found in a direct sig.
>
> How about this wording?
>
> """
> A certificate MAY have multiple signatures that contain Replacement Key subpackets, however at most one Replacement Key subpacket in a certificate is current (and therefore meaningful) at any given time.
> If the primary key is revoked with a Reason for Revocation of "Key is Superseded", the current Replacement Key subpacket (if any) is found in the most recent valid primary Key Revocation signature.
> If it is not revoked, the current Replacement Key subpacket (if any) is found in the most recent valid Direct Key signature.
> If the most recent valid primary Key Revocation or Direct Key signature does not contain a Replacement Key subpacket, or the primary key is revoked for any other reason, then there is no current Replacement Key subpacket.
> """

Sounds good to me.

Best regards,
Falko

>
>> - In the figures in Sections 4.2 and A.3 it says "Reverse RKSP", but I think according to the new terminology it should say "Backwards RKSP”.
> Good catch, thanks!
>
>> - Editorial only: Section 5.1.2: "If so, they may (in some circumstances) send messages encrypted to one of the certificates but addressed to an identity that it does not claim." I suggest for better readability: => " [...] to an identity that this particular certificate does not claim.”
> Thanks, I’ll reword this slightly: “to an identity which that particular certificate does not claim”, which I think works even better.
>
> Thanks once again, particularly for the fast turnaround! ;-)
>
> A
>
>
> _______________________________________________
> openpgp mailing list [email protected]
> To unsubscribe send an email [email protected]
-- 

*MTG AG*
Dr. Falko Strenzke

Phone: +49 6151 8000 24
E-Mail: [email protected]
Web: mtg.de <https://www.mtg.de>

------------------------------------------------------------------------

MTG AG - Dolivostr. 11 - 64293 Darmstadt, Germany
Commercial register: HRB 8901
Register Court: Amtsgericht Darmstadt
Management Board: Jürgen Ruf (CEO), Tamer Kemeröz
Chairman of the Supervisory Board: Dr. Thomas Milde

This email may contain confidential and/or privileged information. If 
you are not the correct recipient or have received this email in error,
please inform the sender immediately and delete this email.Unauthorised 
copying or distribution of this email is not permitted.

Data protection information: Privacy policy 
<https://www.mtg.de/en/privacy-policy>

_______________________________________________
openpgp mailing list -- [email protected]
To unsubscribe send an email to [email protected]