Transport Layer Security (TLS) Application Layer Protocol Negotiation Extension
draft-ietf-tls-applayerprotoneg-04

The information below is for an old version of the document
Document Type Active Internet-Draft (tls WG)
Last updated 2014-02-06 (latest revision 2014-01-24)
Replaces draft-friedl-tls-applayerprotoneg
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Joseph Salowey
Shepherd write-up Show (last changed 2014-02-02)
IESG IESG state Approved-announcement to be sent::AD Followup
Consensus Boilerplate Yes
Telechat date
Responsible AD Sean Turner
Send notices to tls-chairs@tools.ietf.org, draft-ietf-tls-applayerprotoneg@tools.ietf.org
IANA IANA review state IANA OK - Actions Needed
IANA action state None
Network Working Group                                          S. Friedl
Internet-Draft                                       Cisco Systems, Inc.
Intended status: Standards Track                                A. Popov
Expires: July 28, 2014                                   Microsoft Corp.
                                                              A. Langley
                                                             Google Inc.
                                                              E. Stephan
                                                                  Orange
                                                        January 24, 2014

 Transport Layer Security (TLS) Application Layer Protocol Negotiation
                               Extension
                   draft-ietf-tls-applayerprotoneg-04

Abstract

   This document describes a Transport Layer Security (TLS) extension
   for application layer protocol negotiation within the TLS handshake.
   For instances in which the TLS connection is established over a well
   known TCP/IP port not associated with the desired application layer
   protocol, this extension allows the application layer to negotiate
   which protocol will be used within the TLS connection.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 28, 2014.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction
   2.  Requirements Language
   3.  Application Layer Protocol Negotiation
     3.1.  The Application Layer Protocol Negotiation Extension
     3.2.  Protocol Selection
   4.  Design Considerations
   5.  Security Considerations
   6.  IANA Considerations
   7.  Acknowledgements
   8.  References
     8.1.  Normative References
     8.2.  Informative References
   Authors' Addresses

1.  Introduction

   Increasingly, application layer protocols are encapsulated in the TLS
   security 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 application protocols are supported on a single server-
   side port number, such as port 443, the client and the server need to
   negotiate an application protocol for use with each connection.  It
   is desirable to accomplish this negotiation without adding network
   round-trips between the client and the server, as each round-trip
   will degrade an end-user's experience.  Further, it would be
   advantageous to allow certificate selection based on the negotiated
   application protocol.

   This document specifies a TLS extension which permits the application
   layer to negotiate protocol selection within the TLS handshake.  This
   work was requested by the HTTPbis WG to address the negotiation of
   HTTP version ([RFC2616], [I-D.ietf-httpbis-http2]) over TLS, however
   ALPN facilitates negotiation of arbitrary application layer
   protocols.

   With ALPN, the client sends the list of supported application
   protocols as part of the TLS ClientHello message.  The server chooses
   a protocol and sends the selected protocol as part of the TLS
   ServerHello message.  The application protocol negotiation can thus
   be accomplished within the TLS handshake, without adding network
   round-trips, and allows the server to associate a different
   certificate with each application protocol, if desired.

2.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

3.  Application Layer Protocol Negotiation
Show full document text