Use the SAN field
draft-rsalz-use-san-00

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00

TBD Working Group                                                R. Salz
Internet-Draft                                       Akamai Technologies
Intended status: Standards Track                         4 February 2021
Expires: 8 August 2021

                           Use the SAN field
                         draft-rsalz-use-san-00

Abstract

   In the decade since [RFC6125] was published, the subjectAltName
   extension, as defined in [RFC5280] has become ubiquitous.  This
   document updates [RFC6125] to specify that the fall-back techniques
   of using commonName attribute to identify the service MUST NOT be
   used.

Discussion Venues

   This note is to be removed before publishing as an RFC.

   Source for this draft and an issue tracker can be found at
   https://github.com/richsalz/draft-rsalz-use-san.

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 8 August 2021.

Copyright Notice

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

Salz                      Expires 8 August 2021                 [Page 1]
Internet-Draft              Use the SAN field              February 2021

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions and Definitions . . . . . . . . . . . . . . . . .   2
   3.  The New Rules . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Designing Application Protocols . . . . . . . . . . . . .   3
     3.2.  Representing Server Identity  . . . . . . . . . . . . . .   3
     3.3.  Verifying Service Identity  . . . . . . . . . . . . . . .   3
   4.  Constraints on Wildcards  . . . . . . . . . . . . . . . . . .   3
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   4
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .   4
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   In the decade since [RFC6125] was published, the subjectAltName
   extension, as defined in [RFC5280] has become ubiquitous.  This
   document updates [RFC6125] to specify that the fall-back techniques
   of using commonName attribute to identify the service MUST NOT be
   used.

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.

   The terminology from [RFC6125] is used here.  Specifically, the
   following terms and brief definition (as a reminder):

   *  CN-ID: the Common Name element from a Distingiushed Name.

   *  DNS-ID, SRV-ID, URI-ID: different types of entries in a
      subjectAltName extension.

Salz                      Expires 8 August 2021                 [Page 2]
Internet-Draft              Use the SAN field              February 2021

3.  The New Rules

   The CN-ID MUST NOT be used.  The appropriate value in the
   subjectAltName extension MUST be used to get the presented identity
   of the server.

   While not discussed in [RFC6125], this section also implicitly
   prohibits the use of the Domain Component or emailAddress RDN's.

   The following sections repeat the above rule in other forms, for the
   purpose of updating [RFC6125].

3.1.  Designing Application Protocols

   Applications should determine which form of name they want to use,
   and specify the appropriate subjectAltName extension.  Unless there
   are reasons to do otherwise, applications SHOULD use the DNS-ID form.