About: Application-Layer Protocol Negotiation is a research topic. Over the lifetime, 5 publications have been published within this topic receiving 71 citations. The topic is also known as: ALPN.
TL;DR: This document describes a Transport Layer Security (TLS) extension for application-layer protocol negotiation within the TLS handshake that allows the application layer to negotiate which protocol will be used within a TLS connection.
Abstract: This document describes a Transport Layer Security (TLS) extension for
application-layer protocol negotiation within the TLS handshake. For
instances in which multiple application protocols are supported on the
same TCP or UDP port, this extension allows the application layer to
negotiate which protocol will be used within the TLS connection.
TL;DR: This document describes two alternative methods for an user-agent to automatically discover and for an users to provide consent for a Trusted Proxy to be securely involved when he or she is requesting an HTTP URI resource over HTTP2 with TLS.
Abstract: The purpose of this Internet Draft is to continue the discussion on
explicit and trusted proxy as intermediary of HTTP2 traffic. The
httpbis wg has agreed on the HTTP2 usage with HTTP URIs, with or
without TLS, without any constraints from the standard (see: issue
314). To distinguish between an HTTP2 connection meant to transport
"https" URIs resources and an HTTP2 connection meant to transport
"http" URIs resource, the draft proposes to register a new value in
the Application Layer Protocol negotiation (ALPN) Protocol IDs
registry specific to signal the usage of HTTP2 to transport "http"
URIs resources: h2clr. This document describes two alternative methods
for an user-agent to automatically discover and for an user to provide
consent for a Trusted Proxy to be securely involved when he or she is
requesting an HTTP URI resource over HTTP2 with TLS. The consent is
supposed to be per network access. The draft also describes the role
of the Trusted Proxy in helping the user to fetch HTTP URIs resource
when the user has provided consent to the Trusted Proxy to be
involved.
TL;DR: This document specifies a new challenge for the Automated Certificate Management Environment (ACME) protocol that allows for domain control validation using TLS.
Abstract: This document specifies a new challenge for the Automated Certificate
Management Environment (ACME) protocol that allows for domain control
validation using TLS.
TL;DR: This document specifies two Application Layer Protocol Negotiation (ALPN) labels for use with Web Real-Time Communications (WebRTC), and the "c-webrtc" label describes the same protocol, but the peers also agree to maintain the confidentiality of the media by not sharing it with other applications.
Abstract: This document specifies two Application Layer Protocol Negotiation
(ALPN) labels for use with Web Real-Time Communications (WebRTC). The
"webrtc" label identifies regular WebRTC communications: a DTLS
session that is used establish keys for Secure Real-time Transport
Protocol (SRTP) or to establish data channels using SCTP over DTLS.
The "c-webrtc" label describes the same protocol, but the peers also
agree to maintain the confidentiality of the media by not sharing it
with other applications.
TL;DR: Application-Layer Protocol Negotiation labels for Session Traversal Utilities for NAT (STUN) usages, such asTraversal Using Relays around NAT (TURN) and NAT discovery, are defined in this document to allow an application layer to negotiate STUN usages within the Transport Layer Security (TLS) connection.
Abstract: Application-Layer Protocol Negotiation (ALPN) labels for Session
Traversal Utilities for NAT (STUN) usages, such as Traversal Using
Relays around NAT (TURN) and NAT discovery, are defined in this
document to allow an application layer to negotiate STUN usages within
the Transport Layer Security (TLS) connection. ALPN protocol
identifiers defined in this document apply to both TLS and Datagram
Transport Layer Security (DTLS).