[Lln-futures] Notes from hallway meeting in Vancouver
Geoff Mulligan <geoff.ietf@mulligan.com> Wed, 12 September 2012 17:58 UTC
Return-Path: <geoff.ietf@mulligan.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 D049B21F8545 for <lln-futures@ietfa.amsl.com>;
Wed, 12 Sep 2012 10:58:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Level:
X-Spam-Status: No,
score=-0.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74]
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 6sF8g9N0P3WS for
<lln-futures@ietfa.amsl.com>; Wed, 12 Sep 2012 10:58:36 -0700 (PDT)
Received: from mail.coslabs.com (mail.coslabs.com [199.233.92.34]) by
ietfa.amsl.com (Postfix) with ESMTP id 4607121F84C9 for
<lln-futures@ietf.org>; Wed, 12 Sep 2012 10:58:36 -0700 (PDT)
Received: from [199.233.92.4] (unknown [199.233.92.4]) (using TLSv1 with
cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested)
by mail.coslabs.com (Postfix) with ESMTPSA id A35605FCB7 for
<lln-futures@ietf.org>; Wed, 12 Sep 2012 11:58:34 -0600 (MDT)
Message-ID: <5050CD4B.8000302@mulligan.com>
Date: Wed, 12 Sep 2012 11:58:35 -0600
From: Geoff Mulligan <geoff.ietf@mulligan.com>
User-Agent: Mozilla/5.0 (X11; Linux i686;
rv:15.0) Gecko/20120827 Thunderbird/15.0
MIME-Version: 1.0
To: lln-futures@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [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: Wed, 12 Sep 2012 17:58:36 -0000
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] 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