Subject: [netmod] FW: FW: Last Call: draft-ietf-netmod-yang (YANG - A data modeling languagefor NETCONF) to Proposed Standard

From: "Romascanu, Dan (Dan)" <[email-masked]>
Date: Thu, 11 Mar 2010 14:35:56 +0100

-----Original Message-----
From: Julian Reschke [mailto:[email-masked]] 
Sent: Thursday, March 11, 2010 3:33 PM
To: Romascanu, Dan (Dan)
Cc: [email-masked]; [email-masked]
Subject: Re: FW: Last Call: draft-ietf-netmod-yang (YANG - A data
modeling languagefor NETCONF) to Proposed Standard

On 11.03.2010 14:13, Romascanu, Dan (Dan) wrote:
>   XML and APPS Experts,
>
> I would like to draw you attention on the IETF Last Call for the YANG 
> data modeling language for NETCONF that started yesterday and will 
> last for about one month.
>
> Your comments and reviews will be appreciated.
>
> Thanks and Regards,
>
> Dan
> ...

Isolated comment:

> 5.3.  XML Namespaces
>
>    All YANG definitions are specified within a module that is bound to
a
>    particular XML Namespace [XML-NAMES], which is a globally unique
URI
>    [RFC3986].  A NETCONF client or server uses the namespace during
XML
>    encoding of data.
>
>    Namespaces for modules published in RFC streams [RFC4844] MUST be
>    assigned by IANA, see Section 14.

I don't see why this is a requirement. The whole point of using URIs as
XML namespace identifiers is that you don't *need* a central authority
for assignment.

>    Namespaces for private modules are assigned by the organization
>    owning the module without a central registry.  Namespace URIs MUST
be
>    chosen so they cannot collide with standard or other enterprise
>    namespaces, for example by using the enterprise or organization
name
>    in the namespace.

That's true, but IMHO just repeats best XML practice.

>    The "namespace" statement is covered in Section 7.1.3.

Best regards, Julian