[6lo] About the IID construction in 6lo-WBAN

"Houjianqiang (Derek)" <houjianqiang@huawei.com> Fri, 17 November 2017 02:48 UTC

Return-Path: <houjianqiang@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 32CE1127B60 for <6lo@ietfa.amsl.com>; Thu, 16 Nov 2017 18:48:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level:
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 uNsHtfIP7Iaq for <6lo@ietfa.amsl.com>; Thu, 16 Nov 2017 18:48:17 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 62D9F126B71 for <6lo@ietf.org>; Thu, 16 Nov 2017 18:48:14 -0800 (PST)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id ED7FEB4BD4B48 for <6lo@ietf.org>; Fri, 17 Nov 2017 02:48:11 +0000 (GMT)
Received: from DGGEMM406-HUB.china.huawei.com (10.3.20.214) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.361.1; Fri, 17 Nov 2017 02:48:12 +0000
Received: from DGGEMM506-MBS.china.huawei.com ([169.254.4.18]) by DGGEMM406-HUB.china.huawei.com ([10.3.20.214]) with mapi id 14.03.0361.001; Fri, 17 Nov 2017 10:48:01 +0800
From: "Houjianqiang (Derek)" <houjianqiang@huawei.com>
To: "dthaler@microsoft.com" <dthaler@microsoft.com>, "Rahul Arvind Jadhav (Rahul Arvind Jadhav, 2012 Labs)" <rahul.jadhav@huawei.com>
CC: "6lo@ietf.org" <6lo@ietf.org>
Thread-Topic: About the IID construction in 6lo-WBAN
Thread-Index: AdNfTlbvc08UcUWmQCOc0QjWVKlz2Q==
Date: Fri, 17 Nov 2017 02:48:01 +0000
Message-ID: <DD0A994E4D6B3F4080662703C8C7C086A9321C@DGGEMM506-MBS.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.52.37.182]
Content-Type: multipart/alternative; boundary="_000_DD0A994E4D6B3F4080662703C8C7C086A9321CDGGEMM506MBSchina_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/D_GqqI2sH3XdFPMhUVw_rCy4zNU>
Subject: [6lo] About the IID construction in 6lo-WBAN
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 17 Nov 2017 02:48:21 -0000

Hi Dave and Rahul,

Thanks for your valuable comments on the IID construction in 6lo-WBAN. Since I am one of the co-authors, it is my pleasure to provide more information of the current IID construction in this draft:

There are two kinds of nodes in a WBAN, namely BAN coordinator and BAN nodes (not sure whether I name them correctly). Each BAN coordinator holds an 8-bit BAN ID. BAN nodes need to associate with the BAN coordinator using MAC48 address, then the BAN coordinator allocates an 8-bit short address to each BAN node. When multiple BAN coordinators exist in a subnet, each BAN coordinator holds an unique BAN ID after negotiations. So, the BAN ID and the 8-bit node address are not built-in constant addresses in a WBAN device, and the current IID construction method in the draft guarantees its uniqueness inside a subnet.

Regards,
Jianqiang Hou (Derek)

draft-sajjad-6lo-wban-01
https://datatracker.ietf.org/doc/draft-sajjad-6lo-wban/