Re: [netmod] I-D Action: draft-ietf-netmod-schema-mount-07.txt

[Martin Bjorklund]

"t.petch"  wrote:
> - Original Message -
> From: "Ladislav Lhotka" 
> Sent: Thursday, October 05, 2017 1:52 PM
> > Martin Bjorklund  writes:
> >
> > > This version fixes the XPath context for parent-reference.
> > >
> > > However, there is one more thing to discuss, which is the term
> "mount
> > > point".
> > >
> > > The current text says:
> > >
> > >- mount point: container or list node whose definition contains
> > >  the "mount-point" extension statement. The argument of the
> > >  "mount-point" statement defines the name of the mount point.
> > >
> > > So if we have:
> > >
> > >   container top {
> > > container root {
> > >   yangmnt:mount-point ni;
> > > }
> > >   }
> > >
> > > There is one mount point, the node /top/root, with the name "ni".
> > >
> > > Pretty confusing...   Does anyone have any comments around this?
> >
> > What about this?
> >
> > OLD
> >
> > - mount point: container or list node whose definition contains
> >   the "mount-point" extension statement. The argument of the
> >   "mount-point" statement defines the name of the mount point.
> >
> > NEW
> >
> > - mount point: container or list node whose definition contains
> >   the "mount-point" extension statement. The argument of the
> >   "mount-point" statement defines a label that is used for
> >   referencing the mount point.
> 
> Lada
> 
> Trouble is 'label' is not a defined term in RFC7950 which leaves me (and
> others) wondering what is this undefined concept.  I know plenty of
> languages that have the concept of a label but YANG is not one of them.

As Lada explained, currently we have two meanings of the term "mount
point name" - it means both the name of the container/list node, and
the argument to the extension.  So the idea is to have a different
term for the latter.

> I looked to see what the ABNF says for inspiration but there isn't
> any:-)  I think that there should be.
> 
> I looked for a worked example for inspiration, nope, none of them
> either!   What I mean is that in e.g. A.3  mount point with name root
> appears, but that is the only instance of 'root'.  The whole point is
> that root should appear more than once, once for where the mount will
> be, and then once or more times for the part that will be mounted, so an
> example where name appears once is not an example IMHO!

I don't understand this.  Can you elaborate?


/martin


> 
> Tom Petch
> 
> > Lada
> >
> > >
> > >
> > >
> > > /martin
> > >
> 

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] I-D Action: draft-ietf-netmod-schema-mount-07.txt

[t.petch]

- Original Message -
From: "Ladislav Lhotka" 
Sent: Thursday, October 05, 2017 1:52 PM
> Martin Bjorklund  writes:
>
> > This version fixes the XPath context for parent-reference.
> >
> > However, there is one more thing to discuss, which is the term
"mount
> > point".
> >
> > The current text says:
> >
> >- mount point: container or list node whose definition contains
> >  the "mount-point" extension statement. The argument of the
> >  "mount-point" statement defines the name of the mount point.
> >
> > So if we have:
> >
> >   container top {
> > container root {
> >   yangmnt:mount-point ni;
> > }
> >   }
> >
> > There is one mount point, the node /top/root, with the name "ni".
> >
> > Pretty confusing...   Does anyone have any comments around this?
>
> What about this?
>
> OLD
>
> - mount point: container or list node whose definition contains
>   the "mount-point" extension statement. The argument of the
>   "mount-point" statement defines the name of the mount point.
>
> NEW
>
> - mount point: container or list node whose definition contains
>   the "mount-point" extension statement. The argument of the
>   "mount-point" statement defines a label that is used for
>   referencing the mount point.

Lada

Trouble is 'label' is not a defined term in RFC7950 which leaves me (and
others) wondering what is this undefined concept.  I know plenty of
languages that have the concept of a label but YANG is not one of them.

I looked to see what the ABNF says for inspiration but there isn't
any:-)  I think that there should be.

I looked for a worked example for inspiration, nope, none of them
either!   What I mean is that in e.g. A.3  mount point with name root
appears, but that is the only instance of 'root'.  The whole point is
that root should appear more than once, once for where the mount will
be, and then once or more times for the part that will be mounted, so an
example where name appears once is not an example IMHO!

