[lp-wan] Comments to the [lpwan] Overview re: Wi-SUN characteristics

Charlie Perkins <charles.perkins@earthlink.net> Wed, 19 July 2017 04:08 UTC

Return-Path: <charles.perkins@earthlink.net>
X-Original-To: lp-wan@ietfa.amsl.com
Delivered-To: lp-wan@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF25E1274D0 for <lp-wan@ietfa.amsl.com>; Tue, 18 Jul 2017 21:08:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level:
X-Spam-Status: No, score=-2.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=earthlink.net; domainkeys=pass (2048-bit key) header.from=charles.perkins@earthlink.net header.d=earthlink.net
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 OIyKhT8wDuDE for <lp-wan@ietfa.amsl.com>; Tue, 18 Jul 2017 21:08:01 -0700 (PDT)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 058D91270AC for <lp-wan@ietf.org>; Tue, 18 Jul 2017 21:08:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=earthlink.net; s=dk12062016; t=1500437281; bh=UGpUzgBzBB+50q6SxpyJBH15yPFnn/wGskxz z6PgAQE=; h=Received:Subject:References:To:From:Cc: X-Forwarded-Message-Id:Message-ID:Date:User-Agent:MIME-Version: In-Reply-To:Content-Type:Content-Language:X-ELNK-Trace: X-Originating-IP; b=jtM3L+qI3frLaH61bqvdtLoirxhcdXqV7fylmJJBCZeGbo iR9HfxSVuq8Ic9jqkVNtoAC7MrTnxsZVKLy5mdEFZb5sY6OK6vlnFtdihDJy5pt9KtZ f5ecXWJba0eIlawsov/EQjc5bjR1Jixpr1KwTtQ6dbkTIVn2bNpfXNW/qb5A8uQFsnc l6ZX/W5HtFHJxKWm4eJrTB1b8HSSN2rcgfx2jbRljcfUZwrKzWspvnr5+6oMyq+NvdF 2T+8vZcmRgGIDp/X48/0i5Hc5n8Hkk+jQxyYO7Ztm9tlQV2RkXt2fmCUeE2pUOYNa82 aLkYQH5FKq77iwV+NahgJvi7sW/g==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016; d=earthlink.net; b=iFlHKgT2kV1LtJZKzvQrkVNPHBRoxU+zEonTLe1VEKSq3rLlt82pmBPys64r4GglGTe3PRYCm2HjXcSU/XZfjhZkSs4dhe2CjjEfi7WBULBL1tfsHKh2VDk9tdTi3v1MelcYtvcqMHnnagwBIworOrIYjF3/TLkJWSQCVKf0YKkJsPDbXaMCR1+MQ/KK+aKdZKR57x5tWdnTmgroofxpSJ7LSish6DN/Ihi0fGmLfeYC3Qz57aoWqY0ufvsHdmvY09cX2VuNhbx6AQm2Gye4zOIxmsO3OK9mmVgPhLesBZF54OLiV0C4lW/Yi0IPcMievxlzfmAw6brAxrOFxu6C7A==; h=Received:Subject:References:To:From:Cc:X-Forwarded-Message-Id:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Language:X-ELNK-Trace:X-Originating-IP;
Received: from [31.133.157.127] by elasmtp-galgo.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1dXgH7-000EnF-I8; Wed, 19 Jul 2017 00:07:49 -0400
References: <6f22c5a9-60f6-3995-f8e5-79f0443ff748@earthlink.net>
To: lp-wan <lp-wan@ietf.org>
From: Charlie Perkins <charles.perkins@earthlink.net>
Cc: Bob Heile <bheile@ieee.org>, Mingui Zhang <zhangmingui@huawei.com>, Remy Liubing <remy.liubing@huawei.com>, Jonathan Muñoz <jonathan.munoz@inria.fr>
X-Forwarded-Message-Id: <6f22c5a9-60f6-3995-f8e5-79f0443ff748@earthlink.net>
Message-ID: <d124d204-cf9f-cd83-b731-c2820b993913@earthlink.net>
Date: Tue, 18 Jul 2017 21:07:47 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <6f22c5a9-60f6-3995-f8e5-79f0443ff748@earthlink.net>
Content-Type: multipart/mixed; boundary="------------A556DCA9E7EC0E57B422A2BC"
Content-Language: en-US
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956846b590522b13c95a430b483b5cfea8607ec5b6c5ae5293a350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 31.133.157.127
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/9j3Sx9A0mZKI5Mc9nG9LMHlTOV4>
Subject: [lp-wan] Comments to the [lpwan] Overview re: Wi-SUN characteristics
X-BeenThere: lp-wan@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Low-Power Wide Area Networking \(LP-WAN\), also known as LPWA or Low-Rate WAN \(LR-WAN\)" <lp-wan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lp-wan>, <mailto:lp-wan-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lp-wan/>
List-Post: <mailto:lp-wan@ietf.org>
List-Help: <mailto:lp-wan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lp-wan>, <mailto:lp-wan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 04:08:03 -0000

