< draft-zhou-netconf-multi-stream-originators-09.txt		draft-zhou-netconf-multi-stream-originators-10.txt >
	NETCONF T. Zhou		NETCONF T. Zhou
	Internet-Draft G. Zheng		Internet-Draft G. Zheng
	Intended status: Standards Track Huawei		Intended status: Standards Track Huawei
	Expires: May 3, 2020 E. Voit		Expires: May 7, 2020 E. Voit
	Cisco Systems		Cisco Systems
	A. Clemm		A. Clemm
	Futurewai		Futurewai
	A. Bierman		November 4, 2019
	YumaWorks
	October 31, 2019
	Subscription to Multiple Stream Originators		Subscription to Multiple Stream Originators
	draft-zhou-netconf-multi-stream-originators-09		draft-zhou-netconf-multi-stream-originators-10
	Abstract		Abstract
	This document describes the distributed data export mechanism that		This document describes the distributed data export mechanism that
	allows multiple data streams to be managed using a single		allows multiple data streams to be managed by using a single
	subscription. Specifically, multiple data streams are pushed		subscription. Specifically, device can decide to decompse one
	directly to the collector without passing through a broker for		subscription into multiple subscriptions to the line-cards. So that
	internal consolidation.		each line-card can directly push data to the collector without
			passing through a broker for internal consolidation. And the device
			can indicate the subscription decomposition result to the receiver to
			check the data integrity.
	Requirements Language		Requirements Language
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in RFC 2119 [RFC2119].		document are to be interpreted as described in RFC 2119 [RFC2119].
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	skipping to change at page 1, line 46 ¶		skipping to change at page 1, line 47 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at https://datatracker.ietf.org/drafts/current/.		Drafts is at https://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on May 3, 2020.		This Internet-Draft will expire on May 7, 2020.
	Copyright Notice		Copyright Notice
	Copyright (c) 2019 IETF Trust and the persons identified as the		Copyright (c) 2019 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 3, line 24 ¶		skipping to change at page 3, line 24 ¶
	of updates, rather than requiring updates to be tunneled through a		of updates, rather than requiring updates to be tunneled through a
	central server where they are combined. What is needed is a		central server where they are combined. What is needed is a
	distributed mechanism that allows to directly push multiple		distributed mechanism that allows to directly push multiple
	individual data substreams, without needing to first pass them		individual data substreams, without needing to first pass them
	through an additional processing stage for internal consolidation,		through an additional processing stage for internal consolidation,
	but still allowing those substreams to be managed and controlled via		but still allowing those substreams to be managed and controlled via
	a single subscription.		a single subscription.
	This document will describe such distributed data export mechanism		This document will describe such distributed data export mechanism
	and how it can work by extending existing push mechanism.		and how it can work by extending existing push mechanism.
	Specifically, this document asks the device to indicate the		Specifically, device can decide to decompse one subscription into
	subscription decomposition result to the receiver. The proposal will		multiple subscriptions to the line-cards. So that each line-card can
	focus on the scenario when data collection from devices with main-		directly push data to the collector without passing through a broker
	board and line-cards. It could be generalized to other distributed		for internal consolidation. And the device can indicate the
	data export scenarios.		subscription decomposition result to the receiver to check the data
			integrity. The proposal will focus on the scenario when data
			collection from devices with main-board and line-cards. It could be
			generalized to other distributed data export scenarios.
	2. Data Collection from Devices with Main-board and Line-cards		2. Data Collection from Devices with Main-board and Line-cards
	For data collection from devices with main-board and line-cards,		For data collection from devices with main-board and line-cards,
	existing push solutions consider only one push server typically		existing push solutions consider only one push server typically
	reside in the main board. As shown in the following figure, data are		reside in the main board. As shown in the following figure, data are
	collected from line cards and aggregate to the main board as one		collected from line cards and aggregate to the main board as one
	consolidated stream. So the main board can easily become the		consolidated stream. So the main board can easily become the
	performance bottle-neck. The optimization is to apply the		performance bottle-neck. The optimization is to apply the
	distributed data export mechanism which can directly push data from		distributed data export mechanism which can directly push data from
	skipping to change at page 22, line 36 ¶		skipping to change at line 960 ¶
	Email: evoit@cisco.com		Email: evoit@cisco.com
	Alexander Clemm		Alexander Clemm
	Futurewai		Futurewai
	2330 Central Expressway		2330 Central Expressway
	Santa Clara, California		Santa Clara, California
	United States of America		United States of America
	Email: ludwig@clemm.org		Email: ludwig@clemm.org
	Andy Bierman
	YumaWorks
	United States of America
	Email: andy@yumaworks.com
End of changes. 7 change blocks.
	15 lines changed or deleted		19 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/