IETF Logo Mail Archive

Re: [6lo] WG last call on draft-ietf-6lo-blemesh-04

"Bilhanan Silverajan (TAU)" <bilhanan.silverajan@tuni.fi> Tue, 29 January 2019 14:04 UTC

Return-Path: <bilhanan.silverajan@tuni.fi>
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 D2D2A129AB8 for <6lo@ietfa.amsl.com>; Tue, 29 Jan 2019 06:04:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.043
X-Spam-Level:
X-Spam-Status: No, score=-2.043 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=tuni.onmicrosoft.com
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 rjTUP2jMnrah for <6lo@ietfa.amsl.com>; Tue, 29 Jan 2019 06:04:15 -0800 (PST)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-am5eur03on0708.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe08::708]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 705E91277CC for <6lo@ietf.org>; Tue, 29 Jan 2019 06:04:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tuni.onmicrosoft.com; s=selector1-tuni-fi; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=DJMG8R38fXtu9mV04OGdii5FLD/nzfOIkTv6ea47/28=; b=YJORWHhlQ4/E7xBJrimUd6TRsFfy9aP/FCfIaOYPGxNN0CR1Ru3CtpxqIdpDgsnncqGJU2h7gr1vRzMrbVBn4FqH76iWpSjo1MSrsnUIoukPf2nBjf1UbHMwCgSPT93+o1xcfHdgEJEWlpHZej9QVJWpg6mhDIe2FEdZmCn7cNY=
Received: from AM0PR08MB4482.eurprd08.prod.outlook.com (20.179.35.148) by AM0PR08MB4068.eurprd08.prod.outlook.com (20.178.119.161) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1558.16; Tue, 29 Jan 2019 14:04:12 +0000
Received: from AM0PR08MB4482.eurprd08.prod.outlook.com ([fe80::3153:75ac:94d6:58ab]) by AM0PR08MB4482.eurprd08.prod.outlook.com ([fe80::3153:75ac:94d6:58ab%3]) with mapi id 15.20.1558.023; Tue, 29 Jan 2019 14:04:12 +0000
From: "Bilhanan Silverajan (TAU)" <bilhanan.silverajan@tuni.fi>
To: "6lo@ietf.org" <6lo@ietf.org>
Thread-Topic: WG last call on draft-ietf-6lo-blemesh-04
Thread-Index: AQHUt9uCrq6Lo4Nx00KZ3yoKlpi40w==
Date: Tue, 29 Jan 2019 14:04:12 +0000
Message-ID: <25fb202b-ba4a-0e89-5f0c-619ad80f87e2@tuni.fi>
Accept-Language: en-IE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: HE1PR0902CA0012.eurprd09.prod.outlook.com (2603:10a6:3:e5::22) To AM0PR08MB4482.eurprd08.prod.outlook.com (2603:10a6:208:145::20)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=bilhanan.silverajan@tuni.fi;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [2001:708:310:156:ec4c:cf3f:7783:9068]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM0PR08MB4068; 6:pcLFth1BC2FexytOfM2NhHaVXj0IHEoSPYXq5tVRUeIcRu0RDG5DBTvuEmkdmHamPB6XNK5hV67O6IBXuMo+KwUKDy8HsPJ0tdSf+eKQ0de3MfQtBGDfIOXOe//JGUgygzsu8IvAHOYoEvv5JffXW+8wjATjVndUaQw+rjGoeVhXUdpuA3yMpoZZ7UeO8UTjjRcAvyiBo5k5J5oSz5eL1Ggs0tvNrZBw4Dcv5XH5FK3OF17pGjDJcVLY9WEGTnIK/8bd8Zq+DBEcZjgkxiTuToa1iiQtKCnRJlxsTnfXCGrbr9dD1zRavZuoEvacrlhk0PypIwoANgc2+ddvz/PbMkt1H10ftpLiZz92bZr09vKUO8sW6fNhmGfyRcG7s0G00Wi1/klB5rRGFUmw3FH/AvdKnBloX7gGgKS57ANzVKE+kB1g/eTu80ZXG9cUF59eSpYw+nZtfOYAFKPfNjaVkg==; 5:NtmJKJ2BTZB7fBdwOXa1NJtX860TP/Gnqf4vfyPo8ZB0AFF1V6JqUr0qIly3/I9Dek1ZWqCb9Qdq+gdt+DsxuMGChrcXWjQEt0/I3RvZ0ESat+gxzIWv6LW7i36GzYZkk6vWwHuH+GfpXaJqYLuobFXDB7SEA5c0bIIGcT1XbRK3j1s2V47udOIACJTDrhoFcknk4Io30XCvgQVNX0ZBqA==; 7:yxCYFEriLrtvusq0lKRsDrXhtLg/psvSp7SMZTlYWU55iqxZxcNSX6rzQMA/CWwg3k41zH4K0YiHgJmoEWhCwHHq352wf0y3TfuQC4LsWPbGfdLWj6ns2zAADtotaJ8lNvjJGG6IinvljDeGVOb6rw==
x-ms-office365-filtering-correlation-id: f56fe89d-c925-4634-701c-08d685f2a542
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600110)(711020)(4605077)(2017052603328)(7153060)(7193020); SRVR:AM0PR08MB4068;
x-ms-traffictypediagnostic: AM0PR08MB4068:
x-microsoft-antispam-prvs: <AM0PR08MB4068D589C673C9B1874C1587EF970@AM0PR08MB4068.eurprd08.prod.outlook.com>
x-forefront-prvs: 093290AD39
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(396003)(136003)(376002)(366004)(346002)(53754006)(199004)(189003)(386003)(14444005)(8936002)(256004)(6486002)(229853002)(105586002)(7736002)(2351001)(106356001)(74482002)(97736004)(31686004)(31696002)(6916009)(305945005)(86362001)(46003)(2616005)(186003)(6116002)(2501003)(102836004)(786003)(476003)(14454004)(53936002)(486006)(478600001)(36756003)(6246003)(71200400001)(81156014)(81166006)(99286004)(5640700003)(25786009)(2906002)(8676002)(71190400001)(68736007)(6436002)(316002)(52116002)(6512007)(6506007); DIR:OUT; SFP:1102; SCL:1; SRVR:AM0PR08MB4068; H:AM0PR08MB4482.eurprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: tuni.fi does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: B8cgKn63dhdTG+nXbN+uiTze471WCM5DDXNqOEgu27/0lmOEu0g6CeZE3HdSu5kiI1WIhZ0CwtaTODBvrVIayvpQxmgV3A5u55ca+OTN747Q1KetEaCE4i7RQ16fVuVe6srOtolHTO/nhKBDw/SA9rVpzqRteYnRUP2p0L22Sag/NyD4TZEedqguOEtxnm5oSfBOtccJ0tYbOJi7tZ4mlMrQRIcW/tpICC6Xk8BkuWieqrv49MB62jieo4dfMaPxN9Q8XZoEbuLYEDRjmj3BYRFKcdCuFjQJ+oUYdHliHFCFYrpVBf0lOb2AgxvmKnWCdy7Xf1ms+1AX/L1bKKRB8gQJJ/dRHyRU33ZSjeClZMLbfKXg81gHjLfqLjPJUqtWZXLBrpz3wxFXyHHW+JeRWzJc7jz/OuIeXBsTFL07iz4=
Content-Type: text/plain; charset="utf-8"
Content-ID: <C594C6B6F7BD484BB52B556BEF237111@eurprd08.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: tuni.fi
X-MS-Exchange-CrossTenant-Network-Message-Id: f56fe89d-c925-4634-701c-08d685f2a542
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Jan 2019 14:04:11.8476 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: fa6944af-cc7c-4cd8-9154-c01132798910
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR08MB4068
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/G6kNRzWrHKHrSM7nyflYVZ8BHe8>
Subject: Re: [6lo] WG last call on draft-ietf-6lo-blemesh-04
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.29
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, 29 Jan 2019 14:04:19 -0000

Hi all,

I read the draft and I think this is an important work particularly to 
extend RFC 7668 from its existing star topology. I have the following 
comments:

* In several places, the phrase "IPv6 over mesh networks composed of BLE 
links" is used. In others, the phrase "IPv6 mesh over Bluetooth LE" is 
used, while I also discovered "IPv6-enabled mesh of Bluetooth LE links". 
I think the authors should settle on one phrase (my preference would be 
"IPv6 mesh over BLE links") to avoid confusion that the draft is about 
deploying IPv6 over the recently standardised BLE mesh technology.

* Section 1 has the following sentence: "However, subsequent Bluetooth 
specifications allow the formation of extended topologies [BTCorev4.1], 
such as the mesh
    topology." What extended topologies from the BT Core document are 
relevant for the mesh described in this document, which didn't exist 
when RFC 7668 became available? If none, I suggest removing this 
sentence (and perhaps avoiding the issue mentioned in the next bullet 
point).

* Bluetooth SIG deprecated the Bluetooth Core Specification 4.1 
mentioned in the previous point was very recently (actually, yesterday). 
Perhaps this should be taken into account?


Otherwise the draft is in good shape and is ready for submission to IESG.

Best regards,

Bill

v2.23.0 | Report a Bug | By Email