Re: [Netconf] request for comments on draft-ietf-netconf-udp-pub-channel

Hi,

I have read draft-ietf-netconf-udp-pub-channel-02, but struggle with
some basics.

I don't understand how this new transport is supposed to fit into the
design of draft-ietf-netconf-subscribed-notifications.  For example,
the udp-pub-channel draft seems to expect a request to
"establish-subscription" over NETCONF to send the notifications over
UDP.  But AFAICT this is not possible with the current design of
establish-subscription.

Is the transport in this draft supposed to work for notifications in
general, or only YANG push notifications?

Also, it seems many of the references to yang-push really should be to
subscribed-notifications.

It would also be useful to align terminology with the other
documents.  It seems a "Master" is really the management protocol
server?  And "Agent" is what subscribed-notifications calls a
"publisher"?  Or maybe the "Master" is the "publisher"?

You also use the term "data originator", but I am not quite sure if
that is the same as "Agent"?

/martin

Tianran Zhou <zhoutianran@huawei.com> wrote:
> Hi WG,
> 
> We've got some comments on the UDP based Publication Channel for
> Streaming Telemetry. And we are going to update it, specifically on
> the security aspect.
> https://datatracker.ietf.org/doc/draft-ietf-netconf-udp-pub-channel/ 
> 
> Could you please help to review?
> Any comment is appreciated.
> 
> Thanks,
> Tianran
> 
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
> 