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

The information below is for an old version of the document
Document Type Active Internet-Draft (tls WG)
Last updated 2013-04-08
Replaces draft-friedl-tls-applayerprotoneg
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        S.F. Friedl
Internet-Draft                                       Cisco Systems, Inc.
Intended status: Standards Track                              A.P. Popov
Expires: October 07, 2013                                Microsoft Corp.
                                                          April 05, 2013

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

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 session.

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 October 07, 2013.

Copyright Notice

   Copyright (c) 2013 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

Friedl & Popov          Expires October 07, 2013                [Page 1]
Internet-Draft   TLS App Layer Protocol Negotiation Ext       April 2013

   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
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  Application Layer Protocol Negotiation  . . . . . . . . . . .   3
     3.1.  The Application Layer Protocol Negotiation Extension  . .   3
     3.2.  Protocol Selection  . . . . . . . . . . . . . . . . . . .   5
   4.  Design Considerations . . . . . . . . . . . . . . . . . . . .   6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   Currently, the Next Protocol Negotiation extension (NPN) is used to
   establish a SPDY [spdy] protocol session within a TLS RFC 5246
   [RFC5246] session on port 443.  NPN is not specific to SPDY and can
   be used to negotiate sessions for a wide variety of protocols within
   the TLS handshake.

   NPN seeks to provide a reliable mechanism for application developers
   to establish secure sessions for arbitrary protocols without
   interference from firewalls, HTTP proxies and MITM proxies.  It
   addresses this goal by introducing a protocol negotiation process
   into the TLS handshake under the constraints that no additional
   roundtrips be added to the handshake and that the final protocol
   selection be opaque to the network carrying the TLS session.  Within
   the NPN extension, it is the server that first generates and
   transmits an offer of supported protocols to the client.  The offer
   is sent as part of the TLS ServerHello message before the
   [ChangeCipherSpec] subprotocol has been started, therefore the list
   of protocols supported by the server is transmitted in plaintext.
   The client chooses a protocol which may or may not appear in the
   offer from the server and then responds with the definitive protocol
   selection answer.  The client response is sent after the
   [ChangeCipherSpec] subprotocol has been initiated, so the protocol
   selected is encrypted in the client response.

   In many other application layer protocol negotiation processes, it is
Show full document text