[Mip4] DHCP vs FA

Behcet Sarikaya <behcetsarikaya@yahoo.com> Thu, 04 January 2007 22:46 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H2bLw-0004Oa-4Y; Thu, 04 Jan 2007 17:46:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H2bLu-0004O3-1X for mip4@ietf.org; Thu, 04 Jan 2007 17:46:26 -0500
Received: from web60317.mail.yahoo.com ([209.73.178.125]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1H2bLr-00066R-Hv for mip4@ietf.org; Thu, 04 Jan 2007 17:46:26 -0500
Received: (qmail 38365 invoked by uid 60001); 4 Jan 2007 22:46:23 -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:MIME-Version:Content-Type; b=r4SPTUiS9JBVF3zh9XzmIMEGkQ6GRcl+kTUaM/pHOaj4pAiCdoF0knPXIBQxNRui1VFoSXZTkfn+X92e6Y/I1OEj0Lp9U7MOPBqYGMbOVPrN8fZwfP0Be0Eq0ul+Rl6czfA53fe4rqQOSr8F/Hpj4ORo35kLjzDx2kG1NJLOtEM= ;
Message-ID: <20070104224623.38363.qmail@web60317.mail.yahoo.com>
Received: from [12.129.211.52] by web60317.mail.yahoo.com via HTTP; Thu, 04 Jan 2007 14:46:23 PST
Date: Thu, 04 Jan 2007 14:46:23 -0800
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: mip4@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 21bf7a2f1643ae0bf20c1e010766eb78
Subject: [Mip4] DHCP vs FA
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
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>
Content-Type: multipart/mixed; boundary="===============0757034916=="
Errors-To: mip4-bounces@ietf.org

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/