IETF Logo Mail Archive

Re: [Trans] Directory instead of .well-known for URL structure

Melinda Shore <melinda.shore@gmail.com> Mon, 24 June 2019 00:05 UTC

Return-Path: <melinda.shore@gmail.com>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E4941200F1 for <trans@ietfa.amsl.com>; Sun, 23 Jun 2019 17:05:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 LejhIr85xcp2 for <trans@ietfa.amsl.com>; Sun, 23 Jun 2019 17:05:31 -0700 (PDT)
Received: from mail-pf1-x434.google.com (mail-pf1-x434.google.com [IPv6:2607:f8b0:4864:20::434]) (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 22ECD120047 for <trans@ietf.org>; Sun, 23 Jun 2019 17:05:30 -0700 (PDT)
Received: by mail-pf1-x434.google.com with SMTP id 19so6444613pfa.4 for <trans@ietf.org>; Sun, 23 Jun 2019 17:05:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=3nbs6eHtrqbhuXiSWbA45ly36+83xIS2NLvlHXTD0nA=; b=BLM5aml552Z+xNgvmirN75KWL64c7SmDBkzgvFPl6VJ4CvCkuyf7TP4bVZM93Yvurd 3SjaxwuI86N4yCxxUxMZHzHbfaMi7ntETKsCByTSncTXlX49nWL1IAcSoM1SxGZCcy7B u/yVRLwmPMrH9Cy6VR5m+r7AjQyC95cD1BAoGKquJFiZgUXsFrkGW6DtqsBSin0YKq7c 9pkUILZVqglTAYSkHYALo8O8AJh0W7wdM/GLnfpMnyzg0ub/P2hs0mRfmDMJummG7Has N5i2wENAQDvATQttEnG5LODLcHsWC3NRT5nNRgErZmT1V4MX+ZQMoLg18167dqrsO7zy i75w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=3nbs6eHtrqbhuXiSWbA45ly36+83xIS2NLvlHXTD0nA=; b=Jyw5+E980/sty72nSRqanJ3Mg5qdEMJdtzV/cqXuhuVqZdhp07G4dX0mQjXcNv1QCm DnV8rtJpeVpIKltqZyXHPWYz23fGWEDWfrsYY3jfLtSzvzSbvYeGD8auwT4p7ODnmJ94 5SIP22U4wVdu5QQD1I1CZbpoHg/pLj7kWD8ZABTqwpa2KV8FzPTjY0yYWfrHYYkQySjq s0xuNNOTXhJa6aicXGuK1EmDARHL0D8fm+dGi6OeJR8RhSiScOorfkADVdbFGFKYEhl9 NCg8uT6xaDFG+6UnIeamQGA4i1o3wDLBhIMseCi8Ut+DR+r1AedXbO2wlWozhxMIDDwT sSew==
X-Gm-Message-State: APjAAAWbY2wQ7Mn4lltkiFaCGcB+Mv8eN27KsxJ92vox9yfp/QPaM6Sg fhtyaap0hsJA9wUMFETkWB0GEMRf
X-Google-Smtp-Source: APXvYqzX+Gq0Tyz2WB9tw//Jr0//AG5PX09dGClndoUPpGfxnA3/tIdvCTPyU7zW5cREsD4a1q6jMQ==
X-Received: by 2002:a17:90a:2488:: with SMTP id i8mr20870816pje.123.1561334729719; Sun, 23 Jun 2019 17:05:29 -0700 (PDT)
Received: from aspen.local ([63.140.70.85]) by smtp.gmail.com with ESMTPSA id o2sm7607368pgp.74.2019.06.23.17.05.28 for <trans@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 23 Jun 2019 17:05:29 -0700 (PDT)
To: trans@ietf.org
References: <0d5e05fc-8f1e-54b5-536d-231153e7baf7@eff.org> <48a31dcd-71d9-42c8-9ec3-6104939a59ab@www.fastmail.com>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <7161898d-a58d-1625-a041-2e93961e71a2@gmail.com>
Date: Sun, 23 Jun 2019 16:05:27 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <48a31dcd-71d9-42c8-9ec3-6104939a59ab@www.fastmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/ArPK2JAYxxvyRNeA9Zb5jcLrza0>
Subject: Re: [Trans] Directory instead of .well-known for URL structure
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Public Notary Transparency working group discussion list <trans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trans>, <mailto:trans-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trans/>
List-Post: <mailto:trans@ietf.org>
List-Help: <mailto:trans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trans>, <mailto:trans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jun 2019 00:05:33 -0000

On 6/23/19 3:28 PM, Martin Thomson wrote:
> I agree with Jacob here. As I have expressed in the past, I believe
> that this is a better design than the well-known prefix.

> On Fri, Jun 21, 2019, at 08:33, Jacob Hoffman-Andrews wrote:
>> The latest draft adopts a /.well-known/ path for CT as a way to get
>>  around BCP 190 (URI Design and Ownership: 
>> https://tools.ietf.org/html/bcp190#section-3).
>> 
>> Personally I think BCP 190 makes it needlessly painful to specify 
>> HTTP-based APIs using techniques that are very common among 
>> practitioners. However, given that it is still considered best
>> practice for IETF documents, I propose that CT should use a
>> different workaround, one used very successfully by ACME: Directory
>> URLs.

I have a fairly profound dislike for BCP 190, to be honest,
and am in agreement with the proposal.

Melinda

-- 
Melinda Shore
melinda.shore@gmail.com

Software longa, hardware brevis

v2.23.0 | Report a Bug | By Email