Re: [Acme] Discussion of draft-ietf-acme-ip

Jacob Hoffman-Andrews <jsha@eff.org> Wed, 20 December 2017 21:27 UTC

Return-Path: <jsha@eff.org>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 707D9124239 for <acme@ietfa.amsl.com>; Wed, 20 Dec 2017 13:27:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.011
X-Spam-Level:
X-Spam-Status: No, score=-7.011 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, T_RP_MATCHES_RCVD=-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 ilGxDGjCLjfi for <acme@ietfa.amsl.com>; Wed, 20 Dec 2017 13:27:55 -0800 (PST)
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 43B0F1200C5 for <acme@ietf.org>; Wed, 20 Dec 2017 13:27:55 -0800 (PST)
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:To:Subject; bh=V9mYtH/pmEMoHyYNgyoNkCSp1jTXamEfIxmLnwzGM8w=; b=sFc1UT/8PX2WzcJ8U+DyLwZ5wU/PihTqTXNfW+eV/+jy8eEkB6Oqsh5oaL1k1wOyJiLsyePutGE08HfexD90CBjt7O5IzD9dbRYplBio23JR/LdMTfFYpTcInAGkbCQefD/tH/WQBH4lGU4Ogg6SFwwkYF7Or2Pj/kPnmYOvFI4=;
Received: ; Wed, 20 Dec 2017 13:27:49 -0800
To: acme@ietf.org
References: <ff57fed6-c989-57ec-e7be-2e8eb8240fad@letsencrypt.org>
From: Jacob Hoffman-Andrews <jsha@eff.org>
Message-ID: <676b57df-95c2-4e65-59e2-a3c45a3412c3@eff.org>
Date: Wed, 20 Dec 2017 13:27:53 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <ff57fed6-c989-57ec-e7be-2e8eb8240fad@letsencrypt.org>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/tjfbLtg9jwkBy8i6wn1jgQ7AE7w>
Subject: Re: [Acme] Discussion of draft-ietf-acme-ip
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Dec 2017 21:27:57 -0000

On 11/16/2017 02:28 PM, Roland Bracewell Shoemaker wrote:
> The point of the draft is to provide a method for validating the control
> of IP addresses in the same way that the ACME draft does for DNS names.
> This allows ACME implementing CAs to be on an equal footing with
> existing implementations. The draft does three major things
> 
> * Adds a IP identifier type
> * Provides guidance on using http-01 and tls-sni-02 challenges for IP
> validation
> * Adds a new challenge, reverse-dns-01, which conforms with CABF B/R
> Section 3.2.2.5.
> 
> The only major objection that was previously voiced revolved around the
> lack of a policy mechanism for allowing a IP/network owner to block
> issuance and that there should be some kind of default denial required.
> It is my opinion that this draft is the wrong place for CA policy to be
> dictated and the right place to fix this problem would be in a document
> implementing an lookup mechanism for CAA records for IP addresses (see
> draft-shoemaker-caa-ip).
> 
> Any major thoughts/objections? If there are no significant hurdles I'd
> like to move towards getting this document finalized.

Any further thoughts about draft-shoemaker-caa-ip? I'd love to get it
adopted as a WG document.