Re: [6lo] PASA smart home use case

Zhe Lou <zhe.lou@huawei.com> Tue, 15 November 2022 08:14 UTC

Return-Path: <zhe.lou@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 C23AEC14CE55 for <6lo@ietfa.amsl.com>; Tue, 15 Nov 2022 00:14:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 8oaV_aA_wM6V for <6lo@ietfa.amsl.com>; Tue, 15 Nov 2022 00:14:12 -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 1DD65C14F723 for <6lo@ietf.org>; Tue, 15 Nov 2022 00:14:12 -0800 (PST)
Received: from frapeml500002.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4NBJk44c3vz67yqV; Tue, 15 Nov 2022 16:09:32 +0800 (CST)
Received: from frapeml500004.china.huawei.com (7.182.85.22) by frapeml500002.china.huawei.com (7.182.85.205) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Tue, 15 Nov 2022 09:14:08 +0100
Received: from frapeml500004.china.huawei.com ([7.182.85.22]) by frapeml500004.china.huawei.com ([7.182.85.22]) with mapi id 15.01.2375.031; Tue, 15 Nov 2022 09:14:08 +0100
From: Zhe Lou <zhe.lou@huawei.com>
To: Esko Dijk <esko.dijk@iotconsultancy.nl>, "6lo@ietf.org" <6lo@ietf.org>
Thread-Topic: PASA smart home use case
Thread-Index: Adj4EXRaoxonJI6mSlWwQ7YUhrnUFwADmL7AAAbARBAAI3DLgA==
Date: Tue, 15 Nov 2022 08:14:08 +0000
Message-ID: <3132b6b662464937a4ae9d64031e765b@huawei.com>
References: <DU0P190MB19780BA254BBDEE4142C680EFD059@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM> <2881aaeb422744d79c953939b0ccfefb@huawei.com> <DU0P190MB1978B72A3EF2B07076D65729FD059@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM>
In-Reply-To: <DU0P190MB1978B72A3EF2B07076D65729FD059@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.81.215.176]
Content-Type: multipart/alternative; boundary="_000_3132b6b662464937a4ae9d64031e765bhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/2eYCkq5c3EIgEQQEFEcOR2njS6Y>
Subject: Re: [6lo] PASA smart home use case
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, 15 Nov 2022 08:14:16 -0000

Hi Esko,

You are right. Although the home gateway is also capable of providing internet access for laptops, TVs, etc., those devices can, but not necessarily to be included into the PASA network as the new addressing doesn’t provide too much gain for them.

We will update the figure 2 in the next version.

Regards
David

From: Esko Dijk [mailto:esko.dijk@iotconsultancy.nl]
Sent: Monday, 14 November 2022 16:25
To: Zhe Lou <zhe.lou@huawei.com>; 6lo@ietf.org
Subject: RE: PASA smart home use case

Thanks David,

It would be nice to add some clarification for this, indeed. E.g. the Ethernet link between Home Gateway and one PLC GW could be explicitly drawn. Now it’s not so clear where the Home Gateway link is going (it interferes with the ASCII art room boxes).

Also how the PLC network as drawn relates to the user’s further Wi-Fi / internet-access home network, would be useful to just mention. From what I read the Home Gateway provides also the internet access for other devices (laptop, TV, smartphone, etc). But these are not necessarily participating in the PASA addressing if they are on high-speed segments of the home network.

The type of powerline technology you refer is being used as an Ethernet replacements (so multi-Mbps speeds), I wonder if this is still of interest to the 6lo WG?
I would consider more constrained PLC use cases to be better targets for 6lo / PASA type technology, e.g. something with very low speed (like <= 500 kbps) or severe packet size limitations (<  100-500 bytes).

Regards
Esko

From: Zhe Lou <zhe.lou@huawei.com<mailto:zhe.lou@huawei.com>>
Sent: Monday, November 14, 2022 13:13
To: Esko Dijk <esko.dijk@iotconsultancy.nl<mailto:esko.dijk@iotconsultancy.nl>>; 6lo@ietf.org<mailto:6lo@ietf.org>
Subject: RE: PASA smart home use case

Hi Esko,

Thanks for comments. In fact the second interpretation is closer. The Home Gateway is the PASA root. However, the connection from the Home Gateway to the PLC GWs is combination of Ethernet and PLC. More precisely, the Home Gateway connects to a PLC GW (e.g. gwR) via Ethernet. Then this gwR connects to other PLC GWs via PLC. Herewith one example from Telenet, I used at home. This device offers both PLC and Ethernet interfaces
https://www2.telenet.be/nl/business/klantenservice/wat-is-powerline-en-hoe-installeren/
(Although in Dutch, I think you can read it :)

In such, we create at least 2 levels where PASA could be applied.

I can update the figure accordingly if you prefer.

Kind regards
David


From: 6lo [mailto:6lo-bounces@ietf.org] On Behalf Of Esko Dijk
Sent: Monday, 14 November 2022 11:47
To: 6lo@ietf.org<mailto:6lo@ietf.org>
Subject: [6lo] PASA smart home use case

Hi PASA authors,

As requested in the 6lo WG meeting I’m relaying my comments on the smart home use case (section 3.2 of draft-li-6lo-path-aware-semantic-addressing-00).

In Fig 2, it could be clarified better where the PASA Root sits (i.e. the root and 6lo Border Router as depicted in the architecture Fig 5). A first assumption I had was that each PLC GW contains a PASA root, because the PLC network segment beneath it is the constrained 6lowpan network technology benefitting from PASA addressing.  Then each PLC segment has to deal with constrained nodes and constraints on the network throughput (i.e. low-speed PLC). In this case, the link connecting all the PLC gateways and the Home Gateway would be another e.g. high-speed (Ethernet, Wi-Fi) technology. This link uses in typical homes its own existing addressing which may be based on SLAAC or DHCPv6 delegated prefix via CPE / Home Gateway, or ULAs, or something else. The HomeNet WG defined solutions for such addressing using a new protocol I think and SNAC WG is now aiming to provide solutions for that as well that re-use already-present protocols & products in the home. That would not use PASA addresses and there seems to be no need to do that.

But, another interpretation of this figure is that Home Gateway provides the PASA Root. In this case all underlying devices including PLC Gateways themselves will get a PASA assigned address. This then would suggest that the link connecting the PLC GWs and Home Gateway is another kind of wired link, not PLC. What would this link technology be like -- is Ethernet assumed?  In this case where would the other home devices like laptops, smartphones, wireless smart home devices etc., be connected? It could be to a separate network that is not shown and that doesn’t use PASA addressing. Or maybe these devices are not shown but are on the same Ethernet link, not using PASA addresses but another type (the DHCPv6 / SLAAC / ULA / SNAC solutions mentioned above).

In summary, it’s hard for me to understand the current use case because not fully clear which interpretation of the 2 above I should assume.

In case of interpretation 1, the diagram does not show any tree topology per PLC network so I don’t understand yet why using PASA addresses here would be useful? SLAAC would work equally well. The diagram suggests that all PLC devices in a segment can talk to all other PLC devices in the segment in a single hop – no tree. That suggests all PLC devices are leaf devices. Is that intended? I recall there are also PLC technologies that build a tree when some device can’t reach the GW in one hop.

Regards
Esko Dijk


IoTconsultancy.nl  |  Email/Teams: esko.dijk@iotconsultancy.nl<mailto:esko.dijk@iotconsultancy.nl>