On Wed, May 20, 2015 at 11:27 PM, Juergen Schoenwaelder
j.schoenwael...@jacobs-university.de wrote:
On Wed, May 20, 2015 at 10:51:28AM -0700, Andy Bierman wrote:
The solution is not intuitive at all. The implications of cherry-picking
YANG statements from various revisions of a YANG module
On Mon, Jun 8, 2015 at 11:49 AM, Ladislav Lhotka lho...@nic.cz wrote:
Andy Bierman a...@yumaworks.com writes:
On Mon, Jun 8, 2015 at 8:39 AM, Kent Watsen kwat...@juniper.net wrote:
I think the two leafs are coupled through the path statement and so the
values of both should conform
On Thu, Jun 25, 2015 at 1:14 AM, Martin Bjorklund m...@tail-f.com wrote:
Andy Bierman a...@yumaworks.com wrote:
On Wed, Jun 24, 2015 at 2:14 PM, Martin Bjorklund m...@tail-f.com
wrote:
Hi,
I am preparing a new version of draft-ietf-netmod-rfc6020bis in order
to address Y45-04
On Thu, Jun 25, 2015 at 12:40 AM, Juergen Schoenwaelder
j.schoenwael...@jacobs-university.de wrote:
On Thu, Jun 25, 2015 at 12:29:13AM -0700, Anees Shaikh wrote:
hi Juergen,
I don't believe it involves tracking anything beyond what you would need
to
track however the model is
On Thu, Jun 25, 2015 at 9:35 AM, Juergen Schoenwaelder
j.schoenwael...@jacobs-university.de wrote:
On Wed, Jun 24, 2015 at 06:24:25AM -0700, Andy Bierman wrote:
I prepared 1 slide (based on Kent's slide).
I am trying to understand the types of data
and how they are identified in YANG
On Wed, Jun 24, 2015 at 2:14 PM, Martin Bjorklund m...@tail-f.com wrote:
Hi,
I am preparing a new version of draft-ietf-netmod-rfc6020bis in order
to address Y45-04. Note that YANG 1.1 uses the module
ietf-yang-library from draft-ietf-netconf-yang-library (hence the
crossposting).
[BTW,
Hi,
I prepared 1 slide (based on Kent's slide).
I am trying to understand the types of data
and how they are identified in YANG and conceptually
separated for protocol access.
Andy
extended_datastores.pdf
Description: Adobe PDF document
___
netmod
-identifier in all 3 datastores
Andy
On Wed, Jun 24, 2015 at 6:28 AM, Joel M. Halpern j...@joelhalpern.com
wrote:
The separations and effects shown there match my understanding.
Thank you,
Joel
On 6/24/15 9:24 AM, Andy Bierman wrote:
Hi,
I prepared 1 slide (based on Kent's slide).
I
On Sat, Jun 27, 2015 at 1:19 AM, Martin Bjorklund m...@tail-f.com wrote:
Andy Bierman a...@yumaworks.com wrote:
On Fri, Jun 26, 2015 at 1:59 AM, Martin Bjorklund m...@tail-f.com
wrote:
Andy Bierman a...@yumaworks.com wrote:
On Wed, Jun 24, 2015 at 2:14 PM, Martin Bjorklund m...@tail
Hi,
Can the NETMOD chairs remember to post the meeting info
before the meeting?
Can't find it so please post again
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
On Wed, Jul 1, 2015 at 6:01 AM, Ladislav Lhotka lho...@nic.cz wrote:
On 01 Jul 2015, at 14:33, Juergen Schoenwaelder
j.schoenwael...@jacobs-university.de wrote:
On Wed, Jul 01, 2015 at 02:03:15PM +0200, Ladislav Lhotka wrote:
On 01 Jul 2015, at 09:21, Juergen Schoenwaelder
On Wed, Jul 1, 2015 at 7:41 AM, Benoit Claise bcla...@cisco.com wrote:
Hi Lada,
- In the introduction, you mention:
Typical use cases are:
o Deactivating a subtree in a configuration datastore while
keeping
the data in place.
o Complementing data model
On Tue, Jun 30, 2015 at 1:44 AM, Martin Bjorklund m...@tail-f.com wrote:
Hi,
Here's a short summary, and then some questions for the WG.
The ietf-yang-library module is designed to serve two purposes:
1. A protocol-independent advertisement mechanism for YANG 1.1
modules.
2.
On Sun, Jul 5, 2015 at 11:57 PM, Juergen Schoenwaelder
j.schoenwael...@jacobs-university.de wrote:
On Fri, Jul 03, 2015 at 02:12:30PM -0700, Andy Bierman wrote:
I propose this text in the conformance leaf:
For import statements that do not specify a revision
Hi,
I submitted a new draft for defining YANG packages.
http://www.ietf.org/id/draft-bierman-netmod-yang-package-00.txt
IMO this could be useful for organizing YANG modules.
It may also be applicable for CoMI, by allowing
a tiny number of packages to be advertised to the client,
instead of a
.
In order for a union to work correctly in all encodings
it must be specified so the types are ordered from most specific
to most generic. This is not any rule in YANG, but
maybe it should be a rule (YANG guidelines draft?)
Andy
On Sun, Jun 28, 2015 at 12:10 PM, Andy Bierman a...@yumaworks.com
On Wed, Jul 1, 2015 at 11:33 PM, Ladislav Lhotka lho...@nic.cz wrote:
Andy Bierman a...@yumaworks.com writes:
I agree with Juergen that the implementation of YANG constraints
on a datastore is not XML-specific. The text refers to data nodes
not XML elements. It is quite possible
if the imported module is also an implemented module.
No other modules will be listed.
Andy
On Tue, Jun 30, 2015 at 11:10 AM, Andy Bierman a...@yumaworks.com wrote:
On Tue, Jun 30, 2015 at 5:45 AM, Juergen Schoenwaelder
j.schoenwael...@jacobs-university.de wrote:
Writing as technical contributor
On Thu, May 21, 2015 at 10:38 AM, Per Hedeland p...@tail-f.com wrote:
On 2015-05-21 19:14, Andy Bierman wrote:
On Thu, May 21, 2015 at 7:37 AM, Ladislav Lhotka lho...@nic.cz wrote:
RFC 6020 also states that must and when expessions are XPath 1.0, and we
are moving away from it. This is IMO
On Thu, May 21, 2015 at 1:36 PM, Martin Bjorklund m...@tail-f.com wrote:
Andy,
I don't think the implementation burden on the server is that heavy.
A YANG 1.0 compliant server today supports:
leaf a in module A of type foo from foo@2001-01-01
leaf b in module B of type foo from
On Thu, May 21, 2015 at 5:40 AM, Ladislav Lhotka lho...@nic.cz wrote:
Kent Watsen kwat...@juniper.net writes:
You seem to be suggesting that Kent is an uninformed observer and Y45-04
is actually really easy to understand. Neither is true.
I appreciate Andy's vote of confidence, but the
On Thu, May 21, 2015 at 7:37 AM, Ladislav Lhotka lho...@nic.cz wrote:
On 21 May 2015, at 16:21, Andy Bierman a...@yumaworks.com wrote:
On Thu, May 21, 2015 at 5:40 AM, Ladislav Lhotka lho...@nic.cz wrote:
Kent Watsen kwat...@juniper.net writes:
You seem to be suggesting that Kent
On Mon, Jul 6, 2015 at 8:04 AM, Juergen Schoenwaelder
j.schoenwael...@jacobs-university.de wrote:
On Mon, Jul 06, 2015 at 07:59:29AM -0700, Andy Bierman wrote:
On Mon, Jul 6, 2015 at 12:45 AM, Juergen Schoenwaelder
j.schoenwael...@jacobs-university.de wrote:
On Mon, Jul 06, 2015 at 12
On Mon, Jul 6, 2015 at 12:45 AM, Juergen Schoenwaelder
j.schoenwael...@jacobs-university.de wrote:
On Mon, Jul 06, 2015 at 12:39:21AM -0700, Andy Bierman wrote:
On Sun, Jul 5, 2015 at 11:57 PM, Juergen Schoenwaelder
j.schoenwael...@jacobs-university.de wrote:
On Fri, Jul 03, 2015
On Mon, Aug 3, 2015 at 2:25 AM, Juergen Schoenwaelder
j.schoenwael...@jacobs-university.de wrote:
On Mon, Aug 03, 2015 at 11:06:41AM +0200, Jernej Tuljak wrote:
Juergen Schoenwaelder je 3.8.2015 ob 10:18 napisal:
Any description statement in principle can do this. We trust that sane
data
On Mon, Aug 3, 2015 at 9:01 AM, t.petch ie...@btconnect.com wrote:
- Original Message -
From: Andy Bierman a...@yumaworks.com
To: t.petch ie...@btconnect.com
Cc: NETMOD Working Group netmod@ietf.org
Sent: Monday, August 03, 2015 4:10 PM
On Mon, Aug 3, 2015 at 7:48 AM, t.petch ie
On Tue, Aug 11, 2015 at 12:12 AM, Juergen Schoenwaelder
j.schoenwael...@jacobs-university.de wrote:
On Fri, Aug 07, 2015 at 03:21:48PM -0400, Rob Shakir wrote:
Juergen Schoenwaelder wrote:
But you are right, it is not just the path that is needed to identify
data residing in
On Tue, Aug 18, 2015 at 9:59 AM, Robert Wilton rwil...@cisco.com wrote:
On 11/08/2015 08:38, Ladislav Lhotka wrote:
On 10 Aug 2015, at 22:15, Andy Bierman a...@yumaworks.com wrote:
On Mon, Aug 10, 2015 at 12:34 PM, Acee Lindem (acee) a...@cisco.com
wrote:
I think there is agreement
On Fri, Aug 21, 2015 at 6:01 AM, Martin Bjorklund m...@tail-f.com wrote:
Robert Wilton rwil...@cisco.com wrote:
Hi Martin,
On 20/08/2015 09:15, Martin Bjorklund wrote:
Andy Bierman a...@yumaworks.com wrote:
On Wed, Aug 19, 2015 at 4:25 AM, Martin Bjorklund m...@tail-f.com
wrote
On Mon, Aug 24, 2015 at 10:53 AM, Ladislav Lhotka lho...@nic.cz wrote:
On 24 Aug 2015, at 18:42, Andy Bierman a...@yumaworks.com wrote:
On Mon, Aug 24, 2015 at 9:35 AM, Ladislav Lhotka lho...@nic.cz wrote:
Ladislav Lhotka lho...@nic.cz writes:
Hi,
2. The rogue vendor can
Hi,
I assume this draft is what we should be reviewing and not
the obsolete openconfig draft?
https://tools.ietf.org/html/draft-rtgyangdt-rtgwg-device-model-00
Q1) scope
sec 2:
The model organization can itself be thought of as a meta-model,
in that it describes the relationships
On Thu, Aug 20, 2015 at 7:58 AM, Nadeau Thomas tnad...@lucidvision.com
wrote:
On Aug 20, 2015:10:30 AM, at 10:30 AM, Ladislav Lhotka lho...@nic.cz
wrote:
On 20 Aug 2015, at 16:00, Nadeau Thomas tnad...@lucidvision.com
wrote:
.
o management protocols such as NETCONF or
On Wed, Aug 19, 2015 at 10:49 AM, Martin Bjorklund m...@tail-f.com wrote:
Andy Bierman a...@yumaworks.com wrote:
On Wed, Aug 19, 2015 at 5:49 AM, Martin Bjorklund m...@tail-f.com
wrote:
Hi,
[joining this discussion a bit late]
Ladislav Lhotka lho...@nic.cz wrote
On Mon, Jun 29, 2015 at 2:40 PM, Phil Shafer p...@juniper.net wrote:
Juergen Schoenwaelder writes:
And my understanding is that the list foo defined above will never
have an instance, correct? I assume decent compilers will continue to
create warnings when they can decide that a list will
On Tue, Jun 30, 2015 at 5:45 AM, Juergen Schoenwaelder
j.schoenwael...@jacobs-university.de wrote:
Writing as technical contributor...
On Tue, Jun 30, 2015 at 10:44:49AM +0200, Martin Bjorklund wrote:
Hi,
Here's a short summary, and then some questions for the WG.
The
On Tue, Jul 28, 2015 at 2:56 AM, Ladislav Lhotka lho...@nic.cz wrote:
On 28 Jul 2015, at 11:42, Martin Bjorklund m...@tail-f.com wrote:
Hi,
Andy Bierman a...@yumaworks.com wrote:
On Sun, Jul 26, 2015 at 12:16 AM, Juergen Schoenwaelder
j.schoenwael...@jacobs-university.de wrote
, Martin Bjorklund m...@tail-f.com wrote:
Andy Bierman a...@yumaworks.com wrote:
The real difference is that extensions can be ignored by all
YANG tools and real statements cannot be ignored.
Are you saying that a server that advertises both ietf-system and nacm
is free to ignore the nacm
On Mon, Aug 3, 2015 at 11:58 AM, Ladislav Lhotka lho...@nic.cz wrote:
On 03 Aug 2015, at 18:01, Andy Bierman a...@yumaworks.com wrote:
On Mon, Aug 3, 2015 at 7:48 AM, Ladislav Lhotka lho...@nic.cz wrote:
On 03 Aug 2015, at 16:41, Andy Bierman a...@yumaworks.com wrote
-
From:
Einar Nilsen-Nygaard (einarnn) eina...@cisco.com
To:
Andy Bierman a...@yumaworks.com
Cc:
NETMOD Working Group netmod@ietf.org
Sent:
Sat, 8 Aug 2015 11:10:15 +
Subject:
Re: [netmod] Y34 - root node
Andy,
I agree that there is a need for organization of models, but I
On Mon, Aug 10, 2015 at 4:24 AM, Ladislav Lhotka lho...@nic.cz wrote:
On 10 Aug 2015, at 12:17, Andy Bierman a...@yumaworks.com wrote:
Hi,
I am strongly against changing the contract on extensions.
They MAY be ignored by any YANG tool. Period.
That means they are far from mandatory
On Mon, Aug 10, 2015 at 9:37 AM, Ladislav Lhotka lho...@nic.cz wrote:
On 10 Aug 2015, at 17:32, Andy Bierman a...@yumaworks.com wrote:
On Mon, Aug 10, 2015 at 4:24 AM, Ladislav Lhotka lho...@nic.cz wrote:
On 10 Aug 2015, at 12:17, Andy Bierman a...@yumaworks.com wrote:
Hi
On Mon, Aug 10, 2015 at 10:01 AM, Ladislav Lhotka lho...@nic.cz wrote:
On 10 Aug 2015, at 18:46, Andy Bierman a...@yumaworks.com wrote:
On Mon, Aug 10, 2015 at 9:37 AM, Ladislav Lhotka lho...@nic.cz wrote:
On 10 Aug 2015, at 17:32, Andy Bierman a...@yumaworks.com wrote
very much like a dark art! It is not just the
individual modules, it is how to put them together to best manage a device
(let alone a system).
Jonathan
- Original Message -
From:
Einar Nilsen-Nygaard (einarnn) eina...@cisco.com
To:
Andy Bierman a...@yumaworks.com
Cc:
NETMOD
On Fri, Aug 14, 2015 at 4:32 PM, heasley h...@shrubbery.net wrote:
On Thu, Aug 13, 2015 at 12:43 PM, Ladislav Lhotka lho...@nic.cz wrote:
On 13 Aug 2015, at 21:31, Andy Bierman a...@yumaworks.com wrote:
Hi,
IMO this is issue is closed.
I see no reason to re-open
On Sat, Aug 15, 2015 at 10:10 AM, Ladislav Lhotka lho...@nic.cz wrote:
On 15 Aug 2015, at 18:00, Andy Bierman a...@yumaworks.com wrote:
Hi,
If you are using mandatory nodes in augment, it is because you expect
that all clients will know and implement both modules.
However YANG has
Hi,
I am strongly against changing the contract on extensions.
They MAY be ignored by any YANG tool. Period.
That means they are far from mandatory.
They are little more than a keyword and a description clause.
There are not even any rules or help determining
which extensions can appear as
On Thu, Aug 6, 2015 at 5:50 AM, Ladislav Lhotka lho...@nic.cz wrote:
On 06 Aug 2015, at 13:03, Andy Bierman a...@yumaworks.com wrote:
On Thu, Aug 6, 2015 at 12:43 AM, Ladislav Lhotka lho...@nic.cz wrote:
Andy Bierman a...@yumaworks.com writes:
On Mon, Aug 3, 2015 at 11:58 AM
On Sun, Jul 26, 2015 at 12:22 AM, Juergen Schoenwaelder
j.schoenwael...@jacobs-university.de wrote:
On Sat, Jul 25, 2015 at 03:15:45PM -0700, Andy Bierman wrote:
On Sat, Jul 25, 2015 at 1:25 AM, Juergen Schoenwaelder
j.schoenwael...@jacobs-university.de wrote:
This is the summary
or symlink data models,
please do so in a separate thread. (And no, we do not accept new
issues for YANG 1.1 either at this point in time.)
/js
On Mon, Jul 20, 2015 at 07:42:49PM +0200, Ladislav Lhotka wrote:
On 20 Jul 2015, at 19:29, Andy Bierman a...@yumaworks.com wrote
guidelines on XPath to avoid.
Basically any Xpath that selects nodes by specific names can be
relocated automatically. Nodes selected by function, wildcard, axis, etc.
will not be so easy.
Thanks,
Lou
Andy
On July 26, 2015 4:41:32 PM Andy Bierman a...@yumaworks.com wrote:
Hi Acee,
I
...
On Sun, Jul 26, 2015 at 4:47 AM, Juergen Schoenwaelder
j.schoenwael...@jacobs-university.de wrote:
On Sun, Jul 26, 2015 at 04:17:26AM -0700, Andy Bierman wrote:
On Sun, Jul 26, 2015 at 12:16 AM, Juergen Schoenwaelder
j.schoenwael...@jacobs-university.de wrote:
On Sat, Jul 25, 2015 at 05
On Sat, Jul 25, 2015 at 1:25 AM, Juergen Schoenwaelder
j.schoenwael...@jacobs-university.de wrote:
This is the summary of the discussion of YANG 1.1 issue Y60 at the
IETF 93 meeting in Prague:
- It is OK for a YANG 1.1 module to import a YANG 1.0 module (which
will of course be
Hi,
I would like to open another issue for YANG 1.1,
because I don't want to have 1.1 and then 1.2 right away.
The NETMOD WG should evaluate the different ways to
support ephemeral state, based on Jeff's draft.
Andy
___
netmod mailing list
On Mon, Aug 24, 2015 at 12:01 PM, Martin Bjorklund m...@tail-f.com wrote:
Ladislav Lhotka lho...@nic.cz wrote:
On 24 Aug 2015, at 20:17, Andy Bierman a...@yumaworks.com wrote:
YANG does not provide any mechanism to REQUIRE modules A and B
to both be implemented on a server. You may
On Sat, Oct 24, 2015 at 6:07 AM, Martin Bjorklund wrote:
> Juergen Schoenwaelder wrote:
> > On Fri, Oct 23, 2015 at 10:35:48AM +0200, Ladislav Lhotka wrote:
> > > Martin Bjorklund writes:
> > >
> > > > auto-deletion in
On Fri, Oct 23, 2015 at 1:58 AM, Martin Bjorklund wrote:
> Ladislav Lhotka wrote:
> > Martin Bjorklund writes:
> >
> > > Balazs Lengyel wrote:
> > >> Hello Lada,
> > >> The issue is what is "too much protocol
On Fri, Oct 23, 2015 at 9:15 AM, Randy Presuhn wrote:
> Hi -
>
> >From: Martin Bjorklund
> >Sent: Oct 23, 2015 12:24 AM
> >To: randy_pres...@mindspring.com
> >Cc: netmod@ietf.org
> >Subject: Re: [netmod] Yang 1.0/1.1 ABNF Grammar: the rule ...>
>
On Wed, Oct 21, 2015 at 4:45 AM, Balazs Lengyel wrote:
> I would love to get rid of the autodelete feature. It really complicates
> things.
>
So how would when-stmt work?
It would be an error if a false when-stmt ever occurred?
leaf X { type int32; }
leaf Y
he YANG definition.
>
> The whole idea behind model driven OAM is that we have one model that
> works (mostly) the same way on all interfaces. The more differences we have
> the less usable the product, the more difficult to implement.
> regards Balazs
>
> On 2015-10-21 15:07, Andy
On Wed, Oct 21, 2015 at 11:15 AM, Martin Bjorklund <m...@tail-f.com> wrote:
> Andy Bierman <a...@yumaworks.com> wrote:
>
> [...]
>
> > But the "when-stmt" never causes an error for application within
> > a datastore.
> >
> &g
Hi,
Here are my review comments on YANG 1.1.
IMO the document is almost ready for publication.
I plan to implement YANG 1.1 in YumaPro tools soon.
Andy
Review of draft-ietf-netmod-rfc6020bis-08.txt
Andy Bierman
2015-10-27
Sec 1:
- text about 'proposed to be used' should be 'going to be used
you
> please give a sense of when they might be ready?
>
> —Tom
>
> Sent from my Apple ][
>
>
>
> On Oct 28, 2015:12:22 PM, at 12:22 PM, Andy Bierman <a...@yumaworks.com>
> wrote:
>
>
>
> On Wed, Oct 28, 2015 at 4:55 AM, Nadeau Thomas <tnad...@lu
On Wed, Oct 28, 2015 at 4:55 AM, Nadeau Thomas <tnad...@lucidvision.com>
wrote:
>
>
> > On Oct 27, 2015:1:51 PM, at 1:51 PM, Andy Bierman <a...@yumaworks.com>
> wrote:
> >
> > Hi,
> >
> > Here are my review comments on YANG 1.1.
&
On Mon, Oct 26, 2015 at 4:55 AM, Martin Bjorklund wrote:
> Juergen Schoenwaelder wrote:
> > On Sat, Oct 24, 2015 at 03:07:41PM +0200, Martin Bjorklund wrote:
> > > Juergen Schoenwaelder wrote:
> > > >
On Mon, Oct 26, 2015 at 8:57 AM, Ladislav Lhotka <lho...@nic.cz> wrote:
>
> > On 26 Oct 2015, at 16:10, Andy Bierman <a...@yumaworks.com> wrote:
> >
> >
> >
> > On Mon, Oct 26, 2015 at 4:55 AM, Martin Bjorklund <m...@tail-f.com>
> wr
On Sun, Oct 25, 2015 at 6:58 AM, Martin Bjorklund <m...@tail-f.com> wrote:
> Andy Bierman <a...@yumaworks.com> wrote:
> > On Sat, Oct 24, 2015 at 6:07 AM, Martin Bjorklund <m...@tail-f.com>
> wrote:
> >
> > > Juergen Schoenwaelder <j.schoenwael...@
On Wed, Oct 21, 2015 at 6:22 AM, Ladislav Lhotka <lho...@nic.cz> wrote:
>
> > On 21 Oct 2015, at 15:07, Andy Bierman <a...@yumaworks.com> wrote:
> >
> >
> >
> > On Wed, Oct 21, 2015 at 5:46 AM, Ladislav Lhotka <lho...@nic.cz> wrot
On Wed, Oct 21, 2015 at 5:46 AM, Ladislav Lhotka <lho...@nic.cz> wrote:
>
> > On 21 Oct 2015, at 14:33, Andy Bierman <a...@yumaworks.com> wrote:
> >
> > Hi,
> >
> > IMO we do not need lots of rules for when-stmt.
> > They are harder
On Wed, Nov 11, 2015 at 7:32 AM, Juergen Schoenwaelder <
j.schoenwael...@jacobs-university.de> wrote:
> On Wed, Nov 11, 2015 at 03:14:13PM +0100, Ladislav Lhotka wrote:
> >
> > > On 11 Nov 2015, at 14:59, Juergen Schoenwaelder <
> j.schoenwael...@jacobs-university.de> wrote:
> > >
> > > On Wed,
On Mon, Nov 9, 2015 at 1:11 PM, Martin Bjorklund <m...@tail-f.com> wrote:
> Andy Bierman <a...@yumaworks.com> wrote:
> > On Mon, Nov 9, 2015 at 10:38 AM, Martin Bjorklund <m...@tail-f.com>
> wrote:
> >
> > > Hi,
> > >
> > >
Hi,
I am not in favor of anything XML or JSON specific in YANG.
In reality, nobody uses anyxml as a configuration data node,
so an improper roundtrip translation from JSON to XML
is not going to happen.
Encoding anyxml as a string is not going to happen either.
Not sure what the difference
On Mon, Nov 9, 2015 at 11:55 AM, Randy Presuhn wrote:
> Hi -
>
> >From: Martin Bjorklund
> >Sent: Nov 9, 2015 10:27 AM
> >To: a...@yumaworks.com
> >Cc: netmod@ietf.org
> >Subject: Re: [netmod] yang 1.1 last call comment resolution
> ...
> >> > -
On Mon, Nov 9, 2015 at 10:38 AM, Martin Bjorklund wrote:
> Hi,
>
> I implemented most of the 1.1 features that affect the compiler in
> pyang on the flight back from Yokohama. (if you have 1.1 modules, I'd
> appreciate if you could try it out).
>
> In doing this, I realized
On Wed, Nov 11, 2015 at 11:51 PM, Juergen Schoenwaelder <
j.schoenwael...@jacobs-university.de> wrote:
> On Thu, Nov 12, 2015 at 08:10:51AM +0100, Ladislav Lhotka wrote:
> > Juergen Schoenwaelder writes:
> >
> > > On Wed, Nov 11, 2015 at 03:14:13PM +0100,
On Mon, Nov 16, 2015 at 3:55 AM, Juergen Schoenwaelder <
j.schoenwael...@jacobs-university.de> wrote:
> On Sat, Nov 14, 2015 at 09:05:00AM -0800, Andy Bierman wrote:
> >
> > YANG 1.1 is going to take 2 more years if we slowly revisit every issue.
> > I thought the whole
ect
use of RFC 2119 terminology. If MUST is used, that is the only option.
You also need to explain exactly what interoperability is lost if the MUST
is not followed. (e.g., mixed mode XML will not be translated properly to
JSON).
Andy
Lada
>
> >
> > Rob
> >
> >
&
oes not retain
> modeling context nor encoding details of the data being transported --
> rendering reliable automated translation impossible.
>
> Bye,
> Robert
>
> On 11/10/2015 03:19 AM, Andy Bierman wrote:
>
> Hi,
>
> I am not in favor of anything XML or JSON
On Sun, Nov 1, 2015 at 8:46 PM, Jeffrey (Zhaohui) Zhang
wrote:
> Hi,
>
> Earlier today Mach and I were asking Lada if we could have a config list
> w/o keys for our use case and he pointed us to this thread.
>
> This is exactly what we need. For some lists we don't need to
Hi,
I started a separate thread for this issue.
The current YANG 1.1 text is incomplete wrt/ default-stmt.
leaf broken {
type enumeration {
enum option1 {
if-feature option1;
}
enum option2 {
if-feature option2;
}
enum option3;
Hi,
Why is this WG discussing issues that have been declared DEAD for
various reasons? Optional keys break old clients, remember?
There was not enough interest in adding these features.
Andy
On Sun, Nov 1, 2015 at 6:51 AM, Juergen Schoenwaelder <
j.schoenwael...@jacobs-university.de> wrote:
On Sun, Nov 1, 2015 at 5:12 AM, Ladislav Lhotka wrote:
> Martin Bjorklund writes:
> >
> >> Sec. 1.1
> >>o Made "when" and "if-feature" illegal on list keys, unless the
> >> parent is also conditional, and the condition matches the parent's
> >>
On Fri, Oct 30, 2015 at 8:45 AM, Martin Bjorklund wrote:
> Hi Andy,
>
> ...
>
> > - Should 'may' be 'MAY'?
>
> Actually, since the enitire section 4 is not marked as:
>
>This non-normative section is intended to give a high-level overview
>of YANG to first-time
On Sun, Nov 1, 2015 at 4:20 PM, Ladislav Lhotka <lho...@nic.cz> wrote:
>
> > On 02 Nov 2015, at 02:16, Andy Bierman <a...@yumaworks.com> wrote:
> >
> > Hi,
> >
> > I started a separate thread for this issue.
> > The current YANG 1.1 text is
; total or partial
> disclosure, reproduction, or dissemination) by persons other than the
> intended
> recipient(s) is prohibited. If you receive this e-mail in error, please
> notify the sender by
> phone or email immediately and delete it!
>
> *发件人:* netmod [mailto:n
Hi,
I asked about this text on page 156:
In statements that have any data definition statements as
substatements, those data definition substatements MUST NOT be
reordered.
I asked why this new rule was added.
I do not see why it is needed, or how it can be enforced.
If I add a new
On Sun, Nov 1, 2015 at 4:48 PM, Ladislav Lhotka <lho...@nic.cz> wrote:
>
> > On 02 Nov 2015, at 09:40, Andy Bierman <a...@yumaworks.com> wrote:
> >
> >
> >
> > On Sun, Nov 1, 2015 at 4:20 PM, Ladislav Lhotka <lho...@nic.cz> wrot
On Thu, Nov 5, 2015 at 4:50 PM, Martin Bjorklund <m...@tail-f.com> wrote:
> Hi,
>
> Andy Bierman <a...@yumaworks.com> wrote:
> > Hi,
> >
> > I asked about this text on page 156:
> >
> >
> >In statements that have any data definition
On Fri, Nov 6, 2015 at 1:37 PM, Juergen Schoenwaelder <
j.schoenwael...@jacobs-university.de> wrote:
> On Fri, Nov 06, 2015 at 01:24:14PM -0800, Andy Bierman wrote:
> >
> > IMO auto-deletion should not be changed.
> > It works fine and the only issue that has ever c
On Wed, Oct 14, 2015 at 8:24 AM, David Reid wrote:
> > There seems to be 3 solutions, none of which are very good:
> >
> > 1) document everything: return lots of
> > instance-level conformance information and expect the client
> > to sort it out
> >
> > 2) Advertise the newer
On Fri, Oct 16, 2015 at 12:49 PM, Martin Bjorklund <m...@tail-f.com> wrote:
> Andy Bierman <a...@yumaworks.com> wrote:
> > Hi,
> >
> > I find all this fretting over when-stmt corner-cases to be a waste of
> time.
> > I certainly have no intention of sp
ing violated?
Andy
On Thu, Oct 15, 2015 at 1:00 AM, Balazs Lengyel <balazs.leng...@ericsson.com
> wrote:
> See below, Balazs
>
> On 2015-10-14 23:06, Andy Bierman wrote:
>
>
>
> On Wed, Oct 14, 2015 at 1:26 PM, Martin Bjorklund < <m...@tail-f.com>
> m...@tail
On Wed, Oct 14, 2015 at 12:25 PM, Martin Bjorklund wrote:
> Balazs Lengyel wrote:
> > Hello Martin,
> > I agree that A1 is what follows the spirit of YANG, but then IMHO you
> > should change/correct 8.2.1 in YANG because that implies A2 and error.
On Wed, Oct 14, 2015 at 11:00 AM, Kent Watsen wrote:
>
> Thank you Robert for bringing the discussion back to the github issues.
>
> Robert writes:
>
> > In particular:
> >- does it include support for templating (as per
> openconfig-netmod-opstate-01 section 7.3.)?
> >
On Thu, Oct 15, 2015 at 4:53 AM, Martin Bjorklund <m...@tail-f.com> wrote:
> Andy Bierman <a...@yumaworks.com> wrote:
> > Hi,
> >
> > You are incorrect.
> >
> > Within the PAYLOAD (as this section describes), there is no when-stmt
> > for
he when defined in a definition of an rpc or
> action.
> regards Balazs
>
> On 2015-10-15 17:02, Andy Bierman wrote:
>
>
>
> On Thu, Oct 15, 2015 at 4:53 AM, Martin Bjorklund < <m...@tail-f.com>
> m...@tail-f.com> wrote:
>
>> Andy Bierman &
Hi,
I find all this fretting over when-stmt corner-cases to be a waste of time.
I certainly have no intention of spending 100s of hours coding for
corner-cases
that have no operational value whatsoever. When-stmt has always been full
of problems that exist on paper but not in real servers.
On Fri, Oct 16, 2015 at 5:23 AM, Martin Bjorklund wrote:
> Robert Wilton wrote:
> > Hi Kent,
> >
> > Here is my attempt at word smithing section 3:
> >
> > The old D and E have been merged together (now labelled as C). A new
> > D has been added to try and
On Tue, Oct 20, 2015 at 1:09 AM, Martin Bjorklund <m...@tail-f.com> wrote:
> Ladislav Lhotka <lho...@nic.cz> wrote:
> >
> > > On 19 Oct 2015, at 21:22, Andy Bierman <a...@yumaworks.com> wrote:
> > >
> > >
> > >
> > > On
On Sun, Oct 18, 2015 at 1:31 AM, Juergen Schoenwaelder <
j.schoenwael...@jacobs-university.de> wrote:
> On Sat, Oct 17, 2015 at 07:49:06PM -0700, Randy Presuhn wrote:
> > Hi -
> >
> > > From: Andy Bierman
> > > Sent: Oct 17, 2015 10:42 AM
> > ...
&
On Sun, Oct 18, 2015 at 5:17 AM, Martin Bjorklund <m...@tail-f.com> wrote:
> Juergen Schoenwaelder <j.schoenwael...@jacobs-university.de> wrote:
> > On Sun, Oct 18, 2015 at 01:50:12AM -0700, Andy Bierman wrote:
> > > On Sun, Oct 18, 2015 at 1:31 AM, Juergen Scho
1 - 100 of 1099 matches
Mail list logo