RE: [6lowpan] 6lowpan hallway pre-meeting
"Kushalnagar, Nandakishore" <nandakishore.kushalnagar@intel.com> Wed, 03 August 2005 14:07 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E0Ju0-0007oa-J4; Wed, 03 Aug 2005 10:07:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E0Jtx-0007o2-J6 for 6lowpan@megatron.ietf.org; Wed, 03 Aug 2005 10:07:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18593 for <6lowpan@ietf.org>; Wed, 3 Aug 2005 10:07:19 -0400 (EDT)
Received: from fmr18.intel.com ([134.134.136.17] helo=orsfmr003.jf.intel.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E0KQe-0002mZ-Ii for 6lowpan@ietf.org; Wed, 03 Aug 2005 10:41:09 -0400
Received: from orsfmr100.jf.intel.com (orsfmr100.jf.intel.com [10.7.209.16]) by orsfmr003.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 j73E79WE019794 for <6lowpan@ietf.org>; Wed, 3 Aug 2005 14:07:09 GMT
Received: from orsmsxvs041.jf.intel.com (orsmsxvs041.jf.intel.com [192.168.65.54]) by orsfmr100.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 j73E78VV015738 for <6lowpan@ietf.org>; Wed, 3 Aug 2005 14:07:09 GMT
Received: from orsmsx331.amr.corp.intel.com ([192.168.65.56]) by orsmsxvs041.jf.intel.com (SAVSMTP 3.1.7.47) with SMTP id M2005080307070918979 for <6lowpan@ietf.org>; Wed, 03 Aug 2005 07:07:09 -0700
Received: from orsmsx410.amr.corp.intel.com ([192.168.65.64]) by orsmsx331.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 3 Aug 2005 07:06:33 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
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] 6lowpan hallway pre-meeting
Date: Wed, 03 Aug 2005 07:06:31 -0700
Message-ID: <9D602ABCE51B0B488BF857A4787939B5055D0060@orsmsx410>
Thread-Topic: [6lowpan] 6lowpan hallway pre-meeting
thread-index: AcWV9bStxfGgVGk6STmrH9vCNLgjKgCNWHUw
From: "Kushalnagar, Nandakishore" <nandakishore.kushalnagar@intel.com>
To: 6lowpan@ietf.org
X-OriginalArrivalTime: 03 Aug 2005 14:06:33.0908 (UTC) FILETIME=[8E104740:01C59834]
X-Scanned-By: MIMEDefang 2.44
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Content-Transfer-Encoding: quoted-printable
Cc:
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: <https://www1.ietf.org/mailman/listinfo/6lowpan>, <mailto:6lowpan-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/6lowpan>
List-Post: <mailto:6lowpan@lists.ietf.org>
List-Help: <mailto:6lowpan-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/6lowpan>, <mailto:6lowpan-request@lists.ietf.org?subject=subscribe>
Sender: 6lowpan-bounces@lists.ietf.org
Errors-To: 6lowpan-bounces@lists.ietf.org
All, Thanks for the meeting minutes. I am sorry I could not attend. My initial comments: Address assignment: Before I comment on this I agree scalability is a concern in routing, but I am a bit concerned of assuming the amount of "MAC technologies" embedded into addresses such as the topology information. In this path, I am afraid that solutions would not be generic enough. From my perspective, I think how addresses are assigned is implementation dependent. Dictating the addressing methodology to have implicit routing information is an interesting idea but not sure all implementations may need it. Decoupling the addressing and routing because of the following reasons: 1. Making a node to route a particular fashion may not be suitable for lowpans as nodes are constrained in different manners. (bandwidth, energy, etc) and may want to choose routing via different nodes depending on these constraints. 2. Heterogeneity can exist at different layers. Various kinds of heterogeneity may exist. Addressing is just one kind of service. 3. Specifying how MAC addresses are assigned may not be an IETF concern. Optimization: I agree that device constraints restrain the packet size. My 2c for the "It is not quite clear what we are optimizing for", is in my mind, I think we one of the many things that we may are optimizing for is the control messages to be within one 802.15.4 packet. (Control packets could be packets needed to maintain the network such as routing packets, etc.) The others are of course the amount of packets needed, methods for disseminating packets, etc. I also want to capture one more important application that I found missing here is the industrial automation space: This includes proactive maintenance, machine monitoring, etc. This is an important space as this has some unique requirements is characterized by frequent bursty data but less frequent in terms of collection cycles. Interface to routing: I really like the "plug and play" concept for routing layers as the routing protocol is application dependent. One strategy we may choose to do is to specify frame work for reactive and proactive routing protocols at LoWPAN and specify guidelines for adapting routing layer to lowpans. Nandu am a little concerned about specifying addresses where routing is embedded. -----Original Message----- From: 6lowpan-bounces@lists.ietf.org [mailto:6lowpan-bounces@lists.ietf.org] On Behalf Of Carsten Bormann Sent: Sunday, July 31, 2005 10:29 AM To: 6lowpan@ietf.org Cc: Carsten Bormann Subject: [6lowpan] 6lowpan hallway pre-meeting Lowpanners, there are 9 drafts that are relevant to this week's meeting at the IETF. Two working group drafts: draft-ietf-6lowpan-format-00.txt draft-ietf-6lowpan-problem-00.txt Seven independent submissions: draft-chakrabarti-lowpan-ipv6-nd-00.txt draft-chakrabarti-mobopts-lowpan-req-00.txt draft-daniel-6lowpan-hilow-hierarchical-routing-00.txt draft-daniel-6lowpan-interoperability-01.txt draft-daniel-6lowpan-load-adhoc-routing-01.txt draft-daniel-6lowpan-sslp-00.txt draft-montenegro-lowpan-aodv-00.txt It is pretty clear that we can't cover this ground in the one-hour meeting we have on the official agenda. Since most of the authors and other interested people are here in Paris, I'm proposing that we have an off-line meeting Monday, 18:30, at the corner of the terminal room to the right of the entrance (where the L-shaped table arrangement is). We need to discuss: What is the impact of each of the seven independent submissions on the probable course of action? Is the charter's assumption that we'll finish the encapsulation/ format first and then tackle security/routing the right way forward? Are the additional proposals going to require changes in our current standards track document (draft-ietf-6lowpan-format-00.txt)? What do the authors want to have happen to the additional submissions? Of course, no decisions are made in smoke-filled rooms; this is just about maximizing use of the face time. We will summarize the discussion to the list. Gruesse, Carsten _______________________________________________ 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
- [6lowpan] 6lowpan hallway pre-meeting Carsten Bormann
- Re: [6lowpan] 6lowpan hallway pre-meeting Soohong Daniel Park
- Re: [6lowpan] 6lowpan hallway pre-meeting gabriel montenegro
- Re: [6lowpan] 6lowpan hallway pre-meeting Geoff Mulligan
- Re: [6lowpan] 6lowpan hallway pre-meeting Soohong Daniel Park
- [6lowpan] Notes in Wiki (Re: 6lowpan hallway pre-… Carsten Bormann
- RE: [6lowpan] 6lowpan hallway pre-meeting Kushalnagar, Nandakishore
- Re: [6lowpan] 6lowpan hallway pre-meeting Carsten Bormann
- RE: [6lowpan] 6lowpan hallway pre-meeting Kushalnagar, Nandakishore
- Re: [6lowpan] 6lowpan hallway pre-meeting Tiago Camilo