Re: [16NG] Review on FMIP6 over IEEE 802.16e Networks

Behcet Sarikaya <behcetsarikaya@yahoo.com> Wed, 16 May 2007 16:24 UTC

Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HoMJ2-0003mc-S7; Wed, 16 May 2007 12:24:52 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43) id 1HoMJ1-0003lP-Ua for 16ng-confirm+ok@megatron.ietf.org; Wed, 16 May 2007 12:24:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HoMIy-0003ju-QT for 16ng@ietf.org; Wed, 16 May 2007 12:24:48 -0400
Received: from web84113.mail.mud.yahoo.com ([68.142.206.200]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HoMIy-0008K1-AL for 16ng@ietf.org; Wed, 16 May 2007 12:24:48 -0400
Received: (qmail 29127 invoked by uid 60001); 16 May 2007 16:24:44 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=AdXGVeh0jqTJrxJCwLFkha+VUe8kkosBl9jDCm+AdSN+whBTQ6SW769Awk6i7BT/3a7mbgVp3cEWuMihE8mwOGYb7IFIUqGz3PWC5d9AvSUa7zbyNxwVFswUyqoeG0bD4ZYQCHENrJPgZ2t2pgNANNcFrRHPWCisvL8AafY20Zg=;
X-YMail-OSG: 7o00RDIVM1lGHAfVSWTix5HYHY.a545xnkNF48KX18yTmdcKxTG0kwh9RKV61qoGqFzhWavj7aRcWihYpg.LA.NlhWayxvrwun64_jRp5tjDdI58.14-
Received: from [206.16.17.212] by web84113.mail.mud.yahoo.com via HTTP; Wed, 16 May 2007 09:24:44 PDT
X-Mailer: YahooMailRC/478 YahooMailWebService/0.7.41.10
Date: Wed, 16 May 2007 09:24:44 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Re: [16NG] Review on FMIP6 over IEEE 802.16e Networks
To: Daniel Park <soohongp@gmail.com>, mipshop@ietf.org
MIME-Version: 1.0
Message-ID: <503305.28730.qm@web84113.mail.mud.yahoo.com>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: "16ng@ietf.org" <16ng@ietf.org>
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1650609655=="
Errors-To: 16ng-bounces@ietf.org

Hi Daniel,
  I agree with Jin-Hyeock's comment, I think that Sec 3 should probably not be removed but instead a clarification to the base FMIPv6 can be made.
  On 802.16e links, the AR-Info triplet:
 [Router's L2 address, Router's IP address and Prefix] 
the prefix in the triplet is valid on the interface to which the Access Point (identified by AP-ID) and is different for each MN that is attached due to p2p link model. 

Based on this, the second paragraph can be slightly modified as follows:
Figure 1 shows the deployment with two ARs (ASN-GWs).  
Each MN under an access router
   (AR) and several base stations (BSs) forms a single subnet.  In this
   case, the movement between BSs does not always require IP mobility.
   The handover from BS1 to BS2,  can be carried
   out using link layer mobility without IP mobility.  However, the
   handover from BS5 to BS6 may require IP mobility since they belong to
   the different subnets respectively.We are checking if Sec. 6 requires any changes because of p2p link model and let you know soon.

Regards,

Behcet
----- Original Message ----
From: Daniel Park <soohongp@gmail.com>
To: mipshop@ietf.org
Cc: "16ng@ietf.org" <16ng@ietf.org>
Sent: Wednesday, May 9, 2007 5:37:45 AM
Subject: [16NG] Review on FMIP6 over IEEE 802.16e Networks

To MIPSHOP WG,

Here is an official review by 16NG expert as Jinhyeock Choi. Also, two
more experts are in the progress of reviewing this document. They will
get back to MIPSHOP soon.

=================

I went over the draft and overall it looks fine. It presents an useful
information to efficiently run FMIPv6 over 802.16e with primitives.

I found no technical issue except one.

There are incorrect statements in Sec 3 Deployment Architecture. For
example, there can be more than 2 subnets in figure 1, whereas it's
written that 'Figure 1 shows the deployment with two IP subnets'. In
fact there can be as many subnets as the # of MNs according to
per-MN-prefix link/subnet model. I recommend to re-write the section
or remove it altogether. IMO, the draft will do fine without the
section.

I have a few more comments but they are all editorial. I'll send them
to the authors in a separate mail.

Thanks in advance for your kind consideration.

Best Regards

JinHyeock

=================

Hope this helps...

-- Daniel Park


_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng




_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng