- Original Message -
From: "Juergen Schoenwaelder"
To: "Martin Bjorklund"
Cc:
Sent: Monday, January 11, 2016 10:48 AM
> On Mon, Jan 11, 2016 at 11:21:43AM +0100, Martin Bjorklund wrote:
> > Juergen Schoenwaelder
On Thu, Jan 14, 2016 at 9:32 AM, t.petch wrote:
> - Original Message -
> From: "Juergen Schoenwaelder"
> To: "Martin Bjorklund"
> Cc:
> Sent: Monday, January 11, 2016 10:48 AM
>
> > On Mon,
Anees,
I am trying to understand (again/still) exactly what your (openconfig)
intention is re applied config.
First, re. pre-configuration.
draft-openconfig-netmod-opstate-01.txt says:
It is notable that the intended configuration and the applied
configuration represent exactly the same
"Martin Ciglan -X (mciglan - PANTHEON TECHNOLOGIES at Cisco)"
wrote:
> Dear all
>
> We've come across following set of import statements in YANG file:
>
> import a {
> prefix "a0";
> }
>
> import a {
> prefix "a1";
> }
>
> So, there is one module imported with 2
Ladislav Lhotka wrote:
>
> > On 14 Jan 2016, at 10:28, Martin Bjorklund wrote:
> >
> > "Martin Ciglan -X (mciglan - PANTHEON TECHNOLOGIES at Cisco)"
> > wrote:
> >> Dear all
> >>
> >> We've come across following set of import statements in
> On 14 Jan 2016, at 10:28, Martin Bjorklund wrote:
>
> "Martin Ciglan -X (mciglan - PANTHEON TECHNOLOGIES at Cisco)"
> wrote:
>> Dear all
>>
>> We've come across following set of import statements in YANG file:
>>
>> import a {
>>prefix "a0";
>> }
Hi all
Thank you for sharing your knowledge.
Obviously, we see the point of importing different revisions of very same
module,
but in our case, revision is only one, so, that's why we've checked with you.
Thanks.
Best Regards
Martin
Od:
Hi,
the module "ietf-netconf-acm" defines its own instance-identifier type
(node-instance-identifier) in order to be able to refer to multiple instances
in one rule. This has some drawbacks because generic tools cannot recognize it
as an instance-identifier, so for example automatic