Re: [netmod] 6087bis namespace recommendations

Mahesh Jethanandani <mjethanandani@gmail.com> Tue, 12 January 2016 00:12 UTC

Return-Path: <mjethanandani@gmail.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEA0F1AC43B for <netmod@ietfa.amsl.com>; Mon, 11 Jan 2016 16:12:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 wRnE-C0m2Z2A for <netmod@ietfa.amsl.com>; Mon, 11 Jan 2016 16:12:39 -0800 (PST)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (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 85BC91AC439 for <netmod@ietf.org>; Mon, 11 Jan 2016 16:12:39 -0800 (PST)
Received: by mail-pa0-x22a.google.com with SMTP id yy13so236597069pab.3 for <netmod@ietf.org>; Mon, 11 Jan 2016 16:12:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=VIW66ejd14hoX5/6K5jg/wZq8h/jiLQWoVnJpoNTzBM=; b=cxqBV4DrfsIt8/kmwQ3vXR9odrahHe6V5L9Rxku80WfHQG54vqwj7KrE7Rnayw1M78 k7iP1LaeFvyRAxM7WfP5CaujZAHpj2SWYKjqGqj9zGb2KXtUirJchbblEm0uUOefpwqV KMTTNujJ/rKalZhfmtUwuHXPBRJFkDhEV8r5povpfn1ee3UvE3J7wrGsqeDR7NYOELOU ILY/z6KpHPdbFkqOBBBItwAXp357r5j2pqpNp5ZkNGfnqgOWqhxbDPc+TjAa45m6F6DX 4KB+lvXFrD/7liaK7gn+d+YzMZwj4ec/MLKougUSv3Ewmnupwp2moPXrJS3nwDqTMRlv +Ztw==
X-Received: by 10.66.251.226 with SMTP id zn2mr185428718pac.44.1452557559233; Mon, 11 Jan 2016 16:12:39 -0800 (PST)
Received: from [10.155.129.45] ([128.107.241.163]) by smtp.gmail.com with ESMTPSA id c90sm25709122pfd.31.2016.01.11.16.12.37 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 11 Jan 2016 16:12:38 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_615836C3-B2A2-480B-B6A4-D1341B595440"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Mahesh Jethanandani <mjethanandani@gmail.com>
In-Reply-To: <20160111.101526.1720014765007751699.mbj@tail-f.com>
Date: Mon, 11 Jan 2016 16:12:35 -0800
Message-Id: <163715AC-361A-4500-B362-7283A573DB0D@gmail.com>
References: <20160111.101526.1720014765007751699.mbj@tail-f.com>
To: Martin Bjorklund <mbj@tail-f.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/netmod/rTVK4bDhLo0kKCd10hdD2Cl-g04>
Cc: netmod@ietf.org
Subject: Re: [netmod] 6087bis namespace recommendations
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 12 Jan 2016 00:12:41 -0000

> On Jan 11, 2016, at 1:15 AM, Martin Bjorklund <mbj@tail-f.com> wrote:
> 
> Hi,
> 
> Currently, 6087bis says that standards-track, published and
> unpublished modules SHOULD use the URN prefix
> "urn:ietf:params:xml:ns:yang:".
> 
> There are two issues with this:
> 
>  1.  We already publish experimental modules w/ this prefix.
>      (ietf-netconf-time and ietf-complex-types).

True.

> 
>      So 6087bis should remove "standards track" from this
>      recommendation.

Yes. 

> 
>  2.  There was some discussion about recommending a different URN
>      prefix for unpublished modules (i.e., modules in Internet
>      Drafts).
> 
>      Should 6087bis recommend some special urn prefix for drafts,
>      with a note to the RFC editor to change the namespace once it
>      has been registered with IANA?

I am inclined to let the urn prefixes be what they will be once the document gets adopted as an RFC. There are plenty of tools and work today that extracts the module and uses it as is on an experimental basis. Having to change them every time the drafts changes or modify existing code once the module it uses becomes RFC is painful. Besides, the chances of conflict are low with the URN namespaces, so why make the process onerous.

> 
> And another issue.  6087bis also has this:
> 
> OLD: 
> 
>  The following examples are for non-Standards-Track modules.
>  The domain "example.com" SHOULD be used in all namespace URIs
>  for example modules.
> 
>      http://example.com/ns/example-interfaces
> 
>      http://example.com/ns/example-system
> 
> 
> First of all, the sentence about non-Standards-Track modules is
> confusing.  Second, since the publication of RFC 6087, RFC 6963 has
> been published, which defines a URN for examples.  I suggest we update
> 6087bis like this:
> 
> NEW:
> 
>  Example modules in all types of documents SHOULD use a namespace
>  with either the example URN [RFC 6963] or the domain "example.com".
>  For example:
> 
>      urn:example:interfaces
> 
>      http://example.com/ns/example-system <http://example.com/ns/example-system>

Agree.

> 
> 
> 
> /martin
> 
> 
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod

Mahesh Jethanandani
mjethanandani@gmail.com