All,
This updates some compilation errors (in the examples) found in 00
Lyle
A new version of I-D, draft-bertz-netmod-commonaugment-01.txt
has been successfully submitted by Lyle Bertz and posted to the
IETF repository.
Name: draft-bertz-netmod-commonaugment
Revision: 01
Title:
Hi Lou,
> The charters from the last couple of years don't have the intended status
-- at least the ones we checked.
> I actually feel pretty strongly about this (which of course can be easily
overruled by our AD). It's my experience that premature discussions on
intended status, i.e.,
>
Hi Lou,
no issue at all, we can get in sync again. As I see in exchanged mails we
discussed to not hurry and to plan a joint session.
AFAIK the timing between 7950bis and NETCONF documents as well as the content
split is still subject to finalize.
It is not clear yet how and where to address
Understood.
Let's discuss at the meeting though. This was a significant issue in the
development of the IETF DMM FPC yang files and our open source project. I
am open to this going in the proper direction wherever that is but wanted
to bring the issue and a possible solution to the table.
"Bogaert, Bart (Nokia - BE)" wrote:
> So; to make this work the YANG property of the parent leaf in the config
> data tree should be set to false to allow a reference to hardware-state,
> correct?
It would be:
leaf parent {
type leafref {
path
Original Message -
From: "Andy Bierman"
To: "Kent Watsen"
Cc:
Sent: Wednesday, March 08, 2017 7:14 PM
> On Wed, Mar 8, 2017 at 10:56 AM, Kent Watsen
wrote:
>
> > > I think we can allow both and leave it to
So; to make this work the YANG property of the parent leaf in the config
data tree should be set to false to allow a reference to hardware-state,
correct?
Regards, Bart
Juergen Schoenwaelder wrote:
> On Wed, Mar 08, 2017 at 02:48:15PM +, Bogaert, Bart
> On 8 Mar 2017, at 20:34, Juergen Schoenwaelder
> wrote:
>
> On Wed, Mar 08, 2017 at 06:56:20PM +, Kent Watsen wrote:
>>
>> This way, reader can focus more quickly on the diffs, but also this
>> likely mimics what happened in reality (start with
On 08/03/2017 20:57, Kent Watsen wrote:
This way, reader can focus more quickly on the diffs, but also this
likely mimics what happened in reality (start with `pyang -f tree`
and then manually edit from there). What do you think?
Manually edited tree diagrams? I hope not. Perhaps we