> The list's key nodes are encoded as subelements to the list's
>identifier element, in the same order as they are defined within the
>"key" statement.
I read as the sentence above already implies that an out of order key is an not
ok,
Otherwise why bother to specify it?
When
Andy Bierman writes:
> Where does is say the server MUST reject list keys provided by the client
> that are out of order? Where does is say what error-tag is returned?
Maybe this is due to my inexperience, but I read the text of 7.8.4, "A
list is encoded ..." as "When
Andy Bierman wrote:
> Hi,
>
> YANG 1.1, sec. 7.8.4 says:
>
>The list's key nodes are encoded as subelements to the list's
>identifier element, in the same order as they are defined within the
>"key" statement.
>
>The rest of the list's child nodes are
Hi,
YANG 1.1, sec. 7.8.4 says:
The list's key nodes are encoded as subelements to the list's
identifier element, in the same order as they are defined within the
"key" statement.
The rest of the list's child nodes are encoded as subelements to the
list element, after the keys.
t.petch wrote:
> Martin
>
> Is there any changelog available for the last four versions? The log I
> see stops at -10.
No :( You'll have to use rfcdiff (which OTOH has the benefit that it
is guearanteed to be correct :)
/martin
>
> Tom Petch
>
>
> - Original
Martin
Is there any changelog available for the last four versions? The log I
see stops at -10.
Tom Petch
- Original Message -
From: "Ladislav Lhotka"
To: "Andy Bierman"
Cc:
Sent: Monday, June 20, 2016 6:58 AM
Subject: Re: