Internet Engineering Task Force (IETF) P. Patil
Request for Comments: 7443 T. Reddy
Category: Informational G. Salgueiro
ISSN: 2070-1721 Cisco
M. Petit-Huguenin
Impedance Mismatch
January 2015
Application-Layer Protocol Negotiation (ALPN) Labels for Session Traversal Utilities for NAT (STUN) Usages
Patil, et al. Informational [Page 1]
RFC 7443 ALPN for STUN/TURN January 2015
Copyright Notice
1. Introduction
STUN can be securely transported using TLS-over-TCP (referred to as TLS [RFC5246]), as specified in [RFC5389], or TLS-over-UDP (referred to as DTLS [RFC6347]), as specified in [RFC7350].
Patil, et al. Informational [Page 2]
RFC 7443 ALPN for STUN/TURN January 2015
for TURN (Section 4.6 of [RFC7350]).
2. IANA Considerations
The following entries have been added to the "Application-Layer Protocol Negotiation (ALPN) Protocol IDs" registry established by [RFC7301].
3. Security Considerations
The ALPN STUN protocol identifier does not introduce any specific security considerations beyond those detailed in the TLS ALPN Extension specification [RFC7301]. It also does not impact the security of TLS/DTLS session establishment or application data exchange.
Patil, et al. Informational [Page 3]
RFC 7443 ALPN for STUN/TURN January 2015 4. References 4.1. Normative References[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
4.2. Informative References
[RFC5766] Mahy, R., Matthews, P., and J. Rosenberg, "Traversal Using
Patil, et al. Informational [Page 4]
RFC 7443 ALPN for STUN/TURN January 2015
Authors' Addresses