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

Tianran Zhou <zhoutianran@huawei.com> Tue, 25 June 2019 07:59 UTC

Return-Path: <zhoutianran@huawei.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5277120236 for <netconf@ietfa.amsl.com>; Tue, 25 Jun 2019 00:59:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aV4gBAYaa5zp for <netconf@ietfa.amsl.com>; Tue, 25 Jun 2019 00:59:23 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EEE0120127 for <netconf@ietf.org>; Tue, 25 Jun 2019 00:59:23 -0700 (PDT)
Received: from lhreml706-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id D32E7CA6AD14BF982F9C for <netconf@ietf.org>; Tue, 25 Jun 2019 08:59:21 +0100 (IST)
Received: from lhreml706-chm.china.huawei.com (10.201.108.55) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 25 Jun 2019 08:59:21 +0100
Received: from lhreml706-chm.china.huawei.com (10.201.108.55) by lhreml706-chm.china.huawei.com (10.201.108.55) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Tue, 25 Jun 2019 08:59:21 +0100
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml706-chm.china.huawei.com (10.201.108.55) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1713.5 via Frontend Transport; Tue, 25 Jun 2019 08:59:21 +0100
Received: from NKGEML515-MBS.china.huawei.com ([169.254.5.134]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0415.000; Tue, 25 Jun 2019 15:59:06 +0800
From: Tianran Zhou <zhoutianran@huawei.com>
To: "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: New Version Notification for draft-zhou-netconf-multi-stream-originators-05.txt
Thread-Index: AQHVKymVikbFg4pw9E+hWuDNiqq4Raar/RuA
Date: Tue, 25 Jun 2019 07:59:05 +0000
Message-ID: <BBA82579FD347748BEADC4C445EA0F21BEE632C1@NKGEML515-MBS.china.huawei.com>
References: <156144856115.22899.11212877494632957803.idtracker@ietfa.amsl.com>
In-Reply-To: <156144856115.22899.11212877494632957803.idtracker@ietfa.amsl.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.156.116]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/GbrfX26dvv1jzCnD06MXLQtM7B4>
Subject: [netconf] FW: New Version Notification for draft-zhou-netconf-multi-stream-originators-05.txt
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jun 2019 07:59:26 -0000

Hi WG,

I just posted the update on the multi-stream-originators document.
Please review and comment.
Any suggestion is appreciated.

Many people show interest about this draft. And there are several comments from the 104 meeting.
1. It's still to be discussed if the IoT use case is suitable. In my opinion, this use case only meant to show that the sub/pub can use the mechanism proposed in this draft. The agent discovery and management is out of the scope. I am OK to remove this use case and focus on the multi-line cards one.
2. I checked and think both dynamic and configured subscription can be covered by the solution proposed.
3. I add a section on transport considerations to mention the congestion control requirement for transport. However, the solution proposed in document is transport independent.

In addition, I also correct the YANG model, add the IANA and security considerations.

Thanks,
Tianran

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Tuesday, June 25, 2019 3:43 PM
To: Andy Bierman <andy@yumaworks.com>om>; Eric Voit <evoit@cisco.com>om>; Zhengguangying (Walker) <zhengguangying@huawei.com>om>; Alexander Clemm <ludwig@clemm.org>rg>; Tianran Zhou <zhoutianran@huawei.com>
Subject: New Version Notification for draft-zhou-netconf-multi-stream-originators-05.txt


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

Name:		draft-zhou-netconf-multi-stream-originators
Revision:	05
Title:		Subscription to Multiple Stream Originators
Document date:	2019-06-25
Group:		Individual Submission
Pages:		17
URL:            https://www.ietf.org/internet-drafts/draft-zhou-netconf-multi-stream-originators-05.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-05
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-05

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