Re: [Netconf] a joint discussion on dynamic subscription

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Thu, 14 June 2018 12:05 UTC

Return-Path: <j.schoenwaelder@jacobs-university.de>
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 A4F23131062 for <netconf@ietfa.amsl.com>; Thu, 14 Jun 2018 05:05:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.136
X-Spam-Level:
X-Spam-Status: No, score=0.136 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, LONGWORDS=2.035, URIBL_BLOCKED=0.001] autolearn=no 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 glb_v8L8W0FP for <netconf@ietfa.amsl.com>; Thu, 14 Jun 2018 05:05:58 -0700 (PDT)
Received: from anna.localdomain (anna.eecs.jacobs-university.de [IPv6:2001:638:709:5::7]) by ietfa.amsl.com (Postfix) with ESMTP id C280B126F72 for <netconf@ietf.org>; Thu, 14 Jun 2018 05:05:57 -0700 (PDT)
Received: by anna.localdomain (Postfix, from userid 501) id 9CBE02239F08; Thu, 14 Jun 2018 14:05:56 +0200 (CEST)
Date: Thu, 14 Jun 2018 14:05:55 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Tianran Zhou <zhoutianran@huawei.com>
Cc: Martin Bjorklund <mbj@tail-f.com>, "netconf@ietf.org" <netconf@ietf.org>
Message-ID: <20180614120555.sh2d2zef6cfhmuqz@anna.jacobs.jacobs-university.de>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Tianran Zhou <zhoutianran@huawei.com>, Martin Bjorklund <mbj@tail-f.com>, "netconf@ietf.org" <netconf@ietf.org>
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> <BBA82579FD347748BEADC4C445EA0F21B55CE3BC@NKGEML515-MBX.china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BBA82579FD347748BEADC4C445EA0F21B55CE3BC@NKGEML515-MBX.china.huawei.com>
User-Agent: NeoMutt/20180512
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/C44ip8DnMt00sRk7CEsP4q8So4E>
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 12:06:00 -0000

Well, if I fail to understand four terms, it usually does not help me
much to add a couple of additional terms that I do not understand
either. Note that device internal mechanisms likely should remain
device internal implementation details and not subject to any
standardization. Whether this applies to your figure or not, I do not
know (since I do not know what the figure tells me, see first remark).

/js

On Thu, Jun 14, 2018 at 11:42:32AM +0000, Tianran Zhou wrote:
> 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

-- 
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/>