Dear all,
Based on all the comments we received during the WG Last Call process, we've
updated the document to version 6.
We believe all the LC comments are resolved and the consensus is reflected in
this new revision.
Many thanks to Martin, Tal, Opher, Alex, John and many others who had
On Thu, Oct 26, 2017 at 07:03:11PM -0400, Lou Berger wrote:
>
>As tree diagrams are intended to provide a simplified view of a
>module, diagrams longer than a page should generally be avoided. If
>the complete tree diagram for a module becomes too long, the diagram
>can be split
On 10/26/2017 6:17 PM, Juergen Schoenwaelder wrote:
> On Thu, Oct 26, 2017 at 01:32:45PM -0400, Lou Berger wrote:
>
>>> But what practical advice can we give them?
>> we added section 3.2 covering Long Diagrams in general, and due to this
>> draft we added:
>>
>>When long diagrams are
Resending as I previously sent this to i-d-announces by mistake and it appears
the whole message was rejected (i.e. it didn't get sent to netmod either)
Hi Xiaojian,
* The published module ietf-ip (RFC 7277) overlaps the data being provided in
this module.
Especially
Hi Xiaojian,
* The published module ietf-ip (RFC 7277) overlaps the data being provided in
this module.
Especially your /arp/arp-tables and /arp/arp-static-tables seem to correspond
to /interfaces-state/interface/ipv4/neighbor and
/interfaces/interface/ipv4/neighbor from ietf-ip.
I think
On Thu, Oct 26, 2017 at 01:32:45PM -0400, Lou Berger wrote:
> > But what practical advice can we give them?
>
> we added section 3.2 covering Long Diagrams in general, and due to this
> draft we added:
>
>When long diagrams are included in a document, authors
>should consider whether
Hi -
On 10/26/2017 11:42 AM, Andy Bierman wrote:
On Thu, Oct 26, 2017 at 11:22 AM, Randy Presuhn
> wrote:
Hi -
On 10/26/2017 10:44 AM, Robert Wilton wrote:
Hi ,
Separating out the issue
Hi Martin,
I'm OK with that direction ('enabled' affects ifAdminStatus). I'm questioning
the other direction. I think a change in ifAdminStatus should be reflected in
'enabled'.
Rgds,
Jason
> -Original Message-
> From: Martin Bjorklund [mailto:m...@tail-f.com]
> Sent: Thursday,
"Sterne, Jason (Nokia - CA/Ottawa)" wrote:
> Hi all,
>
> The issue I'm raising isn't new to the 'bis' version of RFC7223, but
> I'm questioning whether we should consider changing something about it
> while we're in there.
>
> The 'enabled' leaf has this in the
On Thu, Oct 26, 2017 at 11:22 AM, Randy Presuhn <
randy_pres...@alumni.stanford.edu> wrote:
> Hi -
>
> On 10/26/2017 10:44 AM, Robert Wilton wrote:
>
>> Hi ,
>>
>> Separating out the issue regarding which datastore action and RPC apply
>> to, we propose the following NEW text to the datastores
Indeed. There is a lot of grouping expansion occurring in some of your drafts.
K. // contributor
I would find an option to show "uses" very useful, instead of always having to
expand groupings. Depending on the groupings and the amount of groupings reuse
it can cut down complexity of
Hi -
On 10/26/2017 10:44 AM, Robert Wilton wrote:
Hi ,
Separating out the issue regarding which datastore action and RPC apply
to, we propose the following NEW text to the datastores draft:
6.2 Invocation of Actions and RPC Operations
This section updates section 7.15. of RFC 7950.
Hi Tom,
On 10/26/2017 12:50 PM, t.petch wrote:
> Lou
>
> I like the advice that diagrams should be one page long but wonder how
> to apply that to those I see in routing WGs. I have just been looking
> at
>
> draft-ietf-teas-yang-te-topo-12
>
> where the diagram is 36 pages long - which may
On Thu, 2017-10-26 at 09:02 -0700, Andy Bierman wrote:
>
>
> On Tue, Oct 24, 2017 at 5:27 AM, Vladimir Vassilev
> wrote:
> > On 10/24/2017 03:42 AM, Andy Bierman wrote:
> >
> > >
> > >
> > > Although the instance-identifier is problematic, it is rarely used at
Hi,
A refined version of the proposed text is below (because "schema" isn't
defined):
On 26/10/2017 11:10, Martin Bjorklund wrote:
Andy Bierman wrote:
On Wed, Oct 25, 2017 at 12:49 PM, Martin Bjorklund wrote:
Andy Bierman wrote:
Hi ,
Separating out the issue regarding which datastore action and RPC apply
to, we propose the following NEW text to the datastores draft:
6.2 Invocation of Actions and RPC Operations
This section updates section 7.15. of RFC 7950.
In YANG data models, the "action" statement may appear
> On Oct 26, 2017, at 9:50 AM, t.petch wrote:
>
> Lou
>
> I like the advice that diagrams should be one page long but wonder how
> to apply that to those I see in routing WGs. I have just been looking
> at
>
> draft-ietf-teas-yang-te-topo-12
>
> where the diagram is 36
On 26/10/2017 17:50, t.petch wrote:
Lou
I like the advice that diagrams should be one page long but wonder how
to apply that to those I see in routing WGs. I have just been looking
at
draft-ietf-teas-yang-te-topo-12
where the diagram is 36 pages long - which may be one of the larger ones
Hi all,
The issue I'm raising isn't new to the 'bis' version of RFC7223, but I'm
questioning whether we should consider changing something about it while we're
in there.
The 'enabled' leaf has this in the description:
Changes in this leaf in the intended configuration are
Lou
I like the advice that diagrams should be one page long but wonder how
to apply that to those I see in routing WGs. I have just been looking
at
draft-ietf-teas-yang-te-topo-12
where the diagram is 36 pages long - which may be one of the larger ones
but by no means exceptional - and I
Andy Bierman writes:
>I think text() and node() are just filter tests.
>
> /foo/*[text()] would return all the child nodes of /foo that are leaf or
>leaf-list
>
>text() returns a boolean (0 or 1). Do not use it for value testing:
>
> /foo/*[text() =3D 'fred'] // wrong!
>
> /foo/*[. =3D
On Tue, Oct 24, 2017 at 5:27 AM, Vladimir Vassilev wrote:
> On 10/24/2017 03:42 AM, Andy Bierman wrote:
>
>
>>
>> Although the instance-identifier is problematic, it is rarely used at all,
>> let alone using it as a list key.
>>
> It is used as a key in
Andy Bierman wrote:
> On Wed, Oct 25, 2017 at 12:49 PM, Martin Bjorklund wrote:
>
> > Andy Bierman wrote:
> > > I think NMDA is creating much more complexity and disruption than is
> > > required.
> > > The original issue was the
"Acee Lindem (acee)" wrote:
> Hi Mahesh,
>
> On 10/25/17, 9:22 PM, "Mahesh Jethanandani"
> wrote:
>
> >Acee,
> >
> >Thanks for reviewing the draft.
> >
> >> On Oct 25, 2017, at 6:21 AM, Acee Lindem (acee) wrote:
> >>
> >> Hi Kent,
Hi Mahesh,
On 10/25/17, 9:22 PM, "Mahesh Jethanandani"
wrote:
>Acee,
>
>Thanks for reviewing the draft.
>
>> On Oct 25, 2017, at 6:21 AM, Acee Lindem (acee) wrote:
>>
>> Hi Kent, Mahesh, et al,
>>
>> I have read the draft and support publication. I
Hi all,
The ARP YANG module defined in this document has common properties that need to
be configured.
It provides freedom for service providers to adapt this data model to different
product implementations.
Please have a look and provide comments on the list.
Thanks,
Xiaojian
A new
26 matches
Mail list logo