From 6lowpan-bounces@ietf.org Wed Feb 9 01:04:30 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27501; Wed, 9 Feb 2005 01:04:30 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CylHU-00077k-1z; Wed, 09 Feb 2005 01:24:56 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cykvu-0004wi-I9; Wed, 09 Feb 2005 01:02:38 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cyku7-0004J3-Gj for 6lowpan@megatron.ietf.org; Wed, 09 Feb 2005 01:00:47 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27382 for <6lowpan@ietf.org>; Wed, 9 Feb 2005 01:00:46 -0500 (EST) Received: from kame195.kame.net ([203.178.141.195] helo=papa.tanu.org) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CylDp-00074C-Ir for 6lowpan@ietf.org; Wed, 09 Feb 2005 01:21:12 -0500 Received: from localhost (cp.64translator.com [202.214.123.2]) by papa.tanu.org (8.12.9/8.12.8) with ESMTP id j1960mhB067913; Wed, 9 Feb 2005 15:00:48 +0900 (JST) (envelope-from sakane@kame.net) To: gab@sun.com Subject: Re: [6lowpan] 01 version of IP over IEEE 802.15.4 In-Reply-To: Your message of "Tue, 25 Jan 2005 12:45:19 -0800" <41F6AFDF.4060900@sun.com> References: <41F6AFDF.4060900@sun.com> X-Mailer: Cue version 0.8 (041108-2350/sakane) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Message-Id: <20050209150024G.sakane@kame.net> Date: Wed, 09 Feb 2005 15:00:24 +0900 From: Shoichi Sakane X-Dispatcher: imput version 20030322(IM144) Lines: 17 X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on papa.tanu.org X-Virus-Status: Clean X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Cc: 6lowpan@ietf.org X-BeenThere: 6lowpan@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.lists.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: 6lowpan-bounces@ietf.org Errors-To: 6lowpan-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Hi, > draft-montenegro-lowpan-ipv6-over-802.15.4-01.txt as i read the draft, let me say thank you for the great work, and i have two comments. 1. A link fragment defined at the section 2 is always placed to the MAC payload in the MAC protocol data unit of IEEE 802.15.4, right ? If my understanding is correct, it would be better for me to describe that though it might be explicit thing. 2. in the section 8.1, "PI" is defined like below: PI: Prefix included in-line "in-line" means that the prefix included in the following IPv6 header ? or it included anywhere ? _______________________________________________ 6lowpan mailing list 6lowpan@lists.ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Wed Feb 9 14:08:41 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28166; Wed, 9 Feb 2005 14:08:40 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyxWT-0006iU-Px; Wed, 09 Feb 2005 14:29:14 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cyx3A-00041p-IF; Wed, 09 Feb 2005 13:58:56 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CywzJ-00039I-5q for 6lowpan@megatron.ietf.org; Wed, 09 Feb 2005 13:54:57 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26735 for <6lowpan@ietf.org>; Wed, 9 Feb 2005 13:54:55 -0500 (EST) Received: from dyn50.sunlabs.com ([204.153.12.50] helo=mail-mta.sunlabs.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyxJ9-0006Gq-41 for 6lowpan@ietf.org; Wed, 09 Feb 2005 14:15:28 -0500 Received: from mail.sunlabs.com ([152.70.2.186]) by mail-mta.sfvic.sunlabs.com (Sun Java System Messaging Server 6.1 HotFix 0.02 (built Aug 25 2004)) with ESMTP id <0IBN0038YR6NAN00@mail-mta.sfvic.sunlabs.com> for 6lowpan@ietf.org; Wed, 09 Feb 2005 10:54:23 -0800 (PST) Received: from [172.16.1.34] ([69.106.235.181]) by mail.sunlabs.com (Sun Java System Messaging Server 6.1 HotFix 0.02 (built Aug 25 2004)) with ESMTPSA id <0IBN0087QR6N0I00@mail.sunlabs.com> for 6lowpan@ietf.org; Wed, 09 Feb 2005 10:54:23 -0800 (PST) Date: Wed, 09 Feb 2005 10:54:21 -0800 From: gabriel montenegro Subject: Re: [6lowpan] 01 version of IP over IEEE 802.15.4 In-reply-to: <20050209150024G.sakane@kame.net> To: Shoichi Sakane Message-id: <420A5C5D.8040202@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en References: <41F6AFDF.4060900@sun.com> <20050209150024G.sakane@kame.net> User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Spam-Score: 0.0 (/) X-Scan-Signature: 25620135586de10c627e3628c432b04a Content-Transfer-Encoding: 7BIT Cc: 6lowpan@ietf.org X-BeenThere: 6lowpan@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.lists.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: 6lowpan-bounces@ietf.org Errors-To: 6lowpan-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248 Content-Transfer-Encoding: 7BIT Sakane-san, Thanks for your generous words. Shoichi Sakane wrote: > Hi, > > >> draft-montenegro-lowpan-ipv6-over-802.15.4-01.txt > > > as i read the draft, let me say thank you for the great work, > and i have two comments. > > 1. A link fragment defined at the section 2 is always placed to the MAC > payload in the MAC protocol data unit of IEEE 802.15.4, right ? > If my understanding is correct, it would be better for me to describe > that though it might be explicit thing. Not sure I understand the question. Section two does not talk much about fragmenation. In that respect, there is no mention of "link fragments" as per your question. There is, however, mention of IPv6 links (which map to IPv6 prefixes). There is mention of link fragments in section 4, however. Even so, not all packets will need to be fragmented (the expectation is that most will be small enough). Only those that are fragmented use the encapsulation in figures 2 and 3. Unfragmented packets use the simpler encapsulation format in figure 1. Perhaps you're asking where exactly this encapsulationn format (figs 1-3) occurs. Yes, it is the MAC frame payload in the 15.4 MAC PDU. I agree that it makes sense to say so explicitly. Added this as a new first paragraph in section 4.1: All IP datagrams transported over IEEE 802.15.4 are prefixed by an encapsulation header with one of the formats illustrated below. The encapsulation formats defined in this section are the payload in the IEEE 802.15.4 MAC protocol data unit (PDU). > > 2. in the section 8.1, "PI" is defined like below: > PI: Prefix included in-line > "in-line" means that the prefix included in the following IPv6 header ? > or it included anywhere ? > It means that it is included as a non-compressed field. Notice that what follows the encoding bit maps is not an IPv6 header, as the point is to compress it. Rather, what follows is a smaller version of an IPv6 header comprising the non-compressed fields as specified in section 8.2. I've added references to section 8.2 whenever 'carried in-line' is used, as in: E.g., this is how it reads now: PI: Prefix carried in-line (Section 8.2) PC: Prefix compressed (link-local prefix assumed) II: Interface identifier carried in-line (Section 8.2) IC: Interface identifier compressed (derived from link-layer address) And added this as the new first paragraph in section 8.2: This scheme allows the IPv6 header to be compressed to different degrees. Hence, instead of the entire (standard) IPv6 header, only non-compressed fields need to be sent. The subsequent header (as specified by the Next Header field in the original IPv6 header) immediately follows the IPv6 non-compressed fields. Hope that helps, -gabriel _______________________________________________ 6lowpan mailing list 6lowpan@lists.ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Wed Feb 9 21:30:31 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24326; Wed, 9 Feb 2005 21:30:31 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cz4Q8-000714-HH; Wed, 09 Feb 2005 21:51:08 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cz44N-0003o2-Mz; Wed, 09 Feb 2005 21:28:39 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cz43Q-0003Xg-DE for 6lowpan@megatron.ietf.org; Wed, 09 Feb 2005 21:27:40 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24142 for <6lowpan@ietf.org>; Wed, 9 Feb 2005 21:27:38 -0500 (EST) Received: from kame195.kame.net ([203.178.141.195] helo=papa.tanu.org) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cz4NK-0006yA-3p for 6lowpan@ietf.org; Wed, 09 Feb 2005 21:48:15 -0500 Received: from localhost (cp.64translator.com [202.214.123.2]) by papa.tanu.org (8.12.9/8.12.8) with ESMTP id j1A2RnhB074681 for <6lowpan@ietf.org>; Thu, 10 Feb 2005 11:27:52 +0900 (JST) (envelope-from sakane@kame.net) To: 6lowpan@ietf.org Subject: Re: [6lowpan] 01 version of IP over IEEE 802.15.4 In-Reply-To: Your message of "Wed, 09 Feb 2005 10:54:21 -0800" <420A5C5D.8040202@sun.com> References: <420A5C5D.8040202@sun.com> X-Mailer: Cue version 0.8 (041108-2350/sakane) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Message-Id: <20050210112754T.sakane@kame.net> Date: Thu, 10 Feb 2005 11:27:54 +0900 From: Shoichi Sakane X-Dispatcher: imput version 20030322(IM144) Lines: 12 X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on papa.tanu.org X-Virus-Status: Clean X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 X-BeenThere: 6lowpan@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.lists.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: 6lowpan-bounces@ietf.org Errors-To: 6lowpan-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 > > 1. A link fragment defined at the section 2 is always placed to the MAC > > payload in the MAC protocol data unit of IEEE 802.15.4, right ? > > If my understanding is correct, it would be better for me to describe > > that though it might be explicit thing. > > Not sure I understand the question. Section two does not talk much about sorry, my fault, I meant the section 4. > Hope that helps, both are fine to me, thank you very much. _______________________________________________ 6lowpan mailing list 6lowpan@lists.ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Mon Feb 14 19:33:45 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07820; Mon, 14 Feb 2005 19:33:45 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0qzj-0004JZ-F1; Mon, 14 Feb 2005 19:55:19 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0qZr-0001HN-VI; Mon, 14 Feb 2005 19:28:31 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0qWQ-0000YC-Ff for 6lowpan@megatron.ietf.org; Mon, 14 Feb 2005 19:24:58 -0500 Received: from mail-mta.sunlabs.com (dyn50.sunlabs.com [204.153.12.50]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07349 for <6lowpan@lists.ietf.org>; Mon, 14 Feb 2005 19:24:54 -0500 (EST) Received: from mail.sunlabs.com ([152.70.2.186]) by mail-mta.sfvic.sunlabs.com (Sun Java System Messaging Server 6.1 HotFix 0.02 (built Aug 25 2004)) with ESMTP id <0IBX005HXFSOPS00@mail-mta.sfvic.sunlabs.com> for 6lowpan@lists.ietf.org; Mon, 14 Feb 2005 16:24:24 -0800 (PST) Received: from [172.16.1.34] ([69.106.235.181]) by mail.sunlabs.com (Sun Java System Messaging Server 6.1 HotFix 0.02 (built Aug 25 2004)) with ESMTPSA id <0IBX00AGMFSNZ700@mail.sunlabs.com> for 6lowpan@lists.ietf.org; Mon, 14 Feb 2005 16:24:24 -0800 (PST) Date: Mon, 14 Feb 2005 16:24:22 -0800 From: gabriel montenegro In-reply-to: <41F6AFDF.4060900@sun.com> To: 6lowpan@ietf.org Message-id: <42114136.9020805@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-2022-JP Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en References: <41F6AFDF.4060900@sun.com> User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) Content-Transfer-Encoding: 7BIT Subject: [6lowpan] 00 version of Goals and Assumptions submitted X-BeenThere: 6lowpan@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.lists.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: 6lowpan-bounces@ietf.org Errors-To: 6lowpan-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Content-Transfer-Encoding: 7BIT Folks, We've submitted the first *official* version of this draft (previous ones had circulated on the alias, though). The draft is available in anticipation of it appearing at the IETF repository in either html or txt formats: draft-kushalnagar-lowpan-goals-assumptions-00.txt draft-kushalnagar-lowpan-goals-assumptions-00.html To fetch it, please go here: http://f2.pg.briefcase.yahoo.com/gabriel_montenegro_2000 [it's in the "lowpan" directory] tnx, -gabriel _______________________________________________ 6lowpan mailing list 6lowpan@lists.ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Tue Feb 15 05:52:50 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA16840; Tue, 15 Feb 2005 05:52:50 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D10f6-0000z7-EP; Tue, 15 Feb 2005 06:14:36 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D10Ih-00029i-Ls; Tue, 15 Feb 2005 05:51:27 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D10GC-0001cu-IK for 6lowpan@megatron.ietf.org; Tue, 15 Feb 2005 05:48:52 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA16548 for <6lowpan@ietf.org>; Tue, 15 Feb 2005 05:48:50 -0500 (EST) Received: from mailout3.samsung.com ([203.254.224.33]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D10bA-0000sy-26 for 6lowpan@ietf.org; Tue, 15 Feb 2005 06:10:36 -0500 Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) id <0IBY00H018OFEL@mailout3.samsung.com> for 6lowpan@ietf.org; Tue, 15 Feb 2005 19:48:15 +0900 (KST) 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 <0IBY00HMS8OFKH@mailout3.samsung.com> for 6lowpan@ietf.org; Tue, 15 Feb 2005 19:48:15 +0900 (KST) Received: from LocalHost ([168.219.198.109]) by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTPA id <0IBY004H68OFSI@mmp2.samsung.com> for 6lowpan@ietf.org; Tue, 15 Feb 2005 19:48:15 +0900 (KST) Date: Tue, 15 Feb 2005 19:50:27 +0900 From: Soohong Daniel Park Subject: RE: [6lowpan] 00 version of Goals and Assumptions submitted In-reply-to: <42114136.9020805@sun.com> To: gabriel montenegro , 6lowpan@ietf.org Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Content-type: text/plain; charset=ISO-2022-JP Content-transfer-encoding: 7BIT Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal X-Spam-Score: 0.0 (/) X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4 Content-Transfer-Encoding: 7BIT X-BeenThere: 6lowpan@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.lists.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: 6lowpan-bounces@ietf.org Errors-To: 6lowpan-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 25620135586de10c627e3628c432b04a Content-Transfer-Encoding: 7BIT Hi Nandakishore and Gabriel Overall looks good for me and several comments are as below; 1. similar words make an unnecessary confusion, for example LoWPAN, LoWPANs, LoWPAN network and LoWPAN networks I guess all above term mentions the same meaning through this document. Personally, LoWPAN is so preferable. 2. Prior to addressing the section 4.1, the related assumption should be indicated in the section 3. For example, Devices within LoWPAN have a IP function to discover, control, manage and communicate with each other. Further, IPv6 is considered in this document to support the unique address to the large number of devices. 3. Regarding the section 4.2, I am not sure why topologies including mesh and star of IEEE 802.15.4 is a problematic. 4. In section 6 Instead of TBD, I'd propose below mention simply, No IANA considerations are required in this document. Thanks. Daniel (Soohong Daniel Park) Mobile Platform Lab. Samsung Electronics. > -----Original Message----- > From: 6lowpan-bounces@lists.ietf.org > [mailto:6lowpan-bounces@lists.ietf.org]On Behalf Of gabriel montenegro > Sent: Tuesday, February 15, 2005 9:24 AM > To: 6lowpan@ietf.org > Subject: [6lowpan] 00 version of Goals and Assumptions submitted > > > Folks, > > We've submitted the first *official* version of this draft > (previous ones had circulated > on the alias, though). > > The draft is available in anticipation of it appearing at the IETF > repository in either html or txt formats: > > draft-kushalnagar-lowpan-goals-assumptions-00.txt > draft-kushalnagar-lowpan-goals-assumptions-00.html > > To fetch it, please go here: > > http://f2.pg.briefcase.yahoo.com/gabriel_montenegro_2000 > > [it's in the "lowpan" directory] > > tnx, > > -gabriel > > > > _______________________________________________ > 6lowpan mailing list > 6lowpan@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/6lowpan > > _______________________________________________ 6lowpan mailing list 6lowpan@lists.ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Thu Feb 17 02:18:15 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12298; Thu, 17 Feb 2005 02:18:14 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1gGt-000252-1k; Thu, 17 Feb 2005 02:40:23 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1fsF-00010I-Be; Thu, 17 Feb 2005 02:14:55 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1fqJ-0000KU-2W for 6lowpan@megatron.ietf.org; Thu, 17 Feb 2005 02:12:56 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07114 for <6lowpan@ietf.org>; Thu, 17 Feb 2005 02:12:54 -0500 (EST) Received: from dyn50.sunlabs.com ([204.153.12.50] helo=mail-mta.sunlabs.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1gBh-0001we-7e for 6lowpan@ietf.org; Thu, 17 Feb 2005 02:35:02 -0500 Received: from mail.sunlabs.com ([152.70.2.186]) by mail-mta.sfvic.sunlabs.com (Sun Java System Messaging Server 6.1 HotFix 0.02 (built Aug 25 2004)) with ESMTP id <0IC100704O0M9C00@mail-mta.sfvic.sunlabs.com> for 6lowpan@ietf.org; Wed, 16 Feb 2005 23:12:22 -0800 (PST) Received: from [172.16.1.34] ([69.106.235.181]) by mail.sunlabs.com (Sun Java System Messaging Server 6.1 HotFix 0.02 (built Aug 25 2004)) with ESMTPSA id <0IC100C4KO0I8A10@mail.sunlabs.com> for 6lowpan@ietf.org; Wed, 16 Feb 2005 23:12:18 -0800 (PST) Date: Wed, 16 Feb 2005 23:12:18 -0800 From: gabriel montenegro Subject: Re: [6lowpan] 00 version of Goals and Assumptions submitted In-reply-to: To: Soohong Daniel Park Message-id: <421443D2.8010006@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-2022-JP Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en References: User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Spam-Score: 0.0 (/) X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955 Content-Transfer-Encoding: 7BIT Cc: 6lowpan@ietf.org X-BeenThere: 6lowpan@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.lists.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: 6lowpan-bounces@ietf.org Errors-To: 6lowpan-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d Content-Transfer-Encoding: 7BIT Soohong Daniel Park wrote: > Hi Nandakishore and Gabriel > > Overall looks good for me and several comments are as below; thanks > 1. similar words make an unnecessary confusion, for example > LoWPAN, LoWPANs, LoWPAN network and LoWPAN networks > I guess all above term mentions the same meaning through this > document. Personally, LoWPAN is so preferable. Well, LoWPAN and LoWPANs are just singular and plural of the same word. But I agree that "LoWPAN network/s" does not make much sense because it is redundant, given that LoWPAN already includes "network/s": low-power wireless personal area *networks*. Modified accordingly. > 2. Prior to addressing the section 4.1, the related assumption > should be indicated in the section 3. For example, > > Devices within LoWPAN have a IP function to discover, control, > manage and communicate with each other. Further, IPv6 is > considered in this document to support the unique address to > the large number of devices. Ok, what I did was move the first numbered list under IP connectivity to the end of section 3 as follows: IP technology is assumed to provide the following benefits: 1. The pervasive nature of IP networks allows use of existing infrastructure. 2. IP based technologies already exist, are well known and proven to be working. 3. An admittedly non-technical but important consideration is that intellectual property conditions for IP networking technology are either more favorable or at least better understood than proprietary and newer solutions. Hope this helps. > 3. Regarding the section 4.2, I am not sure why topologies > including mesh and star of IEEE 802.15.4 is a problematic. Well, we list some items there as to why. perhaps you don't agree with those? Or are you confused by the last paragraph in that section, which I also found lacking. In case this is it, I've reworded that last paragraph slightly as follows: As with mesh topologies, star topologies include provisioning a subset of devices with packet forwarding functionality. If, in addition to IEEE 802.15.4, these devices use other kinds of network interfaces such as ethernet, IEEE 802.11, etc., the goal is to seamlessly integrate the networks built over those different technologies. This, or course, is a primary motivation to use IP to begin with. > 4. In section 6 > Instead of TBD, I'd propose below mention simply, > > No IANA considerations are required in this document. I've filled in this section. thanks! -gabriel _______________________________________________ 6lowpan mailing list 6lowpan@lists.ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Sun Feb 20 07:48:16 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29642; Sun, 20 Feb 2005 07:48:16 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2qra-0004cK-7s; Sun, 20 Feb 2005 08:11:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D2p8j-00045g-JP; Sun, 20 Feb 2005 06:20:41 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D2nvO-0007O1-B2 for 6lowpan@megatron.ietf.org; Sun, 20 Feb 2005 05:02:50 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18401 for <6lowpan@ietf.org>; Sun, 20 Feb 2005 05:02:42 -0500 (EST) Received: from dyn50.sunlabs.com ([204.153.12.50] helo=mail-mta.sunlabs.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2oHM-0000KZ-6V for 6lowpan@ietf.org; Sun, 20 Feb 2005 05:25:32 -0500 Received: from mail.sunlabs.com ([152.70.2.186]) by mail-mta.sfvic.sunlabs.com (Sun Java System Messaging Server 6.1 HotFix 0.02 (built Aug 25 2004)) with ESMTP id <0IC70080SFVIT600@mail-mta.sfvic.sunlabs.com> for 6lowpan@ietf.org; Sun, 20 Feb 2005 02:02:06 -0800 (PST) Received: from [192.168.1.40] ([66.89.130.142]) by mail.sunlabs.com (Sun Java System Messaging Server 6.1 HotFix 0.02 (built Aug 25 2004)) with ESMTPSA id <0IC700E7RFVD0800@mail.sunlabs.com> for 6lowpan@ietf.org; Sun, 20 Feb 2005 02:02:04 -0800 (PST) Date: Sun, 20 Feb 2005 02:01:24 -0800 From: gabriel montenegro To: 6lowpan@ietf.org Message-id: <42185FF4.9040707@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-2022-JP Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Spam-Score: 0.0 (/) X-Scan-Signature: cdb443e3957ca9b4c5b55e78cfcf4b26 Content-Transfer-Encoding: 7BIT Subject: [6lowpan] Agenda and latest charter X-BeenThere: 6lowpan@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.lists.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: 6lowpan-bounces@ietf.org Errors-To: 6lowpan-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 926f893f9bbbfa169f045f85f0cdb955 Content-Transfer-Encoding: 7BIT Folks, According to the cutoff dates for the next IETF: http://www.ietf.org/meetings/cutoff_dates_62.html We have until this Monday to make our scheduling changes. We have asked for a 2 hour slot as per the request included below. Even though it does not appear yet on the preliminary agenda, it will appear in due time. Below you'll see the proposed slot agenda as well as the current version of the charter for our working group proposal. Please send in any further suggestions to the agenda soon. thanks, -gabriel ------------------------------------------------------------------------------- NOTE: Request for for a slot in Minneapolis was done using the format for BoF meetings, although it is expected to become a WG before the meeting. ------------------------------------------------------------------------------- a. IPv6 over IEEE 802.15.4 [6LOWPAN] ("IPv6 over low-power WPAN") b. Internet Area (int) Thomas Narten Margaret Wasserman c. Conflicts to Avoid: IPv6, V6OPS, MANET, ROHC, MOBOPTS, MIP6, MULTI6, CAPWAP, MOBIKE, NEMO, RFID, AUTOCONF d. Expected Attendance: 100 e. Special Requests: Not on Friday f. Number of slots: 1 g. Length of slot: 2 hours --------------------------------- IPv6 over IEEE 802.15.4 [6LOWPAN] --------------------------------- Chairs: Geoff Mulligan Nandakishore Kushalnagar Gabriel Montenegro Duration: 2 Hour Agenda: Agenda Bashing 5m Problem Statement 25m 6LoWPAN: Overview, Requirements, Assumptions, Problems and Goals draft-kushalnagar-lowpan-goals-assumptions The original milestones targetted a WG last call on this document for February, which is not likely. Thus, this slot will hopefully arrive at closure to prepare for the WG last call. IPv6 over IEEE 802.15.4 30m Transmission of IPv6 Packets over IEEE 802.15.4 Networks draft-montenegro-lowpan-ipv6-over-802.15.4 Summarize the decisions taken and the technical approach. Finer details about framing, header compression and packet delivery in a mesh will benefit from the discussion. Security Discussion 20m No draft yet. The purpose is to put forth an initial description of the threat model and the potential solutions in order to better understand which IETF security mechanisms are relevant. Implementation Considerations 20m No draft yet. This slot will allow us to talk about how one would implement such a device. Although this does not directly reflect a document targetted for WG official status, it is important from the point of view of better understanding and sharing what actual "running code" might be like. Gap Discussion 20m No draft yet. The goal is to discuss what other desirable work items are missing from the current charter and how to address them. NOTE: FYI, The WG charter as proposed and as being discussed follows below: ------------------------------------------------------------------------------- IPv6 over IEEE 802.15.4 (6lowpan) Chair(s): ??? Internet Area Director(s): *Thomas Narten * *Margaret Wasserman * Mailing Lists: General Discussion: 6lowpan@lists.ietf.org To Subscribe: 6lowpan-request@lists.ietf.org In Body: subscribe List Info: https://www1.ietf.org/mailman/listinfo/6lowpan Description of Working Group: Note: Given that there is not much precedent for this type of activity at the IETF, the text that follows is of an introductory nature. Hence, its objective is to give a general idea of the application area and motivations for the work. In particular, this section is not to be construed as detailing work items for the working group. That is done in the following section on the "Scope of the Working Group." Well-established fields such as control networks, and burgeoning ones such as "sensor" (or transducer) networks, are increasingly being based on wireless technologies. Most (but certainly not all) of these nodes are amongst the most constrained that have ever been networked wirelessly. Extreme low power (such that they will run potentially for years on batteries) and extreme low cost (total device cost in single digit dollars, and riding Moore's law to continuously reduce that price point) are seen as essential enablers towards their deployment in networks with the following characteristics: * Significantly more devices than current networks * Severely limited code and ram space (e.g., highly desirable to fit the required code--MAC, IP and anything else needed to execute the embedded application-- in, for example, 32K of flash memory, using 8-bit microprocessors) * Unobtrusive but very different user interface for configuration (e.g., using gestures or interactions involving the physical world) * Robustness and simplicity in routing or network fabric A chief component of these devices is wireless communication technology. In particular, the IEEE 802.15.4 standard is very promising for the lower (physical and link) layers. As for higher layer functions, there is considerable interest from non-IETF groups in using IP technology (the ZigBee alliance, for example, is currently studying what such a work item might entail). The working group is expected to coordinate and interact with such groups. The required work includes items in the following (incomplete) list: * IP adaptation/Packet Formats and interoperability * Addressing schemes and address management * Network management * Routing in dynamically adaptive topologies * Security, including set-up and maintenance * Application programming interface * Discovery (of devices, of services, etc) * Implementation considerations Whereas at least some of the above items are within the purview of the IETF, at this point it is not clear that all of them are. Accordingly, the 6LoWPAN working group will address a reduced, more focused set of objectives. Scope of 6lowpan: Produce "Problems Statement, Assumptions and Goals for IPv6 for LoWPANs" (draft-ietf-lowpan-goals-assumptions-xx.txt) to define the problem statement and goals of 6lowpan networks. Produce "Transmission of IPv6 Packets over IEEE 802.15.4 WPAN Networks" (draft-ietf-lowpan-ipv6-over-802.15.4-xx.txt) to define the basic packet formats and sub-IP adaptation layer for transmission of IPv6 packets over IEEE 802.15.4. This includes framing, adaptation, header compression and address generation. Furthermore, IEEE 802.15.4 devices are expected to be deployed in mesh topologies. 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. Goals and Milestones: MAR 2005 Working group last call on draft-ietf-lowpan-goals-assumptions-xx.txt APR 2005 Submit draft-ietf-lowpan-goals-assumptions-xx.txt to IESG for consideration of publication as Informational MAY 2005 Working Group Last Call on draft-ietf-lowpan-ipv6-over-802.15.4-xx.txt JUL 2005 Submit draft-ietf-lowpan-ipv6-over-802.15.4-xx.txt to IESG for consideration of publication as Proposed Standard ------------------------------------------------------------------------ _______________________________________________ 6lowpan mailing list 6lowpan@lists.ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Wed Feb 23 15:49:21 2005 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14413; Wed, 23 Feb 2005 15:49:21 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D43oV-0000yY-Fn; Wed, 23 Feb 2005 16:12:55 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3lkA-0005ft-Qr; Tue, 22 Feb 2005 20:55:14 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3lk7-0005eo-7g for 6lowpan@megatron.ietf.org; Tue, 22 Feb 2005 20:55:12 -0500 Received: from mail-mta.sunlabs.com (dyn50.sunlabs.com [204.153.12.50]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23801 for <6lowpan@lists.ietf.org>; Tue, 22 Feb 2005 20:55:03 -0500 (EST) Received: from mail.sunlabs.com ([152.70.2.186]) by mail-mta.sfvic.sunlabs.com (Sun Java System Messaging Server 6.1 HotFix 0.02 (built Aug 25 2004)) with ESMTP id <0ICC009GDDAMQ700@mail-mta.sfvic.sunlabs.com> for 6lowpan@lists.ietf.org; Tue, 22 Feb 2005 17:54:22 -0800 (PST) Received: from [172.16.1.34] ([69.106.235.181]) by mail.sunlabs.com (Sun Java System Messaging Server 6.1 HotFix 0.02 (built Aug 25 2004)) with ESMTPSA id <0ICC00FF7DAKNZ00@mail.sunlabs.com> for 6lowpan@lists.ietf.org; Tue, 22 Feb 2005 17:54:20 -0800 (PST) Date: Tue, 22 Feb 2005 17:54:22 -0800 From: gabriel montenegro In-reply-to: <41F6AFDF.4060900@sun.com> Message-id: <421BE24E.2010502@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-2022-JP Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en References: <41F6AFDF.4060900@sun.com> User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) Content-Transfer-Encoding: 7BIT Cc: 6lowpan@ietf.org Subject: [6lowpan] 02 version of IP over IEEE 802.15.4 X-BeenThere: 6lowpan@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.lists.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: 6lowpan-bounces@ietf.org Errors-To: 6lowpan-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 Content-Transfer-Encoding: 7BIT Folks, We've submitted a new version of this draft. This version adds UDP to the basic header compression and includes more informative/clarifying text. Draft name is: draft-montenegro-lowpan-ipv6-over-802.15.4-02.txt In anticipation of the draft being available off the IETF repository, I've posted it here: http://f2.pg.briefcase.yahoo.com/gabriel_montenegro_2000 [it's in the "lowpan" directory] There, you'll find a txt as well as an html version (both dated Feb 21). tnx, -gabriel _______________________________________________ 6lowpan mailing list 6lowpan@lists.ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan