…erations This document uses several registries that were originally created in [RFC4346] and updated in [RFC8447]. IANA has updated these to reference this document. The registries and their allocation policies are below: - TLS Cipher Suites registry: values with the first byte i…
…eries of specifications that describe the TLS protocol v1.0 [ RFC2246 ], v1.1 [ RFC4346 ], v1.2 [ RFC5246 ], and v1.3 [ RFC8446 ], and DTLS (Datagram TLS) v1.0 [ RFC4347 ], v1.2 [ RFC6347 ], and v1.3 [ draft-ietf-tls-dtls13 ], as well as extensions to the protocols and ciphersuit…
…derations This document uses several registries that were originally created in RFC4346 ] and updated in [ RFC8447 ]. IANA has updated these to reference this document. The registries and their allocation policies are below: - TLS Cipher Suites registry: values with the first byt…
…erations This document uses several registries that were originally created in [RFC4346] and updated in [RFC8447]. IANA has updated these to reference this document. The registries and their allocation policies are below: - TLS Cipher Suites registry: values with the first byte i…
…C 8447 Obsoletes RFC 4346 RFC 4366 RFC 3268 Updates RFC 4492 Was draft-ietf-tls-rfc4346-bis tls WG Authors Eric Rescorla Tim Dierks 2020-01-21 RFC stream Internet Engineering Task Force (IETF) Formats txt html pdf htmlized w/errata bibtex Additional resources Mailing list discuss…
…eries of specifications that describe the TLS protocol v1.0 [ RFC2246 ], v1.1 [ RFC4346 ], v1.2 [ RFC5246 ], and v1.3 [ RFC8446 ], and DTLS (Datagram TLS) v1.0 [ RFC4347 ], v1.2 [ RFC6347 ], and v1.3 [ draft-ietf-tls-dtls13 ], as well as extensions to the protocols and ciphersuit…
…derations This document uses several registries that were originally created in RFC4346 ] and updated in [ RFC8447 ]. IANA has updated these to reference this document. The registries and their allocation policies are below: - TLS Cipher Suites registry: values with the first byt…
…age 7. The 4th paragraph of the same section (on page 6) clearly refers to TLS [RFC4346]. SSL is *not* TLS, it's the predecessor, updated in the IETF to fix serious security issues detected. Hence the RFC should consistently refer to "TLS" and not mix in "SSL". Errata ID: 1360 St…
…age 7. The 4th paragraph of the same section (on page 6) clearly refers to TLS [RFC4346]. SSL is *not* TLS, it's the predecessor, updated in the IETF to fix serious security issues detected. Hence the RFC should consistently refer to "TLS" and not mix in "SSL". Errata ID: 1360 St…