Should this draft add base sn:configurable-encoding to the https identity?

[mjethanandani]

Background on this issue. See this email thread - https://mailarchive.ietf.org/arch/msg/netconf/DhpmlJ98bd33CLOh-lkJ7q1yiGI/

and, in particular this email from Thomas.

Apologies. I was wrong. Andy is correct. "base sn:configurable-encoding;" should be added to the transport protocol identities and an errata to https://datatracker.ietf.org/doc/html/rfc8639#appendix-A should be filed. Errata 8073 should be rejected.

See: https://mailarchive.ietf.org/arch/msg/netconf/BRzA6DoJKgQd1twikAalC8TNqzE/

Reviewing

https://datatracker.ietf.org/doc/html/draft-ietf-netconf-https-notif#section-6.2
 identity https {
   base sn:transport;
   description
     "HTTPS transport for notifications.";
 }

https://datatracker.ietf.org/doc/html/draft-ietf-netconf-udp-notif#section-7.2
 identity udp-notif {
   base sn:transport;
   base sn:configurable-encoding;
   description
     "UDP-Notif is used as transport for notification messages
       and state change notifications.";
 }

It appears that draft-ietf-netconf-https-notif is missing the update.