IETF Logo Mail Archive

Re: [netmod] update on "rdns" URN for enterprise YANG models

Alex Campbell <Alex.Campbell@Aviatnet.com> Fri, 27 May 2016 00:53 UTC

Return-Path: <Alex.Campbell@Aviatnet.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0396912B008 for <netmod@ietfa.amsl.com>; Thu, 26 May 2016 17:53:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.327
X-Spam-Level:
X-Spam-Status: No, score=-3.327 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham 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 Z-iY-qvYIZLS for <netmod@ietfa.amsl.com>; Thu, 26 May 2016 17:53:43 -0700 (PDT)
Received: from mail-send.aviatnet.com (mail-send.aviatnet.com [192.147.115.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77FF812D9EC for <netmod@ietf.org>; Thu, 26 May 2016 17:53:43 -0700 (PDT)
From: Alex Campbell <Alex.Campbell@Aviatnet.com>
To: "Ing-Wher (Helen) Chen" <ichen@kuatrotech.com>
Thread-Topic: [netmod] update on "rdns" URN for enterprise YANG models
Thread-Index: AdGXJqT2atwqDO1sS7m+/GLgZx0D2AAPsN6AAAEKSAAAEGZBAAC512KAAAQnzAAAKonEAAcZFxLS
Date: Fri, 27 May 2016 00:53:41 +0000
Message-ID: <1464310422122.33255@Aviatnet.com>
References: <DB5PR06MB095051F32B9B7264669E6263D0680@DB5PR06MB0950.eurprd06.prod.outlook.com> <20160415152317.GB95324@elstar.local> <DB5PR06MB095009600454D4236CBDED94D0680@DB5PR06MB0950.eurprd06.prod.outlook.com> <20160415234236.GC95761@elstar.local> <DB5PR06MB0950D0118D54BCBBF10BEE64D06C0@DB5PR06MB0950.eurprd06.prod.outlook.com> <20160419182250.GA3771@elstar.local>, <DB5PR06MB0950607CBB91B3190358A46ED06D0@DB5PR06MB0950.eurprd06.prod.outlook.com>
In-Reply-To: <DB5PR06MB0950607CBB91B3190358A46ED06D0@DB5PR06MB0950.eurprd06.prod.outlook.com>
Accept-Language: en-NZ, en-US
Content-Language: en-NZ
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.15.6.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/netmod/yLq3mDT_rNoMHtYT9lMgrOADljA>
Cc: "netmod@ietf.org" <netmod@ietf.org>
Subject: Re: [netmod] update on "rdns" URN for enterprise YANG models
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 May 2016 00:53:45 -0000

> From: netmod <netmod-bounces@ietf.org> on behalf of Ing-Wher (Helen) Chen <ichen@kuatrotech.com>
> Sent: Thursday, 21 April 2016 2:40 a.m.
> To: Juergen Schoenwaelder
> Cc: netmod@ietf.org
> Subject: Re: [netmod] update on "rdns" URN for enterprise YANG models
> 
> > -----Original Message-----
> > From: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs-
> > university.de]
> > Sent: Tuesday, April 19, 2016 2:23 PM
> > To: Ing-Wher (Helen) Chen <ichen@kuatrotech.com>
> > Cc: netmod@ietf.org
> > Subject: Re: [netmod] update on "rdns" URN for enterprise YANG models
> >
> > On Tue, Apr 19, 2016 at 04:23:51PM +0000, Ing-Wher (Helen) Chen wrote:
> > > I'm not an expert on XML namespaces and I'm a little confused by some
> > > of the questions, so I apologize if my response below does not quite
> > > answer the questions.  I'd like to point out that the request for
> > > "rdns" URN is not to prevent the use of URLs. The request for "rdns"
> > > URN is to allow an enterprise to easily create a URN namespace, if the
> > > enterprise happens to prefer to use URN as a YANG module namespace.  I
> > > also think that the problems that arise when a YANG module uses a URN
> > > based on an enterprise's domain name are the same problems that arise
> > > when a YANG module uses a URL based on an enterprise's domain name.
> > > (Of course, this is not an excuse to fix the problems that should be
> > > fixed.)
> >
> > You write "happen to prefer to use URN" - why?

> draft-chen-rdns-urn Section 4 <https://tools.ietf.org/html/draft-chen-rdns-urn-06#section-4>
> discusses why an enterprise might prefer to use URN over URL.  URL provides
> resource access mechanism, which might mislead a customer to request that
> the YANG module be accessible at a specific location.  It's true that the device
> does not care that the YANG module is not at a particular URL, but I can still
> imagine getting a bug requesting that the YANG module be accessible at the URL.

URLs are frequently used as namespaces in XML, without referring to a particular resource (and most of them are HTTP URLs that return generic error-404 pages).
Does this proposal suggest that YANG namespaces should be treated differently from XML namespaces?

> Thanks,
> Helen

v2.23.0 | Report a Bug | By Email