IETF Logo Mail Archive

Re: [Netconf] a joint discussion on dynamic subscription

Tianran Zhou <zhoutianran@huawei.com> Thu, 14 June 2018 11:42 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 DEC36130F52 for <netconf@ietfa.amsl.com>; Thu, 14 Jun 2018 04:42:51 -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 egIxSwWnajOF for <netconf@ietfa.amsl.com>; Thu, 14 Jun 2018 04:42:50 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 CE5C5130EB9 for <netconf@ietf.org>; Thu, 14 Jun 2018 04:42:49 -0700 (PDT)
Received: from LHREML713-CAH.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 7CCC0347293D2; Thu, 14 Jun 2018 12:42:45 +0100 (IST)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by LHREML713-CAH.china.huawei.com (10.201.108.36) with Microsoft SMTP Server (TLS) id 14.3.382.0; Thu, 14 Jun 2018 12:42:47 +0100
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0382.000; Thu, 14 Jun 2018 19:42:33 +0800
From: Tianran Zhou <zhoutianran@huawei.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Martin Bjorklund <mbj@tail-f.com>
CC: "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [Netconf] a joint discussion on dynamic subscription
Thread-Index: AdQCx01ede4gaRHPTgG2WyMdkd0r2gARka+AABfQcAAAAsUAAAACxI2AABQ6gYA=
Date: Thu, 14 Jun 2018 11:42:32 +0000
Message-ID: <BBA82579FD347748BEADC4C445EA0F21B55CE3BC@NKGEML515-MBX.china.huawei.com>
References: <BBA82579FD347748BEADC4C445EA0F21B55CCDB7@NKGEML515-MBX.china.huawei.com> <b256b91c7cbc4b3093c858e55c912f88@XCH-RTP-013.cisco.com> <20180614.091828.21142123428745204.mbj@tail-f.com> <20180614.103746.8291316293283106.mbj@tail-f.com> <20180614095701.74rqetmhark3tzpd@anna.jacobs.jacobs-university.de>
In-Reply-To: <20180614095701.74rqetmhark3tzpd@anna.jacobs.jacobs-university.de>
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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/ZDj48MitaBtAzYqWBVtI-CAH0r4>
Subject: Re: [Netconf] a joint discussion on dynamic subscription
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Network Configuration WG mailing 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: Thu, 14 Jun 2018 11:42:52 -0000

I am not sure if the figure 3 in draft-zhou-netconf-multi-stream-originators can help to explain.
In this distributed data collection scenario, each stream originator include two components. One for subscription, one for publication.

                  +-------------------------------------+
                  |      Collector      +-------------+ |
                  |                    +|-----------+ | |
                  |   +------------+   || Receiver  | <-----+
                  |   | Subscriber |   |+-------------+ |   |
                  |   +-^----+-----+   +------------+   |   |
                  |     |    |                |         |   |
                  +-------------------------------------+   |
             Global     |    |Global          | push        |
             Capability |    |Subscription    |             |
                  +-------------------------------------+   |
                  |     |    |   Master       |         |   |
                  |  +--+----v------+  +------+------+  |   |
                  |  | Subscription |  | Publisher   |  |   |
                  |  | Server       |  |             |  |   |
                  |  +--^----+------+  +-------------+  |   |
                  |     |    |                          |   |
                  +-------------------------------------+   |
             Component  |    | Component               push |
             Capability |    | Subscription                 |
                  +-------------------------------------+   |
                  |     |    |   Agent                  |   |
                  |  +--+----v------+  +-------------+  |   |
                  |  | Component    |  | Publisher   |  |   |
                  |  | Subscription |  |             +------+
                  |  | Server       |  +-------------+  |
                  |  +--------------+                   |
                  +-------------------------------------+

         Fig. 3 The Generic Distributed Data Collection Framework

> -----Original Message-----
> From: Netconf [mailto:netconf-bounces@ietf.org] On Behalf Of Juergen
> Schoenwaelder
> Sent: Thursday, June 14, 2018 5:57 PM
> To: Martin Bjorklund <mbj@tail-f.com>
> Cc: netconf@ietf.org
> Subject: Re: [Netconf] a joint discussion on dynamic subscription
> 
> On Thu, Jun 14, 2018 at 10:37:46AM +0200, Martin Bjorklund wrote:
> >
> > Also, I think it would be useful to draw a picture that demonstrates
> > the roles:
> >
> >       subscriber/client    receiver
> >           |                   ^
> >           | (1)               | (3)
> >           |                   |
> >           |                   |
> >           v        (2)        |
> >         server  ----------> publisher
> >
> > (1) is creation of the subscriptionE; dynamic or configured
> > (2) is implementation specific
> > (3) is the delivery of notifications / event records
> >
> > NOTE: the subscriber and receiver MAY be the same entity
> > NOTE: for some transports, if (1) is dynamic, (3) is sent over the
> >       same session as (1)
> > NOTE: for some transports, the sevrer and publisher are the same
> > entity
> 
> So why do we need the distinct role of a publisher?
> 
> > If we can agree on an architectural picture like this, the different
> > transport docs can refer to this architecture and be defined related
> > to it.   For example, the netconf transport doc can state that the
> > publisher is always the same entity etc.
> 
> So we introduce the role of a publisher because of some transports that do
> have a server? If the publisher is truely distinct entity from the server
> (and the state it has), we may get interesting security considerations to
> write.
> 
> /js
> 
> --
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   +49 421 200 3103         <https://www.jacobs-university.de/>
> 
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf

v2.23.0 | Report a Bug | By Email