[TLS] RFC 8879 on TLS Certificate Compression

rfc-editor@rfc-editor.org Wed, 02 December 2020 07:32 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 349AC3A113E; Tue, 1 Dec 2020 23:32:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 N0pFG841II0J; Tue, 1 Dec 2020 23:32:46 -0800 (PST)
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 CB9E53A1138; Tue, 1 Dec 2020 23:32:46 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 20E60F40758; Tue, 1 Dec 2020 23:32:44 -0800 (PST)
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, tls@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20201202073244.20E60F40758@rfc-editor.org>
Date: Tue, 1 Dec 2020 23:32:44 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/gFQFp0sZ3Vw81bE4I8swJ_arnLU>
Subject: [TLS] =?utf-8?q?RFC_8879_on_TLS_Certificate_Compression?=
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.29
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, 02 Dec 2020 07:32:48 -0000

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

        
        RFC 8879

        Title:      TLS Certificate Compression 
        Author:     A. Ghedini,
                    V. Vasiliev
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2020
        Mailbox:    alessandro@cloudflare.com, 
                    vasilvv@google.com
        Pages:      8
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tls-certificate-compression-10.txt

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

        DOI:        10.17487/RFC8879

In TLS handshakes, certificate chains often take up the majority of
the bytes transmitted.

This document describes how certificate chains can be compressed to
reduce the amount of data transmitted and avoid some round trips.

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