Re: [urn] [Marketing Mail] Re: New Version Notification for draft-mahesh-etsi-urn-03.txt (Was Re: URN expert review of 'etsi' NID)

Peter Saint-Andre <stpeter@mozilla.com> Tue, 23 October 2018 18:52 UTC

Return-Path: <stpeter@mozilla.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA751130EEC for <urn@ietfa.amsl.com>; Tue, 23 Oct 2018 11:52:22 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mozilla.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 MzABKNtwjdPr for <urn@ietfa.amsl.com>; Tue, 23 Oct 2018 11:52:19 -0700 (PDT)
Received: from mail-it1-x143.google.com (mail-it1-x143.google.com [IPv6:2607:f8b0:4864:20::143]) (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 31302130F17 for <urn@ietf.org>; Tue, 23 Oct 2018 11:52:19 -0700 (PDT)
Received: by mail-it1-x143.google.com with SMTP id 74-v6so3166854itw.1 for <urn@ietf.org>; Tue, 23 Oct 2018 11:52:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla.com; s=google; h=subject:from:to:references:openpgp:autocrypt:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=tCC0bhD5JHkhA/HGA8HKZSzeITsIH6f5yoafNXZisTQ=; b=RX8yM2KmAIHsJcbHYRb3cklkkaIdhtbJbmAepvfA8RwezXIA/3EkJN+/LsupfXFnn+ cnbwyzN4x/E6JnB3JCl9Hj4vLBO0STDk1ZXIOb0qT3Jxdr0m42Wf7kAmWj2ZmI4gpzWs uUdQawwwPE0yyYbyviQ8WoqVCsIxan7kINHDw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:references:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=tCC0bhD5JHkhA/HGA8HKZSzeITsIH6f5yoafNXZisTQ=; b=nuCPaWNaBm75M0qezb5pkW1MfSZXV8qHwplEBHjOchMtZmzvt78p+TRcC75rKqh6d0 I5LE4DrLd+yaGcXfCvKbN7O8O+kFjE47OJFVhTbOUPhsAolX5WZenntAm7/LLd/Pyo+I U/qMnEIiMQ/heFc+2SrNsilwQ7p4dLAThQf8TxJ0D6OnzNkzhpG1wPD1dw17qBjn+TOi B6QEreNCyNbR5sMVORQHbXc7GMiNmQ2ZoLZA1fWknINDE94ESVfxuyS3NzFcmzU8NINo RciWU2jhAoTsEqwmYV69EsMHpw1MmwN+hCg65lW+r6fAM4ActJW/m5mfPiMOiokrO2OW zyJQ==
X-Gm-Message-State: ABuFfogVyNKNKWNJ0n/kyt0V8Oo/yNh8CdKdbabpXuAPQWqnNZByZE3l wcaRcA4jC1KReYKsilOLwWpoASoHdGU=
X-Google-Smtp-Source: ACcGV614j7KxnyUjh7/r1CppRRiTQV1U6ALPiIURqHWLrhz/Duszo8x+AxbZuZ8yJ2YlVvIwvgmL/A==
X-Received: by 2002:a24:670a:: with SMTP id u10-v6mr13374427itc.114.1540320737756; Tue, 23 Oct 2018 11:52:17 -0700 (PDT)
Received: from dragon.local ([76.25.3.152]) by smtp.gmail.com with ESMTPSA id t20-v6sm283824ioa.64.2018.10.23.11.52.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 Oct 2018 11:52:17 -0700 (PDT)
From: Peter Saint-Andre <stpeter@mozilla.com>
To: "Svensson, Lars" <L.Svensson@dnb.de>, "urn@ietf.org" <urn@ietf.org>
References: <87fu1yhwlk.fsf@hobgoblin.ariadne.com> <241B7429-246F-4D13-9402-393315B4727A@gmail.com> <6D608C59-3032-494C-92F8-959FA5D4CA91@gmail.com> <48eaed30-d3a0-fa81-da88-8759d795978a@mozilla.com> <17e4d21c533440a48bd0e1459ab5f48a@dnb.de> <55ac5694-a235-34b4-a49f-9fe9deb350f7@mozilla.com>
Openpgp: preference=signencrypt
Autocrypt: addr=stpeter@mozilla.com; prefer-encrypt=mutual; keydata= xsFNBFonEf4BEADvZ+RGsJoOyZaw2rKedB9pBb2nNXVGgymNS9+FAL/9SsfcrKaGYSiWEz7P Lvc97hWH3LACFAHvnzoktv+4IWHjItvhdi9kUQ3Gcbahe55OcdZuSXXH3w5cHF0rKz9aYRpN jENqXM5dA8x4zIymJraqYvHlFsuuPB8rcRIV9SKsvcy14w9iRqu770NjXfE/aIsyRwwmTPiU FQ0fOSDPA/x2DLjed/GYHem90C5vF4Er9InMqH5KAMLnjIYZ9DbPx5c5EME4zW/d648HOvPB bm+roZs4JTHBhjlrTtzDDpMcxHq1e8YPvSdDLPvgFXDcTD4+ztkdO5rvDkbc61QFcLlidU8H 3KBiOVMA/5Rgl4lcWZzGfJBnwvSrKVPsxzpuCYDg01Y/7TH4AuVkv5Na6jKymJegjxEuJUNw CBzAhxOb0H9dXROkvxnRdYS9f0slcNDBrq/9h9dIBOqLhoIvhu+Bhz6L/NP5VunQWsEleGaO 3gxGh9PP/LMyjweDjPz74+7pbyOW0b5VnIDFcvCTJKP0sBJjRU/uqmQ25ckozuYrml0kqVGp EfxhSKVqCFoAS4Q7ux99yT4re2X1kmlHh3xntzmOaRpcZsS8mJEnVyhJZBMOhqE280m80ZbS CYghd2K0EIuRbexd+lfdjZ+t8ROMMdW5L51CJVigF0anyYTcAwARAQABzSdQZXRlciBTYWlu dC1BbmRyZSA8c3RwZXRlckBtb3ppbGxhLmNvbT7CwZQEEwEIAD4WIQQ1VSPTuPTvyWCdvvRl YYwYf2gUqQUCWicR/gIbIwUJCWYBgAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRBlYYwY f2gUqdaREAChG8qU1853mP0sv2Mersns8TLG1ztgoKHvMXFlMUpNz6Oi6CjjaMNFhP7eUY4T D43+yQs7f4qCkOAPWuuqO8FbNWQ+yUoVkqF8NUrrVkZUlZ1VZBMQHNlaEwwu1CGoHsLoRohP SiZ0hpmGTWB3V6cDDK4KN6nl610WJbzE9LeKY1AxtePdJi2KM281U0Fz8ntij1jWu0gF2xU4 Sez46JDogHLWKgd0srauhcCVzZjAhiWrXp1+ryzSWYaZO8Kh8SnF1f4o6jtYikMqkxUaI5nX wvD3kNX4AMSkCAZfG7Jcfj/SLDojTcREgO87g7B9bcOOsHN4lj3lHoFV0aXpgPmjfIvAjJHu fHkXZAQAH8w0u9bgJqRn703+A4NPfLopnjegyhlNi7fQ3cMQV1H7Oj7WrB/pCcprx+1u/6Uq oTtDwWh1U5uVthVAI0QojpNWR08zABDX19TlGtVoeygaQV3CAEolxTiYQtCfVavUzUplCZ/t 3v4YiRov+NylflJd+1akyOs1IAgARf444BnoH1fotkpfXNOpp9wUXXwsQcFRdP7vpMkSCkc0 sxPNTVX3ei0QImp4NsrFdaep7LV3zEb3wkAp6KE5Qno4hVVEypULbvB0G6twNZbeRfcs2Rjp jnPb2fofvg2WhAKB20dnRfIfK8OKTD/P+JDcauJANjmekM7BTQRaJxH+ARAApPwkbOTChAQu jMvteb/xcwuL5JZElmLxIqvJhqybV7JknM+3ATyN0CTYQFvPTgIrhpk4zSn0A6pEePdK8mKK 5/aHyd7pr7rLEi1sI/X3UE8ld/E83MExksKrYbs0UX1wSQwYXU6g64KicnuP2Abqg+8wrQ18 1nPcZci9jJI75XVPnTdUpZD5aaQWGp7IJ06NTbiOk30I50ORfulgKoe4m3UfsMALFxIx3pJk oy76xC2tjxYGf+4Uq1M0iK3Wy655GrcwXq/5ieODNUcAZzvK5hsUVRodBq0Lq3g1ivQF4ba7 RQayDzlW6XgoeU49xnCr9XdZYnTnj4iaPmr2NtY6AacBwRz+bJsyugeSyGgHsnVGyUSMk8YN wZHvUykMjH21LLzIUX5NFlcumLUXDOECELCJwewui4W81sI5Sq/WDJet+iJwwylUX22TSulG VwDS+j66TLZpk1hEwPanGLwFBSosafqSNBMDVWegKWvZZVyoNHIaaQbrTIoAwuAGvdVncSQz ttC6KkaFlAtlZt3+eUFWlMUOQ9jxQKTWymyliWKrx+S6O1cr4hwVRbg7RQkpfA8E2Loa13oO vRSQy/M2YBRZzRecTKY6nslJo6FWTftpGO7cNcvbmQ6I++5cBG1B1eNy2RFGJUzGh1vlYo51 pdfSg0U1oPHBPCHNvPYCJ7UAEQEAAcLBfAQYAQgAJhYhBDVVI9O49O/JYJ2+9GVhjBh/aBSp BQJaJxH+AhsMBQkJZgGAAAoJEGVhjBh/aBSpAw0P/1tEcEaZUO1uLenNtqysi3mQ6qAHYALR Df3p2z/RBKRVx0DJlzDfDvJ2R/GRwoo+vyCviecuG2RNKmJbf1vSm/QTtbQMUjwut9mx6KCY CyKwniqdhaMBmjCfV2DB2MxxZLYMtDfx/2mY7vzAci7AkjC+RkSUByMEOkyscUydKC/ETdf9 tvI8GhTY/8Q7JSylS3lQA5pMUHiIf+KpSmqKZeBPkGc7nSKM1w1UKUvFAsyyVsiG6A/hWrTr 7tTQAl7YfjtOGE8n4IKGktvrT99bbh9wdWKZ5FdHUN9hx2Q8VP8+0lR1CH2laVFbEwCOv1vM W4cgQDLxwwpo1iOTdHBVtQDxlQ9hPMKVlB1KP9KjchxuiLc24wLmCjP3pDMml4LQxOYB34Eq cgPZ3uHvJZG309sb2wTMTWaXobWNI++ZrsRD5GTmuzF3kkx3krtrq6HI5NSaemxK6MTDTjDN Rj/OwTl0yU35eJXuuryB20GFOSUsxiw00I2hMGQ1Cy9L/+IW6Dvotd8O3LmKh2tFArzXaKLx /rZyGNurS/Go5YjHp8wdJOs7Ka2p1U31js24PMWO6hf6hIiY2WRUsnE6xZNhvBTgKOY6u0KT V6hTevFqEw7OAZDCWUoE2Ob2/oHGZCCMW5SLAMgp7eihF0kGf2S2CmpIFYXGb61hAD8SqSY7 Fn7V
Message-ID: <370bfde8-8318-73de-3a3a-c70709787b8e@mozilla.com>
Date: Tue, 23 Oct 2018 12:52:16 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <55ac5694-a235-34b4-a49f-9fe9deb350f7@mozilla.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/3XJYw1ZQjKoynl3WFAMcu3oXibc>
Subject: Re: [urn] [Marketing Mail] Re: New Version Notification for draft-mahesh-etsi-urn-03.txt (Was Re: URN expert review of 'etsi' NID)
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Revisions to URN RFCs <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/urn/>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2018 18:52:23 -0000

Hi all,

Yesterday Mahesh submitted a revised I-D:

https://tools.ietf.org/html/draft-mahesh-etsi-urn-04

Although I'd prefer to see more detail in the syntax description (which
exists in documentation on the ETSI site), as far as I can see all
issues have been addressed and this can move forward.

