A Survey of the Interaction Between Security Protocols and Transport Services
draft-ietf-taps-transport-security-12

Document Type Active Internet-Draft (taps WG)
Last updated 2020-04-29 (latest revision 2020-04-23)
Replaces draft-pauly-taps-transport-security
Stream IETF
Intended RFC status Informational
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
Reviews
Additional URLs
- Document source repository
- Mailing list discussion
Stream WG state Submitted to IESG for Publication
Document shepherd Philipp Tiesel
Shepherd write-up Show (last changed 2019-10-04)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Magnus Westerlund
Send notices to Philipp Tiesel <philipp@tiesel.net>, caw@heapingbits.net
IANA IANA review state Version Changed - Review Needed
IANA action state No IANA Actions
RFC Editor RFC Editor state EDIT
Network Working Group                                        T. Enghardt
Internet-Draft                                                 TU Berlin
Intended status: Informational                                  T. Pauly
Expires: 25 October 2020                                      Apple Inc.
                                                              C. Perkins
                                                   University of Glasgow
                                                                 K. Rose
                                               Akamai Technologies, Inc.
                                                               C.A. Wood
                                                              Cloudflare
                                                           23 April 2020

  A Survey of the Interaction Between Security Protocols and Transport
                                Services
                 draft-ietf-taps-transport-security-12

Abstract

   This document provides a survey of commonly used or notable network
   security protocols, with a focus on how they interact and integrate
   with applications and transport protocols.  Its goal is to supplement
   efforts to define and catalog transport services by describing the
   interfaces required to add security protocols.  This survey is not
   limited to protocols developed within the scope or context of the
   IETF, and those included represent a superset of features a Transport
   Services system may need to support.

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 https://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 25 October 2020.

Enghardt, et al.         Expires 25 October 2020                [Page 1]
Internet-Draft          Transport Security Survey             April 2020

Copyright Notice

   Copyright (c) 2020 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 (https://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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Goals . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.2.  Non-Goals . . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Transport Security Protocol Descriptions  . . . . . . . . . .   6
     3.1.  Application Payload Security Protocols  . . . . . . . . .   7
       3.1.1.  TLS . . . . . . . . . . . . . . . . . . . . . . . . .   7
       3.1.2.  DTLS  . . . . . . . . . . . . . . . . . . . . . . . .   7
     3.2.  Application-Specific Security Protocols . . . . . . . . .   8
       3.2.1.  Secure RTP  . . . . . . . . . . . . . . . . . . . . .   8
     3.3.  Transport-Layer Security Protocols  . . . . . . . . . . .   8
       3.3.1.  IETF QUIC . . . . . . . . . . . . . . . . . . . . . .   8
       3.3.2.  Google QUIC . . . . . . . . . . . . . . . . . . . . .   9
       3.3.3.  tcpcrypt  . . . . . . . . . . . . . . . . . . . . . .   9
       3.3.4.  MinimaLT  . . . . . . . . . . . . . . . . . . . . . .   9
       3.3.5.  CurveCP . . . . . . . . . . . . . . . . . . . . . . .   9
     3.4.  Packet Security Protocols . . . . . . . . . . . . . . . .   9
       3.4.1.  IPsec . . . . . . . . . . . . . . . . . . . . . . . .  10
       3.4.2.  WireGuard . . . . . . . . . . . . . . . . . . . . . .  10
       3.4.3.  OpenVPN . . . . . . . . . . . . . . . . . . . . . . .  10
   4.  Transport Dependencies  . . . . . . . . . . . . . . . . . . .  10
     4.1.  Reliable Byte-Stream Transports . . . . . . . . . . . . .  10
     4.2.  Unreliable Datagram Transports  . . . . . . . . . . . . .  11
       4.2.1.  Datagram Protocols with Defined Byte-Stream
               Mappings  . . . . . . . . . . . . . . . . . . . . . .  11
     4.3.  Transport-Specific Dependencies . . . . . . . . . . . . .  12
   5.  Application Interface . . . . . . . . . . . . . . . . . . . .  12
Show full document text