[saag] Re: [EXTERNAL] Re: NIST Requests Comments on SP 800-52 Rev. 2 | Selection, Configuration, and Use of TLS Implementations

--===============6180579877830238304==
Content-Type: multipart/alternative; boundary="00000000000012197506534a6ba2"

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

I think that enterprises that operate with tight licenses want full
visibility into their endpoints. They aren't big fans of tls 1.3, ech and
quic. They want proxies for outgoing tls connections.

I think that those enterprises will likely support tls 1.2 for a very
very long time ?



On Tue, 02 Jun 2026, 23:28 Salz, Rich, <[email protected]=
>
wrote:

> The RFC-to-be 9846, a product of the UTA working group, says TLS 1.3 is a
> MUST and you MAY do TLS 1.2 if you have installed base or other deploymen=
t
> concerns.  The pre-pub draft is at [1].
>
> Disclaimer: I=E2=80=99m a co-author.
>
> [1] https://datatracker.ietf.org/doc/draft-ietf-uta-require-tls13/
> _______________________________________________
> saag mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>

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

<div dir=3D"auto">I think that enterprises that operate with tight licenses=
 want full visibility into their endpoints. They aren&#39;t big fans of tls=
 1.3, ech and quic. They want proxies for outgoing tls connections.=C2=A0<d=
iv dir=3D"auto"><br></div><div dir=3D"auto">I think that those enterprises =
will likely support tls 1.2 for a very very=C2=A0long time ?</div><div dir=
=3D"auto"><br></div><div dir=3D"auto"><br></div></div><br><div class=3D"gma=
il_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Tu=
e, 02 Jun 2026, 23:28 Salz, Rich, &lt;rsalz=3D<a href=3D"mailto:40akamai.co=
[email protected]">[email protected]</a>&gt; wrote:<br></div><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex">



<div>
<div style=3D"direction:ltr;font-family:Aptos,Arial,Helvetica,sans-serif;fo=
nt-size:12pt;color:rgb(0,0,0)">
The RFC-to-be=C2=A09846, a product of the UTA working group, says TLS 1.3 i=
s a MUST and you MAY do TLS 1.2 if you have installed base or other deploym=
ent concerns.=C2=A0 The pre-pub draft is at [1].</div>
<div style=3D"direction:ltr;font-family:Aptos,Arial,Helvetica,sans-serif;fo=
nt-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style=3D"direction:ltr;font-family:Aptos,Arial,Helvetica,sans-serif;fo=
nt-size:12pt;color:rgb(0,0,0)">
Disclaimer: I=E2=80=99m a co-author.</div>
<div style=3D"direction:ltr;font-family:Aptos,Arial,Helvetica,sans-serif;fo=
nt-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style=3D"direction:ltr;font-family:Aptos,Arial,Helvetica,sans-serif;fo=
nt-size:12pt;color:rgb(0,0,0)">
[1] <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-uta-require-tls1=
3/" target=3D"_blank" rel=3D"noreferrer">
https://datatracker.ietf.org/doc/draft-ietf-uta-require-tls13/</a></div>
</div>

_______________________________________________<br>
saag mailing list -- <a href=3D"mailto:[email protected]" target=3D"_blank" rel=
=3D"noreferrer">[email protected]</a><br>
To unsubscribe send an email to <a href=3D"mailto:[email protected]" targ=
et=3D"_blank" rel=3D"noreferrer">[email protected]</a><br>
</blockquote></div>

--00000000000012197506534a6ba2--


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

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18Kc2FhZyBtYWls
aW5nIGxpc3QgLS0gc2FhZ0BpZXRmLm9yZwpUbyB1bnN1YnNjcmliZSBzZW5kIGFuIGVtYWlsIHRv
IHNhYWctbGVhdmVAaWV0Zi5vcmcK

--===============6180579877830238304==--