Applying GREASE to TLS Extensibility
draft-davidben-tls-grease-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-07-25
Replaced by draft-ietf-tls-grease
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        D. Benjamin
Internet-Draft                                                    Google
Updates: 5246 (if approved)                                July 25, 2016
Intended status: Informational
Expires: January 26, 2017

                  Applying GREASE to TLS Extensibility
                      draft-davidben-tls-grease-00

Abstract

   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 by clients to ensure servers correctly handle
   unknown values.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 26, 2017.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Benjamin                Expires January 26, 2017                [Page 1]
Internet-Draft    Applying GREASE to TLS Extensibility         July 2016

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  GREASE Values . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Client Behavior . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Server Behavior . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   The TLS protocol [RFC5246] includes several points of extensibility,
   including the list of cipher suites and the list of extensions.  The
   values in these lists identify implementation capabilities.  TLS
   follows a model where clients advertise capabilities and servers
   select them.  It is required that servers ignore unknown values so
   that new capabilities may be introduced to the ecosystem while
   maintaining interoperability.

   However, bugs may cause a server to reject unknown values.  These
   broken servers will interoperate with existing clients, so the
   mistake may spread through the ecosystem unnoticed.  Later, when new
   values are defined, updated clients will discover that the
   metaphorical joint in the protocol has rusted shut and that the new
   values cannot be deployed without interoperability failures.

   To avoid this problem, this document reserves some currently unused
   values for clients to advertise at random.  Correct server
   implementations will ignore these values and interoperate.  Servers
   that do not tolerate unknown values will fail to interoperate with
   existing clients, revealing the mistake before it is widespread.
   This document reserves such values in the TLS cipher suite,
   extension, named group [RFC4492], and ALPN [RFC7301] registries.

   In keeping with the rusted joint metaphor, this technique is named
   GREASE (Generate Random Extensions And Sustain Extensibility).

Benjamin                Expires January 26, 2017                [Page 2]
Internet-Draft    Applying GREASE to TLS Extensibility         July 2016

1.1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

2.  GREASE Values

   This document reserves a number of TLS protocol values, referred to
   as GREASE values.  These values were allocated sparsely to discourage
Show full document text