[tcpinc] RFC 8548 on Cryptographic Protection of TCP Streams (tcpcrypt)

rfc-editor@rfc-editor.org Wed, 22 May 2019 15:52 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: tcpinc@ietfa.amsl.com
Delivered-To: tcpinc@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 6418D1201EA; Wed, 22 May 2019 08:52:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id NbOoldLEZJ3a; Wed, 22 May 2019 08:52:11 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 521511201EB; Wed, 22 May 2019 08:52:11 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 636B0B82435; Wed, 22 May 2019 08:51:49 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, tcpinc@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20190522155149.636B0B82435@rfc-editor.org>
Date: Wed, 22 May 2019 08:51:49 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpinc/Fd0pd2Axldts1KCC7t7yg_hE9Xs>
Subject: [tcpinc] =?utf-8?q?RFC_8548_on_Cryptographic_Protection_of_TCP_S?= =?utf-8?q?treams_=28tcpcrypt=29?=
X-BeenThere: tcpinc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Working group mailing list for TCP Increased Security \(tcpinc\)" <tcpinc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpinc>, <mailto:tcpinc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpinc/>
List-Post: <mailto:tcpinc@ietf.org>
List-Help: <mailto:tcpinc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpinc>, <mailto:tcpinc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 May 2019 15:52:22 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 8548

        Title:      Cryptographic Protection of TCP Streams (tcpcrypt) 
        Author:     A. Bittau,
                    D. Giffin,
                    M. Handley,
                    D. Mazieres,
                    Q. Slack,
                    E. Smith
        Status:     Experimental
        Stream:     IETF
        Date:       May 2019
        Mailbox:    bittau@google.com, 
        Pages:      32
        Characters: 75149
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tcpinc-tcpcrypt-15.txt

        URL:        https://www.rfc-editor.org/info/rfc8548

        DOI:        10.17487/RFC8548

This document specifies "tcpcrypt", a TCP encryption protocol
designed for use in conjunction with the TCP Encryption Negotiation
Option (TCP-ENO).  Tcpcrypt coexists with middleboxes by tolerating
resegmentation, NATs, and other manipulations of the TCP header.  The
protocol is self-contained and specifically tailored to TCP
implementations, which often reside in kernels or other environments
in which large external software dependencies can be undesirable.
Because the size of TCP options is limited, the protocol requires one
additional one-way message latency to perform key exchange before
application data can be transmitted.  However, the extra latency can
be avoided between two hosts that have recently established a
previous tcpcrypt connection.

This document is a product of the TCP Increased Security Working Group of the IETF.

EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC