draft-ietf-tram-alpn-06.txt   draft-ietf-tram-alpn-07.txt 
TRAM P. Patil TRAM P. Patil
Internet-Draft T. Reddy Internet-Draft T. Reddy
Intended status: Standards Track G. Salgueiro Intended status: Standards Track G. Salgueiro
Expires: April 9, 2015 Cisco Expires: May 2, 2015 Cisco
M. Petit-Huguenin M. Petit-Huguenin
Impedance Mismatch Impedance Mismatch
October 6, 2014 October 29, 2014
Application Layer Protocol Negotiation (ALPN) labels for Session Application Layer Protocol Negotiation (ALPN) labels for Session
Traversal Utilities for NAT (STUN) Usages Traversal Utilities for NAT (STUN) Usages
draft-ietf-tram-alpn-06 draft-ietf-tram-alpn-07
Abstract Abstract
Application Layer Protocol Negotiation (ALPN) labels for Session Application Layer Protocol Negotiation (ALPN) labels for Session
Traversal Utilities for NAT (STUN) usages, such as Traversal Using Traversal Utilities for NAT (STUN) usages, such as Traversal Using
Relays around NAT (TURN) and NAT discovery, are defined in this Relays around NAT (TURN) and NAT discovery, are defined in this
document to allow an application layer negotiate STUN usages within document to allow an application layer negotiate STUN usages within
the Transport Layer Security (TLS) connection. ALPN protocol the Transport Layer Security (TLS) connection. ALPN protocol
identifiers defined in this document apply to both TLS and Datagram identifiers defined in this document apply to both TLS and Datagram
Transport Layer Security (DTLS). Transport Layer Security (DTLS).
skipping to change at page 1, line 40 skipping to change at page 1, line 40
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 9, 2015. This Internet-Draft will expire on May 2, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. ALPN Labels for STUN . . . . . . . . . . . . . . . . . . . . 3 2. ALPN Labels for STUN . . . . . . . . . . . . . . . . . . . . 2
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
6.1. Normative References . . . . . . . . . . . . . . . . . . 4 6.1. Normative References . . . . . . . . . . . . . . . . . . 4
6.2. Informative References . . . . . . . . . . . . . . . . . 4 6.2. Informative References . . . . . . . . . . . . . . . . . 4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction 1. Introduction
STUN can be securely transported using TLS-over-TCP (referred to as STUN can be securely transported using TLS-over-TCP (referred to as
TLS [RFC5246]), as specified in [RFC5389], or TLS-over-UDP (referred TLS [RFC5246]), as specified in [RFC5389], or TLS-over-UDP (referred
to as DTLS [RFC6347]), as specified in [RFC7350]. to as DTLS [RFC6347]), as specified in [RFC7350].
ALPN [RFC7301] enables an endpoint to positively identify an ALPN [RFC7301] enables an endpoint to positively identify an
application protocol in TLS/DTLS and distinguish it from other TLS/ application protocol in TLS/DTLS and distinguish it from other TLS/
DTLS protocols. With ALPN, the client sends the list of supported DTLS protocols. With ALPN, the client sends the list of supported
application protocols as part of the TLS/DTLS ClientHello message. application protocols as part of the TLS/DTLS ClientHello message.
The server chooses a protocol and sends the selected protocol as part The server chooses a protocol and sends the selected protocol as part
of the TLS/DTLS ServerHello message. Application protocol of the TLS/DTLS ServerHello message. Application protocol
negotiation can thus be accomplished within the TLS/DTLS handshake, negotiation can thus be accomplished within the TLS/DTLS handshake,
without adding network round-trips. without adding network round-trips.
STUN protocol usages, such as TURN [RFC5766], can be used to identify STUN protocol usages, such as TURN [RFC5766], can be used to identify
the purpose of a flow without initiating a session. This capability the purpose of a flow without initiating a session.
is useful and adds efficiency, as shown in the following scenarios.
1. Consider an Enterprise network that deploys a TURN server in a
DeMilitarized Zone (DMZ) to audit all media sessions from inside
the Enterprise premises to any external peer. In this
deployment, an Enterprise firewall could use the TURN ALPN
identifier to detect the use of a TURN server that is outside the
Enterprise domain (i.e., a TURN server provided by an application
server, access network, etc).
2. If a firewall is configured to block all outgoing traffic except
for TCP traffic to specific ports (e.g., 443 for HTTPS), a TURN
server listening on its default ports (3478 for TCP/UDP, 5349 for
TLS) would not be reachable. However, despite the restrictions
imposed by the firewall, a TURN server can still be reached on
the allowed HTTPS port if the TURN ALPN identifier is used to
establish usage of TURN as part of the TLS handshake.
This document defines entries in the "Application Layer Protocol This document defines entries in the "Application Layer Protocol
Negotiation (ALPN) Protocol IDs" registry established by [RFC7301] to Negotiation (ALPN) Protocol IDs" registry established by [RFC7301] to
identify STUN protocol usages. identify STUN protocol usages.
2. ALPN Labels for STUN 2. ALPN Labels for STUN
The document proposes the following ALPN labels to identify STUN The document proposes the following ALPN labels to identify STUN
protocol [RFC5389] usages. protocol [RFC5389] usages.
 End of changes. 8 change blocks. 
26 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/