IETF Logo Mail Archive

Re: [6lo] privacy enhanced L3 addresses derived from short L2 addresses

"samita Chakrabarti" <samitac.ietf@gmail.com> Tue, 20 September 2016 23:44 UTC

Return-Path: <samitac.ietf@gmail.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 F2AEB127058 for <6lo@ietfa.amsl.com>; Tue, 20 Sep 2016 16:44:15 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 5l-Wf7BsZrGW for <6lo@ietfa.amsl.com>; Tue, 20 Sep 2016 16:44:14 -0700 (PDT)
Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71454126D74 for <6lo@ietf.org>; Tue, 20 Sep 2016 16:44:14 -0700 (PDT)
Received: by mail-yw0-x22e.google.com with SMTP id g192so26919549ywh.1 for <6lo@ietf.org>; Tue, 20 Sep 2016 16:44:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-transfer-encoding:thread-index:content-language; bh=uqZv1sn1iqnUb7RnLHgGxVqr5HOlhHjxaJk3FTpDRiA=; b=opcXnzZsJ13Sv/gYUg/xWIYZZU5bK3TdiAyFRfIQWziSJOv0r/6EQE+xRSCyEVJPsT b9cOWPIECNw09jHZvtne+imyhfh23ARG5m8IXBQQyi1dyWF6dyQAaOT5POyveyzdG4eE EwJ6t8ZdxsXesoGEajujS5T+f9ZpBfMmxPwygdXGi8nV7eodMLWkSs80+I0dSkekz1WB MqAuQm4SLs3SokX4ZNTnXo+bICIPEI1ehQzmrtrDexqhU+iNCj+X3M1+wqfz0Nd4TB4R 2HWnhoVW1Lg0qpsfUrgjOz2aTsKSZ9Ffhf48Yf92WsTP72tdq8A+pXkhCEPsI18BfZAQ o8KA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=uqZv1sn1iqnUb7RnLHgGxVqr5HOlhHjxaJk3FTpDRiA=; b=b3cYT1hNuF70wOg8AV/Babo5u2e6VhXwOJczoMhHRyK21BJQqE//pTi7w9mHpuNSB1 4Th2Bgnn86h9HhWzLEU0d412L3tECHrCpZd32G5UUaEHfXb+E0R32v5QKc/oSAMb2+DY dLqpWIzYfFV/2Jo7xN6Q3d1GZGySa4xvq1tZtmo0fdhpriTQuwoK1HGlKvZ9Hum0abuq mZ7181m1UnReoU0EBqieVdN0HqqXCwfoIX9YPlpWS1P/0G0E0yQHaVrH/npR2YFNXhm+ ggAqu232UTQvjGIaEt+hSk/K3TEOTaRenHsTb/yAiEk2aEOuPDWTj6sD9NPopQDxGTEN pFCg==
X-Gm-Message-State: AE9vXwNnB23bCChqcEep9hm8wTa6riqA/BvbPmdLNXunCt7pTZ8qc7Hg2M+pouWohfrsgQ==
X-Received: by 10.129.76.6 with SMTP id z6mr33669495ywa.257.1474415053598; Tue, 20 Sep 2016 16:44:13 -0700 (PDT)
Received: from DESKTOPIHCV2EF ([2602:306:ccdc:8a10:dc3f:73e4:4598:be]) by smtp.gmail.com with ESMTPSA id z193sm12525789ywg.26.2016.09.20.16.44.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Sep 2016 16:44:13 -0700 (PDT)
From: samita Chakrabarti <samitac.ietf@gmail.com>
To: 'Michael Richardson' <mcr+ietf@sandelman.ca>, 'lo' <6lo@ietf.org>
References: <5153.1474402344@obiwan.sandelman.ca>
In-Reply-To: <5153.1474402344@obiwan.sandelman.ca>
Date: Tue, 20 Sep 2016 16:44:18 -0700
Message-ID: <02c401d21398$e84d9140$b8e8b3c0$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQJr4gjL6oGXds/H8DGj4t0+675QUp9Pa+bw
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/ZsQfS4Cs1MQIqebCL1aUu-o2c8A>
Subject: Re: [6lo] privacy enhanced L3 addresses derived from short L2 addresses
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.17
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, 20 Sep 2016 23:44:16 -0000

Hi Michael,

>>such work does not yet exist.  I think it would be in charter for 6lo at
this time?  It would seem to be an extension to
draft-ietf-6lo-paging-dispatch in >>some way.  I wonder if it worth delay to
do this now?

Right, there is no document on 6lo address formation  that standardizes the
following suggestion made in the privacy document.
It is though covered in the charter as part of the extension of 6lowpan
stack. 

I don't quite relate the connection with 6lo-paging-dispatch...  

Which document to delay ?

Thanks,
-Samita
-----Original Message-----
From: 6lo [mailto:6lo-bounces@ietf.org] On Behalf Of Michael Richardson
Sent: Tuesday, September 20, 2016 1:12 PM
To: lo <6lo@ietf.org>
Subject: [6lo] privacy enhanced L3 addresses derived from short L2 addresses


draft-ietf-6lo-privacy-considerations says:

   When Short Addresses are desired on links that are not guaranteed to
   have a short enough lifetime, the mechanism for constructing an IPv6
   interface identifier from a Short Address could be designed to
   sufficiently mitigate the problem.  For example, if all nodes on a
   given L2 network have a shared secret (such as the key needed to get
   on the layer-2 network), the 64-bit IID might be generated using a
   one-way hash that includes (at least) the shared secret together
   with the Short Address.  The use of such a hash would result in the IIDs
   being spread out among the full range of IID address space, thus
   mitigating address scans, while still allowing full stateless
   compression/elision.

such work does not yet exist.  I think it would be in charter for 6lo at
this time?  It would seem to be an extension to
draft-ietf-6lo-paging-dispatch in some way.  I wonder if it worth delay to
do this now?

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works  -=
IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email