Subject: [lamps] Re: WG Last Call: draft-ietf-lamps-pq-composite-sigs-08 (Ends 2025-10-06)
From: tirumal reddy <[email-masked]>
To: Russ Housley <[email-masked]>
Cc: [email-masked], [email-masked], [email-masked]
Date: Wed, 24 Sep 2025 12:06:14 +0530
List-Id: This is the mail list for the LAMPS Working Group <spasm.ietf.org>

Hi,

I am reviewing IPR disclosure 4761
<https://datatracker.ietf.org/ipr/4761/?utm_source=chatgpt.com> related to
Composite ML-DSA. I would like to understand whether the licensing terms
allow implementations in open source projects. From my reading, the
disclosure appears to provide a commitment that is conditional.

Does this IPR declaration permit open source implementations without the
need for individual agreements with CableLabs ?

Your clarification will help assess whether Composite ML-DSA can be adopted
in open source cryptographic libraries and security protocols (use of
composite ML-DSA is proposed in TLS, IKEv2 and JOSE).

-Tiru
On Mon, 22 Sept 2025 at 21:23, Russ Housley <[email-masked]> wrote:

> As part of this WG Last Call, be aware that this IPR disclosure was
> submitted four years ago:
> https://datatracker.ietf.org/ipr/4761/
>
> Russ
>
>
> On Sep 22, 2025, at 11:50 AM, Russ Housley via Datatracker <
> [email-masked]> wrote:
>
>
> Subject: WG Last Call: draft-ietf-lamps-pq-composite-sigs-08 (Ends
> 2025-10-06)
>
> This message starts a 2-week WG Last Call for this document.
>
> Abstract:
>   This document defines combinations of ML-DSA [FIPS.204] in hybrid
>   with traditional algorithms RSASSA-PKCS1-v1.5, RSASSA-PSS, ECDSA,
>   Ed25519, and Ed448.  These combinations are tailored to meet security
>   best practices and regulatory guidelines.  Composite ML-DSA is
>   applicable in any application that uses X.509 or PKIX data structures
>   that accept ML-DSA, but where the operator wants extra protection
>   against breaks or catastrophic bugs in ML-DSA.
>
> File can be retrieved from:
> https://datatracker.ietf.org/doc/draft-ietf-lamps-pq-composite-sigs/
>
> Please review and indicate your support or objection to proceed with the
> publication of this document by replying to this email keeping
> [email-masked]
> in copy. Objections should be motivated and suggestions to resolve them are
> highly appreciated.
>
> Authors, and WG participants in general, are reminded again of the
> Intellectual Property Rights (IPR) disclosure obligations described in BCP
> 79
> [1]. Appropriate IPR disclosures required for full conformance with the
> provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of
> any. Sanctions available for application to violators of IETF IPR Policy
> can
> be found at [3].
>
> Thank you.
>
> [1] https://datatracker.ietf.org/doc/bcp78/
> [2] https://datatracker.ietf.org/doc/bcp79/
> [3] https://datatracker.ietf.org/doc/rfc6701/
>
>
>
>
> _______________________________________________
> Spasm mailing list -- [email-masked]
> To unsubscribe send an email to [email-masked]
>