On Tue, Dec 19, 2017 at 07:11:59AM +0100, Ladislav Lhotka wrote:
> On Mon, 2017-12-18 at 15:30 -0500, Lou Berger wrote:
> > lada,
> >
> > See below.
> >
> >
> > On 12/15/2017 8:59 AM, Ladislav Lhotka wrote:
> > > Hi,
> > >
> > > unfortunately, using an action for querying embedded YANG libr
On Tue, 2017-12-19 at 10:05 +0100, Juergen Schoenwaelder wrote:
> On Tue, Dec 19, 2017 at 07:11:59AM +0100, Ladislav Lhotka wrote:
> > On Mon, 2017-12-18 at 15:30 -0500, Lou Berger wrote:
> > > lada,
> > >
> > > See below.
> > >
> > >
> > > On 12/15/2017 8:59 AM, Ladislav Lhotka wrote:
> > >
Lada,
On December 19, 2017 1:12:35 AM Ladislav Lhotka wrote:
On Mon, 2017-12-18 at 15:30 -0500, Lou Berger wrote:
lada,
See below.
On 12/15/2017 8:59 AM, Ladislav Lhotka wrote:
> Hi,
>
> unfortunately, using an action for querying embedded YANG library data
> (needed for the "inline"
On Tue, 2017-12-19 at 06:20 -0500, Lou Berger wrote:
> Lada,
>
>
> On December 19, 2017 1:12:35 AM Ladislav Lhotka wrote:
>
> > On Mon, 2017-12-18 at 15:30 -0500, Lou Berger wrote:
> > > lada,
> > >
> > > See below.
> > >
> > >
> > > On 12/15/2017 8:59 AM, Ladislav Lhotka wrote:
> > > >
Woops that should be rw...
On December 19, 2017 6:21:22 AM Lou Berger wrote:
Lada,
On December 19, 2017 1:12:35 AM Ladislav Lhotka wrote:
On Mon, 2017-12-18 at 15:30 -0500, Lou Berger wrote:
lada,
See below.
On 12/15/2017 8:59 AM, Ladislav Lhotka wrote:
> Hi,
>
> unfortunately, u
Hi Lada,
On 12/19/2017 6:23 AM, Ladislav Lhotka wrote:
> On Tue, 2017-12-19 at 06:20 -0500, Lou Berger wrote:
>> Lada,
>>
>>
>> On December 19, 2017 1:12:35 AM Ladislav Lhotka wrote:
>>
>>> On Mon, 2017-12-18 at 15:30 -0500, Lou Berger wrote:
lada,
See below.
On
On Tue, 2017-12-19 at 06:43 -0500, Lou Berger wrote:
> Hi Lada,
>
> On 12/19/2017 6:23 AM, Ladislav Lhotka wrote:
> > On Tue, 2017-12-19 at 06:20 -0500, Lou Berger wrote:
> > > Lada,
> > >
> > >
> > > On December 19, 2017 1:12:35 AM Ladislav Lhotka wrote:
> > >
> > > > On Mon, 2017-12-18 at 15
On 12/19/2017 7:36 AM, Ladislav Lhotka wrote:
> On Tue, 2017-12-19 at 06:43 -0500, Lou Berger wrote:
>> Hi Lada,
>>
>> On 12/19/2017 6:23 AM, Ladislav Lhotka wrote:
>>> On Tue, 2017-12-19 at 06:20 -0500, Lou Berger wrote:
Lada,
On December 19, 2017 1:12:35 AM Ladislav Lhotka
On Tue, 2017-12-19 at 07:49 -0500, Lou Berger wrote:
>
> On 12/19/2017 7:36 AM, Ladislav Lhotka wrote:
> > On Tue, 2017-12-19 at 06:43 -0500, Lou Berger wrote:
> > > Hi Lada,
> > >
> > > On 12/19/2017 6:23 AM, Ladislav Lhotka wrote:
> > > > On Tue, 2017-12-19 at 06:20 -0500, Lou Berger 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 Tree Diagrams
Authors : Martin Bjorklund
Lou Berger
Filename:
Hi,
This version changes the intended status to BCP, and adds the "-u"
notation for non-expanded uses statements.
We believe this draft is now ready for WGLC.
[FYI - I have added an option --tree-no-expand-uses to pyang, which
uses this new notation.]
/martin
internet-dra...@ietf.org wrote:
During the discussions of TE tunnel and topology models, we have found that
it is desirable to have the capability of augmenting a grouping.
In our case, there are multiple technology specific models augmenting a
base generic model. In the base model, some groupings are used multiple
times, and ea
FYI - note this version does not include a reference to a wiki, as
discussed at IETF100, based on the on-list discussion.
Lou
(as co-author)
On 12/19/2017 9:34 AM, Martin Bjorklund wrote:
> Hi,
>
> This version changes the intended status to BCP, and adds the "-u"
> notation for non-expanded uses
+1
Very much needed capability
Regards,
Jeff
> On Dec 19, 2017, at 08:45, Xufeng Liu wrote:
>
> During the discussions of TE tunnel and topology models, we have found that
> it is desirable to have the capability of augmenting a grouping.
>
> In our case, there are multiple technology specif
+1
I would like to see such a capability as well. As mentioned, specifically when
groupings are used in multiple places, augmentation becomes really unwieldy
without an option to simply augment the grouping instead. It also gets harder
to read; to some degree it negates the benefits from ntro
Authors, Contributors, WG,
As part of the preparation for WG Last Call:
Are you aware of any IPR that applies to drafts identified above?
Please state either:
"No, I'm not aware of any IPR that applies to this draft"
or
"Yes, I'm aware of IPR that applies to this draft"
If so, has this IPR bee
The current approach may be verbose but it protects users of groupings
from unwanted and uncontrolled side effects. Augmenting a grouping as
suggested affects _all_ uses of a grouping; this can be tricky in
situations where groupings are widely used.
/js
On Tue, Dec 19, 2017 at 11:45:06AM -0500,
IMHO it would be worth a try. If you wanted to only augment _some_ uses of a
grouping, you could still do the same as today. Also, I would expect
augmentations to only affect servers that support the module defining the
augmentation. If verbosity were not an issue, why were groupings introduc
Hi,
I do not want YANG to have augment for groupings because there is
no way to control all possible uses-stmts and make sure the augmentation
is only used where intended. This seems no different than OO code.
A new class name is required for the derived class. In YANG a new grouping
is required
joel jaeggli wrote:
> Authors, Contributors, WG,
>
> As part of the preparation for WG Last Call:
>
> Are you aware of any IPR that applies to drafts identified above?
No, I'm not aware of any IPR that applies to this draft
/martin
>
> Please state either:
>
> "No, I'm not aware of any IP
The question is not why we have groupings, the question is why
augmentations are restricted to schema node identifiers. I provided an
answer for the later, namely explicit control of augmentation effects.
It is of course OK to disagree with the design. I am just trying to
explain that this was an
Hi Andy,
Andy Bierman wrote:
> Hi,
>
> I have reviewed draft-07 and my previous comments about NMDA have been
> addressed.
>
> This might be the most important sentence in the draft:
>
> sec. 5.3
>
>The datastore schema for MUST be a superset of the
>combined datastore schema used in
Hi Lou,
Lou Berger wrote:
> Hi,
> These comments are based on my Shepherd review of this document and
> should be addressed as part of addressing any LC comments:
>
> 1) Considering the recent discussion on Library made me consider the
> general case of a module that is composed entirely o
On Tue, Dec 19, 2017 at 12:31 PM, Martin Bjorklund wrote:
> Hi Lou,
>
> Lou Berger wrote:
> > Hi,
> > These comments are based on my Shepherd review of this document and
> > should be addressed as part of addressing any LC comments:
> >
> > 1) Considering the recent discussion on Library m
On Tue, Dec 19, 2017 at 12:41:28PM -0800, Andy Bierman wrote:
> On Tue, Dec 19, 2017 at 12:31 PM, Martin Bjorklund wrote:
>
> > Hi Lou,
> >
> > Lou Berger wrote:
> > > Hi,
> > > These comments are based on my Shepherd review of this document and
> > > should be addressed as part of address
Joel Jaeggli has requested publication of draft-ietf-netmod-rfc7223bis-01 as
Proposed Standard on behalf of the NETMOD working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-netmod-rfc7223bis/
___
netmod maili
Joel Jaeggli has requested publication of draft-ietf-netmod-rfc7277bis-01 as
Proposed Standard on behalf of the NETMOD working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-netmod-rfc7277bis/
___
netmod maili
The IESG has received a request from the Network Modeling WG (netmod) to
consider the following document: - 'A YANG Data Model for IP Management'
as Proposed Standard
The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive co
The IESG has received a request from the Network Modeling WG (netmod) to
consider the following document: - 'A YANG Data Model for Interface
Management'
as Proposed Standard
The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substan
29 matches
Mail list logo
