Re: [netconf] New Version Notification for draft-zhou-netconf-multi-stream-originators-06.txt

I think your idea in this draft is to eliminate broker for internal consolidation at the sending side, but you introduce the new attribute message ID to multiplex multi-stream into one stream at the receiving side.
Two quick questions:
1. In dynamic subscription case, how does Publisher agent behind Publisher master know where a particular receiver is when pushing subscribed data to the receiver in a separate channel?
2. How multi-stream originator works for configured subscription case? How does receive know the number of publisher agents or message originators? Can receiver negotiate with publisher agent directly? What's the role of publisher master in between?

-Qin
-----邮件原件-----
发件人: netconf [mailto:netconf-bounces@ietf.org] 代表 Tianran Zhou
发送时间: 2019年7月8日 11:07
收件人: netconf@ietf.org
抄送: netconf-chairs@ietf.org
主题: [netconf] FW: New Version Notification for draft-zhou-netconf-multi-stream-originators-06.txt

Hi WG,

Thanks Kent for the remind of adding examples to illustrate the model usage.
1. This revision mainly work on the examples. 
2. We also add a grouping on the resource-access-list. So that some transport, e.g., RESTCONF, is able to access multiple message generators.

I think the document is ready for the working group adoption for further improvement.

There is an open discussion, whether to include the transport configuration in this document?
Existing subscribed notifications does not include this part. So this is for example defined in the https notif with a new "receivers" container.
https://datatracker.ietf.org/doc/draft-mahesh-netconf-https-notif/

In multiple message originators scenario, I prefer to leaving the transport configuration to specific transport just as the subscribed notifications draft.
So I add an example on how to configure the https notif in multiple message originators scenario.

Thanks,
Tianran
-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Monday, July 08, 2019 10:39 AM
To: Andy Bierman <andy@yumaworks.com>; Eric Voit <evoit@cisco.com>; Zhengguangying (Walker) <zhengguangying@huawei.com>; Alexander Clemm <ludwig@clemm.org>; Tianran Zhou <zhoutianran@huawei.com>
Subject: New Version Notification for draft-zhou-netconf-multi-stream-originators-06.txt

A new version of I-D, draft-zhou-netconf-multi-stream-originators-06.txt
has been successfully submitted by Tianran Zhou and posted to the IETF repository.

Name:		draft-zhou-netconf-multi-stream-originators
Revision:	06
Title:		Subscription to Multiple Stream Originators
Document date:	2019-07-07
Group:		Individual Submission
Pages:		21
URL:            https://www.ietf.org/internet-drafts/draft-zhou-netconf-multi-stream-originators-06.txt
Status:         https://datatracker.ietf.org/doc/draft-zhou-netconf-multi-stream-originators/
Htmlized:       https://tools.ietf.org/html/draft-zhou-netconf-multi-stream-originators-06
Htmlized:       https://datatracker.ietf.org/doc/html/draft-zhou-netconf-multi-stream-originators
Diff:           https://www.ietf.org/rfcdiff?url2=draft-zhou-netconf-multi-stream-originators-06

Abstract:
   This document describes the distributed data export mechanism that
   allows multiple data streams to be managed using a single
   subscription.  Specifically, multiple data streams are pushed
   directly to the collector without passing through a broker for
   internal consolidation.

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.

The IETF Secretariat

_______________________________________________
netconf mailing list
netconf@ietf.org
https://www.ietf.org/mailman/listinfo/netconf