From 6lowpan-bounces@ietf.org Thu Mar 02 11:12:21 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FEqPW-0003Hm-B8; Thu, 02 Mar 2006 11:12:14 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FEqPU-00039S-EM for 6lowpan@ietf.org; Thu, 02 Mar 2006 11:12:12 -0500 Received: from violet.upc.es ([147.83.2.51]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FEqPS-0004Me-QJ for 6lowpan@ietf.org; Thu, 02 Mar 2006 11:12:12 -0500 Received: from violet.upc.es (localhost [127.0.0.1]) by violet.upc.es (8.13.0/8.13.0) with ESMTP id k22GC8uE010005 for <6lowpan@ietf.org>; Thu, 2 Mar 2006 17:12:09 +0100 Received: from localhost (wmail-mat.upc.es [147.83.39.70]) by violet.upc.es (8.13.0/8.13.0) with ESMTP id k22GBRoH009791 for <6lowpan@ietf.org>; Thu, 2 Mar 2006 17:11:27 +0100 Received: from 147.83.113.31 ( [147.83.113.31]) as user carlesgo@mat.upc.es by wmail-mat.upc.es with HTTP; Thu, 2 Mar 2006 16:53:47 +0100 Message-ID: <1141314827.4407150be596a@wmail-mat.upc.es> Date: Thu, 2 Mar 2006 16:53:47 +0100 From: Carles Gomez To: 6lowpan@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.1 X-Originating-IP: 147.83.113.31 X-Spam-Score: 0.0 (/) X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 Subject: [6lowpan] Announcement: NST-AODV implementation available for TinyOS 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org Hello all, We would like to announce the public release of NST-AODV: an AODV implementation based on TinyAODV for TinyOS devices. NST-AODV provides a number of additional features which are expected to be advantageous in non-static scenarios. The benefits come at the expense of memory storage requirements increase. NST-AODV operates closely to the proposed 6LoWPAN Ad Hoc On-Demand Distance Vector Routing (LOAD) protocol, although a few differences exist between the two proposals. The implementation can be found at the web page of the i2cat Foundation: www.i2cat.net -> i2CAT Platform -> UbiCAT -> Routing (NST-AODV) If you are interested in further information, do not hesitate to contact me. Best regards, Carles Gómez i Montenegro Wireless Networks Group Technical University of Catalonia carlesgo@entel.upc.edu Tel: +34 93 413 7206 ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Sun Mar 05 19:51:36 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FG3wk-00021G-Qw; Sun, 05 Mar 2006 19:51:34 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FG3wj-0001yt-I1 for 6lowpan@ietf.org; Sun, 05 Mar 2006 19:51:33 -0500 Received: from mailout1.samsung.com ([203.254.224.24]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FG3wi-0000Pj-5Q for 6lowpan@ietf.org; Sun, 05 Mar 2006 19:51:33 -0500 Received: from ep_mmp2 (mailout1.samsung.com [203.254.224.24]) by mailout1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0IVO0069DL1AAF@mailout1.samsung.com> for 6lowpan@ietf.org; Mon, 06 Mar 2006 09:51:10 +0900 (KST) Received: from daniellaptop ([124.235.139.1]) by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTPA id <0IVO00B44L17OL@mmp2.samsung.com> for 6lowpan@ietf.org; Mon, 06 Mar 2006 09:51:10 +0900 (KST) Date: Mon, 06 Mar 2006 09:51:15 +0900 From: Soohong Daniel Park To: 6lowpan@ietf.org Message-id: <007901c640b8$1403eec0$45706f0a@daniellaptop> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Outlook Express 6.00.2900.2180 Content-type: text/plain; charset=ks_c_5601-1987 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Subject: [6lowpan] LOAD Updated 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org Folks - LOAD (6LoWPAN Ad Hoc On-Demand Distance Vector Routing) has been updated and you can use the following links before ietf repository. http://daniel.vsix.net/ietf/6lowpan/draft-daniel-6lowpan-load-adhoc-routing-02.txt Diff from 01 version: http://daniel.vsix.net/ietf/6lowpan/draft-daniel-6lowpan-load-adhoc-routing-02_diff.htm Any comments are highly welcome, See you in Dallas soon. Daniel (Soohong Daniel Park) Mobile Convergence Laboratory, SAMSUNG Electronics. _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Mon Mar 06 11:21:13 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGISO-0007IW-Ur; Mon, 06 Mar 2006 11:21:12 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGIQS-0004oC-0n for 6lowpan@lists.ietf.org; Mon, 06 Mar 2006 11:19:12 -0500 Received: from grab.coslabs.com ([199.233.92.34]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FGIJe-0007yJ-63 for 6lowpan@lists.ietf.org; Mon, 06 Mar 2006 11:12:11 -0500 Received: from dellx1.coslabs.com (dellx1.coslabs.com [199.233.92.20]) by grab.coslabs.com (8.12.10/8.12.10) with ESMTP id k26GC9Jr008622 for <6lowpan@lists.ietf.org>; Mon, 6 Mar 2006 09:12:09 -0700 (MST) From: Geoff Mulligan To: 6lowpan <6lowpan@lists.ietf.org> Content-Type: text/plain Date: Mon, 06 Mar 2006 09:12:16 -0700 Message-Id: <1141661536.7959.37.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Cc: Subject: [6lowpan] Working group last-call on problems document 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org Hi, This note starts the 6loWPAN Working Group Last-call for comments on draft-ietf-6lowpan-problem-02.txt, "6LoWPAN: Overview, Assumptions, Problem Statement and Goals". The document can be found at ftp://ftp.ietf.org/internet-drafts/draft-ietf-6lowpan-problem-02.txt Please review the document carefully, and send your feedback to the list. Please also indicate whether or not you believe that this document is ready to go to the IESG. This Last Call will end on 20 March 2006 at 0900 MST (UTC - 7), two weeks form the time of this call. Thanks, geoff _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Mon Mar 06 15:00:39 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGLsh-0006Df-Qs; Mon, 06 Mar 2006 15:00:35 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGLsg-0006C1-TQ for 6lowpan@lists.ietf.org; Mon, 06 Mar 2006 15:00:34 -0500 Received: from mailout1.samsung.com ([203.254.224.24]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FGLsf-0007NQ-D1 for 6lowpan@lists.ietf.org; Mon, 06 Mar 2006 15:00:34 -0500 Received: from ep_mmp2 (mailout1.samsung.com [203.254.224.24]) by mailout1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0IVQ00L7J28VEX@mailout1.samsung.com> for 6lowpan@lists.ietf.org; Tue, 07 Mar 2006 05:00:32 +0900 (KST) Received: from daniellaptop ([124.235.139.3]) by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTPA id <0IVQ001I928UPI@mmp2.samsung.com> for 6lowpan@lists.ietf.org; Tue, 07 Mar 2006 05:00:31 +0900 (KST) Date: Tue, 07 Mar 2006 05:00:37 +0900 From: Soohong Daniel Park Subject: Re: [6lowpan] Working group last-call on problems document To: Geoff Mulligan , 6lowpan <6lowpan@lists.ietf.org> Message-id: <038a01c64158$a5b3a860$45706f0a@daniellaptop> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Outlook Express 6.00.2900.2180 Content-type: text/plain; charset=ks_c_5601-1987 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <1141661536.7959.37.camel@localhost.localdomain> X-Spam-Score: 0.0 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Cc: 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org I believe it is ready to the IESG. Good job Nandu and Gab...:-) Minor nits: both LoWPAN and 6LoWPAN seem a bit confused around the document. If available, defining terminology would be favorable. Daniel (Soohong Daniel Park) Mobile Convergence Laboratory, SAMSUNG Electronics. ----- Original Message ----- From: "Geoff Mulligan" To: "6lowpan" <6lowpan@lists.ietf.org> Sent: Tuesday, March 07, 2006 1:12 AM Subject: [6lowpan] Working group last-call on problems document > Hi, > This note starts the 6loWPAN Working Group Last-call for comments on > draft-ietf-6lowpan-problem-02.txt, "6LoWPAN: Overview, Assumptions, > Problem Statement and Goals". The document can be found at > ftp://ftp.ietf.org/internet-drafts/draft-ietf-6lowpan-problem-02.txt > > Please review the document carefully, and send your feedback to the > list. Please also indicate whether or not you believe that this > document is ready to go to the IESG. > > This Last Call will end on 20 March 2006 at 0900 MST (UTC - 7), two > weeks form the time of this call. > > Thanks, > geoff > > > > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan > > _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Mon Mar 06 16:25:30 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGNCs-0001C8-Du; Mon, 06 Mar 2006 16:25:30 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGNCr-0001C3-Qa for 6lowpan@ietf.org; Mon, 06 Mar 2006 16:25:29 -0500 Received: from xproxy.gmail.com ([66.249.82.196]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FGNCq-0007QJ-Jo for 6lowpan@ietf.org; Mon, 06 Mar 2006 16:25:29 -0500 Received: by xproxy.gmail.com with SMTP id h29so868565wxd for <6lowpan@ietf.org>; Mon, 06 Mar 2006 13:25:28 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ND4SEEl00geh5hrto92hAKO/aF1OpjrfON3f1Jak+l+gTjwZZ1WwQDGB3W/f+6+LtaI77qvZR1ud8V+nlmOBmT4RQBa+3H70hF26RaDAvC8wnlh2DvJDqAI0wX4cmz/OJqFVHve8sKMUu8IslMLprDhg4xWX/+vOya/VKqHDMKU= Received: by 10.70.72.7 with SMTP id u7mr803003wxa; Mon, 06 Mar 2006 13:25:28 -0800 (PST) Received: by 10.70.28.4 with HTTP; Mon, 6 Mar 2006 13:25:28 -0800 (PST) Message-ID: Date: Tue, 7 Mar 2006 06:25:28 +0900 From: "Soohong Daniel Park" To: 6lowpan@ietf.org Subject: Re: [6lowpan] LOAD Updated In-Reply-To: <007901c640b8$1403eec0$45706f0a@daniellaptop> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <007901c640b8$1403eec0$45706f0a@daniellaptop> X-Spam-Score: 0.0 (/) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org Here is an official release: http://www.ietf.org/internet-drafts/draft-daniel-6lowpan-load-adhoc-routing= -02.txt On 3/6/06, Soohong Daniel Park wrote: > Folks - LOAD (6LoWPAN Ad Hoc On-Demand Distance Vector Routing) > has been updated and you can use the following links before ietf reposito= ry. > > http://daniel.vsix.net/ietf/6lowpan/draft-daniel-6lowpan-load-adhoc-routi= ng-02.txt > > Diff from 01 version: > http://daniel.vsix.net/ietf/6lowpan/draft-daniel-6lowpan-load-adhoc-routi= ng-02_diff.htm > > Any comments are highly welcome, > > See you in Dallas soon. > > Daniel (Soohong Daniel Park) > Mobile Convergence Laboratory, SAMSUNG Electronics. > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Mon Mar 06 19:45:31 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGQKQ-0000E5-4w; Mon, 06 Mar 2006 19:45:30 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGQKO-0000E0-6i for 6lowpan@lists.ietf.org; Mon, 06 Mar 2006 19:45:28 -0500 Received: from fmr19.intel.com ([134.134.136.18] helo=orsfmr004.jf.intel.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FGQKN-0000lI-Jk for 6lowpan@lists.ietf.org; Mon, 06 Mar 2006 19:45:28 -0500 Received: from orsfmr101.jf.intel.com (orsfmr101.jf.intel.com [10.7.209.17]) by orsfmr004.jf.intel.com (8.12.10/8.12.10/d: major-outer.mc,v 1.1 2004/09/17 17:50:56 root Exp $) with ESMTP id k270jMWE010215; Tue, 7 Mar 2006 00:45:22 GMT Received: from orsmsxvs041.jf.intel.com (orsmsxvs041.jf.intel.com [192.168.65.54]) by orsfmr101.jf.intel.com (8.12.10/8.12.10/d: major-inner.mc,v 1.2 2004/09/17 18:05:01 root Exp $) with SMTP id k270jFWi018310; Tue, 7 Mar 2006 00:45:20 GMT Received: from orsmsx332.amr.corp.intel.com ([192.168.65.60]) by orsmsxvs041.jf.intel.com (SAVSMTP 3.1.7.47) with SMTP id M2006030616451518278 ; Mon, 06 Mar 2006 16:45:15 -0800 Received: from orsmsx410.amr.corp.intel.com ([192.168.65.64]) by orsmsx332.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 6 Mar 2006 16:45:03 -0800 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Subject: RE: [6lowpan] Working group last-call on problems document Date: Mon, 6 Mar 2006 16:44:54 -0800 Message-ID: <9D602ABCE51B0B488BF857A4787939B5077C401B@orsmsx410> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [6lowpan] Working group last-call on problems document Thread-Index: AcZBWMHfBRvZv6zGTWWaOj0zysq26AAJ1rnQ From: "Kushalnagar, Nandakishore" To: "Soohong Daniel Park" , "Geoff Mulligan" , "6lowpan" <6lowpan@lists.ietf.org> X-OriginalArrivalTime: 07 Mar 2006 00:45:03.0159 (UTC) FILETIME=[5EF85470:01C64180] X-Scanned-By: MIMEDefang 2.52 on 10.7.209.17 X-Spam-Score: 0.0 (/) X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0 Cc: 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org Thanks Daniel. Once all the comments are in, we will do a final walk through to clarify these inconsistencies. Regards Nandu -----Original Message----- From: Soohong Daniel Park [mailto:soohong.park@samsung.com]=20 Sent: Monday, March 06, 2006 12:01 PM To: Geoff Mulligan; 6lowpan Subject: Re: [6lowpan] Working group last-call on problems document I believe it is ready to the IESG. Good job Nandu and Gab...:-) Minor nits: both LoWPAN and 6LoWPAN seem a bit confused around the document. If available, defining terminology would be favorable. Daniel (Soohong Daniel Park) Mobile Convergence Laboratory, SAMSUNG Electronics. ----- Original Message -----=20 From: "Geoff Mulligan" To: "6lowpan" <6lowpan@lists.ietf.org> Sent: Tuesday, March 07, 2006 1:12 AM Subject: [6lowpan] Working group last-call on problems document > Hi, > This note starts the 6loWPAN Working Group Last-call for comments on > draft-ietf-6lowpan-problem-02.txt, "6LoWPAN: Overview, Assumptions, > Problem Statement and Goals". The document can be found at > ftp://ftp.ietf.org/internet-drafts/draft-ietf-6lowpan-problem-02.txt >=20 > Please review the document carefully, and send your feedback to the > list. Please also indicate whether or not you believe that this > document is ready to go to the IESG. >=20 > This Last Call will end on 20 March 2006 at 0900 MST (UTC - 7), two > weeks form the time of this call. >=20 > Thanks, > geoff >=20 >=20 >=20 >=20 > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan >=20 > _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Tue Mar 07 06:09:19 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGa3y-0004dj-Sb; Tue, 07 Mar 2006 06:09:10 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGa3w-0004dZ-Ua for 6lowpan@lists.ietf.org; Tue, 07 Mar 2006 06:09:08 -0500 Received: from mailx.danfoss.com ([193.162.34.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FGa3w-0006dW-Ek for 6lowpan@lists.ietf.org; Tue, 07 Mar 2006 06:09:08 -0500 Received: from DKDN04MX62.dkdn04.danfoss.net ([10.6.2.62]) by mailx.danfoss.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 7 Mar 2006 12:09:07 +0100 Received: from dkdn01mx21.danfoss.net ([10.12.129.21]) by DKDN04MX62.dkdn04.danfoss.net with InterScan Message Security Suite; Tue, 07 Mar 2006 12:09:07 +0100 Received: from dkdn01mx25.danfoss.net ([10.12.129.25]) by dkdn01mx21.danfoss.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 7 Mar 2006 12:09:06 +0100 Received: from DKDN01MX34.danfoss.net ([10.12.128.14]) by dkdn01mx25.danfoss.net with Microsoft SMTPSVC(6.0.3790.211); Tue, 7 Mar 2006 12:09:05 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 7 Mar 2006 12:09:03 +0100 Message-ID: <49A38D2FE2C53946A57916AD6A1F00D77DB48D@DKDN01MX34.danfoss.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: new 6lowpan charter Thread-Index: AcZB14toHwySxQ5BQ6WUHbNZm5KIAw== From: "Schumacher Christian Peter Pii" To: <6lowpan@lists.ietf.org> X-OriginalArrivalTime: 07 Mar 2006 11:09:05.0702 (UTC) FILETIME=[8C76FC60:01C641D7] X-Spam-Score: 0.1 (/) X-Scan-Signature: 16c9da4896bf5539ae3547c6c25f06a0 Cc: Subject: [6lowpan] new 6lowpan charter 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1138548196==" Errors-To: 6lowpan-bounces@ietf.org This is a multi-part message in MIME format. --===============1138548196== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C641D7.8BF0612B" This is a multi-part message in MIME format. ------_=_NextPart_001_01C641D7.8BF0612B Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi. During the 6lowpan interim meeting in January, the working group discussed possible topics for a future rechartering of 6lowpan. Based on available information from that meeting I've compiled the following text, which is an edited version of the scope present in the current 6lowpan charter. Feedback is appreciated.=20 --- start of scope --- Scope of 6lowpan: Produce "Optimization of the Neighbor Discovery Protocol for 6lowpans" to define how to apply the existing Neighbor Discovery protocol in a=20 6lowpan.=20 Produce "IPv6 over Low Power WPAN Security Analysis" to define the=20 assumptions for a security model for 6lowpan. This includes analysis of threats, identify types of devices and define the levels of trust between these devices. Produce "6lowpan Co-existence with other Networks" to define how to co-exist with other networks. This includes analysis of how to survive interference caused by IEEE 802.11 based networks, and investigate how to recognize and co-exist with other networks based on IEEE 802.15.4. As such, the working group may also work on an informational document to show how to apply an existing MANET protocol to LoWPANs (e.g., AODV, OLSR, DYMO, etc). The working group will reuse existing specifications whenever reasonable and possible. The working group will also serve as a venue for ongoing discussions on other topics related to the more complete list outlined above. Additional related milestones may be added in the future via a rechartering operation. Note: As may be obvious from its official name above, this particular working group will not work on IPv4 over IEEE 802.15.4 specifications. Given the limitations of the target devices, dual-stack deployments are not practical. Because of its higher potential for header compression, its support for the huge number of devices expected and of cleanly built-in features such as address autoconfiguration, IPv6 is the exclusive focus of the working group. --- end of scope --- Looking forward to receive your feedback. Regards Christian PS: The original charter can be found at http://www.ietf.org/html.charters/6lowpan-charter.html ------_=_NextPart_001_01C641D7.8BF0612B Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable new 6lowpan charter

Hi.

During the 6lowpan interim = meeting in January, the working group discussed possible topics for a = future rechartering of 6lowpan. Based on available information from that = meeting I've compiled the following text, which is an edited version of = the scope present in the current 6lowpan charter. Feedback is = appreciated.

--- start of scope ---

Scope of 6lowpan:

Produce "Optimization of the = Neighbor Discovery Protocol for 6lowpans"
to define how to apply the = existing Neighbor Discovery protocol in a
6lowpan.

Produce "IPv6 over Low Power = WPAN Security Analysis" to define the
assumptions for a security model = for 6lowpan. This includes analysis
of threats, identify types of = devices and define the levels of trust
between these devices.

Produce "6lowpan = Co-existence with other Networks" to define how to
co-exist with other networks. = This includes analysis of how to survive
interference caused by IEEE = 802.11 based networks, and investigate how to
recognize and co-exist with = other networks based on IEEE 802.15.4.

As such, the working group may = also work on an informational document
to show how to apply an existing = MANET protocol to LoWPANs (e.g.,
AODV, OLSR, DYMO, etc).

The working group will reuse = existing specifications whenever
reasonable and possible.

The working group will also serve = as a venue for ongoing discussions
on other topics related to the = more complete list outlined above.
Additional related milestones = may be added in the future via a
rechartering operation.

Note: As may be obvious from its = official name above, this particular
working group will not work on = IPv4 over IEEE 802.15.4 specifications.
Given the limitations of the = target devices, dual-stack deployments
are not practical. Because of = its higher potential for header
compression, its support for the = huge number of devices expected and
of cleanly built-in features = such as address autoconfiguration, IPv6
is the exclusive focus of the = working group.

--- end of scope ---

Looking forward to receive your = feedback.

Regards
Christian

PS: The original charter can be = found at http://www.ietf.org/html.charters/6lowpan-charter.html

------_=_NextPart_001_01C641D7.8BF0612B-- --===============1138548196== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --===============1138548196==-- From 6lowpan-bounces@ietf.org Tue Mar 07 07:57:21 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGbke-0000lj-Qr; Tue, 07 Mar 2006 07:57:20 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGbkd-0000kx-N7 for 6lowpan@lists.ietf.org; Tue, 07 Mar 2006 07:57:19 -0500 Received: from xproxy.gmail.com ([66.249.82.199]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FGbka-0001B7-Or for 6lowpan@lists.ietf.org; Tue, 07 Mar 2006 07:57:19 -0500 Received: by xproxy.gmail.com with SMTP id s19so966204wxc for <6lowpan@lists.ietf.org>; Tue, 07 Mar 2006 04:57:16 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:return-receipt-to:from:to:cc:subject:date:message-id:mime-version:content-type:x-mailer:in-reply-to:thread-index:x-mimeole:disposition-notification-to; b=mgQ3ucc8BSi4nevDwtaGMjl/Ydbyb3BKyUyscCr8EaQlgiP5y9PIUIUov5vfPHXbIzL09qsmZLmWwf6K4RNkK/hoLItL1wn9Zpy0UyT8W33oDh/9YV0NXlJxirlFBqXomnfbPpLwAWWvMz3F48zfBCDMmaq7Ib6XxCp+CWEUEF0= Received: by 10.70.91.7 with SMTP id o7mr1012484wxb; Tue, 07 Mar 2006 04:57:16 -0800 (PST) Received: from ncman ( [202.30.3.195]) by mx.gmail.com with ESMTP id i36sm520451wxd.2006.03.07.04.57.13; Tue, 07 Mar 2006 04:57:15 -0800 (PST) From: "Ki-Hyung Kim" To: "'Schumacher Christian Peter Pii'" Subject: RE: [6lowpan] new 6lowpan charter Date: Tue, 7 Mar 2006 21:57:04 +0900 Message-ID: MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <49A38D2FE2C53946A57916AD6A1F00D77DB48D@DKDN01MX34.danfoss.net> Thread-Index: AcZB14toHwySxQ5BQ6WUHbNZm5KIAwACK2hw X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.6 (/) X-Scan-Signature: 2df02f1a0db129c5d94869f6959903ec Cc: 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1193032478==" Errors-To: 6lowpan-bounces@ietf.org This is a multi-part message in MIME format. --===============1193032478== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0791_01C64232.14EE2FF0" This is a multi-part message in MIME format. ------=_NextPart_000_0791_01C64232.14EE2FF0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, Schumacher, As I remember, there were some additional rechartering items which we had reached on consensus in the last interim meeting, such as mesh routing protocols, service discovery, scalability (routing and addressing) and management. Is there anything I don't know during the time or any reason why we can't move forward on these issues? -- Ki-Hyung Kim Associate Professor Division of Information and Computer Engineering, Ajou University, Suwon, Korea 442-749 Tel: +82-31-219-2433, Cel: +82-17-760-2551, Fax: +82-31-219-2433 http://ilab.ajou.ac.kr/kkim86/index.htm _____ From: Schumacher Christian Peter Pii [mailto:schumacher@danfoss.com] Sent: Tuesday, March 07, 2006 8:09 PM To: 6lowpan@lists.ietf.org Subject: [6lowpan] new 6lowpan charter Hi. During the 6lowpan interim meeting in January, the working group discussed possible topics for a future rechartering of 6lowpan. Based on available information from that meeting I've compiled the following text, which is an edited version of the scope present in the current 6lowpan charter. Feedback is appreciated. --- start of scope --- Scope of 6lowpan: Produce "Optimization of the Neighbor Discovery Protocol for 6lowpans" to define how to apply the existing Neighbor Discovery protocol in a 6lowpan. Produce "IPv6 over Low Power WPAN Security Analysis" to define the assumptions for a security model for 6lowpan. This includes analysis of threats, identify types of devices and define the levels of trust between these devices. Produce "6lowpan Co-existence with other Networks" to define how to co-exist with other networks. This includes analysis of how to survive interference caused by IEEE 802.11 based networks, and investigate how to recognize and co-exist with other networks based on IEEE 802.15.4. As such, the working group may also work on an informational document to show how to apply an existing MANET protocol to LoWPANs (e.g., AODV, OLSR, DYMO, etc). The working group will reuse existing specifications whenever reasonable and possible. The working group will also serve as a venue for ongoing discussions on other topics related to the more complete list outlined above. Additional related milestones may be added in the future via a rechartering operation. Note: As may be obvious from its official name above, this particular working group will not work on IPv4 over IEEE 802.15.4 specifications. Given the limitations of the target devices, dual-stack deployments are not practical. Because of its higher potential for header compression, its support for the huge number of devices expected and of cleanly built-in features such as address autoconfiguration, IPv6 is the exclusive focus of the working group. --- end of scope --- Looking forward to receive your feedback. Regards Christian PS: The original charter can be found at http://www.ietf.org/html.charters/6lowpan-charter.html ------=_NextPart_000_0791_01C64232.14EE2FF0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable new 6lowpan charter

Hi, Schumacher,

 =

As = I remember, there were some additional rechartering items which we had reached on = consensus in the last interim meeting, such as mesh routing protocols, service = discovery, scalability (routing and addressing) and = management.

 =

Is = there anything I don’t know during the time or any reason why = we can’t move forward on these = issues?

From: Schumacher Christian Peter Pii [mailto:schumacher@danfoss.com]
Sent: Tuesday, March 07, = 2006 8:09 = PM
To: = 6lowpan@lists.ietf.org
Subject: [6lowpan] new = 6lowpan charter

 

Hi. =

During the 6lowpan interim meeting in = January, the working group discussed possible topics for a future rechartering of = 6lowpan. Based on available information from that meeting I've compiled the = following text, which is an edited version of the scope present in the current = 6lowpan charter. Feedback is appreciated.

--- start of scope ---

Scope of 6lowpan:

Produce "Optimization of the Neighbor = Discovery Protocol for 6lowpans"
to define how to apply the existing Neighbor Discovery protocol in a
6lowpan.

Produce "IPv6 over Low Power WPAN = Security Analysis" to define the
assumptions for a security model for 6lowpan. = This includes analysis
of threats, identify types of devices and = define the levels of trust
between these devices.

Produce "6lowpan Co-existence with other Networks" to define how to
co-exist with other networks. This includes = analysis of how to survive
interference caused by IEEE 802.11 based = networks, and investigate how to
recognize and co-exist with other networks = based on IEEE 802.15.4.

As such, the working group may also work on = an informational document
to show how to apply an existing MANET = protocol to LoWPANs (e.g.,
AODV, OLSR, DYMO, etc).

The working group will reuse existing = specifications whenever
reasonable and possible.

The working group will also serve as a venue = for ongoing discussions
on other topics related to the more complete = list outlined above.
Additional related milestones may be added in = the future via a
rechartering operation.

Note: As may be obvious from its official = name above, this particular
working group will not work on IPv4 over IEEE 802.15.4 specifications.
Given the limitations of the target devices, dual-stack deployments
are not practical. Because of its higher = potential for header
compression, its support for the huge number = of devices expected and
of cleanly built-in features such as address autoconfiguration, IPv6
is the exclusive focus of the working = group.

--- end of scope ---

Looking forward to receive your = feedback.

Regards
Christian =

PS: The original charter can be found at = http://www.ietf.org/html.charters/6lowpan-charter.html

------=_NextPart_000_0791_01C64232.14EE2FF0-- --===============1193032478== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --===============1193032478==-- From 6lowpan-bounces@ietf.org Tue Mar 07 08:17:24 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGc42-0008P1-4f; Tue, 07 Mar 2006 08:17:22 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGc3P-0007mP-JG for 6lowpan@lists.ietf.org; Tue, 07 Mar 2006 08:16:43 -0500 Received: from mailx.danfoss.com ([193.162.34.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FGbsm-0001Kq-GP for 6lowpan@lists.ietf.org; Tue, 07 Mar 2006 08:05:47 -0500 Received: from DKDN04MX64.dkdn04.danfoss.net ([10.6.2.64]) by mailx.danfoss.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 7 Mar 2006 14:05:43 +0100 Received: from dkdn01mx22.danfoss.net ([10.12.129.22]) by DKDN04MX64.dkdn04.danfoss.net with InterScan Message Security Suite; Tue, 07 Mar 2006 14:05:43 +0100 Received: from DKDN01MX34.danfoss.net ([10.12.128.14]) by dkdn01mx22.danfoss.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 7 Mar 2006 14:05:43 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [6lowpan] new 6lowpan charter Date: Tue, 7 Mar 2006 14:05:41 +0100 Message-ID: <49A38D2FE2C53946A57916AD6A1F00D77DB4C7@DKDN01MX34.danfoss.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [6lowpan] new 6lowpan charter Thread-Index: AcZB14toHwySxQ5BQ6WUHbNZm5KIAwACK2hwAAGmIhA= From: "Schumacher Christian Peter Pii" To: "Ki-Hyung Kim" X-OriginalArrivalTime: 07 Mar 2006 13:05:43.0038 (UTC) FILETIME=[D733B9E0:01C641E7] X-Spam-Score: 0.1 (/) X-Scan-Signature: 645960076aa293effd9740db2f975dc3 Cc: 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0422936114==" Errors-To: 6lowpan-bounces@ietf.org This is a multi-part message in MIME format. --===============0422936114== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C641E7.D6C7BD06" This is a multi-part message in MIME format. ------_=_NextPart_001_01C641E7.D6C7BD06 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Kim =20 Unfortunately there doesn't seem to be any official minutes from the interim meeting in January, and I assumed we only wanted to focus on a few of these points. However, if you could provide some key-words for these other items you mentioned, I would be happy to incorporate them into the text. =20 Regards Christian ________________________________ From: Ki-Hyung Kim [mailto:kkim86@gmail.com]=20 Sent: 7. marts 2006 13:57 To: Schumacher Christian Peter Pii Cc: 6lowpan@lists.ietf.org Subject: RE: [6lowpan] new 6lowpan charter Hi, Schumacher, =20 As I remember, there were some additional rechartering items which we had reached on consensus in the last interim meeting, such as mesh routing protocols, service discovery, scalability (routing and addressing) and management. =20 Is there anything I don't know during the time or any reason why we can't move forward on these issues? =20 =20 =20 -- Ki-Hyung Kim Associate Professor Division of Information and Computer Engineering, Ajou University, Suwon, Korea 442-749 Tel: +82-31-219-2433, Cel: +82-17-760-2551, Fax: +82-31-219-2433 http://ilab.ajou.ac.kr/kkim86/index.htm =20 ________________________________ From: Schumacher Christian Peter Pii [mailto:schumacher@danfoss.com]=20 Sent: Tuesday, March 07, 2006 8:09 PM To: 6lowpan@lists.ietf.org Subject: [6lowpan] new 6lowpan charter =20 Hi.=20 During the 6lowpan interim meeting in January, the working group discussed possible topics for a future rechartering of 6lowpan. Based on available information from that meeting I've compiled the following text, which is an edited version of the scope present in the current 6lowpan charter. Feedback is appreciated.=20 --- start of scope ---=20 Scope of 6lowpan:=20 Produce "Optimization of the Neighbor Discovery Protocol for 6lowpans"=20 to define how to apply the existing Neighbor Discovery protocol in a=20 6lowpan.=20 Produce "IPv6 over Low Power WPAN Security Analysis" to define the=20 assumptions for a security model for 6lowpan. This includes analysis=20 of threats, identify types of devices and define the levels of trust=20 between these devices.=20 Produce "6lowpan Co-existence with other Networks" to define how to=20 co-exist with other networks. This includes analysis of how to survive=20 interference caused by IEEE 802.11 based networks, and investigate how to=20 recognize and co-exist with other networks based on IEEE 802.15.4.=20 As such, the working group may also work on an informational document=20 to show how to apply an existing MANET protocol to LoWPANs (e.g.,=20 AODV, OLSR, DYMO, etc).=20 The working group will reuse existing specifications whenever=20 reasonable and possible.=20 The working group will also serve as a venue for ongoing discussions=20 on other topics related to the more complete list outlined above.=20 Additional related milestones may be added in the future via a=20 rechartering operation.=20 Note: As may be obvious from its official name above, this particular=20 working group will not work on IPv4 over IEEE 802.15.4 specifications.=20 Given the limitations of the target devices, dual-stack deployments=20 are not practical. Because of its higher potential for header=20 compression, its support for the huge number of devices expected and=20 of cleanly built-in features such as address autoconfiguration, IPv6=20 is the exclusive focus of the working group.=20 --- end of scope ---=20 Looking forward to receive your feedback.=20 Regards=20 Christian=20 PS: The original charter can be found at http://www.ietf.org/html.charters/6lowpan-charter.html =20 ------_=_NextPart_001_01C641E7.D6C7BD06 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable new 6lowpan = charter
Hi Kim
 
Unfortunately there doesn't seem to be any = official minutes=20 from the interim meeting in January, and I = assumed we only=20 wanted to focus on a few of these points. However, if you could = provide=20 some key-words for these other items you mentioned, I would be happy to=20 incorporate them into the text.
 
Regards
Christian

From: Ki-Hyung Kim = [mailto:kkim86@gmail.com]=20
Sent: 7. marts 2006 13:57
To: Schumacher Christian = Peter=20 Pii
Cc: 6lowpan@lists.ietf.org
Subject: RE: = [6lowpan] new=20 6lowpan charter

Hi,=20 Schumacher,

 

As I = remember, there=20 were some additional rechartering items which we had reached on = consensus in the=20 last interim meeting, such as mesh routing protocols, service discovery, = scalability (routing and addressing) and=20 management.

 

Is there = anything I=20 don’t know during = the time=20 or any reason why we can’t move = forward on these=20 issues?

 

 

 

--

Ki-Hyung=20 Kim

Associate=20 Professor

Division of=20 Information and Computer Engineering,

Ajou University, Suwon, Korea=20 442-749

Tel:=20 +82-31-219-2433, Cel: +82-17-760-2551,  Fax:=20 +82-31-219-2433

http://ilab.ajou.ac.kr/kkim86/index.htm<= /FONT> =20

From: Schumacher Christian = Peter Pii=20 [mailto:schumacher@danfoss.com]
Sent: Tuesday, March 07, 2006 = 8:09 = PM
To: = 6lowpan@lists.ietf.org
Subject: [6lowpan] new 6lowpan=20 charter

 

Hi.

During the 6lowpan = interim=20 meeting in January, the working group discussed possible topics for a = future=20 rechartering of 6lowpan. Based on available information from that = meeting I've=20 compiled the following text, which is an edited version of the scope = present in=20 the current 6lowpan charter. Feedback is appreciated. =

--- start of scope = ---

Scope of=20 6lowpan:

Produce = "Optimization of the=20 Neighbor Discovery Protocol for 6lowpans"=20
to define how to = apply the=20 existing Neighbor Discovery protocol in a
6lowpan. =

Produce "IPv6 over = Low Power=20 WPAN Security Analysis" to define the
assumptions for a = security=20 model for 6lowpan. This includes analysis=20
of threats, = identify types=20 of devices and define the levels of trust=20
between these=20 devices.

Produce "6lowpan=20 Co-existence with other Networks" to define how to
co-exist with = other=20 networks. This includes analysis of how to survive
interference = caused by IEEE=20 802.11 based networks, and investigate how to=20
recognize and = co-exist with=20 other networks based on IEEE 802.15.4.=20

As such, the = working group=20 may also work on an informational document=20
to show how to = apply an=20 existing MANET protocol to LoWPANs (e.g.,=20
AODV, OLSR, DYMO,=20 etc).

The working group = will reuse=20 existing specifications whenever =
reasonable and=20 possible.

The working group = will also=20 serve as a venue for ongoing discussions=20
on other topics = related to=20 the more complete list outlined above.=20
Additional related = milestones may be added in the future via a=20
rechartering=20 operation.

Note: As may be = obvious from=20 its official name above, this particular=20
working group will = not work=20 on IPv4 over IEEE 802.15.4 specifications.=20
Given the = limitations of the=20 target devices, dual-stack deployments=20
are not practical. = Because=20 of its higher potential for header=20
compression, its = support for=20 the huge number of devices expected and =
of cleanly = built-in features=20 such as address autoconfiguration, IPv6 =
is the exclusive = focus of=20 the working group. =

--- end of scope=20 ---

Looking forward to = receive=20 your feedback.

Regards
Christian

PS: The original = charter can=20 be found at http://www.ietf.org/html.charters/6lowpan-charter.html=20

------_=_NextPart_001_01C641E7.D6C7BD06-- --===============0422936114== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --===============0422936114==-- From 6lowpan-bounces@ietf.org Tue Mar 07 10:49:44 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGeRT-0005N4-KV; Tue, 07 Mar 2006 10:49:43 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGeRT-0005Mq-2S for 6lowpan@lists.ietf.org; Tue, 07 Mar 2006 10:49:43 -0500 Received: from szxga02-in.huawei.com ([61.144.161.54] helo=huawei.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FGeRR-0007Y8-CJ for 6lowpan@lists.ietf.org; Tue, 07 Mar 2006 10:49:43 -0500 Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IVR001R0LT96C@szxga02-in.huawei.com> for 6lowpan@lists.ietf.org; Wed, 08 Mar 2006 00:00:46 +0800 (CST) Received: from szxml01-in ([172.24.1.3]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IVR0087OLRD2E@szxga02-in.huawei.com> for 6lowpan@lists.ietf.org; Wed, 08 Mar 2006 00:00:45 +0800 (CST) Received: from [10.124.8.172] by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0IVR00M12LS6GF@szxml01-in.huawei.com>; Wed, 08 Mar 2006 00:00:14 +0800 (CST) Date: Tue, 07 Mar 2006 09:43:41 -0600 From: Behcet Sarikaya Subject: Re: [6lowpan] new 6lowpan charter In-reply-to: <49A38D2FE2C53946A57916AD6A1F00D77DB4C7@DKDN01MX34.danfoss.net> To: 6lowpan@lists.ietf.org Message-id: <440DAA2D.6080608@yahoo.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) References: <49A38D2FE2C53946A57916AD6A1F00D77DB4C7@DKDN01MX34.danfoss.net> X-Spam-Score: 2.2 (++) X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed Cc: X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Behcet Sarikaya List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org I am also for adding the cases where fully functional devices (FFD) not being sensor nodes and gateway protocols into the charter reflecting state-of-the-art in wireless sensor networks. Thanks. --behcet _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Tue Mar 07 16:39:18 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGjtk-000212-Ht; Tue, 07 Mar 2006 16:39:16 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGjt2-0000sa-0m for 6lowpan@lists.ietf.org; Tue, 07 Mar 2006 16:38:32 -0500 Received: from mailout2.samsung.com ([203.254.224.25]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FGjkH-0008Bg-20 for 6lowpan@lists.ietf.org; Tue, 07 Mar 2006 16:29:29 -0500 Received: from ep_mmp1 (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 <0IVS00L74113R2@mailout2.samsung.com> for 6lowpan@lists.ietf.org; Wed, 08 Mar 2006 06:29:27 +0900 (KST) Received: from daniellaptop ([124.235.139.2]) by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTPA id <0IVS004ZP111FD@mmp1.samsung.com> for 6lowpan@lists.ietf.org; Wed, 08 Mar 2006 06:29:27 +0900 (KST) Date: Wed, 08 Mar 2006 06:29:35 +0900 From: Soohong Daniel Park Subject: Re: [6lowpan] new 6lowpan charter To: Schumacher Christian Peter Pii , 6lowpan@lists.ietf.org Message-id: <036501c6422e$3c947950$45706f0a@daniellaptop> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-Priority: 3 X-MSMail-priority: Normal References: <49A38D2FE2C53946A57916AD6A1F00D77DB48D@DKDN01MX34.danfoss.net> X-Spam-Score: 0.1 (/) X-Scan-Signature: 4b7d60495f1a7f2e853e8cbae7e6dbfc Cc: 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0949363763==" Errors-To: 6lowpan-bounces@ietf.org This is a multi-part message in MIME format. --===============0949363763== Content-type: multipart/alternative; boundary="Boundary_(ID_H9daFGmWuXtw1vaR2jckDA)" This is a multi-part message in MIME format. --Boundary_(ID_H9daFGmWuXtw1vaR2jckDA) Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT new 6lowpan charterChristian - Let me clarify one point. Is this announcement an official rechartering discussion agreed with Chairs/ADs views ? Geoff and Carsten, Christian is responsible for rechartering work instead of you ? Thanks, Daniel (Soohong Daniel Park) Mobile Convergence Laboratory, SAMSUNG Electronics. ----- Original Message ----- From: Schumacher Christian Peter Pii To: 6lowpan@lists.ietf.org Sent: Tuesday, March 07, 2006 8:09 PM Subject: [6lowpan] new 6lowpan charter Hi. During the 6lowpan interim meeting in January, the working group discussed possible topics for a future rechartering of 6lowpan. Based on available information from that meeting I've compiled the following text, which is an edited version of the scope present in the current 6lowpan charter. Feedback is appreciated. --- start of scope --- Scope of 6lowpan: Produce "Optimization of the Neighbor Discovery Protocol for 6lowpans" to define how to apply the existing Neighbor Discovery protocol in a 6lowpan. Produce "IPv6 over Low Power WPAN Security Analysis" to define the assumptions for a security model for 6lowpan. This includes analysis of threats, identify types of devices and define the levels of trust between these devices. Produce "6lowpan Co-existence with other Networks" to define how to co-exist with other networks. This includes analysis of how to survive interference caused by IEEE 802.11 based networks, and investigate how to recognize and co-exist with other networks based on IEEE 802.15.4. As such, the working group may also work on an informational document to show how to apply an existing MANET protocol to LoWPANs (e.g., AODV, OLSR, DYMO, etc). The working group will reuse existing specifications whenever reasonable and possible. The working group will also serve as a venue for ongoing discussions on other topics related to the more complete list outlined above. Additional related milestones may be added in the future via a rechartering operation. Note: As may be obvious from its official name above, this particular working group will not work on IPv4 over IEEE 802.15.4 specifications. Given the limitations of the target devices, dual-stack deployments are not practical. Because of its higher potential for header compression, its support for the huge number of devices expected and of cleanly built-in features such as address autoconfiguration, IPv6 is the exclusive focus of the working group. --- end of scope --- Looking forward to receive your feedback. Regards Christian PS: The original charter can be found at http://www.ietf.org/html.charters/6lowpan-charter.html ------------------------------------------------------------------------------ _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --Boundary_(ID_H9daFGmWuXtw1vaR2jckDA) Content-type: text/html; charset=ISO-8859-1 Content-transfer-encoding: 7BIT new 6lowpan charter
Christian - Let me clarify one point. Is this announcement
an official rechartering discussion agreed with Chairs/ADs
views ? Geoff and Carsten, Christian is responsible for
rechartering work instead of you ?
 
Thanks,
 
Daniel (Soohong Daniel Park)
Mobile Convergence Laboratory, SAMSUNG Electronics.
----- Original Message -----
Sent: Tuesday, March 07, 2006 8:09 PM
Subject: [6lowpan] new 6lowpan charter

Hi.

During the 6lowpan interim meeting in January, the working group discussed possible topics for a future rechartering of 6lowpan. Based on available information from that meeting I've compiled the following text, which is an edited version of the scope present in the current 6lowpan charter. Feedback is appreciated.

--- start of scope ---

Scope of 6lowpan:

Produce "Optimization of the Neighbor Discovery Protocol for 6lowpans"
to define how to apply the existing Neighbor Discovery protocol in a
6lowpan.

Produce "IPv6 over Low Power WPAN Security Analysis" to define the
assumptions for a security model for 6lowpan. This includes analysis
of threats, identify types of devices and define the levels of trust
between these devices.

Produce "6lowpan Co-existence with other Networks" to define how to
co-exist with other networks. This includes analysis of how to survive
interference caused by IEEE 802.11 based networks, and investigate how to
recognize and co-exist with other networks based on IEEE 802.15.4.

As such, the working group may also work on an informational document
to show how to apply an existing MANET protocol to LoWPANs (e.g.,
AODV, OLSR, DYMO, etc).

The working group will reuse existing specifications whenever
reasonable and possible.

The working group will also serve as a venue for ongoing discussions
on other topics related to the more complete list outlined above.
Additional related milestones may be added in the future via a
rechartering operation.

Note: As may be obvious from its official name above, this particular
working group will not work on IPv4 over IEEE 802.15.4 specifications.
Given the limitations of the target devices, dual-stack deployments
are not practical. Because of its higher potential for header
compression, its support for the huge number of devices expected and
of cleanly built-in features such as address autoconfiguration, IPv6
is the exclusive focus of the working group.

--- end of scope ---

Looking forward to receive your feedback.

Regards
Christian

PS: The original charter can be found at http://www.ietf.org/html.charters/6lowpan-charter.html

_______________________________________________
6lowpan mailing list
6lowpan@ietf.org
https://www1.ietf.org/mailman/listinfo/6lowpan
--Boundary_(ID_H9daFGmWuXtw1vaR2jckDA)-- --===============0949363763== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --===============0949363763==-- From 6lowpan-bounces@ietf.org Tue Mar 07 20:59:05 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGnxA-0004m8-Mm; Tue, 07 Mar 2006 20:59:04 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGnx8-0004jr-Mu for 6lowpan@lists.ietf.org; Tue, 07 Mar 2006 20:59:02 -0500 Received: from pop3.ajou.ac.kr ([202.30.0.18] helo=mail.ajou.ac.kr) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FGnx6-0007qU-0W for 6lowpan@lists.ietf.org; Tue, 07 Mar 2006 20:59:02 -0500 Received: from spam.ajou.ac.kr ([202.30.0.9]) by maru (Crinity Message Backbone-2.8) with SMTP ID 536; Wed, 8 Mar 2006 11:00:42 +0900 (KST) Received: from 202.30.3.195 ([202.30.3.195]) by seodang.ajou.ac.kr (Spambreaker ESMTP Server); Wed, 8 Mar 2006 10:58:45 +0900 (KST) From: Ki-Hyung Kim To: 'Schumacher Christian Peter Pii' Subject: RE: [6lowpan] new 6lowpan charter Date: Wed, 8 Mar 2006 10:58:39 +0900 Message-ID: MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <49A38D2FE2C53946A57916AD6A1F00D77DB4C7@DKDN01MX34.danfoss.net> Thread-Index: AcZB14toHwySxQ5BQ6WUHbNZm5KIAwACK2hwAAGmIhAAGsT70A== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 2.1 (++) X-Scan-Signature: acbee687725127cbf106f41c48a81403 Cc: 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1391548996==" Errors-To: 6lowpan-bounces@ietf.org This is a multi-part message in MIME format. --===============1391548996== Content-Type: multipart/alternative; boundary="----=_NextPart_000_089D_01C6429F.41E94E00" This is a multi-part message in MIME format. ------=_NextPart_000_089D_01C6429F.41E94E00 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi Christian, I am curious why the official minutes are not available yet, but there were such items we had mentioned. Anyway, the following items were discussed and summarized by Carsten(? If my memory is correct) as rechartering items on the last interim meeting. 1) Mesh routing protocol 2) Service discovery 3) Scalability of 6lowpan (routing and addressing) 4) Mobility issues 5) Naming service for mesh layer 6) Gateway architecture (This item was discussed as "HC compression" on the last meeting) If you need polished statements for these items, let me know. Regards, -- Ki-Hyung Kim Associate Professor Division of Information and Computer Engineering, Ajou University, Suwon, Korea 442-749 Tel: +82-31-219-2433, Cel: +82-17-760-2551, Fax: +82-31-219-2433 http://ilab.ajou.ac.kr/kkim86/index.htm _____ From: Schumacher Christian Peter Pii [mailto:schumacher@danfoss.com] Sent: Tuesday, March 07, 2006 10:06 PM To: Ki-Hyung Kim Cc: 6lowpan@lists.ietf.org Subject: RE: [6lowpan] new 6lowpan charter Hi Kim Unfortunately there doesn't seem to be any official minutes from the interim meeting in January, and I assumed we only wanted to focus on a few of these points. However, if you could provide some key-words for these other items you mentioned, I would be happy to incorporate them into the text. Regards Christian _____ From: Ki-Hyung Kim [mailto:kkim86@gmail.com] Sent: 7. marts 2006 13:57 To: Schumacher Christian Peter Pii Cc: 6lowpan@lists.ietf.org Subject: RE: [6lowpan] new 6lowpan charter Hi, Schumacher, As I remember, there were some additional rechartering items which we had reached on consensus in the last interim meeting, such as mesh routing protocols, service discovery, scalability (routing and addressing) and management. Is there anything I don't know during the time or any reason why we can't move forward on these issues? -- Ki-Hyung Kim Associate Professor Division of Information and Computer Engineering, Ajou University, Suwon, Korea 442-749 Tel: +82-31-219-2433, Cel: +82-17-760-2551, Fax: +82-31-219-2433 http://ilab.ajou.ac.kr/kkim86/index.htm _____ From: Schumacher Christian Peter Pii [mailto:schumacher@danfoss.com] Sent: Tuesday, March 07, 2006 8:09 PM To: 6lowpan@lists.ietf.org Subject: [6lowpan] new 6lowpan charter Hi. During the 6lowpan interim meeting in January, the working group discussed possible topics for a future rechartering of 6lowpan. Based on available information from that meeting I've compiled the following text, which is an edited version of the scope present in the current 6lowpan charter. Feedback is appreciated. --- start of scope --- Scope of 6lowpan: Produce "Optimization of the Neighbor Discovery Protocol for 6lowpans" to define how to apply the existing Neighbor Discovery protocol in a 6lowpan. Produce "IPv6 over Low Power WPAN Security Analysis" to define the assumptions for a security model for 6lowpan. This includes analysis of threats, identify types of devices and define the levels of trust between these devices. Produce "6lowpan Co-existence with other Networks" to define how to co-exist with other networks. This includes analysis of how to survive interference caused by IEEE 802.11 based networks, and investigate how to recognize and co-exist with other networks based on IEEE 802.15.4. As such, the working group may also work on an informational document to show how to apply an existing MANET protocol to LoWPANs (e.g., AODV, OLSR, DYMO, etc). The working group will reuse existing specifications whenever reasonable and possible. The working group will also serve as a venue for ongoing discussions on other topics related to the more complete list outlined above. Additional related milestones may be added in the future via a rechartering operation. Note: As may be obvious from its official name above, this particular working group will not work on IPv4 over IEEE 802.15.4 specifications. Given the limitations of the target devices, dual-stack deployments are not practical. Because of its higher potential for header compression, its support for the huge number of devices expected and of cleanly built-in features such as address autoconfiguration, IPv6 is the exclusive focus of the working group. --- end of scope --- Looking forward to receive your feedback. Regards Christian PS: The original charter can be found at http://www.ietf.org/html.charters/6lowpan-charter.html ------=_NextPart_000_089D_01C6429F.41E94E00 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable new 6lowpan charter

Hi = Christian,

I = am curious why the official minutes are not available yet, but there were such = items we had mentioned.

Anyway, the following items were discussed and summarized by Carsten(? If my memory = is correct) as rechartering items on the last interim = meeting.

 =

1) = Mesh routing protocol

2) = Service discovery

3) = Scalability of 6lowpan (routing and addressing)

4) = Mobility issues

5) = Naming service for mesh layer

6) Gateway architecture (This item was discussed as “HC compression” on the last = meeting)

 

If you need polished statements for = these items, let me know.

 

Regards,

 

--

Ki-Hyung Kim

Associate = Professor

Division of Information and Computer = Engineering,

Ajou University, = Suwon, Korea 442-749

Tel: +82-31-219-2433, Cel: = +82-17-760-2551,  Fax: +82-31-219-2433

http://ilab.ajou.ac.kr/kkim86/index.htm<= /font>  =

From: Schumacher Christian Peter Pii [mailto:schumacher@danfoss.com]
Sent: Tuesday, March 07, = 2006 10:06 = PM
To: Ki-Hyung Kim
Cc: = 6lowpan@lists.ietf.org
Subject: RE: [6lowpan] = new 6lowpan charter

 

Hi = Kim

 

Unfortunately = there doesn't seem to be any official minutes from the interim meeting in January, and I assumed we only wanted to focus on a few of these = points. However, if you could provide some key-words for these other items you mentioned, I would be happy to incorporate them into the = text.

 

Regards

Christian<= /font>

 

From: Ki-Hyung Kim [mailto:kkim86@gmail.com]
Sent: 7. marts 2006 = 13:57
To: Schumacher Christian = Peter Pii
Cc: = 6lowpan@lists.ietf.org
Subject: RE: [6lowpan] = new 6lowpan charter

Hi, Schumacher,

 =

As = I remember, there were some additional rechartering items which we had reached on = consensus in the last interim meeting, such as mesh routing protocols, service = discovery, scalability (routing and addressing) and = management.

 =

Is = there anything I don’t know during the time or any reason why = we can’t move forward on these = issues?

 

 

 

--

Ki-Hyung Kim

Associate = Professor

Division of Information and Computer = Engineering,

Ajou University, Suwon, Korea = 442-749

Tel: +82-31-219-2433, Cel: = +82-17-760-2551,  Fax: +82-31-219-2433

http://ilab.ajou.ac.kr/kkim86/index.htm<= /font>  =

From: Schumacher Christian Peter Pii [mailto:schumacher@danfoss.com]
Sent: Tuesday, March 07, = 2006 8:09 = PM
To: = 6lowpan@lists.ietf.org
Subject: [6lowpan] new = 6lowpan charter

 

Hi. =

During the 6lowpan interim meeting in = January, the working group discussed possible topics for a future rechartering of = 6lowpan. Based on available information from that meeting I've compiled the = following text, which is an edited version of the scope present in the current = 6lowpan charter. Feedback is appreciated.

--- start of scope ---

Scope of 6lowpan:

Produce "Optimization of the Neighbor = Discovery Protocol for 6lowpans"
to define how to apply the existing Neighbor Discovery protocol in a
6lowpan.

Produce "IPv6 over Low Power WPAN = Security Analysis" to define the
assumptions for a security model for 6lowpan. = This includes analysis
of threats, identify types of devices and = define the levels of trust
between these devices.

Produce "6lowpan Co-existence with other Networks" to define how to
co-exist with other networks. This includes = analysis of how to survive
interference caused by IEEE 802.11 based = networks, and investigate how to
recognize and co-exist with other networks = based on IEEE 802.15.4.

As such, the working group may also work on = an informational document
to show how to apply an existing MANET = protocol to LoWPANs (e.g.,
AODV, OLSR, DYMO, etc).

The working group will reuse existing = specifications whenever
reasonable and possible.

The working group will also serve as a venue = for ongoing discussions
on other topics related to the more complete = list outlined above.
Additional related milestones may be added in = the future via a
rechartering operation.

Note: As may be obvious from its official = name above, this particular
working group will not work on IPv4 over IEEE 802.15.4 specifications.
Given the limitations of the target devices, dual-stack deployments
are not practical. Because of its higher = potential for header
compression, its support for the huge number = of devices expected and
of cleanly built-in features such as address autoconfiguration, IPv6
is the exclusive focus of the working = group.

--- end of scope ---

Looking forward to receive your = feedback.

Regards
Christian =

PS: The original charter can be found at = http://www.ietf.org/html.charters/6lowpan-charter.html

------=_NextPart_000_089D_01C6429F.41E94E00-- --===============1391548996== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --===============1391548996==-- From 6lowpan-bounces@ietf.org Wed Mar 08 03:19:42 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGttU-0000UE-6D; Wed, 08 Mar 2006 03:19:40 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGtTp-00021a-12 for 6lowpan@lists.ietf.org; Wed, 08 Mar 2006 02:53:09 -0500 Received: from mailx.danfoss.com ([193.162.34.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FGtTl-0002J3-Hc for 6lowpan@lists.ietf.org; Wed, 08 Mar 2006 02:53:07 -0500 Received: from DKDN04MX62.dkdn04.danfoss.net ([10.6.2.62]) by mailx.danfoss.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 8 Mar 2006 08:51:04 +0100 Received: from dkdn01mx21.danfoss.net ([10.12.129.21]) by DKDN04MX62.dkdn04.danfoss.net with InterScan Message Security Suite; Wed, 08 Mar 2006 08:51:03 +0100 Received: from DKDN01MX34.danfoss.net ([10.12.128.14]) by dkdn01mx21.danfoss.net with Microsoft SMTPSVC(6.0.3790.1830); Wed, 8 Mar 2006 08:51:03 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [6lowpan] new 6lowpan charter Date: Wed, 8 Mar 2006 08:51:02 +0100 Message-ID: <49A38D2FE2C53946A57916AD6A1F00D77DB525@DKDN01MX34.danfoss.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [6lowpan] new 6lowpan charter Thread-Index: AcZB14toHwySxQ5BQ6WUHbNZm5KIAwACK2hwAAGmIhAAGsT70AAMfVyA From: "Schumacher Christian Peter Pii" To: "Ki-Hyung Kim" X-OriginalArrivalTime: 08 Mar 2006 07:51:03.0360 (UTC) FILETIME=[0C733C00:01C64285] X-Spam-Score: 0.1 (/) X-Scan-Signature: 0948f555ba0a8c21aad67160fcd59720 Cc: 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0000392459==" Errors-To: 6lowpan-bounces@ietf.org This is a multi-part message in MIME format. --===============0000392459== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C64285.0C26A08C" This is a multi-part message in MIME format. ------_=_NextPart_001_01C64285.0C26A08C Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Kim =20 It would be very helpful if you could provide me with polished statements for these items. =20 Regards Christian ________________________________ From: Ki-Hyung Kim [mailto:kkim86@ajou.ac.kr]=20 Sent: 8. marts 2006 02:59 To: Schumacher Christian Peter Pii Cc: 6lowpan@lists.ietf.org; 'Geoff Mulligan' Subject: RE: [6lowpan] new 6lowpan charter Hi Christian, I am curious why the official minutes are not available yet, but there were such items we had mentioned. Anyway, the following items were discussed and summarized by Carsten(? If my memory is correct) as rechartering items on the last interim meeting. =20 1) Mesh routing protocol 2) Service discovery 3) Scalability of 6lowpan (routing and addressing) 4) Mobility issues 5) Naming service for mesh layer 6) Gateway architecture (This item was discussed as "HC compression" on the last meeting) =20 If you need polished statements for these items, let me know. =20 Regards, =20 -- Ki-Hyung Kim Associate Professor Division of Information and Computer Engineering, Ajou University, Suwon, Korea 442-749 Tel: +82-31-219-2433, Cel: +82-17-760-2551, Fax: +82-31-219-2433 http://ilab.ajou.ac.kr/kkim86/index.htm =20 ________________________________ From: Schumacher Christian Peter Pii [mailto:schumacher@danfoss.com]=20 Sent: Tuesday, March 07, 2006 10:06 PM To: Ki-Hyung Kim Cc: 6lowpan@lists.ietf.org Subject: RE: [6lowpan] new 6lowpan charter =20 Hi Kim =20 Unfortunately there doesn't seem to be any official minutes from the interim meeting in January, and I assumed we only wanted to focus on a few of these points. However, if you could provide some key-words for these other items you mentioned, I would be happy to incorporate them into the text. =20 Regards Christian =20 ________________________________ From: Ki-Hyung Kim [mailto:kkim86@gmail.com]=20 Sent: 7. marts 2006 13:57 To: Schumacher Christian Peter Pii Cc: 6lowpan@lists.ietf.org Subject: RE: [6lowpan] new 6lowpan charter Hi, Schumacher, =20 As I remember, there were some additional rechartering items which we had reached on consensus in the last interim meeting, such as mesh routing protocols, service discovery, scalability (routing and addressing) and management. =20 Is there anything I don't know during the time or any reason why we can't move forward on these issues? =20 =20 =20 -- Ki-Hyung Kim Associate Professor Division of Information and Computer Engineering, Ajou University, Suwon, Korea 442-749 Tel: +82-31-219-2433, Cel: +82-17-760-2551, Fax: +82-31-219-2433 http://ilab.ajou.ac.kr/kkim86/index.htm =20 ________________________________ From: Schumacher Christian Peter Pii [mailto:schumacher@danfoss.com]=20 Sent: Tuesday, March 07, 2006 8:09 PM To: 6lowpan@lists.ietf.org Subject: [6lowpan] new 6lowpan charter =20 Hi.=20 During the 6lowpan interim meeting in January, the working group discussed possible topics for a future rechartering of 6lowpan. Based on available information from that meeting I've compiled the following text, which is an edited version of the scope present in the current 6lowpan charter. Feedback is appreciated.=20 --- start of scope ---=20 Scope of 6lowpan:=20 Produce "Optimization of the Neighbor Discovery Protocol for 6lowpans"=20 to define how to apply the existing Neighbor Discovery protocol in a=20 6lowpan.=20 Produce "IPv6 over Low Power WPAN Security Analysis" to define the=20 assumptions for a security model for 6lowpan. This includes analysis=20 of threats, identify types of devices and define the levels of trust=20 between these devices.=20 Produce "6lowpan Co-existence with other Networks" to define how to=20 co-exist with other networks. This includes analysis of how to survive=20 interference caused by IEEE 802.11 based networks, and investigate how to=20 recognize and co-exist with other networks based on IEEE 802.15.4.=20 As such, the working group may also work on an informational document=20 to show how to apply an existing MANET protocol to LoWPANs (e.g.,=20 AODV, OLSR, DYMO, etc).=20 The working group will reuse existing specifications whenever=20 reasonable and possible.=20 The working group will also serve as a venue for ongoing discussions=20 on other topics related to the more complete list outlined above.=20 Additional related milestones may be added in the future via a=20 rechartering operation.=20 Note: As may be obvious from its official name above, this particular=20 working group will not work on IPv4 over IEEE 802.15.4 specifications.=20 Given the limitations of the target devices, dual-stack deployments=20 are not practical. Because of its higher potential for header=20 compression, its support for the huge number of devices expected and=20 of cleanly built-in features such as address autoconfiguration, IPv6=20 is the exclusive focus of the working group.=20 --- end of scope ---=20 Looking forward to receive your feedback.=20 Regards=20 Christian=20 PS: The original charter can be found at http://www.ietf.org/html.charters/6lowpan-charter.html =20 ------_=_NextPart_001_01C64285.0C26A08C Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable new 6lowpan = charter
Hi Kim
 
It=20 would be very helpful if you could provide me with polished = statements for=20 these items.
 
Regards
Christian
From: Ki-Hyung Kim = [mailto:kkim86@ajou.ac.kr]=20
Sent: 8. marts 2006 02:59
To: Schumacher Christian = Peter=20 Pii
Cc: 6lowpan@lists.ietf.org; 'Geoff = Mulligan'
Subject:=20 RE: [6lowpan] new 6lowpan charter

Hi=20 Christian,

I am curious = why the=20 official minutes are not available yet, but there were such items we had = mentioned.

Anyway, the = following=20 items were discussed and summarized by Carsten(? If my memory is = correct) as=20 rechartering items on the last interim = meeting.

 

1) Mesh = routing=20 protocol

2) Service=20 discovery

3) = Scalability of=20 6lowpan (routing and addressing)

4) Mobility=20 issues

5) Naming = service for=20 mesh layer

6) Gateway = architecture (This item was discussed as “HC compression” on = the last=20 meeting)

 

If you = need polished=20 statements for these items, let me know.

 

Regards,

 

--

Ki-Hyung=20 Kim

Associate=20 Professor

Division of=20 Information and Computer Engineering,

Ajou University, Suwon, Korea=20 442-749

Tel:=20 +82-31-219-2433, Cel: +82-17-760-2551,  Fax:=20 +82-31-219-2433

http://ilab.ajou.ac.kr/kkim86/index.htm<= /FONT> =20

From: Schumacher Christian = Peter Pii=20 [mailto:schumacher@danfoss.com]
Sent: Tuesday, March 07, 2006 = 10:06 = PM
To: Ki-Hyung Kim
Cc: = 6lowpan@lists.ietf.org
Subject: RE: [6lowpan] new = 6lowpan=20 charter

 

Hi=20 Kim

 

Unfortunately = there=20 doesn't seem to be any official minutes from the interim meeting in = January, and I assumed we only wanted to focus on a few of these = points.=20 However, if you could provide some key-words for these other items you=20 mentioned, I would be happy to incorporate them into the=20 text.

 

Regards

Christian

 

From: Ki-Hyung Kim=20 [mailto:kkim86@gmail.com]
Sent: 7. marts 2006 13:57
To: Schumacher Christian Peter=20 Pii
Cc:=20 6lowpan@lists.ietf.org
Subject:=20 RE: [6lowpan] new 6lowpan charter

Hi,=20 Schumacher,

 

As I = remember, there=20 were some additional rechartering items which we had reached on = consensus in the=20 last interim meeting, such as mesh routing protocols, service discovery, = scalability (routing and addressing) and=20 management.

 

Is there = anything I=20 don’t know during = the time=20 or any reason why we can’t move = forward on these=20 issues?

 

 

 

--

Ki-Hyung=20 Kim

Associate=20 Professor

Division of=20 Information and Computer Engineering,

Ajou University,=20 Suwon,=20 Korea=20 442-749

Tel:=20 +82-31-219-2433, Cel: +82-17-760-2551,  Fax:=20 +82-31-219-2433

http://ilab.ajou.ac.kr/kkim86/index.htm<= /FONT> =20

From: Schumacher Christian = Peter Pii=20 [mailto:schumacher@danfoss.com]
Sent: Tuesday, March 07, 2006 = 8:09 = PM
To: = 6lowpan@lists.ietf.org
Subject: [6lowpan] new 6lowpan=20 charter

 

Hi.

During the 6lowpan = interim=20 meeting in January, the working group discussed possible topics for a = future=20 rechartering of 6lowpan. Based on available information from that = meeting I've=20 compiled the following text, which is an edited version of the scope = present in=20 the current 6lowpan charter. Feedback is appreciated. =

--- start of scope = ---

Scope of=20 6lowpan:

Produce = "Optimization of the=20 Neighbor Discovery Protocol for 6lowpans"=20
to define how to = apply the=20 existing Neighbor Discovery protocol in a
6lowpan. =

Produce "IPv6 over = Low Power=20 WPAN Security Analysis" to define the
assumptions for a = security=20 model for 6lowpan. This includes analysis=20
of threats, = identify types=20 of devices and define the levels of trust=20
between these=20 devices.

Produce "6lowpan=20 Co-existence with other Networks" to define how to
co-exist with = other=20 networks. This includes analysis of how to survive
interference = caused by IEEE=20 802.11 based networks, and investigate how to=20
recognize and = co-exist with=20 other networks based on IEEE 802.15.4.=20

As such, the = working group=20 may also work on an informational document=20
to show how to = apply an=20 existing MANET protocol to LoWPANs (e.g.,=20
AODV, OLSR, DYMO,=20 etc).

The working group = will reuse=20 existing specifications whenever =
reasonable and=20 possible.

The working group = will also=20 serve as a venue for ongoing discussions=20
on other topics = related to=20 the more complete list outlined above.=20
Additional related = milestones may be added in the future via a=20
rechartering=20 operation.

Note: As may be = obvious from=20 its official name above, this particular=20
working group will = not work=20 on IPv4 over IEEE 802.15.4 specifications.=20
Given the = limitations of the=20 target devices, dual-stack deployments=20
are not practical. = Because=20 of its higher potential for header=20
compression, its = support for=20 the huge number of devices expected and =
of cleanly = built-in features=20 such as address autoconfiguration, IPv6 =
is the exclusive = focus of=20 the working group. =

--- end of scope=20 ---

Looking forward to = receive=20 your feedback.

Regards
Christian

PS: The original = charter can=20 be found at http://www.ietf.org/html.charters/6lowpan-charter.html=20

------_=_NextPart_001_01C64285.0C26A08C-- --===============0000392459== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --===============0000392459==-- From 6lowpan-bounces@ietf.org Wed Mar 08 04:00:16 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGuWk-0003BF-8J; Wed, 08 Mar 2006 04:00:14 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGuWi-0003BA-KG for 6lowpan@lists.ietf.org; Wed, 08 Mar 2006 04:00:12 -0500 Received: from brmea-mail-4.sun.com ([192.18.98.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FGuWg-00087k-UR for 6lowpan@lists.ietf.org; Wed, 08 Mar 2006 04:00:12 -0500 Received: from jurassic.eng.sun.com ([129.146.56.36]) by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id k28902uf003809; Wed, 8 Mar 2006 02:00:02 -0700 (MST) Received: from eng.sun.com (vpn-129-150-20-31.SFBay.Sun.COM [129.150.20.31]) by jurassic.eng.sun.com (8.13.5+Sun/8.13.5) with ESMTP id k289004D748858; Wed, 8 Mar 2006 01:00:01 -0800 (PST) Message-ID: <440E9D0D.3040401@eng.sun.com> Date: Wed, 08 Mar 2006 00:59:57 -0800 From: Samita Chakrabarti User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Schumacher Christian Peter Pii Subject: Re: [6lowpan] new 6lowpan charter References: <49A38D2FE2C53946A57916AD6A1F00D77DB4C7@DKDN01MX34.danfoss.net> In-Reply-To: <49A38D2FE2C53946A57916AD6A1F00D77DB4C7@DKDN01MX34.danfoss.net> Content-Type: multipart/mixed; boundary="------------010805030907030102080304" X-Spam-Score: 0.0 (/) X-Scan-Signature: 8aa7cbc518894eb04182283f0682f662 Cc: 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org This is a multi-part message in MIME format. --------------010805030907030102080304 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi Folks, I have attached my unofficial meeting minutes, while we wait on the official one. I know Carsten had good notes on the charter items. I had the charter listed as line items and intended volunteers. Regards, -Samita Schumacher Christian Peter Pii wrote: > Hi Kim > Unfortunately there doesn't seem to be any official minutes from the > interim meeting in January, and I assumed we only wanted to focus on a > few of these points. However, if you could provide some key-words for > these other items you mentioned, I would be happy to incorporate them > into the text. > Regards > Christian > > ------------------------------------------------------------------------ > *From:* Ki-Hyung Kim [mailto:kkim86@gmail.com] > *Sent:* 7. marts 2006 13:57 > *To:* Schumacher Christian Peter Pii > *Cc:* 6lowpan@lists.ietf.org > *Subject:* RE: [6lowpan] new 6lowpan charter > > Hi, Schumacher, > > As I remember, there were some additional rechartering items which we > had reached on consensus in the last interim meeting, such as mesh > routing protocols, service discovery, scalability (routing and > addressing) and management. > > Is there anything I dont know during the time or any reason why we > cant move forward on these issues? > > -- > > Ki-Hyung Kim > > Associate Professor > > Division of Information and Computer Engineering, > > Ajou University, Suwon, Korea 442-749 > > Tel: +82-31-219-2433, Cel: +82-17-760-2551, Fax: +82-31-219-2433 > > http://ilab.ajou.ac.kr/kkim86/index.htm > > ------------------------------------------------------------------------ > > *From:* Schumacher Christian Peter Pii [mailto:schumacher@danfoss.com] > *Sent:* Tuesday, March 07, 2006 8:09 PM > *To:* 6lowpan@lists.ietf.org > *Subject:* [6lowpan] new 6lowpan charter > > Hi. > > During the 6lowpan interim meeting in January, the working group > discussed possible topics for a future rechartering of 6lowpan. Based > on available information from that meeting I've compiled the following > text, which is an edited version of the scope present in the current > 6lowpan charter. Feedback is appreciated. > > --- start of scope --- > > Scope of 6lowpan: > > Produce "Optimization of the Neighbor Discovery Protocol for 6lowpans" > to define how to apply the existing Neighbor Discovery protocol in a > 6lowpan. > > Produce "IPv6 over Low Power WPAN Security Analysis" to define the > assumptions for a security model for 6lowpan. This includes analysis > of threats, identify types of devices and define the levels of trust > between these devices. > > Produce "6lowpan Co-existence with other Networks" to define how to > co-exist with other networks. This includes analysis of how to survive > interference caused by IEEE 802.11 based networks, and investigate how to > recognize and co-exist with other networks based on IEEE 802.15.4. > > As such, the working group may also work on an informational document > to show how to apply an existing MANET protocol to LoWPANs (e.g., > AODV, OLSR, DYMO, etc). > > The working group will reuse existing specifications whenever > reasonable and possible. > > The working group will also serve as a venue for ongoing discussions > on other topics related to the more complete list outlined above. > Additional related milestones may be added in the future via a > rechartering operation. > > Note: As may be obvious from its official name above, this particular > working group will not work on IPv4 over IEEE 802.15.4 specifications. > Given the limitations of the target devices, dual-stack deployments > are not practical. Because of its higher potential for header > compression, its support for the huge number of devices expected and > of cleanly built-in features such as address autoconfiguration, IPv6 > is the exclusive focus of the working group. > > --- end of scope --- > > Looking forward to receive your feedback. > > Regards > Christian > > PS: The original charter can be found at > http://www.ietf.org/html.charters/6lowpan-charter.html > >------------------------------------------------------------------------ > >_______________________________________________ >6lowpan mailing list >6lowpan@ietf.org >https://www1.ietf.org/mailman/listinfo/6lowpan > > --------------010805030907030102080304 Content-Type: text/plain; name="min.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="min.txt" IETF meeting 1/27/06 6lowpan ----- Summary: 6lowpan IETF interim meeting took place on 27th January at Menlopark, CA. Main objective was to close remaining issues for the problem statement draft and format draft. Several presentations were made at the meeting; the details are discussed below. At the end the working group discussed future possible work for re-chartering. The following are grouped according to the presentations. Some comments are also captured in the minutes, but not all of them. 6lowpan problem statement and goals - Nandu Kushalnagar Security Consideration - Need to fix the current text for security. Comment on the list by Samita - concern about the IPSec tunnel mode within the 802.15.4 network for the limitation of 802.15.4 dataframe size. Gabriel - Should fix the text by saying that IPSec gateway can sit and tunnel in the internet side, but if we need to provide IPSEC gatway in the 802.15.4 network, use different model like SSL. Other comments: Could 802.15.4 link-layer security be used for in-PAN communication. Mark Townsley- Outline the two different models of security for gateway. When to use tunnel mode and when to avoid with respect to the type of network (6lowpan or non-6lowpan network). Vipul - Can we mention protocols in the goals doc? dtls ? Mark - Not in this document. IPSec is mentioned becuase of IPv6 IPSec requirement for IPv6. Consensus - no mention of SSL or specific mention of other security protocols except IPSec because of its special requirement for IPv6. This draft should go for Last call - use 4wks or so for review. Chairs are going to estimate the last call date. 6lowPan interoperability with external networks - Prof. Kim This proposal provides a Gateway architecture and addressing for connecting a 6lowpan network to the outside world(Internet). Gateway architecture => A Router which reduces NS traffic as mentioned in ND-lowpan draft => RA for default router setting in every devices => def gw routes packet to the externaletwork => Does it need an extra bit in adapatation layer for identifying traffic for external network? Erik, Geoff : Don't see a need for an extra bit. L2 and L3 routing should take care of that. Geoff/Alex : May be there needs to be more than one default gateway Erik : Then it would break redirect mechanisms - need to ignore redirects Prof Kim proposed a way of mapping IPv6 address to 16bit MAC addrr (unique per lowpan) then it sets a bit, default gw at the junction translate 16bit MACaddr to IPv6 addr and transfer. ( mapping table at the gw). Carsten - ND optimization, adapatation layer function; where should we add more function to make IPv6 work efficiently on 802.15.4? Erik/Gabe: Functional draft first and then optimization Alex Sy - 64bit address, IPv6 addresses, short addresses, ND does not provide means for choosing addresses, what should be done ? Erik - We could approach in pieces ( conventional and optimized) for understanding the problems and make progress. Broadcast might be useful for some bootstrapping. The architecture should consider or distinguish two models - basic one with broadcast and multicast and the optimized model with reduced broadcast/multicast. GW architecture: - Interop issues - RA issues Comments for format document: Michel Veillete Problems: Adaptation layer : insufficient guarantee of delivery and error handling. Transmission error on a single segment makes the protocol fail - out of order pkt processing required Header compression - reduces overhead but increases complexity Stream support - TCP model? Where does IPv6 feature support stop? ICMPv6 support? IPv6node ---Tiny IPv6 Proxy --- tiny IPv6 node What can make IPv6 tiny? Comments - Tiny IPv6 world is a very limited view of the world, we want to approach this as an open solution which can be applied in arrays of devices for different purposes/usages. 6lowpan Header compression - requires states in the PAN - no additional states Today we talked about GW doing the header compression In this solution, we need to build states in mesh. Sequenced delivery - NAK? Use TCP endpoint negotiation (Erik), set MSS for smaller value for 802.15.4. Gabe: Applications may be built differently Rahul/Geoff: TCP has its own problem in lossy network Erik: There is a solution - but complex; SACK. Alex: Fragmentation puts a burden in CSMA network - fragemntations are not quite efficient in 802.15.4 network Samita: Should we consider stating what kind of applications we are targeting in the goals doc? Several folks commented(Geoff, Erik, Nandu, Gabe?) Geoff: Perhaps we should have a separate BCP doc after these two docs are done. Others: TCP can be speciifed, audio/video possible? Conclusion: out of order delivery -- NAK, ACK packets mechanism needed. 6lowpan HC is simple - we know that it is different than ROHC. The format document needs clarification on that;perhaps we could name it differently. Mention TCP in the format document(?). - separate draft(informational) for IPv6 on sensors. This draft may address buffering requirement, ICMPv6 error messages which carries big messages or errors for other unsupported upper layer protocols that these nodes don't understand. - Current charter does not support proxy approches. It might be useful to include proxy in the charter later. After Michel's presentation we had lunch break. During lunch break, Roger Meike from Sun Microsystems Laboratories welcomed the working group members and gave a short talk on SunLabs Research prototype on sensor platforms that run JAVA on the metal. He also showed a demo on 802.15.4 controlled robo-wheeler. Michel Veillete and Alex Sy showed their company's products on radio and sensor devices. After lunch the meeting resumed with discussions around the neighbor discovery draft for 6lowpan. IPv6 Neighbor Discovery related discussions by Erik Nordmark It discussed different topology. Only star topology is described in IEEE 802.15.4. 802.15.4 does not define Mesh topology, but peer-to-peer topology. The presentation discussed possible mesh topology that wg can agree upon. How about full mesh and hybrid topologies? Who should assign IPv6 address in different topological scenarios? Simple optimizations (star tolpology, one co-ordinator) Alex Sy pointed out that Pan co-ordinators are special co-ordinators - Pan co-ordinators are at the high-level address assigner(assigning PANID). Co-ordinators assign addresses only - PAN ID bit tells who is the true PAN co-ordinator. The draft suggested optimizations for avoiding unnecessary packets in the network Avoid Multicast NS(in the draft) Should it reduce Neighbor unreachability detection? Carsten - need to have something like ICMP eror or RouteError saying that dest addr(default router?) does not exist Gabe - Can NUD be used to map error back since link layer does not provide error back other than ACK- is there a need to have a router error mechanism to transmit to the rfds and co-ordinators that do not do routing If we assume that L2 address of a node does not change for an IPv6 address then we can avoid avoid NUD from host-to-host as well as router-to-host. Other open issues: Should the ND draft support both long and short addresses ? -Yes already in farmat draft. - Can we discover mechanism to discover L2 mechansim to discover and update the mapping bet L2 short and long addr? - Did not catch the timing issue that Gabe mentioned about NUD (anyone?) ND to deal with both short and 64bit addr for linklayer? The 16bit short address is not unique and it might change frequently while the 64bit address is relatively stable. Suggestion to Prof. Kim on GW interop by the chairs -- Take out ND part and work with ND draft authors Write separate draft for header compression ZigBee format compatibility - Geoff : ZigBee 1 PAN per channel Beacon pattern for lowpan =6 Gabe suggests beacon for lowpan might be a separate draft [Geoff - to fill in more data here.] Format draft - Gabriel Montenegro Draft changes as presneted in Vancuver - PAN specific broadcast 16bit zeros + PAN ID -> address forming unicast - both type of addr Relax the MUST on both src and dst link-layer (current doc is fine) version - leave it out reassembly - 15sec time out offset for reassembly now is multiple of 8 What is reassembly keyed on? current : source, tag Discussion: dest, size? Mesh delivery header and constant overhead 802.15.4 allows mix of 16bit /64bit addr in mesh, Should format allow mix of short and long src/dst addr? Question: What it meant by supporting broadcast to the mesh layer, ie. adding 0xffff in the mesh layer header dest field (controlled bcast)? Is it same as PAN specific broadcast? We need to support both short/long src/dst MACaddr in order to support broadcast from a unicast 64bit addr Discussion : We need to specify in the doc about *radio* layer, *mesh* layer broadcasts. Mesh should not preclude possiblity of supporting multicast in Mesh layer (EUI supports group addr capability) mesh delivery layer - should we add support for both 16/64bit addr? for broadcst ( 2 type bits, 6 hops left=64 hops) - Answer: Yes mesh multicast support - Yes, it depends on whether the routing supports it Address management: Pan co-ordinator is the ultimate authority More info on PANID and on its role Charter Discussion:(Carsten has good notes) - ND Optimization is useful item for future to work on - HC compression discussion in a separate document? (to be in wg?) - End-to-end reliable data delivery (NAK, small MSS, small windows, - Mesh layer routing - Service Discovery (application) Kim, Samita - Naming service for Mesh Layer? - assignment of addresses of different sizes - name lookup issues - Easy application configuration/provisioning - Link-layer Address assignment - Scalability -Routing - Addressing - - Security - Key management - Co-existence with other network (surviving with 802.11: channel interference problem solution. channel hopping and selecting a good channel dynamically when there is an intereference) Security Model No Brainers -- ND and optimizations thereof -- Recommendations for TCP usage in 6lowpan -- Recommendation for App? -- Mesh Routing? 802.15.5 - routing for UWB? Not-so-no brainers -- Beacons (vs 802.21 and DNA) Security Key management for 15.4 security? Recommended practices in this space Who: Vipul, Daniel, Carsten Mobility issues? - Samita to submit new version of mobility draft. - Another lowpan mobility draft is also available in the draft directory WSN security - Gabriel Montenegro Gabriel described his thoughts of Wireless sensor security mechanism in mesh network - the idea was inspired by "resurrecting duckling" paper. Sun Microsystems has IPR on this method. Prof. Kim's presentation on Protocol scalability, Adhoc routing protocols and Service discovery based on his internet drafts and research findings. His adhoc routing protocol results are quite interesting. The details are on the slides. The meeting was adjourned at 7pm and many attendees including the chairs went to have dinner together. --------------010805030907030102080304 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --------------010805030907030102080304-- From 6lowpan-bounces@ietf.org Wed Mar 08 10:33:54 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FH0fh-0001bx-0R; Wed, 08 Mar 2006 10:33:53 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FH0fg-0001ab-3h for 6lowpan@lists.ietf.org; Wed, 08 Mar 2006 10:33:52 -0500 Received: from grab.coslabs.com ([199.233.92.34]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FH0fe-0005fm-9L for 6lowpan@lists.ietf.org; Wed, 08 Mar 2006 10:33:52 -0500 Received: from dellx1.coslabs.com (dellx1.coslabs.com [199.233.92.20]) by grab.coslabs.com (8.12.10/8.12.10) with ESMTP id k28FWjJr021970; Wed, 8 Mar 2006 08:32:45 -0700 (MST) From: Geoff Mulligan To: Samita Chakrabarti In-Reply-To: <440E9D0D.3040401@eng.sun.com> References: <49A38D2FE2C53946A57916AD6A1F00D77DB4C7@DKDN01MX34.danfoss.net> <440E9D0D.3040401@eng.sun.com> Content-Type: text/plain Date: Wed, 08 Mar 2006 08:33:04 -0700 Message-Id: <1141831984.25972.23.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 28dc73ba51024f450a593b05aa945739 Cc: 6lowpan@lists.ietf.org Subject: [6lowpan] 6lowpan interim meeting minutes REQUEST 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org If anyone else has any notes taken during the meeting, Carsten, could you please forward them to me soon and I will create some office meeting minutes. If I don't get anything in the next couple of days, I'll use Samita's and some of my own. Thanks, geoff On Wed, 2006-03-08 at 00:59 -0800, Samita Chakrabarti wrote: > Hi Folks, > > I have attached my unofficial meeting minutes, while we wait on the > official one. > I know Carsten had good notes on the charter items. I had the charter > listed as line > items and intended volunteers. > > Regards, > -Samita > > > Schumacher Christian Peter Pii wrote: > > > Hi Kim > > Unfortunately there doesn't seem to be any official minutes from the > > interim meeting in January, and I assumed we only wanted to focus on a > > few of these points. However, if you could provide some key-words for > > these other items you mentioned, I would be happy to incorporate them > > into the text. > > Regards > > Christian > > > > ------------------------------------------------------------------------ > > *From:* Ki-Hyung Kim [mailto:kkim86@gmail.com] > > *Sent:* 7. marts 2006 13:57 > > *To:* Schumacher Christian Peter Pii > > *Cc:* 6lowpan@lists.ietf.org > > *Subject:* RE: [6lowpan] new 6lowpan charter > > > > Hi, Schumacher, > > > > As I remember, there were some additional rechartering items which we > > had reached on consensus in the last interim meeting, such as mesh > > routing protocols, service discovery, scalability (routing and > > addressing) and management. > > > > Is there anything I dont know during the time or any reason why we > > cant move forward on these issues? > > > > -- > > > > Ki-Hyung Kim > > > > Associate Professor > > > > Division of Information and Computer Engineering, > > > > Ajou University, Suwon, Korea 442-749 > > > > Tel: +82-31-219-2433, Cel: +82-17-760-2551, Fax: +82-31-219-2433 > > > > http://ilab.ajou.ac.kr/kkim86/index.htm > > > > ------------------------------------------------------------------------ > > > > *From:* Schumacher Christian Peter Pii [mailto:schumacher@danfoss.com] > > *Sent:* Tuesday, March 07, 2006 8:09 PM > > *To:* 6lowpan@lists.ietf.org > > *Subject:* [6lowpan] new 6lowpan charter > > > > Hi. > > > > During the 6lowpan interim meeting in January, the working group > > discussed possible topics for a future rechartering of 6lowpan. Based > > on available information from that meeting I've compiled the following > > text, which is an edited version of the scope present in the current > > 6lowpan charter. Feedback is appreciated. > > > > --- start of scope --- > > > > Scope of 6lowpan: > > > > Produce "Optimization of the Neighbor Discovery Protocol for 6lowpans" > > to define how to apply the existing Neighbor Discovery protocol in a > > 6lowpan. > > > > Produce "IPv6 over Low Power WPAN Security Analysis" to define the > > assumptions for a security model for 6lowpan. This includes analysis > > of threats, identify types of devices and define the levels of trust > > between these devices. > > > > Produce "6lowpan Co-existence with other Networks" to define how to > > co-exist with other networks. This includes analysis of how to survive > > interference caused by IEEE 802.11 based networks, and investigate how to > > recognize and co-exist with other networks based on IEEE 802.15.4. > > > > As such, the working group may also work on an informational document > > to show how to apply an existing MANET protocol to LoWPANs (e.g., > > AODV, OLSR, DYMO, etc). > > > > The working group will reuse existing specifications whenever > > reasonable and possible. > > > > The working group will also serve as a venue for ongoing discussions > > on other topics related to the more complete list outlined above. > > Additional related milestones may be added in the future via a > > rechartering operation. > > > > Note: As may be obvious from its official name above, this particular > > working group will not work on IPv4 over IEEE 802.15.4 specifications. > > Given the limitations of the target devices, dual-stack deployments > > are not practical. Because of its higher potential for header > > compression, its support for the huge number of devices expected and > > of cleanly built-in features such as address autoconfiguration, IPv6 > > is the exclusive focus of the working group. > > > > --- end of scope --- > > > > Looking forward to receive your feedback. > > > > Regards > > Christian > > > > PS: The original charter can be found at > > http://www.ietf.org/html.charters/6lowpan-charter.html > > > >------------------------------------------------------------------------ > > > >_______________________________________________ > >6lowpan mailing list > >6lowpan@ietf.org > >https://www1.ietf.org/mailman/listinfo/6lowpan > > > > > > plain text document attachment (min.txt) > IETF meeting 1/27/06 6lowpan > ----- > > Summary: > 6lowpan IETF interim meeting took place on 27th January at Menlopark, CA. > Main objective was to close remaining issues for the problem statement draft > and format draft. Several presentations were made at the meeting; the details > are discussed below. At the end the working group discussed future possible > work for re-chartering. > > The following are grouped according to the presentations. Some comments are > also captured in the minutes, but not all of them. > > 6lowpan problem statement and goals - Nandu Kushalnagar > > Security Consideration - > Need to fix the current text for security. > Comment on the list by Samita - concern about the IPSec tunnel mode within the > 802.15.4 network for the limitation of 802.15.4 dataframe size. > Gabriel - Should fix the text by saying that IPSec gateway > can sit and tunnel in the internet side, but if we need to provide IPSEC > gatway in the 802.15.4 network, use different model like SSL. > > Other comments: Could 802.15.4 link-layer security be used for in-PAN > communication. > > Mark Townsley- Outline the two different models of security for gateway. > When to use tunnel mode and when to avoid with respect to > the type of network (6lowpan or non-6lowpan network). > > Vipul - Can we mention protocols in the goals doc? dtls ? > Mark - Not in this document. IPSec is mentioned becuase of IPv6 IPSec > requirement for IPv6. > > Consensus - no mention of SSL or specific mention of other security protocols > except IPSec because of its special requirement for IPv6. > > This draft should go for Last call - use 4wks or so for review. > Chairs are going to estimate the last call date. > > > 6lowPan interoperability with external networks - Prof. Kim > This proposal provides a Gateway architecture and addressing for connecting a > 6lowpan network to the outside world(Internet). > > Gateway architecture > => A Router which reduces NS traffic as mentioned in ND-lowpan draft > => RA for default router setting in every devices > => def gw routes packet to the externaletwork > => Does it need an extra bit in adapatation layer for identifying traffic > for external network? > Erik, Geoff : Don't see a need for an extra bit. L2 and L3 routing should > take care of that. > Geoff/Alex : May be there needs to be more than one default gateway > Erik : Then it would break redirect mechanisms - need to ignore redirects > > Prof Kim proposed a way of mapping IPv6 address to 16bit MAC addrr (unique > per lowpan) then it sets a bit, default gw at the junction translate 16bit MACaddr > to IPv6 addr and transfer. ( mapping table at the gw). > > Carsten - ND optimization, adapatation layer function; where should we > add more function to make IPv6 work efficiently on 802.15.4? > Erik/Gabe: Functional draft first and then optimization > Alex Sy - 64bit address, IPv6 addresses, short addresses, ND does not > provide means for choosing addresses, what should be done ? > Erik - We could approach in pieces ( conventional and optimized) for > understanding the problems and make progress. Broadcast might be > useful for some bootstrapping. The architecture should consider > or distinguish two models - basic one with broadcast and multicast > and the optimized model with reduced broadcast/multicast. > > GW architecture: > - Interop issues > - RA issues > > Comments for format document: Michel Veillete > Problems: > Adaptation layer : insufficient guarantee of delivery and error handling. > Transmission error on a single segment makes the protocol fail > - out of order pkt processing required > Header compression > - reduces overhead but increases complexity > Stream support - TCP model? > Where does IPv6 feature support stop? ICMPv6 support? > IPv6node ---Tiny IPv6 Proxy --- tiny IPv6 node > What can make IPv6 tiny? > Comments - Tiny IPv6 world is a very limited view of the world, we > want to approach this as an open solution which can be applied in arrays > of devices for different purposes/usages. > 6lowpan Header compression - requires states in the PAN - no additional states > Today we talked about GW doing the header compression > In this solution, we need to build states in mesh. > > Sequenced delivery - NAK? > Use TCP endpoint negotiation (Erik), set MSS for smaller value > for 802.15.4. > Gabe: Applications may be built differently > Rahul/Geoff: TCP has its own problem in lossy network > Erik: There is a solution - but complex; SACK. > Alex: Fragmentation puts a burden in CSMA network - fragemntations > are not quite efficient in 802.15.4 network > Samita: Should we consider stating what kind of applications we are > targeting in the goals doc? > Several folks commented(Geoff, Erik, Nandu, Gabe?) > Geoff: Perhaps we should have a separate BCP doc after these two docs > are done. > Others: TCP can be speciifed, audio/video possible? > > Conclusion: out of order delivery -- NAK, ACK packets mechanism needed. > 6lowpan HC is simple - we know that it is different than ROHC. > The format document needs clarification on that;perhaps we could > name it differently. Mention TCP in the format document(?). > > - separate draft(informational) for IPv6 on sensors. This draft > may address buffering requirement, > ICMPv6 error messages which carries big messages or errors for other > unsupported upper layer protocols that these nodes don't > understand. > > - Current charter does not support proxy approches. It might be > useful to include proxy in the charter later. > > After Michel's presentation we had lunch break. During lunch break, Roger Meike from > Sun Microsystems Laboratories welcomed the working group members and gave a short > talk on SunLabs Research prototype on sensor platforms that run JAVA on the metal. > He also showed a demo on 802.15.4 controlled robo-wheeler. Michel Veillete and Alex Sy > showed their company's products on radio and sensor devices. After lunch the meeting > resumed with discussions around the neighbor discovery draft for 6lowpan. > > > > IPv6 Neighbor Discovery related discussions by Erik Nordmark > > It discussed different topology. Only star topology is described in IEEE 802.15.4. > 802.15.4 does not define Mesh topology, but peer-to-peer topology. > The presentation discussed possible mesh topology that wg can agree upon. > How about full mesh and hybrid topologies? Who should assign IPv6 address in > different topological scenarios? > Simple optimizations (star tolpology, one co-ordinator) > Alex Sy pointed out that Pan co-ordinators are special co-ordinators - Pan co-ordinators > are at the high-level address assigner(assigning PANID). > Co-ordinators assign addresses only - PAN ID bit tells who > is the true PAN co-ordinator. > > > > The draft suggested optimizations for avoiding unnecessary packets in the network > Avoid Multicast NS(in the draft) > Should it reduce Neighbor unreachability detection? > > Carsten - need to have something like ICMP eror or RouteError > saying that dest addr(default router?) does not exist > Gabe - Can NUD be used to map error back since link layer does not > provide error back other than ACK- is there a need to have > a router error mechanism to transmit to the rfds and co-ordinators > that do not do routing > > If we assume that L2 address of a node does not change for an IPv6 address > then we can avoid avoid NUD from host-to-host as well as router-to-host. > > Other open issues: > Should the ND draft support both long and short addresses ? -Yes already in farmat draft. > - Can we discover mechanism to discover L2 mechansim to discover > and update the mapping bet L2 short and long addr? > - Did not catch the timing issue that Gabe mentioned about NUD (anyone?) > > ND to deal with both short and 64bit addr for linklayer? > The 16bit short address is not unique and it might change > frequently while the 64bit address is relatively stable. > > > Suggestion to Prof. Kim on GW interop by the chairs -- > Take out ND part and work with ND draft authors > Write separate draft for header compression > > > > ZigBee format compatibility - > Geoff : > ZigBee 1 PAN per channel > Beacon pattern for lowpan =6 > > Gabe suggests beacon for lowpan might be a separate draft > > [Geoff - to fill in more data here.] > > Format draft - Gabriel Montenegro > Draft changes as presneted in Vancuver > - PAN specific broadcast > > 16bit zeros + PAN ID -> address forming > unicast - both type of addr > Relax the MUST on both src and dst link-layer (current doc is fine) > version - leave it out > reassembly - 15sec time out > offset for reassembly now is multiple of 8 > What is reassembly keyed on? > current : source, tag > Discussion: dest, size? > Mesh delivery header and constant overhead > 802.15.4 allows mix of 16bit /64bit addr in mesh, > Should format allow mix of short and long src/dst addr? > Question: > What it meant by supporting broadcast to the mesh layer, ie. > adding 0xffff in the mesh layer header dest field (controlled bcast)? > Is it same as PAN specific broadcast? > We need to support both short/long src/dst MACaddr in order to > support broadcast from a unicast 64bit addr > > Discussion : We need to specify in the doc about *radio* layer, *mesh* layer > broadcasts. Mesh should not preclude possiblity of supporting > multicast in Mesh layer (EUI supports group addr capability) > > > mesh delivery layer - should we add support for both 16/64bit addr? > for broadcst ( 2 type bits, 6 hops left=64 hops) > - Answer: Yes > mesh multicast support - > Yes, it depends on whether the routing supports it > > Address management: > Pan co-ordinator is the ultimate authority > More info on PANID and on its role > > > Charter Discussion:(Carsten has good notes) > > - ND Optimization is useful item for future to work on > - HC compression discussion in a separate document? (to be in wg?) > - End-to-end reliable data delivery (NAK, small MSS, small windows, > > - Mesh layer routing > - Service Discovery (application) > Kim, Samita > - Naming service for Mesh Layer? > - assignment of addresses of different sizes > - name lookup issues > > - Easy application configuration/provisioning > - Link-layer Address assignment > - Scalability > -Routing > - Addressing > - > - Security > - Key management > > - Co-existence with other network > (surviving with 802.11: channel interference problem solution. > channel hopping and selecting a good channel dynamically when > there is an intereference) > > Security Model > > No Brainers > -- ND and optimizations thereof > -- Recommendations for TCP usage in 6lowpan > -- Recommendation for App? > -- Mesh Routing? > > 802.15.5 - routing for UWB? > > Not-so-no brainers > -- Beacons (vs 802.21 and DNA) > > Security > Key management for 15.4 security? > Recommended practices in this space > Who: Vipul, Daniel, Carsten > > > Mobility issues? > - Samita to submit new version of mobility draft. > - Another lowpan mobility draft is also available in the draft directory > > > > WSN security - Gabriel Montenegro > > Gabriel described his thoughts of Wireless sensor security mechanism > in mesh network - the idea was inspired by "resurrecting duckling" paper. > Sun Microsystems has IPR on this method. > > > Prof. Kim's presentation on Protocol scalability, Adhoc routing protocols and > Service discovery based on his internet drafts and research findings. His > adhoc routing protocol results are quite interesting. The details are on the slides. > > The meeting was adjourned at 7pm and many attendees including the chairs went to have > dinner together. > > > > > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Wed Mar 08 12:21:19 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FH2Lb-0005pb-Tz; Wed, 08 Mar 2006 12:21:16 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FH2La-0005pW-9r for 6lowpan@lists.ietf.org; Wed, 08 Mar 2006 12:21:14 -0500 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FH0z5-0006FG-HU for 6lowpan@lists.ietf.org; Wed, 08 Mar 2006 10:53:55 -0500 Received: from grab.coslabs.com ([199.233.92.34]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FH0lQ-0003Af-Td for 6lowpan@lists.ietf.org; Wed, 08 Mar 2006 10:39:51 -0500 Received: from dellx1.coslabs.com (dellx1.coslabs.com [199.233.92.20]) by grab.coslabs.com (8.12.10/8.12.10) with ESMTP id k28FdeJr022046; Wed, 8 Mar 2006 08:39:41 -0700 (MST) Subject: RE: [6lowpan] new 6lowpan charter From: Geoff Mulligan To: Ki-Hyung Kim In-Reply-To: References: Content-Type: text/plain; charset=UTF-8 Date: Wed, 08 Mar 2006 08:40:00 -0700 Message-Id: <1141832400.25972.29.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by grab.coslabs.com id k28FdeJr022046 X-Spam-Score: -2.6 (--) X-Scan-Signature: df9edf1223802dd4cf213867a3af6121 Cc: 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org The lack of minutes is probably my fault. I dropped the ball. Yes Carsten created a very good list of rechartering items with names by the items. I was hoping that it was on the wiki, but it doesn't seem to be there yet. If Carsten will forward it I will incorporate it in to the meeting minutes and we can get on with that discussion. Are there any comments on "problem statement" document? geoff On Wed, 2006-03-08 at 10:58 +0900, Ki-Hyung Kim wrote: > Hi Christian, >=20 > I am curious why the official minutes are not available yet, but there > were such items we had mentioned. >=20 > Anyway, the following items were discussed and summarized by Carsten(? > If my memory is correct) as rechartering items on the last interim > meeting. >=20 > =20 >=20 > 1) Mesh routing protocol >=20 > 2) Service discovery >=20 > 3) Scalability of 6lowpan (routing and addressing) >=20 > 4) Mobility issues >=20 > 5) Naming service for mesh layer >=20 > 6) Gateway architecture (This item was discussed as =E2=80=9CHC compres= sion=E2=80=9D > on the last meeting) >=20 > =20 >=20 > If you need polished statements for these items, let me know. >=20 > =20 >=20 > Regards, >=20 > =20 >=20 > -- >=20 > Ki-Hyung Kim >=20 > Associate Professor >=20 > Division of Information and Computer Engineering, >=20 > Ajou University, Suwon, Korea 442-749 >=20 > Tel: +82-31-219-2433, Cel: +82-17-760-2551, Fax: +82-31-219-2433 >=20 > http://ilab.ajou.ac.kr/kkim86/index.htm =20 >=20 >=20 > =20 > ______________________________________________________________________ > From:Schumacher Christian Peter Pii [mailto:schumacher@danfoss.com]=20 > Sent: Tuesday, March 07, 2006 10:06 PM > To: Ki-Hyung Kim > Cc: 6lowpan@lists.ietf.org > Subject: RE: [6lowpan] new 6lowpan charter >=20 >=20 > =20 >=20 > Hi Kim >=20 > =20 >=20 > Unfortunately there doesn't seem to be any official minutes from the > interim meeting in January, and I assumed we only wanted to focus on a > few of these points. However, if you could provide some key-words for > these other items you mentioned, I would be happy to incorporate them > into the text. >=20 > =20 >=20 > Regards >=20 > Christian >=20 > =20 >=20 > =20 > ______________________________________________________________________ > From:Ki-Hyung Kim [mailto:kkim86@gmail.com]=20 > Sent: 7. marts 2006 13:57 > To: Schumacher Christian Peter Pii > Cc: 6lowpan@lists.ietf.org > Subject: RE: [6lowpan] new 6lowpan charter >=20 > Hi, Schumacher, >=20 > =20 >=20 > As I remember, there were some additional rechartering items which we > had reached on consensus in the last interim meeting, such as mesh > routing protocols, service discovery, scalability (routing and > addressing) and management. >=20 > =20 >=20 > Is there anything I don=E2=80=99t know during the time or any reason wh= y we > can=E2=80=99t move forward on these issues? >=20 > =20 >=20 > =20 >=20 > =20 >=20 > -- >=20 > Ki-Hyung Kim >=20 > Associate Professor >=20 > Division of Information and Computer Engineering, >=20 > Ajou University, Suwon, Korea 442-749 >=20 > Tel: +82-31-219-2433, Cel: +82-17-760-2551, Fax: +82-31-219-2433 >=20 > http://ilab.ajou.ac.kr/kkim86/index.htm =20 >=20 >=20 > =20 > ______________________________________________________________________ > From:Schumacher Christian Peter Pii [mailto:schumacher@danfoss.com]=20 > Sent: Tuesday, March 07, 2006 8:09 PM > To: 6lowpan@lists.ietf.org > Subject: [6lowpan] new 6lowpan charter >=20 >=20 > =20 >=20 > Hi.=20 >=20 > During the 6lowpan interim meeting in January, the working group > discussed possible topics for a future rechartering of 6lowpan. Based > on available information from that meeting I've compiled the following > text, which is an edited version of the scope present in the current > 6lowpan charter. Feedback is appreciated.=20 >=20 > --- start of scope ---=20 >=20 > Scope of 6lowpan:=20 >=20 > Produce "Optimization of the Neighbor Discovery Protocol for > 6lowpans"=20 > to define how to apply the existing Neighbor Discovery protocol in a=20 > 6lowpan.=20 >=20 > Produce "IPv6 over Low Power WPAN Security Analysis" to define the=20 > assumptions for a security model for 6lowpan. This includes analysis=20 > of threats, identify types of devices and define the levels of trust=20 > between these devices.=20 >=20 > Produce "6lowpan Co-existence with other Networks" to define how to=20 > co-exist with other networks. This includes analysis of how to > survive=20 > interference caused by IEEE 802.11 based networks, and investigate how > to=20 > recognize and co-exist with other networks based on IEEE 802.15.4.=20 >=20 > As such, the working group may also work on an informational document=20 > to show how to apply an existing MANET protocol to LoWPANs (e.g.,=20 > AODV, OLSR, DYMO, etc).=20 >=20 > The working group will reuse existing specifications whenever=20 > reasonable and possible.=20 >=20 > The working group will also serve as a venue for ongoing discussions=20 > on other topics related to the more complete list outlined above.=20 > Additional related milestones may be added in the future via a=20 > rechartering operation.=20 >=20 > Note: As may be obvious from its official name above, this particular=20 > working group will not work on IPv4 over IEEE 802.15.4 > specifications.=20 > Given the limitations of the target devices, dual-stack deployments=20 > are not practical. Because of its higher potential for header=20 > compression, its support for the huge number of devices expected and=20 > of cleanly built-in features such as address autoconfiguration, IPv6=20 > is the exclusive focus of the working group.=20 >=20 > --- end of scope ---=20 >=20 > Looking forward to receive your feedback.=20 >=20 > Regards=20 > Christian=20 >=20 > PS: The original charter can be found at > http://www.ietf.org/html.charters/6lowpan-charter.html=20 >=20 >=20 _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Wed Mar 08 14:12:42 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FH45R-0008TK-Bz; Wed, 08 Mar 2006 14:12:41 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FH45Q-0008TF-GS for 6lowpan@lists.ietf.org; Wed, 08 Mar 2006 14:12:40 -0500 Received: from mailout3.samsung.com ([203.254.224.33]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FH45P-0004bj-OQ for 6lowpan@lists.ietf.org; Wed, 08 Mar 2006 14:12:40 -0500 Received: from ep_mmp1 (mailout3.samsung.com [203.254.224.33]) by mailout3.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0IVT00AUBPD2XX@mailout3.samsung.com> for 6lowpan@lists.ietf.org; Thu, 09 Mar 2006 04:12:38 +0900 (KST) Received: from daniellaptop ([124.235.139.1]) by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTPA id <0IVT00DNAPCZHU@mmp1.samsung.com> for 6lowpan@lists.ietf.org; Thu, 09 Mar 2006 04:12:38 +0900 (KST) Date: Thu, 09 Mar 2006 04:12:48 +0900 From: Soohong Daniel Park Subject: Re: [6lowpan] new 6lowpan charter To: Schumacher Christian Peter Pii , 6lowpan@lists.ietf.org Message-id: <00e701c642e4$4b93c530$19706f0a@daniellaptop> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Outlook Express 6.00.2900.2180 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <49A38D2FE2C53946A57916AD6A1F00D77DB48D@DKDN01MX34.danfoss.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88 Cc: 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org new 6lowpan charterI believe 6lowpan adhoc routing protocol must be included into our rechartering more specific than now. It is one of urgent task toward 6LoWPAN Current text is just copy-and-paste from the existing charter as follows: "As such, the working group may also work on an informational document to show how to apply an existing MANET protocol to LoWPANs (e.g., AODV, OLSR, DYMO, etc)." So, my suggestion is as follows: Produce "Optimization of the Adhoc Routing Protocol for 6lowpans" to apply an existing MANET Protocol to LoWPANs. Thanks in advance. Daniel (Soohong Daniel Park) Mobile Convergence Laboratory, SAMSUNG Electronics. ----- Original Message ----- From: Schumacher Christian Peter Pii To: 6lowpan@lists.ietf.org Sent: Tuesday, March 07, 2006 8:09 PM Subject: [6lowpan] new 6lowpan charter Hi. During the 6lowpan interim meeting in January, the working group discussed possible topics for a future rechartering of 6lowpan. Based on available information from that meeting I've compiled the following text, which is an edited version of the scope present in the current 6lowpan charter. Feedback is appreciated. --- start of scope --- Scope of 6lowpan: Produce "Optimization of the Neighbor Discovery Protocol for 6lowpans" to define how to apply the existing Neighbor Discovery protocol in a 6lowpan. Produce "IPv6 over Low Power WPAN Security Analysis" to define the assumptions for a security model for 6lowpan. This includes analysis of threats, identify types of devices and define the levels of trust between these devices. Produce "6lowpan Co-existence with other Networks" to define how to co-exist with other networks. This includes analysis of how to survive interference caused by IEEE 802.11 based networks, and investigate how to recognize and co-exist with other networks based on IEEE 802.15.4. As such, the working group may also work on an informational document to show how to apply an existing MANET protocol to LoWPANs (e.g., AODV, OLSR, DYMO, etc). The working group will reuse existing specifications whenever reasonable and possible. The working group will also serve as a venue for ongoing discussions on other topics related to the more complete list outlined above. Additional related milestones may be added in the future via a rechartering operation. Note: As may be obvious from its official name above, this particular working group will not work on IPv4 over IEEE 802.15.4 specifications. Given the limitations of the target devices, dual-stack deployments are not practical. Because of its higher potential for header compression, its support for the huge number of devices expected and of cleanly built-in features such as address autoconfiguration, IPv6 is the exclusive focus of the working group. --- end of scope --- Looking forward to receive your feedback. Regards Christian PS: The original charter can be found at http://www.ietf.org/html.charters/6lowpan-charter.html _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Wed Mar 08 16:41:28 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FH5kR-0001Js-TO; Wed, 08 Mar 2006 15:59:09 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FH5bg-0007EL-Hy; Wed, 08 Mar 2006 15:50:04 -0500 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=cypress.neustar.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FH5bf-0008HI-Us; Wed, 08 Mar 2006 15:50:04 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by cypress.neustar.com (8.12.8/8.12.8) with ESMTP id k28Ko30e006068 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Mar 2006 20:50:03 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1FH5bf-0002s7-5X; Wed, 08 Mar 2006 15:50:03 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Wed, 08 Mar 2006 15:50:03 -0500 X-Spam-Score: -2.5 (--) X-Scan-Signature: 73734d43604d52d23b3eba644a169745 Cc: 6lowpan@lists.ietf.org Subject: [6lowpan] I-D ACTION:draft-ietf-6lowpan-format-02.txt 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IPv6 over Low power WPAN Working Group of the IETF. Title : Transmission of IPv6 Packets over IEEE 802.15.4 Networks Author(s) : G. Montenegro, N. Kushalnagar Filename : draft-ietf-6lowpan-format-02.txt Pages : 26 Date : 2006-3-8 This document describes the frame format for transmission of IPv6 packets and the method of forming IPv6 link-local addresses and statelessly autoconfigured addresses on IEEE 802.15.4 networks. Additional specifications include a simple header compression scheme using shared context and provisions for packet delivery in IEEE 802.15.4 meshes. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-6lowpan-format-02.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-6lowpan-format-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-6lowpan-format-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2006-3-8142740.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-6lowpan-format-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-6lowpan-format-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-3-8142740.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --NextPart-- From 6lowpan-bounces@ietf.org Wed Mar 08 21:13:57 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FHAf2-0000wh-Ji; Wed, 08 Mar 2006 21:13:52 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FHAf0-0000vu-UQ for 6lowpan@lists.ietf.org; Wed, 08 Mar 2006 21:13:50 -0500 Received: from nwkea-mail-4.sun.com ([192.18.42.26]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FHAex-0006V0-Gp for 6lowpan@lists.ietf.org; Wed, 08 Mar 2006 21:13:50 -0500 Received: from jurassic.eng.sun.com ([129.146.17.57]) by nwkea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id k292Dk3W004511 for <6lowpan@lists.ietf.org>; Wed, 8 Mar 2006 18:13:46 -0800 (PST) Received: from eng.sun.com (d-mpk16-75-68.SFBay.Sun.COM [129.146.75.68]) by jurassic.eng.sun.com (8.13.5+Sun/8.13.5) with ESMTP id k292DkQa972321 for <6lowpan@lists.ietf.org>; Wed, 8 Mar 2006 18:13:46 -0800 (PST) Message-ID: <440F8F56.1080502@eng.sun.com> Date: Wed, 08 Mar 2006 18:13:42 -0800 From: Samita Chakrabarti User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: 6lowpan@lists.ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Cc: Subject: [6lowpan] 6LowPan Neighbor Discovery version 01 available 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org Based on the feedback at the January interim meeting, we have updated the 6lowPan Neighbor Discovery Draft - http://www.ietf.org/internet-drafts/draft-chakrabarti-6lowpan-ipv6-nd-01.txt Please provide comments. Erik Nordmark Samita Chakrabarti _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Sat Mar 11 08:13:29 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FI3uK-0002wr-5N; Sat, 11 Mar 2006 08:13:20 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FI3uJ-0002wm-E5 for 6lowpan@lists.ietf.org; Sat, 11 Mar 2006 08:13:19 -0500 Received: from violet.upc.es ([147.83.2.51]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FI3uH-00048d-N1 for 6lowpan@lists.ietf.org; Sat, 11 Mar 2006 08:13:19 -0500 Received: from violet.upc.es (localhost [127.0.0.1]) by violet.upc.es (8.13.0/8.13.0) with ESMTP id k2BDDFMr001707 for <6lowpan@lists.ietf.org>; Sat, 11 Mar 2006 14:13:16 +0100 Received: from localhost (wmail-mat.upc.es [147.83.39.70]) by violet.upc.es (8.13.0/8.13.0) with ESMTP id k2BDD7so001636 for <6lowpan@lists.ietf.org>; Sat, 11 Mar 2006 14:13:07 +0100 Received: from 62.57.138.12 ( [62.57.138.12]) as user carlesgo@mat.upc.es by wmail-mat.upc.es with HTTP; Sat, 11 Mar 2006 13:54:29 +0100 Message-ID: <1142081669.4412c885c0f73@wmail-mat.upc.es> Date: Sat, 11 Mar 2006 13:54:29 +0100 From: =?ISO-8859-1?B?Q2FybGVzIEfzbWV6?= To: 6lowpan@lists.ietf.org References: <49A38D2FE2C53946A57916AD6A1F00D77DB4C7@DKDN01MX34.danfoss.net> <440E9D0D.3040401@eng.sun.com> In-Reply-To: <440E9D0D.3040401@eng.sun.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.1 X-Originating-IP: 62.57.138.12 X-Spam-Score: 0.0 (/) X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81 Cc: Subject: [6lowpan] Comments about LOAD (draft version 02) 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org Dear all, I have a couple of doubts regarding the LOAD specification. Just in case I am missing something, I would like to expose them in the list. My doubts are: 1) WEAK_LQI_VALUE ***************** In Section 3, page 4, the latest LOAD draft states that "The approach taken by LOAD avoids a route which contains weak links whose LQI is below certain threshold value (i.e. WEAK_LQI_VALUE)". On the other hand, the proposed default value for the WEAK_LQI_VALUE parameter is 8. However, according to the datasheet of the CC2400 radio chip (i.e. the one included in Crossbow's MICAz motes), LQI values range between 50 (bad quality) and 110 (good quality). We (and also other researchers) have conducted experiments which confirm this range of values. In consequence, it seems difficult that a link could have an LQI value below 8 (at least with MICAz motes). Is it possible that proposing WEAK_LQI_VALUE equal to 8 comes from experiences with other platforms (i.e. not the MICAz ones)? Do you think a different default value for WEAK_LQI_VALUE could be proposed by default? 2) Sequence numbers ******************* LOAD avoids usage of sequence numbers for the sake of simplicity, forcing that only the destination is allowed to generate RREP messages in order to avoid routing inconsistencies (loops, etc.). However, I would like to expose the following doubt. In Section 6.3, LOAD spec. states that: "When the destination receives a RREQ, it tries to find the entry of the same originator address and RREQ ID pair in the route request table. If the entry is found, the destination compares the route cost of the RREQ with the forward route cost of the entry. If the cost of the RREQ is better than (i.e. less than) that of the entry, the destination updates the reverse route to the originator in the routing table and generates a RREP in reply. If the cost of the RREQ is not less than that of the entry, the destination just discards the RREQ". Let's consider the following network topology, where A transmits data to C. Let's assume all links are equal and have the same quality: B / \ A C \ / D - E According to the 'minimum hop while avoiding weak links' metric, the chosen path will be ABC. Now, if the AB link is broken, A starts a new Route Discovery. There is one available path for transmitting data from A to C (ADEC) but since this path has a higher cost than the former (let's assume information about the old route hasn't yet expired at C), then C discards the RREQ according to Section 6.3. In consequence, it would not be possible to use the available path. Am I missing something? Would it be necessary to use sequence numbers to take into account, not only the routes cost but also their freshness? Many thanks in advance. With best regards, Carles Gómez Wireless Networks Group Technical University of Catalonia (UPC) ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Mon Mar 13 11:48:50 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FIqDo-0001Xw-T8; Mon, 13 Mar 2006 11:48:40 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FIqDn-0001Wd-Bs for 6lowpan@lists.ietf.org; Mon, 13 Mar 2006 11:48:39 -0500 Received: from bellwecs3.bellnexxia.net ([207.236.237.115] helo=bellwecs3.srvr.bell.ca) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FIqDm-0004Ec-0W for 6lowpan@lists.ietf.org; Mon, 13 Mar 2006 11:48:39 -0500 Received: (qmail 18829 invoked from network); 13 Mar 2006 16:48:37 -0000 Received: from peter.sherbin@bell.ca by bellwecs3.srvr.bell.ca with EntrustECS-Server-7.4; 13 Mar 2006 16:48:37 -0000 Received: from bellwfep8.bellnexxia.net (HELO bellwfep8-srv.bellnexxia.net) (207.236.237.101) by bellwecs3.srvr.bell.ca with SMTP; 13 Mar 2006 16:48:37 -0000 Received: from TOROONDC918.bell.corp.bce.ca ([142.182.89.79]) by bellwfep8-srv.bellnexxia.net (InterMail vM.5.01.06.10 201-253-122-130-110-20040306) with ESMTP id <20060313164837.FQCG20742.bellwfep8-srv.bellnexxia.net@TOROONDC918.bell.corp.bce.ca>; Mon, 13 Mar 2006 11:48:37 -0500 Received: from TOROONDC915.bell.corp.bce.ca ([142.182.89.18]) by TOROONDC918.bell.corp.bce.ca with Microsoft SMTPSVC(6.0.3790.1830); Mon, 13 Mar 2006 11:48:36 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: [6lowpan] IEEE 802.15.4-2003 Date: Mon, 13 Mar 2006 11:48:35 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [6lowpan] IEEE 802.15.4-2003 Thread-Index: AcZFDZNAW7u78/L7QmONJyA5npJKuwBrIKgg From: To: <6lowpan@lists.ietf.org> X-OriginalArrivalTime: 13 Mar 2006 16:48:37.0093 (UTC) FILETIME=[F93D1150:01C646BD] X-Spam-Score: 0.2 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Cc: Jim.Bound@hp.com 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org So far 6lowpan WG has posted 2 drafts each referencing IEEE = 802.15.4-2003. Is it correct to assume that this standard is going to = remain a technology of choice for Layers 1 / 2 connectivity in sensor = networks? If yes would it be fair to ask for making 802.15.4 available in the same = fashion IETF publications are available? E.g. make a WG draft quoting = all relevant parts of IEEE 802.15.4? Thank you, Peter _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Mon Mar 13 11:50:49 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FIqFt-0002iS-PI; Mon, 13 Mar 2006 11:50:49 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FIqFs-0002iJ-OJ for 6lowpan@lists.ietf.org; Mon, 13 Mar 2006 11:50:48 -0500 Received: from [216.183.86.37] (helo=mail.ca.certicom.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FIqFq-0004He-Cb for 6lowpan@lists.ietf.org; Mon, 13 Mar 2006 11:50:48 -0500 Received: from spamfilter.certicom.com (localhost.localdomain [127.0.0.1]) by mail.ca.certicom.com (Postfix) with ESMTP id D9F7E100233E0; Mon, 13 Mar 2006 11:50:45 -0500 (EST) Received: from mail.ca.certicom.com ([127.0.0.1]) by spamfilter.certicom.com (storm [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26836-25; Mon, 13 Mar 2006 11:50:44 -0500 (EST) Received: from certicom1.certicom.com (domino1.certicom.com [10.0.1.24]) by mail.ca.certicom.com (Postfix) with ESMTP id ED401100233C3; Mon, 13 Mar 2006 11:50:43 -0500 (EST) In-Reply-To: To: Subject: Re: [6lowpan] IEEE 802.15.4-2003 MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.5.5 November 30, 2005 Message-ID: From: Rene Struik Date: Mon, 13 Mar 2006 11:50:43 -0500 X-MIMETrack: Serialize by Router on Certicom1/Certicom(Release 6.5.4|March 27, 2005) at 03/13/2006 11:50:43 AM, Serialize complete at 03/13/2006 11:50:43 AM X-Spam-Score: 0.1 (/) X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a Cc: 6lowpan@lists.ietf.org, Jim.Bound@hp.com 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0317645335==" Errors-To: 6lowpan-bounces@ietf.org This is a multipart message in MIME format. --===============0317645335== Content-Type: multipart/alternative; boundary="=_alternative 005CFA7985257130_=" This is a multipart message in MIME format. --=_alternative 005CFA7985257130_= Content-Type: text/plain; charset="US-ASCII" Hi Peter: 802.15.4-2003 will disappear in time and be replaced by 802.15.4-2006 (what currently is 802.15.4b). Rene ----- Certicom Research http://www.certicom.com 03/13/2006 11:48 AM To <6lowpan@lists.ietf.org> cc Jim.Bound@hp.com Subject [6lowpan] IEEE 802.15.4-2003 So far 6lowpan WG has posted 2 drafts each referencing IEEE 802.15.4-2003. Is it correct to assume that this standard is going to remain a technology of choice for Layers 1 / 2 connectivity in sensor networks? If yes would it be fair to ask for making 802.15.4 available in the same fashion IETF publications are available? E.g. make a WG draft quoting all relevant parts of IEEE 802.15.4? Thank you, Peter _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --=_alternative 005CFA7985257130_= Content-Type: text/html; charset="US-ASCII"
Hi Peter:

802.15.4-2003 will disappear in time and be replaced by 802.15.4-2006 (what currently is 802.15.4b).

Rene
-----
Certicom Research
http://www.certicom.com


<peter.sherbin@bell.ca>

03/13/2006 11:48 AM

To
<6lowpan@lists.ietf.org>
cc
Jim.Bound@hp.com
Subject
[6lowpan] IEEE 802.15.4-2003





So far 6lowpan WG has posted 2 drafts each referencing IEEE 802.15.4-2003. Is it correct to assume that this standard is going to remain a technology of choice for Layers 1 / 2 connectivity in sensor networks?

If yes would it be fair to ask for making 802.15.4 available in the same fashion IETF publications are available? E.g. make a WG draft quoting all relevant parts of IEEE 802.15.4?

Thank you,

Peter

_______________________________________________
6lowpan mailing list
6lowpan@ietf.org
https://www1.ietf.org/mailman/listinfo/6lowpan
--=_alternative 005CFA7985257130_=-- --===============0317645335== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --===============0317645335==-- From 6lowpan-bounces@ietf.org Sun Mar 19 13:27:53 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FL2d4-0006fc-FV; Sun, 19 Mar 2006 13:27:50 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FL2d3-0006KO-1C for 6lowpan@lists.ietf.org; Sun, 19 Mar 2006 13:27:49 -0500 Received: from mailx.danfoss.com ([193.162.34.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FL2d2-0004Ue-7e for 6lowpan@lists.ietf.org; Sun, 19 Mar 2006 13:27:48 -0500 Received: from DKDN04MX62.dkdn04.danfoss.net ([10.6.2.62]) by mailx.danfoss.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 19 Mar 2006 19:27:40 +0100 Received: from dkdn01mx21.danfoss.net ([10.12.129.21]) by DKDN04MX62.dkdn04.danfoss.net with InterScan Message Security Suite; Sun, 19 Mar 2006 19:27:40 +0100 Received: from DKDN01MX34.danfoss.net ([10.12.128.14]) by dkdn01mx21.danfoss.net with Microsoft SMTPSVC(6.0.3790.1830); Sun, 19 Mar 2006 19:27:40 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [6lowpan] Working group last-call on problems document Date: Sun, 19 Mar 2006 19:27:37 +0100 Message-ID: <49A38D2FE2C53946A57916AD6A1F00D782E7A1@DKDN01MX34.danfoss.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [6lowpan] Working group last-call on problems document Thread-Index: AcZBWMHfBRvZv6zGTWWaOj0zysq26AAJ1rnQAn9UBjA= From: "Schumacher Christian Peter Pii" To: "Kushalnagar, Nandakishore" , "Soohong Daniel Park" , "Geoff Mulligan" , "6lowpan" <6lowpan@lists.ietf.org> X-OriginalArrivalTime: 19 Mar 2006 18:27:40.0171 (UTC) FILETIME=[CE114DB0:01C64B82] X-Spam-Score: 0.0 (/) X-Scan-Signature: b22590c27682ace61775ee7b453b40d3 Cc: 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org Sorry for the late feedback. As Daniel said, good job Nandu and Gab. However, I have the following nitpicks:=20 Section: 2. Overview Possibly missing a linespace between bullet 9. and 10. Section: 4.2. Topologies Last sentence in this section:=20 "This, or course..."=20 should probably be "This, of course" Section: 4.4. Limited configuration and management Last sentence in this section:=20 "...yet be powerful to control dense..." I suggest maybe to add "enough" between "powerful" and "to". Section: 4.6. Security Last sentence in this section: "Please refer to security consideration section below for an in depth requirements for security" I suggest change to: "Please refer to the security considerations section below for in depth security requirements." Section: 5. Goals (Page 7-8): I think the reader would gain a better understanding of the goals for 6lowpan if we start each goal with a clear definition (one-sentence) of the goal, then followed by the related background information. The goals appear more or less hidden in the text in its current form. This is especially true for goal nr. 2, which is mostly background information until at the end it is stated "this goal needs to investigate using existing header compression... ".=20 I also think the usage of word goal in goals 2 and 3 are confusing. Examples: "...this goal needs to investigate..." (Goal nr. 2) "The goal should specify a method..." (Goal nr. 3) It is we (the working group) not the goal , which needs to investigate and to specify. Correct me, if I'm reading it wrong. Overall I think the document is good, and I believe if you incorporate my nits on the goals section, then it is IESG ready.=20 Again, excellent work. :-) Regards Christian -----Original Message----- From: Kushalnagar, Nandakishore [mailto:nandakishore.kushalnagar@intel.com]=20 Sent: 7. marts 2006 01:45 To: Soohong Daniel Park; Geoff Mulligan; 6lowpan Subject: RE: [6lowpan] Working group last-call on problems document Thanks Daniel. Once all the comments are in, we will do a final walk through to clarify these inconsistencies. Regards Nandu -----Original Message----- From: Soohong Daniel Park [mailto:soohong.park@samsung.com]=20 Sent: Monday, March 06, 2006 12:01 PM To: Geoff Mulligan; 6lowpan Subject: Re: [6lowpan] Working group last-call on problems document I believe it is ready to the IESG. Good job Nandu and Gab...:-) Minor nits: both LoWPAN and 6LoWPAN seem a bit confused around the document. If available, defining terminology would be favorable. Daniel (Soohong Daniel Park) Mobile Convergence Laboratory, SAMSUNG Electronics. ----- Original Message -----=20 From: "Geoff Mulligan" To: "6lowpan" <6lowpan@lists.ietf.org> Sent: Tuesday, March 07, 2006 1:12 AM Subject: [6lowpan] Working group last-call on problems document > Hi, > This note starts the 6loWPAN Working Group Last-call for comments on > draft-ietf-6lowpan-problem-02.txt, "6LoWPAN: Overview, Assumptions, > Problem Statement and Goals". The document can be found at > ftp://ftp.ietf.org/internet-drafts/draft-ietf-6lowpan-problem-02.txt >=20 > Please review the document carefully, and send your feedback to the > list. Please also indicate whether or not you believe that this > document is ready to go to the IESG. >=20 > This Last Call will end on 20 March 2006 at 0900 MST (UTC - 7), two > weeks form the time of this call. >=20 > Thanks, > geoff >=20 >=20 >=20 >=20 > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan >=20 > _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Sun Mar 19 13:48:43 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FL2xG-0002Sp-LQ; Sun, 19 Mar 2006 13:48:42 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FL2xF-0002Sk-Fu for 6lowpan@lists.ietf.org; Sun, 19 Mar 2006 13:48:41 -0500 Received: from mailx.danfoss.com ([193.162.34.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FL2xE-00057M-Vr for 6lowpan@lists.ietf.org; Sun, 19 Mar 2006 13:48:41 -0500 Received: from DKDN04MX62.dkdn04.danfoss.net ([10.6.2.62]) by mailx.danfoss.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 19 Mar 2006 19:48:40 +0100 Received: from dkdn01mx21.danfoss.net ([10.12.129.21]) by DKDN04MX62.dkdn04.danfoss.net with InterScan Message Security Suite; Sun, 19 Mar 2006 19:48:40 +0100 Received: from DKDN01MX34.danfoss.net ([10.12.128.14]) by dkdn01mx21.danfoss.net with Microsoft SMTPSVC(6.0.3790.1830); Sun, 19 Mar 2006 19:48:39 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [6lowpan] new 6lowpan charter Date: Sun, 19 Mar 2006 19:48:37 +0100 Message-ID: <49A38D2FE2C53946A57916AD6A1F00D782E7A3@DKDN01MX34.danfoss.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [6lowpan] new 6lowpan charter Thread-Index: AcZC5EXvFK1PZKYLTgCcIAcaNUaspgIoL1Rg From: "Schumacher Christian Peter Pii" To: "6lowpan" <6lowpan@lists.ietf.org> X-OriginalArrivalTime: 19 Mar 2006 18:48:39.0827 (UTC) FILETIME=[BCE18E30:01C64B85] X-Spam-Score: 0.0 (/) X-Scan-Signature: 93e7fb8fef2e780414389440f367c879 Cc: 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org Based on received feedback, I have a new suggestion for charter scope. --- start of scope ---=20 Scope of 6lowpan:=20 Produce "Optimization of the Adhoc Routing Protocol for 6lowpans" to apply an existing MANET Protocol to LoWPANs. Produce "Optimization of the Neighbor Discovery Protocol for 6lowpans"=20 to define how to apply the existing Neighbor Discovery protocol in a=20 6lowpan.=20 Produce "IPv6 over Low Power WPAN Security Analysis" to define the=20 assumptions for a security model for 6lowpan. This includes analysis=20 of threats, identify types of devices and define the levels of trust=20 between these devices.=20 Produce "6lowpan Co-existence with other Networks" to define how to=20 co-exist with other networks. This includes analysis of how to survive=20 interference caused by IEEE 802.11 based networks, and investigate how to recognize and co-exist with other networks based on IEEE 802.15.4.=20 As such, the working group may also work on informational documents for service discovery, scalability of 6lowpan (routing and addressing),=20 mobility issues, naming service for mesh layer and gateway architecture. The working group will reuse existing specifications whenever=20 reasonable and possible.=20 The working group will also serve as a venue for ongoing discussions=20 on other topics related to the more complete list outlined above.=20 Additional related milestones may be added in the future via a=20 rechartering operation.=20 Note: As may be obvious from its official name above, this particular=20 working group will not work on IPv4 over IEEE 802.15.4 specifications.=20 Given the limitations of the target devices, dual-stack deployments=20 are not practical. Because of its higher potential for header=20 compression, its support for the huge number of devices expected and=20 of cleanly built-in features such as address autoconfiguration, IPv6=20 is the exclusive focus of the working group.=20 --- end of scope ---=20 Please provide feedback. Regards Christian PS: The original charter can be found at http://www.ietf.org/html.charters/6lowpan-charter.html=20 -----Original Message----- From: Soohong Daniel Park [mailto:soohong.park@samsung.com]=20 Sent: 8. marts 2006 20:13 To: Schumacher Christian Peter Pii; 6lowpan@lists.ietf.org Subject: Re: [6lowpan] new 6lowpan charter new 6lowpan charterI believe 6lowpan adhoc routing protocol must be included into our rechartering more specific than now. It is one of urgent task toward 6LoWPAN Current text is just copy-and-paste from the existing charter as follows: "As such, the working group may also work on an=20 informational document to show how to apply an=20 existing MANET protocol to LoWPANs (e.g.,=20 AODV, OLSR, DYMO, etc)." So, my suggestion is as follows: Produce "Optimization of the Adhoc Routing Protocol=20 for 6lowpans" to apply an existing MANET Protocol=20 to LoWPANs. Thanks in advance. Daniel (Soohong Daniel Park) Mobile Convergence Laboratory, SAMSUNG Electronics. ----- Original Message -----=20 From: Schumacher Christian Peter Pii=20 To: 6lowpan@lists.ietf.org=20 Sent: Tuesday, March 07, 2006 8:09 PM Subject: [6lowpan] new 6lowpan charter Hi.=20 During the 6lowpan interim meeting in January, the working group discussed possible topics for a future rechartering of 6lowpan. Based on available information from that meeting I've compiled the following text, which is an edited version of the scope present in the current 6lowpan charter. Feedback is appreciated.=20 --- start of scope ---=20 Scope of 6lowpan:=20 Produce "Optimization of the Neighbor Discovery Protocol for 6lowpans"=20 to define how to apply the existing Neighbor Discovery protocol in a=20 6lowpan.=20 Produce "IPv6 over Low Power WPAN Security Analysis" to define the=20 assumptions for a security model for 6lowpan. This includes analysis=20 of threats, identify types of devices and define the levels of trust=20 between these devices.=20 Produce "6lowpan Co-existence with other Networks" to define how to=20 co-exist with other networks. This includes analysis of how to survive=20 interference caused by IEEE 802.11 based networks, and investigate how to=20 recognize and co-exist with other networks based on IEEE 802.15.4.=20 As such, the working group may also work on an informational document=20 to show how to apply an existing MANET protocol to LoWPANs (e.g.,=20 AODV, OLSR, DYMO, etc).=20 The working group will reuse existing specifications whenever=20 reasonable and possible.=20 The working group will also serve as a venue for ongoing discussions=20 on other topics related to the more complete list outlined above.=20 Additional related milestones may be added in the future via a=20 rechartering operation.=20 Note: As may be obvious from its official name above, this particular=20 working group will not work on IPv4 over IEEE 802.15.4 specifications.=20 Given the limitations of the target devices, dual-stack deployments=20 are not practical. Because of its higher potential for header=20 compression, its support for the huge number of devices expected and=20 of cleanly built-in features such as address autoconfiguration, IPv6=20 is the exclusive focus of the working group.=20 --- end of scope ---=20 Looking forward to receive your feedback.=20 Regards=20 Christian=20 PS: The original charter can be found at http://www.ietf.org/html.charters/6lowpan-charter.html=20 _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Sun Mar 19 18:01:44 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FL6u8-0006lo-Hp; Sun, 19 Mar 2006 18:01:44 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FL6u6-0006l3-Jb for 6lowpan@lists.ietf.org; Sun, 19 Mar 2006 18:01:42 -0500 Received: from mailx.danfoss.com ([193.162.34.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FL6u5-0006cK-AP for 6lowpan@lists.ietf.org; Sun, 19 Mar 2006 18:01:42 -0500 Received: from DKDN04MX62.dkdn04.danfoss.net ([10.6.2.62]) by mailx.danfoss.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 20 Mar 2006 00:01:40 +0100 Received: from dkdn01mx21.danfoss.net ([10.12.129.21]) by DKDN04MX62.dkdn04.danfoss.net with InterScan Message Security Suite; Mon, 20 Mar 2006 00:01:40 +0100 Received: from dkdn01mx25.danfoss.net ([10.12.129.25]) by dkdn01mx21.danfoss.net with Microsoft SMTPSVC(6.0.3790.1830); Mon, 20 Mar 2006 00:01:39 +0100 Received: from DKDN01MX34.danfoss.net ([10.12.128.14]) by dkdn01mx25.danfoss.net with Microsoft SMTPSVC(6.0.3790.1830); Mon, 20 Mar 2006 00:01:39 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Mon, 20 Mar 2006 00:01:32 +0100 Message-ID: <49A38D2FE2C53946A57916AD6A1F00D782E7B1@DKDN01MX34.danfoss.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: friday's agenda Thread-Index: AcZLqRB5Nxmk5y/SQH+/c7PBtdEOMg== From: "Schumacher Christian Peter Pii" To: "Carsten Bormann" , "Geoff Mulligan" X-OriginalArrivalTime: 19 Mar 2006 23:01:39.0730 (UTC) FILETIME=[14CEEF20:01C64BA9] X-Spam-Score: 0.0 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Cc: 6lowpan <6lowpan@lists.ietf.org> Subject: [6lowpan] friday's agenda 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0644343623==" Errors-To: 6lowpan-bounces@ietf.org This is a multi-part message in MIME format. --===============0644343623== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C64BA9.141A314A" This is a multi-part message in MIME format. ------_=_NextPart_001_01C64BA9.141A314A Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Carsten and Geoff, what is the status of the official agenda for 6lowpan WG meeting on friday? Regards Christian ------_=_NextPart_001_01C64BA9.141A314A Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable friday's agenda

Carsten and Geoff, what is the status = of the official agenda for 6lowpan WG meeting on friday?

Regards
Christian



------_=_NextPart_001_01C64BA9.141A314A-- --===============0644343623== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --===============0644343623==-- From 6lowpan-bounces@ietf.org Mon Mar 20 03:06:12 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLFOt-0004h9-GU; Mon, 20 Mar 2006 03:06:03 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLFOr-0004gj-L9 for 6lowpan@lists.ietf.org; Mon, 20 Mar 2006 03:06:01 -0500 Received: from pproxy.gmail.com ([64.233.166.181]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLFOq-0007dV-DK for 6lowpan@lists.ietf.org; Mon, 20 Mar 2006 03:06:01 -0500 Received: by pproxy.gmail.com with SMTP id n25so205060pyg for <6lowpan@lists.ietf.org>; Mon, 20 Mar 2006 00:06:00 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=k392yayaIot9wC/RYVlJJg9ov/Z6nRzRb+zE7uwrocRj1U/4t9/lVOofebfBgu/w1S2xFyCQe/rE+GYnF8vCho1xHKeHvCKIEqWJiiOLiV5Bh5EGB+/kpbSawzo4U9EO/QV99SnB5hRL1asfJt1OoHg9IKZGr1OSCOiSjr4NqhQ= Received: by 10.64.233.4 with SMTP id f4mr180739qbh; Mon, 20 Mar 2006 00:05:59 -0800 (PST) Received: by 10.64.203.5 with HTTP; Mon, 20 Mar 2006 00:05:59 -0800 (PST) Message-ID: Date: Mon, 20 Mar 2006 17:05:59 +0900 From: "Ki-Hyung Kim" To: "Schumacher Christian Peter Pii" Subject: Re: [6lowpan] new 6lowpan charter In-Reply-To: <49A38D2FE2C53946A57916AD6A1F00D782E7A3@DKDN01MX34.danfoss.net> MIME-Version: 1.0 References: <49A38D2FE2C53946A57916AD6A1F00D782E7A3@DKDN01MX34.danfoss.net> X-Spam-Score: 0.8 (/) X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1337563787==" Errors-To: 6lowpan-bounces@ietf.org --===============1337563787== Content-Type: multipart/alternative; boundary="----=_Part_14979_23334061.1142841959930" ------=_Part_14979_23334061.1142841959930 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline >As such, the working group may also work on informational documents for >service discovery, scalability of 6lowpan (routing and addressing), >mobility issues, naming service for mesh layer and gateway architecture. Christian, let me add more details in terms of our rechartering deliberables into the listed items as follows; Produce "Service Discovery Protocol for 6LoWPAN" to define how to discover, control and maintain services provided by 6lowpan devices. Produce "Scalability of 6LoWPAN" to define a routing protocol for the lare number of devices which is expected to be deployed in 6LoWPAN while considering the limited capabilities of the devices (low power, limited memory space, and small packet size). Produce "Interoperability of 6LoWPAN" to define the gateway Architecture between 6LoWPAN and external IPv6 networks. All comment are highly welcome. __ Ki-Hyung Kim Associate Professor Division of Information and Computer Eng., Ajou University, Suwon, Korea 442-749 Tel:+82-31-219-2433, http://ilab.ajou.ac.kr ------=_Part_14979_23334061.1142841959930 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
>As such, the working group may also work on informational document= s for
>service discovery, scalability of 6lowpan (routing and address= ing),
>mobility issues, naming service for mesh layer and gateway arc= hitecture.
 
Christian, let me add more details in terms of our rechartering
deliberables into the listed items as follows;

Produce "Service Discovery Protocol for 6LoWPAN" to defi= ne how
to discover, control and maintain services provided by 6lowpan d= evices.

Produce "Scalability of 6LoWPAN" to define a routing protocol<= br>for the lare number of devices which is expected to be deployed in
6= LoWPAN while considering the limited capabilities of the devices
(low p= ower, limited memory space, and small packet size).

Produce "Interoperability of 6LoWPAN" to define the gateway Architecture between 6LoWPAN and external IPv6 networks.

All comment are highly welcome. 

__
Ki-Hyung Kim
Associate Professor
Division of Informati= on and Computer Eng.,
Ajou University, Suwon, Korea 442-749
Tel:+82-= 31-219-2433, http://ilab.ajou.ac.kr
 
------=_Part_14979_23334061.1142841959930-- --===============1337563787== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --===============1337563787==-- From 6lowpan-bounces@ietf.org Mon Mar 20 14:19:27 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLPuV-00036d-5s; Mon, 20 Mar 2006 14:19:23 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLPuU-00036Y-Ap for 6lowpan@lists.ietf.org; Mon, 20 Mar 2006 14:19:22 -0500 Received: from mailx.danfoss.com ([193.162.34.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLPuS-00079w-ST for 6lowpan@lists.ietf.org; Mon, 20 Mar 2006 14:19:22 -0500 Received: from DKDN04MX62.dkdn04.danfoss.net ([10.6.2.62]) by mailx.danfoss.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 20 Mar 2006 20:19:17 +0100 Received: from dkdn01mx21.danfoss.net ([10.12.129.21]) by DKDN04MX62.dkdn04.danfoss.net with InterScan Message Security Suite; Mon, 20 Mar 2006 20:19:16 +0100 Received: from DKDN01MX34.danfoss.net ([10.12.128.14]) by dkdn01mx21.danfoss.net with Microsoft SMTPSVC(6.0.3790.1830); Mon, 20 Mar 2006 20:19:16 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [6lowpan] new 6lowpan charter Date: Mon, 20 Mar 2006 20:19:09 +0100 Message-ID: <49A38D2FE2C53946A57916AD6A1F00D782E8A4@DKDN01MX34.danfoss.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [6lowpan] new 6lowpan charter Thread-Index: AcZL9SCJHpLkANQ3R+SR1ZRxCbknSgAXUcCg From: "Schumacher Christian Peter Pii" To: "Ki-Hyung Kim" X-OriginalArrivalTime: 20 Mar 2006 19:19:16.0445 (UTC) FILETIME=[2E00F8D0:01C64C53] X-Spam-Score: 0.1 (/) X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1738924455==" Errors-To: 6lowpan-bounces@ietf.org This is a multi-part message in MIME format. --===============1738924455== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C64C53.2DBA1223" This is a multi-part message in MIME format. ------_=_NextPart_001_01C64C53.2DBA1223 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I've put the current version of the edited charter onto the 6lowpan wiki. =20 You can find it at: http://6lowpan.tzi.org/recharter =20 Regards Christian ________________________________ From: Ki-Hyung Kim [mailto:kkim86@gmail.com]=20 Sent: 20. marts 2006 02:06 To: Schumacher Christian Peter Pii Cc: 6lowpan Subject: Re: [6lowpan] new 6lowpan charter >As such, the working group may also work on informational documents for >service discovery, scalability of 6lowpan (routing and addressing), >mobility issues, naming service for mesh layer and gateway architecture.=20 =20 Christian, let me add more details in terms of our rechartering deliberables into the listed items as follows; Produce "Service Discovery Protocol for 6LoWPAN" to define how=20 to discover, control and maintain services provided by 6lowpan devices. Produce "Scalability of 6LoWPAN" to define a routing protocol for the lare number of devices which is expected to be deployed in=20 6LoWPAN while considering the limited capabilities of the devices=20 (low power, limited memory space, and small packet size).=20 Produce "Interoperability of 6LoWPAN" to define the gateway=20 Architecture between 6LoWPAN and external IPv6 networks. All comment are highly welcome.=20 __ Ki-Hyung Kim Associate Professor Division of Information and Computer Eng.,=20 Ajou University, Suwon, Korea 442-749 Tel:+82-31-219-2433, http://ilab.ajou.ac.kr=20 =20 ------_=_NextPart_001_01C64C53.2DBA1223 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
I've=20 put the current version of the edited charter onto the 6lowpan=20 wiki.
 
You=20 can find it at: http://6lowpan.tzi.org/recharte= r
 
Regards
Christian

From: Ki-Hyung Kim = [mailto:kkim86@gmail.com]=20
Sent: 20. marts 2006 02:06
To: Schumacher Christian = Peter=20 Pii
Cc: 6lowpan
Subject: Re: [6lowpan] new 6lowpan=20 charter

>As such, the working group may also work on informational = documents=20 for
>service discovery, scalability of 6lowpan (routing and=20 addressing),
>mobility issues, naming service for mesh layer and = gateway=20 architecture.
 
Christian, let me add more details in terms of our = rechartering
deliberables into the listed items as follows;

Produce "Service Discovery Protocol for 6LoWPAN" to define how =
to=20 discover, control and maintain services provided by 6lowpan = devices.

Produce "Scalability of 6LoWPAN" to define a routing protocol
for = the lare=20 number of devices which is expected to be deployed in
6LoWPAN while=20 considering the limited capabilities of the devices
(low power, = limited=20 memory space, and small packet size).

Produce "Interoperability of 6LoWPAN" to define the gateway =
Architecture=20 between 6LoWPAN and external IPv6 networks.

All comment are highly welcome. 

__
Ki-Hyung Kim
Associate Professor
Division of = Information=20 and Computer Eng.,
Ajou University, Suwon, Korea=20 442-749
Tel:+82-31-219-2433, http://ilab.ajou.ac.kr=20
 
------_=_NextPart_001_01C64C53.2DBA1223-- --===============1738924455== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --===============1738924455==-- From 6lowpan-bounces@ietf.org Mon Mar 20 15:56:12 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRQB-00006l-B8; Mon, 20 Mar 2006 15:56:11 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRQ9-00006d-SL for 6lowpan@ietf.org; Mon, 20 Mar 2006 15:56:09 -0500 Received: from mailhost.informatik.uni-bremen.de ([134.102.201.18] helo=informatik.uni-bremen.de) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLRQ8-0003Aj-Fl for 6lowpan@ietf.org; Mon, 20 Mar 2006 15:56:09 -0500 Received: from [127.0.0.1] (maildrop.informatik.uni-bremen.de [134.102.201.19]) by informatik.uni-bremen.de (8.13.4/8.13.2) with ESMTP id k2KKtfdp009594; Mon, 20 Mar 2006 21:55:45 +0100 (CET) In-Reply-To: <49A38D2FE2C53946A57916AD6A1F00D782E7B1@DKDN01MX34.danfoss.net> References: <49A38D2FE2C53946A57916AD6A1F00D782E7B1@DKDN01MX34.danfoss.net> Mime-Version: 1.0 (Apple Message framework v746.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Carsten Bormann Subject: Re: [6lowpan] friday's agenda Date: Mon, 20 Mar 2006 14:55:40 -0600 To: Schumacher Christian Peter Pii X-Mailer: Apple Mail (2.746.3) X-Virus-Scanned: by amavisd-new X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Cc: Carsten Bormann , 6lowpan@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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org On Mar 19 2006, at 17:01, Christian Schumacher wrote: > Carsten and Geoff, what is the status of the official agenda for > 6lowpan WG meeting on friday? Well, I think that status is called "very very late" in English... An initial draft of the agenda is at http://6lowpan.tzi.org/6lowpan_20at_20IETF_2065 Please also follow the "recharter" link and send comments on the draft charter to this list. There are names of possible contributors in the proposed charter -- these are not meant to be exclusive, and we would like to hear which ones of the potential charter items each of you wants to work on. Apart from the Friday WG meeting, we plan to have a 6lowpan dinner on Thursday (after the plenary) -- please RSVP to Christian if you want to participate. Gruesse, Carsten _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Mon Mar 20 18:01:56 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLTNr-0005BF-Ch; Mon, 20 Mar 2006 18:01:55 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLTNq-0005AA-5E for 6lowpan@ietf.org; Mon, 20 Mar 2006 18:01:54 -0500 Received: from wproxy.gmail.com ([64.233.184.198]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLTNo-0008Ud-S5 for 6lowpan@ietf.org; Mon, 20 Mar 2006 18:01:54 -0500 Received: by wproxy.gmail.com with SMTP id i23so1167678wra for <6lowpan@ietf.org>; Mon, 20 Mar 2006 15:01:52 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=lZJk5cFcEfKAXjBAQ1QOjmgiPMoUq+OBYNiG+89UY9iml+JsF3QmS5y37fBmeOnPfHgUEmJXXMvCJWJYNhFPi8ftkp3v1gKxTKsP8tB+2vlIjgaRS6w12dzK8mWinYnno25DMHksSxeBp7ED0znWuJ1tNHgzX+5fLpuOYng4kcc= Received: by 10.65.235.12 with SMTP id m12mr767944qbr; Mon, 20 Mar 2006 15:01:13 -0800 (PST) Received: by 10.64.203.5 with HTTP; Mon, 20 Mar 2006 15:01:13 -0800 (PST) Message-ID: Date: Tue, 21 Mar 2006 08:01:13 +0900 From: "Ki-Hyung Kim" To: "Carsten Bormann" Subject: Re: [6lowpan] friday's agenda In-Reply-To: MIME-Version: 1.0 References: <49A38D2FE2C53946A57916AD6A1F00D782E7B1@DKDN01MX34.danfoss.net> X-Spam-Score: 0.6 (/) X-Scan-Signature: 73734d43604d52d23b3eba644a169745 Cc: 6lowpan@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: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1754168201==" Errors-To: 6lowpan-bounces@ietf.org --===============1754168201== Content-Type: multipart/alternative; boundary="----=_Part_1491_16133756.1142895673799" ------=_Part_1491_16133756.1142895673799 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I will participate the dinner on thursday. On 3/21/06, Carsten Bormann wrote: > > On Mar 19 2006, at 17:01, Christian Schumacher wrote: > > Carsten and Geoff, what is the status of the official agenda for > > 6lowpan WG meeting on friday? > Well, I think that status is called "very very late" in English... > > An initial draft of the agenda is at > > http://6lowpan.tzi.org/6lowpan_20at_20IETF_2065 > > Please also follow the "recharter" link and send comments on the > draft charter to this list. > There are names of possible contributors in the proposed charter -- > these are not meant to be exclusive, and we would like to hear which > ones of the potential charter items each of you wants to work on. > > Apart from the Friday WG meeting, we plan to have a 6lowpan dinner on > Thursday (after the plenary) -- please RSVP to Christian if you want > to participate. > > Gruesse, Carsten > > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan > -- __ Ki-Hyung Kim Associate Professor Division of Information and Computer Eng., Ajou University, Suwon, Korea 442-749 Tel:+82-31-219-2433, http://ilab.ajou.ac.kr ------=_Part_1491_16133756.1142895673799 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
I will participate the dinner on thursday.


 
On 3/21/06, = Carsten Bormann <cabo@tzi.org>= ; wrote:
On Mar 19 2006, at 17:01, Christ= ian Schumacher wrote:
> Carsten and Geoff, what is the status of the = official agenda for
> 6lowpan WG meeting on friday?
Well, I think that status is call= ed "very very late" in English...

An initial draft of the = agenda is at

       http://6lowpan.tzi.org/6lowpan_20at_20IETF_2065

Please also foll= ow the "recharter" link and send comments on the
draft charter= to this list.
There are names of possible contributors in the proposed = charter --
these are not meant to be exclusive, and we would like to hear whichones of the potential charter items each of you wants to work on.

A= part from the Friday WG meeting, we plan to have a 6lowpan dinner on
Thursday (after the plenary) -- please RSVP to Christian if you want
to = participate.

Gruesse, Carsten


___________________________= ____________________
6lowpan mailing list
6lowpan@ietf.org
https://www1.ietf.org/mailman/listinfo/6lowpan
=



--
__
Ki-Hyung Kim
Associate Prof= essor
Division of Information and Computer Eng.,
Ajou University, Suwon, = Korea 442-749
Tel:+82-31-219-2433, ht= tp://ilab.ajou.ac.kr
------=_Part_1491_16133756.1142895673799-- --===============1754168201== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --===============1754168201==-- From 6lowpan-bounces@ietf.org Mon Mar 20 19:38:01 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLUsp-0004pP-7m; Mon, 20 Mar 2006 19:37:59 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLUsn-0004nw-Le for 6lowpan@ietf.org; Mon, 20 Mar 2006 19:37:57 -0500 Received: from wproxy.gmail.com ([64.233.184.202]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLUsm-0004VS-Ak for 6lowpan@ietf.org; Mon, 20 Mar 2006 19:37:57 -0500 Received: by wproxy.gmail.com with SMTP id 50so1138920wri for <6lowpan@ietf.org>; Mon, 20 Mar 2006 16:37:56 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=T8jEhG++znZxJnF9nF7ih3N62fPUlyc03W+OL2mP9on6VCy8jCLlHF9Vjnj94fYhLpkvvLtml72u1qbT0yYLC7X1wUDR0dpa/wJSjKRDZwfOUjwUqDsUK7AKLqFvRO1HO2QV1p2zsX7f8mZn15mNfDwBbQPVgpfBvkm5d+xIgEM= Received: by 10.65.20.2 with SMTP id x2mr854681qbi; Mon, 20 Mar 2006 16:37:55 -0800 (PST) Received: by 10.64.203.5 with HTTP; Mon, 20 Mar 2006 16:37:55 -0800 (PST) Message-ID: Date: Tue, 21 Mar 2006 09:37:55 +0900 From: "Ki-Hyung Kim" To: "Carsten Bormann" Subject: Re: [6lowpan] friday's agenda In-Reply-To: MIME-Version: 1.0 References: <49A38D2FE2C53946A57916AD6A1F00D782E7B1@DKDN01MX34.danfoss.net> X-Spam-Score: 0.6 (/) X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0 Cc: 6lowpan@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: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0072889098==" Errors-To: 6lowpan-bounces@ietf.org --===============0072889098== Content-Type: multipart/alternative; boundary="----=_Part_2387_26060231.1142901475011" ------=_Part_2387_26060231.1142901475011 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Geoff and Carsten, On 6lowpan WG meeting friday, I would like to request a 30-minute demonstration of a 6lowpan prototype in which users on the Internet can directly access 6lowpan devices via a gateway. The web page of the prototype is www.6lowpan.net. The webserver is currently collecting temperature measurement from IPv6 enabled 6lowpan devices via a gateway. Additionally, a user will be able to access the 6lowpan devices directly vi= a a client program, not only via a web server. In the 30-minute demonstration, I would like to briefly present the overall architecture of the prototype, including the compliance to the current format document, the routing protocol, gateway, etc. On 3/21/06, Carsten Bormann wrote: > > On Mar 19 2006, at 17:01, Christian Schumacher wrote: > > Carsten and Geoff, what is the status of the official agenda for > > 6lowpan WG meeting on friday? > Well, I think that status is called "very very late" in English... > > An initial draft of the agenda is at > > http://6lowpan.tzi.org/6lowpan_20at_20IETF_2065 > > Please also follow the "recharter" link and send comments on the > draft charter to this list. > There are names of possible contributors in the proposed charter -- > these are not meant to be exclusive, and we would like to hear which > ones of the potential charter items each of you wants to work on. > > Apart from the Friday WG meeting, we plan to have a 6lowpan dinner on > Thursday (after the plenary) -- please RSVP to Christian if you want > to participate. > > Gruesse, Carsten > > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan > -- __ Ki-Hyung Kim Associate Professor Division of Information and Computer Eng., Ajou University, Suwon, Korea 442-749 Tel:+82-31-219-2433, http://ilab.ajou.ac.kr ------=_Part_2387_26060231.1142901475011 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Geoff and Carsten,
On 6lowpan WG meeting friday, I would like to request a 30-m= inute demonstration of a 6lowpan prototype in which users on the Internet c= an directly access 6lowpan devices via a gateway.
 
The web page of the prototype is www.6lowpan.net.
The webserver is currently collecting temperature measurement fro= m IPv6 enabled 6lowpan devices via a gateway.
Additionally, a user will be able to access the 6lowpan devi= ces directly via a client program, not only via a web server.
 
In the 30-minute demonstration, I would like to briefly present t= he overall architecture of the prototype, including the compliance to the c= urrent format document, the routing protocol, gateway, etc.
 
 


 
On 3/21/06, = Carsten Bormann <cabo@tzi.org>= ; wrote:
On Mar 19 2006, at 17:01, Christ= ian Schumacher wrote:
> Carsten and Geoff, what is the status of the = official agenda for
> 6lowpan WG meeting on friday?
Well, I think that status is call= ed "very very late" in English...

An initial draft of the = agenda is at

       http://6lowpan.tzi.org/6lowpan_20at_20IETF_2065

Please also foll= ow the "recharter" link and send comments on the
draft charter= to this list.
There are names of possible contributors in the proposed = charter --
these are not meant to be exclusive, and we would like to hear whichones of the potential charter items each of you wants to work on.

A= part from the Friday WG meeting, we plan to have a 6lowpan dinner on
Thursday (after the plenary) -- please RSVP to Christian if you want
to = participate.

Gruesse, Carsten


___________________________= ____________________
6lowpan mailing list
6lowpan@ietf.org
https://www1.ietf.org/mailman/listinfo/6lowpan
=



--
__
Ki-Hyung Kim
Associate Prof= essor
Division of Information and Computer Eng.,
Ajou University, Suwon, = Korea 442-749
Tel:+82-31-219-2433, ht= tp://ilab.ajou.ac.kr
------=_Part_2387_26060231.1142901475011-- --===============0072889098== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --===============0072889098==-- From 6lowpan-bounces@ietf.org Mon Mar 20 19:41:38 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLUwM-0006ht-O5; Mon, 20 Mar 2006 19:41:38 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLUwM-0006ho-2g for 6lowpan@ietf.org; Mon, 20 Mar 2006 19:41:38 -0500 Received: from zproxy.gmail.com ([64.233.162.196]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLUwK-0004jk-PV for 6lowpan@ietf.org; Mon, 20 Mar 2006 19:41:38 -0500 Received: by zproxy.gmail.com with SMTP id q3so1267268nzb for <6lowpan@ietf.org>; Mon, 20 Mar 2006 16:41:36 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=LA/zA/dBQZGrL6KN6PVjOeDJmAWp6HFwN0m5leXSaB3sstTqDk15gweJlqIAERekd5XkiOMHnY6eoAQSexOYEuofd0xlDdFqwV4wdvY/siSzCBzjCeKfZwi4pBoXx7qH+NB8ekc+XDyDa89KiM/l9bU8zAui1pB+ZGxorOZq/z0= Received: by 10.65.98.6 with SMTP id a6mr878741qbm; Mon, 20 Mar 2006 16:41:35 -0800 (PST) Received: by 10.65.185.14 with HTTP; Mon, 20 Mar 2006 16:41:35 -0800 (PST) Message-ID: <43b91d370603201641k73da9c25mb3b846473eee39d9@mail.gmail.com> Date: Mon, 20 Mar 2006 16:41:35 -0800 From: "Samita Chakrabarti" To: "Carsten Bormann" Subject: Re: [6lowpan] friday's agenda In-Reply-To: MIME-Version: 1.0 References: <49A38D2FE2C53946A57916AD6A1F00D782E7B1@DKDN01MX34.danfoss.net> X-Spam-Score: 0.1 (/) X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43 Cc: 6lowpan@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: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0791709562==" Errors-To: 6lowpan-bounces@ietf.org --===============0791709562== Content-Type: multipart/alternative; boundary="----=_Part_9012_28182245.1142901695830" ------=_Part_9012_28182245.1142901695830 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi Carsten: I wonder if we have time for 6lowpan-ND draft update presentation this time? As per interim meeting discussion, we have submitted a new draft. Would like to receive wg input on that. Thanks, -Samita On 3/20/06, Carsten Bormann wrote: > > On Mar 19 2006, at 17:01, Christian Schumacher wrote: > > Carsten and Geoff, what is the status of the official agenda for > > 6lowpan WG meeting on friday? > Well, I think that status is called "very very late" in English... > > An initial draft of the agenda is at > > http://6lowpan.tzi.org/6lowpan_20at_20IETF_2065 > > Please also follow the "recharter" link and send comments on the > draft charter to this list. > There are names of possible contributors in the proposed charter -- > these are not meant to be exclusive, and we would like to hear which > ones of the potential charter items each of you wants to work on. > > Apart from the Friday WG meeting, we plan to have a 6lowpan dinner on > Thursday (after the plenary) -- please RSVP to Christian if you want > to participate. > > Gruesse, Carsten > > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan > ------=_Part_9012_28182245.1142901695830 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Hi Carsten:
 
I wonder if we have time for 6lowpan-ND draft update presentation
this time?  As per interim meeting discussion, we have submitted<= /div>
a new draft.  Would like to receive wg input on that.
 
Thanks,
-Samita
 


 
On 3/20/06, = Carsten Bormann <cabo@tzi.org>= ; wrote:
On Mar 19 2006, at 17:01, Christ= ian Schumacher wrote:
> Carsten and Geoff, what is the status of the = official agenda for
> 6lowpan WG meeting on friday?
Well, I think that status is call= ed "very very late" in English...

An initial draft of the = agenda is at

       http://6lowpan.tzi.org/6lowpan_20at_20IETF_2065

Please also foll= ow the "recharter" link and send comments on the
draft charter= to this list.
There are names of possible contributors in the proposed = charter --
these are not meant to be exclusive, and we would like to hear whichones of the potential charter items each of you wants to work on.

A= part from the Friday WG meeting, we plan to have a 6lowpan dinner on
Thursday (after the plenary) -- please RSVP to Christian if you want
to = participate.

Gruesse, Carsten


___________________________= ____________________
6lowpan mailing list
6lowpan@ietf.org
https://www1.ietf.org/mailman/listinfo/6lowpan
=

------=_Part_9012_28182245.1142901695830-- --===============0791709562== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --===============0791709562==-- From 6lowpan-bounces@ietf.org Mon Mar 20 20:05:17 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLVJD-0002cC-TN; Mon, 20 Mar 2006 20:05:15 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLVJC-0002c6-JD for 6lowpan@ietf.org; Mon, 20 Mar 2006 20:05:14 -0500 Received: from mailhost.informatik.uni-bremen.de ([134.102.201.18] helo=informatik.uni-bremen.de) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLVJB-0005on-7H for 6lowpan@ietf.org; Mon, 20 Mar 2006 20:05:14 -0500 Received: from [127.0.0.1] (maildrop.informatik.uni-bremen.de [134.102.201.19]) by informatik.uni-bremen.de (8.13.4/8.13.2) with ESMTP id k2L155hK013751; Tue, 21 Mar 2006 02:05:06 +0100 (CET) In-Reply-To: <43b91d370603201641k73da9c25mb3b846473eee39d9@mail.gmail.com> References: <49A38D2FE2C53946A57916AD6A1F00D782E7B1@DKDN01MX34.danfoss.net> <43b91d370603201641k73da9c25mb3b846473eee39d9@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v746.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <28603F54-9471-4C2F-B5F2-D07FBB22FE03@tzi.org> Content-Transfer-Encoding: 7bit From: Carsten Bormann Subject: Re: [6lowpan] friday's agenda Date: Mon, 20 Mar 2006 19:05:01 -0600 To: "Samita Chakrabarti" X-Mailer: Apple Mail (2.746.3) X-Virus-Scanned: by amavisd-new X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Cc: Carsten Bormann , 6lowpan@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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org On Mar 20 2006, at 18:41 , Samita Chakrabarti wrote: > Hi Carsten: > > I wonder if we have time for 6lowpan-ND draft update presentation > this time? As per interim meeting discussion, we have submitted > a new draft. Would like to receive wg input on that. Sure; this would be under the heading "new work" of the provisional agenda. I've put you down there (assuming you are referring to draft- chakrabarti-6lowpan-ipv6-nd-01.txt). We still need to allocate time, what's your time requirement? (Quick update + discussion time?) Gruesse, Carsten _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Mon Mar 20 20:13:22 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLVR3-0000A2-QR; Mon, 20 Mar 2006 20:13:21 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLVR2-00009u-VF for 6lowpan@lists.ietf.org; Mon, 20 Mar 2006 20:13:20 -0500 Received: from zproxy.gmail.com ([64.233.162.201]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLVR2-0006Ba-C0 for 6lowpan@lists.ietf.org; Mon, 20 Mar 2006 20:13:20 -0500 Received: by zproxy.gmail.com with SMTP id s1so1380690nze for <6lowpan@lists.ietf.org>; Mon, 20 Mar 2006 17:13:19 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=IkgQlXEq7AU3IZPEihArNt9WF6SS4+KeclZzvXKD7hcFjtfQWGp7myfp0s62Sd/xg0tz98srcVByZ4xRqimHsv5AV7iKTKykMbYeAvP+Ll7di6nibkWsjgszm3DShi0RgBmQDeGo4y5dZgC6umKrWQCSa8+/GFN7EuinEz4omc8= Received: by 10.65.156.12 with SMTP id i12mr901838qbo; Mon, 20 Mar 2006 17:13:19 -0800 (PST) Received: by 10.65.185.14 with HTTP; Mon, 20 Mar 2006 17:13:19 -0800 (PST) Message-ID: <43b91d370603201713y426f34fk1ede4fc89faa6a50@mail.gmail.com> Date: Mon, 20 Mar 2006 17:13:19 -0800 From: "Samita Chakrabarti" To: "Schumacher Christian Peter Pii" Subject: Re: [6lowpan] new 6lowpan charter In-Reply-To: <49A38D2FE2C53946A57916AD6A1F00D782E7A3@DKDN01MX34.danfoss.net> MIME-Version: 1.0 References: <49A38D2FE2C53946A57916AD6A1F00D782E7A3@DKDN01MX34.danfoss.net> X-Spam-Score: 0.5 (/) X-Scan-Signature: f0ea5880a0890be2408609376fa519aa 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1336455532==" Errors-To: 6lowpan-bounces@ietf.org --===============1336455532== Content-Type: multipart/alternative; boundary="----=_Part_9252_958299.1142903599571" ------=_Part_9252_958299.1142903599571 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi Christian: Thanks for bringing up the charter discussion. My comments are in-line. On 3/19/06, Schumacher Christian Peter Pii wrote: > > Based on received feedback, I have a new suggestion for charter scope. > > --- start of scope --- > > Scope of 6lowpan: > > Produce "Optimization of the Adhoc Routing Protocol for 6lowpans" > to apply an existing MANET Protocol to LoWPANs. Agree. Produce "Optimization of the Neighbor Discovery Protocol for 6lowpans" > to define how to apply the existing Neighbor Discovery protocol in a > 6lowpan. Agree. Produce "IPv6 over Low Power WPAN Security Analysis" to define the > assumptions for a security model for 6lowpan. This includes analysis > of threats, identify types of devices and define the levels of trust > between these devices. I think this document would be an informational document. In addition to analysis of threats, it would be useful to discuss what level of security t= o be applied in different level of communications such as in application-layer, network layer or link-layer. Produce "6lowpan Co-existence with other Networks" to define how to > co-exist with other networks. This includes analysis of how to survive > interference caused by IEEE 802.11 based networks, and investigate how > to recognize and co-exist with other networks based on IEEE 802.15.4. This might be another useful guideline to the community. But I'd think, it as a low priority item. As such, the working group may also work on informational documents for > service discovery, scalability of 6lowpan (routing and addressing), I am not sure about importance of scalability in 6lowPan. I thought, we introduced IPv6 to solve the scalability problem. If we use 64bit UID address scheme for MAC address, then I don't see a scalability issue. The 16bit MAC addresses could be treated as local addresses - same way as IPv6 treats link-local addresses - we can simply decide not to route those addresses outside local PAN and use 64bit unique address for global communication end-to-end. Adding 16bit address support for inter-pan communication will add much complexity. Thanks, -Samita mobility issues, naming service for mesh layer and gateway architecture. > > The working group will reuse existing specifications whenever > reasonable and possible. > > The working group will also serve as a venue for ongoing discussions > on other topics related to the more complete list outlined above. > Additional related milestones may be added in the future via a > rechartering operation. > > Note: As may be obvious from its official name above, this particular > working group will not work on IPv4 over IEEE 802.15.4 specifications. > Given the limitations of the target devices, dual-stack deployments > are not practical. Because of its higher potential for header > compression, its support for the huge number of devices expected and > of cleanly built-in features such as address autoconfiguration, IPv6 > is the exclusive focus of the working group. > > --- end of scope --- > > Please provide feedback. > > Regards > Christian > > PS: The original charter can be found at > http://www.ietf.org/html.charters/6lowpan-charter.html > > > -----Original Message----- > From: Soohong Daniel Park [mailto:soohong.park@samsung.com] > Sent: 8. marts 2006 20:13 > To: Schumacher Christian Peter Pii; 6lowpan@lists.ietf.org > Subject: Re: [6lowpan] new 6lowpan charter > > new 6lowpan charterI believe 6lowpan adhoc routing protocol must be > included into our rechartering more specific than > now. It is one of urgent task toward 6LoWPAN > Current text is just copy-and-paste from the > existing charter as follows: > > "As such, the working group may also work on an > informational document to show how to apply an > existing MANET protocol to LoWPANs (e.g., > AODV, OLSR, DYMO, etc)." > > So, my suggestion is as follows: > > Produce "Optimization of the Adhoc Routing Protocol > for 6lowpans" to apply an existing MANET Protocol > to LoWPANs. > > Thanks in advance. > > Daniel (Soohong Daniel Park) > Mobile Convergence Laboratory, SAMSUNG Electronics. > > ----- Original Message ----- > From: Schumacher Christian Peter Pii > To: 6lowpan@lists.ietf.org > Sent: Tuesday, March 07, 2006 8:09 PM > Subject: [6lowpan] new 6lowpan charter > > > Hi. > During the 6lowpan interim meeting in January, the working group > discussed possible topics for a future rechartering of 6lowpan. Based on > available information from that meeting I've compiled the following > text, which is an edited version of the scope present in the current > 6lowpan charter. Feedback is appreciated. > --- start of scope --- > Scope of 6lowpan: > Produce "Optimization of the Neighbor Discovery Protocol for 6lowpans" > to define how to apply the existing Neighbor Discovery protocol in a > 6lowpan. > Produce "IPv6 over Low Power WPAN Security Analysis" to define the > assumptions for a security model for 6lowpan. This includes analysis > of threats, identify types of devices and define the levels of trust > between these devices. > Produce "6lowpan Co-existence with other Networks" to define how to > co-exist with other networks. This includes analysis of how to survive > interference caused by IEEE 802.11 based networks, and investigate how > to > recognize and co-exist with other networks based on IEEE 802.15.4. > As such, the working group may also work on an informational document > to show how to apply an existing MANET protocol to LoWPANs (e.g., > AODV, OLSR, DYMO, etc). > The working group will reuse existing specifications whenever > reasonable and possible. > The working group will also serve as a venue for ongoing discussions > on other topics related to the more complete list outlined above. > Additional related milestones may be added in the future via a > rechartering operation. > Note: As may be obvious from its official name above, this particular > working group will not work on IPv4 over IEEE 802.15.4 specifications. > Given the limitations of the target devices, dual-stack deployments > are not practical. Because of its higher potential for header > compression, its support for the huge number of devices expected and > of cleanly built-in features such as address autoconfiguration, IPv6 > is the exclusive focus of the working group. > --- end of scope --- > Looking forward to receive your feedback. > Regards > Christian > PS: The original charter can be found at > http://www.ietf.org/html.charters/6lowpan-charter.html > > > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan > ------=_Part_9252_958299.1142903599571 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline

Hi Christian:
 
Thanks for  bringing up the charter discussion. My comments are i= n-line.
 
On 3/19/06, = Schumacher Christian Peter Pii <schumacher@danfoss.com> wrote:
Based on received feedback, I ha= ve a new suggestion for charter scope.

--- start of scope ---
Scope of 6lowpan:

Produce "Optimization of the Adhoc Routing Pr= otocol for 6lowpans"
to apply an existing MANET Protocol to LoWPANs= .
 
Agree.

Produce "Optimization of th= e Neighbor Discovery Protocol for 6lowpans"
to define how to apply = the existing Neighbor Discovery protocol in a
6lowpan.
 
Agree.

Produce "IPv6 over Low Powe= r WPAN Security Analysis" to define the
assumptions for a security = model for 6lowpan. This includes analysis
of threats, identify types of devices and define the levels of trustbetween these devices.
 
 
I think this document would be an informational document. In= addition to analysis of threats, it would be useful to discuss what level = of security to be applied in
different level of communications such as in application-layer, n= etwork layer or link-layer.
 

Produce "6lowpan Co-existen= ce with other Networks" to define how to
co-exist with other networ= ks. This includes analysis of how to survive
interference caused by IEEE 802.11 based networks, and investigate how<= br>to recognize and co-exist with other networks based on IEEE 802.15.4.
 
 
This might be another useful guideline to the community. But I'd think= , it as a
low priority item.
 
 
 

As such, the working group may a= lso work on informational documents for
service discovery, scalability o= f 6lowpan (routing and addressing),
 
 
I am not sure about importance of scalability in 6lowPan. I thought, w= e introduced
IPv6 to solve the scalability problem. If we use 64bit UID address sch= eme for
MAC address, then I don't see a scalability issue.
The 16bit MAC addresses could be treated as local addresses - same way= as
IPv6 treats link-local addresses - we can simply decide not to route t= hose
addresses outside local PAN and use 64bit unique address for global co= mmunication end-to-end. Adding 16bit address support for inter-pan com= munication will add much complexity.
 
Thanks,
-Samita
 

mobility issues, naming service = for mesh layer and gateway architecture.

The working group will reus= e existing specifications whenever
reasonable and possible.

The working group will also serve as a = venue for ongoing discussions
on other topics related to the more comple= te list outlined above.
Additional related milestones may be added in th= e future via a
rechartering operation.

Note: As may be obvious from its officia= l name above, this particular
working group will not work on IPv4 over I= EEE 802.15.4 specifications.
Given the limitations of the target devices= , dual-stack deployments
are not practical. Because of its higher potential for header
compre= ssion, its support for the huge number of devices expected and
of cleanl= y built-in features such as address autoconfiguration, IPv6
is the exclu= sive focus of the working group.

--- end of scope ---

Please provide feedback.

Regards=
Christian

PS: The original charter can be found at
http://www.ietf.or= g/html.charters/6lowpan-charter.html


-----Original Message-----
From: Soohong Daniel Park [ma= ilto:soohong.park@samsung.com]
Sent: 8. marts 2006 20:13
To: Schumacher Christian Peter Pii; 6lowpan@lists.ietf.org
Subject: Re: [6lowpan] new 6lowpan charter
new 6lowpan charterI believe 6lowpan adhoc routing protocol must beincluded into our rechartering more specific than
now. It is one of urg= ent task toward 6LoWPAN
Current text is just copy-and-paste from the
existing charter as fol= lows:

"As such, the working group may also work on an
inform= ational document to show how to apply an
existing MANET protocol to LoWP= ANs ( e.g.,
AODV, OLSR, DYMO, etc)."

So, my suggestion is as follo= ws:

Produce "Optimization of the Adhoc Routing Protocol
for = 6lowpans" to apply an existing MANET Protocol
to LoWPANs.

Thanks in advance.

Daniel (Soohong Daniel Park)
Mobile Convergenc= e Laboratory, SAMSUNG Electronics.

----- Original Message -----
F= rom: Schumacher Christian Peter Pii
To: 6lowpan@lists.ietf.org
Sent: Tuesday, March 07, 2006 8:09 PM
Subj= ect: [6lowpan] new 6lowpan charter


Hi.
During the 6lowpan int= erim meeting in January, the working group
discussed possible topics for= a future rechartering of 6lowpan. Based on
available information from that meeting I've compiled the following
= text, which is an edited version of the scope present in the current
6lo= wpan charter. Feedback is appreciated.
--- start of scope ---
Scope o= f 6lowpan:
Produce "Optimization of the Neighbor Discovery Protocol for 6lowp= ans"
to define how to apply the existing Neighbor Discovery protoco= l in a
6lowpan.
Produce "IPv6 over Low Power WPAN Security Analy= sis" to define the
assumptions for a security model for 6lowpan. This includes analysisof threats, identify types of devices and define the levels of trust
be= tween these devices.
Produce "6lowpan Co-existence with other Netwo= rks" to define how to
co-exist with other networks. This includes analysis of how to survive<= br>interference caused by IEEE 802.11 based networks, and investigate howto
recognize and co-exist with other networks based on IEEE 802.15.4 .
As such, the working group may also work on an informational document<= br>to show how to apply an existing MANET protocol to LoWPANs (e.g.,
AOD= V, OLSR, DYMO, etc).
The working group will reuse existing specification= s whenever
reasonable and possible.
The working group will also serve as a venu= e for ongoing discussions
on other topics related to the more complete l= ist outlined above.
Additional related milestones may be added in the fu= ture via a
rechartering operation.
Note: As may be obvious from its official na= me above, this particular
working group will not work on IPv4 over IEEE = 802.15.4 specifications.
Given the limitations of the target devices, du= al-stack deployments
are not practical. Because of its higher potential for header
compre= ssion, its support for the huge number of devices expected and
of cleanl= y built-in features such as address autoconfiguration, IPv6
is the exclu= sive focus of the working group.
--- end of scope ---
Looking forward to receive your feedback.
Re= gards
Christian
PS: The original charter can be found at
http://www.ietf= .org/html.charters/6lowpan-charter.html



_______________________________________________
6low= pan mailing list
6lowpan@ietf.org
https://www= 1.ietf.org/mailman/listinfo/6lowpan

_______________________________________________
6lowpan mail= ing list
6lowpan@ietf.org
https://www1.ietf.o= rg/mailman/listinfo/6lowpan

------=_Part_9252_958299.1142903599571-- --===============1336455532== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --===============1336455532==-- From 6lowpan-bounces@ietf.org Mon Mar 20 20:23:41 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLVb2-00062h-Sm; Mon, 20 Mar 2006 20:23:40 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLVb1-00062c-NW for 6lowpan@ietf.org; Mon, 20 Mar 2006 20:23:39 -0500 Received: from zproxy.gmail.com ([64.233.162.201]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLVb1-0006dc-Bi for 6lowpan@ietf.org; Mon, 20 Mar 2006 20:23:39 -0500 Received: by zproxy.gmail.com with SMTP id z3so1197113nzf for <6lowpan@ietf.org>; Mon, 20 Mar 2006 17:23:38 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=VbqTy1X/ZKWmDfNuSgmEuAzHPqGOtIgrUQETYbFTWCUQoFAJ1U9iH2BgO87KD1xivFd02iH8EN7uy97387SqbhkATSln0d27pG5bULYzrSUTkkqPtZTkSRlECt78AJhPzXWuM+NmU6MOJ9FGrjzEUBa8fu4SqKgO9fGScllKBrc= Received: by 10.65.114.6 with SMTP id r6mr470843qbm; Mon, 20 Mar 2006 17:23:38 -0800 (PST) Received: by 10.65.185.14 with HTTP; Mon, 20 Mar 2006 17:23:38 -0800 (PST) Message-ID: <43b91d370603201723jb6d1163t70c5b77dc4e4badf@mail.gmail.com> Date: Mon, 20 Mar 2006 17:23:38 -0800 From: "Samita Chakrabarti" To: "Carsten Bormann" Subject: Re: [6lowpan] friday's agenda In-Reply-To: <28603F54-9471-4C2F-B5F2-D07FBB22FE03@tzi.org> MIME-Version: 1.0 References: <49A38D2FE2C53946A57916AD6A1F00D782E7B1@DKDN01MX34.danfoss.net> <43b91d370603201641k73da9c25mb3b846473eee39d9@mail.gmail.com> <28603F54-9471-4C2F-B5F2-D07FBB22FE03@tzi.org> X-Spam-Score: 0.1 (/) X-Scan-Signature: f66b12316365a3fe519e75911daf28a8 Cc: 6lowpan@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: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1566814278==" Errors-To: 6lowpan-bounces@ietf.org --===============1566814278== Content-Type: multipart/alternative; boundary="----=_Part_9436_6527561.1142904218407" ------=_Part_9436_6527561.1142904218407 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi Carsten: > > I wonder if we have time for 6lowpan-ND draft update presentation > > this time? As per interim meeting discussion, we have submitted > > a new draft. Would like to receive wg input on that. > > Sure; this would be under the heading "new work" of the provisional > agenda. Thanks! I've put you down there (assuming you are referring to draft- > chakrabarti-6lowpan-ipv6-nd-01.txt). I was not sure whether I'd be attending this IETF; Erik Nordmark kindly agreed to present this time as well. Yes, I was referring to the chakrabarti-6lowpan-ipv6-nd-01.txt. We still need to allocate time, what's your time requirement? > (Quick update + discussion time?) My guestimate would be 15 - 20 minutes. Working on the slides. > > > Thanks, -Samita ------=_Part_9436_6527561.1142904218407 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
 
Hi Carsten:
 
> I wonder if we have time fo= r 6lowpan-ND draft update presentation
> this time?  As per= interim meeting discussion, we have submitted
> a new draft.  Would like to receive wg input on that.
Sure; this would be under the heading "new work" of the prov= isional
agenda.
 
 
Thanks!

I've put you down there (assumin= g you are referring to draft-
chakrabarti-6lowpan-ipv6-nd-01.txt).
 
 
I was not sure whether I'd be attending this IETF; Erik Nordmark kindl= y agreed
to present this time as well. Yes, I was referring to the chakrabarti-= 6lowpan-ipv6-nd-01.txt.

We still need to allocate time, = what's your time requirement?
(Quick update + discussion time?)
 
 
My guestimate would be 15 - 20 minutes.  Working on the slides.
 


 
Thanks,
-Samita
 
------=_Part_9436_6527561.1142904218407-- --===============1566814278== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --===============1566814278==-- From 6lowpan-bounces@ietf.org Mon Mar 20 23:58:45 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLYxB-0006sw-32; Mon, 20 Mar 2006 23:58:45 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLYx9-0006sr-Kb for 6lowpan@ietf.org; Mon, 20 Mar 2006 23:58:43 -0500 Received: from zproxy.gmail.com ([64.233.162.205]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLYx8-00052r-Bf for 6lowpan@ietf.org; Mon, 20 Mar 2006 23:58:43 -0500 Received: by zproxy.gmail.com with SMTP id i1so1404700nzh for <6lowpan@ietf.org>; Mon, 20 Mar 2006 20:58:42 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=OuQElP3dOaUyV85PqqE/P/IgPFI8TebovuxDeHg/QiB7wZc0ZmDwIWmJx+tKYT+buZM/KNIxP9aTxPKdyocU6/As5+zdiXvDuhCVxRQUPwa5AyQXGF2BBeWiGe15gKnT1VOXPddaMCUN50Fz9VM5YkmZrv7+AzOxoF5kw9fBOzg= Received: by 10.36.221.37 with SMTP id t37mr2369684nzg; Mon, 20 Mar 2006 20:58:41 -0800 (PST) Received: by 10.37.18.77 with HTTP; Mon, 20 Mar 2006 20:58:41 -0800 (PST) Message-ID: <374005f30603202058r503deb87qdd15316839992e7c@mail.gmail.com> Date: Mon, 20 Mar 2006 20:58:41 -0800 From: "Ian Chakeres" To: "Soohong Daniel Park" Subject: Re: [6lowpan] LOAD Updated In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <007901c640b8$1403eec0$45706f0a@daniellaptop> X-Spam-Score: 0.0 (/) X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30 Cc: 6lowpan@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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org I have several comments about the LOAD draft. I will enumerate them below. I still believe that DYMO is more appropriate for 6lowpan, it should require few if any modifications to run in 6lowpan networks. Ian Chakeres FYI: I am in Dallas. Comments: As I mentioned at the last IETF during the meeting, AODV and LOAD will create routing loops if sequence numbers are not included and considered correctly. Therefore, I think that sequence numbers MUST be used - 16 bits are probably enough. That is the length we are currently considering for DYMO. As I also mentioned during the last IETF, the interaction between a QoS metric and distance vector routing is unclear. This topic is still a research topic and not ready for protocol engineering. The lifetime definition in the routing table entry should be changed to something like AODV or DYMO, that is it should be the time the route expires; as opposed to the current text, which states it is the time before expiration/deletion. How do links break? Are links monitored? How do route entries timeout? Do you update the route timeout on transmission or reception of packets? Additional discussion on using link quality to ignore weak control messages and on using the "weak" link indicator in RREQ should be included. I think if you expect to have unidirectional links (after the above mentioned changes) you should probably specify a blacklisting mechanism. RERR for low battery and routing cost not supported will result in broadcast storms. I suggest they be removed. If nodes need to discourage their routing of packets on behalf of others (being on the chosen route), I suggest a mechanism in one of my research papers that I think is appropriate and flexible. """Ian D. Chakeres and Elizabeth M. Belding-Royer. "Transparent Influence of Path Selection in Heterogeneous Ad hoc Networks." Proceedings of the 15th IEEE International Symposium on Personal, Indoor and Mobile Radio Communications (PIMRC), Barcelona, Spain, September 2004.""" I don't think the load format requires an IANA port since it will be operating at L2. On 3/6/06, Soohong Daniel Park wrote: > Here is an official release: > http://www.ietf.org/internet-drafts/draft-daniel-6lowpan-load-adhoc-routi= ng-02.txt > > > On 3/6/06, Soohong Daniel Park wrote: > > Folks - LOAD (6LoWPAN Ad Hoc On-Demand Distance Vector Routing) > > has been updated and you can use the following links before ietf reposi= tory. > > > > http://daniel.vsix.net/ietf/6lowpan/draft-daniel-6lowpan-load-adhoc-rou= ting-02.txt > > > > Diff from 01 version: > > http://daniel.vsix.net/ietf/6lowpan/draft-daniel-6lowpan-load-adhoc-rou= ting-02_diff.htm > > > > Any comments are highly welcome, > > > > See you in Dallas soon. > > > > Daniel (Soohong Daniel Park) > > Mobile Convergence Laboratory, SAMSUNG Electronics. > > > > _______________________________________________ > > 6lowpan mailing list > > 6lowpan@ietf.org > > https://www1.ietf.org/mailman/listinfo/6lowpan > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan > _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Tue Mar 21 00:13:16 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLZBB-0006xu-KV; Tue, 21 Mar 2006 00:13:13 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLZB9-0006xp-Q2 for 6lowpan@lists.ietf.org; Tue, 21 Mar 2006 00:13:12 -0500 Received: from zproxy.gmail.com ([64.233.162.192]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLZB8-0005iK-EQ for 6lowpan@lists.ietf.org; Tue, 21 Mar 2006 00:13:11 -0500 Received: by zproxy.gmail.com with SMTP id z6so1635872nzd for <6lowpan@lists.ietf.org>; Mon, 20 Mar 2006 21:13:10 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=SnGIG1tTtagtELn169k+baZbJdys2eVLtyTC63pr4q2hyxbyLq7C06bY0F1paiYWVdI/v1XM/jlAJv8I1Npcfg6v9dn+zpPsWJQeTtZ5zQlFblIpafp9svnJJheSRnLUD9elKh4oL7ClT4mN27geBvzk800HAuFKneSw6vIXB6g= Received: by 10.36.221.21 with SMTP id t21mr3708726nzg; Mon, 20 Mar 2006 21:13:10 -0800 (PST) Received: by 10.37.18.77 with HTTP; Mon, 20 Mar 2006 21:13:09 -0800 (PST) Message-ID: <374005f30603202113m3c008c97t2437156f4aa1152e@mail.gmail.com> Date: Mon, 20 Mar 2006 21:13:09 -0800 From: "Ian Chakeres" To: "Schumacher Christian Peter Pii" Subject: Re: [6lowpan] new 6lowpan charter In-Reply-To: <49A38D2FE2C53946A57916AD6A1F00D782E7A3@DKDN01MX34.danfoss.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <49A38D2FE2C53946A57916AD6A1F00D782E7A3@DKDN01MX34.danfoss.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: 225414c974e0d6437992164e91287a51 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org Comments - inline. On 3/19/06, Schumacher Christian Peter Pii wrote: > Based on received feedback, I have a new suggestion for charter scope. > > --- start of scope --- > > Scope of 6lowpan: > > Produce "Optimization of the Adhoc Routing Protocol for 6lowpans" > to apply an existing MANET Protocol to LoWPANs. I do not think the MANET protocols should be re-engineered in 6lowpan. I believe that a L2 implementation of minimal DYMO can fulfil 6lowpans requirements. I think packet optimizations are acceptable to explore, but protocol behavior should not be changed. I think that the charter should state exactly what type of "optimizations" are to be explored. > Produce "Optimization of the Neighbor Discovery Protocol for 6lowpans" > to define how to apply the existing Neighbor Discovery protocol in a > 6lowpan. Again, I think we should reuse IPv6 ND or use a MANET hello protocol (OLSRv2 or SMF neighborhood discovery seem suitable). Again, packet formats could be optimized, but the protocol behavior should not. > Produce "IPv6 over Low Power WPAN Security Analysis" to define the > assumptions for a security model for 6lowpan. This includes analysis > of threats, identify types of devices and define the levels of trust > between these devices. > > Produce "6lowpan Co-existence with other Networks" to define how to > co-exist with other networks. This includes analysis of how to survive > interference caused by IEEE 802.11 based networks, and investigate how > to recognize and co-exist with other networks based on IEEE 802.15.4. > > As such, the working group may also work on informational documents for > service discovery, scalability of 6lowpan (routing and addressing), > mobility issues, naming service for mesh layer and gateway architecture. > > The working group will reuse existing specifications whenever > reasonable and possible. > > The working group will also serve as a venue for ongoing discussions > on other topics related to the more complete list outlined above. > Additional related milestones may be added in the future via a > rechartering operation. > > Note: As may be obvious from its official name above, this particular > working group will not work on IPv4 over IEEE 802.15.4 specifications. > Given the limitations of the target devices, dual-stack deployments > are not practical. Because of its higher potential for header > compression, its support for the huge number of devices expected and > of cleanly built-in features such as address autoconfiguration, IPv6 > is the exclusive focus of the working group. > > --- end of scope --- > > Please provide feedback. > > Regards > Christian > > PS: The original charter can be found at > http://www.ietf.org/html.charters/6lowpan-charter.html > > > -----Original Message----- > From: Soohong Daniel Park [mailto:soohong.park@samsung.com] > Sent: 8. marts 2006 20:13 > To: Schumacher Christian Peter Pii; 6lowpan@lists.ietf.org > Subject: Re: [6lowpan] new 6lowpan charter > > new 6lowpan charterI believe 6lowpan adhoc routing protocol must be > included into our rechartering more specific than > now. It is one of urgent task toward 6LoWPAN > Current text is just copy-and-paste from the > existing charter as follows: > > "As such, the working group may also work on an > informational document to show how to apply an > existing MANET protocol to LoWPANs (e.g., > AODV, OLSR, DYMO, etc)." > > So, my suggestion is as follows: > > Produce "Optimization of the Adhoc Routing Protocol > for 6lowpans" to apply an existing MANET Protocol > to LoWPANs. > > Thanks in advance. > > Daniel (Soohong Daniel Park) > Mobile Convergence Laboratory, SAMSUNG Electronics. > > ----- Original Message ----- > From: Schumacher Christian Peter Pii > To: 6lowpan@lists.ietf.org > Sent: Tuesday, March 07, 2006 8:09 PM > Subject: [6lowpan] new 6lowpan charter > > > Hi. > During the 6lowpan interim meeting in January, the working group > discussed possible topics for a future rechartering of 6lowpan. Based on > available information from that meeting I've compiled the following > text, which is an edited version of the scope present in the current > 6lowpan charter. Feedback is appreciated. > --- start of scope --- > Scope of 6lowpan: > Produce "Optimization of the Neighbor Discovery Protocol for 6lowpans" > to define how to apply the existing Neighbor Discovery protocol in a > 6lowpan. > Produce "IPv6 over Low Power WPAN Security Analysis" to define the > assumptions for a security model for 6lowpan. This includes analysis > of threats, identify types of devices and define the levels of trust > between these devices. > Produce "6lowpan Co-existence with other Networks" to define how to > co-exist with other networks. This includes analysis of how to survive > interference caused by IEEE 802.11 based networks, and investigate how > to > recognize and co-exist with other networks based on IEEE 802.15.4. > As such, the working group may also work on an informational document > to show how to apply an existing MANET protocol to LoWPANs (e.g., > AODV, OLSR, DYMO, etc). > The working group will reuse existing specifications whenever > reasonable and possible. > The working group will also serve as a venue for ongoing discussions > on other topics related to the more complete list outlined above. > Additional related milestones may be added in the future via a > rechartering operation. > Note: As may be obvious from its official name above, this particular > working group will not work on IPv4 over IEEE 802.15.4 specifications. > Given the limitations of the target devices, dual-stack deployments > are not practical. Because of its higher potential for header > compression, its support for the huge number of devices expected and > of cleanly built-in features such as address autoconfiguration, IPv6 > is the exclusive focus of the working group. > --- end of scope --- > Looking forward to receive your feedback. > Regards > Christian > PS: The original charter can be found at > http://www.ietf.org/html.charters/6lowpan-charter.html > > > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan > _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Tue Mar 21 08:30:02 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLgvx-0004r0-JU; Tue, 21 Mar 2006 08:30:01 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLgvw-0004mE-2x for 6lowpan@lists.ietf.org; Tue, 21 Mar 2006 08:30:00 -0500 Received: from mailx.danfoss.com ([193.162.34.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLgvu-0007rs-IM for 6lowpan@lists.ietf.org; Tue, 21 Mar 2006 08:30:00 -0500 Received: from DKDN04MX62.dkdn04.danfoss.net ([10.6.2.62]) by mailx.danfoss.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 21 Mar 2006 14:29:57 +0100 Received: from dkdn01mx21.danfoss.net ([10.12.129.21]) by DKDN04MX62.dkdn04.danfoss.net with InterScan Message Security Suite; Tue, 21 Mar 2006 14:29:57 +0100 Received: from dkdn01mx25.danfoss.net ([10.12.129.25]) by dkdn01mx21.danfoss.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 21 Mar 2006 14:29:56 +0100 Received: from DKDN01MX34.danfoss.net ([10.12.128.14]) by dkdn01mx25.danfoss.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 21 Mar 2006 14:29:56 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [6lowpan] new 6lowpan charter Date: Tue, 21 Mar 2006 14:29:49 +0100 Message-ID: <49A38D2FE2C53946A57916AD6A1F00D782E931@DKDN01MX34.danfoss.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [6lowpan] new 6lowpan charter Thread-Index: AcZMpiZttv5C2mvfRnqxhUZ+JaeWzAARR34A From: "Schumacher Christian Peter Pii" To: "Ian Chakeres" , "Samita Chakrabarti" X-OriginalArrivalTime: 21 Mar 2006 13:29:56.0654 (UTC) FILETIME=[8B686CE0:01C64CEB] X-Spam-Score: 0.0 (/) X-Scan-Signature: 48472a944c87678fcfe8db15ffecdfff 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org Thanks for your feedback. The current version, which has been altered quite a bit, of the charter for discussion can be found at http://6lowpan.tzi.org/recharter Regards Christian -----Original Message----- From: Ian Chakeres [mailto:ian.chakeres@gmail.com]=20 Sent: 20. marts 2006 23:13 To: Schumacher Christian Peter Pii Cc: 6lowpan Subject: Re: [6lowpan] new 6lowpan charter Comments - inline. On 3/19/06, Schumacher Christian Peter Pii wrote: > Based on received feedback, I have a new suggestion for charter scope. > > --- start of scope --- > > Scope of 6lowpan: > > Produce "Optimization of the Adhoc Routing Protocol for 6lowpans" > to apply an existing MANET Protocol to LoWPANs. I do not think the MANET protocols should be re-engineered in 6lowpan. I believe that a L2 implementation of minimal DYMO can fulfil 6lowpans requirements. I think packet optimizations are acceptable to explore, but protocol behavior should not be changed. I think that the charter should state exactly what type of "optimizations" are to be explored. > Produce "Optimization of the Neighbor Discovery Protocol for 6lowpans" > to define how to apply the existing Neighbor Discovery protocol in a > 6lowpan. Again, I think we should reuse IPv6 ND or use a MANET hello protocol (OLSRv2 or SMF neighborhood discovery seem suitable). Again, packet formats could be optimized, but the protocol behavior should not. > Produce "IPv6 over Low Power WPAN Security Analysis" to define the > assumptions for a security model for 6lowpan. This includes analysis > of threats, identify types of devices and define the levels of trust > between these devices. > > Produce "6lowpan Co-existence with other Networks" to define how to > co-exist with other networks. This includes analysis of how to survive > interference caused by IEEE 802.11 based networks, and investigate how > to recognize and co-exist with other networks based on IEEE 802.15.4. > > As such, the working group may also work on informational documents for > service discovery, scalability of 6lowpan (routing and addressing), > mobility issues, naming service for mesh layer and gateway architecture. > > The working group will reuse existing specifications whenever > reasonable and possible. > > The working group will also serve as a venue for ongoing discussions > on other topics related to the more complete list outlined above. > Additional related milestones may be added in the future via a > rechartering operation. > > Note: As may be obvious from its official name above, this particular > working group will not work on IPv4 over IEEE 802.15.4 specifications. > Given the limitations of the target devices, dual-stack deployments > are not practical. Because of its higher potential for header > compression, its support for the huge number of devices expected and > of cleanly built-in features such as address autoconfiguration, IPv6 > is the exclusive focus of the working group. > > --- end of scope --- > > Please provide feedback. > > Regards > Christian > > PS: The original charter can be found at > http://www.ietf.org/html.charters/6lowpan-charter.html > > > -----Original Message----- > From: Soohong Daniel Park [mailto:soohong.park@samsung.com] > Sent: 8. marts 2006 20:13 > To: Schumacher Christian Peter Pii; 6lowpan@lists.ietf.org > Subject: Re: [6lowpan] new 6lowpan charter > > new 6lowpan charterI believe 6lowpan adhoc routing protocol must be > included into our rechartering more specific than > now. It is one of urgent task toward 6LoWPAN > Current text is just copy-and-paste from the > existing charter as follows: > > "As such, the working group may also work on an > informational document to show how to apply an > existing MANET protocol to LoWPANs (e.g., > AODV, OLSR, DYMO, etc)." > > So, my suggestion is as follows: > > Produce "Optimization of the Adhoc Routing Protocol > for 6lowpans" to apply an existing MANET Protocol > to LoWPANs. > > Thanks in advance. > > Daniel (Soohong Daniel Park) > Mobile Convergence Laboratory, SAMSUNG Electronics. > > ----- Original Message ----- > From: Schumacher Christian Peter Pii > To: 6lowpan@lists.ietf.org > Sent: Tuesday, March 07, 2006 8:09 PM > Subject: [6lowpan] new 6lowpan charter > > > Hi. > During the 6lowpan interim meeting in January, the working group > discussed possible topics for a future rechartering of 6lowpan. Based on > available information from that meeting I've compiled the following > text, which is an edited version of the scope present in the current > 6lowpan charter. Feedback is appreciated. > --- start of scope --- > Scope of 6lowpan: > Produce "Optimization of the Neighbor Discovery Protocol for 6lowpans" > to define how to apply the existing Neighbor Discovery protocol in a > 6lowpan. > Produce "IPv6 over Low Power WPAN Security Analysis" to define the > assumptions for a security model for 6lowpan. This includes analysis > of threats, identify types of devices and define the levels of trust > between these devices. > Produce "6lowpan Co-existence with other Networks" to define how to > co-exist with other networks. This includes analysis of how to survive > interference caused by IEEE 802.11 based networks, and investigate how > to > recognize and co-exist with other networks based on IEEE 802.15.4. > As such, the working group may also work on an informational document > to show how to apply an existing MANET protocol to LoWPANs (e.g., > AODV, OLSR, DYMO, etc). > The working group will reuse existing specifications whenever > reasonable and possible. > The working group will also serve as a venue for ongoing discussions > on other topics related to the more complete list outlined above. > Additional related milestones may be added in the future via a > rechartering operation. > Note: As may be obvious from its official name above, this particular > working group will not work on IPv4 over IEEE 802.15.4 specifications. > Given the limitations of the target devices, dual-stack deployments > are not practical. Because of its higher potential for header > compression, its support for the huge number of devices expected and > of cleanly built-in features such as address autoconfiguration, IPv6 > is the exclusive focus of the working group. > --- end of scope --- > Looking forward to receive your feedback. > Regards > Christian > PS: The original charter can be found at > http://www.ietf.org/html.charters/6lowpan-charter.html > > > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan > _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Tue Mar 21 08:44:46 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLhAE-0002wQ-3D; Tue, 21 Mar 2006 08:44:46 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLhAC-0002wL-H4 for 6lowpan@lists.ietf.org; Tue, 21 Mar 2006 08:44:44 -0500 Received: from mailhost.informatik.uni-bremen.de ([134.102.201.18] helo=informatik.uni-bremen.de) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLhAB-0008F7-4i for 6lowpan@lists.ietf.org; Tue, 21 Mar 2006 08:44:44 -0500 Received: from [127.0.0.1] (maildrop.informatik.uni-bremen.de [134.102.201.19]) by informatik.uni-bremen.de (8.13.4/8.13.2) with ESMTP id k2LDiM9m028740; Tue, 21 Mar 2006 14:44:24 +0100 (CET) In-Reply-To: <374005f30603202113m3c008c97t2437156f4aa1152e@mail.gmail.com> References: <49A38D2FE2C53946A57916AD6A1F00D782E7A3@DKDN01MX34.danfoss.net> <374005f30603202113m3c008c97t2437156f4aa1152e@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v746.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <2FBF073D-1808-4247-B373-7F2AFE7D914C@tzi.org> Content-Transfer-Encoding: 7bit From: Carsten Bormann Subject: Re: [6lowpan] new 6lowpan charter Date: Tue, 21 Mar 2006 07:44:21 -0600 To: "Ian Chakeres" X-Mailer: Apple Mail (2.746.3) X-Virus-Scanned: by amavisd-new X-Spam-Score: 0.0 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Cc: Carsten Bormann , 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org Hi Ian, > I do not think the MANET protocols should be re-engineered in 6lowpan. > I believe that a L2 implementation of minimal DYMO can fulfil 6lowpans > requirements. > > I think packet optimizations are acceptable to explore, but protocol > behavior should not be changed. > > I think that the charter should state exactly what type of > "optimizations" are to be explored. Good point. "Optimization" is highly ambiguous. No, we don't want to create another protocol; in other environments, what we are trying to do would have been called "profiling", i.e., defining a subset that is interoperable in the specific domain. >> Produce "Optimization of the Neighbor Discovery Protocol for >> 6lowpans" >> to define how to apply the existing Neighbor Discovery protocol in a >> 6lowpan. > > Again, I think we should reuse IPv6 ND or use a MANET hello protocol > (OLSRv2 or SMF neighborhood discovery seem suitable). Again, packet > formats could be optimized, but the protocol behavior should not. Here I'm not so sure. I wouldn't want to rule out new protocol development in this space. What makes you confident that either ND as is or the MANET protocols will fit the bill? Gruesse, Carsten _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Tue Mar 21 11:23:57 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLjeG-0004Az-Q7; Tue, 21 Mar 2006 11:23:56 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLjeF-0004Au-PA for 6lowpan@lists.ietf.org; Tue, 21 Mar 2006 11:23:55 -0500 Received: from mailout1.samsung.com ([203.254.224.24]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLjeE-00064B-0Z for 6lowpan@lists.ietf.org; Tue, 21 Mar 2006 11:23:55 -0500 Received: from ep_mmp2 (mailout1.samsung.com [203.254.224.24]) by mailout1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0IWH004AGK7RI8@mailout1.samsung.com> for 6lowpan@lists.ietf.org; Wed, 22 Mar 2006 01:23:51 +0900 (KST) Received: from daniellaptop ([124.235.139.6]) by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTPA id <0IWH00LZJK7P5V@mmp2.samsung.com> for 6lowpan@lists.ietf.org; Wed, 22 Mar 2006 01:23:51 +0900 (KST) Date: Tue, 21 Mar 2006 10:23:57 -0600 From: Soohong Daniel Park Subject: Re: [6lowpan] new 6lowpan charter To: Ian Chakeres , Schumacher Christian Peter Pii Message-id: <012301c64d03$dbf0a660$f6828182@daniellaptop> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Outlook Express 6.00.2900.2180 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <49A38D2FE2C53946A57916AD6A1F00D782E7A3@DKDN01MX34.danfoss.net> <374005f30603202113m3c008c97t2437156f4aa1152e@mail.gmail.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org >> Produce "Optimization of the Adhoc Routing Protocol for 6lowpans" >> to apply an existing MANET Protocol to LoWPANs. > >I do not think the MANET protocols should be re-engineered in 6lowpan. >I believe that a L2 implementation of minimal DYMO can fulfil 6lowpans >requirements. *minimal* is what Optimization means. Daniel (Soohong Daniel Park) Mobile Convergence Laboratory, SAMSUNG Electronics. _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Tue Mar 21 11:40:23 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLjuA-0005gE-Dh; Tue, 21 Mar 2006 11:40:22 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLju9-0005g9-BX for 6lowpan@ietf.org; Tue, 21 Mar 2006 11:40:21 -0500 Received: from zproxy.gmail.com ([64.233.162.192]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLju7-0006rN-W2 for 6lowpan@ietf.org; Tue, 21 Mar 2006 11:40:21 -0500 Received: by zproxy.gmail.com with SMTP id l1so1502640nzf for <6lowpan@ietf.org>; Tue, 21 Mar 2006 08:40:19 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=aKbhr8mQY665A4fA1hzXcJs9yFzKkvPiIIl8SsXnCKkgLGkjjcUpQzge4Y4octLPuUSQs9JvdyK3xgqgT8uUMy5zRd2H/Tiq6147ONK7ULzmWOBvNX6bsrM47JoOXj6ijCxsJAvd58IVHd9PNV87Hcn/ddSQlSqY/B3WeogOI90= Received: by 10.65.234.5 with SMTP id l5mr429599qbr; Tue, 21 Mar 2006 08:40:18 -0800 (PST) Received: by 10.64.203.5 with HTTP; Tue, 21 Mar 2006 08:40:18 -0800 (PST) Message-ID: Date: Wed, 22 Mar 2006 01:40:18 +0900 From: "Ki-Hyung Kim" To: "Carsten Bormann" Subject: Re: [6lowpan] friday's agenda In-Reply-To: MIME-Version: 1.0 References: <49A38D2FE2C53946A57916AD6A1F00D782E7B1@DKDN01MX34.danfoss.net> X-Spam-Score: 0.6 (/) X-Scan-Signature: 200d029292fbb60d25b263122ced50fc Cc: 6lowpan@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: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0257161080==" Errors-To: 6lowpan-bounces@ietf.org --===============0257161080== Content-Type: multipart/alternative; boundary="----=_Part_12436_32178160.1142959218172" ------=_Part_12436_32178160.1142959218172 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Geoff and Carsten, I would like to ask the time slots for our proposals in the 6lowpan WG agenda. Initially, I have asked 30-minute demonstration of our testbed. Could I refine the request as follows: (If you think that the allocatable time to us is not enough, I could re-arrange the items in the priority-based) 1) Optimization of the Adhoc Routing Protocol for 6lowpans 15 minutes I would like to present the updated version of LOAD document and DYMO-low about the received comments. 2) Scalability of 6LoWPAN (routing and addressing issues) 15 minutes In this slot, I would like to raise the issue of the scalability with regar= d to the 6lowpan deliverables. I would like to mention the meaning of the scalability in that IPv6 is scalable, but the table-based routing (eg. ad hoc routing) is not. 3) Service Discovery Protocol for 6LoWPAN and Interoperability of 6LoWPAN 15 minutes 4) Demonstration of the testbed (www.6ylowpan.net) 15 minutes On 3/21/06, Carsten Bormann wrote: > > On Mar 19 2006, at 17:01, Christian Schumacher wrote: > > Carsten and Geoff, what is the status of the official agenda for > > 6lowpan WG meeting on friday? > Well, I think that status is called "very very late" in English... > > An initial draft of the agenda is at > > http://6lowpan.tzi.org/6lowpan_20at_20IETF_2065 > > Please also follow the "recharter" link and send comments on the > draft charter to this list. > There are names of possible contributors in the proposed charter -- > these are not meant to be exclusive, and we would like to hear which > ones of the potential charter items each of you wants to work on. > > Apart from the Friday WG meeting, we plan to have a 6lowpan dinner on > Thursday (after the plenary) -- please RSVP to Christian if you want > to participate. > > Gruesse, Carsten > > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan > -- __ Ki-Hyung Kim Associate Professor Division of Information and Computer Eng., Ajou University, Suwon, Korea 442-749 Tel:+82-31-219-2433, http://ilab.ajou.ac.kr ------=_Part_12436_32178160.1142959218172 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Geoff and Carsten,
 
I would like to ask the time slots for our proposals in the 6lowp= an WG agenda.
Initially, I have asked 30-minute demonstration of our testbed.
Could I refine the request as follows: (If you think that the all= ocatable time to us is not enough, I could re-arrange the items i= n the priority-based)
 
1) Optimization of the Adhoc Routing Protocol for 6lowpans
15 minutes
I would like to present the updated version of LOAD document and = DYMO-low about the received comments.
 
2) Scalability of 6LoWPAN (routing and addressing issues)
15 minutes
In this slot, I would like to raise the issue of the scalability&= nbsp;with regard to the 6lowpan deliverables.  I would like&= nbsp;to mention the meaning of the scalability in that IPv6 is sc= alable, but the table-based routing (eg. ad hoc routing) is not.
 
3) Service Discovery Protocol for 6LoWPAN and Interoperability of 6LoW= PAN
15 minutes
 
4) Demonstration of the testbed (w= ww.6ylowpan.net)
15 minutes
 
 
 


 
On 3/21/06, = Carsten Bormann <cabo@tzi.org>= ; wrote:
On Mar 19 2006, at 17:01, Christ= ian Schumacher wrote:
> Carsten and Geoff, what is the status of the = official agenda for
> 6lowpan WG meeting on friday?
Well, I think that status is call= ed "very very late" in English...

An initial draft of the = agenda is at

       http://6lowpan.tzi.org/6lowpan_20at_20IETF_2065

Please also foll= ow the "recharter" link and send comments on the
draft charter= to this list.
There are names of possible contributors in the proposed = charter --
these are not meant to be exclusive, and we would like to hear whichones of the potential charter items each of you wants to work on.

A= part from the Friday WG meeting, we plan to have a 6lowpan dinner on
Thursday (after the plenary) -- please RSVP to Christian if you want
to = participate.

Gruesse, Carsten


___________________________= ____________________
6lowpan mailing list
6lowpan@ietf.org
https://www1.ietf.org/mailman/listinfo/6lowpan
=



--
__
Ki-Hyung Kim
Associate Prof= essor
Division of Information and Computer Eng.,
Ajou University, Suwon, = Korea 442-749
Tel:+82-31-219-2433, ht= tp://ilab.ajou.ac.kr
------=_Part_12436_32178160.1142959218172-- --===============0257161080== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --===============0257161080==-- From 6lowpan-bounces@ietf.org Tue Mar 21 12:01:40 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLkEb-00043s-Lp; Tue, 21 Mar 2006 12:01:29 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLkEa-00041j-0S for 6lowpan@ietf.org; Tue, 21 Mar 2006 12:01:28 -0500 Received: from grab.coslabs.com ([199.233.92.34]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLkEW-00083y-I1 for 6lowpan@ietf.org; Tue, 21 Mar 2006 12:01:27 -0500 Received: from [10.1.139.11] ([207.40.99.3]) by grab.coslabs.com (8.12.10/8.12.10) with ESMTP id k2LH1IJr007234; Tue, 21 Mar 2006 10:01:19 -0700 (MST) Subject: Re: [6lowpan] friday's agenda From: Geoff Mulligan To: Ki-Hyung Kim In-Reply-To: References: <49A38D2FE2C53946A57916AD6A1F00D782E7B1@DKDN01MX34.danfoss.net> Content-Type: text/plain Date: Tue, 21 Mar 2006 09:50:55 -0700 Message-Id: <1142959855.25121.8.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab Cc: Carsten Bormann , 6lowpan@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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org I will be at dinner. geoff On Tue, 2006-03-21 at 08:01 +0900, Ki-Hyung Kim wrote: > I will participate the dinner on thursday. > > > > On 3/21/06, Carsten Bormann wrote: > On Mar 19 2006, at 17:01, Christian Schumacher wrote: > > Carsten and Geoff, what is the status of the official agenda > for > > 6lowpan WG meeting on friday? > Well, I think that status is called "very very late" in > English... > > An initial draft of the agenda is at > > http://6lowpan.tzi.org/6lowpan_20at_20IETF_2065 > > Please also follow the "recharter" link and send comments on > the > draft charter to this list. > There are names of possible contributors in the proposed > charter -- > these are not meant to be exclusive, and we would like to hear > which > ones of the potential charter items each of you wants to work > on. > > Apart from the Friday WG meeting, we plan to have a 6lowpan > dinner on > Thursday (after the plenary) -- please RSVP to Christian if > you want > to participate. > > Gruesse, Carsten > > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan > > > > -- > __ > Ki-Hyung Kim > Associate Professor > Division of Information and Computer Eng., > Ajou University, Suwon, Korea 442-749 > Tel:+82-31-219-2433, http://ilab.ajou.ac.kr > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Tue Mar 21 14:48:26 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLmq9-0003St-E7; Tue, 21 Mar 2006 14:48:25 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLmq7-0003R2-Ul for 6lowpan@ietf.org; Tue, 21 Mar 2006 14:48:23 -0500 Received: from smtp101.plus.mail.re2.yahoo.com ([206.190.53.26]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FLmq6-0005r4-LT for 6lowpan@ietf.org; Tue, 21 Mar 2006 14:48:23 -0500 Received: (qmail 13374 invoked from network); 21 Mar 2006 19:48:22 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:Message-ID:Date:From:Reply-To:User-Agent:X-Accept-Language:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=rIJ5pt+L0jwQJN/2ADA/mtfOEM9vMe5ZWK6TKW11TjVRHkBEBGqmeWyEcvz7uW6ipT7M+SNKQupv0INosmD0Jpnspwzng9SW7JaO1j4DfNT2TffseE0uTQvmEbi0Ke4hA/xLa/0beL6UE8vRVGLqnzG554V+r2tqB5KY9oSR5Ho= ; Received: from unknown (HELO ?130.129.131.79?) (behcetsarikaya@130.129.131.79 with plain) by smtp101.plus.mail.re2.yahoo.com with SMTP; 21 Mar 2006 19:48:22 -0000 Message-ID: <4420587F.6040309@yahoo.com> Date: Tue, 21 Mar 2006 11:48:15 -0800 From: Behcet Sarikaya User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Carsten Bormann Subject: Re: [6lowpan] friday's agenda References: <49A38D2FE2C53946A57916AD6A1F00D782E7B1@DKDN01MX34.danfoss.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Cc: 6lowpan@ietf.org X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sarikaya@ieee.org List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org Hi Carsten, I would like a 5 minute slot to present my draft on serial forwarding. Thanks. --behcet Carsten Bormann wrote: > On Mar 19 2006, at 17:01, Christian Schumacher wrote: > >> Carsten and Geoff, what is the status of the official agenda for >> 6lowpan WG meeting on friday? > > Well, I think that status is called "very very late" in English... > > An initial draft of the agenda is at > > http://6lowpan.tzi.org/6lowpan_20at_20IETF_2065 > > Please also follow the "recharter" link and send comments on the > draft charter to this list. > There are names of possible contributors in the proposed charter -- > these are not meant to be exclusive, and we would like to hear which > ones of the potential charter items each of you wants to work on. > > Apart from the Friday WG meeting, we plan to have a 6lowpan dinner on > Thursday (after the plenary) -- please RSVP to Christian if you want > to participate. > > Gruesse, Carsten > > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan > > _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Tue Mar 21 17:18:11 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLpB2-0003qS-El; Tue, 21 Mar 2006 17:18:08 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLpB1-0003qI-Bd for 6lowpan@ietf.org; Tue, 21 Mar 2006 17:18:07 -0500 Received: from mailhost.informatik.uni-bremen.de ([134.102.201.18] helo=informatik.uni-bremen.de) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLpAz-0006XF-UI for 6lowpan@ietf.org; Tue, 21 Mar 2006 17:18:07 -0500 Received: from [127.0.0.1] (maildrop.informatik.uni-bremen.de [134.102.201.19]) by informatik.uni-bremen.de (8.13.4/8.13.2) with ESMTP id k2LMI0Go021432; Tue, 21 Mar 2006 23:18:01 +0100 (CET) In-Reply-To: References: <49A38D2FE2C53946A57916AD6A1F00D782E7B1@DKDN01MX34.danfoss.net> Mime-Version: 1.0 (Apple Message framework v746.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Carsten Bormann Subject: Re: [6lowpan] friday's agenda Date: Tue, 21 Mar 2006 16:17:58 -0600 To: Ki-Hyung Kim X-Mailer: Apple Mail (2.746.3) X-Virus-Scanned: by amavisd-new X-Spam-Score: 0.0 (/) X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8 Cc: Carsten Bormann , 6lowpan@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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org Hi Kim, > 1) Optimization of the Adhoc Routing Protocol for 6lowpans > 15 minutes > I would like to present the updated version of LOAD document and > DYMO-low about the received comments. The view of the people present at the Interim was that this subject is very relevant. When you say "updated", I assume that this is about what has changed since the Interim? Can we split this into: 1) discussion about the way forward (in the rechartering segment), and 2) technical specifics. For 1, in particular, we need to understand what the specific "optimizations" are that we want to apply to these protocols -- why can't we use the MANET protocols as they are and what is the best way to achieve long-term sustainability in a world where both the underlying L2 network and the MANET base protocols still are changing. > 2) Scalability of 6LoWPAN (routing and addressing issues) > 15 minutes > In this slot, I would like to raise the issue of the scalability > with regard to the 6lowpan deliverables. I would like to mention > the meaning of the scalability in that IPv6 is scalable, but the > table-based routing (eg. ad hoc routing) is not. One of the results of the Interim was that we didn't see this as one of the priority items to be picked up by the WG. Do you have any new considerations that would lead the people present at the Interim to reconsider this? > 3) Service Discovery Protocol for 6LoWPAN and Interoperability of > 6LoWPAN > 15 minutes As a result of the Interim, we said we wanted to discuss service discovery in the context of application configuration and installation/commissioning. So, for the rechartering segment, I would be interested in seeing thoughts on how to achieve this. At the Interim, there was little that we thought the WG needed to pick up from the Interoperability presentation. Again, we should focus on updates since the Interim, and on the aspects that will influence the charter discussion. > 4) Demonstration of the testbed (www.6ylowpan.net) > 15 minutes Can we do this outside the WG meeting (e.g., from 08:40 to 08:55 or so)? I'm very interested in seeing this, but I don't see us spending WG meeting time on a testbed demonstration. Gruesse, Carsten _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Tue Mar 21 17:22:20 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLpF6-0006sD-TM; Tue, 21 Mar 2006 17:22:20 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLpF5-0006ry-5D for 6lowpan@ietf.org; Tue, 21 Mar 2006 17:22:19 -0500 Received: from mailhost.informatik.uni-bremen.de ([134.102.201.18] helo=informatik.uni-bremen.de) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLpF3-0006oc-Ny for 6lowpan@ietf.org; Tue, 21 Mar 2006 17:22:19 -0500 Received: from [127.0.0.1] (maildrop.informatik.uni-bremen.de [134.102.201.19]) by informatik.uni-bremen.de (8.13.4/8.13.2) with ESMTP id k2LMMClX022790; Tue, 21 Mar 2006 23:22:13 +0100 (CET) In-Reply-To: <4420587F.6040309@yahoo.com> References: <49A38D2FE2C53946A57916AD6A1F00D782E7B1@DKDN01MX34.danfoss.net> <4420587F.6040309@yahoo.com> Mime-Version: 1.0 (Apple Message framework v746.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Carsten Bormann Subject: Re: [6lowpan] friday's agenda Date: Tue, 21 Mar 2006 16:22:10 -0600 To: sarikaya@ieee.org X-Mailer: Apple Mail (2.746.3) X-Virus-Scanned: by amavisd-new X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Cc: Carsten Bormann , 6lowpan@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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org Hi Behcet, > I would like a 5 minute slot to present my draft on serial > forwarding. I assume this is about draft-sarikaya-6lowpan-forwarding-00.txt It would seem this is a bit out of (both current and future) scope, but then I have seen some quite strong requirements in this space in some real-world 6lowpan application environments. I've put this segment at the end of the "new work" section. See you on Friday! Gruesse, Carsten _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Tue Mar 21 18:13:02 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLq29-0005J2-Gj; Tue, 21 Mar 2006 18:13:01 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLq28-0005Ix-8k for 6lowpan@lists.ietf.org; Tue, 21 Mar 2006 18:13:00 -0500 Received: from zproxy.gmail.com ([64.233.162.206]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLq26-0000GW-S2 for 6lowpan@lists.ietf.org; Tue, 21 Mar 2006 18:13:00 -0500 Received: by zproxy.gmail.com with SMTP id n1so7371nzf for <6lowpan@lists.ietf.org>; Tue, 21 Mar 2006 15:12:58 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=c7scnZDYDsBubs0W3pOYGI7phZ7p8du2+dcPpLkQ7qpNZ/UQ9UbekgL0ulTRFu7k5bLvyKmkjjBCFda4vo1KhliqT5yazie+WX4oSTYWWA7Hto7UfCElXIEVwCN/V7ZI8yPQpQGiWFMZ6tkXtmNSeV6VeOEOH6ysp6RnRFc97iI= Received: by 10.36.252.68 with SMTP id z68mr250590nzh; Tue, 21 Mar 2006 15:12:58 -0800 (PST) Received: by 10.37.18.77 with HTTP; Tue, 21 Mar 2006 15:12:58 -0800 (PST) Message-ID: <374005f30603211512o1fb7938dy8113f2eb20bbb54e@mail.gmail.com> Date: Tue, 21 Mar 2006 15:12:58 -0800 From: "Ian Chakeres" To: "Carsten Bormann" Subject: Re: [6lowpan] new 6lowpan charter In-Reply-To: <2FBF073D-1808-4247-B373-7F2AFE7D914C@tzi.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <49A38D2FE2C53946A57916AD6A1F00D782E7A3@DKDN01MX34.danfoss.net> <374005f30603202113m3c008c97t2437156f4aa1152e@mail.gmail.com> <2FBF073D-1808-4247-B373-7F2AFE7D914C@tzi.org> X-Spam-Score: 0.0 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org Comments in line. On 3/21/06, Carsten Bormann wrote: > Hi Ian, > > > I do not think the MANET protocols should be re-engineered in 6lowpan. > > I believe that a L2 implementation of minimal DYMO can fulfil 6lowpans > > requirements. > > > > I think packet optimizations are acceptable to explore, but protocol > > behavior should not be changed. > > > > I think that the charter should state exactly what type of > > "optimizations" are to be explored. > > Good point. "Optimization" is highly ambiguous. > No, we don't want to create another protocol; in other environments, > what we are trying to do would have been called "profiling", i.e., > defining a subset that is interoperable in the specific domain. > > >> Produce "Optimization of the Neighbor Discovery Protocol for > >> 6lowpans" > >> to define how to apply the existing Neighbor Discovery protocol in a > >> 6lowpan. > > > > Again, I think we should reuse IPv6 ND or use a MANET hello protocol > > (OLSRv2 or SMF neighborhood discovery seem suitable). Again, packet > > formats could be optimized, but the protocol behavior should not. > > Here I'm not so sure. I wouldn't want to rule out new protocol > development in this space. > What makes you confident that either ND as is or the MANET protocols > will fit the bill? I am not an expert in ND or 6lowpan, but my intuition says that an existing algorithm can be harnessed to accomplish ND or neighborhood discovery in 6lowpan with little modification, except for the packet format of course. Ian Chakeres _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Tue Mar 21 18:52:35 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLqeR-0005WN-3I; Tue, 21 Mar 2006 18:52:35 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLqeP-0005WH-Qu for 6lowpan@ietf.org; Tue, 21 Mar 2006 18:52:33 -0500 Received: from mga01.intel.com ([192.55.52.88] helo=fmsmga101-1.fm.intel.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLqeO-0001ye-AT for 6lowpan@ietf.org; Tue, 21 Mar 2006 18:52:33 -0500 Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga101-1.fm.intel.com with ESMTP; 21 Mar 2006 15:52:31 -0800 Received: from orsmsx331.jf.intel.com (HELO orsmsx331.amr.corp.intel.com) ([192.168.65.56]) by fmsmga001.fm.intel.com with ESMTP; 21 Mar 2006 15:52:31 -0800 X-IronPort-AV: i="4.03,116,1141632000"; d="scan'208"; a="14905298:sNHT23817220" Received: from orsmsx405.amr.corp.intel.com ([192.168.65.46]) by orsmsx331.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 21 Mar 2006 15:52:30 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [6lowpan] friday's agenda Date: Tue, 21 Mar 2006 15:52:28 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [6lowpan] friday's agenda Thread-Index: AcZMYO5qdzMbu7CySracDKNSWBwBDAA4Hasw From: "Shah, Rahul C" To: "Carsten Bormann" , "Schumacher Christian Peter Pii" X-OriginalArrivalTime: 21 Mar 2006 23:52:30.0086 (UTC) FILETIME=[83C9D260:01C64D42] X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 Cc: 6lowpan@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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org Carsten/Geoff, >From the perspective of a new member to the group, I was wondering why the "Gateway architecture between 6LoWPAN and IPv6 networks" is not being given priority in the current rechartering... I would think this is important since no 6LoWPAN network is going to be a standalone network. Additionally, I would suggest that the group also consider a gateway architecture between 6LoWPAN and an IPv4 network, due to the preponderance of IPv4 in the short term. I am not suggesting that any flavor of IPv4 be used inside the 6LoWPAN, but it would be useful to consider connecting to such a network.=20 What does the group have to say? Thanks, Rahul Shah. -----Original Message----- From: Carsten Bormann [mailto:cabo@tzi.org]=20 Sent: Monday, March 20, 2006 12:56 PM To: Schumacher Christian Peter Pii Cc: Carsten Bormann; 6lowpan@ietf.org Subject: Re: [6lowpan] friday's agenda On Mar 19 2006, at 17:01, Christian Schumacher wrote: > Carsten and Geoff, what is the status of the official agenda for =20 > 6lowpan WG meeting on friday? Well, I think that status is called "very very late" in English... An initial draft of the agenda is at http://6lowpan.tzi.org/6lowpan_20at_20IETF_2065 Please also follow the "recharter" link and send comments on the =20 draft charter to this list. There are names of possible contributors in the proposed charter -- =20 these are not meant to be exclusive, and we would like to hear which =20 ones of the potential charter items each of you wants to work on. Apart from the Friday WG meeting, we plan to have a 6lowpan dinner on =20 Thursday (after the plenary) -- please RSVP to Christian if you want =20 to participate. Gruesse, Carsten _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Tue Mar 21 19:41:11 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLrPR-0005Bg-Fp; Tue, 21 Mar 2006 19:41:09 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLrPQ-00053i-J7 for 6lowpan@ietf.org; Tue, 21 Mar 2006 19:41:08 -0500 Received: from mailhost.informatik.uni-bremen.de ([134.102.201.18] helo=informatik.uni-bremen.de) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLrPP-00048h-6M for 6lowpan@ietf.org; Tue, 21 Mar 2006 19:41:08 -0500 Received: from [127.0.0.1] (maildrop.informatik.uni-bremen.de [134.102.201.19]) by informatik.uni-bremen.de (8.13.4/8.13.2) with ESMTP id k2M0exgW015257; Wed, 22 Mar 2006 01:41:00 +0100 (CET) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v746.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <52905402-62E7-45BA-81A4-44EEA61F50DA@tzi.org> Content-Transfer-Encoding: 7bit From: Carsten Bormann Subject: Re: [6lowpan] friday's agenda Date: Tue, 21 Mar 2006 18:40:58 -0600 To: "Shah, Rahul C" X-Mailer: Apple Mail (2.746.3) X-Virus-Scanned: by amavisd-new X-Spam-Score: 0.0 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Cc: Carsten Bormann , 6lowpan@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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org On Mar 21 2006, at 17:52 , Shah, Rahul C wrote: > Carsten/Geoff, > >> From the perspective of a new member to the group, I was wondering >> why > the "Gateway architecture between 6LoWPAN and IPv6 networks" is not > being given priority in the current rechartering... I would think this > is important since no 6LoWPAN network is going to be a standalone > network. When this question came up in the past, my recollection of the consensus was that no work was necessary as this gateway is doing the same thing as any other IPv6 router in the IPv6 architecture. Do you have requirements on this gateway that go beyond an IPv6 router? > Additionally, I would suggest that the group also consider a gateway > architecture between 6LoWPAN and an IPv4 network, due to the > preponderance of IPv4 in the short term. I am not suggesting that any > flavor of IPv4 be used inside the 6LoWPAN, but it would be useful to > consider connecting to such a network. This is a good point; from my personal point of view, this is just another case of an IPv4/IPv6 transition scenario, and the issues are not different from any other of these. Again, I'd like to hear about specific requirements of 6lowpans. Gruesse, Carsten _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Tue Mar 21 20:24:48 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLs5e-0000Ri-5e; Tue, 21 Mar 2006 20:24:46 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLs5c-0000Rd-Op for 6lowpan@lists.ietf.org; Tue, 21 Mar 2006 20:24:44 -0500 Received: from mailx.danfoss.com ([193.162.34.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLs5b-0005N7-Fa for 6lowpan@lists.ietf.org; Tue, 21 Mar 2006 20:24:44 -0500 Received: from DKDN04MX62.dkdn04.danfoss.net ([10.6.2.62]) by mailx.danfoss.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 22 Mar 2006 02:24:42 +0100 Received: from dkdn01mx21.danfoss.net ([10.12.129.21]) by DKDN04MX62.dkdn04.danfoss.net with InterScan Message Security Suite; Wed, 22 Mar 2006 02:24:42 +0100 Received: from DKDN01MX34.danfoss.net ([10.12.128.14]) by dkdn01mx21.danfoss.net with Microsoft SMTPSVC(6.0.3790.1830); Wed, 22 Mar 2006 02:24:42 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 22 Mar 2006 02:24:31 +0100 Message-ID: <49A38D2FE2C53946A57916AD6A1F00D782E985@DKDN01MX34.danfoss.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: thursday dinner Thread-Index: AcZNT17BvKqEjZg1SQyIH0NvjVJcIw== From: "Schumacher Christian Peter Pii" To: "6lowpan" <6lowpan@lists.ietf.org> X-OriginalArrivalTime: 22 Mar 2006 01:24:42.0439 (UTC) FILETIME=[6553E570:01C64D4F] X-Spam-Score: 0.0 (/) X-Scan-Signature: 00e94c813bef7832af255170dca19e36 Cc: Subject: [6lowpan] thursday dinner 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1387983972==" Errors-To: 6lowpan-bounces@ietf.org This is a multi-part message in MIME format. --===============1387983972== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C64D4F.64F16D75" This is a multi-part message in MIME format. ------_=_NextPart_001_01C64D4F.64F16D75 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable As mentioned by Carsten , the 6lowpan WG will join up for a dinner on Thursday after the plenary. We'll probably go for one of the restaurants at the Hilton Anatole.=20 The following people have RSVP'ed that they will attend: Carsten Bormann Christian Schumacher Erik Nordmark Geoff Mulligan Ki-Hyung Kim Samita Chakrabarti Please respond to this mail, if you would like to attend. Regards Christian ------_=_NextPart_001_01C64D4F.64F16D75 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable thursday dinner

As mentioned by Carsten , the 6lowpan = WG will join up for a dinner on Thursday after the plenary. We'll = probably go for one of the restaurants at the Hilton Anatole. =

The following people have RSVP'ed that = they will attend:

Carsten Bormann
Christian Schumacher
Erik Nordmark
Geoff Mulligan
Ki-Hyung Kim
Samita Chakrabarti

Please respond to this mail, if you = would like to attend.

Regards
Christian

------_=_NextPart_001_01C64D4F.64F16D75-- --===============1387983972== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --===============1387983972==-- From 6lowpan-bounces@ietf.org Tue Mar 21 22:31:13 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLu3z-0002Ir-MY; Tue, 21 Mar 2006 22:31:11 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLu3x-0002Im-Ql for 6lowpan@ietf.org; Tue, 21 Mar 2006 22:31:09 -0500 Received: from mail4.hitachi.co.jp ([133.145.228.5]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLu3v-0001Lj-St for 6lowpan@ietf.org; Tue, 21 Mar 2006 22:31:09 -0500 Received: from mlsv5.hitachi.co.jp (unknown [133.145.228.16]) by mail4.hitachi.co.jp (Postfix) with ESMTP id 9051B33CCD for <6lowpan@ietf.org>; Wed, 22 Mar 2006 12:31:06 +0900 (JST) Received: from mfilter-s3.hitachi.co.jp by mlsv5.hitachi.co.jp (8.12.10/8.12.10) id k2M3V6wp017671; Wed, 22 Mar 2006 12:31:06 +0900 Received: from vshuts2.hitachi.co.jp (unverified) by mfilter-s3.hitachi.co.jp (Content Technologies SMTPRS 4.3.17) with SMTP id ; Wed, 22 Mar 2006 12:31:06 +0900 Received: from hsdlgw92.sdl.hitachi.co.jp ([133.144.7.20]) by vshuts2.hitachi.co.jp with SMTP id M2006032212310429300 ; Wed, 22 Mar 2006 12:31:06 +0900 Received: from vgate2.sdl.hitachi.co.jp by hsdlgw92.sdl.hitachi.co.jp (8.9.3/3.7W01100113) id MAA08443; Wed, 22 Mar 2006 12:31:04 +0900 Received: from maila.sdl.hitachi.co.jp ([133.144.14.196]) by vgate2.sdl.hitachi.co.jp (SAVSMTP 3.1.1.32) with SMTP id M2006032212310412503 ; Wed, 22 Mar 2006 12:31:04 +0900 Received: from IGARASHINOTE ([158.213.205.29]) by maila.sdl.hitachi.co.jp (8.13.1/3.7W04031011) with ESMTP id k2M3V0Ji029986; Wed, 22 Mar 2006 12:31:02 +0900 From: "IGARASHI Yuichi" To: "'Shah, Rahul C'" , "'Carsten Bormann'" , "'Schumacher Christian Peter Pii'" Subject: RE: [6lowpan] friday's agenda Date: Wed, 22 Mar 2006 12:31:11 +0900 Message-ID: <000401c64d61$134eb6d0$fd4b050c@IGARASHINOTE> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcZMYO5qdzMbu7CySracDKNSWBwBDAA4HaswAAfmDiA= X-Spam-Score: 0.0 (/) X-Scan-Signature: 73734d43604d52d23b3eba644a169745 Cc: 6lowpan@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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org To the group from a new member The follow are only my personal opinion: I also agree with Rahul's opinion. I think it would be useful to consider connecting to external network for applications, and that gateway architecture is important subject. But, I think that issues inside 6LoWPAN should be solved first. For example, compression header format of TCP/ICMPv6, scalability of 6LoWPAN, and correspondence to IPv6 ready logo, etc. Because most important purpose of 6LoWPAN is to transmit IPv6 packets efficiently over IEEE 802.15.4, I think. I would like to hear about perspective for the future (order of the subject which should be solved) in WG. Thanks, Yuichi IGARASHI -----Original Message----- From: Shah, Rahul C [mailto:rahul.c.shah@intel.com] Sent: Wednesday, March 22, 2006 8:52 AM To: Carsten Bormann; Schumacher Christian Peter Pii Cc: 6lowpan@ietf.org Subject: RE: [6lowpan] friday's agenda Carsten/Geoff, >From the perspective of a new member to the group, I was wondering why the "Gateway architecture between 6LoWPAN and IPv6 networks" is not being given priority in the current rechartering... I would think this is important since no 6LoWPAN network is going to be a standalone network. Additionally, I would suggest that the group also consider a gateway architecture between 6LoWPAN and an IPv4 network, due to the preponderance of IPv4 in the short term. I am not suggesting that any flavor of IPv4 be used inside the 6LoWPAN, but it would be useful to consider connecting to such a network. What does the group have to say? Thanks, Rahul Shah. -----Original Message----- From: Carsten Bormann [mailto:cabo@tzi.org] Sent: Monday, March 20, 2006 12:56 PM To: Schumacher Christian Peter Pii Cc: Carsten Bormann; 6lowpan@ietf.org Subject: Re: [6lowpan] friday's agenda On Mar 19 2006, at 17:01, Christian Schumacher wrote: > Carsten and Geoff, what is the status of the official agenda for > 6lowpan WG meeting on friday? Well, I think that status is called "very very late" in English... An initial draft of the agenda is at http://6lowpan.tzi.org/6lowpan_20at_20IETF_2065 Please also follow the "recharter" link and send comments on the draft charter to this list. There are names of possible contributors in the proposed charter -- these are not meant to be exclusive, and we would like to hear which ones of the potential charter items each of you wants to work on. Apart from the Friday WG meeting, we plan to have a 6lowpan dinner on Thursday (after the plenary) -- please RSVP to Christian if you want to participate. Gruesse, Carsten _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Wed Mar 22 10:05:51 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FM4uD-0000g5-Ru; Wed, 22 Mar 2006 10:05:49 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FM4uC-0000fz-Ue for 6lowpan@lists.ietf.org; Wed, 22 Mar 2006 10:05:48 -0500 Received: from mailx.danfoss.com ([193.162.34.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FM4u9-0002dS-8A for 6lowpan@lists.ietf.org; Wed, 22 Mar 2006 10:05:48 -0500 Received: from DKDN04MX62.dkdn04.danfoss.net ([10.6.2.62]) by mailx.danfoss.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 22 Mar 2006 16:05:44 +0100 Received: from dkdn01mx21.danfoss.net ([10.12.129.21]) by DKDN04MX62.dkdn04.danfoss.net with InterScan Message Security Suite; Wed, 22 Mar 2006 16:05:44 +0100 Received: from DKDN01MX34.danfoss.net ([10.12.128.14]) by dkdn01mx21.danfoss.net with Microsoft SMTPSVC(6.0.3790.1830); Wed, 22 Mar 2006 16:05:43 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 22 Mar 2006 16:05:37 +0100 Message-ID: <49A38D2FE2C53946A57916AD6A1F00D782EA1B@DKDN01MX34.danfoss.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: thursday dinner update Thread-Index: AcZNT17BvKqEjZg1SQyIH0NvjVJcIwAcg8vQ From: "Schumacher Christian Peter Pii" To: "6lowpan" <6lowpan@lists.ietf.org> X-OriginalArrivalTime: 22 Mar 2006 15:05:43.0869 (UTC) FILETIME=[176D96D0:01C64DC2] X-Spam-Score: 0.0 (/) X-Scan-Signature: 21be852dc93f0971708678c18d38c096 Cc: Subject: [6lowpan] FW: thursday dinner update 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0405121949==" Errors-To: 6lowpan-bounces@ietf.org This is a multi-part message in MIME format. --===============0405121949== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C64DC2.16FB3394" This is a multi-part message in MIME format. ------_=_NextPart_001_01C64DC2.16FB3394 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi again. The list of attendees for thursdays dinner (after plenary) are currently: Behcet Sarikaya Brian Minard Carsten Bormann Christian Schumacher Erik Nordmark Geoff Mulligan Ki-Hyung Kim Samita Chakrabarti If you're not on the list and would like to join the 6lowpan WG for dinner thursday evening, please send me a mail ( if you've already sent a mail, but you're not on the list, please send it again as I might have missed it. ) I will sent out the name of the restaurant (at Hilton Anatole) before lunch tomorrow. Regards Christian > ______________________________________________=20 > From: Schumacher Christian Peter Pii =20 > Sent: 21. marts 2006 19:25 > To: 6lowpan > Subject: thursday dinner >=20 > As mentioned by Carsten , the 6lowpan WG will join up for a dinner on > Thursday after the plenary. We'll probably go for one of the > restaurants at the Hilton Anatole.=20 >=20 > The following people have RSVP'ed that they will attend: >=20 > Carsten Bormann > Christian Schumacher > Erik Nordmark > Geoff Mulligan > Ki-Hyung Kim > Samita Chakrabarti >=20 > Please respond to this mail, if you would like to attend. >=20 > Regards > Christian ------_=_NextPart_001_01C64DC2.16FB3394 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable FW: thursday dinner update

Hi again.

The list of attendees for thursdays = dinner (after plenary) are currently:

Behcet Sarikaya
Brian Minard
Carsten Bormann
Christian Schumacher
Erik Nordmark
Geoff Mulligan
Ki-Hyung Kim
Samita Chakrabarti

If you're not on the list and would = like to join the 6lowpan WG for dinner thursday evening, please send me = a mail
( if you've already sent a mail, but = you're not on the list, please send it again as I might have missed it. = )

I will sent out the name of the = restaurant (at Hilton Anatole) before lunch tomorrow.

Regards
Christian

______________________________________________
From:   Schumacher Christian Peter Pii 
Sent:   21. marts 2006 19:25
To:     6lowpan
Subject:       = thursday dinner

As mentioned by Carsten , the 6lowpan = WG will join up for a dinner on Thursday after the plenary. We'll = probably go for one of the restaurants at the Hilton Anatole. =

The following people have RSVP'ed that = they will attend:

Carsten Bormann
Christian Schumacher
Erik Nordmark
Geoff Mulligan
Ki-Hyung Kim
Samita Chakrabarti

Please respond to this mail, if you = would like to attend.

Regards
Christian

------_=_NextPart_001_01C64DC2.16FB3394-- --===============0405121949== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --===============0405121949==-- From 6lowpan-bounces@ietf.org Wed Mar 22 11:43:18 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FM6QP-0006em-9U; Wed, 22 Mar 2006 11:43:09 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FM6QN-0006eh-Qw for 6lowpan@ietf.org; Wed, 22 Mar 2006 11:43:07 -0500 Received: from mailout3.samsung.com ([203.254.224.33]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FM6QM-0007M2-8A for 6lowpan@ietf.org; Wed, 22 Mar 2006 11:43:07 -0500 Received: from ep_mmp2 (mailout3.samsung.com [203.254.224.33]) by mailout3.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0IWJ006YTFRSZT@mailout3.samsung.com> for 6lowpan@ietf.org; Thu, 23 Mar 2006 01:43:04 +0900 (KST) Received: from daniellaptop ([124.235.139.2]) by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTPA id <0IWJ005R7FRNND@mmp2.samsung.com> for 6lowpan@ietf.org; Thu, 23 Mar 2006 01:43:03 +0900 (KST) Date: Wed, 22 Mar 2006 10:43:10 -0600 From: Soohong Daniel Park Subject: Re: [6lowpan] friday's agenda To: IGARASHI Yuichi , "'Shah, Rahul C'" , 'Carsten Bormann' , 'Schumacher Christian Peter Pii' Message-id: <05c601c64dcf$b65f5d70$f6828182@daniellaptop> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Outlook Express 6.00.2900.2180 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <000401c64d61$134eb6d0$fd4b050c@IGARASHINOTE> X-Spam-Score: 0.0 (/) X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8 Cc: 6lowpan@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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org I am so confusing of why TCP over 6LoWPAN is on the table of discussion. So far, I can't see any requirement in terms of TCP usage over 6LoWPAN. It seems very hard to be implemented on the 6LoWPAN from the engineering perspective. So, we need to clarify TCP requirement before jumping into the TCP discussion. To me I am a bit negative. Thanks, Daniel (Soohong Daniel Park) Mobile Convergence Laboratory, SAMSUNG Electronics. ----- Original Message ----- From: "IGARASHI Yuichi" To: "'Shah, Rahul C'" ; "'Carsten Bormann'" ; "'Schumacher Christian Peter Pii'" Cc: <6lowpan@ietf.org> Sent: Tuesday, March 21, 2006 9:31 PM Subject: RE: [6lowpan] friday's agenda > To the group from a new member > > The follow are only my personal opinion: > I also agree with Rahul's opinion. I think it would be useful to consider > connecting to external network for applications, and that gateway > architecture is important subject. > But, I think that issues inside 6LoWPAN should be solved first. For example, > compression header format of TCP/ICMPv6, scalability of 6LoWPAN, and > correspondence to IPv6 ready logo, etc. Because most important purpose of > 6LoWPAN is to transmit IPv6 packets efficiently over IEEE 802.15.4, I think. > > > I would like to hear about perspective for the future (order of the subject > which should be solved) in WG. > > Thanks, > Yuichi IGARASHI > > -----Original Message----- > From: Shah, Rahul C [mailto:rahul.c.shah@intel.com] > Sent: Wednesday, March 22, 2006 8:52 AM > To: Carsten Bormann; Schumacher Christian Peter Pii > Cc: 6lowpan@ietf.org > Subject: RE: [6lowpan] friday's agenda > > Carsten/Geoff, > >>From the perspective of a new member to the group, I was wondering why > the "Gateway architecture between 6LoWPAN and IPv6 networks" is not > being given priority in the current rechartering... I would think this > is important since no 6LoWPAN network is going to be a standalone > network. > > Additionally, I would suggest that the group also consider a gateway > architecture between 6LoWPAN and an IPv4 network, due to the > preponderance of IPv4 in the short term. I am not suggesting that any > flavor of IPv4 be used inside the 6LoWPAN, but it would be useful to > consider connecting to such a network. > > What does the group have to say? > > Thanks, > Rahul Shah. > > > > -----Original Message----- > From: Carsten Bormann [mailto:cabo@tzi.org] > Sent: Monday, March 20, 2006 12:56 PM > To: Schumacher Christian Peter Pii > Cc: Carsten Bormann; 6lowpan@ietf.org > Subject: Re: [6lowpan] friday's agenda > > On Mar 19 2006, at 17:01, Christian Schumacher wrote: >> Carsten and Geoff, what is the status of the official agenda for >> 6lowpan WG meeting on friday? > Well, I think that status is called "very very late" in English... > > An initial draft of the agenda is at > > http://6lowpan.tzi.org/6lowpan_20at_20IETF_2065 > > Please also follow the "recharter" link and send comments on the > draft charter to this list. > There are names of possible contributors in the proposed charter -- > these are not meant to be exclusive, and we would like to hear which > ones of the potential charter items each of you wants to work on. > > Apart from the Friday WG meeting, we plan to have a 6lowpan dinner on > Thursday (after the plenary) -- please RSVP to Christian if you want > to participate. > > Gruesse, Carsten > > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan > > > > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan > > _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Wed Mar 22 15:58:06 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMAP8-0004N6-A4; Wed, 22 Mar 2006 15:58:06 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMAP7-0004MB-1M for 6lowpan@ietf.org; Wed, 22 Mar 2006 15:58:05 -0500 Received: from pproxy.gmail.com ([64.233.166.183]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FMAP5-000299-KW for 6lowpan@ietf.org; Wed, 22 Mar 2006 15:58:05 -0500 Received: by pproxy.gmail.com with SMTP id m51so232109pye for <6lowpan@ietf.org>; Wed, 22 Mar 2006 12:58:03 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=LK5eLNikrqdeoB+38BEUwuo5o+tGjPATfrrpt7IayW9uNh1dBpdB59HCBHhvu4VmgNKPEGRSV2DQY3rmE0esNGhTyYQPAPmi/CN2BHONOpRZIfNIkmsKOHt1oF/SZHqEYoz2JeS0Y5RnB9908E1zvLh+OdX4qxz7CdBYa2EhYyg= Received: by 10.65.44.13 with SMTP id w13mr1027401qbj; Wed, 22 Mar 2006 12:58:02 -0800 (PST) Received: by 10.64.203.5 with HTTP; Wed, 22 Mar 2006 12:58:02 -0800 (PST) Message-ID: Date: Thu, 23 Mar 2006 05:58:02 +0900 From: "Ki-Hyung Kim" To: "Carsten Bormann" Subject: Re: [6lowpan] friday's agenda In-Reply-To: MIME-Version: 1.0 References: <49A38D2FE2C53946A57916AD6A1F00D782E7B1@DKDN01MX34.danfoss.net> X-Spam-Score: 1.0 (+) X-Scan-Signature: f2984bf50fb52a9e56055f779793d783 Cc: 6lowpan@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: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1918984333==" Errors-To: 6lowpan-bounces@ietf.org --===============1918984333== Content-Type: multipart/alternative; boundary="----=_Part_7847_4932955.1143061082434" ------=_Part_7847_4932955.1143061082434 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi Carsten, My answers are in line. On 3/22/06, Carsten Bormann wrote: > Hi Kim, > > > 1) Optimization of the Adhoc Routing Protocol for 6lowpans > > 15 minutes > > I would like to present the updated version of LOAD document and > > DYMO-low about the received comments. > > The view of the people present at the Interim was that this subject > is very relevant. > When you say "updated", I assume that this is about what has changed > since the Interim? Your assumption is correct. > Can we split this into: > 1) discussion about the way forward (in the rechartering segment), and > 2) technical specifics. > For 1, in particular, we need to understand what the specific > "optimizations" are that we want to apply to these protocols -- why > can't we use the MANET protocols as they are and what is the best way > to achieve long-term sustainability in a world where both the > underlying L2 network and the MANET base protocols still are changing. That's a good idea. I will try to split the presentation. > > 2) Scalability of 6LoWPAN (routing and addressing issues) > > 15 minutes > > In this slot, I would like to raise the issue of the scalability > > with regard to the 6lowpan deliverables. I would like to mention > > the meaning of the scalability in that IPv6 is scalable, but the > > table-based routing (eg. ad hoc routing) is not. > > One of the results of the Interim was that we didn't see this as one > of the priority items to be picked up by the WG. > Do you have any new considerations that would lead the people present > at the Interim to reconsider this? I think that the explanation of this issue at the interim is not enough because of the shortage of time, and we didn't even have a chance to discuss the necessity of this issue. I still believe that this issue is very urgent and should be included in the rechartering items on this round. That's why I want to ask you of the chance to explain the necessity and importance of this issue in this WG session. > > 3) Service Discovery Protocol for 6LoWPAN and Interoperability of > > 6LoWPAN > > 15 minutes > > As a result of the Interim, we said we wanted to discuss service > discovery in the context of application configuration and > installation/commissioning. > So, for the rechartering segment, I would be interested in seeing > thoughts on how to achieve this. > > At the Interim, there was little that we thought the WG needed to > pick up from the Interoperability presentation. > Again, we should focus on updates since the Interim, and on the > aspects that will influence the charter discussion. > > > 4) Demonstration of the testbed (www.6ylowpan.net) > > 15 minutes > > Can we do this outside the WG meeting (e.g., from 08:40 to 08:55 or so)? > I'm very interested in seeing this, but I don't see us spending WG > meeting time on a testbed demonstration. I think the demonstration of the testbed could be short (just 5 minutes might be OK for the presentation of the architecture and implementation of 6lowpan). If you still think that it might be better to do the demonstration before the WG, it is OK. Gruesse, Carsten > > -- __ Ki-Hyung Kim Associate Professor Division of Information and Computer Eng., Ajou University, Suwon, Korea 442-749 Tel:+82-31-219-2433, http://ilab.ajou.ac.kr ------=_Part_7847_4932955.1143061082434 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Hi Carsten,

My answers are in line.
 
On 3/22/06, = Carsten Bormann <cabo@tzi.org>= ; wrote:
Hi Kim,

> 1) Optimizat= ion of the Adhoc Routing Protocol for 6lowpans
> 15 minutes
> I= would like to present the updated version of LOAD document and
> DYMO-low about the received comments.

The view of the peopl= e present at the Interim was that this subject
is very relevant.
When= you say "updated", I assume that this is about what has changed
since the Interim?
 
Your assumption is correct.

 
Can we split this into:
1) di= scussion about the way forward (in the rechartering segment), and
2) tec= hnical specifics.
For 1, in particular, we need to understand what the specific
"= optimizations" are that we want to apply to these protocols -- why
= can't we use the MANET protocols as they are and what is the best way
to achieve long-term sustainability in a world where both the
underlying= L2 network and the MANET base protocols still are changing.
 
That's a good idea. I will try to split the presentation.

 
>  2) Scalability o= f 6LoWPAN (routing and addressing issues)
> 15 minutes
> In thi= s slot, I would like to raise the issue of the scalability
> with regard to the 6lowpan deliverables.  I would like t= o mention
> the meaning of the scalability in that IPv6 is scalable, = but the
> table-based routing (eg. ad hoc routing) is not.

One= of the results of the Interim was that we didn't see this as one
of the priority items to be picked up by the WG.
Do you have any new= considerations that would lead the people present
at the Interim to rec= onsider this?
 
I think that the explanation of this issue at the interim is not enoug= h because of the shortage of time, and we didn't even have a chance to disc= uss the necessity of this issue.  I still believe that this issue= is very urgent and should be included in the rechartering items on this ro= und. That's why I want to ask you of the chance to explain the necessity an= d importance of this issue in this WG session. 

 
>  3) Service Disco= very Protocol for 6LoWPAN and Interoperability of
> 6LoWPAN
> 1= 5 minutes

As a result of the Interim, we said we wanted to discuss servicediscovery in the context of application configuration and
installation/= commissioning.
So, for the rechartering segment, I would be interested i= n seeing
thoughts on how to achieve this.

At the Interim, there was littl= e that we thought the WG needed to
pick up from the Interoperability pre= sentation.
Again, we should focus on updates since the Interim, and on t= he
aspects that will influence the charter discussion.

> &n= bsp;4) Demonstration of the testbed (ww= w.6ylowpan.net)
> 15 minutes

Can we do this outside the WG= meeting ( e.g., from 08:40 to 08:55 or so)?
I'm very interested in seeing this, bu= t I don't see us spending WG
meeting time on a testbed demonstration.
 
I think the demonstration of the testbed could be short (just 5 minute= s might be OK for the presentation of the architecture and implementat= ion of 6lowpan).  If you still think that it might be better to do the= demonstration before the WG, it is OK.

Gruesse, Carsten




--
__
Ki-Hyung Kim
Associate Profe= ssor
Division of Information and Computer Eng.,
Ajou University, Suwon, = Korea 442-749
Tel:+82-31-219-2433, ht= tp://ilab.ajou.ac.kr
------=_Part_7847_4932955.1143061082434-- --===============1918984333== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --===============1918984333==-- From 6lowpan-bounces@ietf.org Thu Mar 23 10:29:35 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMRkh-0000wY-3m; Thu, 23 Mar 2006 10:29:31 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMRkg-0000wT-Cu for 6lowpan@lists.ietf.org; Thu, 23 Mar 2006 10:29:30 -0500 Received: from mailx.danfoss.com ([193.162.34.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FMRkg-000822-2l for 6lowpan@lists.ietf.org; Thu, 23 Mar 2006 10:29:30 -0500 Received: from DKDN04MX62.dkdn04.danfoss.net ([10.6.2.62]) by mailx.danfoss.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 23 Mar 2006 16:29:29 +0100 Received: from dkdn01mx21.danfoss.net ([10.12.129.21]) by DKDN04MX62.dkdn04.danfoss.net with InterScan Message Security Suite; Thu, 23 Mar 2006 16:29:28 +0100 Received: from dkdn01mx25.danfoss.net ([10.12.129.25]) by dkdn01mx21.danfoss.net with Microsoft SMTPSVC(6.0.3790.1830); Thu, 23 Mar 2006 16:29:28 +0100 Received: from DKDN01MX34.danfoss.net ([10.12.128.14]) by dkdn01mx25.danfoss.net with Microsoft SMTPSVC(6.0.3790.1830); Thu, 23 Mar 2006 16:29:28 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [6lowpan] Working group last-call on problems document Date: Thu, 23 Mar 2006 16:29:20 +0100 Message-ID: <49A38D2FE2C53946A57916AD6A1F00D782EAAA@DKDN01MX34.danfoss.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [6lowpan] Working group last-call on problems document Thread-Index: AcZBWMHfBRvZv6zGTWWaOj0zysq26AAJ1rnQA0N6YtA= From: "Schumacher Christian Peter Pii" To: "Shah, Rahul C" X-OriginalArrivalTime: 23 Mar 2006 15:29:28.0350 (UTC) FILETIME=[92E5E3E0:01C64E8E] X-Spam-Score: 0.0 (/) X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org Hi Rahul The problem statement document for 6lowpan is on the agenda tomorrow. I assume you've taken authorship of this document after Nandakishore Kushalnagar.=20 The mailing list has received two mails with nits on this document. Will you collect the importants nits received and give a quick presentation? Regards Christian -----Original Message----- From: Kushalnagar, Nandakishore [mailto:nandakishore.kushalnagar@intel.com]=20 Sent: 6. marts 2006 18:45 To: Soohong Daniel Park; Geoff Mulligan; 6lowpan Subject: RE: [6lowpan] Working group last-call on problems document Thanks Daniel. Once all the comments are in, we will do a final walk through to clarify these inconsistencies. Regards Nandu -----Original Message----- From: Soohong Daniel Park [mailto:soohong.park@samsung.com]=20 Sent: Monday, March 06, 2006 12:01 PM To: Geoff Mulligan; 6lowpan Subject: Re: [6lowpan] Working group last-call on problems document I believe it is ready to the IESG. Good job Nandu and Gab...:-) Minor nits: both LoWPAN and 6LoWPAN seem a bit confused around the document. If available, defining terminology would be favorable. Daniel (Soohong Daniel Park) Mobile Convergence Laboratory, SAMSUNG Electronics. ----- Original Message -----=20 From: "Geoff Mulligan" To: "6lowpan" <6lowpan@lists.ietf.org> Sent: Tuesday, March 07, 2006 1:12 AM Subject: [6lowpan] Working group last-call on problems document > Hi, > This note starts the 6loWPAN Working Group Last-call for comments on > draft-ietf-6lowpan-problem-02.txt, "6LoWPAN: Overview, Assumptions, > Problem Statement and Goals". The document can be found at > ftp://ftp.ietf.org/internet-drafts/draft-ietf-6lowpan-problem-02.txt >=20 > Please review the document carefully, and send your feedback to the > list. Please also indicate whether or not you believe that this > document is ready to go to the IESG. >=20 > This Last Call will end on 20 March 2006 at 0900 MST (UTC - 7), two > weeks form the time of this call. >=20 > Thanks, > geoff >=20 >=20 >=20 >=20 > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan >=20 > _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Thu Mar 23 13:41:36 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMUkN-00071O-LD; Thu, 23 Mar 2006 13:41:23 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMUkM-00071I-PE for 6lowpan@lists.ietf.org; Thu, 23 Mar 2006 13:41:22 -0500 Received: from mailx.danfoss.com ([193.162.34.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FMUkL-0007XN-FB for 6lowpan@lists.ietf.org; Thu, 23 Mar 2006 13:41:22 -0500 Received: from DKDN04MX62.dkdn04.danfoss.net ([10.6.2.62]) by mailx.danfoss.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 23 Mar 2006 19:41:20 +0100 Received: from dkdn01mx21.danfoss.net ([10.12.129.21]) by DKDN04MX62.dkdn04.danfoss.net with InterScan Message Security Suite; Thu, 23 Mar 2006 19:41:20 +0100 Received: from dkdn01mx25.danfoss.net ([10.12.129.25]) by dkdn01mx21.danfoss.net with Microsoft SMTPSVC(6.0.3790.1830); Thu, 23 Mar 2006 19:41:20 +0100 Received: from DKDN01MX34.danfoss.net ([10.12.128.14]) by dkdn01mx25.danfoss.net with Microsoft SMTPSVC(6.0.3790.1830); Thu, 23 Mar 2006 19:41:19 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: FW: [6lowpan] FW: thursday dinner update Date: Thu, 23 Mar 2006 19:41:12 +0100 Message-ID: <49A38D2FE2C53946A57916AD6A1F00D782EAB1@DKDN01MX34.danfoss.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [6lowpan] FW: thursday dinner update Thread-Index: AcZNT17BvKqEjZg1SQyIH0NvjVJcIwAcg8vQADkJYvA= From: "Schumacher Christian Peter Pii" To: "6lowpan" <6lowpan@lists.ietf.org> X-OriginalArrivalTime: 23 Mar 2006 18:41:19.0908 (UTC) FILETIME=[60523E40:01C64EA9] X-Spam-Score: 0.0 (/) X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30 Cc: 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org Hi. As promised details for tonights dinner. Restaurant:=20 The Terrace http://www.hilton.com/en/hi/hotels/dining.jhtml?ctyhocn=3DDFWANHH#1 Time:=20 8 pm (20:00)=20 =20 Attendees: Behcet Sarikaya=20 Brian Minard=20 Carsten Bormann Chieh-yih Wan Christian Schumacher=20 Erik Nordmark=20 Geoff Mulligan=20 Ki-Hyung Kim=20 Rahul Shah Samita Chakrabarti Tim Salo Questions? Mail me. Not on the dinner-list? Mail me. Regards Christian ________________________________ From: Schumacher Christian Peter Pii [mailto:schumacher@danfoss.com]=20 Sent: 22. marts 2006 09:06 To: 6lowpan Subject: [6lowpan] FW: thursday dinner update Hi again.=20 The list of attendees for thursdays dinner (after plenary) are currently:=20 Behcet Sarikaya=20 Brian Minard=20 Carsten Bormann=20 Christian Schumacher=20 Erik Nordmark=20 Geoff Mulligan=20 Ki-Hyung Kim=20 Samita Chakrabarti=20 If you're not on the list and would like to join the 6lowpan WG for dinner thursday evening, please send me a mail=20 ( if you've already sent a mail, but you're not on the list, please send it again as I might have missed it. )=20 I will sent out the name of the restaurant (at Hilton Anatole) before lunch tomorrow.=20 Regards=20 Christian=20 ______________________________________________=20 From: Schumacher Christian Peter Pii =20 Sent: 21. marts 2006 19:25=20 To: 6lowpan=20 Subject: thursday dinner=20 As mentioned by Carsten , the 6lowpan WG will join up for a dinner on Thursday after the plenary. We'll probably go for one of the restaurants at the Hilton Anatole.=20 The following people have RSVP'ed that they will attend:=20 Carsten Bormann=20 Christian Schumacher=20 Erik Nordmark=20 Geoff Mulligan=20 Ki-Hyung Kim=20 Samita Chakrabarti=20 Please respond to this mail, if you would like to attend.=20 Regards=20 Christian=20 _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Thu Mar 23 13:49:36 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMUsJ-0006PP-4x; Thu, 23 Mar 2006 13:49:35 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMUsH-0006M9-Kf for 6lowpan@lists.ietf.org; Thu, 23 Mar 2006 13:49:33 -0500 Received: from mailx.danfoss.com ([193.162.34.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FMUsG-0007uy-A2 for 6lowpan@lists.ietf.org; Thu, 23 Mar 2006 13:49:33 -0500 Received: from DKDN04MX64.dkdn04.danfoss.net ([10.6.2.64]) by mailx.danfoss.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 23 Mar 2006 19:49:23 +0100 Received: from dkdn01mx22.danfoss.net ([10.12.129.22]) by DKDN04MX64.dkdn04.danfoss.net with InterScan Message Security Suite; Thu, 23 Mar 2006 19:49:22 +0100 Received: from DKDN01MX34.danfoss.net ([10.12.128.14]) by dkdn01mx22.danfoss.net with Microsoft SMTPSVC(6.0.3790.1830); Thu, 23 Mar 2006 19:49:22 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: FW: [6lowpan] Working group last-call on problems document Date: Thu, 23 Mar 2006 19:49:03 +0100 Message-ID: <49A38D2FE2C53946A57916AD6A1F00D782EAB2@DKDN01MX34.danfoss.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [6lowpan] Working group last-call on problems document Thread-Index: AcZBWMHfBRvZv6zGTWWaOj0zysq26AAJ1rnQA0N6YtAABv/VwA== From: "Schumacher Christian Peter Pii" To: "Shah, Rahul C" X-OriginalArrivalTime: 23 Mar 2006 18:49:22.0074 (UTC) FILETIME=[7FB6EFA0:01C64EAA] X-Spam-Score: 0.0 (/) X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org Hi Rahul Gabriel Montenegro, which is the co-author of the problem statement document, has volunteered to present the problem statement document and nits at the WG meeting tomorrow, so you can forget my previous mail. If you still want to present something you must coordinate with Gabriel, and Carsten to reserve time in the agenda.=20 Regards Christian -----Original Message----- From: Schumacher Christian Peter Pii=20 Sent: 23. marts 2006 09:29 To: 'Shah, Rahul C' Cc: 'Kushalnagar, Nandakishore'; Soohong Daniel Park; Geoff Mulligan; 6lowpan Subject: RE: [6lowpan] Working group last-call on problems document Hi Rahul The problem statement document for 6lowpan is on the agenda tomorrow. I assume you've taken authorship of this document after Nandakishore Kushalnagar.=20 The mailing list has received two mails with nits on this document. Will you collect the importants nits received and give a quick presentation? Regards Christian -----Original Message----- From: Kushalnagar, Nandakishore [mailto:nandakishore.kushalnagar@intel.com]=20 Sent: 6. marts 2006 18:45 To: Soohong Daniel Park; Geoff Mulligan; 6lowpan Subject: RE: [6lowpan] Working group last-call on problems document Thanks Daniel. Once all the comments are in, we will do a final walk through to clarify these inconsistencies. Regards Nandu -----Original Message----- From: Soohong Daniel Park [mailto:soohong.park@samsung.com]=20 Sent: Monday, March 06, 2006 12:01 PM To: Geoff Mulligan; 6lowpan Subject: Re: [6lowpan] Working group last-call on problems document I believe it is ready to the IESG. Good job Nandu and Gab...:-) Minor nits: both LoWPAN and 6LoWPAN seem a bit confused around the document. If available, defining terminology would be favorable. Daniel (Soohong Daniel Park) Mobile Convergence Laboratory, SAMSUNG Electronics. ----- Original Message -----=20 From: "Geoff Mulligan" To: "6lowpan" <6lowpan@lists.ietf.org> Sent: Tuesday, March 07, 2006 1:12 AM Subject: [6lowpan] Working group last-call on problems document > Hi, > This note starts the 6loWPAN Working Group Last-call for comments on > draft-ietf-6lowpan-problem-02.txt, "6LoWPAN: Overview, Assumptions, > Problem Statement and Goals". The document can be found at > ftp://ftp.ietf.org/internet-drafts/draft-ietf-6lowpan-problem-02.txt >=20 > Please review the document carefully, and send your feedback to the > list. Please also indicate whether or not you believe that this > document is ready to go to the IESG. >=20 > This Last Call will end on 20 March 2006 at 0900 MST (UTC - 7), two > weeks form the time of this call. >=20 > Thanks, > geoff >=20 >=20 >=20 >=20 > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan >=20 > _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Thu Mar 23 14:51:33 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMVqD-0004P1-1E; Thu, 23 Mar 2006 14:51:29 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMVqB-0004Ow-SB for 6lowpan@lists.ietf.org; Thu, 23 Mar 2006 14:51:27 -0500 Received: from saloits.com ([208.42.140.127] helo=newbsd.saloits.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FMVqA-0002CP-FV for 6lowpan@lists.ietf.org; Thu, 23 Mar 2006 14:51:27 -0500 Received: from newbsd.saloits.com (localhost.saloits.com [127.0.0.1]) by newbsd.saloits.com (8.13.1/8.13.1) with ESMTP id k2NJpPfd066179 for <6lowpan@lists.ietf.org>; Thu, 23 Mar 2006 13:51:25 -0600 (CST) (envelope-from salo@newbsd.saloits.com) Received: (from salo@localhost) by newbsd.saloits.com (8.13.1/8.13.1/Submit) id k2NJpPKH066178 for 6lowpan@lists.ietf.org; Thu, 23 Mar 2006 13:51:25 -0600 (CST) (envelope-from salo) Date: Thu, 23 Mar 2006 13:51:25 -0600 (CST) From: "Timothy J. Salo" Message-Id: <200603231951.k2NJpPKH066178@newbsd.saloits.com> To: 6lowpan@lists.ietf.org Subject: Re: [6lowpan] IEEE 802.15.4-2003 In-Reply-To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Cc: 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org > Subject: [6lowpan] IEEE 802.15.4-2003 > Date: Mon, 13 Mar 2006 11:48:35 -0500 > From: > [...] > If yes would it be fair to ask for making 802.15.4 available in > the same fashion IETF publications are available? You mean, online and free? See: http://standards.ieee.org/getieee802/802.15.html Unfortunately, draft documents don't appear to be readily available without charge. See: http://shop.ieee.org/ieeestore/Product.aspx?product_no=UE5954 > E.g. make a WG draft quoting all relevant parts of IEEE 802.15.4? I think that a brief tutorial of 802.15.4 would help 6lowpan documents read better. I would have made this suggestion for the problem-statement draft, but I didn't have time to write this overview at the time... -tjs _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Thu Mar 23 15:14:30 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMWCI-0004GV-EW; Thu, 23 Mar 2006 15:14:18 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMWCG-0004FA-Pk for 6lowpan@lists.ietf.org; Thu, 23 Mar 2006 15:14:16 -0500 Received: from web81910.mail.mud.yahoo.com ([68.142.207.189]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FMWCG-0003g0-D3 for 6lowpan@lists.ietf.org; Thu, 23 Mar 2006 15:14:16 -0500 Received: (qmail 36321 invoked by uid 60001); 23 Mar 2006 20:14:12 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=vqZLDAN0FKZLNUIyJ3lgIQYIiHILdoxFbH5BHGycqiW3w9QJTEydCw5Jpk3pZAeMoQA1teFg2Z4RD6N/bvygP2aAYsWGpnNGZhoOLU3ojn3SzS+ldPLKJ+H+08RcdA3/bHnTrvlJcsxCkm/UzR95CP8glKtlrzPxjjaPax86gPU= ; Message-ID: <20060323201412.36319.qmail@web81910.mail.mud.yahoo.com> Received: from [130.129.133.67] by web81910.mail.mud.yahoo.com via HTTP; Thu, 23 Mar 2006 12:14:12 PST Date: Thu, 23 Mar 2006 12:14:12 -0800 (PST) From: gabriel montenegro Subject: Re: FW: [6lowpan] Working group last-call on problems document To: Schumacher Christian Peter Pii , "Shah, Rahul C" , nandakishore.kushalnagar@intel.com In-Reply-To: <49A38D2FE2C53946A57916AD6A1F00D782EAB2@DKDN01MX34.danfoss.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.9 (/) X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org Could either of you forward those nits to me? For some reason I was unsusbscribed from the list and just found out and resubscribed yesterday... thanks, -gabriel --- Schumacher Christian Peter Pii wrote: > Hi Rahul > > Gabriel Montenegro, which is the co-author of the problem statement > document, has volunteered to present the problem statement document and > nits at the WG meeting tomorrow, so you can forget my previous mail. If > you still want to present something you must coordinate with Gabriel, > and Carsten to reserve time in the agenda. > > Regards > Christian > > > -----Original Message----- > From: Schumacher Christian Peter Pii > Sent: 23. marts 2006 09:29 > To: 'Shah, Rahul C' > Cc: 'Kushalnagar, Nandakishore'; Soohong Daniel Park; Geoff Mulligan; > 6lowpan > Subject: RE: [6lowpan] Working group last-call on problems document > > Hi Rahul > > The problem statement document for 6lowpan is on the agenda tomorrow. > I assume you've taken authorship of this document after Nandakishore > Kushalnagar. > The mailing list has received two mails with nits on this document. Will > you collect the importants nits received and give a quick presentation? > > Regards > Christian > > > > -----Original Message----- > From: Kushalnagar, Nandakishore > [mailto:nandakishore.kushalnagar@intel.com] > Sent: 6. marts 2006 18:45 > To: Soohong Daniel Park; Geoff Mulligan; 6lowpan > Subject: RE: [6lowpan] Working group last-call on problems document > > Thanks Daniel. > > Once all the comments are in, we will do a final walk through to clarify > these inconsistencies. > > Regards > Nandu > > -----Original Message----- > From: Soohong Daniel Park [mailto:soohong.park@samsung.com] > Sent: Monday, March 06, 2006 12:01 PM > To: Geoff Mulligan; 6lowpan > Subject: Re: [6lowpan] Working group last-call on problems document > > I believe it is ready to the IESG. Good job Nandu and Gab...:-) > > Minor nits: both LoWPAN and 6LoWPAN seem a bit confused > around the document. If available, defining terminology would > be favorable. > > Daniel (Soohong Daniel Park) > Mobile Convergence Laboratory, SAMSUNG Electronics. > > ----- Original Message ----- > From: "Geoff Mulligan" > To: "6lowpan" <6lowpan@lists.ietf.org> > Sent: Tuesday, March 07, 2006 1:12 AM > Subject: [6lowpan] Working group last-call on problems document > > > > Hi, > > This note starts the 6loWPAN Working Group Last-call for comments on > > draft-ietf-6lowpan-problem-02.txt, "6LoWPAN: Overview, Assumptions, > > Problem Statement and Goals". The document can be found at > > ftp://ftp.ietf.org/internet-drafts/draft-ietf-6lowpan-problem-02.txt > > > > Please review the document carefully, and send your feedback to the > > list. Please also indicate whether or not you believe that this > > document is ready to go to the IESG. > > > > This Last Call will end on 20 March 2006 at 0900 MST (UTC - 7), two > > weeks form the time of this call. > > > > Thanks, > > geoff > > > > > > > > > > _______________________________________________ > > 6lowpan mailing list > > 6lowpan@ietf.org > > https://www1.ietf.org/mailman/listinfo/6lowpan > > > > > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Thu Mar 23 15:33:37 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMWUg-00035b-2Q; Thu, 23 Mar 2006 15:33:18 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMWUe-00035W-RY for 6lowpan@lists.ietf.org; Thu, 23 Mar 2006 15:33:16 -0500 Received: from mailx.danfoss.com ([193.162.34.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FMWUe-0004UJ-Ag for 6lowpan@lists.ietf.org; Thu, 23 Mar 2006 15:33:16 -0500 Received: from DKDN04MX62.dkdn04.danfoss.net ([10.6.2.62]) by mailx.danfoss.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 23 Mar 2006 21:33:15 +0100 Received: from dkdn01mx21.danfoss.net ([10.12.129.21]) by DKDN04MX62.dkdn04.danfoss.net with InterScan Message Security Suite; Thu, 23 Mar 2006 21:33:14 +0100 Received: from dkdn01mx25.danfoss.net ([10.12.129.25]) by dkdn01mx21.danfoss.net with Microsoft SMTPSVC(6.0.3790.1830); Thu, 23 Mar 2006 21:33:14 +0100 Received: from DKDN01MX34.danfoss.net ([10.12.128.14]) by dkdn01mx25.danfoss.net with Microsoft SMTPSVC(6.0.3790.1830); Thu, 23 Mar 2006 21:33:14 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: FW: [6lowpan] Working group last-call on problems document Date: Thu, 23 Mar 2006 21:33:06 +0100 Message-ID: <49A38D2FE2C53946A57916AD6A1F00D782EAB9@DKDN01MX34.danfoss.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: FW: [6lowpan] Working group last-call on problems document Thread-Index: AcZOtlr+iew2/QnJR1K21OZSS9fZxwAAjUdQ From: "Schumacher Christian Peter Pii" To: "gabriel montenegro" X-OriginalArrivalTime: 23 Mar 2006 20:33:14.0009 (UTC) FILETIME=[023CC090:01C64EB9] X-Spam-Score: 0.0 (/) X-Scan-Signature: 76c7db407a166e4c39f35d8215d8dd32 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org =20 Hi Gabriel. The nits collected are from me and Daniel, mostly editorial nits, but here goes: ### Daniels nits ### I believe it is ready to the IESG. Good job Nandu and Gab...:-) Minor nits: both LoWPAN and 6LoWPAN seem a bit confused around the document. If available, defining terminology would be favorable. Daniel (Soohong Daniel Park) Mobile Convergence Laboratory, SAMSUNG Electronics. ### End of Daniels nits ### ### My nits ### Sorry for the late feedback. As Daniel said, good job Nandu and Gab. However, I have the following nitpicks:=20 Section: 2. Overview Possibly missing a linespace between bullet 9. and 10. Section: 4.2. Topologies Last sentence in this section:=20 "This, or course..."=20 should probably be "This, of course" Section: 4.4. Limited configuration and management Last sentence in this section:=20 "...yet be powerful to control dense..." I suggest maybe to add "enough" between "powerful" and "to". Section: 4.6. Security Last sentence in this section: "Please refer to security consideration section below for an in depth requirements for security" I suggest change to: "Please refer to the security considerations section below for in depth security requirements." Section: 5. Goals (Page 7-8): I think the reader would gain a better understanding of the goals for 6lowpan if we start each goal with a clear definition (one-sentence) of the goal, then followed by the related background information. The goals appear more or less hidden in the text in its current form. This is especially true for goal nr. 2, which is mostly background information until at the end it is stated "this goal needs to investigate using existing header compression... ".=20 I also think the usage of word goal in goals 2 and 3 are confusing. Examples: "...this goal needs to investigate..." (Goal nr. 2) "The goal should specify a method..." (Goal nr. 3) It is we (the working group) not the goal , which needs to investigate and to specify. Correct me, if I'm reading it wrong. Overall I think the document is good, and I believe if you incorporate my nits on the goals section, then it is IESG ready.=20 Again, excellent work. :-) Regards Christian ### End of my nits ### Regards Christian -----Original Message----- From: gabriel montenegro [mailto:gabriel_montenegro_2000@yahoo.com]=20 Sent: 23. marts 2006 14:14 To: Schumacher Christian Peter Pii; Shah, Rahul C; nandakishore.kushalnagar@intel.com Cc: 6lowpan Subject: Re: FW: [6lowpan] Working group last-call on problems document Could either of you forward those nits to me? For some reason I was unsusbscribed from the list and just found out and resubscribed yesterday... thanks, -gabriel --- Schumacher Christian Peter Pii wrote: > Hi Rahul >=20 > Gabriel Montenegro, which is the co-author of the problem statement > document, has volunteered to present the problem statement document and > nits at the WG meeting tomorrow, so you can forget my previous mail. If > you still want to present something you must coordinate with Gabriel, > and Carsten to reserve time in the agenda.=20 >=20 > Regards > Christian >=20 >=20 > -----Original Message----- > From: Schumacher Christian Peter Pii=20 > Sent: 23. marts 2006 09:29 > To: 'Shah, Rahul C' > Cc: 'Kushalnagar, Nandakishore'; Soohong Daniel Park; Geoff Mulligan; > 6lowpan > Subject: RE: [6lowpan] Working group last-call on problems document >=20 > Hi Rahul >=20 > The problem statement document for 6lowpan is on the agenda tomorrow. > I assume you've taken authorship of this document after Nandakishore > Kushalnagar.=20 > The mailing list has received two mails with nits on this document. Will > you collect the importants nits received and give a quick presentation? >=20 > Regards > Christian >=20 >=20 >=20 > -----Original Message----- > From: Kushalnagar, Nandakishore > [mailto:nandakishore.kushalnagar@intel.com]=20 > Sent: 6. marts 2006 18:45 > To: Soohong Daniel Park; Geoff Mulligan; 6lowpan > Subject: RE: [6lowpan] Working group last-call on problems document >=20 > Thanks Daniel. >=20 > Once all the comments are in, we will do a final walk through to clarify > these inconsistencies. >=20 > Regards > Nandu >=20 > -----Original Message----- > From: Soohong Daniel Park [mailto:soohong.park@samsung.com]=20 > Sent: Monday, March 06, 2006 12:01 PM > To: Geoff Mulligan; 6lowpan > Subject: Re: [6lowpan] Working group last-call on problems document >=20 > I believe it is ready to the IESG. Good job Nandu and Gab...:-) >=20 > Minor nits: both LoWPAN and 6LoWPAN seem a bit confused > around the document. If available, defining terminology would > be favorable. >=20 > Daniel (Soohong Daniel Park) > Mobile Convergence Laboratory, SAMSUNG Electronics. >=20 > ----- Original Message -----=20 > From: "Geoff Mulligan" > To: "6lowpan" <6lowpan@lists.ietf.org> > Sent: Tuesday, March 07, 2006 1:12 AM > Subject: [6lowpan] Working group last-call on problems document >=20 >=20 > > Hi, > > This note starts the 6loWPAN Working Group Last-call for comments on > > draft-ietf-6lowpan-problem-02.txt, "6LoWPAN: Overview, Assumptions, > > Problem Statement and Goals". The document can be found at > > ftp://ftp.ietf.org/internet-drafts/draft-ietf-6lowpan-problem-02.txt > >=20 > > Please review the document carefully, and send your feedback to the > > list. Please also indicate whether or not you believe that this > > document is ready to go to the IESG. > >=20 > > This Last Call will end on 20 March 2006 at 0900 MST (UTC - 7), two > > weeks form the time of this call. > >=20 > > Thanks, > > geoff > >=20 > >=20 > >=20 > >=20 > > _______________________________________________ > > 6lowpan mailing list > > 6lowpan@ietf.org > > https://www1.ietf.org/mailman/listinfo/6lowpan > >=20 > > >=20 > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan >=20 > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan >=20 > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan >=20 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around=20 http://mail.yahoo.com=20 _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Fri Mar 24 00:58:15 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMfJH-0000bs-KC; Fri, 24 Mar 2006 00:58:07 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMfJG-0000bC-Lg for 6lowpan@ietf.org; Fri, 24 Mar 2006 00:58:06 -0500 Received: from web81904.mail.mud.yahoo.com ([68.142.207.183]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FMfJF-0006fJ-9R for 6lowpan@ietf.org; Fri, 24 Mar 2006 00:58:06 -0500 Received: (qmail 13471 invoked by uid 60001); 24 Mar 2006 05:58:04 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=JFSMXp7ADK7wpOw5Gy4cGHJvQf2XUWtIcMy8Nq76VdR0OP3WQjJ7gpxrqD1d01JWYb5kEE20Vs2cpOBFLiaTqQCfWoL0xHROx+3na/0WKZdDhQUQKEoRaiNsVMhEjq2WvvHhAnRDZZP03kfKs/nymp2jkweu0WP7HvCI20cNfUM= ; Message-ID: <20060324055804.13469.qmail@web81904.mail.mud.yahoo.com> Received: from [204.96.114.166] by web81904.mail.mud.yahoo.com via HTTP; Thu, 23 Mar 2006 21:58:04 PST Date: Thu, 23 Mar 2006 21:58:04 -0800 (PST) From: gabriel montenegro Subject: Re: [6lowpan] LOAD Updated To: 6lowpan@ietf.org, ian.chakeres@gmail.com MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.9 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Cc: 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org Ian, You said: "I still believe that DYMO is more appropriate for 6lowpan, it should require few if any modifications to run in 6lowpan networks." I'd like to understand the tradeoff here: DYMO - supposedly improved. how? what are the advantages over AODV? is it really very different? - slated for proposed standard. when? AODV - de facto standard adopted in modified form by these other groups: - zigbee - as explained to me during an open house, they use a modified form of AODV (among other mesh solutions) - 802.11s: after something like 15 proposals, the recently chosen basis for the group's work uses a modified form of AODV with OLSR as optional. It is attractive to align with the above groups, so DYMO should be sufficiently better so as to offset ths. Could you help me better understand the relative merits of aodv versus dymo? thanks, -gabriel __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Fri Mar 24 01:06:01 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMfQv-0008Ju-RQ; Fri, 24 Mar 2006 01:06:01 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMfQu-0008I2-DH for 6lowpan@lists.ietf.org; Fri, 24 Mar 2006 01:06:00 -0500 Received: from web81903.mail.mud.yahoo.com ([68.142.207.182]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FMfQq-000703-0o for 6lowpan@lists.ietf.org; Fri, 24 Mar 2006 01:05:57 -0500 Received: (qmail 94580 invoked by uid 60001); 24 Mar 2006 06:05:55 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=2jn1OUX8LU16Lp0TC1zLs1OMMocbvohdbQqkXyJ0zFUMgL5CPN6Xz4LEVykjJ6UXxtlS2GVoE5G+ROuK1tquVKTIywqsLMyXFdXamcgDZYT2yufwOIzLHGXZVHLhDIqSBgaSPUby5P+e6V80BEuyBnz287u2n/7bCJOI+yJsHI4= ; Message-ID: <20060324060555.94578.qmail@web81903.mail.mud.yahoo.com> Received: from [204.96.114.166] by web81903.mail.mud.yahoo.com via HTTP; Thu, 23 Mar 2006 22:05:55 PST Date: Thu, 23 Mar 2006 22:05:55 -0800 (PST) From: gabriel montenegro Subject: RE: [6lowpan] Working group last-call on problems document To: Schumacher Christian Peter Pii , "Shah, Rahul C" , nandakishore.kushalnagar@intel.com In-Reply-To: <49A38D2FE2C53946A57916AD6A1F00D782EAAA@DKDN01MX34.danfoss.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.9 (/) X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org By the way, Nandu, could you send me the latest and greatest XML source to edit the final nits? tnx, -gabriel --- Schumacher Christian Peter Pii wrote: > Hi Rahul > > The problem statement document for 6lowpan is on the agenda tomorrow. > I assume you've taken authorship of this document after Nandakishore > Kushalnagar. > The mailing list has received two mails with nits on this document. Will > you collect the importants nits received and give a quick presentation? > > Regards > Christian > > > > -----Original Message----- > From: Kushalnagar, Nandakishore > [mailto:nandakishore.kushalnagar@intel.com] > Sent: 6. marts 2006 18:45 > To: Soohong Daniel Park; Geoff Mulligan; 6lowpan > Subject: RE: [6lowpan] Working group last-call on problems document > > Thanks Daniel. > > Once all the comments are in, we will do a final walk through to clarify > these inconsistencies. > > Regards > Nandu > > -----Original Message----- > From: Soohong Daniel Park [mailto:soohong.park@samsung.com] > Sent: Monday, March 06, 2006 12:01 PM > To: Geoff Mulligan; 6lowpan > Subject: Re: [6lowpan] Working group last-call on problems document > > I believe it is ready to the IESG. Good job Nandu and Gab...:-) > > Minor nits: both LoWPAN and 6LoWPAN seem a bit confused > around the document. If available, defining terminology would > be favorable. > > Daniel (Soohong Daniel Park) > Mobile Convergence Laboratory, SAMSUNG Electronics. > > ----- Original Message ----- > From: "Geoff Mulligan" > To: "6lowpan" <6lowpan@lists.ietf.org> > Sent: Tuesday, March 07, 2006 1:12 AM > Subject: [6lowpan] Working group last-call on problems document > > > > Hi, > > This note starts the 6loWPAN Working Group Last-call for comments on > > draft-ietf-6lowpan-problem-02.txt, "6LoWPAN: Overview, Assumptions, > > Problem Statement and Goals". The document can be found at > > ftp://ftp.ietf.org/internet-drafts/draft-ietf-6lowpan-problem-02.txt > > > > Please review the document carefully, and send your feedback to the > > list. Please also indicate whether or not you believe that this > > document is ready to go to the IESG. > > > > This Last Call will end on 20 March 2006 at 0900 MST (UTC - 7), two > > weeks form the time of this call. > > > > Thanks, > > geoff > > > > > > > > > > _______________________________________________ > > 6lowpan mailing list > > 6lowpan@ietf.org > > https://www1.ietf.org/mailman/listinfo/6lowpan > > > > > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Fri Mar 24 01:16:06 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMfaU-0000Mr-Ni; Fri, 24 Mar 2006 01:15:54 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMfaT-0000JC-PD for 6lowpan@ietf.org; Fri, 24 Mar 2006 01:15:53 -0500 Received: from saloits.com ([208.42.140.127] helo=newbsd.saloits.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FMfaP-0007Rv-Br for 6lowpan@ietf.org; Fri, 24 Mar 2006 01:15:50 -0500 Received: from newbsd.saloits.com (localhost.saloits.com [127.0.0.1]) by newbsd.saloits.com (8.13.1/8.13.1) with ESMTP id k2O6FmSo068558 for <6lowpan@ietf.org>; Fri, 24 Mar 2006 00:15:48 -0600 (CST) (envelope-from salo@newbsd.saloits.com) Received: (from salo@localhost) by newbsd.saloits.com (8.13.1/8.13.1/Submit) id k2O6FmMi068557 for 6lowpan@ietf.org; Fri, 24 Mar 2006 00:15:48 -0600 (CST) (envelope-from salo) Date: Fri, 24 Mar 2006 00:15:48 -0600 (CST) From: "Timothy J. Salo" Message-Id: <200603240615.k2O6FmMi068557@newbsd.saloits.com> To: 6lowpan@ietf.org Subject: Re: [6lowpan] LOAD Updated In-Reply-To: <20060324055804.13469.qmail@web81904.mail.mud.yahoo.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org > Date: Thu, 23 Mar 2006 21:58:04 -0800 (PST) > From: gabriel montenegro > Subject: Re: [6lowpan] LOAD Updated > > Ian said: > > > "I still believe that DYMO is more appropriate for 6lowpan, it should > > require few if any modifications to run in 6lowpan networks." > > I'd like to understand the tradeoff here: > > DYMO > - supposedly improved. how? what are the advantages over AODV? > is it really very different? > - slated for proposed standard. when? > [...] The short answer is that DYMO is the next-generation reactive ad hoc routing protocol being developed within the MANET working group: http://www.ietf.org/html.charters/manet-charter.html It arguably embodies the lessons learned from the development of the previous iteration of protocols developed in the MANET working group, including AODV. This week's DYMO presentation is available: http://www3.ietf.org/proceedings/06mar/slides/manet-0.pdf -tjs _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Fri Mar 24 01:42:19 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMfzu-0005Jm-Fy; Fri, 24 Mar 2006 01:42:10 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMfzt-0004yc-0J for 6lowpan@ietf.org; Fri, 24 Mar 2006 01:42:09 -0500 Received: from zproxy.gmail.com ([64.233.162.197]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FMfrl-0007tD-G0 for 6lowpan@ietf.org; Fri, 24 Mar 2006 01:33:46 -0500 Received: by zproxy.gmail.com with SMTP id r28so725714nza for <6lowpan@ietf.org>; Thu, 23 Mar 2006 22:33:44 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=rNKg2lXYjEsqz8QOlcATZ+qVqMTMwCcO6JEj3UWYFObWdy6MSPbJ8OmswxaLMsAnXW3afX2M2awd+jGphEgSwyVvIFcHAc/5UeXaVRqkZkuAvO/PLiXHJpcyGh7sVko9IzAhJT+GvuZ//YCi4JD+XKAElAOvp6BLBDWbVx1+Syk= Received: by 10.36.221.43 with SMTP id t43mr709124nzg; Thu, 23 Mar 2006 22:33:44 -0800 (PST) Received: by 10.37.18.77 with HTTP; Thu, 23 Mar 2006 22:33:44 -0800 (PST) Message-ID: <374005f30603232233y1ca548acu8fc38de8eafd764b@mail.gmail.com> Date: Thu, 23 Mar 2006 22:33:44 -0800 From: "Ian Chakeres" To: "gabriel montenegro" Subject: Re: [6lowpan] LOAD Updated In-Reply-To: <20060324055804.13469.qmail@web81904.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060324055804.13469.qmail@web81904.mail.mud.yahoo.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe Cc: 6lowpan@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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org First off, I would like to say that LOAD is not AODV. LOAD suffers from several serious flaws. I would like to point out my statement """I still believe that DYMO is more appropriate for 6lowpan, it should require few if any modifications to run in 6lowpan networks.""" was in regards to LOAD vs DYMO, not AODV vs DYMO. For 6lowpan purposes, DYMO is a simpler version of AODV. DYMO is easier to implement and has lower requirements (in terms of memory, code, etc.) than AODV. DYMO is close to what has been implemented for sensor networks, such as tinyAODV. AODV is no longer being explored in the MANET WG. If you would like to chat about this, feel free to catch me before/during the 6lowpan meeting, Ian Chakeres Please see the archived proceedings form previous IETFs to see more details about the differences between AODV and DYMO. On 3/23/06, gabriel montenegro wrote: > Ian, > > You said: > > "I still believe that DYMO is more appropriate for 6lowpan, it should > require few if any modifications to run in 6lowpan networks." > > I'd like to understand the tradeoff here: > > DYMO > - supposedly improved. how? what are the advantages over AODV? is it real= ly very > different? > - slated for proposed standard. when? > > AODV > - de facto standard adopted in modified form by these other groups: > - zigbee - as explained to me during an open house, they use a modified= form > of AODV (among other mesh solutions) > - 802.11s: after something like 15 proposals, the recently chosen basis= for the > group's work uses a modified form of AODV with OLSR as optional. > > It is attractive to align with the above groups, so DYMO should be suffic= iently > better so as to offset ths. Could you help me better understand the relat= ive > merits of aodv versus dymo? > > thanks, > > -gabriel > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Fri Mar 24 02:20:42 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMgb0-0008Vw-FI; Fri, 24 Mar 2006 02:20:30 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMgaz-0008TL-QZ for 6lowpan@lists.ietf.org; Fri, 24 Mar 2006 02:20:29 -0500 Received: from mga03.intel.com ([143.182.124.21] helo=azsmga101-1.ch.intel.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FMgav-0001MI-DH for 6lowpan@lists.ietf.org; Fri, 24 Mar 2006 02:20:29 -0500 Received: from azsmga001.ch.intel.com ([10.2.17.19]) by azsmga101-1.ch.intel.com with ESMTP; 23 Mar 2006 23:20:23 -0800 Received: from orsmsx331.jf.intel.com (HELO orsmsx331.amr.corp.intel.com) ([192.168.65.56]) by azsmga001.ch.intel.com with ESMTP; 23 Mar 2006 23:20:22 -0800 X-IronPort-AV: i="4.03,124,1141632000"; d="xml'217?scan'217,208,217"; a="14816002:sNHT408991933" Received: from orsmsx410.amr.corp.intel.com ([192.168.65.64]) by orsmsx331.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 23 Mar 2006 23:20:14 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C64F13.64680D45" Subject: RE: [6lowpan] Working group last-call on problems document Date: Thu, 23 Mar 2006 23:20:09 -0800 Message-ID: <9D602ABCE51B0B488BF857A4787939B507ABD996@orsmsx410> X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: [6lowpan] Working group last-call on problems document Thread-Index: AcZPCQRFoT9+rHNbTaqjr35/wjUOEAACh1pA From: "Kushalnagar, Nandakishore" To: "gabriel montenegro" , "Schumacher Christian Peter Pii" , "Shah, Rahul C" X-OriginalArrivalTime: 24 Mar 2006 07:20:14.0127 (UTC) FILETIME=[64D4ABF0:01C64F13] X-Spam-Score: 0.0 (/) X-Scan-Signature: b4be0d55bab88df9d21005ced9551e26 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org This is a multi-part message in MIME format. ------_=_NextPart_001_01C64F13.64680D45 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Here you go. Thanks for taking this along Gab! Nandu -----Original Message----- From: gabriel montenegro [mailto:gabriel_montenegro_2000@yahoo.com]=20 Sent: Thursday, March 23, 2006 10:06 PM To: Schumacher Christian Peter Pii; Shah, Rahul C; Kushalnagar, Nandakishore Cc: 6lowpan Subject: RE: [6lowpan] Working group last-call on problems document By the way, Nandu, could you send me the latest and greatest XML source to edit the final nits? tnx, -gabriel --- Schumacher Christian Peter Pii wrote: > Hi Rahul >=20 > The problem statement document for 6lowpan is on the agenda tomorrow. > I assume you've taken authorship of this document after Nandakishore > Kushalnagar.=20 > The mailing list has received two mails with nits on this document. Will > you collect the importants nits received and give a quick presentation? >=20 > Regards > Christian >=20 >=20 >=20 > -----Original Message----- > From: Kushalnagar, Nandakishore > [mailto:nandakishore.kushalnagar@intel.com]=20 > Sent: 6. marts 2006 18:45 > To: Soohong Daniel Park; Geoff Mulligan; 6lowpan > Subject: RE: [6lowpan] Working group last-call on problems document >=20 > Thanks Daniel. >=20 > Once all the comments are in, we will do a final walk through to clarify > these inconsistencies. >=20 > Regards > Nandu >=20 > -----Original Message----- > From: Soohong Daniel Park [mailto:soohong.park@samsung.com]=20 > Sent: Monday, March 06, 2006 12:01 PM > To: Geoff Mulligan; 6lowpan > Subject: Re: [6lowpan] Working group last-call on problems document >=20 > I believe it is ready to the IESG. Good job Nandu and Gab...:-) >=20 > Minor nits: both LoWPAN and 6LoWPAN seem a bit confused > around the document. If available, defining terminology would > be favorable. >=20 > Daniel (Soohong Daniel Park) > Mobile Convergence Laboratory, SAMSUNG Electronics. >=20 > ----- Original Message -----=20 > From: "Geoff Mulligan" > To: "6lowpan" <6lowpan@lists.ietf.org> > Sent: Tuesday, March 07, 2006 1:12 AM > Subject: [6lowpan] Working group last-call on problems document >=20 >=20 > > Hi, > > This note starts the 6loWPAN Working Group Last-call for comments on > > draft-ietf-6lowpan-problem-02.txt, "6LoWPAN: Overview, Assumptions, > > Problem Statement and Goals". The document can be found at > > ftp://ftp.ietf.org/internet-drafts/draft-ietf-6lowpan-problem-02.txt > >=20 > > Please review the document carefully, and send your feedback to the > > list. Please also indicate whether or not you believe that this > > document is ready to go to the IESG. > >=20 > > This Last Call will end on 20 March 2006 at 0900 MST (UTC - 7), two > > weeks form the time of this call. > >=20 > > Thanks, > > geoff > >=20 > >=20 > >=20 > >=20 > > _______________________________________________ > > 6lowpan mailing list > > 6lowpan@ietf.org > > https://www1.ietf.org/mailman/listinfo/6lowpan > >=20 > > >=20 > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan >=20 > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan >=20 > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan >=20 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around=20 http://mail.yahoo.com=20 ------_=_NextPart_001_01C64F13.64680D45 Content-Type: text/xml; name="draft-ietf-6lowpan-problem-02.xml" Content-Transfer-Encoding: base64 Content-Description: draft-ietf-6lowpan-problem-02.xml Content-Disposition: attachment; filename="draft-ietf-6lowpan-problem-02.xml" PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4NCjwhRE9DVFlQRSByZmMgU1lT VEVNICJyZmMyNjI5LmR0ZCIgWw0KPCFFTlRJVFkgUkZDMzU2MSBQVUJMSUMgJycgImh0dHA6Ly94 bWwucmVzb3VyY2Uub3JnL3B1YmxpYy9yZmMvYmlieG1sL3JlZmVyZW5jZS5SRkMuMzU2MS54bWwi Pg0KPCFFTlRJVFkgUkZDMzYyNiBQVUJMSUMgJycgImh0dHA6Ly94bWwucmVzb3VyY2Uub3JnL3B1 YmxpYy9yZmMvYmlieG1sL3JlZmVyZW5jZS5SRkMuMzYyNi54bWwiPg0KPCFFTlRJVFkgUkZDMzY4 NCBQVUJMSUMgJycgImh0dHA6Ly94bWwucmVzb3VyY2Uub3JnL3B1YmxpYy9yZmMvYmlieG1sL3Jl ZmVyZW5jZS5SRkMuMzY4NC54bWwiPg0KPCFFTlRJVFkgUkZDMzQxMSBQVUJMSUMgJycgImh0dHA6 Ly94bWwucmVzb3VyY2Uub3JnL3B1YmxpYy9yZmMvYmlieG1sL3JlZmVyZW5jZS5SRkMuMzQxMS54 bWwiPg0KPCFFTlRJVFkgUkZDMjExOSBQVUJMSUMgJycgImh0dHA6Ly94bWwucmVzb3VyY2Uub3Jn L3B1YmxpYy9yZmMvYmlieG1sL3JlZmVyZW5jZS5SRkMuMjExOS54bWwiPg0KPCFFTlRJVFkgUkZD MjQ2MCBQVUJMSUMgJycgImh0dHA6Ly94bWwucmVzb3VyY2Uub3JnL3B1YmxpYy9yZmMvYmlieG1s L3JlZmVyZW5jZS5SRkMuMjQ2MC54bWwiPg0KPCFFTlRJVFkgTkQgICAgICBQVUJMSUMgJycgImh0 dHA6Ly94bWwucmVzb3VyY2Uub3JnL3B1YmxpYy9yZmMvYmlieG1sMy9yZWZlcmVuY2UuSS1ELmll dGYtaXB2Ni0yNDYxYmlzLnhtbCI+DQo8IUVOVElUWSBBRERSLUNPTkYgUFVCTElDICcnICJodHRw Oi8veG1sLnJlc291cmNlLm9yZy9wdWJsaWMvcmZjL2JpYnhtbDMvcmVmZXJlbmNlLkktRC5pZXRm LWlwdjYtcmZjMjQ2MmJpcy54bWwiPg0KPCFFTlRJVFkgUkZDMzc1NiBQVUJMSUMgJycgImh0dHA6 Ly94bWwucmVzb3VyY2Uub3JnL3B1YmxpYy9yZmMvYmlieG1sL3JlZmVyZW5jZS5SRkMuMzc1Ni54 bWwiPg0KXT4NCg0KPD94bWwtc3R5bGVzaGVldCB0eXBlPSd0ZXh0L3hzbCcgaHJlZj0ncmZjMjYy OS54c2x0JyA/Pg0KPD9yZmMgdG9jPSJ5ZXMiID8+DQo8P3JmYyBzeW1yZWZzPSJ5ZXMiID8+DQo8 P3JmYyBzb3J0cmVmcz0ieWVzIj8+DQo8P3JmYyBpcHJub3RpZmllZD0ibm8iID8+DQo8P3JmYyBz dHJpY3Q9InllcyIgPz4NCjw/cmZjIGNvbXBhY3Q9InllcyIgPz4NCjxyZmMgY2F0ZWdvcnk9J3N0 ZCcgaXByPSdmdWxsMzk3OCcgZG9jTmFtZT0nZHJhZnQtaWV0Zi02bG93cGFuLXByb2JsZW0tMDIu dHh0Jz4NCiAgPGZyb250Pg0KICAgIDx0aXRsZSBhYmJyZXY9IjZsb3dwYW4gUHJvYmxlbXMgYW5k IEdvYWxzIj4NCiAgICA2TG9XUEFOOiBPdmVydmlldywgQXNzdW1wdGlvbnMsIFByb2JsZW0gU3Rh dGVtZW50IGFuZCBHb2FsczwvdGl0bGU+DQoNCiAgICA8YXV0aG9yIGZ1bGxuYW1lPSJOYW5kYWtp c2hvcmUgS3VzaGFsbmFnYXIiIGluaXRpYWxzPSJOLiIgc3VybmFtZT0iS3VzaGFsbmFnYXIiPg0K ICAgICAgPG9yZ2FuaXphdGlvbj5JbnRlbCBDb3JwPC9vcmdhbml6YXRpb24+DQoNCiAgICAgIDxh ZGRyZXNzPg0KICAgICAgICA8ZW1haWw+bmFuZGFraXNob3JlLmt1c2hhbG5hZ2FyQGludGVsLmNv bTwvZW1haWw+DQogICAgICA8L2FkZHJlc3M+DQogICAgPC9hdXRob3I+DQogICAgDQogICAgPGF1 dGhvciBmdWxsbmFtZT0iR2FicmllbCBNb250ZW5lZ3JvIiBpbml0aWFscz0iRy4iIHN1cm5hbWU9 Ik1vbnRlbmVncm8iPg0KICAgICAgPG9yZ2FuaXphdGlvbj5NaWNyb3NvZnQgQ29ycG9yYXRpb248 L29yZ2FuaXphdGlvbj4NCg0KICAgICAgPGFkZHJlc3M+DQogICAgICAgIDxlbWFpbD5nYWJyaWVs X21vbnRlbmVncm9fMjAwMEB5YWhvby5jb208L2VtYWlsPg0KICAgICAgPC9hZGRyZXNzPg0KICAg IDwvYXV0aG9yPg0KDQogICAgPGRhdGUgbW9udGg9IkZlYnJ1YXJ5IiB5ZWFyPSIyMDA2IiAvPg0K DQogICAgPGFic3RyYWN0Pg0KICAgIDx0Pg0KICAgIFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVzIHRo ZSBhc3N1bXB0aW9ucywgDQogICAgcHJvYmxlbSBzdGF0ZW1lbnQgYW5kIGdvYWxzIGZvciB0cmFu c21pdHRpbmcgSVAgb3ZlciANCiAgICBJRUVFIDgwMi4xNS40IG5ldHdvcmtzLiBUaGUgc2V0IG9m IGdvYWxzIGVudW1lcmF0ZWQgaW4gdGhpcyANCiAgICBkb2N1bWVudCBmb3JtIGFuIGluaXRpYWwg c2V0IG9ubHkuIEFkZGl0aW9uYWwgZ29hbHMgbWF5IGJlIA0KICAgIGZvdW5kIG5lY2Vzc2FyeSBv dmVyIHRpbWUgYW5kIG1heSBiZSBhZGRlZCB0byB0aGlzIGRvY3VtZW50Lg0KPC90Pg0KICAgIDwv YWJzdHJhY3Q+DQogIDwvZnJvbnQ+DQoNCiAgPG1pZGRsZT4NCiAgICA8c2VjdGlvbiB0aXRsZT0i SW50cm9kdWN0aW9uIj4NCiAgICA8dD4gTG93LXBvd2VyIHdpcmVsZXNzIHBlcnNvbmFsIGFyZWEg bmV0d29ya3MgKExvV1BBTnMpIGNvbXByaXNlDQogICAgZGV2aWNlcyB0aGF0IGNvbmZvcm0gdG8g dGhlIElFRUUgODAyLjE1LjQtMjAwMyBzdGFuZGFyZCBieSANCiAgICB0aGUgSUVFRSA8eHJlZiB0 YXJnZXQ9ImllZWU4MDIuMTUuNCI+PC94cmVmPi4gVGhlIElFRUUgODAyLjE1LjQgDQogICAgZGV2 aWNlcyBhcmUgY2hhcmFjdGVyaXplZCBieSBzaG9ydCByYW5nZSwgbG93IGJpdCByYXRlLCBsb3cg cG93ZXIgYW5kIA0KICAgIGxvdyBjb3N0Lg0KICAgIDwvdD4NCiAgICA8dD4NCiAgICBUaGlzIGRv Y3VtZW50IGdpdmVzIGFuIG92ZXJ2aWV3IG9mIExvV1BBTnMgYW5kIGRlc2NyaWJlcyANCiAgICBo b3cgdGhleSBiZW5lZml0IGZyb20gSVAgYW5kIElQdjYgbmV0d29ya2luZy4NCiAgICBJdCBkZXNj cmliZXMgdGhlIHJlcXVpcmVtZW50cyBvZiBMb1dQQU5zIHdpdGggcmVnYXJkcyB0byBJUCBsYXll ciBhbmQgYWJvdmUuIEl0IA0KICAgIHNwZWxscyBvdXQgdGhlIHVuZGVybHlpbmcgYXNzdW1wdGlv bnMgb2YgSVAgZm9yIExvV1BBTnMuIEZpbmFsbHksDQogICAgaXQgZGVzY3JpYmVzIHByb2JsZW1z IGFzc29jaWF0ZWQgd2l0aCBlbmFibGluZyBJUCBjb21tdW5pY2F0aW9uDQogICAgYmV0d2VlbiBk ZXZpY2VzIGluIExvV1BBTiwgYW5kIGRlZmluZXMgZ29hbHMgdG8gYWRkcmVzcyB0aGVzZSBpbiAN CiAgICBhIHByaW9yaXRpemVkIG1hbm5lci4gQWRtaXR0ZWRseSwgbm90IGFsbCBpdGVtcyBvbiB0 aGlzIGxpc3QgYXJlDQogICAgbmVjZXNzYXJpbHkgYXBwcm9wcmlhdGUgdGFza3MgZm9yIHRoZSBJ RVRGLiBOZXZlcnRoZWxlc3MsIHRoZXkgYXJlDQogICAgZG9jdW1lbnRlZCBoZXJlIHRvIGdpdmUg YSBnZW5lcmFsIG92ZXJ2aWV3IG9mIHRoZSBsYXJnZXIgcHJvYmxlbS4NCiAgICBUaGlzIGlzIHVz ZWZ1bCBib3RoIHRvIHN0cnVjdHVyZSB3b3JrIHdpdGhpbiB0aGUgSUVURiBhcyB3ZWxsIGFzIHRv IA0KICAgIHVuZGVyc3RhbmQgYmV0dGVyIGhvdyB0byBjb29yZGluYXRlIHdpdGggZXh0ZXJuYWwg b3JnYW5pemF0aW9ucy4NCiAgICA8L3Q+DQoNCiAgICAgIDxzZWN0aW9uIHRpdGxlPSJSZXF1aXJl bWVudHMgbm90YXRpb24iPg0KICAgICAgICA8dD5UaGUga2V5IHdvcmRzICJNVVNUIiwgIk1VU1Qg Tk9UIiwgIlJFUVVJUkVEIiwgIlNIQUxMIiwgIlNIQUxMIE5PVCIsDQogICAgICAgICJTSE9VTEQi LCAiU0hPVUxEIE5PVCIsICJSRUNPTU1FTkRFRCIsICJNQVkiLCBhbmQgIk9QVElPTkFMIiBpbiB0 aGlzDQogICAgICAgIGRvY3VtZW50IGFyZSB0byBiZSBpbnRlcnByZXRlZCBhcyBkZXNjcmliZWQg aW4gPHhyZWYNCiAgICAgICAgdGFyZ2V0PSJSRkMyMTE5Ij48L3hyZWY+LjwvdD4NCiAgICAgIDwv c2VjdGlvbj4NCiAgICA8L3NlY3Rpb24+DQoNCg0KICAgIDxzZWN0aW9uIHRpdGxlPSJPdmVydmll dyI+IA0KICAgIDx0PiANCiAgICBBIExvV1BBTiBpcyBhIHNpbXBsZSBsb3cgY29zdCBjb21tdW5p Y2F0aW9uIG5ldHdvcmsgdGhhdCBhbGxvd3Mgd2lyZWxlc3MNCiAgICBjb25uZWN0aXZpdHkgaW4g YXBwbGljYXRpb25zIHdpdGggbGltaXRlZCBwb3dlciBhbmQgcmVsYXhlZCB0aHJvdWdocHV0IA0K ICAgIHJlcXVpcmVtZW50cy4gQSBMb1dQQU4gdHlwaWNhbGx5IGluY2x1ZGVzIGRldmljZXMgdGhh dCB3b3JrIA0KICAgIHRvZ2V0aGVyIHRvIGNvbm5lY3QgdGhlIHBoeXNpY2FsIGVudmlyb25tZW50 IHRvIHJlYWwtd29ybGQgYXBwbGljYXRpb25zLA0KICAgIGUuZy4sIHdpcmVsZXNzIHNlbnNvcnMu IA0KICAgIExvV1BBTnMgY29uZm9ybSB0byB0aGUgSUVFRSA4MDIuMTUuNC0yMDAzIHN0YW5kYXJk Lg0KICAgIDx4cmVmIHRhcmdldD0iaWVlZTgwMi4xNS40Ij48L3hyZWY+Lg0KICAgIDwvdD4NCiAg ICANCiAgICA8dD4NCiAgICBTb21lIG9mIHRoZSBjaGFyYWN0ZXJpc3RpY3Mgb2YgTG9XUEFOcyBh cmU6DQogICAgICA8dnNwYWNlIGJsYW5rTGluZXM9JzEnIC8+DQoNCiAgICA8bGlzdCBzdHlsZT0i bnVtYmVycyI+DQogICAgPHQ+IFNtYWxsIHBhY2tldCBzaXplLiBHaXZlbiB0aGF0IHRoZSBtYXhp bXVtIHBoeXNpY2FsIGxheWVyIHBhY2tldCANCiAgICAgICBpcyAxMjcgYnl0ZXMsIHRoZSByZXN1 bHRpbmcgbWF4aW11bSBmcmFtZSBzaXplIGF0IHRoZSANCiAgICAgICBtZWRpYSBhY2Nlc3MgY29u dHJvbCBsYXllciBpcyAxMDIgb2N0ZXRzLiBMaW5rLWxheWVyIHNlY3VyaXR5IGltcG9zZXMNCiAg ICAgICBmdXJ0aGVyIG92ZXJoZWFkLCB3aGljaCBpbiB0aGUgbWF4aW11bSBjYXNlICgyMSBvY3Rl dHMgb2YgDQogICAgICAgb3ZlcmhlYWQgaW4gdGhlIEFFUy1DQ00tMTI4IGNhc2UsIHZlcnN1cyA5 IGFuZCAxMyBmb3IgDQogICAgICAgQUVTLUNDTS0zMiBhbmQgQUVTLUNDTS02NCwgcmVzcGVjdGl2 ZWx5KSBsZWF2ZXMgODEgb2N0ZXRzIA0KICAgICAgIGZvciBkYXRhIHBhY2tldHMuDQogICAgICA8 dnNwYWNlIGJsYW5rTGluZXM9JzEnIC8+DQogICAgPC90Pg0KICAgIDx0Pg0KICAgICAgIFN1cHBv cnQgZm9yIGJvdGggMTYtYml0IHNob3J0IG9yIElFRUUgNjQtYml0IGV4dGVuZGVkIG1lZGlhIGFj Y2VzcyBjb250cm9sIA0KICAgICAgIGFkZHJlc3Nlcy4NCiAgICAgIDx2c3BhY2UgYmxhbmtMaW5l cz0nMScgLz4NCiAgICA8L3Q+DQogICAgPHQ+DQogICAgICAgTG93IGJhbmR3aWR0aC4gRGF0YSBy YXRlcyBvZiAyNTAga2JwcywgDQogICAgICAgNDAga2JwcyBhbmQgMjAga2JwcyBmb3IgZWFjaCBv ZiB0aGUgY3VycmVudGx5IGRlZmluZWQgcGh5c2ljYWwgbGF5ZXJzDQogICAgICAgKDIuNCBHSHos IDkxNSBNSHogYW5kIDg2OCBNSHosIHJlc3BlY3RpdmVseSkuDQogICAgICA8dnNwYWNlIGJsYW5r TGluZXM9JzEnIC8+DQogICAgPC90Pg0KICAgIDx0Pg0KICAgICAgIFRvcG9sb2dpZXMgaW5jbHVk ZSBzdGFyIGFuZCBtZXNoIG9wZXJhdGlvbi4NCiAgICAgIDx2c3BhY2UgYmxhbmtMaW5lcz0nMScg Lz4NCiAgICA8L3Q+DQogICAgPHQ+DQogICAgICAgTG93IHBvd2VyLCB0eXBpY2FsbHkgc29tZSBv ciBhbGwgZGV2aWNlcyBhcmUgYmF0dGVyeSBvcGVyYXRlZC4NCiAgICAgIDx2c3BhY2UgYmxhbmtM aW5lcz0nMScgLz4NCiAgICA8L3Q+DQogICAgPHQ+DQogICAgICAgTG93IGNvc3QsIHR5cGljYWxs eSBhc3NvY2lhdGVkIHdpdGggc2Vuc29ycywgc3dpdGNoZXMsIA0KICAgICAgIGV0Yy4gVGhlc2Ug ZHJpdmUgc29tZSBvZiB0aGUgb3RoZXIgY2hhcmFjdGVyaXN0aWNzIHN1Y2ggYXMgbG93DQogICAg ICAgcHJvY2Vzc2luZywgbG93IG1lbW9yeSwgZXRjLiBOdW1lcmljYWwgdmFsdWVzIGZvciAibG93 Ig0KICAgICAgIGhhdmUgbm90IGJlZW4gZXhwbGljaXRseSBtZW50aW9uZWQgaGVyZSBhcyBoaXN0 b3JpY2FsbHkgdGhlIA0KICAgICAgIGNvc3RzIHRlbmQgdG8gY2hhbmdlIG92ZXIgdGltZS4NCiAg ICAgIDx2c3BhY2UgYmxhbmtMaW5lcz0nMScgLz4NCiAgICA8L3Q+DQogICAgPHQ+ICAgICANCgkg ICAgTGFyZ2UgbnVtYmVyIG9mIGRldmljZXMgZXhwZWN0ZWQgdG8gYmUgZGVwbG95ZWQgZHVyaW5n IHRoZSBsaWZlLXRpbWUgb2YNCgkgICAgdGhlIHRlY2hub2xvZ3kuIFRoaXMgbnVtYmVyIGlzIGV4 cGVjdGVkIHRvIGR3YXJmIHRoZSBudW1iZXIgb2YgZGVwbG95ZWQNCgkgICAgcGVyc29uYWwgY29t cHV0ZXJzLCBmb3IgZXhhbXBsZS4NCiAgICAgIDx2c3BhY2UgYmxhbmtMaW5lcz0nMScgLz4NCiAg ICA8L3Q+DQogICAgPHQ+DQogICAgICAgTG9jYXRpb24gb2YgdGhlIGRldmljZXMgYXJlIHR5cGlj YWxseSBub3QgcHJlZGVmaW5lZCwgdGh1cw0KICAgICAgIHRoZXNlIGRldmljZXMgYXJlIGRlcGxv eWVkIGluIGFuIGFkaG9jIGZhc2hpb24uIEZ1cnRoZXJtb3JlLCANCiAgICAgICBzb21ldGltZXMg dGhlIGxvY2F0aW9uIG9mIHRoZXNlIGRldmljZXMgbWF5IG5vdCBiZSBlYXNpbHkNCiAgICAgICBh Y2Nlc3NpYmxlLiBBZGRpdGlvbmFsbHkgdGhlc2UgZGV2aWNlcyBtYXkgbW92ZSB0byBuZXcgbG9j YXRpb25zLg0KICAgICAgPHZzcGFjZSBibGFua0xpbmVzPScxJyAvPg0KICAgIDwvdD4NCiAgICA8 dD4NCiAgICAgICBEZXZpY2VzIHdpdGhpbiBMb1dQQU5zIGhhdmUgYSBoaWdoZXIgcG9zc2liaWxp dHkgb2YgYmVpbmcgDQogICAgICAgdW5yZWxpYWJsZSBkdWUgdG8gdmFyaWV0eSBvZiByZWFzb25z Og0KICAgICAgIHVuY2VydGFpbiByYWRpbyBjb25uZWN0aXZpdHksIGJhdHRlcnkgZHJhaW4sIGRl dmljZSBsb2NrdXBzLCANCiAgICAgICBwaHlzaWNhbCB0YW1wZXJpbmcsIGV0Yy4NCiAgICA8L3Q+ DQogICAgPHQ+DQogICAgICAgRGV2aWNlcyB3aXRoaW4gTG9XUEFOcyBoYXZlIGEgaGlnaGVyIHBv c3NpYmlsaXR5IG9mIGJlaW5nIA0KICAgICAgIHVuYXZhaWxhYmxlIGJlY2F1c2Ugb2Z0ZW4gdGhl c2UgZGV2aWNlcyBhcmUgaW4gc2xlZXAgbW9kZSBvcg0KICAgICAgIGluIGEgcG93ZXIgZG93biBt b2RlIHRvIGNvbnNlcnZlIHBvd2VyLg0KICAgIDwvdD4NCiAgICA8L2xpc3Q+ICAgICAgIA0KICAg IDwvdD4NCg0KICAgIDx0PiANCiAgICBUaGUgZm9sbG93aW5nIHNlY3Rpb25zIHRha2UgaW50byBh Y2NvdW50IHRoZXNlIGNoYXJhY3RlcmlzdGljcyANCiAgICBpbiBkZXNjcmliaW5nIHRoZSAgYXNz dW1wdGlvbnMsIHByb2JsZW1zIHN0YXRlbWVudCBhbmQgDQogICAgZ29hbHMgZm9yIExvV1BBTnMu DQogICAgPC90Pg0KICAgIDwvc2VjdGlvbj4NCiAgICANCiAgICA8c2VjdGlvbiB0aXRsZT0iQXNz dW1wdGlvbnMiPg0KICAgIDx0Pg0KICAgIEdpdmVuIHRoZSBzbWFsbCBwYWNrZXQgc2l6ZSBvZiBM b1dQQU5zLCB0aGlzIGRvY3VtZW50IHByZXN1bWVzIA0KICAgIGFwcGxpY2F0aW9ucyB0eXBpY2Fs bHkgc2VuZCBzbWFsbCBhbW91bnRzIG9mIGRhdGEuIEhvd2V2ZXIsIA0KICAgIHRoZSBwcm90b2Nv bHMgdGhlbXNlbHZlcyBkbyBub3QgcmVzdHJpY3QgYnVsayBkYXRhIHRyYW5zZmVycy4gDQogICAg PC90PiAgIA0KICAgIDx0Pg0KICAgIExvV1BBTnMgYXMgZGVzY3JpYmVkIGluIHRoaXMgZG9jdW1l bnQgYXJlIGJhc2VkIG9uIA0KICAgIElFRUUgODAyLjE1LjQtMjAwMy4gSXQgaXMgcG9zc2libGUg dGhhdCB0aGUgc3BlY2lmaWNhdGlvbg0KICAgIG1heSB1bmRlcmdvIGNoYW5nZXMgaW4gdGhlIGZ1 dHVyZSBhbmQgbWF5IGNoYW5nZSBzb21lIG9mIHRoZSANCiAgICByZXF1aXJlbWVudHMgbWVudGlv bmVkIGFib3ZlLg0KICAgIDwvdD4NCiAgICA8dD4NCiAgICBTb21lIG9mIHRoZXNlIGFzc3VtcHRp b25zIGFyZSBiYXNlZCBvbiB0aGUgbGltaXRlZCBjYXBhYmlsaXRpZXMgb2YNCiAgICBkZXZpY2Vz IHdpdGhpbiBMb1dQQU5zLiBBcyBkZXZpY2VzIGJlY29tZSBtb3JlIHBvd2VyZnVsLCBhbmQNCiAg ICBjb25zdW1lIGxlc3MgcG93ZXIsIHNvbWUgb2YgdGhlIHJlcXVpcmVtZW50cyBtZW50aW9uZWQg YWJvdmUgbWF5IGJlDQogICAgc29tZXdoYXQgcmVsYXhlZC4NCiAgICA8L3Q+DQoNCjx0Pg0KCU5l dmVydGhlbGVzcywgbm90IGFsbCBkZXZpY2VzIGluIGEgTG9XUEFOIGFyZSBleHBlY3RlZCB0byAN CgliZSBleHRyZW1lbHkgbGltaXRlZC4gVGhpcyBpcyB0cnVlIG9mIHNvLWNhbGxlZCAiUmVkdWNl ZCBGdW5jdGlvbg0KCURldmljZXMiIChSRkRzKSwgYnV0IG5vdCBuZWNlc3NhcmlseSBvZiAiRnVs bCBGdW5jdGlvbiBEZXZpY2VzIiAoRkZEcykuDQoJVGhlc2Ugd2lsbCBhbHNvIGJlIHByZXNlbnQg YWxiZWl0IGluIG11Y2ggc21hbGxlciBudW1iZXJzLCBhbmQgd2lsbCANCgl0eXBpY2FsbHkgaGF2 ZSBtb3JlIHJlc291cmNlcyBhbmQgYmUgbWFpbnMgcG93ZXJlZC4gQWNjb3JkaW5nbHksDQoJRkZE cyB3aWxsIGFpZCBSRkRzIGJ5IHByb3ZpZGluZyBmdW5jdGlvbnMgc3VjaCBhcyBuZXR3b3JrIGNv b3JkaW5hdGlvbiwNCglwYWNrZXQgZm9yd2FyZGluZywgaW50ZXJmYWNpbmcgd2l0aCBvdGhlciB0 eXBlcyBvZiBuZXR3b3JrcywgZXRjLg0KPC90Pg0KICAgIDx0Pg0KICAgIElQIHRlY2hub2xvZ3kg aXMgYXNzdW1lZCB0byBwcm92aWRlIHRoZSBmb2xsb3dpbmcgYmVuZWZpdHM6DQoJPHZzcGFjZSBi bGFua0xpbmVzPScxJyAvPg0KDQogICAgPGxpc3Qgc3R5bGU9Im51bWJlcnMiPg0KICAgIDx0Pg0K ICAgICAgIFRoZSBwZXJ2YXNpdmUgbmF0dXJlIG9mIElQIG5ldHdvcmtzIGFsbG93cyB1c2Ugb2Yg ZXhpc3RpbmcgDQogICAgICAgaW5mcmFzdHJ1Y3R1cmUuDQogICAgPC90Pg0KICAgIDx0Pg0KICAg ICAgIElQIGJhc2VkIHRlY2hub2xvZ2llcyBhbHJlYWR5IGV4aXN0LCBhcmUgd2VsbCBrbm93biBh bmQgDQogICAgICAgcHJvdmVuIHRvIGJlIHdvcmtpbmcuDQogICAgPC90Pg0KICAgIDx0PiBBbiBh ZG1pdHRlZGx5IG5vbi10ZWNobmljYWwgYnV0IGltcG9ydGFudCBjb25zaWRlcmF0aW9uIGlzIA0K CSAgICB0aGF0IGludGVsbGVjdHVhbCBwcm9wZXJ0eSBjb25kaXRpb25zIGZvciANCiAgICAgICBJ UCBuZXR3b3JraW5nIHRlY2hub2xvZ3kgYXJlIGVpdGhlciBtb3JlIGZhdm9yYWJsZSBvciBhdCAN CiAgICAgICBsZWFzdCBiZXR0ZXIgdW5kZXJzdG9vZCB0aGFuIHByb3ByaWV0YXJ5IGFuZCBuZXdl ciBzb2x1dGlvbnMuIA0KICAgIDwvdD4NCiAgIDx0PiBUb29scyBmb3IgZGlhZ25vc3RpY3MsIG1h bmFnZW1lbnQgYW5kIGNvbW1pc3Npb25pbmcgb2YgSVAgbmV0d29ya3MNCiAgICAgICBhbHJlYWR5 IGV4aXN0cy4NCiAgICA8L3Q+DQogICA8dD4gSVAgYmFzZWQgZGV2aWNlcyBjYW4gbW9yZSBlYXNp bHkgYmUgY29ubmVjdGVkIHRvIG90aGVyIElQIGJhc2VkIG5ldHdvcmtzLCB3aXRob3V0IA0KICAg ICAgIHRoZSBuZWVkIGZvciB0cmFuc2xhdGlvbiBnYXRld2F5cyBhbmQgdGhlIGxpa2UuDQogICAg PC90Pg0KDQogICAgPC9saXN0Pg0KICAgIDwvdD4NCiAgICA8L3NlY3Rpb24+DQogICAgDQo8c2Vj dGlvbiB0aXRsZT0iUHJvYmxlbXMiPg0KICAgIDx0Pg0KCUJhc2VkIG9uIHRoZSBjaGFyYWN0ZXJp c3RpY3MgZGVmaW5lZCBpbiB0aGUgb3ZlcnZpZXcgc2VjdGlvbiwgdGhlDQoJZm9sbG93aW5nIHNl Y3Rpb25zIGVsYWJvcmF0ZSBvbiB0aGUgbWFpbiBwcm9ibGVtcyB3aXRoIElQIGZvciBMb1dQQU5z DQoJTm90ZSB0aGF0IGEgY29tbW9uIHVuZGVybHlpbmcgZ29hbCBpcyB0byByZWR1Y2UNCglwYWNr ZXQgb3ZlcmhlYWQsIGJhbmR3aWR0aCBjb25zdW1wdGlvbiwgYW5kIHByb2Nlc3NpbmcgcmVxdWly ZW1lbnRzLg0KCTwvdD4NCgkNCgk8c2VjdGlvbiB0aXRsZT0iSVAgQ29ubmVjdGl2aXR5Ij4NCiAg ICA8dD4NCiAgICBUaGUgcmVxdWlyZW1lbnQgZm9yIElQIGNvbm5lY3Rpdml0eSANCiAgICB3aXRo aW4gYSBMb1dQQU4gaXMgZHJpdmVuIGJ5IHRoZSBmb2xsb3dpbmc6DQoJPHZzcGFjZSBibGFua0xp bmVzPScxJyAvPg0KDQogICAgPGxpc3Qgc3R5bGU9Im51bWJlcnMiPiANCiAgICA8dD4NCgkgICAg VGhlIG1hbnkgZGV2aWNlcyBpbiBhIExvV1BBTiBtYWtlIG5ldHdvcmsgYXV0byBjb25maWd1cmF0 aW9uDQogICAgICAgYW5kIHN0YXRlbGVzc25lc3MgaGlnaGx5IGRlc2lyYWJsZS4gQW5kIGZvciB0 aGlzLCBJUHY2IGhhcw0KICAgICAgIHJlYWR5IHNvbHV0aW9ucy4gDQogICAgPC90Pg0KICAgIDx0 Pg0KCSAgVGhlIGxhcmdlIG51bWJlciBvZiBkZXZpY2VzIA0KCSAgICBwb3NlcyB0aGUgbmVlZCBm b3IgYSBsYXJnZSBhZGRyZXNzIHNwYWNlLA0KICAgICAgIHdlbGwgbWV0IGJ5IElQdjYuDQogICAg PC90Pg0KICAgIDx0Pg0KICAgICAgIEdpdmVuIHRoZSBsaW1pdGVkIHBhY2tldCBzaXplIG9mIExv V1BBTnMsIHRoZSBJUHY2IGFkZHJlc3MgZm9ybWF0IA0KICAgICAgIGFsbG93cyBzdWJzdW1pbmcg b2YgSUVFRSA4MDIuMTUuNCBhZGRyZXNzZXMgaWYgc28gZGVzaXJlZC4NCiAgICA8L3Q+DQogICAg PHQ+DQoJU2ltcGxlIGludGVyY29ubmVjdGl2aXR5IHRvIG90aGVyIElQIG5ldHdvcmtzIGluY2x1 ZGluZyB0aGUgSW50ZXJuZXQuDQogICAgPC90Pg0KICAgIDwvbGlzdD4NCiAgICA8L3Q+DQogICAg DQogICAgPHQ+DQogICAgSG93ZXZlciwgZ2l2ZW4gdGhlIGxpbWl0ZWQgcGFja2V0IHNpemUsDQog ICAgaGVhZGVycyBmb3IgSVB2NiBhbmQgYWJvdmUgbGF5ZXJzIG11c3QgYmUgY29tcHJlc3NlZCB3 aGVuZXZlciANCiAgICBwb3NzaWJsZS4NCiAgICA8L3Q+DQogICAgDQogICAgPC9zZWN0aW9uPgkN CiAgICANCiAgICA8c2VjdGlvbiB0aXRsZT0iVG9wb2xvZ2llcyI+DQogICAgPHQ+DQoJICAgIExv V1BBTnMgbXVzdA0KCSAgICBzdXBwb3J0IHZhcmlvdXMgdG9wb2xvZ2llcw0KICAgIGluY2x1ZGlu ZyBtZXNoIGFuZCBzdGFyLg0KICAgIDwvdD4NCiAgICANCiAgICA8dD4NCiAgICBNZXNoIHRvcG9s b2dpZXMgaW1wbHkgbXVsdGktaG9wIHJvdXRpbmcsDQogICAgdG8gYSBkZXNpcmVkIGRlc3RpbmF0 aW9uLiBJbiB0aGlzIGNhc2UsDQogICAgaW50ZXJtZWRpYXRlIGRldmljZXMgYWN0IGFzIHBhY2tl dCBmb3J3YXJkZXJzIGF0IHRoZSBsaW5rIGxheWVyDQogICAgKGFraW4gdG8gcm91dGVycyBhdCB0 aGUgbmV0d29yayBsYXllcikuIA0KICAgIFR5cGljYWxseSB0aGVzZSBhcmUgImZ1bGwgZnVuY3Rp b24gZGV2aWNlcyIgDQogICAgdGhhdCBoYXMgbW9yZSBjYXBhYmlsaXRpZXMgaW4gdGVybXMgb2Yg cG93ZXIsIGNvbXB1dGF0aW9uLCBldGMuIA0KICAgIFRoZSByZXF1aXJlbWVudHMgdGhhdCBhcHBs eSBvbiB0aGUgY2hvc2VuIHJvdXRpbmcgcHJvdG9jb2wgYXJlOg0KCTx2c3BhY2UgYmxhbmtMaW5l cz0nMScgLz4NCg0KICAgIDxsaXN0IHN0eWxlPSJudW1iZXJzIj4NCiAgICA8dD4gICANCiAgICAg ICBHaXZlbiB0aGUgbWluaW1hbCBwYWNrZXQgc2l6ZSBvZiBMb1dQQU5zLCB0aGUgcm91dGluZyBw cm90b2NvbCANCiAgICAgICBtdXN0IGltcG9zZSBsb3cgKG9yIG5vKSBvdmVyaGVhZCBvbiBkYXRh IHBhY2tldHMsIGhvcGVmdWxseQ0KICAgICAgIGluZGVwZW5kZW50bHkgb2YgdGhlIG51bWJlciBv ZiBob3BzLiAgDQogICAgPC90Pg0KICAgIDx0Pg0KICAgICAgIFRoZSByb3V0aW5nIHByb3RvY29s cyBzaG91bGQgaGF2ZSBsb3cgcm91dGluZyBvdmVyaGVhZCANCiAgICAgICAobGVzcyBjaGF0dHkp IGJhbGFuY2VkIHdpdGggdG9wb2xvZ3kgY2hhbmdlcyBhbmQgcG93ZXIgDQogICAgICAgY29uc2Vy dmF0aW9uLg0KICAgIDwvdD4NCiAgICA8dD4NCiAgICAgICBUaGUgY29tcHV0YXRpb24gYW5kIG1l bW9yeSByZXF1aXJlbWVudHMgaW4gdGhlIHJvdXRpbmcgcHJvdG9jb2wgDQogICAgICAgc2hvdWxk IGJlIG1pbmltYWwgdG8gc2F0aXNmeSBsb3cgY29zdCBhbmQgbG93IHBvd2VyDQogICAgICAgY2hh cmFjdGVyaXN0aWNzLiBUaHVzIHN0b3JhZ2UgYW5kIG1haW50YWluaW5nIG9mIGxhcmdlIHJvdXRp bmcNCiAgICAgICB0YWJsZXMgbWF5IGJlIGRldHJpbWVudGFsLg0KICAgIDwvdD4NCiAgICA8L2xp c3Q+DQogICAgPC90Pg0KICAgIDx0Pg0KICAgIEFzIHdpdGggbWVzaCB0b3BvbG9naWVzLCBzdGFy IHRvcG9sb2dpZXMgaW5jbHVkZSBwcm92aXNpb25pbmcgYSBzdWJzZXQgb2YgZGV2aWNlcyB3aXRo IHBhY2tldA0KICAgIGZvcndhcmRpbmcgZnVuY3Rpb25hbGl0eS4gDQogICAgSWYsIGluIGFkZGl0 aW9uIHRvIElFRUUgODAyLjE1LjQsICB0aGVzZSBkZXZpY2VzIHVzZSBvdGhlciBraW5kcyBvZiBu ZXR3b3JrDQogICAgaW50ZXJmYWNlcyBzdWNoIGFzIGV0aGVybmV0LCBJRUVFIDgwMi4xMSwgZXRj LiwgdGhlIGdvYWwgaXMgdG8gc2VhbWxlc3NseQ0KICAgIGludGVncmF0ZSB0aGUgbmV0d29ya3Mg YnVpbHQgb3ZlciB0aG9zZSBkaWZmZXJlbnQgdGVjaG5vbG9naWVzLg0KICAgIFRoaXMsIG9yIGNv dXJzZSwgaXMgYSBwcmltYXJ5IG1vdGl2YXRpb24gdG8gdXNlIElQIHRvIGJlZ2luIHdpdGguDQog ICAgPC90Pg0KICAgIA0KICAgIDwvc2VjdGlvbj4NCiAgICANCiAgICA8c2VjdGlvbiB0aXRsZT0i TGltaXRlZCBQYWNrZXQgU2l6ZSI+DQogICAgPHQ+DQogICAgQXBwbGljYXRpb25zIHdpdGhpbiBM b1dQQU5zIGFyZSBleHBlY3RlZCB0byBvcmlnaW5hdGUgc21hbGwgcGFja2V0cy4NCiAgICBBZGRp bmcgYWxsIGxheWVycyBmb3IgSVAgY29ubmVjdGl2aXR5IHNob3VsZCBzdGlsbCBhbGxvdyB0cmFu c21pc3Npb24NCiAgICBpbiBvbmUgZnJhbWUgd2l0aG91dCBpbmN1cnJpbmcgDQogICAgZXhjZXNz aXZlIGZyYWdtZW50YXRpb24gYW5kIHJlYXNzZW1ibHkuIEZ1cnRoZXJtb3JlLCANCiAgICBwcm90 b2NvbHMgbXVzdCBiZSBkZXNpZ25lZCBvciBjaG9zZW4gc28gdGhhdCB0aGUgaW5kaXZpZHVhbCAN CiAgICAiY29udHJvbC9wcm90b2NvbCBwYWNrZXRzIiBmaXQgd2l0aGluIGEgc2luZ2xlIDgwMi4x NS40IGZyYW1lLg0KICAgIDwvdD4NCiAgICA8L3NlY3Rpb24+DQogICAgDQogICAgPHNlY3Rpb24g dGl0bGU9IkxpbWl0ZWQgY29uZmlndXJhdGlvbiBhbmQgbWFuYWdlbWVudCI+DQogICAgPHQ+DQoJ ICAgIEFzIGFsbHVkZWQgdG8gYWJvdmUsIGRldmljZXMgd2l0aGluIExvV1BBTnMgYXJlIGV4cGVj dGVkIHRvIGJlIGRlcGxveWVkIGluIA0KCSAgICBleGNlZWRpbmdseSBsYXJnZSBudW1iZXJzLiAN CgkgICAgQWRkaXRpb25hbGx5LCB0aGV5IGFyZSBleHBlY3RlZCB0byBoYXZlIGxpbWl0ZWQgZGlz cGxheSBhbmQgaW5wdXQgDQogICAgY2FwYWJpbGl0aWVzLiBGdXJ0aGVybW9yZSwgdGhlIGxvY2F0 aW9uIG9mIHNvbWUgb2YgdGhlc2UgZGV2aWNlcyBtYXkgDQogICAgYmUgaGFyZCB0byBhY2Nlc3Mu IEFzIHN1Y2gsIHByb3RvY29scyBkZXNpZ25lZCBmb3IgTG9XUEFOcyBzaG91bGQgaGF2ZQ0KICAg IG1pbmltYWwgY29uZmlndXJhdGlvbiwgcHJlZmVyYWJseSB3b3JrICJvdXQgb2YgdGhlIGJveCIs IHByb3ZpZGUNCiAgICBlYXN5IGJvb3RzdHJhcHBpbmcsIGFuZCB0aGUgbmV0d29yayBzaG91bGQg YmUgYWJsZSB0byBzZWxmIGhlYWwgZ2l2ZW4gdGhlIA0KICAgIGluaGVyZW50IHVucmVsaWFibGUg Y2hhcmFjdGVyaXN0aWMgb2YgdGhlc2UgZGV2aWNlcy4gVGhlIA0KICAgIG5ldHdvcmsgbWFuYWdl bWVudCBzaG91bGQgaGF2ZSBsZXNzIG92ZXJoZWFkIHlldCBiZSBwb3dlcmZ1bCANCiAgICB0byBj b250cm9sIGRlbnNlIGRlcGxveW1lbnQgb2YgZGV2aWNlcy4NCiAgICA8L3Q+DQogICAgPC9zZWN0 aW9uPg0KICAgIA0KICAgIDxzZWN0aW9uIHRpdGxlPSJTZXJ2aWNlIGRpc2NvdmVyeSI+DQogICAg PHQ+DQogICAgTG9XUEFOcyByZXF1aXJlIHNpbXBsZSBzZXJ2aWNlIGRpc2NvdmVyeSBuZXR3b3Jr IHByb3RvY29scyB0bw0KICAgIGRpc2NvdmVyLCBjb250cm9sIGFuZCBtYWludGFpbiBzZXJ2aWNl cyBwcm92aWRlZCBieSBkZXZpY2VzLiANCiAgICBJbiBzb21lIGNhc2VzLCBlc3BlY2lhbGx5IGlu IGRlbnNlIGRlcGxveW1lbnRzLCBhYnN0cmFjdGlvbiBvZg0KICAgIHNldmVyYWwgbm9kZXMgdG8g cHJvdmlkZSBhIHNlcnZpY2UgbWF5IGJlIGJlbmVmaWNpYWwuIEluIA0KICAgIG9yZGVyIHRvIGVu YWJsZSBzdWNoIGZlYXR1cmVzLCBuZXcgcHJvdG9jb2xzIG1heSBoYXZlIA0KICAgIHRvIGJlIGRl c2lnbmVkLiANCiAgICA8L3Q+DQogICAgPC9zZWN0aW9uPg0KICAgIA0KICAgIDxzZWN0aW9uIHRp dGxlPSJTZWN1cml0eSI+DQogICAgPHQ+DQogICAgU2VjdXJpdHkgZm9yIExvV1BBTiBkZXZpY2Vz IG11c3QgYmUgY2FyZWZ1bGx5IGNvbnNpZGVyZWQgDQogICAgZGVwZW5kaW5nIHVwb24gdGhlIGFw cGxpY2F0aW9uIG5lZWRzLiBJRUVFIDgwMi4xNS40IHByb3ZpZGVzIA0KICAgIEFFUyBsaW5rIGxh eWVyIHNlY3VyaXR5LiBEdWUgdG8gdGhlIG5hdHVyZSBvZiA2TG9XUEFOIGRldmljZXMsDQogICAg c2VjdXJpdHkgc29sdXRpb25zIHRoYXQgbmVlZCBleGNlc3NpdmUgY29tcHV0aW5nLCBvciBiYW5k d2lkdGggDQogICAgbWF5IG5vdCBiZSBzdWl0YWJsZSBmb3IgTG9XUEFOIGRldmljZXMuIA0KICAg IFBsZWFzZSByZWZlciB0byBzZWN1cml0eSBjb25zaWRlcmF0aW9uIHNlY3Rpb24gYmVsb3cgZm9y IGFuIGluIGRlcHRoIA0KICAgIHJlcXVpcmVtZW50cyBmb3Igc2VjdXJpdHkuDQogICAgPC90Pg0K ICAgIDwvc2VjdGlvbj4NCiAgICANCiAgICA8L3NlY3Rpb24+DQogICAgDQogICAgPHNlY3Rpb24g dGl0bGU9IkdvYWxzIj4NCiAgICA8dD4NCiAgICBHb2FscyBtZW50aW9uZWQgaGVyZSBtYXkgcG9p bnQgYXQgcmVsZXZhbnQgd29yayB0aGF0IGNhbiBiZSBkb25lIA0KICAgIHdpdGhpbiB0aGUgSUVU RiAoZS5nLiwgc3BlY2lmaWNhdGlvbiByZXF1aXJlZCB0byB0cmFuc21pdCBJUCwgDQogICAgcHJv ZmlsZSBvZiBiZXN0IHByYWN0aWNlcyBmb3IgdHJhbnNtaXR0aW5nIElQIHBhY2tldHMsIA0KICAg IGFuZCBhc3NvY2lhdGVkIHVwcGVyIGxldmVsIHByb3RvY29scywgZXRjKS4gSXQgbWF5IA0KICAg IGFsc28gcG9pbnQgYXQgd29yayB0byBiZSBkb25lIGluIG90aGVyIHN0YW5kYXJkcyBib2RpZXMg dGhhdA0KICAgIGV4aXN0IG9yIG1heSBleGlzdCBpbiB0aGUgZnV0dXJlIChlLmcuLCBkZXNpcmFi bGUgY2hhbmdlcyBvciANCiAgICBwcm9maWxlcyByZWxldmFudCB0byBJRUVFIDgwMi4xNS40LCBX M0MsIGV0YykuIFdoZW4gdGhlIGdvYWxzIGZhbGwgdW5kZXIgDQogICAgdGhlIElFVEYncyBwdXJ2 aWV3LCB0aGV5IHNlcnZlIHRvIHBvaW50IG91dCB3aGF0IHRob3NlIGVmZm9ydHMgDQogICAgc2hv dWxkIHN0cml2ZSB0byBhY2NvbXBsaXNoLiBSZWdhcmRsZXNzIG9mIHdoZXRoZXIgdGhleSBhcmUN CiAgICBwdXJzdWVkIHdpdGhpbiBvbmUgKG9yIG1vcmUpIG5ldyAob3IgZXhpc3RpbmcpIHdvcmtp bmcgZ3JvdXBzLg0KICAgIFdoZW4gdGhlIGdvYWxzIGRvIG5vdCBmYWxsIHVuZGVyIHRoZSANCiAg ICBwdXJ2aWV3IG9mIHRoZSBJRVRGLCBkb2N1bWVudGluZyB0aGVtIGhlcmUgc2VydmVzIGFzIGlu cHV0IHRvIA0KICAgIHRob3NlIG90aGVyIG9yZ2FuaXphdGlvbnMgPHhyZWYgdGFyZ2V0PSJsaWFp c29uIj48L3hyZWY+LiANCiAgICA8L3Q+DQogICAgIA0KICAgIDx0Pg0KICAgIFRoZSBmb2xsb3dp bmcgYXJlIHRoZSBnb2FscyBhY2NvcmRpbmcgdG8gcHJpb3JpdHkgZm9yIExvV1BBTnM6IA0KCTx2 c3BhY2UgYmxhbmtMaW5lcz0nMScgLz4NCg0KICAgIDxsaXN0IHN0eWxlPSJudW1iZXJzIj4gICAN CiAgICAgIDx0Pg0KCSAgICAgIEFzIG1lbnRpb25lZCBpbiB0aGUgb3ZlcnZpZXcsIHRoZSBwcm90 b2NvbCBkYXRhIHVuaXRzIG1heSBiZSBhcyBzbWFsbCANCgkgICAgICA4MSBieXRlcy4NCgkgICAg ICBUaGlzIGlzDQogICAgICBvYnZpb3VzbHkgZmFyIGJlbG93IHRoZSBtaW5pbXVtIElQdjYgcGFj a2V0IHNpemUgb2YgMTI4MCBvY3RldHMsIGFuZCBpbg0KICAgICAga2VlcGluZyB3aXRoIHNlY3Rp b24gNSBvZiB0aGUgSVB2NiBzcGVjaWZpY2F0aW9uIDx4cmVmDQogICAgICB0YXJnZXQ9IlJGQzI0 NjAiPjwveHJlZj4sIGEgZnJhZ21lbnRhdGlvbiBhbmQgcmVhc3NlbWJseSBhZGFwdGF0aW9uIGxh eWVyDQogICAgICBtdXN0IGJlIHByb3ZpZGVkIGF0IHRoZSBsYXllciBiZWxvdyBJUC4NCiAgICAg IDx2c3BhY2UgYmxhbmtMaW5lcz0nMScgLz4NCiAgICAgIDwvdD4NCiAgICAgIA0KICAgICAgPHQ+ DQogICAgICBHaXZlbiB0aGF0IGluIHRoZSB3b3JzdCBjYXNlIHRoZSBtYXhpbXVtIHNpemUgYXZh aWxhYmxlIGZvciB0cmFuc21pdHRpbmcgSVAgcGFja2V0cyBvdmVyIA0KICAgICAgSUVFRSA4MDIu MTUuNCBmcmFtZSBpcyA4MSBvY3RldHMsIGFuZCB0aGF0IHRoZSBJUHY2IGhlYWRlciBpcyA0MCBv Y3RldHMgbG9uZywNCiAgICAgICh3aXRob3V0IG9wdGlvbmFsIGhlYWRlcnMpLCB0aGlzIGxlYXZl cyBvbmx5IDQxIG9jdGV0cyBmb3IgDQogICAgICB1cHBlci1sYXllciBwcm90b2NvbHMsIGxpa2Ug VURQIGFuZCBUQ1AuIFVEUCB1c2VzIDggb2N0ZXRzIGluIHRoZSBoZWFkZXINCiAgICAgIGFuZCBU Q1AgdXNlcyAyMCBvY3RldHMuIFRoaXMgbGVhdmVzIDMzIG9jdGV0cyBmb3IgZGF0YSBvdmVyIFVE UCBhbmQgMjEgDQogICAgICBvY3RldHMgZm9yIGRhdGEgb3ZlciBUQ1AuIEFkZGl0aW9uYWxseSwg YXMgcG9pbnRlZCBhYm92ZSwgdGhlcmUgaXMgYWxzbyANCiAgICAgIGEgbmVlZCBmb3IgYSBmcmFn bWVudGF0aW9uIGFuZCByZWFzc2VtYmx5IGxheWVyLCB3aGljaCB3aWxsIHVzZSBldmVuIG1vcmUg DQogICAgICBvY3RldHMgbGVhdmluZyB2ZXJ5IGZldyBvY3RldHMgZm9yIGRhdGEuIFRodXMgaWYg b25lIHdlcmUgdG8gdXNlIHRoZSANCiAgICAgIHByb3RvY29scyBhcyBpcywgaXQgd291bGQgbGVh ZCB0byBleGNlc3NpdmUgZnJhZ21lbnRhdGlvbiBhbmQgcmVhc3NlbWJseSANCiAgICAgIGV2ZW4g d2hlbiBkYXRhIHBhY2tldHMgYXJlIGp1c3QgMTBzIG9mIG9jdGV0cyBsb25nLiBUaGlzIHBvaW50 cyB0byB0aGUgbmVlZA0KICAgICAgZm9yIGhlYWRlciBjb21wcmVzc2lvbiANCiAgICAgIEFzIHRo ZXJlIGlzIG11Y2ggcHVibGlzaGVkIGFuZCBpbi1wcm9ncmVzcyANCiAgICAgIHN0YW5kYXJkaXph dGlvbiB3b3JrIG9uIGhlYWRlciBjb21wcmVzc2lvbiwgdGhpcyBnb2FsIG5lZWRzIHRvIGludmVz dGlnYXRlIA0KICAgICAgdXNpbmcgZXhpc3RpbmcgaGVhZGVyIGNvbXByZXNzaW9uIHRlY2huaXF1 ZXMgYW5kIGlmIG5lY2Vzc2FyeSBzcGVjaWZ5IA0KICAgICAgbmV3IG9uZXMuDQogICAgICA8dnNw YWNlIGJsYW5rTGluZXM9JzEnIC8+DQogICAgICA8L3Q+DQogICAgDQogICAgICA8dD4NCiAgICAg IDx4cmVmIHRhcmdldD0iSS1ELmlldGYtaXB2Ni1yZmMyNDYyYmlzIiAvPiBzcGVjaWZ5IG1ldGhv ZHMgZm9yIGNyZWF0aW5nIA0KICAgICAgSVB2NiBzdGF0ZWxlc3MgYWRkcmVzcyBhdXRvIGNvbmZp Z3VyYXRpb24uIFN0YXRlbGVzcyBhdXRvIGNvbmZpZ3VyYXRpb24NCiAgICAgIGhhcyBhbiBhZHZh bnRhZ2Ugb3ZlciBzdGF0ZWZ1bCBieSBoYXZpbmcgbGVzcyBjb25maWd1cmF0aW9uIG92ZXJoZWFk IA0KICAgICAgb24gdGhlIGhvc3RzIHN1aXRhYmxlIGZvciBMb1dQQU5zLiBUaGUgZ29hbCBzaG91 bGQgc3BlY2lmeSBhIG1ldGhvZA0KICAgICAgdG8gZ2VuZXJhdGUgYW4gImludGVyZmFjZSBpZGVu dGlmaWVyIiBmcm9tIHRoZSBFVUktNjQgDQogICAgICA8eHJlZiB0YXJnZXQ9IkVVSTY0Ii8+IGFz c2lnbmVkIHRvIHRoZSBJRUVFIDgwMi4xNS40IGRldmljZS4NCiAgICAgIDx2c3BhY2UgYmxhbmtM aW5lcz0nMScgLz4NCiAgICAgIDwvdD4NCiAgICAgIA0KICAgICAgPHQ+DQoJICAgICAgQSByb3V0 aW5nIHByb3RvY29sIHRvDQogICAgICBzdXBwb3J0IGEgbXVsdGktaG9wIG1lc2ggbmV0d29yayBp cyBuZWNlc3NhcnkuIFRoZXJlIGlzIG11Y2gNCiAgICAgIHB1Ymxpc2hlZCB3b3JrIG9uIGFkaG9j IG11bHRpIGhvcCByb3V0aW5nIGZvciBkZXZpY2VzLiBTb21lIGV4YW1wbGVzDQogICAgICBpbmNs dWRlIDx4cmVmIHRhcmdldD0iUkZDMzU2MSI+PC94cmVmPiwgPHhyZWYgdGFyZ2V0PSJSRkMzNjI2 Ij48L3hyZWY+LCANCiAgICAgIDx4cmVmIHRhcmdldD0iUkZDMzY4NCI+PC94cmVmPiwgYWxsDQog ICAgICBleHBlcmltZW50YWwuIEFsc28sIHRoZXNlIHByb3RvY29scyBhcmUgZGVzaWduZWQgdG8g dXNlIElQIGJhc2VkIA0KICAgICAgYWRkcmVzc2VzIHRoYXQgaGF2ZSBsYXJnZSBvdmVyaGVhZHMu IEZvciBleGFtcGxlLCB0aGUgQU9EViANCiAgICAgIDx4cmVmIHRhcmdldD0iUkZDMzU2MSI+PC94 cmVmPiByb3V0aW5nIHByb3RvY29sIHVzZXMgNDggb2N0ZXRzIA0KICAgICAgZm9yIGEgcm91dGUg cmVxdWVzdCBiYXNlZCBvbiBJUHY2IGFkZHJlc3NpbmcuIEdpdmVuIHRoZSBwYWNrZXQNCiAgICAg IHNpemUgY29uc3RyYWludHMsIHRyYW5zbWl0dGluZyB0aGlzIHBhY2tldCB3aXRob3V0IA0KICAg ICAgZnJhZ21lbnRhdGlvbiBhbmQgcmVhc3NlbWJseSBtYXkgYmUgZGlmZmljdWx0LiBUaHVzIGNh cmUgc2hvdWxkIGJlIHRha2VuIHdoZW4gDQogICAgICB1c2luZyBleGlzdGluZyBwcm90b2NvbHMg b3IgZGVzaWduaW5nIG5ldyBwcm90b2NvbHMgZm9yIHJvdXRpbmcgDQogICAgICBzbyB0aGF0IHRo ZSByb3V0aW5nIHBhY2tldHMgZml0IHdpdGhpbiBhIHNpbmdsZSBJRUVFIDgwMi4xNS40IA0KICAg ICAgZnJhbWUuIA0KICAgICAgPHZzcGFjZSBibGFua0xpbmVzPScxJyAvPg0KICAgICAgPC90Pg0K ICAgIA0KICAgICAgPHQ+DQogICAgICBPbmUgb2YgdGhlIHBvaW50cyBvZiB0cmFuc21pdHRpbmcg SVB2NiBwYWNrZXRzLCBpcyB0byByZXVzZSANCiAgICAgIGV4aXN0aW5nIHByb3RvY29scyBhcyBt dWNoIGFzIHBvc3NpYmxlLiBOZXR3b3JrIG1hbmFnZW1lbnQgDQogICAgICBmdW5jdGlvbmFsaXR5 IGlzIGNyaXRpY2FsIGZvciBMb1dQQU5zLiA8eHJlZiB0YXJnZXQ9IlJGQzM0MTEiPjwveHJlZj4g DQogICAgICBzcGVjaWZpZXMgU05NUHYzIHByb3RvY29sIG9wZXJhdGlvbnMuIFNOTVAgZnVuY3Rp b25hbGl0eQ0KICAgICAgbWF5IGJlIHRyYW5zbGF0ZWQgImFzIGlzIiB0byBMb1dQQU5zLiBIb3dl dmVyLCBmdXJ0aGVyIA0KICAgICAgaW52ZXN0aWdhdGlvbiBpcyByZXF1aXJlZC4gU05NUHYzIG1h eSBiZSBmb3VuZCB0byBiZSBub3Qgc3VpdGFibGUsIA0KICAgICAgb3IgaXQgbWF5IGJlIG9ubHkg c3VpdGFibGUgYWZ0ZXIgYWRhcHRpbmcgaXQgYXBwcm9wcmlhdGVseS4NCiAgICAgIFRoaXMgYWRh cHRhdGlvbiBjb3VsZCBpbmNsdWRlIGxpbWl0aW5nIHRoZSBkYXRhIHR5cGVzIGFuZCANCiAgICAg IHNpbXBsaWZ5aW5nIHRoZSBCYXNpYyBFbmNvZGluZyBSdWxlcyBzbyBhcyB0byByZWR1Y2UgdGhl IHNpemUNCiAgICAgIGFuZCBjb21wbGV4aXR5IG9mIHRoZSBBU04uMSBwYXJzZXIsIHRoZXJlYnkg cmVkdWNpbmcgdGhlIG1lbW9yeSANCiAgICAgIGFuZCBwcm9jZXNzaW5nIG5lZWRzIHRvIGJldHRl ciBmaXQgaW50byB0aGUgbGltaXRlZCBtZW1vcnkgYW5kIA0KICAgICAgcG93ZXIgb2YgTG9XUEFO IGRldmljZXMuDQogICAgICA8dnNwYWNlIGJsYW5rTGluZXM9JzEnIC8+DQogICAgICA8L3Q+DQog ICAgICANCiAgICAgIDx0Pg0KICAgICAgSXQgbWF5IGJlIHRoZSBjYXNlIHRoYXQgdHJhbnNtaXR0 aW5nIElQIG92ZXIgSUVFRSA4MDIuMTUuNCANCiAgICAgIHdvdWxkIGJlY29tZSBtb3JlIGJlbmVm aWNpYWwgaWYgaW1wbGVtZW50ZWQgaW4gYSAiY2VydGFpbiIgd2F5LiANCiAgICAgIEFjY29yZGlu Z2x5LCBpbXBsZW1lbnRhdGlvbiBjb25zaWRlcmF0aW9ucyBhcmUgdG8gYmUgZG9jdW1lbnRlZC4N CiAgICAgIDx2c3BhY2UgYmxhbmtMaW5lcz0nMScgLz4NCiAgICAgIDwvdD4NCiAgICAgIA0KICAg ICAgPHQ+DQoJICAgICAgQXMgaGVhZGVyIGNvbXByZXNzaW9uIGJlY29tZXMgbW9yZSBwcmV2YWxl bnQsIG92ZXJhbGwgcGVyZm9ybWFuY2UNCgkgICAgICB3aWxsIGRlcGVuZCBldmVuIG1vcmUgb24g ZWZmaWNpZW5jeSBvZiBhcHBsaWNhdGlvbiBwcm90b2NvbHMuDQogICAgICBIZWF2eXdlaWdodCBw cm90b2NvbHMgYmFzZWQgb24gWE1MIHN1Y2ggYXMgU09BUA0KICAgICAgPHhyZWYgdGFyZ2V0PSJT T0FQIj48L3hyZWY+LCBtYXkgbm90IGJlIHN1aXRhYmxlIGZvciANCiAgICAgIExvV1BBTnMuIEFz IHN1Y2gsIG1vcmUgY29tcGFjdCBlbmNvZGluZ3MgKGFuZCBwZXJoYXBzIHByb3RvY29scykNCiAg ICAgIG1heSBiZWNvbWUgbmVjZXNzYXJ5LiBUaGUNCiAgICAgIGdvYWwgaGVyZSBpcyB0byBzcGVj aWZ5IG9yIHN1Z2dlc3QgbW9kaWZpY2F0aW9ucyB0byBleGlzdGluZw0KICAgICAgcHJvdG9jb2xz IHNvIHRoYXQgaXQgaXMgc3VpdGFibGUgZm9yIExvV1BBTnMuIEZ1cnRoZXJtb3JlLCANCiAgICAg IGFwcGxpY2F0aW9uIGxldmVsIGludGVyb3BlcmFiaWxpdHkgc3BlY2lmaWNhdGlvbnMgbWF5DQog ICAgICBhbHNvIGJlY29tZSBuZWNlc3NhcnkgaW4gdGhlIGZ1dHVyZSBhbmQgbWF5IHRodXMgYmUg c3BlY2lmaWVkLg0KICAgICAgPHZzcGFjZSBibGFua0xpbmVzPScxJyAvPg0KICAgICAgPC90Pg0K ICAgICAgDQogICAgICA8dD4NCgkgICAgICBTZWN1cml0eSB0aHJlYXRzIGF0IGRpZmZlcmVudCBs YXllcnMgbXVzdCBiZSBjbGVhcmx5IHVuZGVyc3Rvb2QgYW5kDQogICAgICBkb2N1bWVudGVkLiAN CiAgICAgIEJvb3RzdHJhcHBpbmcgb2YgZGV2aWNlcyBpbnRvIGEgc2VjdXJlIG5ldHdvcmsgY291 bGQgYWxzbyBiZSANCiAgICAgIGNvbnNpZGVyZWQgZ2l2ZW4gdGhlIGxvY2F0aW9uLCBsaW1pdGVk IGRpc3BsYXksIGhpZ2ggZGVuc2l0eSANCiAgICAgIGFuZCBhZCBob2MgZGVwbG95bWVudCBvZiBk ZXZpY2VzLiANCiAgICAgIDwvdD4NCiAgICAgIA0KICAgIDwvbGlzdD4NCiAgICA8L3Q+DQogICAg PC9zZWN0aW9uPg0KDQo8c2VjdGlvbiBhbmNob3I9ImlhbmEiIHRpdGxlPSJJQU5BIENvbnNpZGVy YXRpb25zIj4NCjx0Pg0KVGhpcyBkb2N1bWVudCBjb250YWlucyBubyBJQU5BIGNvbnNpZGVyYXRp b25zLg0KPC90Pg0KPC9zZWN0aW9uPg0KDQogICAgPHNlY3Rpb24gYW5jaG9yPSJzZWN1cml0eSIg dGl0bGU9IlNlY3VyaXR5IENvbnNpZGVyYXRpb25zIj4NCjx0PiANCjZsb3dwYW4gYXBwbGljYXRp b25zIG9mdGVuIHJlcXVpcmUgY29uZmlkZW50aWFsaXR5IGFuZCBpbnRlZ3JpdHkgIA0KcHJvdGVj dGlvbi4NClRoaXMgY2FuIGJlIHByb3ZpZGVkIGF0IHRoZSBhcHBsaWNhdGlvbiBvciB0cmFuc3Bv cnQgbGV2ZWwsIGF0IHRoZSAgDQpuZXR3b3JrIGxheWVyLCBhbmQvb3IgYXQgdGhlIGxpbmsgbGF5 ZXIsIGkuZS4gd2l0aGluIHRoZSA2bG93cGFuIHNldCAgDQpvZiBzcGVjaWZpY2F0aW9ucy4NCklu IGFsbCB0aGVzZSBjYXNlcywgNkxvV1BBTiBjb25zdHJhaW50cyB3aWxsIGluZmx1ZW5jZSB0aGUg Y2hvaWNlIG9mICANCmEgcGFydGljdWxhciBwcm90b2NvbC4gU29tZSBvZiB0aGUgbW9yZSByZWxl dmFudCBjb25zdHJhaW50cyBhcmUgIA0Kc21hbGwgY29kZSBzaXplLCBsb3cgcG93ZXIgb3BlcmF0 aW9uLCBsb3cgY29tcGxleGl0eSwgYW5kIHNtYWxsICANCmJhbmR3aWR0aCByZXF1aXJlbWVudHMu DQo8L3Q+IA0KPHQ+IA0KSXQgaXMgdW5kZXJzdGFuZGFibGUgdGhhdCB0aGVzZSBjb25zdHJhaW50 cyBoYXZlIGFzc29jaWF0ZWQgIA0KdHJhZGVvZmZzLiBUaHVzIGEgdGhyZWF0IG1vZGVsIGZvciA2 TG9XUEFOIGRldmljZXMgbmVlZHMgdG8gYmUgZmlyc3QgIA0KZGV2ZWxvcGVkIGluIG9yZGVyIHRv IHdlaWdodCBhbnkgcmlza3MgYWdhaW5zdCB0aGUgY29zdCBvZiBzZWN1cml0eSAgDQphbmQgYXQg dGhlIHNhbWUgdGltZSBtYWtlIG1lYW5pbmdmdWwgYXNzdW1wdGlvbnMgYW5kICANCnNpbXBsaWZp Y2F0aW9ucy4gIFNvbWUgZXhhbXBsZXMgZm9yIHRocmVhdHMgdGhhdCB3b3VsZCBiZSBjb25zaWRl cmVkICANCmFyZSBtYW4gaW4gdGhlIG1pZGRsZSBhdHRhY2tzLCBkZW5pYWwgb2Ygc2VydmljZSBh dHRhY2tzLg0KPC90PiANCjx0PiANCkEgc2VwYXJhdGUgc2V0IG9mIHNlY3VyaXR5IGNvbnNpZGVy YXRpb25zIG1pZ2h0IGFwcGx5IHRvICANCmJvb3RzdHJhcHBpbmcgYSA2bG93cGFuIGRldmljZSBp bnRvIHRoZSBuZXR3b3JrLCBpbiBwYXJ0aWN1bGFyICANCmluaXRpYWwga2V5IGVzdGFibGlzaG1l bnQgcHJvY2Vzc2VzLiBUaGlzIGlzIGdlbmVyYWxseSBpbnZvbHZlZCB3aXRoICANCm90aGVyIGFw cGxpY2F0aW9uIGxldmVsIHRyYW5zYWN0aW9ucyBhbmQgbWF5IHJlbHkgb24gYW4gYXBwbGljYXRp b24tIA0Kc3BlY2lmaWMgdHJ1c3QgbW9kZWw7IHRodXMgaXQgd2lsbCBub3QgYmUgcGFydCBvZiA2 TG9XUEFOLiBTb21lICANCmNob2ljZXMgbWF5IGJlIHRvIHVzZSBvdXQgb2YgYmFuZCBjb21tdW5p Y2F0aW9uIHRlY2huaXF1ZXMgc3VjaCBhcyAgDQpVU0IsIGluZnJhcmVkIG9yIE5GQyAoTmVhciBG aWVsZCBDb21tdW5pY2F0aW9uKSBmb3IgdGhlIGluaXRpYWwga2V5ICANCmVzdGFibGlzaG1lbnQu DQo8L3Q+IA0KPHQ+IA0KQWZ0ZXIgdGhlIGluaXRpYWwga2V5IGVzdGFibGlzaG1lbnQsIHN1YnNl cXVlbnQga2V5IG1hbmFnZW1lbnQgIA0KcHJvdG9jb2xzIHdvdWxkIGZhbGwgdW5kZXIgdGhlIHB1 cnZpZXcgb2YgNkxvV1BBTi4gSW4gb3JkZXIgdG8gYmUgIA0KYWJsZSB0byBzZWxlY3QgKG9yIGRl c2lnbikgdGhpcyBuZXh0IHNldCBvZiBwcm90b2NvbHMsIHRoZXJlIG5lZWRzIHRvICANCmJlIGEg Y29tbW9uIG1vZGVsIG9mIHRoZSBrZXlpbmcgbWF0ZXJpYWwgY3JlYXRlZCBieSB0aGUgaW5pdGlh bCBrZXkgIA0KZXN0YWJsaXNobWVudC4gVGhlcmUgYXJlIGEgZmV3IGNyeXB0b2dyYXBoaWMgcHJv dG9jb2xzIHRvIGNob29zZSAgDQpmcm9tLiBJdCBpcyB0byBiZSBzZWVuIGlmIHRoZSBwcm90b2Nv bHMgYXZhaWxhYmxlIGFzIHBhcnQgb2YgSVBzZWMgIA0KbWVldCB0aGUgY29uc3RyYWludHMgb2Yg NkxvV1BBTi4NCjwvdD4gDQo8dD4gDQpPbmUgYXJndW1lbnQgZm9yIHVzaW5nIGxpbmsgbGF5ZXIg c2VjdXJpdHkgaXMgdGhhdCBtb3N0IElFRUUgODAyLjE1LjQgIA0KY2hpcHMgYWxyZWFkeSBoYXZl IHN1cHBvcnQgZm9yIEFFUyBsaW5rIGxheWVyIHNlY3VyaXR5LiAgQUVTIGlzIGEgIA0KYmxvY2sg Y2lwaGVyIG9wZXJhdGluZyBvbiBibG9ja3Mgb2YgZml4ZWQgbGVuZ3RoLCBpLmUuLCAxMjggYml0 cy4gVG8gIA0KZW5jcnlwdCBsb25nZXIgbWVzc2FnZXMsIHNldmVyYWwgbW9kZXMgb2Ygb3BlcmF0 aW9uIG1heSBiZSB1c2VkLiBUaGUgIA0KZWFybGllc3QgbW9kZXMgZGVzY3JpYmVkLCBzdWNoIGFz IEVDQiwgQ0JDLCBPRkIgYW5kIENGQiBwcm92aWRlIG9ubHkgIA0KY29uZmlkZW50aWFsaXR5LCBh bmQgdGhpcyBkb2VzIG5vdCBlbnN1cmUgbWVzc2FnZSBpbnRlZ3JpdHkuIE90aGVyICANCm1vZGVz IGhhdmUgYmVlbiBkZXNpZ25lZCB3aGljaCBlbnN1cmUgYm90aCBjb25maWRlbnRpYWxpdHkgYW5k ICANCm1lc3NhZ2UgaW50ZWdyaXR5LCBzdWNoIGFzIENDTSogbW9kZS4gNkxvV1BBTiBjb3VsZCBj aG9vc2UgdG8gDQpvcGVyYXRlIGluIG9uZSBvZiB0aGUgbW9kZXMgb2Ygb3BlcmF0aW9uLCBidXQg aXQgaXMgIA0KZGVzaXJhYmxlIHRvIHV0aWxpemUgYXMgbXVjaCBvZiBsaW5rIGxldmVsIHNlY3Vy aXR5IGFzIHBvc3NpYmxlIGFuZCAgDQpidWlsZCB1cG9uIGl0Lg0KPC90PiANCjx0PiANCkZvciBu ZXR3b3JrIGxheWVyIHNlY3VyaXR5LCB0d28gbW9kZWxzIGFyZSBhcHBsaWNhYmxlOiBlbmQtdG8t ZW5kICANCnNlY3VyaXR5LCBlLmcuIHVzaW5nIElQc2VjIHRyYW5zcG9ydCBtb2RlLCBvciBzZWN1 cml0eSB0aGF0IGlzICANCmxpbWl0ZWQgdG8gdGhlIHdpcmVsZXNzIHBvcnRpb24gb2YgdGhlIG5l dHdvcmssIGUuZy4gdXNpbmcgYSBzZWN1cml0eSAgDQpnYXRld2F5IGFuZCBJUHNlYyB0dW5uZWwg bW9kZS4gIFRoZSBkaXNhZHZhbnRhZ2Ugb2YgdGhlIGxhdHRlciBpcyB0aGUgIA0KbGFyZ2VyIGhl YWRlciBzaXplLCB3aGljaCBpcyBzaWduaWZpY2FudCBhdCB0aGUgNmxvd3BhbiBmcmFtZSBNVFVz LiAgDQpUbyBzaW1wbGlmeSA2bG93cGFuIGltcGxlbWVudGF0aW9ucywgaXQgd291bGQgYmUgYmVu ZWZpY2lhbCB0byAgDQpjb25zaWRlciBzZWN1cml0eSBtb2RlbCBuZWVkZWQgYW5kIGlkZW50aWZ5 IGEgcHJlZmVycmVkIHNldCBvZiANCmNpcGhlciBzdWl0ZXMgdGhhdCBhcmUgYXBwcm9wcmlhdGUg Z2l2ZW4gdGhlIDZsb3dwYW4gY29uc3RyYWludHMuDQo8L3Q+DQogICAgPC9zZWN0aW9uPg0KICAg IA0KICAgIDxzZWN0aW9uIHRpdGxlPSJBY2tub3dsZWRnZW1lbnRzIj4NCiAgICA8dD4NCglUaGFu a3MgdG8gOg0KCTwvdD4NCgk8dD4NCglHZW9mZiBNdWxsaWdhbg0KCTwvdD4NCgk8dD4NCglTb29o b25nIERhbmllbCBQYXJrDQoJPC90Pg0KCTx0Pg0KCVNhbWl0YSBDaGFrcmFiYXJ0aQ0KCTwvdD4N Cgk8dD4NCiAgICBCcmlqZXNoIEt1bWFyDQogICAgPC90Pg0KICAgIDx0PiBmb3IgdGhlaXIgY29t bWVudHMgYW5kIGhlbHAgc2hhcGluZyB0aGlzIGRvY3VtZW50Lg0KICAgIDwvdD4NCiAgICA8L3Nl Y3Rpb24+DQogIDwvbWlkZGxlPg0KDQogIDxiYWNrPg0KICAgIDxyZWZlcmVuY2VzIHRpdGxlPSJO b3JtYXRpdmUgUmVmZXJlbmNlcyI+DQogICAgIA0KICAgICAgJlJGQzIxMTk7DQoNCiAgICAgICZS RkMyNDYwOw0KDQogICAgICAmTkQ7DQoNCiAgICAgICZBRERSLUNPTkY7DQoNCiAgICAgIDxyZWZl cmVuY2UgYW5jaG9yPSJFVUk2NCI+DQogICAgICAgIDxmcm9udD4NCgkJPHRpdGxlPkdVSURFTElO RVMgRk9SDQoJCQk2NC1CSVQgR0xPQkFMIElERU5USUZJRVIgKEVVSS02NCkNCgkJCVJFR0lTVFJB VElPTiBBVVRIT1JJVFk8L3RpdGxlPg0KDQoJICA8YXV0aG9yPiA8b3JnYW5pemF0aW9uPjwvb3Jn YW5pemF0aW9uPiA8L2F1dGhvcj4NCg0KICAgICAgICA8L2Zyb250Pg0KCTxzZXJpZXNJbmZvIG5h bWU9J0lFRUUnIHZhbHVlPSdodHRwOi8vc3RhbmRhcmRzLmllZWUub3JnL3JlZ2F1dGgvb3VpL3R1 dG9yaWFscy9FVUk2NC5odG1sJyAgLz4NCiAgICA8L3JlZmVyZW5jZT4NCg0KICAgIDxyZWZlcmVu Y2UgYW5jaG9yPSJpZWVlODAyLjE1LjQiPg0KICAgICAgICA8ZnJvbnQ+DQogICAgICAgICAgPHRp dGxlPklFRUUgU3RkLiA4MDIuMTUuNC0yMDAzPC90aXRsZT4NCg0KICAgICAgICAgIDxhdXRob3Ig c3VybmFtZT0iSUVFRSBDb21wdXRlciBTb2NpZXR5Ij4NCiAgICAgICAgICAgIDxvcmdhbml6YXRp b24+PC9vcmdhbml6YXRpb24+DQogICAgICAgICAgPC9hdXRob3I+DQoNCiAgICAgICAgICA8ZGF0 ZSBtb250aD0iT2N0b2JlciIgeWVhcj0iMjAwMyIgLz4NCiAgICAgICAgPC9mcm9udD4NCiAgICAg IDwvcmVmZXJlbmNlPg0KICAgIDwvcmVmZXJlbmNlcz4NCg0KICAgIDxyZWZlcmVuY2VzIHRpdGxl PSJJbmZvcm1hdGl2ZSBSZWZlcmVuY2VzIj4NCg0KICAgICAgJlJGQzM1NjE7DQogICAgICANCiAg ICAgICZSRkMzNjI2Ow0KICAgICAgDQogICAgICAmUkZDMzY4NDsNCiAgICAgIA0KICAgICAgJlJG QzM0MTE7DQogICAgICANCiAgICAgICZSRkMzNzU2Ow0KDQogICAgICA8cmVmZXJlbmNlIGFuY2hv cj0ibGlhaXNvbiI+DQogICAgICAgIDxmcm9udD4NCgkJPHRpdGxlPkxJQVNPTlM8L3RpdGxlPg0K DQoJICA8YXV0aG9yPiA8b3JnYW5pemF0aW9uPjwvb3JnYW5pemF0aW9uPiA8L2F1dGhvcj4NCg0K ICAgICAgICA8L2Zyb250Pg0KCTxzZXJpZXNJbmZvIG5hbWU9J0lFVEYnIHZhbHVlPSdodHRwOi8v d3d3LmlldGYub3JnL2xpYWlzb25BY3Rpdml0aWVzLmh0bWwnICAvPgkNCiAgICA8L3JlZmVyZW5j ZT4NCiAgICANCiAgICAgIDxyZWZlcmVuY2UgYW5jaG9yPSJTT0FQIj4NCiAgICAgICAgPGZyb250 Pg0KCQk8dGl0bGU+U09BUDwvdGl0bGU+DQoNCgkgIDxhdXRob3I+IDxvcmdhbml6YXRpb24+PC9v cmdhbml6YXRpb24+IDwvYXV0aG9yPg0KDQogICAgICAgIDwvZnJvbnQ+DQoJPHNlcmllc0luZm8g bmFtZT0nVzNDJyB2YWx1ZT0naHR0cDovL3d3dy53M2Mub3JnLzIwMDAveHAvR3JvdXAvJyAgLz4J DQogICAgPC9yZWZlcmVuY2U+DQoNCiAgICA8L3JlZmVyZW5jZXM+DQogIDwvYmFjaz4NCjwvcmZj Pg0KDQo= ------_=_NextPart_001_01C64F13.64680D45 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan ------_=_NextPart_001_01C64F13.64680D45-- From 6lowpan-bounces@ietf.org Fri Mar 24 12:27:39 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMq4Z-0008AB-Bn; Fri, 24 Mar 2006 12:27:39 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMq4Y-00086c-G1 for 6lowpan@lists.ietf.org; Fri, 24 Mar 2006 12:27:38 -0500 Received: from saloits.com ([208.42.140.127] helo=newbsd.saloits.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FMq4X-00033S-58 for 6lowpan@lists.ietf.org; Fri, 24 Mar 2006 12:27:38 -0500 Received: from newbsd.saloits.com (localhost.saloits.com [127.0.0.1]) by newbsd.saloits.com (8.13.1/8.13.1) with ESMTP id k2OHRaYG071124 for <6lowpan@lists.ietf.org>; Fri, 24 Mar 2006 11:27:36 -0600 (CST) (envelope-from salo@newbsd.saloits.com) Received: (from salo@localhost) by newbsd.saloits.com (8.13.1/8.13.1/Submit) id k2OHRarM071123 for 6lowpan@lists.ietf.org; Fri, 24 Mar 2006 11:27:36 -0600 (CST) (envelope-from salo) Date: Fri, 24 Mar 2006 11:27:36 -0600 (CST) From: "Timothy J. Salo" Message-Id: <200603241727.k2OHRarM071123@newbsd.saloits.com> To: 6lowpan@lists.ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea Cc: Subject: [6lowpan] Interim Meetings 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org I suggest that we be aware of the IESG guidance on interim IETF Working Group meetings: http://www.ietf.org/IESG/STATEMENTS/Interim-meetings.txt -tjs _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Fri Mar 24 17:39:59 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMuwo-0003Pw-Be; Fri, 24 Mar 2006 17:39:58 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMuwn-0003Pr-IO for 6lowpan@ietf.org; Fri, 24 Mar 2006 17:39:57 -0500 Received: from mailout2.samsung.com ([203.254.224.25]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FMuwl-0006t3-SA for 6lowpan@ietf.org; Fri, 24 Mar 2006 17:39:57 -0500 Received: from ep_mmp1 (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 <0IWN00DZ7LMHBK@mailout2.samsung.com> for 6lowpan@ietf.org; Sat, 25 Mar 2006 07:39:53 +0900 (KST) Received: from daniellaptop ([124.235.139.5]) by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTPA id <0IWN00126LMFRC@mmp1.samsung.com> for 6lowpan@ietf.org; Sat, 25 Mar 2006 07:39:53 +0900 (KST) Date: Sat, 25 Mar 2006 07:39:50 +0900 From: Soohong Daniel Park To: 6lowpan@ietf.org Message-id: <06be01c64f93$de488800$f6828182@daniellaptop> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Outlook Express 6.00.2900.2180 Content-type: text/plain; charset=ks_c_5601-1987 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal X-Spam-Score: 0.0 (/) X-Scan-Signature: 08e48e05374109708c00c6208b534009 Subject: [6lowpan] May Interim and 802 Interim Schedule 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org FYI. IEEE 802 Interm is 14-19 of May in Jacksonvill, FL (802.11/15/21/...). Thanks, Daniel (Soohong Daniel Park) Mobile Convergence Laboratory, SAMSUNG Electronics. _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Sat Mar 25 09:53:20 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNA8e-00066S-2s; Sat, 25 Mar 2006 09:53:12 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNA8d-00065E-1D for 6lowpan@lists.ietf.org; Sat, 25 Mar 2006 09:53:11 -0500 Received: from grab.coslabs.com ([199.233.92.34]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FNA8b-0002JO-N2 for 6lowpan@lists.ietf.org; Sat, 25 Mar 2006 09:53:11 -0500 Received: from dellx1.coslabs.com (dellx1.coslabs.com [199.233.92.20]) by grab.coslabs.com (8.12.10/8.12.10) with ESMTP id k2PEr6Jr000935; Sat, 25 Mar 2006 07:53:06 -0700 (MST) Subject: Re: [6lowpan] Interim Meetings From: Geoff Mulligan To: "Timothy J. Salo" In-Reply-To: <200603241727.k2OHRarM071123@newbsd.saloits.com> References: <200603241727.k2OHRarM071123@newbsd.saloits.com> Content-Type: text/plain Date: Sat, 25 Mar 2006 07:53:09 -0700 Message-Id: <1143298389.11646.8.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Cc: 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org Tim, We are well aware of this. geoff On Fri, 2006-03-24 at 11:27 -0600, Timothy J. Salo wrote: > I suggest that we be aware of the IESG guidance on interim IETF > Working Group meetings: > > http://www.ietf.org/IESG/STATEMENTS/Interim-meetings.txt > > -tjs > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Sat Mar 25 10:39:40 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNArb-0000lZ-ID; Sat, 25 Mar 2006 10:39:39 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNAra-0000lU-Al for 6lowpan@ietf.org; Sat, 25 Mar 2006 10:39:38 -0500 Received: from grab.coslabs.com ([199.233.92.34]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FNArY-0004Sa-VD for 6lowpan@ietf.org; Sat, 25 Mar 2006 10:39:38 -0500 Received: from dellx1.coslabs.com (dellx1.coslabs.com [199.233.92.20]) by grab.coslabs.com (8.12.10/8.12.10) with ESMTP id k2PFdZJr001093; Sat, 25 Mar 2006 08:39:35 -0700 (MST) Subject: Re: [6lowpan] May Interim and 802 Interim Schedule From: Geoff Mulligan To: Soohong Daniel Park In-Reply-To: <06be01c64f93$de488800$f6828182@daniellaptop> References: <06be01c64f93$de488800$f6828182@daniellaptop> Content-Type: text/plain Date: Sat, 25 Mar 2006 08:39:38 -0700 Message-Id: <1143301179.11646.33.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Cc: 6lowpan@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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org Are there many folks in this group that would be attending this IEEE interim? If so maybe we could hold the 6lowpan interim in jacksonville on thursday and friday of the week before (11 and 12 may)? Thoughts? geoff On Sat, 2006-03-25 at 07:39 +0900, Soohong Daniel Park wrote: > FYI. > > IEEE 802 Interm is 14-19 of May in Jacksonvill, FL (802.11/15/21/...). > > Thanks, > > Daniel (Soohong Daniel Park) > Mobile Convergence Laboratory, SAMSUNG Electronics. > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Sat Mar 25 12:06:40 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNCDo-0007UT-1i; Sat, 25 Mar 2006 12:06:40 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNCDm-0007UO-14 for 6lowpan@ietf.org; Sat, 25 Mar 2006 12:06:38 -0500 Received: from smtp102.plus.mail.re2.yahoo.com ([206.190.53.27]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FNCDl-0007Tx-Mm for 6lowpan@ietf.org; Sat, 25 Mar 2006 12:06:37 -0500 Received: (qmail 45668 invoked from network); 25 Mar 2006 17:06:37 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:Message-ID:Date:From:Reply-To:User-Agent:X-Accept-Language:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type; b=KyX7nzUy7zAzRWqV9RzKQn4U2s1oOOvKaFZRGDplMOrohy4HMSRave8W0yLoZ6rkkVacNryzAYrrlJB23HwDWUG+0HQOLWdTUUnVu4ARph1bLj6dM9nn9xT6BPukK2IW9gZph3n0Oya8fS/HwzO5mBwFjrv8Y95QOucKiGTprP0= ; Received: from unknown (HELO ?192.168.1.101?) (behcetsarikaya@67.166.225.5 with plain) by smtp102.plus.mail.re2.yahoo.com with SMTP; 25 Mar 2006 17:06:37 -0000 Message-ID: <4425789B.3080209@yahoo.com> Date: Sat, 25 Mar 2006 09:06:35 -0800 From: Behcet Sarikaya User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Geoff Mulligan Subject: Re: [6lowpan] May Interim and 802 Interim Schedule References: <06be01c64f93$de488800$f6828182@daniellaptop> <1143301179.11646.33.camel@localhost.localdomain> In-Reply-To: <1143301179.11646.33.camel@localhost.localdomain> X-Spam-Score: 0.1 (/) X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f Cc: 6lowpan@ietf.org X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sarikaya@ieee.org List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2139619326==" Errors-To: 6lowpan-bounces@ietf.org This is a multi-part message in MIME format. --===============2139619326== Content-Type: multipart/alternative; boundary="------------030703090708000606000404" This is a multi-part message in MIME format. --------------030703090708000606000404 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Some of us will be attending WiMAX F2F meeting in Ottawa, May 23-25. I suggest an interim around this activity? --behcet Geoff Mulligan wrote: >Are there many folks in this group that would be attending this IEEE >interim? If so maybe we could hold the 6lowpan interim in jacksonville >on thursday and friday of the week before (11 and 12 may)? > > Thoughts? > > geoff > >On Sat, 2006-03-25 at 07:39 +0900, Soohong Daniel Park wrote: > > >>FYI. >> >>IEEE 802 Interm is 14-19 of May in Jacksonvill, FL (802.11/15/21/...). >> >>Thanks, >> >>Daniel (Soohong Daniel Park) >>Mobile Convergence Laboratory, SAMSUNG Electronics. >> >>_______________________________________________ >>6lowpan mailing list >>6lowpan@ietf.org >>https://www1.ietf.org/mailman/listinfo/6lowpan >> >> > > >_______________________________________________ >6lowpan mailing list >6lowpan@ietf.org >https://www1.ietf.org/mailman/listinfo/6lowpan > > > > --------------030703090708000606000404 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Some of us will be attending WiMAX F2F meeting in Ottawa, May 23-25.
I suggest an interim around this activity?

--behcet

Geoff Mulligan wrote:
Are there many folks in this group that would be attending this IEEE
interim?  If so maybe we could hold the 6lowpan interim in jacksonville
on thursday and friday of the week before (11 and 12 may)?

	Thoughts?

	geoff

On Sat, 2006-03-25 at 07:39 +0900, Soohong Daniel Park wrote:
  
FYI.

IEEE 802 Interm is 14-19 of May in Jacksonvill, FL (802.11/15/21/...). 

Thanks, 

Daniel (Soohong Daniel Park)
Mobile Convergence Laboratory, SAMSUNG Electronics.

_______________________________________________
6lowpan mailing list
6lowpan@ietf.org
https://www1.ietf.org/mailman/listinfo/6lowpan
    


_______________________________________________
6lowpan mailing list
6lowpan@ietf.org
https://www1.ietf.org/mailman/listinfo/6lowpan
--------------030703090708000606000404-- --===============2139619326== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --===============2139619326==-- From 6lowpan-bounces@ietf.org Sat Mar 25 21:29:37 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNL0a-0005Zv-5t; Sat, 25 Mar 2006 21:29:36 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNL0Z-0005Y0-Ca for 6lowpan@lists.ietf.org; Sat, 25 Mar 2006 21:29:35 -0500 Received: from mailx.danfoss.com ([193.162.34.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FNL0Y-0004lA-01 for 6lowpan@lists.ietf.org; Sat, 25 Mar 2006 21:29:35 -0500 Received: from DKDN04MX62.dkdn04.danfoss.net ([10.6.2.62]) by mailx.danfoss.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 26 Mar 2006 04:29:32 +0200 Received: from dkdn01mx21.danfoss.net ([10.12.129.21]) by DKDN04MX62.dkdn04.danfoss.net with InterScan Message Security Suite; Sun, 26 Mar 2006 04:29:32 +0200 Received: from dkdn01mx25.danfoss.net ([10.12.129.25]) by dkdn01mx21.danfoss.net with Microsoft SMTPSVC(6.0.3790.1830); Sun, 26 Mar 2006 04:29:32 +0200 Received: from DKDN01MX34.danfoss.net ([10.12.128.14]) by dkdn01mx25.danfoss.net with Microsoft SMTPSVC(6.0.3790.1830); Sun, 26 Mar 2006 04:29:32 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Sun, 26 Mar 2006 04:29:24 +0200 Message-ID: <49A38D2FE2C53946A57916AD6A1F00D782EB94@DKDN01MX34.danfoss.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: minutes Thread-Index: AcZQfRjNHoD1ZSXxSMul7Y3fpwEcXQ== From: "Schumacher Christian Peter Pii" To: "6lowpan" <6lowpan@lists.ietf.org> X-OriginalArrivalTime: 26 Mar 2006 02:29:32.0508 (UTC) FILETIME=[1DA451C0:01C6507D] X-Spam-Score: 0.1 (/) X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8 Cc: Subject: [6lowpan] minutes 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0652681488==" Errors-To: 6lowpan-bounces@ietf.org This is a multi-part message in MIME format. --===============0652681488== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6507D.1B026B87" This is a multi-part message in MIME format. ------_=_NextPart_001_01C6507D.1B026B87 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable In agreement with the chairs, I will write up the offical minutes for our WG meeting (Fri 24 March).=20 If you have notes from the WG meeting (Fri 24 March) please submit these to me no later than Wed 29 March, so I'll have time to incorporate them. I will send the minutes to the chairs no later than Thu 30 March.=20 Regards Christian ------_=_NextPart_001_01C6507D.1B026B87 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable minutes

In agreement with the chairs, I will = write up the offical minutes for our WG meeting (Fri 24 March).

If you have notes from the WG meeting = (Fri 24 March) please submit these to me no later than Wed 29 March, so = I'll have time to incorporate them.

I will send the minutes to the chairs = no later than Thu 30 March.

Regards
Christian

------_=_NextPart_001_01C6507D.1B026B87-- --===============0652681488== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --===============0652681488==-- From 6lowpan-bounces@ietf.org Tue Mar 28 08:41:28 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FOEQK-0007nP-9r; Tue, 28 Mar 2006 08:39:52 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FOEQJ-0007nK-8i for 6lowpan@lists.ietf.org; Tue, 28 Mar 2006 08:39:51 -0500 Received: from mailx.danfoss.com ([193.162.34.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FOEQH-0002vu-VU for 6lowpan@lists.ietf.org; Tue, 28 Mar 2006 08:39:51 -0500 Received: from DKDN04MX62.dkdn04.danfoss.net ([10.6.2.62]) by mailx.danfoss.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 28 Mar 2006 15:39:48 +0200 Received: from dkdn01mx21.danfoss.net ([10.12.129.21]) by DKDN04MX62.dkdn04.danfoss.net with InterScan Message Security Suite; Tue, 28 Mar 2006 15:39:48 +0200 Received: from dkdn01mx25.danfoss.net ([10.12.129.25]) by dkdn01mx21.danfoss.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 28 Mar 2006 15:39:48 +0200 Received: from DKDN01MX34.danfoss.net ([10.12.128.14]) by dkdn01mx25.danfoss.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 28 Mar 2006 15:39:48 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 28 Mar 2006 15:39:46 +0200 Message-ID: <49A38D2FE2C53946A57916AD6A1F00D782ED70@DKDN01MX34.danfoss.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: poll for interim meeting locations Thread-Index: AcZSbRPedWZ3ub4ZSmOrLSqj5qxFyA== From: "Schumacher Christian Peter Pii" To: "6lowpan" <6lowpan@lists.ietf.org> X-OriginalArrivalTime: 28 Mar 2006 13:39:48.0526 (UTC) FILETIME=[15152CE0:01C6526D] X-Spam-Score: 0.0 (/) X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86 Cc: Subject: [6lowpan] poll for interim meeting locations 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1825094650==" Errors-To: 6lowpan-bounces@ietf.org This is a multi-part message in MIME format. --===============1825094650== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6526D.14D0C489" This is a multi-part message in MIME format. ------_=_NextPart_001_01C6526D.14D0C489 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dear 6lowpanners There has been suggested the following locations for a 2-day interim meeting: - Europe: Danfoss A/S, Denmark TZI, Germany - Canada: In connection with WiMAX F2F meeting in Ottawa, May 23-25 - USA: In connection (possibly May 11-12) with IEEE 802 Interim in Jacksonville, May14-19 Please reply your preference to this mail and CC the mailing list, so we can determine the overall preference. Deadline for this poll is Friday 7th of April. Regards Christian Schumacher ------_=_NextPart_001_01C6526D.14D0C489 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable poll for interim meeting locations

Dear 6lowpanners

There has been suggested the following = locations for a 2-day interim meeting:

- Europe:
        Danfoss A/S, Denmark
        TZI, Germany
- Canada:
        In connection with WiMAX F2F meeting in Ottawa, May = 23-25
- USA:
        In connection (possibly May 11-12) with IEEE 802 Interim = in Jacksonville, May14-19

Please reply your preference to this = mail and CC the mailing list, so we can determine the overall = preference.

Deadline for this poll is Friday 7th of = April.

Regards
Christian Schumacher


------_=_NextPart_001_01C6526D.14D0C489-- --===============1825094650== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --===============1825094650==-- From 6lowpan-bounces@ietf.org Tue Mar 28 12:34:21 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FOI5F-0007lz-FW; Tue, 28 Mar 2006 12:34:21 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FOI5D-0007lr-Un for 6lowpan@lists.ietf.org; Tue, 28 Mar 2006 12:34:19 -0500 Received: from web81903.mail.mud.yahoo.com ([68.142.207.182]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FOI5C-00050Y-JC for 6lowpan@lists.ietf.org; Tue, 28 Mar 2006 12:34:19 -0500 Received: (qmail 72024 invoked by uid 60001); 28 Mar 2006 17:07:38 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=bKGtayvt38tK9zNrngjY4XtiE5OxTy7inG1SHJjU0B9+3fdQRMWr0UdOZgzKUCv5cG76c+OpMwgnOA1lSluqCz9LcHzg+X5gJlPohBiOIrIGDrq4+RQr/p/ov++2RUO9E96slFFBqkeZIqqSYcYcCQIXafAPrKWm9gcw2XTyB38= ; Message-ID: <20060328170738.72022.qmail@web81903.mail.mud.yahoo.com> Received: from [71.227.195.193] by web81903.mail.mud.yahoo.com via HTTP; Tue, 28 Mar 2006 09:07:38 PST Date: Tue, 28 Mar 2006 09:07:38 -0800 (PST) From: gabriel montenegro Subject: Re: [6lowpan] poll for interim meeting locations To: Schumacher Christian Peter Pii , 6lowpan <6lowpan@lists.ietf.org> In-Reply-To: <49A38D2FE2C53946A57916AD6A1F00D782ED70@DKDN01MX34.danfoss.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.9 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Cc: 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org Why is an interim needed? What would be the agenda and desired outcome of this meeting? What do we need to get done before we're ready for such a meeting? I'd vote for Jacksonville, but really, without a clearer idea of the above I'd be unable to justify this expense in time and money. -gabriel --- Schumacher Christian Peter Pii wrote: > Dear 6lowpanners > > There has been suggested the following locations for a 2-day interim > meeting: > > - Europe: > Danfoss A/S, Denmark > TZI, Germany > - Canada: > In connection with WiMAX F2F meeting in Ottawa, May 23-25 > - USA: > In connection (possibly May 11-12) with IEEE 802 Interim in > Jacksonville, May14-19 > > Please reply your preference to this mail and CC the mailing list, so we > can determine the overall preference. > > Deadline for this poll is Friday 7th of April. > > Regards > Christian Schumacher > > > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Tue Mar 28 13:06:10 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FOIa1-0000mY-8x; Tue, 28 Mar 2006 13:06:09 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FOIa0-0000kf-3i for 6lowpan@lists.ietf.org; Tue, 28 Mar 2006 13:06:08 -0500 Received: from smtp102.plus.mail.re2.yahoo.com ([206.190.53.27]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FOIZz-0006lK-R0 for 6lowpan@lists.ietf.org; Tue, 28 Mar 2006 13:06:08 -0500 Received: (qmail 3465 invoked from network); 28 Mar 2006 18:06:07 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:Message-ID:Date:From:Reply-To:User-Agent:X-Accept-Language:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type; b=HSONL/nBATfsUaLPJ/C+DzL8mRSizlLY8sXnkzvpOShuqEPxZR0QX3L9xcFq/PC3SG1ZZdjh3AoOKJU5on+35Sr5RZxqutyybnbscyeVXITt70CEii2rWUaAxZFQRez/+RgaSz044mXtY1Iscgt7GWR8rA8fJzNvVKW50llVGSc= ; Received: from unknown (HELO ?192.168.1.137?) (behcetsarikaya@12.169.152.34 with plain) by smtp102.plus.mail.re2.yahoo.com with SMTP; 28 Mar 2006 18:06:07 -0000 Message-ID: <44297B0C.3040101@yahoo.com> Date: Tue, 28 Mar 2006 10:06:04 -0800 From: Behcet Sarikaya User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: gabriel montenegro Subject: Re: [6lowpan] poll for interim meeting locations References: <20060328170738.72022.qmail@web81903.mail.mud.yahoo.com> In-Reply-To: <20060328170738.72022.qmail@web81903.mail.mud.yahoo.com> X-Spam-Score: 0.1 (/) X-Scan-Signature: 21be852dc93f0971708678c18d38c096 Cc: 6lowpan <6lowpan@lists.ietf.org> X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sarikaya@ieee.org List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0339392149==" Errors-To: 6lowpan-bounces@ietf.org This is a multi-part message in MIME format. --===============0339392149== Content-Type: multipart/alternative; boundary="------------080706090202030405020008" This is a multi-part message in MIME format. --------------080706090202030405020008 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit I agree with Gabriel. We should not meet if there is not much to do/not enough attendance is expected, etc. I think that not many people were happy with the last interim. Regards, Behcet gabriel montenegro wrote: >Why is an interim needed? >What would be the agenda and desired outcome of this meeting? >What do we need to get done before we're ready for such a meeting? > >I'd vote for Jacksonville, but really, without a clearer idea of the above I'd be unable >to justify this expense in time and money. > >-gabriel > >--- Schumacher Christian Peter Pii wrote: > > > >>Dear 6lowpanners >> >>There has been suggested the following locations for a 2-day interim >>meeting: >> >>- Europe: >> Danfoss A/S, Denmark >> TZI, Germany >>- Canada: >> In connection with WiMAX F2F meeting in Ottawa, May 23-25 >>- USA: >> In connection (possibly May 11-12) with IEEE 802 Interim in >>Jacksonville, May14-19 >> >>Please reply your preference to this mail and CC the mailing list, so we >>can determine the overall preference. >> >>Deadline for this poll is Friday 7th of April. >> >>Regards >>Christian Schumacher >> >> >> >> >>>_______________________________________________ >>> >>> >>6lowpan mailing list >>6lowpan@ietf.org >>https://www1.ietf.org/mailman/listinfo/6lowpan >> >> >> > > >__________________________________________________ >Do You Yahoo!? >Tired of spam? Yahoo! Mail has the best spam protection around >http://mail.yahoo.com > >_______________________________________________ >6lowpan mailing list >6lowpan@ietf.org >https://www1.ietf.org/mailman/listinfo/6lowpan > > > > --------------080706090202030405020008 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit I agree with Gabriel. We should not meet if there is not much to do/not enough attendance is expected, etc. I think that not many people were happy with the last interim.

Regards,

Behcet

gabriel montenegro wrote:
Why is an interim needed? 
What would be the agenda and desired outcome of this meeting?
What do we need to get done before we're ready for such a meeting? 

I'd vote for Jacksonville, but really, without a clearer idea of the above I'd be unable
to justify this expense in time and money.

-gabriel

--- Schumacher Christian Peter Pii <schumacher@danfoss.com> wrote:

  
Dear 6lowpanners

There has been suggested the following locations for a 2-day interim
meeting:

- Europe:
	Danfoss A/S, Denmark
	TZI, Germany
- Canada:
	In connection with WiMAX F2F meeting in Ottawa, May 23-25
- USA:
	In connection (possibly May 11-12) with IEEE 802 Interim in
Jacksonville, May14-19

Please reply your preference to this mail and CC the mailing list, so we
can determine the overall preference.

Deadline for this poll is Friday 7th of April.

Regards
Christian Schumacher


    
_______________________________________________
      
6lowpan mailing list
6lowpan@ietf.org
https://www1.ietf.org/mailman/listinfo/6lowpan

    


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

_______________________________________________
6lowpan mailing list
6lowpan@ietf.org
https://www1.ietf.org/mailman/listinfo/6lowpan
--------------080706090202030405020008-- --===============0339392149== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --===============0339392149==-- From 6lowpan-bounces@ietf.org Tue Mar 28 14:05:52 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FOJVn-0001a5-Qg; Tue, 28 Mar 2006 14:05:51 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FOJVm-0001a0-GU for 6lowpan@lists.ietf.org; Tue, 28 Mar 2006 14:05:50 -0500 Received: from zproxy.gmail.com ([64.233.162.201]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FOJVm-0001Gi-5y for 6lowpan@lists.ietf.org; Tue, 28 Mar 2006 14:05:50 -0500 Received: by zproxy.gmail.com with SMTP id m22so1742nzf for <6lowpan@lists.ietf.org>; Tue, 28 Mar 2006 11:05:49 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=efIJ2awlctQJHMJe+CetUFtV+hPKEVGWOAnj7Lisb+us9aZ67EnhnErlzWumQ8Q/eGycHErwFbhwaKNkuTkFSuvhFmNd93IYLPTRuL8BZziy0OqeZA4pPnVSugD3wLoe0g4Qoed0B4cdhZkTAEyBbI38RQmgw9yr2+Vht7Pkm70= Received: by 10.65.96.12 with SMTP id y12mr3691761qbl; Tue, 28 Mar 2006 11:05:49 -0800 (PST) Received: by 10.65.185.15 with HTTP; Tue, 28 Mar 2006 11:05:49 -0800 (PST) Message-ID: <43b91d370603281105l2345e623q4d5d7208c2e81067@mail.gmail.com> Date: Tue, 28 Mar 2006 11:05:49 -0800 From: "Samita Chakrabarti" To: "Schumacher Christian Peter Pii" Subject: Re: [6lowpan] poll for interim meeting locations In-Reply-To: <49A38D2FE2C53946A57916AD6A1F00D782ED70@DKDN01MX34.danfoss.net> MIME-Version: 1.0 References: <49A38D2FE2C53946A57916AD6A1F00D782ED70@DKDN01MX34.danfoss.net> X-Spam-Score: 0.1 (/) X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1818693744==" Errors-To: 6lowpan-bounces@ietf.org --===============1818693744== Content-Type: multipart/alternative; boundary="----=_Part_26621_31368171.1143572749376" ------=_Part_26621_31368171.1143572749376 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi Christian, Can we have a tentative agenda for the interim to see if it is really necessary? I am not sure whether I can attend the interim, but I think having it in mid-May is too close to produce any updates and review before the meeting. It'd be also hard to justify the expenses as well as Gabe mentioned. Perhaps we can be more active and do our work and publish first drafts of targeted documents before we meet again. It might be more meaningful to have an interim after the summer meeting if it is required, IMHO. Regards, -Samita On 3/28/06, Schumacher Christian Peter Pii wrote: > > Dear 6lowpanners > > There has been suggested the following locations for a 2-day interim > meeting: > > - Europe: > Danfoss A/S, Denmark > TZI, Germany > - Canada: > In connection with WiMAX F2F meeting in Ottawa, May 23-25 > - USA: > In connection (possibly May 11-12) with IEEE 802 Interim in > Jacksonville, May14-19 > > Please reply your preference to this mail and CC the mailing list, so we > can determine the overall preference. > > Deadline for this poll is Friday 7th of April. > > Regards > Christian Schumacher > > > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan > > > ------=_Part_26621_31368171.1143572749376 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Hi Christian,
 
Can we have a tentative agenda for the interim to see if it is really = necessary?
 
I am not sure whether I can attend the interim, but I think having it = in mid-May
is too close to produce any updates and review before the meeting. It'= d be
also hard to justify the expenses as well as Gabe mentioned.
 
Perhaps we can be more active and do our work and publish first drafts=
of targeted documents before we meet again. It might be more meaningfu= l
to have an interim after the summer meeting if it is required, IM= HO.
 
Regards,
-Samita

 
On 3/28/06, = Schumacher Christian Peter Pii <schumacher@danfoss.com> wrote:

Dear 6lowpanners

There has been suggested the following l= ocations for a 2-day interim meeting:

- Europe:
   &= nbsp;    Danfoss A/S, Denmar= k
        TZI, Germany
- Cana= da:
        In connection with WiMAX F2F meeting in Ottawa, May 23-25 - USA:
    =     In connection (possibly = May 11-12) with IEEE 802 Interim in Jacksonville, May14-19

Please reply your preference to this mai= l and CC the mailing list, so we can determine the overall preference.

Deadline for this poll is Friday 7th of = April.

Regards
Christian Schumacher


 

____________= ___________________________________
6lowpan mailing list
6lowpan@ietf.org
https://www1.ietf.org/mailman/listinfo/6lowpan



------=_Part_26621_31368171.1143572749376-- --===============1818693744== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --===============1818693744==-- From 6lowpan-bounces@ietf.org Tue Mar 28 18:38:55 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FONm2-0008Rq-6m; Tue, 28 Mar 2006 18:38:54 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FONm1-0008QL-H1 for 6lowpan@lists.ietf.org; Tue, 28 Mar 2006 18:38:53 -0500 Received: from mailout2.samsung.com ([203.254.224.25]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FONlx-0005MA-MO for 6lowpan@lists.ietf.org; Tue, 28 Mar 2006 18:38:53 -0500 Received: from ep_mmp1 (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 <0IWV008YM30N5H@mailout2.samsung.com> for 6lowpan@lists.ietf.org; Wed, 29 Mar 2006 08:38:47 +0900 (KST) Received: from daniellaptop ([168.219.198.109]) by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTPA id <0IWV00C8R30NPW@mmp1.samsung.com> for 6lowpan@lists.ietf.org; Wed, 29 Mar 2006 08:38:47 +0900 (KST) Date: Wed, 29 Mar 2006 08:38:57 +0900 From: Soohong Daniel Park Subject: Re: [6lowpan] poll for interim meeting locations To: Schumacher Christian Peter Pii , 6lowpan <6lowpan@lists.ietf.org> Message-id: <00a701c652c0$c890f760$6dc6dba8@daniellaptop> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-Priority: 3 X-MSMail-priority: Normal References: <49A38D2FE2C53946A57916AD6A1F00D782ED70@DKDN01MX34.danfoss.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5 Cc: 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1241840753==" Errors-To: 6lowpan-bounces@ietf.org This is a multi-part message in MIME format. --===============1241840753== Content-type: multipart/alternative; boundary="Boundary_(ID_MGwvC14U+HlWPpOaLDbteA)" This is a multi-part message in MIME format. --Boundary_(ID_MGwvC14U+HlWPpOaLDbteA) Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT poll for interim meeting locationsJacksonville works for me, but several people said, I also want to sense why we need an interim before summer IETF. Daniel (Soohong Daniel Park) Mobile Convergence Laboratory, SAMSUNG Electronics. ----- Original Message ----- From: Schumacher Christian Peter Pii To: 6lowpan Sent: Tuesday, March 28, 2006 10:39 PM Subject: [6lowpan] poll for interim meeting locations Dear 6lowpanners There has been suggested the following locations for a 2-day interim meeting: - Europe: Danfoss A/S, Denmark TZI, Germany - Canada: In connection with WiMAX F2F meeting in Ottawa, May 23-25 - USA: In connection (possibly May 11-12) with IEEE 802 Interim in Jacksonville, May14-19 Please reply your preference to this mail and CC the mailing list, so we can determine the overall preference. Deadline for this poll is Friday 7th of April. Regards Christian Schumacher ------------------------------------------------------------------------------ _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --Boundary_(ID_MGwvC14U+HlWPpOaLDbteA) Content-type: text/html; charset=ISO-8859-1 Content-transfer-encoding: 7BIT poll for interim meeting locations
Jacksonville works for me, but several people said, I also
want to sense why we need an interim before summer IETF.

Daniel (Soohong Daniel Park)
Mobile Convergence Laboratory, SAMSUNG Electronics.
----- Original Message -----
To: 6lowpan
Sent: Tuesday, March 28, 2006 10:39 PM
Subject: [6lowpan] poll for interim meeting locations

Dear 6lowpanners

There has been suggested the following locations for a 2-day interim meeting:

- Europe:
        Danfoss A/S, Denmark
        TZI, Germany
- Canada:
        In connection with WiMAX F2F meeting in Ottawa, May 23-25
- USA:
        In connection (possibly May 11-12) with IEEE 802 Interim in Jacksonville, May14-19

Please reply your preference to this mail and CC the mailing list, so we can determine the overall preference.

Deadline for this poll is Friday 7th of April.

Regards
Christian Schumacher


_______________________________________________
6lowpan mailing list
6lowpan@ietf.org
https://www1.ietf.org/mailman/listinfo/6lowpan
--Boundary_(ID_MGwvC14U+HlWPpOaLDbteA)-- --===============1241840753== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --===============1241840753==-- From 6lowpan-bounces@ietf.org Wed Mar 29 07:10:40 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FOZVT-0005MU-1C; Wed, 29 Mar 2006 07:10:35 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FOZVR-0005Lw-Oi for 6lowpan@lists.ietf.org; Wed, 29 Mar 2006 07:10:33 -0500 Received: from mailx.danfoss.com ([193.162.34.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FOZVP-0000uX-M4 for 6lowpan@lists.ietf.org; Wed, 29 Mar 2006 07:10:33 -0500 Received: from DKDN04MX64.dkdn04.danfoss.net ([10.6.2.64]) by mailx.danfoss.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 29 Mar 2006 14:10:31 +0200 Received: from dkdn01mx22.danfoss.net ([10.12.129.22]) by DKDN04MX64.dkdn04.danfoss.net with InterScan Message Security Suite; Wed, 29 Mar 2006 14:10:31 +0200 Received: from DKDN01MX34.danfoss.net ([10.12.128.14]) by dkdn01mx22.danfoss.net with Microsoft SMTPSVC(6.0.3790.1830); Wed, 29 Mar 2006 14:10:30 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C65329.C5C9DABD" Subject: FW: [6lowpan] poll for interim meeting locations Date: Wed, 29 Mar 2006 14:10:29 +0200 Message-ID: <49A38D2FE2C53946A57916AD6A1F00D782EE08@DKDN01MX34.danfoss.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [6lowpan] poll for interim meeting locations Thread-Index: AcZSih8Cinj2sVwbSouv05BL4Hp8UgAnJ4dgAACyYHA= From: "Schumacher Christian Peter Pii" To: "6lowpan" <6lowpan@lists.ietf.org> X-OriginalArrivalTime: 29 Mar 2006 12:10:30.0332 (UTC) FILETIME=[C5C367C0:01C65329] X-Spam-Score: 0.0 (/) X-Scan-Signature: 3dc828214e948ff35b815af10e94a823 Cc: 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org This is a multi-part message in MIME format. ------_=_NextPart_001_01C65329.C5C9DABD Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Due to pending moderator request (due to mail size above limit), I submit this mail again with minutes zipped. -----Original Message----- From: Schumacher Christian Peter Pii=20 Sent: 29. marts 2006 14:07 To: 'gabriel montenegro'; 'Behcet Sarikaya' Cc: 6lowpan Subject: RE: [6lowpan] poll for interim meeting locations I assumed the consensus for an interim was already present.=20 (To Bechet: My feel regarding the January interim was that people felt it was quite productive, you've heard otherwise?) The rough topics I can think of (after having read my minutes) 1. Finish format document before 66th IETF Issue raised concerning allocation of addresses 2. Determine 6lowpan requirements to MANET WG How do we proceed in this area? Timeline involved! Requirements probably need to be=20 submitted to MANET WG as soon as possible 3. Find authors for charter bullets Bullet nr. 1 could probably be solved without Interim:=20 - draft on mailing list - intense mailing-list debate - last-call - comments - submissal to IESG Bullet nr. 2 is a candidate for face-2-face interaction since I completely fail to see how we proceed in this area (feedback please!) Bullet nr. 3 is an obvious candidate for face-2-face interaction. I think a debate on these bullets (and others you can think of, hint: read the attached minutes) is necessary so we clearly can determine whether a May interim meeting is needed or not.=20 BTW: I have just sent the minutes to Carsten and Geoff. Carsten promised to do a review on friday, so we can probably expect an official annoucement shortly after. I've attached the unofficial minutes so you can get an early look. Regards Christian -----Original Message----- From: gabriel montenegro [mailto:gabriel_montenegro_2000@yahoo.com]=20 Sent: 28. marts 2006 19:08 To: Schumacher Christian Peter Pii; 6lowpan Subject: Re: [6lowpan] poll for interim meeting locations Why is an interim needed?=20 What would be the agenda and desired outcome of this meeting? What do we need to get done before we're ready for such a meeting?=20 I'd vote for Jacksonville, but really, without a clearer idea of the above I'd be unable to justify this expense in time and money. -gabriel --- Schumacher Christian Peter Pii wrote: > Dear 6lowpanners >=20 > There has been suggested the following locations for a 2-day interim > meeting: >=20 > - Europe: > Danfoss A/S, Denmark > TZI, Germany > - Canada: > In connection with WiMAX F2F meeting in Ottawa, May 23-25 > - USA: > In connection (possibly May 11-12) with IEEE 802 Interim in > Jacksonville, May14-19 >=20 > Please reply your preference to this mail and CC the mailing list, so we > can determine the overall preference. >=20 > Deadline for this poll is Friday 7th of April. >=20 > Regards > Christian Schumacher >=20 >=20 > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan >=20 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around=20 http://mail.yahoo.com=20 ------_=_NextPart_001_01C65329.C5C9DABD Content-Type: application/x-zip-compressed; name="6lowpan.zip" Content-Transfer-Encoding: base64 Content-Description: 6lowpan.zip Content-Disposition: attachment; filename="6lowpan.zip" UEsDBBQAAAAIAAltfTTFvKXSDzsAANPUAAALAAAANmxvd3Bhbi50eHTtfVtv3Fa25nuA/AeefjiR gFLZki+daKaPIEt2rG7ZViSlPT0vAYu1q4oRi6zmRZUK5lfkGP17Z31rrb1JFjdLlHwGGGCGDaQt iVz7tu63/TrJ1qswDcIyeP2qXAQXb2/fBUtjyjidB59//Pabgweeb7/59pubJCuPg3d5PA5+OH7+ PDgIDg+PXzz/9pvrLFseBx+y1JR47y8PPd9+E3zMSlMEZXhn0mCyOabfBGeLPC7KmGZ5ZUqTB1dx HNxEi2oZRguT443rcFElwdk4uFmEC4wUfIjTCoDCojDLSWKmQ4ENmOO33+zdZ3FkgtxEWT6lnSqC tclNkGZlUBU01izLg3JhChMsZR6j4NtvJlUZFIusSmguJgjvwzgJaWbBLM+WwaIsV8fPnq3X63Fs ytk4y+f7GOl0btJpeBzwoui5MfOlScviWH6U/+I5HAfPdfMv0jLPgjCdBiF/PQreZPkyTNNg7/D5 fv3JEX9yiE/e4YUyuFmZaITzKk1q5gRk72Xzgxf8wSt8cG2iRZjTBtLqR7SpYZwXwd7r5tsvx8Hh c3n7o1kHn7P8rv4jnrDxwjkDucvDCUGNn32kfV2G+V2wd/Rqv/3VZAzsOnyFSWQV42m1moa8yX+L l7TG7S+iseAjfXFDEw6TIKYF5rMw4snfhHl8F27CYG/7Q8Js2e7gfxzbAzjPogq/2iv2j+u3T8fu D8Eqp4OnAabBtML2BIUFMq4/ePPYD8bjcfPIz7L03uRFWMZZ2phH89cW2tSOc2pH4j8P/OhNz0du PvWcbqolndkGZGCK9qSipCro80KQ3a2PmYf+8AgE9p1EPdzFOPiTIOR3QZHEU1P8qUEnNaG9cJT2 bJVnkTFMyc+ev6ZFPJMPn70W9njwaryazrbXy4N1RyOeEyyzaTyL6xMlZmC56p++di6vfXPx4ENr R/6dZ3oDSMEhtvjq/nWQ0SfBZbYOVhnxr+Dz1elH4vlExjLSvnfBbVhHwdbWN//4ggZyUuU4ULAY QtjaNrU1fzoL84K4UPuXeH4MJ3lskmAdJ0kwi9O4WIDfgn1ZpB13v/ps5IMp4VVUVsQD1sSPggEr fEmL+Lwg6HFhV3DSgD9w1teGJMGUNjmbWSjdl35Ok/jOBBlhS04nJOczy7IRiZdgEd6boMxINCZ3 QTgh1kfyh4QW0CtMki404FyaASHjVH4wJRY9HrJqsFd3XvFd/KQVk+Q1LAhp7+9ii+4Kdlz+HgPh B0zmNY7gR2IbUW5K4jC+T/D0zuWzbl+VZrNZHJEISDYELjERuG6tEhDlukFYiNu5dkFeMELUAIMi TkklyKo8OD0P9j5AeN1m67RIzGafXk2/c4y+wzgZXnvJf6Ylf1qRDvQhTkxRkgZF4pWZJ22Eit5g Rexx/7gFZuCGnCbLrADBpDgbolDiOqSLEGsmPm+YH0/zcFYOmOn3lj7WwDDaTsJRorIym4Z6UAPn 9FNFC4WQGAVRtmQt54TUwZXpviq/6ZM39b8+0vqaMmagxtMj7Ftb8Kc9B5SOQKEVBE21ka9m80fj 1aqz/z1ivzUzy5gPgktoRSXQJZ0T/hz2oYmy1O4+vyO9Tb8eBcCVxMxKwvFyFEzjIqqKohZxrFPF y5ZeYJ+fqji6I5KzM1kTDysXeVbNFy2tpvkQzU7jKciGVGpmIhBPF6QoQpGOZ44n0ryYQeI1L5hw OqVpRmGFXXMIMwrKPEyLGEeYhmVF+jvxZlLQ8xJfEKkWphh7ICoCB0U1p7WAgVQrUpyIGYutsREb AFpAFS0AlLYmw8864y5I+gMbEKQk0U7env5Igs0k087etCTr1ukePfp0T5OEZX9RxJM4icsN5rqM f7N7cfiadbDXL4NJ3NiTURcSCZgoLPijpSF5rJImyFVB38PZELgGnP3gL/9BzHYV5rSMLkS8CQac mHRe8iZmeTyP6aDolwpiRNMTWdl5uQtwCuaSio6r3/sOF1iXAelAyvFs40XnCxIVsFboyIqAmEa1 onMtyKorwZXpfELMYZZkGej7GbbkWVFWs1nveULJuM2CcyEqH0n0nuIHmgfEVlqwelBUqxVQuEpj OhLZlwntEm3/s+2TPOlCa//mJlzGZdh9y7FqVUSWVVLKcLRfouy63+howSarviO8WoarFW2KB4eK 4PLI/vlkxxZ4Tu22NSLmQKMFczLHSdIHh0ffY92g+M2KXoHwfwu8ITQdyZum7AItsiVjNJaTNNdG OmcJib8Kcd4pQ2BONNkQRY71tS5ABiJUUEDEGTWHWBfvbtgecfqNfJSRnlLue1ll3xHR702DUIjG 5yl7QWhkdlqAkk62gA1EOdF9wu6cR9ivNGNRQTztLs3Wuwbom/vfQyIKVeofxNHeWVql3Z0fjscD 7h90fCtCYvceY8somMf3htFWEFoQE0S+NsT9L4+eXb6w6+4Cta8TRbb5HrCjiJdxEuaEhvRni4nB XoEjA/fYf2jNfRt3mvO+h0mRifoqBO/O6emb+Sml2epKHDj429iftQbX1NFOgr9WyncM68Ymjfxs 9Fe8RxtVbxLTTu0jy1YssYlen8ypLmYyObD0dUiinsYi0iOxw9xykmfhFEt5CH6v1vophXIiNj6U YBJ7BS/enus4eBfnjvBp8JR0bJrIfZhUHiYBiZtDrr84EkYRW28o8woPyYnhARydYaAuSAzLug5t EdQVyCaeErOVEfGzKYGEt3S9MCxP61GyvAvPihaH0TwCzTObTmk6Bl/RS/QPyzFpu8vgQo7BB48M Y2zKlFnsgpSSC1j2U2ia2Nyih92MO2j1KAYGd+3hq/FLOL8JyUinzQzbaVaG1ogOtMyASfqnLkhY UaQGsfpjfiNUgb/Lanwe5B+IXjefCCM2TibQLuWlV3wOXPlNVosF1XFiUVZTmm4Klps8fbYXaXCx un+p2rgcJyMxCKI+Pv49U78ovCKeu+AW0ImFDdOs/6lKRwDH8ENTfJvHnndOA/gzGgIQ554B96c1 PcGILcAcIL5EAYiLp+HZ29/CqEw2I/HAEMqxlgx9hMBaJH7aUkhRjZhPwqeQ3wPPEjJfViHxgtZu PxlV3Aiw5om3jZhgmMslJMBoz544daI+OLGs8mjZCXNmdzJj2NTO7Gv8oQtvGc8XJeQF4dysSlgL Fu2dFZE93aF9Ym8xGWRrLApkHmUJlG8/LYsX7oRUSzo2hSCBHYZN6p/oVOxvJHSGHCAbg34DbOrC bGsBDGhrYc3pERLC96cz5Al1QRJjwPpMUpgxTgtiQrTWWU54B1JR9ZXRYixriX3aSpPR3YbOB8nf jYLmDoBm0o19l83wLjz2A4XBzKzr3XLmozPcQ0VXOq9VBWcuCbgHUaqfp89YV4OQFydUvFwl4spq iDPs6ofT6xt5l7da8a8LkWDQET0Ryc/EhUUcG27ne2i0IyJ/UCqZi3xKciq0i7mZV6QPOkrwHRGT d32WLJCWKlkhHdmpTTqaW+sIb6dqxZQaKG0//DHz4RaCzyr2AKgUE9fAOPhgqWwdA9+g5HUhTs2E 0J9F+BJyq8v8rYTnP9sFi5Idp559XJmMjlGc90Arr/MUzxADeUzHgiNnBXkJPCcirpasZo4hvSKT lyExa+vAiD1CTsgURwH3Bgz+wsenVPdJ2QStMdADT9l4SFCfjm8f2qsZCYm5c60FQ0pEuTRhCs+j HGNw9Oq1h7v4nSQDN/3T33Z9tlOBgDUs7hSgb8kxclITSG7+8MMrVh10ahz5yKMFiaIIGNsF5/yN xtyBcxUZPl9nUDjZZzljGoijSswxoDbIfhHm03Xsg3h5VHMy6I0s1VdZTJQ+Etm4DDcT47RetmjY 147QTrLpQoTY42kG74ksoIL6sMkpKmwgFDCxR8JbuhA13BPG+VcYz2orkexnmxheExpTjfIn4uj5 JiUzLWLc5O0vMdewDjbTOi9OP56CIcYFmSxMl7SBvCtkGHsmyrIa/tN6wmB5YpLB0ktMSfseTOPZ jNTJFEZrRvYFsxs+Pg8Xs/MR/acIN0FE9FkaOW5ahBF62uPZwqQjKS3TLfa9ti6rsmx0gm9UiRG2 qKdKc2VEyWBlW628aDqbuhB1j2Ba0xGBD9ktIAQlhoOsl8ByXIQ9nbc1uH535vN9DkQN+EtYwLNb kXeAcbLMKyZDnKnbwachysYOgQM1MxB/zUGtawXHvMa+Ap/YbhM68ihfOWTXV3qSnNs/jKdjpCmB CtnDT+cfwQ8o6qyoyssMGzHzOwLrrVL9zJ4lKKIwJOgt48LZBe/ByUEO62U79hwMJDvZwabr0g1Y T0XQBNsopGGVKTqDLsh5FkzC6I6Rdk0L/qOgM1itDKSKkCSzcWtQK4OLsqkZMTf0MULQt/vcEgax nFWWwItUjNnNazebds6eCJRavx4ahekfZY335SIj/r6KTcTEBbM/h9ckfdhA78WN90Z8bjQUdsWN xUEyEqxNvx8CV2tDjFSiV0y1HuwgdvPq8OgkOAfXUyUftugTjl5oFUovzGjBynBNA9DqU9EpaSNx gs6LPWZVGi6jKk89zBE47uhT0Jw1UBMWG/tP1RwT44J19gvPch23hiGjECCATf70UznN58J/JCzE 4kZEMUtnlT8h4fbqgL1yFYsibMhIFLwuTPgRDRJHgJ98djudAj20mPFW4IxV+SWDqOZtc0P68j8r Du+Pau0N8zrx8K9rfkGWQhrMHCbjoiLizawrgBlk0wBKJT5JiNUFR4p+mfSG2+3Tq7wtNy6NgPcI 2N/x2cEAVAVlhV/fsZ9v1oU2p12ALWcKMYML1QVa7nzgCgnpVKKw1gkHVboLsMFS1B4+TTegBZp3 qPiCAbCGEGFcJhmxuzwsUI9vxMKP38rNkmwHCQAdPvs+MGwxAQOtgfeCfjvzuTA0jIkQOscp5w+i vn1OiZ08FzvLoov/xTM1bV44IcAf7fATNb86bH7VbzLj+cRrabtM4NwlkkZ2DStJQ9xpvhWfc0JH 9xM/sUFeCGshNFH3s3j1VGbNM43RiPAStOUUAA/61Hy8AQimbLyESxiikpkX3niQcZls5sF5TNik Jp8jSgdqncFunQqBE87eGc68UE22JqkuJCt5lxyjZJS0ByiQkUayCKfZmkzjJZT7OIWOCw7sIW2J bD64rH67bkb7j3gsmB9rYzyllvHVwH6nSvm0czVBWKDSlqyBVxzSKSFx8GsSeKnK2Cnp0lO26eYe Gtb42DPrndvSV2QkFQgcMYgjqAoCyJd+VA/Rzs5oZQ/hudAMZA74pSX0/TyAVXovHOpfmNLvJs+Y So819+VYJ9qG1cpZ2UVYSMEGTmkqDOw5cFNfHoxuyFY6zC7g13X+CwjjzmzgLUzbiRfEKqdhGc7z cEk2/e8kA5Kq6CrJRVblvDX8Bb2/a+APCLlMTRJzvHxhQqRZYgpg+GuhnWX8m6yqkwPRhrV3KPyt TuIPy32rQASva3/WIlsVvyAbaicn+9AJ6lvjRXMH4CadwXbbYmcaOzwm1v6ceO+h+///xbLvl+9/ wUx+yWa/QM/+ZYkxfsEYu2aDh/093/uCMvUMN/DyJZyCoAT9YEAaj0KNoGSnW/Ffzo5CvsieMvdB EN+rl9jq1E3nuc9HsgcxsO+NWarD2UmlOgSmHmhGlpZ/nyWHh/+IsV3A8gsL6wwfspyP4hV3yyEj WQxcq1TaSdWaimd4dyZjlnpsj4oxg/CkxM5TyXwRhxHr6ND3fbuiTuUtn5YhDJjHKVtzEl6mF/CD rN3HlTEkJBPYeSlqv0TuiL7zLFtipZx9POzgxTDpnJIqHqxf0YaVWROBU4/mc2fMCmpXuWi6thsb PHYbSvqApvTR7x/ET+Y6SbhBtJyHF1+RpjMI7rDPz+WBjezsO/FbCTT0B7naP0HjY8ngdqc+9IkG XveIf7v8j05Vi/2XppupKNgK6zdTWOpEDKUTzSirQfkSBb0Jqnjg6GSlK50mdKzrrO1WZVqotRy4 gDkG0QaCJOgwQs4p7Wi0ncvW/gnemo0p66TVEZw3NplV3OLZeicrPyN7mXZ3JYaifsHLjuQveUwq pKQsqDuOloGftgwtayLB9yyxjWnGZ1cYcCjr9rI5CO24YUdeMQvALBxX2F7EG01YskU3R/z6ix0F TTUEmz+Nf++sMPEqfjcc+sLs4WNg3QPB+5i9PGTQlaKAIHrVpPOtFdwihkLiFqFd+HFpSl0Nm18i Oruz/KvY0HyWzENIfcsS5h4c8YklSWcsXj1PZAy6JA2SkiyDe2gZc6TBm5HIdQVQUlz2M9mUUwlw gtUnGa99RlvMmdKO3ryotluh/OhMH/m9TT8fUpQ3KKH9/7maKZlLK5f/xf6xcHabuUyQyyzKEmaB y/h3Rv+vns6Lgbn9rQNqlXAd1vU5ZBzk2SoDgqHO8kyLQy4I/wvfknmsPkPtlv1FRJKEugXbClk6 q4pGLoEq2KASDsLRX7wRD7w7a9dlqS+/kCqTpOEVVSdBCSLvgnp/xsFsjaCY32IxEq/fndWgAWkO 25mUqZkxSawZed6JFca5JITISdQlJP3UflznMelNEUmWlWXXXTB1pYz1oNoCGJvsY7lZ99sfQ/aR uJWoS1rZJBxk2Dn8fHEeWPuTTgKumC40h6PQXAuXppybf1ZxzlPUYJMsUiwxzn/swprCipIgKDKU rVONE2nY1xgZZmMZG1t25LEXAyaSVLt9bDLL5onOw1XhBN/E44C0p2ymbPaHnnIlUaBRyF6ikhvq kH+r2t8NUkffkTlK0GNIlLiQHD9lECPQQ844oLA9urEHYpxqDVpEzK7cICkG2fHQAxpOKbY6bRDT vdwF14yCs1+FA9JxoVCMSChx/1go9Lsw2RRWl28D/StCnMHfzHLl8VKpDxtJBHSICIwWDthONayX 62x8LqxHzOiWZ8GKDeHS/9nJbHPiI65vl3SRG1NWK54Gh78+ngefGmKDZPHVjbeoFk/vfKC8cpIO gWtKoUKsLM5lcTG4QkiI1SQPnrjEloJnusc2QzxnR5yCk6ygFD0bFsyjh5QBH6Ig6apDlJalEwcP 9i7SWe/ie/yh7K0oJdYIVsRciAfca4DeH7sXi9BDHTVpoWED0rLYlrUQRrK7VnvULHTaCw8figtV B6FGhpJCTBZ9llTt6nj7fErZQ0w7ubGJffiCGDHn/tvyUg+HuLBp0WQ80mD/zWbLI8WPs7PAgG36 nyABvJcP8rNeNCN7hHPFJuyepd2p4JgM/jsWbKb/sS3GzsPUG3lDfQAxhqJOu5dkwHRTY4PdL6lR 6NZU6zMIRbLJfZxVBZJ3zHdkbjSOMbikf7P/T/N06t3zBYtltsouNwGMhoLw206aI03gxL+pDKIF PnZzLoJwnhuJtV98t5QzbaUjaSSZNKssuZd8E69sHbQ3GIIty3AD8Dys6HMsSCUIV4sKz2GSRkpC e05bwBmmnF9mY7SEmXZHRhradkKcJHC07eoZiIc3yAbNoc+qAEOstNaUVOMo6mR9Y9i5xETVBWd9 hbPMeoPVFTnWQJXNoJREzWwlvksPenBq43jLamoxwZdigwmLUZa/pXgV/XxwGxpK8NkWsW1ORHoM 3EZR5F0eXdgwPq2eCZgoXN0ydTzST+OqaOOgeLMRQuFiD5YakCKLKodDR4+P7XX/gYBv4WTpa+Lq OgEmKz3vmmUzjrKfxDOtBed7OVWM7WwsSUJlan5441an6cali3OE0CWR0zbMxEUhOp2i296H049v bwuPX1C0c6BRoYouaViSHd9++Q2Z575CQxZeYaBF7yNOVeVETRHV+H2VIge375S5OmYNC5NMshCl U0lM8mHkjrblIexCsbZQ/Ls3p/9jxtntFhgdERLYcDJLuAM9X9h+AGBlSMgrs5XzLCdILmLHqe9D W3PAsfd8i5ZQULPYBLYiaA7R6A+np6ZJdJ2T6I9TKoNma6K0lUvsXedRnblZF6lZd76nLHpiorCS suhG0LZhhXGpyRgFERp1YatK8NIDj+CoTUDnTOByYrZIYOAwcamtkDqL3ak5E7etlppUu4yBHoCS mjXLCjIUMo14C7PFlnz//GiMsikPHmnVxTZHQZlp++3exJ3/Gc/fGCMJn5ApQFkM6B2P40PcwyKc hivpUITNOP10/nfWwtm7Vzx6RyShG8ZpO6FFPAc1T9DJIp2mM0bvChskS7bKgbVVNHtYK27gJ4k5 b1V0xT4Pi0BKSeAmZIbSmos109Uj1ntBKCRnGyaiLTWlFWsqkurQrIcmtafymUl4XfNXpc7aAr08 qvdt5OoMJSFPtrELrN5ooTZM0gY4SBo1lOfhW69bhF0TGTNla7tOQmMK1AJdrOYz3uqCks+wFVy1 y98yyYSplVrtPzhvh+cErq5lQ0eqWYVcNBCHqcd9tPMsrQVGMFiRYVfLo1CTeG5i7pHLIm4aCDRH Tpx2/mhimrEeSgoIiaSEppWLgezSles6HaGvxDak6oKD5wVK+UVguyGtiP0xYoZLpIHhV4JOnOZt Ext3HCHS9/PsnpNExDHI6+ZgYQ4wNlW8UaUqsaKtTe1RwYWinWXB0Vrms9wrYrlBum8HWF81c807 YO+xmJ8J3+AzkuJj24Yi3VIkfI07pBAmm8SosZC36ZjiyGidOkK/1iSpUhnlWXD+jw+fgmddaJef Ts85ppOtwCgAYrnVnaLWNAKrUA7cyV/VxI+IMNGYw4mKGIgpLjgujxVejamKWTKtlhNfUhzn+6zT YI8T9KR4CqFytWn23QDqtCY0Qd6KB5DN5SkkwYU3kAzTX01U8j4qoBgpegkx1ntvIUicFhVRBzuh g5t4njITTUs7r4UJ76EZQ1Ed7YRUpVXBZTM6B5vow0lHXJK+ved/iz3rOpWYP+Sr6qYImm0sgq3t 1nDTK+cK9ijbb2o9iHW2bAJXskoYTKzPjua+nh6iUrvW/Eb75dw1opgcFi50CrOV1CM+ApJxXTi1 5Q21Eka/VvvWRNuQNzt8+r0c9YrDmuCpYWG4O4ZOkifNjAv+9qbewtj76fLmGgm/A4eBaZ5A9bdm mRNnVpK5bhhWEY2MbWXRBQf6fobJdGbQ7HzjQRhkWQqHSwMkw3JgQNgFWgShy9ZvpesrxzpQH3UW EAsSD9zeIcCEHEGGXUtec6pC6S11lGGE4C1riBPoW7mxbbtsNBq8H3P2Kl1I8eWM2FZ5pNNVNehS u+dKLUnyMN810oekEZtMhtY0MygYbzrGhiMb0irqREj1N8JTP1GDhvBup0t89+l+CH+FUDSSIwi5 GSLkEpFFVCViZwU3ZLGlyIJpvOo5WyXQDM1i0gP9EckTK3Vsa7uKohF4LHz+bOJQkpliPwVu1Lph J55iHgHJwyNtB78iaBqD7dceGUuWj7fOodFf87g71+5vvOwbz5uwiKNGWWjDXQJ7/PJop2txkEeK yTpOK3Yp1t+24fa7qZxA57pwZFoayRUBCbDPhel9baxLoA5qdqHRIfMnXk8JR0jA6AnNvyu4Is/z HhNRyJ072F2scssilDVu2CRKzHRuEESRLDSvj6pWDva7/Nyv6XCvHVvnxITr6qfQGDdxy2RDNV5y yI8Lm7uwLrjfBQtvj4f9c103CQ40BYpOK2gMxwfnj+P9Z47bSKURscCC5salUDOeZUKqwu6GU71Y ck78+bmnRnnQdsrH1mOdsC/7jXRPLYjguQU34drnH6UBTDCLVYXkPT7ZHuUxm/LGzCT5Emn9U2s8 bwwE8nm7GgFbl1veo/qoh02h2jFT2xlYyo42tgow967HcRH5PI4Oe1QHf6Sc33RH2hGBKPONMuCU NAJGEYhhpupmiy7UR8cL0g8fORu26pN5ltOZLcVilVQx195mJGVPNnQX8m75eDeeTJO5WMNQ6S7u DvFucCfHGZwt0hxsXm0Kv12v7jB2qI2abUfSWRJHD6ce9OzpBy5hI/4kJFvreo1pK05jfhfe9rWP 22BubKX+zjlC7cOVEtY7LzhLYmpL38YCsuRyTuhf6I1Yex4IUyp/nxISv2W50aYAJ+zu4EotSIeM MPnmR5ohkxxjeKM3loeWNCV8QfZUMAFFNjIC62ZDdhtFCHkdCYmGGTVRliQ7fsKHH8/xmesP2Khw 8a3NertAzkNlhS73iLiLnfIYh0GUlyTSESbUuj7SWCOjzSHW0nC0C88pS6QoMEMSQrWe7C/COdRj qFYzu7a+jL3qsrhL2IZESiT6dWKAiYGX5+LqEc47rmJm8uUWFo7id2q0fWyprMO5zssq+V+KMo5D Xr7wrusx9IOUUIcDzOb1QC6PgmJBWiVx4csXQ31A0uNPWmmKv7adBEdGcRLKTtW2XuH3ILsMLE5X ceUHqLnRGAtm26h846qO38Jlj6rTbPE+EhXKWqRWb2plpXEaduxveCN9aROjUXHWKrQZY2G2wbiw ua63C67MZOtpr4pHChgIMRsXdmFU8f5uzWSs/nL2SRlfPYLj1mwZIzcEa4pYS5MuEtqMf42MZpGV LsDZBcdvxbhegV01lz9d1KHskLP8uBUtrBbkiI2ki53GVrvgKk1tEQVpWrH5WldzA5QY8zZQMdEI mZRDd4i5V6G7QtaBchohNcv+RmQ6I/WhkF5NVr1lfOS2on491/qD0UaHJUgpfbvuNdWEm1+hJEOy PCaGsxtJA4zhLRjENKQ9izMMeABYKic2IU78xLxBVaq9KLyo3eA2j8mAeQBLpcies6hdw8AR2y/E Z+KUDoIY8OWLkR5h0ZhGF1rNG5+qptTb5agSeMMtBsVx+RW+iNut+t2Jcegu2rCNO5WiFozwj1ke Ln2mv+0VwC6qPDcRWoV6FIaBuI2wgd5zsgiju0QSe6/fnZ2cSMSSpvIr2eOELzkJhSxbfU3JsLt4 yJr18EQhToJ/Hx88WMfUn4dTLYNqdVx3xF473QxO91wcVRgNv1hJEuzTT/SCkaXuYMOSiNdMtnpb JxtBSaj7Qfpy3m6dZCvgicOVP0iH1/C2jURNG3Ye82O4Xe+PPHz25sM72PnpQYnDnYRwCdeVZ618 tmWYGjR1yA1Z0r6wUyXhVWOzVJq+LmbQTi9mkzVA2U9axn6DkFkeBgokllpDb4LdV7cY1sfindbj gYW0HpdzwdWSgDzlWMPmANk6akm5NmmoVOkCIi1d283qGgvHf4gSjLps03kiF5Rw5zWSH77U6Ybr pZFNAcc/X90xhWQqN+MHdRMWlI3eeHX7P4tziG99fH/Ouq8muMvCu8AKo20fgBY07AlR9njbDnX2 nuQ/dqFIvYtmgnB060udxvAlaDWa5mx52wLf1wWLPQAOrbEVl0ctKV4noHxZmmkcfgm0aZYXp7hs coEL0jIUVejdADZ+JBo/Gx6kHj9KfBIz/MJhwi8k2tONOPQbMQnmmxBQXykNhQFoVo00ONjShiVm 5GSh9k/0HDbHp3P7ASNvlIDWwAZYsR26BWcZ4mOfZV6tgA2yv6qVaFi29xPff+VhzC5eHrYM1CF2 fi+zFwOa06yhOxmubV5x7LC5tm2H8Gu+Uk3rCU41k2V3pvdD6QLQ8dRPpkW0W+1dXRvTouI3194i HyOdd+tqB4nr9IoKjsVYu6yRKjlu5uskXKXZV4TBNUytiLv0usIkNa9DfB7NDDBOhOvCArZ52tqK hinNMbhxTiG5X7pGfOXV6/k7SL7zTzcSTObKZHiiiKWHFQnBMZOE633TDJx04U2s6hxw/z7Lodkl yWFUltcXVy6HEVFAcJNl7CtLYDdgK21o7TLutg5QKFd1nS4k50Q5Ca5MvkBdEZy+chELkS6K106C 65tT9Kdg6cptk7yL1Exy7WcvHVtdfXg3PORvQaPOTZInKxNopUGdO8S3bX5hPP/CnXX7uRDZRLHE kJDhM4a6jymBXNQNA2ZeqOvG7ZpHl4m195l+hjwRnh19+WVhkpWm2345cfcJ8KwRue8C4xVEcRn/ bpCgWS8hACieMUPzOHr8PFI60xOXWtVRCWCVXNpmNa2Bu1+3eVQaxqZPsqw8QDs9KW9nRjKUg7fL Z0Z1kqH6MJfYqYnjIJI44JH97qY6JjotILM+l4hOTumA5khifUXqmLp3PAysluxWZZhmWX6QZNGd CJEEjARLHWJm+DeyyHx+JU5mzTPU2+0OLPfsZqvSqv7XtpTBXWj1NWiDfQwQrNICKQ3nxt5LtjGl q1aok3g5ifTcRAgyDZr6e7PRcJGL9Lcyh3GMWohbM42O32mnMETd16TiHjGEREvEL1Iu2yB+nYF1 x3O9fKiRzL/YvnEFD618TlqbZLAH8inXWMMqsJ0QnTOgm627m7jsdADK6uiXL8QO0gwh7iEPkaLV NR5gVwecGE5KsUnEF4ZT1UicuyPFuRLGEhPuuVGicQ8diSPNhJG2LsMjF5jPAc+n0fy6DlKoa13L jdi04CV4CBQ36eHmndtwkxCLHKlol5iAhJa6X3HKvR1NQKyNQ2q3EVNgtMfztoiNpweeC2uIDuHK YRvdoX+jxTSIbRvCLSw7zt4Ii6aytpWrfxJcFE60nHBkpQtLe/+JqSowc3HyJq5yy2MH3J5dAdek 9o4TynrFQg/1fraiEk5ayVQSzygwhsB34PQymc91oYoLc2pWnL2crF5do1y6C8mkuA7PmQVY5M/n V3Xe7XisCWOIT/M/xC3jAVVYTbFWHlmEq6nhwgVDsYYVIGsnW4zvlmR12NuuWsOyVqsdlkcLvlb7 4o+li9UmBt4sDpNvLbT9U2+0pLStOfh0a7HMQQWJP/M/wbVoz0fyO288l/0yPMW6Wt22FGk3EBAH vEP/wfuimmHFUpbQRyRVK9ax8dUa9OWRqA3Fl6cu7F0exxx2cF2orPYunb+Wpk8ddh1GXW5VfZ3s EHHR7C3cqBSUOkfu3BBHKHG2PGnMd3PCIvCdBFuGjYATd2rhxsL0z6wC0TRb13nd8K5v41g7jF+8 fftW8JtvbIQUP0GlWJZ6hOLO0KJUWrGuJFnmKQP/t4GSVWVyHdqvlRUlv7GIbg7EcLryCVpIdUE1 26PNtPUO64QZk1ejx9P2zZdDfRqMCTFzOtYscuTmIo2c7MA68bmhomBbx7JPPixD619n5vgYroae IL9YOZjk2R1fdCEyAP1lG5d+TeUcO8vxpsxxAoCIRpYr2wVo7J3ijZA4n2YUZr6MQivcnJuaBeaK +1UX4pNjZ0A1jdnzxSeqE+9Cc8qTzTTrlm2K99n+2RKGxwAs4Qu1JKh3WFjToURR34Gbig2rOY2/ C82mLKm3ADENhcnRUg6nYBfH9n4E1n04nFv5HL4KLlaXMIcvtUCUc184BwWHw5XLJudlq649FGm1 zA9F2FNxhYAARE/nWLJ0+3/NLeZWxJd4pAPvpd32HEZ8txQaqMRT+Rm8NOZWvgPZ/+cFG2+sAdV2 NI7AlnDIFgrvZO701LDRRTCvwBcbeLxV7AYDlFlX2bZ6vcpLo3eqRKM12QVb4jZozHyWI4Lxqj/7 vKgmiKCIho+S7Ds6JlvoF5e2gZfrHcSaxB/ebCF1ZtV8VEoXxhxQ5ghiqAcsRbwz7oic+YS/3JKN frXAT8B6pucbSCYe/r69UdJuvAsMf6Jlgfv/wVxlzRCPD/Ylb2ciDfK4uRtzTOl369n37U22p4AE G5E77TkNE0C3QETbMLkjslW/rXcV5aJPxMOlTWarg8R1isRDMP2Tv5Kuelp7bDeGdB7ug88oxZGu FRdlBMfnvfXlTGztxNiRHHQnQ3Akrh82rLn5v5ftFtapjb4SOQ7IBp8L2wwQSpjLyc3j6dybyzKX +knLFhoGqtPrHMvYg3K339fVXsZwIAkx7dUvjYCABOsOmOMeZLMDaBJV3vWa1XU8+GkQAqxhd1bp 1HI2y+dgmJV1Eyri8XBhQJBISNNb0cX3Bc2lQnDChT1oxxMUS9IQCG3RIan2zgsXYESfee/6oW+X m+D930/PGn7ssatcXEjfCS3P55irzxg7rciSzpZZVdjSOpIUWSkhXRZei2oZatKpXNvmwemkmn+X frdKkDx5pv5B/rgqmtskXbBaAekuMK4RSXHBDBoo+BPAx1BCoXSQ6VEaZ8oMVfa5OgsXQliRoqV4 DYZyccUkCjfxcAnZ7BEOgBylLdDvCx0JfoCLrCq9XXB+jO9FvSEafCXZAHLFrxb92Az1YCQuMeis mqTqQVrVZtX91nC873aD9rqaSKnXfgbsmtQbwWwkPpJOjqDJsJrXeaTs3u1Cs/WsiOtkuWuXjIhl lSQQrQNjF5wyAcuqkSo/4oYyYHJtXziMCrLeuAMVeJEP7ZCb4NGHejiDUY8dskzUrSjRH1vtifQE Us2tk1AbkvTeKC9r90y7ZiqsZD4kdXqRsw053h4K4rPhNKDNUi7kmWuWlS5C8dB8eraP4LfA/Bc1 Qxs09rsM13taNBUHtssAZSmyO17Q5835B7edS0vm/60V9vlYnu2qJrYeujXbyHN1gDbO7Mmo0DSd TBHl8UQTBoUUWxVgQGVaitxV5NMWl6HcYMDo8kRs0BAA+w2XxDXZ/8cuOJQOpYhbkyTZLs/BswW+ t3dA7RnEAud5mOJeB9GNCiJ8bvVD0/iztOkh6bNnHZHFvo/qWrVzLpGYO09z1gZIF+kjD9xQ2BN6 4kqEeMoubI6I28l8xTVheujOM8pe+6JWyWxhaWPqYtB2YWl4XdQw+o5vuWg0IbEwn56f6XaAU6HM H3mrPgEU22IfT5RsCGJtcyIbB2/9chzcSkqLv6Qdeby4DCj3CZDr8FcP/rSV0eYzlIhtdDAiGch9 6/T2baEm7jWLRgaiP7DFgn4PPieBdJS1PhmieU2Ck3JZ8J9hIrl0eY3aMlbsVm6iqi7UscNDjm8Y bUDoc7ZdnX4s2I8GNQoK0BMI6XNoA4jBqupGOHfc0GUCFwPAxcm5EZPHhHfAGPHArjNHl8VuDPTv 10c42RBXKZ0d/RA69EYS0nYWau2v47sxY4fnQY3oXuGujlyJEUxc6iw+Z4bxIAPa0b1KVOsiGznr HbjbIZi+NTrnavMaO+bn9uKmbYTDzc7eOgcr7duV7NuvDUKxwzFjC/jUHtPNJJtu9rfUC5rFMxqK 99Enxv5haoWkwI2R6dRDEUeuhJ19/tpPR7Ks6oajJ21oPh9rnc7XM9KLMQPhmy4Qkvvd+PbnZfct z9pe8VujIEy+/DVeBm/Ino42X55AzBqwhEfsaQraC2BOg2Rx+tuR4SfMK81wTVLIrM15oSSWJ8xH G5zgUoHxLvh9jTl53BGM3ejO1kuLu5Iz33VUpLZdfHxXB1B9prq6hpxHXWMgEPlf2eoUPg3hZSxx 2LUxQaWJrbDWrtrO6I57yr7WW9VSdo7cBwMGqOiifCm7y59gOYFMxi68aR3OmKH8xl0PqXCXZjnB dWPxyvXCmWR8HVy48aU+cMEgD4+BJbOKQy/MiTBJMWlpfdpr0rNI5BtLKOf6HR2paGVY7fBw7Edu 6CFX93Gim413br945fw5a42tWF24mevJZWrOKc0RkLhzPQge+TjdLHx9pvoEKiONVb9tzHvE961Z AtTMcMIaE0aZa2Hiw+KBO7QxIZyhHRXvyeUs3PsATlEh8vq6leY9As6zjv2bkfRVLcZvBbNQfVD2 7DDlkOGBAjeOSWXTcIObgtTnhKlIbbO7BRpeksiaVF14tsuMhqxGNvHDipMRO3Bwf4TV+3fOfTtZ 7vvgQPL04+VwRP/JpgWBwBV19OoNLJqMlBNW9IoqIqWz4HbIafBXMvHCfPPksz4XtiGyROopqtS1 b3r6idGZiGOvmVWvKQNZB5mQxOkW7bteQTs3wAJ1RY82Ff09hPtJI0c8defoU0LeVggaBMdyu8YO JBm0fzZ7BQGxkCOmP98wPmJSTOm6LPyS73Pr0UXyMC44okjTNzzF9juDZvM+XIdxfELIMie17wO6 8aFE6DwuUmNL/eS/u++5aV5i03uD1EebPWI0iUc0lzoWrn49z0U+1gHXBujySGzYlZ1AccpZ0t3e ux5Gg75sEy0QltsxWs362dthU1RYFvl6CXd/g8deJhBLNjuqn4jX3ItSodlBD97k6v/tlb06xoUM 2DWD/q61K8zdEc7pzpP72OtgxVPXxE02zRrM3qvN7OP/7ZkW0dLaG9V2ZhmmuPLrMZD0DvSt3KU+ Lx+e7m9dK3jPFTh72jMIXmrn/2GdQfpJ+mQsNNeTwUhwY+/MYRyQqiTJDrTTQsJmsIdbcY5ePf/z KLj+9P5sH2/7AWri0KN20Sq+VsPk+hvuANG438XOp04ODyT9twdnuCs/d4hsGIuDT/fBhuv/qjMw R/jLqCZRTw9Lmx3NHz9rhQaGnpTbpa3ExkchbJ1n28iIYYSi9US0iGpK/ymiUmIY1o3psS3wdH/b 9K4OXdhVbVew1eWOvJuLxJcqlVxu7r/2HU+dQYBXjx6zPZ8bmnSju3kj4F/PJS7RZHVka5V75lJb GZwn/5jJfGwnRrS7z6vK3WkCpw59P0T29ColPHJb7H0/0rW37otN6CNZ5HK/R+orFMDTg9NwWzv1 xwZONGH3Xxz203Z/7CxxLYPPb64fMwxh2Gzc7LRnpMGR276WTH0MZDw/E4t5/RIxmN23Kjaf3dBw mgflZoWsbJMwEsTpVJIBeA9syzYyzgtkJvSDy+VOMFbCkPgN2n/SvNCcDxZIwXZ8QPumXmrD/UFs wv7V+3/0VR/aZ8cYjclK05D/fG+SJPviFmqxYBSwTGSFwl8eYR+9TBXqXxoXy8JdsXt69jfcdSQ2 K53XCnpzEZgy8tgI9un/y4c4BQoZbbQCLdx2R7RaI4lF0vk8rRft0/8XPOdS7MKNEhq3XxekqbG7 JUUz0h37jmf3X8VM5qtYw9YYJfoB6O1C19dvfwr2YEXnuBG9R/zax1JYgoYUHq2k+QxePq7ZTTCj MP6q9V4bFoWuQLkuhkdCD+ma12+vr6WFa/gAmuHhKMN/wRJdM1jxuqHoEuW/cEN+DfSflWTt/dml LC/nTfDK6+azg2pNSz0VzdRRmWPZHKEspGjW1zbZPrZD02PJ5NZVymA60v5H5gIbG/uKEheXkLPH BmcPRvp/+1kcnAAfbvUXknRfXqO71t92M/EDq0s7RtpCLSht+7qLq8a9xfUNhlrD36P2lJlUGtS5 9pxF30qCBHCeJLs7+5vm2OdWOynWKpXLFC50TnXxC2sX0hbn4vSNH2A/d/X/Fu0Y6tQMHtz1UJMr 6uoKAM40RqrbfQ/u2MMaodlbX9eV+qU6JiXtlP1AXc+aRvulMtsRnMLT/a3rd9C+P3H3R60PY1xV LCU3ccH1Do/ZaLVk5eJFqZd81OfuBpsqthdrS0sV5Qp3ZqMls/Ia2W/Lx5kueq142yP8DB1gSGJ5 7KpnNmHKf6cIHv9vrd5tne3nUH2lyPKPQrXdPfQKGsw8cIFuXa9Liu37ZqmUq5QCc/k1Y3ewZuIq k/JQJztjD3C/u7unCj/Y5HFwXJdWPsDnmWqVYiuTkaGgPWKhtcdSAgX3Gze/bXmC9YLgjuPt6uYY NKXuIL2oof7zRTo7xn+EFXGn7E4T1fZkrbPlTSv5g3tGN6Jhzru15S5rXZXZBW5tUc9lkz73TLsl SRecz4vgfII7rm/rQsJz2+tw+Ar3gp1O8/rZYC8Nfgse2CrXu3qbc+1ezLuKfX4aByi2tOEjyZpi j4R9RXAP7Y2Dvb9W4LRICs3ut4a4aEcYvI5y8bl/8HVfukVSSLjxcIq36rvG/2wX9pfj4PC5XI8O 4v5MUuj/34a+8zZ018D+5f6xlzi/dvjD3uH/vjU6d4qqVtOWv/lpg770XbmOZ3vMG8JN9Iuzfdu/ duDnMrDFr95b3lvo9+8+tGgi4V/6nj5q3o4T/sCtm3TZx442hFj+dXh4/OLV9rzw7Mp4lYymTj8r 5hMipuq0DSlnejrm9a6/9XRG0MXXl+djhJ+3EMz7Da55fkPm55xFa98u4/Fnon3Q4mTOSAjvMykS rLXZnqniXuUfs7B5Kaf3PVw9auNqn2YaOCnqrIkEY1yb+55hXjF71AjWeR3BSpHRIzxp77C3p5d/ xZdkHm5aUpiQQZQyTu5zkI/Pux+3f/OnD2eikTSKXLFrf+pZzusByzna7/n4zwM+fvHIvThH70Mt i5U6pBjNHqFHomarWvEeEbefbIjfrUhh7HHNWaPHoylezIIFnH6cTxlOSetAGpI4o8e2WHLNnYHl tujgw1kXSpGRrhOXW+Tm3SikGtxIHOqmJJl/S7pjks03PfsKjnN5JIEH+yrhLAf7H7ebMigS+OuL TbBAuZ64YP26Wfjus9GYvciJdBmRsonnTPO4QQXZZ14SxNOfaDw0Bbmn/kYaXxtutYJe4VmVR8a1 NBi51tEV1xWGpUTEfY4+dZx1somGTH3QVO29ha62ncOrNnuUUD6Mk2Ls05X7Nh9M+hR8Ekuf5Fk4 ZT4paQ0xJ1td37CGeX3aBwNM+4rkOelS0Y7XXrihan58ftrgSu1Z96dgacXkGHnH3KS+LNVjacUN E2Jd/ufatY46R9NfWIdTLg19TTYVPIQS2UKUnYuk9LcntiO0LfDztRVw+8qJg7neJup6TmgNbe1C ZjTD8jw4RideLtaLWNwqtk9FsL2u3t27eUuyeI+MFJLJ+zQEovTzjLaJy864aR/XhHOGHdjY27Mz 0jaIW/oyKt/bm6+LBe78Uox8TP1ibnD9uVR6BrOEZDanF2OaY/teH0a9dBj1wWGUkyk3DRZb9EF4 5Uf/vY9kPXOdUpZqRmPJTXR7Ab3m7mka8uBCVczl5/PGnrXXfx3+2t0QN/kzBPQDGjWXfpO2YxN7 PK2h4lI0npCyz5nMjX4CrE9GPCrQXIoaY6kUYU87DiXV6RW9vBxS3bWgVUnMl+8geR9ys9u+qJ85 CmXl8t1WX47mVQq8kKXGW/3FXWhYv7B+OCTNrJu9emvn8jC8vUGWZ27p1lKyKJ3aRUAzxhbc8PT2 7KoLJMrSVDQU8RTzzacJ++wJb8bcmkpqY0B9ccJNo715RxUhQcLvIyEPKcvM/y6uNNjnnSdSiLug tGVlFK84IILpSwza3k7R2aGdzfU+axsAyJCY8azQjA3hN9LR5gno+zMvWS680bA/WqF+t2SlDLfS thz0Mjbf3uwvFtErWG2XsRnx1an4DTck0R4h0Jdw6JV6MyGzDL2cFQ245jEcdOyClApbMVGQiY03 u9D4z4VQk7e/Tq+eYOl6yhLMpowTDXOImPvJJuGqzB4svuwVJOxOjZC1Le1NMUgUSudwCfwXNYG6 Pjh68p6lqr7V2iXMxc9oWCtu91Lq40k/WB6PA72JuSE634yBmb6THgsnPR8fQTn9xBTwCU2FLtR7 PnCPWq09tPwVGlwUwTfJac20c4ev6dfE6dCTJOX2GXPfdWLcKV46/TSTgf3zhl53JhUWxTObeFx4 pdEwf9BuB4AfasMPcJl9hr1wOiXxEAWf0oNzCK8pLL8SN3AHf5euEe7OQ0zCa/7VgKF3iglOVvCW Y3fgASGrlXf8PkxIo967/Olin13/2nzFtS6lyVYgIcIVj70Yp6597IPBBW9LLBDPGjV5Mo9Y7zC2 hez12JzCR3r5fTdbFs87tMMKubYGcgUQkY3CUAdkkPdt04JM3Ihv/o4aGzKF2ffgDR7e9dpWA7aC e0mGH7d0mfF8+SIR4tvoHaN+HLdFXWD0BfNTzvTmG4/vjUuL7E0prvEIhskVLH5OMbpoNX73YSAe 76rexwfIFYEEsXUKpnmJfl9SmG9S0G0/8aUaSXCaR4sY7gzdImyFBXlLpN262tcH7JVdIULzBVtL WX3lg0jP3RCg316hj1/SCtrYTjK7P4ZWeJPBQ3Ig4eUz182lz//hvv2+4XLrvLbrp+Ee512srY+9 4dlDPQAO22XRtZ1d/1c5mNtg8PTfFks89Y7NDb31IMclxNw/b+wBJv/YXW5g8YXTX/4lEmbPpSHu 91YgaBg+r5PtSHkHh4DsYPaGNCS9gMlxKa6f3VYynDe4/mwXIt3ojTZaprgdmOvuGk01JOtEOThS tpX7dl/t/oZj7FuZa02HQCttbAjAi7rPkauR/Cm7IUZbonwd2ze1ovdeRO8j0pQv45lB5pDIybhN xbs+497T9EHG0bY9OVdAgkkCu4z+mRfD0vU/23O0yaCSozZwx39OY1GmJMjuwQf/d5wjBroAp5+E aHQnEdj/bCCpdO/R+7a/ODXCd9UssNKXwtT+TS2e4h7x1P0GTx1MG9sMnCwfdMQqVzrj2f/9b1BL AQIUABQAAAAIAAltfTTFvKXSDzsAANPUAAALAAAAAAAAAAEAIAAAAAAAAAA2bG93cGFuLnR4dFBL BQYAAAAAAQABADkAAAA4OwAAAAA= ------_=_NextPart_001_01C65329.C5C9DABD Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan ------_=_NextPart_001_01C65329.C5C9DABD-- From 6lowpan-bounces@ietf.org Wed Mar 29 07:31:25 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FOZpW-0008ML-Tt; Wed, 29 Mar 2006 07:31:18 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FOZpV-0008MG-59 for 6lowpan@lists.ietf.org; Wed, 29 Mar 2006 07:31:17 -0500 Received: from mailhost.informatik.uni-bremen.de ([134.102.201.18] helo=informatik.uni-bremen.de) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FOZpT-0001fv-PS for 6lowpan@lists.ietf.org; Wed, 29 Mar 2006 07:31:17 -0500 Received: from [127.0.0.1] (maildrop.informatik.uni-bremen.de [134.102.201.19]) by informatik.uni-bremen.de (8.13.4/8.13.2) with ESMTP id k2TCVBH7022815; Wed, 29 Mar 2006 14:31:11 +0200 (CEST) In-Reply-To: <49A38D2FE2C53946A57916AD6A1F00D782EE08@DKDN01MX34.danfoss.net> References: <49A38D2FE2C53946A57916AD6A1F00D782EE08@DKDN01MX34.danfoss.net> Mime-Version: 1.0 (Apple Message framework v746.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Carsten Bormann Subject: Re: [6lowpan] poll for interim meeting locations Date: Wed, 29 Mar 2006 15:31:02 +0300 To: "Schumacher Christian Peter Pii" X-Mailer: Apple Mail (2.746.3) X-Virus-Scanned: by amavisd-new X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Cc: Carsten Bormann , 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org On Mar 29 2006, at 15:10 , Schumacher Christian Peter Pii wrote: > (To Behcet: My feel regarding the January interim was that people felt > it was quite productive, you've heard otherwise?) Well, we had at least one problem: we ran out of time. Apart from that, I do believe the Interim meeting was very good for shaping the focus of the WG. I would expect the next Interim would contain more actual protocol work, which is another argument for allocating more time. I do agree that the preconditions and the expected results of such an Interim still need to be decided, however. Gruesse, Carsten _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Thu Mar 30 17:00:15 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FP5Bc-0006Ep-V7; Thu, 30 Mar 2006 17:00:12 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FP5Bb-0006EU-Oo for 6lowpan@lists.ietf.org; Thu, 30 Mar 2006 17:00:11 -0500 Received: from grab.coslabs.com ([199.233.92.34]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FP5Bb-0001xH-Bo for 6lowpan@lists.ietf.org; Thu, 30 Mar 2006 17:00:11 -0500 Received: from dellx1.coslabs.com (dellx1.coslabs.com [199.233.92.20]) by grab.coslabs.com (8.12.10/8.12.10) with ESMTP id k2ULxaJr000365; Thu, 30 Mar 2006 14:59:37 -0700 (MST) Subject: Re: [6lowpan] poll for interim meeting locations From: Geoff Mulligan To: sarikaya@ieee.org In-Reply-To: <44297B0C.3040101@yahoo.com> References: <20060328170738.72022.qmail@web81903.mail.mud.yahoo.com> <44297B0C.3040101@yahoo.com> Content-Type: text/plain Date: Thu, 30 Mar 2006 15:00:11 -0700 Message-Id: <1143756011.11646.147.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org While a do agree that we should not meet if we do not have clear agenda and take exception to your characterization that people were not happy with the last interim. Everyone that I have spoken with were pleased with the progress that we made and the topics covered at the interim and felt that it was very productive and useful. If that is not the case, please speak up. geoff On Tue, 2006-03-28 at 10:06 -0800, Behcet Sarikaya wrote: > I agree with Gabriel. We should not meet if there is not much to > do/not enough attendance is expected, etc. I think that not many > people were happy with the last interim. > > Regards, > > Behcet > > gabriel montenegro wrote: > > Why is an interim needed? > > What would be the agenda and desired outcome of this meeting? > > What do we need to get done before we're ready for such a meeting? > > > > I'd vote for Jacksonville, but really, without a clearer idea of the above I'd be unable > > to justify this expense in time and money. > > > > -gabriel > > > > --- Schumacher Christian Peter Pii wrote: > > > > > > > Dear 6lowpanners > > > > > > There has been suggested the following locations for a 2-day interim > > > meeting: > > > > > > - Europe: > > > Danfoss A/S, Denmark > > > TZI, Germany > > > - Canada: > > > In connection with WiMAX F2F meeting in Ottawa, May 23-25 > > > - USA: > > > In connection (possibly May 11-12) with IEEE 802 Interim in > > > Jacksonville, May14-19 > > > > > > Please reply your preference to this mail and CC the mailing list, so we > > > can determine the overall preference. > > > > > > Deadline for this poll is Friday 7th of April. > > > > > > Regards > > > Christian Schumacher > > > > > > > > > > > > > _______________________________________________ > > > > > > > 6lowpan mailing list > > > 6lowpan@ietf.org > > > https://www1.ietf.org/mailman/listinfo/6lowpan > > > > > > > > > > > > __________________________________________________ > > Do You Yahoo!? > > Tired of spam? Yahoo! Mail has the best spam protection around > > http://mail.yahoo.com > > > > _______________________________________________ > > 6lowpan mailing list > > 6lowpan@ietf.org > > https://www1.ietf.org/mailman/listinfo/6lowpan > > > > > > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Thu Mar 30 17:29:47 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FP5eD-0004TQ-BO; Thu, 30 Mar 2006 17:29:45 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FP5eC-0004Qv-4D for 6lowpan@lists.ietf.org; Thu, 30 Mar 2006 17:29:44 -0500 Received: from web81911.mail.mud.yahoo.com ([68.142.207.190]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FP5eB-0003Yi-OV for 6lowpan@lists.ietf.org; Thu, 30 Mar 2006 17:29:44 -0500 Received: (qmail 31030 invoked by uid 60001); 30 Mar 2006 22:29:42 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=iaf/xbPfXdykPoMwVlzGzp01/eZ74rvEBIoZ1aBK16lKdaVfjUJ2JwLbbuFxwE05J8KlWK+r+ru86RKX4a/kwgbjMkUNubxw+lP//5a7+hLCj26SBZnC970w2XDIRXsgHmyUIlE45DVfP1VmGkAaEn+2LB3OP7vBciujWU38E0c= ; Message-ID: <20060330222942.31028.qmail@web81911.mail.mud.yahoo.com> Received: from [131.107.0.88] by web81911.mail.mud.yahoo.com via HTTP; Thu, 30 Mar 2006 14:29:42 PST Date: Thu, 30 Mar 2006 14:29:42 -0800 (PST) From: gabriel montenegro Subject: Re: [6lowpan] poll for interim meeting locations To: Geoff Mulligan , sarikaya@ieee.org In-Reply-To: <1143756011.11646.147.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.9 (/) X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: 6lowpan-bounces@ietf.org Just to clarify: I think the interim we had was very productive and wish we had had more time. I'm one of the happy ones. And if it makes sense, I'm all for having another productive one (as per the subject line in this message). All I'm saying is that every interim/meeting is an expense in time and money, and it's good to have as much info in advance in order to weigh the priorities with other commitments. Things like teleconferences are used regularly in IEEE or other venues, and that's perhaps something to explore as well. -gabriel --- Geoff Mulligan wrote: > While a do agree that we should not meet if we do not have clear agenda > and take exception to your characterization that people were not happy > with the last interim. > > Everyone that I have spoken with were pleased with the progress that we > made and the topics covered at the interim and felt that it was very > productive and useful. > > If that is not the case, please speak up. > > geoff > > On Tue, 2006-03-28 at 10:06 -0800, Behcet Sarikaya wrote: > > I agree with Gabriel. We should not meet if there is not much to > > do/not enough attendance is expected, etc. I think that not many > > people were happy with the last interim. > > > > Regards, > > > > Behcet > > > > gabriel montenegro wrote: > > > Why is an interim needed? > > > What would be the agenda and desired outcome of this meeting? > > > What do we need to get done before we're ready for such a meeting? > > > > > > I'd vote for Jacksonville, but really, without a clearer idea of the above I'd be > unable > > > to justify this expense in time and money. > > > > > > -gabriel > > > > > > --- Schumacher Christian Peter Pii wrote: > > > > > > > > > > Dear 6lowpanners > > > > > > > > There has been suggested the following locations for a 2-day interim > > > > meeting: > > > > > > > > - Europe: > > > > Danfoss A/S, Denmark > > > > TZI, Germany > > > > - Canada: > > > > In connection with WiMAX F2F meeting in Ottawa, May 23-25 > > > > - USA: > > > > In connection (possibly May 11-12) with IEEE 802 Interim in > > > > Jacksonville, May14-19 > > > > > > > > Please reply your preference to this mail and CC the mailing list, so we > > > > can determine the overall preference. > > > > > > > > Deadline for this poll is Friday 7th of April. > > > > > > > > Regards > > > > Christian Schumacher > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > > 6lowpan mailing list > > > > 6lowpan@ietf.org > > > > https://www1.ietf.org/mailman/listinfo/6lowpan > > > > > > > > > > > > > > > > > __________________________________________________ > > > Do You Yahoo!? > > > Tired of spam? Yahoo! Mail has the best spam protection around > > > http://mail.yahoo.com > > > > > > _______________________________________________ > > > 6lowpan mailing list > > > 6lowpan@ietf.org > > > https://www1.ietf.org/mailman/listinfo/6lowpan > > > > > > > > > > > _______________________________________________ > > 6lowpan mailing list > > 6lowpan@ietf.org > > https://www1.ietf.org/mailman/listinfo/6lowpan > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Fri Mar 31 13:09:14 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FPO3W-0001yQ-Pe; Fri, 31 Mar 2006 13:09:06 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FPO3V-0001yL-OX for 6lowpan@lists.ietf.org; Fri, 31 Mar 2006 13:09:05 -0500 Received: from wproxy.gmail.com ([64.233.184.239]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FPO3V-00074m-BH for 6lowpan@lists.ietf.org; Fri, 31 Mar 2006 13:09:05 -0500 Received: by wproxy.gmail.com with SMTP id i4so1754884wra for <6lowpan@lists.ietf.org>; Fri, 31 Mar 2006 10:09:05 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=lYi4S2I3A0LY77F1BBJhNoqz36q50TL+z3f0Y29a3Vh1K+oGJwgRsEEVuCZN+C/qmRJ2dc1uTLa5m+UX7ZoJgu5rui3Rsm6hPQXVjm91Ja+G8HCzoiP23RqFVkB6MRnv1IqaeUUFXqiSnhwrijvEEXb4eWybnULfkNpJ2xeV5Bw= Received: by 10.65.51.18 with SMTP id d18mr342190qbk; Fri, 31 Mar 2006 10:09:05 -0800 (PST) Received: by 10.65.241.8 with HTTP; Fri, 31 Mar 2006 10:09:04 -0800 (PST) Message-ID: <43b91d370603311009i4880f300qb318779e6b75cd08@mail.gmail.com> Date: Fri, 31 Mar 2006 10:09:04 -0800 From: "Samita Chakrabarti" To: "gabriel montenegro" Subject: Re: [6lowpan] poll for interim meeting locations In-Reply-To: <20060330222942.31028.qmail@web81911.mail.mud.yahoo.com> MIME-Version: 1.0 References: <1143756011.11646.147.camel@localhost.localdomain> <20060330222942.31028.qmail@web81911.mail.mud.yahoo.com> X-Spam-Score: 0.1 (/) X-Scan-Signature: 32029c790f79bd4a84a26bd2915c54b9 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: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2041773143==" Errors-To: 6lowpan-bounces@ietf.org --===============2041773143== Content-Type: multipart/alternative; boundary="----=_Part_9457_26107456.1143828544977" ------=_Part_9457_26107456.1143828544977 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello All: On 3/30/06, gabriel montenegro wrote: > > Just to clarify: I think the interim we had was very productive and wish > we had had > more time. I'm one of the happy ones. And if it makes sense, I'm all for > having > another productive one (as per the subject line in this message). Agree 100% that January Interim was a very productive meeting. Wish we had more time indeed. Given the optimistic schedule for the documents, it may make all sense to have interim meeting(s) again. Having concalls might also be an effectiv= e way to communicate in the meantime, since we are a small group so far. Looking forward to another productive Interim meeting in the future. -Samita --- Geoff Mulligan wrote: > > > While a do agree that we should not meet if we do not have clear agenda > > and take exception to your characterization that people were not happy > > with the last interim. > > > > Everyone that I have spoken with were pleased with the progress that we > > made and the topics covered at the interim and felt that it was very > > productive and useful. > > > > If that is not the case, please speak up. > > > > geoff > > > > On Tue, 2006-03-28 at 10:06 -0800, Behcet Sarikaya wrote: > > > I agree with Gabriel. We should not meet if there is not much to > > > do/not enough attendance is expected, etc. I think that not many > > > people were happy with the last interim. > > > > > > Regards, > > > > > > Behcet > > > > > > gabriel montenegro wrote: > > > > Why is an interim needed? > > > > What would be the agenda and desired outcome of this meeting? > > > > What do we need to get done before we're ready for such a meeting? > > > > > > > > I'd vote for Jacksonville, but really, without a clearer idea of th= e > above I'd be > > unable > > > > to justify this expense in time and money. > > > > > > > > -gabriel > > > > > > > > --- Schumacher Christian Peter Pii wrote: > > > > > > > > > > > > > Dear 6lowpanners > > > > > > > > > > There has been suggested the following locations for a 2-day > interim > > > > > meeting: > > > > > > > > > > - Europe: > > > > > Danfoss A/S, Denmark > > > > > TZI, Germany > > > > > - Canada: > > > > > In connection with WiMAX F2F meeting in Ottawa, May 23-25 > > > > > - USA: > > > > > In connection (possibly May 11-12) with IEEE 802 Interim > in > > > > > Jacksonville, May14-19 > > > > > > > > > > Please reply your preference to this mail and CC the mailing list= , > so we > > > > > can determine the overall preference. > > > > > > > > > > Deadline for this poll is Friday 7th of April. > > > > > > > > > > Regards > > > > > Christian Schumacher > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > > > > 6lowpan mailing list > > > > > 6lowpan@ietf.org > > > > > https://www1.ietf.org/mailman/listinfo/6lowpan > > > > > > > > > > > > > > > > > > > > > > __________________________________________________ > > > > Do You Yahoo!? > > > > Tired of spam? Yahoo! Mail has the best spam protection around > > > > http://mail.yahoo.com > > > > > > > > _______________________________________________ > > > > 6lowpan mailing list > > > > 6lowpan@ietf.org > > > > https://www1.ietf.org/mailman/listinfo/6lowpan > > > > > > > > > > > > > > > _______________________________________________ > > > 6lowpan mailing list > > > 6lowpan@ietf.org > > > https://www1.ietf.org/mailman/listinfo/6lowpan > > > > > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan > ------=_Part_9457_26107456.1143828544977 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello All:

On 3/30/06, = gabriel montenegro <gabriel_montenegro_2000@yahoo.com> wrote:
Just to clarify: I think the int= erim we had was very productive and wish we had had
more time. I'm one o= f the happy ones. And if it makes sense, I'm all for having
another productive one (as per the subject line in this message).
 
 
Agree 100% that January Interim was a very productive meeting. Wish we= had more
time indeed. Given the optimistic schedule for the documents, it may m= ake all sense
to have interim meeting(s) again. Having concalls might also be&n= bsp;an effective way to
communicate in the meantime, since we are a small group so far. Lookin= g forward to
another productive Interim meeting  in the future.
 
-Samita

--- Geoff Mulligan <geoff@mulligan.com> wrote:

>= ; While a do agree that we should not meet if we do not have clear agenda
> and take exception to your characterization that people were not h= appy
> with the last interim.
>
> Everyone that I have sp= oken with were pleased with the progress that we
> made and the topic= s covered at the interim and felt that it was very
> productive and useful.
>
> If that is not the case, pl= ease speak up.
>
>       geoff>
> On Tue, 2006-03-28 at 10:06 -0800, Behcet Sarikaya wrote:
= > > I agree with Gabriel. We should not meet if there is not much to
> > do/not enough attendance is expected, etc. I think that not m= any
> > people were happy with the last interim.
> >
&= gt; > Regards,
> >
> > Behcet
> >
> >= ; gabriel montenegro wrote:
> > > Why is an interim needed?
> > > What would b= e the agenda and desired outcome of this meeting?
> > > What do= we need to get done before we're ready for such a meeting?
> > &g= t;
> > > I'd vote for Jacksonville, but really, without a clearer= idea of the above I'd be
> unable
> > > to justify this = expense in time and money.
> > >
> > > -gabriel
> > >
> > > --- Schumacher Christian Peter Pii <= ;schumacher@danfoss.com> w= rote:
> > >
> > >
> > > > Dear 6lowp= anners
> > > >
> > > > There has been suggested the= following locations for a 2-day interim
> > > > meeting:> > > >
> > > > - Europe:
> > > >= ;         Danfoss A/S, Denmark
> > > >         TZI= , Germany
> > > > - Canada:
> > > > &nbs= p;       In connection with WiMAX F2F meeting= in Ottawa, May 23-25
> > > > - USA:
> > > >&= nbsp;        In connection (possibly May= 11-12) with IEEE 802 Interim in
> > > > Jacksonville, May14-19
> > > >
&g= t; > > > Please reply your preference to this mail and CC the mail= ing list, so we
> > > > can determine the overall preference= .
> > > >
> > > > Deadline for this poll is Fr= iday 7th of April.
> > > >
> > > > Regards> > > > Christian Schumacher
> > > >
> &g= t; > >
> > > >
> > > > > _______________________= ________________________
> > > > >
> > > >= 6lowpan mailing list
> > > > 6lowpan@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/6lowpan<= /a>
> > > >
> > > >
> > >
>= > >
> > > __________________________________________________
&g= t; > > Do You Yahoo!?
> > > Tired of spam?  Yah= oo! Mail has the best spam protection around
> > > http://mail.yahoo.com
> > >
> > > _____________= __________________________________
> > > 6lowpan mailing list> > > 6lowpan@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/6lowpan
> > >
= > > >
> > >
> > _____________________________= __________________
> > 6lowpan mailing list
> > 6lowpan@ietf.org
> > https://www1.ietf.org/mailman/listinfo/6lowpan
>
>


_______________________________________________= ___
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best= spam protection around
http://mail.ya= hoo.com

_______________________________________________
6lowpan mailing = list
6lowpan@ietf.org
https://www1.ietf.org/m= ailman/listinfo/6lowpan

------=_Part_9457_26107456.1143828544977-- --===============2041773143== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --===============2041773143==--