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

Martin Thomson <martin.thomson@gmail.com> Fri, 08 January 2016 22:58 UTC

Return-Path: <martin.thomson@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 41AC31B2C7D for <acme@ietfa.amsl.com>; Fri, 8 Jan 2016 14:58:39 -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 EKMLL9iwezAP for <acme@ietfa.amsl.com>; Fri, 8 Jan 2016 14:58:38 -0800 (PST)
Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (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 CDCC61B2C80 for <acme@ietf.org>; Fri, 8 Jan 2016 14:58:37 -0800 (PST)
Received: by mail-ig0-x22a.google.com with SMTP id z14so85550819igp.0 for <acme@ietf.org>; Fri, 08 Jan 2016 14:58:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QarNf4OM1M1EGqEgS4yqL44CXdkbor8oUpVk08KyD2E=; b=tomymJASk9jt0IrlqPMX2WJqARgrv0VeXOslo6AJKpFoJnNF7qyJYQW3HsWTD5AVA7 wBXsbVtTEA9Wkhk6dXvC5LexNgFnnRrg0NK3Qarhyao2l9wSUxQt+otlMjcvWa/Gy9p4 MGfO8eL6TMRZBLqnWUtv8u0YQbea/DEV1PSvfV/dq92jZPFUvXJrB3fFdSysTmM+K7Un NnWEB6NefKAxHr/1Kku2yfvSUQlSTudSLprB1AABrx70N36EGKcJamzjU37hxaTPqE6P 9jpUnm/GZLAq6SKO3vIyQPGQ+NEmviM07i7kTLZTL8irkbNiZe3iDLBlgVjGW+I2JB0h TlHA==
MIME-Version: 1.0
X-Received: by 10.50.60.6 with SMTP id d6mr1445554igr.94.1452293917115; Fri, 08 Jan 2016 14:58:37 -0800 (PST)
Received: by 10.36.149.130 with HTTP; Fri, 8 Jan 2016 14:58:37 -0800 (PST)
In-Reply-To: <20160108224655.3e86921f@lilith>
References: <20160108204956.4930f429@lilith> <513bd0198dd74fa4ab7fabdee8be242d@usma1ex-dag1mb1.msg.corp.akamai.com> <20160108213330.68bb52a8@lilith> <20160108224655.3e86921f@lilith>
Date: Sat, 9 Jan 2016 09:58:37 +1100
Message-ID: <CABkgnnXvs4s5xrRLyCNuUHADmPA_ZQDaOeW8nptrbpV-awBw8A@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Albert ARIBAUD <albert.aribaud@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/YULH1df5RDPfeMwaTCa5PdSShhQ>
Cc: "Salz, Rich" <rsalz@akamai.com>, "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 22:58:39 -0000

On 9 January 2016 at 08:46, Albert ARIBAUD <albert.aribaud@gmail.com> wrote:
> 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).


That's right.  This string
"https://acme-v01.api.letsencrypt.org/directory" is what you need to
know to use the LE service.  That part isn't subject to
standardization.