Subject: [Netconf] Issue #3 Support for notifications

From: Mahesh Jethanandani <[email-masked]>
Date: Mon, 25 Jun 2018 18:50:53 -0700

Since a question was raised in IETF 101, about support of binary encoding for notifications, have added an issue in GitHub at https://github.com/netconf-wg/binary-encoding/issues/3 <https://github.com/netconf-wg/binary-encoding/issues/3>,  that reads:

RFC 5277 defines notifications capability built on top of NETCONF. A notification is created by a request, where, once the subscription is created, it cannot be modified. Since binary encoding is currently suggesting a change in encoding format mid-stream (after the "hello" message), it is not foreseeable how encoding format could be changed for these subscriptions.

This might be different in the case of draft-ietf-netconf-subscribed-notifications, where subscribed notifications carry a 'encoding' attribute that can be used to not only specify a specific form of encoding at creation time, but can also be modified using 'subscription-modified'. The identity 'encoding' would have to be extended to support other forms of encoding, including 'cbor+sid’.

Comments/questions are welcome.

Mahesh Jethanandani
[email-masked]