[6lowpan] Re: Comments on the Format-02 document
gabriel montenegro <gabriel_montenegro_2000@yahoo.com> Sat, 24 June 2006 16:50 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FuBKh-00036b-LV; Sat, 24 Jun 2006 12:50:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FuBKg-00035Z-H0 for 6lowpan@ietf.org; Sat, 24 Jun 2006 12:50:06 -0400
Received: from web81904.mail.mud.yahoo.com ([68.142.207.183]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FuBKf-0007AD-Uy for 6lowpan@ietf.org; Sat, 24 Jun 2006 12:50:06 -0400
Received: (qmail 71227 invoked by uid 60001); 24 Jun 2006 16:50:05 -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:In-Reply-To:MIME-Version:Content-Type; b=RbqXBR8T3N+LQXfKgZ/0eG5DZos0JD6wm40O+GEaGva+chwoNT5clSbDUSCyHJJ1DOMiMOkdVXUL1E3nk/Wx9ONjWqY13kL9Wk2etbshMd/d9J+IWMgSdMF8r8biEuz29egSjHpnf24eJP2W+X8L38UMGczwtWIlACnb+iWBurc= ;
Message-ID: <20060624165005.71225.qmail@web81904.mail.mud.yahoo.com>
Received: from [200.21.190.118] by web81904.mail.mud.yahoo.com via HTTP; Sat, 24 Jun 2006 09:50:05 PDT
Date: Sat, 24 Jun 2006 09:50:05 -0700
From: gabriel montenegro <gabriel_montenegro_2000@yahoo.com>
To: Samita Chakrabarti <samitac2@gmail.com>, 6lowpan@ietf.org
In-Reply-To: <43b91d370604281745j765a191bp22843d890af5eab9@mail.gmail.com>
MIME-Version: 1.0
X-Spam-Score: 1.4 (+)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c
Cc:
Subject: [6lowpan] Re: Comments on the Format-02 document
X-BeenThere: 6lowpan@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: gabriel montenegro <gabriel_montenegro_2000@yahoo.com>
List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/6lowpan>
List-Post: <mailto:6lowpan@ietf.org>
List-Help: <mailto:6lowpan-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1202441649=="
Errors-To: 6lowpan-bounces@ietf.org
inline... ----- Original Message ---- From: Samita Chakrabarti <samitac2@gmail.com> To: gabriel montenegro <gabriel_montenegro_2000@yahoo.com>; 6lowpan@ietf.org Sent: Friday, April 28, 2006 5:45:12 PM Subject: Comments on the Format-02 document Hello Gabriel: Here are some comments on the latest version of the format document. Hope they are not too late. Thanks, -Samita Nits: Typo in Introduction: Likewise, the provisions required for packet delivery in IEEE 802.15.4 meshes <is> defined. Section 2. gab> reworded slightly "As usual, hosts learn IPv6 prefixes via router advertisements ([I-D.ietf-ipv6-2461bis])." Does it make sense to mention about ND for lowpan work in this context as well ? gab> just mentioned that the WG may be pursuing more work here. Section 4 ( Reassembly): Each fragment contains "datagram_size" and datagram_tag and offset. Should "datagram_size" be replaced by "fragment_size" for the fragmented packets ? Is there anyway, during re-assembly one would know about the fragment payload size ? Note that the offset and datagram_size do not provide the info on the current fragment size. gab> I left it as datagram_size, because that is what it means: the size of the entire IP layer datagram. The size of this particular fragment can be inferred from the PPDU information (the "Frame Length" field in the PHY 802.15.4 packet). Section 7. Please have a subheading for defining the IPv6 SLLA, TLLA option formats. On the first look, it is a bit confusing as it seems IPv6 unicast address mapping from the 802.15.4 short and long addresses. gab> Left it as is, since this is exactly the same thing that the IP over ethernet spec (rfc 2464) says. SLLA/TLLA is already mentioned as in that document: The Source/Target Link-layer Address option has the following forms when the link layer is IEEE 802.15.4 and the addresses are EUI-64 or 16-bit short addresses, respectively. Section 8. Please clarify that multicast 802.15.4 address is 16bit address. Q: Can IETF specify such L2 addressing and specification ? Is there any plan on IEEE to accomodate this feature? gab> done. dunno about IEEE. I don't expect they're doing this, as this is done here to map IPv6 multicast addresses specifically. Notice that this support is optional in our format document, as the full specification is not to be done here, but in other document. The rest looks ok to me. The header compression part is a bit tricky and complex. Should this draft suggest a default header compression scheme for a suggestion to the implementors? gab> Dunno, I think there is text already very strongly suggesting this be supported (otherwise IPv6 is not practical). thanks, -gabriel
_______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www1.ietf.org/mailman/listinfo/6lowpan
- [6lowpan] Comments on the Format-02 document Samita Chakrabarti
- [6lowpan] Re: Comments on the Format-02 document gabriel montenegro