On Fri, Mar 06, 2020 at 07:24:01PM -0800, Benjamin Kaduk wrote:
> > > It seems like this would avoid the trap of alternating full and resumption
> > > handshakes that was discussed downthread for the case where client
> > > supports
> > > reuse but server does not.
> >
> > Yes, there is some wig
On Thu, Mar 05, 2020 at 09:27:47PM -0500, Viktor Dukhovni wrote:
> On Thu, Mar 05, 2020 at 05:30:04PM -0800, Benjamin Kaduk wrote:
>
> > > No it does not, because he specifically emphasised treating 0 in the
> > > resumption count as issue no tickets, whereas PR#18 says that that that
> > > don't
The following errata report has been submitted for RFC8447,
"IANA Registry Updates for TLS and DTLS".
--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6009
--
Type: Editorial
Reported by: Benjam
The following errata report has been verified for RFC8446,
"The Transport Layer Security (TLS) Protocol Version 1.3".
--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid5976
--
Status: Verified
T
This is great news. Thanks for helping make it happen!
-Ekr
On Fri, Mar 6, 2020 at 4:03 PM John Mattsson wrote:
> Hi,
>
> I am happy to report that 3GPP just took the decision to forbid support of
> MD5 and SHA-1, as well as all non-AEAD and non-PFS cipher suites in TLS.
> The changes apply to
All,
Dan and I have a new draft that describes how a mechanism similar to the Wi-Fi
Alliance Device Provisioning Profile can be used on wired networks via proposed
new TLS extensions, with those extensions being leveraged in an EAP
transaction. Importantly, the DPP bootstrap key format, and thu
Hi,
I am happy to report that 3GPP just took the decision to forbid support of MD5
and SHA-1, as well as all non-AEAD and non-PFS cipher suites in TLS. The
changes apply to all Rel-16 3GPP systems that use TLS and DTLS, which are quite
many.
3GPP had already mandaded support of TLS 1.3, forbid
The Transport Layer Security (tls) WG in the Security Area of the IETF is
undergoing rechartering. The IESG has not made any determination yet. The
following draft charter was submitted, and is provided for informational
purposes only. Please send your comments to the IESG mailing list
(i...@ietf.o
Hi!
Just aa gentle reminder for agenda topic request. Also, if you are planning to
be a remote presenter please let us know.
spt
> On Feb 18, 2020, at 20:05, Sean Turner wrote:
>
> The TLS WG will be meeting @ IETF 107 in Vancouver. To help the chairs get a
> better handle on how arrange our
