RFC 7443: Application-Layer Protocol Negotiation (ALPN) Labels for Session Traversal Utilities for NAT (STUN) Usages
In plain English — editorial summary, not part of the RFC
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).
Document record
- Document ID
- RFC7443
- Published
- January 2015
- Authors
- P. Patil; T. Reddy; G. Salgueiro; M. Petit-Huguenin
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 5
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7430Analysis of Residual Threats and Possible Fixes for Multipath TCP (MPTCP)Current
July 2015
- RFC 7376Problems with Session Traversal Utilities for NAT (STUN) Long-Term Authentication for Traversal Using Relays around NAT (TURN)Current
September 2014
- RFC 7350Datagram Transport Layer Security (DTLS) as Transport for Session Traversal Utilities for NAT (STUN)Current
August 2014
- RFC 7567IETF Recommendations Regarding Active Queue ManagementCurrent
July 2015
- RFC 7574Peer-to-Peer Streaming Peer Protocol (PPSPP)Current
July 2015
- RFC 7306Remote Direct Memory Access (RDMA) Protocol ExtensionsCurrent
June 2014
- RFC 7635Session Traversal Utilities for NAT (STUN) Extension for Third-Party AuthorizationCurrent
August 2015
- RFC 7713Congestion Exposure (ConEx) Concepts, Abstract Mechanism, and RequirementsCurrent
December 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?