IETF Logo Mail Archive

Re: [6lo] Generation of IPv6 IIDs

Fernando Gont <fgont@si6networks.com> Sat, 03 May 2014 20:52 UTC

Return-Path: <fgont@si6networks.com>
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 607571A012F for <6lo@ietfa.amsl.com>; Sat, 3 May 2014 13:52:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 egpQYAHIGXTy for <6lo@ietfa.amsl.com>; Sat, 3 May 2014 13:52:37 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) by ietfa.amsl.com (Postfix) with ESMTP id 36FD51A012E for <6lo@ietf.org>; Sat, 3 May 2014 13:52:37 -0700 (PDT)
Received: from [187.185.71.234] (helo=[172.17.65.68]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <fgont@si6networks.com>) id 1Wggv9-0001i6-K8; Sat, 03 May 2014 22:52:32 +0200
Message-ID: <5365561E.2030404@si6networks.com>
Date: Sat, 03 May 2014 15:48:30 -0500
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: robert.cragie@gridmerge.com, "Dijk, Esko" <esko.dijk@philips.com>, "6lo@ietf.org" <6lo@ietf.org>
References: <5361A67D.4010508@si6networks.com> <031DD135F9160444ABBE3B0C36CED61816A16351@AMSPRD9003MB066.MGDPHG.emi.philips.com> <5362B6CE.1020000@gridmerge.com>
In-Reply-To: <5362B6CE.1020000@gridmerge.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/6lo/7UYMj-I80wBWQrvowtPxRllx_kU
Cc: "6lo-chairs@tools.ietf.org" <6lo-chairs@tools.ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@tools.ietf.org>, Dave Thaler <dthaler@microsoft.com>
Subject: Re: [6lo] Generation of IPv6 IIDs
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: <http://www.ietf.org/mail-archive/web/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: Sat, 03 May 2014 20:52:38 -0000

Hi, Robert,

On 05/01/2014 04:04 PM, Robert Cragie wrote:
> It is also worth noting the different scopes the IIDs can be used in. If
> the address is globally routable, there is certainly a case for adopting
> privacy addresses. However, for link local addresses, especially in a
> route-over mesh where a link-local IP packet travels strictly one node
> hop, it does not seem as critical. As mentioned below, in many cases
> 6LoWPAN compression relies on a one-to-one correspondence between a link
> local and IPv6 address to provide effective compression.

The link-local case has been discussed within 6man already. Short
summary: these addresses can link (think e.g. a node contacting an MTA
on the local network, and then the link-local address leaking out via
the email headers).

Predictable/constant addresses is something with well-known
implications. We should move away from them.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492

v2.23.0 | Report a Bug | By Email