…tificateType Identifiers Expert(s) Yoav Nir, Rich Salz, Nick Sullivan Reference RFC5246 ][ RFC8447 ][ RFC-ietf-tls-tls12-frozen-08 ][ RFC9847 Note If the "Specification Required" [ RFC8126 ] procedure applies, registration requests can be sent to iana@iana.org or submitted via IA…

… this covers connections both with and without Transport Layer Security (TLS) [ RFC5246 ] as defined for SMTP in [ RFC3207 ]. Example: service record _submission._tcp SRV 0 1 587 mail.example.com. 3.2 . IMAP This specification adds two SRV service labels for IMAP [ RFC3501 ]: _im…

…. . 11 1. Introduction A full handshake in TLS protocol versions up to TLS 1.2 [RFC5246] requires two full protocol rounds (four flights) before the handshake is complete and the protocol parties may begin to send application data. Thus, using TLS can add a latency penalty of two…

…. . 11 . Introduction A full handshake in TLS protocol versions up to TLS 1.2 [ RFC5246 requires two full protocol rounds (four flights) before the handshake is complete and the protocol parties may begin to send application data. Thus, using TLS can add a latency penalty of two …

…ction The Transport Layer Security (TLS) Protocol Version 1.2 is specified in [ RFC5246 ]. That specification includes the framework for extensions to TLS, considerations in designing such extensions (see Section 7.4.1.4 of [RFC5246] ), and IANA Considerations for the allocation …

…om Function (PRF) from that version is used; otherwise, the PRF is the TLS PRF [RFC5246] with SHA-256 as the hash function. 3.2. ECDHE_PSK Cipher Suites Using SHA-2 Hashes CipherSuite TLS_ECDHE_PSK_WITH_AES_128_CBC_SHA256 = {0xC0,0x37}; CipherSuite TLS_ECDHE_PSK_WITH_AES_256_CBC_…

…thenticator in version 1.2 or later of the the Transport Layer Security (TLS) [ RFC5246 ] protocol, as well as version 1.2 or later of the Datagram Transport Layer Security (DTLS) protocol [ RFC6347 ]. ChaCha [ CHACHA ] is a stream cipher developed by D. J. Bernstein in 2008. It …

…le policies in parallel: LDAP [ RFC4520 TLS ClientCertificateType Identifiers [ RFC5246 ] (as detailed in the subsections below) MPLS Pseudowire Types Registry [ RFC4446 4.1 . Private Use Private Use is for private or local use only, with the type and purpose defined by the local…

…le policies in parallel: LDAP [ RFC4520 TLS ClientCertificateType Identifiers [ RFC5246 ] (as detailed in the subsections below) MPLS Pseudowire Types Registry [ RFC4446 4.1 . Private Use Private Use is for private or local use only, with the type and purpose defined by the local…

…le policies in parallel: LDAP [ RFC4520 TLS ClientCertificateType Identifiers [ RFC5246 ] (as detailed in the subsections below) MPLS Pseudowire Types Registry [ RFC4446 4.1 . Private Use Private Use is for private or local use only, with the type and purpose defined by the local…

…ment supersedes and obsoletes previous versions of TLS, including version 1.2 [ RFC5246 ]. It also obsoletes the TLS ticket mechanism defined in [ RFC5077 ] and replaces it with the mechanism defined in Section 2.2 . Because TLS 1.3 changes the way keys are derived, it updates [ …

…25 TLS Recommendations May 2015 1. Introduction Transport Layer Security (TLS) [RFC5246] and Datagram Transport Security Layer (DTLS) [RFC6347] are widely used to protect data exchanged over application protocols such as HTTP, SMTP, IMAP, POP, SIP, and XMPP. Over the last few yea…

…ument supersedes and obsoletes previous versions of TLS, including version 1.2 [RFC5246]. It also obsoletes the TLS ticket mechanism defined in [RFC5077] and replaces it with the mechanism defined in Section 2.2. Because TLS 1.3 changes the way keys are derived, it updates [RFC57…

…ment supersedes and obsoletes previous versions of TLS, including version 1.2 [ RFC5246 ]. It also obsoletes the TLS ticket mechanism defined in [ RFC5077 ] and replaces it with the mechanism defined in Section 2.2 . Because TLS 1.3 changes the way keys are derived, it updates [ …

…of bearer tokens over HTTP/1.1 RFC2616 ] using Transport Layer Security (TLS) [ RFC5246 ] to access protected resources. TLS is mandatory to implement and use with this specification; other specifications may extend this specification for use with other protocols. While designed …