Hello folks,

I'd like to suggest some additional text to be included in the Wi-SUN 
overview section of the document.  I think it is important to emphasize 
the following characteristics.  These comments can be viewed as more or 
less the distillation of information described at longer length in our 
individual Internet Draft contribution submitted earlier about Wi-SUN.  
We have received many comments about that draft, and it needs to be 
significantly revised and resubmitted as soon as possible.  But the 
[lpwan] Overview document is in Last Call, and we don't have time to 
revise our individual draft before the end of Last Call.

Given a little more time after this busy week, I would also like to 
include a fuller description about the Wi-SUN mesh protocol choices.  If 
that is acceptable, I will provide text next week.

Regards,
Charlie P.
-----------------------------------------------------------------------------------------------------------

-Coverage

The range of Wi-SUN FAN is typically 2~3 km in line of sight, matching 
the needs of neighborhood area networks, campus area networks, or 
corporate area networks. The range can also be extended via multi-hop 
networking.

- High bandwidth, low latency

Wi-SUN's relatively high bandwidth, i.e. up to 300 kbps [FANTPS], 
enables remote update and upgrade of devices so that they can handle new 
applications, extending their working life. Some IoT applications may 
require on-demand control, e.g. on-demand metering in AMI, device 
control in distribution automation. Wi-SUN supports these requirements 
by providing high bandwidth, low latency (0.02s) and bi-directional 
communication.

- Low power consumption

FAN devices draw less than 2 uA when resting and only 8 mA when 
listening [COM]. Such devices can maintain a long lifetime even if they 
are frequently listening. For instance, suppose the device transmits 
data for 10 ms once every 10 s; theoretically, a battery of 1000 mAh can 
last more than 10 years.

- Mesh topology

Wi-SUN FAN mesh networks offer self-forming and self-healing 
capabilities. When a new device is powered up, it can automatically 
discover communication peers. If the link is interrupted by obstacles, a 
device can switch to alternative redundant paths. The reliability of 
Wi-SUN has been proven for years in harsh and remote environments.

- Scalability

10s of millions Wi-SUN FAN devices have been deployed all over the 
world, including several deployments with more than 1 million devices 
[COM]. This demonstrates the scalability of Wi-SUN FAN in urban, 
suburban and rural environments.


The following references could be added in the LPWAN overview draft:

[COM] Wi-SUN Alliance, “Comparing IoT Networks at a Glance”, May 2017.

[FANTPS] Wi-SUN Alliance, "Technical Profile Specification Field Area 
Network", May 2016.

Figure.8 needs a column for Wi-SUN:

Another paragraph could be added regarding the Wi-SUN security solution, 
something along the following lines.

    Wi-SUN has made it a design goal to rely on industry standard
    security solutions instead of special-purpose or proprietary
    methods.  In this way, users and equipment vendors can have a high
    degree of confidence that their system will truly be secure. 
    Moreover it will be easier to provide secure interfaces to other
    system modules and components, which are more likely to support
    standard security protocols without special purpose coding.

--------------------------------------------------------------------------------------------------------------------------

Regards,
Charlie P.