IETF Logo Mail Archive

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

"Liguangpeng (Roc, Network Technology Laboratory)" <liguangpeng@huawei.com> Tue, 23 August 2022 04:48 UTC

Return-Path: <liguangpeng@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 C473AC1522C8 for <6lo@ietfa.amsl.com>; Mon, 22 Aug 2022 21:48:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, 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=ham 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 uvpmgNVY--oB for <6lo@ietfa.amsl.com>; Mon, 22 Aug 2022 21:48:44 -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 6F512C1522BB for <6lo@ietf.org>; Mon, 22 Aug 2022 21:48:44 -0700 (PDT)
Received: from fraeml738-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4MBcDg3S6Kz67MmR; Tue, 23 Aug 2022 12:48:19 +0800 (CST)
Received: from dggpemm500001.china.huawei.com (7.185.36.107) 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.2375.24; Tue, 23 Aug 2022 06:48:40 +0200
Received: from dggpemm500004.china.huawei.com (7.185.36.219) by dggpemm500001.china.huawei.com (7.185.36.107) 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 12:48:39 +0800
Received: from dggpemm500004.china.huawei.com ([7.185.36.219]) by dggpemm500004.china.huawei.com ([7.185.36.219]) with mapi id 15.01.2375.024; Tue, 23 Aug 2022 12:48:39 +0800
From: "Liguangpeng (Roc, Network Technology Laboratory)" <liguangpeng@huawei.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
CC: 6lo <6lo@ietf.org>
Thread-Topic: [6lo] Call for WG adoption of draft-li-6lo-native-short-address-03
Thread-Index: AQHYpbcKGargMhUv+EOL6QnUF5qTP62wNvUAgAWE74CAACwYAIAAVbmAgADd29CAAD3rgIAAd6AAgADnRKCAAGYvAIABMrhQgABYRACAAV8ioA==
Date: Tue, 23 Aug 2022 04:48:39 +0000
Message-ID: <33704cc0ef56415ea05632a282d2564d@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> <20127.1661182844@localhost>
In-Reply-To: <20127.1661182844@localhost>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.235.213]
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/6lo/jBmabgMiI86IARRzmc2Sa4J_ROc>
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 04:48:46 -0000


> -----Original Message-----
> From: Michael Richardson <mcr+ietf@sandelman.ca>
> Sent: Monday, August 22, 2022 11:41 PM
> To: Liguangpeng (Roc, Network Technology Laboratory)
> <liguangpeng@huawei.com>
> Cc: 6lo <6lo@ietf.org>
> Subject: Re: [6lo] Call for WG adoption of draft-li-6lo-native-short-address-03
> 
> 
> "Liguangpeng (Roc, Network Technology Laboratory)" wrote:
>     > Thanks for the clarification. Please see below:
>     >> If I insert a new device in the tree, then all of the tree below that
>     >> device has to renumber.
> 
>     > Technically saying, it may exist but it seems weird to insert a new
>     > device in the middle of the tree.
> 
> Let's say that I have a device with four physical ports.
> Port 3 is being used to speak to the rank-1.
> Port 2 and Port 4 are being used to speak to downstream systems.
> Port 1 is empty.  New device goes on port 1.
> 
> Isn't that a renumber too?
> Maybe there was a device on port 1 before, and it was removed.
> 
Which device is renumbered you think in this scenario? According to NSA, the new device may get a new address that is different from removed port1's device (considering the address of original port1's device may have not been release yet). 

>     > When a user wants a new device, a
>     > normal way is append them to the network at the end of an existing
>     > rank.
> 
> This is going to be a total fail once remote hands are involved.
> The only use case we have so far is sensors in a data center
> 
The sensors in DC scenario just makes the use case clear and concrete. It represents a range of use cases.

>     >> I also think that it can happen if I add a new device to an existing
>     >> rank.
> 
>     > No, as long as there is enough address for this new device.
> 
> And if there isn't?
> 
What happens if you want add the 256th device to a subnet with /24 IPv4 address block?
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
>            Sandelman Software Works Inc, Ottawa and Worldwide
> 
> 
>

v2.23.0 | Report a Bug | By Email