Legacy RSASSA-PKCS1-v1_5 codepoints for TLS 1.3
draft-davidben-tls13-pkcs1-00

Document Type Active Internet-Draft (individual)
Last updated 2019-07-29
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
tls                                                          D. Benjamin
Internet-Draft                                                Google LLC
Intended status: Experimental                              July 29, 2019
Expires: January 30, 2020

            Legacy RSASSA-PKCS1-v1_5 codepoints for TLS 1.3
                     draft-davidben-tls13-pkcs1-00

Abstract

   This document allocates code points for the use of RSASSA-PKCS1-v1_5
   with client certificates in TLS 1.3.

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 https://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 30, 2020.

Copyright Notice

   Copyright (c) 2019 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
   (https://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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Benjamin                Expires January 30, 2020                [Page 1]
Internet-Draft    Legacy PKCS#1 codepoints for TLS 1.3         July 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions and Definitions . . . . . . . . . . . . . . . . .   2
   3.  PKCS#1 v1.5 SignatureScheme Types . . . . . . . . . . . . . .   2
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   TLS 1.3 [RFC8446] removed support for RSASSA-PKCS1-v1_5 [RFC8017] in
   CertificateVerify messages in favor of RSASSA-PSS.  While RSASSA-PSS
   is a long-established signature algorithm, some legacy hardware
   cryptographic devices lack support for it.  Due to performance
   requirements, such devices are uncommon in TLS servers, but are
   sometimes used by TLS clients for client certificates.  Moreover, TLS
   negotiates the protocol version before client certificates, so this
   limitation can further impact adjacent connections that do not use
   affected keys.

   This document allocates code points to use these legacy keys with
   client certificates in TLS 1.3.

2.  Conventions and Definitions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

3.  PKCS#1 v1.5 SignatureScheme Types

   The following SignatureScheme values are defined for use with TLS
   1.3.

       enum {
           rsa_pkcs1_sha256_legacy(TBD1),
           rsa_pkcs1_sha384_legacy(TBD2),
           rsa_pkcs1_sha512_legacy(TBD3),
       } SignatureScheme;

   The above code points indicate a signature algorithm using RSASSA-
   PKCS1-v1_5 [RFC8017] with the corresponding hash algorithm as defined

Benjamin                Expires January 30, 2020                [Page 2]
Internet-Draft    Legacy PKCS#1 codepoints for TLS 1.3         July 2019

   in [SHS].  They are only defined for signatures in the client
   CertificateVerify message and are not defined for use in other
   contexts.  In particular, servers intending to advertise support for
   RSASSA-PKCS1-v1_5 signatures in the certificates themselves should
   use the rsa_pkcs1_* constants defined in [RFC8446].

   Clients MUST NOT advertise these values in the "signature_algorithms"
   extension of the ClientHello.  They MUST NOT accept these values in
   the server CertificateVerify message.

   Servers that wish to support clients authenticating with legacy
   RSASSA-PKCS1-v1_5-only keys MAY send these values in the
Show full document text