Tom Petch

> Lada
>
> >
> >
> >
> > /martin
> >

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] I-D Action: draft-ietf-netmod-schema-mount-07.txt

[Ladislav Lhotka]

Martin Bjorklund  writes:

> Hi,
>
> This version fixes the XPath context for parent-reference.
>
>
> However, there is one more thing to discuss, which is the term "mount
> point".  
>
> The current text says:
>
>- mount point: container or list node whose definition contains
>  the "mount-point" extension statement. The argument of the
>  "mount-point" statement defines the name of the mount point.
>
>
> So if we have:
> 
>   container top {
> container root {
>   yangmnt:mount-point ni;
> }
>   }
> 
> There is one mount point, the node /top/root, with the name "ni".
>
> Pretty confusing...   Does anyone have any comments around this?

What about this?

OLD

- mount point: container or list node whose definition contains
  the "mount-point" extension statement. The argument of the
  "mount-point" statement defines the name of the mount point.

NEW

- mount point: container or list node whose definition contains
  the "mount-point" extension statement. The argument of the
  "mount-point" statement defines a label that is used for
  referencing the mount point.

Lada

>
>
>
> /martin
>
>
>
>
>
> internet-dra...@ietf.org wrote:
>> 
>> A New Internet-Draft is available from the on-line Internet-Drafts 
>> directories.
>> This draft is a work item of the Network Modeling WG of the IETF.
>> 
>> Title   : YANG Schema Mount
>> Authors : Martin Bjorklund
>>   Ladislav Lhotka
>>  Filename: draft-ietf-netmod-schema-mount-07.txt
>>  Pages   : 27
>>  Date: 2017-09-27
>> 
>> Abstract:
>>This document defines a mechanism to combine YANG modules into the
>>schema defined in other YANG modules.
>> 
>> 
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-netmod-schema-mount/
>> 
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-ietf-netmod-schema-mount-07
>> https://datatracker.ietf.org/doc/html/draft-ietf-netmod-schema-mount-07
>> 
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-netmod-schema-mount-07
>> 
>> 
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>> 
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>> 
>> ___
>> netmod mailing list
>> netmod@ietf.org
>> https://www.ietf.org/mailman/listinfo/netmod
>> 
>
> ___
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod

-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] I-D Action: draft-ietf-netmod-schema-mount-07.txt

[Martin Bjorklund]

Lou Berger  wrote:
> Hi Martin,
> 
> See below
> 
> On 9/27/2017 6:55 AM, Martin Bjorklund wrote:
> > Hi,
> >
> > This version fixes the XPath context for parent-reference.
> >
> >
> > However, there is one more thing to discuss, which is the term "mount
> > point".  
> >
> > The current text says:
> >
> >- mount point: container or list node whose definition contains
> >  the "mount-point" extension statement. The argument of the
> >  "mount-point" statement defines the name of the mount point.
> >
> >
> > So if we have:
> > 
> >   container top {
> > container root {
> >   yangmnt:mount-point ni;
> > }
> >   }
> > 
> > There is one mount point, the node /top/root, with the name "ni".
> in the NI draft [1] we solve this by keeping the names the same:
> 
>     container vrf-root {
>   description
>     "Container for mount point.";
>   yangmnt:mount-point "vrf-root" {
>     description
>   "Root for L3VPN type models. This will typically
>    not be an inline type mount point.";
>   }
>     }
> 
> [1] https://tools.ietf.org/html/draft-ietf-rtgwg-ni-model-04
> > Pretty confusing...   Does anyone have any comments around this?
> >
> When the NE authors discussed this, we (a) discussed it's not a
> significant impediment or issue worth discussing, and (b) one author
> noted that the flexibility may even be useful down the road.

Yes, I don't want to change any functionality, but perhaps change the
terminology to make it less confusion.

Maybe change the extension to:

  extension mount-point {
argument id; // instead of 'name'
...
  }

So the container "vrf-root" would be a mount point, with id "ni".



/martin




