[netconf] suggest to consider multiple message originators//RE: New Version Notification for draft-mahesh-netconf-https-notif-00.txt

Tianran Zhou <zhoutianran@huawei.com> Wed, 10 July 2019 01:36 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 213CE120077 for <netconf@ietfa.amsl.com>; Tue, 9 Jul 2019 18:36:43 -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 Ys8EB5hwaaGm for <netconf@ietfa.amsl.com>; Tue, 9 Jul 2019 18:36:41 -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 CF3D012001E for <netconf@ietf.org>; Tue, 9 Jul 2019 18:36:40 -0700 (PDT)
Received: from lhreml709-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 6A897BB8B663FF8D8664; Wed, 10 Jul 2019 02:36:38 +0100 (IST)
Received: from lhreml707-chm.china.huawei.com (10.201.108.56) by lhreml709-cah.china.huawei.com (10.201.108.32) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 10 Jul 2019 02:36:38 +0100
Received: from lhreml707-chm.china.huawei.com (10.201.108.56) by lhreml707-chm.china.huawei.com (10.201.108.56) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Wed, 10 Jul 2019 02:36:37 +0100
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by lhreml707-chm.china.huawei.com (10.201.108.56) 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; Wed, 10 Jul 2019 02:36:37 +0100
Received: from NKGEML515-MBS.china.huawei.com ([169.254.5.134]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0415.000; Wed, 10 Jul 2019 09:36:31 +0800
From: Tianran Zhou <zhoutianran@huawei.com>
To: Mahesh Jethanandani <mjethanandani@gmail.com>, Netconf <netconf@ietf.org>
Thread-Topic: suggest to consider multiple message originators//RE: New Version Notification for draft-mahesh-netconf-https-notif-00.txt
Thread-Index: AdU2vkNwf7i6e/TxTYq3YWQjfpnTeA==
Date: Wed, 10 Jul 2019 01:36:30 +0000
Message-ID: <BBA82579FD347748BEADC4C445EA0F21BEE7E779@NKGEML515-MBS.china.huawei.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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/YmIh2l1xGJUq5gYwvrzcwnRphPg>
Subject: [netconf] suggest to consider multiple message originators//RE: New Version Notification for draft-mahesh-netconf-https-notif-00.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: Wed, 10 Jul 2019 01:36:43 -0000

Hi Mahesh,

When preparing a configured subscription example for multiple message originators. I think your proposal in draft-mahesh-netconf-https-notif-00 could easily adapt to multiple message originators scenario.
You can see my example in A.2 in draft-zhou-netconf-multi-stream-originators-06. 
I suggest to include a list of channels in the receiver configuration. On one hand, it can support the multiple message originators scenario. On the other hand, one channel configuration can be compatible with existing sub-notif.

Cheers,
Tianran

> -----Original Message-----
> From: netconf [mailto:netconf-bounces@ietf.org] On Behalf Of Mahesh
> Jethanandani
> Sent: Thursday, June 27, 2019 8:44 AM
> To: Netconf <netconf@ietf.org>
> Subject: [netconf] Fwd: New Version Notification for
> draft-mahesh-netconf-https-notif-00.txt
> 
> Just posted this new draft.
> 
> As the introduction says, the Subscribed Notifications draft defines a YANG
> module for configuring subscribed notifications. That module defines a
> subscription container that contains a list of receivers. But that draft
> defers the configuration and management of the receivers to other documents.
> This draft defines one of those transports and how to configure it.
> 
> Comments are welcome.
> 
> > Begin forwarded message:
> >
> >
> > A new version of I-D, draft-mahesh-netconf-https-notif-00.txt
> > has been successfully submitted by Mahesh Jethanandani and posted to
> > the IETF repository.
> >
> > Name:		draft-mahesh-netconf-https-notif
> > Revision:	00
> > Title:		An HTTPS-based Transport for Configured Subscriptions
> > Document date:	2019-06-26
> > Group:		Individual Submission
> > Pages:		11
> > URL:
> https://www.ietf.org/internet-drafts/draft-mahesh-netconf-https-notif-00
> .txt
> > Status:
> https://datatracker.ietf.org/doc/draft-mahesh-netconf-https-notif/
> > Htmlized:
> https://tools.ietf.org/html/draft-mahesh-netconf-https-notif-00
> > Htmlized:
> https://datatracker.ietf.org/doc/html/draft-mahesh-netconf-https-notif
> >
> >
> > Abstract:
> >   This document defines a YANG data module for configuring HTTPS based
> >   configured subscription, as defined I-D.ietf-netconf-subscribed-
> >   notifications.  The use of HTTPS maximizes transport-level
> >   interoperability, while allowing for encoding selection from text,
> >   e.g.  XML or JSON, to binary.
> >
> >
> >
> >
> > 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
> >
> 
> Mahesh Jethanandani
> mjethanandani@gmail.com
> 
> 
> 
> _______________________________________________
> netconf mailing list
> netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf