Re: [Netconf] WG adoption poll draft-voit-netconf-notification-messages-01

Hi,

I support the problem statement in this draft, but I have concerns
with the proposed solution.

Currently, the notification message is defined in RFC 5277, for both
NETCONF and RESTCONF.  It has a non-exensible header, and I agree that
it would be good to fix that.

We have a set of notfication-related documents that are supposed to
replace RFC 5277, to make it more flexible.  I think that one of the
documents in this set (not sure which one) needs to properly define a
new notification message, and introduce an extensibility mechanism for
the header.  Then a followup document (like
draft-voit-netconf-notification-messages) can use this extensibility
mechanism to define more common header fields.

On another level, I'm also worried that this becomes a kitchen-sink of
various headers that may or may not useful.  I would prefer an
initially small set of well thought-through headers, and work from
there.

I would like to see these concerns addressed before the WG adopts this
document.

/martin

Kent Watsen <kwatsen@juniper.net> wrote:
> 
> All,
> 
> This is start of a two-week poll on making the following draft a
> NETCONF working group document:
> 
>   draft-voit-netconf-notification-messages-01 [1]
> 
> Please send email to the list indicating "yes/support" or "no/do not
> support".  If indicating no, please state your reservations with the
> document.  If yes, please also feel free to provide comments you'd like
> to see addressed once the document is a WG document.
> 
> 
> [1] https://tools.ietf.org/id/draft-voit-netconf-notification-messages-01
> 
> 
> Thank you,
> Kent (and Mahesh)
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
> 