IETF Logo Mail Archive

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

Kent Watsen <kent+ietf@watsen.net> Wed, 11 September 2019 05:15 UTC

Return-Path: <0100016d1ebfb4e0-9a8da9f1-686e-4d72-b682-e13338db20db-000000@amazonses.watsen.net>
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 7D04512026E for <netconf@ietfa.amsl.com>; Tue, 10 Sep 2019 22:15:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.com
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 mKuxALeyJHkL for <netconf@ietfa.amsl.com>; Tue, 10 Sep 2019 22:15:45 -0700 (PDT)
Received: from a8-83.smtp-out.amazonses.com (a8-83.smtp-out.amazonses.com [54.240.8.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C73C4120168 for <netconf@ietf.org>; Tue, 10 Sep 2019 22:15:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1568178943; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=rTPBYyg22g1SbxqX5hX37DH3dT7brnc3GjXgSaJKYZ4=; b=adYsc6kL+Y5oye8IhjPxonZjGn/0S9gqipzis9zDrHedbG3kStjWfze2L0yHCxl4 hJ0dbQWNgIc1AGQoRXl7JsBUgSXQCtJ9WPKx/bhzvCgjw72/fMtfo4OutB5JgD7hq/e CHNpwr7JvncleCA+idmCl/m9950zY+n7HjzLdUOI=
From: Kent Watsen <kent+ietf@watsen.net>
Message-ID: <0100016d1ebfb4e0-9a8da9f1-686e-4d72-b682-e13338db20db-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_96BA2B1A-C6C7-43F5-B618-7846BF2ED3C7"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Wed, 11 Sep 2019 05:15:43 +0000
In-Reply-To: <E6BC9BBCBCACC246846FC685F9FF41EA2DAF6B83@DGGEMM527-MBX.china.huawei.com>
Cc: "netconf@ietf.org" <netconf@ietf.org>
To: wangzitao <wangzitao@huawei.com>
References: <E6BC9BBCBCACC246846FC685F9FF41EA2DAF6B83@DGGEMM527-MBX.china.huawei.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-SES-Outgoing: 2019.09.11-54.240.8.83
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/hLPU-1kjolX3Yyidow2ozd5C2LI>
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: Wed, 11 Sep 2019 05:15:47 -0000

Hi Michael,

> IMHO, this model can be used in call-home scenarios, for example the server can initiate a transport session to those receivers in the subscription using the address and port specified. 
> Therefore, I suggest to add some attributes, such as Listen Port, to support call-home.

I'm not entirely sure I follow you.   

Firstly, the draft is describing the NC/RC server initiating a protocol connection to a remote peer (the receiver).  So, in this since, it is "call home" already.

That said, maybe you mean "call home" in the sense of protocol-reversals (e.g., reverse TLS).  If so, note that the protocol being discussed here is more like Syslog than RESTCONF.   If it were Syslog, would you also to think there is a need to have a protocol-reversal?

Kent // as co-author

v2.23.0 | Report a Bug | By Email