From 6lowpan-bounces@ietf.org Thu Aug 03 20:55:48 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G8nyd-0007IH-Gr; Thu, 03 Aug 2006 20:55:47 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G8nyc-00079K-Cs for 6lowpan@lists.ietf.org; Thu, 03 Aug 2006 20:55:46 -0400 Received: from web81901.mail.mud.yahoo.com ([68.142.207.180]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1G8nyZ-0000aj-Vk for 6lowpan@lists.ietf.org; Thu, 03 Aug 2006 20:55:46 -0400 Received: (qmail 62684 invoked by uid 60001); 4 Aug 2006 00:55:41 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=Z4ZqTvpC1vS5y9dWQlmgL2ywCRD/4tE+cW9Wx+bJVsNxx6RXJaus7iZ3IWXhv8EErS/n9shemo+mdMP3LJNTAtyi64sG1VcfYgGG3WgYXfWg5RHax+1UnJwSy9MCU6FKMlW0N0pDe1057euev3Y05qCSF8rntLKJOYiK8L2vkf0= ; Message-ID: <20060804005541.62682.qmail@web81901.mail.mud.yahoo.com> Received: from [131.107.0.103] by web81901.mail.mud.yahoo.com via HTTP; Thu, 03 Aug 2006 17:55:41 PDT Date: Thu, 3 Aug 2006 17:55:41 -0700 (PDT) From: gabriel montenegro Subject: Re: [6lowpan] WG Last call on Problem Statement Document To: Geoff Mulligan , 6lowpan <6lowpan@lists.ietf.org> In-Reply-To: <1153344589.4878.38.camel@localhost> MIME-Version: 1.0 X-Spam-Score: 1.0 (+) X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c Cc: Carsten Bormann X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gabriel montenegro 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="===============1967636184==" Errors-To: 6lowpan-bounces@ietf.org --===============1967636184== Content-Type: multipart/alternative; boundary="0-835673349-1154652941=:60163" --0-835673349-1154652941=:60163 Content-Type: text/plain; charset=us-ascii Based on discussion this time around, I added this text to the end of 4.3. Limited Packet Size: ... Along these lines, IPv6's requirement of sub-IP reassembly (see Section 5) may pose challenges for low-end LoWPAN devices that do not have enough RAM or storage for a 1280-octet packet. and have submitted it as version 05. Should show up soon in the internet-drafts repository. This has now gone through two WG LC's and is ready for IESG when it appears on the repository -gabriel ----- Original Message ---- From: Geoff Mulligan To: 6lowpan <6lowpan@lists.ietf.org> Sent: Wednesday, July 19, 2006 2:29:49 PM Subject: [6lowpan] WG Last call on Problem Statement Document Folks, This note formally starts the WG Last Call for comments on draft-ietf-6lowpan-problem-04.txt, "6LoWPAN: Overview, Assumptions, Problem Statement and Goals". The document can be found at: http://www.ietf.org/internet-drafts/draft-ietf-6lowpan-problem-04.txt The document is intended to be submitted by this Working Group to the IESG for publication as an Informational Document. Please review the document carefully (one last time), and send your comments to the 6lowpan list. Please also indicate in your response whether or not you think this document is ready to go to the IESG. This Last Call will end on Wednesday 02 August 2006 at 2359 UTC. Thanks, Geoff & Carsten _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --0-835673349-1154652941=:60163 Content-Type: text/html; charset=us-ascii
Based on discussion this time around, I added this text to the end of
4.3.  Limited Packet Size:
 
    ... Along these lines, IPv6's requirement of sub-IP
   reassembly (see Section 5) may pose challenges for low-end LoWPAN
   devices that do not have enough RAM or storage for a 1280-octet
   packet.

and have submitted it as version 05. Should show up soon in the internet-drafts repository.
This has now gone through two WG LC's and is ready for IESG when it appears on
the repository
 
-gabriel
----- Original Message ----
From: Geoff Mulligan <geoff@mulligan.com>
To: 6lowpan <6lowpan@lists.ietf.org>
Sent: Wednesday, July 19, 2006 2:29:49 PM
Subject: [6lowpan] WG Last call on Problem Statement Document

Folks,
  This note formally starts the WG Last Call for comments on
draft-ietf-6lowpan-problem-04.txt, "6LoWPAN: Overview, Assumptions,
Problem Statement and Goals".

The document can be found at:
http://www.ietf.org/internet-drafts/draft-ietf-6lowpan-problem-04.txt

The document is intended to be submitted by this Working Group to the
IESG for publication as an Informational Document.

Please review the document carefully (one last time), and send your
comments to the 6lowpan list.  Please also indicate in your response
whether or not you think this document is ready to go to the IESG.

This Last Call will end on Wednesday 02 August 2006 at 2359 UTC.

    Thanks,
        Geoff & Carsten



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

--0-835673349-1154652941=:60163-- --===============1967636184== 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 --===============1967636184==-- From 6lowpan-bounces@ietf.org Thu Aug 03 21:25:40 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G8oRX-0003Pc-PD; Thu, 03 Aug 2006 21:25:39 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G8oRW-0003NM-If for 6lowpan@lists.ietf.org; Thu, 03 Aug 2006 21:25:38 -0400 Received: from web81902.mail.mud.yahoo.com ([68.142.207.181]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1G8oRV-0006dO-7F for 6lowpan@lists.ietf.org; Thu, 03 Aug 2006 21:25:38 -0400 Received: (qmail 83588 invoked by uid 60001); 4 Aug 2006 01:25:36 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=biTEtF7628WxP5YansRU5UiH7uxLf++a7LZLFUKc4DTTt1oENURARY8VbTFbtk1b2y8M8z1BeJp5qHQXS+gc/Rz3QChOuDwfV7z/XGhHaWU4m4LDcgVHniSFleZW44Kr7pVSVRHTyV75WtW4M06MMwV9uShfZxRLNxGXuOzWdLw= ; Message-ID: <20060804012536.83586.qmail@web81902.mail.mud.yahoo.com> Received: from [131.107.0.103] by web81902.mail.mud.yahoo.com via HTTP; Thu, 03 Aug 2006 18:25:36 PDT Date: Thu, 3 Aug 2006 18:25:36 -0700 (PDT) From: gabriel montenegro Subject: Re: [6lowpan] WG Last Call on Format Document To: Geoff Mulligan , 6lowpan <6lowpan@lists.ietf.org> In-Reply-To: <1153344785.4878.41.camel@localhost> MIME-Version: 1.0 X-Spam-Score: 1.0 (+) X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 Cc: Carsten Bormann X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gabriel montenegro 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="===============1313194180==" Errors-To: 6lowpan-bounces@ietf.org --===============1313194180== Content-Type: multipart/alternative; boundary="0-178648927-1154654736=:76418" --0-178648927-1154654736=:76418 Content-Type: text/plain; charset=us-ascii The only thing mentioned during this WG LC was Daniel's pointing out some minor cosmetics in a couple of diagrams (figures 8 & 9). With those changes incorporated, I have resubmitted as version 04. Once it appears in the repository, this draft is ready to progress to the IESG> tnx, -gabriel ----- Original Message ---- From: Geoff Mulligan To: 6lowpan <6lowpan@lists.ietf.org> Sent: Wednesday, July 19, 2006 2:33:05 PM Subject: [6lowpan] WG Last Call on Format Document Folks, This note formally starts the WG Last Call for comments on draft-ietf-6lowpan-format-03, "Transmission of IPv6 Packets over IEEE 802.15.4 Networks draft-ietf-6lowpan-format-03". The document can be found at: http://www.ietf.org/internet-drafts/draft-ietf-6lowpan-format-03.txt The document is intended to be submitted by this Working Group to the IESG for publication as an Proposed Standard Document. Please review the document carefully (one last time), and send your comments to the 6lowpan list. Please also indicate in your response whether or not you think this document is ready to go to the IESG. This Last Call will end on Wednesday 02 August 2006 at 2359 UTC. Thanks, Geoff & Carsten _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan --0-178648927-1154654736=:76418 Content-Type: text/html; charset=us-ascii
The only thing mentioned during this WG LC was Daniel's pointing out some minor cosmetics in a couple
of diagrams (figures 8 & 9). With those changes incorporated, I have resubmitted as version 04.
 
Once it appears in the repository, this draft is ready to progress to the IESG>
 
tnx,
 
-gabriel

----- Original Message ----
From: Geoff Mulligan <geoff@mulligan.com>
To: 6lowpan <6lowpan@lists.ietf.org>
Sent: Wednesday, July 19, 2006 2:33:05 PM
Subject: [6lowpan] WG Last Call on Format Document

Folks,
  This note formally starts the WG Last Call for comments on
draft-ietf-6lowpan-format-03, "Transmission of IPv6 Packets over IEEE
802.15.4 Networks draft-ietf-6lowpan-format-03".

The document can be found at:
http://www.ietf.org/internet-drafts/draft-ietf-6lowpan-format-03.txt

The document is intended to be submitted by this Working Group to the
IESG for publication as an Proposed Standard Document.

Please review the document carefully (one last time), and send your
comments to the 6lowpan list.  Please also indicate in your response
whether or not you think this document is ready to go to the IESG.

This Last Call will end on Wednesday 02 August 2006 at 2359 UTC.

        Thanks,
                Geoff & Carsten



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

--0-178648927-1154654736=:76418-- --===============1313194180== 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 --===============1313194180==-- From 6lowpan-bounces@ietf.org Fri Aug 04 18:34:04 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G98F1-0001J9-V2; Fri, 04 Aug 2006 18:34:03 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G98F0-0001IQ-6o for 6lowpan@lists.ietf.org; Fri, 04 Aug 2006 18:34:02 -0400 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 1G95tT-00069B-W9 for 6lowpan@lists.ietf.org; Fri, 04 Aug 2006 16:03:40 -0400 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G95gm-0007NI-B6 for 6lowpan@lists.ietf.org; Fri, 04 Aug 2006 15:50:37 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 23591175A1; Fri, 4 Aug 2006 19:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1G95gH-0003sJ-PX; Fri, 04 Aug 2006 15:50:01 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Fri, 04 Aug 2006 15:50:01 -0400 X-Spam-Score: -5.9 (-----) X-Scan-Signature: 73734d43604d52d23b3eba644a169745 Cc: 6lowpan@lists.ietf.org Subject: [6lowpan] I-D ACTION:draft-ietf-6lowpan-format-04.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-04.txt Pages : 28 Date : 2006-8-4 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-04.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-04.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-04.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-8-4134113.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-6lowpan-format-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-6lowpan-format-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-8-4134113.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 Fri Aug 04 18:41:30 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G98ME-0002Ej-L3; Fri, 04 Aug 2006 18:41:30 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G98ME-0002CB-1F for 6lowpan@lists.ietf.org; Fri, 04 Aug 2006 18:41:30 -0400 Received: from web81915.mail.mud.yahoo.com ([68.142.207.63]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1G98MC-0001xl-My for 6lowpan@lists.ietf.org; Fri, 04 Aug 2006 18:41:30 -0400 Received: (qmail 54549 invoked by uid 60001); 4 Aug 2006 22:41:23 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=AV22HA8DbRokJPmiIt30BZJTUCbeerNEdL3uBCpcYCGKtx2Ha8jn9dcP+rR+EKIirryB4k2+3ZNnVHbO5su9aqD1IH22oKlMsu4T1w1sZwRTnxLtiM832QuhAvd7u3dtRIt7ddOPu1wc+cit7EUhxaPGbfKx9zg1sJz4WILWnp4= ; Message-ID: <20060804224123.54547.qmail@web81915.mail.mud.yahoo.com> Received: from [131.107.0.103] by web81915.mail.mud.yahoo.com via HTTP; Fri, 04 Aug 2006 15:41:23 PDT Date: Fri, 4 Aug 2006 15:41:23 -0700 (PDT) From: gabriel montenegro To: Geoff Mulligan , Carsten Bormann In-Reply-To: MIME-Version: 1.0 X-Spam-Score: 0.9 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Cc: 6lowpan@lists.ietf.org Subject: [6lowpan] Ready for IESG: draft-ietf-6lowpan-problem-05.txt and draft-ietf-6lowpan-format-04.txt X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gabriel montenegro 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="===============0488257552==" Errors-To: 6lowpan-bounces@ietf.org --===============0488257552== Content-Type: multipart/alternative; boundary="0-282184820-1154731283=:53813" --0-282184820-1154731283=:53813 Content-Type: text/plain; charset=us-ascii Esteemed chairs, These drafts are now ready to advance to the IESG: http://www.ietf.org/internet-drafts/draft-ietf-6lowpan-format-04.txt http://www.ietf.org/internet-drafts/draft-ietf-6lowpan-problem-05.txt tnx, -gabriel --0-282184820-1154731283=:53813 Content-Type: text/html; charset=us-ascii

Esteemed chairs,

 

These drafts are now ready to advance to the IESG:

 

http://www.ietf.org/internet-drafts/draft-ietf-6lowpan-format-04.txt

http://www.ietf.org/internet-drafts/draft-ietf-6lowpan-problem-05.txt

 

tnx,

 

-gabriel

--0-282184820-1154731283=:53813-- --===============0488257552== 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 --===============0488257552==-- From 6lowpan-bounces@ietf.org Fri Aug 04 19:23:18 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G990f-0003ct-Rq; Fri, 04 Aug 2006 19:23:17 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G990f-0003Zm-60 for 6lowpan@lists.ietf.org; Fri, 04 Aug 2006 19:23:17 -0400 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 1G95tU-00069B-46 for 6lowpan@lists.ietf.org; Fri, 04 Aug 2006 16:03:40 -0400 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G95gm-0007NK-Bz for 6lowpan@lists.ietf.org; Fri, 04 Aug 2006 15:50:36 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 29B29175A9; Fri, 4 Aug 2006 19:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1G95gH-0003sM-Q7; Fri, 04 Aug 2006 15:50:01 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Fri, 04 Aug 2006 15:50:01 -0400 X-Spam-Score: -5.9 (-----) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Cc: 6lowpan@lists.ietf.org Subject: [6lowpan] I-D ACTION:draft-ietf-6lowpan-problem-05.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 : 6LoWPAN: Overview, Assumptions, Problem Statement and Goals Author(s) : N. Kushalnagar, G. Montenegro Filename : draft-ietf-6lowpan-problem-05.txt Pages : 13 Date : 2006-8-4 This document describes the assumptions, problem statement and goals for transmitting IP over IEEE 802.15.4 networks. The set of goals enumerated in this document form an initial set only. Additional goals may be found necessary over time and may be added to this document. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-6lowpan-problem-05.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-problem-05.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-problem-05.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-8-4134239.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-6lowpan-problem-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-6lowpan-problem-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-8-4134239.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 Sat Aug 05 05:46:58 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G9IkD-0005an-Cm; Sat, 05 Aug 2006 05:46:57 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G9IkC-0005Zg-Kl for 6lowpan@ietf.org; Sat, 05 Aug 2006 05:46:56 -0400 Received: from py-out-1112.google.com ([64.233.166.182]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G9IkA-0006ur-RB for 6lowpan@ietf.org; Sat, 05 Aug 2006 05:46:56 -0400 Received: by py-out-1112.google.com with SMTP id m51so47675pye for <6lowpan@ietf.org>; Sat, 05 Aug 2006 02:46:54 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:to:cc:subject:date:mime-version:content-type:x-priority:x-msmail-priority:x-mailer:x-mimeole:from; b=O/7xPoQVW5UeLf96ip2Uzwrna6dCeaC4TuARx1y0cSC1RvgljRMWOGfcsorQb3SzGCFBvNNMVpOBeR3sgIuiMWBq+AtjuqbvRwTMS+Vs0/BqFUsBuq+ABs/NKfbWd8VeV5OYyKXvrX+hRG4AHoM2IkqWOxstO0uy61c8s+pE78k= Received: by 10.35.96.11 with SMTP id y11mr7012670pyl; Sat, 05 Aug 2006 02:46:54 -0700 (PDT) Received: from Maoer ( [211.144.102.60]) by mx.gmail.com with ESMTP id c12sm516898nzc.2006.08.05.02.46.52; Sat, 05 Aug 2006 02:46:53 -0700 (PDT) Message-ID: <00ef01c6b874$ed928f00$7fc0a8c0@netlab.cs.ecnu.edu.cn> To: "gabriel montenegro" Date: Sat, 5 Aug 2006 17:52:52 +0800 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1807 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1807 From: Mario Mao X-Spam-Score: 1.2 (+) X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632 Cc: 6lowpan@ietf.org Subject: [6lowpan] Some comments about draft-ietf-6lowpan-format-04 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="===============0138953001==" Errors-To: 6lowpan-bounces@ietf.org This is a multi-part message in MIME format. --===============0138953001== Content-Type: multipart/alternative; boundary="----=_NextPart_000_00EC_01C6B8B7.F9478E20" This is a multi-part message in MIME format. ------=_NextPart_000_00EC_01C6B8B7.F9478E20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: base64 SGkgR2FicmllbCwNCg0KVGhlcmUgaXMgc29tZSBjb21tZW50cyBhYm91dCB0aGUgbGFzdCBkcmFm dCwgdGhhbmtzLg0KDQpJbiBTZWN0aW9uIDExLCB0aGUgZHJhZnQgbWVudGlvbnMgdGhhdCBhIHNw ZWNpYWwgZm9ybWF0IG9mICJNZXNoIERlbGl2ZXJ5IiBmaWVsZCBzaG91bGQgYmUgdXNlZCB3aGVu IEJyb2FkY2FzdCBvciBNdWx0aWNhc3QuIFRoaXMga2luZCBvZiBmaWVsZCBpcyBjYWxsZWQgYXMg TWVzaCBCcm9hZGNhc3Qgb3IgTXVsdGljYXN0IERlbGl2ZXJ5IEZpZWxkIGFuZCBhICJTZXF1ZW5j ZSBOdW1iZXIiIGlzIGFkZGVkLg0KDQpGb3IgU291cmNlIE5vZGUsIGl0IHdpbGwgYmUgY2xlYXIg dGhhdCB3aGljaCBraW5kIG9mIGZvcm1hdCBpdCBzaG91bGQgdXNlLiBCdXQgZm9yIERlc3RpbmF0 aW9uIE5vZGUgb3IgUmVsYXkgTm9kZSwgbG9va3MgbGlrZSB0aGVyZSB3aWxsIGJlIHNvbWUgY29u ZnVzaW9uIHdoZW4gdGhleSB0cnlpbmcgdG8gZXhwbGFpbiB0aGlzIGZvcm1hdC4NCg0KVGhlIGNh dXNlIG9mIHN1Y2ggY29uZnVzaW9uIGlzIHRoZSB3YXkgaW5ib3VuZCBOb2RlIGlkZW50aWZ5aW5n IHN1Y2gga2luZCBvZiBmaWVsZCBmb3JtYXQuIEFzIHRoZSBkcmFmdCBtZW50aW9uZWQsIHRoZSBk ZXN0aW5hdGlvbiBhZGRyZXNzIGlzIHRoZSBpZGVudGlmaWNhdGlvbiBvZiBzdWNoIGtpbmQgb2Yg ZmllbGQuIEhvd2V2ZXIsIGZvciB0aGUgRmluYWwgRGVzdGluYXRpb24gQWRkcmVzcyBpcyBiZWhp bmQgdGhlIFNlcXVlbmNlIE51bWJlciwgdGhlIGluYm91bmQgTm9kZSB3aWxsIGJlIHVuYXdhcmUg b2YgdGhlIGV4aXN0ZW5jZSBvZiB0aGlzIGZpZWxkIGJlZm9yZSBpdCBjaGVjayB0aGUgRmluYWwg RGVzdGluYXRpb24gQWRkcmVzcy4gSWYgaW5ib3VuZCBOb2RlIGhhbmRsZSBhbGwgQnJvYWRjYXN0 IERlbGl2ZXJ5IEZpZWxkIGFzIHRoZSBub3JtYWwgIk1lc2ggRGVsaXZlcnkiIGZpZWxkLCB3aGVu IGl0IGJlZ2lucyB0byBjaGVjayB0aGUgRmluYWwgRGVzdGluYXRpb24gQWRkcmVzcywgdGhlcmUg d2lsbCBiZSA4LWJpdHMgc2hpZnQgb2YgdGhlIHJpZ2h0IHBvc2l0aW9uLiBUaGlzIHNjZW5hcmlv IG11c3QgbGVhZCB0byBhbiBtaXN0YWtlLg0KDQpUaGVyZSBpcyBhbHNvIGFub3RoZXIgd2F5IHRv IGlkZW50aWZ5IHRoZSBCcm9hZGNhc3QgRGVsaXZlcnkgRmllbGQuIFRoYXQgaXMgY2hlY2tpbmcg dGhlIGRlc3RpbmF0aW9uIE1BQyBhZGRyZXNzIGluIHRoZSBJRUVFIDgwMi4xNS40IGhlYWRlciAo MHhGRkZGKS4gQnV0IGluIHByYWN0aWNlLCBhbiBJRUVFIDgwMi4xNS40IGJyb2FkY2FzdCBmcmFt ZSBjYW4ndCBiZSBkZWxpdmVyZWQgdG8gZXZlcnkgRU5EIERFVklDRSAoUkZEKS4gVGhpcyBpcyBi ZWNhdXNlIHRoZSBFTkQgREVWSUNFIGRpc2FibGUgaXRzIHRyYW5zY2VpdmVyIGR1cmluZyBDQVAg d2hlbiB0aGVyZSBpcyBubyBmcmFtZSBkaXJlY3RseSBzZW50IHRvIGl0Lg0KDQpUbyBhdm9pZCBz dWNoIGluY29ycmVjdCBzY2VuYXJpbywgb25lIGZsYWcgbWF5IGJlIG5lZWRlZCBpbiB0aGUgZml4 ZWQgZmlsZWQgKGluIEFkYXB0YXRpb24gSGVhZGVyKS4gVGhhdCBtYWtlIGFsbCBub2RlIGNvdWxk IHJlY29nbml6ZSB0aGUgc3BlY2lhbCBCcm9hZGNhc3QgRGVsaXZlcnkgRmllbGQgaW4gcmlnaHQg d2F5Lg0KDQpSZWdhcmRzLA0KDQoNCk1hcmlvIE1hbw0KTWFyaW9NYW9AR21haWwuY29tDQogICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICA= ------=_NextPart_000_00EC_01C6B8B7.F9478E20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu dD0idGV4dC9odG1sOyBjaGFyc2V0PWlzby04ODU5LTEiPg0KPE1FVEEgY29udGVudD0iTVNIVE1M IDYuMDAuMjgwMC4xNTU1IiBuYW1lPUdFTkVSQVRPUj4NCjxTVFlMRT48L1NUWUxFPg0KPC9IRUFE Pg0KPEJPRFkgYmdDb2xvcj0jZmZmZmZmPg0KPERJVj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mj5I aSBHYWJyaWVsLDwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1BcmlhbCBzaXplPTI+PC9G T05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mj5UaGVyZSBpcyBz b21lIGNvbW1lbnRzIGFib3V0IHRoZSBsYXN0IGRyYWZ0LCANCnRoYW5rcy48L0ZPTlQ+PC9ESVY+ DQo8RElWPjxGT05UIGZhY2U9QXJpYWwgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+ PEZPTlQgZmFjZT1BcmlhbCBzaXplPTI+SW4gU2VjdGlvbiAxMSwgdGhlIGRyYWZ0IG1lbnRpb25z IHRoYXQgYSBzcGVjaWFsIA0KZm9ybWF0IG9mICJNZXNoIERlbGl2ZXJ5IiBmaWVsZCBzaG91bGQg YmUgdXNlZCB3aGVuIEJyb2FkY2FzdCBvciBNdWx0aWNhc3QuIFRoaXMgDQpraW5kIG9mIGZpZWxk IGlzIGNhbGxlZCBhcyZuYnNwO01lc2ggQnJvYWRjYXN0IG9yIE11bHRpY2FzdCBEZWxpdmVyeSBG aWVsZCANCmFuZCZuYnNwO2EgIlNlcXVlbmNlIE51bWJlciIgaXMgYWRkZWQuPC9GT05UPjwvRElW Pg0KPERJVj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElW PjxGT05UIGZhY2U9QXJpYWwgc2l6ZT0yPkZvciBTb3VyY2UgTm9kZSwgaXQgd2lsbCBiZSBjbGVh ciB0aGF0IHdoaWNoIGtpbmQgDQpvZiBmb3JtYXQgaXQgc2hvdWxkIHVzZS4gQnV0IGZvciBEZXN0 aW5hdGlvbiBOb2RlIG9yIFJlbGF5IE5vZGUsIGxvb2tzIGxpa2UgDQp0aGVyZSB3aWxsIGJlIHNv bWUgY29uZnVzaW9uIHdoZW4gdGhleSB0cnlpbmcgdG8gZXhwbGFpbiB0aGlzIA0KZm9ybWF0Ljwv Rk9OVD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1BcmlhbCBzaXplPTI+PC9GT05UPiZuYnNwOzwv RElWPg0KPERJVj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mj5UaGUgY2F1c2Ugb2Ygc3VjaCBjb25m dXNpb24gaXMgdGhlIHdheSBpbmJvdW5kIA0KTm9kZSZuYnNwO2lkZW50aWZ5aW5nIHN1Y2gga2lu ZCBvZiBmaWVsZCBmb3JtYXQuIEFzIHRoZSBkcmFmdCBtZW50aW9uZWQsIHRoZSANCmRlc3RpbmF0 aW9uIGFkZHJlc3MgaXMgdGhlIGlkZW50aWZpY2F0aW9uIG9mIHN1Y2gga2luZCBvZiANCmZpZWxk LiZuYnNwO0hvd2V2ZXIsJm5ic3A7Zm9yIHRoZSBGaW5hbCBEZXN0aW5hdGlvbiBBZGRyZXNzIA0K aXMmbmJzcDtiZWhpbmQmbmJzcDt0aGUgU2VxdWVuY2UgTnVtYmVyLCB0aGUgaW5ib3VuZCBOb2Rl IHdpbGwgYmUgdW5hd2FyZSBvZiB0aGUgDQpleGlzdGVuY2Ugb2YgdGhpcyBmaWVsZCBiZWZvcmUg aXQgY2hlY2sgdGhlIEZpbmFsIERlc3RpbmF0aW9uIEFkZHJlc3MuIElmIA0KaW5ib3VuZCBOb2Rl IGhhbmRsZSBhbGwgQnJvYWRjYXN0Jm5ic3A7RGVsaXZlcnkgRmllbGQgYXMgdGhlIG5vcm1hbCAi TWVzaCANCkRlbGl2ZXJ5IiBmaWVsZCwgd2hlbiBpdCBiZWdpbnMgdG8gY2hlY2sgdGhlIEZpbmFs IERlc3RpbmF0aW9uIEFkZHJlc3MsIA0KdGhlcmUmbmJzcDt3aWxsIGJlIDgtYml0cyBzaGlmdCBv ZiB0aGUgcmlnaHQgcG9zaXRpb24uIFRoaXMgc2NlbmFyaW8gbXVzdCBsZWFkIA0KdG8gYW4gbWlz dGFrZS48L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9QXJpYWwgc2l6ZT0yPjwvRk9OVD4m bmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1BcmlhbCBzaXplPTI+VGhlcmUgaXMgYWxzbyBh bm90aGVyIHdheSB0byBpZGVudGlmeSB0aGUgQnJvYWRjYXN0IA0KRGVsaXZlcnkgRmllbGQuIFRo YXQgaXMgY2hlY2tpbmcgdGhlIGRlc3RpbmF0aW9uIE1BQyBhZGRyZXNzIGluIHRoZSBJRUVFIA0K ODAyLjE1LjQmbmJzcDtoZWFkZXIgKDB4RkZGRikuJm5ic3A7QnV0IGluIHByYWN0aWNlLCBhbiBJ RUVFIDgwMi4xNS40IGJyb2FkY2FzdCANCmZyYW1lIGNhbid0IGJlIGRlbGl2ZXJlZCB0byBldmVy eSBFTkQgREVWSUNFIChSRkQpLiBUaGlzIGlzIGJlY2F1c2UgdGhlJm5ic3A7RU5EIA0KREVWSUNF Jm5ic3A7ZGlzYWJsZSBpdHMgdHJhbnNjZWl2ZXImbmJzcDtkdXJpbmcgQ0FQIHdoZW4gdGhlcmUg aXMgbm8gZnJhbWUgDQpkaXJlY3RseSBzZW50IHRvIGl0LjwvRk9OVD48L0RJVj4NCjxESVY+PEZP TlQgZmFjZT1BcmlhbCBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBmYWNl PUFyaWFsIHNpemU9Mj5UbyBhdm9pZCBzdWNoIGluY29ycmVjdCBzY2VuYXJpbywgb25lIGZsYWcg bWF5IGJlIA0KbmVlZGVkIGluIHRoZSBmaXhlZCBmaWxlZCAoaW4gQWRhcHRhdGlvbiBIZWFkZXIp LiBUaGF0IG1ha2UgYWxsIG5vZGUgY291bGQgDQpyZWNvZ25pemUgdGhlIHNwZWNpYWwgQnJvYWRj YXN0IERlbGl2ZXJ5IEZpZWxkIGluIHJpZ2h0IHdheS48L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05U IGZhY2U9QXJpYWwgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1B cmlhbCBzaXplPTI+UmVnYXJkcyw8L0ZPTlQ+PC9ESVY+DQo8RElWPjxCUj4NCjxESVY+PEZPTlQg ZmFjZT1BcmlhbCBzaXplPTI+TWFyaW8gTWFvPC9GT05UPjwvRElWPg0KPERJVj48VT48Rk9OVCBm YWNlPUFyaWFsIGNvbG9yPSMwMDAwZmYgc2l6ZT0yPjxBIA0KaHJlZj0ibWFpbHRvOk1hcmlvTWFv QEdtYWlsLmNvbSI+TWFyaW9NYW9AR21haWwuY29tPC9BPjwvRk9OVD48L1U+PC9ESVY+DQo8RElW PjxGT05UIGZhY2U9QXJpYWwgDQpzaXplPTI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7 Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7 Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7PC9GT05UPjwvRElWPjwvRElWPjwvQk9E WT48L0hUTUw+DQo= ------=_NextPart_000_00EC_01C6B8B7.F9478E20-- --===============0138953001== 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 --===============0138953001==-- From 6lowpan-bounces@ietf.org Tue Aug 08 11:56:29 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GATwS-0008TE-IG; Tue, 08 Aug 2006 11:56:28 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GATwR-0008T9-QN for 6lowpan@ietf.org; Tue, 08 Aug 2006 11:56:27 -0400 Received: from web81908.mail.mud.yahoo.com ([68.142.207.187]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GATwP-0004Wb-6z for 6lowpan@ietf.org; Tue, 08 Aug 2006 11:56:27 -0400 Received: (qmail 6076 invoked by uid 60001); 8 Aug 2006 15:56:24 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=CVNynYHGsDFC2Jy5Z5q1Z9apC/eODr06TmFrz2ZhfRV+5QRAZ7JAJxuZv/a3pJ7b4uwEKxLiGVjtA8mxn4N5j7iAS2ozUug6ORCsQ2W6eNT9NuyzqgLwtAbQJVvLVQzvcuvgNkAgAjwYkR7SyJYR/x9BtyPfSeEUK/pBTNXxzd0= ; Message-ID: <20060808155624.6074.qmail@web81908.mail.mud.yahoo.com> Received: from [24.16.14.130] by web81908.mail.mud.yahoo.com via HTTP; Tue, 08 Aug 2006 08:56:24 PDT Date: Tue, 8 Aug 2006 08:56:24 -0700 (PDT) From: gabriel montenegro To: Mario Mao In-Reply-To: <00ef01c6b874$ed928f00$7fc0a8c0@netlab.cs.ecnu.edu.cn> MIME-Version: 1.0 X-Spam-Score: 0.9 (/) X-Scan-Signature: 0e9ebc0cbd700a87c0637ad0e2c91610 Cc: 6lowpan@ietf.org Subject: [6lowpan] Re: Some comments about draft-ietf-6lowpan-format-04 X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gabriel montenegro 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="===============0826767122==" Errors-To: 6lowpan-bounces@ietf.org --===============0826767122== Content-Type: multipart/alternative; boundary="0-1335176006-1155052584=:5018" --0-1335176006-1155052584=:5018 Content-Type: text/plain; charset=us-ascii Good point, yes. The confusion is that upon reception it is not easy to determine which of the two following mesh header formats is being used because the fixed part of the header does not tell us: 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |O|F| Hops Left | Originator Address... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ...Final Destination Address +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 10: Mesh Delivery Field 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |O|F| Hops Left |Sequence Number| Originator Address... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ...Final Destination Address +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 11: Mesh Broadcast or Multicast Delivery FieldWe could put the indication in the fixed part of the header by : 1. adding a bit field to distinguish. Two alternatives: (a) We could add one bit and move everything after it over one bit. Not that our alignment was great to begin with, but this would make it uglier. (b) We could make this bit field larger than 1 bit, in which case we'd be able to distinguish between the two current formats and leave some bit patterns reserved in case we end up defining other mesh headers in the future. 2. adding a bit by stealing one from, say, hops_left. This means we'd have a max of 32 hops instead of the current 64. I still think this is enough. This would not alter whatever alignment we now have. 3. Grow the 'F' field by one more bit, and assign bit patterns for 64 bit address, 16-bit address and 16-bit bcast/mcast address (as per the current draft). This would leave one bit pattern reserved. 4. Move the distinguishing field, "Final Destination Address" into the fixed part of the header (right after hops_left). Sequence number and originator address would relocate after final destination address. This does not waste any bits, but is esthetically unpleasant. But we may not care about such things. Any others? Comments? Would the folks who are implementing this please express their opinions? -gabriel ----- Original Message ---- From: Mario Mao To: gabriel montenegro Cc: 6lowpan@ietf.org Sent: Saturday, August 5, 2006 2:52:52 AM Subject: Some comments about draft-ietf-6lowpan-format-04 Hi Gabriel, There is some comments about the last draft, thanks. In Section 11, the draft mentions that a special format of "Mesh Delivery" field should be used when Broadcast or Multicast. This kind of field is called as Mesh Broadcast or Multicast Delivery Field and a "Sequence Number" is added. For Source Node, it will be clear that which kind of format it should use. But for Destination Node or Relay Node, looks like there will be some confusion when they trying to explain this format. The cause of such confusion is the way inbound Node identifying such kind of field format. As the draft mentioned, the destination address is the identification of such kind of field. However, for the Final Destination Address is behind the Sequence Number, the inbound Node will be unaware of the existence of this field before it check the Final Destination Address. If inbound Node handle all Broadcast Delivery Field as the normal "Mesh Delivery" field, when it begins to check the Final Destination Address, there will be 8-bits shift of the right position. This scenario must lead to an mistake. There is also another way to identify the Broadcast Delivery Field. That is checking the destination MAC address in the IEEE 802.15.4 header (0xFFFF). But in practice, an IEEE 802.15.4 broadcast frame can't be delivered to every END DEVICE (RFD). This is because the END DEVICE disable its transceiver during CAP when there is no frame directly sent to it. To avoid such incorrect scenario, one flag may be needed in the fixed filed (in Adaptation Header). That make all node could recognize the special Broadcast Delivery Field in right way. Regards, Mario Mao MarioMao@Gmail.com --0-1335176006-1155052584=:5018 Content-Type: text/html; charset=us-ascii
Good point, yes. The confusion is that upon reception it is not easy to determine which of the two following mesh header formats is being used because
the fixed part of the header does not tell us:

                           1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |O|F| Hops Left |            Originator Address...
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
         ...Final Destination Address
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


                      Figure 10: Mesh Delivery
 Field

                           1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |O|F| Hops Left |Sequence Number|     Originator Address...
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
         ...Final Destination Address
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

           Figure 11: Mesh Broadcast or Multicast Delivery Field
We could put the indication in the fixed part of the header by :

1. adding a bit field to distinguish. Two alternatives: (a) We could add one bit and move everything after it over one bit. Not that our alignment was
    great to begin with, but this would make it uglier. (b) We could make this bit field larger than 1 bit, in which case we'd be able
    to distinguish between the two current formats and leave some bit patterns reserved in case we end up defining other
    mesh headers in the future.
2. adding a bit by stealing one from, say, hops_left. This means we'd have a max of 32 hops instead of the current 64. I still think this
    is enough. This would not alter whatever alignment we now have.
3. Grow the 'F' field by one more bit, and assign bit patterns for 64 bit address, 16-bit address and 16-bit bcast/mcast address (as per
    the current draft).
    This would leave one bit pattern reserved.
4. Move the distinguishing field, "Final Destination Address" into the fixed part of the header (right after hops_left). Sequence number and originator
    address would relocate after final destination address. This does not waste any bits, but is esthetically unpleasant. But we may not care about such
    things.

Any others?

Comments? Would the folks who are implementing this please express their opinions?

-gabriel

----- Original Message ----
From: Mario Mao <mariomao@gmail.com>
To: gabriel montenegro <gabriel_montenegro_2000@yahoo.com>
Cc: 6lowpan@ietf.org
Sent: Saturday, August 5, 2006 2:52:52 AM
Subject: Some comments about draft-ietf-6lowpan-format-04

Hi Gabriel,
 
There is some comments about the last draft, thanks.
 
In Section 11, the draft mentions that a special format of "Mesh Delivery" field should be used when Broadcast or Multicast. This kind of field is called as Mesh Broadcast or Multicast Delivery Field and a "Sequence Number" is added.
 
For Source Node, it will be clear that which kind of format it should use. But for Destination Node or Relay Node, looks like there will be some confusion when they trying to explain this format.
 
The cause of such confusion is the way inbound Node identifying such kind of field format. As the draft mentioned, the destination address is the identification of such kind of field. However, for the Final Destination Address is behind the Sequence Number, the inbound Node will be unaware of the existence of this field before it check the Final Destination Address. If inbound Node handle all Broadcast Delivery Field as the normal "Mesh Delivery" field, when it begins to check the Final Destination Address, there will be 8-bits shift of the right position. This scenario must lead to an mistake.
 
There is also another way to identify the Broadcast Delivery Field. That is checking the destination MAC address in the IEEE 802.15.4 header (0xFFFF). But in practice, an IEEE 802.15.4 broadcast frame can't be delivered to every END DEVICE (RFD). This is because the END DEVICE disable its transceiver during CAP when there is no frame directly sent to it.
 
To avoid such incorrect scenario, one flag may be needed in the fixed filed (in Adaptation Header). That make all node could recognize the special Broadcast Delivery Field in right way.
 
Regards,

Mario Mao
                                       

--0-1335176006-1155052584=:5018-- --===============0826767122== 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 --===============0826767122==-- From 6lowpan-bounces@ietf.org Thu Aug 24 01:59:46 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GG8Fm-0001mY-7I; Thu, 24 Aug 2006 01:59:46 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GG8Fk-0001mS-Ic for 6lowpan@lists.ietf.org; Thu, 24 Aug 2006 01:59:44 -0400 Received: from grab.coslabs.com ([199.233.92.34]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GG8Fj-0007Ce-8S for 6lowpan@lists.ietf.org; Thu, 24 Aug 2006 01:59:44 -0400 Received: from dellx1.coslabs.com (dellx1.coslabs.com [199.233.92.20]) by grab.coslabs.com (8.13.6/8.13.6) with ESMTP id k7O5xZm1029050 for <6lowpan@lists.ietf.org>; Wed, 23 Aug 2006 23:59:36 -0600 (MDT) From: Geoff Mulligan To: 6lowpan <6lowpan@lists.ietf.org> Content-Type: text/plain Date: Wed, 23 Aug 2006 23:59:40 -0600 Message-Id: <1156399180.5025.32.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Cc: Subject: [6lowpan] Closing WG last call for Problem 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 Since it appears that we have reached the time limit and consensus on the problem document we are officially closing the WG last call on: http://www.ietf.org/internet-drafts/draft-ietf-6lowpan-problem-05.txt We will be forwarding this document to the IESG, but will probably hold off until we complete the format document. geoff _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan