Re: [netconf] [core] some comments on netconf-adaptive-subscription

Qin Wu <bill.wu@huawei.com> Fri, 25 June 2021 17:12 UTC

Return-Path: <bill.wu@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 F34D23A0BF1; Fri, 25 Jun 2021 10:12:10 -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, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, 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 53H_1TjRMAYX; Fri, 25 Jun 2021 10:12:06 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 017E43A0BF0; Fri, 25 Jun 2021 10:12:06 -0700 (PDT)
Received: from fraeml710-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4GBNdr5098z6G8LR; Sat, 26 Jun 2021 01:04:32 +0800 (CST)
Received: from dggeml751-chm.china.huawei.com (10.1.199.150) by fraeml710-chm.china.huawei.com (10.206.15.59) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2176.2; Fri, 25 Jun 2021 19:12:03 +0200
Received: from dggeml753-chm.china.huawei.com (10.1.199.152) by dggeml751-chm.china.huawei.com (10.1.199.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Sat, 26 Jun 2021 01:12:01 +0800
Received: from dggeml753-chm.china.huawei.com ([10.1.199.152]) by dggeml753-chm.china.huawei.com ([10.1.199.152]) with mapi id 15.01.2176.012; Sat, 26 Jun 2021 01:12:00 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, "netconf@ietf.org" <netconf@ietf.org>, "core@ietf.org" <core@ietf.org>
Thread-Topic: [core] some comments on netconf-adaptive-subscription
Thread-Index: Addp5FkYCLrfoHWHSouJ7G0uLCP+5w==
Date: Fri, 25 Jun 2021 17:12:00 +0000
Message-ID: <a9f3f2dd6ceb48f4a45ed5ef866978d7@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.52.202.106]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/GOpvvPHrLVMb25r-ON6WbzPV3SE>
Subject: Re: [netconf] [core] some comments on netconf-adaptive-subscription
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: Fri, 25 Jun 2021 17:12:11 -0000

-----邮件原件-----
发件人: Michael Richardson [mailto:mcr+ietf@sandelman.ca] 
发送时间: 2021年6月26日 0:58
收件人: Qin Wu <bill.wu@huawei.com>om>; netconf@ietf.org; core@ietf.org
主题: Re: [core] some comments on netconf-adaptive-subscription

Qin Wu <bill.wu@huawei.com> wrote:
    mcr> I didn't finish my thought here.  Specifically, it seems that the CORE
    mcr> WG is doing a lot of stuff with CoAP Observes and SENML and all sorts
    mcr> of interesting triggers.

    Qin> data modeling language such as YANG can be common work for both CORE
    Qin> WG and NETCONF WG, But they may choose different transport protocol,
    Qin> such as NETCONF, RESTCONF, HTTP 2.0, COAP, MQTT, COMI Secondly, I
    Qin> think it will be nice to separate constrained device management from
    Qin> resource unconstrained network device management, Constraint device
    Qin> as IoT device can be temperature sensor, current, voltage sensor
    Qin> which can be seen as affiliated devices pertaining to resource
    Qin> unstrained network device.

temperature, current are critical values for routing equipment, aren't they?

[Qin]: My understanding is yes, there is hardware YANG model which can be used to collect these inventory data associated with the routing equipment
See RFC8348.

    Qin> In data center scenarios, we do see a lot of such affiliated devices or
    Qin> sensors such as air conditioner, water leakage alarm sensor deployed
    Qin> together with data center switch devices.  These IoT devices only
    Qin> use MQTT/COAP/HTTP to communicate with their IoT platform, for data
    Qin> center switch devices, you may still rely on network management
    Qin> protocols such as NETCONF, SNMP, gRPC, etc.  Do you see this
    Qin> differently? Michael?

It seems that we ought to seek convergence here.
That's what I'm saying.  That any split here is for historical reasons, and does not make sense going forward.

[Qin]: Tend to agree, unified data modeling or semantics interoperability may be the solution. One of example is to
Build digital twin data model and models sensor data and network device health data together.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide