IETF Logo Mail Archive

Re: [6lowpan] 01 version of IP over IEEE 802.15.4

Shoichi Sakane <sakane@kame.net> Wed, 09 February 2005 06:04 UTC

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 <sakane@kame.net>
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: <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@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

v2.23.0 | Report a Bug | By Email