Subject: [netconf] Issue #1 Can binary be an added option to the encoding mechanism

From: Mahesh Jethanandani <[email-masked]>
Date: Tue, 14 Jan 2020 17:00:50 -0800

The above issue was opened on GitHub to track support for binary encoding of notifications in draft-ietf-netconf-https-notification draft. The question is how does a publisher learn of the receiver capabilities, including its ability to receive binary encoded notifications.

The original suggestion was to use OPTIONS method in HTTP to learn receivers capability. It turns out that OPTIONS does not have a header that can be used for this purpose. Martin suggested using Accept-Post, but the IETF draft that suggested that header has expired, and we are not clear on the support for it.

Therefore, the current proposal is to use GET with a specific Content-Type that returns metadata, i.e. an ordered set of encodings.

Comments/Questions?

Mahesh Jethanandani
[email-masked]