o support old clients.
> >
> > With a MAJOR update in a semver world, it means that the old nodes are
> > removed (or rather, possibly, that the old nodes have new syntax
> > and/or semantics).
> >
> >
> >
>
>
--
Ladislav Lhotka
Head, CZ.NIC La
On Wed, 2017-11-15 at 05:27 -0500, Joe Clarke wrote:
> On 11/15/17 05:06, Ladislav Lhotka wrote:
> > > I suppose my gut reaction to Lou's question as to whether a server
> > > should support multiple versions was, "no." A client may have multiple
> >
ic version number
>>> changed. Or the semantic version number indicates only minor changes
>>> that sill break your client.
>>>
>>>>CH 2.3)
>>>>As we need to create a new Yang Module (YAM) even for the smallest
>>>>incompatible modification, this increases the number of modules.
>>>
>>> So it seems to boil down to the question whether foo and foo2 is
>>> significantly more expensive than foo { semver 1.x.y } and foo {
>>> semver 2.x.y }. The main argument seems to be that the later keeps
>>> references that involve module names or namespaces unchanged (but
>>> they may or may not mean different things).
>>>
>>>>IMHO YANG package definition should be a separate issue, left out of
>>>> this
>>>>document. Andy has already provided some very good ideas about this
>>>> topic.
>>>
>>> I think it is necessary to think about how the semantic version
>>> numbers are used. See my remark above about imports. If we allow
>>> incompatible changes, than this has side effects and I think we are
>>> not done by just adding a semantic version number without going
>>> working throught the implications.
>>>
>>> /js
>>>
>>> --
>>> Juergen Schoenwaelder Jacobs University Bremen gGmbH
>>> Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
>>> Fax: +49 421 200 3103 <http://www.jacobs-university.de/>
>>
>
> ___
> 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
On Wed, 2017-11-15 at 08:24 +0100, Martin Bjorklund wrote:
> Ladislav Lhotka wrote:
> > On Wed, 2017-11-15 at 08:00 +0100, Martin Bjorklund wrote:
> > > Balazs Lengyel wrote:
> > > > See bellow!
> > > >
> > > >
> > > > On 20
, for example the ability to import two
different revisions of the same module.
Lada
>
>
> /martin
>
> _______
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
--
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76
On Wed, 2017-11-15 at 14:23 +0800, Ladislav Lhotka wrote:
> Hi,
>
> regarding my proposed reorganization of documents: I strongly disagree with
> Martin's comment on jabber that it would be a mere split of the contents into
> two documents. It is certainly not true because
>
rent mechanisms,
and the "inline" method invites various instance-related considerations whereas
"use-schema" doesn't; it's been my experience that people keep confusing schema
construction and instance data mounting.
Lada
--
Ladislav Lhotk
Robert Wilton writes:
> On 09/11/2017 15:37, Ladislav Lhotka wrote:
>> Robert Wilton writes:
...
>>>>> 3. Sec 2.1 Glossary of New Terms: "Schema" isn't actually defined
>>>>> anywhere (RFC 7950 doesn't define this). Should it be
Juergen Schoenwaelder writes:
> On Fri, Nov 10, 2017 at 04:39:36PM +0100, Ladislav Lhotka wrote:
>> >
>> > So what is the difference between "schema tree" and "schema"? Or to
>> > put it differently, what is "all associated semantics&q
w I understand it.
Lada
>
> If I understand 'definition hierarchy' correctly, than it seems
> "schema" is just an abbreviation of "schema tree", i.e., there is no
> semantic difference between these two terms. If there is a difference,
> we need to be ab
On Thu, 2017-11-09 at 08:34 -0800, Andy Bierman wrote:
>
>
> On Thu, Nov 9, 2017 at 7:37 AM, Ladislav Lhotka wrote:
> > Robert Wilton writes:
> >
> > >>
> > >>> 2. Sec 1. Introduction, page 4, paragraph starting "2.
> > >>> I
Martin Bjorklund writes:
> Ladislav Lhotka wrote:
>> On Wed, 2017-11-08 at 09:50 +0100, Martin Bjorklund wrote:
>> > Kent Watsen wrote:
>> > >
>> > >
>> > > > Hi Kent,
>> > > >
>> > > > thanks for
be to make things as
>> simple and easy to understand as possible. They are complex enough
>> anyway.
> Thanks,
> Rob
>
>
>>
>> Thanks, Lada
>>
>>> Thanks,
>>> Rob
>>>
>>>
>>> On 20/10
e:
>> All,
>>
>> This starts a two-week working group last call on
>> draft-ietf-netmod-schema-mount-07.
>>
>> The working group last call ends on November 3.
>> Please send your comments to the netmod mailing list.
>>
>> Positive comments, e.g., &q
Correct
> > >
> > >
> > >> - may extend this model by defining
> > >> + may extend this solution by defining
> > >
> > > Or perhaps "approach"? I would leave "solution" to marketing folks.
> >
> > "approac
ULD be
> present if any groupings are used from the external module."
>
>
> 'Appendix D. Data Tree Example':
>
> - The example in the Appendix D. has not been updated and it must be
> extended in order to demonstrate a usecase of operational datastore of
firm one more time that they are
> > unaware of any IPR related to this draft.
> >
> > Thank you,
> > Netmod Chairs
> >
> >
> > ___
> > netmod mailing list
> > netmod@ietf.org
> > http
be done to provide more context would be helpful.
It seems to make sense in A.3 - to demonstrate an URI of a resource
inside an NI.
>
> For the 2nd half of A2, what happens if there is an "lne-2", will it
> also get "eth0&
ly CC-ed on this email,
>> please also confirm one more time that they are
>> unaware of any IPR related to this draft.
>>
>> Thank you,
>> Netmod Chairs
>>
>>
>> ___
>> netmod mailing list
>> netmod@ietf.org
>
Andy
>
>
>
>
> ___
> 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
wasted
because they are tightly connected to XML (instead of being applicable to
general tree-like data).
It is perhaps also worth noting that XPath 1.0 spec now includes a note that
basically declares it deprecated and unmaintained.
Lada
>
> /jan
>
>
le : The YANG 1.1 Data Modeling Language
> > > Publication Date: August 2016
> > > Author(s) : M. Bjorklund, Ed.
> > > Category: PROPOSED STANDARD
> > > Source : NETCONF Data Modeling Language
> > > Area: Operations and Management
> > > Stream : IETF
> > > Verifying Party : IESG
> > > .
> > >
>
> ___
> 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
t;>>
>>>>> Hi Lada,
>>>>>
>>>>> Thanks for the explanation, that makes sense.
>>>>>
>>>>>
>>>>> On 20/10/2017 16:27, Ladislav Lhotka wrote:
>>>>>
>>>>>> Hi Rob,
>&g
xyz node, which is defined as the concatenation of
the string-values of all text node descendants of xyz.
Lada
>
> Thanks,
> Rob
>
>
>
> ___
> netmod mailing list
> netmod@ietf.org
>
dressed once the document is a WG
> document.
>
> The poll ends Oct 27.
>
> Thanks,
> Kent (and Lou)
>
> ___
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
--
Ladislav Lhotka
He
t.petch píše v Pá 06. 10. 2017 v 12:39 +0100:
> - 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.
> >
e 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-netm
Martin Bjorklund píše v Po 25. 09. 2017 v 11:57 +0200:
> Ladislav Lhotka wrote:
> > Robert Wilton píše v Čt 21. 09. 2017 v 10:38 +0100:
>
>
> [...]
>
> > > Yes, I agree that this scenario is very likely, but I think that the
>
> > > solution here
Robert Wilton writes:
> On 21/09/2017 16:10, Ladislav Lhotka wrote:
>> Robert Wilton píše v Čt 21. 09. 2017 v 10:38 +0100:
>>> On 20/09/2017 15:33, Ladislav Lhotka wrote:
>>>> Robert Wilton writes:
>>>>
>>>>> On 19/09/2017 15:07, Lad
Robert Wilton píše v Čt 21. 09. 2017 v 10:38 +0100:
>
> On 20/09/2017 15:33, Ladislav Lhotka wrote:
> > Robert Wilton writes:
> >
> > > On 19/09/2017 15:07, Ladislav Lhotka wrote:
> > > > Robert Wilton píše v Út 19. 09. 2017 v 14:49 +0100:
> > >
Robert Wilton writes:
> On 19/09/2017 15:07, Ladislav Lhotka wrote:
>> Robert Wilton píše v Út 19. 09. 2017 v 14:49 +0100:
>>> Hi Lada,
>>>
>>>
>>> On 19/09/2017 14:37, Ladislav Lhotka wrote:
>>>> Martin Bjorklund writes:
>>>>
ase notation but what it
> shows is fundamentally different.
+1
Lada
>
> /js
>
--
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
Robert Wilton píše v Út 19. 09. 2017 v 14:49 +0100:
> Hi Lada,
>
>
> On 19/09/2017 14:37, Ladislav Lhotka wrote:
> > Martin Bjorklund writes:
> >
> > > Ladislav Lhotka wrote:
> > > > Hi,
> > > >
> > > > I support
Martin Bjorklund writes:
> Ladislav Lhotka wrote:
>> Hi,
>>
>> I support the adoption but I propose two conceptual changes:
>>
>> 1. Introduce a new module name and namespace so that it is not
>> necessary to carry along the deprecated baggage. If read
ent is a WG document.
>
> The poll ends Oct 2.
>
> Thanks,
>
> Lou (and Kent)
>
> ___
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
--
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key
.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty.
>
> Thank you,
> NetMod WG Chairs
>
> PS Please include all listed in the headers of this message in your
> response.
>
>
>
--
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
option and continue to try and
>>> resolve this issue at the same time ;-). I think that it would be good to
>>> try and get the updated model drafts to WG LC by Singapore.
>>>
>>> I know that it hasn't been asked yet, but I support adoption of any 8022
>
> Thank you,
> > Netmod Chairs
> >
> > ___
> > netmod mailing list
> > netmod@ietf.org
> > https://www.ietf.org/mailman/listinfo/netmod
>
> ___
> netmod mailing
Martin Bjorklund píše v Pá 15. 09. 2017 v 13:40 +0200:
> Robert Wilton wrote:
> >
>
> >
>
> > On 15/09/2017 11:21, Ladislav Lhotka wrote:
>
> > > Andy Bierman píše v Čt 14. 09. 2017 v 08:43 -0700:
>
> > >> Hi,
>
> > >>
//tools.ietf.org/html/draft-bjorklund-netmod-rfc7277bis-00
> > > 3. https://tools.ietf.org/html/draft-acee-netmod-rfc8022bis-00
> > >
> > > Please take a look (comments welcome!) and stay tuned for the related
> > > adoption calls.
> > >
> > > Tha
draft-ietf-netmod-yang-tree-diagrams?
> >
> > 3. What changes to the output format would you recommend?
> >
> > Thanks.
> >
> > Joe
> >
> > _______
> > netmod
that are supposed to
hold in all data trees should IMO stay no matter what.
Lada
--
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
ns to use '-state'.
Yes there might, but most likely when someone uses "-state" in the name of a
container they will be doing the wrong thing, and it may cause them problems
down the line. Warning them of the potential problems now so that they make
a
then appropriate.
Regarding the documentation needs, 6087bis could recommend not to rely
completely on the inheritance of deprecated status, and put it to other places
for documentation purposes (using common sense).
Lada
>
> /js
>
--
Ladislav Lhotka
Head, C
; > > > path-stmt.
> > > >
> > > >leaf foo {
> > > > type string;
> > > > status deprecated;
> > > > }
> > > >
> > > > leaf bar {
> > > > type leafref { path /foo; }
> > > > }
> > > >
> > > > If it apples to path-stmt, then why not all XPath?
> > >
> > > B/c in XPath it is even ok to refer to non-existing nodes. And you
> > > might have things like /baz/*.
> > >
> > > > Why doesn't "reference" include descendant nodes?
> > > >
> > > > The text in 7950 is too strict and can cause a massive ripple-effect
> > > > when
> > > > any status-stmt is changed.
> > > > At the same time it is too vague to be useful to implementors.
> > >
> > > While I agree that it is not clear what it means to have a "current"
> > > child to a "deprecated" node, I don't think this is a big issue. If a
> > > node is deprecated, it is ok for an implementation to not implement
> > > it. Obviously this means that no child nodes to that node is
> > > implemented either, regardless of their status, if they are augmented
> > > in, or comes from a grouping.
> >
> > what about the mandatory nodes inside a deprecated container?
> > Formally, they are not deprecated (default status is current) so
> > still mandatory, right?
>
> mandatory or not doesn't matter; mandatory doesn't mean "must
> implement", but "must exist if the parent exists".
>
>
>
> /martin
> ___
> 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
Thanks,
> Rob
>
>
> On 05/09/2017 22:37, Lou Berger wrote:
> > Rob,
> >
> > (as chair)
> > On 9/5/2017 1:17 PM, Robert Wilton wrote:
> > > However, I have thrown in the towel on my regex crusade.
> >
> > I'm sorry, I've lost the thread here a bit. in order to guage consensus
> > on this topic, it would be helpful to send the latest text that you are
> > proposing for inclusion in the the bis. If you are willing to do these,
> > we can poll to see if there is/is not support for inclusion of this
> > text. Are you willing, i.e., can you send the current proposed text change?
> >
> > Thank you,
> > Lou
> >
> > .
> >
>
>
--
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
atever the reason really is, still will either have to continue to
> cheat by silently interpreting XSD pattern as POSIX pattern or they
> create a proper new statement to at least properly distinguish
> different pattern languages.
>
> /js
>
--
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
Robert Wilton píše v Po 04. 09. 2017 v 17:07 +0100:
> Hi Lada,
>
> On 04/09/2017 15:59, Ladislav Lhotka wrote:
> > Robert Wilton píše v Po 04. 09. 2017 v 15:05 +0100:
> > > Hi Andy,
> > >
> > > On 02/09/2017 17:46, Andy Bierman wrote:
> > > >
>
> > > --
> > > Juergen Schoenwaelder Jacobs University Bremen gGmbH
> > > Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
> > > Fax: +49 421 200 3103 <http://www.jacobs-university.de/>
> > >
> > > ___
> > > 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
--
> > You may review the report below and at:
> > http://www.rfc-editor.org/errata/eid5105
> >
> > ------
> > Type: Technical
> > Reported by: Ladislav Lhotka
> >
> > Section: 3
> >
> > Original
Lou Berger writes:
> On August 29, 2017 9:03:22 AM Per Hedeland wrote:
>
>> On 2017-08-29 14:34, Lou Berger wrote:
>>> On 08/29/2017 03:37 AM, Martin Bjorklund wrote:
>>>> Lou Berger wrote:
>>>>> Lada,
>>>>>
>>>>>
&
Lou Berger writes:
> Lada,
>
>
> On 8/28/2017 10:16 AM, Ladislav Lhotka wrote:
>> Lou Berger píše v Po 28. 08. 2017 v 09:40 -0400:
>>> Lada,
>>>
>>> On 8/28/2017 9:30 AM, Ladislav Lhotka wrote:
>>>>> Can you please take a look at it a
Lou Berger píše v Po 28. 08. 2017 v 09:40 -0400:
> Lada,
>
> On 8/28/2017 9:30 AM, Ladislav Lhotka wrote:
> > > Can you please take a look at it and see if we have any other disconnects?
> >
> > This is really scary.
>
> I agree!
>
> > How can we
mounts under choices/cases? Isn't the resulting path to
> > > > > data nodes indistinguishable when the parent is a list or container?
> > > >
> > > > Suppose a server lists a couple of modules for "vrf-root" and some
> > > > other for "vsi-r
t;>> supported in the POSIX variant. If possible, the model designers SHOULD
>>> avoid using Unicode characters, such as: \p{L} and \p{N}.
>>>
>>> 1.3. Conversion Tools
>>> Tools can automatically convert regular expressions from one variant to
>>&g
7;t, is not (in my
> opinion).
I completely agree.
Lada
>
> --Per
>
> > I agree with Rob that the pattern in draft-ietf-rtgwg-routing-types-09 is
> > complicated to read. I have the feeling the design can be improved without
> > c
Robert Wilton píše v St 23. 08. 2017 v 17:58 +0100:
>
> On 23/08/2017 15:22, Ladislav Lhotka wrote:
> > Juergen Schoenwaelder píše v St 23. 08. 2017 v 15:36 +0200:
> > > On Wed, Aug 23, 2017 at 02:23:12PM +0100, Robert Wilton wrote:
> > > > 1) Email address. I
t.petch píše v St 23. 08. 2017 v 17:28 +0100:
> - Original Message -
> From: "Ladislav Lhotka"
> Sent: Wednesday, August 23, 2017 11:53 AM
>
> > "t.petch" writes:
> >
> > > - Original Message -
> > > From
alse negatives, i.e. reject valid
values. For some regexes this is what makes them complicated.
Also, I don't see any need for replacing existing patterns unless they are
wrong. We have descriptions to tell human readers about the permitted value set.
Lada
>
> /js
>
--
Ladisl
087Bis.
>> >
>> > Thanks,
>> > Acee
>> >
>> > On 8/21/17, 9:44 AM, "netmod on behalf of Ivory, William"
>> >
> wrote:
>> >
>> >> Hi Rob,
>> >>
>> >> That would make it very hard to updat
bmodule is arguably in a different module.
> >
> >
> >
> > Lada
> >
> > ‘
> >
> > Thanks,
> >
> > William
> >
> > ___
> >
and be specified separately.
> FWIW, in terms of complexity, I think that schema-mount in particular has
> pushed the YANG-complexity envelope more so than any other recent
> activity.
I fully agree and I have said it myself several times. My concern a
Hi Rob,
> On 28 Jul 2017, at 12:34, Robert Wilton wrote:
>
> Hi Lada,
>
>
> On 26/07/2017 11:46, Ladislav Lhotka wrote:
>> "Sterne, Jason (Nokia - CA/Ottawa)" writes:
>>
>>> OK – so the same leaf (in the schema) has the same value spa
quot; into
>> "ethernet-mac-like" and "ethernet-phy-like". At Aviat we have microwave
>> radio interfaces that behave like Ethernet at the MAC level but have totally
>> different PHYs. The distinction is also useful for virtual links, such as
>> link agg
for config ? I’m thinking of the basic admin/oper state
> for interfaces for example where config may allow enable/disable but state
> may have additional values like ‘testing’. If the config & state value
> spaces aren’t 100% the same, are module designers recommended to create a
t; properties could also be defined.
>
> I'm seeking input from the WG as to whether they like this approach, AND
> also whether the WG drafts: draft-ietf-netmod-intf-ext-yang-05 and
> draft-ietf-netmod-sub-intf-vlan-model-02 should be updated to make use
> of this approach
ference
>>> "IEEE 802.3";
>>> }
>>>
>>> identity ETHERTYPE_IPV4 {
>>> base ETHERTYPE;
>>> description
>>> "IPv4 protocol (0x0800)";
>>> }
>>>
>>> ...
>>> ...
>>>
>&g
gt; payload.";
> reference
> "IEEE 802.3";
> }
>
> identity ETHERTYPE_IPV4 {
> base ETHERTYPE;
> description
> "IPv4 protocol (0x0800)";
> }
>
> ...
> ...
>
> and so on.
>
> —
> You are receiving this because you are subscribe
> On 14 Jun 2017, at 13:43, Lou Berger wrote:
>
> Hi,
>
> (speaking as contributor...)
>
>
> On 6/14/2017 7:17 AM, Ladislav Lhotka wrote:
>> Hi Xufeng,
>>
>> please see my answers inline.
>>
>> Xufeng Liu writes:
>>
>>
ut
there is no "schema" entry under "schema-mounts" to worry about.
Lada
>
> For example, ietf-ospf module augments ietf-routing. When we mount
> ietf-routing ietf-yang-library to LNE, should we list ietf-ospf in the mount
> module list? And a
> On 14 Jun 2017, at 11:21, Robert Wilton wrote:
>
>
>
> On 14/06/2017 09:28, Ladislav Lhotka wrote:
>>> On 14 Jun 2017, at 00:35, Alex Campbell wrote:
>>>
>>>
>>> Presumably a device is free to not implement an optional config=false
>
>
> Alex
>
> From: netmod on behalf of Andy Bierman
>
> Sent: Wednesday, 14 June 2017 7:30 a.m.
> To: Ladislav Lhotka
> Cc: netmod@ietf.org
> Subject: Re: [netmod] Question on intefaces-state model
>
>
> On Tue, Jun 13, 2017 at 11:52 AM, Ladislav
GmbH
>> Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
>> Fax: +49 421 200 3103 <http://www.jacobs-university.de/>
>>
>> ___
>> netmod mailing list
>> netmod@ietf.org
>> https://www.ietf.org/ma
in default
> RIBs.
> Is it intended that this will be left to vendor-specific modules and/or
> future standards?
>
> Alex
> ___
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listi
uot;It is RECOMMENDED that
>> security-sensitive or privacy-sensitive data be modeled as regular YANG
>> data nodes rather than annotations."
>> >
>> >
>> >
>>
>> > ___
>> > netmod mailing list
>> > netmod@ietf
nt provides support
only for the latter two cases. Design-time mounts are outside the scope
of this document, and could be possibly dealt with in a future revision
of the YANG data modeling language.
Lada
>
> Lou
>
>
> __
.
Lada
>
> Lou
>
>
> ___
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
--
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
; A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> > This draft is a work item of the NETCONF Data Modeling Language of the IETF.
> >
> > Title : YANG Schema Mount
> > Authors : Martin Bjorklund
> &g
airs
>
>
>
>
> ___
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
--
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
p, the translation can actualy
be easier and more robust: for example, the translator can recognize YANG
identifiers in the text and avoid translating them.
Lada
>
> Andy
>
>
> On Fri, Apr 21, 2017 at 6:03 AM, Robert Wilton wrote:
> Hi Lada,
>
>
> On 20/04/2017 1
> On 21 Apr 2017, at 15:03, Robert Wilton wrote:
>
> Hi Lada,
>
>
> On 20/04/2017 13:28, Ladislav Lhotka wrote:
>> Kent Watsen writes:
>>
>>> All,
>>>
>>> We're a couple days away from the 2-week window. As of now, the
>
e of converting YANG automatically
>> to something else (not only to HTML, it starts already with YIN) knows
>> that transferring descriptions and other similar texts is tricky.
>>
>> Lada
>>
>>>
>>> Thanks,
>>> Phil
>>>
>>> _
(not only to HTML, it starts already with YIN) knows
> that transferring descriptions and other similar texts is tricky.
>
> Lada
>
>>
>> Thanks,
>> Phil
>>
>> ___
>> netmod mailing list
>> netmod@ietf.org
>> https://www.ietf.org/mailman/listi
thing else (not only to HTML, it starts already with YIN) knows
that transferring descriptions and other similar texts is tricky.
Lada
>
> Thanks,
> Phil
>
> ___
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailm
Robert Wilton writes:
> On 13/04/2017 17:08, Andy Bierman wrote:
>>
>>
>> On Thu, Apr 13, 2017 at 5:45 AM, Ladislav Lhotka > <mailto:lho...@nic.cz>> wrote:
>>
>>
>> > On 13 Apr 2017, at 13:34, t.petch > <mailto:ie...@btco
heasley writes:
>> > On 13 Apr 2017, at 09:14, Juergen Schoenwaelder
>> > wrote:
>> >
>> > On Thu, Apr 13, 2017 at 08:28:08AM +0200, Ladislav Lhotka wrote:
>> >>
>> >> We are talking past each other. Are you willing to admit t
Andy Bierman writes:
> On Thu, Apr 13, 2017 at 11:41 AM, Ladislav Lhotka wrote:
>
>>
>> > On 13 Apr 2017, at 18:08, Andy Bierman wrote:
>> >
>> >
>> >
>> > On Thu, Apr 13, 2017 at 5:45 AM, Ladislav Lhotka wr
> On 12 Apr 2017, at 19:59, Andy Bierman wrote:
>
>
>
> On Wed, Apr 12, 2017 at 10:39 AM, Ladislav Lhotka wrote:
>
> > On 12 Apr 2017, at 18:44, Andy Bierman wrote:
> >
> >
> >
> > On Wed, Apr 12, 2017 at 6:02 AM, Juergen Schoenwae
As the draft also tries to explain, some trivial markup is already commonly
used in IETF modules (for example, bulleted lists) and inconsistent indentation
rules make it difficult for applications to properly format such texts.
Lada
>
>
> /js
>
>
> Andy
>
>
ne, but module readers should have little
difficulty if not.
Thanks, Lada
>
> Thanks,
> Rob
>
>
> On 10/04/2017 12:45, Ladislav Lhotka wrote:
>> As the author: yes/support.
>>
>> Two changes seemed to have support in IETF 98 audience:
>>
>> 1.
nt.
>>
>> Thank you,
>> NETMOD WG Chairs
>
> ___
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
--
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
s
>
>
> ___
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
--
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
https://www.ietf.org/mailman/listinfo/netmod
>> .
>>
>
> ___
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
--
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
t is important to have all this information
represented in a compact way and in a single place.
Thanks, Lada
--
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
pression is evaluated once for each entry, always with the
same result. It may or may not be a problem depending on the number of entries.
Lada
>
> Regards, Bart
>
> -----Original Message-
> From: Ladislav Lhotka [mailto:lho...@nic.cz]
> Sent: 29 March 2017 14:37
t a-list {
>
> key "entry";
>
> leaf entry {
>
> type uint16;
>
> }
>
> }
>
> }
>
>
>
> And used in another module
>
>
>
> container a-container {
>
> uses a-group;
>
> must "count(a-list) != 1" {
>
> description
>
> "This list must either be empty or have at least 2 elements";
>
> }
>
> }
>
>
>
> Best regards - Vriendelijke groeten,
>
> Bart Bogaert
>
> ___
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
--
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
> On 21 Mar 2017, at 15:11, Juergen Schoenwaelder
> wrote:
>
> On Tue, Mar 21, 2017 at 01:01:58PM +0100, Ladislav Lhotka wrote:
>>
>>> On 21 Mar 2017, at 12:50, Robert Wilton wrote:
>>>
>>>
>>> So I am suggesting perhaps just havin
> On 21 Mar 2017, at 12:50, Robert Wilton wrote:
>
>
>
> On 21/03/2017 10:49, Ladislav Lhotka wrote:
>>> On 21 Mar 2017, at 11:25, Juergen Schoenwaelder
>>> wrote:
>>>
>>> Hi,
>>>
>>> if we want to standardize tr
ng
>
> notifications:
>+--n- notification
> +--nt boom? string
>
> (And I think the oops leafs should have triggered an error.)
>
> /js
>
> --
> Juergen Schoenwaelder Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587
> On 21 Mar 2017, at 11:30, Juergen Schoenwaelder
> wrote:
>
> On Tue, Mar 21, 2017 at 10:59:11AM +0100, Ladislav Lhotka wrote:
>>
>> If the "config" statement really carried some protocol-specific semantics
>> that isn't meaningful for all
401 - 500 of 1331 matches
Mail list logo
