IETF Logo Mail Archive

Re: [art] On BCP 190

Jacob Hoffman-Andrews <jsha@letsencrypt.org> Wed, 31 July 2019 21:10 UTC

Return-Path: <jsha@letsencrypt.org>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EF5212001A for <art@ietfa.amsl.com>; Wed, 31 Jul 2019 14:10:46 -0700 (PDT)
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, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=letsencrypt.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 sbqqmufxNcFI for <art@ietfa.amsl.com>; Wed, 31 Jul 2019 14:10:44 -0700 (PDT)
Received: from mail-qt1-x832.google.com (mail-qt1-x832.google.com [IPv6:2607:f8b0:4864:20::832]) (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 A3D64120018 for <art@ietf.org>; Wed, 31 Jul 2019 14:10:44 -0700 (PDT)
Received: by mail-qt1-x832.google.com with SMTP id x22so63043588qtp.12 for <art@ietf.org>; Wed, 31 Jul 2019 14:10:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=letsencrypt.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=cFAS8vWtb8s/fm/dy/hbtf9uPIoBMA9QKCmpeqJ0Pp8=; b=AgIBs3RwhrxqER2qy9tYFh46nHMydykRR6wu4vOmE/EX/Mot/BAvbwt+9hFXBGgweB jK+ng3fXMJitT/ESH8/VWliAKQF0oKJxXkUuBh3ntL2d1ThdzwV02vr+uOckvV2j4bls 2mhrccYM+OhVZSWEDh/UUKdl3Ps4zjp+NOhew=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=cFAS8vWtb8s/fm/dy/hbtf9uPIoBMA9QKCmpeqJ0Pp8=; b=rLM0qKrR5bcvBaPn7fN+xvyDVq8KNAgd26frktE6PtkkMjgjAUQfSFS1fWerxMj6vA 66EA362ytY9brc8h0RYAVYmpoQSuo33UnL+w3FTT7vMwGBHJumoPpyEsTpQ+rfiSUZjG lvZkDwO1YRkTqE4ar6SuRLbMa3KQ0WhIb6iw7nd4k3D9+oAw00rH9W747Z00OgCG9bMe umcsyW4deGmrD3cMpMYwHOFSR8QhVrSK6vPhCE2HeYblsKgirDirSIJ9AgzZGnfG0Aj1 kD9culuoJW6pAPUsuKKzoNS8HVMpPnU6Qvv2u+UnwTEKTYhEz43SH48iH3An65R1johL Rovw==
X-Gm-Message-State: APjAAAUQYooKafGTpuGx+U7G4pf0YlL/rD/pvPSRPwNDafWDPZe3GXj6 fsukcnWKf2kYXsUCNKP7W1ONnfxVp+opTKJ7b6je0Q==
X-Google-Smtp-Source: APXvYqw/XzFPicSUTFXChn//pl1FSWTb9iV/KU6AunsBj3t37kNSJFo0u2/lrx9NQ8EUmqbGzKwd//kSXIh3r55RFTY=
X-Received: by 2002:ac8:26d9:: with SMTP id 25mr89077927qtp.377.1564607443798; Wed, 31 Jul 2019 14:10:43 -0700 (PDT)
MIME-Version: 1.0
References: <58BF6171-03BB-4F83-940F-3A101EFDD67F@mnot.net> <CAN3x4Q=Jo1uBvfCG6CSrociYgdG+E4jq+4cB1txPjgboth2q9g@mail.gmail.com> <372FA049-7B33-4981-A0E0-41BD454CB770@mnot.net> <CAN3x4QmJsfx48MdhcBB+XWX+vfv=skSR2Z6kNPBWGVobvzNuFA@mail.gmail.com> <004601d5450d$62b33220$28199660$@acm.org>
In-Reply-To: <004601d5450d$62b33220$28199660$@acm.org>
From: Jacob Hoffman-Andrews <jsha@letsencrypt.org>
Date: Wed, 31 Jul 2019 14:10:17 -0700
Message-ID: <CAN3x4Q=XR+=ugv6HEmOgsA6v64GkQ+4u-Hk+OBQ0Lp9jn-Cy=A@mail.gmail.com>
To: Larry Masinter <LMM@acm.org>
Cc: Mark Nottingham <mnot@mnot.net>, ART Area <art@ietf.org>, Devon O'Brien <devon.obrien@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000e69f61058f008e07"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/ltZn5t13rHKtxgWfn5iMTM0VrlY>
Subject: Re: [art] On BCP 190
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Jul 2019 21:10:46 -0000

On Sat, Jul 27, 2019 at 11:26 PM Larry Masinter <LMM@acm.org> wrote:

> The use of / in the path of URLs was supposed to
>
> be restricted to hierarchical data, and yet CT doesn’t
> do that.
>
> http://masinter.blogspot.com/2019/05/on-nature-of-hierarchical-urls.html
>

CT and all prefix-using APIs do that, with a single level hierarchy. The
domain owner specifies a prefix, ending with a "/". All of the URLs that
are part of the API follow that prefix - they are subordinate in the
hierarchy.

Coming back to the main point: What remains in order to find consensus on
this issue?

Thanks,
Jacob

v2.23.0 | Report a Bug | By Email