[openpgp] draft-ietf-openpgp-nist-bp-comp: WGLC readiness an d interoperability evidence

Blue Dog <[email protected]> Thu, 21 May 2026 05:15:14 +0800
Newsgroups gmane.ietf.openpgp
Message-ID <CAK08nYZaovmkhvLpLZiRaNH_QUr005YvCqDTXbNF-1Ap+_Jniw@mail.gmail.com>
Hello,

I read the recent discussion around draft-ietf-openpgp-nist-bp-comp and
reviewed the current -03 draft. Based on the stated implementation status
and the inclusion of test vectors, I support moving the document to WGLC if
the authors and chairs believe the technical content is stable enough for
broader review.

The most useful additional item, in my view, would be to make the
interoperability evidence easy for future implementers to reproduce. This
need not block WGLC, but it would be valuable before publication.

Specifically, I suggest recording:

   - the exact draft revision and algorithm combinations covered by the
   current implementations;
   - where the test vectors are maintained and which vectors correspond to
   each algorithm ID;
   - at least one positive cross-implementation validation path, for
   example generation in one implementation and parsing or verification in
   another;
   - at least one negative or malformed-vector case, if available, to
   document expected rejection behavior;
   - any known limitations in the current implementation coverage,
   especially where algorithm IDs, secret-key encoding, or composite signature
   behavior are still changing.

This would make the two-implementation signal more useful to later
implementers and reviewers, and would also reduce the risk that WGLC
comments focus on reproducibility rather than the remaining technical
choices in the draft.

Best regards,

Songbo Bu

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