Re: [Netconf] I-D Action: draft-ietf-netconf-udp-pub-channel-04.txt

["Eric Voit (evoit)" <[e-mail]>]

Hi Tianran,

The definition of dynamic subscription does allow for different transports to be used for notifications.   So I agree that augmenting “transport” into the <establish-subscription>  RPC is the way to accomplish this.  As a “transport” object already exists in the Data Nodes, this should be a minimalistic addition for supporting this.

The choice of the transport carrying the <establish-subscription> RPC itself does matter for your draft.  Section 4.1 does note that both NETCONF and RESTCONF can be used for signaling.  Looking at those two transport drafts:

·       For NETCONF, draft-ietf-netconf-netconf-event-notifications section 6, says: “ For dynamic subscriptions, all notification messages MUST use the NETCONF transport session used by the <establish-subscription> RPC.  Based on this, you will need to clarify the proper operation if you use that document as upon which to build your specification.

·       For RESTCONF, you will also need to decide if you will be building on top of draft-ietf-netconf-restconf-notif and its embedded YANG model.  In draft-ietf-netconf-restconf-notif, a separate session is used to make the connection for the notifications, and SSE is used.  Which is would need to be clarified quite a bit.

One other thing you might want to consider augmenting is the <establish-subscription>  RPC response.  draft-ietf-netconf-restconf-notif augments extra parameters into a successful response to an <establish-subscription>  request.    I believe a similar mechanism can be used in your draft to match what is needed to support the channels (b) in Fig 2.  Specifically, the <establish-subscription> response could be able to send a list of information component subscription servers from which notifications should be expected.

Additionally if you wanted,  information on Figure 2’s destination ports or addresses/ports could be augmented in as part of an <establish-subscription> request.  But whether that is needed is up to you.

Eric

From: Tianran Zhou, October 23, 2018 9:54 AM

Hi Martin,

Thank you for the review. You are right, that is also our concern on the dynamic subscription.
Is this operation legal by the dynamic subscription definition?
If so, we can augment the establish-subsciption RPC with an transport option.

Tianran
--------------------------------------------------
Sent from WeLink
发件人：Martin Bjorklund
收件人：[e-mail]<mailto:[e-mail]>,
时间：2018-10-22 21:48:43
主 题：Re: [Netconf] I-D Action: draft-ietf-netconf-udp-pub-channel-04.txt

Hi,

In section 4.1, this draft explains how a dynamic subscription can be
used with UPC.  How is this supposed to work?  There is no way to
indicate in an <establish-subscription> that the UPC protocol should
be used instead of sending <notifications> to the NETCONF client that
sent the <establish-subscription>.


/martin



[e-mail]<mailto:[e-mail]> wrote:
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Network Configuration WG of the IETF.
>
>         Title           : UDP based Publication Channel for Streaming Telemetry
>         Authors         : Guangying Zheng
>                           Tianran Zhou
>                           Alexander Clemm
>        Filename        : draft-ietf-netconf-udp-pub-channel-04.txt
>        Pages           : 22
>        Date            : 2018-10-19
>
> Abstract:
>    This document describes a UDP-based publication channel for streaming
>    telemetry use to collect data from devices.  A new shim header is
>    proposed to facilitate the distributed data collection mechanism
>    which directly pushes data from line cards to the collector.  Because
>    of the lightweight UDP encapsulation, higher frequency and better
>    transit performance can be achieved.
>
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-netconf-udp-pub-channel/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-netconf-udp-pub-channel-04
> https://datatracker.ietf.org/doc/html/draft-ietf-netconf-udp-pub-channel-04
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-netconf-udp-pub-channel-04
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> Netconf mailing list
> [e-mail]<mailto:[e-mail]>
> https://www.ietf.org/mailman/listinfo/netconf
>

_______________________________________________
Netconf mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/netconf