Re: [Lln-futures] Notes from hallway meeting in Vancouver
"Keoh, Sye Loong" <sye.loong.keoh@philips.com> Mon, 17 September 2012 11:15 UTC
Return-Path: <sye.loong.keoh@philips.com>
X-Original-To: lln-futures@ietfa.amsl.com
Delivered-To: lln-futures@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix)
with ESMTP id AC06121F8606 for <lln-futures@ietfa.amsl.com>;
Mon, 17 Sep 2012 04:15:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9BF52iVaKRKY for
<lln-futures@ietfa.amsl.com>; Mon, 17 Sep 2012 04:15:59 -0700 (PDT)
Received: from tx2outboundpool.messaging.microsoft.com
(tx2ehsobe003.messaging.microsoft.com [65.55.88.13]) by ietfa.amsl.com
(Postfix) with ESMTP id BB49121F8604 for <lln-futures@ietf.org>;
Mon, 17 Sep 2012 04:15:57 -0700 (PDT)
Received: from mail14-tx2-R.bigfish.com (10.9.14.247) by
TX2EHSOBE008.bigfish.com (10.9.40.28) with Microsoft SMTP Server id
14.1.225.23; Mon, 17 Sep 2012 11:15:57 +0000
Received: from mail14-tx2 (localhost [127.0.0.1]) by mail14-tx2-R.bigfish.com
(Postfix) with ESMTP id 25359160106 for <lln-futures@ietf.org>;
Mon, 17 Sep 2012 11:15:57 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.7.222; KIP:(null); UIP:(null); IPV:NLI;
H:mail.philips.com; RD:none; EFVD:NLI
X-SpamScore: -39
X-BigFish: VPS-39(zz217bL15d6O9251J168aJ542Md6f1izz1202h1d1ah1d2ahzz1033IL8275dhz2dh2a8h668h839h944hd25hf0ah107ah1220h1288h12a5h12a9h12bdh1155h)
Received: from mail14-tx2 (localhost.localdomain [127.0.0.1]) by mail14-tx2
(MessageSwitch) id 1347880555636575_24756;
Mon, 17 Sep 2012 11:15:55 +0000 (UTC)
Received: from TX2EHSMHS029.bigfish.com (unknown [10.9.14.249]) by
mail14-tx2.bigfish.com (Postfix) with ESMTP id 9345B180070 for
<lln-futures@ietf.org>; Mon, 17 Sep 2012 11:15:55 +0000 (UTC)
Received: from mail.philips.com (157.55.7.222) by TX2EHSMHS029.bigfish.com
(10.9.99.129) with Microsoft SMTP Server (TLS) id 14.1.225.23;
Mon, 17 Sep 2012 11:15:52 +0000
Received: from 011-DB3MPN1-032.MGDPHG.emi.philips.com ([169.254.2.49]) by
011-DB3MMR1-007.MGDPHG.emi.philips.com ([10.128.28.57]) with mapi id
14.02.0309.003; Mon, 17 Sep 2012 12:16:30 +0100
From: "Keoh, Sye Loong" <sye.loong.keoh@philips.com>
To: "lln-futures@ietf.org" <lln-futures@ietf.org>
Thread-Topic: [Lln-futures] Notes from hallway meeting in Vancouver
Thread-Index: AQHNkRBp5L6v20chUEaH7OJpapJRhZeOZspQ
Date: Mon, 17 Sep 2012 11:16:29 +0000
Message-ID: <EAE29B174013F643B5245BA11953A1BE0CFB83@011-DB3MPN1-032.MGDPHG.emi.philips.com>
References: <5050CD4B.8000302@mulligan.com>
In-Reply-To: <5050CD4B.8000302@mulligan.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [194.171.252.104]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: philips.com
Subject: Re: [Lln-futures] Notes from hallway meeting in Vancouver
X-BeenThere: lln-futures@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <lln-futures.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lln-futures>,
<mailto:lln-futures-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/lln-futures>
List-Post: <mailto:lln-futures@ietf.org>
List-Help: <mailto:lln-futures-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lln-futures>,
<mailto:lln-futures-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Sep 2012 11:15:59 -0000
Dear all, I agree that having a formal BOF in Atlanta would be great to kick off some discussion. Geoff, what do we need to prepare for a formal BOF in IETF? Security for LLN is definitely one of the areas that we should address. A common solution for key management, communication security, security bootstrapping is beneficial as we can remove redundancies due to the constraints of the devices. Cheers Sye Loong -----Original Message----- From: lln-futures-bounces@ietf.org [mailto:lln-futures-bounces@ietf.org] On Behalf Of Geoff Mulligan Sent: woensdag 12 september 2012 19:59 To: lln-futures@ietf.org Subject: [Lln-futures] Notes from hallway meeting in Vancouver LLN people, Here are the notes (thank you Justin) from the hallway meeting in Vancouver. There seems to be some "sort-of" parallel efforts (coman and solace), but potentially focused on different areas. We had about 7 or 8 people attend the hallway discussion. There seem to folks interested in a variety of topics related to LLNs that were not addressed by 6lowpan. If we would like to have a formal BOF in Atlanta I need to request it soon so we should have some good discussion about work items and topics for the the BOF. Please read these notes below and lets start talking... geoff ---------------- Notes --------------------- 6lowpan has shut down but there is still stuff to be done. What are the gaps in getting M2M communication to work within the scope of LLNs? Management of constrained devices might be taking place in COMAN. Where do we do architectures for LLNs? In general the IETF doesn't do architectures but its hard to tackle these problems without an over arching framework. There are lots of different drafts and protocols and who is the person/group looking over them and seeing if they are going to work and how they fit together. What about a common security solution for LLNs? There are different levels of security for different type of systems. It might be possible to leverage the shared medium characteristics to help secure these devices. With the layering approach we have so far....our feeling is that we have many different solutions at the different layers. We end up with different solutions doing the same work and potentially not interoperable. There is an interest in security and key management. End to end security in a multihop network. The original drafts we put out we said you can't do IPSEC. Technology has increased so perhaps we can do ipsec in these smaller devices, or some subset of ipsec. The 802.15 group has been expanding at a rapid rate- some new PHYs and MACs. Is there interest in IP over these? Working groups cluster multi dimensional issues together and the solutions to the different issues might not be the same. LLN (as low power lossy networks) are they low power or are they lossy or are they both? Perhaps we should focus on one or the other What about device identity issues. Is this in SOLACE or COMAN _______________________________________________ Lln-futures mailing list Lln-futures@ietf.org https://www.ietf.org/mailman/listinfo/lln-futures ________________________________ The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.
- [Lln-futures] Notes from hallway meeting in Vanco… Geoff Mulligan
- Re: [Lln-futures] Notes from hallway meeting in V… Keoh, Sye Loong
- Re: [Lln-futures] Notes from hallway meeting in V… JP Vasseur (jvasseur)
- Re: [Lln-futures] Notes from hallway meeting in V… Ralph Droms
- Re: [Lln-futures] Notes from hallway meeting in V… Thomas Heide Clausen
- Re: [Lln-futures] Notes from hallway meeting in V… Mani, Mehdi
- Re: [Lln-futures] Notes from hallway meeting in V… Ralph Droms
- Re: [Lln-futures] Notes from hallway meeting in V… Geoff Mulligan
- Re: [Lln-futures] Notes from hallway meeting in V… Geoff Mulligan
- Re: [Lln-futures] Notes from hallway meeting in V… Geoff Mulligan
- Re: [Lln-futures] Notes from hallway meeting in V… Mani, Mehdi