Re: [Iotops] IOTOPS Draft Charter

"Panwei (William)" <william.panwei@huawei.com> Thu, 12 November 2020 01:34 UTC

Return-Path: <william.panwei@huawei.com>
X-Original-To: iotops@ietfa.amsl.com
Delivered-To: iotops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49E223A130F for <iotops@ietfa.amsl.com>; Wed, 11 Nov 2020 17:34:44 -0800 (PST)
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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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 lKNg74PrboUZ for <iotops@ietfa.amsl.com>; Wed, 11 Nov 2020 17:34:42 -0800 (PST)
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 E91033A1308 for <iotops@ietf.org>; Wed, 11 Nov 2020 17:34:41 -0800 (PST)
Received: from fraeml738-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4CWkd71TQqz67HTF; Thu, 12 Nov 2020 09:33:15 +0800 (CST)
Received: from nkgeml704-chm.china.huawei.com (10.98.57.158) by fraeml738-chm.china.huawei.com (10.206.15.219) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Thu, 12 Nov 2020 02:34:39 +0100
Received: from nkgeml705-chm.china.huawei.com (10.98.57.154) by nkgeml704-chm.china.huawei.com (10.98.57.158) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Thu, 12 Nov 2020 09:34:37 +0800
Received: from nkgeml705-chm.china.huawei.com ([10.98.57.154]) by nkgeml705-chm.china.huawei.com ([10.98.57.154]) with mapi id 15.01.1913.007; Thu, 12 Nov 2020 09:34:37 +0800
From: "Panwei (William)" <william.panwei@huawei.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, Alexey Melnikov <alexey.melnikov@isode.com>, "Rob Wilton (rwilton)" <rwilton@cisco.com>, "iotops@ietf.org" <iotops@ietf.org>
Thread-Topic: [Iotops] IOTOPS Draft Charter
Thread-Index: Adax30q2qgoRJah6TfKWMxRovMp5tP//zwiAgAddDoCABav7AP//bv2Q
Date: Thu, 12 Nov 2020 01:34:37 +0000
Message-ID: <a77093403c814c9d980340afd2f3e1b3@huawei.com>
References: <MN2PR11MB4366A96960B97A66D3383045B5110@MN2PR11MB4366.namprd11.prod.outlook.com> <31244.1604425849@localhost> <6A9B1079-86EE-478A-9044-D676471CE1D6@isode.com> <26359.1605142472@localhost>
In-Reply-To: <26359.1605142472@localhost>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.99.125]
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/iotops/lxTTaq817leUFtEJiAd_I8KJ790>
Subject: Re: [Iotops] IOTOPS Draft Charter
X-BeenThere: iotops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IOT Operations <iotops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iotops>, <mailto:iotops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iotops/>
List-Post: <mailto:iotops@ietf.org>
List-Help: <mailto:iotops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iotops>, <mailto:iotops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Nov 2020 01:34:48 -0000

+1

Regards & Thanks!
Wei Pan

> -----Original Message-----
> From: Iotops [mailto:iotops-bounces@ietf.org] On Behalf Of Michael
> Richardson
> Sent: Thursday, November 12, 2020 8:55 AM
> To: Alexey Melnikov <alexey.melnikov@isode.com>; Rob Wilton (rwilton)
> <rwilton@cisco.com>; iotops@ietf.org
> Subject: Re: [Iotops] IOTOPS Draft Charter
> 
> 
> Alexey Melnikov <alexey.melnikov@isode.com> wrote:
>     >> On 3 Nov 2020, at 17:50, Michael Richardson
> <mcr+ietf@sandelman.ca> wrote:
>     >>
>     >> To me, the point was to deal with the lifecycle issues of IoT.
>     >> That's one the list in point (1) was about.
> 
>     > If the proposed WG to work on lifecycle issues: do you think these
>     > would be extensions to protocols done elsewhere in IETF, new
> protocols
>     > or something else?
> 
> Well, all three.
> 
> I think that the WG should first look for available existing protocols.
> Said protocols might need profiles and/or new code points to deal with the
> specific situation.  Such a document could occur in an active WG, if one
> exists, but it could be that the WG is no longer alive.
> 
> I feel it very unlikely that there would be new protocols from scratch.
> But, say, some variation of webdav to do configuration
> management/updates?
> Or a YANG module?  Or an extension to the CAPPORT API? (assuming that
> WG concludes) A document giving a series of EAT (RATS) claims?
> 
> Under "something else", I would include adopting work that has occured in
> some industry-specific vertical, under the whole "Informational 1.0", and
> "IETF Change-Controlled 2.0" pattern.
> 
> Plus, of course, the handful of MUD extensions, and another handful of IoT
> focused BRSKI extensions.
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT
> consulting )
>            Sandelman Software Works Inc, Ottawa and Worldwide