I like the idea of relocatable modules. It is almost to say everything defined
by the IETF should be a grouping, allowing others to assemble the pieces as
they see fit. I do not think it makes sense for IETF to define an uber
structure, especially using a language mandating forever backwards
Ladislav Lhotka lho...@nic.cz wrote:
On 25 Aug 2015, at 14:48, Martin Bjorklund m...@tail-f.com wrote:
Ladislav Lhotka lho...@nic.cz wrote:
On 25 Aug 2015, at 14:01, Martin Bjorklund m...@tail-f.com wrote:
Hi,
I think this could work (thanks Robert; maybe this is what you
Hi,
I think this could work (thanks Robert; maybe this is what you
meant!):
container zones {
list zone {
...
list rrset {
...
leaf type {
type identityref { ... }
}
list rdata {
key id;
...
choice
Hi Lada,
Thank you for this extensive review! Comments inline.
Ladislav Lhotka lho...@nic.cz wrote:
Hi,
this time I reviewed the complete text so my comments aren't limited to
YANG 1.1 stuff.
Lada
General comments
1. Would it make sense to at least mention that YANG is
Randy Presuhn randy_pres...@mindspring.com writes:
Hi -
From: Ladislav Lhotka lho...@nic.cz
Sent: Aug 24, 2015 11:44 AM
To: Andy Bierman a...@yumaworks.com
Cc: netmod@ietf.org netmod@ietf.org
Subject: Re: [netmod] Y26 again, sorry
...
YANG does not provide any mechanism to REQUIRE modules A
Hi Martin,
as far as I can tell, these groupings are OK, and pyang also doesn't
complain.
Ahoj, Láďa
Martin Ciglan -X (mciglan - PANTHEON TECHNOLOGIES at Cisco)
mcig...@cisco.com writes:
Hello
I've come across a yang module which defines a short-case-stmt in
augment-stmt or
From: Andy Bierman, Friday, August 21, 2015 10:28 AM
snip
Currently we have a proprietary way of relocating YANG modules, and
ODL has its mount, and I think Andy has some other mechanism. Maybe
the time has come to standardize how mount works, and maybe then also
standardize the list of
Hello
I've come across a yang module which defines a short-case-stmt in augment-stmt
or uses-augment-stmt
Something like this:
grouping grp1 {
uses grp2 {
augment mychoice {
leaf myleaf1 {
type string;
}
}
}
}
grouping grp2 {
On 25 Aug 2015, at 14:48, Martin Bjorklund m...@tail-f.com wrote:
Ladislav Lhotka lho...@nic.cz wrote:
On 25 Aug 2015, at 14:01, Martin Bjorklund m...@tail-f.com wrote:
Hi,
I think this could work (thanks Robert; maybe this is what you
meant!):
container zones {
list zone {
On 25 Aug 2015, at 14:01, Martin Bjorklund m...@tail-f.com wrote:
Hi,
I think this could work (thanks Robert; maybe this is what you
meant!):
container zones {
list zone {
...
list rrset {
...
leaf type {
type identityref { ... }
}
Ladislav Lhotka lho...@nic.cz wrote:
On 25 Aug 2015, at 14:01, Martin Bjorklund m...@tail-f.com wrote:
Hi,
I think this could work (thanks Robert; maybe this is what you
meant!):
container zones {
list zone {
...
list rrset {
...
leaf type
11 matches
Mail list logo
