r
extensions but it breaks down as soon as such extensions interfere with
the YANG core (with and each other, or both).
Lada
>
> Regards,
> Robert
>
--
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
21 200 3587 Campus Ring 1 | 28759 Bremen | Germany
>> Fax: +49 421 200 3103 <https://www.jacobs-university.de/
>> <https://www.jacobs-university.de/>>
>>
>> ___
>> netmod mailing list
>> netmod@ietf.org <mailto: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
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
On Sat, 2018-04-21 at 03:16 +0200, Robert Varga wrote:
> On 17/04/18 07:35, Ladislav Lhotka wrote:
> > Hi,
> >
> > this is a slippery slope. If we want to turn YANG into a general-purpose
> > schema language, it should IMO be done the other way around: design a
> >
; at the top level.
>
> If the WG agrees with what I wrote above, we need to change the
> augment-yang-data extension so that you would write for example:
>
> yx:augment-yang-data /ex:my-first-rpc-error-info/ex:user-info {
> ...
> }
>
> Comments?
>
>
>
> /martin
>
> ___
ceptually) exists if its parent exists - regardless of number of
> > children.
> >
> > So if the parent exists, any must expressions in the NP-container are
> > evaluated.
> >
>
> what about top-level NP-container with must constraint? Is a root n
if a device
>> implements support for PPP configuration/operational state then it would
>> also naturally define any PPP related interface identities at the same time.
>>
>> If a vendor wants to define their own flavour of Ethernet interface then
>> they can do so in t
On Fri, 2018-04-06 at 14:29 +0200, Juergen Schoenwaelder wrote:
> On Fri, Apr 06, 2018 at 02:01:30PM +0200, Ladislav Lhotka wrote:
> > On Fri, 2018-04-06 at 13:36 +0200, Juergen Schoenwaelder wrote:
> > > On Fri, Apr 06, 2018 at 10:51:48AM +0200, Ladislav Lhotka wrot
On Fri, 2018-04-06 at 13:36 +0200, Juergen Schoenwaelder wrote:
> On Fri, Apr 06, 2018 at 10:51:48AM +0200, Ladislav Lhotka wrote:
> > Juergen Schoenwaelder writes:
> >
> > > If we would have a mechanism to deviate an identityref to a subset of
> > >
t;> shorter "by itself". Now iana-if-type is just a collection of all interface
>> types that have been defined once without any kind of "structure".
>>
>> Regards, Bart
>>
>> -Original Message-
>> From: Ladislav Lhotka [mailto:l
completions if an operator would ask for
> the possible values of the type of an interface.
> Has this ever been considered/discussed?
>
> Best regards,
> Bart
> ___
> netmod mailing list
> netmod@ietf.org
> https://w
ot;entry";
> > > leaf entry {
> > > type uint16;
> > > }
> > > leaf another-entry {
> > > type uint32;
> > > }
> > > }
> > > }
> > >
> > > I think I could also replace that
that some of N devices are
> having different
>versions of modules.
>This can lead to each instance of mount point, having different schema.
>How can the client understand the schema of each mount-point instance ?
> Preferably get-schema of these devices and then know the model ?
>
> With Regards,
>
> Rohit R
> ___
> 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, 2018-03-07 at 14:06 +0100, Martin Bjorklund wrote:
> Ladislav Lhotka wrote:
> > Hi,
> >
> > sec. 6.4.1 in RFC 7950 says in the second bullet item:
> >
> > Names without a namespace prefix belong to the same namespace as
> > the identif
Robert Varga writes:
> On 27/02/18 08:02, Ladislav Lhotka wrote:
>> The initial virtual interim decided to use Martin's combined proposal
>> and most of my subsequent objections were rejected on the basis of that
>> decision. That's why I hate discussing complicate
x belong to the same namespace as
the identifier of the current node.
NEW
Names without a namespace prefix belong to the same namespace as
the identifier of the context node.
If there are no objections, I will file an erratum.
Lada
>
> Regards,
> Michal
>
> On Wednes
;
...
}
}
...
}
What is the namespace of "quux" in the when expression? Is it "example-4-a"
(option 1 above) or "example-4-b" (option 2)?
Thanks, Lada
--
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67
__
Schoenwaelder Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
> Fax: +49 421 200 3103 <https://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 Mon, 2018-03-05 at 15:49 +0100, Per Hedeland wrote:
> On 2018-03-05 15:41, Ladislav Lhotka wrote:
> > On Mon, 2018-03-05 at 15:26 +0100, Martin Bjorklund wrote:
> > > Juergen Schoenwaelder wrote:
> > > > On Mon, Mar 05, 2018 at 02:54:18PM
yang:dotted-quad
>
>
> /martin
>
>
> > The document (as far as I searched for it) does not clearly say that
> > 'node' means 'schema node'. In hindsight, it might have been useful to
> > explicitel
Christian Hopps writes:
> Ladislav Lhotka writes:
>
>> On Tue, 2018-02-27 at 09:31 +0100, Juergen Schoenwaelder wrote:
>>> On Mon, Feb 26, 2018 at 04:09:21PM +0100, Martin Bjorklund wrote:
>>> > Hi,
>>> >
>>> > Christian Hopps wrote:
&g
ocument that just defines the mount point extension and
> we do an update of this document that adds all the details needed to
> obtain the schema information?
I would say so. It would be immediately usable for the inline case.
Lada
>
> /js
>
--
Ladislav Lhotka
Head, CZ.NIC Lab
gt;> >>>> > Details -- for those who want
>>> >>>> > ==
>>> >>>> > As background, my understanding/view is that the -08 version of the
>>> >>>> > both NMDA and non-NMDA supporting implementations, but there are
>>> >>>> > limitations in its NMDA applicability. Used with Yang Library,
>>> >>>> > [rfc7895], only non-NMDA implementations can be supported. When used
>>> >>>> > with the revised Yang Library defined in
>>> >>>> > [I.D.ietf-netconf-rfc7895bis-], NMDA implementations can be
>>> >>>> > supported with certain limitations. Specifically, this document
>>> >>>> > requires use of the now deprecated module-list grouping, and the same
>>> >>>> > schema represented in schema list of the Schema Mount module MUST be
>>> >>>> > used in all datastores. Inline type mount points, which don't use the
>>> >>>> > schema list, can support different schema in different data stores
>>> >>>> > not by instantiating the [I.D.ietf-netconf-rfc7895bis-] version of
>>> >>>> > YANG library under the inline mount point.
>>> >>>> >
>>> >>>> > module: ietf-yang-schema-mount
>>> >>>> > +--ro schema-mounts
>>> >>>> > +--ro namespace* [prefix]
>>> >>>> > | +--ro prefix yang:yang-identifier
>>> >>>> > | +--ro uri? inet:uri
>>> >>>> > +--ro mount-point* [module name]
>>> >>>> > | +--ro module yang:yang-identifier
>>> >>>> > | +--ro name yang:yang-identifier
>>> >>>> > | +--ro config? boolean
>>> >>>> > | +--ro (schema-ref)?
>>> >>>> > | +--:(inline)
>>> >>>> > | | +--ro inline? empty
>>> >>>> > | +--:(use-schema)
>>> >>>> > | +--ro use-schema* [name]
>>> >>>> > | +--ro name
>>> >>>> > | | -> /schema-mounts/schema/name
>>> >>>> > | +--ro parent-reference* yang:xpath1.0
>>> >>>> > +--ro schema* [name]
>>> >>>> > +--ro name string
>>> >>>> > ADD +--ro datastore* ds:datastore-ref {revised-datastores}
>>> >>>> > +--ro module* [name revision]
>>> >>>> > | +--ro name yang:yang-identifier
>>> >>>> > | +--ro revision union
>>> >>>> > | +--ro schema? inet:uri
>>> >>>> > | +--ro namespace inet:uri
>>> >>>> > | +--ro feature* yang:yang-identifier
>>> >>>> > | +--ro deviation* [name revision]
>>> >>>> > | | +--ro name yang:yang-identifier
>>> >>>> > | | +--ro revision union
>>> >>>> > | +--ro conformance-type enumeration
>>> >>>> > | +--ro submodule* [name revision]
>>> >>>> > | +--ro name yang:yang-identifier
>>> >>>> > | +--ro revision union
>>> >>>> > | +--ro schema? inet:uri
>>> >>>> > +--ro mount-point* [module name]
>>> >>>> > +--ro module yang:yang-identifier
>>> >>>> > +--ro name yang:yang-identifier
>>> >>>> > +--ro config? boolean
>>> >>>> > +--ro (schema-ref)?
>>> >>>> > +--:(inline)
>>> >>>> > | +--ro inline? empty
>>> >>>> > +--:(use-schema)
>>> >>>> > +--ro use-schema* [name]
>>> >>>> > +--ro name
>>> >>>> > | -> /schema-mounts/schema/name
>>> >>>> > +--ro parent-reference* yang:xpath1.0
>>> >>>> >
>>> >>>> > We would expect that the revised-datastores feature would be used
>>> >>>> > (perhaps required) for any implementation that supports
>>> >>>> > ietf-datastores
>>> >>>> > and yl-bis.
>>> >>>> >
>>> >>>> >
>>> >>>> >
>>> >>>> > ___
>>> >>>> > 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
>>> >>>
>>> >>> ___
>>> >>> 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
Per Hedeland writes:
> [Adding Cc to draft-ietf-netmod-acl-mo...@ietf.org]
>
> On 2018-02-26 14:24, Ladislav Lhotka wrote:
>> Per Hedeland writes:
>>
>>> Hi,
>>>
>>> A customer of ours using one of the draft versions of the
>>> ietf-acc
On Mon, 2018-02-26 at 14:16 +, Robert Wilton wrote:
> Hi Lada,
>
>
> On 26/02/2018 14:05, Ladislav Lhotka wrote:
> > Hi Rob,
> >
> > Robert Wilton writes:
> >
> > > Hi Chris,
> > >
> > > I've got no desire or intent to
gt;>>> > | +--:(use-schema)
>>>> > | +--ro use-schema* [name]
>>>> > | +--ro name
>>>> > | | -> /schema-mounts/schema/name
>>>> > | +--ro parent-reference* yang:xpath1.0
>>>> > +--ro schema* [name]
>>>> > +--ro name string
eflexivity property of identity derivation,
which is, in my view, an unnecessary complication. It would be simpler
but sufficient to define derivation as a reflexive relation, and have
only one "derived-from()" XPath function.
Identities that are considered "abstract" should n
g-identifier
>> +--ro config? boolean
>> +--ro (schema-ref)?
>> +--:(inline)
>> | +--ro inline? empty
>> +--:(u
Robert Wilton writes:
> Hi Lada,
>
>
> On 16/02/2018 09:06, Ladislav Lhotka wrote:
>> Robert Wilton writes:
>>
>>> I should add, as a contributor, I have read this document and think that
>>> is ready for advancement.
>>>
>>> I ha
>
>
>> /js
>>
>
>
> Andy
>
>
>>
>> --
>> Juergen Schoenwaelder Jacobs University Bremen gGmbH
>> Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
>> Fax: +49 421 200 3103 <http
Y&e=>
>>
>> Mahesh & Kent
>>
>>
>>
>>
>> ___
>>
>> Netconf mailing list
>>
>> netc...@ietf.org <mailto:netc...@ietf.org>
>>
>> https://www.ietf.org/mailman/listinfo/netconf
&
gt;> WG,
>>>>>>
>>>>>> The authors of rfc7895bis have indicated that they believe the
>>>>>> document is
>>>>> ready for LC[1].
>>>>>> This starts a two week LC on the
>>>>>> draft<https://tools.ietf.org/html/draft-ietf-
>>
On Mon, 2018-02-12 at 15:37 +0100, Juergen Schoenwaelder wrote:
> On Mon, Feb 12, 2018 at 03:26:31PM +0100, Ladislav Lhotka wrote:
>
> > > > Sec. 1 - YANG library stability
> > > >
> > > > The text basically says that the YANG library infor
On Mon, 2018-02-12 at 13:02 +0100, Martin Bjorklund wrote:
> Hi,
>
> Thank you for this review. Comments inline.
>
> Ladislav Lhotka wrote:
> > Hi,
> >
> > here is my review of the rfc7895bis document:
> >
> > *** General comments
> &g
git.
Nits
- sec 1. paragraph 2: s/informaton/information/
Lada
--
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
x27;s fine. But I don't think we should fundamentally
> change the solution that the WG agreed upon.
I don't agree that we are *strongly* changing the solution. Simplifications and
clarifications are IMO badly needed.
Lada
>
>
> /martin
>
>
>
> Ladislav
On Wed, 2018-02-07 at 11:41 +, Robert Wilton wrote:
>
> On 07/02/2018 10:29, Ladislav Lhotka wrote:
> > On Wed, 2018-02-07 at 11:14 +0100, Martin Bjorklund wrote:
> > > Juergen Schoenwaelder wrote:
> > > > On Tue, Feb 06, 2018 at 03:25:52PM +, Robert Wil
t" evokes that some
*instance* data being added, which is what happens in the "inline" case but not
for "use-schema".
Lada
>
>
> /martin
>
> >
> > > Whether it would be right to change these at this time, I've no idea ...
> >
whether and when the embedded YL data magically appears in -
it is the mount event that does exactly this, and only after that the
mounted resource can be configured. This concept would also be more
alike to the mount operation known from Unix filesystems.
Comments?
Lada
--
Ladislav Lhotk
are of any IPR for either of the
>> drafts.
>>
>> Thanks.
>>
>> Mahesh & Kent
>>
>
> Mahesh & Kent
>
> ___
> Netconf mailing list
> netc...@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
--
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
tastore Architecture
normatively in the data model for routing manangement.
Personnel
Joel Jaeggli is the document shepherd,
Benoit Claise is the Responsible AD.
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo
incOfM&s=DRRZhdQAI9SIgw8UL1SByT8FGQjfJDpvuNf4jK_1UgQ&e=
>> .
>>
>
>
>
> ___
> 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, 2018-01-24 at 09:35 -0500, joel jaeggli wrote:
>
> On 1/24/18 8:07 AM, Ladislav Lhotka wrote:
> > Hi,
> >
> > Kent Watsen writes:
> >
> > > Thank you all for the important discussion since the completion of WGLC on
> > > Nov 6th.
&
hanks,
> Kent, Lou, and Joel
>
>
>
> ___
> 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
3587 Campus Ring 1 | 28759 Bremen | Germany
> Fax: +49 421 200 3103 <https://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
200 3103 <https://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
anyways.
Yes, and also keeping some deprecated nodes from the old version, which
would make the new model hard to read. This is IMO too high a price.
Lada
>
> Kent
>
>
>
>
> ___
> netmod mailing list
> netmod@ietf.org
> h
Robert Wilton writes:
> On 17/01/2018 16:40, Martin Bjorklund wrote:
>> Ladislav Lhotka wrote:
>
>
>
>>>> Ok. I'm ok with keeping the inline case as it is. However, I think
>>> I don't agree. The metadata annotation solves real issues.
&
whose impact can be fully analyzed.
>
> Lou
>
> On January 19, 2018 3:59:22 AM Martin Bjorklund wrote:
> ...
> > Hi,
> >
> > joel jaeggli wrote:
> > >
> > >
> > > On 1/18/18 11:15 AM, Martin Bjorklund wrote:
> > > > Ladislav
On Thu, 2018-01-18 at 13:25 -0800, joel jaeggli wrote:
>
> On 1/18/18 11:15 AM, Martin Bjorklund wrote:
> > Ladislav Lhotka wrote:
> > > On Thu, 2018-01-18 at 14:39 +0100, Juergen Schoenwaelder wrote:
> > > > Ignoring process issues (not sure there are any), does
> > > > > requiring inline schemas to be available at the top level.
> > > > >
> > > > > Ok. I'm ok with keeping the inline case as it is. However, I think
> > > > > we need to use the new YL-bis, so that we can support the NMDA.
> > > >
> > > > Given that NMDA support is not yet fully defined, we're still in the
> > > > transition period where support for both NMDA and non-NMDA
> > > > implementations need to be considered. Rob presented some options
> > > > earlier in the thread that I think captures this.
> > >
> > > Again, note that YLbis supports both NMDA and non-NMDA servers.
> > >
> > > Also note that YLbis is just a different read-only monitoring
> > > structure. Given an implementation that supports the old YL, it is
> > > trivial to add support for YLbis (especially compared to the more than
> > > non-trivial amount of work required to support schema mount...).
> > >
> > >
> > > /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
owever, I think
> > > we need to use the new YL-bis, so that we can support the NMDA.
> >
> > Given that NMDA support is not yet fully defined, we're still in the
> > transition period where support for both NMDA and non-NMDA
> > implementations need to be conside
On Wed, 2018-01-17 at 14:14 -0500, Lou Berger wrote:
>
> On 1/17/2018 11:57 AM, Ladislav Lhotka wrote:
> > > > > Ok. I'm ok with keeping the inline case as it is. However, I think
> > > >
> > > > I don't agree. The metadata annotat
On Wed, 2018-01-17 at 17:40 +0100, Martin Bjorklund wrote:
> Ladislav Lhotka wrote:
> > On Wed, 2018-01-17 at 17:18 +0100, Martin Bjorklund wrote:
> > > Lou Berger wrote:
> > > >
> > > >
> > > > On January 17, 2018 9:42:43 AM Martin B
> > > > > > > > doesn't work equally at an inline mount point. Can you
> > > > > > > > > elaborate?
> > > > > > > >
> > > > > > > > With NMDA, a server may have one schema for the config datastore
>
nal. Thus, there's no
> > > > > > > way a
> > > > > > > client can learn the schema for config.
> > > > > >
> > > > > > If the LNE mounted the full YL-bis at the mount point then you would
> > > &
On Wed, 2018-01-17 at 09:09 -0500, Lou Berger wrote:
>
> On 1/17/2018 1:59 AM, Ladislav Lhotka wrote:
> ...
> > > > > > > I think
> > > > > > > it is incumbent upon those revisiting past/closed WG decisions (in
> > > > > >
On Wed, 2018-01-17 at 09:27 +0100, Juergen Schoenwaelder wrote:
> On Wed, Jan 17, 2018 at 09:04:29AM +0100, Ladislav Lhotka wrote:
> > > Lada,
> > > Understanding impact of your proposal on the following would be
> > > quite helpful:
> > > https://da
Lou Berger writes:
> On 1/16/2018 10:22 AM, Ladislav Lhotka wrote:
>>>> I think
>>>> it is incumbent upon those revisiting past/closed WG decisions (in
>>>> this case, inline schema being represented by YL) to argue why the
>>>> decision needs
for operational (one is a superset of the other). A
> > mounted YL can only be present in operational. Thus, there's no way a
> > client can learn the schema for config.
>
> If the LNE mounted the full YL-bis at the mount point then you would
> have the list of datastores,
a-ref leafref with
which the mount point instance undergoing the change is annotated.
> cases where the ability to access information under an inline mount
> point will dynamically change in operation (and top level YL would need
> to remove schema information for the inline mount point.) As before,
> from the usage standpoint, these changes don't provide a whole lot of
> value and seem to optimizing for something not needed in the inline case.
>
> > > I think
> > > it is incumbent upon those revisiting past/closed WG decisions (in
> > > this case, inline schema being represented by YL) to argue why the
> > > decision needs to be revisited.
> >
> > I'm repeating my self: b/c the current solution doesn't work well with
> > the NMDA.
>
> I simply don't understand how YL-bis works at the root node but doesn't
> work equally at an inline mount point. Can you elaborate?
I propose that we update the schema mount draft in a separate branch on GitHub,
and then continue the discussion.
Lada
>
> Lou
>
> >
> >
> > /martin
> >
>
>
--
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67
___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
t; >> wrote:
> > >>
> > >>> Lou Berger wrote:
> > >>>> Lada,
> > >>>>
> > >>>>
> > >>>> On January 16, 2018 7:07:15 AM Ladislav Lhotka wrote:
> > >>>>
> > >>>>>
On Tue, 2018-01-16 at 13:40 +, Robert Wilton wrote:
>
> On 16/01/2018 13:23, Lou Berger wrote:
> > On 1/16/2018 7:41 AM, Robert Wilton wrote:
> > >
> > > On 16/01/2018 07:14, Ladislav Lhotka wrote:
> > > > Hi Lou,
> > > >
> >
On Tue, 2018-01-16 at 13:19 +0100, Martin Bjorklund wrote:
> Ladislav Lhotka wrote:
> > Hi Lou,
> >
> > in my view, we should do the following two (significant) changes:
> >
> > 1. Instead of borrowing a grouping from ietf-yang-library and having
> >
need to be returned to their WGs if either change is made.
>
> Martin,
>
> Do share Lada's view?
>
> Lou
>
>
> On January 16, 2018 2:14:42 AM Ladislav Lhotka wrote:
>
> > Hi Lou,
> >
> > in my view, we should do the following two (sig
outstanding?
>
> Thank you,
>
> Lou
>
> On 12/19/2017 8:26 AM, Ladislav Lhotka wrote:
> > 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 w
gt; 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 : A YANG Data Model for Routing Management
>
On Thu, 2017-12-21 at 14:25 +0100, Martin Bjorklund wrote:
> Ladislav Lhotka wrote:
> > Martin Bjorklund writes:
> >
> > > Hi Andy,
> > >
> > > Andy Bierman wrote:
> > >> Hi,
> > >>
> > >> I have re
t;> > A diff can be found at
>> > https://tools.ietf.org/rfcdiff?difftype=--hwdiff&url1=draft-ietf-netmod-
>> > revised-datastores-04.txt&url2=draft-ietf-netmod-revised-datastores-07.txt
>> >
>> > Comments along the of: I have reviewed this version of the document and it
>> > addresses my previous comments would be particularly helpful.
>> >
>> > Thank you,
>> > Netmod Chairs
>> >
>> > ___
>> > 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
Martin Bjorklund writes:
> Ladislav Lhotka wrote:
>> Hi Ian,
>>
>> On Thu, 2017-12-21 at 10:42 +0100, Ian Farrer wrote:
>> > Hi,
>> >
>> > I’m just looking at the guidance on wrapping long lines given in Section
>> > 3.1.
>>
augment "/nat:nat/nat:instances/nat:instance/"
+ "nat:mapping-table/nat:mapping-entry";
Lada
>
> Thanks,
> Ian
> ___
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailm
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: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
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 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.
> > >
> > &g
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 "in
-dsdt-nmda-guidelines-01
>>> [2]
>>>https://tools.ietf.org/rfcdiff?difftype=--hwdiff&url1=rfc8022.txt&url2=dr
>>>aft-ietf-netmod-rfc8022bis-01.txt
>>>
>>> Thank you,
>>> Netmod Chairs
>>>
>>
>>___
>>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
emas would be included in the
top-level YANG library, and mount point instances in all datastores
would be annotated with leafref pointing to the actual schema.
Unlike regular state data, it is IMO no problem to permit such
annotations in configuration datastores.
Opinions?
Thanks, Lada
Ladis
Lada will like these kind of meta and meta-meta datastores.
Not really. Metadata needn't be in datastores.
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
osal is to move from YANG library as state data to an operation. It
could be done along with changing the YANG library structure, so there will be
little extra impact on implementations.
Lada
--
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67
__
eed to reuse the
same module sets, and it will also be quite easy to add schema mount
specification to this.
Lada
--
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-12-06 at 15:00 +0100, Martin Bjorklund wrote:
> Ladislav Lhotka wrote:
> > On Wed, 2017-12-06 at 14:51 +0100, Martin Bjorklund wrote:
> > > Juergen Schoenwaelder wrote:
> > > > I am not sure design decisions of some web clients that provide clumsy
ou replicate it in this extension's
parameter?
Lada
>
>
> /martin
>
>
> >
> > /js
> >
> > On Wed, Dec 06, 2017 at 01:37:36PM +0100, Ladislav Lhotka wrote:
> > > Hi,
> > >
> > > although detailed descriptions is a go
followed by an empty line,
and the rest of the description after that. User interfaces could then easily
recognize and use the summary line.
Perhaps 6087bis could include such a recommendation.
Lada
--
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67
Martin Bjorklund writes:
> Ladislav Lhotka wrote:
>> On Mon, 2017-12-04 at 18:22 +0100, Juergen Schoenwaelder wrote:
>> > On Mon, Dec 04, 2017 at 06:05:58PM +0100, Ladislav Lhotka wrote:
>> > > On Mon, 2017-12-04 at 17:34 +0100, Martin Bjorklund wrote:
&
es. Speaking about syntactic
> > versus semantic seems fluffy.
>
> See RFC 7950, section 8 (esp. 8.1 and 8.2).
Yes, and I think it is fully appropriate to denote constraints that have to be
satisfied in all data trees as "syntactic" (or "schema constraints")
On Tue, 2017-12-05 at 11:25 +0100, Juergen Schoenwaelder wrote:
> On Tue, Dec 05, 2017 at 10:03:07AM +0100, Ladislav Lhotka wrote:
> > On Mon, 2017-12-04 at 21:00 +0100, Juergen Schoenwaelder wrote:
> > > On Mon, Dec 04, 2017 at 07:09:51PM +0100, Ladislav Lhotka wrote:
>
On Mon, 2017-12-04 at 17:29 +, Robert Wilton wrote:
> Hi Lada,
>
>
> On 04/12/2017 17:05, Ladislav Lhotka wrote:
> > On Mon, 2017-12-04 at 17:34 +0100, Martin Bjorklund wrote:
> > > Ladislav Lhotka wrote:
> > > > Hi,
> > > >
> &
On Mon, 2017-12-04 at 21:00 +0100, Juergen Schoenwaelder wrote:
> On Mon, Dec 04, 2017 at 07:09:51PM +0100, Ladislav Lhotka wrote:
> >
> > Well, according to draft-ietf-netmod-revised-datastores-07:
> >
> >o datastore schema: The combined set of s
On Mon, 2017-12-04 at 09:36 -0800, Andy Bierman wrote:
>
>
> On Mon, Dec 4, 2017 at 9:22 AM, Juergen Schoenwaelder university.de> wrote:
> > On Mon, Dec 04, 2017 at 06:05:58PM +0100, Ladislav Lhotka wrote:
> > > On Mon, 2017-12-04 at 17:34 +0100, Martin Bjorklund wro
On Mon, 2017-12-04 at 18:22 +0100, Juergen Schoenwaelder wrote:
> On Mon, Dec 04, 2017 at 06:05:58PM +0100, Ladislav Lhotka wrote:
> > On Mon, 2017-12-04 at 17:34 +0100, Martin Bjorklund wrote:
> > > Ladislav Lhotka wrote:
> > > > Hi,
> > > >
> >
On Mon, 2017-12-04 at 17:34 +0100, Martin Bjorklund wrote:
> Ladislav Lhotka wrote:
> > Hi,
> >
> > if we have
> >
> > augment "/target/node" {
> > when "...";
> > ...
> > }
> >
> > is the "when&quo
t node for XPath evaluation is "the
augment's target node in the data tree", but with NMDA we have multiple data
trees, hence multiple target nodes.
Lada
--
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67
___
netmod mail
ch as ...
NEW
The YANG module specified in this document defines a schema for data that is
designed to be accessed via network management protocols such as ...
[1] https://trac.ietf.org/trac/ops/wiki/yang-security-guidelines
Lada
--
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F
On Thu, 2017-11-16 at 21:55 -0500, Joe Clarke wrote:
> On 11/15/17 05:38, Ladislav Lhotka wrote:
> > 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 a
vision is still
> compatible, it still supports XXX, but the next one won't. This way for OSS
> the migration from XXX to YYY is less painful.
> regards Balazs
>
> On 2017-11-16 10:04, Ladislav Lhotka wrote:
> > > BALAZS: You still need at leaast deprecated: my prop
The limiting factor is the document-oriented nature of
YANG. It is a good use case for schema mount though.
Lada
>
> Randy
>
> ___
> netmod mailing list
> netmod@ietf.org
> https://www.iet
Balazs Lengyel writes:
> On 2017-11-15 21:20, Martin Bjorklund wrote:
>
> Ladislav Lhotka wrote:
>
> On Wed, 2017-11-15 at 12:17 +0100, Martin Bjorklund wrote:
>
> Balazs Lengyel wrote:
>
> The server MAY implement obsoleted nodes or MAY NOT. This may
> or ma
gt; Makes sense to me. I could ask what you will do with the RFC 2119
> language in the ID but hey I do not ask these questions anymore. ;-)
+1
2119 terms should be replaced with plain words.
Lada
>
> /js
>
--
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67
On Wed, 2017-11-15 at 13:14 +0100, Martin Bjorklund wrote:
> 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
&
Ericsson Hungary Ltd.
> > Senior Specialist
> > Mobile: +36-70-330-7909 email: balazs.leng...@ericsson.com
> >
>
> ___
> 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
301 - 400 of 1331 matches
Mail list logo
