Re: [Uta] Benjamin Kaduk's Discuss on draft-ietf-uta-smtp-require-tls-08: (with DISCUSS and COMMENT)

Viktor Dukhovni <ietf-dane@dukhovni.org> Wed, 31 July 2019 09:08 UTC

Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: uta@ietfa.amsl.com
Delivered-To: uta@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACBED1200F4; Wed, 31 Jul 2019 02:08:45 -0700 (PDT)
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_HELO_NONE=0.001, SPF_PASS=-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 EX3ekemGoJhs; Wed, 31 Jul 2019 02:08:44 -0700 (PDT)
Received: from straasha.imrryr.org (straasha.imrryr.org [100.2.39.101]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DF381200EF; Wed, 31 Jul 2019 02:08:43 -0700 (PDT)
Received: by straasha.imrryr.org (Postfix, from userid 1001) id 6DE2D43DB7; Wed, 31 Jul 2019 05:08:42 -0400 (EDT)
Date: Wed, 31 Jul 2019 05:08:42 -0400
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: uta@ietf.org
Cc: The IESG <iesg@ietf.org>
Message-ID: <20190731090842.GB24255@straasha.imrryr.org>
Reply-To: uta@ietf.org, The IESG <iesg@ietf.org>
References: <156339110885.25873.1576291155471550816.idtracker@ietfa.amsl.com> <c2469336-c6ca-37e1-2a5a-12a9e3a3fec4@bluepopcorn.net> <20190731000222.GV47715@kduck.mit.edu> <58bed186-4130-7023-b124-37749e4512ef@bluepopcorn.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <58bed186-4130-7023-b124-37749e4512ef@bluepopcorn.net>
User-Agent: Mutt/1.11.4 (2019-03-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/uta/lcvPRwUVCdUr_OL5x8PK6GiGsvc>
Subject: Re: [Uta] Benjamin Kaduk's Discuss on draft-ietf-uta-smtp-require-tls-08: (with DISCUSS and COMMENT)
X-BeenThere: uta@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: UTA working group mailing list <uta.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uta>, <mailto:uta-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uta/>
List-Post: <mailto:uta@ietf.org>
List-Help: <mailto:uta-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uta>, <mailto:uta-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Jul 2019 09:08:46 -0000

On Tue, Jul 30, 2019 at 11:16:25PM -0700, Jim Fenton wrote:

> The RFC 7672 definition of Reference Identifier includes the CN-ID, so it
> would be more consistent to include it when referencing 6125 as well.

For the record, RFC7672 has aged a bit since ~2014 when most of it
was written, so at some point support for CN-ID could be reconsidered.

In that light, I took a look at the certificates currently live on
MX hosts found by the DANE survey, and of 854 certificates on MX
hosts that use DANE-TA records (for which name checks are in scope)
22 have CN-ID and no SAN.  That may be too high a rate to pull the
plug just yet. :-(

One notable example is the state of Bavaria:

  bayern.de. IN MX 10 mail.bayern.de. ; NoError AD=1
  _25._tcp.mail.bayern.de. IN TLSA 2 0 1 32a2bc1d515cdbc412b62b47a1cccf2bb1b8e3ef309f982458d3a7c61797422a ; NoError AD=1
      cert sha256 [matched] <- 2 0 1 32a2bc1d515cdbc412b62b47a1cccf2bb1b8e3ef309f982458d3a7c61797422a
      cert sha256 [matched] <- 2 0 1 32a2bc1d515cdbc412b62b47a1cccf2bb1b8e3ef309f982458d3a7c61797422a

which sports a V1 cert (no extensions, hence no SANs).  The issuer
looks like a private CA:

  C = DE
  ST = Bayern
  O = Freistaat Bayern
  CN = Bayerische DANE-CA

-- 
	Viktor.