IETF Logo Mail Archive

Re: [6lo] Alissa Cooper's Discuss on draft-ietf-6lo-btle-14: (with DISCUSS and COMMENT)

Alissa Cooper <alissa@cooperw.in> Tue, 04 August 2015 04:18 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F07AF1B34F2 for <6lo@ietfa.amsl.com>; Mon, 3 Aug 2015 21:18:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 Qx90Gcma_8Hl for <6lo@ietfa.amsl.com>; Mon, 3 Aug 2015 21:18:39 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66DB81B3571 for <6lo@ietf.org>; Mon, 3 Aug 2015 21:18:39 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id DB22E207DB for <6lo@ietf.org>; Tue, 4 Aug 2015 00:18:37 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute5.internal (MEProxy); Tue, 04 Aug 2015 00:18:37 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=2SITy63ajVG+VUGda4BjzV63tr4=; b=BX8P8N eXv0Vsx9MyAHTO3l2wjqROJ3HeGJgmK1XIIw58y4yfRnmU5bP/JsjFiBkTJ1qFz9 nwxebPyyTBBN286xWkq1d9V7/2kLfI6eLTcG8sZBb76lUD9N1/AOkN6w5VYRtyhg OpZ2yGxphbCTnZ/B+Zf42L98owjhi/5oQ/MBE=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=2SITy63ajVG+VUG da4BjzV63tr4=; b=HWZK0+2b/5g3fVCzbqNAEAzQBsmVINcYKZyzyncs8svaVdU dNHGog78ClP6BQUDHEV74EpA7t8SgogZT5J7ggBD2fiy6Vl/XIDP04b81YLMOD7J HRpb6n9fdQLMph8saw0fICY4JDwyaK6DZ8EuUHAEFTWMenMARDtAjh5HpL30=
X-Sasl-enc: qE24EJ4sDrpxS/d2P+scgU8ICd4ZciHGRe54wMg38KyB 1438661917
Received: from sjc-alcoop-88112.cisco.com (unknown [128.107.241.190]) by mail.messagingengine.com (Postfix) with ESMTPA id EE313C00022; Tue, 4 Aug 2015 00:18:33 -0400 (EDT)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <99ABD7AF-8196-463C-B045-718DE94C3635@cooperw.in>
Date: Mon, 03 Aug 2015 21:18:32 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <1D0CB901-AD19-461C-8C5B-D17F47BEC514@cooperw.in>
References: <b366d082-133c-487f-a988-9bc5bfeb01a3@email.android.com> <32BFA1BC-3196-4DC3-B4E1-2151EA1345DE@cooperw.in> <4ab14b6a1a9146ef839ea3bff732ebb7@NOKWDCFIEXCH02P.nnok.nokia.com> <55A8EB70.1070307@innovationslab.net> <99ABD7AF-8196-463C-B045-718DE94C3635@cooperw.in>
To: "Savolainen Teemu (Nokia-TECH/Tampere)" <teemu.savolainen@nokia.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/6lo/m1bzf6bZgD0NpVFtUNo2k59qvF4>
X-Mailman-Approved-At: Mon, 10 Aug 2015 08:43:15 -0700
Cc: ext Kerry Lynn <kerlyn@ieee.org>, "6lo-chairs@ietf.org" <6lo-chairs@ietf.org>, "draft-ietf-6lo-btle.ad@ietf.org" <draft-ietf-6lo-btle.ad@ietf.org>, Will Cheng <liushucheng@huawei.com>, Dave Thaler <dthaler@microsoft.com>, "draft-ietf-6lo-btle@ietf.org" <draft-ietf-6lo-btle@ietf.org>, "Gabriel.Montenegro@microsoft.com" <Gabriel.Montenegro@microsoft.com>, "draft-ietf-6lo-btle.shepherd@ietf.org" <draft-ietf-6lo-btle.shepherd@ietf.org>, "6lo@ietf.org" <6lo@ietf.org>, IESG <iesg@ietf.org>, Fernando Gont <fgont@si6networks.com>, Brian Haberman <brian@innovationslab.net>
Subject: Re: [6lo] Alissa Cooper's Discuss on draft-ietf-6lo-btle-14: (with DISCUSS and COMMENT)
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Aug 2015 04:18:41 -0000

I had a look at the -16. Thanks for making the changes and bearing with me here. I have two questions left on the new text.

In 3.2.2 it says:

A 6LN and a 6LBR are RECOMMENDED to use
   random Bluetooth device addresses.  A 6LN SHOULD pick a different
   Bluetooth device address for every Bluetooth LE connection with a
   6LBR, and a 6LBR SHOULD periodically change its random Bluetooth
   device address.

Does this effectively mean that 6LNs and 6LBRs are RECOMMENDED to use private addresses (since they are also recommended to not be static)? 

Then further down it says:

In situations where the
   Bluetooth device address is known to be a random device address (i.e.
   a static or private device address) and/or the header compression
   benefits of embedding the device address in the IID are required to
   support deployment constraints, 6LNs MAY form a 64-bit IID by
   utilizing the 48-bit Bluetooth device address.

Shouldn’t the exception in the first part of the sentence only apply to private addresses and not static ones, since static addresses can be very long-lived?

Thanks,
Alissa

v2.23.0 | Report a Bug | By Email