Re: [urn] URN expert review of 'etsi' NID

Mahesh Jethanandani <mjethanandani@gmail.com> Fri, 08 June 2018 16:56 UTC

Return-Path: <mjethanandani@gmail.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 00173130F23; Fri, 8 Jun 2018 09:56:05 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 sVLWYuuC4oQk; Fri, 8 Jun 2018 09:56:03 -0700 (PDT)
Received: from mail-pf0-x236.google.com (mail-pf0-x236.google.com [IPv6:2607:f8b0:400e:c00::236]) (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 C1E0A130F19; Fri, 8 Jun 2018 09:56:03 -0700 (PDT)
Received: by mail-pf0-x236.google.com with SMTP id j20-v6so6918070pff.10; Fri, 08 Jun 2018 09:56:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=dzx+zcueeiNHIWf3AxwRN6gGyqC+u0rl4l72W1LmOV4=; b=ET/MWjbE+Syfyyvty2uuHr7h83/Dtn72lG2aPR622WOG+DUPUQKzaBKWCAobU+K4yT QRDnWZm9Ju5wpB6JrPZrpfSjWeH2Pr8VRQmLttUWDG9xJOKSXlECFC7V5mvn2DtFW9II VnyPyAJrhOs3Ie744NSFmcSXORw9oxUg6QP0so+79GNX7FVlqGByJB9ElhUJdbFyOnEh mfSrHAjz/XjkuzzDEo81UsnlhTZyETL+XXA9WPfBiYeFWc2b1wsiJ4VUhobojAqhZqNm nJrA0HLNzIUplX3LGjrAUczXMDbla0fruq4T8gZGNuMGIwCE4/jCv/JY0GMAOow/OJPm Vhpw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=dzx+zcueeiNHIWf3AxwRN6gGyqC+u0rl4l72W1LmOV4=; b=MtKif/gADLjocNpM8R5ummk8ieSgt9k3QhX5jUXTQGaaEq0nbp3lP5S6az4jMZeycW sDlFZYLalnxHeMxyt9Hszl8WAMoVYvh6jWlpCIFXgUdLNcHAo66yDFqku22WsaxLOcx8 UmFqebP0WV0Re6G8khmjYOBB7Fv+AbyT0R/+WhocFKeraLZ0pKmzpOPZKyWQqnZuPUI9 v6djYvB6qkXQb5k5nRtdtHr16zMH5PduHj6n3lMwhbMUFNHQM/9IRKOiuMzh2ZXp6XxI qFIehn/krB2nu2NrQinJUViRnU/KsG95bWr6qp57euxG/7tre/3Gyf9Pg4fmSKZptR4D EczQ==
X-Gm-Message-State: APt69E0bytfs2LEEKSlYz0cfVjq4dwMEabGOt7z7V5vTsmtCcHZre2vc gLSAJwj5tZZRGiMLacpg5ko=
X-Google-Smtp-Source: ADUXVKIp7chYZiwY73b4VVkXD7kd2/ScNcBHHXQULO4xh5+jpEtaKZicIwQK5/GSIN135NVH9pRaVw==
X-Received: by 2002:a65:62ce:: with SMTP id m14-v6mr5934580pgv.407.1528476963300; Fri, 08 Jun 2018 09:56:03 -0700 (PDT)
Received: from ?IPv6:2601:647:4700:1280:433:2e83:815e:b150? ([2601:647:4700:1280:433:2e83:815e:b150]) by smtp.gmail.com with ESMTPSA id 29-v6sm97878348pfj.14.2018.06.08.09.56.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 08 Jun 2018 09:56:02 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\))
From: Mahesh Jethanandani <mjethanandani@gmail.com>
In-Reply-To: <87fu1yhwlk.fsf@hobgoblin.ariadne.com>
Date: Fri, 08 Jun 2018 09:56:01 -0700
Cc: Peter Saint-Andre <stpeter@mozilla.com>, urn@ietf.org, Ignas Bagdonas <ibagdona@gmail.com>, draft-mahesh-etsi-urn@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <11EAC9EB-F3B8-45AF-88F1-E70F8CA9F0D5@gmail.com>
References: <87fu1yhwlk.fsf@hobgoblin.ariadne.com>
To: "Dale R. Worley" <worley@ariadne.com>
X-Mailer: Apple Mail (2.3445.8.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/cXZoDgshsxRYnfSLXHlFPXonP_w>
Subject: Re: [urn] URN expert review of 'etsi' NID
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.26
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: Fri, 08 Jun 2018 16:56:06 -0000

Hi Dale,

> On Jun 7, 2018, at 6:53 PM, Dale R. Worley <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        |

Ok. Will add ETSI in front of the definition for PNNS.

> 
>   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.

In my response to Peter, I stated that the syntax of the NSS will be specified as part of the ancillary document at the URL specified, and I will work with my co-author to publish that URL such that it is readable by the world.

> 
>   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…".

Updated the text to say:

ETSI will guarantee the uniqueness of the strings …

> 
> Similarly, "ETSI could..." is used where it is more natural to say "ETSI
> may…".

Updated to say:

ETSI may allow for use of experimental type values ...

> 
>      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.

That will be part of the NSS definition in the ancillary document. But basically, the idea is use something like :xid:, or experimental id, as part of the NSS to distinguish it from assigned values.

Thanks.

> 
> Dale

Mahesh Jethanandani
mjethanandani@gmail.com