https-notif draft issue presented at 107 virtual meeting

Mandatory encoding issue

RFC 8639 states that the "encoding" leaf is "mandatory false". When not specified, then the underlying "notif" transport (or out-of-band mechanism) is to provide a means to identify which encoding to use.

The current "https-notif" draft already supports an ability for the publisher to discover which encoding(s) a receiver supports. Please note that, in any of the options below, other encodings (e.g, CBOR) MAY also be supported.

Please select one of the following.

Question Title

* 1. Please sort (drag-n-drop) your preferences

Let the market decide

Publisher MUST implement JSON encoding

Publisher MUST implement XML encoding

Publisher MUST implement JSON and XML encoding

Receiver MUST implement JSON encoding

Receiver MUST implement XML encoding

Receiver MUST implement JSON and XML encoding