RE: [6lowpan] Agenda for next meeting
Daniel Park <soohong.park@samsung.com> Mon, 05 March 2007 01:09 UTC
Return-path: <6lowpan-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HO1iB-0007Q5-16; Sun, 04 Mar 2007 20:09:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HO1iA-0007Q0-2j for 6lowpan@lists.ietf.org; Sun, 04 Mar 2007 20:09:58 -0500
Received: from mailout2.samsung.com ([203.254.224.25]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HO1i5-0001hv-Ko for 6lowpan@lists.ietf.org; Sun, 04 Mar 2007 20:09:58 -0500
Received: from ep_mmp2 (mailout2.samsung.com [203.254.224.25]) by mailout2.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0JEE000TOOKGA5@mailout2.samsung.com> for 6lowpan@lists.ietf.org; Mon, 05 Mar 2007 10:09:52 +0900 (KST)
Received: from daniel ([168.219.198.109]) by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTPA id <0JEE00MNSOKFXU@mmp2.samsung.com> for 6lowpan@lists.ietf.org; Mon, 05 Mar 2007 10:09:52 +0900 (KST)
Date: Mon, 05 Mar 2007 10:09:44 +0900
From: Daniel Park <soohong.park@samsung.com>
Subject: RE: [6lowpan] Agenda for next meeting
In-reply-to: <1173052621.4869.103.camel@dellx1>
To: 'Geoff Mulligan' <geoff@mulligan.com>, 'Carsten Bormann' <cabo@tzi.de>
Message-id: <0JEE00MNUOKFXU@mmp2.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Thread-index: AcdeuTx6KSYcA53sSsWLZMjAVGT2oAABfExQ
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: '6lowpan' <6lowpan@lists.ietf.org>
X-BeenThere: 6lowpan@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/6lowpan>
List-Post: <mailto:6lowpan@ietf.org>
List-Help: <mailto:6lowpan-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=subscribe>
Errors-To: 6lowpan-bounces@ietf.org
inline... > Here is the complete list of topics that have been suggested > on this list (in no particular order): > > Neighbor Discovery and Secure Neighbor Discovery (proposed > standard) Stateful header compression (informational) 6lowpan > applications (informational) mesh routing (proposed standard) > Security analysis (informational) bootstrapping mobility MIB > definition service discovery scalable routing commissioning > power saving schemes (beacons) Architecture document For group's information here: * Routing http://daniel.vsix.net/ietf/6lowpan/draft-daniel-6lowpan-hilow-hierarchical- routing-01.txt http://daniel.vsix.net/ietf/6lowpan/draft-daniel-6lowpan-load-adhoc-routing- 01.txt http://daniel.vsix.net/ietf/6lowpan/draft-montenegro-6lowpan-dymo-low-routin g-02.txt *Security http://daniel.vsix.net/ietf/6lowpan/draft-daniel-6lowpan-security-analysis-0 2.txt * Service Discovery http://daniel.vsix.net/ietf/6lowpan/draft-daniel-6lowpan-sslp-01.txt * MIB http://daniel.vsix.net/ietf/6lowpan/draft-daniel-lowpan-mib-00.txt > I see at least 2 very important topics that we need to finish - > * Neighbor Discovery for 6lowpan > * 6lowpan architecture document > > Additionally, we need to reach some consensus on: > * Routing (scalable, mesh under, route over) > * Security > * bootstrapping/commissioning > > Since we already have a draft (expired) for ND we should > seriously consider finishing this work. We are have a number > of drafts (also > expired) and one not expired on routing alternatives. > > I think that the main topic for the meeting is the > rechartering, but I think that it is extremely important that > we talk with the Manet group and understand if their work can > apply to 6lowpans. > > This understanding though may be based on the network > architecture that we are trying to build. This is why I > think that we should start with defining the 6lowpan arch. sounds like ZB network architecture ? Daniel _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan
- [6lowpan] Agenda for next meeting Geoff Mulligan
- Re: [6lowpan] Agenda for next meeting Samita Chakrabarti
- RE: [6lowpan] Agenda for next meeting Daniel Park
- Re: [6lowpan] Agenda for next meeting Myung-Ki Shin
- RE: [6lowpan] Agenda for next meeting Eunsook Kim
- RE: [6lowpan] Agenda for next meeting Eunsook Kim
- Re: [6lowpan] Agenda for next meeting Wassim Haddad
- RE: [6lowpan] Agenda for next meeting Daniel Park
- Re: [6lowpan] Agenda for next meeting Tiago Camilo
- RE: [6lowpan] Agenda for next meeting Wassim Haddad