Re: Request for well-known URI: ets

Mark Nottingham <mnot@mnot.net> Fri, 10 May 2019 06:50 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: wellknown-uri-review@ietfa.amsl.com
Delivered-To: wellknown-uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA089120178 for <wellknown-uri-review@ietfa.amsl.com>; Thu, 9 May 2019 23:50:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, 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=mnot.net header.b=VBjhNayl; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=iSLZEx7T
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 qarHhdbDL1GX for <wellknown-uri-review@ietfa.amsl.com>; Thu, 9 May 2019 23:50:35 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5495B120169 for <wellknown-uri-review@ietf.org>; Thu, 9 May 2019 23:50:35 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 25E1022572; Fri, 10 May 2019 02:50:34 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Fri, 10 May 2019 02:50:34 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=E v0I1P4zVvQfyu6JBjzCOK62tP5NUmuduOE2Llf5LQU=; b=VBjhNaylwYat4m6nX Kc6fJq4LvME0TPH349AZ8v3d82Np8lrmCJw3eZHTJrr29PqSHuXAHvyhuE5UR6K3 xEbQkyH4WECU0cfUKIYt2KrJRm9P0FkkFIV4g26y2saANXJCl09vTKPg4SUAFwRB H/P+cEcyC9XbzLClYOv/DZZ6jxgi2v5xOLtz/CAdL86rBink3YAtZTtVrNajmraf rQq6e+8gjSoX/KCNoXOZojEXLkrVxSaFXbiQwcBYh35z8qVU2/HoG6kMtdSSF37u 4yEqsXpYn+oCetHaHMfouJjqjiYVFHaKJFH0ubT1gG+By5s/P7UEHCVmy0HzKmUk MBr7Q==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=Ev0I1P4zVvQfyu6JBjzCOK62tP5NUmuduOE2Llf5L QU=; b=iSLZEx7TJuvgM/Pq/VSe9jyeIUYc2mHJ6ac+Z6o6Xa5t1KZcVpMbBfpdK IAQW8eVHJMgou1WWxUBbPecj067qkHqoSTaQqKNksGs7UnV+TQVBWw9BxRVODzZi b3QrpDpNXE2zkgfDdGsXX+RfammVl2rx7ZPC7UvCj9h28bd7hiWVEr7af4JlxVkq qCz4dkSiC7CczEjf22HrfE4jD+jz+5P0gyVg7wghR0YYY0FMa4GNOqQis9fn6ZqY VG3ZN3Z02FI11QGJqWEC9A/ejspBBrTd7TywvVRPVX+7yJHPrU6R2JYPF2LHdPN7 pSAD2wZ0NEKPxcn37XLTc4C0Its3w==
X-ME-Sender: <xms:OB_VXH58bBsyNXLJGhR9HYu4Q_K2pYrA_705QtCTEYSWU9D5a22QjA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrkeejgdefiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpeforghrkhcu pfhothhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuffhomhgrihhnpe gvthhsihdrohhrghdpmhhnohhtrdhnvghtpdgvgigrmhhplhgvrdgtohhmnecukfhppedu geegrddufeeirddujeehrddvkeenucfrrghrrghmpehmrghilhhfrhhomhepmhhnohhtse hmnhhothdrnhgvthenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:OB_VXBIrV85NMqrNGCsqCCrBVwfc9o-SARKXuuUjt-8TeerGAlfq1A> <xmx:OB_VXJdvEj7ISDqyXovBq5fVMHS19L_py29vQtwgVfkXde4NTHxa8w> <xmx:OB_VXMc2Tt41qGiAR6sbFndxFvPUgPO_a74GFYiRQd7bqMJ0y_fgfg> <xmx:Oh_VXFLoiruoyzCk_LJ8f5WMCEXQEEXWNaekUko8BK_QKSyqbyVrrQ>
Received: from macbook-pro.mnot.net (unknown [144.136.175.28]) by mail.messagingengine.com (Postfix) with ESMTPA id 80F1F8005A; Fri, 10 May 2019 02:50:31 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Subject: Re: Request for well-known URI: ets
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <0df132aee40041318adaa85048936dd9@xMail.etsihq.org>
Date: Fri, 10 May 2019 16:50:28 +1000
Cc: "wellknown-uri-review@ietf.org" <wellknown-uri-review@ietf.org>, iana@iana.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <DED41FF6-88EC-4306-8265-9A1AA10722E4@mnot.net>
References: <ecb7980ee9da48ed92c71d6546bed0b5@xMail.etsihq.org> <2ED04D76-AF0D-42C1-9D84-31544ABE614A@mnot.net> <0df132aee40041318adaa85048936dd9@xMail.etsihq.org>
To: ETSI CyberSupport <CyberSupport@etsi.org>
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wellknown-uri-review/SFLIf4fRjL2SWpQE7lCokM4OUPc>
X-BeenThere: wellknown-uri-review@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Well-Known URI review list <wellknown-uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wellknown-uri-review>, <mailto:wellknown-uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wellknown-uri-review/>
List-Post: <mailto:wellknown-uri-review@ietf.org>
List-Help: <mailto:wellknown-uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wellknown-uri-review>, <mailto:wellknown-uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 May 2019 06:50:39 -0000

That's great, thank you. 

IANA, please register the template below in the well-known URI registry, but with the URI suffix "enterprise-transport-security".

Cheers,


> On 10 May 2019, at 4:47 pm, ETSI CyberSupport <CyberSupport@etsi.org>; wrote:
> 
> Dear Mark,
> 
> Finally getting back to you. The group considered your feedback and proposes to expand ets.
> So the URI suffix is proposed to be: enterprise-transport-security
> 
> Does it work?
> 
> Thank you
> Best regards,
> Sonia
> 
> -----Original Message-----
> From: Mark Nottingham <mnot@mnot.net>; 
> Sent: 08 April 2019 2:49 AM
> To: ETSI CyberSupport <CyberSupport@etsi.org>;
> Cc: wellknown-uri-review@ietf.org
> Subject: Re: Request for well-known URI: ets
> 
> Hello,
> 
> Thank you for the request. The only issue I see is that the name 'ets' is quite short, for such a specific purpose; as per RFC5785bis:
> 
>> Registered names for a specific application SHOULD be correspondingly precise; “squatting” on generic terms is not encouraged. For example, if the Example application wants a well-known location for metadata, an appropriate registered name might be “example-metadata” or even “example.com-metadata”, not “metadata”.
> 
> As such a name like "etsi-ets" would be more appropriate. Would changing it cause issues (i.e., is this protocol already seeing wide deployment)?
> 
> Regards,
> 
> 
> 
>> On 3 Apr 2019, at 9:18 pm, ETSI CyberSupport <CyberSupport@etsi.org>; wrote:
>> 
>> Dear wellknown-uri-review group,
>> 
>> Please find below a request to register a Well-Known URI:
>> 
>> URI suffix: ets
>> 
>> Change controller:  ETSI (TC CYBER) cybersupport@etsi.org
>> 
>> Specification document(s): ETSI TS 103 523-3 clause 4.3.8.3 available at  https://www.etsi.org/deliver/etsi_ts/103500_103599/10352303/01.02.01_60/ts_10352303v010201p.pdf
>> 
>> Best regards
>> ETSI TC CYBER support.
>> 
> 
> --
> Mark Nottingham   https://www.mnot.net/
> 

--
Mark Nottingham   https://www.mnot.net/