> 
> Thanks,
> Lou
> (As contributor)
>  
> >
> > /martin
> >
> >
> >
> >
> >
> > internet-dra...@ietf.org wrote:
> >> A New Internet-Draft is available from the on-line Internet-Drafts 
> >> directories.
> >> This draft is a work item of the Network Modeling WG of the IETF.
> >>
> >> Title   : YANG Schema Mount
> >> Authors : Martin Bjorklund
> >>   Ladislav Lhotka
> >>Filename: draft-ietf-netmod-schema-mount-07.txt
> >>Pages   : 27
> >>Date: 2017-09-27
> >>
> >> Abstract:
> >>This document defines a mechanism to combine YANG modules into the
> >>schema defined in other YANG modules.
> >>
> >>
> >> The IETF datatracker status page for this draft is:
> >> https://datatracker.ietf.org/doc/draft-ietf-netmod-schema-mount/
> >>
> >> There are also htmlized versions available at:
> >> https://tools.ietf.org/html/draft-ietf-netmod-schema-mount-07
> >> https://datatracker.ietf.org/doc/html/draft-ietf-netmod-schema-mount-07
> >>
> >> A diff from the previous version is available at:
> >> https://www.ietf.org/rfcdiff?url2=draft-ietf-netmod-schema-mount-07
> >>
> >>
> >> Please note that it may take a couple of minutes from the time of 
> >> submission
> >> until the htmlized version and diff are available at tools.ietf.org.
> >>
> >> Internet-Drafts are also available by anonymous FTP at:
> >> ftp://ftp.ietf.org/internet-drafts/
> >>
> >> ___
> >> netmod mailing list
> >> netmod@ietf.org
> >> https://www.ietf.org/mailman/listinfo/netmod
> >>
> > ___
> > netmod mailing list
> > netmod@ietf.org
> > https://www.ietf.org/mailman/listinfo/netmod
> >
> 
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] I-D Action: draft-ietf-netmod-schema-mount-07.txt

[Lou Berger]

Hi Martin,

See below

On 9/27/2017 6:55 AM, Martin Bjorklund wrote:
> Hi,
>
> This version fixes the XPath context for parent-reference.
>
>
> However, there is one more thing to discuss, which is the term "mount
> point".  
>
> The current text says:
>
>- mount point: container or list node whose definition contains
>  the "mount-point" extension statement. The argument of the
>  "mount-point" statement defines the name of the mount point.
>
>
> So if we have:
> 
>   container top {
> container root {
>   yangmnt:mount-point ni;
> }
>   }
> 
> There is one mount point, the node /top/root, with the name "ni".
in the NI draft [1] we solve this by keeping the names the same:

    container vrf-root {
  description
    "Container for mount point.";
  yangmnt:mount-point "vrf-root" {
    description
  "Root for L3VPN type models. This will typically
   not be an inline type mount point.";
  }
    }

[1] https://tools.ietf.org/html/draft-ietf-rtgwg-ni-model-04
> Pretty confusing...   Does anyone have any comments around this?
>
When the NE authors discussed this, we (a) discussed it's not a
significant impediment or issue worth discussing, and (b) one author
noted that the flexibility may even be useful down the road.

Thanks,
Lou
(As contributor)
 
>
> /martin
>
>
>
>
>
> internet-dra...@ietf.org wrote:
>> A New Internet-Draft is available from the on-line Internet-Drafts 
>> directories.
>> This draft is a work item of the Network Modeling WG of the IETF.
>>
>> Title   : YANG Schema Mount
>> Authors : Martin Bjorklund
>>   Ladislav Lhotka
>>  Filename: draft-ietf-netmod-schema-mount-07.txt
>>  Pages   : 27
>>  Date: 2017-09-27
>>
>> Abstract:
>>This document defines a mechanism to combine YANG modules into the
>>schema defined in other YANG modules.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-netmod-schema-mount/
>>
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-ietf-netmod-schema-mount-07
>> https://datatracker.ietf.org/doc/html/draft-ietf-netmod-schema-mount-07
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-netmod-schema-mount-07
>>
>>
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> ___
>> netmod mailing list
>> netmod@ietf.org
>> https://www.ietf.org/mailman/listinfo/netmod
>>
> ___
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
>

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] I-D Action: draft-ietf-netmod-schema-mount-07.txt

[Xufeng Liu]

Alternatively we can use "/top/root" as the name of the mount-point, then
there won't be case for 
  'A module MAY contain multiple "mount-point" statements having the same
