RFC 8701 on Applying Generate Random Extensions And Sustain Extensibility (GREASE) to TLS Extensibility

rfc-editor@rfc-editor.org Wed, 29 January 2020 20:34 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3699A120048; Wed, 29 Jan 2020 12:34:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7-oZ1mJ-UtW3; Wed, 29 Jan 2020 12:34:03 -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 0F809120045; Wed, 29 Jan 2020 12:34:03 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 90690F406C4; Wed, 29 Jan 2020 12:33:57 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8701 on Applying Generate Random Extensions And Sustain Extensibility (GREASE) to TLS Extensibility
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: <20200129203357.90690F406C4@rfc-editor.org>
Date: Wed, 29 Jan 2020 12:33:57 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/We86F8igx_ROKOSJm0pbPZBKi0k>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2020 20:34:08 -0000

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

        
        RFC 8701

        Title:      Applying Generate Random Extensions And 
                    Sustain Extensibility (GREASE) to TLS Extensibility 
        Author:     D. Benjamin
        Status:     Informational
        Stream:     IETF
        Date:       January 2019
        Mailbox:    davidben@google.com
        Pages:      12
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tls-grease-04.txt

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

        DOI:        10.17487/RFC8701

This document describes GREASE (Generate Random Extensions And
Sustain Extensibility), a mechanism to prevent extensibility failures
in the TLS ecosystem. It reserves a set of TLS protocol values that
may be advertised to ensure peers correctly handle unknown values.

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