IETF Logo Mail Archive

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

Rob Stradling <rob@sectigo.com> Mon, 24 June 2019 14:15 UTC

Return-Path: <rob@sectigo.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 E9BDF120151 for <trans@ietfa.amsl.com>; Mon, 24 Jun 2019 07:15:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=comodoca.onmicrosoft.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 Vf5XVaoYaWEy for <trans@ietfa.amsl.com>; Mon, 24 Jun 2019 07:15:49 -0700 (PDT)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-eopbgr760043.outbound.protection.outlook.com [40.107.76.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F77A12012B for <trans@ietf.org>; Mon, 24 Jun 2019 07:15:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comodoca.onmicrosoft.com; s=selector1-comodoca-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=4+2B7AmNbTF5mA/pcmMeLnzbr3MySaf3I0oyfTBAXc8=; b=hUTaPVTffPmL4wNCO7REnvXSHoGxrUmMVmOHQSyGm/Bk+kKs5ZmO9IqP1Kl5FQSej+AktlgiDVv9KOU+GSkO/KLfZ7+ordX9dtYZvs71MqMWCGQROKpcjgRdziLV9HwwdK4AgLvXELVewKOLtVoal1xbogoeQHvwb+CkpC7mahk=
Received: from DM5PR17MB1211.namprd17.prod.outlook.com (10.173.132.148) by DM5PR17MB1068.namprd17.prod.outlook.com (10.168.118.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2008.16; Mon, 24 Jun 2019 14:15:47 +0000
Received: from DM5PR17MB1211.namprd17.prod.outlook.com ([fe80::b556:345c:94cf:7258]) by DM5PR17MB1211.namprd17.prod.outlook.com ([fe80::b556:345c:94cf:7258%6]) with mapi id 15.20.2008.017; Mon, 24 Jun 2019 14:15:47 +0000
From: Rob Stradling <rob@sectigo.com>
To: Melinda Shore <melinda.shore@gmail.com>, "trans@ietf.org" <trans@ietf.org>
Thread-Topic: [Trans] Directory instead of .well-known for URL structure
Thread-Index: AQHVJ7g3xV77fgqjj0ive+Voenofmqap50UAgAAKWICAAO2MAA==
Date: Mon, 24 Jun 2019 14:15:47 +0000
Message-ID: <f03a2bc2-9058-bafd-37a1-50a1fd5d02d2@sectigo.com>
References: <0d5e05fc-8f1e-54b5-536d-231153e7baf7@eff.org> <48a31dcd-71d9-42c8-9ec3-6104939a59ab@www.fastmail.com> <7161898d-a58d-1625-a041-2e93961e71a2@gmail.com>
In-Reply-To: <7161898d-a58d-1625-a041-2e93961e71a2@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: DB6PR0202CA0020.eurprd02.prod.outlook.com (2603:10a6:4:29::30) To DM5PR17MB1211.namprd17.prod.outlook.com (2603:10b6:3:8b::20)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rob@sectigo.com;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [82.109.38.206]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 955a9ae9-2d1f-4bab-1b95-08d6f8ae73c5
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:DM5PR17MB1068;
x-ms-traffictypediagnostic: DM5PR17MB1068:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <DM5PR17MB1068D5DB57587815E7F6D840AAE00@DM5PR17MB1068.namprd17.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 007814487B
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(39850400004)(366004)(136003)(346002)(376002)(199004)(189003)(66066001)(36756003)(26005)(8936002)(81166006)(81156014)(102836004)(71200400001)(71190400001)(2501003)(8676002)(186003)(386003)(6506007)(478600001)(2906002)(66446008)(64756008)(66556008)(66946007)(31686004)(53546011)(305945005)(7736002)(73956011)(14454004)(6246003)(31696002)(66476007)(99286004)(6116002)(76176011)(561944003)(6512007)(3846002)(52116002)(25786009)(86362001)(256004)(14444005)(316002)(68736007)(5660300002)(486006)(110136005)(476003)(6436002)(6486002)(2616005)(229853002)(53936002)(6306002)(446003)(966005)(11346002)(142923001); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR17MB1068; H:DM5PR17MB1211.namprd17.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: sectigo.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: b9pD/Oop0x2VX4chmkcbz0XNcZpBw5saXbNBNYy9WGeS55gb38AzyD2GVxlETjBA88m0tz4qJ/xDr6NViKZsLr+uN36LOcXI3U3v+/ixQccQCVZuJVwp0HtS11WudUgqfXFTLFoa1u8NZHrrqC/RvbTDtS2Lg9ipUMcUuChRjgPqDYu105CQcP/wHbFJ4phy65oeVFegvFOL9bQSmPIhF1ccMJ6jozIzC9nRQUuoKQBkRDvtrVDq0/vJFIpIiiRYoxvEFxaifmkEfwIm0izGuB5yEPrOkiRPi9QhLv3lxRmByuWuLRHN9B4UnHh0GHbszZhTPOl3NnQqHpIfm9xm+EDMVs1z681ClMsm/b0vJandU3gYPR1r7rvhDyoNk+ZG1wJ5Lk6hAvsu4pFWdmXmf45TLodxM3kwSh8S0gjMcac=
Content-Type: text/plain; charset="utf-8"
Content-ID: <DDE4AD607B607249B584108E3FC886CB@namprd17.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: sectigo.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 955a9ae9-2d1f-4bab-1b95-08d6f8ae73c5
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Jun 2019 14:15:47.2971 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0e9c4894-6caa-465d-9660-4b6968b49fb7
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: robs@comodoca.net
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR17MB1068
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/ojsx1zJVrqKbhYqD8zsTrRoegmE>
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 14:15:52 -0000

This sounds unanimous.  :-)

I'll go ahead and make this change, and I'll cancel the registration 
process for "ct" as a .well-known URI suffix.

On 24/06/2019 01:05, Melinda Shore wrote:
> 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
> 

-- 
Rob Stradling
Senior Research & Development Scientist
Email: rob@sectigo.com
Bradford, UK
Office: +441274024707
Sectigo Limited

This message and any files associated with it may contain legally 
privileged, confidential, or proprietary information. If you are not the 
intended recipient, you are not permitted to use, copy, or forward it, 
in whole or in part without the express consent of the sender. Please 
notify the sender by reply email, disregard the foregoing messages, and 
delete it immediately.

v2.23.0 | Report a Bug | By Email