argument.'
The "mount-point" extension statement won't take an argument, which will be
cleaner, and make the extension statement look more like a property
specifier than a node declaration.

Thanks,
- Xufeng

> -Original Message-
> From: netmod [mailto:netmod-boun...@ietf.org] On Behalf Of Martin
> Bjorklund
> Sent: Wednesday, September 27, 2017 6:56 AM
> To: netmod@ietf.org
> Subject: Re: [netmod] I-D Action: draft-ietf-netmod-schema-mount-07.txt
> 
> Hi,
> 
> This version fixes the XPath context for parent-reference.
> 
> 
> However, there is one more thing to discuss, which is the term "mount
point".
> 
> The current text says:
> 
>- mount point: container or list node whose definition contains
>  the "mount-point" extension statement. The argument of the
>  "mount-point" statement defines the name of the mount point.
> 
> 
> So if we have:
> 
>   container top {
> container root {
>   yangmnt:mount-point ni;
> }
>   }
> 
> There is one mount point, the node /top/root, with the name "ni".
> 
> Pretty confusing...   Does anyone have any comments around this?
> 
> 
> 
> /martin
> 
> 
> 
> 
> 
> internet-dra...@ietf.org wrote:
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
directories.
> > This draft is a work item of the Network Modeling WG of the IETF.
> >
> > Title   : YANG Schema Mount
> > Authors : Martin Bjorklund
> >   Ladislav Lhotka
> > Filename: draft-ietf-netmod-schema-mount-07.txt
> > Pages   : 27
> > Date: 2017-09-27
> >
> > Abstract:
> >This document defines a mechanism to combine YANG modules into the
> >schema defined in other YANG modules.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-netmod-schema-mount/
> >
> > There are also htmlized versions available at:
> > https://tools.ietf.org/html/draft-ietf-netmod-schema-mount-07
> > https://datatracker.ietf.org/doc/html/draft-ietf-netmod-schema-mount-0
> > 7
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-netmod-schema-mount-07
> >
> >
> > Please note that it may take a couple of minutes from the time of
> > submission until the htmlized version and diff are available at
tools.ietf.org.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > ___
> > netmod mailing list
> > netmod@ietf.org
> > https://www.ietf.org/mailman/listinfo/netmod
> >
> 
> ___
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] I-D Action: draft-ietf-netmod-schema-mount-07.txt

[Martin Bjorklund]

Hi,

This version fixes the XPath context for parent-reference.


However, there is one more thing to discuss, which is the term "mount
point".  

The current text says:

   - mount point: container or list node whose definition contains
 the "mount-point" extension statement. The argument of the
 "mount-point" statement defines the name of the mount point.


So if we have:

  container top {
container root {
  yangmnt:mount-point ni;
}
  }

There is one mount point, the node /top/root, with the name "ni".

Pretty confusing...   Does anyone have any comments around this?



/martin





internet-dra...@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
> This draft is a work item of the Network Modeling WG of the IETF.
> 
> Title   : YANG Schema Mount
> Authors : Martin Bjorklund
>   Ladislav Lhotka
>   Filename: draft-ietf-netmod-schema-mount-07.txt
>   Pages   : 27
>   Date: 2017-09-27
> 
> Abstract:
>This document defines a mechanism to combine YANG modules into the
>schema defined in other YANG modules.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-netmod-schema-mount/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-netmod-schema-mount-07
> https://datatracker.ietf.org/doc/html/draft-ietf-netmod-schema-mount-07
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-netmod-schema-mount-07
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> ___
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
> 

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

[netmod] I-D Action: draft-ietf-netmod-schema-mount-07.txt

[internet-drafts]

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Network Modeling WG of the IETF.

Title   : YANG Schema Mount
Authors : Martin Bjorklund
  Ladislav Lhotka
Filename: draft-ietf-netmod-schema-mount-07.txt
Pages   : 27
Date: 2017-09-27

Abstract:
   This document defines a mechanism to combine YANG modules into the
   schema defined in other YANG modules.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-netmod-schema-mount/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-netmod-schema-mount-07
https://datatracker.ietf.org/doc/html/draft-ietf-netmod-schema-mount-07

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-netmod-schema-mount-07


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod