On Fri, 22 Nov 2024 at 20:39, Ilari Liusvaara
wrote:
> On Fri, Nov 22, 2024 at 07:34:18PM +0530, tirumal reddy wrote:
> > Thank you, Alicja, for the review. I agree with all your comments and
> have
> > raised a PR https://github.com/tireddy2/composite-mldsa/pull/1 to
> address
> > them.
>
> I th
Andrew Campling mailto:andrew.campl...@419.cons>ulting> writes:
>it should be possible to communicate clearly to implementers and others the
>relative positions of TLS 1.2, TLS-LTS and TLS 1.3 with reference RFC 9325
>and any other relevant documents etc.
On 11/25/24, 6:47 AM, "Peter Gutmann" ma
Andrew Campling writes:
>it should be possible to communicate clearly to implementers and others the
>relative positions of TLS 1.2, TLS-LTS and TLS 1.3 with reference RFC 9325
>and any other relevant documents etc.
Makes sense, I'd have no problems doing that, although as mentioned for RFC
9325
On Mon, Nov 25, 2024, 8:47 PM Salz, Rich
wrote:
>
>- Could you explain why thiis way is better than changing to TLS 1.3?
>
>
>
> It is often the case that organizations will find it easy to make a fairly
> minor change rather than installing a whole new version. You’ve never seen
> this?
>
T
I don't know.
Could you explain why thiis way is better than changing to TLS 1.3?
thanks,
Rob
On Mon, Nov 25, 2024 at 5:38 PM Peter Gutmann
wrote:
> Salz, Rich writes:
>
> >I'd be willing to provide some rough/initial text if it would help this
> get adopted.
>
> Sure, any input is welcome.
* Could you explain why thiis way is better than changing to TLS 1.3?
It is often the case that organizations will find it easy to make a fairly
minor change rather than installing a whole new version. You’ve never seen this?
___
TLS mailing list --
Salz, Rich writes:
>I'd be willing to provide some rough/initial text if it would help this get
>adopted.
Sure, any input is welcome.
Peter.
___
TLS mailing list -- tls@ietf.org
To unsubscribe send an email to tls-le...@ietf.org
