Re: [lamps] Ambiguities in RFC 6844 regarding CAA resource record sets with no "issue" property tags
Jacob Hoffman-Andrews <jsha@eff.org> Wed, 30 May 2018 22:20 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 89FFB12D94A for <spasm@ietfa.amsl.com>; Wed, 30 May 2018 15:20:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.01
X-Spam-Level:
X-Spam-Status: No, score=-7.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 YneHwATGIJqn for <spasm@ietfa.amsl.com>; Wed, 30 May 2018 15:20:52 -0700 (PDT)
Received: from mail2.eff.org (mail2.eff.org [173.239.79.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5DDF12EB96 for <spasm@ietf.org>; Wed, 30 May 2018 15:20:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=eff.org; s=mail2; h=Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From: References:To:Subject:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID :Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To: Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe :List-Post:List-Owner:List-Archive; bh=0BBbchuoliRAGYLDRZp5M2GA+m6KLH9nbCV9Rk8XcvI=; b=ecYycOqrWdLZrAHpxgz2Ciz0wF t9HyfE5qVC/XEzMY5arK+pYznlbPy/b/reC966hwHaJVAiG1qyKEQ5VxEfOjLainuQvXtlUwBz9ek iNs4dncJTjpjFGlJoYNlL1HG28PQH3X0Dzmr6qNSgJqgWqpzWLEY3s7aM5tUTcfxuAjA=;
Received: ; Wed, 30 May 2018 15:20:52 -0700
To: Corey Bonnell <CBonnell@trustwave.com>, "spasm@ietf.org" <spasm@ietf.org>
References: <878C91A0-6875-47A4-872F-F5D1F7F7AE7E@trustwave.com> <ed4efa8d-c82f-018e-143c-63388e540763@eff.org> <C051979C-4726-4AF9-9C7A-B63DB7309426@trustwave.com>
From: Jacob Hoffman-Andrews <jsha@eff.org>
Message-ID: <d24ad93e-1b88-d9fb-6980-62c907d89ac0@eff.org>
Date: Wed, 30 May 2018 15:20:51 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <C051979C-4726-4AF9-9C7A-B63DB7309426@trustwave.com>
Content-Type: multipart/alternative; boundary="------------30A0DB75163B0E255ED04EAC"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/YY4WDbZ723jULNKrgAl_29Vmdto>
Subject: Re: [lamps] Ambiguities in RFC 6844 regarding CAA resource record sets with no "issue" property tags
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, 30 May 2018 22:21:02 -0000
On 03/27/2018 07:27 AM, Corey Bonnell wrote: > As for my original erratum text not specifying "issuewild", that is > because section 5.3 (5.3. CAA issuewild Property) specifies that "The > issuewild property has the same syntax and semantics as the issue > property except that issuewild properties only grant authorization to > issue certificates that specify a wildcard domain". Given that > issuewild property tags have the same semantics as issue property > tags, the addition of my original erratum text (in section 5.2, which > defines issue property tag semantics) will also address the case of a > resource record set not containing issue property tags and not > containing issuewild property tags (only in the case of wildcard > domain names, since issuewild property tags are otherwise ignored as > per section 5.3). > > If you think that's too vague and it's better to explicitly mention > the lack of issuewild tags, we should qualify the language a bit to > say "A non-empty CAA record set that contains no issue property tags > (and also does not contain any issuewild property tags when performing > issue restriction processing for a wildcard domain) is authorization > to any certificate issuer to issue for the corresponding domain, > provided that no records in the CAA record set otherwise prohibit > issuance." Otherwise, it is unclear how to handle the case of a > non-empty CAA record set for a non-wildcard domain that does not > contain an issue property tag but contains one or more issuewild > property tags. > I updated my PR to reflect this feedback. I decided to go with "more verbose is better," so now the section that describes what to do when there is no "issue" tag specifically excludes wildcard domains. And I added to the "issuewild" section language that say both "issue" and "issuewild" must be absent to be considered authorization to issue: https://github.com/jsha/caa-simplification/pull/1/commits/65a5665c6cc6db6e90c8b43fed4ae0bf5e8f83ee I'll merge this shortly to produce a new draft, but am happy to keep discussing the fine details. :-)
- [lamps] Ambiguities in RFC 6844 regarding CAA res… Corey Bonnell
- Re: [lamps] Ambiguities in RFC 6844 regarding CAA… Quirin Scheitle
- Re: [lamps] Ambiguities in RFC 6844 regarding CAA… Tim Hollebeek
- Re: [lamps] Ambiguities in RFC 6844 regarding CAA… Ryan Sleevi
- Re: [lamps] Ambiguities in RFC 6844 regarding CAA… Tim Hollebeek
- Re: [lamps] Ambiguities in RFC 6844 regarding CAA… Jacob Hoffman-Andrews
- Re: [lamps] Ambiguities in RFC 6844 regarding CAA… Tim Hollebeek
- Re: [lamps] Ambiguities in RFC 6844 regarding CAA… Corey Bonnell
- Re: [lamps] Ambiguities in RFC 6844 regarding CAA… Jacob Hoffman-Andrews