[tcpinc] RFC 8547 on TCP-ENO: Encryption Negotiation Option

rfc-editor@rfc-editor.org Wed, 22 May 2019 15:51 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 29575120199; Wed, 22 May 2019 08:51:56 -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 4GgSaBgkp5xN; Wed, 22 May 2019 08:51:53 -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 CA422120158; Wed, 22 May 2019 08:51:53 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id DE4D5B82426; Wed, 22 May 2019 08:51:31 -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: <20190522155131.DE4D5B82426@rfc-editor.org>
Date: Wed, 22 May 2019 08:51:31 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpinc/gqHSk6OteTtVVkI15gV4Z4hJuwI>
Subject: [tcpinc] =?utf-8?q?RFC_8547_on_TCP-ENO=3A_Encryption_Negotiation?= =?utf-8?q?_Option?=
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:51:56 -0000

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

        RFC 8547

        Title:      TCP-ENO: Encryption Negotiation Option 
        Author:     A. Bittau,
                    D. Giffin,
                    M. Handley,
                    D. Mazieres,
                    E. Smith
        Status:     Experimental
        Stream:     IETF
        Date:       May 2019
        Mailbox:    bittau@google.com, 
        Pages:      31
        Characters: 72176
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tcpinc-tcpeno-19.txt

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

        DOI:        10.17487/RFC8547

Despite growing adoption of TLS, a significant fraction of TCP
traffic on the Internet remains unencrypted.  The persistence of
unencrypted traffic can be attributed to at least two factors.
First, some legacy protocols lack a signaling mechanism (such as a
STARTTLS command) by which to convey support for encryption, thus
making incremental deployment impossible.  Second, legacy
applications themselves cannot always be upgraded and therefore
require a way to implement encryption transparently entirely within
the transport layer.  The TCP Encryption Negotiation Option (TCP-ENO)
addresses both of these problems through a new TCP option kind
providing out-of-band, fully backward-compatible negotiation of

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