[TLS] RFC 7918 on Transport Layer Security (TLS) False Start

rfc-editor@rfc-editor.org Wed, 10 August 2016 22:05 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E03C12D675; Wed, 10 Aug 2016 15:05:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.869
X-Spam-Level:
X-Spam-Status: No, score=-103.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.247, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Iu7lbKWJc3yt; Wed, 10 Aug 2016 15:04:59 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB0DC12D0DF; Wed, 10 Aug 2016 15:04:59 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B1F48B80B40; Wed, 10 Aug 2016 15:04:59 -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
Message-Id: <20160810220459.B1F48B80B40@rfc-editor.org>
Date: Wed, 10 Aug 2016 15:04:59 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/IfaENg-FHSIY22Vf6tf7NApvnFM>
Cc: drafts-update-ref@iana.org, tls@ietf.org, rfc-editor@rfc-editor.org
Subject: [TLS] RFC 7918 on Transport Layer Security (TLS) False Start
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2016 22:05:02 -0000

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

        
        RFC 7918

        Title:      Transport Layer Security (TLS) False Start 
        Author:     A. Langley,
                    N. Modadugu,
                    B. Moeller
        Status:     Informational
        Stream:     IETF
        Date:       August 2016
        Mailbox:    agl@google.com, 
                    nagendra@cs.stanford.edu, 
                    bmoeller@acm.org
        Pages:      11
        Characters: 23825
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tls-falsestart-02.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7918

This document specifies an optional behavior of Transport Layer
Security (TLS) client implementations, dubbed "False Start".  It
affects only protocol timing, not on-the-wire protocol data, and can
be implemented unilaterally.  A TLS False Start reduces handshake
latency to one round trip.

This document is a product of the Transport Layer Security Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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