Cryptographic protection of TCP Streams (tcpcrypt)
draft-bittau-tcpinc-tcpcrypt-03

The information below is for an old version of the document
Document Type Active Internet-Draft (individual in tsv area)
Last updated 2015-10-14 (latest revision 2015-07-02)
Replaced by draft-ietf-tcpinc-tcpcrypt, rfc8548
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state AD is watching
Consensus Boilerplate Unknown
Telechat date
Responsible AD Martin Stiemerling
Send notices to (None)
Internet Engineering Task Force                                A. Bittau
Internet-Draft                                                  D. Boneh
Intended status: Standards Track                               D. Giffin
Expires: January 3, 2016                                      M. Hamburg
                                                     Stanford University
                                                              M. Handley
                                               University College London
                                                             D. Mazieres
                                                                Q. Slack
                                                     Stanford University
                                                            July 2, 2015

           Cryptographic protection of TCP Streams (tcpcrypt)
                  draft-bittau-tcpinc-tcpcrypt-03.txt

Abstract

   This document presents tcpcrypt, a TCP extension for
   cryptographically protecting TCP connections.  Tcpcrypt maintains the
   confidentiality of data transmitted in TCP connections against a
   passive eavesdropper.  Additionally, applications that perform
   authentication can obtain end-to-end confidentiality and integrity
   guarantees by tying authentication to tcpcrypt Session ID values.

   The extension defines a new TCP option, CRYPT, which is designed to
   provide compatible interworking with TCPs that do not implement
   tcpcrypt.  The CRYPT option allows hosts to negotiate the use of
   tcpcrypt and establish shared, secret encryption keys.  These keys
   are then used with an authenticated-encryption mode to protect both
   the confidentiality and the integrity of transmitted application
   data.  Tcpcrypt is designed to require relatively low overhead,
   particularly at servers, so as to be useful even in the case of
   servers accepting many TCP connections per second.

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

Bittau, et al.           Expires January 3, 2016                [Page 1]
Internet-Draft                  tcpcrypt                       July 2015

   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 January 3, 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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Requirements Language . . . . . . . . . . . . . . . . . . . .   4
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Idealized protocol  . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Stages of the protocol  . . . . . . . . . . . . . . . . .   5
       3.1.1.  The setup phase . . . . . . . . . . . . . . . . . . .   5
       3.1.2.  The ENCRYPTING state  . . . . . . . . . . . . . . . .   6
       3.1.3.  The DISABLED state  . . . . . . . . . . . . . . . . .   6
     3.2.  Cryptographic algorithms  . . . . . . . . . . . . . . . .   6
     3.3.  "C" and "S" roles . . . . . . . . . . . . . . . . . . . .   8
     3.4.  Protocol negotiation  . . . . . . . . . . . . . . . . . .   8
     3.5.  Key exchange protocol . . . . . . . . . . . . . . . . . .   8
Show full document text