Re: [TLS] RFC 7924 on Transport Layer Security (TLS) Cached Information Extension

Sean Turner <sean@sn3rd.com> Thu, 21 July 2016 09:22 UTC

Return-Path: <sean@sn3rd.com>
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 D208E12DC4E for <tls@ietfa.amsl.com>; Thu, 21 Jul 2016 02:22:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.com
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 1QUGbOb2XTsU for <tls@ietfa.amsl.com>; Thu, 21 Jul 2016 02:22:13 -0700 (PDT)
Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D847E12D0AC for <tls@ietf.org>; Thu, 21 Jul 2016 02:22:12 -0700 (PDT)
Received: by mail-qk0-x233.google.com with SMTP id o67so68401796qke.1 for <tls@ietf.org>; Thu, 21 Jul 2016 02:22:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=irLcqk0Z7KbHsenmbDwXe+R+peqG+sut6aCO+ZZlDEg=; b=B/ZDwPa7M5HfOBShzWYliK2iX8kznOySVGt5oFbAmhDrcGyn2HlEHbrURbxDByN+A7 Q2+bavkz/6lutnWC4bDBe0b5Ci6lGaL10iKZ20O/JQTtDRe2pHLuxssTFencdycfmMpr vRlDbpaRzSyrlUWtBJf6W20oQ3z1obn9nxEoQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=irLcqk0Z7KbHsenmbDwXe+R+peqG+sut6aCO+ZZlDEg=; b=BM9ywM8jz6Pi+J/rqWK8DCtKDl2othLDN+mYFzEFglOWebYUhWOXPOvqSfeCn5GRZt ylEGtd9gAsZPYTZYLFdWUXdAIE7e9gcvuWqFkFshmDmV/9r6qvA1UC8ZgLkWwGCOKHpg kgnP0qRRaj9pf+rBWVm0CXMAFB+xDJ+MSQX1tj2w0tDeeCzlkeSMGh8n2qFAuK9K3lEE a6AO4uYWnUEsejYZxG29gRnsadafBM1MhiY59Vh2yjyZXYy8nqQTmfv53iIVNQWYRuUH guQhwL1LjXx0xt2yCsMV/T0lhf9bRGbbTJkikuZ7h+5brjUcYC+j6LU+vfS8sBgqiE0N txAw==
X-Gm-Message-State: ALyK8tIOidLbMuLwhx2RXhJpjfPBOOP5PrnF3WAsomfL13TieK8ovkOFIXkXQl4MI2umcQ==
X-Received: by 10.55.136.133 with SMTP id k127mr26187202qkd.0.1469092931898; Thu, 21 Jul 2016 02:22:11 -0700 (PDT)
Received: from [172.16.0.112] ([96.231.230.69]) by smtp.gmail.com with ESMTPSA id l22sm3774607qtl.34.2016.07.21.02.22.10 for <tls@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 21 Jul 2016 02:22:11 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <20160719140100.B2F20B80E05@rfc-editor.org>
Date: Thu, 21 Jul 2016 05:22:09 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9703F211-2396-40C4-91CE-C98EEA024C0F@sn3rd.com>
References: <20160719140100.B2F20B80E05@rfc-editor.org>
To: "<tls@ietf.org>" <tls@ietf.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/U3CRH3wkrrmSvX-6tAr5yhZa68g>
Subject: Re: [TLS] RFC 7924 on Transport Layer Security (TLS) Cached Information Extension
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: Thu, 21 Jul 2016 09:22:15 -0000

Congrats to all involved!

spt

> On Jul 19, 2016, at 10:01, rfc-editor@rfc-editor.org wrote:
> 
> A new Request for Comments is now available in online RFC libraries.
> 
> 
>        RFC 7924
> 
>        Title:      Transport Layer Security (TLS) Cached 
>                    Information Extension 
>        Author:     S. Santesson, H. Tschofenig
>        Status:     Standards Track
>        Stream:     IETF
>        Date:       July 2016
>        Mailbox:    sts@aaa-sec.com, 
>                    Hannes.Tschofenig@gmx.net
>        Pages:      19
>        Characters: 35144
>        Updates/Obsoletes/SeeAlso:   None
> 
>        I-D Tag:    draft-ietf-tls-cached-info-23.txt
> 
>        URL:        https://www.rfc-editor.org/info/rfc7924
> 
>        DOI:        http://dx.doi.org/10.17487/RFC7924
> 
> Transport Layer Security (TLS) handshakes often include fairly static
> information, such as the server certificate and a list of trusted
> certification authorities (CAs).  This information can be of
> considerable size, particularly if the server certificate is bundled
> with a complete certificate chain (i.e., the certificates of
> intermediate CAs up to the root CA).
> 
> This document defines an extension that allows a TLS client to inform
> a server of cached information, thereby enabling the server to omit
> already available information.
> 
> This document is a product of the Transport Layer Security Working Group of the IETF.
> 
> This is now a Proposed Standard.
> 
> STANDARDS TRACK: This document specifies an Internet Standards Track
> protocol for the Internet community, and requests discussion and suggestions
> for improvements.  Please refer to the current edition of the Official
> Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
> standardization state and status of this protocol.  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
> 
> 
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls