[Mip4] RE: Questions on draft-leung-mip4-proxy-mode-03.txt

"Kent Leung \(kleung\)" <kleung@cisco.com> Wed, 19 September 2007 05:08 UTC

Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IXrnM-000352-A2; Wed, 19 Sep 2007 01:08:16 -0400
Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IXrnL-00034x-S6 for mip4-confirm+ok@megatron.ietf.org; Wed, 19 Sep 2007 01:08:15 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IXrnL-00034V-Fp for mip4@ietf.org; Wed, 19 Sep 2007 01:08:15 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IXrnK-0003n0-RA for mip4@ietf.org; Wed, 19 Sep 2007 01:08:15 -0400
X-IronPort-AV: E=Sophos;i="4.20,271,1186383600"; d="scan'208";a="220747496"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 18 Sep 2007 22:08:14 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l8J58EgZ010726; Tue, 18 Sep 2007 22:08:14 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l8J58Ein023531; Wed, 19 Sep 2007 05:08:14 GMT
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 18 Sep 2007 22:08:13 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 18 Sep 2007 22:08:13 -0700
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC520491395E@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <C089A1D88F85E84B9051FF4C97B574F6022CBC92@de01exm68.ds.mot.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Questions on draft-leung-mip4-proxy-mode-03.txt
Thread-Index: AcfCepH8JZUWbZyPRmGc+WR4bU2zLQzvAjUgACp4ufAAmQojQAABp2DQ
From: "Kent Leung (kleung)" <kleung@cisco.com>
To: Tjandra Paula-CPT015 <Paula.Tjandra@motorola.com>, "Gopal Dommety (gdommety)" <gdommety@cisco.com>, "Parviz Yegani (pyegani)" <pyegani@cisco.com>, kchowdhury@starentnetworks.com
X-OriginalArrivalTime: 19 Sep 2007 05:08:13.0983 (UTC) FILETIME=[14C69AF0:01C7FA7B]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3420; t=1190178494; x=1191042494; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=kleung@cisco.com; z=From:=20=22Kent=20Leung=20\(kleung\)=22=20<kleung@cisco.com> |Subject:=20RE=3A=20Questions=20on=20draft-leung-mip4-proxy-mode-03.txt |Sender:=20; bh=SKHaJnpJART+AJudD2qruiaHpyXiw/OkVqF0FAvN8no=; b=FcmpARooOImxAqRrWni1dXlEtNmpQzWk5XDCdZdkhMf0PSzSosdU2ngfRhs2HOvKvUf2L4TB v/1VQ4LTE4S3oQf04Jw1u0y2LmlA31ayPr+8mVnOkKyn1OAi3/CO4ip4;
Authentication-Results: sj-dkim-3; header.From=kleung@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: mip4@ietf.org
Subject: [Mip4] RE: Questions on draft-leung-mip4-proxy-mode-03.txt
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Comments below. 

-----Original Message-----
From: Tjandra Paula-CPT015 [mailto:Paula.Tjandra@motorola.com] 
Sent: Monday, September 17, 2007 9:46 AM
To: Kent Leung (kleung); Gopal Dommety (gdommety); Parviz Yegani
(pyegani); kchowdhury@starentnetworks.com
Cc: mip4@ietf.org
Subject: RE: Questions on draft-leung-mip4-proxy-mode-03.txt

Thanks for the response Kent.  

Few more comments:
Section 5:
It should be clarified that "Proxy Mobile IPv4 Mode Extension" and
"PMIPv4 Per-Node Authentication Method Extension" are mandatory only
when per-node Security Association is used.

KL> Yes, this is clarified in the next version.

General:
Assuming you added a reference to draft-ietf-mip4-gen-ext-04.txt to
provide the host configuration information, I think there should also be
a section to cover compatibility with Home Agent that does not support
draft-ietf-mip4-gen-ext-04.txt.

KL> I know that there are implementations that support RFC 4332.  The
right method is requiring the MAG/PMA and HA to support
draft-ietf-mip4-gen-ext.


E.g. 
If the home network prefix mask is not provided in Config Option
Exchange Ext., what should be the prefix mask return in the DHCP
response? If default gateway information is not provided in Config
Option Exchange Ext., should the MAG assume that the first address in
the range of IP address associated with the HoA (HoA's subnet or assumed
HoA's subnet) is the IP address of the default gateway?

KL> See above.

Kent

I am not sure if accuracy if important if all packets will be sent back
to LMA anyway. But, I think we need consistency in the implementation to
handle this case.

Thanks, Paula.

-----Original Message-----
From: Kent Leung (kleung) [mailto:kleung@cisco.com]
Sent: Friday, September 14, 2007 10:50 AM
To: Tjandra Paula-CPT015; Gopal Dommety (gdommety); Parviz Yegani
(pyegani); kchowdhury@starentnetworks.com
Cc: mip4@ietf.org
Subject: RE: Questions on draft-leung-mip4-proxy-mode-03.txt

Hi Paula.  Comments below. 

-----Original Message-----
From: Tjandra Paula-CPT015 [mailto:Paula.Tjandra@motorola.com]
Sent: Thursday, September 13, 2007 12:41 PM
To: Kent Leung (kleung); Gopal Dommety (gdommety); Parviz Yegani
(pyegani); kchowdhury@starentnetworks.com
Cc: mip4@ietf.org
Subject: Questions on draft-leung-mip4-proxy-mode-03.txt

Hi,

I have a couple of questions on this draft.

First question is on how DHCP Proxy (in the MAG) populates the DHCP
Offer. The draft only indicates that the IPv4 address set to the
received HoA (from the Proxy MIP RRP). 
draft-ietf-mip4-gen-ext-04.txt describes mechanism to provide the host
configuration. Should this internet draft be referenced for the purpose
of obtaining host configuration?

KL> Yes, we will reference this draft in the next version.

Second question, on section 9.3: the draft seems to imply that the MN's
default gateway is set the LMA (the Home Agent). 
The LMA/Home Agent might not be in the same subnet as the HoA. Will this
cause a problem with the IP stack which requires the default gateway to
be in the same subnet as the HoA

KL> We will need to clarify that the MN's default gateway is set to the
LMA/HA's IP address on the subnet associated with the HoA.  This is one
of the information that comes from Config Option Exchange Ext.

Thx.

Kent

Regards,
Paula Tjandra. 
 


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/