Using TLS to Protect TCP Streams
draft-ietf-tcpinc-use-tls-00

The information below is for an old version of the document
Document Type Active Internet-Draft (tcpinc WG)
Last updated 2015-11-02
Replaces draft-rescorla-tcpinc-tls-option
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
TCPING                                                       E. Rescorla
Internet-Draft                                                   Mozilla
Intended status: Standards Track                        November 3, 2015
Expires: May 6, 2016

                    Using TLS to Protect TCP Streams
                      draft-ietf-tcpinc-use-tls-00

Abstract

   This document defines the use of TLS [RFC5246] with the TCP-ENO
   option [I-D.bittau-tcpinc-tcpeno].

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 May 6, 2016.

Copyright Notice

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

Rescorla                   Expires May 6, 2016                  [Page 1]
Internet-Draft                 TCP-use-TLS                 November 2015

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  TCP-ENO Binding . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Suboption Definition  . . . . . . . . . . . . . . . . . .   3
     3.2.  Session ID  . . . . . . . . . . . . . . . . . . . . . . .   4
     3.3.  Channel Close . . . . . . . . . . . . . . . . . . . . . .   4
   4.  TLS Profile . . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  TLS 1.3 Profile . . . . . . . . . . . . . . . . . . . . .   5
       4.1.1.  Handshake Modes . . . . . . . . . . . . . . . . . . .   5
       4.1.2.  Basic 1-RTT Handshake . . . . . . . . . . . . . . . .   6
       4.1.3.  Hello Retry Request [6.3.1.3] . . . . . . . . . . . .  10
       4.1.4.  Zero-RTT Exchange . . . . . . . . . . . . . . . . . .  10
       4.1.5.  Key Schedule  . . . . . . . . . . . . . . . . . . . .  12
       4.1.6.  Record Protection . . . . . . . . . . . . . . . . . .  13
     4.2.  TLS 1.2 Profile . . . . . . . . . . . . . . . . . . . . .  13
     4.3.  Deprecated Features . . . . . . . . . . . . . . . . . . .  14
     4.4.  Cryptographic Algorithms  . . . . . . . . . . . . . . . .  14
   5.  Transport Integrity . . . . . . . . . . . . . . . . . . . . .  14
   6.  API Considerations  . . . . . . . . . . . . . . . . . . . . .  15
   7.  Implementation Considerations . . . . . . . . . . . . . . . .  15
   8.  NAT/Firewall considerations . . . . . . . . . . . . . . . . .  15
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  16
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  16
     11.2.  Informative References . . . . . . . . . . . . . . . . .  18

1.  Introduction

   RFC EDITOR: PLEASE REMOVE THE FOLLOWING PARAGRAPH The source for this
   draft is maintained in GitHub.  Suggested changes should be submitted
   as pull requests at https://github.com/ekr/tcpinc-tls.  Instructions
   are on that page as well.

   The TCPINC WG is chartered to define protocols to provide ubiquitous,
   transparent security for TCP connections.  The WG is specifying The
   TCP Encryption Negotiation Option (TCP-ENO)
   [I-D.bittau-tcpinc-tcpeno] which allows for negotiation of encryption
   at the TCP layer.  This document describes a binding of TLS [RFC5246]
   to TCP-ENO as what ENO calls an "encryption spec", thus allowing TCP-
   ENO to negotiate TLS.

Rescorla                   Expires May 6, 2016                  [Page 2]
Internet-Draft                 TCP-use-TLS                 November 2015

2.  Overview

   The basic idea behind this draft is simple.  The SYN and SYN/ACK
   messages carry the TCP-ENO options indicating the willingness to do
   TLS.  If both sides want to do TLS, then a TLS handshake is started
Show full document text