IETF Logo Mail Archive

Re: [lamps] Next steps on CAA

Jacob Hoffman-Andrews <jsha@eff.org> Fri, 06 October 2017 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 9B01D133090 for <spasm@ietfa.amsl.com>; Fri, 6 Oct 2017 15:20:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.001
X-Spam-Level:
X-Spam-Status: No, score=-7.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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 pEPJyCl-BmA8 for <spasm@ietfa.amsl.com>; Fri, 6 Oct 2017 15:20:21 -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 049B5133064 for <spasm@ietf.org>; Fri, 6 Oct 2017 15:20:21 -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:In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To:Subject; bh=SAgeeBpNFI8jRriAt36Rtnx0Qb0hFvwzla/tSHVAgxs=; b=ikKCPqCAwxV5MPBIoAoDHSy0RLK+tc8FeF8avexrH1l8TZoHS7MjU592az6Q26Q8YPMFTYNOX7X9/4B0qkCrDdUtnMWuDE/n0BSxWSNiPWMCGAXfs78Rr1YqBScQanW3hN1AdKto6QOyisdsEyp6bT3hPQtxpQsKWj/jZmc35U0=;
Received: ; Fri, 06 Oct 2017 15:20:18 -0700
To: John R Levine <johnl@taugh.com>
Cc: SPASM <spasm@ietf.org>
References: <CACh0qC+jRjPMsf7YmDqoKZ0X1zWE2p=fUAo5uN3bZwwzBRG9Kg@mail.gmail.com> <alpine.OSX.2.21.1710061656080.33175@ary.qy> <7b98f765-4fea-5b71-e860-e46c11d6617e@eff.org> <alpine.OSX.2.21.1710061748500.33785@ary.qy>
From: Jacob Hoffman-Andrews <jsha@eff.org>
Message-ID: <61e71386-fb35-0c00-e473-03f2a100c32c@eff.org>
Date: Fri, 06 Oct 2017 15:20:20 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <alpine.OSX.2.21.1710061748500.33785@ary.qy>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Received-SPF: skipped for local relay
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/nLCVO496grAKRvEuFbvHg921uKM>
Subject: Re: [lamps] Next steps on CAA
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: Fri, 06 Oct 2017 22:20:23 -0000

On 10/06/2017 03:14 PM, John R Levine wrote:
> If you'll review the messages you're responding to, you'll see that
> the problem is that we want a CNAME'd web server and a non-CNAME'd
> CAA.  There are some cases where tree climbing might fix that, but a
> lot where it won't, e.g.:
>
> mydom.example.  CAA issue "nope"   ; no web server here
> www.mydom.example. CNAME somehost.example. ; web server here
>
> Where does the CAA go?
Three options:

 - Remove the record on mydom.example
 - Adjust the record for mydom.example to allow issuance by preferred CAs
 - Ask the maintainer of somehost.example to install an appropriate CAA
record

v2.23.0 | Report a Bug | By Email