[lamps] Call for consensus on CAA DNAME erratum
Jacob Hoffman-Andrews <jsha@eff.org> Wed, 04 October 2017 22:49 UTC
Return-Path: <jsha@eff.org>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 007A313336A for <spasm@ietfa.amsl.com>; Wed, 4 Oct 2017 15:49:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.101
X-Spam-Level:
X-Spam-Status: No, score=-5.101 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eff.org
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 sVtrJah16bhH for <spasm@ietfa.amsl.com>; Wed, 4 Oct 2017 15:49:44 -0700 (PDT)
Received: from mail2.eff.org (mail2.eff.org [173.239.79.204]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3ACF120724 for <spasm@ietf.org>; Wed, 4 Oct 2017 15:49:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=eff.org; s=mail2; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Date:Message-ID:To:Subject:From; bh=kv+c+iTp1Yr2m39ANt90OAlODFQHMiQUxUDlx4weSaE=; b=h0O5dD8Maj0IhQWwhlD8bekjVL58qYDY/55y4v01Jc9pjrZDgEsDWyiqgwxqyEeCUAxlP/NNaY071gmkNhWEXfTSVQ7vvTZbCK5tpcvv5QNJxPuxcYTxwZ954wABj5FiPNq1dLznoiU4r8GJYc6iUKPgNKFpla+DwROu3aEBSb4=;
Received: ; Wed, 04 Oct 2017 15:43:37 -0700
From: Jacob Hoffman-Andrews <jsha@eff.org>
To: Russ Housley <housley@vigilsec.com>, SPASM <spasm@ietf.org>
Message-ID: <b27d7daf-40d7-6439-e5a7-93beb3ed12d3@eff.org>
Date: Wed, 04 Oct 2017 15:43:39 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
Received-SPF: skipped for local relay
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/57jRXhy96uhnrYFcmOyoY6oeEUM>
Subject: [lamps] Call for consensus on CAA DNAME erratum
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Oct 2017 22:49:46 -0000
In August, Andrew Ayer posted a small erratum regarding DNAME: https://www.rfc-editor.org/errata/eid5097. Note that this is entirely independent from erratum 5065. Both errata are fixed in my caa-simplification draft. However, given that it takes significant time for drafts to become RFCs, I think it is useful to come to consensus on erratum 5097 and set it to "held for document update," so that the CA/Browser Forum can clearly see the intent of this standards-setting body is to treat DNAMEs the same way they are treated elsewhere -- as generators of CNAME aliases rather than as aliases themselves. That will remove some uncertainty while we resolve the issue more thoroughly with a new RFC. Russ, as chair, would you mind calling for consensus on this? Thanks, Jacob
- [lamps] Call for consensus on CAA DNAME erratum Jacob Hoffman-Andrews