> On 09 Jun 2016, at 13:57, Juergen Schoenwaelder
> wrote:
>
> On Thu, Jun 09, 2016 at 01:08:36PM +0200, Ladislav Lhotka wrote:
>>
>>> On 09 Jun 2016, at 02:25, Andy Bierman wrote:
>>>
>>> Hi,
>>>
>>>
>>> We have been asked to
> On 08 Jun 2016, at 17:22, Dale R. Worley wrote:
>
> Martin Bjorklund writes:
>> The text for "path" already says:
>>
>> It takes as an argument a
>> string that MUST refer to a leaf or leaf-list node.
>
> Given what the text must mean, that's
All,
RFC 6020bis says “The ABNF grammar [RFC5234] [RFC7405] defines the canonical
order. To improve module readability, it is RECOMMENDED that clauses be entered
in this order.”
The ABNF places linkage-stmts (import, include) before meta-stmts
(organization, contact, description, reference)
Ladislav Lhotka wrote:
>
> > On 09 Jun 2016, at 02:25, Andy Bierman wrote:
> >
> > Hi,
> >
> >
> > We have been asked to make the YANG library module consistent
> > wrt/ use of a container parent for a list. We decided to remove the
> > submodules
> On 09 Jun 2016, at 02:25, Andy Bierman wrote:
>
> Hi,
>
>
> We have been asked to make the YANG library module consistent
> wrt/ use of a container parent for a list. We decided to remove the
> submodules container parent from the child submodule.
> The submodule list
On Thu, Jun 09, 2016 at 01:08:36PM +0200, Ladislav Lhotka wrote:
>
> > On 09 Jun 2016, at 02:25, Andy Bierman wrote:
> >
> > Hi,
> >
> >
> > We have been asked to make the YANG library module consistent
> > wrt/ use of a container parent for a list. We decided to remove
Ladislav Lhotka wrote:
>
> > On 09 Jun 2016, at 13:57, Juergen Schoenwaelder
> > wrote:
> >
> > On Thu, Jun 09, 2016 at 01:08:36PM +0200, Ladislav Lhotka wrote:
> >>
> >>> On 09 Jun 2016, at 02:25, Andy Bierman wrote:
> On 09 Jun 2016, at 14:18, Martin Bjorklund wrote:
>
> Ladislav Lhotka wrote:
>>
>>> On 09 Jun 2016, at 13:57, Juergen Schoenwaelder
>>> wrote:
>>>
>>> On Thu, Jun 09, 2016 at 01:08:36PM +0200, Ladislav Lhotka wrote:
wor...@ariadne.com (Dale R. Worley) wrote:
> William Lupton writes:
> > Consider the YANG module, submodule and tree files shown
> > below. Suppose that I regret the decision to make "submod" be a
> > submodule and want to replace it with a module (see listings
Martin,
I think that the answer is “yes” but please could you just confirm that the
alternatives presented here are valid? In the real world I think I would
usually follow the second approach of retaining the submodule (including its
groupings) but simply breaking out the definitions of the
I'm also in favor of B.
I personally do not like the way state/config are expressed in [1] as it
complexifies the way yang modules are written while a solution like [4] allows
to have a more cleaner yang module while achieving the same goal.
As expressed by others, B will also be faster with
Dean/Acee,
Is this a relevant example of ACL being configured on an interface?
http://www.cisco.com/c/en/us/td/docs/routers/asr9000/software/asr9k_r4-2/addr_serv/configuration/guide/b_ipaddr_cg42a9k/b_ipaddr_cg42a9k_chapter_01.html#task_1049371
Talking to implementers, the feature is very much
FYI.
Forwarded Message
Subject:YANG Model Coordination Group directory closure
Date: Thu, 9 Jun 2016 17:35:07 +0200
From: Benoit Claise
To: IETF-Discussion list , yang-co...@ietf.org
Dear all,
The YANG
Hi Mahesh,
From: Mahesh Jethanandani
Date: Thursday, June 9, 2016 at 10:35 AM
To: Dean Bogdanovic
Cc: Acee Lindem , netmod WG
Subject: Re: [netmod] Remove input-interface (metadata) from
netmod-acl-model-07 ?
Martin Bjorklund writes:
> Do you have an suggestion for what to write? These kinds of
> multi-line strings are almost always 'description' statements,
> used for human consumption. It is not clear to me what the warning
> would be.
>> So you can't write an isolated CR in most
> -Original Message-
> From: Alex Campbell [mailto:alex.campb...@aviatnet.com]
> Sent: Thursday, May 26, 2016 8:54 PM
> To: Ing-Wher (Helen) Chen
> Cc: netmod@ietf.org
> Subject: Re: [netmod] update on "rdns" URN for enterprise YANG models
>
>
> > From: netmod
wor...@ariadne.com (Dale R. Worley) wrote:
> Martin Bjorklund writes:
> > Do you have an suggestion for what to write? These kinds of
> > multi-line strings are almost always 'description' statements,
> > used for human consumption. It is not clear to me what the warning
> >
My preference is not to add schema nodes that are not useful.
If it is foreseen that other nodes will be added in the container then the
container is fine; otherwise I see no reason to have one.
From: netmod on behalf of Andy Bierman
Martin Bjorklund writes:
>> If I understand Yang correctly, that error can't be fixed by revising
>> the new module test to clone mod:util as test:util, because though the
>> new grouping is semantically identical to the old grouping, it's still a
>> change in its definition:
>
>
> On Jun 9, 2016, at 7:58 AM, Acee Lindem (acee) wrote:
>>
>> Is this a relevant example of ACL being configured on an interface?
>>
>> http://www.cisco.com/c/en/us/td/docs/routers/asr9000/software/asr9k_r4-2/a
>>
At this point, I think there are some aspects of the use of strings and
identifiers that aren't completely specified, but I'd have to check the
current text to know for certain. However, that's a minor matter.
The issue that concerns me is that the ABNF doesn't specify what is
allowed as a
It is shown in the draft as an example of how to augment the interface module.
Just to be clear -> the link you sent to the Cisco doc does not show the use of
'metadata' or an input-interface match criteria.
Jason
-Original Message-
From: netmod [mailto:netmod-boun...@ietf.org] On
22 matches
Mail list logo