IETF Logo Mail Archive

Re: [netconf] Adoption Call for draft-mahesh-netconf-https-notif-00

Martin Bjorklund <mbj@tail-f.com> Mon, 16 September 2019 19:27 UTC

Return-Path: <mbj@tail-f.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 1C87812012E for <netconf@ietfa.amsl.com>; Mon, 16 Sep 2019 12:27:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 jcsooUg7PNZe for <netconf@ietfa.amsl.com>; Mon, 16 Sep 2019 12:27:29 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id C354B120131 for <netconf@ietf.org>; Mon, 16 Sep 2019 12:27:19 -0700 (PDT)
Received: from localhost (h-46-233.A165.priv.bahnhof.se [46.59.46.233]) by mail.tail-f.com (Postfix) with ESMTPSA id 125341AE0187; Mon, 16 Sep 2019 21:27:19 +0200 (CEST)
Date: Mon, 16 Sep 2019 21:27:18 +0200
Message-Id: <20190916.212718.107254905075592848.mbj@tail-f.com>
To: kent+ietf@watsen.net
Cc: zhoutianran@huawei.com, netconf@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <0100016d3ad2b4f2-e591bc21-9b47-49a0-81df-3e8d9ca23fce-000000@email.amazonses.com>
References: <0100016ccff35064-9da3c8b6-263c-47f6-a4f2-4db9495bc8b7-000000@email.amazonses.com> <BBA82579FD347748BEADC4C445EA0F21BEFB1420@NKGEML515-MBX.china.huawei.com> <0100016d3ad2b4f2-e591bc21-9b47-49a0-81df-3e8d9ca23fce-000000@email.amazonses.com>
X-Mailer: Mew version 6.7 on Emacs 25.2 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/0Fg1Lww5LS2gW2RUyvI1erZhHf8>
Subject: Re: [netconf] Adoption Call for draft-mahesh-netconf-https-notif-00
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: Mon, 16 Sep 2019 19:27:35 -0000

Kent Watsen <kent+ietf@watsen.net> wrote:
> 
> Hi Tianran,
> 
> 
> > Considering the multiple stream originator case, I would suggest this https-notif to add a channel level configuration.
> > i.e.
> >  
> > +--receivers
> >    +--receiver
> >       +--channels
> >          +--channel
> >             +--here put the http client server configurations
> >  
> > This is compatible with the single originator case with only one channel configuration.
> 
> We can look at this.  Maybe use a choice statement between the two options...

I don't think this is a good idea.  But then I don't really understand
the 'channel' concept.  I don't understand why the client needs to be
aware of these channels, but this should probably be discussed in a
separate thread.


/martin


> 
> Kent // co-author
> 
> 
> >  
> > If you do not like this, I think existing https-notif model also works.
> > i.e. each receiver configuration stands for one channel.
> > But this is not clear IMO.
> >  
> > Best,
> > Tianran

v2.28.0 | Report a Bug | By Email | System Status