Re: [Mip4] DHCP vs FA

Sri Gundavelli <sgundave@cisco.com> Thu, 04 January 2007 22:51 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H2bQb-00015h-0G; Thu, 04 Jan 2007 17:51:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H2bQZ-0000zZ-KF for mip4@ietf.org; Thu, 04 Jan 2007 17:51:15 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H2bQY-0006mn-4x for mip4@ietf.org; Thu, 04 Jan 2007 17:51:15 -0500
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-3.cisco.com with ESMTP; 04 Jan 2007 14:51:14 -0800
X-IronPort-AV: i="4.12,240,1165219200"; d="scan'208"; a="455265038:sNHT48535392"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l04MpDpo023702; Thu, 4 Jan 2007 14:51:13 -0800
Received: from irp-view7.cisco.com (irp-view7.cisco.com [171.70.65.144]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l04MpD05010180; Thu, 4 Jan 2007 14:51:13 -0800 (PST)
Date: Thu, 04 Jan 2007 14:51:13 -0800
From: Sri Gundavelli <sgundave@cisco.com>
To: Behcet Sarikaya <sarikaya@ieee.org>
Subject: Re: [Mip4] DHCP vs FA
In-Reply-To: <20070104224623.38363.qmail@web60317.mail.yahoo.com>
Message-ID: <Pine.GSO.4.63.0701041448120.15838@irp-view7.cisco.com>
References: <20070104224623.38363.qmail@web60317.mail.yahoo.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4151; t=1167951073; x=1168815073; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=sgundave@cisco.com; z=From:=20Sri=20Gundavelli=20<sgundave@cisco.com> |Subject:=20Re=3A=20[Mip4]=20DHCP=20vs=20FA |Sender:=20; bh=flHAZ4p5BSv5sedjPGxh9zfgcld0Ox4UsvZU9YbqvOM=; b=0aPEnzp31E0jb5QA6KazleWaksya6Ovu1ra63JM362j1prMrRUhIeBG0+BXNP+CoJ2CNHufZ 5D15Dj8Ex9rtRlcfIxK6aEjxeMhjtmHHvLg/B3izPWOBjoQ8Il4FDWNi;
Authentication-Results: sj-dkim-2; header.From=sgundave@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
Cc: mip4@ietf.org
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

If the "R" bit is the agent advertisement is not set,
it is up to the mobile to decide on the FA-COA or
CCOA mode of registration.

Sri

On Thu, 4 Jan 2007, Behcet Sarikaya wrote:

> Hi all,
>  I was reading RFC 3344 and noticed that it is not clear on the choice between the co-located care-of address mode using DHCP and FA provided care-of address mode of operation. If MN does get a
> co-located care-of address and there is an FA what happens then?
> If this had been discussed in the past, I'll appreciate if someone can summarize the conclusion.
>
> Regards,
>
> --behcet
>
> ----- Original Message ----
> From: McCann Peter-A001034 <pete.mccann@motorola.com>
> To: mip4@ietf.org
> Sent: Thursday, January 4, 2007 4:03:26 PM
> Subject: RE: [Mip4] I-D ACTION:draft-ietf-mip4-mobike-connectivity-02.txt
>
>
> Thanks Vijay for submitting a new version.
>
> Can the people who raised issues please check this version
> to see that they were addressed?
>
> If there are no further issues we will proceed to send this
> version up to the IESG.
>
> -Pete
>
> Internet-Drafts@ietf.org wrote:
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Mobility for IPv4 Working Group of
>> the IETF.
>>
>>     Title        : Secure Connectivity and Mobility using Mobile
> IPv4 and
>>     MOBIKE Author(s)    : V. Devarapalli, P. Eronen
>>     Filename    : draft-ietf-mip4-mobike-connectivity-02.txt
>>     Pages        : 15
>>     Date        : 2007-1-4
>>
>> Enterprise users require mobility and secure connectivity when they
>>    roam and connect to the services offered in the enterprise.  Secure
>>    connectivity is required when the user connects to the enterprise
>>    from an untrusted network.  Mobility is beneficial when the user
>>    moves, either inside or outside the enterprise network, and
>>    acquires a new IP address.  This document describes a solution
>>    using Mobile IPv4 and mobility extensions to IKEv2 (MOBIKE) to
>>    provide secure connectivity and mobility.
>>
>> A URL for this Internet-Draft is:
>>
> http://www.ietf.org/internet-drafts/draft-ietf-mip4-mobike-connectivity-
> 02.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-mip4-mobike-connectivity-02.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-mip4-mobike-connectivity-02.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.
>
>
> --
> 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/

-- 
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/