Peter

On 8/14/18 1:20 PM, Peter Saint-Andre wrote:
> During discussion with IANA, Lars noticed that the "Security and
> Privacy" section of the template says:
> 
>    If an namespace is URN-equivalent to another namespace used by the
>    device, as per the rules specified in Section 3.1 of URNs [RFC8141],
>    Section 6.1 of URI Generic Syntax [RFC3986], and the lexical rules
>    specified in this document, the request is rejected.
> 
> It would be helpful to clarify what kind of request is involved here
> (presumably a configuration or management request using YANG, but let's
> make that explicit).
> 
> Also, the "Purpose" section says "the URN" in two places, but that
> should be "the URN namespace".
> 
> The "Declaration of syntactic structure" section doesn't seem to reflect
> the structure of the examples (e.g., "urn:etsi:yang:etsi-services"). Do
> you foresee having additional "sub-identifiers" other than "yang"?
> 
> Finally, draft-mahesh-etsi-urn-03 uses the old template from RFC 3406,
> but IANA requires that registrations use the new template from RFC 8141.
> 
> Thanks!
> 
> Peter
> 
> On 6/14/18 9:22 AM, Svensson, Lars wrote:
>> Apart from what Peter already said, I have no further comments on this draft, as far as I'm concerned we're ready to proceed.
>>
>> Best,
>>
>> Lars
>>
>>> -----Original Message-----
>>> From: urn [mailto:urn-bounces@ietf.org] On Behalf Of Peter Saint-Andre
>>> Sent: Thursday, June 14, 2018 2:57 AM
>>> To: urn@ietf.org
>>> Subject: [Marketing Mail] Re: [urn] New Version Notification for draft-mahesh-etsi-
>>> urn-03.txt (Was Re: URN expert review of 'etsi' NID)
>>>
>>> Thanks, Mahesh, that is helpful.
>>>
>>> I'm still not sure if we want to make a normative reference to RFC 1737
>>> (an Informational RFC from 1994) in the Security Considerations section;
>>> do you feel that it discusses issues that we left out of RFC 8141?
>>>
>>> Other than that, the document looks ready to proceed.
>>>
>>> Peter
>>>
>>> On 6/13/18 5:18 PM, Mahesh Jethanandani wrote:
>>>> ETSI has now published a web page that is publicly available and
>>>> describes the two questions outlined below. Please let us know if there
>>>> are any questions.
>>>>
>>>> https://portal.etsi.org/PNNS/GenericAllocation/ETSIURNNamespace.aspx
>>>>
>>>> Thanks.
>>>>
>>>> On Jun 8, 2018, at 8:18 PM, Mahesh Jethanandani <mjethanandani@gmail.com
>>>> <mailto:mjethanandani@gmail.com>> wrote:
>>>>
>>>>> The following update to the draft addresses the comments raised as
>>>>> part of expert review. The remaining action items are for us to make
>>>>> available a public version of the ancillary document, whose URL was
>>>>> provided in the draft, that describes:
>>>>>
>>>>> - the NSS namespace and how it will be allocated by ETSI
>>>>> - how a separate “root” namespace under the allocated URN can be used
>>>>> for experimental namespaces.
>>>>>
>>>>> Thanks
>>>>> ---------------------------------------------------
>>>>>
>>>>> A new version of I-D, draft-mahesh-etsi-urn-03.txt
>>>>> has been successfully submitted by Mahesh Jethanandani and posted to the
>>>>> IETF repository.
>>>>>
>>>>> Name:draft-mahesh-etsi-urn
>>>>> Revision:03
>>>>> Title:URN Namespace for ETSI Documents
>>>>> Document date:2018-06-08
>>>>> Group:Individual Submission
>>>>> Pages:6
>>>>> URL:
>>>>>            https://www.ietf.org/internet-drafts/draft-mahesh-etsi-urn-03.txt
>>>>> Status:         https://datatracker.ietf.org/doc/draft-mahesh-etsi-urn/
>>>>> Htmlized:       https://tools.ietf.org/html/draft-mahesh-etsi-urn-03
>>>>> Htmlized:
>>>>>       https://datatracker.ietf.org/doc/html/draft-mahesh-etsi-urn
>>>>> Diff:           https://www.ietf.org/rfcdiff?url2=draft-mahesh-etsi-urn-03
>>>>>
>>>>> Abstract:
>>>>>   This document describes the Namespace Identifier (NID) 'etsi' for
>>>>>   Uniform Resource Names (URNs) used to identify resources published by
>>>>>   European Telecommunications Standards Institute (http://etsi.org).
>>>>>   ETSI specifies and manages resources that utilize this URN
>>>>>   identification model.  Management activities for these and other
>>>>>   resources types are handled by the manager of the ETSI Protocol
>>>>>   Naming and Numbering Service (PNNS).
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Please note that it may take a couple of minutes from the time of
>>>>> submission
>>>>> until the htmlized version and diff are available at tools.ietf.org
>>>>> <http://tools.ietf.org>.
>>>>>
>>>>> The IETF Secretariat
>>>>>
>>>>>> On Jun 7, 2018, at 6:53 PM, Dale R. Worley <worley@ariadne.com
>>>>>> <mailto:worley@ariadne.com>> wrote:
>>>>>>
>>>>>> Comments on draft-mahesh-etsi-urn-02
>>>>>>
>>>>>>   1.1.  Terminology
>>>>>>
>>>>>>       | PNNS    | Protocol Name and Numbering Service             |
>>>>>>
>>>>>> It would be helpful to state that PNNS is an ETSI function:
>>>>>>
>>>>>>       | PNNS    | ETSI Protocol Name and Numbering Service        |
>>>>>>
>>>>>>   Declaration of syntactic structure:
>>>>>>
>>>>>>      The syntax of namespace specific strings for the 'etsi' namespace
>>>>>>      is <NSS> in Uniform Resource Names (URNs) [RFC8141].
>>>>>>
>>>>>> This is completely legitimate, but it is not satisfying.  If ETSI has
>>>>>> plans for how it will organize the space of NSSs, it would be nice to
>>>>>> describe them here.
>>>>>>
>>>>>>   Relevant ancillary documentation:
>>>>>>
>>>>>>      ETSI publishes information regarding the registered resources in
>>>>>>      the ETSI URN Namespace (EUN) registry
>>>>>>      (https://portal.etsi.org/PNNS/GenericAllocation/
>>>>>>      ETSIURNNamespace.aspx).
>>>>>>
>>>>>> It's good that ETSI gives the URL of its URN registry; many other
>>>>>> organizations do not.  However, I notice that that URL is
>>>>>> password-protected.  It would be much better for the community if the
>>>>>> registry was readable by the world, since there is no stated intention
>>>>>> that etsi URNs are used only within a closed community.
>>>>>>
>>>>>>   Identifier uniqueness considerations:
>>>>>>
>>>>>>      [...]  ETSI is expected to guarantee the uniqueness [...]
>>>>>>
>>>>>> Formally, this registration is being submitted by ETSI, so it reads
>>>>>> oddly for ETSI to say "ETSI is expected...".   Much better would be
>>>>>> "ETSI will...".
>>>>>>
>>>>>> Similarly, "ETSI could..." is used where it is more natural to say "ETSI
>>>>>> may...".
>>>>>>
>>>>>>      Note that using experimental types may create
>>>>>>      collision as multiple users may use the same values for different
>>>>>>      resources and specific strings.
>>>>>>
>>>>>> It would be very helpful if the registration stated how the ETSI
>>>>>> registry will make clear how to recognize experimental URIs within the
>>>>>> etsi namespace.
>>>>>>
>>>>>> Dale
>>>>>
>>>>> Mahesh Jethanandani
>>>>> mjethanandani@gmail.com <mailto:mjethanandani@gmail.com>
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> urn mailing list
>>>> urn@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/urn
>>>>
>>
>