Subject: [netconf] netconf-config-change notification & YANG push for ordered-by user list

From: "Sterne, Jason (Nokia - CA/Ottawa)" <[email-masked]>
Date: Fri, 14 Aug 2020 17:25:01 +0000

Hi all,

What is the expected output for the RFC 6470 netconf-config-change notification in the following situation (after the commit) ? Note that the notification is not an edit-time notification. It is a notification intended to be sent after a commit (and actual change to the running).

Similar question -> what YANG Push notification(s) would we expect if someone had subscribed "on-change" to the running config?

A) YANG model

list foo {
   ordered-by user
   key "foo-name";
   leaf foo-name { type string; }
   leaf bar { type unit16; }
}

B) initial contents of running

foo red {
    bar 55
}
foo blue {
    bar 66
}
foo yellow {
    bar 77
}

C) edit the candidate so it contains this (change the order of blue and red)

foo blue {
    bar 66
}
foo red {
    bar 55
}
foo yellow {
    bar 77
}

D) commit

Questions:
Q1) contents of the netconf-config-change notification?
Q2) YANG PUSH notifications for an on-change subscription to the running config?

I see that RFC8072 (patch) has a concept of a "move" operation (RFC 6470 / 6241 doesn't have that). But patch could describe this change in a few different ways in theory (option 1 seems most ideal, but maybe it depends what the underlying system will do with the change).

OPTION 1:
--------------
- operation=move, target = foo red, point = foo blue, where = after

OPTION 2:
--------------
- delete foo red
- insert foo red after foo blue

OPTION 3:
-------------
- delete foo blue
- insert foo blue before foo red

RFC 6470 doesn't really seem to have those semantics.

Rgds,
Jason