Re: [netconf] WGLC: draft-ietf-netconf-https-notif-06

Hi,

I reviewed draft-07 that was just published.

It seems too much of the language is limited to XML or JSON encoding.
The media type extensibility should be well-defined so this draft
does not have unintended limitations later on.

There is a significant architectural change made without any real mention
(sec. 4)
In NETCONF and RESTCONF, a notification is a one-way message, meaning there
is no application layer response whatsoever.

That is not the case here. Instead, the publisher sends an HTTPS POST for
every notification
and expects a "204 No Content" response for each one.
The draft should explain the reasons for this change.
HTTP client implementations tend to wait for a response to a POST.
That is probably not what is intended here, but no text explains the
details.

Sec. 4 does not mention what the publisher is supposed to do if the
receiver does not
send a response or sends something other than 204.  It seems like this
redundant ACK
adds complexity and network traffic for no benefit.

Andy

On Thu, Jan 14, 2021 at 5:12 AM Rob Wilton (rwilton) <rwilton=
40cisco.com@dmarc.ietf.org> wrote:

> This message begins a two-week WGLC for draft-ietf-netconf-https-notif-06
> ending on Jan 28.  Here is a direct link to the HTML version of the draft:
>
>         https://tools.ietf.org/html/draft-ietf-netconf-https-notif-06
>
> Positive comments, e.g., "I've reviewed this document and believe it is
> ready for publication", are welcome!  This is useful and important, even
> from authors.  Objections, concerns, and suggestions are also welcomed at
> this time.
>
> Please note, the reason that I am making this request rather than the
> WG chairs is because both chairs are listed as authors on this document.
>
> Thank you,
> Rob Wilton, OPS AD
>
> _______________________________________________
> netconf mailing list
> netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
>