Re: [urn] Formal URN request for ONF
worley@ariadne.com (Dale R. Worley) Sat, 26 May 2018 03:27 UTC
Return-Path: <worley@alum.mit.edu>
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 A8AA21277BB for <urn@ietfa.amsl.com>; Fri, 25 May 2018 20:27:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.686
X-Spam-Level:
X-Spam-Status: No, score=-1.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 7dfvOU1bj7qp for <urn@ietfa.amsl.com>; Fri, 25 May 2018 20:27:39 -0700 (PDT)
Received: from resqmta-ch2-04v.sys.comcast.net (resqmta-ch2-04v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:36]) (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 D6CA8124217 for <urn@ietf.org>; Fri, 25 May 2018 20:27:38 -0700 (PDT)
Received: from resomta-ch2-18v.sys.comcast.net ([69.252.207.114]) by resqmta-ch2-04v.sys.comcast.net with ESMTP id MOyqfQIwP40iXMPrlfFYm1; Sat, 26 May 2018 03:27:37 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-18v.sys.comcast.net with ESMTPA id MPrjfSvk9EY3qMPrjfMOWi; Sat, 26 May 2018 03:27:36 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id w4Q3RYxJ008886; Fri, 25 May 2018 23:27:34 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id w4Q3RXCj008883; Fri, 25 May 2018 23:27:33 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Scott Mansfield <scott.mansfield@ericsson.com>, timon@opennetworking.org
Cc: urn@ietf.org
In-Reply-To: <EF35EE4B92789843B1DECBC0E24558646BDDCAF9@eusaamb107.ericsson.se> (scott.mansfield@ericsson.com)
Sender: worley@ariadne.com
Date: Fri, 25 May 2018 23:27:32 -0400
Message-ID: <87h8mvqeor.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfDYBibld2mgrxkNXLDX5MUWxFn+6oosixFBdGpXBDHpsM0C5LSz/vHZwtjDXnXs9Gbm8WhQ0DjdQ5lKCyMcRMAp1y1NZMmuyEs8ATntsnYsFFbuChMGR r5VI3lFURyHUzybfjuNjnY4I5EfeX3aMzJWFpZ0OlGDZUlvcRnQu3n5nNr6qbXjCB//806Ots/fbZW0f9lCWg0wwMMbx6zjUJz7hvNWYe73rEEUCVAAOjMJs v3vs6vvtfIYmi+ycuZ+BDGYPEAGL7P6VvEQF2zsCPCL60A6p1nWpqYBv4Q/ivcyHOxqRQkfejczvSbuwUkwF/A==
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/CsjLpBXzBT1bdVmwXxLC5UnPSNY>
Subject: Re: [urn] Formal URN request for ONF
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 26 May 2018 03:27:42 -0000
Comments on draft-onf-urn, dated 22 May 2018: The draft is quite straightforward and well-conceived. It does need some improvements in how the namespace is explained. I was going to complain that the document does not specify any rules for lexical equivalence, but RFC 8141 seems to have eliminated the requirement to specify lexical equivalence rules, and to have provided default rules. 2.5. Purpose Namespace needed for YANG RFC 6020 [2] RFC 7950 [3] modules. It seems like it would be wise to allow other uses of the URN namespace. Perhaps: Namespace needed for identifiers defined by ONF, including those of YANG modules [2][3]. 2.6. Syntax urn:onf:{ResourceSpecificString} "ResourceSpecificString" identifies the information about the resource. You want to add "It must conform to the syntax NSS in [1]." so as to have an unambiguous statement of the syntax. urn:{ONF-NamespaceId}:{ONF-Project}:{ONF-SubProject}:{Protocol}:{ModuleName} o ONF-NamespaceId: onf The following four component descriptions present the four components in four distinct ways. I suggest you make them consistent and clearly separate (1) the name of the component, (2) the example value of the component, and (3) the meaning of the example value, for each of the four components. E.g., o The ONF-Project: Example: "otcc" (Open Transport Configuration & Control) etc. 2.7. Assignment ONF manages resources that utilize this URN identification model. More to the point, ONF manages the *identifiers* in this URN model. Perhaps phrase this as ONF manages this URN identification model and the assignment of identifiers within it to resources. 2.11. Documentation The ONF maintains a Uniform Resource Names (URN) document that provides the mechanism to ensure the resource identifiers are unique. Is there any (public) reference to this document describing the mechanism? 4. Revision Information o v1: Initial Version o v2: Aligned with template in Appendix A RFC 8141 [1] o v3: Moved example to the syntax system. Removed reference to RFC1737, and moved RFC8141 to normative. It took me a moment to realize that this section described revisions of this document, and not revisions of the URN registration. Document-revision information is usually removed upon publication, so you want to add a note: [Note to RFC Editor: Please remove this section before publication.] 5. Acknowledgements Technical contact person: Kam Lam Role: Co-Chair of Open Information Modeling and Tooling Project Email: kam.lam@fiberhome.com Is this an acknowledgment (in which case the heading line is not really correct), or does it provide a technical contact (which should be added to section 2.4)? Or perhaps it is both? Dale
- [urn] Formal URN request for ONF Scott Mansfield
- Re: [urn] Formal URN request for ONF Peter Saint-Andre
- Re: [urn] Formal URN request for ONF Svensson, Lars
- Re: [urn] Formal URN request for ONF Dale R. Worley