Re: [lamps] CAA records on CNAMEs

Jan Schaumann <jschauma@netmeister.org> Mon, 18 March 2019 17:49 UTC

Return-Path: <jschauma@netmeister.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 C6C9713121A for <spasm@ietfa.amsl.com>; Mon, 18 Mar 2019 10:49:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 z3mwZBwXDqQX for <spasm@ietfa.amsl.com>; Mon, 18 Mar 2019 10:49:45 -0700 (PDT)
Received: from panix.netmeister.org (panix.netmeister.org [IPv6:2001:470:30:84:e276:63ff:fe72:3900]) by ietfa.amsl.com (Postfix) with ESMTP id 30CBD131158 for <spasm@ietf.org>; Mon, 18 Mar 2019 10:49:45 -0700 (PDT)
Received: by panix.netmeister.org (Postfix, from userid 1000) id A655565341; Mon, 18 Mar 2019 13:49:44 -0400 (EDT)
Date: Mon, 18 Mar 2019 13:49:44 -0400
From: Jan Schaumann <jschauma@netmeister.org>
To: spasm@ietf.org
Message-ID: <20190318174944.GE22311@netmeister.org>
Mail-Followup-To: spasm@ietf.org
References: <20190316223225.GC11586@netmeister.org> <20190317180256.GA4279@LK-Perkele-VII> <20190318160211.GC22311@netmeister.org> <BN6PR14MB1106E81499036021704CA32683470@BN6PR14MB1106.namprd14.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <BN6PR14MB1106E81499036021704CA32683470@BN6PR14MB1106.namprd14.prod.outlook.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/TqgqA4-CivuTLYeDmrX5W9LwsEE>
Subject: Re: [lamps] CAA records on CNAMEs
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 18 Mar 2019 17:49:56 -0000

Tim Hollebeek <tim.hollebeek@digicert.com> wrote:
 
> As such, I think the proposal is strictly inferior to much simpler solutions
> e.g. the ones involving prefix tags.

Agreed.

> The prefix tag issue resurfaces every six to twelve months or so

I'd be interested to hear arguments previously used against a prefix
tag to ensure they are addressed or at least considered should we
propose to pursue this.

-Jan