Re: [6lo] Call for WG adoption of draft-li-6lo-native-short-address-03

Luigi IANNONE <luigi.iannone@huawei.com> Tue, 23 August 2022 15:47 UTC

Return-Path: <luigi.iannone@huawei.com>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFCEDC1522A8 for <6lo@ietfa.amsl.com>; Tue, 23 Aug 2022 08:47:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rlkQf0VCZmJr for <6lo@ietfa.amsl.com>; Tue, 23 Aug 2022 08:47:43 -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 68E43C1524B5 for <6lo@ietf.org>; Tue, 23 Aug 2022 08:47:43 -0700 (PDT)
Received: from fraeml709-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4MBtnZ1pDpz686w8; Tue, 23 Aug 2022 23:44:18 +0800 (CST)
Received: from dggpemm500002.china.huawei.com (7.185.36.229) by fraeml709-chm.china.huawei.com (10.206.15.37) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Tue, 23 Aug 2022 17:47:39 +0200
Received: from lhrpeml500002.china.huawei.com (7.191.160.78) by dggpemm500002.china.huawei.com (7.185.36.229) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Tue, 23 Aug 2022 23:47:37 +0800
Received: from lhrpeml500002.china.huawei.com ([7.191.160.78]) by lhrpeml500002.china.huawei.com ([7.191.160.78]) with mapi id 15.01.2375.024; Tue, 23 Aug 2022 16:47:35 +0100
From: Luigi IANNONE <luigi.iannone@huawei.com>
To: "Pascal Thubert (pthubert)" <pthubert=40cisco.com@dmarc.ietf.org>, Michael Richardson <mcr+ietf@sandelman.ca>
CC: "Liguangpeng (Roc, Network Technology Laboratory)" <liguangpeng@huawei.com>, 6lo <6lo@ietf.org>
Thread-Topic: [6lo] Call for WG adoption of draft-li-6lo-native-short-address-03
Thread-Index: AQHYpbcL/0Mtvwt2ykurFU1IGZMNo62wrE4AgAWE74CAACwYAIAAXxfAgABYvACAALmsgIAAd6AAgABniICAAOXrAIAAr+qAgAA90ICAAC5hgIAAb94AgABOwACAAVRXkA==
Date: Tue, 23 Aug 2022 15:47:35 +0000
Message-ID: <a27f793453344ae89d20257196240285@huawei.com>
References: <91f63618-ebbc-cdc6-b38e-d7b5a3d3e850@gmail.com> <5497C7A1-231D-414E-BCEF-956BB65298C2@gmail.com> <CACQW0Eq3_oFijtuKNcPV9rHrpiwPejBEjyVcktv0xACQGw-oSg@mail.gmail.com> <6066dc1b32a5406a94b0761a8b5d1251@huawei.com> <d640c88034da4c97817593ea6a7d6f75@huawei.com> <CACQW0EpiNuKMShika=R7Moz0n+ehgwzoiVCS=AUz5wG7ChBEeA@mail.gmail.com> <21673.1661026414@localhost> <f4c7e8966daf48e98f7653273f874b77@huawei.com> <12584.1661098022@localhost> <e43cd90127b84c6c9ddcb0f94fdd955f@huawei.com> <2BA3D49D-7E3F-4760-872B-80801466F59B@cisco.com> <bc6b7046cafa46d4ab8409d634bb2470@huawei.com> <21423.1661183056@localhost> <AC16A716-57F3-469A-AA7D-210AE5677997@cisco.com>
In-Reply-To: <AC16A716-57F3-469A-AA7D-210AE5677997@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.125.228.70]
Content-Type: multipart/alternative; boundary="_000_a27f793453344ae89d20257196240285huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/DkvYNhFWIunuXrAJeAMlxDe2eao>
Subject: Re: [6lo] Call for WG adoption of draft-li-6lo-native-short-address-03
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2022 15:47:45 -0000

Hi Pascal,



From: 6lo <6lo-bounces@ietf.org> On Behalf Of Pascal Thubert (pthubert)
Sent: Monday, 22 August 2022 22:26
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: Liguangpeng (Roc, Network Technology Laboratory) <liguangpeng@huawei.com>; 6lo <6lo@ietf.org>
Subject: Re: [6lo] Call for WG adoption of draft-li-6lo-native-short-address-03

I’m with you Michael

Though in the case of this proposal I would have one IP address per constrained Device and multiple L2NSA to account for the redundant networks.

I would thus not derive the IP from l2NSA but use a table eg a SCHC rule or a 6LoWPAN context to map the IP from the MAC.

[LI] You are creating some how an overlay here. Not sure how much this will help in the reliability case. You still need to guarantee reliability at L2.


I’m still left to be convinced that someone wants to deploy a network that must be carefully updated (only attach extensions after the last leaf) lest renumbering happens. A network that can not heal and will necessitate restart from scratch when some physical changes happen.

[LI] This is not the case. But we can discuss this more on a reliability thread.

Ciao

L.


I’m open to use cases like the DC sensors. Not sure that the simplicity of routing is worth the complexity in maintenance. Usually people prefer less human hassle and more protocol work than the other way around.

I’d probably deploy RPL there and possibly BIER too.

Keep safe;

Regards,

Pascal


Le 22 août 2022 à 17:44, Michael Richardson <mcr+ietf@sandelman.ca<mailto:mcr+ietf@sandelman.ca>> a écrit :

"Liguangpeng (Roc, Network Technology Laboratory)" wrote:

-----Original Message----- From: Pascal Thubert (pthubert)
<pthubert=40cisco.com@dmarc.ietf.org<mailto:pthubert=40cisco.com@dmarc.ietf.org>> Sent: Monday, August 22, 2022
2:18 PM To: Liguangpeng (Roc, Network Technology Laboratory)
<liguangpeng@huawei.com<mailto:liguangpeng@huawei.com>> Cc: Michael Richardson
<mcr+ietf@sandelman.ca<mailto:mcr+ietf@sandelman.ca>>; 6lo <6lo@ietf.org<mailto:6lo@ietf.org>> Subject: Re: [6lo] Call
for WG adoption of draft-li-6lo-native-short-address-03

Hello Guangpeng

If we take the DC sensors as use case and racks are organized in
trees, and you add a new rack then there will be renumbering.


No, it doesn't. Just attach this new rack to existing racks and don't
move existing racks to this new rack meanwhile. The latter action is
weird and superfluous.

no, what you suggest is weird.
More cables and more tangles.
(I still operate systems in cabinets in data centres)


Do it at L3 and you’re screwed.

BTW, I think derive IPv6 from L2 is not a reliable assumption
considering privacy issues and fake MAC problems. This is why we need
develop a short L3 address in 6lo.

Given a wired situation of sensors in a data center, I have no privacy concerns.
If we are talking about 100baseT1, then I also have no concern with packet size.

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