Re: [Acme] The path to the "directory" resource should not be "/" and should be specified in draft-ietf-acme-acme-01

Albert ARIBAUD <albert.aribaud@gmail.com> Fri, 08 January 2016 21:47 UTC

Return-Path: <albert.aribaud@gmail.com>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4D701B2C02 for <acme@ietfa.amsl.com>; Fri, 8 Jan 2016 13:47:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 egKyVMOQQWhL for <acme@ietfa.amsl.com>; Fri, 8 Jan 2016 13:46:59 -0800 (PST)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19F401A00F6 for <acme@ietf.org>; Fri, 8 Jan 2016 13:46:59 -0800 (PST)
Received: by mail-wm0-x22c.google.com with SMTP id b14so190619017wmb.1 for <acme@ietf.org>; Fri, 08 Jan 2016 13:46:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; bh=/F0UlXKhRK0yO3wg7DlTRUAX8aMIftcdkEt+Bau1xv0=; b=CwB1wtk29kl9y8A2KEfjJnMNM8dHrV8sZyWPoQtWdZRBKic4E3Na+0RydecUnk3cA6 xPTfCYAs+oJ6wPHa9bR/fOtzgzvbgVvZbMaUkbI4beN6rLwqzllm83KRH5lwJcFeAV1J DEzeVfOXMmM7A0P6Zce+Tr0+EhnH2Ka/NyrH0eZBx0TKGMGpnr70jnQPR34AKqOvOKz1 konLTSX2D7BOZqdTA+looO2maULcXriCEfqEoemZwbtQuO3nsGubcSE9Br5geQlYoipB GH8T6Mp5IFtdEq54gDkrFPHt9kxZKUXHyrdTidNr2EJT6PZ2lWlQhMXUpnj6NMT1Y9W0 ADGA==
X-Received: by 10.194.184.210 with SMTP id ew18mr106246770wjc.79.1452289617731; Fri, 08 Jan 2016 13:46:57 -0800 (PST)
Received: from lilith ([2001:470:1f13:25f:ae22:bff:fe1a:1040]) by smtp.gmail.com with ESMTPSA id w1sm996821wmd.2.2016.01.08.13.46.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 08 Jan 2016 13:46:57 -0800 (PST)
Date: Fri, 8 Jan 2016 22:46:55 +0100
From: Albert ARIBAUD <albert.aribaud@gmail.com>
To: "Salz, Rich" <rsalz@akamai.com>
Message-ID: <20160108224655.3e86921f@lilith>
In-Reply-To: <20160108213330.68bb52a8@lilith>
References: <20160108204956.4930f429@lilith> <513bd0198dd74fa4ab7fabdee8be242d@usma1ex-dag1mb1.msg.corp.akamai.com> <20160108213330.68bb52a8@lilith>
X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/QgxRrhfivVggjqsJrQtSMSQiggc>
Cc: "acme@ietf.org" <acme@ietf.org>
Subject: Re: [Acme] The path to the "directory" resource should not be "/" and should be specified in draft-ietf-acme-acme-01
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 08 Jan 2016 21:47:01 -0000

Hi again,

Le Fri, 8 Jan 2016 21:33:30 +0100
Albert ARIBAUD <albert.aribaud@gmail.com> a écrit:

> Hi Rich,
> 
> Le Fri, 8 Jan 2016 19:52:34 +0000
> "Salz, Rich" <rsalz@akamai.com> a écrit:
> 
> > 
> > > draft-ietf-acme-acme-01 states:
> > > 
> > > 	In order to help clients configure themselves with the
> > > right URIs for each ACME operation, ACME servers provide a
> > > directory object. This should be the root URL with which clients
> > > are configured.
> > > 
> > > The question is, what exactly is the "root URL"? At first thought
> > > it would be the "/" path on the server.
> > 
> > The wording misled you, and perhaps should be fixed.  It's more like
> > the "subroot for the ACME tree" or something.
> 
> Can I offer a pull request on github with a fix?

Done : https://github.com/ietf-wg-acme/acme/pull/66

> (note: acme-v01.api.letsencrypt.org would still not match the draft)

Actually, I withdraw this statement: acme-v01.api.letsencrypt.org's
"/directory" is just as compliant as "/acme" or "/". There is no
reason to constrain the path of the directory object to a specific
value.

In fact, not constraining the directory path allows running several
ACME servers on a single HTTP host (if anyone finds a need for that),
as long as each server has a unique directory URL (and unique
resource URIs, to avoid collisions with other ACME servers).

Amicalement,
-- 
Albert.