…Multimedia Internet KEYing (MIKEY) Modes and Extensions", RFC 5197, June 2008. [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security (TLS) Protocol Version 1.2", RFC 5246, August 2008. [SDP-CAP] Andreasen, F., "SDP Capability Negotiation", Work in Progress, July 200…
…ncreasingly, application-layer protocols are encapsulated in the TLS protocol [ RFC5246 ]. This encapsulation enables applications to use the existing, secure communications links already present on port 443 across virtually the entire global IP infrastructure. When multiple appl…
…nternet-Draft ChaCha20Poly1305 for TLS Nov 2013 1 . Introduction Existing TLS [ RFC5246 ] cipher suites either suffer from cryptographic weaknesses (RC4), major implementation pitfalls (CBC mode block ciphers) or are difficult to efficiently and securely implement in software (AE…
… in the Simplified BSD License. 1. Introduction Transport Layer Security ( TLS [RFC5246] ) allows clients to authenticate themselves using Client Certificates. In practice, clients tend to ask for user consent before using Client Certificates. This is to allay privacy concerns ab…
… in the Simplified BSD License. 1. Introduction Transport Layer Security ( TLS [RFC5246] ) allows clients to authenticate themselves using Client Certificates. In practice, clients tend to ask for user consent before using Client Certificates. This is to allay privacy concerns ab…
…l further communication on this channel MUST run through the encrypted tunnel [ RFC5246 ]. Clients MUST use the Server Name Indication extension in the TLS handshake [ RFC6066 ]. Once a connection to the server has been established (including a connection via a proxy or over a TL…
…3 TLS_RSA_EXPORT_WITH_RC4_40_MD5 [ RFC4346 0x00,0x04 TLS_RSA_WITH_RC4_128_MD5 [ RFC5246 0x00,0x05 TLS_RSA_WITH_RC4_128_SHA [ RFC5246 0x00,0x17 TLS_DH_anon_EXPORT_WITH_RC4_40_MD5 [ RFC4346 Rescorla & Modadugu Standards Track [Page 28] RFC 6347 DTLS January 2012 0x00,0x18 TLS_DH_an…
…l further communication on this channel MUST run through the encrypted tunnel [ RFC5246 ]. Clients MUST use the Server Name Indication extension in the TLS handshake [ RFC6066 ]. Once a connection to the server has been established (including a connection via a proxy or over a TL…
…l further communication on this channel MUST run through the encrypted tunnel [ RFC5246 ]. Clients MUST use the Server Name Indication extension in the TLS handshake [ RFC6066 ]. Once a connection to the server has been established (including a connection via a proxy or over a TL…
…l further communication on this channel MUST run through the encrypted tunnel. [RFC5246] Clients MUST use the Server Name Indication extension in the TLS handshake. [RFC6066] Once a connection to the server has been established (including a connection via a proxy or over a TLS-en…
…l further communication on this channel MUST run through the encrypted tunnel [ RFC5246 ]. Clients MUST use the Server Name Indication extension in the TLS handshake [ RFC6066 ]. Once a connection to the server has been established (including a connection via a proxy or over a TL…
…nnection through an intermediary, such as when Transport Layer Security (TLS, [ RFC5246 ]) is used to establish confidential communication through a shared firewall proxy. Fielding & Reschke Standards Track [Page 10] RFC 7230 HTTP/1.1 Message Syntax and Routing June 2014 The abov…
…ll further communication on this channel MUST run through the encrypted tunnel [RFC5246]. Clients MUST use the Server Name Indication extension in the TLS handshake [RFC6066]. Once a connection to the server has been established (including a connection via a proxy or over a TLS-e…
…onnection through an intermediary, such as when Transport Layer Security (TLS, [RFC5246] ) is used to establish confidential communication through a shared firewall proxy. The above categories for intermediary only consider those acting as participants in the HTTP communication. …
…me. As an example, consider Transport Layer Security (TLS) session resumption [ RFC5246 ] or TLS session resumption without server-side state [ RFC5077 ]. In RFC 5246 RFC5246 ], a server provides the client with a session_id in the ServerHello message and caches the master_secret…