From mip4-bounces@ietf.org  Tue Mar  1 00:51:34 2005
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 AAA22361
	for <mip4-web-archive@ietf.org>; Tue, 1 Mar 2005 00:51:34 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D60J6-0002Zx-FX
	for mip4-web-archive@ietf.org; Tue, 01 Mar 2005 00:52:32 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D60Fj-0008L9-DS; Tue, 01 Mar 2005 00:49:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D60Fg-0008Kw-Nh
	for mip4@megatron.ietf.org; Tue, 01 Mar 2005 00:49:00 -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 AAA22220
	for <mip4@ietf.org>; Tue, 1 Mar 2005 00:48:57 -0500 (EST)
Received: from szxga03-in.huawei.com ([61.144.161.55] helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D60GQ-0002X6-Q1
	for mip4@ietf.org; Tue, 01 Mar 2005 00:49:55 -0500
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0ICN00IGFS5ORP@szxga03-in.huawei.com> for
	mip4@ietf.org; Tue, 01 Mar 2005 13:49:00 +0800 (CST)
Received: from szxml01-in ([172.24.1.3])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0ICN0002SS5NXF@szxga03-in.huawei.com> for
	mip4@ietf.org; Tue, 01 Mar 2005 13:48:59 +0800 (CST)
Received: from Arun1649 ([10.18.4.165])
	by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0ICN007U8SCZR4@szxml01-in.huawei.com> for
	mip4@ietf.org; Tue, 01 Mar 2005 13:53:25 +0800 (CST)
Date: Tue, 01 Mar 2005 11:18:12 +0530
From: Arun H S <HS_Arun@huawei.com>
Subject: RE: [Mip4] Query For error code from HA ..
In-reply-to: <020201c51b34$a46810e0$3a476c6b@sisodomain.com>
To: mip4@ietf.org
Message-id: <001d01c51e22$41fbf5c0$a504120a@in.huawei.com>
Organization: htipl
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook, Build 10.0.6626
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 4bb0e9e1ca9d18125bc841b2d8d77e24
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: HS_Arun@huawei.com
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="===============0504178432=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: fca741f5016e6ff607eaed2fd431d10d

This is a multi-part message in MIME format.

--===============0504178432==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_6H3m+uibHx9Q9S5D96CViQ)"

This is a multi-part message in MIME format.

--Boundary_(ID_6H3m+uibHx9Q9S5D96CViQ)
Content-type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT

Hi,
 
Sorry, I guess the problem was not understood properly.
 
 
    The problem in question is as follows:
 
    __________                         ____________
    |                | HA1                  |                    |
    |    HA        | ============|        FA        |
    |                |                 FA1  |                    |
    -----------------                         ----------------------
                                                        ||   COA
                                                        ||
                                                        ||
                                                ___________
                                                |                  |
                                                |        MN     |
                                                |                  |
                                                --------------------
 
Now when MN sends an RRQ with Care-of-Address as COA, to Home-Agent Address,
HA1, the Registration is successful because the IP addresses HA1 and FA1 are
routable. However, since the tunnel that is created is between the IP
addresses HA1 and COA, at the Home Agent, there may not be any route in HA
for the IP Address COA. 
In such a scenario, what type of error-code should the Home Agent send back
to the Mobile Node. 
 
PS: In such a scenario, the Registration will be successful, however the
packet forwarding to the Mobile Node will fail since there is no route to
the COA at the Home Agent.
 
Regards,
Arun
 
 

-----Original Message-----
From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of
Radhakrishnan Suryanarayanan
Sent: Friday, February 25, 2005 05:52 PM
To: keshavak@huawei.com; mip4@ietf.org
Subject: Re: [Mip4] Query For error code from HA ..


Hi Mr.Keshav,
If you are talking about Registration reply, HA will recv ICMP Destination
unreachable (from intermediate routers) for CoA of MN.
Where is the question of HA sending any error msg to MN if MN's CoA in
unreachable?????
 
Regards
Radhakrishnan

----- Original Message ----- 
From: keshav <mailto:keshavak@huawei.com>  
To: mip4@ietf.org 
Cc: keshavaak@huawei.com 
Sent: Friday, February 25, 2005 5:32 PM
Subject: [Mip4] Query For error code from HA ..


Hi,

            I would like to know is there any error code that HA has to send
to MN if the 

            Care of address of the MN is not reachable during registration?

            

            

 

 

            

Thanks & regards,

Keshava

 



  _____  




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



--Boundary_(ID_6H3m+uibHx9Q9S5D96CViQ)
Content-type: text/html; charset=US-ASCII
Content-Transfer-Encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>

<META content="MSHTML 6.00.2800.1491" name=GENERATOR>
<STYLE>@font-face {
	font-family: MS Mincho;
}
@font-face {
	font-family: @MS Mincho;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: Arial
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=purple link=blue bgColor=#ffffff>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=506073005-01032005>Hi,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=506073005-01032005>Sorry, 
I guess the problem was not understood properly.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=506073005-01032005>&nbsp;&nbsp;&nbsp; The problem in question is as 
follows:</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=506073005-01032005>&nbsp;&nbsp;&nbsp; 
__________&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
____________</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=506073005-01032005>&nbsp;&nbsp;&nbsp; 
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
|&nbsp;HA1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
|</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=506073005-01032005>&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp; 
HA&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
|&nbsp;============|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
FA&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=506073005-01032005>&nbsp;&nbsp;&nbsp; 
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;FA1&nbsp; 
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
|</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=506073005-01032005>&nbsp;&nbsp;&nbsp; 
-----------------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
----------------------</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
||&nbsp;&nbsp; COA</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
||</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
||</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=506073005-01032005><FONT 
face=Arial color=#0000ff size=2><SPAN 
class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;___________</SPAN></FONT></DIV>
<DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
|</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;MN&nbsp;&nbsp;&nbsp;&nbsp; 
|</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
|</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;--------------------</SPAN></FONT></DIV></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=506073005-01032005>Now 
when MN sends an RRQ with Care-of-Address as COA, to Home-Agent Address, HA1, 
the Registration is successful because the IP addresses HA1 and FA1 are 
routable. However, since the tunnel that is created is between the IP addresses 
HA1 and COA, at the Home Agent, there may not be any route in HA for the IP 
Address COA. </SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=506073005-01032005>In 
such a scenario, what type of error-code should the Home Agent send back to the 
Mobile Node. </SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=506073005-01032005>PS: In 
such a scenario, the Registration will be successful, however the packet 
forwarding to the Mobile Node will fail since there is no route to the COA at 
the Home Agent.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=506073005-01032005>Regards,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=506073005-01032005>Arun</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT 
  face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> 
  mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] <B>On Behalf Of 
  </B>Radhakrishnan Suryanarayanan<BR><B>Sent:</B> Friday, February 25, 2005 
  05:52 PM<BR><B>To:</B> keshavak@huawei.com; mip4@ietf.org<BR><B>Subject:</B> 
  Re: [Mip4] Query For error code from HA ..<BR><BR></FONT></DIV>
  <DIV><FONT face=Arial size=2>Hi Mr.Keshav,</FONT></DIV>
  <DIV><FONT face=Arial size=2>If&nbsp;you</FONT><FONT face=Arial size=2> are 
  talking about Registration reply, </FONT><FONT face=Arial size=2>HA will recv 
  ICMP Destination unreachable (from intermediate routers) for CoA of 
  MN.</FONT></DIV>
  <DIV><FONT face=Arial size=2>Where is the question of HA sending any error msg 
  to MN if&nbsp;MN's CoA in unreachable?????</FONT></DIV>
  <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>Regards</FONT></DIV>
  <DIV><FONT face=Arial size=2>Radhakrishnan</FONT></DIV>
  <BLOCKQUOTE 
  style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
    <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
    <DIV 
    style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
    <A title=keshavak@huawei.com href="mailto:keshavak@huawei.com">keshav</A> 
    </DIV>
    <DIV style="FONT: 10pt arial"><B>To:</B> <A title=mip4@ietf.org 
    href="mailto:mip4@ietf.org">mip4@ietf.org</A> </DIV>
    <DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=keshavaak@huawei.com 
    href="mailto:keshavaak@huawei.com">keshavaak@huawei.com</A> </DIV>
    <DIV style="FONT: 10pt arial"><B>Sent:</B> Friday, February 25, 2005 5:32 
    PM</DIV>
    <DIV style="FONT: 10pt arial"><B>Subject:</B> [Mip4] Query For error code 
    from HA ..</DIV>
    <DIV><BR></DIV>
    <DIV class=Section1>
    <P class=MsoNormal><FONT face=Arial size=2><SPAN 
    style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi,</SPAN></FONT></P>
    <P class=MsoNormal><FONT face=Arial size=2><SPAN 
    style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    I would like to know is there any error code that HA has to send to MN if 
    the </SPAN></FONT></P>
    <P class=MsoNormal><FONT face=Arial size=2><SPAN 
    style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Care of address of the MN is not reachable during 
    registration?</SPAN></FONT></P>
    <P class=MsoNormal><FONT face=Arial size=2><SPAN 
    style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    </SPAN></FONT></P>
    <P class=MsoNormal><FONT face=Arial size=2><SPAN 
    style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    </SPAN></FONT></P>
    <P class=MsoNormal><FONT face=Arial size=2><SPAN 
    style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
    <P class=MsoNormal><FONT face=Arial size=2><SPAN 
    style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
    <P class=MsoNormal><FONT face=Arial size=2><SPAN 
    style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    </SPAN></FONT></P>
    <P class=MsoNormal><FONT face=Arial size=2><SPAN 
    style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Thanks &amp; 
    regards,</SPAN></FONT></P>
    <P class=MsoNormal><FONT face=Arial size=2><SPAN 
    style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Keshav</SPAN></FONT><FONT 
    face=Arial size=2><SPAN 
    style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">a</SPAN></FONT></P>
    <P class=MsoNormal><FONT face=Arial size=2><SPAN 
    style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P></DIV>
    <P>
    <HR>

    <P></P>-- <BR>Mip4 mailing list: <A 
    href="mailto:Mip4@ietf.org">Mip4@ietf.org</A><BR>&nbsp;&nbsp;&nbsp; Web 
    interface: <A 
    href="https://www1.ietf.org/mailman/listinfo/mip4">https://www1.ietf.org/mailman/listinfo/mip4</A><BR>&nbsp;&nbsp;&nbsp;&nbsp; 
    Charter page: <A 
    href="http://www.ietf.org/html.charters/mip4-charter.html">http://www.ietf.org/html.charters/mip4-charter.html</A><BR>Supplemental 
    site: http://www.mip4.org/<BR></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_6H3m+uibHx9Q9S5D96CViQ)--


--===============0504178432==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0504178432==--



From mip4-bounces@ietf.org  Tue Mar  1 02:20:31 2005
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 CAA17571
	for <mip4-web-archive@ietf.org>; Tue, 1 Mar 2005 02:20:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D61hA-0004Ct-2p
	for mip4-web-archive@ietf.org; Tue, 01 Mar 2005 02:21:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D61du-0005f8-Tn; Tue, 01 Mar 2005 02:18:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D61dW-0005Zm-5L
	for mip4@megatron.ietf.org; Tue, 01 Mar 2005 02:17:45 -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 CAA14850
	for <mip4@ietf.org>; Tue, 1 Mar 2005 02:17:40 -0500 (EST)
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D61eL-0004Af-Po
	for mip4@ietf.org; Tue, 01 Mar 2005 02:18:37 -0500
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	id <0ICN00K04W8ZOE@mailout2.samsung.com> for mip4@ietf.org; Tue,
	01 Mar 2005 16:17:23 +0900 (KST)
Received: from ep_mmp2 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTP id <0ICN0069TW8YH1@mailout2.samsung.com> for mip4@ietf.org;
	Tue, 01 Mar 2005 16:17:22 +0900 (KST)
Received: from Radhakrishnan ([107.108.71.58])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0ICN00LVCW8VQ4@mmp2.samsung.com> for
	mip4@ietf.org; Tue, 01 Mar 2005 16:17:22 +0900 (KST)
Date: Tue, 01 Mar 2005 12:41:53 +0530
From: Radhakrishnan Suryanarayanan <rkrishnan.s@samsung.com>
Subject: Re: [Mip4] Query For error code from HA ..
To: HS_Arun@huawei.com
Message-id: <07c401c51e2d$f3b69d00$3a476c6b@sisodomain.com>
Organization: SAMSUNG India Software Operations
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-Priority: 3
X-MSMail-priority: Normal
References: <001d01c51e22$41fbf5c0$a504120a@in.huawei.com>
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 5b943e80df8c8cad631fd60298783617
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Radhakrishnan Suryanarayanan <rkrishnan.s@samsung.com>
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="===============0812387776=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 509eeaf340e89c687918a6101c6def35

This is a multi-part message in MIME format.

--===============0812387776==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_oWQ5W5E/qQQQKcIu31nifg)"

This is a multi-part message in MIME format.

--Boundary_(ID_oWQ5W5E/qQQQKcIu31nifg)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

MessageHi arun,
  For further understanding your problem can you please clarify the following:
  Is the CoA address of the FA (in case registration is being done via FA) or that MN (co-located CoA)?

Regards
Radhakrishnan
  ----- Original Message ----- 
  From: Arun H S 
  To: mip4@ietf.org 
  Sent: Tuesday, March 01, 2005 11:18 AM
  Subject: RE: [Mip4] Query For error code from HA ..


  Hi,

  Sorry, I guess the problem was not understood properly.


      The problem in question is as follows:

      __________                         ____________
      |                | HA1                  |                    |
      |    HA        | ============|        FA        |
      |                |                 FA1  |                    |
      -----------------                         ----------------------
                                                          ||   COA
                                                          ||
                                                          ||
                                                  ___________
                                                  |                  |
                                                  |        MN     |
                                                  |                  |
                                                  --------------------

  Now when MN sends an RRQ with Care-of-Address as COA, to Home-Agent Address, HA1, the Registration is successful because the IP addresses HA1 and FA1 are routable. However, since the tunnel that is created is between the IP addresses HA1 and COA, at the Home Agent, there may not be any route in HA for the IP Address COA. 
  In such a scenario, what type of error-code should the Home Agent send back to the Mobile Node. 

  PS: In such a scenario, the Registration will be successful, however the packet forwarding to the Mobile Node will fail since there is no route to the COA at the Home Agent.

  Regards,
  Arun


    -----Original Message-----
    From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of Radhakrishnan Suryanarayanan
    Sent: Friday, February 25, 2005 05:52 PM
    To: keshavak@huawei.com; mip4@ietf.org
    Subject: Re: [Mip4] Query For error code from HA ..


    Hi Mr.Keshav,
    If you are talking about Registration reply, HA will recv ICMP Destination unreachable (from intermediate routers) for CoA of MN.
    Where is the question of HA sending any error msg to MN if MN's CoA in unreachable?????

    Regards
    Radhakrishnan
      ----- Original Message ----- 
      From: keshav 
      To: mip4@ietf.org 
      Cc: keshavaak@huawei.com 
      Sent: Friday, February 25, 2005 5:32 PM
      Subject: [Mip4] Query For error code from HA ..


      Hi,

                  I would like to know is there any error code that HA has to send to MN if the 

                  Care of address of the MN is not reachable during registration?

                  

                  





                  

      Thanks & regards,

      Keshava





--------------------------------------------------------------------------


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

--Boundary_(ID_oWQ5W5E/qQQQKcIu31nifg)
Content-type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1491" name=GENERATOR>
<STYLE>@font-face {
	font-family: MS Mincho;
}
@font-face {
	font-family: @MS Mincho;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: Arial
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=purple link=blue bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Hi arun,</FONT></DIV>
<DIV><FONT face=Arial size=2>&nbsp; For further understanding your problem can 
you please clarify the following:</FONT></DIV>
<DIV><FONT face=Arial size=2>&nbsp; Is the CoA address of the FA (in case 
registration is being done via FA) or that MN (co-located CoA)?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Regards</FONT></DIV>
<DIV><FONT face=Arial size=2>Radhakrishnan</FONT></DIV>
<BLOCKQUOTE 
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV 
  style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
  <A title=HS_Arun@huawei.com href="mailto:HS_Arun@huawei.com">Arun H S</A> 
  </DIV>
  <DIV style="FONT: 10pt arial"><B>To:</B> <A title=mip4@ietf.org 
  href="mailto:mip4@ietf.org">mip4@ietf.org</A> </DIV>
  <DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, March 01, 2005 11:18 
  AM</DIV>
  <DIV style="FONT: 10pt arial"><B>Subject:</B> RE: [Mip4] Query For error code 
  from HA ..</DIV>
  <DIV><BR></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=506073005-01032005>Hi,</SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=506073005-01032005>Sorry, I guess the problem was not understood 
  properly.</SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=506073005-01032005>&nbsp;&nbsp;&nbsp; The problem in question is as 
  follows:</SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=506073005-01032005>&nbsp;&nbsp;&nbsp; 
  __________&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  ____________</SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=506073005-01032005>&nbsp;&nbsp;&nbsp; 
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |&nbsp;HA1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |</SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=506073005-01032005>&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp; 
  HA&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |&nbsp;============|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  FA&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=506073005-01032005>&nbsp;&nbsp;&nbsp; 
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;FA1&nbsp; 
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |</SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=506073005-01032005>&nbsp;&nbsp;&nbsp; 
  -----------------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  ----------------------</SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  ||&nbsp;&nbsp; COA</SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  ||</SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  ||</SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=506073005-01032005><FONT face=Arial color=#0000ff size=2><SPAN 
  class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;___________</SPAN></FONT></DIV>
  <DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |</SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;MN&nbsp;&nbsp;&nbsp;&nbsp; 
  |</SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |</SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;--------------------</SPAN></FONT></DIV></SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN class=506073005-01032005>Now 
  when MN sends an RRQ with Care-of-Address as COA, to Home-Agent Address, HA1, 
  the Registration is successful because the IP addresses HA1 and FA1 are 
  routable. However, since the tunnel that is created is between the IP 
  addresses HA1 and COA, at the Home Agent, there may not be any route in HA for 
  the IP Address COA. </SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN class=506073005-01032005>In 
  such a scenario, what type of error-code should the Home Agent send back to 
  the Mobile Node. </SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN class=506073005-01032005>PS: 
  In such a scenario, the Registration will be successful, however the packet 
  forwarding to the Mobile Node will fail since there is no route to the COA at 
  the Home Agent.</SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=506073005-01032005>Regards,</SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=506073005-01032005>Arun</SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
  <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
    <DIV></DIV>
    <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT 
    face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> 
    mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] <B>On Behalf Of 
    </B>Radhakrishnan Suryanarayanan<BR><B>Sent:</B> Friday, February 25, 2005 
    05:52 PM<BR><B>To:</B> keshavak@huawei.com; mip4@ietf.org<BR><B>Subject:</B> 
    Re: [Mip4] Query For error code from HA ..<BR><BR></FONT></DIV>
    <DIV><FONT face=Arial size=2>Hi Mr.Keshav,</FONT></DIV>
    <DIV><FONT face=Arial size=2>If&nbsp;you</FONT><FONT face=Arial size=2> are 
    talking about Registration reply, </FONT><FONT face=Arial size=2>HA will 
    recv ICMP Destination unreachable (from intermediate routers) for CoA of 
    MN.</FONT></DIV>
    <DIV><FONT face=Arial size=2>Where is the question of HA sending any error 
    msg to MN if&nbsp;MN's CoA in unreachable?????</FONT></DIV>
    <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial size=2>Regards</FONT></DIV>
    <DIV><FONT face=Arial size=2>Radhakrishnan</FONT></DIV>
    <BLOCKQUOTE 
    style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
      <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
      <DIV 
      style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
      <A title=keshavak@huawei.com href="mailto:keshavak@huawei.com">keshav</A> 
      </DIV>
      <DIV style="FONT: 10pt arial"><B>To:</B> <A title=mip4@ietf.org 
      href="mailto:mip4@ietf.org">mip4@ietf.org</A> </DIV>
      <DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=keshavaak@huawei.com 
      href="mailto:keshavaak@huawei.com">keshavaak@huawei.com</A> </DIV>
      <DIV style="FONT: 10pt arial"><B>Sent:</B> Friday, February 25, 2005 5:32 
      PM</DIV>
      <DIV style="FONT: 10pt arial"><B>Subject:</B> [Mip4] Query For error code 
      from HA ..</DIV>
      <DIV><BR></DIV>
      <DIV class=Section1>
      <P class=MsoNormal><FONT face=Arial size=2><SPAN 
      style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi,</SPAN></FONT></P>
      <P class=MsoNormal><FONT face=Arial size=2><SPAN 
      style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
      I would like to know is there any error code that HA has to send to MN if 
      the </SPAN></FONT></P>
      <P class=MsoNormal><FONT face=Arial size=2><SPAN 
      style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
      Care of address of the MN is not reachable during 
      registration?</SPAN></FONT></P>
      <P class=MsoNormal><FONT face=Arial size=2><SPAN 
      style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
      </SPAN></FONT></P>
      <P class=MsoNormal><FONT face=Arial size=2><SPAN 
      style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
      </SPAN></FONT></P>
      <P class=MsoNormal><FONT face=Arial size=2><SPAN 
      style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
      <P class=MsoNormal><FONT face=Arial size=2><SPAN 
      style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
      <P class=MsoNormal><FONT face=Arial size=2><SPAN 
      style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
      </SPAN></FONT></P>
      <P class=MsoNormal><FONT face=Arial size=2><SPAN 
      style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Thanks &amp; 
      regards,</SPAN></FONT></P>
      <P class=MsoNormal><FONT face=Arial size=2><SPAN 
      style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Keshav</SPAN></FONT><FONT 
      face=Arial size=2><SPAN 
      style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">a</SPAN></FONT></P>
      <P class=MsoNormal><FONT face=Arial size=2><SPAN 
      style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P></DIV>
      <P>
      <HR>

      <P></P>-- <BR>Mip4 mailing list: <A 
      href="mailto:Mip4@ietf.org">Mip4@ietf.org</A><BR>&nbsp;&nbsp;&nbsp; Web 
      interface: <A 
      href="https://www1.ietf.org/mailman/listinfo/mip4">https://www1.ietf.org/mailman/listinfo/mip4</A><BR>&nbsp;&nbsp;&nbsp;&nbsp; 
      Charter page: <A 
      href="http://www.ietf.org/html.charters/mip4-charter.html">http://www.ietf.org/html.charters/mip4-charter.html</A><BR>Supplemental 
      site: http://www.mip4.org/<BR></BLOCKQUOTE></BLOCKQUOTE>
  <P>
  <HR>

  <P></P>-- <BR>Mip4 mailing list: Mip4@ietf.org<BR>&nbsp;&nbsp;&nbsp; Web 
  interface: 
  https://www1.ietf.org/mailman/listinfo/mip4<BR>&nbsp;&nbsp;&nbsp;&nbsp; 
  Charter page: 
  http://www.ietf.org/html.charters/mip4-charter.html<BR>Supplemental site: 
  http://www.mip4.org/<BR></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_oWQ5W5E/qQQQKcIu31nifg)--


--===============0812387776==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0812387776==--



From mip4-bounces@ietf.org  Tue Mar  1 02:34:22 2005
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 CAA20400
	for <mip4-web-archive@ietf.org>; Tue, 1 Mar 2005 02:34:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D61uZ-0004SI-H7
	for mip4-web-archive@ietf.org; Tue, 01 Mar 2005 02:35:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D61sA-0000ti-MX; Tue, 01 Mar 2005 02:32:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D61s3-0000rX-Og
	for mip4@megatron.ietf.org; Tue, 01 Mar 2005 02:32:44 -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 CAA20155
	for <mip4@ietf.org>; Tue, 1 Mar 2005 02:32:39 -0500 (EST)
Received: from szxga03-in.huawei.com ([61.144.161.55] helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D61sk-0004PZ-Vs
	for mip4@ietf.org; Tue, 01 Mar 2005 02:33:37 -0500
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0ICN007H0WWQ26@szxga03-in.huawei.com> for
	mip4@ietf.org; Tue, 01 Mar 2005 15:31:39 +0800 (CST)
Received: from szxml01-in ([172.24.1.3])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0ICN006HTWWQP4@szxga03-in.huawei.com> for
	mip4@ietf.org; Tue, 01 Mar 2005 15:31:38 +0800 (CST)
Received: from Arun1649 ([10.18.4.165])
	by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0ICN00CYBX422J@szxml01-in.huawei.com>; Tue,
	01 Mar 2005 15:36:03 +0800 (CST)
Date: Tue, 01 Mar 2005 13:00:50 +0530
From: Arun H S <HS_Arun@huawei.com>
Subject: RE: [Mip4] Query For error code from HA ..
In-reply-to: <07c401c51e2d$f3b69d00$3a476c6b@sisodomain.com>
To: "'Radhakrishnan Suryanarayanan'" <rkrishnan.s@samsung.com>
Message-id: <002e01c51e30$98be50c0$a504120a@in.huawei.com>
Organization: htipl
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook, Build 10.0.6626
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 85e99493ec37f9acef29c7843dbf2e68
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: HS_Arun@huawei.com
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="===============0096062387=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: dfc64cf6e4c6efdbf6b8f4c995df04df

This is a multi-part message in MIME format.

--===============0096062387==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_xfCgrOlFZjUKWO5eS94QJg)"

This is a multi-part message in MIME format.

--Boundary_(ID_xfCgrOlFZjUKWO5eS94QJg)
Content-type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT

For the Home Agent, I think it dows not matter whether the "COA" is a CLCOA
or a COA

-----Original Message-----
From: Radhakrishnan Suryanarayanan [mailto:rkrishnan.s@samsung.com] 
Sent: Tuesday, March 01, 2005 12:42 PM
To: HS_Arun@huawei.com
Cc: mip4@ietf.org
Subject: Re: [Mip4] Query For error code from HA ..


Hi arun,
  For further understanding your problem can you please clarify the
following:
  Is the CoA address of the FA (in case registration is being done via FA)
or that MN (co-located CoA)?
 
Regards
Radhakrishnan

----- Original Message ----- 
From: Arun H S <mailto:HS_Arun@huawei.com>  
To: mip4@ietf.org 
Sent: Tuesday, March 01, 2005 11:18 AM
Subject: RE: [Mip4] Query For error code from HA ..

Hi,
 
Sorry, I guess the problem was not understood properly.
 
 
    The problem in question is as follows:
 
    __________                         ____________
    |                | HA1                  |                    |
    |    HA        | ============|        FA        |
    |                |                 FA1  |                    |
    -----------------                         ----------------------
                                                        ||   COA
                                                        ||
                                                        ||
                                                ___________
                                                |                  |
                                                |        MN     |
                                                |                  |
                                                --------------------
 
Now when MN sends an RRQ with Care-of-Address as COA, to Home-Agent Address,
HA1, the Registration is successful because the IP addresses HA1 and FA1 are
routable. However, since the tunnel that is created is between the IP
addresses HA1 and COA, at the Home Agent, there may not be any route in HA
for the IP Address COA. 
In such a scenario, what type of error-code should the Home Agent send back
to the Mobile Node. 
 
PS: In such a scenario, the Registration will be successful, however the
packet forwarding to the Mobile Node will fail since there is no route to
the COA at the Home Agent.
 
Regards,
Arun
 
 

-----Original Message-----
From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of
Radhakrishnan Suryanarayanan
Sent: Friday, February 25, 2005 05:52 PM
To: keshavak@huawei.com; mip4@ietf.org
Subject: Re: [Mip4] Query For error code from HA ..


Hi Mr.Keshav,
If you are talking about Registration reply, HA will recv ICMP Destination
unreachable (from intermediate routers) for CoA of MN.
Where is the question of HA sending any error msg to MN if MN's CoA in
unreachable?????
 
Regards
Radhakrishnan

----- Original Message ----- 
From: keshav <mailto:keshavak@huawei.com>  
To: mip4@ietf.org 
Cc: keshavaak@huawei.com 
Sent: Friday, February 25, 2005 5:32 PM
Subject: [Mip4] Query For error code from HA ..


Hi,

            I would like to know is there any error code that HA has to send
to MN if the 

            Care of address of the MN is not reachable during registration?

            

            

 

 

            

Thanks & regards,

Keshava

 



  _____  




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



--Boundary_(ID_xfCgrOlFZjUKWO5eS94QJg)
Content-type: text/html; charset=US-ASCII
Content-Transfer-Encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>

<META content="MSHTML 6.00.2800.1491" name=GENERATOR>
<STYLE>@font-face {
	font-family: MS Mincho;
}
@font-face {
	font-family: @MS Mincho;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: Arial
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=purple link=blue bgColor=#ffffff>
<DIV><SPAN class=297153007-01032005><FONT face=Arial color=#0000ff size=2>For 
the Home Agent, I think it dows not matter whether the "COA" is a CLCOA or a 
COA</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT 
  face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Radhakrishnan 
  Suryanarayanan [mailto:rkrishnan.s@samsung.com] <BR><B>Sent:</B> Tuesday, 
  March 01, 2005 12:42 PM<BR><B>To:</B> HS_Arun@huawei.com<BR><B>Cc:</B> 
  mip4@ietf.org<BR><B>Subject:</B> Re: [Mip4] Query For error code from HA 
  ..<BR><BR></FONT></DIV>
  <DIV><FONT face=Arial size=2>Hi arun,</FONT></DIV>
  <DIV><FONT face=Arial size=2>&nbsp; For further understanding your problem can 
  you please clarify the following:</FONT></DIV>
  <DIV><FONT face=Arial size=2>&nbsp; Is the CoA address of the FA (in case 
  registration is being done via FA) or that MN (co-located CoA)?</FONT></DIV>
  <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>Regards</FONT></DIV>
  <DIV><FONT face=Arial size=2>Radhakrishnan</FONT></DIV>
  <BLOCKQUOTE 
  style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
    <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
    <DIV 
    style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
    <A title=HS_Arun@huawei.com href="mailto:HS_Arun@huawei.com">Arun H S</A> 
    </DIV>
    <DIV style="FONT: 10pt arial"><B>To:</B> <A title=mip4@ietf.org 
    href="mailto:mip4@ietf.org">mip4@ietf.org</A> </DIV>
    <DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, March 01, 2005 11:18 
    AM</DIV>
    <DIV style="FONT: 10pt arial"><B>Subject:</B> RE: [Mip4] Query For error 
    code from HA ..</DIV>
    <DIV><BR></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005>Hi,</SPAN></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005>Sorry, I guess the problem was not understood 
    properly.</SPAN></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005>&nbsp;&nbsp;&nbsp; The problem in question is as 
    follows:</SPAN></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005>&nbsp;&nbsp;&nbsp; 
    __________&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    ____________</SPAN></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005>&nbsp;&nbsp;&nbsp; 
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |&nbsp;HA1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |</SPAN></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005>&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp; 
    HA&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |&nbsp;============|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    FA&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</SPAN></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005>&nbsp;&nbsp;&nbsp; 
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;FA1&nbsp; 
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |</SPAN></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005>&nbsp;&nbsp;&nbsp; 
    -----------------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    ----------------------</SPAN></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    ||&nbsp;&nbsp; COA</SPAN></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    ||</SPAN></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    ||</SPAN></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;___________</SPAN></FONT></DIV>
    <DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |</SPAN></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;MN&nbsp;&nbsp;&nbsp;&nbsp; 
    |</SPAN></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |</SPAN></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;--------------------</SPAN></FONT></DIV></SPAN></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005>Now when MN sends an RRQ with Care-of-Address as 
    COA, to Home-Agent Address, HA1, the Registration is successful because the 
    IP addresses HA1 and FA1 are routable. However, since the tunnel that is 
    created is between the IP addresses HA1 and COA, at the Home Agent, there 
    may not be any route in HA for the IP Address COA. </SPAN></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN class=506073005-01032005>In 
    such a scenario, what type of error-code should the Home Agent send back to 
    the Mobile Node. </SPAN></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005>PS: In such a scenario, the Registration will be 
    successful, however the packet forwarding to the Mobile Node will fail since 
    there is no route to the COA at the Home Agent.</SPAN></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005>Regards,</SPAN></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005>Arun</SPAN></FONT></DIV>
    <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
    class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
    <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
      <DIV></DIV>
      <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT 
      face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> 
      mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] <B>On Behalf Of 
      </B>Radhakrishnan Suryanarayanan<BR><B>Sent:</B> Friday, February 25, 2005 
      05:52 PM<BR><B>To:</B> keshavak@huawei.com; 
      mip4@ietf.org<BR><B>Subject:</B> Re: [Mip4] Query For error code from HA 
      ..<BR><BR></FONT></DIV>
      <DIV><FONT face=Arial size=2>Hi Mr.Keshav,</FONT></DIV>
      <DIV><FONT face=Arial size=2>If&nbsp;you</FONT><FONT face=Arial size=2> 
      are talking about Registration reply, </FONT><FONT face=Arial size=2>HA 
      will recv ICMP Destination unreachable (from intermediate routers) for CoA 
      of MN.</FONT></DIV>
      <DIV><FONT face=Arial size=2>Where is the question of HA sending any error 
      msg to MN if&nbsp;MN's CoA in unreachable?????</FONT></DIV>
      <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
      <DIV><FONT face=Arial size=2>Regards</FONT></DIV>
      <DIV><FONT face=Arial size=2>Radhakrishnan</FONT></DIV>
      <BLOCKQUOTE 
      style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
        <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
        <DIV 
        style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
        <A title=keshavak@huawei.com 
        href="mailto:keshavak@huawei.com">keshav</A> </DIV>
        <DIV style="FONT: 10pt arial"><B>To:</B> <A title=mip4@ietf.org 
        href="mailto:mip4@ietf.org">mip4@ietf.org</A> </DIV>
        <DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=keshavaak@huawei.com 
        href="mailto:keshavaak@huawei.com">keshavaak@huawei.com</A> </DIV>
        <DIV style="FONT: 10pt arial"><B>Sent:</B> Friday, February 25, 2005 
        5:32 PM</DIV>
        <DIV style="FONT: 10pt arial"><B>Subject:</B> [Mip4] Query For error 
        code from HA ..</DIV>
        <DIV><BR></DIV>
        <DIV class=Section1>
        <P class=MsoNormal><FONT face=Arial size=2><SPAN 
        style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi,</SPAN></FONT></P>
        <P class=MsoNormal><FONT face=Arial size=2><SPAN 
        style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
        I would like to know is there any error code that HA has to send to MN 
        if the </SPAN></FONT></P>
        <P class=MsoNormal><FONT face=Arial size=2><SPAN 
        style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
        Care of address of the MN is not reachable during 
        registration?</SPAN></FONT></P>
        <P class=MsoNormal><FONT face=Arial size=2><SPAN 
        style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
        </SPAN></FONT></P>
        <P class=MsoNormal><FONT face=Arial size=2><SPAN 
        style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
        </SPAN></FONT></P>
        <P class=MsoNormal><FONT face=Arial size=2><SPAN 
        style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
        <P class=MsoNormal><FONT face=Arial size=2><SPAN 
        style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
        <P class=MsoNormal><FONT face=Arial size=2><SPAN 
        style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
        </SPAN></FONT></P>
        <P class=MsoNormal><FONT face=Arial size=2><SPAN 
        style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Thanks &amp; 
        regards,</SPAN></FONT></P>
        <P class=MsoNormal><FONT face=Arial size=2><SPAN 
        style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Keshav</SPAN></FONT><FONT 
        face=Arial size=2><SPAN 
        style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">a</SPAN></FONT></P>
        <P class=MsoNormal><FONT face=Arial size=2><SPAN 
        style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P></DIV>
        <P>
        <HR>

        <P></P>-- <BR>Mip4 mailing list: <A 
        href="mailto:Mip4@ietf.org">Mip4@ietf.org</A><BR>&nbsp;&nbsp;&nbsp; Web 
        interface: <A 
        href="https://www1.ietf.org/mailman/listinfo/mip4">https://www1.ietf.org/mailman/listinfo/mip4</A><BR>&nbsp;&nbsp;&nbsp;&nbsp; 
        Charter page: <A 
        href="http://www.ietf.org/html.charters/mip4-charter.html">http://www.ietf.org/html.charters/mip4-charter.html</A><BR>Supplemental 
        site: http://www.mip4.org/<BR></BLOCKQUOTE></BLOCKQUOTE>
    <P>
    <HR>

    <P></P>-- <BR>Mip4 mailing list: Mip4@ietf.org<BR>&nbsp;&nbsp;&nbsp; Web 
    interface: 
    https://www1.ietf.org/mailman/listinfo/mip4<BR>&nbsp;&nbsp;&nbsp;&nbsp; 
    Charter page: 
    http://www.ietf.org/html.charters/mip4-charter.html<BR>Supplemental site: 
    http://www.mip4.org/<BR></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_xfCgrOlFZjUKWO5eS94QJg)--


--===============0096062387==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0096062387==--



From mip4-bounces@ietf.org  Tue Mar  1 02:56:44 2005
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 CAA22071
	for <mip4-web-archive@ietf.org>; Tue, 1 Mar 2005 02:56:44 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D62GD-0004s3-U5
	for mip4-web-archive@ietf.org; Tue, 01 Mar 2005 02:57:42 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D62E2-00050R-82; Tue, 01 Mar 2005 02:55:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D62Dv-00050F-2R
	for mip4@megatron.ietf.org; Tue, 01 Mar 2005 02:55:19 -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 CAA21991
	for <mip4@ietf.org>; Tue, 1 Mar 2005 02:55:17 -0500 (EST)
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D62En-0004qm-DD
	for mip4@ietf.org; Tue, 01 Mar 2005 02:56:14 -0500
Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	id <0ICN00604XZPLD@mailout1.samsung.com> for mip4@ietf.org; Tue,
	01 Mar 2005 16:55:02 +0900 (KST)
Received: from ep_mmp2 (mailout1.samsung.com [203.254.224.24])
	by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTP id <0ICN0048RXZPU6@mailout1.samsung.com> for mip4@ietf.org;
	Tue, 01 Mar 2005 16:55:01 +0900 (KST)
Received: from Radhakrishnan ([107.108.71.58])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0ICN00MHLXZLTA@mmp2.samsung.com> for
	mip4@ietf.org; Tue, 01 Mar 2005 16:55:01 +0900 (KST)
Date: Tue, 01 Mar 2005 13:19:31 +0530
From: Radhakrishnan Suryanarayanan <rkrishnan.s@samsung.com>
Subject: Re: [Mip4] Query For error code from HA ..
To: HS_Arun@huawei.com
Message-id: <081601c51e33$354c85e0$3a476c6b@sisodomain.com>
Organization: SAMSUNG India Software Operations
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-Priority: 3
X-MSMail-priority: Normal
References: <003e01c51e33$016af7c0$a504120a@in.huawei.com>
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 4de5d7f989d6c039c8b887f1940f36ab
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Radhakrishnan Suryanarayanan <rkrishnan.s@samsung.com>
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="===============0079414480=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: dc7bd83d90806aed39f33478866e2683

This is a multi-part message in MIME format.

--===============0079414480==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_aPvZdh4ETOcpHWeNiOvkdQ)"

This is a multi-part message in MIME format.

--Boundary_(ID_aPvZdh4ETOcpHWeNiOvkdQ)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

MessageHi arun,
I got ur scenario. see section 6.4 RFC 3344
"
 128-192    Error Codes from the Home Agent
"
Cisco's behavior is quite right!
  ----- Original Message ----- 
  From: Arun H S 
  To: 'Radhakrishnan Suryanarayanan' 
  Sent: Tuesday, March 01, 2005 1:18 PM
  Subject: RE: [Mip4] Query For error code from HA ..


  do U have a Cisco Rtr there ... U can chk out ... he sends back code 128 (reason un-specified) as the registration reply
    -----Original Message-----
    From: Radhakrishnan Suryanarayanan [mailto:rkrishnan.s@samsung.com] 
    Sent: Tuesday, March 01, 2005 01:09 PM
    To: HS_Arun@huawei.com
    Subject: Re: [Mip4] Query For error code from HA ..


    In such a case the MN/FA can never be reached even to intimate the error. The packet is just discarded at the HA.
    FA/MN does retransmission and The Registration fails! 
      ----- Original Message ----- 
      From: Arun H S 
      To: 'Radhakrishnan Suryanarayanan' 
      Cc: mip4@ietf.org 
      Sent: Tuesday, March 01, 2005 1:00 PM
      Subject: RE: [Mip4] Query For error code from HA ..


      For the Home Agent, I think it dows not matter whether the "COA" is a CLCOA or a COA
        -----Original Message-----
        From: Radhakrishnan Suryanarayanan [mailto:rkrishnan.s@samsung.com] 
        Sent: Tuesday, March 01, 2005 12:42 PM
        To: HS_Arun@huawei.com
        Cc: mip4@ietf.org
        Subject: Re: [Mip4] Query For error code from HA ..


        Hi arun,
          For further understanding your problem can you please clarify the following:
          Is the CoA address of the FA (in case registration is being done via FA) or that MN (co-located CoA)?

        Regards
        Radhakrishnan
          ----- Original Message ----- 
          From: Arun H S 
          To: mip4@ietf.org 
          Sent: Tuesday, March 01, 2005 11:18 AM
          Subject: RE: [Mip4] Query For error code from HA ..


          Hi,

          Sorry, I guess the problem was not understood properly.


              The problem in question is as follows:

              __________                         ____________
              |                | HA1                  |                    |
              |    HA        | ============|        FA        |
              |                |                 FA1  |                    |
              -----------------                         ----------------------
                                                                  ||   COA
                                                                  ||
                                                                  ||
                                                          ___________
                                                          |                  |
                                                          |        MN     |
                                                          |                  |
                                                          --------------------

          Now when MN sends an RRQ with Care-of-Address as COA, to Home-Agent Address, HA1, the Registration is successful because the IP addresses HA1 and FA1 are routable. However, since the tunnel that is created is between the IP addresses HA1 and COA, at the Home Agent, there may not be any route in HA for the IP Address COA. 
          In such a scenario, what type of error-code should the Home Agent send back to the Mobile Node. 

          PS: In such a scenario, the Registration will be successful, however the packet forwarding to the Mobile Node will fail since there is no route to the COA at the Home Agent.

          Regards,
          Arun


            -----Original Message-----
            From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of Radhakrishnan Suryanarayanan
            Sent: Friday, February 25, 2005 05:52 PM
            To: keshavak@huawei.com; mip4@ietf.org
            Subject: Re: [Mip4] Query For error code from HA ..


            Hi Mr.Keshav,
            If you are talking about Registration reply, HA will recv ICMP Destination unreachable (from intermediate routers) for CoA of MN.
            Where is the question of HA sending any error msg to MN if MN's CoA in unreachable?????

            Regards
            Radhakrishnan
              ----- Original Message ----- 
              From: keshav 
              To: mip4@ietf.org 
              Cc: keshavaak@huawei.com 
              Sent: Friday, February 25, 2005 5:32 PM
              Subject: [Mip4] Query For error code from HA ..


              Hi,

                          I would like to know is there any error code that HA has to send to MN if the 

                          Care of address of the MN is not reachable during registration?

                          

                          





                          

              Thanks & regards,

              Keshava





------------------------------------------------------------------


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



--------------------------------------------------------------------------


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

--Boundary_(ID_aPvZdh4ETOcpHWeNiOvkdQ)
Content-type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1491" name=GENERATOR>
<STYLE>@font-face {
	font-family: MS Mincho;
}
@font-face {
	font-family: @MS Mincho;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: Arial
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=purple link=blue bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Hi arun,</FONT></DIV>
<DIV><FONT face=Arial size=2>I got ur scenario. </FONT><FONT face=Arial 
size=2>see section 6.4 RFC 3344</FONT></DIV>
<DIV><FONT face=Arial size=2>"</FONT></DIV>
<DIV>&nbsp;128-192&nbsp;&nbsp;&nbsp; Error Codes from the Home Agent<BR><FONT 
face=Arial size=2>"</FONT></DIV>
<DIV><FONT face=Arial size=2>Cisco's behavior is quite right!</FONT></DIV>
<BLOCKQUOTE dir=ltr 
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV 
  style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
  <A title=HS_Arun@huawei.com href="mailto:HS_Arun@huawei.com">Arun H S</A> 
  </DIV>
  <DIV style="FONT: 10pt arial"><B>To:</B> <A title=rkrishnan.s@samsung.com 
  href="mailto:rkrishnan.s@samsung.com">'Radhakrishnan Suryanarayanan'</A> 
</DIV>
  <DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, March 01, 2005 1:18 
  PM</DIV>
  <DIV style="FONT: 10pt arial"><B>Subject:</B> RE: [Mip4] Query For error code 
  from HA ..</DIV>
  <DIV><BR></DIV>
  <DIV><SPAN class=750124707-01032005><FONT face=Arial color=#0000ff size=2>do U 
  have a Cisco Rtr there ... U can chk out ... he sends back code 128 (reason 
  un-specified) as the registration reply</FONT></SPAN></DIV>
  <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
    <DIV></DIV>
    <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT 
    face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Radhakrishnan 
    Suryanarayanan [mailto:rkrishnan.s@samsung.com] <BR><B>Sent:</B> Tuesday, 
    March 01, 2005 01:09 PM<BR><B>To:</B> <A 
    href="mailto:HS_Arun@huawei.com">HS_Arun@huawei.com</A><BR><B>Subject:</B> 
    Re: [Mip4] Query For error code from HA ..<BR><BR></FONT></DIV>
    <DIV><FONT face=Arial size=2>In such a case the MN/FA can never be reached 
    even to intimate the error. The packet is just discarded at the 
    HA.</FONT></DIV>
    <DIV><FONT face=Arial size=2>FA/MN does retransmission&nbsp;and The 
    Registration fails!&nbsp;</FONT></DIV>
    <BLOCKQUOTE 
    style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
      <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
      <DIV 
      style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
      <A title=HS_Arun@huawei.com href="mailto:HS_Arun@huawei.com">Arun H S</A> 
      </DIV>
      <DIV style="FONT: 10pt arial"><B>To:</B> <A title=rkrishnan.s@samsung.com 
      href="mailto:rkrishnan.s@samsung.com">'Radhakrishnan Suryanarayanan'</A> 
      </DIV>
      <DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=mip4@ietf.org 
      href="mailto:mip4@ietf.org">mip4@ietf.org</A> </DIV>
      <DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, March 01, 2005 1:00 
      PM</DIV>
      <DIV style="FONT: 10pt arial"><B>Subject:</B> RE: [Mip4] Query For error 
      code from HA ..</DIV>
      <DIV><BR></DIV>
      <DIV><SPAN class=297153007-01032005><FONT face=Arial color=#0000ff 
      size=2>For the Home Agent, I think it dows not matter whether the "COA" is 
      a CLCOA or a COA</FONT></SPAN></DIV>
      <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
        <DIV></DIV>
        <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT 
        face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> 
        Radhakrishnan Suryanarayanan [mailto:rkrishnan.s@samsung.com] 
        <BR><B>Sent:</B> Tuesday, March 01, 2005 12:42 PM<BR><B>To:</B> <A 
        href="mailto:HS_Arun@huawei.com">HS_Arun@huawei.com</A><BR><B>Cc:</B> <A 
        href="mailto:mip4@ietf.org">mip4@ietf.org</A><BR><B>Subject:</B> Re: 
        [Mip4] Query For error code from HA ..<BR><BR></FONT></DIV>
        <DIV><FONT face=Arial size=2>Hi arun,</FONT></DIV>
        <DIV><FONT face=Arial size=2>&nbsp; For further understanding your 
        problem can you please clarify the following:</FONT></DIV>
        <DIV><FONT face=Arial size=2>&nbsp; Is the CoA address of the FA (in 
        case registration is being done via FA) or that MN (co-located 
        CoA)?</FONT></DIV>
        <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
        <DIV><FONT face=Arial size=2>Regards</FONT></DIV>
        <DIV><FONT face=Arial size=2>Radhakrishnan</FONT></DIV>
        <BLOCKQUOTE 
        style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
          <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
          <DIV 
          style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
          <A title=HS_Arun@huawei.com href="mailto:HS_Arun@huawei.com">Arun H 
          S</A> </DIV>
          <DIV style="FONT: 10pt arial"><B>To:</B> <A title=mip4@ietf.org 
          href="mailto:mip4@ietf.org">mip4@ietf.org</A> </DIV>
          <DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, March 01, 2005 
          11:18 AM</DIV>
          <DIV style="FONT: 10pt arial"><B>Subject:</B> RE: [Mip4] Query For 
          error code from HA ..</DIV>
          <DIV><BR></DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005>Hi,</SPAN></FONT></DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005>Sorry, I guess the problem was not understood 
          properly.</SPAN></FONT></DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005>&nbsp;&nbsp;&nbsp; The problem in question is 
          as follows:</SPAN></FONT></DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005>&nbsp;&nbsp;&nbsp; 
          __________&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
          ____________</SPAN></FONT></DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005>&nbsp;&nbsp;&nbsp; 
          |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
          |&nbsp;HA1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
          |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
          |</SPAN></FONT></DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005>&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp; 
          HA&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
          |&nbsp;============|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
          FA&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</SPAN></FONT></DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005>&nbsp;&nbsp;&nbsp; 
          |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
          |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;FA1&nbsp; 
          |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
          |</SPAN></FONT></DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005>&nbsp;&nbsp;&nbsp; 
          -----------------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
          ----------------------</SPAN></FONT></DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
          ||&nbsp;&nbsp; COA</SPAN></FONT></DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
          ||</SPAN></FONT></DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
          ||</SPAN></FONT></DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;___________</SPAN></FONT></DIV>
          <DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
          |</SPAN></FONT></DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;MN&nbsp;&nbsp;&nbsp;&nbsp; 
          |</SPAN></FONT></DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
          |</SPAN></FONT></DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;--------------------</SPAN></FONT></DIV></SPAN></FONT></DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005>Now when MN sends an RRQ with Care-of-Address 
          as COA, to Home-Agent Address, HA1, the Registration is successful 
          because the IP addresses HA1 and FA1 are routable. However, since the 
          tunnel that is created is between the IP addresses HA1 and COA, at the 
          Home Agent, there may not be any route in HA for the IP Address COA. 
          </SPAN></FONT></DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005>In such a scenario, what type of error-code 
          should the Home Agent send back to the Mobile Node. 
          </SPAN></FONT></DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005>PS: In such a scenario, the Registration will 
          be successful, however the packet forwarding to the Mobile Node will 
          fail since there is no route to the COA at the Home 
          Agent.</SPAN></FONT></DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005>Regards,</SPAN></FONT></DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005>Arun</SPAN></FONT></DIV>
          <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
          class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
          <DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
          <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
            <DIV></DIV>
            <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT 
            face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> 
            mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] <B>On Behalf Of 
            </B>Radhakrishnan Suryanarayanan<BR><B>Sent:</B> Friday, February 
            25, 2005 05:52 PM<BR><B>To:</B> keshavak@huawei.com; 
            mip4@ietf.org<BR><B>Subject:</B> Re: [Mip4] Query For error code 
            from HA ..<BR><BR></FONT></DIV>
            <DIV><FONT face=Arial size=2>Hi Mr.Keshav,</FONT></DIV>
            <DIV><FONT face=Arial size=2>If&nbsp;you</FONT><FONT face=Arial 
            size=2> are talking about Registration reply, </FONT><FONT 
            face=Arial size=2>HA will recv ICMP Destination unreachable (from 
            intermediate routers) for CoA of MN.</FONT></DIV>
            <DIV><FONT face=Arial size=2>Where is the question of HA sending any 
            error msg to MN if&nbsp;MN's CoA in unreachable?????</FONT></DIV>
            <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
            <DIV><FONT face=Arial size=2>Regards</FONT></DIV>
            <DIV><FONT face=Arial size=2>Radhakrishnan</FONT></DIV>
            <BLOCKQUOTE 
            style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
              <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
              <DIV 
              style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
              <A title=keshavak@huawei.com 
              href="mailto:keshavak@huawei.com">keshav</A> </DIV>
              <DIV style="FONT: 10pt arial"><B>To:</B> <A title=mip4@ietf.org 
              href="mailto:mip4@ietf.org">mip4@ietf.org</A> </DIV>
              <DIV style="FONT: 10pt arial"><B>Cc:</B> <A 
              title=keshavaak@huawei.com 
              href="mailto:keshavaak@huawei.com">keshavaak@huawei.com</A> </DIV>
              <DIV style="FONT: 10pt arial"><B>Sent:</B> Friday, February 25, 
              2005 5:32 PM</DIV>
              <DIV style="FONT: 10pt arial"><B>Subject:</B> [Mip4] Query For 
              error code from HA ..</DIV>
              <DIV><BR></DIV>
              <DIV class=Section1>
              <P class=MsoNormal><FONT face=Arial size=2><SPAN 
              style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi,</SPAN></FONT></P>
              <P class=MsoNormal><FONT face=Arial size=2><SPAN 
              style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
              I would like to know is there any error code that HA has to send 
              to MN if the </SPAN></FONT></P>
              <P class=MsoNormal><FONT face=Arial size=2><SPAN 
              style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
              Care of address of the MN is not reachable during 
              registration?</SPAN></FONT></P>
              <P class=MsoNormal><FONT face=Arial size=2><SPAN 
              style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
              </SPAN></FONT></P>
              <P class=MsoNormal><FONT face=Arial size=2><SPAN 
              style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
              </SPAN></FONT></P>
              <P class=MsoNormal><FONT face=Arial size=2><SPAN 
              style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
              <P class=MsoNormal><FONT face=Arial size=2><SPAN 
              style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
              <P class=MsoNormal><FONT face=Arial size=2><SPAN 
              style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
              </SPAN></FONT></P>
              <P class=MsoNormal><FONT face=Arial size=2><SPAN 
              style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Thanks &amp; 
              regards,</SPAN></FONT></P>
              <P class=MsoNormal><FONT face=Arial size=2><SPAN 
              style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Keshav</SPAN></FONT><FONT 
              face=Arial size=2><SPAN 
              style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">a</SPAN></FONT></P>
              <P class=MsoNormal><FONT face=Arial size=2><SPAN 
              style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P></DIV>
              <P>
              <HR>

              <P></P>-- <BR>Mip4 mailing list: <A 
              href="mailto:Mip4@ietf.org">Mip4@ietf.org</A><BR>&nbsp;&nbsp;&nbsp; 
              Web interface: <A 
              href="https://www1.ietf.org/mailman/listinfo/mip4">https://www1.ietf.org/mailman/listinfo/mip4</A><BR>&nbsp;&nbsp;&nbsp;&nbsp; 
              Charter page: <A 
              href="http://www.ietf.org/html.charters/mip4-charter.html">http://www.ietf.org/html.charters/mip4-charter.html</A><BR>Supplemental 
              site: http://www.mip4.org/<BR></BLOCKQUOTE></BLOCKQUOTE>
          <P>
          <HR>

          <P></P>-- <BR>Mip4 mailing list: Mip4@ietf.org<BR>&nbsp;&nbsp;&nbsp; 
          Web interface: 
          https://www1.ietf.org/mailman/listinfo/mip4<BR>&nbsp;&nbsp;&nbsp;&nbsp; 
          Charter page: 
          http://www.ietf.org/html.charters/mip4-charter.html<BR>Supplemental 
          site: http://www.mip4.org/<BR></BLOCKQUOTE></BLOCKQUOTE>
      <P>
      <HR>

      <P></P>-- <BR>Mip4 mailing list: Mip4@ietf.org<BR>&nbsp;&nbsp;&nbsp; Web 
      interface: 
      https://www1.ietf.org/mailman/listinfo/mip4<BR>&nbsp;&nbsp;&nbsp;&nbsp; 
      Charter page: 
      http://www.ietf.org/html.charters/mip4-charter.html<BR>Supplemental site: 
      http://www.mip4.org/<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_aPvZdh4ETOcpHWeNiOvkdQ)--


--===============0079414480==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0079414480==--



From mip4-bounces@ietf.org  Tue Mar  1 03:09:18 2005
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 DAA00367
	for <mip4-web-archive@ietf.org>; Tue, 1 Mar 2005 03:09:17 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D62SN-000591-6N
	for mip4-web-archive@ietf.org; Tue, 01 Mar 2005 03:10:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D62OI-0006it-O0; Tue, 01 Mar 2005 03:06:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D62NV-0006ab-VN
	for mip4@megatron.ietf.org; Tue, 01 Mar 2005 03:05:14 -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 DAA23086
	for <mip4@ietf.org>; Tue, 1 Mar 2005 03:05:12 -0500 (EST)
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D62OO-00053N-DO
	for mip4@ietf.org; Tue, 01 Mar 2005 03:06:09 -0500
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	id <0ICN00A01YG8XQ@mailout3.samsung.com> for mip4@ietf.org; Tue,
	01 Mar 2005 17:04:56 +0900 (KST)
Received: from ep_mmp2 (mailout3.samsung.com [203.254.224.33])
	by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTP id <0ICN00B6LYG875@mailout3.samsung.com> for mip4@ietf.org;
	Tue, 01 Mar 2005 17:04:56 +0900 (KST)
Received: from Radhakrishnan ([107.108.71.58])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0ICN00KSZYG2BG@mmp2.samsung.com> for
	mip4@ietf.org; Tue, 01 Mar 2005 17:04:56 +0900 (KST)
Date: Tue, 01 Mar 2005 13:29:24 +0530
From: Radhakrishnan Suryanarayanan <rkrishnan.s@samsung.com>
Subject: Re: [Mip4] Query For error code from HA ..
To: HS_Arun@huawei.com
Message-id: <083b01c51e34$97517d80$3a476c6b@sisodomain.com>
Organization: SAMSUNG India Software Operations
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-Priority: 3
X-MSMail-priority: Normal
References: <003e01c51e33$016af7c0$a504120a@in.huawei.com>
	<081601c51e33$354c85e0$3a476c6b@sisodomain.com>
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 09f2eafe5f7c426554d5f494540a89cd
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Radhakrishnan Suryanarayanan <rkrishnan.s@samsung.com>
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="===============0918782475=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 0e831a3b581a967a651997b2cbc2bae7

This is a multi-part message in MIME format.

--===============0918782475==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_lyDXuacsLHQtk8x6G/mXCg)"

This is a multi-part message in MIME format.

--Boundary_(ID_lyDXuacsLHQtk8x6G/mXCg)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

Message
http://www.ietf.org/internet-drafts/draft-ietf-mip4-experimental-messages-02.txt

This shld help u!
  ----- Original Message ----- 
  From: Radhakrishnan Suryanarayanan 
  To: HS_Arun@huawei.com 
  Cc: mip4@ietf.org 
  Sent: Tuesday, March 01, 2005 1:19 PM
  Subject: Re: [Mip4] Query For error code from HA ..


  Hi arun,
  I got ur scenario. see section 6.4 RFC 3344
  "
   128-192    Error Codes from the Home Agent
  "
  Cisco's behavior is quite right!
    ----- Original Message ----- 
    From: Arun H S 
    To: 'Radhakrishnan Suryanarayanan' 
    Sent: Tuesday, March 01, 2005 1:18 PM
    Subject: RE: [Mip4] Query For error code from HA ..


    do U have a Cisco Rtr there ... U can chk out ... he sends back code 128 (reason un-specified) as the registration reply
      -----Original Message-----
      From: Radhakrishnan Suryanarayanan [mailto:rkrishnan.s@samsung.com] 
      Sent: Tuesday, March 01, 2005 01:09 PM
      To: HS_Arun@huawei.com
      Subject: Re: [Mip4] Query For error code from HA ..


      In such a case the MN/FA can never be reached even to intimate the error. The packet is just discarded at the HA.
      FA/MN does retransmission and The Registration fails! 
        ----- Original Message ----- 
        From: Arun H S 
        To: 'Radhakrishnan Suryanarayanan' 
        Cc: mip4@ietf.org 
        Sent: Tuesday, March 01, 2005 1:00 PM
        Subject: RE: [Mip4] Query For error code from HA ..


        For the Home Agent, I think it dows not matter whether the "COA" is a CLCOA or a COA
          -----Original Message-----
          From: Radhakrishnan Suryanarayanan [mailto:rkrishnan.s@samsung.com] 
          Sent: Tuesday, March 01, 2005 12:42 PM
          To: HS_Arun@huawei.com
          Cc: mip4@ietf.org
          Subject: Re: [Mip4] Query For error code from HA ..


          Hi arun,
            For further understanding your problem can you please clarify the following:
            Is the CoA address of the FA (in case registration is being done via FA) or that MN (co-located CoA)?

          Regards
          Radhakrishnan
            ----- Original Message ----- 
            From: Arun H S 
            To: mip4@ietf.org 
            Sent: Tuesday, March 01, 2005 11:18 AM
            Subject: RE: [Mip4] Query For error code from HA ..


            Hi,

            Sorry, I guess the problem was not understood properly.


                The problem in question is as follows:

                __________                         ____________
                |                | HA1                  |                    |
                |    HA        | ============|        FA        |
                |                |                 FA1  |                    |
                -----------------                         ----------------------
                                                                    ||   COA
                                                                    ||
                                                                    ||
                                                            ___________
                                                            |                  |
                                                            |        MN     |
                                                            |                  |
                                                            --------------------

            Now when MN sends an RRQ with Care-of-Address as COA, to Home-Agent Address, HA1, the Registration is successful because the IP addresses HA1 and FA1 are routable. However, since the tunnel that is created is between the IP addresses HA1 and COA, at the Home Agent, there may not be any route in HA for the IP Address COA. 
            In such a scenario, what type of error-code should the Home Agent send back to the Mobile Node. 

            PS: In such a scenario, the Registration will be successful, however the packet forwarding to the Mobile Node will fail since there is no route to the COA at the Home Agent.

            Regards,
            Arun


              -----Original Message-----
              From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of Radhakrishnan Suryanarayanan
              Sent: Friday, February 25, 2005 05:52 PM
              To: keshavak@huawei.com; mip4@ietf.org
              Subject: Re: [Mip4] Query For error code from HA ..


              Hi Mr.Keshav,
              If you are talking about Registration reply, HA will recv ICMP Destination unreachable (from intermediate routers) for CoA of MN.
              Where is the question of HA sending any error msg to MN if MN's CoA in unreachable?????

              Regards
              Radhakrishnan
                ----- Original Message ----- 
                From: keshav 
                To: mip4@ietf.org 
                Cc: keshavaak@huawei.com 
                Sent: Friday, February 25, 2005 5:32 PM
                Subject: [Mip4] Query For error code from HA ..


                Hi,

                            I would like to know is there any error code that HA has to send to MN if the 

                            Care of address of the MN is not reachable during registration?

                            

                            





                            

                Thanks & regards,

                Keshava





----------------------------------------------------------------


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



------------------------------------------------------------------------


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

--Boundary_(ID_lyDXuacsLHQtk8x6G/mXCg)
Content-type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1491" name=GENERATOR>
<STYLE>@font-face {
	font-family: MS Mincho;
}
@font-face {
	font-family: @MS Mincho;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: Arial
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=purple link=blue bgColor=#ffffff>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2><A 
href="http://www.ietf.org/internet-drafts/draft-ietf-mip4-experimental-messages-02.txt">http://www.ietf.org/internet-drafts/draft-ietf-mip4-experimental-messages-02.txt</A></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>This shld help u!</FONT></DIV>
<BLOCKQUOTE 
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV 
  style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
  <A title=rkrishnan.s@samsung.com 
  href="mailto:rkrishnan.s@samsung.com">Radhakrishnan Suryanarayanan</A> </DIV>
  <DIV style="FONT: 10pt arial"><B>To:</B> <A title=HS_Arun@huawei.com 
  href="mailto:HS_Arun@huawei.com">HS_Arun@huawei.com</A> </DIV>
  <DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=mip4@ietf.org 
  href="mailto:mip4@ietf.org">mip4@ietf.org</A> </DIV>
  <DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, March 01, 2005 1:19 
  PM</DIV>
  <DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [Mip4] Query For error code 
  from HA ..</DIV>
  <DIV><BR></DIV>
  <DIV><FONT face=Arial size=2>Hi arun,</FONT></DIV>
  <DIV><FONT face=Arial size=2>I got ur scenario. </FONT><FONT face=Arial 
  size=2>see section 6.4 RFC 3344</FONT></DIV>
  <DIV><FONT face=Arial size=2>"</FONT></DIV>
  <DIV>&nbsp;128-192&nbsp;&nbsp;&nbsp; Error Codes from the Home Agent<BR><FONT 
  face=Arial size=2>"</FONT></DIV>
  <DIV><FONT face=Arial size=2>Cisco's behavior is quite right!</FONT></DIV>
  <BLOCKQUOTE dir=ltr 
  style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
    <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
    <DIV 
    style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
    <A title=HS_Arun@huawei.com href="mailto:HS_Arun@huawei.com">Arun H S</A> 
    </DIV>
    <DIV style="FONT: 10pt arial"><B>To:</B> <A title=rkrishnan.s@samsung.com 
    href="mailto:rkrishnan.s@samsung.com">'Radhakrishnan Suryanarayanan'</A> 
    </DIV>
    <DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, March 01, 2005 1:18 
    PM</DIV>
    <DIV style="FONT: 10pt arial"><B>Subject:</B> RE: [Mip4] Query For error 
    code from HA ..</DIV>
    <DIV><BR></DIV>
    <DIV><SPAN class=750124707-01032005><FONT face=Arial color=#0000ff size=2>do 
    U have a Cisco Rtr there ... U can chk out ... he sends back code 128 
    (reason un-specified) as the registration reply</FONT></SPAN></DIV>
    <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
      <DIV></DIV>
      <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT 
      face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> 
      Radhakrishnan Suryanarayanan [mailto:rkrishnan.s@samsung.com] 
      <BR><B>Sent:</B> Tuesday, March 01, 2005 01:09 PM<BR><B>To:</B> <A 
      href="mailto:HS_Arun@huawei.com">HS_Arun@huawei.com</A><BR><B>Subject:</B> 
      Re: [Mip4] Query For error code from HA ..<BR><BR></FONT></DIV>
      <DIV><FONT face=Arial size=2>In such a case the MN/FA can never be reached 
      even to intimate the error. The packet is just discarded at the 
      HA.</FONT></DIV>
      <DIV><FONT face=Arial size=2>FA/MN does retransmission&nbsp;and The 
      Registration fails!&nbsp;</FONT></DIV>
      <BLOCKQUOTE 
      style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
        <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
        <DIV 
        style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
        <A title=HS_Arun@huawei.com href="mailto:HS_Arun@huawei.com">Arun H 
        S</A> </DIV>
        <DIV style="FONT: 10pt arial"><B>To:</B> <A 
        title=rkrishnan.s@samsung.com 
        href="mailto:rkrishnan.s@samsung.com">'Radhakrishnan Suryanarayanan'</A> 
        </DIV>
        <DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=mip4@ietf.org 
        href="mailto:mip4@ietf.org">mip4@ietf.org</A> </DIV>
        <DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, March 01, 2005 1:00 
        PM</DIV>
        <DIV style="FONT: 10pt arial"><B>Subject:</B> RE: [Mip4] Query For error 
        code from HA ..</DIV>
        <DIV><BR></DIV>
        <DIV><SPAN class=297153007-01032005><FONT face=Arial color=#0000ff 
        size=2>For the Home Agent, I think it dows not matter whether the "COA" 
        is a CLCOA or a COA</FONT></SPAN></DIV>
        <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
          <DIV></DIV>
          <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT 
          face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> 
          Radhakrishnan Suryanarayanan [mailto:rkrishnan.s@samsung.com] 
          <BR><B>Sent:</B> Tuesday, March 01, 2005 12:42 PM<BR><B>To:</B> <A 
          href="mailto:HS_Arun@huawei.com">HS_Arun@huawei.com</A><BR><B>Cc:</B> 
          <A href="mailto:mip4@ietf.org">mip4@ietf.org</A><BR><B>Subject:</B> 
          Re: [Mip4] Query For error code from HA ..<BR><BR></FONT></DIV>
          <DIV><FONT face=Arial size=2>Hi arun,</FONT></DIV>
          <DIV><FONT face=Arial size=2>&nbsp; For further understanding your 
          problem can you please clarify the following:</FONT></DIV>
          <DIV><FONT face=Arial size=2>&nbsp; Is the CoA address of the FA (in 
          case registration is being done via FA) or that MN (co-located 
          CoA)?</FONT></DIV>
          <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
          <DIV><FONT face=Arial size=2>Regards</FONT></DIV>
          <DIV><FONT face=Arial size=2>Radhakrishnan</FONT></DIV>
          <BLOCKQUOTE 
          style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
            <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
            <DIV 
            style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
            <A title=HS_Arun@huawei.com href="mailto:HS_Arun@huawei.com">Arun H 
            S</A> </DIV>
            <DIV style="FONT: 10pt arial"><B>To:</B> <A title=mip4@ietf.org 
            href="mailto:mip4@ietf.org">mip4@ietf.org</A> </DIV>
            <DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, March 01, 2005 
            11:18 AM</DIV>
            <DIV style="FONT: 10pt arial"><B>Subject:</B> RE: [Mip4] Query For 
            error code from HA ..</DIV>
            <DIV><BR></DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005>Hi,</SPAN></FONT></DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005>Sorry, I guess the problem was not 
            understood properly.</SPAN></FONT></DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005>&nbsp;&nbsp;&nbsp; The problem in question 
            is as follows:</SPAN></FONT></DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005>&nbsp;&nbsp;&nbsp; 
            __________&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
            ____________</SPAN></FONT></DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005>&nbsp;&nbsp;&nbsp; 
            |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
            |&nbsp;HA1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
            |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
            |</SPAN></FONT></DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005>&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp; 
            HA&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
            |&nbsp;============|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
            FA&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</SPAN></FONT></DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005>&nbsp;&nbsp;&nbsp; 
            |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
            |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;FA1&nbsp; 
            |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
            |</SPAN></FONT></DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005>&nbsp;&nbsp;&nbsp; 
            -----------------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
            ----------------------</SPAN></FONT></DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
            ||&nbsp;&nbsp; COA</SPAN></FONT></DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
            ||</SPAN></FONT></DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
            ||</SPAN></FONT></DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;___________</SPAN></FONT></DIV>
            <DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
            |</SPAN></FONT></DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;MN&nbsp;&nbsp;&nbsp;&nbsp; 
            |</SPAN></FONT></DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
            |</SPAN></FONT></DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;--------------------</SPAN></FONT></DIV></SPAN></FONT></DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005>Now when MN sends an RRQ with 
            Care-of-Address as COA, to Home-Agent Address, HA1, the Registration 
            is successful because the IP addresses HA1 and FA1 are routable. 
            However, since the tunnel that is created is between the IP 
            addresses HA1 and COA, at the Home Agent, there may not be any route 
            in HA for the IP Address COA. </SPAN></FONT></DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005>In such a scenario, what type of error-code 
            should the Home Agent send back to the Mobile Node. 
            </SPAN></FONT></DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005>PS: In such a scenario, the Registration 
            will be successful, however the packet forwarding to the Mobile Node 
            will fail since there is no route to the COA at the Home 
            Agent.</SPAN></FONT></DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005>Regards,</SPAN></FONT></DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005>Arun</SPAN></FONT></DIV>
            <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
            class=506073005-01032005></SPAN></FONT>&nbsp;</DIV>
            <DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
            <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
              <DIV></DIV>
              <DIV class=OutlookMessageHeader lang=en-us dir=ltr 
              align=left><FONT face=Tahoma size=2>-----Original 
              Message-----<BR><B>From:</B> mip4-bounces@ietf.org 
              [mailto:mip4-bounces@ietf.org] <B>On Behalf Of </B>Radhakrishnan 
              Suryanarayanan<BR><B>Sent:</B> Friday, February 25, 2005 05:52 
              PM<BR><B>To:</B> keshavak@huawei.com; 
              mip4@ietf.org<BR><B>Subject:</B> Re: [Mip4] Query For error code 
              from HA ..<BR><BR></FONT></DIV>
              <DIV><FONT face=Arial size=2>Hi Mr.Keshav,</FONT></DIV>
              <DIV><FONT face=Arial size=2>If&nbsp;you</FONT><FONT face=Arial 
              size=2> are talking about Registration reply, </FONT><FONT 
              face=Arial size=2>HA will recv ICMP Destination unreachable (from 
              intermediate routers) for CoA of MN.</FONT></DIV>
              <DIV><FONT face=Arial size=2>Where is the question of HA sending 
              any error msg to MN if&nbsp;MN's CoA in 
              unreachable?????</FONT></DIV>
              <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
              <DIV><FONT face=Arial size=2>Regards</FONT></DIV>
              <DIV><FONT face=Arial size=2>Radhakrishnan</FONT></DIV>
              <BLOCKQUOTE 
              style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
                <DIV style="FONT: 10pt arial">----- Original Message ----- 
</DIV>
                <DIV 
                style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
                <A title=keshavak@huawei.com 
                href="mailto:keshavak@huawei.com">keshav</A> </DIV>
                <DIV style="FONT: 10pt arial"><B>To:</B> <A title=mip4@ietf.org 
                href="mailto:mip4@ietf.org">mip4@ietf.org</A> </DIV>
                <DIV style="FONT: 10pt arial"><B>Cc:</B> <A 
                title=keshavaak@huawei.com 
                href="mailto:keshavaak@huawei.com">keshavaak@huawei.com</A> 
                </DIV>
                <DIV style="FONT: 10pt arial"><B>Sent:</B> Friday, February 25, 
                2005 5:32 PM</DIV>
                <DIV style="FONT: 10pt arial"><B>Subject:</B> [Mip4] Query For 
                error code from HA ..</DIV>
                <DIV><BR></DIV>
                <DIV class=Section1>
                <P class=MsoNormal><FONT face=Arial size=2><SPAN 
                style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi,</SPAN></FONT></P>
                <P class=MsoNormal><FONT face=Arial size=2><SPAN 
                style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
                I would like to know is there any error code that HA has to send 
                to MN if the </SPAN></FONT></P>
                <P class=MsoNormal><FONT face=Arial size=2><SPAN 
                style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
                Care of address of the MN is not reachable during 
                registration?</SPAN></FONT></P>
                <P class=MsoNormal><FONT face=Arial size=2><SPAN 
                style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
                </SPAN></FONT></P>
                <P class=MsoNormal><FONT face=Arial size=2><SPAN 
                style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
                </SPAN></FONT></P>
                <P class=MsoNormal><FONT face=Arial size=2><SPAN 
                style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
                <P class=MsoNormal><FONT face=Arial size=2><SPAN 
                style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
                <P class=MsoNormal><FONT face=Arial size=2><SPAN 
                style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
                </SPAN></FONT></P>
                <P class=MsoNormal><FONT face=Arial size=2><SPAN 
                style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Thanks &amp; 
                regards,</SPAN></FONT></P>
                <P class=MsoNormal><FONT face=Arial size=2><SPAN 
                style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Keshav</SPAN></FONT><FONT 
                face=Arial size=2><SPAN 
                style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">a</SPAN></FONT></P>
                <P class=MsoNormal><FONT face=Arial size=2><SPAN 
                style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P></DIV>
                <P>
                <HR>

                <P></P>-- <BR>Mip4 mailing list: <A 
                href="mailto:Mip4@ietf.org">Mip4@ietf.org</A><BR>&nbsp;&nbsp;&nbsp; 
                Web interface: <A 
                href="https://www1.ietf.org/mailman/listinfo/mip4">https://www1.ietf.org/mailman/listinfo/mip4</A><BR>&nbsp;&nbsp;&nbsp;&nbsp; 
                Charter page: <A 
                href="http://www.ietf.org/html.charters/mip4-charter.html">http://www.ietf.org/html.charters/mip4-charter.html</A><BR>Supplemental 
                site: http://www.mip4.org/<BR></BLOCKQUOTE></BLOCKQUOTE>
            <P>
            <HR>

            <P></P>-- <BR>Mip4 mailing list: Mip4@ietf.org<BR>&nbsp;&nbsp;&nbsp; 
            Web interface: 
            https://www1.ietf.org/mailman/listinfo/mip4<BR>&nbsp;&nbsp;&nbsp;&nbsp; 
            Charter page: 
            http://www.ietf.org/html.charters/mip4-charter.html<BR>Supplemental 
            site: http://www.mip4.org/<BR></BLOCKQUOTE></BLOCKQUOTE>
        <P>
        <HR>

        <P></P>-- <BR>Mip4 mailing list: Mip4@ietf.org<BR>&nbsp;&nbsp;&nbsp; Web 
        interface: 
        https://www1.ietf.org/mailman/listinfo/mip4<BR>&nbsp;&nbsp;&nbsp;&nbsp; 
        Charter page: 
        http://www.ietf.org/html.charters/mip4-charter.html<BR>Supplemental 
        site: http://www.mip4.org/<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <P>
  <HR>

  <P></P>-- <BR>Mip4 mailing list: Mip4@ietf.org<BR>&nbsp;&nbsp;&nbsp; Web 
  interface: 
  https://www1.ietf.org/mailman/listinfo/mip4<BR>&nbsp;&nbsp;&nbsp;&nbsp; 
  Charter page: 
  http://www.ietf.org/html.charters/mip4-charter.html<BR>Supplemental site: 
  http://www.mip4.org/<BR></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_lyDXuacsLHQtk8x6G/mXCg)--


--===============0918782475==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0918782475==--



From mip4-bounces@ietf.org  Tue Mar  1 09:55:50 2005
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 JAA02126
	for <mip4-web-archive@ietf.org>; Tue, 1 Mar 2005 09:55:49 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D68nr-0005IU-I1
	for mip4-web-archive@ietf.org; Tue, 01 Mar 2005 09:56:51 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D68lj-00016O-Oq; Tue, 01 Mar 2005 09:54:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D56zM-0001wO-Tn
	for mip4@megatron.ietf.org; Sat, 26 Feb 2005 13:48:28 -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 NAA22378
	for <mip4@ietf.org>; Sat, 26 Feb 2005 13:48:25 -0500 (EST)
Received: from cs-exs2.bu.edu ([128.197.10.200])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D56zk-0000Yq-Ut
	for mip4@ietf.org; Sat, 26 Feb 2005 13:48:53 -0500
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Sat, 26 Feb 2005 13:48:32 -0500
Message-ID: <0511C607B17F804EBE96FFECD1FD98591E8333@cs-exs2.cs-nt.bu.edu>
Thread-Topic: SenMetrics 2005 CFP
Thread-Index: AcUcM7QAdRQIGC1dTLib10XSQwk4Tw==
From: "Ibrahim Matta" <matta@cs.bu.edu>
To: <mip4@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Tue, 01 Mar 2005 09:54:39 -0500
Subject: [Mip4] SenMetrics 2005 CFP
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d
Content-Transfer-Encoding: quoted-printable


CALL FOR PAPERS

SenMetrics 2005

Third International Workshop on Measurement, Modeling,=20
and Performance Analysis of Wireless Sensor Networks=20

San Diego, CA, USA
July 21, 2005

(in conjunction with MobiQuitous 2005)

http://www.senmetrics.org/
E-mail: senmetrics@ece.osu.edu


The SenMetrics workshop solicits papers on the development=20
and application of analytic, simulation, prototype testbed,=20
and measurement-based performance evaluation techniques to=20
the area of wireless sensor networks. Of particular interest=20
is work that furthers the state-of-the-art in performance=20
evaluation methods, or those that creatively apply=20
previously developed methods to understand or to gain=20
important insights into key design trade-offs in wireless=20
sensor networks.=20

Topics of interest include, but are not limited to:
=20
Performance-oriented design and evaluation studies of:
- wireless sensor networks
- sensor node hardware and software architectures
- data collection
- addressing=20
- security, reliability, and robustness
- operating systems
- energy aware network protocols
- applications
- localization
- fundamental limits and tradeoffs
- topology management
- deployment
- distributed actuation and control
- system development and testbed experience
- benchmarks

Performance methodology techniques and algorithms for:=20
- system, protocol, and algorithm modeling
- analytic evaluation
- system measurement and monitoring
- model verification and validation
- workload characterization
- simulation
- statistical analysis
- stochastic modeling=20
- experimental design
- reliability analysis
- performance optimization


IMPORTANT DATES:

Paper Submission Deadline: April 15, 2005
Notification of Acceptance: June 1, 2005
Camera Ready Paper Due: June 15, 2005
Workshop Date: July 21, 2005


PAPERS:

Authors are invited to submit for review, papers that=20
neither have been previously published nor are under review=20
by another conference or journal. Priority will be given to=20
original contributions describing recent and innovative=20
research results or developments in the scope of the workshop.=20

Papers must be written in English, using font no smaller than=20
10 points and not to exceed 10 pages. Only PDF and PostScript=20
formats will be accepted, and all submissions will be handled=20
electronically. Further details on submission procedures will=20
be soon available at  http://www.senmetrics.org/


GENERAL CHAIR:

Raghupathy Sivakumar, Georgia Institute of Technology

PROGRAM CHAIRS:

Eylem Ekici, Ohio State University
Ibrahim Matta, Boston University

PUBLICITY CHAIR:

Seung-Jong Park, Louisiana State University


TECHNICAL PROGRAM COMMITTEE:

Alhussein Abouzeid (RPI)
Ozgur B. Akan (Middle East Technical U, Turkey)
Andrew Campbell (Columbia University)=20
Sonia Fahmy (Purdue University)=20
Paul Havinga (University of Twente, The Netherlands)
Ahmed Helmy (USC)
Holger Karl (University of Paderborn, Germany)
Bhaskar Khrisnamachari (USC)=20
Marwan Krunz (University of Arizona)
Kang-Won Lee (IBM Research)
Mingyan Liu (University of Michigan)
Stephan Olariu (Old Dominion University)
Sergio Palazzo (University of Catania, Italy)
Seung-Jong Park (Louisiana State University)
Ness Shroff (Purdue University)=20
David Starobinski (Boston University)=20
Ioannis Stavrakakis (University of Athens, Greece)=20
Xin Wang (University at Buffalo)
Wenye Wang (North Carolina State University)=20
Lixia Zhang (UCLA)
Taieb Znati (University of Pittsburgh)

_______________________________________________________


=3D=3D=3D
Ibrahim Matta, Associate Professor
Computer Science Department
Boston University, Boston, MA 02215, USA
Tel: (617) 358-1062, Fax: (617) 353-6457
matta@cs.bu.edu
http://www.cs.bu.edu/~matta=20

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


From mip4-bounces@ietf.org  Thu Mar  3 06:07:39 2005
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 GAA07168
	for <mip4-web-archive@ietf.org>; Thu, 3 Mar 2005 06:07:39 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D6oCW-00053H-0G
	for mip4-web-archive@ietf.org; Thu, 03 Mar 2005 06:09:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D6o8N-0002cs-9O; Thu, 03 Mar 2005 06:04:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D6o8H-0002cj-KD
	for mip4@megatron.ietf.org; Thu, 03 Mar 2005 06:04:41 -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 GAA06920
	for <mip4@ietf.org>; Thu, 3 Mar 2005 06:04:39 -0500 (EST)
Received: from web42208.mail.yahoo.com ([66.218.93.209])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D6o9c-0004zf-B9
	for mip4@ietf.org; Thu, 03 Mar 2005 06:06:05 -0500
Received: (qmail 26514 invoked by uid 60001); 3 Mar 2005 11:04:31 -0000
Message-ID: <20050303110431.26512.qmail@web42208.mail.yahoo.com>
Received: from [193.204.86.131] by web42208.mail.yahoo.com via HTTP;
	Thu, 03 Mar 2005 12:04:31 CET
Date: Thu, 3 Mar 2005 12:04:31 +0100 (CET)
From: dav s <daikrux@yahoo.it>
To: mip4@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id GAA06920
Subject: [Mip4] FA&HA on the same machine
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: quoted-printable

Hello everybody,
i hope it's the right place for my questions...
can i put on the same machine a Foreign Agent and an
Home Agent or could I have some problems?=20
thanks in advance!
davide.


	=09
___________________________________=20
Nuovo Yahoo! Messenger: E' molto pi=F9 divertente: Audibles, Avatar, Webc=
am, Giochi, Rubrica=85 Scaricalo ora!=20
http://it.messenger.yahoo.it

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


From mip4-bounces@ietf.org  Thu Mar  3 06:27:47 2005
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 GAA09679
	for <mip4-web-archive@ietf.org>; Thu, 3 Mar 2005 06:27:47 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D6oW2-0005gH-7A
	for mip4-web-archive@ietf.org; Thu, 03 Mar 2005 06:29:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D6oS7-00064X-Ub; Thu, 03 Mar 2005 06:25:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D6oS6-00064S-4g
	for mip4@megatron.ietf.org; Thu, 03 Mar 2005 06:25:10 -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 GAA09207
	for <mip4@ietf.org>; Thu, 3 Mar 2005 06:25:06 -0500 (EST)
Received: from smtp2.nblnetworks.fi ([217.30.182.231])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D6oTR-0005Yq-3X
	for mip4@ietf.org; Thu, 03 Mar 2005 06:26:33 -0500
Received: from yin.bjorns.net (xdsl-178-232.nblnetworks.fi [217.30.178.232])
	by smtp2.nblnetworks.fi (8.12.8/8.12.8) with ESMTP id j23BP17A005816;
	Thu, 3 Mar 2005 13:25:01 +0200
Received: from bjorn by yin.bjorns.net with local (Exim 3.36 #1 (Debian))
	id 1D6oRw-0004sg-00; Thu, 03 Mar 2005 13:25:00 +0200
Date: Thu, 3 Mar 2005 13:25:00 +0200
From: bjorn@iki.fi
To: dav s <daikrux@yahoo.it>
Subject: Re: [Mip4] FA&HA on the same machine
Message-ID: <20050303112500.GC18660@yin.bjorns.net>
References: <20050303110431.26512.qmail@web42208.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050303110431.26512.qmail@web42208.mail.yahoo.com>
X-Spam-Score: 0.3 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906

On Thu, Mar 03 2005, at 12:04:31 +0100, dav s wrote:
> Hello everybody,
> i hope it's the right place for my questions...
> can i put on the same machine a Foreign Agent and an
> Home Agent or could I have some problems? 

There is nothing in the RFCs that prohibits this setup, you shouldn't
have any problems protocolwise. There are also several implementation
that allows this setup, but there are also implementations where this
is not possible. 

Regards,
Bjorn Andersson

-- 
Bjorn Andersson <bjorn@iki.fi>
PGP id 5AFC144B

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


From mip4-bounces@ietf.org  Thu Mar  3 07:17:30 2005
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 HAA15744
	for <mip4-web-archive@ietf.org>; Thu, 3 Mar 2005 07:17:30 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D6pI8-00079F-VS
	for mip4-web-archive@ietf.org; Thu, 03 Mar 2005 07:18:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D6pDe-0001HF-OB; Thu, 03 Mar 2005 07:14:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D6pDd-0001H3-Ju
	for mip4@megatron.ietf.org; Thu, 03 Mar 2005 07:14:17 -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 HAA15393
	for <mip4@ietf.org>; Thu, 3 Mar 2005 07:14:14 -0500 (EST)
Received: from web42207.mail.yahoo.com ([66.218.93.208])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D6pEy-00074i-Gt
	for mip4@ietf.org; Thu, 03 Mar 2005 07:15:41 -0500
Received: (qmail 78416 invoked by uid 60001); 3 Mar 2005 12:14:04 -0000
Message-ID: <20050303121404.78414.qmail@web42207.mail.yahoo.com>
Received: from [193.204.86.131] by web42207.mail.yahoo.com via HTTP;
	Thu, 03 Mar 2005 13:14:04 CET
Date: Thu, 3 Mar 2005 13:14:04 +0100 (CET)
From: davide <daikrux@yahoo.it>
Subject: Re: [Mip4] FA&HA on the same machine
To: bjorn@iki.fi
In-Reply-To: <20050303112500.GC18660@yin.bjorns.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id HAA15393
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: quoted-printable

Thanks Bjorn,
I've seen in RFC 3344 that Home Agent and Foreign
Agent listen to Registration Requests on the same port
(434).
I think that this could cause problems if I put the HA
and FA on the same machine.
What do you think?
Thanks!


 --- bjorn@iki.fi ha scritto:=20
> On Thu, Mar 03 2005, at 12:04:31 +0100, davide
wrote:
> > Hello everybody,
> > i hope it's the right place for my questions...
> > can i put on the same machine a Foreign Agent and
> an
> > Home Agent or could I have some problems?=20
>=20
> There is nothing in the RFCs that prohibits this
> setup, you shouldn't
> have any problems protocolwise. There are also
> several implementation
> that allows this setup, but there are also
> implementations where this
> is not possible.=20
>=20
> Regards,
> Bjorn Andersson
>=20
> --=20
> Bjorn Andersson <bjorn@iki.fi>
> PGP id 5AFC144B
> =20


	=09
___________________________________=20
Nuovo Yahoo! Messenger: E' molto pi=F9 divertente: Audibles, Avatar, Webc=
am, Giochi, Rubrica=85 Scaricalo ora!=20
http://it.messenger.yahoo.it

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


From mip4-bounces@ietf.org  Thu Mar  3 09:18:13 2005
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 JAA27288
	for <mip4-web-archive@ietf.org>; Thu, 3 Mar 2005 09:18:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D6rAy-0001Vh-R8
	for mip4-web-archive@ietf.org; Thu, 03 Mar 2005 09:19:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D6r8g-00041A-1v; Thu, 03 Mar 2005 09:17:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D6r8e-000415-Gv
	for mip4@megatron.ietf.org; Thu, 03 Mar 2005 09:17:16 -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 JAA27217
	for <mip4@ietf.org>; Thu, 3 Mar 2005 09:17:14 -0500 (EST)
Received: from smtp2.nblnetworks.fi ([217.30.182.231])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D6rA0-0001Ua-Ok
	for mip4@ietf.org; Thu, 03 Mar 2005 09:18:42 -0500
Received: from yin.bjorns.net (xdsl-178-232.nblnetworks.fi [217.30.178.232])
	by smtp2.nblnetworks.fi (8.12.8/8.12.8) with ESMTP id j23EH96U029397;
	Thu, 3 Mar 2005 16:17:09 +0200
Received: from bjorn by yin.bjorns.net with local (Exim 3.36 #1 (Debian))
	id 1D6r8X-00052f-00; Thu, 03 Mar 2005 16:17:09 +0200
Date: Thu, 3 Mar 2005 16:17:09 +0200
From: bjorn@iki.fi
To: davide <daikrux@yahoo.it>
Subject: Re: [Mip4] FA&HA on the same machine
Message-ID: <20050303141709.GB19249@yin.bjorns.net>
References: <20050303112500.GC18660@yin.bjorns.net>
	<20050303121404.78414.qmail@web42207.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050303121404.78414.qmail@web42207.mail.yahoo.com>
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007

On Thu, Mar 03 2005, at 13:14:04 +0100, davide wrote:
> Thanks Bjorn,
> I've seen in RFC 3344 that Home Agent and Foreign
> Agent listen to Registration Requests on the same port
> (434).
> I think that this could cause problems if I put the HA
> and FA on the same machine.
> What do you think?

This is not a problem. You can deterimine if the packet is destined to
the home agent or foreign agent based on the home agent address in the
registration request message. As I said, there is empirical evidence in
several Mobile IP implementations that it is possible to run the foreign
and home agent on the same host. It is an implementation specific issue
if it possible to run both services on the same host.

Regards,
Bjorn

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


From mip4-bounces@ietf.org  Fri Mar  4 16:55:17 2005
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 QAA09203
	for <mip4-web-archive@ietf.org>; Fri, 4 Mar 2005 16:55:17 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D7Kn8-0007Jo-Hp
	for mip4-web-archive@ietf.org; Fri, 04 Mar 2005 16:57:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D7KjB-0002Rm-TI; Fri, 04 Mar 2005 16:52:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D7Kj7-0002Qb-Ou
	for mip4@megatron.ietf.org; Fri, 04 Mar 2005 16:52:54 -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 QAA09094
	for <mip4@ietf.org>; Fri, 4 Mar 2005 16:52:51 -0500 (EST)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D7Kkl-0007HM-Qx
	for mip4@ietf.org; Fri, 04 Mar 2005 16:54:36 -0500
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (Motorola/Motgate8) with ESMTP id j24Lt02C000766
	for <mip4@ietf.org>; Fri, 4 Mar 2005 14:55:00 -0700 (MST)
Received: from il27exm03.cig.mot.com (il27exm03.cig.mot.com [10.17.193.4])
	by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id j24LrSoT011474
	for <mip4@ietf.org>; Fri, 4 Mar 2005 15:53:28 -0600 (CST)
Received: by il27exm03.cig.mot.com with Internet Mail Service (5.5.2657.72)
	id <D3VHLD20>; Fri, 4 Mar 2005 15:52:51 -0600
Message-ID: <EBF631554F9CD7118D0B00065BF34DCB18379493@il27exm03.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'Pete McCann'" <mccap@lucent.com>, Archana <archana_p@huawei.com>
Subject: RE: [Mip4] Query regarding MN-AAA authenticator calculation.
Date: Fri, 4 Mar 2005 15:52:50 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1

Hi, 

I have been meaning to respond to this as well. I agree there is no RADIUS MD5. However, there is a problem with sending all the following

Preceding Mobile IP data ||
        Type, Subtype (if present), Length, SPI) ||
       Least-order 237 bytes from Challenge

Over RADIUS messages, since RADIUS packets can be at most 4K long and attributes at most 253 bytes (if I understood this correctly), which means you do have to calculate a hash of the data above before packing it over RADIUS messaging, if you want the AAA server to do the same calculations. If anybody has a number on the number of bytes the data above takes, I would appreciate it??
We tried to explain this in our draft on RADIUS support for MIP-AAA signaling.

http://www.ietf.org/internet-drafts/draft-nakhjiri-radius-mip4-00.txt

We ran into another problem with this and that was: the challenge is used only in conjunctions with FAs and when the MN uses a CcoA and registers through HA directly, there won't be any challenge to calculate 

MD5      (High-order byte from Challenge || Key ||
        MD5(Preceding Mobile IP data ||
        Type, Subtype (if present), Length, SPI) ||
        Least-order 237 bytes from Challenge))

Our proposal based on Charlie's suggestion (no mean to push the blame, Charlie :) ) was to include zero octets whenever challenge data was needed in that case.

Any thoughts?

Madjid
-----Original Message-----
From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of Pete McCann
Sent: Friday, February 25, 2005 9:48 AM
To: Archana
Cc: mip4@ietf.org
Subject: [Mip4] Query regarding MN-AAA authenticator calculation.


Hi, Archana,

Archana writes:
 > Hi 
 > According to RFC 3012, the MN-AAA authenticator is computed by applying MD5
 > on the following data
 > 
 >       High-order byte from Challenge || Key ||
 >       MD5(Preceding Mobile IP data ||
 >       Type, Subtype (if present), Length, SPI) ||
 >       Least-order 237 bytes from Challenge
 > 
 > I have the following queries regarding the above computation. Any help in
 > the clarifying them will be highly appreciated.
 > 
 > 1. What is meant by High-order and Least order ? 

"High-order" means "most significant".  You can also interpret it as
"leftmost" when looking at the encoding of the Challenge in a Mobile
IP Extension.

 > 2. How does the Radius MD5 algorithm differ in calculating the Authenticator
 > from a MD5 algorithm

There is no special "Radius MD5" as far as I know.

MD5 is specified in RFC3121.  It is a well-known hash function that
processes the input and produces a 16 octet hash.

The calculation shown above is compatible with existing RADIUS servers
that are used for authenticating PPP/CHAP, i.e., the code used for
PPP/CHAP can be re-used to compute the above authenticator, assuming
that the FA can precompute the inner MD5 and send it in an
Access-Request.

-Pete

 > Thanks in advance
 > Archana


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


From mip4-bounces@ietf.org  Fri Mar  4 20:23:19 2005
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 UAA27975
	for <mip4-web-archive@ietf.org>; Fri, 4 Mar 2005 20:23:19 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D7O2S-0003lr-U1
	for mip4-web-archive@ietf.org; Fri, 04 Mar 2005 20:25:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D7NzL-0005Gx-3n; Fri, 04 Mar 2005 20:21:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D7NzI-0005Gs-LO
	for mip4@megatron.ietf.org; Fri, 04 Mar 2005 20:21:49 -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 UAA27905
	for <mip4@ietf.org>; Fri, 4 Mar 2005 20:21:46 -0500 (EST)
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.33)
	id 1D7O0x-0003kP-Ah
	for mip4@ietf.org; Fri, 04 Mar 2005 20:23:32 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-3.cisco.com with ESMTP; 04 Mar 2005 18:37:54 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.90,137,1107734400"; 
	d="scan'208"; a="231601745:sNHT22288816"
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j251LUZV005337;
	Fri, 4 Mar 2005 17:21:30 -0800 (PST)
Received: from kleung-w2k01.cisco.com (sjc-vpn5-220.cisco.com [10.21.88.220])
	by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with ESMTP id BCM35452;
	Fri, 4 Mar 2005 17:21:25 -0800 (PST)
Message-Id: <4.3.2.7.2.20050304171245.03635250@mira-sjcm-2.cisco.com>
X-Sender: kleung@mira-sjcm-2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 04 Mar 2005 17:21:21 -0800
To: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
From: Kent Leung <kleung@cisco.com>
Subject: RE: [Mip4] Query regarding MN-AAA authenticator calculation.
In-Reply-To: <EBF631554F9CD7118D0B00065BF34DCB18379493@il27exm03.cig.mot .com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede
Cc: "'Pete McCann'" <mccap@lucent.com>, Archana <archana_p@huawei.com>,
        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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3

Hi Madjid.  The rfc3012bis draft covers the CCoA mode.

>Based on local policy, a Mobile Node with co-located care-of-address
>    MAY include the Mobile-AAA Authentication extension in Registration
>    Request.  In this case, if the Mobile Node uses SPI value of CHAP_SPI
>    or HMAC_CHAP_SPI (section 8) in the MN-AAA Authentication extension,
>    Mobile Node MUST include the Mobile-Foreign Challenge extension prior
>    to the Mobile-AAA Authentication extension.  The mechanism used by
>    the Mobile Node to obtain the Challenge value is outside the scope of
>    this document.

Kent


At 03:52 PM 3/4/2005 -0600, Nakhjiri Madjid-MNAKHJI1 wrote:
>Hi,
>
>I have been meaning to respond to this as well. I agree there is no RADIUS 
>MD5. However, there is a problem with sending all the following
>
>Preceding Mobile IP data ||
>         Type, Subtype (if present), Length, SPI) ||
>        Least-order 237 bytes from Challenge
>
>Over RADIUS messages, since RADIUS packets can be at most 4K long and 
>attributes at most 253 bytes (if I understood this correctly), which means 
>you do have to calculate a hash of the data above before packing it over 
>RADIUS messaging, if you want the AAA server to do the same calculations. 
>If anybody has a number on the number of bytes the data above takes, I 
>would appreciate it??
>We tried to explain this in our draft on RADIUS support for MIP-AAA signaling.
>
>http://www.ietf.org/internet-drafts/draft-nakhjiri-radius-mip4-00.txt
>
>We ran into another problem with this and that was: the challenge is used 
>only in conjunctions with FAs and when the MN uses a CcoA and registers 
>through HA directly, there won't be any challenge to calculate
>
>MD5      (High-order byte from Challenge || Key ||
>         MD5(Preceding Mobile IP data ||
>         Type, Subtype (if present), Length, SPI) ||
>         Least-order 237 bytes from Challenge))
>
>Our proposal based on Charlie's suggestion (no mean to push the blame, 
>Charlie :) ) was to include zero octets whenever challenge data was needed 
>in that case.
>
>Any thoughts?
>
>Madjid
>-----Original Message-----
>From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of 
>Pete McCann
>Sent: Friday, February 25, 2005 9:48 AM
>To: Archana
>Cc: mip4@ietf.org
>Subject: [Mip4] Query regarding MN-AAA authenticator calculation.
>
>
>Hi, Archana,
>
>Archana writes:
>  > Hi
>  > According to RFC 3012, the MN-AAA authenticator is computed by 
> applying MD5
>  > on the following data
>  >
>  >       High-order byte from Challenge || Key ||
>  >       MD5(Preceding Mobile IP data ||
>  >       Type, Subtype (if present), Length, SPI) ||
>  >       Least-order 237 bytes from Challenge
>  >
>  > I have the following queries regarding the above computation. Any help in
>  > the clarifying them will be highly appreciated.
>  >
>  > 1. What is meant by High-order and Least order ?
>
>"High-order" means "most significant".  You can also interpret it as
>"leftmost" when looking at the encoding of the Challenge in a Mobile
>IP Extension.
>
>  > 2. How does the Radius MD5 algorithm differ in calculating the 
> Authenticator
>  > from a MD5 algorithm
>
>There is no special "Radius MD5" as far as I know.
>
>MD5 is specified in RFC3121.  It is a well-known hash function that
>processes the input and produces a 16 octet hash.
>
>The calculation shown above is compatible with existing RADIUS servers
>that are used for authenticating PPP/CHAP, i.e., the code used for
>PPP/CHAP can be re-used to compute the above authenticator, assuming
>that the FA can precompute the inner MD5 and send it in an
>Access-Request.
>
>-Pete
>
>  > Thanks in advance
>  > Archana
>
>
>--
>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/

--
      |           |                   Kent Leung
     :|:         :|:                  IP Mobility Development
    :|||:       :|||:                 Internet Technologies Division
   :|||||||:   :|||||||:              Voice: 408.526.5030
.:|||||||||:.:|||||||||:.             Fax:   408.525.1653
  c i s c o S y s t e m s             Email: kleung@cisco.com

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


From mip4-bounces@ietf.org  Sun Mar  6 17:35:31 2005
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 RAA03584
	for <mip4-web-archive@ietf.org>; Sun, 6 Mar 2005 17:35:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D84Na-0007wG-Qj
	for mip4-web-archive@ietf.org; Sun, 06 Mar 2005 17:37:43 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D84Fp-0004aD-Aw; Sun, 06 Mar 2005 17:29:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D84Fl-0004Zc-Vu
	for mip4@megatron.ietf.org; Sun, 06 Mar 2005 17:29:38 -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 RAA03066
	for <mip4@ietf.org>; Sun, 6 Mar 2005 17:29:35 -0500 (EST)
Received: from carrierpigeon.cs.umd.edu ([128.8.129.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D84Hp-0007m9-Vo
	for mip4@ietf.org; Sun, 06 Mar 2005 17:31:46 -0500
Received: from MINDLAP2 (mindlap2.cs.umd.edu [172.16.0.37])
	(authenticated bits=0)
	by carrierpigeon.cs.umd.edu (8.12.10/8.12.5) with ESMTP id
	j26MTNnC001730
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <mip4@ietf.org>; Sun, 6 Mar 2005 17:29:28 -0500 (EST)
Message-Id: <200503062229.j26MTNnC001730@carrierpigeon.cs.umd.edu>
From: "Moustafa Youssef" <moustafa@cs.umd.edu>
To: <mip4@ietf.org>
Date: Sun, 6 Mar 2005 17:29:04 -0500
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_01C7_01C52272.04DA2AF0"
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-MS-TNEF-Correlator: 0000000006F61F65A15E334E985099AB7E0DC8D364542200
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7e439b86d3292ef5adf93b694a43a576
Subject: [Mip4] [Deadline Approaching] Final CFP: IEEE WirelessCom Symposium
	on Mobile Computing, 2005
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2a76bcd37b1c8a21336eb0a1ea6bbf48

This is a multi-part message in MIME format.

------=_NextPart_000_01C7_01C52272.04DA2AF0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

(Our apologies if you receive multiple copies of this CFP)

-------------------------------------------------------------
                    Final Call for Papers
              Symposium on Mobile Computing
  http://www.csee.umbc.edu/~younis/WC_MobCom05.htm
                       as part of=20
                IEEE WirelessCom 2005
Sheraton Maui Resort, Kaanapali Beach, Maui, Hawaii, USA
           http://sa1.sice.umkc.edu/wc05/=20
                   June 13-16, 2005
  Technical Sponsorship: IEEE TCCC, TCPC, and SSCTC


Recent years have witnessed an enormous growth in the development and
applications of mobile computing environments and devices. Many
practitioners envision a future empowered with context and location =
aware
computation and communication infrastructure that allow users to access =
data
and receive service at any place and any time. Compared to conventional
platforms, the mobility of computing nodes introduces many challenges to =
the
design of almost all systems components.=20

This symposium will foster a forum for discussing and presenting recent
research results on mobile computer systems. Original papers are invited =
in
the broader area of mobile computing. Papers must report high-quality =
and
previously unpublished work. Topics of interest include, but are not =
limited
to, the following:

=95	Architecture and infrastructure support=09
=95	Middleware and operating systems services
=95	Development platforms and environments
=95	Adaptive resource management schemes
=95	Pervasive and Context-aware Computing
=95	Performance metrics and studies
=95	Power aware computation and communication
=95	Data consistency and synchronization protocols
=95	Fault-tolerant architectural and operation models
=95	Wearable computing devices and systems
=95	Time constrained mobile systems
=95	Robust ad-hoc networking techniques
=95	Efficient localization techniques
=95	Wireless sensor networks
=95	Mobile peer to peer systems
=95	Quality of service provisioning
=95	Context-conscious computing
=95	Web caching and services
=95	Emerging applications and systems
=95	Mobile agents
=95	Mobile commerce
=95	Security and privacy issues


Submission Guidelines
---------------------
Original papers are solicited and must represent high-quality and =
previously
unpublished work, not currently under review by another conference or
journal. Prospective authors should submit their paper electronically
through https://msrcmt.research.microsoft.com/WirelessCom2005. All =
papers
are limited to 6 pages in standard IEEE double-column format.=20

Important Dates
---------------
Paper Submission Deadline: 	March 15, 2005
Notification of Acceptance: 	April 15, 2005
Camera-Ready Papers: 	May 1, 2005

Symposium Co-Chairs
-------------------
Mohamed Younis
Department of Computer Science and Electrical Engineering University of
Maryland Baltimore County, 1000 Hilltop Circle, Baltimore, MD 21250
Voice: (410) 455-3968,    FAX: (410) 455-3968
E-mail: younis@csee.umbc.edu=20

Hesham El-Rewini
Department of Computer Science and Engineering
Southern Methodist University
3145 Dyer Street, Dallas, TX 75205
Voice: (214) 768-3278,	FAX: (214) 768-3085
E-mail: rewini@engr.smu.edu


Publicity Chair
----------------
Moustafa Youssef
Department of Computer Science
University of Maryland at College Park,
College Park, MD 20742
Voice: (301) 405-0341,    FAX: (301) 405-6707
E-mail: moustafa@cs.umd.edu

------=_NextPart_000_01C7_01C52272.04DA2AF0
Content-Type: application/ms-tnef;
	name="winmail.dat"
Content-Disposition: attachment;
	filename="winmail.dat"
Content-Transfer-Encoding: base64

eJ8+Ig8WAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy
b3NvZnQgTWFpbC5Ob3RlADEIAQOQBgBICgAAEQAAAAsAAQ4AAAAAAgEKDgEAAAAYAAAAAAAAAAb2
H2WhXjNOmFCZq34NyNPCgAAAAwAUDgEAAAALAB8OAQAAAAIB+A8BAAAAEAAAAAb2H2WhXjNOmFCZ
q34NyNMCAfoPAQAAABAAAAAG9h9loV4zTphQmat+DcjTAwD+DwUAAAACAQkQAQAAALwIAAC4CAAA
RBAAAExaRnW9M78HAwAKAHJjcGcxMjXiMgNDdGV4BUEBAwH3TwqAAqQD4wIAY2gKwHPwZXQwIAcT
AoAP8wBQfwRWCFUHshHFDlEDARDHMvcGAAbDEcUzBEYQyRLbEdPbCO8J9zsYvw4wNRHCDGDOYwBQ
CwkBZDM2EVALpoggKE8IcCBhcBhBTmcIkAQgBpAgeQhgIAEYwGNlaXZlIG1odWx0BSBsH1AFoHBl
HkJvHpB0aAQAEsBG3FApCqIKhAqALSH/Iw+3JB8ktyE0ICYvJlBGC4C/B0ASwAdAAyACEAXAUB3g
fwSQELAl3yZQBrEd8ACQdcZtIGADoE1vYgMQH1BLCFAqEHUfoG5nKLZoQQJAcDovL3cssC4SYxEg
ZS4qYGJjLjEJgHUvfh6xAwBzLxhXQ18qwSsxMDUu7SxAbSi/MAphBCAKsQVAJyBxL08wA0lFMzAg
V95pGMAf0AQQKzEgAdAu4EkhNFNoBJBhdCqSYRx1aQfwB5AYYSwgS55hAHAd4AdANZBCZQDQjmg2
EDViNhBIYXcLcDE3cVVTQTHPLEVzYSwxLg3RLSJrLXR3Y20u4C8xvzvXSi4AH1AxcDMtMTY2EDQ4
O9BU1QWQaAMAYyeRUx3wAICdBbBzILAscDMUVENAMFs2EEAgUEBRAHBkBgBT/kNAICE6ITQ1sB8Q
AjAeoLc24BEQLDBhH0ED8HQ9AHcEEAmAQNEgCfAFsARgdfMEIAnAb3cgoB5wA6AgoO8fUAEAH0AY
UHAHgELRQOL/HeALUD6xH6A/ISBiBGAq4/cFoCtVRHF2M4ACIEZiBCAnQOJF8Tohcy41UW55+zEw
NQBjH6BHYiiBSPMAkL0qkWEoACtwCHAfUGUqEf53BJBEIUOxRWAFoAIwDsL/QOIYUEdEHdA3wEzB
SGRO1f9A8UhhH3A+ok7jC4ADUDEQ/HRyG3BMoyCgNRAd0CfgvUUwIETgS5I1IB3QY0pR/QQgZDUQ
TGBA4h72UyFKMv8d0EaSStELYFVyRsJKwR+g/weASoArMk9RQQBTcU3hH0C/AjBHcSeRC1EAMESh
czYQ/0WyR/NDwErQIHFIaESQAQD/HmECMANgLaBKUR9gSrIQ4Xsn4AnwZweRU3FFtACQZ38DoCBx
B0AEYFHAUqJVEHn/UcBM8AQgSGJLcUmRSoAhOv5UILJfACoWA/An418hHcHXKAIqYSgSZAQAY0Tg
AJD/SNFA4krwB5BYUkjRHvJC0f9kcgrAEOBlch+BIFEDoEf79xMhXwVKgE8FEB4wWKMoY38d0EzB
C4BJIA6wQQBFhWL9A2BhBIFpQkxgR88roEqAfyhUH2FekRjAHfAxYSCwZ/BoLXF1NpFaMWQlSSD9
RNFsStAuACtgAmAEADTg601xBbBrSoBUIBEs8CBi71uRTUFekQuAYwpAAQA2EL5iK3BpQ0SQBUA2
oG1pw181IFl0AhBSwiuROkF7J/45NGABkRFhEOBpwVIEQOI/UX1mMEcAGGF103U9TWn8ZGQf0E9D
QOIgEDTySMLvXwZVJSildZdERglY50DT/0kKdT5UEAUwHzJkcQhhVXH9A4FhXQBGYwTwNOAHgXU9
flBVMTEQHzJA4ghQTgMt/080Kz2DSlkiAHCBkhEwBRD/cPFA4lHAciAeQYYuTSJPL/9QPwIgfG5U
Ik3hAJBfIXHwl26EXwBx8GhJQWl6TtTfSvBzAE6wBvB8XkY1cB+Q/i01IB/QNQBGgnY4J5F6ifdm
kwEAkD9XQxEBoEg7ShX/jnVfI3U9B2KNs1HQC3FEIT9H9Zc/ddMIAHJwXpJkLf5oTrBbIBEwcFJI
wnZxPpH7biCI70UBIA3gCJBC0U6i/zagj1WdD5THM4VVET8ynEb/fF4qxShwEyFTcaRzmh910/5R
bjUgcVUmj8FL9IX/hKf/jcKe0ETSSGeUX3YAPsB2Qe9j9XvvnjUHgHJogWQBRwr/lv+jfoHxf48q
tlCSBJAfEP91PQZgY6AFEG53HzAA0ErQ9wQBoHghSVNvwHNQY8Eqkf5HNYCUEZlRKKUkvyWIaF//
d/IG8J7BadJA4m0WZHRtz/9u32/pNhBy8rVRGMACMMAD92rCv5IH0WK/InMANOFN0u5mTUGHkgWx
aghhJ4Fsgf0DYHMocEshhEIrcJwQQzH7P3AIYGyIcbgSBUBFsTOA/2jURHAf0EsgjxI+wcABIKDt
A2B1vpAsM3MsgVlQZdD1DqAuZYYuc1AFACowIHC/ykBIYS5AM4g0MkqAQSfh82jpczggNjExXQJF
gVHA90DhCxEzFGQIYJWRqfEKQN5tA6CHQ8pAYDtJKhEAIP+R8o1xuT8laihTBgC4GH1Qn2qwuQI/
sHmEZcMxNT2K3k5zAAaQUPYgcUFTsQUw+4eC1mVBtgEDINc8J8CuofxhLTWwarBK0ChU1mdK0J4x
PYo0dSoHCFAtQxDwfzOA0x8lPSrAEPAHgEEAWf8t8yE0fVAxQkZjIHErNNUC257SVkVFyBM+s0Ur
oJlR+wZxSNFVAwAfQBEQWiXW0fZ5C2BA8UIHQFbxBbCFcrcuAFowNhAxNEARUEhiAf01IHASwDOA
cgByQefnNyGeRDQgDiEBQCFDVm86IYk/sCg06QApIDQbAGAtMzk2ODYQJzJB5ljsPiE0RS0AwAMQ
P7DtLeRALPtgO0gHkOGx5PH/28F0gQCg4o/jn+Sl5cg0df8IYMNiKqERMJwQY3EFQOZ4+SE0MzHs
sH1AQwDVEVHQPwngNgGNcCfgMRBAYVggXjcOQDRW6+brMDTskDfz7RDs4DI37SCQ9O2T+3i8MDg0
Ze8WGMDyYkBc4f5yOgAfcC2Ctu/UwG/CvOGfStDfQ9+v4OttIWFmTGD74hFEAWbyr/O/tCbmf+eE
/1KBEtBcwV0AKEHBEdsFCQpx6vMwNzQOUOub/ZAx4+yRLuAtMDPsYO05DGf8NjcLQO68RMID8u/x
LTEKZP+ofREwAwANNP0/AwADAA80/T8DAAIBFDQBAAAAEAAAAE5JVEH5v7gBAKoAN9luAAACAX8A
AQAAADEAAAAwMDAwMDAwMDA2RjYxRjY1QTE1RTMzNEU5ODUwOTlBQjdFMERDOEQzNjQ1NDIyMDAA
AAAAAwAGEP79ipEDAAcQ0woAAAMAEBAAAAAAAwAREAAAAAAeAAgQAQAAAGUAAAAoT1VSQVBPTE9H
SUVTSUZZT1VSRUNFSVZFTVVMVElQTEVDT1BJRVNPRlRISVNDRlApLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tAAAAAEiV

------=_NextPart_000_01C7_01C52272.04DA2AF0
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

------=_NextPart_000_01C7_01C52272.04DA2AF0--




From mip4-bounces@ietf.org  Mon Mar  7 17:36:57 2005
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 RAA12186
	for <mip4-web-archive@ietf.org>; Mon, 7 Mar 2005 17:36:57 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D8Qsj-0000J8-7O
	for mip4-web-archive@ietf.org; Mon, 07 Mar 2005 17:39:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D8QoN-0007U7-Fk; Mon, 07 Mar 2005 17:34:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D8QoK-0007Ty-Vf
	for mip4@megatron.ietf.org; Mon, 07 Mar 2005 17:34:50 -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 RAA11961
	for <mip4@ietf.org>; Mon, 7 Mar 2005 17:34:46 -0500 (EST)
Received: from motgate3.mot.com ([144.189.100.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D8Qqb-0000Ff-DT
	for mip4@ietf.org; Mon, 07 Mar 2005 17:37:09 -0500
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate3.mot.com (8.12.11/Motgate3) with ESMTP id j27MgQTn013563
	for <mip4@ietf.org>; Mon, 7 Mar 2005 15:42:26 -0700 (MST)
Received: from il27exm03.cig.mot.com (il27exm03.cig.mot.com [10.17.193.4])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id j27MbLxQ016888
	for <mip4@ietf.org>; Mon, 7 Mar 2005 16:37:22 -0600 (CST)
Received: by il27exm03.cig.mot.com with Internet Mail Service (5.5.2657.72)
	id <D3VHM67K>; Mon, 7 Mar 2005 16:34:43 -0600
Message-ID: <EBF631554F9CD7118D0B00065BF34DCB1837949D@il27exm03.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'Kent Leung'" <kleung@cisco.com>
Subject: RE: [Mip4] Query regarding MN-AAA authenticator calculation.
Date: Mon, 7 Mar 2005 16:34:42 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Cc: "'Pete McCann'" <mccap@lucent.com>, Archana <archana_p@huawei.com>,
        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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8

Hi Kent, 

thanks for the email. The doc clearly says the method by which the MN gets a challenge is out of scope. If the MN is collocated (there is no FA), what is the meaning of Mobile-foreign challenge extension? 
We thought you would not need any challenge if the MN is collocated and registers with HA directly, did we miss anything?

Madjid

-----Original Message-----
From: Kent Leung [mailto:kleung@cisco.com] 
Sent: Friday, March 04, 2005 7:21 PM
To: Nakhjiri Madjid-MNAKHJI1
Cc: 'Pete McCann'; Archana; mip4@ietf.org
Subject: RE: [Mip4] Query regarding MN-AAA authenticator calculation.

Hi Madjid.  The rfc3012bis draft covers the CCoA mode.

>Based on local policy, a Mobile Node with co-located care-of-address
>    MAY include the Mobile-AAA Authentication extension in Registration
>    Request.  In this case, if the Mobile Node uses SPI value of CHAP_SPI
>    or HMAC_CHAP_SPI (section 8) in the MN-AAA Authentication extension,
>    Mobile Node MUST include the Mobile-Foreign Challenge extension prior
>    to the Mobile-AAA Authentication extension.  The mechanism used by
>    the Mobile Node to obtain the Challenge value is outside the scope of
>    this document.

Kent


At 03:52 PM 3/4/2005 -0600, Nakhjiri Madjid-MNAKHJI1 wrote:
>Hi,
>
>I have been meaning to respond to this as well. I agree there is no RADIUS 
>MD5. However, there is a problem with sending all the following
>
>Preceding Mobile IP data ||
>         Type, Subtype (if present), Length, SPI) ||
>        Least-order 237 bytes from Challenge
>
>Over RADIUS messages, since RADIUS packets can be at most 4K long and 
>attributes at most 253 bytes (if I understood this correctly), which means 
>you do have to calculate a hash of the data above before packing it over 
>RADIUS messaging, if you want the AAA server to do the same calculations. 
>If anybody has a number on the number of bytes the data above takes, I 
>would appreciate it??
>We tried to explain this in our draft on RADIUS support for MIP-AAA signaling.
>
>http://www.ietf.org/internet-drafts/draft-nakhjiri-radius-mip4-00.txt
>
>We ran into another problem with this and that was: the challenge is used 
>only in conjunctions with FAs and when the MN uses a CcoA and registers 
>through HA directly, there won't be any challenge to calculate
>
>MD5      (High-order byte from Challenge || Key ||
>         MD5(Preceding Mobile IP data ||
>         Type, Subtype (if present), Length, SPI) ||
>         Least-order 237 bytes from Challenge))
>
>Our proposal based on Charlie's suggestion (no mean to push the blame, 
>Charlie :) ) was to include zero octets whenever challenge data was needed 
>in that case.
>
>Any thoughts?
>
>Madjid
>-----Original Message-----
>From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of 
>Pete McCann
>Sent: Friday, February 25, 2005 9:48 AM
>To: Archana
>Cc: mip4@ietf.org
>Subject: [Mip4] Query regarding MN-AAA authenticator calculation.
>
>
>Hi, Archana,
>
>Archana writes:
>  > Hi
>  > According to RFC 3012, the MN-AAA authenticator is computed by 
> applying MD5
>  > on the following data
>  >
>  >       High-order byte from Challenge || Key ||
>  >       MD5(Preceding Mobile IP data ||
>  >       Type, Subtype (if present), Length, SPI) ||
>  >       Least-order 237 bytes from Challenge
>  >
>  > I have the following queries regarding the above computation. Any help in
>  > the clarifying them will be highly appreciated.
>  >
>  > 1. What is meant by High-order and Least order ?
>
>"High-order" means "most significant".  You can also interpret it as
>"leftmost" when looking at the encoding of the Challenge in a Mobile
>IP Extension.
>
>  > 2. How does the Radius MD5 algorithm differ in calculating the 
> Authenticator
>  > from a MD5 algorithm
>
>There is no special "Radius MD5" as far as I know.
>
>MD5 is specified in RFC3121.  It is a well-known hash function that
>processes the input and produces a 16 octet hash.
>
>The calculation shown above is compatible with existing RADIUS servers
>that are used for authenticating PPP/CHAP, i.e., the code used for
>PPP/CHAP can be re-used to compute the above authenticator, assuming
>that the FA can precompute the inner MD5 and send it in an
>Access-Request.
>
>-Pete
>
>  > Thanks in advance
>  > Archana
>
>
>--
>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/

--
      |           |                   Kent Leung
     :|:         :|:                  IP Mobility Development
    :|||:       :|||:                 Internet Technologies Division
   :|||||||:   :|||||||:              Voice: 408.526.5030
.:|||||||||:.:|||||||||:.             Fax:   408.525.1653
  c i s c o S y s t e m s             Email: kleung@cisco.com

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


From mip4-bounces@ietf.org  Tue Mar  8 01:48:35 2005
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 BAA29242
	for <mip4-web-archive@ietf.org>; Tue, 8 Mar 2005 01:48:35 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D8YYX-0004NC-S7
	for mip4-web-archive@ietf.org; Tue, 08 Mar 2005 01:51:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D8YTk-0002Wh-CP; Tue, 08 Mar 2005 01:46:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D8YTh-0002Wc-5P
	for mip4@megatron.ietf.org; Tue, 08 Mar 2005 01:46:02 -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 BAA29055
	for <mip4@ietf.org>; Tue, 8 Mar 2005 01:45:59 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D8YW1-0004JU-W5
	for mip4@ietf.org; Tue, 08 Mar 2005 01:48:26 -0500
Received: from sj-core-3.cisco.com (171.68.223.137)
	by sj-iport-4.cisco.com with ESMTP; 07 Mar 2005 22:46:09 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id j286jnTM017398;
	Mon, 7 Mar 2005 22:45:49 -0800 (PST)
Received: from kleung-w2k01.cisco.com (sjc-vpn4-189.cisco.com [10.21.80.189])
	by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with ESMTP id BCO35253;
	Mon, 7 Mar 2005 22:45:47 -0800 (PST)
Message-Id: <4.3.2.7.2.20050307145950.031eb958@mira-sjcm-2.cisco.com>
X-Sender: kleung@mira-sjcm-2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 07 Mar 2005 15:09:53 -0800
To: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
From: Kent Leung <kleung@cisco.com>
Subject: RE: [Mip4] Query regarding MN-AAA authenticator calculation.
In-Reply-To: <EBF631554F9CD7118D0B00065BF34DCB1837949D@il27exm03.cig.mot .com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba
Cc: "'Pete McCann'" <mccap@lucent.com>, Archana <archana_p@huawei.com>,
        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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 20f22c03b5c66958bff5ef54fcda6e48

Hi Madjid.

I think the documents are pretty straight-forward.

There are implementations in commercial products that support
collocated CoA mode which are available in accordance to existing
specifications.

Kent

At 04:34 PM 3/7/2005 -0600, Nakhjiri Madjid-MNAKHJI1 wrote:
>Hi Kent,
>
>thanks for the email. The doc clearly says the method by which the MN gets 
>a challenge is out of scope. If the MN is collocated (there is no FA), 
>what is the meaning of Mobile-foreign challenge extension?
>We thought you would not need any challenge if the MN is collocated and 
>registers with HA directly, did we miss anything?
>
>Madjid
>
>-----Original Message-----
>From: Kent Leung [mailto:kleung@cisco.com]
>Sent: Friday, March 04, 2005 7:21 PM
>To: Nakhjiri Madjid-MNAKHJI1
>Cc: 'Pete McCann'; Archana; mip4@ietf.org
>Subject: RE: [Mip4] Query regarding MN-AAA authenticator calculation.
>
>Hi Madjid.  The rfc3012bis draft covers the CCoA mode.
>
> >Based on local policy, a Mobile Node with co-located care-of-address
> >    MAY include the Mobile-AAA Authentication extension in Registration
> >    Request.  In this case, if the Mobile Node uses SPI value of CHAP_SPI
> >    or HMAC_CHAP_SPI (section 8) in the MN-AAA Authentication extension,
> >    Mobile Node MUST include the Mobile-Foreign Challenge extension prior
> >    to the Mobile-AAA Authentication extension.  The mechanism used by
> >    the Mobile Node to obtain the Challenge value is outside the scope of
> >    this document.
>
>Kent
>
>
>At 03:52 PM 3/4/2005 -0600, Nakhjiri Madjid-MNAKHJI1 wrote:
> >Hi,
> >
> >I have been meaning to respond to this as well. I agree there is no RADIUS
> >MD5. However, there is a problem with sending all the following
> >
> >Preceding Mobile IP data ||
> >         Type, Subtype (if present), Length, SPI) ||
> >        Least-order 237 bytes from Challenge
> >
> >Over RADIUS messages, since RADIUS packets can be at most 4K long and
> >attributes at most 253 bytes (if I understood this correctly), which means
> >you do have to calculate a hash of the data above before packing it over
> >RADIUS messaging, if you want the AAA server to do the same calculations.
> >If anybody has a number on the number of bytes the data above takes, I
> >would appreciate it??
> >We tried to explain this in our draft on RADIUS support for MIP-AAA 
> signaling.
> >
> >http://www.ietf.org/internet-drafts/draft-nakhjiri-radius-mip4-00.txt
> >
> >We ran into another problem with this and that was: the challenge is used
> >only in conjunctions with FAs and when the MN uses a CcoA and registers
> >through HA directly, there won't be any challenge to calculate
> >
> >MD5      (High-order byte from Challenge || Key ||
> >         MD5(Preceding Mobile IP data ||
> >         Type, Subtype (if present), Length, SPI) ||
> >         Least-order 237 bytes from Challenge))
> >
> >Our proposal based on Charlie's suggestion (no mean to push the blame,
> >Charlie :) ) was to include zero octets whenever challenge data was needed
> >in that case.
> >
> >Any thoughts?
> >
> >Madjid
> >-----Original Message-----
> >From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of
> >Pete McCann
> >Sent: Friday, February 25, 2005 9:48 AM
> >To: Archana
> >Cc: mip4@ietf.org
> >Subject: [Mip4] Query regarding MN-AAA authenticator calculation.
> >
> >
> >Hi, Archana,
> >
> >Archana writes:
> >  > Hi
> >  > According to RFC 3012, the MN-AAA authenticator is computed by
> > applying MD5
> >  > on the following data
> >  >
> >  >       High-order byte from Challenge || Key ||
> >  >       MD5(Preceding Mobile IP data ||
> >  >       Type, Subtype (if present), Length, SPI) ||
> >  >       Least-order 237 bytes from Challenge
> >  >
> >  > I have the following queries regarding the above computation. Any 
> help in
> >  > the clarifying them will be highly appreciated.
> >  >
> >  > 1. What is meant by High-order and Least order ?
> >
> >"High-order" means "most significant".  You can also interpret it as
> >"leftmost" when looking at the encoding of the Challenge in a Mobile
> >IP Extension.
> >
> >  > 2. How does the Radius MD5 algorithm differ in calculating the
> > Authenticator
> >  > from a MD5 algorithm
> >
> >There is no special "Radius MD5" as far as I know.
> >
> >MD5 is specified in RFC3121.  It is a well-known hash function that
> >processes the input and produces a 16 octet hash.
> >
> >The calculation shown above is compatible with existing RADIUS servers
> >that are used for authenticating PPP/CHAP, i.e., the code used for
> >PPP/CHAP can be re-used to compute the above authenticator, assuming
> >that the FA can precompute the inner MD5 and send it in an
> >Access-Request.
> >
> >-Pete
> >
> >  > Thanks in advance
> >  > Archana
> >
> >
> >--
> >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/
>
>--
>       |           |                   Kent Leung
>      :|:         :|:                  IP Mobility Development
>     :|||:       :|||:                 Internet Technologies Division
>    :|||||||:   :|||||||:              Voice: 408.526.5030
>.:|||||||||:.:|||||||||:.             Fax:   408.525.1653
>   c i s c o S y s t e m s             Email: kleung@cisco.com

--
      |           |                   Kent Leung
     :|:         :|:                  IP Mobility Development
    :|||:       :|||:                 Internet Technologies Division
   :|||||||:   :|||||||:              Voice: 408.526.5030
.:|||||||||:.:|||||||||:.             Fax:   408.525.1653
  c i s c o S y s t e m s             Email: kleung@cisco.com

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


From mip4-bounces@ietf.org  Wed Mar  9 01:00:19 2005
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 BAA02046
	for <mip4-web-archive@ietf.org>; Wed, 9 Mar 2005 01:00:19 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D8uHZ-0003DL-1y
	for mip4-web-archive@ietf.org; Wed, 09 Mar 2005 01:02:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D8uBV-0007aY-P1; Wed, 09 Mar 2005 00:56:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D8uBR-0007YZ-HW; Wed, 09 Mar 2005 00:56:39 -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 AAA01478;
	Wed, 9 Mar 2005 00:56:34 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D8uDy-00030g-SD; Wed, 09 Mar 2005 00:59:15 -0500
Received: from ISI.EDU (boreas.isi.edu [128.9.160.161])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j295ts615905;
	Tue, 8 Mar 2005 21:55:54 -0800 (PST)
Message-Id: <200503090555.j295ts615905@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Tue, 08 Mar 2005 21:55:54 -0800
X-ISI-4-39-6-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Cc: mip4@ietf.org, rfc-editor@rfc-editor.org
Subject: [Mip4] RFC 3957 on Authentication, Authorization,
	and Accounting (AAA) Registration Keys for Mobile IPv4
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3


--NextPart


A new Request for Comments is now available in online RFC libraries.


        RFC 3957

        Title:      Authentication, Authorization, and Accounting
                    (AAA) Registration Keys for Mobile IPv4
        Author(s):  C. Perkins, P. Calhoun
        Status:     Standards Track
        Date:       March 2005
        Mailbox:    charles.perkins@nokia.com, pcalhoun@airespace.com
        Pages:      27
        Characters: 63576
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-mip4-aaa-key-06.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3957.txt


Authentication, Authorization, and Accounting (AAA) servers, such as
RADIUS and DIAMETER, are in use within the Internet today to provide
authentication and authorization services for dial-up computers.
Mobile IP for IPv4 requires strong authentication between the mobile
node and its home agent.  When the mobile node shares an AAA Security
Association with its home AAA server, however, it is possible to use
that AAA Security Association to create derived Mobility Security
Associations between the mobile node and its home agent, and again
between the mobile node and the foreign agent currently offering
connectivity to the mobile node.  This document specifies extensions
to Mobile IP registration messages that can be used to create Mobility
Security Associations between the mobile node and its home agent,
and/or between the mobile node and a foreign agent.

This document is a product of the Mobility for IPv4 Working Group of
the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <050308215340.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc3957

--OtherAccess
Content-Type: Message/External-body; name="rfc3957.txt"; site="ftp.isi.edu";
	access-type="anon-ftp"; directory="in-notes"

Content-Type: text/plain
Content-ID: <050308215340.RFC@RFC-EDITOR.ORG>


--OtherAccess--
--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--NextPart--



From mip4-bounces@ietf.org  Fri Mar 11 14:09:43 2005
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 OAA26507
	for <mip4-web-archive@ietf.org>; Fri, 11 Mar 2005 14:09:42 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D9pZ7-0004SL-OJ
	for mip4-web-archive@ietf.org; Fri, 11 Mar 2005 14:12:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D9pU1-0002Fz-UU; Fri, 11 Mar 2005 14:07:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D9pTz-0002Am-OO; Fri, 11 Mar 2005 14:07:35 -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 OAA26393;
	Fri, 11 Mar 2005 14:07:34 -0500 (EST)
Received: from mx2.grc.nasa.gov ([128.156.11.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D9pX3-0004L6-AU; Fri, 11 Mar 2005 14:10:45 -0500
Received: from lombok-fi.grc.nasa.gov (seraph1.grc.nasa.gov [128.156.10.10])
	by mx2.grc.nasa.gov (Postfix) with ESMTP id 38952C249;
	Fri, 11 Mar 2005 14:07:21 -0500 (EST)
Received: from apataki.grc.nasa.gov (apataki.grc.nasa.gov [139.88.112.35])
	by lombok-fi.grc.nasa.gov (NASA GRC TCPD 8.12.10/8.12.10) with ESMTP id
	j2BJ7KRs005469; Fri, 11 Mar 2005 14:07:20 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by apataki.grc.nasa.gov (NASA GRC TCPD 8.13.1/8.13.1) with ESMTP id
	j2BJ7KQZ025033; Fri, 11 Mar 2005 14:07:20 -0500 (EST)
Received: from apataki.grc.nasa.gov ([127.0.0.1])by localhost (apataki.grc.n
	asa.gov [127.0.0.1]) (amavisd-new, port 10024)with ESMTP id 20498-20;
	Fri, 11 Mar 2005 14:07:20 -0500 (EST)
Received: from webmail.grc.nasa.gov (ragnarok.grc.nasa.gov [128.156.253.19])
	by apataki.grc.nasa.gov (NASA GRC TCPD 8.13.1/8.13.1) with ESMTP id
	j2BJ7Hq P024910;Fri, 11 Mar 2005 14:07:17 -0500 (EST)
Received: by webmail.grc.nasa.gov (Postfix, from userid 501)id DC23233800F; 
	Fri, 11 Mar 2005 14:07:17 -0500 (EST)
Received: from grc.nasa.gov (oh-northolmstead1-16-134.clvhoh.adelphia.net [6
	8.71.111.134])by webmail.grc.nasa.gov (Postfix) with ESMTPid
	4A18D33800D; F ri, 11 Mar 2005 14:07:15 -0500 (EST)
Message-ID: <4231EC62.3050800@grc.nasa.gov>
Date: Fri, 11 Mar 2005 14:07:14 -0500
From: ivancic <wivancic@grc.nasa.gov>
User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mip4@ietf.org, mip6@ietf.org, nemo <nemo@ietf.org>, hip@ietf.org
Content-Type: text/plain;
	charset=windows-1252;
	format=flowed
X-imss-version: 2.19
X-imss-result: Passed
X-imss-approveListMatch: *@*.nasa.gov
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Content-Transfer-Encoding: quoted-printable
Subject: [Mip4] NAT traversal and cellular network administrative filtering
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Content-Transfer-Encoding: quoted-printable

Please excuse the cross-post.

This week I sat in 4 IETF sessions that all where discussing very=20
similar, if not the same, problem of NAT traversal. HIP, MIP6 and NEMO=20
where generally discussing 6 to 4 tunneling issues and the need to=20
address NATs. MIP4 was not concerned with 6 to 4 tunneling, just NAT=20
traversal in general.

I have used Cisco=92s mobile networking MIP4 code with NAT traversal and=20
Cisco=92s (draft-thubert-nemo-ipv4-traversal-01 - expired) Doors 6 to 4=20
UDP-base tunneling NAT traversal code.

Both work, but here is something to be aware of. About 18 months ago we=20
noticed T-Mobile began administratively filtering traffic. The end=20
result is that traffic that does not originate from the T-Mobile network=20
gets blocked. They appear to be using ports to map the traffic. Thus,=20
and IP-in-IP tunnel gets blocked even though the initial traffic came=20
from within T-Mobile=92s network (no ports to map to for IP-in-IP=20
tunnels). UDP tunnels operate over this. That is why we used T-Mobile=92s=
=20
links for an mobile-ipv6 demonstration. The Doors implementation could=20
handle this.

(See: http://roland.grc.nasa.gov/~ivancic/ICNS2004_Demo/ICNS2004_Demo.htm=
)

Sprint and Verizon may have recently started administratively filtering=20
data =96 similar result as NATing even though you have unchanged public=20
address space. One way to cope with this is UDP-in-IP tunneling, the=20
same as with NAT traversal code.

NOTE: Depending on the implementation, you may have to force UDP=20
tunneling, because the address is not changing (CoA and actual address).=20
Thus, there is no easy way to auto-sense that you are getting=20
administratively filtered. I suspect this will break a lot of=20
implementations for NAT traversal =96 as this really isn=92t NAT traversa=
l,=20
but =93weak=94 firewall traversal.

I spoke to T-Mobile when this first started happening (actually found=20
the right person). They said that the filtering was put into place to=20
eliminate worms probing the networks. The filtering was done no so much=20
for security as to protect the valuable RF bandwidth. T-Mobile is GPRS=20
and you really get somewhere around 30 kbps in practice. Sprint and=20
Verizon are 1xRTT and get around 40 to 60 kbps in practice. Thus, worms=20
were starting to effect the usable bandwidth and QoS =96 or at least that=
=20
was the fear. Thus, I agree with their security implementations as the=20
reasoning appears valid.

See this URL for the T-Mobile problem:
http://roland.grc.nasa.gov/~ivancic/t-mobile=20
<http://roland.grc.nasa.gov/%7Eivancic/t-mobile>
http://roland.grc.nasa.gov/~ivancic/t-mobile/Letter_Customer_Service.pdf=20
<http://roland.grc.nasa.gov/%7Eivancic/t-mobile/Letter_Customer_Service.p=
df>=20

http://roland.grc.nasa.gov/~ivancic/t-mobile/administrative_filtering.pdf=
=20
<http://roland.grc.nasa.gov/%7Eivancic/t-mobile/administrative_filtering.=
pdf>=20


NATs breaks a lot of things. Security breaks the rest! J



Will Ivancic


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


From mip4-bounces@ietf.org  Sun Mar 13 05:02:36 2005
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 FAA24296
	for <mip4-web-archive@ietf.org>; Sun, 13 Mar 2005 05:02:36 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DAPz6-0001SZ-SK
	for mip4-web-archive@ietf.org; Sun, 13 Mar 2005 05:06:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DAPtQ-0005sT-Ur; Sun, 13 Mar 2005 05:00:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DAPtN-0005sI-SN; Sun, 13 Mar 2005 05:00:14 -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 FAA24213;
	Sun, 13 Mar 2005 05:00:11 -0500 (EST)
Received: from ns2.academica.fi ([217.64.177.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DAPwj-0001Qd-0d; Sun, 13 Mar 2005 05:03:44 -0500
Received: from [82.133.140.88] (ip82-133-140-88.adsl.academica.fi
	[82.133.140.88])
	by ns2.academica.fi (Postfix) with ESMTP id 9A89B257055;
	Sun, 13 Mar 2005 11:56:28 +0200 (EET)
Message-ID: <4234106D.1030301@iki.fi>
Date: Sun, 13 Mar 2005 12:05:33 +0200
From: Sami Vaarala <sami.vaarala@iki.fi>
User-Agent: Debian Thunderbird 1.0 (X11/20050116)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ivancic <wivancic@grc.nasa.gov>
Subject: Re: [Mip4] NAT traversal and cellular network administrative filtering
References: <4231EC62.3050800@grc.nasa.gov>
In-Reply-To: <4231EC62.3050800@grc.nasa.gov>
X-Enigmail-Version: 0.90.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: quoted-printable
Cc: nemo <nemo@ietf.org>, mip6@ietf.org, mip4@ietf.org, hip@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: sami.vaarala@iki.fi
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Content-Transfer-Encoding: quoted-printable

Hi,

 > [...]
> Sprint and Verizon may have recently started administratively filtering=
=20
> data =96 similar result as NATing even though you have unchanged public=
=20
> address space. One way to cope with this is UDP-in-IP tunneling, the=20
> same as with NAT traversal code.
>=20
> NOTE: Depending on the implementation, you may have to force UDP=20
> tunneling, because the address is not changing (CoA and actual address)=
.=20
> Thus, there is no easy way to auto-sense that you are getting=20
> administratively filtered. I suspect this will break a lot of=20
> implementations for NAT traversal =96 as this really isn=92t NAT traver=
sal,=20
> but =93weak=94 firewall traversal.

This is certainly an unfortunate development :(  Although networks with
such restrictions weren't common at the time, the 'F' (force UDP
tunnelling) flag was added to the MIP4 NAT-T spec specifically to
deal with such restrictions.  (However, I'm quite sure this level of
paranoia isn't enough, but it hasn't bitten us yet :-)

Since the 'F' flag is part of the core NAT-T spec, MIP4 should be OK
as long as mobile nodes expose the standard UDP forcing mechanism.
Indeed, at least a few vendors made UDP tunnelling the default simply
to avoid irritating blackhole situations which you point to.

> I spoke to T-Mobile when this first started happening (actually found=20
> the right person). They said that the filtering was put into place to=20
> eliminate worms probing the networks. The filtering was done no so much=
=20
> for security as to protect the valuable RF bandwidth. T-Mobile is GPRS=20
 > [...]

I'm curious - given the scenario where public addresses are used and
IP-IP doesn't work, why does IP-over-UDP work better?

With UDP encapsulation the MN RRQ/RRP process will establish firewall
state, while with IP-IP the state is established only after the first
(reverse tunneled) data packet.  Is this the problem?  I.e. the MN does
not have traffic to send but needs to be reachable from external
addresses (without corresponding IP-IP state)?  Or is it the case that
IP-IP state is not tracked as accurately as UDP state?

Best regards,

-Sami
--
Sami Vaarala
Chief Technology Officer
Stinghorn  (http://www.stinghorn.com)
Secure Virtualized Software

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


From mip4-bounces@ietf.org  Mon Mar 14 08:07:01 2005
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 IAA25110
	for <mip4-web-archive@ietf.org>; Mon, 14 Mar 2005 08:07:01 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DApLL-0000Hh-ET
	for mip4-web-archive@ietf.org; Mon, 14 Mar 2005 08:10:47 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DApH4-00079m-QD; Mon, 14 Mar 2005 08:06:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DApH3-00077w-Bn
	for mip4@megatron.ietf.org; Mon, 14 Mar 2005 08:06:21 -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 IAA25037
	for <mip4@ietf.org>; Mon, 14 Mar 2005 08:06:19 -0500 (EST)
Received: from motgate.mot.com ([129.188.136.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DApKf-0000Gk-0f
	for mip4@ietf.org; Mon, 14 Mar 2005 08:10:06 -0500
Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232])
	by motgate.mot.com (Motorola/Motgate) with ESMTP id j2ED68Gf026258;
	Mon, 14 Mar 2005 06:06:08 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id j2ED6CAD007657;
	Mon, 14 Mar 2005 07:06:13 -0600 (CST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 05C928637F6; Mon, 14 Mar 2005 14:06:06 +0100 (CET)
Message-ID: <42358C38.7050608@motorola.com>
Date: Mon, 14 Mar 2005 14:06:00 +0100
From: Alexandru Petrescu <Alexandru.Petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sami.vaarala@iki.fi
Subject: Re: [nemo] Re: [Mip4] NAT traversal and cellular network
	administrative filtering
References: <4231EC62.3050800@grc.nasa.gov> <4234106D.1030301@iki.fi>
In-Reply-To: <4234106D.1030301@iki.fi>
X-Enigmail-Version: 0.89.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: ivancic <wivancic@grc.nasa.gov>, 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>
Content-Type: multipart/mixed; boundary="===============1339326345=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1339326345==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigC95E9306AB34DC0A41C764F2"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigC95E9306AB34DC0A41C764F2
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Sami Vaarala wrote:
> I'm curious - given the scenario where public addresses are used and 
> IP-IP doesn't work, why does IP-over-UDP work better?

Sorry for intruding here...

It may be the case that operator forbids IP-IP because IP-IP has the
potential to deny the effectiveness of all other firewall filtering
rules that may be in place (rules acting on IP, not IP-in-IP - acting on
IP-in-IP requires more processing time which may be detrimental to
performance).

At the same time, operator may allow certain UDP tunneling to pass
through because that operator may have agreements with Content Providers
that are placed outside that operator's network.  "Content" may be video
streaming over UDP.  So operator assumes that UDP mms port 1755
(Microsoft Multimedia Streaming) should pass through, and keeps it open.

Just a potential explanation, and it's pure speculation, and it may be
far from the actual motivation of T-Mobile filtering rules.

Alex

--------------enigC95E9306AB34DC0A41C764F2
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFCNYw9MmC0w56zj54RAmASAKCCxVgKE1Ox3usN+w4nmlxRDeuCvwCg4jCp
gxQy3PoJDesF9YgbVrEtfg0=
=JHu7
-----END PGP SIGNATURE-----

--------------enigC95E9306AB34DC0A41C764F2--


--===============1339326345==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1339326345==--



From mip4-bounces@ietf.org  Mon Mar 14 09:01:44 2005
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 JAA02805
	for <mip4-web-archive@ietf.org>; Mon, 14 Mar 2005 09:01:44 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DAqCI-0002xm-UB
	for mip4-web-archive@ietf.org; Mon, 14 Mar 2005 09:05:32 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DAq7N-000205-Oz; Mon, 14 Mar 2005 09:00:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DAq7M-0001zu-Bp
	for mip4@megatron.ietf.org; Mon, 14 Mar 2005 09:00:24 -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 JAA02685
	for <mip4@ietf.org>; Mon, 14 Mar 2005 09:00:22 -0500 (EST)
Received: from ns2.academica.fi ([217.64.177.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DAqAy-0002sY-PE
	for mip4@ietf.org; Mon, 14 Mar 2005 09:04:10 -0500
Received: from [82.133.140.88] (ip82-133-140-88.adsl.academica.fi
	[82.133.140.88])
	by ns2.academica.fi (Postfix) with ESMTP id 6282F2570B7;
	Mon, 14 Mar 2005 15:56:39 +0200 (EET)
Message-ID: <42359A42.1090605@iki.fi>
Date: Mon, 14 Mar 2005 16:05:54 +0200
From: Sami Vaarala <sami.vaarala@iki.fi>
User-Agent: Debian Thunderbird 1.0 (X11/20050116)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Alexandru Petrescu <Alexandru.Petrescu@motorola.com>
Subject: Re: [nemo] Re: [Mip4] NAT traversal and cellular network
	administrative filtering
References: <4231EC62.3050800@grc.nasa.gov> <4234106D.1030301@iki.fi>
	<42358C38.7050608@motorola.com>
In-Reply-To: <42358C38.7050608@motorola.com>
X-Enigmail-Version: 0.90.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: 7bit
Cc: ivancic <wivancic@grc.nasa.gov>, mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: sami.vaarala@iki.fi
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit

Alexandru,

> It may be the case that operator forbids IP-IP because IP-IP has the
> potential to deny the effectiveness of all other firewall filtering
> rules that may be in place (rules acting on IP, not IP-in-IP - acting on
> IP-in-IP requires more processing time which may be detrimental to
> performance).

Not only processing time, but depending on the firewall architecture
it may be easy, hard, or impossible to peer into IP-IP (or IP-IP-IP,
IP-over-PPP-over-L2TP etc).In this sense, IP-IP may "escape" the normal
policy mechanism.

On the other hand you need a remote IP-IP endpoint for decapsulation,
and if you have that, you may escape the normal policy anyway by using
any of the dozen available tunneling tools out there.

> At the same time, operator may allow certain UDP tunneling to pass
> through because that operator may have agreements with Content Providers
> that are placed outside that operator's network.  "Content" may be video
> streaming over UDP.  So operator assumes that UDP mms port 1755
> (Microsoft Multimedia Streaming) should pass through, and keeps it open.
 >
> Just a potential explanation, and it's pure speculation, and it may be
> far from the actual motivation of T-Mobile filtering rules.

Right.  It may well be that operator X (in general) may want to block
IP-IP but is accidentally letting IP-over-UDP pass because of lacking
support in firewalls to prevent it.  Bypassing that policy using forced
UDP encapsulation is not necessarily very nice (from the operator's
viewpoint), but we lack the common tools to let the operator make this
policy decision.

However, in this case it seemed to me that the effects on normal MIP4
were a side-effect of a response to a perceived threat, not a deliberate
policy to block MIP4.

Best,

-Sami

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


From mip4-bounces@ietf.org  Mon Mar 14 13:32:14 2005
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 NAA05556
	for <mip4-web-archive@ietf.org>; Mon, 14 Mar 2005 13:32:14 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DAuQ8-0006xY-Uy
	for mip4-web-archive@ietf.org; Mon, 14 Mar 2005 13:36:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DAuJF-0003Lt-Tb; Mon, 14 Mar 2005 13:28:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DAj5l-0005LF-8M; Mon, 14 Mar 2005 01:30:17 -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 BAA23898;
	Mon, 14 Mar 2005 01:30:16 -0500 (EST)
From: john.loughney@nokia.com
Received: from mgw-x3.nokia.com ([131.228.20.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DAj9J-00015Z-FN; Mon, 14 Mar 2005 01:33:58 -0500
Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159])
	by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	j2E6U3o26371; Mon, 14 Mar 2005 08:30:05 +0200 (EET)
X-Scanned: Mon, 14 Mar 2005 08:29:12 +0200 Nokia Message Protector V1.3.34
	2004121512 - RELEASE
Received: (from root@localhost)
	by esdks004.ntc.nokia.com (8.12.9/8.12.9) id j2E6TCbJ002599;
	Mon, 14 Mar 2005 08:29:12 +0200
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks004.ntc.nokia.com 004O5NRH; Mon, 14 Mar 2005 08:29:11 EET
Received: from esebh002.NOE.Nokia.com (esebh002.ntc.nokia.com [172.21.138.77])
	by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	j2E6TAU15130; Mon, 14 Mar 2005 08:29:10 +0200 (EET)
Received: from esebe016.NOE.Nokia.com ([172.21.138.55]) by
	esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Mon, 14 Mar 2005 08:28:42 +0200
Received: from esebe105.NOE.Nokia.com ([172.21.143.53]) by
	esebe016.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Mon, 14 Mar 2005 08:28:41 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 14 Mar 2005 08:28:40 +0200
Message-ID: <FBA7FB88A51E804BA4A111CDFD2DE638603F2C@esebe105.NOE.Nokia.com>
Thread-Topic: [Mip6] NAT traversal and cellular network administrative
	filtering
thread-index: AcUnCEWFWpn9HASgRyqZhxMaMNcDnwBVqKhA
To: <wivancic@grc.nasa.gov>, <mip4@ietf.org>, <mip6@ietf.org>, <nemo@ietf.org>,
        <hip@ietf.org>
X-OriginalArrivalTime: 14 Mar 2005 06:28:41.0062 (UTC)
	FILETIME=[10502860:01C5285F]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 14 Mar 2005 13:28:57 -0500
Subject: [Mip4] RE: [Mip6] NAT traversal and cellular network administrative
	filtering
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Content-Transfer-Encoding: quoted-printable

Hi Will,

Just as an FYI - 3GPP2 is starting to work on firewall signaling:
http://www.ietf.org/internet-drafts/draft-bajko-nsis-fw-reqs-00.txt

This is meant so that terminals could selectively open or close firewall
pinholes, so this could potentially help with this issue.

John

> -----Original Message-----
> From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org]On Behalf Of
> ext ivancic
> Sent: 11 March, 2005 21:07
> To: mip4@ietf.org; mip6@ietf.org; nemo; hip@ietf.org
> Subject: [Mip6] NAT traversal and cellular network administrative
> filtering
>=20
>=20
> Please excuse the cross-post.
>=20
> This week I sat in 4 IETF sessions that all where discussing very=20
> similar, if not the same, problem of NAT traversal. HIP, MIP6=20
> and NEMO=20
> where generally discussing 6 to 4 tunneling issues and the need to=20
> address NATs. MIP4 was not concerned with 6 to 4 tunneling, just NAT=20
> traversal in general.
>=20
> I have used Cisco=92s mobile networking MIP4 code with NAT=20
> traversal and=20
> Cisco=92s (draft-thubert-nemo-ipv4-traversal-01 - expired) Doors 6 to =
4=20
> UDP-base tunneling NAT traversal code.
>=20
> Both work, but here is something to be aware of. About 18=20
> months ago we=20
> noticed T-Mobile began administratively filtering traffic. The end=20
> result is that traffic that does not originate from the=20
> T-Mobile network=20
> gets blocked. They appear to be using ports to map the traffic. Thus,=20
> and IP-in-IP tunnel gets blocked even though the initial traffic came=20
> from within T-Mobile=92s network (no ports to map to for IP-in-IP=20
> tunnels). UDP tunnels operate over this. That is why we used=20
> T-Mobile=92s=20
> links for an mobile-ipv6 demonstration. The Doors=20
> implementation could=20
> handle this.
>=20
> (See:=20
> http://roland.grc.nasa.gov/~ivancic/ICNS2004_Demo/ICNS2004_Demo.htm)
>=20
> Sprint and Verizon may have recently started administratively=20
> filtering=20
> data =96 similar result as NATing even though you have unchanged =
public=20
> address space. One way to cope with this is UDP-in-IP tunneling, the=20
> same as with NAT traversal code.
>=20
> NOTE: Depending on the implementation, you may have to force UDP=20
> tunneling, because the address is not changing (CoA and=20
> actual address).=20
> Thus, there is no easy way to auto-sense that you are getting=20
> administratively filtered. I suspect this will break a lot of=20
> implementations for NAT traversal =96 as this really isn=92t NAT=20
> traversal,=20
> but =93weak=94 firewall traversal.
>=20
> I spoke to T-Mobile when this first started happening (actually found=20
> the right person). They said that the filtering was put into place to=20
> eliminate worms probing the networks. The filtering was done=20
> no so much=20
> for security as to protect the valuable RF bandwidth.=20
> T-Mobile is GPRS=20
> and you really get somewhere around 30 kbps in practice. Sprint and=20
> Verizon are 1xRTT and get around 40 to 60 kbps in practice.=20
> Thus, worms=20
> were starting to effect the usable bandwidth and QoS =96 or at=20
> least that=20
> was the fear. Thus, I agree with their security=20
> implementations as the=20
> reasoning appears valid.
>=20
> See this URL for the T-Mobile problem:
> http://roland.grc.nasa.gov/~ivancic/t-mobile=20
> <http://roland.grc.nasa.gov/%7Eivancic/t-mobile>
> http://roland.grc.nasa.gov/~ivancic/t-mobile/Letter_Customer_S
ervice.pdf=20
<http://roland.grc.nasa.gov/%7Eivancic/t-mobile/Letter_Customer_Service.p=
df>=20

http://roland.grc.nasa.gov/~ivancic/t-mobile/administrative_filtering.pdf=
=20
<http://roland.grc.nasa.gov/%7Eivancic/t-mobile/administrative_filtering.=
pdf>=20


NATs breaks a lot of things. Security breaks the rest! J



Will Ivancic


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6

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


From mip4-bounces@ietf.org  Mon Mar 14 14:26:42 2005
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 OAA10259
	for <mip4-web-archive@ietf.org>; Mon, 14 Mar 2005 14:26:42 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DAvGp-0000pk-WE
	for mip4-web-archive@ietf.org; Mon, 14 Mar 2005 14:30:32 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DAvC5-0002XH-C3; Mon, 14 Mar 2005 14:25:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DAvC3-0002XC-QF
	for mip4@megatron.ietf.org; Mon, 14 Mar 2005 14:25:35 -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 OAA10068
	for <mip4@ietf.org>; Mon, 14 Mar 2005 14:25:34 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DAvFi-0000k5-2v
	for mip4@ietf.org; Mon, 14 Mar 2005 14:29:24 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-1.cisco.com with ESMTP; 14 Mar 2005 11:35:58 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.90,162,1107763200"; 
	d="scan'208"; a="619324040:sNHT24667216"
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j2EJJOqA000849
	for <mip4@ietf.org>; Mon, 14 Mar 2005 11:19:33 -0800 (PST)
Received: from kleung-w2k01.cisco.com
	(printer-sj-24-2-128-107-163-58.cisco.com [128.107.163.58])
	by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with ESMTP id BCV51900;
	Mon, 14 Mar 2005 11:19:29 -0800 (PST)
Message-Id: <4.3.2.7.2.20050314105333.02e960d0@mira-sjcm-2.cisco.com>
X-Sender: kleung@mira-sjcm-2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 14 Mar 2005 11:19:29 -0800
To: mip4@ietf.org
From: Kent Leung <kleung@cisco.com>
Subject: [Mip4] Issue #45; Seeking closure for on deregistration with
  FHAE
In-Reply-To: <4.3.2.7.2.20050112094941.02a37718@mira-sjcm-2.cisco.com>
References: <41E4A51B.10701@iprg.nokia.com>
	<4.3.2.7.2.20050111170556.03976dc0@mira-sjcm-2.cisco.com>
	<16861.48387.626374.280537@gargle.gargle.HOWL>
	<4.3.2.7.2.20050104153537.02b0e1a8@mira-sjcm-2.cisco.com>
	<4.3.2.7.2.20041210193834.02df4080@mira-sjcm-2.cisco.com>
	<4.3.2.7.2.20050104171617.02afa688@mira-sjcm-2.cisco.com>
	<16860.3652.719374.748>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca

Hi folks.

I'll try to summarize to see if we can reach some closure on this
issue.

This is the scenario when the problem is encountered.

MN is registered to the HA and moves to a new FA.  The new FA
is somehow misconfigured with the wrong SA with the MN's HA.
This invalid SA means that any registration between FA and HA
will not work because authentication fails.  Just to note that if the
SA is valid or if there is no SA, then everything works fine.

The issue arises when MN deregisters on the new FA which has
an invalid SA with the HA.  The deregistration will not work.

I've maintained that in this scenario, MN will not be able to register
as well.  So it's a configuration error that needs to be fixed as
the security relationship between FA and HA should be upheld.
The FA is configured with FHAE and always add extension to
the RRQ directed to the HA.  HA always authenticate FHAE.  The
security logic is clear, authentication of message exchange between
FA and HA are provided when FHAE service is configured or set.

Charlie feels that this deregistration has nothing to do with the FA
so should not be prevented due to some misconfiguration on the
FA or HA.  To get around the security relationship, check certain
fields such as lifetime, care-of address, D-bit, etc. on the FA
(to decide if FHAE should be added) and HA to figure out the
intent of the RRQ.

Since I get to summarize, I'll add one more point.  :)  I believe that
we should be fine with specification that is simple and clear
for security relationship between FA and HA.  And if real deployment
problem is encountered by operators/customers, _then_ we can
add more logic to support specific scenario.  For now, please just
keep it straightforward.  Thanks.

Kent
--
      |           |                   Kent Leung
     :|:         :|:                  IP Mobility Development
    :|||:       :|||:                 Internet Technologies Division
   :|||||||:   :|||||||:              Voice: 408.526.5030
.:|||||||||:.:|||||||||:.             Fax:   408.525.1653
  c i s c o S y s t e m s             Email: kleung@cisco.com

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


From mip4-bounces@ietf.org  Mon Mar 14 15:55:12 2005
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 PAA20458
	for <mip4-web-archive@ietf.org>; Mon, 14 Mar 2005 15:55:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DAweV-0004Yy-I0
	for mip4-web-archive@ietf.org; Mon, 14 Mar 2005 15:59:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DAwZo-0005PU-La; Mon, 14 Mar 2005 15:54:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DAwZn-0005PJ-3v
	for mip4@megatron.ietf.org; Mon, 14 Mar 2005 15:54:11 -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 PAA20318
	for <mip4@ietf.org>; Mon, 14 Mar 2005 15:54:09 -0500 (EST)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DAwdS-0004Wm-2U
	for mip4@ietf.org; Mon, 14 Mar 2005 15:58:00 -0500
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j2ELOKL16177;
	Mon, 14 Mar 2005 13:24:20 -0800
X-mProtect: <200503142124> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp14191.americas.nokia.com (172.18.141.91,
	claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdojZYri; Mon, 14 Mar 2005 13:24:18 PST
Message-ID: <4235F9DA.4020208@iprg.nokia.com>
Date: Mon, 14 Mar 2005 12:53:46 -0800
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Kent Leung <kleung@cisco.com>
Subject: Re: [Mip4] Issue #45; Seeking closure for on deregistration with FHAE
References: <41E4A51B.10701@iprg.nokia.com>	<4.3.2.7.2.20050111170556.03976dc0@mira-sjcm-2.cisco.com>	<16861.48387.626374.280537@gargle.gargle.HOWL>	<4.3.2.7.2.20050104153537.02b0e1a8@mira-sjcm-2.cisco.com>	<4.3.2.7.2.20041210193834.02df4080@mira-sjcm-2.c
In-Reply-To: <4.3.2.7.2.20050314105333.02e960d0@mira-sjcm-2.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Content-Transfer-Encoding: 7bit
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Content-Transfer-Encoding: 7bit


Hello Kent,

I feel that the summary has been worded to presuppose
a particular resolution.  I'll point out these places below.

Kent Leung wrote:

> MN is registered to the HA and moves to a new FA.  The new FA
> is somehow misconfigured with the wrong SA with the MN's HA.

Check.

> This invalid SA means that any registration between FA and HA
> will not work because authentication fails.

Not necessarily!  This outcome is what needs to be prevented.

> The issue arises when MN deregisters on the new FA which has
> an invalid SA with the HA.

Check.

>   The deregistration will not work.

Not necessarily!  This outcome is what needs to be prevented.

> I've maintained that in this scenario, MN will not be able to register
> as well.  So it's a configuration error that needs to be fixed as
> the security relationship between FA and HA should be upheld.

But it could well be that the MN doesn't want to register anyway.
It might just want to save some money by deregistering.

> The FA is configured with FHAE and always add extension to
> the RRQ directed to the HA.

Not necessarily!  This outcome is what needs to be prevented.

> HA always authenticate FHAE.  The
> security logic is clear, authentication of message exchange between
> FA and HA are provided when FHAE service is configured or set.

It's fine for the home agent to check the authentication.  What is not
fine, is for the home agent to fail to deregister the mobile node's previous
care-of address.

>
> Charlie feels that this deregistration has nothing to do with the FA
> so should not be prevented due to some misconfiguration on the
> FA or HA.

Check.

> To get around the security relationship, check certain
> fields such as lifetime, care-of address, D-bit, etc. on the FA
> (to decide if FHAE should be added) and HA to figure out the
> intent of the RRQ.

The words "get around" presuppose a particular outcome that we
are trying to avoid.

>
> Since I get to summarize, I'll add one more point.  :)  I believe that
> we should be fine with specification that is simple and clear
> for security relationship between FA and HA.

Check.  In particular, it should avoid this deregistration problem.

>   And if real deployment
> problem is encountered by operators/customers, _then_ we can
> add more logic to support specific scenario.

O.K.  Let's interpret this sentence to mean the following:

Allow the deregistration, and if real deployment shows any
problem with the FA when the mobile node wants to deregister,
then we will add more logic.

> For now, please just keep it straightforward.  Thanks.

Check.

Let's keep it straightforward.

Mobile node authenticates   ==>  home agent acts on its
verifiable request.

Regards,
Charlie P.



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


From mip4-bounces@ietf.org  Mon Mar 14 16:06:45 2005
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 QAA22131
	for <mip4-web-archive@ietf.org>; Mon, 14 Mar 2005 16:06:45 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DAwph-0005Jn-55
	for mip4-web-archive@ietf.org; Mon, 14 Mar 2005 16:10:37 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DAwlJ-000789-AQ; Mon, 14 Mar 2005 16:06:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DAwlI-000783-Jd
	for mip4@megatron.ietf.org; Mon, 14 Mar 2005 16:06:04 -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 QAA21970
	for <mip4@ietf.org>; Mon, 14 Mar 2005 16:06:02 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DAwoy-0005Gi-M3
	for mip4@ietf.org; Mon, 14 Mar 2005 16:09:54 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-1.cisco.com with ESMTP; 14 Mar 2005 13:22:13 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.90,162,1107763200"; 
	d="scan'208"; a="619374131:sNHT21952736"
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j2EL5oZX018070;
	Mon, 14 Mar 2005 13:05:52 -0800 (PST)
Received: from kleung-w2k01.cisco.com
	(printer-sj-24-2-128-107-163-58.cisco.com [128.107.163.58])
	by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with ESMTP id BCV66942;
	Mon, 14 Mar 2005 13:05:49 -0800 (PST)
Message-Id: <4.3.2.7.2.20050314130018.0300a830@mira-sjcm-2.cisco.com>
X-Sender: kleung@mira-sjcm-2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 14 Mar 2005 13:05:49 -0800
To: "Charles E. Perkins" <charliep@iprg.nokia.com>
From: Kent Leung <kleung@cisco.com>
Subject: Re: [Mip4] Issue #45; Seeking closure for on deregistration with FHAE
In-Reply-To: <4235F9DA.4020208@iprg.nokia.com>
References: <4.3.2.7.2.20050314105333.02e960d0@mira-sjcm-2.cisco.com>
	<41E4A51B.10701@iprg.nokia.com>
	<4.3.2.7.2.20050111170556.03976dc0@mira-sjcm-2.cisco.com>
	<16861.48387.626374.280537@gargle.gargle.HOWL>
	<4.3.2.7.2.20050104153537.02b0e1a8@mira-sjcm-2.cisco.com>
	<4.3.2.7.2.20041210193834.02df4080@mira-sjcm-2.c>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813

Hi Charlie.  Thanks.  We have now articulated the 2 different
approaches.  I believe we both agree on one thing - closure on
this issue.  :)

Kent

At 12:53 PM 3/14/2005 -0800, Charles E. Perkins wrote:

>Hello Kent,
>
>I feel that the summary has been worded to presuppose
>a particular resolution.  I'll point out these places below.
>
>Kent Leung wrote:
>
>>MN is registered to the HA and moves to a new FA.  The new FA
>>is somehow misconfigured with the wrong SA with the MN's HA.
>
>Check.
>
>>This invalid SA means that any registration between FA and HA
>>will not work because authentication fails.
>
>Not necessarily!  This outcome is what needs to be prevented.
>
>>The issue arises when MN deregisters on the new FA which has
>>an invalid SA with the HA.
>
>Check.
>
>>   The deregistration will not work.
>
>Not necessarily!  This outcome is what needs to be prevented.
>
>>I've maintained that in this scenario, MN will not be able to register
>>as well.  So it's a configuration error that needs to be fixed as
>>the security relationship between FA and HA should be upheld.
>
>But it could well be that the MN doesn't want to register anyway.
>It might just want to save some money by deregistering.
>
>>The FA is configured with FHAE and always add extension to
>>the RRQ directed to the HA.
>
>Not necessarily!  This outcome is what needs to be prevented.
>
>>HA always authenticate FHAE.  The
>>security logic is clear, authentication of message exchange between
>>FA and HA are provided when FHAE service is configured or set.
>
>It's fine for the home agent to check the authentication.  What is not
>fine, is for the home agent to fail to deregister the mobile node's previous
>care-of address.
>
>>
>>Charlie feels that this deregistration has nothing to do with the FA
>>so should not be prevented due to some misconfiguration on the
>>FA or HA.
>
>Check.
>
>>To get around the security relationship, check certain
>>fields such as lifetime, care-of address, D-bit, etc. on the FA
>>(to decide if FHAE should be added) and HA to figure out the
>>intent of the RRQ.
>
>The words "get around" presuppose a particular outcome that we
>are trying to avoid.
>
>>
>>Since I get to summarize, I'll add one more point.  :)  I believe that
>>we should be fine with specification that is simple and clear
>>for security relationship between FA and HA.
>
>Check.  In particular, it should avoid this deregistration problem.
>
>>   And if real deployment
>>problem is encountered by operators/customers, _then_ we can
>>add more logic to support specific scenario.
>
>O.K.  Let's interpret this sentence to mean the following:
>
>Allow the deregistration, and if real deployment shows any
>problem with the FA when the mobile node wants to deregister,
>then we will add more logic.
>
>>For now, please just keep it straightforward.  Thanks.
>
>Check.
>
>Let's keep it straightforward.
>
>Mobile node authenticates   ==>  home agent acts on its
>verifiable request.
>
>Regards,
>Charlie P.

--
      |           |                   Kent Leung
     :|:         :|:                  IP Mobility Development
    :|||:       :|||:                 Internet Technologies Division
   :|||||||:   :|||||||:              Voice: 408.526.5030
.:|||||||||:.:|||||||||:.             Fax:   408.525.1653
  c i s c o S y s t e m s             Email: kleung@cisco.com

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


From mip4-bounces@ietf.org  Mon Mar 14 17:39:14 2005
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 RAA28899
	for <mip4-web-archive@ietf.org>; Mon, 14 Mar 2005 17:39:14 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DAyHC-0000jp-TK
	for mip4-web-archive@ietf.org; Mon, 14 Mar 2005 17:43:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DAy9i-0002SZ-JL; Mon, 14 Mar 2005 17:35:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DAy9g-0002SU-S6
	for mip4@megatron.ietf.org; Mon, 14 Mar 2005 17:35:20 -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 RAA28564
	for <mip4@ietf.org>; Mon, 14 Mar 2005 17:35:18 -0500 (EST)
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DAyDM-0000Vz-Pt
	for mip4@ietf.org; Mon, 14 Mar 2005 17:39:11 -0500
Received: from alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id
	j2EMZ8vE002578
	for <mip4@ietf.org>; Mon, 14 Mar 2005 16:35:08 -0600 (CST)
Message-ID: <4236119C.16EA0352@alcatel.com>
Date: Mon, 14 Mar 2005 16:35:08 -0600
From: Tim Ozugur <tim.ozugur@alcatel.com>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: mip4@ietf.org
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by auds952.usa.alcatel.com
	id j2EMZ8vE002578
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Content-Transfer-Encoding: quoted-printable
Subject: [Mip4] Last CFP: Broadband Wireless Access Network on fixed network
	(BWAN 2005)
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Content-Transfer-Encoding: quoted-printable


(Apologies if you are receiving this message more than once)

******  Submission Deadline is March 15, 2005  ******

------------------------------------------------------------------
                        CALL FOR PAPERS

                 International Workshop on=20
Broadband Wireless Access Network on fixed network (BWAN 2005)
                   (http://www.bwan.org/)

                ORLANDO, FL - JUNE 12, 2005

co-located with International Conference on Multimedia Services=20
     Access Networks (MSAN '05: http://www.msan.org)

                   CO_SPONSORED BY IEEE

      ****** EXTENDED SUBMISSION DEADLINE: March 15, 2005 ******

-------------------------------------------------------------------

Scope:

Workshop: Broadband Wireless Access based on fixed Network=20
(xDSL, FTTx, etc ).=20

This Workshop will deal about complementary wireless broadband access
network based on wired network (xDSL, FTTx, etc), 3G/4G and also about
different techniques that can solved the tremendous challenges making
the sharing of each phone line accessible through wireless access with a
minimum guarantee of service for any connected user. In this workshop,
the challenges to develop a new low cost mobile or semi-mobile access
network with low powering unit will be explored and that may complement
UMTS.=20

The workshop is intended to present new architectures of fixed network
supporting mobility and/or nomadic features for wireless access (802.11,
WiMax,=85802.20=85.), the sharing of the network access, bandwidth sharin=
g
on radio access. (Single Hop, mesh,=85) and discuss about the perspective=
s
of shared access network enhanced with wireless extension based on
technologies such as WiFi,.. 802.16,.. 802.20, etc to maximize the
performance of the overall link and reduce the costs. Within the
framework of BWAN 2005, a new research field to prepare the next
generation of network access.=20

Topics of interest to this workshop include (but are not limited to)
performance studies and solutions (algorithms, protocols, architectures)
that tend to improve experience of users of services and applications
based on Internet.=20

Workshop Topics:

- New Architectures and technologies for broadband wireless=20
  access on fixed network(xDSL/FTTx,etc) with mobility features=20
- AAA (Authentification, Authorization, Accounting)=20
- Micro and macro mobility=20
- Medium access control (QoS, bandwidth sharing, fairness)=20
- End to end security and privacy issues on Mobile and/or nomadic=20
  Access Network=20
- Low cost and low power integrated xDSL/FTTx+WiFi modem with=20
  mobility enhancement=20
- Network cost performance and Business Models SLA-based services=20
- Radio extension such as 802.xy (WiFi, WiMax, etc)  Relating Topics:=20
- Modulation, coding and antennas (MIMO)=20
- Interference mitigation for multiple access=20
- Complementary solutions to UMTS=20
- Location-Based Services Applications=20
- Scalability issues to large number of sites=20
- Standard and regulations=20
- IPv6 impact=20
- Mesh extensions =20

Publication:=20

The submissions to be presented at the workshop will be selected,=20
based on their originality, technical merit and topical relevance=20
of their contents. All accepted papers will be published in the=20
conference proceedings that will be available at the workshop.=20

Important Dates:

- Submission Deadline: March 15, 2005=20
- Notification of acceptance: April 15, 2005=20
- Camera ready due: April 30, 2005=20
- Workshop date: June 12, 2005=20

Submission Guidelines:

We encourage full papers that present well-developed research results
(up to 4 pages double column, including figures and references), but
also short papers that are more speculative in nature, works in progress
and position papers are solicited.=20

Submitted papers must be unpublished and must not be currently under
review for any other publication. If you are unsure whether your work
falls within the scope of the conference, please contact the Program
Co-Chairs.=20

All paper submissions will be carefully reviewed by experts. The authors
of accepted papers must guarantee that their paper will be presented at
the workshop. At least one author of each accepted paper must be
registered for the workshop in order for that paper to appear in the
proceedings and to be scheduled for presentation.=20

All submissions should be sent electronically in Postscript or Adobe PDF
format. Detailed instructions about submissions are available at the
submission page. The electronic submission is available at EDAS.=20
_____________________________

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


From mip4-bounces@ietf.org  Mon Mar 14 19:22:51 2005
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 TAA10915
	for <mip4-web-archive@ietf.org>; Mon, 14 Mar 2005 19:22:51 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DAztV-0005z6-Ea
	for mip4-web-archive@ietf.org; Mon, 14 Mar 2005 19:26:45 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DAznp-0005Y8-TC; Mon, 14 Mar 2005 19:20:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DAzno-0005WL-02
	for mip4@megatron.ietf.org; Mon, 14 Mar 2005 19:20:52 -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 TAA10845
	for <mip4@ietf.org>; Mon, 14 Mar 2005 19:20:48 -0500 (EST)
Received: from av3-1-sn4.m-sp.skanova.net ([81.228.10.114])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DAzrU-0005xS-LO
	for mip4@ietf.org; Mon, 14 Mar 2005 19:24:43 -0500
Received: by av3-1-sn4.m-sp.skanova.net (Postfix, from userid 502)
	id 40B0137E59; Tue, 15 Mar 2005 01:20:33 +0100 (CET)
Received: from smtp2-1-sn4.m-sp.skanova.net (smtp2-1-sn4.m-sp.skanova.net
	[81.228.10.183]) by av3-1-sn4.m-sp.skanova.net (Postfix) with ESMTP
	id 3006237E48; Tue, 15 Mar 2005 01:20:33 +0100 (CET)
Received: from shiraz.levkowetz.com (h195n1fls311o871.telia.com
	[213.64.174.195])
	by smtp2-1-sn4.m-sp.skanova.net (Postfix) with ESMTP id 9975E37E43;
	Tue, 15 Mar 2005 01:20:32 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.44)
	id 1DAznU-0005if-Ak; Tue, 15 Mar 2005 01:20:32 +0100
Message-ID: <42362A4F.6000107@levkowetz.com>
Date: Tue, 15 Mar 2005 01:20:31 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Kent Leung <kleung@cisco.com>
Subject: Re: [Mip4] Issue #45; Seeking closure for on deregistration with FHAE
References: <4.3.2.7.2.20050314105333.02e960d0@mira-sjcm-2.cisco.com>	<41E4A51B.10701@iprg.nokia.com>	<4.3.2.7.2.20050111170556.03976dc0@mira-sjcm-2.cisco.com>	<16861.48387.626374.280537@gargle.gargle.HOWL>	<4.3.2.7.2.20050104153537.02b0e1a8@mira-sjcm-2.cisco.com>	<4.3.2.7.2.20041210193834.02df4080@mira-sjcm-2.c>
	<4.3.2.7.2.20050314130018.0300a830@mira-sjcm-2.cisco.com>
In-Reply-To: <4.3.2.7.2.20050314130018.0300a830@mira-sjcm-2.cisco.com>
X-Enigmail-Version: 0.89.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c54bc2f42d02429833c0ca4b8725abd7
Content-Transfer-Encoding: 7bit
Cc: mip4@ietf.org, "Charles E. Perkins" <charliep@iprg.nokia.com>
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3d7f2f6612d734db849efa86ea692407
Content-Transfer-Encoding: 7bit

Hi Kent and Charlie,

    Below I attach Pete's writeup of the different combinations of
SA selectors we could use to express your respective 2 approaches.
Could you please check through the writeup, and indicate your
preferred selectors in terms of the a) to f) selectors in
Pete's note, (or add other's, if there are more than a) to
f) to consider), so we are clear here on exactly what is being
proposed.  

With that in hand I'll ask the people on the list to please weigh
in with considered opinions, so we can (hopefully) find a consensus
position regarding this, and close it.


	Henrik


On 2005-03-14 10:05 pm Kent Leung said the following:
> Hi Charlie.  Thanks.  We have now articulated the 2 different
> approaches.  I believe we both agree on one thing - closure on
> this issue.  :)
> 
> Kent
> 
> At 12:53 PM 3/14/2005 -0800, Charles E. Perkins wrote:
[...]

>>>   And if real deployment
>>>problem is encountered by operators/customers, _then_ we can
>>>add more logic to support specific scenario.
>>
>>O.K.  Let's interpret this sentence to mean the following:
>>
>>Allow the deregistration, and if real deployment shows any
>>problem with the FA when the mobile node wants to deregister,
>>then we will add more logic.
>>
>>>For now, please just keep it straightforward.  Thanks.
>>
>>Check.
>>
>>Let's keep it straightforward.
>>
>>Mobile node authenticates   ==>  home agent acts on its
>>verifiable request.
>>


On 2005-02-25 10:47 pm Pete McCann said the following:
> Hi, Henrik,
> 
> I went back and reviewed the archives.  There are a lot of complex and
> thorny issues here.

[...]

> Whatever selectors we choose, it is important to understand that they
> serve two purposes:
> 
> 1. The sender of a message must find the right SA with which to
>    compute the authentication extension, or determine that an
>    authentication extension is not necessary.
> 
> 2. The receiver of a message must find the right SA with which to
>    check the authentication extension, or to determine that a message
>    without an authentication extension should be dropped.
> 
> Both ends of the selector computation must be done in exactly the same
> way to guarantee interoperability.
> 
> I would say that we need to choose some subset of the following fields
> as the selector set:
> 
> Possible Registration Request Selector Fields
>   a) The Source IP address
>   b) The Destination IP address
>   c) The Care-of Address
>   d) The Home Agent Address
>   e) The Lifetime field (or a bit which says whether or not it is zero)
>   f) The D bit (set to 1 if co-located CoA is being used)
> 
> Current status quo in the 3344bis text is, I believe, (c,d) with a
> proposal from Charlie to add (e).
> 
> Now, before we consider adding (e) I think we need to get our story
> straight on why (c,d) is such a good choice.  I have already pointed
> out the difficulty with (c,d) when using co-located CoA registering
> via the FA (which may or may not be using the 'R' bit).  A possible
> solution to this difficulty is to configure duplicate SAs at every
> possible legal value of (c,d) (i.e., all CoAs 'c' that could be used
> from a given FA) but this seems like way too much state and doesn't
> handle the case where more than one FA are deployed on a given link.
> 
> Another possible approach is to go back to using (a,d) instead of
> (c,d).  Of course, NATs can change the value of (a) and so this is why
> 3519 mandated (c,d) and a=c.  However, my understanding is that most
> current implementations (those that don't do 3519) actually use (a,d)
> even though this has been ambiguous ever since RFC 2002.  (a,d) seems
> to be the most straightforward approach and matches e.g., IPSec style
> processing.
> 
> I have proposed on the list a possible fix to the NAT issue where
> duplicate SAs are deployed at every possible legal value of (a,d)
> (i.e., all NATs that could be on the path between a given FA and HA)
> but this is a bit of an administrative overhead and doesn't handle the
> case where more than one FA is deployed behind the NAT.  Another
> possible approach is to bury our heads in the sand while uttering some
> wistful complaint about the never-ending stupidity of NATs.  I make it
> sound silly but it is actually my personally favored approach.
> 
> Now, as I understand it, part of the motivation for adding (e) was to
> handle the case when the selector was (c,d) and the CoA 'c' in
> question nevertheless did not belong to the current FA.  We really
> should nail down the question of whether we are going to revert back
> to (a,d) before debating whether to transition to (c,d,e).  Agreed?
> Furthermore, if we do transition to (c,d,e) wouldn't we sometimes want
> an FA-HA authentication extension for (c,d,0)?
> 
> In summary, I do not see a clear winner here.
> 
> 
> 
> Note that for Registration Replies our choices are a bit different as
> the CoA is not represented in the message:
> 
> Possible Registration Reply Selector Fields
>   w) The Source IP address
>   x) The Destination IP address
>   y) The Home Agent Address
>   z) The Lifetime field (or a bit which says whether or not it is zero)
> 
> I assume that most implementations today use (x,y).  Note that in this
> case the NAT issue boils down to modifying 'x' not 'w' because this is
> a response that trickles back through the NAT state set up by the
> request.  How does 3519 handle this case?  It seems like the HA has to
> find the SA based not on the contents of the outgoing message but
> based on the fact that it is a reply to a request and there is a
> corresponding SA pair in place that are bound together with
> administrative provisioning.  Processing on the FA seems similarly
> bound up in the outstanding Request state, at least in the case of
> multi-interfaced FAs with different security policies for each
> interface.
> 
[...]

> -Pete
> 
> 



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


From mip4-bounces@ietf.org  Tue Mar 15 10:09:28 2005
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 KAA24797
	for <mip4-web-archive@ietf.org>; Tue, 15 Mar 2005 10:09:28 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DBDjc-0002z0-TK
	for mip4-web-archive@ietf.org; Tue, 15 Mar 2005 10:13:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DBDZI-0007iB-Rz; Tue, 15 Mar 2005 10:02:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DBDZE-0007hX-P8
	for mip4@megatron.ietf.org; Tue, 15 Mar 2005 10:02:44 -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 KAA22707
	for <mip4@ietf.org>; Tue, 15 Mar 2005 10:02:42 -0500 (EST)
Received: from wproxy.gmail.com ([64.233.184.198])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DBDd4-0002L8-6x
	for mip4@ietf.org; Tue, 15 Mar 2005 10:06:43 -0500
Received: by wproxy.gmail.com with SMTP id 58so8232wri
	for <mip4@ietf.org>; Tue, 15 Mar 2005 07:02:31 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:reply-to:to:subject:date:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:x-mimeole:from;
	b=cmpzKx5R01ZoWtSRj9vaacNJAmj6Tx67hZ0BITOQQJ3BNqWXsTXDjPFfXxnGLLDRlAOxjhHBlWurBH78vJNs1pLq66QIvh+/IoaKmgGPILR0xRT1dhmezVsV3rRZBwtS+8yT3u4QTM8boiK76cdu54zWSkaEQiZZyElcHDYQI6o=
Received: by 10.54.27.49 with SMTP id a49mr158869wra;
	Tue, 15 Mar 2005 07:02:30 -0800 (PST)
Received: from deniohome ([200.241.201.232])
	by mx.gmail.com with ESMTP id d6sm778545wra.2005.03.15.07.02.29;
	Tue, 15 Mar 2005 07:02:30 -0800 (PST)
Message-ID: <004601c52970$0268dd70$7c00020a@deniohome>
To: <mip4@ietf.org>
Date: Tue, 15 Mar 2005 12:02:28 -0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
From: Denio Mariz <deniomariz@gmail.com>
X-Spam-Score: 2.3 (++)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit
Subject: [Mip4] Summary for MIP Open Issues
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Denio Mariz <denio@gprt.ufpe.br>
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 2.3 (++)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit

Hello:

I'm trying to become updated with the evolutions, known problems and
solutions for MIv4 since RFC 3344 in Aug 2002. I intend to write a
summary with these questions and, despite I think that the best way to
carry this out is starting reading the current Internet-Drafts from
MIP4 Workgroup charter, I would like to know if anyone already did
something similar.

Or, maybe can anyone point any good paper or link with a overview or a
discussion.

TIA,

Denio Mariz


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


From mip4-bounces@ietf.org  Tue Mar 15 13:07:25 2005
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 NAA29525
	for <mip4-web-archive@ietf.org>; Tue, 15 Mar 2005 13:07:24 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DBGJL-0007xS-BQ
	for mip4-web-archive@ietf.org; Tue, 15 Mar 2005 12:58:32 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DBGCz-0006ug-NX; Tue, 15 Mar 2005 12:51:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DBGCv-0006pP-KK
	for mip4@megatron.ietf.org; Tue, 15 Mar 2005 12:51:55 -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 MAA28346
	for <mip4@ietf.org>; Tue, 15 Mar 2005 12:51:46 -0500 (EST)
Received: from ftpbox.mot.com ([129.188.136.101])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DBG26-0006Gl-09
	for mip4@ietf.org; Tue, 15 Mar 2005 12:40:43 -0500
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234])
	by ftpbox.mot.com (Motorola/Ftpbox) with ESMTP id j2FHa7PP015810;
	Tue, 15 Mar 2005 10:36:07 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id j2FHaknJ028216;
	Tue, 15 Mar 2005 11:36:47 -0600 (CST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 6BFE3865980; Tue, 15 Mar 2005 18:36:05 +0100 (CET)
Message-ID: <42371CFF.9040003@motorola.com>
Date: Tue, 15 Mar 2005 18:35:59 +0100
From: Alexandru Petrescu <Alexandru.Petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Denio Mariz <denio@gprt.ufpe.br>
Subject: Re: [Mip4] Summary for MIP Open Issues
References: <004601c52970$0268dd70$7c00020a@deniohome>
In-Reply-To: <004601c52970$0268dd70$7c00020a@deniohome>
X-Enigmail-Version: 0.89.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
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>
Content-Type: multipart/mixed; boundary="===============1166818481=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1166818481==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig93F72288D6DF96E7C42F9850"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig93F72288D6DF96E7C42F9850
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Denio Mariz wrote:
> I'm trying to become updated with the evolutions, known problems and 
> solutions for MIv4 since RFC 3344 in Aug 2002. I intend to write a 
> summary with these questions and, despite I think that the best way
> to carry this out is starting reading the current Internet-Drafts
> from MIP4 Workgroup charter, I would like to know if anyone already
> did something similar.
> 
> Or, maybe can anyone point any good paper or link with a overview or
> a discussion.

Denio, do you attend the IETF meetings?  Do you know about IETF?

What you intend to do is usually done by the WG Chairs, usually for
every meeting i.e. about three times per year, here's an example:
http://www.mip4.org/ietf62/agenda.pyht (see section 2 "Document Status").

Of course, usually nobody would stop you from doing the same thing but
the immediate question that comes up is why would you do so?  For your
personal elightenment?  Or do you look for implementing bleeding edge
features?  Or do you write some analysis report?

Note I'm not a regular poster to this list and this is just a sidenote.
  For definitive info on this stuff please talk to Chairs of this WG.

Thanks,

Alex

--------------enig93F72288D6DF96E7C42F9850
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFCNx0FMmC0w56zj54RAgfrAKCX9g22/0Fpeq8UkCnXkXhLX4mH5wCgnMJL
BDbj2IlmYaiTeB4zfd0EapI=
=rtDJ
-----END PGP SIGNATURE-----

--------------enig93F72288D6DF96E7C42F9850--


--===============1166818481==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1166818481==--



From mip4-bounces@ietf.org  Tue Mar 15 14:12:32 2005
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 OAA07475
	for <mip4-web-archive@ietf.org>; Tue, 15 Mar 2005 14:12:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DBHJj-0005la-PE
	for mip4-web-archive@ietf.org; Tue, 15 Mar 2005 14:02:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DBHDJ-0005a2-Ob; Tue, 15 Mar 2005 13:56:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DBHDI-0005ZM-4n
	for mip4@megatron.ietf.org; Tue, 15 Mar 2005 13:56:20 -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 NAA05425
	for <mip4@ietf.org>; Tue, 15 Mar 2005 13:56:14 -0500 (EST)
Received: from wproxy.gmail.com ([64.233.184.196])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DBH2Z-0003rI-KZ
	for mip4@ietf.org; Tue, 15 Mar 2005 13:45:15 -0500
Received: by wproxy.gmail.com with SMTP id 70so2165272wra
	for <mip4@ietf.org>; Tue, 15 Mar 2005 10:41:06 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
	b=FHls3Y/SXd6+QcSPdKi7SrCyAE3DlYn0y2yQyH4dBV7IfCDuJN0s4uL7EjY64+PgTc7TJHQtp30zHe2q4KmdvztGumfneZ4nN3wQGh6eKSAkCDwFFc4Xj/6Y7E7FIvpPokt95eRB/Lx1QZWLu7eMCrYtFw57/XEd9zwfHsFdMPs=
Received: by 10.54.7.54 with SMTP id 54mr12483wrg;
	Tue, 15 Mar 2005 10:41:06 -0800 (PST)
Received: by 10.54.37.67 with HTTP; Tue, 15 Mar 2005 10:41:06 -0800 (PST)
Message-ID: <dde9f3ed050315104125cb6602@mail.gmail.com>
Date: Tue, 15 Mar 2005 15:41:06 -0300
From: Denio Mariz <deniomariz@gmail.com>
To: Alexandru Petrescu <Alexandru.Petrescu@motorola.com>
Subject: Re: [Mip4] Summary for MIP Open Issues
In-Reply-To: <42371CFF.9040003@motorola.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
References: <004601c52970$0268dd70$7c00020a@deniohome>
	<42371CFF.9040003@motorola.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: denio@gprt.ufpe.br
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: 7bit

Hi Alex.
Thanks for your reply.

No. I don't attend the IETF meetings, because it is expensive to me (I
live at Brazil) :-)

I'm a teacher and last time I have taught on Mobile IP was soon after RFC 3344. 
Currently I'm going to teach again MIPv4 and I'm just looking for some
updates, because I know that some open issues present at that time
have already some solutions.

Thank you for your hint about WG meeting documents.

Best regards,

Denio.


On Tue, 15 Mar 2005 18:35:59 +0100, Alexandru Petrescu
<Alexandru.Petrescu@motorola.com> wrote:
> Denio Mariz wrote:
> > I'm trying to become updated with the evolutions, known problems and
> > solutions for MIv4 since RFC 3344 in Aug 2002. I intend to write a
> > summary with these questions and, despite I think that the best way
> > to carry this out is starting reading the current Internet-Drafts
> > from MIP4 Workgroup charter, I would like to know if anyone already
> > did something similar.
> >
> > Or, maybe can anyone point any good paper or link with a overview or
> > a discussion.
> 
> Denio, do you attend the IETF meetings?  Do you know about IETF?
> 
> What you intend to do is usually done by the WG Chairs, usually for
> every meeting i.e. about three times per year, here's an example:
> http://www.mip4.org/ietf62/agenda.pyht (see section 2 "Document Status").
> 
> Of course, usually nobody would stop you from doing the same thing but
> the immediate question that comes up is why would you do so?  For your
> personal elightenment?  Or do you look for implementing bleeding edge
> features?  Or do you write some analysis report?
> 
> Note I'm not a regular poster to this list and this is just a sidenote.
>   For definitive info on this stuff please talk to Chairs of this WG.
> 
> Thanks,
> 
> Alex
> 
> 
>

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


From mip4-bounces@ietf.org  Wed Mar 16 08:10:36 2005
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 IAA16875
	for <mip4-web-archive@ietf.org>; Wed, 16 Mar 2005 08:10:36 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DBYMK-0003EU-Gg
	for mip4-web-archive@ietf.org; Wed, 16 Mar 2005 08:14:48 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DBXz1-0002GG-BE; Wed, 16 Mar 2005 07:50:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DBXyz-0002B3-2p
	for mip4@megatron.ietf.org; Wed, 16 Mar 2005 07:50:42 -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 HAA14739
	for <mip4@ietf.org>; Wed, 16 Mar 2005 07:50:15 -0500 (EST)
Received: from carrierpigeon.cs.umd.edu ([128.8.129.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DBY2c-0001wZ-EP
	for mip4@ietf.org; Wed, 16 Mar 2005 07:54:26 -0500
Received: from MINDLAP2 (newvpn11.cs.umd.edu [172.16.2.11])
	(authenticated bits=0)
	by carrierpigeon.cs.umd.edu (8.12.10/8.12.5) with ESMTP id
	j2GCnvnD018391
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <mip4@ietf.org>; Wed, 16 Mar 2005 07:50:06 -0500 (EST)
Message-Id: <200503161250.j2GCnvnD018391@carrierpigeon.cs.umd.edu>
From: "Moustafa Youssef" <moustafa@cs.umd.edu>
To: <mip4@ietf.org>
Date: Wed, 16 Mar 2005 07:49:28 -0500
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0018_01C529FC.BF0A5530"
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MS-TNEF-Correlator: 0000000006F61F65A15E334E985099AB7E0DC8D3245C2200
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba
Subject: [Mip4] IMPORTANT: WIRELESSCOM extension March 31 -- Symposium on
	Mobile Computing, 2005
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ee80a2074afbfe28d15369f4e74e579d

This is a multi-part message in MIME format.

------=_NextPart_000_0018_01C529FC.BF0A5530
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

(Our apologies if you receive multiple copies of this CFP)

Due to the large number of requests, the submission deadline has been
extended to March 31.
-------------------------------------------------------------
                    Call for Papers
              Symposium on Mobile Computing
  http://www.csee.umbc.edu/~younis/WC_MobCom05.htm
                       as part of 
                IEEE WirelessCom 2005
Sheraton Maui Resort, Kaanapali Beach, Maui, Hawaii, USA
           http://sa1.sice.umkc.edu/wc05/ 
                   June 13-16, 2005
  Technical Sponsorship: IEEE TCCC, TCPC, and SSCTC


Recent years have witnessed an enormous growth in the development and
applications of mobile computing environments and devices. Many
practitioners envision a future empowered with context and location aware
computation and communication infrastructure that allow users to access data
and receive service at any place and any time. Compared to conventional
platforms, the mobility of computing nodes introduces many challenges to the
design of almost all systems components. 

This symposium will foster a forum for discussing and presenting recent
research results on mobile computer systems. Original papers are invited in
the broader area of mobile computing. Papers must report high-quality and
previously unpublished work. Topics of interest include, but are not limited
to, the following:

* Architecture and infrastructure support	
* Middleware and operating systems services
* Development platforms and environments
* Adaptive resource management schemes
* Pervasive and Context-aware Computing
* Performance metrics and studies
* Power aware computation and communication
* Data consistency and synchronization protocols
* Fault-tolerant architectural and operation models
* Wearable computing devices and systems
* Time constrained mobile systems
* Robust ad-hoc networking techniques
* Efficient localization techniques
* Wireless sensor networks
* Mobile peer to peer systems
* Quality of service provisioning
* Context-conscious computing
* Web caching and services
* Emerging applications and systems
* Mobile agents
* Mobile commerce
* Security and privacy issues


Submission Guidelines
---------------------
Original papers are solicited and must represent high-quality and previously
unpublished work, not currently under review by another conference or
journal. Prospective authors should submit their paper electronically
through https://msrcmt.research.microsoft.com/WirelessCom2005. All papers
are limited to 6 pages in standard IEEE double-column format. 

Important Dates
---------------
Paper Submission Deadline: 	March 31, 2005 (extended)
Notification of Acceptance: 	April 22, 2005
Camera-Ready Papers: 	May 1, 2005

Symposium Co-Chairs
-------------------
Mohamed Younis
Department of Computer Science and Electrical Engineering University of
Maryland Baltimore County, 1000 Hilltop Circle, Baltimore, MD 21250
Voice: (410) 455-3968,    FAX: (410) 455-3968
E-mail: younis@csee.umbc.edu 

Hesham El-Rewini
Department of Computer Science and Engineering
Southern Methodist University
3145 Dyer Street, Dallas, TX 75205
Voice: (214) 768-3278,	FAX: (214) 768-3085
E-mail: rewini@engr.smu.edu


Publicity Chair
----------------
Moustafa Youssef
Department of Computer Science
University of Maryland at College Park,
College Park, MD 20742
Voice: (301) 405-0341,    FAX: (301) 405-6707
E-mail: moustafa@cs.umd.edu

------=_NextPart_000_0018_01C529FC.BF0A5530
Content-Type: application/ms-tnef;
	name="winmail.dat"
Content-Disposition: attachment;
	filename="winmail.dat"
Content-Transfer-Encoding: base64

eJ8+IjgMAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy
b3NvZnQgTWFpbC5Ob3RlADEIAQOQBgB8CgAAEQAAAAsAAQ4AAAAAAgEKDgEAAAAYAAAAAAAAAAb2
H2WhXjNOmFCZq34NyNPCgAAAAwAUDgEAAAALAB8OAQAAAAIB+A8BAAAAEAAAAAb2H2WhXjNOmFCZ
q34NyNMCAfoPAQAAABAAAAAG9h9loV4zTphQmat+DcjTAwD+DwUAAAACAQkQAQAAAO8IAADrCAAA
BhAAAExaRnV+6uIiAwAKAHJjcGcxMjXiMgNDdGV4BUEBAwH3/wqAAqQD5AcTAoAP8wBQBFY/CFUH
shElDlEDAQIAY2jhCsBzZXQyBgAGwxEl9jMERhO3MBIsETMI7wn3tjsYHw4wNREiDGBjAFAzCwkB
ZDM2FlALpiAook8IcCBhcBehZwiQUwQgBpAgeQhgIBggYwBlaXZlIG11bFp0BSBsHrAFoHAdom8Z
HfB0aAQAEiBGUCm3CqIKhAqARApQH/BvH/GTHrALYHJnHrBudQbQFxKBH9EYIHEKUHN0c0IsIbNz
dWJtBAFpxQIgIAEAYWRsC4AesO8T4AQgIpAJ8CAOwQnwAQAaZCGCTQrAE9AgMzH6LiCULSdvKH8p
jyonIJT2ICufK8BDB0ADIAIQBcD2UB1ABJBzKz8rwQaxHVCPAJAicB/AA6BNb2IDEJcesAhQLyB1
HwBuZy3GgmgCQHA6Ly93McAkLmMUEGUuInFjLjEJgHUvfh4RAwBzLxhXQ18v0TBBMDUu/TFQbS3P
NRolMQqxBUAf0RM0XzUTSUU4QCBXae8YIB8wBBAwQSAB0DPwIJQyUyHQcmEhkC+xYXWeaQfwB5AX
wSOAS2EAcPcdQAdAOqBCJKAT0COAOnIxI4BIYXcLcDyBVVPmQTbfMVVzYSbgDdEyMtJrMoR3YzPw
LzbPQOcGSjMQHrAxMy0xNlcjgDlIQOBUBZBoAwBj3wdABgAdUACABbBzIBAxgLk4JFRDRUAjgEUw
UEVh4wBwJiBTU0NFMCCaIJT/OsAecAIwHgAkoBQAJREeof0D8HQk8AQQJhEDkQnwBbDNBGB1BCAJ
wG93IAAd0N8DoCHCAQAeoBewcAeAR+H/RfIdQAtQQ8EfAEQxH8IEYO8v8wWgMGVJgXY4kAIgS3JP
BCBF8ksBPzFzLiZhbvZ5NkA6EGMfAExyLZFOA70kQ2EtEDCACHAesGUvIf53BJAmEUjBJrAFoAIw
DsL/RfIXsExUHTA80FHRTXRT5f9GAU1xHtBDslPzC4ADUCUw/HRyGtBRsyAAOiAdMCzw/UpAIEnw
UKIhkQDQT2EEIP5kOiBRcEXyHlZYMU9CHTD/S6JP4QtgWoJL0k/RHwAHgP9PkDBCVGEmI1LxHqAC
MCRR/0PhC1EAMEmxI3VNA0jQT+D/H9FNeEmgAQAdwQIwA2AysP9PYR7AT8IT0SzwCfAiMFhj+0rE
AJBnA6Af0QdABGAjUPtXsiPQeSNQUgAEIE1yUIH3TqFPkCCaVCASZBAvJgPwvyzzZDEdIS0SL3Et
ImQEAP5jSfAAkE3hRfJQAAeQXWL/TeEeUkfhaYImg2mBHuEfsd8DoE0LEoFkFU+QTwUQHZD/XbMt
cx0wUdELgE4wDrAmIP1KlWIDYCSwZ5IYIFFwTN//MLBPkC1kHsFjoRggHVA2cfEgEGdoLSMgO6Ff
QWk1+04wSeFsT+AzEDBwAmAEANch0FKBBbBrT5BUH3EyAN8fwmChUlFjoQuAYwpAAQD9I4BiMIBu
U0mgBUAk0CQQv27iIZAjhAIQV9IwoTogmv4qEMET0G7RVxRF8laNI+AfTBAXwQyCQFV6oE1pZP8k
wAfQVGJF8h9wOgJN0mQW91o1LbV6oERLGV33ReNOGv96R1kgBTAekmmBCGFagQOBfmEiMEtzBPAh
0AeBekZQv1pBJTAekkXyCFBTEy1URP8wTYaTXjIAcITiFCAFEHYB/0XyI1B3MB2hhjdSMlQ/VU//
AiCAl1kyUvEAkGQxdwBzlMtkEHcAaE5RaXpT5FAAb3gQU8AG8ICHRjqAHvAt/yGQHzA6EEuSethD
4X65a6P7AQCRyFdIIQGgTUtPJZAF/2QzekYHYo9DVuALcSYRTQWPl+0IAHeAY6JkLWhTwP8iUBQg
dWJN0nsRQ6EjInpG/kUBIA3gCJBH4VOyJNCQ5f+c3zh3WiFEQpwWgIcv1S2A7xKBIZGi85ftUXNF
H9FaNv+RUVEEiNmHlo9SnjBJ4k13v5V4fWBD0HrhaQWAHkUHgP8iIGjzTBqXr6JnhUGDSS/V/1Wi
BJAecHpGBmBosAUQc4e/HpAA0E/gBAGdRyCaUyP4/kc6kJUxJOEttSovKvhtb/98kgbwniFu4kXy
ciZphHLf/3PvdPkjgHgCsMEYIAIwu3P3b9K7AgfRYrqSeBA58VLi7mZSUYoCBbFqCGFdsXGR/QNg
cy2AUDGHIjCAm+BIQftEgAhgbIrhI/IFQCHBOJD/beQloB8wUDCQokPRu3EgAO0DYHW6ADFDczGR
XmAmkPUOoC5qli4kEAUAL0Af0L/FsE1xM1A4mDlCT5BBLPHzbfl4SCA2NkFiEkqRI1D3RfELETgk
ZAhglkGnkQpA3m0DoImzxbBlS0kvIQAg/5MSjwG0ryraLWMGACP4gRD/JLREwH0zJnZClBzgJbYg
hd5OeBAGkFYGH9FBWMEFMJuJ8tHVQbFxAyAyMkKa8yzQq2FhLTrAJLBP4C1kP9HXT+DStbK7LxcI
UC1D/xPgOJDOjyqtL9AT4AeAJiD+WTMDIPVygDZhS3Mf0TBEt9BynjJbVUXDg0PDRTCw9yThBnFN
4VUDAB6gFABfNe0mcXkLYEYBQgdAXAEFsG+IUjMQX0AjgDE5UBZQSPtnESGQcBIgOJB3EHdR5Ac9
PDFEOTAOIQFAIKNWbxM/MUTAKDTlICkgNMEaYC0zOTY4I4BA4ZhGQVjoXiCURS0AwLcDEETAMvRA
MgtlS0gHkP/d0eER1+F5kQCg3q/fv+DF/+HoOYUIYL7SL7EUIJvgaIH/BUDimCCUJtDo0IEASBDQ
gX9W4AngOxGPACzwJTBFcVi8IDcOQDlm6AbnUDTosOY36TDpADI36UB9M+mkefeYMDg5des2GCDu
gkD9YfFyPxAe0DKSsl/QMHTSP7hRT+DbY9vP3QtyMWFm91Fw3jFJEWbuz+/fsAbin//jpFeRCFBh
0SIxLWC8gdcl4wUq5xMwNzQOUOe7+bDGMeixM/AtMDPogOlZ+QiHNjcHYOrcSdIAEuwRFTJBZPvI
fQ1QAAMADTT9PwMAAwAPNP0/AwACARQ0AQAAABAAAABOSVRB+b+4AQCqADfZbgAAAgF/AAEAAAAx
AAAAMDAwMDAwMDAwNkY2MUY2NUExNUUzMzRFOTg1MDk5QUI3RTBEQzhEMzI0NUMyMjAwAAAAAAMA
BhCt9GqAAwAHECMLAAADABAQAAAAAAMAERAAAAAAHgAIEAEAAABlAAAAKE9VUkFQT0xPR0lFU0lG
WU9VUkVDRUlWRU1VTFRJUExFQ09QSUVTT0ZUSElTQ0ZQKURVRVRPVEhFTEFSR0VOVU1CRVJPRlJF
UVVFU1RTLFRIRVNVQk1JU1NJT05ERUFETElORQAAAAC1rw==

------=_NextPart_000_0018_01C529FC.BF0A5530
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

------=_NextPart_000_0018_01C529FC.BF0A5530--




From mip4-bounces@ietf.org  Thu Mar 17 16:55:56 2005
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 QAA24686
	for <mip4-web-archive@ietf.org>; Thu, 17 Mar 2005 16:55:56 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DC32Z-0007ps-GH
	for mip4-web-archive@ietf.org; Thu, 17 Mar 2005 17:00:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DC2w8-0002mp-7f; Thu, 17 Mar 2005 16:53:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DC2w4-0002mi-1H
	for mip4@megatron.ietf.org; Thu, 17 Mar 2005 16:53:44 -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 QAA24526
	for <mip4@ietf.org>; Thu, 17 Mar 2005 16:53:41 -0500 (EST)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DC30N-0007mR-MD
	for mip4@ietf.org; Thu, 17 Mar 2005 16:58:12 -0500
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j2HMNmX19891;
	Thu, 17 Mar 2005 14:23:48 -0800
X-mProtect: <200503172223> Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89,
	claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdZ9g5tj; Thu, 17 Mar 2005 14:23:47 PST
Message-ID: <4239FC52.33760051@iprg.nokia.com>
Date: Thu, 17 Mar 2005 13:53:22 -0800
From: "Charles E.Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Mobile IPv4 Mailing List <mip4@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit
Cc: Rajeev Koodli <rajeev.koodli@nokia.com>
Subject: [Mip4] Request to consider FMIPv4 as a working group document
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit



Hello folks,

We made a presentation at IETF 61 about a way to do
fast handovers with Mobile IPv4.  Our method is adapted
from the protocol for Mobile IPv6,
     draft-ietf-mipshop-fast-mipv6-03.txt

The Mobile IPv6 protocol has been approved for
publication and is currently in the RFC editor's
queue.

The discussion at IETF 61 can be reviewed from the
minutes, located at:
http://www1.ietf.org/proceedings_new/04nov/toc.html#int

As part of this discussion, I showed some results which
indicate very good performance for FMIPv4, suitable for
handling interactive voice applications.  I probably have
the PowerPoint presentation around somewhere if needed.

The protocol specification for the Mobile IPv4 fast
handovers is documented in the Internet Draft:
     draft-koodli-fmipv4-00.txt
which is available in the standard IETF draft
directories.

Thanks in advance for your consideration of our
request.

Regards,
Charlie P.

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


From mip4-bounces@ietf.org  Thu Mar 17 18:49:52 2005
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 SAA05005
	for <mip4-web-archive@ietf.org>; Thu, 17 Mar 2005 18:49:52 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DC4oq-0001zm-HO
	for mip4-web-archive@ietf.org; Thu, 17 Mar 2005 18:54:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DC4ix-0007fs-8M; Thu, 17 Mar 2005 18:48:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DC4iv-0007fn-PH
	for mip4@megatron.ietf.org; Thu, 17 Mar 2005 18:48:17 -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 SAA04944
	for <mip4@ietf.org>; Thu, 17 Mar 2005 18:48:14 -0500 (EST)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DC4nG-0001xt-AM
	for mip4@ietf.org; Thu, 17 Mar 2005 18:52:46 -0500
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j2I0ILP24227;
	Thu, 17 Mar 2005 16:18:21 -0800
X-mProtect: <200503180018> Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89,
	claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdg5jPmz; Thu, 17 Mar 2005 16:18:20 PST
Message-ID: <423A172C.77F2266E@iprg.nokia.com>
Date: Thu, 17 Mar 2005 15:47:56 -0800
From: "Charles E.Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Mobile IPv4 Mailing List <mip4@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Content-Transfer-Encoding: 7bit
Cc: Rajeev Koodli <rajeev.koodli@nokia.com>
Subject: [Mip4] Differences between Low Latency Handovers and FMIPv4
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
Content-Transfer-Encoding: 7bit

Hello folks,

FMIPv4 is a straightforward adaptation of the
Fast Handovers for Mobile IPv6 specification. 
The intention is to utilize the same design for
IPv4 networks, but that requires different 
packet formats.  We would like the [mip4] WG
to standardize these packet formats.  Both the
FMIPv6 and FMIPv4 draft mentioned here have been
implemented and offer the performance needed for 
real-time handovers.  Below, we offer a list of
some differences between our FMIPv4 spec and
the previously published Low Latency Handovers
("LLH") specification for Mobile IPv4.

1) We believe that FMIPv4 will avoid the pitfalls
   documented in the paper from Kempf et al.
   which were described quite a while back.

2) Tight coupling to L2 triggers: The entire LLH
   process is very tightly coupled to L2 triggers, to the
   extent that the protocol does not work without such
   triggers.  In contrast, FMIPv4 can make use of such
   triggers, but entire protocol operation does not
   depend on the availability and tight coupling of L2
   triggers.  For instance, the standard Linux function
   ll_handoff() indicates to IP layer that an interface
   has become available.  FMIPv4 code for FBU from the new
   link can be invoked within ll_handoff().

3) Changes to L2 triggers: In addition to the reliance
   on L2 triggers in LLH, the triggers themselves need to
   be modified to include parameters such as new FA IP
   address, MN IP address, their MAC addresses etc.
   within the triggers themselves.  This would require
   changes to whatever L2 triggers are available on _all_
   links where such triggers are supported. 
 
   This is not at all required for FMIPv4 operation.
   Nor does the spec recommend such changes.
 
4) The number of messages exchanged during handover:  
   4.a) Pre-reg LLH: 
   All the messages between the MN and FAs are exchanged 
   once the trigger event occurs.  This includes two proxy
   router messages and a registration request and 
   possibly registration reply on the old link.  In
   FMIPv4, a single message (FBU) is sent once the 
   decision to undergo handover is made.  The MN need not
   stay on the old link once FBU is sent. 
   4.b) Post-reg LLH: 
   No messages are exchanged between the MN and FA. 
   However, since the MN does not have means to change 
   the default router, it will continue to send packets 
   from the new link to the oFA's MAC address, which 
   should be dropped by the IP stack.  And, consideration
   (3) above applies; the triggers on oFA and nFA must
   contain MN's IP addresses, necessitating changes to L2 
   where the protocol might be useful.  Plus, such a mode
   "defers" MIPv4 operation, which is additional code on 
   the MN. 
   
   FMIPv4 works without imposing restrictions on when
   MIPv4 protocol messages need to be carried out.

5) Changes to MIPv4 operation: The MN changes its
   default access router once the registration reply is
   received in pre-reg LLH even if the MN is still on the
   oFA.  So, packet forwarding needs to be carefully
   constructed. (In post-reg LLH on the other hand, the
   MN does not change its default router at all, even
   though it is on the nFA.  This leads to different set
   of additional considerations).

   In FMIPv4, no changes to default router processing are
   needed.  That is, the MN is free to perform and process
   agent/router advertisements just as any normal
   (mobile) node would.

6) Protocol design: The FMIPv4 protocol clearly
   separates movement detection, IP address and nFA
   configuration, and registration request phases.  None
   of these phases is in the critical time path.  The only
   message that is on the criticial path is the FBU
   message.  For movement detection and IP/nFA
   configuration, the FMIPv4 protocol uses the Proxy
   Router messages, which are exchanged ahead of
   handover, as opposed to intitiating the handover in
   LLH.  There are quite a few other differences to list
   here.

In summary, Rajeev and I believe that the differences are
important enough to consider a separate spec of choice
to implementors.  It is especially appealing to those
considering FMIPv6 as well.

Regards,
Charlie P.

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


From mip4-bounces@ietf.org  Fri Mar 18 06:50:40 2005
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 GAA28657
	for <mip4-web-archive@ietf.org>; Fri, 18 Mar 2005 06:50:40 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DCG47-0001IQ-AC
	for mip4-web-archive@ietf.org; Fri, 18 Mar 2005 06:55:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DCFz4-0004l0-48; Fri, 18 Mar 2005 06:49:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DCFz2-0004kp-FW
	for mip4@megatron.ietf.org; Fri, 18 Mar 2005 06:49:40 -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 GAA27808
	for <mip4@ietf.org>; Fri, 18 Mar 2005 06:49:37 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DCG1u-0000wV-VK
	for mip4@ietf.org; Fri, 18 Mar 2005 06:52:39 -0500
Received: from esealmw127.eemea.ericsson.se ([153.88.254.122])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j2IBlmO6015999; Fri, 18 Mar 2005 12:47:48 +0100
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 18 Mar 2005 12:47:47 +0100
Received: from esealmw115.eemea.ericsson.se ([153.88.200.6]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 18 Mar 2005 12:47:47 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip4] Differences between Low Latency Handovers and FMIPv4
Date: Fri, 18 Mar 2005 12:47:46 +0100
Message-ID: <24521B9781EAC745A4BE65966F69C9BE212AA8@esealmw115.eemea.ericsson.se>
Thread-Topic: [Mip4] Differences between Low Latency Handovers and FMIPv4
Thread-index: AcUrTAkGbbDXaz3tQlSJmeM1XW8IAwAYoID9
From: "Karim El-Malki \(AL/EAB\)" <karim.el-malki@ericsson.com>
To: "Charles E.Perkins " <charliep@iprg.nokia.com>,
        "Mobile IPv4 Mailing List " <mip4@ietf.org>
X-OriginalArrivalTime: 18 Mar 2005 11:47:47.0761 (UTC)
	FILETIME=[4E499210:01C52BB0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
Content-Transfer-Encoding: quoted-printable
Cc: Rajeev Koodli  <rajeev.koodli@nokia.com>
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Content-Transfer-Encoding: quoted-printable

Hi Charlie
I am a bit surprised by the many differences you see
between FMIPv6 and Low Latency. In actual fact low
latency was written first and most of the stuff was
reused when FMIPv6 was first drafted in Madrid (when
George was editing FMIPv6). The same pre-reg (updating
routing before actual handoff) and post-reg (updating
routing after handoff) are still there. I am not
against changes in the spec but it took a while to
get to a stable document to go out as exp rfc with the
purpose of seeing what interest there is. I would hang
on to making changes until we know what are the real
needs from people (apart from ourselves since we
authored these specs) that have reviewed the exp rfc and
want to take it a step further.
Rgds
/Karim

-----Original Message-----
From: mip4-bounces@ietf.org
To: Mobile IPv4 Mailing List
Cc: Rajeev Koodli
Sent: 2005-03-18 00:47
Subject: [Mip4] Differences between Low Latency Handovers and FMIPv4

Hello folks,

FMIPv4 is a straightforward adaptation of the
Fast Handovers for Mobile IPv6 specification.=20
The intention is to utilize the same design for
IPv4 networks, but that requires different=20
packet formats.  We would like the [mip4] WG
to standardize these packet formats.  Both the
FMIPv6 and FMIPv4 draft mentioned here have been
implemented and offer the performance needed for=20
real-time handovers.  Below, we offer a list of
some differences between our FMIPv4 spec and
the previously published Low Latency Handovers
("LLH") specification for Mobile IPv4.

1) We believe that FMIPv4 will avoid the pitfalls
   documented in the paper from Kempf et al.
   which were described quite a while back.

2) Tight coupling to L2 triggers: The entire LLH
   process is very tightly coupled to L2 triggers, to the
   extent that the protocol does not work without such
   triggers.  In contrast, FMIPv4 can make use of such
   triggers, but entire protocol operation does not
   depend on the availability and tight coupling of L2
   triggers.  For instance, the standard Linux function
   ll_handoff() indicates to IP layer that an interface
   has become available.  FMIPv4 code for FBU from the new
   link can be invoked within ll_handoff().

3) Changes to L2 triggers: In addition to the reliance
   on L2 triggers in LLH, the triggers themselves need to
   be modified to include parameters such as new FA IP
   address, MN IP address, their MAC addresses etc.
   within the triggers themselves.  This would require
   changes to whatever L2 triggers are available on _all_
   links where such triggers are supported.=20
=20
   This is not at all required for FMIPv4 operation.
   Nor does the spec recommend such changes.
=20
4) The number of messages exchanged during handover: =20
   4.a) Pre-reg LLH:=20
   All the messages between the MN and FAs are exchanged=20
   once the trigger event occurs.  This includes two proxy
   router messages and a registration request and=20
   possibly registration reply on the old link.  In
   FMIPv4, a single message (FBU) is sent once the=20
   decision to undergo handover is made.  The MN need not
   stay on the old link once FBU is sent.=20
   4.b) Post-reg LLH:=20
   No messages are exchanged between the MN and FA.=20
   However, since the MN does not have means to change=20
   the default router, it will continue to send packets=20
   from the new link to the oFA's MAC address, which=20
   should be dropped by the IP stack.  And, consideration
   (3) above applies; the triggers on oFA and nFA must
   contain MN's IP addresses, necessitating changes to L2=20
   where the protocol might be useful.  Plus, such a mode
   "defers" MIPv4 operation, which is additional code on=20
   the MN.=20
  =20
   FMIPv4 works without imposing restrictions on when
   MIPv4 protocol messages need to be carried out.

5) Changes to MIPv4 operation: The MN changes its
   default access router once the registration reply is
   received in pre-reg LLH even if the MN is still on the
   oFA.  So, packet forwarding needs to be carefully
   constructed. (In post-reg LLH on the other hand, the
   MN does not change its default router at all, even
   though it is on the nFA.  This leads to different set
   of additional considerations).

   In FMIPv4, no changes to default router processing are
   needed.  That is, the MN is free to perform and process
   agent/router advertisements just as any normal
   (mobile) node would.

6) Protocol design: The FMIPv4 protocol clearly
   separates movement detection, IP address and nFA
   configuration, and registration request phases.  None
   of these phases is in the critical time path.  The only
   message that is on the criticial path is the FBU
   message.  For movement detection and IP/nFA
   configuration, the FMIPv4 protocol uses the Proxy
   Router messages, which are exchanged ahead of
   handover, as opposed to intitiating the handover in
   LLH.  There are quite a few other differences to list
   here.

In summary, Rajeev and I believe that the differences are
important enough to consider a separate spec of choice
to implementors.  It is especially appealing to those
considering FMIPv6 as well.

Regards,
Charlie P.

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


From mip4-bounces@ietf.org  Fri Mar 18 08:19:03 2005
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 IAA06040
	for <mip4-web-archive@ietf.org>; Fri, 18 Mar 2005 08:19:03 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DCHS0-0004xg-5x
	for mip4-web-archive@ietf.org; Fri, 18 Mar 2005 08:23:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DCHMH-00027Z-Bm; Fri, 18 Mar 2005 08:17:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DCHMF-00027M-HA
	for mip4@megatron.ietf.org; Fri, 18 Mar 2005 08:17:43 -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 IAA05995
	for <mip4@ietf.org>; Fri, 18 Mar 2005 08:17:41 -0500 (EST)
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DCHQh-0004wK-50
	for mip4@ietf.org; Fri, 18 Mar 2005 08:22:19 -0500
Received: from esealmw129.eemea.ericsson.se ([153.88.254.120])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j2IDHbg2008876; Fri, 18 Mar 2005 14:17:41 +0100 (MET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 18 Mar 2005 14:17:39 +0100
Received: from [147.214.237.81] ([147.214.237.81]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 18 Mar 2005 14:17:39 +0100
Message-ID: <423AD4E9.6040708@levkowetz.com>
Date: Fri, 18 Mar 2005 14:17:29 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Debian Thunderbird 1.0 (X11/20050116)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Karim El-Malki (AL/EAB)" <karim.el-malki@ericsson.com>
Subject: Re: [Mip4] Differences between Low Latency Handovers and FMIPv4
References: <24521B9781EAC745A4BE65966F69C9BE212AA8@esealmw115.eemea.ericsson.se>
In-Reply-To: <24521B9781EAC745A4BE65966F69C9BE212AA8@esealmw115.eemea.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Mar 2005 13:17:39.0462 (UTC)
	FILETIME=[DBFDDA60:01C52BBC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>,
        "Charles E.Perkins" <charliep@iprg.nokia.com>,
        Rajeev Koodli <rajeev.koodli@nokia.com>
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: 7bit

Hi Karim,

<hat type="chair">

    I think it would be good if we could look at this proposed workgroup
    item according to its merits, rather than go into its history, where
    there is a bit of controversy which we don't need to repeat here.

    That the low-latency draft is due for publication as experimental does
    not preclude other experimental drafts in the same area if there is
    good motivation for them.  Quite to the contrary, actually - this is a
    way to improve our understanding and move forward as a community.

    When this work has been discussed in the meetings, there has seemed to
    be a good amount of interest in it, which makes it a valid candidate
    for adoption.  So again, let's consider it on its objective merits.

    I'd also like to hear other people's comments on the merits of adopting
    this as a workgroup item, and the level of interest there currently is in
    this.

</hat>

	Henrik


On 03/18/2005 12:47 PM Karim El-Malki (AL/EAB) said the following:
> Hi Charlie
> I am a bit surprised by the many differences you see
> between FMIPv6 and Low Latency. In actual fact low
> latency was written first and most of the stuff was
> reused when FMIPv6 was first drafted in Madrid (when
> George was editing FMIPv6). The same pre-reg (updating
> routing before actual handoff) and post-reg (updating
> routing after handoff) are still there. I am not
> against changes in the spec but it took a while to
> get to a stable document to go out as exp rfc with the
> purpose of seeing what interest there is. I would hang
> on to making changes until we know what are the real
> needs from people (apart from ourselves since we
> authored these specs) that have reviewed the exp rfc and
> want to take it a step further.
> Rgds
> /Karim

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


From mip4-bounces@ietf.org  Fri Mar 18 09:14:05 2005
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 JAA10303
	for <mip4-web-archive@ietf.org>; Fri, 18 Mar 2005 09:14:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DCIJH-0006vw-Kj
	for mip4-web-archive@ietf.org; Fri, 18 Mar 2005 09:18:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DCID8-0002uI-3t; Fri, 18 Mar 2005 09:12:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DCID5-0002tm-Tw
	for mip4@megatron.ietf.org; Fri, 18 Mar 2005 09:12:19 -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 JAA10099
	for <mip4@ietf.org>; Fri, 18 Mar 2005 09:12:17 -0500 (EST)
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DCIHX-0006sw-Tt
	for mip4@ietf.org; Fri, 18 Mar 2005 09:16:56 -0500
Received: from esealmw127.eemea.ericsson.se ([153.88.254.122])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j2IEBmi2019513; Fri, 18 Mar 2005 15:12:15 +0100 (MET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.173]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 18 Mar 2005 15:11:55 +0100
Received: from esealmw115.eemea.ericsson.se ([153.88.200.6]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 18 Mar 2005 15:11:55 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip4] Differences between Low Latency Handovers and FMIPv4
Date: Fri, 18 Mar 2005 15:11:54 +0100
Message-ID: <24521B9781EAC745A4BE65966F69C9BE212AAA@esealmw115.eemea.ericsson.se>
Thread-Topic: [Mip4] Differences between Low Latency Handovers and FMIPv4
Thread-index: AcUrTAkGbbDXaz3tQlSJmeM1XW8IAwAc3fG6
From: "Karim El-Malki \(AL/EAB\)" <karim.el-malki@ericsson.com>
To: "Charles E.Perkins " <charliep@iprg.nokia.com>,
        "Mobile IPv4 Mailing List " <mip4@ietf.org>
X-OriginalArrivalTime: 18 Mar 2005 14:11:55.0182 (UTC)
	FILETIME=[708D4CE0:01C52BC4]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290
Content-Transfer-Encoding: quoted-printable
Cc: Rajeev Koodli  <rajeev.koodli@nokia.com>
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d
Content-Transfer-Encoding: quoted-printable

Following Henrik's note I'll expand on the technical
issues. As I wrote in my previous email I cannot quite
see the major difference between these drafts. Your new
draft considers link-layer triggers just as FMIPv6 and Low
Latency in order to improve performance. You describe AP
scanning etc. which is not different from the existing
approach. An IP interface becoming available is just a
way of implementing a mobile trigger right? You describe
tunnelling between FAs which is covered by the pre-reg/post-reg.
combination scenario in Low Latency.
One other mechanism was however pointed out a while back: sending
the mobile registration to create the FA-FA tunnel AFTER L2
handoff. I assume that this is the mechanism you want to add
since the advantages you note below are applicable to that
scenario? This wasn't covered in low latency because it was covered
by the PFANE mechanism in route optv4. Have you considered PFANE?
I think the rest is covered already by pre-reg, post-reg and the
combined mechanism.
/Karim

-----Original Message-----
From: mip4-bounces@ietf.org
To: Mobile IPv4 Mailing List
Cc: Rajeev Koodli
Sent: 2005-03-18 00:47
Subject: [Mip4] Differences between Low Latency Handovers and FMIPv4

Hello folks,

FMIPv4 is a straightforward adaptation of the
Fast Handovers for Mobile IPv6 specification.=20
The intention is to utilize the same design for
IPv4 networks, but that requires different=20
packet formats.  We would like the [mip4] WG
to standardize these packet formats.  Both the
FMIPv6 and FMIPv4 draft mentioned here have been
implemented and offer the performance needed for=20
real-time handovers.  Below, we offer a list of
some differences between our FMIPv4 spec and
the previously published Low Latency Handovers
("LLH") specification for Mobile IPv4.

1) We believe that FMIPv4 will avoid the pitfalls
   documented in the paper from Kempf et al.
   which were described quite a while back.

2) Tight coupling to L2 triggers: The entire LLH
   process is very tightly coupled to L2 triggers, to the
   extent that the protocol does not work without such
   triggers.  In contrast, FMIPv4 can make use of such
   triggers, but entire protocol operation does not
   depend on the availability and tight coupling of L2
   triggers.  For instance, the standard Linux function
   ll_handoff() indicates to IP layer that an interface
   has become available.  FMIPv4 code for FBU from the new
   link can be invoked within ll_handoff().

3) Changes to L2 triggers: In addition to the reliance
   on L2 triggers in LLH, the triggers themselves need to
   be modified to include parameters such as new FA IP
   address, MN IP address, their MAC addresses etc.
   within the triggers themselves.  This would require
   changes to whatever L2 triggers are available on _all_
   links where such triggers are supported.=20
=20
   This is not at all required for FMIPv4 operation.
   Nor does the spec recommend such changes.
=20
4) The number of messages exchanged during handover: =20
   4.a) Pre-reg LLH:=20
   All the messages between the MN and FAs are exchanged=20
   once the trigger event occurs.  This includes two proxy
   router messages and a registration request and=20
   possibly registration reply on the old link.  In
   FMIPv4, a single message (FBU) is sent once the=20
   decision to undergo handover is made.  The MN need not
   stay on the old link once FBU is sent.=20
   4.b) Post-reg LLH:=20
   No messages are exchanged between the MN and FA.=20
   However, since the MN does not have means to change=20
   the default router, it will continue to send packets=20
   from the new link to the oFA's MAC address, which=20
   should be dropped by the IP stack.  And, consideration
   (3) above applies; the triggers on oFA and nFA must
   contain MN's IP addresses, necessitating changes to L2=20
   where the protocol might be useful.  Plus, such a mode
   "defers" MIPv4 operation, which is additional code on=20
   the MN.=20
  =20
   FMIPv4 works without imposing restrictions on when
   MIPv4 protocol messages need to be carried out.

5) Changes to MIPv4 operation: The MN changes its
   default access router once the registration reply is
   received in pre-reg LLH even if the MN is still on the
   oFA.  So, packet forwarding needs to be carefully
   constructed. (In post-reg LLH on the other hand, the
   MN does not change its default router at all, even
   though it is on the nFA.  This leads to different set
   of additional considerations).

   In FMIPv4, no changes to default router processing are
   needed.  That is, the MN is free to perform and process
   agent/router advertisements just as any normal
   (mobile) node would.

6) Protocol design: The FMIPv4 protocol clearly
   separates movement detection, IP address and nFA
   configuration, and registration request phases.  None
   of these phases is in the critical time path.  The only
   message that is on the criticial path is the FBU
   message.  For movement detection and IP/nFA
   configuration, the FMIPv4 protocol uses the Proxy
   Router messages, which are exchanged ahead of
   handover, as opposed to intitiating the handover in
   LLH.  There are quite a few other differences to list
   here.

In summary, Rajeev and I believe that the differences are
important enough to consider a separate spec of choice
to implementors.  It is especially appealing to those
considering FMIPv6 as well.

Regards,
Charlie P.

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


From mip4-bounces@ietf.org  Fri Mar 18 13:55:35 2005
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 NAA10522
	for <mip4-web-archive@ietf.org>; Fri, 18 Mar 2005 13:55:35 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DCMhm-0001v8-0i
	for mip4-web-archive@ietf.org; Fri, 18 Mar 2005 14:00:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DCMZt-0006nM-Cx; Fri, 18 Mar 2005 13:52:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DCMZr-0006nE-PR
	for mip4@megatron.ietf.org; Fri, 18 Mar 2005 13:52:08 -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 NAA09914
	for <mip4@ietf.org>; Fri, 18 Mar 2005 13:52:04 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DCMeM-0001lS-Hu
	for mip4@ietf.org; Fri, 18 Mar 2005 13:56:47 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-4.cisco.com with ESMTP; 18 Mar 2005 10:53:15 -0800
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j2IIptZV000658;
	Fri, 18 Mar 2005 10:51:56 -0800 (PST)
Received: from kleung-w2k01.cisco.com (sjc-vpn4-961.cisco.com [10.21.83.192])
	by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with ESMTP id BDA93744;
	Fri, 18 Mar 2005 10:51:54 -0800 (PST)
Message-Id: <4.3.2.7.2.20050318083546.0305f100@mira-sjcm-2.cisco.com>
X-Sender: kleung@mira-sjcm-2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 18 Mar 2005 10:44:44 -0800
To: "Charles E.Perkins" <charliep@iprg.nokia.com>
From: Kent Leung <kleung@cisco.com>
Subject: Re: [Mip4] Request to consider FMIPv4 as a working group
  document
In-Reply-To: <4239FC52.33760051@iprg.nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>,
        Rajeev Koodli <rajeev.koodli@nokia.com>
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36

Hi Charlie.

Generally, I support having a WG solution for fast handover
using MIPv4.

Some of the areas that is debatable in the draft:

  - Key difference between MIPv4 and MIPv6 is FA existence.
  - FMIPv4 enabled ARs not being FAs is unlikely, IMHO.  So
    we can simplify by specifying only FA mode operation, no CCoA
    support needed since ARs would have to be MIPv4 enabled.
    This would fit the deployment model and clean up most of
    draft dealing with IP address management.
  - Support for fast handover in WiFi already exists today w/o
    MIPv4 involvement.  Therefore, realizing deployments using
    this type of scheme will be difficult.

Haven't read the draft in detail for specifics to MIPv4.  Will comment
on them later.

Kent

At 01:53 PM 3/17/2005 -0800, Charles E.Perkins wrote:


>Hello folks,
>
>We made a presentation at IETF 61 about a way to do
>fast handovers with Mobile IPv4.  Our method is adapted
>from the protocol for Mobile IPv6,
>      draft-ietf-mipshop-fast-mipv6-03.txt
>
>The Mobile IPv6 protocol has been approved for
>publication and is currently in the RFC editor's
>queue.
>
>The discussion at IETF 61 can be reviewed from the
>minutes, located at:
>http://www1.ietf.org/proceedings_new/04nov/toc.html#int
>
>As part of this discussion, I showed some results which
>indicate very good performance for FMIPv4, suitable for
>handling interactive voice applications.  I probably have
>the PowerPoint presentation around somewhere if needed.
>
>The protocol specification for the Mobile IPv4 fast
>handovers is documented in the Internet Draft:
>      draft-koodli-fmipv4-00.txt
>which is available in the standard IETF draft
>directories.
>
>Thanks in advance for your consideration of our
>request.
>
>Regards,
>Charlie P.
>
>--
>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/

--
      |           |                   Kent Leung
     :|:         :|:                  IP Mobility Development
    :|||:       :|||:                 Internet Technologies Division
   :|||||||:   :|||||||:              Voice: 408.526.5030
.:|||||||||:.:|||||||||:.             Fax:   408.525.1653
  c i s c o S y s t e m s             Email: kleung@cisco.com

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


From mip4-bounces@ietf.org  Fri Mar 18 14:44:18 2005
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 OAA16052
	for <mip4-web-archive@ietf.org>; Fri, 18 Mar 2005 14:44:17 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DCNSt-00040x-AN
	for mip4-web-archive@ietf.org; Fri, 18 Mar 2005 14:48:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DCNLW-0007zP-0y; Fri, 18 Mar 2005 14:41:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DCNLU-0007zK-2N
	for mip4@megatron.ietf.org; Fri, 18 Mar 2005 14:41:20 -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 OAA15717
	for <mip4@ietf.org>; Fri, 18 Mar 2005 14:41:18 -0500 (EST)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DCNPy-0003wj-HX
	for mip4@ietf.org; Fri, 18 Mar 2005 14:45:59 -0500
Message-ID: <07e101c52bf2$96c46320$0f6115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Henrik Levkowetz" <henrik@levkowetz.com>,
        "Karim El-Malki (AL/EAB)" <karim.el-malki@ericsson.com>
References: <24521B9781EAC745A4BE65966F69C9BE212AA8@esealmw115.eemea.ericsson.se>
	<423AD4E9.6040708@levkowetz.com>
Subject: Re: [Mip4] Differences between Low Latency Handovers and FMIPv4
Date: Fri, 18 Mar 2005 11:42:07 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433
Content-Transfer-Encoding: 7bit
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>,
        "Charles E.Perkins" <charliep@iprg.nokia.com>,
        Rajeev Koodli <rajeev.koodli@nokia.com>
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Content-Transfer-Encoding: 7bit

Henrik,

I'm in support of doing this work. Since MOBOPTS seems to have a lot on its
plate at the moment and MIP4 doesn't, perhaps MIP4 would be the right place.

As Kent mentioned in his email, 802.11 wireless switches now do inter-subnet
handover optimization for "lightweight AP" 802.11 without any need for host
involvment (essentially using a nonstandardized version of Post-reg), so it
is not clear to me how relevant this work is to 802.11. I think it might
make sense to look into bringing the switch vendors into the discussion,
since wireless LAN switches are a large and growing part of the 802.11
market. From a service provider/enterprise customer standpoint, having a PS
RFC protocol for inter-subnet handover on wireless switches would be ideal,
because the switches are shipping product, are being deployed, but are not
interoperable at this level today. Unfortunately, FMIPv4 won't address this,
but it might be useful for other link technologies and for intertechnology
handover.

With regard to Charlie's email about the technical drawbacks of LLH, what
our research found for three different link technology types (simulated
using 802.3, CDMA2K, and 802.11) and with some analysis is that Pre-reg is
nondeterministic for certain deployment and link technology situations, and
we therefore believe it would be very hard to deploy. Post-reg performs very
well when the required link triggers are available (such as on CDMA2K), but
it cannot be implemented on "standalone AP" 802.11 because the link triggers
aren't there (it can be implemented on "lightweight AP" 802.11 because the
wireless switch provides the link trigger and anchor point for the tunnel).
In our research, we implemented an FMIP-like protocol on 802.11 and the
results were good within statistical range for both network-triggered
handover (using the Post-reg and Reassoc.Request() arrival on the AP and a
single AP per subnet) and host-triggered handover (using the FMIPv4 like
protocol).

Note, however, that if one assumes completely decoupled handover at L2 and
L3, as now is apparently the case with "standalone AP" 802.11 due to the
potential for 802.11i/r reauthentication on every AP move, the host must
perform DNAv4 on every L2 handover, which will involve an ARP to the router.
This means that, effectively, there are at least four IP round trips prior
to the MN receiving traffic from the previous FA. Exactly what the impact of
that is on performance-sensitive traffic, such as VoIP, needs to be
clarified.

With respect to the security issue, there is still not a resolution of how
to secure the host to network interaction in FMIPv6, and it is even more
unclear for FMIPv4, particularly in a roaming situation. There are a couple
approaches being worked on for FMIPv6. One approach, on which I am
co-author, uses SEND and therefore is not applicable directly to FMIPv4,
though it could be modified to be so. Another is under development to use
the EAP key hierarchy to derive a handover key, but as yet there is no
written draft in this area.

So, I think this would be a good item for the WG to take up, but I believe
the primary hurdle is security.

        jak



----- Original Message ----- 
From: "Henrik Levkowetz" <henrik@levkowetz.com>
To: "Karim El-Malki (AL/EAB)" <karim.el-malki@ericsson.com>
Cc: "Mobile IPv4 Mailing List" <mip4@ietf.org>; "Charles E.Perkins"
<charliep@iprg.nokia.com>; "Rajeev Koodli" <rajeev.koodli@nokia.com>
Sent: Friday, March 18, 2005 5:17 AM
Subject: Re: [Mip4] Differences between Low Latency Handovers and FMIPv4


> Hi Karim,
>
> <hat type="chair">
>
>     I think it would be good if we could look at this proposed workgroup
>     item according to its merits, rather than go into its history, where
>     there is a bit of controversy which we don't need to repeat here.
>
>     That the low-latency draft is due for publication as experimental does
>     not preclude other experimental drafts in the same area if there is
>     good motivation for them.  Quite to the contrary, actually - this is a
>     way to improve our understanding and move forward as a community.
>
>     When this work has been discussed in the meetings, there has seemed to
>     be a good amount of interest in it, which makes it a valid candidate
>     for adoption.  So again, let's consider it on its objective merits.
>
>     I'd also like to hear other people's comments on the merits of
adopting
>     this as a workgroup item, and the level of interest there currently is
in
>     this.
>
> </hat>
>
> Henrik
>
>
> On 03/18/2005 12:47 PM Karim El-Malki (AL/EAB) said the following:
> > Hi Charlie
> > I am a bit surprised by the many differences you see
> > between FMIPv6 and Low Latency. In actual fact low
> > latency was written first and most of the stuff was
> > reused when FMIPv6 was first drafted in Madrid (when
> > George was editing FMIPv6). The same pre-reg (updating
> > routing before actual handoff) and post-reg (updating
> > routing after handoff) are still there. I am not
> > against changes in the spec but it took a while to
> > get to a stable document to go out as exp rfc with the
> > purpose of seeing what interest there is. I would hang
> > on to making changes until we know what are the real
> > needs from people (apart from ourselves since we
> > authored these specs) that have reviewed the exp rfc and
> > want to take it a step further.
> > Rgds
> > /Karim
>
> -- 
> 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/


From mip4-bounces@ietf.org  Fri Mar 18 14:44:27 2005
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 OAA16093
	for <mip4-web-archive@ietf.org>; Fri, 18 Mar 2005 14:44:27 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DCNT2-000419-No
	for mip4-web-archive@ietf.org; Fri, 18 Mar 2005 14:49:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DCNMB-00084F-Bk; Fri, 18 Mar 2005 14:42:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DCNMA-00084A-Ou
	for mip4@megatron.ietf.org; Fri, 18 Mar 2005 14:42:02 -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 OAA15766
	for <mip4@ietf.org>; Fri, 18 Mar 2005 14:42:00 -0500 (EST)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DCNQf-0003xM-2y
	for mip4@ietf.org; Fri, 18 Mar 2005 14:46:42 -0500
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate8.mot.com (Motorola/Motgate8) with ESMTP id j2IJiE2C024605
	for <mip4@ietf.org>; Fri, 18 Mar 2005 12:44:15 -0700 (MST)
Received: from il02exm13.corp.mot.com (il02exm13.corp.mot.com [10.0.111.24])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id j2IJgKc3028816
	for <mip4@ietf.org>; Fri, 18 Mar 2005 13:42:21 -0600 (CST)
Received: by il02exm13 with Internet Mail Service (5.5.2657.72)
	id <D3S2RQ1Q>; Fri, 18 Mar 2005 13:41:57 -0600
Message-ID: <1B631E11D496D711BB2800065BFCB6A10C97790C@il02exm13>
From: Narayanan Vidya-CVN065 <vidya@motorola.com>
To: "'Kent Leung'" <kleung@cisco.com>,
        "Charles E.Perkins"
	<charliep@iprg.nokia.com>
Subject: RE: [Mip4] Request to consider FMIPv4 as a working group document
Date: Fri, 18 Mar 2005 13:41:56 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>,
        Rajeev Koodli <rajeev.koodli@nokia.com>
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a

Hi Kent, 
What you are implying here seems to be that in order to have a fast handoff solution, the MN must be using an FA CoA - did I get that right? 

If so, that seems a little restrictive to me. There are scenarios where the MN may be using a CCoA and registering through an FA. Also, in general, it seems that a solution that will work with or without FAs will be a preferable one. 

Vidya

-----Original Message-----
From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of Kent Leung
Sent: Friday, March 18, 2005 12:45 PM
To: Charles E.Perkins
Cc: Mobile IPv4 Mailing List; Rajeev Koodli
Subject: Re: [Mip4] Request to consider FMIPv4 as a working group document


Hi Charlie.

Generally, I support having a WG solution for fast handover using MIPv4.

Some of the areas that is debatable in the draft:

  - Key difference between MIPv4 and MIPv6 is FA existence.
  - FMIPv4 enabled ARs not being FAs is unlikely, IMHO.  So
    we can simplify by specifying only FA mode operation, no CCoA
    support needed since ARs would have to be MIPv4 enabled.
    This would fit the deployment model and clean up most of
    draft dealing with IP address management.
  - Support for fast handover in WiFi already exists today w/o
    MIPv4 involvement.  Therefore, realizing deployments using
    this type of scheme will be difficult.

Haven't read the draft in detail for specifics to MIPv4.  Will comment on them later.

Kent

At 01:53 PM 3/17/2005 -0800, Charles E.Perkins wrote:


>Hello folks,
>
>We made a presentation at IETF 61 about a way to do
>fast handovers with Mobile IPv4.  Our method is adapted
>from the protocol for Mobile IPv6,
>      draft-ietf-mipshop-fast-mipv6-03.txt
>
>The Mobile IPv6 protocol has been approved for
>publication and is currently in the RFC editor's
>queue.
>
>The discussion at IETF 61 can be reviewed from the
>minutes, located at: 
>http://www1.ietf.org/proceedings_new/04nov/toc.html#int
>
>As part of this discussion, I showed some results which indicate very 
>good performance for FMIPv4, suitable for handling interactive voice 
>applications.  I probably have the PowerPoint presentation around 
>somewhere if needed.
>
>The protocol specification for the Mobile IPv4 fast
>handovers is documented in the Internet Draft:
>      draft-koodli-fmipv4-00.txt
>which is available in the standard IETF draft
>directories.
>
>Thanks in advance for your consideration of our
>request.
>
>Regards,
>Charlie P.
>
>--
>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/

--
      |           |                   Kent Leung
     :|:         :|:                  IP Mobility Development
    :|||:       :|||:                 Internet Technologies Division
   :|||||||:   :|||||||:              Voice: 408.526.5030
.:|||||||||:.:|||||||||:.             Fax:   408.525.1653
  c i s c o S y s t e m s             Email: kleung@cisco.com

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


From mip4-bounces@ietf.org  Fri Mar 18 15:09:21 2005
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 PAA19500
	for <mip4-web-archive@ietf.org>; Fri, 18 Mar 2005 15:09:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DCNr6-00056B-Vp
	for mip4-web-archive@ietf.org; Fri, 18 Mar 2005 15:14:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DCNjy-0003g4-Dj; Fri, 18 Mar 2005 15:06:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DCNjw-0003fX-53
	for mip4@megatron.ietf.org; Fri, 18 Mar 2005 15:06:36 -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 PAA19028
	for <mip4@ietf.org>; Fri, 18 Mar 2005 15:06:31 -0500 (EST)
Received: from wsip-68-101-41-112.dc.dc.cox.net ([68.101.41.112]
	helo=email-filesrv) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DCNoP-0004ux-Ar
	for mip4@ietf.org; Fri, 18 Mar 2005 15:11:13 -0500
Received: from [198.57.19.100] by email-filesrv
	(ArGoSoft Mail Server Pro for WinNT/2000/XP, Version 1.8 (1.8.1.7));
	Fri, 18 Mar 2005 14:39:13 -0500
Message-ID: <001801c52bf5$fd6f7850$2101a8c0@us.nextel.com>
From: "Qiang Zhang/Aber" <qzhang@aber-networks.net>
To: "Karim El-Malki \(AL/EAB\)" <karim.el-malki@ericsson.com>,
        "Charles E.Perkins " <charliep@iprg.nokia.com>,
        "Mobile IPv4 Mailing List " <mip4@ietf.org>
References: <24521B9781EAC745A4BE65966F69C9BE212AAA@esealmw115.eemea.ericsson.se>
Subject: Re: [Mip4] Differences between Low Latency Handovers and FMIPv4
Date: Fri, 18 Mar 2005 15:05:49 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 2.9 (++)
X-Scan-Signature: 20f22c03b5c66958bff5ef54fcda6e48
Content-Transfer-Encoding: 7bit
Cc: Rajeev Koodli <rajeev.koodli@nokia.com>
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 2.9 (++)
X-Scan-Signature: 848ed35f2a4fc0638fa89629cb640f48
Content-Transfer-Encoding: 7bit

Hello, All

>From an implementor point of view, since there is already a llh draft in
experimental standard,  it will be interesting to debate on the technical
pros/cons between, or if they are having a lot similarity, can those be
combined?

http://www.ietf.org/internet-drafts/draft-ietf-mobileip-lowlatency-handoffs-v4-09.txt

and

http://www.ietf.org/internet-drafts/draft-koodli-fmipv4-00.txt

Thanks
Qiang


----- Original Message ----- 
From: "Karim El-Malki (AL/EAB)" <karim.el-malki@ericsson.com>
To: "Charles E.Perkins " <charliep@iprg.nokia.com>; "Mobile IPv4 Mailing
List " <mip4@ietf.org>
Cc: "Rajeev Koodli" <rajeev.koodli@nokia.com>
Sent: Friday, March 18, 2005 9:11 AM
Subject: RE: [Mip4] Differences between Low Latency Handovers and FMIPv4


Following Henrik's note I'll expand on the technical
issues. As I wrote in my previous email I cannot quite
see the major difference between these drafts. Your new
draft considers link-layer triggers just as FMIPv6 and Low
Latency in order to improve performance. You describe AP
scanning etc. which is not different from the existing
approach. An IP interface becoming available is just a
way of implementing a mobile trigger right? You describe
tunnelling between FAs which is covered by the pre-reg/post-reg.
combination scenario in Low Latency.
One other mechanism was however pointed out a while back: sending
the mobile registration to create the FA-FA tunnel AFTER L2
handoff. I assume that this is the mechanism you want to add
since the advantages you note below are applicable to that
scenario? This wasn't covered in low latency because it was covered
by the PFANE mechanism in route optv4. Have you considered PFANE?
I think the rest is covered already by pre-reg, post-reg and the
combined mechanism.
/Karim

-----Original Message-----
From: mip4-bounces@ietf.org
To: Mobile IPv4 Mailing List
Cc: Rajeev Koodli
Sent: 2005-03-18 00:47
Subject: [Mip4] Differences between Low Latency Handovers and FMIPv4

Hello folks,

FMIPv4 is a straightforward adaptation of the
Fast Handovers for Mobile IPv6 specification.
The intention is to utilize the same design for
IPv4 networks, but that requires different
packet formats.  We would like the [mip4] WG
to standardize these packet formats.  Both the
FMIPv6 and FMIPv4 draft mentioned here have been
implemented and offer the performance needed for
real-time handovers.  Below, we offer a list of
some differences between our FMIPv4 spec and
the previously published Low Latency Handovers
("LLH") specification for Mobile IPv4.

1) We believe that FMIPv4 will avoid the pitfalls
   documented in the paper from Kempf et al.
   which were described quite a while back.

2) Tight coupling to L2 triggers: The entire LLH
   process is very tightly coupled to L2 triggers, to the
   extent that the protocol does not work without such
   triggers.  In contrast, FMIPv4 can make use of such
   triggers, but entire protocol operation does not
   depend on the availability and tight coupling of L2
   triggers.  For instance, the standard Linux function
   ll_handoff() indicates to IP layer that an interface
   has become available.  FMIPv4 code for FBU from the new
   link can be invoked within ll_handoff().

3) Changes to L2 triggers: In addition to the reliance
   on L2 triggers in LLH, the triggers themselves need to
   be modified to include parameters such as new FA IP
   address, MN IP address, their MAC addresses etc.
   within the triggers themselves.  This would require
   changes to whatever L2 triggers are available on _all_
   links where such triggers are supported.

   This is not at all required for FMIPv4 operation.
   Nor does the spec recommend such changes.

4) The number of messages exchanged during handover:
   4.a) Pre-reg LLH:
   All the messages between the MN and FAs are exchanged
   once the trigger event occurs.  This includes two proxy
   router messages and a registration request and
   possibly registration reply on the old link.  In
   FMIPv4, a single message (FBU) is sent once the
   decision to undergo handover is made.  The MN need not
   stay on the old link once FBU is sent.
   4.b) Post-reg LLH:
   No messages are exchanged between the MN and FA.
   However, since the MN does not have means to change
   the default router, it will continue to send packets
   from the new link to the oFA's MAC address, which
   should be dropped by the IP stack.  And, consideration
   (3) above applies; the triggers on oFA and nFA must
   contain MN's IP addresses, necessitating changes to L2
   where the protocol might be useful.  Plus, such a mode
   "defers" MIPv4 operation, which is additional code on
   the MN.

   FMIPv4 works without imposing restrictions on when
   MIPv4 protocol messages need to be carried out.

5) Changes to MIPv4 operation: The MN changes its
   default access router once the registration reply is
   received in pre-reg LLH even if the MN is still on the
   oFA.  So, packet forwarding needs to be carefully
   constructed. (In post-reg LLH on the other hand, the
   MN does not change its default router at all, even
   though it is on the nFA.  This leads to different set
   of additional considerations).

   In FMIPv4, no changes to default router processing are
   needed.  That is, the MN is free to perform and process
   agent/router advertisements just as any normal
   (mobile) node would.

6) Protocol design: The FMIPv4 protocol clearly
   separates movement detection, IP address and nFA
   configuration, and registration request phases.  None
   of these phases is in the critical time path.  The only
   message that is on the criticial path is the FBU
   message.  For movement detection and IP/nFA
   configuration, the FMIPv4 protocol uses the Proxy
   Router messages, which are exchanged ahead of
   handover, as opposed to intitiating the handover in
   LLH.  There are quite a few other differences to list
   here.

In summary, Rajeev and I believe that the differences are
important enough to consider a separate spec of choice
to implementors.  It is especially appealing to those
considering FMIPv6 as well.

Regards,
Charlie P.

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



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


From mip4-bounces@ietf.org  Fri Mar 18 15:25:17 2005
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 PAA21919
	for <mip4-web-archive@ietf.org>; Fri, 18 Mar 2005 15:25:17 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DCO6Y-0005jA-H8
	for mip4-web-archive@ietf.org; Fri, 18 Mar 2005 15:29:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DCNxk-0005qW-1o; Fri, 18 Mar 2005 15:20:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DCNxj-0005qR-Gz
	for mip4@megatron.ietf.org; Fri, 18 Mar 2005 15:20:51 -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 PAA21139
	for <mip4@ietf.org>; Fri, 18 Mar 2005 15:20:49 -0500 (EST)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DCO2F-0005Uv-1H
	for mip4@ietf.org; Fri, 18 Mar 2005 15:25:31 -0500
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j2IKorH13287;
	Fri, 18 Mar 2005 12:50:53 -0800
X-mProtect: <200503182050> Nokia Silicon Valley Messaging Protection
Received: from danira-pool04977.americas.nokia.com (10.241.49.77,
	claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpd65fbMq; Fri, 18 Mar 2005 12:50:51 PST
Message-ID: <423B380A.4000302@iprg.nokia.com>
Date: Fri, 18 Mar 2005 12:20:26 -0800
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Kent Leung <kleung@cisco.com>
Subject: Re: [Mip4] Request to consider FMIPv4 as a working group  document
References: <4.3.2.7.2.20050318083546.0305f100@mira-sjcm-2.cisco.com>
In-Reply-To: <4.3.2.7.2.20050318083546.0305f100@mira-sjcm-2.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: 7bit
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>,
        Rajeev Koodli <rajeev.koodli@nokia.com>
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit


Hello Kent,

Thanks for your comments.  I have several follow-on
discussion points below.


Kent Leung wrote:

> Hi Charlie.
>
> Generally, I support having a WG solution for fast handover
> using MIPv4.

I hope you will find that FMIPv4 is useful for that purpose.

>   - Key difference between MIPv4 and MIPv6 is FA existence.

Well -- there are route optimization details and additional security
features that are also key differences...  But these are not necessarily
relevant to FMIPv4.

>  - FMIPv4 enabled ARs not being FAs is unlikely, IMHO.  So
>    we can simplify by specifying only FA mode operation, no CCoA
>    support needed since ARs would have to be MIPv4 enabled.
>    This would fit the deployment model and clean up most of
>    draft dealing with IP address management.

I think it is reasonable to have an access router that is not
a foreign agent.  Specifying that operation does not seem to
complicate the rest of the specification which relates to the
case of AR == FA.  So, I don't see any reason to take out
that part of the specification, and it could be useful.

>  - Support for fast handover in WiFi already exists today w/o
>    MIPv4 involvement.  Therefore, realizing deployments using
>    this type of scheme will be difficult.

Even WiFi access points or access point controllers might
well implement this feature, especially for the case of
heterogeneous media.

Thanks in advance for any more detailed comments
you can offer.


Regards,
Charlie P.


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


From mip4-bounces@ietf.org  Fri Mar 18 15:26:01 2005
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 PAA22042
	for <mip4-web-archive@ietf.org>; Fri, 18 Mar 2005 15:26:01 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DCO7G-0005kL-5V
	for mip4-web-archive@ietf.org; Fri, 18 Mar 2005 15:30:43 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DCO2Y-0006gz-CO; Fri, 18 Mar 2005 15:25:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DCO2X-0006gr-0M
	for mip4@megatron.ietf.org; Fri, 18 Mar 2005 15:25:49 -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 PAA22012
	for <mip4@ietf.org>; Fri, 18 Mar 2005 15:25:46 -0500 (EST)
Received: from mail.flarion.com ([63.103.94.23]
	helo=ftmailgfi1.flariontech.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DCO71-0005ja-Bd
	for mip4@ietf.org; Fri, 18 Mar 2005 15:30:28 -0500
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	ftmailgfi1.flariontech.com with Microsoft
	SMTPSVC(5.0.2195.6713); Fri, 18 Mar 2005 15:25:31 -0500
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip4] Request to consider FMIPv4 as a working group document
Date: Fri, 18 Mar 2005 15:25:31 -0500
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD17DDBB@ftmailserver.flariontech.com>
Thread-Topic: [Mip4] Request to consider FMIPv4 as a working group document
Thread-Index: AcUrPAp2iq0YUV5GTwaArMdWWRspDwAu7iPg
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Charles E.Perkins" <charliep@iprg.nokia.com>,
        "Mobile IPv4 Mailing List" <mip4@ietf.org>
X-OriginalArrivalTime: 18 Mar 2005 20:25:31.0882 (UTC)
	FILETIME=[A1F244A0:01C52BF8]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Content-Transfer-Encoding: quoted-printable
Cc: Rajeev Koodli <rajeev.koodli@nokia.com>
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Content-Transfer-Encoding: quoted-printable

Hi Charlie,=20

I think this work can be adopted by the WG if there are
concrete benefits over the existing WG doc. It would be really
useful if you could highlight the advantages.=20
>From reading through, it seems to me that it is mainly about
doing the same thing differently to make it similar to FMIPv6.
I.e. packetizing information differently.=20
I understand that you have simulations that show good performance,=20
but it's not clear that this is due to the different packet
format or simply because the handover improvement is good. The=20
latter is done by both drafts and, at least intuitively, it doesn't
look like packetizing things differently is having any significant
impact.=20

Some of the work we have discussed recently (i.e. dual stack MIP)
was about literally using the same packet for both v4 and
v6. I can see an advantage in doing that, but this is not what
your draft proposes.=20

thanks,
Hesham

 > -----Original Message-----
 > From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org]On=20
 > Behalf Of
 > Charles E.Perkins
 > Sent: Thursday, March 17, 2005 4:53 PM
 > To: Mobile IPv4 Mailing List
 > Cc: Rajeev Koodli
 > Subject: [Mip4] Request to consider FMIPv4 as a working=20
 > group document
 >=20
 >=20
 >=20
 >=20
 > Hello folks,
 >=20
 > We made a presentation at IETF 61 about a way to do
 > fast handovers with Mobile IPv4.  Our method is adapted
 > from the protocol for Mobile IPv6,
 >      draft-ietf-mipshop-fast-mipv6-03.txt
 >=20
 > The Mobile IPv6 protocol has been approved for
 > publication and is currently in the RFC editor's
 > queue.
 >=20
 > The discussion at IETF 61 can be reviewed from the
 > minutes, located at:
 > http://www1.ietf.org/proceedings_new/04nov/toc.html#int
 >=20
 > As part of this discussion, I showed some results which
 > indicate very good performance for FMIPv4, suitable for
 > handling interactive voice applications.  I probably have
 > the PowerPoint presentation around somewhere if needed.
 >=20
 > The protocol specification for the Mobile IPv4 fast
 > handovers is documented in the Internet Draft:
 >      draft-koodli-fmipv4-00.txt
 > which is available in the standard IETF draft
 > directories.
 >=20
 > Thanks in advance for your consideration of our
 > request.
 >=20
 > Regards,
 > Charlie P.
 >=20
 > --=20
 > Mip4 mailing list: Mip4@ietf.org
 >     Web interface: https://www1.ietf.org/mailman/listinfo/mip4
 >      Charter page:=20
 > http://www.ietf.org/html.charters/mip4-charter.html
 > Supplemental site: http://www.mip4.org/
 >=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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


From mip4-bounces@ietf.org  Fri Mar 18 15:34:40 2005
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 PAA23021
	for <mip4-web-archive@ietf.org>; Fri, 18 Mar 2005 15:34:40 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DCOFe-00066w-Jl
	for mip4-web-archive@ietf.org; Fri, 18 Mar 2005 15:39:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DCO7K-00006U-0u; Fri, 18 Mar 2005 15:30:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DCO7F-00005z-SE
	for mip4@megatron.ietf.org; Fri, 18 Mar 2005 15:30:42 -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 PAA22542
	for <mip4@ietf.org>; Fri, 18 Mar 2005 15:30:39 -0500 (EST)
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.33)
	id 1DCOBk-0005xL-A1
	for mip4@ietf.org; Fri, 18 Mar 2005 15:35:21 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-3.cisco.com with ESMTP; 18 Mar 2005 12:29:25 -0800
X-IronPort-AV: i="3.91,102,1110182400"; 
	d="scan'208"; a="237443662:sNHT583229852"
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j2IKTDgE028914;
	Fri, 18 Mar 2005 12:29:14 -0800 (PST)
Received: from kleung-w2k01.cisco.com (sjc-vpn4-961.cisco.com [10.21.83.192])
	by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with ESMTP id BDB08411;
	Fri, 18 Mar 2005 12:29:12 -0800 (PST)
Message-Id: <4.3.2.7.2.20050318120448.03014980@mira-sjcm-2.cisco.com>
X-Sender: kleung@mira-sjcm-2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 18 Mar 2005 12:29:12 -0800
To: Narayanan Vidya-CVN065 <vidya@motorola.com>
From: Kent Leung <kleung@cisco.com>
Subject: RE: [Mip4] Request to consider FMIPv4 as a working group
  document
In-Reply-To: <1B631E11D496D711BB2800065BFCB6A10C97790C@il02exm13>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>,
        "Charles E.Perkins" <charliep@iprg.nokia.com>,
        Rajeev Koodli <rajeev.koodli@nokia.com>
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede

Hi Vidya.  I wouldn't put it that way.

My logic is that a Mobile IP based fast handover solution will involve 
Mobile IP
operation and messaging on the access router.  If the access router is to
be enabled with Mobile IP to support fast handover, then it might as well
be a Foreign Agent.  I don't see a practical rationale to upgrade the AR part
way in a sense.

Kent

At 01:41 PM 3/18/2005 -0600, Narayanan Vidya-CVN065 wrote:
>Hi Kent,
>What you are implying here seems to be that in order to have a fast 
>handoff solution, the MN must be using an FA CoA - did I get that right?
>
>If so, that seems a little restrictive to me. There are scenarios where 
>the MN may be using a CCoA and registering through an FA. Also, in 
>general, it seems that a solution that will work with or without FAs will 
>be a preferable one.
>
>Vidya
>
>-----Original Message-----
>From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of 
>Kent Leung
>Sent: Friday, March 18, 2005 12:45 PM
>To: Charles E.Perkins
>Cc: Mobile IPv4 Mailing List; Rajeev Koodli
>Subject: Re: [Mip4] Request to consider FMIPv4 as a working group document
>
>
>Hi Charlie.
>
>Generally, I support having a WG solution for fast handover using MIPv4.
>
>Some of the areas that is debatable in the draft:
>
>   - Key difference between MIPv4 and MIPv6 is FA existence.
>   - FMIPv4 enabled ARs not being FAs is unlikely, IMHO.  So
>     we can simplify by specifying only FA mode operation, no CCoA
>     support needed since ARs would have to be MIPv4 enabled.
>     This would fit the deployment model and clean up most of
>     draft dealing with IP address management.
>   - Support for fast handover in WiFi already exists today w/o
>     MIPv4 involvement.  Therefore, realizing deployments using
>     this type of scheme will be difficult.
>
>Haven't read the draft in detail for specifics to MIPv4.  Will comment on 
>them later.
>
>Kent
>
>At 01:53 PM 3/17/2005 -0800, Charles E.Perkins wrote:
>
>
> >Hello folks,
> >
> >We made a presentation at IETF 61 about a way to do
> >fast handovers with Mobile IPv4.  Our method is adapted
> >from the protocol for Mobile IPv6,
> >      draft-ietf-mipshop-fast-mipv6-03.txt
> >
> >The Mobile IPv6 protocol has been approved for
> >publication and is currently in the RFC editor's
> >queue.
> >
> >The discussion at IETF 61 can be reviewed from the
> >minutes, located at:
> >http://www1.ietf.org/proceedings_new/04nov/toc.html#int
> >
> >As part of this discussion, I showed some results which indicate very
> >good performance for FMIPv4, suitable for handling interactive voice
> >applications.  I probably have the PowerPoint presentation around
> >somewhere if needed.
> >
> >The protocol specification for the Mobile IPv4 fast
> >handovers is documented in the Internet Draft:
> >      draft-koodli-fmipv4-00.txt
> >which is available in the standard IETF draft
> >directories.
> >
> >Thanks in advance for your consideration of our
> >request.
> >
> >Regards,
> >Charlie P.
> >
> >--
> >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/
>
>--
>       |           |                   Kent Leung
>      :|:         :|:                  IP Mobility Development
>     :|||:       :|||:                 Internet Technologies Division
>    :|||||||:   :|||||||:              Voice: 408.526.5030
>.:|||||||||:.:|||||||||:.             Fax:   408.525.1653
>   c i s c o S y s t e m s             Email: kleung@cisco.com
>
>--
>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/

--
      |           |                   Kent Leung
     :|:         :|:                  IP Mobility Development
    :|||:       :|||:                 Internet Technologies Division
   :|||||||:   :|||||||:              Voice: 408.526.5030
.:|||||||||:.:|||||||||:.             Fax:   408.525.1653
  c i s c o S y s t e m s             Email: kleung@cisco.com

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


From mip4-bounces@ietf.org  Fri Mar 18 15:53:47 2005
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 PAA28945
	for <mip4-web-archive@ietf.org>; Fri, 18 Mar 2005 15:53:47 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DCOY9-0008Dk-Ow
	for mip4-web-archive@ietf.org; Fri, 18 Mar 2005 15:58:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DCOGe-0002oa-Nj; Fri, 18 Mar 2005 15:40:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DCOGc-0002o5-VY
	for mip4@megatron.ietf.org; Fri, 18 Mar 2005 15:40:23 -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 PAA25175
	for <mip4@ietf.org>; Fri, 18 Mar 2005 15:40:20 -0500 (EST)
Received: from av1-1-sn1.fre.skanova.net ([81.228.11.107])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DCOL6-0006kp-Q8
	for mip4@ietf.org; Fri, 18 Mar 2005 15:45:02 -0500
Received: by av1-1-sn1.fre.skanova.net (Postfix, from userid 502)
	id 9801437F46; Fri, 18 Mar 2005 21:40:08 +0100 (CET)
Received: from smtp3-2-sn1.fre.skanova.net (smtp3-2-sn1.fre.skanova.net
	[81.228.11.164]) by av1-1-sn1.fre.skanova.net (Postfix) with ESMTP
	id 83CC037E9C; Fri, 18 Mar 2005 21:40:08 +0100 (CET)
Received: from shiraz.levkowetz.com (h195n1fls311o871.telia.com
	[213.64.174.195])
	by smtp3-2-sn1.fre.skanova.net (Postfix) with ESMTP id 72D0D37E4D;
	Fri, 18 Mar 2005 21:40:08 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.44)
	id 1DCOGN-0002pg-Uf; Fri, 18 Mar 2005 21:40:08 +0100
Message-ID: <423B3CA7.8020802@levkowetz.com>
Date: Fri, 18 Mar 2005 21:40:07 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Qiang Zhang/Aber <qzhang@aber-networks.net>
Subject: Re: [Mip4] Differences between Low Latency Handovers and FMIPv4
References: <24521B9781EAC745A4BE65966F69C9BE212AAA@esealmw115.eemea.ericsson.se>
	<001801c52bf5$fd6f7850$2101a8c0@us.nextel.com>
In-Reply-To: <001801c52bf5$fd6f7850$2101a8c0@us.nextel.com>
X-Enigmail-Version: 0.89.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit
Cc: Mobile IPv4 Mailing List <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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit

Hello Qiang,

On 2005-03-18 9:05 pm Qiang Zhang/Aber said the following:

>>From an implementor point of view, since there is already a llh draft in
> experimental standard,  it will be interesting to debate on the technical
> pros/cons between, or if they are having a lot similarity, can those be
> combined?

The lowlatency draft is just waiting for a reference; we will not pull
it back to consider combination.  If after some time out in the wide
world, we find that some intersection of these two drafts seem ripe for
standardization, I think it would be best to start fresh on that effort.

I should have made the point clear in an earlier note, but I expect
the fmipv4 draft, if adopted as a WG item, to also be intended for
publication as an experimental RFC.

Jak's experimental data regarding a lowlatency and a fmipv4-like
implementation is an interesting step on the road to formulating a
proposed standard in this area, but I believe some more experience
with both would be good before taking the next step.

	Henrik


> http://www.ietf.org/internet-drafts/draft-ietf-mobileip-lowlatency-handoffs-v4-09.txt
> 
> and
> 
> http://www.ietf.org/internet-drafts/draft-koodli-fmipv4-00.txt
> 


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


From mip4-bounces@ietf.org  Fri Mar 18 16:17:10 2005
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 QAA07222
	for <mip4-web-archive@ietf.org>; Fri, 18 Mar 2005 16:17:10 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DCOul-0002yg-Ll
	for mip4-web-archive@ietf.org; Fri, 18 Mar 2005 16:21:51 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DCOFR-0002Jh-KJ; Fri, 18 Mar 2005 15:39:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DCOFQ-0002Jc-Rp
	for mip4@megatron.ietf.org; Fri, 18 Mar 2005 15:39:08 -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 PAA24657
	for <mip4@ietf.org>; Fri, 18 Mar 2005 15:39:06 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DCOJv-0006bp-Js
	for mip4@ietf.org; Fri, 18 Mar 2005 15:43:49 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-1.cisco.com with ESMTP; 18 Mar 2005 12:55:57 -0800
X-IronPort-AV: i="3.91,102,1110182400"; 
	d="scan'208"; a="620977986:sNHT26489936"
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j2IKcqZV025479;
	Fri, 18 Mar 2005 12:38:53 -0800 (PST)
Received: from kleung-w2k01.cisco.com (sjc-vpn4-961.cisco.com [10.21.83.192])
	by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with ESMTP id BDB09896;
	Fri, 18 Mar 2005 12:38:51 -0800 (PST)
Message-Id: <4.3.2.7.2.20050318123303.02cc0920@mira-sjcm-2.cisco.com>
X-Sender: kleung@mira-sjcm-2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 18 Mar 2005 12:38:51 -0800
To: Narayanan Vidya-CVN065 <vidya@motorola.com>
From: Kent Leung <kleung@cisco.com>
Subject: RE: [Mip4] Request to consider FMIPv4 as a working group
  document
In-Reply-To: <1B631E11D496D711BB2800065BFCB6A10C97790C@il02exm13>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>,
        "Charles E.Perkins" <charliep@iprg.nokia.com>,
        Rajeev Koodli <rajeev.koodli@nokia.com>
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464

Oops, I missed one of your comments.

At 01:41 PM 3/18/2005 -0600, Narayanan Vidya-CVN065 wrote:
>Hi Kent,
>What you are implying here seems to be that in order to have a fast 
>handoff solution, the MN must be using an FA CoA - did I get that right?
>
>If so, that seems a little restrictive to me. There are scenarios where 
>the MN may be using a CCoA and registering through an FA.


Hmm, I haven't seen a deployment case for this scenario.  My main point is to
focus activities around deployments, which is a charter item.  As such 
needs arise,
we can address them then.  Just trying to simplify document.

Kent


--
      |           |                   Kent Leung
     :|:         :|:                  IP Mobility Development
    :|||:       :|||:                 Internet Technologies Division
   :|||||||:   :|||||||:              Voice: 408.526.5030
.:|||||||||:.:|||||||||:.             Fax:   408.525.1653
  c i s c o S y s t e m s             Email: kleung@cisco.com

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


From mip4-bounces@ietf.org  Fri Mar 18 16:24:26 2005
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 QAA09907
	for <mip4-web-archive@ietf.org>; Fri, 18 Mar 2005 16:24:26 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DCP1o-0003tP-9C
	for mip4-web-archive@ietf.org; Fri, 18 Mar 2005 16:29:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DCOhM-0006BS-J5; Fri, 18 Mar 2005 16:08:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DCOhK-0006B1-Uk
	for mip4@megatron.ietf.org; Fri, 18 Mar 2005 16:07:58 -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 QAA03747
	for <mip4@ietf.org>; Fri, 18 Mar 2005 16:07:56 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DCOlq-0001gJ-Np
	for mip4@ietf.org; Fri, 18 Mar 2005 16:12:39 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-2.cisco.com with ESMTP; 18 Mar 2005 13:07:46 -0800
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j2IL7bgE007617;
	Fri, 18 Mar 2005 13:07:38 -0800 (PST)
Received: from kleung-w2k01.cisco.com (sjc-vpn4-961.cisco.com [10.21.83.192])
	by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with ESMTP id BDB13615;
	Fri, 18 Mar 2005 13:07:41 -0800 (PST)
Message-Id: <4.3.2.7.2.20050318123917.030084b8@mira-sjcm-2.cisco.com>
X-Sender: kleung@mira-sjcm-2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 18 Mar 2005 13:07:41 -0800
To: "Charles E. Perkins" <charliep@iprg.nokia.com>
From: Kent Leung <kleung@cisco.com>
Subject: Re: [Mip4] Request to consider FMIPv4 as a working group 
  document
In-Reply-To: <423B380A.4000302@iprg.nokia.com>
References: <4.3.2.7.2.20050318083546.0305f100@mira-sjcm-2.cisco.com>
	<4.3.2.7.2.20050318083546.0305f100@mira-sjcm-2.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>,
        Rajeev Koodli <rajeev.koodli@nokia.com>
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15

At 12:20 PM 3/18/2005 -0800, Charles E. Perkins wrote:


>>   - Key difference between MIPv4 and MIPv6 is FA existence.
>
>Well -- there are route optimization details and additional security
>features that are also key differences...  But these are not necessarily
>relevant to FMIPv4.


The relevance is in the next point of scoping the solution space.


>>  - FMIPv4 enabled ARs not being FAs is unlikely, IMHO.  So
>>    we can simplify by specifying only FA mode operation, no CCoA
>>    support needed since ARs would have to be MIPv4 enabled.
>>    This would fit the deployment model and clean up most of
>>    draft dealing with IP address management.
>
>I think it is reasonable to have an access router that is not
>a foreign agent.  Specifying that operation does not seem to
>complicate the rest of the specification which relates to the
>case of AR == FA.  So, I don't see any reason to take out
>that part of the specification, and it could be useful.


My point here is that "Is it realistic to upgrade the access router
with Mobile IP fast HO function w/o FA?"  Why would a network
deploy MIP and upgrade the IPv4 access router to aid Mobile
IP clients for handover and not perform FA service?  I believe
if only FA mode is supported, the draft would be simpler to
understand and implement.  Maybe I should write up a
narrow-minded version? ;)


>>  - Support for fast handover in WiFi already exists today w/o
>>    MIPv4 involvement.  Therefore, realizing deployments using
>>    this type of scheme will be difficult.
>
>Even WiFi access points or access point controllers might
>well implement this feature, especially for the case of
>heterogeneous media.


I don't see why since solution already works and end users don't care
if Mobile IP is used or not to obtain fast handover.  I think some
of the concepts in the draft are useful in practice.

Kent
--
      |           |                   Kent Leung
     :|:         :|:                  IP Mobility Development
    :|||:       :|||:                 Internet Technologies Division
   :|||||||:   :|||||||:              Voice: 408.526.5030
.:|||||||||:.:|||||||||:.             Fax:   408.525.1653
  c i s c o S y s t e m s             Email: kleung@cisco.com

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


From mip4-bounces@ietf.org  Fri Mar 18 16:25:45 2005
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 QAA10339
	for <mip4-web-archive@ietf.org>; Fri, 18 Mar 2005 16:25:45 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DCP34-00047s-1Y
	for mip4-web-archive@ietf.org; Fri, 18 Mar 2005 16:30:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DCOc6-0003J2-Ci; Fri, 18 Mar 2005 16:02:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DCOc4-0003Ii-5L
	for mip4@megatron.ietf.org; Fri, 18 Mar 2005 16:02:32 -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 QAA01868
	for <mip4@ietf.org>; Fri, 18 Mar 2005 16:02:29 -0500 (EST)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DCOgZ-00010B-B7
	for mip4@ietf.org; Fri, 18 Mar 2005 16:07:12 -0500
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j2ILWWU25362;
	Fri, 18 Mar 2005 13:32:32 -0800
X-mProtect: <200503182132> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp14155.americas.nokia.com (172.18.141.55,
	claiming to be "[172.18.141.55]")
	by darkstar.iprg.nokia.com smtpdLOd39D; Fri, 18 Mar 2005 13:32:30 PST
Message-ID: <423B41CF.10603@iprg.nokia.com>
Date: Fri, 18 Mar 2005 13:02:07 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mip4@ietf.org, karim.el-malki@ericsson.com
References: <95C69691E3067248918990C7214854B59E883D@mvebe001.americas.nokia.com>
In-Reply-To: <95C69691E3067248918990C7214854B59E883D@mvebe001.americas.nokia.com>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: e3ebaaff3b3539efaf29ef65eea2aded
Subject: [Mip4] Re: Differences between Low Latency Handovers and FMIPv4
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>
Content-Type: multipart/mixed; boundary="===============0918504945=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 9aa22b77adc37e7d33e29644e4dc0b33

This is a multi-part message in MIME format.
--===============0918504945==
Content-Type: multipart/alternative;
	boundary="------------020109080203070403010704"

This is a multi-part message in MIME format.
--------------020109080203070403010704
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


Hi Karim,

We implemented the FMIPv6 spec and got the performance
we were looking for. When we considered IPv4, we did not
want to change the L2 to provide L3 subnet information,
what LLH provides in various L2-*T style of triggers,
since that would have limited our implementation to a single L2 alone.
We think making changes to L2 is not desirable.

With that, we set out to implement FMIPv4 by simply changing
the packet formats for FMIPv6, which does not require L2 to
provide the L3 information, and hence easy to implement on any
L2. With our FMIPv4, we got the performance we were
looking for real-time voice handover. See Charlie's presentation
at the DC IETF meeting. So, what we are asking is to standardize
the packet formats for IPv4 using the FMIPv6 design which, contrary
to what you suggest, has crucial differences with respect to LLH
(see the list below) although one could also find some similarities.

Finally, our experience is that those who implement FMIPv6 will find
FMIPv4 rather straightforward to implement since the design is identical and
provides the required performance.

Some comments in-line.. Also, please see the list of differences
we put together, which suggests major differences that exist
in the design.

Regards,

-Rajeev

>Following Henrik's note I'll expand on the technical
>issues. As I wrote in my previous email I cannot quite
>see the major difference between these drafts. Your new
>draft considers link-layer triggers just as FMIPv6 and Low
>Latency in order to improve performance. You describe AP
>  
>
Actually no. Both FMIPv6 and FMIPv4 do not derive L3 information
(nFA's IP address, MN's IP address, their MAC addresses etc.) from the
L2 triggers. This is a big difference since they do not require L2's
to be changed. Please see 3) below.

>scanning etc. which is not different from the existing
>approach. An IP interface becoming available is just a
>way of implementing a mobile trigger right? You describe
>  
>
We did not suggest AP scanning as a difference since _any_ handover protocol
over WLAN has to deal with it. So, it is not essential for discussion here.
Using an "interface up" is hugely different from "provide L3 info from L2"
type of trigger. The former is available without requiring changes to 
L2. The
latter is not, and would require changes to L2. To be clear, FMIPv6 does 
not
tie the protocol operation to L2 triggers at all, leaving implementers 
to use
whatever is available.

>tunnelling between FAs which is covered by the pre-reg/post-reg.
>combination scenario in Low Latency.
>  
>
The tunnel set up can be lot simpler than having to run pre-reg/post-reg in
combination :-) This is a reflection from implementing FMIPv4
while trying to understand LLH however.

>One other mechanism was however pointed out a while back: sending
>the mobile registration to create the FA-FA tunnel AFTER L2
>handoff. I assume that this is the mechanism you want to add
>since the advantages you note below are applicable to that
>scenario? This wasn't covered in low latency because it was covered
>  
>
Without a tunnel subsequent to L2 switching, you don't have the reactive 
handover.

>by the PFANE mechanism in route optv4. Have you considered PFANE?
>I think the rest is covered already by pre-reg, post-reg and the
>combined mechanism.
>  
>
What we are looking for is a way to use FMIPv6 design using IPv4.
This is necessary to enable us to use FMIPv6 and FMIPv4 together in 
environments
where changes to L2 are not necessary nor are required.


>/Karim
>
>-----Original Message-----
>From: mip4-bounces@ietf.org
>To: Mobile IPv4 Mailing List
>Cc: Rajeev Koodli
>Sent: 2005-03-18 00:47
>Subject: [Mip4] Differences between Low Latency Handovers and FMIPv4
>
>Hello folks,
>
>FMIPv4 is a straightforward adaptation of the
>Fast Handovers for Mobile IPv6 specification. 
>The intention is to utilize the same design for
>IPv4 networks, but that requires different 
>packet formats.  We would like the [mip4] WG
>to standardize these packet formats.  Both the
>FMIPv6 and FMIPv4 draft mentioned here have been
>implemented and offer the performance needed for 
>real-time handovers.  Below, we offer a list of
>some differences between our FMIPv4 spec and
>the previously published Low Latency Handovers
>("LLH") specification for Mobile IPv4.
>
>1) We believe that FMIPv4 will avoid the pitfalls
>   documented in the paper from Kempf et al.
>   which were described quite a while back.
>
>2) Tight coupling to L2 triggers: The entire LLH
>   process is very tightly coupled to L2 triggers, to the
>   extent that the protocol does not work without such
>   triggers.  In contrast, FMIPv4 can make use of such
>   triggers, but entire protocol operation does not
>   depend on the availability and tight coupling of L2
>   triggers.  For instance, the standard Linux function
>   ll_handoff() indicates to IP layer that an interface
>   has become available.  FMIPv4 code for FBU from the new
>   link can be invoked within ll_handoff().
>
>3) Changes to L2 triggers: In addition to the reliance
>   on L2 triggers in LLH, the triggers themselves need to
>   be modified to include parameters such as new FA IP
>   address, MN IP address, their MAC addresses etc.
>   within the triggers themselves.  This would require
>   changes to whatever L2 triggers are available on _all_
>   links where such triggers are supported. 
> 
>   This is not at all required for FMIPv4 operation.
>   Nor does the spec recommend such changes.
> 
>4) The number of messages exchanged during handover:  
>   4.a) Pre-reg LLH: 
>   All the messages between the MN and FAs are exchanged 
>   once the trigger event occurs.  This includes two proxy
>   router messages and a registration request and 
>   possibly registration reply on the old link.  In
>   FMIPv4, a single message (FBU) is sent once the 
>   decision to undergo handover is made.  The MN need not
>   stay on the old link once FBU is sent. 
>   4.b) Post-reg LLH: 
>   No messages are exchanged between the MN and FA. 
>   However, since the MN does not have means to change 
>   the default router, it will continue to send packets 
>   from the new link to the oFA's MAC address, which 
>   should be dropped by the IP stack.  And, consideration
>   (3) above applies; the triggers on oFA and nFA must
>   contain MN's IP addresses, necessitating changes to L2 
>   where the protocol might be useful.  Plus, such a mode
>   "defers" MIPv4 operation, which is additional code on 
>   the MN. 
>   
>   FMIPv4 works without imposing restrictions on when
>   MIPv4 protocol messages need to be carried out.
>
>5) Changes to MIPv4 operation: The MN changes its
>   default access router once the registration reply is
>   received in pre-reg LLH even if the MN is still on the
>   oFA.  So, packet forwarding needs to be carefully
>   constructed. (In post-reg LLH on the other hand, the
>   MN does not change its default router at all, even
>   though it is on the nFA.  This leads to different set
>   of additional considerations).
>
>   In FMIPv4, no changes to default router processing are
>   needed.  That is, the MN is free to perform and process
>   agent/router advertisements just as any normal
>   (mobile) node would.
>
>6) Protocol design: The FMIPv4 protocol clearly
>   separates movement detection, IP address and nFA
>   configuration, and registration request phases.  None
>   of these phases is in the critical time path.  The only
>   message that is on the criticial path is the FBU
>   message.  For movement detection and IP/nFA
>   configuration, the FMIPv4 protocol uses the Proxy
>   Router messages, which are exchanged ahead of
>   handover, as opposed to intitiating the handover in
>   LLH.  There are quite a few other differences to list
>   here.
>
>In summary, Rajeev and I believe that the differences are
>important enough to consider a separate spec of choice
>to implementors.  It is especially appealing to those
>considering FMIPv6 as well.
>
>Regards,
>Charlie P.
>
>  
>

--------------020109080203070403010704
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
<br>
Hi Karim,<br>
<br>
We implemented the FMIPv6 spec and got the performance<br>
we were looking for. When we considered IPv4, we did not<br>
want to change the L2 to provide L3 subnet information,<br>
what LLH provides in various L2-*T style of triggers, <br>
since that would have limited our implementation to a single L2 alone. <br>
We think making changes to L2 is not desirable. <br>
<br>
With that, we set out to implement FMIPv4 by simply changing<br>
the packet formats for FMIPv6, which does not require L2 to<br>
provide the L3 information, and hence easy to implement on any<br>
L2. With our FMIPv4, we got the performance we were<br>
looking for real-time voice handover. See Charlie's presentation<br>
at the DC IETF meeting. So, what we are asking is to standardize<br>
the packet formats for IPv4 using the FMIPv6 design which, contrary<br>
to what you suggest, has crucial differences with respect to LLH
<br>
(see the list below) although one could also find some similarities. <br>
<br>
Finally, our experience is that those who implement FMIPv6 will find<br>
FMIPv4 rather straightforward to implement since the design is
identical and<br>
provides the required performance. <br>
<br>
Some comments in-line.. Also, please see the list of differences<br>
we put together, which suggests major differences that exist<br>
in the design. <br>
<br>
Regards,<br>
<br>
-Rajeev<br>
<br>
<blockquote
 cite="mid95C69691E3067248918990C7214854B59E883D@mvebe001.americas.nokia.com"
 type="cite">
  <pre wrap="">Following Henrik's note I'll expand on the technical
issues. As I wrote in my previous email I cannot quite
see the major difference between these drafts. Your new
draft considers link-layer triggers just as FMIPv6 and Low
Latency in order to improve performance. You describe AP
  </pre>
</blockquote>
Actually no. Both FMIPv6 and FMIPv4 do not derive L3 information<br>
(nFA's IP address, MN's IP address, their MAC addresses etc.) from the<br>
L2 triggers. This is a big difference since they do not require L2's<br>
to be changed. Please see 3) below.<br>
<br>
<blockquote
 cite="mid95C69691E3067248918990C7214854B59E883D@mvebe001.americas.nokia.com"
 type="cite">
  <pre wrap="">scanning etc. which is not different from the existing
approach. An IP interface becoming available is just a
way of implementing a mobile trigger right? You describe
  </pre>
</blockquote>
We did not suggest AP scanning as a difference since _any_ handover
protocol<br>
over WLAN has to deal with it. So, it is not essential for discussion
here.<br>
Using an "interface up" is hugely different from "provide L3 info from
L2"<br>
type of trigger. The former is available without requiring changes to
L2. The <br>
latter is not, and would require changes to L2. To be clear, FMIPv6
does not <br>
tie the protocol operation to L2 triggers at all, leaving implementers
to use <br>
whatever is available. <br>
<blockquote
 cite="mid95C69691E3067248918990C7214854B59E883D@mvebe001.americas.nokia.com"
 type="cite">
  <pre wrap="">tunnelling between FAs which is covered by the pre-reg/post-reg.
combination scenario in Low Latency.
  </pre>
</blockquote>
The tunnel set up can be lot simpler than having to run
pre-reg/post-reg in<br>
combination :-) This is a reflection from implementing FMIPv4 <br>
while trying to understand LLH however. <br>
<blockquote
 cite="mid95C69691E3067248918990C7214854B59E883D@mvebe001.americas.nokia.com"
 type="cite">
  <pre wrap="">One other mechanism was however pointed out a while back: sending
the mobile registration to create the FA-FA tunnel AFTER L2
handoff. I assume that this is the mechanism you want to add
since the advantages you note below are applicable to that
scenario? This wasn't covered in low latency because it was covered
  </pre>
</blockquote>
Without a tunnel subsequent to L2 switching, you don't have the
reactive handover.<br>
<br>
<blockquote
 cite="mid95C69691E3067248918990C7214854B59E883D@mvebe001.americas.nokia.com"
 type="cite">
  <pre wrap="">by the PFANE mechanism in route optv4. Have you considered PFANE?
I think the rest is covered already by pre-reg, post-reg and the
combined mechanism.
  </pre>
</blockquote>
What we are looking for is a way to use FMIPv6 design using IPv4.<br>
This is necessary to enable us to use FMIPv6 and FMIPv4 together in
environments<br>
where changes to L2 are not necessary nor are required. <br>
<br>
<br>
<blockquote
 cite="mid95C69691E3067248918990C7214854B59E883D@mvebe001.americas.nokia.com"
 type="cite">
  <pre wrap="">/Karim

-----Original Message-----
From: <a
 class="moz-txt-link-abbreviated" href="mailto:mip4-bounces@ietf.org">mip4-bounces@ietf.org</a>
To: Mobile IPv4 Mailing List
Cc: Rajeev Koodli
Sent: 2005-03-18 00:47
Subject: [Mip4] Differences between Low Latency Handovers and FMIPv4

Hello folks,

FMIPv4 is a straightforward adaptation of the
Fast Handovers for Mobile IPv6 specification. 
The intention is to utilize the same design for
IPv4 networks, but that requires different 
packet formats.  We would like the [mip4] WG
to standardize these packet formats.  Both the
FMIPv6 and FMIPv4 draft mentioned here have been
implemented and offer the performance needed for 
real-time handovers.  Below, we offer a list of
some differences between our FMIPv4 spec and
the previously published Low Latency Handovers
("LLH") specification for Mobile IPv4.

1) We believe that FMIPv4 will avoid the pitfalls
   documented in the paper from Kempf et al.
   which were described quite a while back.

2) Tight coupling to L2 triggers: The entire LLH
   process is very tightly coupled to L2 triggers, to the
   extent that the protocol does not work without such
   triggers.  In contrast, FMIPv4 can make use of such
   triggers, but entire protocol operation does not
   depend on the availability and tight coupling of L2
   triggers.  For instance, the standard Linux function
   ll_handoff() indicates to IP layer that an interface
   has become available.  FMIPv4 code for FBU from the new
   link can be invoked within ll_handoff().

3) Changes to L2 triggers: In addition to the reliance
   on L2 triggers in LLH, the triggers themselves need to
   be modified to include parameters such as new FA IP
   address, MN IP address, their MAC addresses etc.
   within the triggers themselves.  This would require
   changes to whatever L2 triggers are available on _all_
   links where such triggers are supported. 
 
   This is not at all required for FMIPv4 operation.
   Nor does the spec recommend such changes.
 
4) The number of messages exchanged during handover:  
   4.a) Pre-reg LLH: 
   All the messages between the MN and FAs are exchanged 
   once the trigger event occurs.  This includes two proxy
   router messages and a registration request and 
   possibly registration reply on the old link.  In
   FMIPv4, a single message (FBU) is sent once the 
   decision to undergo handover is made.  The MN need not
   stay on the old link once FBU is sent. 
   4.b) Post-reg LLH: 
   No messages are exchanged between the MN and FA. 
   However, since the MN does not have means to change 
   the default router, it will continue to send packets 
   from the new link to the oFA's MAC address, which 
   should be dropped by the IP stack.  And, consideration
   (3) above applies; the triggers on oFA and nFA must
   contain MN's IP addresses, necessitating changes to L2 
   where the protocol might be useful.  Plus, such a mode
   "defers" MIPv4 operation, which is additional code on 
   the MN. 
   
   FMIPv4 works without imposing restrictions on when
   MIPv4 protocol messages need to be carried out.

5) Changes to MIPv4 operation: The MN changes its
   default access router once the registration reply is
   received in pre-reg LLH even if the MN is still on the
   oFA.  So, packet forwarding needs to be carefully
   constructed. (In post-reg LLH on the other hand, the
   MN does not change its default router at all, even
   though it is on the nFA.  This leads to different set
   of additional considerations).

   In FMIPv4, no changes to default router processing are
   needed.  That is, the MN is free to perform and process
   agent/router advertisements just as any normal
   (mobile) node would.

6) Protocol design: The FMIPv4 protocol clearly
   separates movement detection, IP address and nFA
   configuration, and registration request phases.  None
   of these phases is in the critical time path.  The only
   message that is on the criticial path is the FBU
   message.  For movement detection and IP/nFA
   configuration, the FMIPv4 protocol uses the Proxy
   Router messages, which are exchanged ahead of
   handover, as opposed to intitiating the handover in
   LLH.  There are quite a few other differences to list
   here.

In summary, Rajeev and I believe that the differences are
important enough to consider a separate spec of choice
to implementors.  It is especially appealing to those
considering FMIPv6 as well.

Regards,
Charlie P.

  </pre>
</blockquote>
</body>
</html>

--------------020109080203070403010704--


--===============0918504945==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0918504945==--



From mip4-bounces@ietf.org  Fri Mar 18 16:26:55 2005
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 QAA10738
	for <mip4-web-archive@ietf.org>; Fri, 18 Mar 2005 16:26:55 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DCP4D-0004E8-Q0
	for mip4-web-archive@ietf.org; Fri, 18 Mar 2005 16:31:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DCOzg-0000DN-50; Fri, 18 Mar 2005 16:26:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DCOze-0000Cu-TR
	for mip4@megatron.ietf.org; Fri, 18 Mar 2005 16:26:55 -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 QAA10712
	for <mip4@ietf.org>; Fri, 18 Mar 2005 16:26:52 -0500 (EST)
Received: from wsip-68-101-41-112.dc.dc.cox.net ([68.101.41.112]
	helo=email-filesrv) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DCP4A-0004D9-LN
	for mip4@ietf.org; Fri, 18 Mar 2005 16:31:35 -0500
Received: from [198.57.19.100] by email-filesrv
	(ArGoSoft Mail Server Pro for WinNT/2000/XP, Version 1.8 (1.8.1.7));
	Fri, 18 Mar 2005 15:59:40 -0500
Message-ID: <005d01c52c01$3a69f860$2101a8c0@us.nextel.com>
From: "Qiang Zhang/Aber" <qzhang@aber-networks.net>
To: <sami.vaarala@iki.fi>, "Mobile IPv4 Mailing List " <mip4@ietf.org>
Subject: Re: [nemo] Re: [Mip4] NAT traversal and cellular network
	administrative filtering
Date: Fri, 18 Mar 2005 16:27:00 -0500
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 3.4 (+++)
X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593
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>
Content-Type: multipart/mixed; boundary="===============1630226479=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 3.4 (+++)
X-Scan-Signature: 1449ead51a2ff026dcb23465f5379250

This is a multi-part message in MIME format.

--===============1630226479==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_005A_01C52BD7.4F6C2E60"

This is a multi-part message in MIME format.

------=_NextPart_000_005A_01C52BD7.4F6C2E60
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Sami,I am not T-mobile :)It is becoming a trend when providers look for =
data revenues, service selectionmechanisms are being deployed to =
distinguish/charge the byte usages and perform authorizations. The Idea =
to block IP-IP is not the right way to combat worms :) a deep inspection =
is.I am curious which service plan iVincic was referring to and whether =
T-mobile blocks all IP-IP in all different data plansQiangAlexandru,

It may be the case that operator forbids IP-IP because IP-IP has the
potential to deny the effectiveness of all other firewall filtering
rules that may be in place (rules acting on IP, not IP-in-IP - acting on
IP-in-IP requires more processing time which may be detrimental to
performance).
Not only processing time, but depending on the firewall architecture
it may be easy, hard, or impossible to peer into IP-IP (or IP-IP-IP,
IP-over-PPP-over-L2TP etc).In this sense, IP-IP may "escape" the normal
policy mechanism.

On the other hand you need a remote IP-IP endpoint for decapsulation,
and if you have that, you may escape the normal policy anyway by using
any of the dozen available tunneling tools out there.

At the same time, operator may allow certain UDP tunneling to pass
through because that operator may have agreements with Content Providers
that are placed outside that operator's network.  "Content" may be video
streaming over UDP.  So operator assumes that UDP mms port 1755
(Microsoft Multimedia Streaming) should pass through, and keeps it open.
>=20
Just a potential explanation, and it's pure speculation, and it may be
far from the actual motivation of T-Mobile filtering rules.
Right.  It may well be that operator X (in general) may want to block
IP-IP but is accidentally letting IP-over-UDP pass because of lacking
support in firewalls to prevent it.  Bypassing that policy using forced
UDP encapsulation is not necessarily very nice (from the operator's
viewpoint), but we lack the common tools to let the operator make this
policy decision.

However, in this case it seemed to me that the effects on normal MIP4
were a side-effect of a response to a perceived threat, not a deliberate
policy to block MIP4.

Best,

-Sami

--
Mip4 mailing list: Mip4 at 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/            
------=_NextPart_000_005A_01C52BD7.4F6C2E60
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1491" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2><PRE style=3D"MARGIN: =
0em">Sami,</PRE><PRE style=3D"MARGIN: 0em">&nbsp;</PRE><PRE =
style=3D"MARGIN: 0em">I am not T-mobile :)</PRE><PRE style=3D"MARGIN: =
0em">&nbsp;</PRE><PRE style=3D"MARGIN: 0em">It is becoming a trend when =
providers look for data revenues, service selection</PRE><PRE =
style=3D"MARGIN: 0em">mechanisms are being deployed to =
distinguish/charge the byte usages and perform authorizations. =
</PRE><PRE style=3D"MARGIN: 0em">&nbsp;</PRE><PRE style=3D"MARGIN: =
0em">The Idea to block IP-IP is not the right way to combat worms :) a =
deep inspection is.</PRE><PRE style=3D"MARGIN: 0em">&nbsp;</PRE><PRE =
style=3D"MARGIN: 0em">I am curious which service plan iVincic was =
referring to and whether T-mobile blocks all IP-IP in </PRE><PRE =
style=3D"MARGIN: 0em">all different data plans</PRE><PRE =
style=3D"MARGIN: 0em">&nbsp;</PRE><PRE style=3D"MARGIN: =
0em">&nbsp;</PRE><PRE style=3D"MARGIN: 0em">Qiang</PRE><PRE =
style=3D"MARGIN: 0em">&nbsp;</PRE><PRE style=3D"MARGIN: =
0em">&nbsp;</PRE><PRE style=3D"MARGIN: 0em">Alexandru,</PRE><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 0.85em; MARGIN: 0em; BORDER-LEFT: #5555ee 0.2em =
solid"><PRE style=3D"MARGIN: 0em">It may be the case that operator =
forbids IP-IP because IP-IP has the
potential to deny the effectiveness of all other firewall filtering
rules that may be in place (rules acting on IP, not IP-in-IP - acting on
IP-in-IP requires more processing time which may be detrimental to
performance).
</PRE></BLOCKQUOTE><PRE style=3D"MARGIN: 0em"><BR>Not only processing =
time, but depending on the firewall architecture
it may be easy, hard, or impossible to peer into IP-IP (or IP-IP-IP,
IP-over-PPP-over-L2TP etc).In this sense, IP-IP may "escape" the normal
policy mechanism.</PRE><BR><PRE style=3D"MARGIN: 0em">On the other hand =
you need a remote IP-IP endpoint for decapsulation,
and if you have that, you may escape the normal policy anyway by using
any of the dozen available tunneling tools out there.</PRE><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 0.85em; MARGIN: 0em; BORDER-LEFT: #5555ee 0.2em =
solid"><PRE style=3D"MARGIN: 0em">At the same time, operator may allow =
certain UDP tunneling to pass
through because that operator may have agreements with Content Providers
that are placed outside that operator's network.  "Content" may be video
streaming over UDP.  So operator assumes that UDP mms port 1755
(Microsoft Multimedia Streaming) should pass through, and keeps it open.
</PRE></BLOCKQUOTE><TT>&gt; </TT>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 0.85em; MARGIN: 0em; BORDER-LEFT: #5555ee 0.2em =
solid"><PRE style=3D"MARGIN: 0em">Just a potential explanation, and it's =
pure speculation, and it may be
far from the actual motivation of T-Mobile filtering rules.
</PRE></BLOCKQUOTE><PRE style=3D"MARGIN: 0em"><BR>Right.  It may well be =
that operator X (in general) may want to block
IP-IP but is accidentally letting IP-over-UDP pass because of lacking
support in firewalls to prevent it.  Bypassing that policy using forced
UDP encapsulation is not necessarily very nice (from the operator's
viewpoint), but we lack the common tools to let the operator make this
policy decision.</PRE><BR><PRE style=3D"MARGIN: 0em">However, in this =
case it seemed to me that the effects on normal MIP4
were a side-effect of a response to a perceived threat, not a deliberate
policy to block MIP4.</PRE><BR><PRE style=3D"MARGIN: =
0em">Best,</PRE><BR><PRE style=3D"MARGIN: 0em">-Sami</PRE><BR><PRE =
style=3D"MARGIN: 0em">--
Mip4 mailing list: Mip4 at ietf.org
   Web interface: <A =
href=3D"https://www1.ietf.org/mailman/listinfo/mip4">https://www1.ietf.or=
g/mailman/listinfo/mip4</A>
    Charter page: <A =
href=3D"http://www.ietf.org/html.charters/mip4-charter.html">http://www.i=
etf.org/html.charters/mip4-charter.html</A>
Supplemental site: <A =
href=3D"http://www.mip4.org/">http://www.mip4.org/</A>&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; </PRE></FONT></DIV></BODY></HTML>

------=_NextPart_000_005A_01C52BD7.4F6C2E60--




--===============1630226479==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1630226479==--





From mip4-bounces@ietf.org  Fri Mar 18 17:32:50 2005
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 RAA16294
	for <mip4-web-archive@ietf.org>; Fri, 18 Mar 2005 17:32:50 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DCQ62-0006s7-Mx
	for mip4-web-archive@ietf.org; Fri, 18 Mar 2005 17:37:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DCPyv-0002cA-Oy; Fri, 18 Mar 2005 17:30:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DCPyt-0002bz-OT
	for mip4@megatron.ietf.org; Fri, 18 Mar 2005 17:30:11 -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 RAA15828
	for <mip4@ietf.org>; Fri, 18 Mar 2005 17:30:08 -0500 (EST)
Received: from mail.birdstep.com ([80.239.52.35])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DCQ3P-0006lQ-8l
	for mip4@ietf.org; Fri, 18 Mar 2005 17:34:52 -0500
Received: from HPTRYBUY (ti211110a080-3144.bb.online.no [85.165.76.72])
	(authenticated bits=0)
	by mail.birdstep.com (8.12.8/8.12.8) with ESMTP id j2IMTwGa007066
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO);
	Fri, 18 Mar 2005 23:29:59 +0100
Message-Id: <200503182229.j2IMTwGa007066@mail.birdstep.com>
From: "Espen Klovning" <espen@birdstep.com>
To: "'Charles E.Perkins'" <charliep@iprg.nokia.com>,
        "'Mobile IPv4 Mailing List'" <mip4@ietf.org>
Subject: RE: [Mip4] Request to consider FMIPv4 as a working group document
Date: Fri, 18 Mar 2005 23:30:03 +0100
Organization: Birdstep Technology ASA
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <4239FC52.33760051@iprg.nokia.com>
Thread-Index: AcUrPAmoSCVXOdaxSy2rer/dt/XmpAAyOFTw
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Content-Transfer-Encoding: 7bit
Cc: "'Rajeev Koodli'" <rajeev.koodli@nokia.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: espen@birdstep.com
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Content-Transfer-Encoding: 7bit

Hi Charlie

I support making this draft a WG item.

I do have some concerns that more or less reflect what Kent Leung has voiced
in previous mails on the list. 
- AR == FA 
- IP address management

An additional issue is how the MN-PAR auth extension is handled. I take it
this will reuse MN-FA auth extension. It will require key distribution of
some kind that could jeopardize the performance benefits. What am I missing?

regards
espen
Espen Klovning
Birdstep Technology


In addition, 

> -----Original Message-----
> From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of
> Charles E.Perkins
> Sent: Thursday, March 17, 2005 10:53 PM
> To: Mobile IPv4 Mailing List
> Cc: Rajeev Koodli
> Subject: [Mip4] Request to consider FMIPv4 as a working group document
> 
> 
> 
> Hello folks,
> 
> We made a presentation at IETF 61 about a way to do
> fast handovers with Mobile IPv4.  Our method is adapted
> from the protocol for Mobile IPv6,
>      draft-ietf-mipshop-fast-mipv6-03.txt
> 
> The Mobile IPv6 protocol has been approved for
> publication and is currently in the RFC editor's
> queue.
> 
> The discussion at IETF 61 can be reviewed from the
> minutes, located at:
> http://www1.ietf.org/proceedings_new/04nov/toc.html#int
> 
> As part of this discussion, I showed some results which
> indicate very good performance for FMIPv4, suitable for
> handling interactive voice applications.  I probably have
> the PowerPoint presentation around somewhere if needed.
> 
> The protocol specification for the Mobile IPv4 fast
> handovers is documented in the Internet Draft:
>      draft-koodli-fmipv4-00.txt
> which is available in the standard IETF draft
> directories.
> 
> Thanks in advance for your consideration of our
> request.
> 
> Regards,
> Charlie P.
> 
> --
> 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/


From mip4-bounces@ietf.org  Fri Mar 18 18:10:05 2005
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 SAA20862
	for <mip4-web-archive@ietf.org>; Fri, 18 Mar 2005 18:10:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DCQg5-0008OV-OL
	for mip4-web-archive@ietf.org; Fri, 18 Mar 2005 18:14:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DCQaM-0003ao-St; Fri, 18 Mar 2005 18:08:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DCQaL-0003ag-Bc
	for mip4@megatron.ietf.org; Fri, 18 Mar 2005 18:08:53 -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 SAA20713
	for <mip4@ietf.org>; Fri, 18 Mar 2005 18:08:50 -0500 (EST)
Received: from motgate.mot.com ([129.188.136.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DCQes-0008NC-AX
	for mip4@ietf.org; Fri, 18 Mar 2005 18:13:34 -0500
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234])
	by motgate.mot.com (Motorola/Motgate) with ESMTP id j2IN8p99010229
	for <mip4@ietf.org>; Fri, 18 Mar 2005 16:08:51 -0700 (MST)
Received: from il02exm13.corp.mot.com (il02exm13.corp.mot.com [10.0.111.24])
	by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id j2IN9a4s024331
	for <mip4@ietf.org>; Fri, 18 Mar 2005 17:09:37 -0600 (CST)
Received: by il02exm13 with Internet Mail Service (5.5.2657.72)
	id <D3S2RV6V>; Fri, 18 Mar 2005 17:08:50 -0600
Message-ID: <1B631E11D496D711BB2800065BFCB6A10C977916@il02exm13>
From: Narayanan Vidya-CVN065 <vidya@motorola.com>
To: "'Mobile IPv4 Mailing List'" <mip4@ietf.org>
Subject: RE: [Mip4] Request to consider FMIPv4 as a working group document
Date: Fri, 18 Mar 2005 17:08:48 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: "'Rajeev Koodli'" <rajeev.koodli@nokia.com>
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a

All,
Does anyone know what happened to the draft on post-MIT? A few years ago, I thought it was being considered to be part of the low latency handoff spec - but, obviously it has not made it. 

James' draft on Post-MIT was trying to solve the issue of L2 dependency. Essentially, I see this as a major deployment issue to have a fast handoff solution exclusively dependent on receiving an L2 trigger (e.g. the L2 Target Trigger at the nFA). 

I think an approach like FMIPv4 is essential in light of this. Ideally, I think post-MIT should have been a part of LLH - that way, we won't have the need to have 2 specifications that are somewhat close with only minor differences. 

Vidya

-----Original Message-----
From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of Espen Klovning
Sent: Friday, March 18, 2005 4:30 PM
To: 'Charles E.Perkins'; 'Mobile IPv4 Mailing List'
Cc: 'Rajeev Koodli'
Subject: RE: [Mip4] Request to consider FMIPv4 as a working group document


Hi Charlie

I support making this draft a WG item.

I do have some concerns that more or less reflect what Kent Leung has voiced in previous mails on the list. 
- AR == FA 
- IP address management

An additional issue is how the MN-PAR auth extension is handled. I take it this will reuse MN-FA auth extension. It will require key distribution of some kind that could jeopardize the performance benefits. What am I missing?

regards
espen
Espen Klovning
Birdstep Technology


In addition, 

> -----Original Message-----
> From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf 
> Of Charles E.Perkins
> Sent: Thursday, March 17, 2005 10:53 PM
> To: Mobile IPv4 Mailing List
> Cc: Rajeev Koodli
> Subject: [Mip4] Request to consider FMIPv4 as a working group document
> 
> 
> 
> Hello folks,
> 
> We made a presentation at IETF 61 about a way to do
> fast handovers with Mobile IPv4.  Our method is adapted
> from the protocol for Mobile IPv6,
>      draft-ietf-mipshop-fast-mipv6-03.txt
> 
> The Mobile IPv6 protocol has been approved for
> publication and is currently in the RFC editor's
> queue.
> 
> The discussion at IETF 61 can be reviewed from the
> minutes, located at: 
> http://www1.ietf.org/proceedings_new/04nov/toc.html#int
> 
> As part of this discussion, I showed some results which indicate very 
> good performance for FMIPv4, suitable for handling interactive voice 
> applications.  I probably have the PowerPoint presentation around 
> somewhere if needed.
> 
> The protocol specification for the Mobile IPv4 fast
> handovers is documented in the Internet Draft:
>      draft-koodli-fmipv4-00.txt
> which is available in the standard IETF draft
> directories.
> 
> Thanks in advance for your consideration of our
> request.
> 
> Regards,
> Charlie P.
> 
> --
> 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/

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


From mip4-bounces@ietf.org  Sun Mar 20 19:17:16 2005
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 TAA07555
	for <mip4-web-archive@ietf.org>; Sun, 20 Mar 2005 19:17:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDAgc-0007dd-Fa
	for mip4-web-archive@ietf.org; Sun, 20 Mar 2005 19:22:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDAYn-0003Tw-MF; Sun, 20 Mar 2005 19:14:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDAYl-0003To-J3
	for mip4@megatron.ietf.org; Sun, 20 Mar 2005 19:14:19 -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 TAA07398
	for <mip4@ietf.org>; Sun, 20 Mar 2005 19:14:16 -0500 (EST)
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDAdi-0007Yi-6o
	for mip4@ietf.org; Sun, 20 Mar 2005 19:19:27 -0500
Received: from esealmw128.eemea.ericsson.se ([153.88.254.121])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j2L0EAfm029832; Mon, 21 Mar 2005 01:14:10 +0100 (MET)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 21 Mar 2005 01:14:08 +0100
Received: from esealmw115.eemea.ericsson.se ([153.88.200.6]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 21 Mar 2005 01:14:08 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 21 Mar 2005 01:14:06 +0100
Message-ID: <24521B9781EAC745A4BE65966F69C9BE212AAD@esealmw115.eemea.ericsson.se>
Thread-Topic: Differences between Low Latency Handovers and FMIPv4
Thread-index: AcUr/c7W+u4eE/fmRY+POHWDHgF3egBoZGh/
From: "Karim El-Malki \(AL/EAB\)" <karim.el-malki@ericsson.com>
To: "Rajeev Koodli " <rajeev@iprg.nokia.com>, <mip4@ietf.org>
X-OriginalArrivalTime: 21 Mar 2005 00:14:08.0295 (UTC)
	FILETIME=[E6644B70:01C52DAA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4e722e9456ead69ba4cdd21dd3d3600
Content-Transfer-Encoding: quoted-printable
Subject: [Mip4] RE: Differences between Low Latency Handovers and FMIPv4
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8a961490db2a74c7613bf0201229f176
Content-Transfer-Encoding: quoted-printable

Hi Rajeev
I understand your point that you took FMIPv6 and applied
it to v4 to make FMIPv4. But that doesn't make it
substantially different from Low Latency. Your spec does
use link-layer triggers to be able to send the RtSolPr.
An interface coming up in the MN is used just the same in
Low Latency and is defined as a mobile trigger in Low
Latency (L2-LU). PRE-REG involves the MN getting such a
mobile trigger and sending a PrRtSol and receiving a
PrRtAdv. What's the difference compared to your spec?
The messages are even called the same. Nothing special
or L2-dependent about this L2 trigger. For example PRE-REG
can be applied to WLAN using AP scans. I don't think that
the difference in packet formats makes it a substantially
different spec from low latency.  Also, the other case you
are considering involves an L3 handoff that happens after
the MN attaches to the new link. This cannot really be
considered a "fast" handoff, which would instead be where
the handoff happens before or in parallel with the L2 handoff.
This L3-handoff-after-L2-handoff was already covered in the
route optv4 spec using PFANE. You may have missed the question
so I'll repeat it: did you consider the PFANE? Why aren't
you just reusing the PFANE (Previous FA Notification
Extension) work for that scenario?
/Karim

-----Original Message-----
From: Rajeev Koodli
To: mip4@ietf.org; Karim El-Malki (AL/EAB)
Sent: 18/03/2005 22:02
Subject: Re: Differences between Low Latency Handovers and FMIPv4


Hi Karim,

We implemented the FMIPv6 spec and got the performance
we were looking for. When we considered IPv4, we did not
want to change the L2 to provide L3 subnet information,
what LLH provides in various L2-*T style of triggers,=20
since that would have limited our implementation to a single L2 alone.=20
We think making changes to L2 is not desirable.=20

With that, we set out to implement FMIPv4 by simply changing
the packet formats for FMIPv6, which does not require L2 to
provide the L3 information, and hence easy to implement on any
L2. With our FMIPv4, we got the performance we were
looking for real-time voice handover. See Charlie's presentation
at the DC IETF meeting. So, what we are asking is to standardize
the packet formats for IPv4 using the FMIPv6 design which, contrary
to what you suggest, has crucial differences with respect to LLH=20
(see the list below) although one could also find some similarities.=20

Finally, our experience is that those who implement FMIPv6 will find
FMIPv4 rather straightforward to implement since the design is identical
and
provides the required performance.=20

Some comments in-line.. Also, please see the list of differences
we put together, which suggests major differences that exist
in the design.=20

Regards,

-Rajeev



Following Henrik's note I'll expand on the technical

issues. As I wrote in my previous email I cannot quite

see the major difference between these drafts. Your new

draft considers link-layer triggers just as FMIPv6 and Low

Latency in order to improve performance. You describe AP

 =20

Actually no. Both FMIPv6 and FMIPv4 do not derive L3 information
(nFA's IP address, MN's IP address, their MAC addresses etc.) from the
L2 triggers. This is a big difference since they do not require L2's
to be changed. Please see 3) below.



scanning etc. which is not different from the existing

approach. An IP interface becoming available is just a

way of implementing a mobile trigger right? You describe

 =20

We did not suggest AP scanning as a difference since _any_ handover
protocol
over WLAN has to deal with it. So, it is not essential for discussion
here.
Using an "interface up" is hugely different from "provide L3 info from
L2"
type of trigger. The former is available without requiring changes to
L2. The=20
latter is not, and would require changes to L2. To be clear, FMIPv6 does
not=20
tie the protocol operation to L2 triggers at all, leaving implementers
to use=20
whatever is available.=20


tunnelling between FAs which is covered by the pre-reg/post-reg.

combination scenario in Low Latency.

 =20

The tunnel set up can be lot simpler than having to run pre-reg/post-reg
in
combination :-) This is a reflection from implementing FMIPv4=20
while trying to understand LLH however.=20


One other mechanism was however pointed out a while back: sending

the mobile registration to create the FA-FA tunnel AFTER L2

handoff. I assume that this is the mechanism you want to add

since the advantages you note below are applicable to that

scenario? This wasn't covered in low latency because it was covered

 =20

Without a tunnel subsequent to L2 switching, you don't have the reactive
handover.



by the PFANE mechanism in route optv4. Have you considered PFANE?

I think the rest is covered already by pre-reg, post-reg and the

combined mechanism.

 =20

What we are looking for is a way to use FMIPv6 design using IPv4.
This is necessary to enable us to use FMIPv6 and FMIPv4 together in
environments
where changes to L2 are not necessary nor are required.=20




/Karim



-----Original Message-----

From: mip4-bounces@ietf.org <mailto:mip4-bounces@ietf.org>=20

To: Mobile IPv4 Mailing List

Cc: Rajeev Koodli

Sent: 2005-03-18 00:47

Subject: [Mip4] Differences between Low Latency Handovers and FMIPv4



Hello folks,



FMIPv4 is a straightforward adaptation of the

Fast Handovers for Mobile IPv6 specification.=20

The intention is to utilize the same design for

IPv4 networks, but that requires different=20

packet formats.  We would like the [mip4] WG

to standardize these packet formats.  Both the

FMIPv6 and FMIPv4 draft mentioned here have been

implemented and offer the performance needed for=20

real-time handovers.  Below, we offer a list of

some differences between our FMIPv4 spec and

the previously published Low Latency Handovers

("LLH") specification for Mobile IPv4.



1) We believe that FMIPv4 will avoid the pitfalls

   documented in the paper from Kempf et al.

   which were described quite a while back.



2) Tight coupling to L2 triggers: The entire LLH

   process is very tightly coupled to L2 triggers, to the

   extent that the protocol does not work without such

   triggers.  In contrast, FMIPv4 can make use of such

   triggers, but entire protocol operation does not

   depend on the availability and tight coupling of L2

   triggers.  For instance, the standard Linux function

   ll_handoff() indicates to IP layer that an interface

   has become available.  FMIPv4 code for FBU from the new

   link can be invoked within ll_handoff().



3) Changes to L2 triggers: In addition to the reliance

   on L2 triggers in LLH, the triggers themselves need to

   be modified to include parameters such as new FA IP

   address, MN IP address, their MAC addresses etc.

   within the triggers themselves.  This would require

   changes to whatever L2 triggers are available on _all_

   links where such triggers are supported.=20

=20

   This is not at all required for FMIPv4 operation.

   Nor does the spec recommend such changes.

=20

4) The number of messages exchanged during handover: =20

   4.a) Pre-reg LLH:=20

   All the messages between the MN and FAs are exchanged=20

   once the trigger event occurs.  This includes two proxy

   router messages and a registration request and=20

   possibly registration reply on the old link.  In

   FMIPv4, a single message (FBU) is sent once the=20

   decision to undergo handover is made.  The MN need not

   stay on the old link once FBU is sent.=20

   4.b) Post-reg LLH:=20

   No messages are exchanged between the MN and FA.=20

   However, since the MN does not have means to change=20

   the default router, it will continue to send packets=20

   from the new link to the oFA's MAC address, which=20

   should be dropped by the IP stack.  And, consideration

   (3) above applies; the triggers on oFA and nFA must

   contain MN's IP addresses, necessitating changes to L2=20

   where the protocol might be useful.  Plus, such a mode

   "defers" MIPv4 operation, which is additional code on=20

   the MN.=20

  =20

   FMIPv4 works without imposing restrictions on when

   MIPv4 protocol messages need to be carried out.



5) Changes to MIPv4 operation: The MN changes its

   default access router once the registration reply is

   received in pre-reg LLH even if the MN is still on the

   oFA.  So, packet forwarding needs to be carefully

   constructed. (In post-reg LLH on the other hand, the

   MN does not change its default router at all, even

   though it is on the nFA.  This leads to different set

   of additional considerations).



   In FMIPv4, no changes to default router processing are

   needed.  That is, the MN is free to perform and process

   agent/router advertisements just as any normal

   (mobile) node would.



6) Protocol design: The FMIPv4 protocol clearly

   separates movement detection, IP address and nFA

   configuration, and registration request phases.  None

   of these phases is in the critical time path.  The only

   message that is on the criticial path is the FBU

   message.  For movement detection and IP/nFA

   configuration, the FMIPv4 protocol uses the Proxy

   Router messages, which are exchanged ahead of

   handover, as opposed to intitiating the handover in

   LLH.  There are quite a few other differences to list

   here.



In summary, Rajeev and I believe that the differences are

important enough to consider a separate spec of choice

to implementors.  It is especially appealing to those

considering FMIPv6 as well.



Regards,

Charlie P.



 =20


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


From mip4-bounces@ietf.org  Sun Mar 20 23:08:02 2005
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 XAA26582
	for <mip4-web-archive@ietf.org>; Sun, 20 Mar 2005 23:08:02 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDEHx-0006Sy-M6
	for mip4-web-archive@ietf.org; Sun, 20 Mar 2005 23:13:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDEC2-00082E-AO; Sun, 20 Mar 2005 23:07:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDEBy-00081v-R2; Sun, 20 Mar 2005 23:07:04 -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 XAA26549;
	Sun, 20 Mar 2005 23:06:59 -0500 (EST)
Received: from bayc1-pasmtp04.bayc1.hotmail.com ([65.54.191.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDEGx-0006Nm-1F; Sun, 20 Mar 2005 23:12:11 -0500
Message-ID: <BAYC1-PASMTP041BF25DF977082A024677A44D0@cez.ice>
X-Originating-IP: [69.158.137.97]
X-Originating-Email: [jaseem@sympatico.ca]
Received: from ee.ryerson.ca ([69.158.137.97]) by
	bayc1-pasmtp04.bayc1.hotmail.com over TLS secured channel with
	Microsoft SMTPSVC(6.0.3790.211); Sun, 20 Mar 2005 20:06:49 -0800
Message-ID: <423E4849.2060407@ee.ryerson.ca>
Date: Sun, 20 Mar 2005 23:06:33 -0500
From: Muhammad Jaseemuddin <jaseem@ee.ryerson.ca>
Organization: Ryerson University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mip4@ietf.org, mip6@ietf.org, nemo@ietf.org, mobopts@irtf.org
X-OriginalArrivalTime: 21 Mar 2005 04:06:49.0735 (UTC)
	FILETIME=[680EF970:01C52DCB]
X-Spam-Score: 4.3 (++++)
X-Scan-Signature: 6a45e05c1e4343200aa6b327df2c43fc
Subject: [Mip4] CFP: WirelessCom 2005 symposium on Wireless IP
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>
Content-Type: multipart/mixed; boundary="===============1436247963=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 4.6 (++++)
X-Scan-Signature: 71f780ffdd80c541d3e75aa5f2710d3d

This is a multi-part message in MIME format.
--===============1436247963==
Content-Type: multipart/alternative;
	boundary="------------090507080303040703080301"

This is a multi-part message in MIME format.
--------------090507080303040703080301
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

   Symposium on Wireless IP
http://wireless.cs.tku.edu.tw/WirelessIP/ 

As part of IEEE WirelessCom 2005

http:// 
<http://www.ece.queensu.ca/hpages/faculty/safwat/wirelesscom/05/>sa1.sice.umkc.edu/wc05/ 
<http://sa1.sice.umkc.edu/wc05/>


Sheraton Maui Resort, Kaanapali Beach, Maui, Hawaii, USA

http://www.sheraton-maui.com/

June 13-16, 2005

Technical Sponsorship: IEEE TCCC, TCPC, and SSCTC

THEME

Wireless Internet technology will be the next milestone for modern 
telecommunications technology and allows networked communication even 
while a user is on the move. New protocols have been developed in order 
to meet the multifunction requirements of both telecommunication and 
data communications. Protocols such as 802.11a, 802.11b or 802.11g, 
W-CDMA, CDMA-2000, were designed to meet different needs in mobile 
networks. While Internet technologies have succeeded in overcoming the 
barriers of time and distance, they have yet to fully accommodate the 
increasing mobile computer usage. There is a need for a common mobility 
solution to be adopted that would include independence of access network 
technologies and common solutions for fixed and wireless networks. 
Wireless and Mobile IP are promising technologies to serve this purpose, 
providing seamless mobility solution among the diversity of access. 
Wireless IP has been perceived as the potential future mobility 
standard. Original papers are invited in the area of Wireless IP. Papers 
must represent high-quality and previously unpublished work. Topics of 
interest include, but are not limited to, the following:

? Mobile IP-based communications network architecture
? Mobility management for wireless network
? Mobile IP applications
? Mobile IP QoS protocol
? Performance modeling of Mobile IP
? Design and analysis for Mobile IP
? Ad hoc wireless networks using IP mobility
? Mobile IPv6 based overlay communication network architecture
? Mobile IPv6 based management for wireless overlay networks
? IPv6 based mobile computing applications on overlay networks
? Secure mobile IPv6 based wireless communications on overlay networks
? IPv6 based mobile QoS protocol in overlay network environments
? Ad hoc wireless networks using IPv6 mobility in overly network 
environments

Submission Guidelines
All papers are limited to 6 pages and must be in standard IEEE 
double-column format. (IEEE Computer Society Proceedings Manuscripts 
style: two columns, single-spaced), including figures and references, 
using 10 fonts, and number each page. You can confirm the IEEE Computer 
Society Proceedings Author Guidelines at the following web page:
http://computer.org/cspress/instruct.htm.
All submissions will be handled via the conference web site at: 
https://msrcmt.research.microsoft.com/WirelessCom2005.

Important Dates
Paper Submission Deadline: March 31, 2005
Notification of Acceptance: April 15, 2005
Camera-Ready Papers: May 1, 2005

Co-Chairs
Han-Chieh Chao, National Dong Hwa University, hcc@mail.ndhu.edu.tw 
<mailto:hcc@mail.ndhu.edu.tw>
Hiroshi Esaki, University of Tokyo, hiroshi@wide.ad.jp 
<mailto:hiroshi@wide.ad.jp>

Vice-Chairs
Chih-Yung Chang, Tamkang University,  cychang@mail.tku.edu.tw 
<mailto:email@domain.domain>
Yuh-Shyan Chen, National Chung Cheng University 
<http://www.ccu.edu.tw/>, yschen@cs.ccu.edu.tw <mailto:email@domain.domain>
Jie Li, University of Tsukuba, lijie@cs.tsukuba.ac.jp 
<mailto:lijie@cs.tsukuba.ac.jp>
Muhammad Jaseemuddin, Ryerson University, jaseem@ee.ryerson.ca 
<mailto:jaseem@ee.ryerson.ca>


--------------090507080303040703080301
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
<p align="center" style="margin: 0cm 0cm 0.0001pt;"><b><i> <span
 style="font-size: 24pt; font-family: Times New Roman;"> Symposium on
Wireless IP<br>
</span></i></b><font size="4"> <a
 href="http://wireless.cs.tku.edu.tw/WirelessIP/">http://wireless.cs.tku.edu.tw/WirelessIP/</a>&nbsp;
<br>
&#12288;</font></p>
<p align="center" style="margin: 0cm 0cm 0.0001pt;"> <b><font size="4">As
part of IEEE WirelessCom 2005</font></b></p>
<p align="center" style="margin: 0cm 0cm 0.0001pt;"> <font size="4"> <a
 target="_blank"
 href="http://www.ece.queensu.ca/hpages/faculty/safwat/wirelesscom/05/">
http://</a><a href="http://sa1.sice.umkc.edu/wc05/">sa1.sice.umkc.edu/wc05/</a>
</font></p>
<p align="center" style="margin: 0cm 0cm 0.0001pt;"> <b><br>
<font size="4">Sheraton Maui Resort, Kaanapali Beach, Maui, Hawaii, USA</font></b></p>
<p align="center" style="margin: 0cm 0cm 0.0001pt;"> <font size="4"> <a
 target="_blank" href="http://www.sheraton-maui.com/">http://www.sheraton-maui.com/</a>
</font></p>
<p align="center" style="margin: 0cm 0cm 0.0001pt;"> <b>June 13-16,
2005</b></p>
<p align="center" style="margin: 0cm 0cm 0.0001pt;"> <b>Technical
Sponsorship: IEEE TCCC, TCPC, and SSCTC</b></p>
<p align="center" style="margin: 0cm 0cm 0.0001pt; text-align: left;">&#12288;</p>
<p class="MsoNormal" style="text-align: justify;"><b>THEME<br>
<br>
</b><span lang="EN-US"> Wireless Internet technology will be the next
milestone for modern telecommunications technology and allows networked
communication even while a user is on the move. New protocols have been
developed in order to meet the multifunction requirements of both
telecommunication and data communications. Protocols such as 802.11a,
802.11b or 802.11g, W-CDMA, CDMA-2000, were designed to meet different
needs in mobile networks. While Internet technologies have succeeded in
overcoming the barriers of time and distance, they have yet to fully
accommodate the increasing mobile computer usage. There is a need for a
common mobility solution to be adopted that would include independence
of access network technologies and common solutions for fixed and
wireless networks. Wireless and Mobile IP are promising technologies to
serve this purpose, providing seamless mobility solution among the
diversity of access. Wireless IP has been perceived as the potential
future mobility standard. Original papers are invited in the area of
Wireless IP. Papers must represent high-quality and previously
unpublished work. Topics of interest include, but are not limited to,
the following:</span></p>
<p class="MsoNormal" style="text-align: justify; word-spacing: -1px;"> <span
 style="font-family: SymbolMT;"><font size="3">&#8231; </font> </span><span
 lang="EN-US"><font size="3">Mobile IP-based communications network
architecture</font></span><span style="font-family: SymbolMT;"><font
 size="3"><br>
&#8231; </font></span><span lang="EN-US"><font size="3">Mobility management
for wireless network<br>
</font></span><span style="font-family: SymbolMT;"> <font size="3">&#8231; </font></span><span
 lang="EN-US"> <font size="3">Mobile IP applications<br>
</font></span><span style="font-family: SymbolMT;"> <font size="3">&#8231; </font></span><span
 lang="EN-US"> <font size="3">Mobile IP QoS protocol<br>
</font></span><span style="font-family: SymbolMT;"> <font size="3">&#8231; </font></span><span
 lang="EN-US"> <font size="3">Performance modeling of Mobile IP<br>
</font></span><span style="font-family: SymbolMT;"> <font size="3">&#8231; </font></span><span
 lang="EN-US"> <font size="3">Design and analysis for Mobile IP<br>
</font></span><span style="font-family: SymbolMT;"> <font size="3">&#8231; </font></span><span
 lang="EN-US"> <font size="3">Ad hoc wireless networks using IP
mobility<br>
</font></span><span style="font-family: SymbolMT;"> <font size="3">&#8231; </font></span><span
 lang="EN-US"> <font size="3">Mobile IPv6 based overlay communication
network architecture<br>
</font></span><span style="font-family: SymbolMT;"> <font size="3">&#8231; </font></span><span
 lang="EN-US"> <font size="3">Mobile IPv6 based management for
wireless overlay networks<br>
</font></span><span style="font-family: SymbolMT;"> <font size="3">&#8231; </font></span><span
 lang="EN-US"> <font size="3">IPv6 based mobile computing applications
on overlay networks<br>
</font></span><span style="font-family: SymbolMT;"> <font size="3">&#8231; </font></span><span
 lang="EN-US"> <font size="3">Secure mobile IPv6 based wireless
communications on overlay networks<br>
</font></span><span style="font-family: SymbolMT;"> <font size="3">&#8231; </font></span><span
 lang="EN-US"> <font size="3">IPv6 based mobile QoS protocol in
overlay network environments<br>
</font></span><span style="font-family: SymbolMT;"> <font size="3">&#8231;</font></span><font
 size="3"><span style="letter-spacing: -1pt;"> </span><span
 lang="EN-US" style="letter-spacing: 0pt;">Ad hoc wireless networks
using IPv6 mobility</span><span lang="EN-US"
 style="letter-spacing: -1pt;"> in </span><span lang="EN-US"
 style="letter-spacing: 0pt;">overly</span><span lang="EN-US"
 style="letter-spacing: -1pt;"> network </span><span lang="EN-US"
 style="letter-spacing: 0pt;"> environments</span></font></p>
<p class="MsoNormal"><b><span lang="EN-US">Submission Guidelines<br>
</span></b>All papers are limited to 6 pages and must be in standard
IEEE double-column format. (IEEE Computer Society Proceedings
Manuscripts style: two columns, single-spaced), including figures and
references, using 10 fonts, and number each page. You can confirm the
IEEE Computer Society Proceedings Author Guidelines at the following
web page:<br>
<a href="http://computer.org/cspress/instruct.htm">
http://computer.org/cspress/instruct.htm</a>. <br>
All submissions will be handled via the conference web site at:<span
 lang="EN-US" style="font-size: 12pt; font-family: Times New Roman;"> </span>
<a href="https://msrcmt.research.microsoft.com/WirelessCom2005"
 target="_blank"> https://msrcmt.research.microsoft.com/WirelessCom2005</a>.<br>
&#12288;</p>
<p class="MsoNormal"><b><span lang="EN-US">Important Dates<br>
</span></b><span lang="EN-US">Paper Submission Deadline: </span> March<span
 lang="EN-US"> </span>31<span lang="EN-US">, 2005<br>
Notification of Acceptance: April 15, 2005<br>
Camera-Ready Papers: May 1, 2005</span></p>
<p class="MsoNormal"><b><span lang="EN-US">Co-Chairs</span></b><span
 lang="EN-US"><br>
Han-Chieh Chao, National Dong Hwa University, <span
 style="color: blue;"> <a href="mailto:hcc@mail.ndhu.edu.tw"
 style="color: blue; text-decoration: underline;"> hcc@mail.ndhu.edu.tw</a></span>
<br>
Hiroshi Esaki, University of Tokyo, <span style="color: blue;"> <a
 href="mailto:hiroshi@wide.ad.jp"
 style="color: blue; text-decoration: underline;"> hiroshi@wide.ad.jp</a></span></span></p>
<p class="MsoNormal"><b><span lang="EN-US">Vice</span>-<span
 lang="EN-US">Chairs</span></b><span lang="EN-US"><br>
Chih-Yung Chang, Tamkang University, <a
 href="mailto:email@domain.domain"
 style="color: blue; text-decoration: underline;">
&nbsp;cychang@mail.tku.edu.tw</a> <br>
Yuh-Shyan Chen, <a href="http://www.ccu.edu.tw/"
 style="color: blue; text-decoration: underline;"> <span
 style="color: windowtext; text-decoration: none;">National Chung Cheng
University</span></a>, <a href="mailto:email@domain.domain"
 style="color: blue; text-decoration: underline;"> yschen@cs.ccu.edu.tw</a>
<br>
Jie Li, University of Tsukuba,</span><span lang="EN-US"
 style="font-size: 13.5pt;"> </span><span lang="EN-US"> <a
 href="mailto:lijie@cs.tsukuba.ac.jp"
 style="color: blue; text-decoration: underline;">
lijie@cs.tsukuba.ac.jp</a><br>
Muhammad Jaseemuddin, Ryerson University, <a
 href="mailto:jaseem@ee.ryerson.ca"
 style="color: blue; text-decoration: underline;"> jaseem@ee.ryerson.ca</a></span></p>
</body>
</html>

--------------090507080303040703080301--



--===============1436247963==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1436247963==--




From mip4-bounces@ietf.org  Mon Mar 21 07:08:23 2005
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 HAA26033
	for <mip4-web-archive@ietf.org>; Mon, 21 Mar 2005 07:08:23 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDLmk-0004fg-Rt
	for mip4-web-archive@ietf.org; Mon, 21 Mar 2005 07:13:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDLej-0007Rv-9R; Mon, 21 Mar 2005 07:05:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DD1Uy-000308-Ak
	for mip4@megatron.ietf.org; Sun, 20 Mar 2005 09:33:48 -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 JAA19731
	for <mip4@ietf.org>; Sun, 20 Mar 2005 09:33:46 -0500 (EST)
Received: from [204.9.221.21] (helo=thingmagic.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DD1Zp-0006ku-Hz
	for mip4@ietf.org; Sun, 20 Mar 2005 09:38:50 -0500
Received: from [24.61.30.237] (account margaret HELO [10.0.0.171])
	by thingmagic.com (CommuniGate Pro SMTP 4.1.8)
	with ESMTP-TLS id 311565; Sun, 20 Mar 2005 09:31:08 -0500
Mime-Version: 1.0
Message-Id: <p06200743be6337a1d622@[10.0.0.171]>
Date: Sun, 20 Mar 2005 09:29:42 -0500
To: mip4@ietf.org
From: Margaret Wasserman <margaret@thingmagic.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
X-Mailman-Approved-At: Mon, 21 Mar 2005 07:05:12 -0500
Cc: Thomas Narten <narten@us.ibm.com>, Pete McCann <mccap@lucent.com>,
        eva.gustafsson@ericsson.com, charles.perkins@nokia.com,
        Mark Townsley <townsley@cisco.com>, annika.jonsson@ericsson.com,
        Henrik Levkowetz <henrik@levkowetz.com>
Subject: [Mip4] draft-ietf-mip4-reg-tunnel-00.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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab


Hi All,

Just a short update on the status of draft-ietf-mip4-reg-tunnel-00.txt.

With Thomas' departure, I have become the shepherding AD for this 
document.  My understanding is that the authors are currently working 
on a revision of this document to address Thomas Narten's AD review 
comments which can be seen in the public I-D tracker at:

https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=12575&rfc_flag=0

So, unless I hear otherwise, I will wait for a revision of this 
document that addresses Thomas' comments.

Margaret

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


From mip4-bounces@ietf.org  Mon Mar 21 11:46:58 2005
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 LAA25519
	for <mip4-web-archive@ietf.org>; Mon, 21 Mar 2005 11:46:58 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDQ8W-00074C-Cq
	for mip4-web-archive@ietf.org; Mon, 21 Mar 2005 11:52:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDPyC-0001Pv-05; Mon, 21 Mar 2005 11:41:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDPy9-0001Pm-Lh
	for mip4@megatron.ietf.org; Mon, 21 Mar 2005 11:41:33 -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 LAA24970
	for <mip4@ietf.org>; Mon, 21 Mar 2005 11:41:29 -0500 (EST)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDQ3D-0006qn-6L
	for mip4@ietf.org; Mon, 21 Mar 2005 11:46:48 -0500
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234])
	by motgate8.mot.com (Motorola/Motgate8) with ESMTP id j2LGhR2C024488;
	Mon, 21 Mar 2005 09:43:27 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id j2LGg06L022930;
	Mon, 21 Mar 2005 10:42:01 -0600 (CST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 56889865980; Mon, 21 Mar 2005 17:41:09 +0100 (CET)
Message-ID: <423EF91F.6030900@motorola.com>
Date: Mon, 21 Mar 2005 17:41:03 +0100
From: Alexandru Petrescu <Alexandru.Petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: espen@birdstep.com
Subject: Re: [Mip4] Request to consider FMIPv4 as a working group document
References: <200503182229.j2IMTwGa007066@mail.birdstep.com>
In-Reply-To: <200503182229.j2IMTwGa007066@mail.birdstep.com>
X-Enigmail-Version: 0.89.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: "'Mobile IPv4 Mailing List'" <mip4@ietf.org>,
        "'Charles E.Perkins'" <charliep@iprg.nokia.com>,
        "'Rajeev Koodli'" <rajeev.koodli@nokia.com>
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>
Content-Type: multipart/mixed; boundary="===============0609378635=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0609378635==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig2D97C3B27E80BCED9CFC0619"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig2D97C3B27E80BCED9CFC0619
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

[I have some comments on the draft, not the request itself, please
  disregard if already discussed or clarified.]

Espen Klovning wrote:
> I do have some concerns that more or less reflect what Kent Leung has
>  voiced in previous mails on the list. 
 >- AR == FA
 >- IP address management

I tend to agree with this.

The draft explains, but is not clear about what happens to FMIP when
CCoA/DHCP _is_ used.  If DHCP is _not_ used with FMIP then the draft 
should say so and in a coherent manner, IMHO; otherwise the generic 
"compatibility" statements confuse me at three points.

   "[First Scenario]: the access routers are not involved in IP address
    management for the MN. The mobile nodes acquire a new care-of address
    upon attaching to a new subnet link as they normally do."

In some deployments, MN normally acquires an address with DHCP and the
first-hop router is a DHCP Relay, so the AR practically _is_ involved in
IP address management for the MN, although the AR is not a DHCP Server.
  So the question coming to mind immediately is what is meant by "access
routers are not involved in IP address management for the MN"?  Does
that simply mean that AR is not a DHCP Server and is a DHCP Relay?

Second point is about DHCP and additional delays.  If vanilla DHCP is 
used then the effective DHCP delays are in the range 1s-10s with a 
802.11b WEP first-hop, 100Mbit Ether and GHz computers.  That is very 
large, easily influencing real-time.  It is not clear in the draft how 
any of these numbers influence FMIP - is FMIP slower if vanilla DHCP is 
used?

Third point is the apparent incoherence between abstract and body, with 
respect to DHCP.  The abstract says "For reducing the IP address 
configuration, the draft provides two alternatives" and none is DHCP. 
Or, later in the body one can read "Address allocation and configuration 
may be supported using DHCP or any other method."

Just some thoughts...

Alex

--------------enig2D97C3B27E80BCED9CFC0619
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFCPvklMmC0w56zj54RAmczAKDXqTyo59SKhnKSxc/nj5b3Mwud0QCfQB+N
ORdxVwG1c6ykgBSmj9K2vR8=
=yoKG
-----END PGP SIGNATURE-----

--------------enig2D97C3B27E80BCED9CFC0619--


--===============0609378635==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0609378635==--



From mip4-bounces@ietf.org  Mon Mar 21 12:34:41 2005
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 MAA29345
	for <mip4-web-archive@ietf.org>; Mon, 21 Mar 2005 12:34:41 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDQsi-0000OT-Kr
	for mip4-web-archive@ietf.org; Mon, 21 Mar 2005 12:40:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDQkt-0002gb-3G; Mon, 21 Mar 2005 12:31:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDQkr-0002gN-JJ
	for mip4@megatron.ietf.org; Mon, 21 Mar 2005 12:31:53 -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 MAA29085
	for <mip4@ietf.org>; Mon, 21 Mar 2005 12:31:50 -0500 (EST)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDQpx-0000EF-07
	for mip4@ietf.org; Mon, 21 Mar 2005 12:37:10 -0500
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (Motorola/Motgate8) with ESMTP id j2LHY62C020065;
	Mon, 21 Mar 2005 10:34:06 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr01.mot.com (8.13.1/8.13.0) with ESMTP id j2LHXMAX025217;
	Mon, 21 Mar 2005 11:33:23 -0600 (CST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id AA3D6865980; Mon, 21 Mar 2005 18:31:49 +0100 (CET)
Message-ID: <423F0500.2010408@motorola.com>
Date: Mon, 21 Mar 2005 18:31:44 +0100
From: Alexandru Petrescu <Alexandru.Petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Charles E.Perkins" <charliep@iprg.nokia.com>
Subject: Re: [Mip4] Request to consider FMIPv4 as a working group document
References: <4239FC52.33760051@iprg.nokia.com>
In-Reply-To: <4239FC52.33760051@iprg.nokia.com>
X-Enigmail-Version: 0.89.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>,
        Rajeev Koodli <rajeev.koodli@nokia.com>
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>
Content-Type: multipart/mixed; boundary="===============1822584704=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1822584704==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig3B30F56CA06D3ED0F52334E4"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig3B30F56CA06D3ED0F52334E4
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hi Charlie,

Charles E.Perkins wrote:
> As part of this discussion, I showed some results which indicate very
>  good performance for FMIPv4, suitable for handling interactive voice
>  applications.  I probably have the PowerPoint presentation around 
> somewhere if needed.

Yes, I need these slides, please send in if easily available for you,
thank you.

I am interested to find out about "hard" limits on the interruption
times that a human user of a interactive voice IP application is ready
to tolerate.  During some IP and non-IP discussions, very often the
numbers 100ms or 200ms come up.  But for some reason I'm unable to
identify a written report/paper, eventually with some "hands-on"
non-simulated experience to determine this "tolerable delay".  Anything
like a I-D report or ppt slides or journal/conference paper applies, thanks,

Alex

--------------enig3B30F56CA06D3ED0F52334E4
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFCPwUFMmC0w56zj54RAhIhAKD2I71EkoKd3TpslNwWN23UZisHggCeJCzJ
x2ejlH7KctaKGnQm+Rube3U=
=+IVh
-----END PGP SIGNATURE-----

--------------enig3B30F56CA06D3ED0F52334E4--


--===============1822584704==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1822584704==--



From mip4-bounces@ietf.org  Mon Mar 21 12:58:14 2005
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 MAA01002
	for <mip4-web-archive@ietf.org>; Mon, 21 Mar 2005 12:58:14 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDRFV-00019s-6w
	for mip4-web-archive@ietf.org; Mon, 21 Mar 2005 13:03:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDR9O-0006Op-AK; Mon, 21 Mar 2005 12:57:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDR9M-0006Ok-Su
	for mip4@megatron.ietf.org; Mon, 21 Mar 2005 12:57:13 -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 MAA00953
	for <mip4@ietf.org>; Mon, 21 Mar 2005 12:57:09 -0500 (EST)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDRET-00016D-7z
	for mip4@ietf.org; Mon, 21 Mar 2005 13:02:29 -0500
Message-ID: <012d01c52e3f$8fbf8d80$0f6115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Alexandru Petrescu" <Alexandru.Petrescu@motorola.com>,
        "Charles E.Perkins" <charliep@iprg.nokia.com>
References: <4239FC52.33760051@iprg.nokia.com> <423F0500.2010408@motorola.com>
Subject: Re: [Mip4] Request to consider FMIPv4 as a working group document
Date: Mon, 21 Mar 2005 09:58:12 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>,
        Rajeev Koodli <rajeev.koodli@nokia.com>
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit

40-60 ms, depending on the particular phonemes that are interrupted.

            jak

----- Original Message ----- 
From: "Alexandru Petrescu" <Alexandru.Petrescu@motorola.com>
To: "Charles E.Perkins" <charliep@iprg.nokia.com>
Cc: "Mobile IPv4 Mailing List" <mip4@ietf.org>; "Rajeev Koodli"
<rajeev.koodli@nokia.com>
Sent: Monday, March 21, 2005 9:31 AM
Subject: Re: [Mip4] Request to consider FMIPv4 as a working group document


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


From mip4-bounces@ietf.org  Mon Mar 21 14:08:40 2005
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 OAA06134
	for <mip4-web-archive@ietf.org>; Mon, 21 Mar 2005 14:08:40 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDSLe-0003Vp-Fw
	for mip4-web-archive@ietf.org; Mon, 21 Mar 2005 14:13:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDSEL-0008Vt-JD; Mon, 21 Mar 2005 14:06:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDSEJ-0008Vo-Uv
	for mip4@megatron.ietf.org; Mon, 21 Mar 2005 14:06:24 -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 OAA05869
	for <mip4@ietf.org>; Mon, 21 Mar 2005 14:06:22 -0500 (EST)
Received: from motgate6.mot.com ([144.189.100.106])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDSJQ-0003QA-4G
	for mip4@ietf.org; Mon, 21 Mar 2005 14:11:41 -0500
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate6.mot.com (Motorola/Motgate6) with ESMTP id j2LJ6HQi016642;
	Mon, 21 Mar 2005 12:06:17 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id j2LJ6niI021131;
	Mon, 21 Mar 2005 13:06:50 -0600 (CST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 73AD5865980; Mon, 21 Mar 2005 20:06:15 +0100 (CET)
Message-ID: <423F1B21.2090300@motorola.com>
Date: Mon, 21 Mar 2005 20:06:09 +0100
From: Alexandru Petrescu <Alexandru.Petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
Subject: Re: [Mip4] Request to consider FMIPv4 as a working group document
References: <4239FC52.33760051@iprg.nokia.com> <423F0500.2010408@motorola.com>
	<012d01c52e3f$8fbf8d80$0f6115ac@dcml.docomolabsusa.com>
In-Reply-To: <012d01c52e3f$8fbf8d80$0f6115ac@dcml.docomolabsusa.com>
X-Enigmail-Version: 0.89.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>,
        "Charles E.Perkins" <charliep@iprg.nokia.com>,
        Rajeev Koodli <rajeev.koodli@nokia.com>
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>
Content-Type: multipart/mixed; boundary="===============0534812276=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0534812276==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig3B962216213E5D0F7D95585F"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig3B962216213E5D0F7D95585F
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

James Kempf wrote:

> 40-60 ms, depending on the particular phonemes that are interrupted.

Thanks, good to know.  That approximately matches what a 1Ghz i686
laptop, PCMCIA 802.11b WEP, linux can do, as a effective (userspace)
802.11b attachment time.

That does not mean that 802.11b userspace attachment time is that good
everywhere, and in some cases it can be as slow as 4seconds, an
interruption delay to which an IP FMIP protocol could presumably do
little or no help at all.

I'm wondering whether it's worth to note down some range of the
"tolerable L2 interruption delay", with actual quantitative limits,
within which a particular FMIP design is known to work and offer a
better user experience, IMHO.  The word "fast" itself in the protocol
name may invite to think about that, IMHO.

Alex


--------------enig3B962216213E5D0F7D95585F
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFCPxsnMmC0w56zj54RAvABAKDYzkIvmgao8KxIvs5hevx9mqCAGgCeKidq
utgfBwmledWrsTQfJ1b3tKs=
=FlPC
-----END PGP SIGNATURE-----

--------------enig3B962216213E5D0F7D95585F--


--===============0534812276==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0534812276==--



From mip4-bounces@ietf.org  Mon Mar 21 17:07:01 2005
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 RAA01832
	for <mip4-web-archive@ietf.org>; Mon, 21 Mar 2005 17:07:01 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDV8I-0004jA-Fk
	for mip4-web-archive@ietf.org; Mon, 21 Mar 2005 17:12:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDV22-0004pB-AB; Mon, 21 Mar 2005 17:05:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDV20-0004p6-J3
	for mip4@megatron.ietf.org; Mon, 21 Mar 2005 17:05:52 -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 RAA01684
	for <mip4@ietf.org>; Mon, 21 Mar 2005 17:05:50 -0500 (EST)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDV76-0004hD-Tt
	for mip4@ietf.org; Mon, 21 Mar 2005 17:11:11 -0500
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j2LMZds07747;
	Mon, 21 Mar 2005 14:35:39 -0800
X-mProtect: <200503212235> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp141217.americas.nokia.com (172.18.141.217,
	claiming to be "[172.18.141.217]")
	by darkstar.iprg.nokia.com smtpdlJCsGC; Mon, 21 Mar 2005 14:35:38 PST
Message-ID: <423F4523.2020005@iprg.nokia.com>
Date: Mon, 21 Mar 2005 14:05:23 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Karim El-Malki (AL/EAB)" <karim.el-malki@ericsson.com>
Subject: Re: [Mip4] RE: Differences between Low Latency Handovers and FMIPv4
References: <24521B9781EAC745A4BE65966F69C9BE212AAD@esealmw115.eemea.ericsson.se>
In-Reply-To: <24521B9781EAC745A4BE65966F69C9BE212AAD@esealmw115.eemea.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea36de7a5e28e9b4461c8d685f4e97f1
Content-Transfer-Encoding: 7bit
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 94962611154c8404498b19f744990308
Content-Transfer-Encoding: 7bit


Hi Karim,


Karim El-Malki (AL/EAB) wrote:

>Hi Rajeev
>I understand your point that you took FMIPv6 and applied
>it to v4 to make FMIPv4. But that doesn't make it
>substantially different from Low Latency. Your spec does
>use link-layer triggers to be able to send the RtSolPr.
>An interface coming up in the MN is used just the same in
>Low Latency and is defined as a mobile trigger in Low
>Latency (L2-LU). PRE-REG involves the MN getting such a
>mobile trigger and sending a PrRtSol and receiving a
>PrRtAdv. What's the difference compared to your spec?
>  
>
As I explained below (and also itemized in the List below), the essential
difference is that LLH requires L2 to provide L3 information (nFA, MN
IP addresses, their MAC addresses etc.) via various L2-*T type of triggers.
This is a Big difference for us since we do not wish to change L2 to
implement fast handovers. Both FMIPv6 and FMIPv4 work without
requiring such changes to L2. 

>The messages are even called the same. Nothing special
>or L2-dependent about this L2 trigger. For example PRE-REG
>  
>
Well, the essential difference is what requirements LLH imposes on L2
triggers. Table 1 in LLH specifies what information is expected from
L2 triggers including the nFA, MN IP addresses from the various L2-*T
triggers.

>can be applied to WLAN using AP scans. I don't think that
>the difference in packet formats makes it a substantially
>different spec from low latency.  Also, the other case you
>are considering involves an L3 handoff that happens after
>the MN attaches to the new link. This cannot really be
>considered a "fast" handoff, which would instead be where
>the handoff happens before or in parallel with the L2 handoff.
>  
>
Perhaps you have missed something.. The FMIP design allows movement
detection and router/FA discovery phases to be done prior to L2 
handover. The
"reactive" handover we refer to is the one where the FBU is sent from the
new link. But, the MN uses the neighborhood information via Proxy Router
messages to determine movement detection and router/FA config 
information of the
new subnet. So, your description above is not accurate.


>This L3-handoff-after-L2-handoff was already covered in the
>route optv4 spec using PFANE. You may have missed the question
>so I'll repeat it: did you consider the PFANE? Why aren't
>you just reusing the PFANE (Previous FA Notification
>Extension) work for that scenario?
>  
>
Please see above. The key difference with respect to Previous FA (what 
used to be Previous AR
notification in v6) Notification is that you don't incur delays due to 
movement detection and
router/FA discovery.

So, apart from the independence from L2 to provide L3 information, the other
crucial difference is the decoupling of neighborhood discovery from the 
actual
handover signaling. This not only reduces the number of signaling messages
during the handover itself, but also makes the reactive fast handovers 
possible.

-Rajeev


>/Karim
>
>-----Original Message-----
>From: Rajeev Koodli
>To: mip4@ietf.org; Karim El-Malki (AL/EAB)
>Sent: 18/03/2005 22:02
>Subject: Re: Differences between Low Latency Handovers and FMIPv4
>
>
>Hi Karim,
>
>We implemented the FMIPv6 spec and got the performance
>we were looking for. When we considered IPv4, we did not
>want to change the L2 to provide L3 subnet information,
>what LLH provides in various L2-*T style of triggers, 
>since that would have limited our implementation to a single L2 alone. 
>We think making changes to L2 is not desirable. 
>
>With that, we set out to implement FMIPv4 by simply changing
>the packet formats for FMIPv6, which does not require L2 to
>provide the L3 information, and hence easy to implement on any
>L2. With our FMIPv4, we got the performance we were
>looking for real-time voice handover. See Charlie's presentation
>at the DC IETF meeting. So, what we are asking is to standardize
>the packet formats for IPv4 using the FMIPv6 design which, contrary
>to what you suggest, has crucial differences with respect to LLH 
>(see the list below) although one could also find some similarities. 
>
>Finally, our experience is that those who implement FMIPv6 will find
>FMIPv4 rather straightforward to implement since the design is identical
>and
>provides the required performance. 
>
>Some comments in-line.. Also, please see the list of differences
>we put together, which suggests major differences that exist
>in the design. 
>
>Regards,
>
>-Rajeev
>
>
>
>Following Henrik's note I'll expand on the technical
>
>issues. As I wrote in my previous email I cannot quite
>
>see the major difference between these drafts. Your new
>
>draft considers link-layer triggers just as FMIPv6 and Low
>
>Latency in order to improve performance. You describe AP
>
>  
>
>Actually no. Both FMIPv6 and FMIPv4 do not derive L3 information
>(nFA's IP address, MN's IP address, their MAC addresses etc.) from the
>L2 triggers. This is a big difference since they do not require L2's
>to be changed. Please see 3) below.
>
>
>
>scanning etc. which is not different from the existing
>
>approach. An IP interface becoming available is just a
>
>way of implementing a mobile trigger right? You describe
>
>  
>
>We did not suggest AP scanning as a difference since _any_ handover
>protocol
>over WLAN has to deal with it. So, it is not essential for discussion
>here.
>Using an "interface up" is hugely different from "provide L3 info from
>L2"
>type of trigger. The former is available without requiring changes to
>L2. The 
>latter is not, and would require changes to L2. To be clear, FMIPv6 does
>not 
>tie the protocol operation to L2 triggers at all, leaving implementers
>to use 
>whatever is available. 
>
>
>tunnelling between FAs which is covered by the pre-reg/post-reg.
>
>combination scenario in Low Latency.
>
>  
>
>The tunnel set up can be lot simpler than having to run pre-reg/post-reg
>in
>combination :-) This is a reflection from implementing FMIPv4 
>while trying to understand LLH however. 
>
>
>One other mechanism was however pointed out a while back: sending
>
>the mobile registration to create the FA-FA tunnel AFTER L2
>
>handoff. I assume that this is the mechanism you want to add
>
>since the advantages you note below are applicable to that
>
>scenario? This wasn't covered in low latency because it was covered
>
>  
>
>Without a tunnel subsequent to L2 switching, you don't have the reactive
>handover.
>
>
>
>by the PFANE mechanism in route optv4. Have you considered PFANE?
>
>I think the rest is covered already by pre-reg, post-reg and the
>
>combined mechanism.
>
>  
>
>What we are looking for is a way to use FMIPv6 design using IPv4.
>This is necessary to enable us to use FMIPv6 and FMIPv4 together in
>environments
>where changes to L2 are not necessary nor are required. 
>
>
>
>
>/Karim
>
>
>
>-----Original Message-----
>
>From: mip4-bounces@ietf.org <mailto:mip4-bounces@ietf.org> 
>
>To: Mobile IPv4 Mailing List
>
>Cc: Rajeev Koodli
>
>Sent: 2005-03-18 00:47
>
>Subject: [Mip4] Differences between Low Latency Handovers and FMIPv4
>
>
>
>Hello folks,
>
>
>
>FMIPv4 is a straightforward adaptation of the
>
>Fast Handovers for Mobile IPv6 specification. 
>
>The intention is to utilize the same design for
>
>IPv4 networks, but that requires different 
>
>packet formats.  We would like the [mip4] WG
>
>to standardize these packet formats.  Both the
>
>FMIPv6 and FMIPv4 draft mentioned here have been
>
>implemented and offer the performance needed for 
>
>real-time handovers.  Below, we offer a list of
>
>some differences between our FMIPv4 spec and
>
>the previously published Low Latency Handovers
>
>("LLH") specification for Mobile IPv4.
>
>
>
>1) We believe that FMIPv4 will avoid the pitfalls
>
>   documented in the paper from Kempf et al.
>
>   which were described quite a while back.
>
>
>
>2) Tight coupling to L2 triggers: The entire LLH
>
>   process is very tightly coupled to L2 triggers, to the
>
>   extent that the protocol does not work without such
>
>   triggers.  In contrast, FMIPv4 can make use of such
>
>   triggers, but entire protocol operation does not
>
>   depend on the availability and tight coupling of L2
>
>   triggers.  For instance, the standard Linux function
>
>   ll_handoff() indicates to IP layer that an interface
>
>   has become available.  FMIPv4 code for FBU from the new
>
>   link can be invoked within ll_handoff().
>
>
>
>3) Changes to L2 triggers: In addition to the reliance
>
>   on L2 triggers in LLH, the triggers themselves need to
>
>   be modified to include parameters such as new FA IP
>
>   address, MN IP address, their MAC addresses etc.
>
>   within the triggers themselves.  This would require
>
>   changes to whatever L2 triggers are available on _all_
>
>   links where such triggers are supported. 
>
> 
>
>   This is not at all required for FMIPv4 operation.
>
>   Nor does the spec recommend such changes.
>
> 
>
>4) The number of messages exchanged during handover:  
>
>   4.a) Pre-reg LLH: 
>
>   All the messages between the MN and FAs are exchanged 
>
>   once the trigger event occurs.  This includes two proxy
>
>   router messages and a registration request and 
>
>   possibly registration reply on the old link.  In
>
>   FMIPv4, a single message (FBU) is sent once the 
>
>   decision to undergo handover is made.  The MN need not
>
>   stay on the old link once FBU is sent. 
>
>   4.b) Post-reg LLH: 
>
>   No messages are exchanged between the MN and FA. 
>
>   However, since the MN does not have means to change 
>
>   the default router, it will continue to send packets 
>
>   from the new link to the oFA's MAC address, which 
>
>   should be dropped by the IP stack.  And, consideration
>
>   (3) above applies; the triggers on oFA and nFA must
>
>   contain MN's IP addresses, necessitating changes to L2 
>
>   where the protocol might be useful.  Plus, such a mode
>
>   "defers" MIPv4 operation, which is additional code on 
>
>   the MN. 
>
>   
>
>   FMIPv4 works without imposing restrictions on when
>
>   MIPv4 protocol messages need to be carried out.
>
>
>
>5) Changes to MIPv4 operation: The MN changes its
>
>   default access router once the registration reply is
>
>   received in pre-reg LLH even if the MN is still on the
>
>   oFA.  So, packet forwarding needs to be carefully
>
>   constructed. (In post-reg LLH on the other hand, the
>
>   MN does not change its default router at all, even
>
>   though it is on the nFA.  This leads to different set
>
>   of additional considerations).
>
>
>
>   In FMIPv4, no changes to default router processing are
>
>   needed.  That is, the MN is free to perform and process
>
>   agent/router advertisements just as any normal
>
>   (mobile) node would.
>
>
>
>6) Protocol design: The FMIPv4 protocol clearly
>
>   separates movement detection, IP address and nFA
>
>   configuration, and registration request phases.  None
>
>   of these phases is in the critical time path.  The only
>
>   message that is on the criticial path is the FBU
>
>   message.  For movement detection and IP/nFA
>
>   configuration, the FMIPv4 protocol uses the Proxy
>
>   Router messages, which are exchanged ahead of
>
>   handover, as opposed to intitiating the handover in
>
>   LLH.  There are quite a few other differences to list
>
>   here.
>
>
>
>In summary, Rajeev and I believe that the differences are
>
>important enough to consider a separate spec of choice
>
>to implementors.  It is especially appealing to those
>
>considering FMIPv6 as well.
>
>
>
>Regards,
>
>Charlie P.
>
>
>
>  
>
>
>  
>

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


From mip4-bounces@ietf.org  Mon Mar 21 18:21:29 2005
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 SAA11000
	for <mip4-web-archive@ietf.org>; Mon, 21 Mar 2005 18:21:29 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDWIN-0007S9-9z
	for mip4-web-archive@ietf.org; Mon, 21 Mar 2005 18:26:51 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDWBm-0005Ct-Ic; Mon, 21 Mar 2005 18:20:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDWBk-0005CW-LR
	for mip4@megatron.ietf.org; Mon, 21 Mar 2005 18:20:00 -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 SAA10868
	for <mip4@ietf.org>; Mon, 21 Mar 2005 18:19:57 -0500 (EST)
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDWGs-0007QC-MR
	for mip4@ietf.org; Mon, 21 Mar 2005 18:25:20 -0500
Received: from esealmw126.eemea.ericsson.se ([153.88.254.123])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j2LNJufm021281; Tue, 22 Mar 2005 00:19:57 +0100 (MET)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 22 Mar 2005 00:19:55 +0100
Received: from esealmw115.eemea.ericsson.se ([153.88.200.6]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 22 Mar 2005 00:19:55 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and FMIPv4
Date: Tue, 22 Mar 2005 00:19:54 +0100
Message-ID: <24521B9781EAC745A4BE65966F69C9BE212AB4@esealmw115.eemea.ericsson.se>
Thread-Topic: [Mip4] RE: Differences between Low Latency Handovers and FMIPv4
Thread-index: AcUuYh8q8ujN+vNyTlqk2yrHoPEndgAA+jkr
From: "Karim El-Malki \(AL/EAB\)" <karim.el-malki@ericsson.com>
To: "Rajeev Koodli " <rajeev@iprg.nokia.com>
X-OriginalArrivalTime: 21 Mar 2005 23:19:55.0155 (UTC)
	FILETIME=[7DC84630:01C52E6C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 093efd19b5f651b2707595638f6c4003
Content-Transfer-Encoding: quoted-printable

>>I understand your point that you took FMIPv6 and applied
>>it to v4 to make FMIPv4. But that doesn't make it
>>substantially different from Low Latency. Your spec does
>>use link-layer triggers to be able to send the RtSolPr.
>>An interface coming up in the MN is used just the same in
>>Low Latency and is defined as a mobile trigger in Low
>>Latency (L2-LU). PRE-REG involves the MN getting such a
>>mobile trigger and sending a PrRtSol and receiving a
>>PrRtAdv. What's the difference compared to your spec?
>> =20
>>
>As I explained below (and also itemized in the List below), the
>essential
>difference is that LLH requires L2 to provide L3 information (nFA, MN
>IP addresses, their MAC addresses etc.) via various L2-*T type of
>triggers.
>This is a Big difference for us since we do not wish to change L2 to
>implement fast handovers. Both FMIPv6 and FMIPv4 work without
>requiring such changes to L2.=20

That's not correct.
Let's take the case where the L3 handoff is initiated before
L2 handoff. Taking WLAN for example, in LLH the MN gets info
from L2 (e.g. AP scan) and sends a PrRtSol to get a PrRtAdv
containing information of the subnet it may move to. I can't
see any change required to L2. Where is the difference compared
to what you have described? The only difference is that we
definied all "handoff hints" as L2 triggers, just as a result
of the AP scan is defined as a mobile trigger. The LLH spec doesn't
mandate the presence of all trigger types in all cases. It
depends on what the L2 has to offer.

>>The messages are even called the same. Nothing special
>>or L2-dependent about this L2 trigger. For example PRE-REG
>> =20
>>
>Well, the essential difference is what requirements LLH imposes on L2
>triggers. Table 1 in LLH specifies what information is expected from
>L2 triggers including the nFA, MN IP addresses from the various L2-*T
>triggers.

LLH can work with different types of L2 triggers (which is very
different from requiring L2 changes) and supports the case you
have described in FMIPv4. Table 1 specifies the different types
of triggers that LLH can utilise. Note that it includes very
simple triggers that work even on WLAN. It is wrong to say
that all triggers in Table 1 are required on all L2s for LLH
to work.

>>can be applied to WLAN using AP scans. I don't think that
>>the difference in packet formats makes it a substantially
>>different spec from low latency.  Also, the other case you
>>are considering involves an L3 handoff that happens after
>>the MN attaches to the new link. This cannot really be
>>considered a "fast" handoff, which would instead be where
>>the handoff happens before or in parallel with the L2 handoff.
>> =20
>>
>Perhaps you have missed something.. The FMIP design allows movement
>detection and router/FA discovery phases to be done prior to L2=20
>handover. The
>"reactive" handover we refer to is the one where the FBU is sent from
>the
>new link. But, the MN uses the neighborhood information via Proxy =
Router
>messages to determine movement detection and router/FA config=20
>information of the
>new subnet. So, your description above is not accurate.

Note that I first addressed the L3-movement-before-L2 (where I
am saying that FMIPv4 is no different from LLH) and then
I wrote "the other case you are considering....".
Am I incorrect in saying that FMIPv4 also supports the
L3-handoff-after-L2-handoff case? I think I had read that
case in FMIPv4 (i.e. FBU sent from new link).
That's why I had asked about PFANE.

>>This L3-handoff-after-L2-handoff was already covered in the
>>route optv4 spec using PFANE. You may have missed the question
>>so I'll repeat it: did you consider the PFANE? Why aren't
>>you just reusing the PFANE (Previous FA Notification
>>Extension) work for that scenario?
>> =20
>>
>Please see above. The key difference with respect to Previous FA (what=20
>used to be Previous AR
>notification in v6) Notification is that you don't incur delays due to=20
>movement detection and
>router/FA discovery.

If you are only considering the L3-handoff-before-L2-handoff case
then there are very little differences between FMIPv4 and LLH for
the reasons given above.

>So, apart from the independence from L2 to provide L3 information, the
>other
>crucial difference is the decoupling of neighborhood discovery from the =

>actual
>handover signaling. This not only reduces the number of signaling
>messages
>during the handover itself, but also makes the reactive fast handovers=20
>possible.

Again I can't see the crucial difference from LLH.
The ND messages are basically the same (even almost called the same):
PrRtSol and PrRtAdv. LLH uses standard MIPv4 naming (Registration
Request and Reply) while FMIPv4 achieves the same result but calls
this an FBU. Tunnelling between FAs is supported in both specs.
LLH furthermore supports anticipated HA updating or "local" HA
updating (regional registrations). It seems to me that to make
things "faster" one would want to update the local/global HA directly
if possible since FA-FA routing can be inefficient in a tree-like
network structure compared to updating a local HA. I am curious to
understand why you have eliminated that option in FMIPv4 compared
to LLH. Measurements performed on FMIPv6+HMIPv6 integration
prove that it makes sense to combine local/global HA updating with
the FMIP mechanism.
/Karim

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


From mip4-bounces@ietf.org  Mon Mar 21 18:53:31 2005
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 SAA14834
	for <mip4-web-archive@ietf.org>; Mon, 21 Mar 2005 18:53:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDWnN-0000FL-TM
	for mip4-web-archive@ietf.org; Mon, 21 Mar 2005 18:58:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDWhH-0004P6-Eu; Mon, 21 Mar 2005 18:52:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDWhG-0004P1-9U
	for mip4@megatron.ietf.org; Mon, 21 Mar 2005 18:52:34 -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 SAA14789
	for <mip4@ietf.org>; Mon, 21 Mar 2005 18:52:31 -0500 (EST)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDWmO-0000EL-VG
	for mip4@ietf.org; Mon, 21 Mar 2005 18:57:54 -0500
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j2M0MI810069;
	Mon, 21 Mar 2005 16:22:18 -0800
X-mProtect: <200503220022> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp141217.americas.nokia.com (172.18.141.217,
	claiming to be "[172.18.141.217]")
	by darkstar.iprg.nokia.com smtpdK0sjvU; Mon, 21 Mar 2005 16:22:16 PST
Message-ID: <423F5E21.8030702@iprg.nokia.com>
Date: Mon, 21 Mar 2005 15:52:01 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Alexandru Petrescu <Alexandru.Petrescu@motorola.com>
Subject: Re: [Mip4] Request to consider FMIPv4 as a working group document
References: <200503182229.j2IMTwGa007066@mail.birdstep.com>
	<423EF91F.6030900@motorola.com>
In-Reply-To: <423EF91F.6030900@motorola.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Content-Transfer-Encoding: 7bit
Cc: espen@birdstep.com, "'Mobile IPv4 Mailing List'" <mip4@ietf.org>,
        "'Charles E.Perkins'" <charliep@iprg.nokia.com>,
        "'Rajeev Koodli'" <rajeev.koodli@nokia.com>
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Content-Transfer-Encoding: 7bit


Hi Alex, Espen and Kent,

thank you for your comments. We can clarify these points
in the draft. I will also provide some comments below.

Regards,

-Rajeev


Alexandru Petrescu wrote:

> [I have some comments on the draft, not the request itself, please
>  disregard if already discussed or clarified.]
>
> Espen Klovning wrote:
>
>> I do have some concerns that more or less reflect what Kent Leung has
>>  voiced in previous mails on the list. 
>
> >- AR == FA
> >- IP address management
>
> I tend to agree with this.
>
> The draft explains, but is not clear about what happens to FMIP when
> CCoA/DHCP _is_ used.  If DHCP is _not_ used with FMIP then the draft 
> should say so and in a coherent manner, IMHO; otherwise the generic 
> "compatibility" statements confuse me at three points.
>
We decouple new DHCP address acquistion latency by binding the current 
CoA (either CCoA obtained via DHCP or FA-CoA) to the NAR's IP address. 
So, when the MN arrives on the new link, it can do
DHCP/MIP while it can still use its previous CoA to send packets, and it 
receives packets sent to Previous CoA from the NAR.

>   "[First Scenario]: the access routers are not involved in IP address
>    management for the MN. The mobile nodes acquire a new care-of address
>    upon attaching to a new subnet link as they normally do."
>
> In some deployments, MN normally acquires an address with DHCP and the
> first-hop router is a DHCP Relay, so the AR practically _is_ involved in
> IP address management for the MN, although the AR is not a DHCP Server.
>  So the question coming to mind immediately is what is meant by "access
> routers are not involved in IP address management for the MN"?  Does
> that simply mean that AR is not a DHCP Server and is a DHCP Relay?
>
The description is contextual. When we mentioned "access routers are not
involved in IP address management..", it is in reference to the Second and
Third scenarios where the AR/FA provides an IP address.
But, you are right that the First scenario includes an AR acting as a DHCP
relay. The protocol itself does not depend on such a functionality. This can
be clarified.

> Second point is about DHCP and additional delays.  If vanilla DHCP is 
> used then the effective DHCP delays are in the range 1s-10s with a 
> 802.11b WEP first-hop, 100Mbit Ether and GHz computers.  That is very 
> large, easily influencing real-time.  It is not clear in the draft how 
> any of these numbers influence FMIP - is FMIP slower if vanilla DHCP 
> is used?
>
Since packet forwarding to/from MN does not depend on DHCP completion, it
does not affect. (See above. the forwarding is set up for Previous CoA).

> Third point is the apparent incoherence between abstract and body, 
> with respect to DHCP.  The abstract says "For reducing the IP address 
> configuration, the draft provides two alternatives" and none is DHCP. 
> Or, later in the body one can read "Address allocation and 
> configuration may be supported using DHCP or any other method."
>
This needs to be rectified. _If_ the NAR returns a New CoA for exclusive 
use of MN (CCoA) via
DHCP, the NAR must have a pool of addresses to choose from when 
processing HI.



> Just some thoughts...
>
Thanks again for your comments.

> Alex


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


From mip4-bounces@ietf.org  Mon Mar 21 20:59:03 2005
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 UAA25923
	for <mip4-web-archive@ietf.org>; Mon, 21 Mar 2005 20:59:03 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDYkr-0004cp-Vj
	for mip4-web-archive@ietf.org; Mon, 21 Mar 2005 21:04:26 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDYdX-00039c-Rj; Mon, 21 Mar 2005 20:56:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDYdW-00039S-8w
	for mip4@megatron.ietf.org; Mon, 21 Mar 2005 20:56:50 -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 UAA25703
	for <mip4@ietf.org>; Mon, 21 Mar 2005 20:56:48 -0500 (EST)
Received: from motgate4.mot.com ([144.189.100.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDYig-0004Wn-Ru
	for mip4@ietf.org; Mon, 21 Mar 2005 21:02:11 -0500
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate4.mot.com (8.12.11/Motgate4) with ESMTP id j2M21R3G017886
	for <mip4@ietf.org>; Mon, 21 Mar 2005 19:01:28 -0700 (MST)
Received: from il02exm13.corp.mot.com (il02exm13.corp.mot.com [10.0.111.24])
	by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id j2M1vrQS016544
	for <mip4@ietf.org>; Mon, 21 Mar 2005 19:57:53 -0600 (CST)
Received: by il02exm13 with Internet Mail Service (5.5.2657.72)
	id <D3S2T9D6>; Mon, 21 Mar 2005 19:56:46 -0600
Message-ID: <1B631E11D496D711BB2800065BFCB6A10C977920@il02exm13>
From: Narayanan Vidya-CVN065 <vidya@motorola.com>
To: "'Karim El-Malki \\(AL/EAB\\)'" <karim.el-malki@ericsson.com>,
        Rajeev Koodli  <rajeev@iprg.nokia.com>
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4
Date: Mon, 21 Mar 2005 19:56:36 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4

Karim,
I have a rather stupid question. All the triggers listed in table 1 of LLH list some L3 parameter or another that needs to be present in the trigger. This suggests to me that any kind of L2 trigger that is needed for LLH (Pre-reg or post-reg) requires the presence of the appropriate parameter listed in the "Parameters" row of the table. 

Am I missing something here? 

Vidya

-----Original Message-----
From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of Karim El-Malki \(AL/EAB\)
Sent: Monday, March 21, 2005 5:20 PM
To: Rajeev Koodli 
Cc: mip4@ietf.org
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and FMIPv4


>>I understand your point that you took FMIPv6 and applied
>>it to v4 to make FMIPv4. But that doesn't make it substantially 
>>different from Low Latency. Your spec does use link-layer triggers to 
>>be able to send the RtSolPr. An interface coming up in the MN is used 
>>just the same in Low Latency and is defined as a mobile trigger in Low
>>Latency (L2-LU). PRE-REG involves the MN getting such a
>>mobile trigger and sending a PrRtSol and receiving a
>>PrRtAdv. What's the difference compared to your spec?
>>  
>>
>As I explained below (and also itemized in the List below), the 
>essential difference is that LLH requires L2 to provide L3 information 
>(nFA, MN IP addresses, their MAC addresses etc.) via various L2-*T type 
>of triggers.
>This is a Big difference for us since we do not wish to change L2 to
>implement fast handovers. Both FMIPv6 and FMIPv4 work without
>requiring such changes to L2. 

That's not correct.
Let's take the case where the L3 handoff is initiated before
L2 handoff. Taking WLAN for example, in LLH the MN gets info from L2 (e.g. AP scan) and sends a PrRtSol to get a PrRtAdv containing information of the subnet it may move to. I can't see any change required to L2. Where is the difference compared to what you have described? The only difference is that we definied all "handoff hints" as L2 triggers, just as a result of the AP scan is defined as a mobile trigger. The LLH spec doesn't mandate the presence of all trigger types in all cases. It depends on what the L2 has to offer.

>>The messages are even called the same. Nothing special
>>or L2-dependent about this L2 trigger. For example PRE-REG
>>  
>>
>Well, the essential difference is what requirements LLH imposes on L2 
>triggers. Table 1 in LLH specifies what information is expected from L2 
>triggers including the nFA, MN IP addresses from the various L2-*T 
>triggers.

LLH can work with different types of L2 triggers (which is very different from requiring L2 changes) and supports the case you have described in FMIPv4. Table 1 specifies the different types of triggers that LLH can utilise. Note that it includes very simple triggers that work even on WLAN. It is wrong to say that all triggers in Table 1 are required on all L2s for LLH to work.

>>can be applied to WLAN using AP scans. I don't think that
>>the difference in packet formats makes it a substantially different 
>>spec from low latency.  Also, the other case you are considering 
>>involves an L3 handoff that happens after the MN attaches to the new 
>>link. This cannot really be considered a "fast" handoff, which would 
>>instead be where the handoff happens before or in parallel with the L2 
>>handoff.
>>  
>>
>Perhaps you have missed something.. The FMIP design allows movement 
>detection and router/FA discovery phases to be done prior to L2 
>handover. The "reactive" handover we refer to is the one where the FBU 
>is sent from the
>new link. But, the MN uses the neighborhood information via Proxy Router
>messages to determine movement detection and router/FA config 
>information of the
>new subnet. So, your description above is not accurate.

Note that I first addressed the L3-movement-before-L2 (where I am saying that FMIPv4 is no different from LLH) and then I wrote "the other case you are considering....". Am I incorrect in saying that FMIPv4 also supports the L3-handoff-after-L2-handoff case? I think I had read that case in FMIPv4 (i.e. FBU sent from new link). That's why I had asked about PFANE.

>>This L3-handoff-after-L2-handoff was already covered in the route 
>>optv4 spec using PFANE. You may have missed the question so I'll 
>>repeat it: did you consider the PFANE? Why aren't you just reusing the 
>>PFANE (Previous FA Notification
>>Extension) work for that scenario?
>>  
>>
>Please see above. The key difference with respect to Previous FA (what
>used to be Previous AR
>notification in v6) Notification is that you don't incur delays due to 
>movement detection and
>router/FA discovery.

If you are only considering the L3-handoff-before-L2-handoff case then there are very little differences between FMIPv4 and LLH for the reasons given above.

>So, apart from the independence from L2 to provide L3 information, the 
>other crucial difference is the decoupling of neighborhood discovery 
>from the actual
>handover signaling. This not only reduces the number of signaling
>messages
>during the handover itself, but also makes the reactive fast handovers 
>possible.

Again I can't see the crucial difference from LLH.
The ND messages are basically the same (even almost called the same): PrRtSol and PrRtAdv. LLH uses standard MIPv4 naming (Registration Request and Reply) while FMIPv4 achieves the same result but calls this an FBU. Tunnelling between FAs is supported in both specs. LLH furthermore supports anticipated HA updating or "local" HA updating (regional registrations). It seems to me that to make things "faster" one would want to update the local/global HA directly if possible since FA-FA routing can be inefficient in a tree-like network structure compared to updating a local HA. I am curious to understand why you have eliminated that option in FMIPv4 compared to LLH. Measurements performed on FMIPv6+HMIPv6 integration prove that it makes sense to combine local/global HA updating with the FMIP mechanism. /Karim

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


From mip4-bounces@ietf.org  Tue Mar 22 06:15:59 2005
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 GAA00274
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 06:15:59 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDhRv-0006nX-9T
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 06:21:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDhLy-0002fM-CE; Tue, 22 Mar 2005 06:15:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDhJx-00021F-NR
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 06:13:22 -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 GAA00141
	for <mip4@ietf.org>; Tue, 22 Mar 2005 06:13:11 -0500 (EST)
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDhPC-0006ka-PX
	for mip4@ietf.org; Tue, 22 Mar 2005 06:18:39 -0500
Received: from esealmw127.eemea.ericsson.se ([153.88.254.122])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j2MBD6g6028091; Tue, 22 Mar 2005 12:13:10 +0100 (MET)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 22 Mar 2005 12:13:06 +0100
Received: from esealmw115.eemea.ericsson.se ([153.88.200.6]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 22 Mar 2005 12:13:05 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and FMIPv4
Date: Tue, 22 Mar 2005 12:13:06 +0100
Message-ID: <24521B9781EAC745A4BE65966F69C9BE212AB6@esealmw115.eemea.ericsson.se>
Thread-Topic: [Mip4] RE: Differences between Low Latency Handovers and FMIPv4
Thread-index: AcUugmxNkS/+IXBjQf+502cas+h0tQAS7vWp
From: "Karim El-Malki \(AL/EAB\)" <karim.el-malki@ericsson.com>
To: "Narayanan Vidya-CVN065 " <vidya@motorola.com>,
        "Rajeev Koodli " <rajeev@iprg.nokia.com>
X-OriginalArrivalTime: 22 Mar 2005 11:13:05.0962 (UTC)
	FILETIME=[1F1740A0:01C52ED0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 20f22c03b5c66958bff5ef54fcda6e48
Content-Transfer-Encoding: quoted-printable

As you can see from the table some triggers provide very
little info (e.g. link up - L2UP). Others provide L2 OR
L3 parameters (e.g. L2-MT). The result of an AP scan to get
BSSIDs e.g. above a certain signal strength (SNR) is defined
as a trigger in LLH (L2-MT). No L3 parameters involved there.
That doesn't need any special change to L2s, like WLAN in
this example. So my point is that it is incorrect to say
that LLH requires special changes to L2. LLH covers different
types of L2s that provide different trigger info.
/Karim

-----Original Message-----
From: Narayanan Vidya-CVN065
To: Karim El-Malki (AL/EAB); Rajeev Koodli
Cc: mip4@ietf.org
Sent: 22/03/2005 02:56
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and =
FMIPv4

Karim,
I have a rather stupid question. All the triggers listed in table 1 of
LLH list some L3 parameter or another that needs to be present in the
trigger. This suggests to me that any kind of L2 trigger that is needed
for LLH (Pre-reg or post-reg) requires the presence of the appropriate
parameter listed in the "Parameters" row of the table.=20

Am I missing something here?=20

Vidya

-----Original Message-----
From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of
Karim El-Malki \(AL/EAB\)
Sent: Monday, March 21, 2005 5:20 PM
To: Rajeev Koodli=20
Cc: mip4@ietf.org
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and
FMIPv4


>>I understand your point that you took FMIPv6 and applied
>>it to v4 to make FMIPv4. But that doesn't make it substantially=20
>>different from Low Latency. Your spec does use link-layer triggers to=20
>>be able to send the RtSolPr. An interface coming up in the MN is used=20
>>just the same in Low Latency and is defined as a mobile trigger in Low
>>Latency (L2-LU). PRE-REG involves the MN getting such a
>>mobile trigger and sending a PrRtSol and receiving a
>>PrRtAdv. What's the difference compared to your spec?
>> =20
>>
>As I explained below (and also itemized in the List below), the=20
>essential difference is that LLH requires L2 to provide L3 information=20
>(nFA, MN IP addresses, their MAC addresses etc.) via various L2-*T type

>of triggers.
>This is a Big difference for us since we do not wish to change L2 to
>implement fast handovers. Both FMIPv6 and FMIPv4 work without
>requiring such changes to L2.=20

That's not correct.
Let's take the case where the L3 handoff is initiated before
L2 handoff. Taking WLAN for example, in LLH the MN gets info from L2
(e.g. AP scan) and sends a PrRtSol to get a PrRtAdv containing
information of the subnet it may move to. I can't see any change
required to L2. Where is the difference compared to what you have
described? The only difference is that we definied all "handoff hints"
as L2 triggers, just as a result of the AP scan is defined as a mobile
trigger. The LLH spec doesn't mandate the presence of all trigger types
in all cases. It depends on what the L2 has to offer.

>>The messages are even called the same. Nothing special
>>or L2-dependent about this L2 trigger. For example PRE-REG
>> =20
>>
>Well, the essential difference is what requirements LLH imposes on L2=20
>triggers. Table 1 in LLH specifies what information is expected from L2

>triggers including the nFA, MN IP addresses from the various L2-*T=20
>triggers.

LLH can work with different types of L2 triggers (which is very
different from requiring L2 changes) and supports the case you have
described in FMIPv4. Table 1 specifies the different types of triggers
that LLH can utilise. Note that it includes very simple triggers that
work even on WLAN. It is wrong to say that all triggers in Table 1 are
required on all L2s for LLH to work.

>>can be applied to WLAN using AP scans. I don't think that
>>the difference in packet formats makes it a substantially different=20
>>spec from low latency.  Also, the other case you are considering=20
>>involves an L3 handoff that happens after the MN attaches to the new=20
>>link. This cannot really be considered a "fast" handoff, which would=20
>>instead be where the handoff happens before or in parallel with the L2

>>handoff.
>> =20
>>
>Perhaps you have missed something.. The FMIP design allows movement=20
>detection and router/FA discovery phases to be done prior to L2=20
>handover. The "reactive" handover we refer to is the one where the FBU=20
>is sent from the
>new link. But, the MN uses the neighborhood information via Proxy
Router
>messages to determine movement detection and router/FA config=20
>information of the
>new subnet. So, your description above is not accurate.

Note that I first addressed the L3-movement-before-L2 (where I am saying
that FMIPv4 is no different from LLH) and then I wrote "the other case
you are considering....". Am I incorrect in saying that FMIPv4 also
supports the L3-handoff-after-L2-handoff case? I think I had read that
case in FMIPv4 (i.e. FBU sent from new link). That's why I had asked
about PFANE.

>>This L3-handoff-after-L2-handoff was already covered in the route=20
>>optv4 spec using PFANE. You may have missed the question so I'll=20
>>repeat it: did you consider the PFANE? Why aren't you just reusing the

>>PFANE (Previous FA Notification
>>Extension) work for that scenario?
>> =20
>>
>Please see above. The key difference with respect to Previous FA (what
>used to be Previous AR
>notification in v6) Notification is that you don't incur delays due to=20
>movement detection and
>router/FA discovery.

If you are only considering the L3-handoff-before-L2-handoff case then
there are very little differences between FMIPv4 and LLH for the reasons
given above.

>So, apart from the independence from L2 to provide L3 information, the=20
>other crucial difference is the decoupling of neighborhood discovery=20
>from the actual
>handover signaling. This not only reduces the number of signaling
>messages
>during the handover itself, but also makes the reactive fast handovers=20
>possible.

Again I can't see the crucial difference from LLH.
The ND messages are basically the same (even almost called the same):
PrRtSol and PrRtAdv. LLH uses standard MIPv4 naming (Registration
Request and Reply) while FMIPv4 achieves the same result but calls this
an FBU. Tunnelling between FAs is supported in both specs. LLH
furthermore supports anticipated HA updating or "local" HA updating
(regional registrations). It seems to me that to make things "faster"
one would want to update the local/global HA directly if possible since
FA-FA routing can be inefficient in a tree-like network structure
compared to updating a local HA. I am curious to understand why you have
eliminated that option in FMIPv4 compared to LLH. Measurements performed
on FMIPv6+HMIPv6 integration prove that it makes sense to combine
local/global HA updating with the FMIP mechanism. /Karim

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


From mip4-bounces@ietf.org  Tue Mar 22 08:30:09 2005
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 IAA11433
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 08:30:09 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDjXl-0002vy-Gu
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 08:35:37 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDjQN-0004xu-GA; Tue, 22 Mar 2005 08:27:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDjQL-0004xd-OV
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 08:27:57 -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 IAA11103
	for <mip4@ietf.org>; Tue, 22 Mar 2005 08:27:56 -0500 (EST)
Received: from mail-gw1.york.ac.uk ([144.32.128.246])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDjVc-0002sF-0m
	for mip4@ietf.org; Tue, 22 Mar 2005 08:33:24 -0500
Received: from grouse (grouse.ohm.york.ac.uk [144.32.137.104])
	by mail-gw1.york.ac.uk (8.12.10/8.12.10) with SMTP id j2MDRd9r008632;
	Tue, 22 Mar 2005 13:27:39 GMT
Message-ID: <00c101c52ee3$2dccd660$68892090@grouse>
From: "Jee J.Z." <jz105@york.ac.uk>
To: "subrata goswami" <sgoswami@umich.edu>
References: <420BB87E.7090008@umich.edu>
Subject: Re: [Mip4] New ID: End Node based IP Mobility
Date: Tue, 22 Mar 2005 13:29:30 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-York-MailScanner: Found to be clean
X-York-MailScanner-From: jz105@york.ac.uk
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Content-Transfer-Encoding: 7bit
Cc: Mobile IP v4 <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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Content-Transfer-Encoding: 7bit

Hi Subrata,

Thank you for writing this concise ID. I have a few question:

1. Section 2: "...The CN would still use ipx1 as destination address for all
outgoing packets, which would result in all packets sent to subnet X2..."
Are you trying to say "...all packets sent to subnet X1."?

2. It seems you are trying to use only end nodes to support mobility. And as
you have pointed out, how subnet changes are detected is beyond the scope of
this document. However, IMHO, it is hard to quickly detect subnet changes
quickly without the network assistance. Also, how does the access network
know it should offer service to the MN without any securtiy entities in the
network for supporting mobility?

3. It seems you are considering the case that the MN can only communicate
with one access subnet at a time. Therefore, the CN receiving Subnet Change
Challenge responses from both old and new subnets could be viewed as
spoofing. What if the MN can simultaneously communicate with both new and
old access subnets at least during handovers? Are you assuming the MN always
sends only one Subnet Change Challenge response in this case?

4. Without the network assistance, how do you suppose to handle those
mis-routed packets to the old subnet after the MN connects to the new
subnet?

The ID looks like a simple interesting idea, but it seems a lot of issues
are waiting to be considered. Maybe you think it could be too earlly?

Jee

----- Original Message ----- 
From: "subrata goswami" <sgoswami@umich.edu>
To: <mip4@ietf.org>
Sent: Thursday, February 10, 2005 7:39 PM
Subject: [Mip4] New ID: End Node based IP Mobility


> A new Internet Draft is available on mobility support in IP networks.
>
> Title: IPv4 Mobility through Peer Signaling
>
> ID: draft-goswami-mip4-peer-signaling-00.txt
>
> Abstract:  This document describes a way to perform mobility in IPv4
> (potentially IPv6) without requiring any new entity in networks
> infrastructure (e.g. Home Agent, Foreign Agent, etc.). Instead of using
> infrastructure entities this method delegates all the mobility function
> to the end nodes. The method relies on source and destination address
> translation at the end nodes, and signaling between end nodes to perform
> hand offs - all these function can be encapsulated in an entity called
> Mobility Agent (MA) in the end nodes.
>
> URL:
> https://datatracker.ietf.org/public/idindex.cgi?command=id_detail&id=12788
>
>
> -- 
> 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/


From mip4-bounces@ietf.org  Tue Mar 22 11:57:16 2005
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 LAA04678
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 11:57:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDmmF-0002gl-IP
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 12:02:47 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDmdh-0004wT-3Z; Tue, 22 Mar 2005 11:53:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDmdf-0004wJ-GT
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 11:53:55 -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 LAA04320
	for <mip4@ietf.org>; Tue, 22 Mar 2005 11:53:53 -0500 (EST)
Received: from motgate7.mot.com ([129.188.136.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDmix-0002a2-OR
	for mip4@ietf.org; Tue, 22 Mar 2005 11:59:24 -0500
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate7.mot.com (Motorola/Motgate7) with ESMTP id j2MGhQ05023169
	for <mip4@ietf.org>; Tue, 22 Mar 2005 09:43:26 -0700 (MST)
Received: from il02exm13.corp.mot.com (il02exm13.corp.mot.com [10.0.111.24])
	by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id j2MGt93a006202
	for <mip4@ietf.org>; Tue, 22 Mar 2005 10:55:10 -0600 (CST)
Received: by il02exm13 with Internet Mail Service (5.5.2657.72)
	id <D3S243S4>; Tue, 22 Mar 2005 10:53:48 -0600
Message-ID: <1B631E11D496D711BB2800065BFCB6A11B7A6E12@il02exm13>
From: Narayanan Vidya-CVN065 <vidya@motorola.com>
To: "'Karim El-Malki \\(AL/EAB\\)'" <karim.el-malki@ericsson.com>,
        Rajeev Koodli  <rajeev@iprg.nokia.com>
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4
Date: Tue, 22 Mar 2005 10:53:39 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a1852b4f554b02e7e4548cc7928acc1f
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172

Maybe I am just missing something important here. Sorry, but I still don't understand. 

Both in the L2LU and L2MT, it seems like LLH is expecting at least the nFA L2 address (if not the IP address) or some nFA identifier - is that true? 

Typically, this information is not available as a result of the AP scan, right? The FA is most likely more than one L2 hop away from the MN. An AP, by default, will not include any information about the nFA in its beacon. 

What am I missing here? 

Thanks,
Vidya

-----Original Message-----
From: Karim El-Malki \(AL/EAB\) [mailto:karim.el-malki@ericsson.com] 
Sent: Tuesday, March 22, 2005 5:13 AM
To: Narayanan Vidya-CVN065; Rajeev Koodli 
Cc: mip4@ietf.org
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and FMIPv4


As you can see from the table some triggers provide very
little info (e.g. link up - L2UP). Others provide L2 OR
L3 parameters (e.g. L2-MT). The result of an AP scan to get BSSIDs e.g. above a certain signal strength (SNR) is defined as a trigger in LLH (L2-MT). No L3 parameters involved there. That doesn't need any special change to L2s, like WLAN in this example. So my point is that it is incorrect to say that LLH requires special changes to L2. LLH covers different types of L2s that provide different trigger info. /Karim

-----Original Message-----
From: Narayanan Vidya-CVN065
To: Karim El-Malki (AL/EAB); Rajeev Koodli
Cc: mip4@ietf.org
Sent: 22/03/2005 02:56
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and FMIPv4

Karim,
I have a rather stupid question. All the triggers listed in table 1 of LLH list some L3 parameter or another that needs to be present in the trigger. This suggests to me that any kind of L2 trigger that is needed for LLH (Pre-reg or post-reg) requires the presence of the appropriate parameter listed in the "Parameters" row of the table. 

Am I missing something here? 

Vidya

-----Original Message-----
From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of Karim El-Malki \(AL/EAB\)
Sent: Monday, March 21, 2005 5:20 PM
To: Rajeev Koodli 
Cc: mip4@ietf.org
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and FMIPv4


>>I understand your point that you took FMIPv6 and applied
>>it to v4 to make FMIPv4. But that doesn't make it substantially
>>different from Low Latency. Your spec does use link-layer triggers to 
>>be able to send the RtSolPr. An interface coming up in the MN is used 
>>just the same in Low Latency and is defined as a mobile trigger in Low
>>Latency (L2-LU). PRE-REG involves the MN getting such a
>>mobile trigger and sending a PrRtSol and receiving a
>>PrRtAdv. What's the difference compared to your spec?
>>  
>>
>As I explained below (and also itemized in the List below), the
>essential difference is that LLH requires L2 to provide L3 information 
>(nFA, MN IP addresses, their MAC addresses etc.) via various L2-*T type

>of triggers.
>This is a Big difference for us since we do not wish to change L2 to 
>implement fast handovers. Both FMIPv6 and FMIPv4 work without requiring 
>such changes to L2.

That's not correct.
Let's take the case where the L3 handoff is initiated before
L2 handoff. Taking WLAN for example, in LLH the MN gets info from L2 (e.g. AP scan) and sends a PrRtSol to get a PrRtAdv containing information of the subnet it may move to. I can't see any change required to L2. Where is the difference compared to what you have described? The only difference is that we definied all "handoff hints" as L2 triggers, just as a result of the AP scan is defined as a mobile trigger. The LLH spec doesn't mandate the presence of all trigger types in all cases. It depends on what the L2 has to offer.

>>The messages are even called the same. Nothing special
>>or L2-dependent about this L2 trigger. For example PRE-REG
>>  
>>
>Well, the essential difference is what requirements LLH imposes on L2
>triggers. Table 1 in LLH specifies what information is expected from L2

>triggers including the nFA, MN IP addresses from the various L2-*T
>triggers.

LLH can work with different types of L2 triggers (which is very different from requiring L2 changes) and supports the case you have described in FMIPv4. Table 1 specifies the different types of triggers that LLH can utilise. Note that it includes very simple triggers that work even on WLAN. It is wrong to say that all triggers in Table 1 are required on all L2s for LLH to work.

>>can be applied to WLAN using AP scans. I don't think that
>>the difference in packet formats makes it a substantially different
>>spec from low latency.  Also, the other case you are considering 
>>involves an L3 handoff that happens after the MN attaches to the new 
>>link. This cannot really be considered a "fast" handoff, which would 
>>instead be where the handoff happens before or in parallel with the L2

>>handoff.
>>  
>>
>Perhaps you have missed something.. The FMIP design allows movement
>detection and router/FA discovery phases to be done prior to L2 
>handover. The "reactive" handover we refer to is the one where the FBU 
>is sent from the
>new link. But, the MN uses the neighborhood information via Proxy
Router
>messages to determine movement detection and router/FA config
>information of the
>new subnet. So, your description above is not accurate.

Note that I first addressed the L3-movement-before-L2 (where I am saying that FMIPv4 is no different from LLH) and then I wrote "the other case you are considering....". Am I incorrect in saying that FMIPv4 also supports the L3-handoff-after-L2-handoff case? I think I had read that case in FMIPv4 (i.e. FBU sent from new link). That's why I had asked about PFANE.

>>This L3-handoff-after-L2-handoff was already covered in the route
>>optv4 spec using PFANE. You may have missed the question so I'll 
>>repeat it: did you consider the PFANE? Why aren't you just reusing the

>>PFANE (Previous FA Notification
>>Extension) work for that scenario?
>>  
>>
>Please see above. The key difference with respect to Previous FA (what 
>used to be Previous AR notification in v6) Notification is that you 
>don't incur delays due to movement detection and
>router/FA discovery.

If you are only considering the L3-handoff-before-L2-handoff case then there are very little differences between FMIPv4 and LLH for the reasons given above.

>So, apart from the independence from L2 to provide L3 information, the
>other crucial difference is the decoupling of neighborhood discovery 
>from the actual
>handover signaling. This not only reduces the number of signaling
>messages
>during the handover itself, but also makes the reactive fast handovers 
>possible.

Again I can't see the crucial difference from LLH.
The ND messages are basically the same (even almost called the same): PrRtSol and PrRtAdv. LLH uses standard MIPv4 naming (Registration Request and Reply) while FMIPv4 achieves the same result but calls this an FBU. Tunnelling between FAs is supported in both specs. LLH furthermore supports anticipated HA updating or "local" HA updating (regional registrations). It seems to me that to make things "faster" one would want to update the local/global HA directly if possible since FA-FA routing can be inefficient in a tree-like network structure compared to updating a local HA. I am curious to understand why you have eliminated that option in FMIPv4 compared to LLH. Measurements performed on FMIPv6+HMIPv6 integration prove that it makes sense to combine local/global HA updating with the FMIP mechanism. /Karim

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


From mip4-bounces@ietf.org  Tue Mar 22 12:41:02 2005
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 MAA09630
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 12:41:02 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDnSb-0004cj-Vj
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 12:46:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDnLs-0005WL-7D; Tue, 22 Mar 2005 12:39:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDnLo-0005WD-Ls
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 12:39:34 -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 MAA09493
	for <mip4@ietf.org>; Tue, 22 Mar 2005 12:39:29 -0500 (EST)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDnR7-0004aK-1y
	for mip4@ietf.org; Tue, 22 Mar 2005 12:45:01 -0500
Message-ID: <025c01c52f06$413838c0$0f6115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Narayanan Vidya-CVN065" <vidya@motorola.com>,
        "'Karim El-Malki \\(AL/EAB\\)'" <karim.el-malki@ericsson.com>,
        "Rajeev Koodli" <rajeev@iprg.nokia.com>
References: <1B631E11D496D711BB2800065BFCB6A10C977920@il02exm13>
Subject: Re: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4
Date: Tue, 22 Mar 2005 09:40:28 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 86f85b2f88b0d50615aed44a7f9e33c7
Content-Transfer-Encoding: 7bit
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31b28e25e9d13a22020d8b7aedc9832c
Content-Transfer-Encoding: 7bit

I think this whole discussion about L2 triggers and LLH is a red herring.
People are taking the wording "L2 trigger" too literally. It doesn't
actually have to be a protocol message in the L2 protocol, it just must be
indication that handover has occured or will occur. The handover indication
doesn't have to include all the L3 information in Table 1 in one L2 message.
It can be deduced. For example, using something like CARD or even the RtPrxy
messages, the MN can build up a table of AP L2 address to FA address map,
and use that. I believe that is what Karim means when he says that FMIP also
needs this kind of information. Unless an FMIP MN has some way to know that
a handover has occured or will occur, there's no FBU. And unless it has some
information about what new subnet the MN is in or will be, it can't put that
information into the FBU to tell the old FA where to send packets.

I still believe there's value for FMIPv4, believe it is superior to LLH if
host based all-L3 handover optimization is required, and support work on it;
however, this whole argument of FMIP v.s. LLH strikes me as being something
like the medieval argument about how many angles can dance on the head of a
pin. Wireless LAN deployments are increasingly going in the direction of
wireless LAN switches (60% of new purchases and practically all upgrades),
and these switches already have nonstandardized solutions for "IP Mobility",
which, in effect, means tunneling L2 frames in L3 between subnets.
Unfortunately, vendors would like to keep it that way, since having a
standardized solution means that enterprise customers and service providers
would be free to mix and match solutions and less likely to go single
supplier. So FMIP is likely to be of limited interest for WLAN deployments
going forward. Perhaps 3GPP2 is interested in it? Though they already have
their own solution in the A10/A11 interface, which looks strikingly like the
solution adopted by the WLAN switch vendors.

Anyway, if this WG was serious about its charter to focus on deployment, it
would start up an activity to standardize WLAN switching "IP mobility".

            jak


----- Original Message ----- 
From: "Narayanan Vidya-CVN065" <vidya@motorola.com>
To: "'Karim El-Malki \(AL/EAB\)'" <karim.el-malki@ericsson.com>; "Rajeev
Koodli" <rajeev@iprg.nokia.com>
Cc: <mip4@ietf.org>
Sent: Monday, March 21, 2005 5:56 PM
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and FMIP
v4


> Karim,
> I have a rather stupid question. All the triggers listed in table 1 of LLH
list some L3 parameter or another that needs to be present in the trigger.
This suggests to me that any kind of L2 trigger that is needed for LLH
(Pre-reg or post-reg) requires the presence of the appropriate parameter
listed in the "Parameters" row of the table.
>
> Am I missing something here?
>
> Vidya
>
> -----Original Message-----
> From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of
Karim El-Malki \(AL/EAB\)
> Sent: Monday, March 21, 2005 5:20 PM
> To: Rajeev Koodli
> Cc: mip4@ietf.org
> Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and
FMIPv4
>
>
> >>I understand your point that you took FMIPv6 and applied
> >>it to v4 to make FMIPv4. But that doesn't make it substantially
> >>different from Low Latency. Your spec does use link-layer triggers to
> >>be able to send the RtSolPr. An interface coming up in the MN is used
> >>just the same in Low Latency and is defined as a mobile trigger in Low
> >>Latency (L2-LU). PRE-REG involves the MN getting such a
> >>mobile trigger and sending a PrRtSol and receiving a
> >>PrRtAdv. What's the difference compared to your spec?
> >>
> >>
> >As I explained below (and also itemized in the List below), the
> >essential difference is that LLH requires L2 to provide L3 information
> >(nFA, MN IP addresses, their MAC addresses etc.) via various L2-*T type
> >of triggers.
> >This is a Big difference for us since we do not wish to change L2 to
> >implement fast handovers. Both FMIPv6 and FMIPv4 work without
> >requiring such changes to L2.
>
> That's not correct.
> Let's take the case where the L3 handoff is initiated before
> L2 handoff. Taking WLAN for example, in LLH the MN gets info from L2 (e.g.
AP scan) and sends a PrRtSol to get a PrRtAdv containing information of the
subnet it may move to. I can't see any change required to L2. Where is the
difference compared to what you have described? The only difference is that
we definied all "handoff hints" as L2 triggers, just as a result of the AP
scan is defined as a mobile trigger. The LLH spec doesn't mandate the
presence of all trigger types in all cases. It depends on what the L2 has to
offer.
>
> >>The messages are even called the same. Nothing special
> >>or L2-dependent about this L2 trigger. For example PRE-REG
> >>
> >>
> >Well, the essential difference is what requirements LLH imposes on L2
> >triggers. Table 1 in LLH specifies what information is expected from L2
> >triggers including the nFA, MN IP addresses from the various L2-*T
> >triggers.
>
> LLH can work with different types of L2 triggers (which is very different
from requiring L2 changes) and supports the case you have described in
FMIPv4. Table 1 specifies the different types of triggers that LLH can
utilise. Note that it includes very simple triggers that work even on WLAN.
It is wrong to say that all triggers in Table 1 are required on all L2s for
LLH to work.
>
> >>can be applied to WLAN using AP scans. I don't think that
> >>the difference in packet formats makes it a substantially different
> >>spec from low latency.  Also, the other case you are considering
> >>involves an L3 handoff that happens after the MN attaches to the new
> >>link. This cannot really be considered a "fast" handoff, which would
> >>instead be where the handoff happens before or in parallel with the L2
> >>handoff.
> >>
> >>
> >Perhaps you have missed something.. The FMIP design allows movement
> >detection and router/FA discovery phases to be done prior to L2
> >handover. The "reactive" handover we refer to is the one where the FBU
> >is sent from the
> >new link. But, the MN uses the neighborhood information via Proxy Router
> >messages to determine movement detection and router/FA config
> >information of the
> >new subnet. So, your description above is not accurate.
>
> Note that I first addressed the L3-movement-before-L2 (where I am saying
that FMIPv4 is no different from LLH) and then I wrote "the other case you
are considering....". Am I incorrect in saying that FMIPv4 also supports the
L3-handoff-after-L2-handoff case? I think I had read that case in FMIPv4
(i.e. FBU sent from new link). That's why I had asked about PFANE.
>
> >>This L3-handoff-after-L2-handoff was already covered in the route
> >>optv4 spec using PFANE. You may have missed the question so I'll
> >>repeat it: did you consider the PFANE? Why aren't you just reusing the
> >>PFANE (Previous FA Notification
> >>Extension) work for that scenario?
> >>
> >>
> >Please see above. The key difference with respect to Previous FA (what
> >used to be Previous AR
> >notification in v6) Notification is that you don't incur delays due to
> >movement detection and
> >router/FA discovery.
>
> If you are only considering the L3-handoff-before-L2-handoff case then
there are very little differences between FMIPv4 and LLH for the reasons
given above.
>
> >So, apart from the independence from L2 to provide L3 information, the
> >other crucial difference is the decoupling of neighborhood discovery
> >from the actual
> >handover signaling. This not only reduces the number of signaling
> >messages
> >during the handover itself, but also makes the reactive fast handovers
> >possible.
>
> Again I can't see the crucial difference from LLH.
> The ND messages are basically the same (even almost called the same):
PrRtSol and PrRtAdv. LLH uses standard MIPv4 naming (Registration Request
and Reply) while FMIPv4 achieves the same result but calls this an FBU.
Tunnelling between FAs is supported in both specs. LLH furthermore supports
anticipated HA updating or "local" HA updating (regional registrations). It
seems to me that to make things "faster" one would want to update the
local/global HA directly if possible since FA-FA routing can be inefficient
in a tree-like network structure compared to updating a local HA. I am
curious to understand why you have eliminated that option in FMIPv4 compared
to LLH. Measurements performed on FMIPv6+HMIPv6 integration prove that it
makes sense to combine local/global HA updating with the FMIP mechanism.
/Karim
>
> -- 
> 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/
>



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


From mip4-bounces@ietf.org  Tue Mar 22 13:12:07 2005
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 NAA13466
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 13:12:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDnwg-0005vr-RN
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 13:17:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDnqY-0003Br-SS; Tue, 22 Mar 2005 13:11:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDnqW-0003AZ-Ry
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 13:11:17 -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 NAA13345
	for <mip4@ietf.org>; Tue, 22 Mar 2005 13:11:14 -0500 (EST)
Received: from wanderer.mr.itd.umich.edu ([141.211.93.146])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDnvp-0005us-8e
	for mip4@ietf.org; Tue, 22 Mar 2005 13:16:46 -0500
Received: from [10.10.10.111] (mail.greenfieldnetworks.com [64.220.152.74])
	by wanderer.mr.itd.umich.edu (smtp) with ESMTP id j2MIB7rj012948;
	Tue, 22 Mar 2005 13:11:08 -0500
Message-ID: <42405FB6.10006@umich.edu>
Date: Tue, 22 Mar 2005 10:11:02 -0800
From: subrata goswami <sgoswami@umich.edu>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: jz105@york.ac.uk
Subject: Re: [Mip4] New ID: End Node based IP Mobility
References: <420BB87E.7090008@umich.edu>
	<00c101c52ee3$2dccd660$68892090@grouse>
In-Reply-To: <00c101c52ee3$2dccd660$68892090@grouse>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Content-Transfer-Encoding: 7bit
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813
Content-Transfer-Encoding: 7bit

please see in line for any answers.

Jee J.Z. wrote:

>Hi Subrata,
>
>Thank you for writing this concise ID. I have a few question:
>
>1. Section 2: "...The CN would still use ipx1 as destination address for all
>outgoing packets, which would result in all packets sent to subnet X2..."
>Are you trying to say "...all packets sent to subnet X1."?
>
>  
>
no,  packets would be routed to subnet X2 as a result of translation
in the sender.

>2. It seems you are trying to use only end nodes to support mobility. And as
>you have pointed out, how subnet changes are detected is beyond the scope of
>this document. However, IMHO, it is hard to quickly detect subnet changes
>quickly without the network assistance. Also, how does the access network
>know it should offer service to the MN without any securtiy entities in the
>network for supporting mobility?
>  
>
many different approaches have been suggested for detecting network
change, any of these methods can be used.
agreed that some these methods are very slow.

as mobility is entirely handled by  the end nodes, the network does not
really need to get involve (i.e. regular routing
handles all packets).

>3. It seems you are considering the case that the MN can only communicate
>with one access subnet at a time. Therefore, the CN receiving Subnet Change
>Challenge responses from both old and new subnets could be viewed as
>spoofing. What if the MN can simultaneously communicate with both new and
>old access subnets at least during handovers? Are you assuming the MN always
>sends only one Subnet Change Challenge response in this case?
>  
>
there is not really any reason why the MN needs to be connected to only
one subnet.   i do not think there is any
reason why the MN can not talk to both old and new , although at the
point the draft does not address that.

>4. Without the network assistance, how do you suppose to handle those
>mis-routed packets to the old subnet after the MN connects to the new
>subnet?
>  
>
this can be handled by buffering packets at the sender - will be added
in the next version of the draft.
buffering is not required if only TCP type of traffic is supported.

>The ID looks like a simple interesting idea, but it seems a lot of issues
>are waiting to be considered. Maybe you think it could be too earlly?
>  
>
thanks for your comments - will address these issues in the next revision.

>Jee
>
>----- Original Message ----- 
>From: "subrata goswami" <sgoswami@umich.edu>
>To: <mip4@ietf.org>
>Sent: Thursday, February 10, 2005 7:39 PM
>Subject: [Mip4] New ID: End Node based IP Mobility
>
>
>  
>
>>A new Internet Draft is available on mobility support in IP networks.
>>
>>Title: IPv4 Mobility through Peer Signaling
>>
>>ID: draft-goswami-mip4-peer-signaling-00.txt
>>
>>Abstract:  This document describes a way to perform mobility in IPv4
>>(potentially IPv6) without requiring any new entity in networks
>>infrastructure (e.g. Home Agent, Foreign Agent, etc.). Instead of using
>>infrastructure entities this method delegates all the mobility function
>>to the end nodes. The method relies on source and destination address
>>translation at the end nodes, and signaling between end nodes to perform
>>hand offs - all these function can be encapsulated in an entity called
>>Mobility Agent (MA) in the end nodes.
>>
>>URL:
>>https://datatracker.ietf.org/public/idindex.cgi?command=id_detail&id=12788
>>
>>
>>-- 
>>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/


From mip4-bounces@ietf.org  Tue Mar 22 13:59:58 2005
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 NAA18376
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 13:59:58 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDogz-0007vG-4F
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 14:05:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDoa2-0003NZ-LZ; Tue, 22 Mar 2005 13:58:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDoa1-0003NT-9e
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 13:58:17 -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 NAA18249
	for <mip4@ietf.org>; Tue, 22 Mar 2005 13:58:16 -0500 (EST)
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDofK-0007t0-NB
	for mip4@ietf.org; Tue, 22 Mar 2005 14:03:47 -0500
Received: from esealmw129.eemea.ericsson.se ([153.88.254.120])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j2MIwAfm022875; Tue, 22 Mar 2005 19:58:10 +0100 (MET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 22 Mar 2005 19:58:08 +0100
Received: from esealmw115.eemea.ericsson.se ([153.88.200.6]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 22 Mar 2005 19:58:08 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and FMIPv4
Date: Tue, 22 Mar 2005 19:58:07 +0100
Message-ID: <24521B9781EAC745A4BE65966F69C9BE212ABB@esealmw115.eemea.ericsson.se>
Thread-Topic: [Mip4] RE: Differences between Low Latency Handovers and FMIPv4
Thread-index: AcUu/7vFefsZt31DSMK2F44OE62SNAAD8TLT
From: "Karim El-Malki \(AL/EAB\)" <karim.el-malki@ericsson.com>
To: "Narayanan Vidya-CVN065 " <vidya@motorola.com>,
        "Rajeev Koodli " <rajeev@iprg.nokia.com>
X-OriginalArrivalTime: 22 Mar 2005 18:58:08.0875 (UTC)
	FILETIME=[1685E3B0:01C52F11]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 88b11fc64c1bfdb4425294ef5374ca07
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a0534e6179a1e260079328e8b03c7901
Content-Transfer-Encoding: quoted-printable

Here is one way of doing it: the BSSID would be used
in the PrRtSol from MN to oFA, and the oFA would need
to know which AP/BSSID is served by which FA. The BSSID
would therefore be the nFA "identifier". It seems to me
like this is a generic problem with all solutions that
try to anticipate mobility on WLAN. Or am I missing a
case where we can do without these scans and still
achieve L3 mobility before or in parallel with L2
mobility?
/Karim

-----Original Message-----
From: Narayanan Vidya-CVN065
To: Karim El-Malki (AL/EAB); Rajeev Koodli
Cc: mip4@ietf.org
Sent: 22/03/2005 17:53
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and =
FMIPv4

Maybe I am just missing something important here. Sorry, but I still
don't understand.=20

Both in the L2LU and L2MT, it seems like LLH is expecting at least the
nFA L2 address (if not the IP address) or some nFA identifier - is that
true?=20

Typically, this information is not available as a result of the AP scan,
right? The FA is most likely more than one L2 hop away from the MN. An
AP, by default, will not include any information about the nFA in its
beacon.=20

What am I missing here?=20

Thanks,
Vidya

-----Original Message-----
From: Karim El-Malki \(AL/EAB\) [mailto:karim.el-malki@ericsson.com]=20
Sent: Tuesday, March 22, 2005 5:13 AM
To: Narayanan Vidya-CVN065; Rajeev Koodli=20
Cc: mip4@ietf.org
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and
FMIPv4


As you can see from the table some triggers provide very
little info (e.g. link up - L2UP). Others provide L2 OR
L3 parameters (e.g. L2-MT). The result of an AP scan to get BSSIDs e.g.
above a certain signal strength (SNR) is defined as a trigger in LLH
(L2-MT). No L3 parameters involved there. That doesn't need any special
change to L2s, like WLAN in this example. So my point is that it is
incorrect to say that LLH requires special changes to L2. LLH covers
different types of L2s that provide different trigger info. /Karim

-----Original Message-----
From: Narayanan Vidya-CVN065
To: Karim El-Malki (AL/EAB); Rajeev Koodli
Cc: mip4@ietf.org
Sent: 22/03/2005 02:56
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and
FMIPv4

Karim,
I have a rather stupid question. All the triggers listed in table 1 of
LLH list some L3 parameter or another that needs to be present in the
trigger. This suggests to me that any kind of L2 trigger that is needed
for LLH (Pre-reg or post-reg) requires the presence of the appropriate
parameter listed in the "Parameters" row of the table.=20

Am I missing something here?=20

Vidya

-----Original Message-----
From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of
Karim El-Malki \(AL/EAB\)
Sent: Monday, March 21, 2005 5:20 PM
To: Rajeev Koodli=20
Cc: mip4@ietf.org
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and
FMIPv4


>>I understand your point that you took FMIPv6 and applied
>>it to v4 to make FMIPv4. But that doesn't make it substantially
>>different from Low Latency. Your spec does use link-layer triggers to=20
>>be able to send the RtSolPr. An interface coming up in the MN is used=20
>>just the same in Low Latency and is defined as a mobile trigger in Low
>>Latency (L2-LU). PRE-REG involves the MN getting such a
>>mobile trigger and sending a PrRtSol and receiving a
>>PrRtAdv. What's the difference compared to your spec?
>> =20
>>
>As I explained below (and also itemized in the List below), the
>essential difference is that LLH requires L2 to provide L3 information=20
>(nFA, MN IP addresses, their MAC addresses etc.) via various L2-*T type

>of triggers.
>This is a Big difference for us since we do not wish to change L2 to=20
>implement fast handovers. Both FMIPv6 and FMIPv4 work without requiring

>such changes to L2.

That's not correct.
Let's take the case where the L3 handoff is initiated before
L2 handoff. Taking WLAN for example, in LLH the MN gets info from L2
(e.g. AP scan) and sends a PrRtSol to get a PrRtAdv containing
information of the subnet it may move to. I can't see any change
required to L2. Where is the difference compared to what you have
described? The only difference is that we definied all "handoff hints"
as L2 triggers, just as a result of the AP scan is defined as a mobile
trigger. The LLH spec doesn't mandate the presence of all trigger types
in all cases. It depends on what the L2 has to offer.

>>The messages are even called the same. Nothing special
>>or L2-dependent about this L2 trigger. For example PRE-REG
>> =20
>>
>Well, the essential difference is what requirements LLH imposes on L2
>triggers. Table 1 in LLH specifies what information is expected from L2

>triggers including the nFA, MN IP addresses from the various L2-*T
>triggers.

LLH can work with different types of L2 triggers (which is very
different from requiring L2 changes) and supports the case you have
described in FMIPv4. Table 1 specifies the different types of triggers
that LLH can utilise. Note that it includes very simple triggers that
work even on WLAN. It is wrong to say that all triggers in Table 1 are
required on all L2s for LLH to work.

>>can be applied to WLAN using AP scans. I don't think that
>>the difference in packet formats makes it a substantially different
>>spec from low latency.  Also, the other case you are considering=20
>>involves an L3 handoff that happens after the MN attaches to the new=20
>>link. This cannot really be considered a "fast" handoff, which would=20
>>instead be where the handoff happens before or in parallel with the L2

>>handoff.
>> =20
>>
>Perhaps you have missed something.. The FMIP design allows movement
>detection and router/FA discovery phases to be done prior to L2=20
>handover. The "reactive" handover we refer to is the one where the FBU=20
>is sent from the
>new link. But, the MN uses the neighborhood information via Proxy
Router
>messages to determine movement detection and router/FA config
>information of the
>new subnet. So, your description above is not accurate.

Note that I first addressed the L3-movement-before-L2 (where I am saying
that FMIPv4 is no different from LLH) and then I wrote "the other case
you are considering....". Am I incorrect in saying that FMIPv4 also
supports the L3-handoff-after-L2-handoff case? I think I had read that
case in FMIPv4 (i.e. FBU sent from new link). That's why I had asked
about PFANE.

>>This L3-handoff-after-L2-handoff was already covered in the route
>>optv4 spec using PFANE. You may have missed the question so I'll=20
>>repeat it: did you consider the PFANE? Why aren't you just reusing the

>>PFANE (Previous FA Notification
>>Extension) work for that scenario?
>> =20
>>
>Please see above. The key difference with respect to Previous FA (what=20
>used to be Previous AR notification in v6) Notification is that you=20
>don't incur delays due to movement detection and
>router/FA discovery.

If you are only considering the L3-handoff-before-L2-handoff case then
there are very little differences between FMIPv4 and LLH for the reasons
given above.

>So, apart from the independence from L2 to provide L3 information, the
>other crucial difference is the decoupling of neighborhood discovery=20
>from the actual
>handover signaling. This not only reduces the number of signaling
>messages
>during the handover itself, but also makes the reactive fast handovers=20
>possible.

Again I can't see the crucial difference from LLH.
The ND messages are basically the same (even almost called the same):
PrRtSol and PrRtAdv. LLH uses standard MIPv4 naming (Registration
Request and Reply) while FMIPv4 achieves the same result but calls this
an FBU. Tunnelling between FAs is supported in both specs. LLH
furthermore supports anticipated HA updating or "local" HA updating
(regional registrations). It seems to me that to make things "faster"
one would want to update the local/global HA directly if possible since
FA-FA routing can be inefficient in a tree-like network structure
compared to updating a local HA. I am curious to understand why you have
eliminated that option in FMIPv4 compared to LLH. Measurements performed
on FMIPv6+HMIPv6 integration prove that it makes sense to combine
local/global HA updating with the FMIP mechanism. /Karim

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


From mip4-bounces@ietf.org  Tue Mar 22 14:15:17 2005
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 OAA19865
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 14:15:17 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDovo-0008WD-7Y
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 14:20:48 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDope-00069k-KT; Tue, 22 Mar 2005 14:14:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDopd-00069f-Dt
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 14:14:25 -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 OAA19775
	for <mip4@ietf.org>; Tue, 22 Mar 2005 14:14:24 -0500 (EST)
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDouw-0008UY-Vn
	for mip4@ietf.org; Tue, 22 Mar 2005 14:19:55 -0500
Received: from esealmw126.eemea.ericsson.se ([153.88.254.123])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j2MJEJfm024293; Tue, 22 Mar 2005 20:14:19 +0100 (MET)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 22 Mar 2005 20:14:17 +0100
Received: from esealmw115.eemea.ericsson.se ([153.88.200.6]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 22 Mar 2005 20:14:17 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4
Date: Tue, 22 Mar 2005 20:14:16 +0100
Message-ID: <24521B9781EAC745A4BE65966F69C9BE212ABC@esealmw115.eemea.ericsson.se>
Thread-Topic: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4
Thread-index: AcUvBh+c1L57VRlBRkyCwTzZzglV1AAC04xu
From: "Karim El-Malki \(AL/EAB\)" <karim.el-malki@ericsson.com>
To: "James Kempf " <kempf@docomolabs-usa.com>,
        "Narayanan Vidya-CVN065 " <vidya@motorola.com>,
        "Rajeev Koodli " <rajeev@iprg.nokia.com>
X-OriginalArrivalTime: 22 Mar 2005 19:14:17.0486 (UTC)
	FILETIME=[57DC32E0:01C52F13]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 578c2c9d0cb01ffe6e1ca36540edd070
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 155726d2f5fe5eb5c40a9f079fd9e841
Content-Transfer-Encoding: quoted-printable

I agree with what you are saying regarding L2 triggers and
deployment. However I have a comment on the technical
argument and the FMIP/LLH discussion. The issue is not
whether FMIP is superior to LLH or viceversa. My argument
is that they are basically the same thing and use the same
set of messages between MN and FA: proxy router solicitation,
proxy router advertisement, registration request/FBU.
I can't see how one can be better than the other. I'm also
not surprised since FMIPv4 is a v6-ification on FMIPv6 while
FMIPv6 and LLH specs were made similar in the first place.
/Karim

-----Original Message-----
From: James Kempf
To: Narayanan Vidya-CVN065; Karim El-Malki (AL/EAB); Rajeev Koodli
Cc: mip4@ietf.org
Sent: 22/03/2005 18:40
Subject: Re: [Mip4] RE: Differences between Low Latency Handovers and =
FMIP v4

I think this whole discussion about L2 triggers and LLH is a red
herring.
People are taking the wording "L2 trigger" too literally. It doesn't
actually have to be a protocol message in the L2 protocol, it just must
be
indication that handover has occured or will occur. The handover
indication
doesn't have to include all the L3 information in Table 1 in one L2
message.
It can be deduced. For example, using something like CARD or even the
RtPrxy
messages, the MN can build up a table of AP L2 address to FA address
map,
and use that. I believe that is what Karim means when he says that FMIP
also
needs this kind of information. Unless an FMIP MN has some way to know
that
a handover has occured or will occur, there's no FBU. And unless it has
some
information about what new subnet the MN is in or will be, it can't put
that
information into the FBU to tell the old FA where to send packets.

I still believe there's value for FMIPv4, believe it is superior to LLH
if
host based all-L3 handover optimization is required, and support work on
it;
however, this whole argument of FMIP v.s. LLH strikes me as being
something
like the medieval argument about how many angles can dance on the head
of a
pin. Wireless LAN deployments are increasingly going in the direction of
wireless LAN switches (60% of new purchases and practically all
upgrades),
and these switches already have nonstandardized solutions for "IP
Mobility",
which, in effect, means tunneling L2 frames in L3 between subnets.
Unfortunately, vendors would like to keep it that way, since having a
standardized solution means that enterprise customers and service
providers
would be free to mix and match solutions and less likely to go single
supplier. So FMIP is likely to be of limited interest for WLAN
deployments
going forward. Perhaps 3GPP2 is interested in it? Though they already
have
their own solution in the A10/A11 interface, which looks strikingly like
the
solution adopted by the WLAN switch vendors.

Anyway, if this WG was serious about its charter to focus on deployment,
it
would start up an activity to standardize WLAN switching "IP mobility".

            jak


----- Original Message -----=20
From: "Narayanan Vidya-CVN065" <vidya@motorola.com>
To: "'Karim El-Malki \(AL/EAB\)'" <karim.el-malki@ericsson.com>; "Rajeev
Koodli" <rajeev@iprg.nokia.com>
Cc: <mip4@ietf.org>
Sent: Monday, March 21, 2005 5:56 PM
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and
FMIP
v4


> Karim,
> I have a rather stupid question. All the triggers listed in table 1 of
LLH
list some L3 parameter or another that needs to be present in the
trigger.
This suggests to me that any kind of L2 trigger that is needed for LLH
(Pre-reg or post-reg) requires the presence of the appropriate parameter
listed in the "Parameters" row of the table.
>
> Am I missing something here?
>
> Vidya
>
> -----Original Message-----
> From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf
Of
Karim El-Malki \(AL/EAB\)
> Sent: Monday, March 21, 2005 5:20 PM
> To: Rajeev Koodli
> Cc: mip4@ietf.org
> Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and
FMIPv4
>
>
> >>I understand your point that you took FMIPv6 and applied
> >>it to v4 to make FMIPv4. But that doesn't make it substantially
> >>different from Low Latency. Your spec does use link-layer triggers
to
> >>be able to send the RtSolPr. An interface coming up in the MN is
used
> >>just the same in Low Latency and is defined as a mobile trigger in
Low
> >>Latency (L2-LU). PRE-REG involves the MN getting such a
> >>mobile trigger and sending a PrRtSol and receiving a
> >>PrRtAdv. What's the difference compared to your spec?
> >>
> >>
> >As I explained below (and also itemized in the List below), the
> >essential difference is that LLH requires L2 to provide L3
information
> >(nFA, MN IP addresses, their MAC addresses etc.) via various L2-*T
type
> >of triggers.
> >This is a Big difference for us since we do not wish to change L2 to
> >implement fast handovers. Both FMIPv6 and FMIPv4 work without
> >requiring such changes to L2.
>
> That's not correct.
> Let's take the case where the L3 handoff is initiated before
> L2 handoff. Taking WLAN for example, in LLH the MN gets info from L2
(e.g.
AP scan) and sends a PrRtSol to get a PrRtAdv containing information of
the
subnet it may move to. I can't see any change required to L2. Where is
the
difference compared to what you have described? The only difference is
that
we definied all "handoff hints" as L2 triggers, just as a result of the
AP
scan is defined as a mobile trigger. The LLH spec doesn't mandate the
presence of all trigger types in all cases. It depends on what the L2
has to
offer.
>
> >>The messages are even called the same. Nothing special
> >>or L2-dependent about this L2 trigger. For example PRE-REG
> >>
> >>
> >Well, the essential difference is what requirements LLH imposes on L2
> >triggers. Table 1 in LLH specifies what information is expected from
L2
> >triggers including the nFA, MN IP addresses from the various L2-*T
> >triggers.
>
> LLH can work with different types of L2 triggers (which is very
different
from requiring L2 changes) and supports the case you have described in
FMIPv4. Table 1 specifies the different types of triggers that LLH can
utilise. Note that it includes very simple triggers that work even on
WLAN.
It is wrong to say that all triggers in Table 1 are required on all L2s
for
LLH to work.
>
> >>can be applied to WLAN using AP scans. I don't think that
> >>the difference in packet formats makes it a substantially different
> >>spec from low latency.  Also, the other case you are considering
> >>involves an L3 handoff that happens after the MN attaches to the new
> >>link. This cannot really be considered a "fast" handoff, which would
> >>instead be where the handoff happens before or in parallel with the
L2
> >>handoff.
> >>
> >>
> >Perhaps you have missed something.. The FMIP design allows movement
> >detection and router/FA discovery phases to be done prior to L2
> >handover. The "reactive" handover we refer to is the one where the
FBU
> >is sent from the
> >new link. But, the MN uses the neighborhood information via Proxy
Router
> >messages to determine movement detection and router/FA config
> >information of the
> >new subnet. So, your description above is not accurate.
>
> Note that I first addressed the L3-movement-before-L2 (where I am
saying
that FMIPv4 is no different from LLH) and then I wrote "the other case
you
are considering....". Am I incorrect in saying that FMIPv4 also supports
the
L3-handoff-after-L2-handoff case? I think I had read that case in FMIPv4
(i.e. FBU sent from new link). That's why I had asked about PFANE.
>
> >>This L3-handoff-after-L2-handoff was already covered in the route
> >>optv4 spec using PFANE. You may have missed the question so I'll
> >>repeat it: did you consider the PFANE? Why aren't you just reusing
the
> >>PFANE (Previous FA Notification
> >>Extension) work for that scenario?
> >>
> >>
> >Please see above. The key difference with respect to Previous FA
(what
> >used to be Previous AR
> >notification in v6) Notification is that you don't incur delays due
to
> >movement detection and
> >router/FA discovery.
>
> If you are only considering the L3-handoff-before-L2-handoff case then
there are very little differences between FMIPv4 and LLH for the reasons
given above.
>
> >So, apart from the independence from L2 to provide L3 information,
the
> >other crucial difference is the decoupling of neighborhood discovery
> >from the actual
> >handover signaling. This not only reduces the number of signaling
> >messages
> >during the handover itself, but also makes the reactive fast
handovers
> >possible.
>
> Again I can't see the crucial difference from LLH.
> The ND messages are basically the same (even almost called the same):
PrRtSol and PrRtAdv. LLH uses standard MIPv4 naming (Registration
Request
and Reply) while FMIPv4 achieves the same result but calls this an FBU.
Tunnelling between FAs is supported in both specs. LLH furthermore
supports
anticipated HA updating or "local" HA updating (regional registrations).
It
seems to me that to make things "faster" one would want to update the
local/global HA directly if possible since FA-FA routing can be
inefficient
in a tree-like network structure compared to updating a local HA. I am
curious to understand why you have eliminated that option in FMIPv4
compared
to LLH. Measurements performed on FMIPv6+HMIPv6 integration prove that
it
makes sense to combine local/global HA updating with the FMIP mechanism.
/Karim
>
> --=20
> 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/
>
> --=20
> 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/


From mip4-bounces@ietf.org  Tue Mar 22 14:15:36 2005
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 OAA19908
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 14:15:36 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDow7-000054-4W
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 14:21:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDoop-000620-CI; Tue, 22 Mar 2005 14:13:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDoom-00061l-S9
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 14:13:33 -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 OAA19638
	for <mip4@ietf.org>; Tue, 22 Mar 2005 14:13:31 -0500 (EST)
Received: from motgate4.mot.com ([144.189.100.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDou6-0008Se-F4
	for mip4@ietf.org; Tue, 22 Mar 2005 14:19:03 -0500
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234])
	by motgate4.mot.com (8.12.11/Motgate4) with ESMTP id j2MJICOE024391
	for <mip4@ietf.org>; Tue, 22 Mar 2005 12:18:12 -0700 (MST)
Received: from il02exm13.corp.mot.com (il02exm13.corp.mot.com [10.0.111.24])
	by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id j2MJEMKT027816
	for <mip4@ietf.org>; Tue, 22 Mar 2005 13:14:22 -0600 (CST)
Received: by il02exm13 with Internet Mail Service (5.5.2657.72)
	id <D3S24S5X>; Tue, 22 Mar 2005 13:13:29 -0600
Message-ID: <1B631E11D496D711BB2800065BFCB6A11B7A6E14@il02exm13>
From: Narayanan Vidya-CVN065 <vidya@motorola.com>
To: "'James Kempf'" <kempf@docomolabs-usa.com>,
        "'Karim El-Malki \\\\(AL/EAB\\\\)'" <karim.el-malki@ericsson.com>,
        "'Rajeev Koodli'" <rajeev@iprg.nokia.com>
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4
Date: Tue, 22 Mar 2005 13:13:21 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 200d029292fbb60d25b263122ced50fc
Cc: "'mip4@ietf.org'" <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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d16ce744298aacf98517bc7c108bd198

James,
I'll repeat one of my earlier questions here. What happened to your draft on post-MIT? Wasn't it trying to provide a host-based all-L3 handover optimization? 

Vidya

-----Original Message-----
From: James Kempf [mailto:kempf@docomolabs-usa.com] 
Sent: Tuesday, March 22, 2005 11:40 AM
To: Narayanan Vidya-CVN065; 'Karim El-Malki \\(AL/EAB\\)'; Rajeev Koodli
Cc: mip4@ietf.org
Subject: Re: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4


I think this whole discussion about L2 triggers and LLH is a red herring. People are taking the wording "L2 trigger" too literally. It doesn't actually have to be a protocol message in the L2 protocol, it just must be indication that handover has occured or will occur. The handover indication doesn't have to include all the L3 information in Table 1 in one L2 message. It can be deduced. For example, using something like CARD or even the RtPrxy messages, the MN can build up a table of AP L2 address to FA address map, and use that. I believe that is what Karim means when he says that FMIP also needs this kind of information. Unless an FMIP MN has some way to know that a handover has occured or will occur, there's no FBU. And unless it has some information about what new subnet the MN is in or will be, it can't put that information into the FBU to tell the old FA where to send packets.

I still believe there's value for FMIPv4, believe it is superior to LLH if host based all-L3 handover optimization is required, and support work on it; however, this whole argument of FMIP v.s. LLH strikes me as being something like the medieval argument about how many angles can dance on the head of a pin. Wireless LAN deployments are increasingly going in the direction of wireless LAN switches (60% of new purchases and practically all upgrades), and these switches already have nonstandardized solutions for "IP Mobility", which, in effect, means tunneling L2 frames in L3 between subnets. Unfortunately, vendors would like to keep it that way, since having a standardized solution means that enterprise customers and service providers would be free to mix and match solutions and less likely to go single supplier. So FMIP is likely to be of limited interest for WLAN deployments going forward. Perhaps 3GPP2 is interested in it? Though they already have their own solution in the A!
 10/A11 interface, which looks strikingly like the solution adopted by the WLAN switch vendors.

Anyway, if this WG was serious about its charter to focus on deployment, it would start up an activity to standardize WLAN switching "IP mobility".

            jak


----- Original Message ----- 
From: "Narayanan Vidya-CVN065" <vidya@motorola.com>
To: "'Karim El-Malki \(AL/EAB\)'" <karim.el-malki@ericsson.com>; "Rajeev Koodli" <rajeev@iprg.nokia.com>
Cc: <mip4@ietf.org>
Sent: Monday, March 21, 2005 5:56 PM
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4


> Karim,
> I have a rather stupid question. All the triggers listed in table 1 of 
> LLH
list some L3 parameter or another that needs to be present in the trigger. This suggests to me that any kind of L2 trigger that is needed for LLH (Pre-reg or post-reg) requires the presence of the appropriate parameter listed in the "Parameters" row of the table.
>
> Am I missing something here?
>
> Vidya
>
> -----Original Message-----
> From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf 
> Of
Karim El-Malki \(AL/EAB\)
> Sent: Monday, March 21, 2005 5:20 PM
> To: Rajeev Koodli
> Cc: mip4@ietf.org
> Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and
FMIPv4
>
>
> >>I understand your point that you took FMIPv6 and applied
> >>it to v4 to make FMIPv4. But that doesn't make it substantially 
> >>different from Low Latency. Your spec does use link-layer triggers 
> >>to be able to send the RtSolPr. An interface coming up in the MN is 
> >>used just the same in Low Latency and is defined as a mobile trigger 
> >>in Low Latency (L2-LU). PRE-REG involves the MN getting such a 
> >>mobile trigger and sending a PrRtSol and receiving a PrRtAdv. What's 
> >>the difference compared to your spec?
> >>
> >>
> >As I explained below (and also itemized in the List below), the 
> >essential difference is that LLH requires L2 to provide L3 
> >information (nFA, MN IP addresses, their MAC addresses etc.) via 
> >various L2-*T type of triggers. This is a Big difference for us since 
> >we do not wish to change L2 to implement fast handovers. Both FMIPv6 
> >and FMIPv4 work without requiring such changes to L2.
>
> That's not correct.
> Let's take the case where the L3 handoff is initiated before L2 
> handoff. Taking WLAN for example, in LLH the MN gets info from L2 
> (e.g.
AP scan) and sends a PrRtSol to get a PrRtAdv containing information of the subnet it may move to. I can't see any change required to L2. Where is the difference compared to what you have described? The only difference is that we definied all "handoff hints" as L2 triggers, just as a result of the AP scan is defined as a mobile trigger. The LLH spec doesn't mandate the presence of all trigger types in all cases. It depends on what the L2 has to offer.
>
> >>The messages are even called the same. Nothing special
> >>or L2-dependent about this L2 trigger. For example PRE-REG
> >>
> >>
> >Well, the essential difference is what requirements LLH imposes on L2 
> >triggers. Table 1 in LLH specifies what information is expected from 
> >L2 triggers including the nFA, MN IP addresses from the various L2-*T 
> >triggers.
>
> LLH can work with different types of L2 triggers (which is very 
> different
from requiring L2 changes) and supports the case you have described in FMIPv4. Table 1 specifies the different types of triggers that LLH can utilise. Note that it includes very simple triggers that work even on WLAN. It is wrong to say that all triggers in Table 1 are required on all L2s for LLH to work.
>
> >>can be applied to WLAN using AP scans. I don't think that the 
> >>difference in packet formats makes it a substantially different spec 
> >>from low latency.  Also, the other case you are considering involves 
> >>an L3 handoff that happens after the MN attaches to the new link. 
> >>This cannot really be considered a "fast" handoff, which would 
> >>instead be where the handoff happens before or in parallel with the 
> >>L2 handoff.
> >>
> >>
> >Perhaps you have missed something.. The FMIP design allows movement 
> >detection and router/FA discovery phases to be done prior to L2 
> >handover. The "reactive" handover we refer to is the one where the 
> >FBU is sent from the new link. But, the MN uses the neighborhood 
> >information via Proxy Router messages to determine movement detection 
> >and router/FA config information of the
> >new subnet. So, your description above is not accurate.
>
> Note that I first addressed the L3-movement-before-L2 (where I am 
> saying
that FMIPv4 is no different from LLH) and then I wrote "the other case you are considering....". Am I incorrect in saying that FMIPv4 also supports the L3-handoff-after-L2-handoff case? I think I had read that case in FMIPv4 (i.e. FBU sent from new link). That's why I had asked about PFANE.
>
> >>This L3-handoff-after-L2-handoff was already covered in the route 
> >>optv4 spec using PFANE. You may have missed the question so I'll 
> >>repeat it: did you consider the PFANE? Why aren't you just reusing 
> >>the PFANE (Previous FA Notification
> >>Extension) work for that scenario?
> >>
> >>
> >Please see above. The key difference with respect to Previous FA 
> >(what used to be Previous AR notification in v6) Notification is that 
> >you don't incur delays due to movement detection and
> >router/FA discovery.
>
> If you are only considering the L3-handoff-before-L2-handoff case then
there are very little differences between FMIPv4 and LLH for the reasons given above.
>
> >So, apart from the independence from L2 to provide L3 information, 
> >the other crucial difference is the decoupling of neighborhood 
> >discovery from the actual handover signaling. This not only reduces 
> >the number of signaling messages
> >during the handover itself, but also makes the reactive fast handovers
> >possible.
>
> Again I can't see the crucial difference from LLH.
> The ND messages are basically the same (even almost called the same):
PrRtSol and PrRtAdv. LLH uses standard MIPv4 naming (Registration Request and Reply) while FMIPv4 achieves the same result but calls this an FBU. Tunnelling between FAs is supported in both specs. LLH furthermore supports anticipated HA updating or "local" HA updating (regional registrations). It seems to me that to make things "faster" one would want to update the local/global HA directly if possible since FA-FA routing can be inefficient in a tree-like network structure compared to updating a local HA. I am curious to understand why you have eliminated that option in FMIPv4 compared to LLH. Measurements performed on FMIPv6+HMIPv6 integration prove that it makes sense to combine local/global HA updating with the FMIP mechanism. /Karim
>
> --
> 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/
>


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


From mip4-bounces@ietf.org  Tue Mar 22 14:24:31 2005
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 OAA20864
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 14:24:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDp4k-0000QL-Iz
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 14:30:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDoy2-0007a4-3M; Tue, 22 Mar 2005 14:23:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDoy0-0007Zz-R7
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 14:23:04 -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 OAA20628
	for <mip4@ietf.org>; Tue, 22 Mar 2005 14:23:03 -0500 (EST)
Received: from av3-2-sn1.fre.skanova.net ([81.228.11.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDp3J-0000O8-T4
	for mip4@ietf.org; Tue, 22 Mar 2005 14:28:35 -0500
Received: by av3-2-sn1.fre.skanova.net (Postfix, from userid 502)
	id BB1ED37EA8; Tue, 22 Mar 2005 20:22:53 +0100 (CET)
Received: from smtp3-1-sn1.fre.skanova.net (smtp3-1-sn1.fre.skanova.net
	[81.228.11.163])
	by av3-2-sn1.fre.skanova.net (Postfix) with ESMTP id A996037E45
	for <mip4@ietf.org>; Tue, 22 Mar 2005 20:22:53 +0100 (CET)
Received: from shiraz.levkowetz.com (h195n1fls311o871.telia.com
	[213.64.174.195])
	by smtp3-1-sn1.fre.skanova.net (Postfix) with ESMTP id 91ED837E58
	for <mip4@ietf.org>; Tue, 22 Mar 2005 20:22:53 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.44) id 1DDoxp-0005fA-FC
	for mip4@ietf.org; Tue, 22 Mar 2005 20:22:53 +0100
Message-ID: <4240708D.5030303@levkowetz.com>
Date: Tue, 22 Mar 2005 20:22:53 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Mobile IPv4 Mailing List <mip4@ietf.org>
Subject: Fwd: [Mip4] Request to consider FMIPv4 as a working group document
X-Enigmail-Version: 0.89.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Content-Transfer-Encoding: 7bit
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Content-Transfer-Encoding: 7bit


Forwarding a mail to the list, minus the attached slideset which was
too big to be accepted by Mailman.  I've instead made the slides for
Charlie's FMIPv4 presentation from IETF-61 available here:

    http://mip4.org/ietf61/FMIPv4.pdf

Regards,

	Henrik

---- Forwarded Mail: ----

> Subject: Re: [Mip4] Request to consider FMIPv4 as a working group document
> From: "Charles E. Perkins" <charliep@iprg.nokia.com>
> Date: Tue, 22 Mar 2005 07:43:01 -0800
> To: Alexandru Petrescu <Alexandru.Petrescu@motorola.com>
> CC: Mobile IPv4 Mailing List <mip4@ietf.org>, Rajeev Koodli <rajeev.koodli@nokia.com>
> 
> Hello Alexandru,
> 
> Attached, please find my very small set of slides.
> The presentation was pretty lightweight, and in fact
> I only got to make it because there ended up being
> time on the schedule after other more urgent
> presentations were finished.
> 
> Regards,
> Charlie P.
> 
> 
> 
> Alexandru Petrescu wrote:
> 
>> Hi Charlie,
>>
>> Charles E.Perkins wrote:
>>
>>> As part of this discussion, I showed some results which indicate very
>>>  good performance for FMIPv4, suitable for handling interactive voice
>>>  applications.  I probably have the PowerPoint presentation around 
>>> somewhere if needed.
>>
>>
>> Yes, I need these slides, please send in if easily available for you,
>> thank you.
>>
>> I am interested to find out about "hard" limits on the interruption
>> times that a human user of a interactive voice IP application is ready
>> to tolerate.  During some IP and non-IP discussions, very often the
>> numbers 100ms or 200ms come up.  But for some reason I'm unable to
>> identify a written report/paper, eventually with some "hands-on"
>> non-simulated experience to determine this "tolerable delay".  Anything
>> like a I-D report or ppt slides or journal/conference paper applies, 
>> thanks,
>>
>> Alex
> 
> 



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


From mip4-bounces@ietf.org  Tue Mar 22 14:28:20 2005
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 OAA21393
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 14:28:20 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDp8R-0000ck-Ag
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 14:33:52 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDp2Q-0008DE-OR; Tue, 22 Mar 2005 14:27:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDp2O-0008D9-Jx
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 14:27:36 -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 OAA21253
	for <mip4@ietf.org>; Tue, 22 Mar 2005 14:27:35 -0500 (EST)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDp7i-0000V1-3D
	for mip4@ietf.org; Tue, 22 Mar 2005 14:33:07 -0500
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j2MJvQJ21889;
	Tue, 22 Mar 2005 11:57:26 -0800
X-mProtect: <200503221957> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp141217.americas.nokia.com (172.18.141.217,
	claiming to be "[172.18.141.217]")
	by darkstar.iprg.nokia.com smtpdjTwMNh; Tue, 22 Mar 2005 11:57:23 PST
Message-ID: <4240718F.6040301@iprg.nokia.com>
Date: Tue, 22 Mar 2005 11:27:11 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Karim El-Malki (AL/EAB)" <karim.el-malki@ericsson.com>
Subject: Re: [Mip4] RE: Differences between Low Latency Handovers and FMIPv4
References: <24521B9781EAC745A4BE65966F69C9BE212AB4@esealmw115.eemea.ericsson.se>
In-Reply-To: <24521B9781EAC745A4BE65966F69C9BE212AB4@esealmw115.eemea.ericsson.se>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 22f8e36c8d8be0bcbb9bf02fb6ce7335
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>
Content-Type: multipart/mixed; boundary="===============0973487697=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 5d188b91ff79eaa1be2a0e9635461d9a

This is a multi-part message in MIME format.
--===============0973487697==
Content-Type: multipart/alternative;
	boundary="------------080408020800090706060002"

This is a multi-part message in MIME format.
--------------080408020800090706060002
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


Hi Karim,

few comments:

- From Section 3.3,
  "

   ... The Proxy
   Router Advertisement Solicitation unicast to oFA is an agent
   solicitation with a special extension.  The solicitation MUST have an
   extension containing an IP address identifier because the MN is
   soliciting another specific FA's advertisement from the oFA. This
   specific FA will be the MN's nFA.  The IP address identifier contains
   the IP address of the nFA or an identifier that can be used by the
   oFA to resolve to nFA's IP address.  If the identifier is not an IP
   address, it MAY be specific to the underlying wireless technology,
   for example, an Access Point or Base Station ID."

>From this, IP address identifier is required (MUST) in PrRtSol, but MAY 
instead contain an AP of BSS ID? Doesn't that require you to implement 
the IP address identifier? Even otherwise, I just cannot understand the 
entire LLH protocol working without L3 information. For instance, how 
do L2-ST, L2-TT work, how does post-reg work? They require the triggers 
to contain the L3 information. 

- Naming of messages: they come from FMIPv6, no changes. Not from LLH.

- Anticipated HA/GFA registration: We did not "eliminate" that option. We do
  not believe in tying the two together. Implementations are free to use the
  two together if they both exist. Efficiency of those two working together, 
  if needed, can be achieved by means outside the specification of FMIP. 
  
  This also brings another important difference we have listed. (An earlier
  e-mail from Charlie included the other major differences). Our design is 
  minimalistic in the sense that it requires no changes to MIPv4 processing,
  default router processing, RegReg processing etc. All those things can
  take place as they normally do, but we disengage them from the critical path
  for real-time traffic. In other words, we set up routing to support on-going
  traffic, while other protocol processing can take its time. 
  
  An example where tying protocols together leads to unpredictable behavior is
  changing the default router when Registration Reply is received even if the
  MN is still on the old link due to whatever radio conditions. How can the 
  MN send packets ? Don't you  end up changing the behavior here? 

 
- L3-handover-before-L2-handover: There are important differences between FMIP 
  and LLH. At the time of an impending L2 handover, FMIP uses a single message,
  FBU, LLH needs at least 3. (If you use post-reg, there are no messages, but the
  L2 triggers must support L3 information). FMIP has the concept of neighborhood
  discovery, in which a MN resolves its neighborhood L2 devices to their L3 
  parameters in a link-independent way, which is decoupled from the handover timing. 
  LLH does not decouple Proxy messages from Registration messages (presumably 
  because it does not define such a concept). Granted the FMIPv4 design is adapted 
  from FMIPv6, but these are imprtant differences wrt LLH. And, since the design of
  FMIPv6 and FMIPv4 is identical, it is very easy to implement the two together. 

  This was enumerated as one of the differences in our original e-mail.

- L3-handover-after-L2-handover: LLH has no such design, and hence the reference
  to PFANE. As said earlier (and below), the difference between PFANE and FMIPv4 is 
  that FBU is sent as soon as the new link is available without having to perform
  agent discovery. This comes from doing neighborhood discovery before leaving the
  old link.

  An important design aspect of decoupling neighborhood discovery and handover
  signaling is that it allows you to initiate FBU either from the old link or 
  from the new link without having to do movement detection and agent discovery
  on the new link. And, FMIP does this without changing the MIP and default router
  behaviors.

- Performance: In Charlie'e presentation, you can see we get about 80 ms
  for FMIPv4 handover on a Prism2 chipset. The IP overhead during
  handover is time for FBU message, which is 2-3 ms over WLAN. The performance
  of FMIPv6 is similar. With improvements in L2 delay, the entire handover delay 
  can be better. 
  I have not seen evaluations of pre-reg LLH performance other than from 
  James Kempf, which seems to conclude that it is not suitable for deploying
  for certain link technologies. Perhaps it can be made to work.. Post-reg, on
  the other hand, requires L3 information from triggers. 

So, my summary is that there are important differences. Perhaps LLH is suitable for
certain environments, and likewise for FMIPv4. One particular environment
we are interested in is deploying FMIPv6 and FMIPv4 together. 

That's all for me :-)

-Rajeev


Karim El-Malki (AL/EAB) wrote:

>>>I understand your point that you took FMIPv6 and applied
>>>it to v4 to make FMIPv4. But that doesn't make it
>>>substantially different from Low Latency. Your spec does
>>>use link-layer triggers to be able to send the RtSolPr.
>>>An interface coming up in the MN is used just the same in
>>>Low Latency and is defined as a mobile trigger in Low
>>>Latency (L2-LU). PRE-REG involves the MN getting such a
>>>mobile trigger and sending a PrRtSol and receiving a
>>>PrRtAdv. What's the difference compared to your spec?
>>> 
>>>
>>>      
>>>
>>As I explained below (and also itemized in the List below), the
>>essential
>>difference is that LLH requires L2 to provide L3 information (nFA, MN
>>IP addresses, their MAC addresses etc.) via various L2-*T type of
>>triggers.
>>This is a Big difference for us since we do not wish to change L2 to
>>implement fast handovers. Both FMIPv6 and FMIPv4 work without
>>requiring such changes to L2. 
>>    
>>
>
>That's not correct.
>Let's take the case where the L3 handoff is initiated before
>L2 handoff. Taking WLAN for example, in LLH the MN gets info
>from L2 (e.g. AP scan) and sends a PrRtSol to get a PrRtAdv
>containing information of the subnet it may move to. I can't
>see any change required to L2. Where is the difference compared
>to what you have described? The only difference is that we
>definied all "handoff hints" as L2 triggers, just as a result
>of the AP scan is defined as a mobile trigger. The LLH spec doesn't
>mandate the presence of all trigger types in all cases. It
>depends on what the L2 has to offer.
>
>  
>
>>>The messages are even called the same. Nothing special
>>>or L2-dependent about this L2 trigger. For example PRE-REG
>>> 
>>>
>>>      
>>>
>>Well, the essential difference is what requirements LLH imposes on L2
>>triggers. Table 1 in LLH specifies what information is expected from
>>L2 triggers including the nFA, MN IP addresses from the various L2-*T
>>triggers.
>>    
>>
>
>LLH can work with different types of L2 triggers (which is very
>different from requiring L2 changes) and supports the case you
>have described in FMIPv4. Table 1 specifies the different types
>of triggers that LLH can utilise. Note that it includes very
>simple triggers that work even on WLAN. It is wrong to say
>that all triggers in Table 1 are required on all L2s for LLH
>to work.
>
>  
>
>>>can be applied to WLAN using AP scans. I don't think that
>>>the difference in packet formats makes it a substantially
>>>different spec from low latency.  Also, the other case you
>>>are considering involves an L3 handoff that happens after
>>>the MN attaches to the new link. This cannot really be
>>>considered a "fast" handoff, which would instead be where
>>>the handoff happens before or in parallel with the L2 handoff.
>>> 
>>>
>>>      
>>>
>>Perhaps you have missed something.. The FMIP design allows movement
>>detection and router/FA discovery phases to be done prior to L2 
>>handover. The
>>"reactive" handover we refer to is the one where the FBU is sent from
>>the
>>new link. But, the MN uses the neighborhood information via Proxy Router
>>messages to determine movement detection and router/FA config 
>>information of the
>>new subnet. So, your description above is not accurate.
>>    
>>
>
>Note that I first addressed the L3-movement-before-L2 (where I
>am saying that FMIPv4 is no different from LLH) and then
>I wrote "the other case you are considering....".
>Am I incorrect in saying that FMIPv4 also supports the
>L3-handoff-after-L2-handoff case? I think I had read that
>case in FMIPv4 (i.e. FBU sent from new link).
>That's why I had asked about PFANE.
>
>  
>
>>>This L3-handoff-after-L2-handoff was already covered in the
>>>route optv4 spec using PFANE. You may have missed the question
>>>so I'll repeat it: did you consider the PFANE? Why aren't
>>>you just reusing the PFANE (Previous FA Notification
>>>Extension) work for that scenario?
>>> 
>>>
>>>      
>>>
>>Please see above. The key difference with respect to Previous FA (what 
>>used to be Previous AR
>>notification in v6) Notification is that you don't incur delays due to 
>>movement detection and
>>router/FA discovery.
>>    
>>
>
>If you are only considering the L3-handoff-before-L2-handoff case
>then there are very little differences between FMIPv4 and LLH for
>the reasons given above.
>
>  
>
>>So, apart from the independence from L2 to provide L3 information, the
>>other
>>crucial difference is the decoupling of neighborhood discovery from the 
>>actual
>>handover signaling. This not only reduces the number of signaling
>>messages
>>during the handover itself, but also makes the reactive fast handovers 
>>possible.
>>    
>>
>
>Again I can't see the crucial difference from LLH.
>The ND messages are basically the same (even almost called the same):
>PrRtSol and PrRtAdv. LLH uses standard MIPv4 naming (Registration
>Request and Reply) while FMIPv4 achieves the same result but calls
>this an FBU. Tunnelling between FAs is supported in both specs.
>LLH furthermore supports anticipated HA updating or "local" HA
>updating (regional registrations). It seems to me that to make
>things "faster" one would want to update the local/global HA directly
>if possible since FA-FA routing can be inefficient in a tree-like
>network structure compared to updating a local HA. I am curious to
>understand why you have eliminated that option in FMIPv4 compared
>to LLH. Measurements performed on FMIPv6+HMIPv6 integration
>prove that it makes sense to combine local/global HA updating with
>the FMIP mechanism.
>/Karim
>  
>

--------------080408020800090706060002
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
Hi Karim,<br>
<br>
few comments:<br>
<br>
- From Section 3.3,<br>
&nbsp; "<br>
<pre>   ... The Proxy
   Router Advertisement Solicitation unicast to oFA is an agent
   solicitation with a special extension.  The solicitation MUST have an
   extension containing an IP address identifier because the MN is
   soliciting another specific FA's advertisement from the oFA. This
   specific FA will be the MN's nFA.  The IP address identifier contains
   the IP address of the nFA or an identifier that can be used by the
   oFA to resolve to nFA's IP address.  If the identifier is not an IP
   address, it MAY be specific to the underlying wireless technology,
   for example, an Access Point or Base Station ID."

>From this, IP address identifier is required (MUST) in PrRtSol, but MAY 
instead contain an AP of BSS ID? Doesn't that require you to implement 
the IP address identifier? Even otherwise, I just cannot understand the 
entire LLH protocol working without L3 information. For instance, how 
do L2-ST, L2-TT work, how does post-reg work? They require the triggers 
to contain the L3 information. 

- Naming of messages: they come from FMIPv6, no changes. Not from LLH.

- Anticipated HA/GFA registration: We did not "eliminate" that option. We do
  not believe in tying the two together. Implementations are free to use the
  two together if they both exist. Efficiency of those two working together, 
  if needed, can be achieved by means outside the specification of FMIP. 
  
  This also brings another important difference we have listed. (An earlier
  e-mail from Charlie included the other major differences). Our design is 
  minimalistic in the sense that it requires no changes to MIPv4 processing,
  default router processing, RegReg processing etc. All those things can
  take place as they normally do, but we disengage them from the critical path
  for real-time traffic. In other words, we set up routing to support on-going
  traffic, while other protocol processing can take its time. 
  
  An example where tying protocols together leads to unpredictable behavior is
  changing the default router when Registration Reply is received even if the
  MN is still on the old link due to whatever radio conditions. How can the 
  MN send packets ? Don't you  end up changing the behavior here? 

&nbsp;
- L3-handover-before-L2-handover: There are important differences between FMIP 
  and LLH. At the time of an impending L2 handover, FMIP uses a single message,
  FBU, LLH needs at least 3. (If you use post-reg, there are no messages, but the
  L2 triggers must support L3 information). FMIP has the concept of neighborhood
  discovery, in which a MN resolves its neighborhood L2 devices to their L3 
  parameters in a link-independent way, which is decoupled from the handover timing. 
  LLH does not decouple Proxy messages from Registration messages (presumably 
  because it does not define such a concept). Granted the FMIPv4 design is adapted 
  from FMIPv6, but these are imprtant differences wrt LLH. And, since the design of
  FMIPv6 and FMIPv4 is identical, it is very easy to implement the two together. 

  This was enumerated as one of the differences in our original e-mail.

- L3-handover-after-L2-handover: LLH has no such design, and hence the reference
  to PFANE. As said earlier (and below), the difference between PFANE and FMIPv4 is 
  that FBU is sent as soon as the new link is available without having to perform
  agent discovery. This comes from doing neighborhood discovery before leaving the
  old link.

  An important design aspect of decoupling neighborhood discovery and handover
  signaling is that it allows you to initiate FBU either from the old link or 
  from the new link without having to do movement detection and agent discovery
  on the new link. And, FMIP does this without changing the MIP and default router
  behaviors.

- Performance: In Charlie'e presentation, you can see we get about 80 ms
  for FMIPv4 handover on a Prism2 chipset. The IP overhead during
  handover is time for FBU message, which is 2-3 ms over WLAN. The performance
  of FMIPv6 is similar. With improvements in L2 delay, the entire handover delay 
  can be better. 
  I have not seen evaluations of pre-reg LLH performance other than from 
  James Kempf, which seems to conclude that it is not suitable for deploying
  for certain link technologies. Perhaps it can be made to work.. Post-reg, on
  the other hand, requires L3 information from triggers. 

So, my summary is that there are important differences. Perhaps LLH is suitable for
certain environments, and likewise for FMIPv4. One particular environment
we are interested in is deploying FMIPv6 and FMIPv4 together. 

That's all for me :-)

-Rajeev

</pre>
Karim El-Malki (AL/EAB) wrote:
<blockquote
 cite="mid24521B9781EAC745A4BE65966F69C9BE212AB4@esealmw115.eemea.ericsson.se"
 type="cite">
  <blockquote type="cite">
    <blockquote type="cite">
      <pre wrap="">I understand your point that you took FMIPv6 and applied
it to v4 to make FMIPv4. But that doesn't make it
substantially different from Low Latency. Your spec does
use link-layer triggers to be able to send the RtSolPr.
An interface coming up in the MN is used just the same in
Low Latency and is defined as a mobile trigger in Low
Latency (L2-LU). PRE-REG involves the MN getting such a
mobile trigger and sending a PrRtSol and receiving a
PrRtAdv. What's the difference compared to your spec?
 

      </pre>
    </blockquote>
    <pre wrap="">As I explained below (and also itemized in the List below), the
essential
difference is that LLH requires L2 to provide L3 information (nFA, MN
IP addresses, their MAC addresses etc.) via various L2-*T type of
triggers.
This is a Big difference for us since we do not wish to change L2 to
implement fast handovers. Both FMIPv6 and FMIPv4 work without
requiring such changes to L2. 
    </pre>
  </blockquote>
  <pre wrap=""><!---->
That's not correct.
Let's take the case where the L3 handoff is initiated before
L2 handoff. Taking WLAN for example, in LLH the MN gets info
from L2 (e.g. AP scan) and sends a PrRtSol to get a PrRtAdv
containing information of the subnet it may move to. I can't
see any change required to L2. Where is the difference compared
to what you have described? The only difference is that we
definied all "handoff hints" as L2 triggers, just as a result
of the AP scan is defined as a mobile trigger. The LLH spec doesn't
mandate the presence of all trigger types in all cases. It
depends on what the L2 has to offer.

  </pre>
  <blockquote type="cite">
    <blockquote type="cite">
      <pre wrap="">The messages are even called the same. Nothing special
or L2-dependent about this L2 trigger. For example PRE-REG
 

      </pre>
    </blockquote>
    <pre wrap="">Well, the essential difference is what requirements LLH imposes on L2
triggers. Table 1 in LLH specifies what information is expected from
L2 triggers including the nFA, MN IP addresses from the various L2-*T
triggers.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
LLH can work with different types of L2 triggers (which is very
different from requiring L2 changes) and supports the case you
have described in FMIPv4. Table 1 specifies the different types
of triggers that LLH can utilise. Note that it includes very
simple triggers that work even on WLAN. It is wrong to say
that all triggers in Table 1 are required on all L2s for LLH
to work.

  </pre>
  <blockquote type="cite">
    <blockquote type="cite">
      <pre wrap="">can be applied to WLAN using AP scans. I don't think that
the difference in packet formats makes it a substantially
different spec from low latency.  Also, the other case you
are considering involves an L3 handoff that happens after
the MN attaches to the new link. This cannot really be
considered a "fast" handoff, which would instead be where
the handoff happens before or in parallel with the L2 handoff.
 

      </pre>
    </blockquote>
    <pre wrap="">Perhaps you have missed something.. The FMIP design allows movement
detection and router/FA discovery phases to be done prior to L2 
handover. The
"reactive" handover we refer to is the one where the FBU is sent from
the
new link. But, the MN uses the neighborhood information via Proxy Router
messages to determine movement detection and router/FA config 
information of the
new subnet. So, your description above is not accurate.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Note that I first addressed the L3-movement-before-L2 (where I
am saying that FMIPv4 is no different from LLH) and then
I wrote "the other case you are considering....".
Am I incorrect in saying that FMIPv4 also supports the
L3-handoff-after-L2-handoff case? I think I had read that
case in FMIPv4 (i.e. FBU sent from new link).
That's why I had asked about PFANE.

  </pre>
  <blockquote type="cite">
    <blockquote type="cite">
      <pre wrap="">This L3-handoff-after-L2-handoff was already covered in the
route optv4 spec using PFANE. You may have missed the question
so I'll repeat it: did you consider the PFANE? Why aren't
you just reusing the PFANE (Previous FA Notification
Extension) work for that scenario?
 

      </pre>
    </blockquote>
    <pre wrap="">Please see above. The key difference with respect to Previous FA (what 
used to be Previous AR
notification in v6) Notification is that you don't incur delays due to 
movement detection and
router/FA discovery.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
If you are only considering the L3-handoff-before-L2-handoff case
then there are very little differences between FMIPv4 and LLH for
the reasons given above.

  </pre>
  <blockquote type="cite">
    <pre wrap="">So, apart from the independence from L2 to provide L3 information, the
other
crucial difference is the decoupling of neighborhood discovery from the 
actual
handover signaling. This not only reduces the number of signaling
messages
during the handover itself, but also makes the reactive fast handovers 
possible.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Again I can't see the crucial difference from LLH.
The ND messages are basically the same (even almost called the same):
PrRtSol and PrRtAdv. LLH uses standard MIPv4 naming (Registration
Request and Reply) while FMIPv4 achieves the same result but calls
this an FBU. Tunnelling between FAs is supported in both specs.
LLH furthermore supports anticipated HA updating or "local" HA
updating (regional registrations). It seems to me that to make
things "faster" one would want to update the local/global HA directly
if possible since FA-FA routing can be inefficient in a tree-like
network structure compared to updating a local HA. I am curious to
understand why you have eliminated that option in FMIPv4 compared
to LLH. Measurements performed on FMIPv6+HMIPv6 integration
prove that it makes sense to combine local/global HA updating with
the FMIP mechanism.
/Karim
  </pre>
</blockquote>
</body>
</html>

--------------080408020800090706060002--


--===============0973487697==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0973487697==--



From mip4-bounces@ietf.org  Tue Mar 22 14:29:51 2005
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 OAA21562
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 14:29:51 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDp9u-0000eW-EU
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 14:35:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDozJ-0007hz-1b; Tue, 22 Mar 2005 14:24:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDozH-0007hs-CP
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 14:24:23 -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 OAA20850
	for <mip4@ietf.org>; Tue, 22 Mar 2005 14:24:22 -0500 (EST)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDp4a-0000Py-QL
	for mip4@ietf.org; Tue, 22 Mar 2005 14:29:53 -0500
Message-ID: <031a01c52f14$e6c41a30$0f6115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Narayanan Vidya-CVN065" <vidya@motorola.com>,
        "'Karim El-Malki \\\\(AL/EAB\\\\)'" <karim.el-malki@ericsson.com>,
        "'Rajeev Koodli'" <rajeev@iprg.nokia.com>
References: <1B631E11D496D711BB2800065BFCB6A11B7A6E14@il02exm13>
Subject: Re: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4
Date: Tue, 22 Mar 2005 11:25:18 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f2728948111f2edaaf8980b5b9de55af
Content-Transfer-Encoding: 7bit
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1e467ff145ef391eb7b594ef62b8301f
Content-Transfer-Encoding: 7bit

Vidya,

Yes, Post-MIT does provide an all-host based L3 handover optimization. The
draft expired, you can find it in Watersprings if you want. We also tested
Post-MIT extensively against LLH and it is quite competitive.

As to why we let it expire, at the time there did not seem to be much
implementation and deployment interest, so it was dropped except as a
research topic. I don't see any point in reviving it now, since the
semantics of Post-MIT are not sufficiently different from FMIP to make
having two syntactically different host-based IP handover optimization
protocols for IPv4 and IPv6 necessary.

            jak

----- Original Message ----- 
From: "Narayanan Vidya-CVN065" <vidya@motorola.com>
To: "'James Kempf'" <kempf@docomolabs-usa.com>; "'Karim El-Malki
\\(AL/EAB\\)'" <karim.el-malki@ericsson.com>; "'Rajeev Koodli'"
<rajeev@iprg.nokia.com>
Cc: <mip4@ietf.org>
Sent: Tuesday, March 22, 2005 11:13 AM
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and FMIP
v4


> James,
> I'll repeat one of my earlier questions here. What happened to your draft
on post-MIT? Wasn't it trying to provide a host-based all-L3 handover
optimization?
>
> Vidya
>
> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Tuesday, March 22, 2005 11:40 AM
> To: Narayanan Vidya-CVN065; 'Karim El-Malki \\(AL/EAB\\)'; Rajeev Koodli
> Cc: mip4@ietf.org
> Subject: Re: [Mip4] RE: Differences between Low Latency Handovers and FMIP
v4
>
>
> I think this whole discussion about L2 triggers and LLH is a red herring.
People are taking the wording "L2 trigger" too literally. It doesn't
actually have to be a protocol message in the L2 protocol, it just must be
indication that handover has occured or will occur. The handover indication
doesn't have to include all the L3 information in Table 1 in one L2 message.
It can be deduced. For example, using something like CARD or even the RtPrxy
messages, the MN can build up a table of AP L2 address to FA address map, an
d use that. I believe that is what Karim means when he says that FMIP also
needs this kind of information. Unless an FMIP MN has some way to know that
a handover has occured or will occur, there's no FBU. And unless it has some
information about what new subnet the MN is in or will be, it can't put that
information into the FBU to tell the old FA where to send packets.
>
> I still believe there's value for FMIPv4, believe it is superior to LLH if
host based all-L3 handover optimization is required, and support work on it;
however, this whole argument of FMIP v.s. LLH strikes me as being something
like the medieval argument about how many angles can dance on the head of a
pin. Wireless LAN deployments are increasingly going in the direction of
wireless LAN switches (60% of new purchases and practically all upgrades),
and these switches already have nonstandardized solutions for "IP Mobility",
which, in effect, means tunneling L2 frames in L3 between subnets.
Unfortunately, vendors would like to keep it that way, since having a
standardized solution means that enterprise customers and service providers
would be free to mix and match solutions and less likely to go single
supplier. So FMIP is likely to be of limited interest for WLAN deployments
going forward. Perhaps 3GPP2 is interested in it? Though they already have
their own solution in the A!
>  10/A11 interface, which looks strikingly like the solution adopted by the
WLAN switch vendors.
>
> Anyway, if this WG was serious about its charter to focus on deployment,
it would start up an activity to standardize WLAN switching "IP mobility".
>
>             jak
>
>
> ----- Original Message ----- 
> From: "Narayanan Vidya-CVN065" <vidya@motorola.com>
> To: "'Karim El-Malki \(AL/EAB\)'" <karim.el-malki@ericsson.com>; "Rajeev
Koodli" <rajeev@iprg.nokia.com>
> Cc: <mip4@ietf.org>
> Sent: Monday, March 21, 2005 5:56 PM
> Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and FMIP
v4
>
>
> > Karim,
> > I have a rather stupid question. All the triggers listed in table 1 of
> > LLH
> list some L3 parameter or another that needs to be present in the trigger.
This suggests to me that any kind of L2 trigger that is needed for LLH
(Pre-reg or post-reg) requires the presence of the appropriate parameter
listed in the "Parameters" row of the table.
> >
> > Am I missing something here?
> >
> > Vidya
> >
> > -----Original Message-----
> > From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf
> > Of
> Karim El-Malki \(AL/EAB\)
> > Sent: Monday, March 21, 2005 5:20 PM
> > To: Rajeev Koodli
> > Cc: mip4@ietf.org
> > Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and
> FMIPv4
> >
> >
> > >>I understand your point that you took FMIPv6 and applied
> > >>it to v4 to make FMIPv4. But that doesn't make it substantially
> > >>different from Low Latency. Your spec does use link-layer triggers
> > >>to be able to send the RtSolPr. An interface coming up in the MN is
> > >>used just the same in Low Latency and is defined as a mobile trigger
> > >>in Low Latency (L2-LU). PRE-REG involves the MN getting such a
> > >>mobile trigger and sending a PrRtSol and receiving a PrRtAdv. What's
> > >>the difference compared to your spec?
> > >>
> > >>
> > >As I explained below (and also itemized in the List below), the
> > >essential difference is that LLH requires L2 to provide L3
> > >information (nFA, MN IP addresses, their MAC addresses etc.) via
> > >various L2-*T type of triggers. This is a Big difference for us since
> > >we do not wish to change L2 to implement fast handovers. Both FMIPv6
> > >and FMIPv4 work without requiring such changes to L2.
> >
> > That's not correct.
> > Let's take the case where the L3 handoff is initiated before L2
> > handoff. Taking WLAN for example, in LLH the MN gets info from L2
> > (e.g.
> AP scan) and sends a PrRtSol to get a PrRtAdv containing information of
the subnet it may move to. I can't see any change required to L2. Where is
the difference compared to what you have described? The only difference is
that we definied all "handoff hints" as L2 triggers, just as a result of the
AP scan is defined as a mobile trigger. The LLH spec doesn't mandate the
presence of all trigger types in all cases. It depends on what the L2 has to
offer.
> >
> > >>The messages are even called the same. Nothing special
> > >>or L2-dependent about this L2 trigger. For example PRE-REG
> > >>
> > >>
> > >Well, the essential difference is what requirements LLH imposes on L2
> > >triggers. Table 1 in LLH specifies what information is expected from
> > >L2 triggers including the nFA, MN IP addresses from the various L2-*T
> > >triggers.
> >
> > LLH can work with different types of L2 triggers (which is very
> > different
> from requiring L2 changes) and supports the case you have described in
FMIPv4. Table 1 specifies the different types of triggers that LLH can
utilise. Note that it includes very simple triggers that work even on WLAN.
It is wrong to say that all triggers in Table 1 are required on all L2s for
LLH to work.
> >
> > >>can be applied to WLAN using AP scans. I don't think that the
> > >>difference in packet formats makes it a substantially different spec
> > >>from low latency.  Also, the other case you are considering involves
> > >>an L3 handoff that happens after the MN attaches to the new link.
> > >>This cannot really be considered a "fast" handoff, which would
> > >>instead be where the handoff happens before or in parallel with the
> > >>L2 handoff.
> > >>
> > >>
> > >Perhaps you have missed something.. The FMIP design allows movement
> > >detection and router/FA discovery phases to be done prior to L2
> > >handover. The "reactive" handover we refer to is the one where the
> > >FBU is sent from the new link. But, the MN uses the neighborhood
> > >information via Proxy Router messages to determine movement detection
> > >and router/FA config information of the
> > >new subnet. So, your description above is not accurate.
> >
> > Note that I first addressed the L3-movement-before-L2 (where I am
> > saying
> that FMIPv4 is no different from LLH) and then I wrote "the other case you
are considering....". Am I incorrect in saying that FMIPv4 also supports the
L3-handoff-after-L2-handoff case? I think I had read that case in FMIPv4
(i.e. FBU sent from new link). That's why I had asked about PFANE.
> >
> > >>This L3-handoff-after-L2-handoff was already covered in the route
> > >>optv4 spec using PFANE. You may have missed the question so I'll
> > >>repeat it: did you consider the PFANE? Why aren't you just reusing
> > >>the PFANE (Previous FA Notification
> > >>Extension) work for that scenario?
> > >>
> > >>
> > >Please see above. The key difference with respect to Previous FA
> > >(what used to be Previous AR notification in v6) Notification is that
> > >you don't incur delays due to movement detection and
> > >router/FA discovery.
> >
> > If you are only considering the L3-handoff-before-L2-handoff case then
> there are very little differences between FMIPv4 and LLH for the reasons
given above.
> >
> > >So, apart from the independence from L2 to provide L3 information,
> > >the other crucial difference is the decoupling of neighborhood
> > >discovery from the actual handover signaling. This not only reduces
> > >the number of signaling messages
> > >during the handover itself, but also makes the reactive fast handovers
> > >possible.
> >
> > Again I can't see the crucial difference from LLH.
> > The ND messages are basically the same (even almost called the same):
> PrRtSol and PrRtAdv. LLH uses standard MIPv4 naming (Registration Request
and Reply) while FMIPv4 achieves the same result but calls this an FBU.
Tunnelling between FAs is supported in both specs. LLH furthermore supports
anticipated HA updating or "local" HA updating (regional registrations). It
seems to me that to make things "faster" one would want to update the
local/global HA directly if possible since FA-FA routing can be inefficient
in a tree-like network structure compared to updating a local HA. I am
curious to understand why you have eliminated that option in FMIPv4 compared
to LLH. Measurements performed on FMIPv6+HMIPv6 integration prove that it
makes sense to combine local/global HA updating with the FMIP mechanism.
/Karim
> >
> > --
> > 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/
> >
>
>



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


From mip4-bounces@ietf.org  Tue Mar 22 14:30:55 2005
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 OAA21705
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 14:30:55 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDpAw-0000gw-Ul
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 14:36:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDoyM-0007cU-Gj; Tue, 22 Mar 2005 14:23:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDoyK-0007cN-RK
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 14:23:24 -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 OAA20695
	for <mip4@ietf.org>; Tue, 22 Mar 2005 14:23:23 -0500 (EST)
Received: from motgate.mot.com ([129.188.136.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDp3e-0000Oa-Q4
	for mip4@ietf.org; Tue, 22 Mar 2005 14:28:55 -0500
Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232])
	by motgate.mot.com (Motorola/Motgate) with ESMTP id j2MJNM3j021427
	for <mip4@ietf.org>; Tue, 22 Mar 2005 12:23:23 -0700 (MST)
Received: from il02exm13.corp.mot.com (il02exm13.corp.mot.com [10.0.111.24])
	by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id j2MJNh1C004255
	for <mip4@ietf.org>; Tue, 22 Mar 2005 13:23:44 -0600 (CST)
Received: by il02exm13 with Internet Mail Service (5.5.2657.72)
	id <D3S24TD3>; Tue, 22 Mar 2005 13:23:21 -0600
Message-ID: <1B631E11D496D711BB2800065BFCB6A11B7A6E15@il02exm13>
From: Narayanan Vidya-CVN065 <vidya@motorola.com>
To: "'Karim El-Malki \\(AL/EAB\\)'" <karim.el-malki@ericsson.com>,
        James Kempf  <kempf@docomolabs-usa.com>,
        Rajeev Koodli 
	<rajeev@iprg.nokia.com>
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4
Date: Tue, 22 Mar 2005 13:23:13 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ee80a2074afbfe28d15369f4e74e579d
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 202a3ece0492a8c7e7c8672d5214398f

It seems to me that the one thing that is missing from LLH is a method of doing mobile initiated post-reg. This is provided by FMIP. 

Vidya

-----Original Message-----
From: Karim El-Malki \(AL/EAB\) [mailto:karim.el-malki@ericsson.com] 
Sent: Tuesday, March 22, 2005 1:14 PM
To: James Kempf ; Narayanan Vidya-CVN065; Rajeev Koodli 
Cc: mip4@ietf.org
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4


I agree with what you are saying regarding L2 triggers and deployment. However I have a comment on the technical argument and the FMIP/LLH discussion. The issue is not whether FMIP is superior to LLH or viceversa. My argument is that they are basically the same thing and use the same set of messages between MN and FA: proxy router solicitation, proxy router advertisement, registration request/FBU. I can't see how one can be better than the other. I'm also not surprised since FMIPv4 is a v6-ification on FMIPv6 while FMIPv6 and LLH specs were made similar in the first place. /Karim

-----Original Message-----
From: James Kempf
To: Narayanan Vidya-CVN065; Karim El-Malki (AL/EAB); Rajeev Koodli
Cc: mip4@ietf.org
Sent: 22/03/2005 18:40
Subject: Re: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4

I think this whole discussion about L2 triggers and LLH is a red herring. People are taking the wording "L2 trigger" too literally. It doesn't actually have to be a protocol message in the L2 protocol, it just must be indication that handover has occured or will occur. The handover indication doesn't have to include all the L3 information in Table 1 in one L2 message. It can be deduced. For example, using something like CARD or even the RtPrxy messages, the MN can build up a table of AP L2 address to FA address map, and use that. I believe that is what Karim means when he says that FMIP also needs this kind of information. Unless an FMIP MN has some way to know that a handover has occured or will occur, there's no FBU. And unless it has some information about what new subnet the MN is in or will be, it can't put that information into the FBU to tell the old FA where to send packets.

I still believe there's value for FMIPv4, believe it is superior to LLH if host based all-L3 handover optimization is required, and support work on it; however, this whole argument of FMIP v.s. LLH strikes me as being something like the medieval argument about how many angles can dance on the head of a pin. Wireless LAN deployments are increasingly going in the direction of wireless LAN switches (60% of new purchases and practically all upgrades), and these switches already have nonstandardized solutions for "IP Mobility", which, in effect, means tunneling L2 frames in L3 between subnets. Unfortunately, vendors would like to keep it that way, since having a standardized solution means that enterprise customers and service providers would be free to mix and match solutions and less likely to go single supplier. So FMIP is likely to be of limited interest for WLAN deployments going forward. Perhaps 3GPP2 is interested in it? Though they already have their own solution in the A!
 10/A11 interface, which looks strikingly like the solution adopted by the WLAN switch vendors.

Anyway, if this WG was serious about its charter to focus on deployment, it would start up an activity to standardize WLAN switching "IP mobility".

            jak


----- Original Message ----- 
From: "Narayanan Vidya-CVN065" <vidya@motorola.com>
To: "'Karim El-Malki \(AL/EAB\)'" <karim.el-malki@ericsson.com>; "Rajeev Koodli" <rajeev@iprg.nokia.com>
Cc: <mip4@ietf.org>
Sent: Monday, March 21, 2005 5:56 PM
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4


> Karim,
> I have a rather stupid question. All the triggers listed in table 1 of
LLH
list some L3 parameter or another that needs to be present in the trigger. This suggests to me that any kind of L2 trigger that is needed for LLH (Pre-reg or post-reg) requires the presence of the appropriate parameter listed in the "Parameters" row of the table.
>
> Am I missing something here?
>
> Vidya
>
> -----Original Message-----
> From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf
Of
Karim El-Malki \(AL/EAB\)
> Sent: Monday, March 21, 2005 5:20 PM
> To: Rajeev Koodli
> Cc: mip4@ietf.org
> Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and
FMIPv4
>
>
> >>I understand your point that you took FMIPv6 and applied
> >>it to v4 to make FMIPv4. But that doesn't make it substantially 
> >>different from Low Latency. Your spec does use link-layer triggers
to
> >>be able to send the RtSolPr. An interface coming up in the MN is
used
> >>just the same in Low Latency and is defined as a mobile trigger in
Low
> >>Latency (L2-LU). PRE-REG involves the MN getting such a mobile 
> >>trigger and sending a PrRtSol and receiving a PrRtAdv. What's the 
> >>difference compared to your spec?
> >>
> >>
> >As I explained below (and also itemized in the List below), the 
> >essential difference is that LLH requires L2 to provide L3
information
> >(nFA, MN IP addresses, their MAC addresses etc.) via various L2-*T
type
> >of triggers.
> >This is a Big difference for us since we do not wish to change L2 to 
> >implement fast handovers. Both FMIPv6 and FMIPv4 work without 
> >requiring such changes to L2.
>
> That's not correct.
> Let's take the case where the L3 handoff is initiated before L2 
> handoff. Taking WLAN for example, in LLH the MN gets info from L2
(e.g.
AP scan) and sends a PrRtSol to get a PrRtAdv containing information of the subnet it may move to. I can't see any change required to L2. Where is the difference compared to what you have described? The only difference is that we definied all "handoff hints" as L2 triggers, just as a result of the AP scan is defined as a mobile trigger. The LLH spec doesn't mandate the presence of all trigger types in all cases. It depends on what the L2 has to offer.
>
> >>The messages are even called the same. Nothing special
> >>or L2-dependent about this L2 trigger. For example PRE-REG
> >>
> >>
> >Well, the essential difference is what requirements LLH imposes on L2 
> >triggers. Table 1 in LLH specifies what information is expected from
L2
> >triggers including the nFA, MN IP addresses from the various L2-*T 
> >triggers.
>
> LLH can work with different types of L2 triggers (which is very
different
from requiring L2 changes) and supports the case you have described in FMIPv4. Table 1 specifies the different types of triggers that LLH can utilise. Note that it includes very simple triggers that work even on WLAN. It is wrong to say that all triggers in Table 1 are required on all L2s for LLH to work.
>
> >>can be applied to WLAN using AP scans. I don't think that the 
> >>difference in packet formats makes it a substantially different spec 
> >>from low latency.  Also, the other case you are considering involves 
> >>an L3 handoff that happens after the MN attaches to the new link. 
> >>This cannot really be considered a "fast" handoff, which would 
> >>instead be where the handoff happens before or in parallel with the
L2
> >>handoff.
> >>
> >>
> >Perhaps you have missed something.. The FMIP design allows movement 
> >detection and router/FA discovery phases to be done prior to L2 
> >handover. The "reactive" handover we refer to is the one where the
FBU
> >is sent from the
> >new link. But, the MN uses the neighborhood information via Proxy
Router
> >messages to determine movement detection and router/FA config 
> >information of the new subnet. So, your description above is not 
> >accurate.
>
> Note that I first addressed the L3-movement-before-L2 (where I am
saying
that FMIPv4 is no different from LLH) and then I wrote "the other case you are considering....". Am I incorrect in saying that FMIPv4 also supports the L3-handoff-after-L2-handoff case? I think I had read that case in FMIPv4 (i.e. FBU sent from new link). That's why I had asked about PFANE.
>
> >>This L3-handoff-after-L2-handoff was already covered in the route 
> >>optv4 spec using PFANE. You may have missed the question so I'll 
> >>repeat it: did you consider the PFANE? Why aren't you just reusing
the
> >>PFANE (Previous FA Notification
> >>Extension) work for that scenario?
> >>
> >>
> >Please see above. The key difference with respect to Previous FA
(what
> >used to be Previous AR
> >notification in v6) Notification is that you don't incur delays due
to
> >movement detection and
> >router/FA discovery.
>
> If you are only considering the L3-handoff-before-L2-handoff case then
there are very little differences between FMIPv4 and LLH for the reasons given above.
>
> >So, apart from the independence from L2 to provide L3 information,
the
> >other crucial difference is the decoupling of neighborhood discovery 
> >from the actual handover signaling. This not only reduces the number 
> >of signaling messages
> >during the handover itself, but also makes the reactive fast
handovers
> >possible.
>
> Again I can't see the crucial difference from LLH.
> The ND messages are basically the same (even almost called the same):
PrRtSol and PrRtAdv. LLH uses standard MIPv4 naming (Registration Request and Reply) while FMIPv4 achieves the same result but calls this an FBU. Tunnelling between FAs is supported in both specs. LLH furthermore supports anticipated HA updating or "local" HA updating (regional registrations). It seems to me that to make things "faster" one would want to update the local/global HA directly if possible since FA-FA routing can be inefficient in a tree-like network structure compared to updating a local HA. I am curious to understand why you have eliminated that option in FMIPv4 compared to LLH. Measurements performed on FMIPv6+HMIPv6 integration prove that it makes sense to combine local/global HA updating with the FMIP mechanism. /Karim
>
> --
> 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/
>


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


From mip4-bounces@ietf.org  Tue Mar 22 14:44:56 2005
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 OAA23081
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 14:44:56 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDpOV-00019Q-VK
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 14:50:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDpFh-0002dh-1T; Tue, 22 Mar 2005 14:41:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDpFe-0002dZ-Pe
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 14:41:18 -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 OAA22776
	for <mip4@ietf.org>; Tue, 22 Mar 2005 14:41:17 -0500 (EST)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDpKy-00015A-Em
	for mip4@ietf.org; Tue, 22 Mar 2005 14:46:49 -0500
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j2MKAll01279;
	Tue, 22 Mar 2005 12:10:47 -0800
X-mProtect: <200503222010> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp141217.americas.nokia.com (172.18.141.217,
	claiming to be "[172.18.141.217]")
	by darkstar.iprg.nokia.com smtpdHoIYl6; Tue, 22 Mar 2005 12:10:44 PST
Message-ID: <424074B0.9010800@iprg.nokia.com>
Date: Tue, 22 Mar 2005 11:40:32 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
Subject: Re: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4
References: <1B631E11D496D711BB2800065BFCB6A10C977920@il02exm13>
	<025c01c52f06$413838c0$0f6115ac@dcml.docomolabsusa.com>
In-Reply-To: <025c01c52f06$413838c0$0f6115ac@dcml.docomolabsusa.com>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: d4673ea769cc9931269061744af205ce
Cc: mip4@ietf.org, Narayanan Vidya-CVN065 <vidya@motorola.com>,
        "'Karim El-Malki \\\(AL/EAB\\\)'" <karim.el-malki@ericsson.com>
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>
Content-Type: multipart/mixed; boundary="===============1298782516=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 2af167865907217f0b49c659e31a77f7

This is a multi-part message in MIME format.
--===============1298782516==
Content-Type: multipart/alternative;
	boundary="------------060900080203050906080402"

This is a multi-part message in MIME format.
--------------060900080203050906080402
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


Hi Jim,



James Kempf wrote:

>I still believe there's value for FMIPv4, believe it is superior to LLH if
>host based all-L3 handover optimization is required, and support work on it;
>  
>
okay.

>however, this whole argument of FMIP v.s. LLH strikes me as being something
>like the medieval argument about how many angles can dance on the head of a
>pin. Wireless LAN deployments are increasingly going in the direction of
>  
>
:-)

>wireless LAN switches (60% of new purchases and practically all upgrades),
>and these switches already have nonstandardized solutions for "IP Mobility",
>which, in effect, means tunneling L2 frames in L3 between subnets.
>  
>
Looking forward, subnet mobility is crucial for scale and for deployment 
easy.

>Unfortunately, vendors would like to keep it that way, since having a
>standardized solution means that enterprise customers and service providers
>would be free to mix and match solutions and less likely to go single
>supplier. So FMIP is likely to be of limited interest for WLAN deployments
>going forward. Perhaps 3GPP2 is interested in it? Though they already have
>  
>
On the contrary, wouldn't you expect the enterprises to start demanding 
interoperability
between boxes? If vendors have "holds" on enterprises for their boxes 
alone, that does not
sound like a way going forward.

>Anyway, if this WG was serious about its charter to focus on deployment, it
>would start up an activity to standardize WLAN switching "IP mobility".
>
>  
>
Doesn't this mean tunneling?  A switch tunneling an L2 frame in L3 
sounds sub-optimal
since it needs to "go back" through the router to reach the IP network, 
and eventually the
destination router and the switch. Anyway, why is there a need for 
standardization here?

-Rajeev

>            jak
>
>
>----- Original Message ----- 
>From: "Narayanan Vidya-CVN065" <vidya@motorola.com>
>To: "'Karim El-Malki \(AL/EAB\)'" <karim.el-malki@ericsson.com>; "Rajeev
>Koodli" <rajeev@iprg.nokia.com>
>Cc: <mip4@ietf.org>
>Sent: Monday, March 21, 2005 5:56 PM
>Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and FMIP
>v4
>
>
>  
>
>>Karim,
>>I have a rather stupid question. All the triggers listed in table 1 of LLH
>>    
>>
>list some L3 parameter or another that needs to be present in the trigger.
>This suggests to me that any kind of L2 trigger that is needed for LLH
>(Pre-reg or post-reg) requires the presence of the appropriate parameter
>listed in the "Parameters" row of the table.
>  
>
>>Am I missing something here?
>>
>>Vidya
>>
>>-----Original Message-----
>>From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of
>>    
>>
>Karim El-Malki \(AL/EAB\)
>  
>
>>Sent: Monday, March 21, 2005 5:20 PM
>>To: Rajeev Koodli
>>Cc: mip4@ietf.org
>>Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and
>>    
>>
>FMIPv4
>  
>
>>    
>>
>>>>I understand your point that you took FMIPv6 and applied
>>>>it to v4 to make FMIPv4. But that doesn't make it substantially
>>>>different from Low Latency. Your spec does use link-layer triggers to
>>>>be able to send the RtSolPr. An interface coming up in the MN is used
>>>>just the same in Low Latency and is defined as a mobile trigger in Low
>>>>Latency (L2-LU). PRE-REG involves the MN getting such a
>>>>mobile trigger and sending a PrRtSol and receiving a
>>>>PrRtAdv. What's the difference compared to your spec?
>>>>
>>>>
>>>>        
>>>>
>>>As I explained below (and also itemized in the List below), the
>>>essential difference is that LLH requires L2 to provide L3 information
>>>(nFA, MN IP addresses, their MAC addresses etc.) via various L2-*T type
>>>of triggers.
>>>This is a Big difference for us since we do not wish to change L2 to
>>>implement fast handovers. Both FMIPv6 and FMIPv4 work without
>>>requiring such changes to L2.
>>>      
>>>
>>That's not correct.
>>Let's take the case where the L3 handoff is initiated before
>>L2 handoff. Taking WLAN for example, in LLH the MN gets info from L2 (e.g.
>>    
>>
>AP scan) and sends a PrRtSol to get a PrRtAdv containing information of the
>subnet it may move to. I can't see any change required to L2. Where is the
>difference compared to what you have described? The only difference is that
>we definied all "handoff hints" as L2 triggers, just as a result of the AP
>scan is defined as a mobile trigger. The LLH spec doesn't mandate the
>presence of all trigger types in all cases. It depends on what the L2 has to
>offer.
>  
>
>>>>The messages are even called the same. Nothing special
>>>>or L2-dependent about this L2 trigger. For example PRE-REG
>>>>
>>>>
>>>>        
>>>>
>>>Well, the essential difference is what requirements LLH imposes on L2
>>>triggers. Table 1 in LLH specifies what information is expected from L2
>>>triggers including the nFA, MN IP addresses from the various L2-*T
>>>triggers.
>>>      
>>>
>>LLH can work with different types of L2 triggers (which is very different
>>    
>>
>from requiring L2 changes) and supports the case you have described in
>FMIPv4. Table 1 specifies the different types of triggers that LLH can
>utilise. Note that it includes very simple triggers that work even on WLAN.
>It is wrong to say that all triggers in Table 1 are required on all L2s for
>LLH to work.
>  
>
>>>>can be applied to WLAN using AP scans. I don't think that
>>>>the difference in packet formats makes it a substantially different
>>>>spec from low latency.  Also, the other case you are considering
>>>>involves an L3 handoff that happens after the MN attaches to the new
>>>>link. This cannot really be considered a "fast" handoff, which would
>>>>instead be where the handoff happens before or in parallel with the L2
>>>>handoff.
>>>>
>>>>
>>>>        
>>>>
>>>Perhaps you have missed something.. The FMIP design allows movement
>>>detection and router/FA discovery phases to be done prior to L2
>>>handover. The "reactive" handover we refer to is the one where the FBU
>>>is sent from the
>>>new link. But, the MN uses the neighborhood information via Proxy Router
>>>messages to determine movement detection and router/FA config
>>>information of the
>>>new subnet. So, your description above is not accurate.
>>>      
>>>
>>Note that I first addressed the L3-movement-before-L2 (where I am saying
>>    
>>
>that FMIPv4 is no different from LLH) and then I wrote "the other case you
>are considering....". Am I incorrect in saying that FMIPv4 also supports the
>L3-handoff-after-L2-handoff case? I think I had read that case in FMIPv4
>(i.e. FBU sent from new link). That's why I had asked about PFANE.
>  
>
>>>>This L3-handoff-after-L2-handoff was already covered in the route
>>>>optv4 spec using PFANE. You may have missed the question so I'll
>>>>repeat it: did you consider the PFANE? Why aren't you just reusing the
>>>>PFANE (Previous FA Notification
>>>>Extension) work for that scenario?
>>>>
>>>>
>>>>        
>>>>
>>>Please see above. The key difference with respect to Previous FA (what
>>>used to be Previous AR
>>>notification in v6) Notification is that you don't incur delays due to
>>>movement detection and
>>>router/FA discovery.
>>>      
>>>
>>If you are only considering the L3-handoff-before-L2-handoff case then
>>    
>>
>there are very little differences between FMIPv4 and LLH for the reasons
>given above.
>  
>
>>>So, apart from the independence from L2 to provide L3 information, the
>>>other crucial difference is the decoupling of neighborhood discovery
>>>      
>>>
>>>from the actual
>>    
>>
>>>handover signaling. This not only reduces the number of signaling
>>>messages
>>>during the handover itself, but also makes the reactive fast handovers
>>>possible.
>>>      
>>>
>>Again I can't see the crucial difference from LLH.
>>The ND messages are basically the same (even almost called the same):
>>    
>>
>PrRtSol and PrRtAdv. LLH uses standard MIPv4 naming (Registration Request
>and Reply) while FMIPv4 achieves the same result but calls this an FBU.
>Tunnelling between FAs is supported in both specs. LLH furthermore supports
>anticipated HA updating or "local" HA updating (regional registrations). It
>seems to me that to make things "faster" one would want to update the
>local/global HA directly if possible since FA-FA routing can be inefficient
>in a tree-like network structure compared to updating a local HA. I am
>curious to understand why you have eliminated that option in FMIPv4 compared
>to LLH. Measurements performed on FMIPv6+HMIPv6 integration prove that it
>makes sense to combine local/global HA updating with the FMIP mechanism.
>/Karim
>  
>
>>-- 
>>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/
>>
>>    
>>
>
>
>  
>

--------------060900080203050906080402
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
Hi Jim,<br>
<br>
<br>
<br>
James Kempf wrote:<br>
<blockquote
 cite="mid025c01c52f06$413838c0$0f6115ac@dcml.docomolabsusa.com"
 type="cite">
  <pre wrap="">I still believe there's value for FMIPv4, believe it is superior to LLH if
host based all-L3 handover optimization is required, and support work on it;
  </pre>
</blockquote>
okay.<br>
<blockquote
 cite="mid025c01c52f06$413838c0$0f6115ac@dcml.docomolabsusa.com"
 type="cite">
  <pre wrap="">however, this whole argument of FMIP v.s. LLH strikes me as being something
like the medieval argument about how many angles can dance on the head of a
pin. Wireless LAN deployments are increasingly going in the direction of
  </pre>
</blockquote>
:-)<br>
<blockquote
 cite="mid025c01c52f06$413838c0$0f6115ac@dcml.docomolabsusa.com"
 type="cite">
  <pre wrap="">wireless LAN switches (60% of new purchases and practically all upgrades),
and these switches already have nonstandardized solutions for "IP Mobility",
which, in effect, means tunneling L2 frames in L3 between subnets.
  </pre>
</blockquote>
Looking forward, subnet mobility is crucial for scale and for
deployment easy. <br>
<blockquote
 cite="mid025c01c52f06$413838c0$0f6115ac@dcml.docomolabsusa.com"
 type="cite">
  <pre wrap="">Unfortunately, vendors would like to keep it that way, since having a
standardized solution means that enterprise customers and service providers
would be free to mix and match solutions and less likely to go single
supplier. So FMIP is likely to be of limited interest for WLAN deployments
going forward. Perhaps 3GPP2 is interested in it? Though they already have
  </pre>
</blockquote>
On the contrary, wouldn't you expect the enterprises to start demanding
interoperability<br>
between boxes? If vendors have "holds" on enterprises for their boxes
alone, that does not<br>
sound like a way going forward. <br>
<br>
<blockquote
 cite="mid025c01c52f06$413838c0$0f6115ac@dcml.docomolabsusa.com"
 type="cite">
  <pre wrap="">Anyway, if this WG was serious about its charter to focus on deployment, it
would start up an activity to standardize WLAN switching "IP mobility".

  </pre>
</blockquote>
Doesn't this mean tunneling?&nbsp; A switch tunneling an L2 frame in L3
sounds sub-optimal<br>
since it needs to "go back" through the router to reach the IP network,
and eventually the<br>
destination router and the switch. Anyway, why is there a need for
standardization here? <br>
<br>
-Rajeev<br>
<br>
<blockquote
 cite="mid025c01c52f06$413838c0$0f6115ac@dcml.docomolabsusa.com"
 type="cite">
  <pre wrap="">            jak


----- Original Message ----- 
From: "Narayanan Vidya-CVN065" <a class="moz-txt-link-rfc2396E" href="mailto:vidya@motorola.com">&lt;vidya@motorola.com&gt;</a>
To: "'Karim El-Malki \(AL/EAB\)'" <a class="moz-txt-link-rfc2396E" href="mailto:karim.el-malki@ericsson.com">&lt;karim.el-malki@ericsson.com&gt;</a>; "Rajeev
Koodli" <a class="moz-txt-link-rfc2396E" href="mailto:rajeev@iprg.nokia.com">&lt;rajeev@iprg.nokia.com&gt;</a>
Cc: <a class="moz-txt-link-rfc2396E" href="mailto:mip4@ietf.org">&lt;mip4@ietf.org&gt;</a>
Sent: Monday, March 21, 2005 5:56 PM
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and FMIP
v4


  </pre>
  <blockquote type="cite">
    <pre wrap="">Karim,
I have a rather stupid question. All the triggers listed in table 1 of LLH
    </pre>
  </blockquote>
  <pre wrap=""><!---->list some L3 parameter or another that needs to be present in the trigger.
This suggests to me that any kind of L2 trigger that is needed for LLH
(Pre-reg or post-reg) requires the presence of the appropriate parameter
listed in the "Parameters" row of the table.
  </pre>
  <blockquote type="cite">
    <pre wrap="">Am I missing something here?

Vidya

-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:mip4-bounces@ietf.org">mip4-bounces@ietf.org</a> [<a class="moz-txt-link-freetext" href="mailto:mip4-bounces@ietf.org">mailto:mip4-bounces@ietf.org</a>] On Behalf Of
    </pre>
  </blockquote>
  <pre wrap=""><!---->Karim El-Malki \(AL/EAB\)
  </pre>
  <blockquote type="cite">
    <pre wrap="">Sent: Monday, March 21, 2005 5:20 PM
To: Rajeev Koodli
Cc: <a class="moz-txt-link-abbreviated" href="mailto:mip4@ietf.org">mip4@ietf.org</a>
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and
    </pre>
  </blockquote>
  <pre wrap=""><!---->FMIPv4
  </pre>
  <blockquote type="cite">
    <pre wrap="">
    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">I understand your point that you took FMIPv6 and applied
it to v4 to make FMIPv4. But that doesn't make it substantially
different from Low Latency. Your spec does use link-layer triggers to
be able to send the RtSolPr. An interface coming up in the MN is used
just the same in Low Latency and is defined as a mobile trigger in Low
Latency (L2-LU). PRE-REG involves the MN getting such a
mobile trigger and sending a PrRtSol and receiving a
PrRtAdv. What's the difference compared to your spec?


        </pre>
      </blockquote>
      <pre wrap="">As I explained below (and also itemized in the List below), the
essential difference is that LLH requires L2 to provide L3 information
(nFA, MN IP addresses, their MAC addresses etc.) via various L2-*T type
of triggers.
This is a Big difference for us since we do not wish to change L2 to
implement fast handovers. Both FMIPv6 and FMIPv4 work without
requiring such changes to L2.
      </pre>
    </blockquote>
    <pre wrap="">That's not correct.
Let's take the case where the L3 handoff is initiated before
L2 handoff. Taking WLAN for example, in LLH the MN gets info from L2 (e.g.
    </pre>
  </blockquote>
  <pre wrap=""><!---->AP scan) and sends a PrRtSol to get a PrRtAdv containing information of the
subnet it may move to. I can't see any change required to L2. Where is the
difference compared to what you have described? The only difference is that
we definied all "handoff hints" as L2 triggers, just as a result of the AP
scan is defined as a mobile trigger. The LLH spec doesn't mandate the
presence of all trigger types in all cases. It depends on what the L2 has to
offer.
  </pre>
  <blockquote type="cite">
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">The messages are even called the same. Nothing special
or L2-dependent about this L2 trigger. For example PRE-REG


        </pre>
      </blockquote>
      <pre wrap="">Well, the essential difference is what requirements LLH imposes on L2
triggers. Table 1 in LLH specifies what information is expected from L2
triggers including the nFA, MN IP addresses from the various L2-*T
triggers.
      </pre>
    </blockquote>
    <pre wrap="">LLH can work with different types of L2 triggers (which is very different
    </pre>
  </blockquote>
  <pre wrap=""><!---->from requiring L2 changes) and supports the case you have described in
FMIPv4. Table 1 specifies the different types of triggers that LLH can
utilise. Note that it includes very simple triggers that work even on WLAN.
It is wrong to say that all triggers in Table 1 are required on all L2s for
LLH to work.
  </pre>
  <blockquote type="cite">
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">can be applied to WLAN using AP scans. I don't think that
the difference in packet formats makes it a substantially different
spec from low latency.  Also, the other case you are considering
involves an L3 handoff that happens after the MN attaches to the new
link. This cannot really be considered a "fast" handoff, which would
instead be where the handoff happens before or in parallel with the L2
handoff.


        </pre>
      </blockquote>
      <pre wrap="">Perhaps you have missed something.. The FMIP design allows movement
detection and router/FA discovery phases to be done prior to L2
handover. The "reactive" handover we refer to is the one where the FBU
is sent from the
new link. But, the MN uses the neighborhood information via Proxy Router
messages to determine movement detection and router/FA config
information of the
new subnet. So, your description above is not accurate.
      </pre>
    </blockquote>
    <pre wrap="">Note that I first addressed the L3-movement-before-L2 (where I am saying
    </pre>
  </blockquote>
  <pre wrap=""><!---->that FMIPv4 is no different from LLH) and then I wrote "the other case you
are considering....". Am I incorrect in saying that FMIPv4 also supports the
L3-handoff-after-L2-handoff case? I think I had read that case in FMIPv4
(i.e. FBU sent from new link). That's why I had asked about PFANE.
  </pre>
  <blockquote type="cite">
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">This L3-handoff-after-L2-handoff was already covered in the route
optv4 spec using PFANE. You may have missed the question so I'll
repeat it: did you consider the PFANE? Why aren't you just reusing the
PFANE (Previous FA Notification
Extension) work for that scenario?


        </pre>
      </blockquote>
      <pre wrap="">Please see above. The key difference with respect to Previous FA (what
used to be Previous AR
notification in v6) Notification is that you don't incur delays due to
movement detection and
router/FA discovery.
      </pre>
    </blockquote>
    <pre wrap="">If you are only considering the L3-handoff-before-L2-handoff case then
    </pre>
  </blockquote>
  <pre wrap=""><!---->there are very little differences between FMIPv4 and LLH for the reasons
given above.
  </pre>
  <blockquote type="cite">
    <blockquote type="cite">
      <pre wrap="">So, apart from the independence from L2 to provide L3 information, the
other crucial difference is the decoupling of neighborhood discovery
      </pre>
    </blockquote>
    <pre wrap="">&gt;from the actual
    </pre>
    <blockquote type="cite">
      <pre wrap="">handover signaling. This not only reduces the number of signaling
messages
during the handover itself, but also makes the reactive fast handovers
possible.
      </pre>
    </blockquote>
    <pre wrap="">Again I can't see the crucial difference from LLH.
The ND messages are basically the same (even almost called the same):
    </pre>
  </blockquote>
  <pre wrap=""><!---->PrRtSol and PrRtAdv. LLH uses standard MIPv4 naming (Registration Request
and Reply) while FMIPv4 achieves the same result but calls this an FBU.
Tunnelling between FAs is supported in both specs. LLH furthermore supports
anticipated HA updating or "local" HA updating (regional registrations). It
seems to me that to make things "faster" one would want to update the
local/global HA directly if possible since FA-FA routing can be inefficient
in a tree-like network structure compared to updating a local HA. I am
curious to understand why you have eliminated that option in FMIPv4 compared
to LLH. Measurements performed on FMIPv6+HMIPv6 integration prove that it
makes sense to combine local/global HA updating with the FMIP mechanism.
/Karim
  </pre>
  <blockquote type="cite">
    <pre wrap="">-- 
Mip4 mailing list: <a class="moz-txt-link-abbreviated" href="mailto:Mip4@ietf.org">Mip4@ietf.org</a>
    Web interface: <a class="moz-txt-link-freetext" href="https://www1.ietf.org/mailman/listinfo/mip4">https://www1.ietf.org/mailman/listinfo/mip4</a>
     Charter page: <a class="moz-txt-link-freetext" href="http://www.ietf.org/html.charters/mip4-charter.html">http://www.ietf.org/html.charters/mip4-charter.html</a>
Supplemental site: <a class="moz-txt-link-freetext" href="http://www.mip4.org/">http://www.mip4.org/</a>

-- 
Mip4 mailing list: <a class="moz-txt-link-abbreviated" href="mailto:Mip4@ietf.org">Mip4@ietf.org</a>
    Web interface: <a class="moz-txt-link-freetext" href="https://www1.ietf.org/mailman/listinfo/mip4">https://www1.ietf.org/mailman/listinfo/mip4</a>
     Charter page: <a class="moz-txt-link-freetext" href="http://www.ietf.org/html.charters/mip4-charter.html">http://www.ietf.org/html.charters/mip4-charter.html</a>
Supplemental site: <a class="moz-txt-link-freetext" href="http://www.mip4.org/">http://www.mip4.org/</a>

    </pre>
  </blockquote>
  <pre wrap=""><!---->

  </pre>
</blockquote>
</body>
</html>

--------------060900080203050906080402--


--===============1298782516==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1298782516==--



From mip4-bounces@ietf.org  Tue Mar 22 14:53:45 2005
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 OAA23641
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 14:53:45 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDpX2-0001TV-72
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 14:59:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDpQT-0004N3-5D; Tue, 22 Mar 2005 14:52:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDpQS-0004My-L4
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 14:52:28 -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 OAA23610
	for <mip4@ietf.org>; Tue, 22 Mar 2005 14:52:27 -0500 (EST)
Received: from av1-1-sn3.vrr.skanova.net ([81.228.9.105])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDpVk-0001SS-Qa
	for mip4@ietf.org; Tue, 22 Mar 2005 14:57:59 -0500
Received: by av1-1-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 2175537E9B; Tue, 22 Mar 2005 20:52:08 +0100 (CET)
Received: from smtp1-2-sn3.vrr.skanova.net (smtp1-2-sn3.vrr.skanova.net
	[81.228.9.178]) by av1-1-sn3.vrr.skanova.net (Postfix) with ESMTP
	id 144F837E42; Tue, 22 Mar 2005 20:52:08 +0100 (CET)
Received: from shiraz.levkowetz.com (h195n1fls311o871.telia.com
	[213.64.174.195])
	by smtp1-2-sn3.vrr.skanova.net (Postfix) with ESMTP id EF75638010;
	Tue, 22 Mar 2005 20:52:07 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.44)
	id 1DDpQ7-0006Ee-Cx; Tue, 22 Mar 2005 20:52:07 +0100
Message-ID: <42407765.9050900@levkowetz.com>
Date: Tue, 22 Mar 2005 20:52:05 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
Subject: Re: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4
References: <1B631E11D496D711BB2800065BFCB6A10C977920@il02exm13>
	<025c01c52f06$413838c0$0f6115ac@dcml.docomolabsusa.com>
In-Reply-To: <025c01c52f06$413838c0$0f6115ac@dcml.docomolabsusa.com>
X-Enigmail-Version: 0.89.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit

on 2005-03-22 6:40 pm James Kempf said the following:

<snip a lot of stuff on which I basically agree>

> Anyway, if this WG was serious about its charter to focus on deployment, it
> would start up an activity to standardize WLAN switching "IP mobility".

Interesting point.  

If we do propose to take this up in the new charter proposal, do we
have people who would be willing to spend some time and energy on
this?

	Henrik


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


From mip4-bounces@ietf.org  Tue Mar 22 14:56:38 2005
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 OAA24150
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 14:56:37 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDpZp-0001dN-Pk
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 15:02:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDpTR-0004ec-Eh; Tue, 22 Mar 2005 14:55:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDpTP-0004eX-Ko
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 14:55:31 -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 OAA23939
	for <mip4@ietf.org>; Tue, 22 Mar 2005 14:55:30 -0500 (EST)
Received: from mail-gw0.york.ac.uk ([144.32.128.245])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDpYj-0001ZP-OW
	for mip4@ietf.org; Tue, 22 Mar 2005 15:01:02 -0500
Received: from [172.16.1.146] (host-172-16-1-146.sns.york.ac.uk [172.16.1.146])
	by mail-gw0.york.ac.uk (8.12.10/8.12.10) with ESMTP id j2MJtOW5027545; 
	Tue, 22 Mar 2005 19:55:24 GMT
Received: from 127.0.0.1 (AVG SMTP 7.0.300 [265.6.10]);
	Tue, 22 Mar 2005 19:56:14 +0000
Message-ID: <001701c52f19$33d67df0$920110ac@Desktop>
From: "Jee J.Z." <jz105@york.ac.uk>
To: "subrata goswami" <sgoswami@umich.edu>
References: <420BB87E.7090008@umich.edu><00c101c52ee3$2dccd660$68892090@grouse>
	<42405FB6.10006@umich.edu>
Subject: Re: [Mip4] New ID: End Node based IP Mobility
Date: Tue, 22 Mar 2005 19:56:12 -0000
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Mime-Version: 1.0
Content-Transfer-Encoding: base64
Content-Type: multipart/mixed; boundary="=======AVGMAIL-4240785E5935======="
X-York-MailScanner: Found to be clean
X-York-MailScanner-From: jz105@york.ac.uk
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Cc: Mobile IP v4 <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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7

--=======AVGMAIL-4240785E5935=======
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: base64

SGkgU2licmF0YSwNCg0KDQoNCj4gcGxlYXNlIHNlZSBpbiBsaW5lIGZvciBhbnkgYW5zd2Vycy4N
Cj4gDQo+IEplZSBKLlouIHdyb3RlOg0KPiANCj4gPkhpIFN1YnJhdGEsDQo+ID4NCj4gPlRoYW5r
IHlvdSBmb3Igd3JpdGluZyB0aGlzIGNvbmNpc2UgSUQuIEkgaGF2ZSBhIGZldyBxdWVzdGlvbjoN
Cj4gPg0KPiA+MS4gU2VjdGlvbiAyOiAiLi4uVGhlIENOIHdvdWxkIHN0aWxsIHVzZSBpcHgxIGFz
IGRlc3RpbmF0aW9uIGFkZHJlc3MgZm9yIGFsbA0KPiA+b3V0Z29pbmcgcGFja2V0cywgd2hpY2gg
d291bGQgcmVzdWx0IGluIGFsbCBwYWNrZXRzIHNlbnQgdG8gc3VibmV0IFgyLi4uIg0KPiA+QXJl
IHlvdSB0cnlpbmcgdG8gc2F5ICIuLi5hbGwgcGFja2V0cyBzZW50IHRvIHN1Ym5ldCBYMS4iPw0K
PiA+DQo+ID4gIA0KPiA+DQo+IG5vLCAgcGFja2V0cyB3b3VsZCBiZSByb3V0ZWQgdG8gc3VibmV0
IFgyIGFzIGEgcmVzdWx0IG9mIHRyYW5zbGF0aW9uDQo+IGluIHRoZSBzZW5kZXIuDQoNCk9LLiAN
Cg0KPiA+Mi4gSXQgc2VlbXMgeW91IGFyZSB0cnlpbmcgdG8gdXNlIG9ubHkgZW5kIG5vZGVzIHRv
IHN1cHBvcnQgbW9iaWxpdHkuIEFuZCBhcw0KPiA+eW91IGhhdmUgcG9pbnRlZCBvdXQsIGhvdyBz
dWJuZXQgY2hhbmdlcyBhcmUgZGV0ZWN0ZWQgaXMgYmV5b25kIHRoZSBzY29wZSBvZg0KPiA+dGhp
cyBkb2N1bWVudC4gSG93ZXZlciwgSU1ITywgaXQgaXMgaGFyZCB0byBxdWlja2x5IGRldGVjdCBz
dWJuZXQgY2hhbmdlcw0KPiA+cXVpY2tseSB3aXRob3V0IHRoZSBuZXR3b3JrIGFzc2lzdGFuY2Uu
IEFsc28sIGhvdyBkb2VzIHRoZSBhY2Nlc3MgbmV0d29yaw0KPiA+a25vdyBpdCBzaG91bGQgb2Zm
ZXIgc2VydmljZSB0byB0aGUgTU4gd2l0aG91dCBhbnkgc2VjdXJ0aXkgZW50aXRpZXMgaW4gdGhl
DQo+ID5uZXR3b3JrIGZvciBzdXBwb3J0aW5nIG1vYmlsaXR5Pw0KPiA+ICANCj4gPg0KPiBtYW55
IGRpZmZlcmVudCBhcHByb2FjaGVzIGhhdmUgYmVlbiBzdWdnZXN0ZWQgZm9yIGRldGVjdGluZyBu
ZXR3b3JrDQo+IGNoYW5nZSwgYW55IG9mIHRoZXNlIG1ldGhvZHMgY2FuIGJlIHVzZWQuDQo+IGFn
cmVlZCB0aGF0IHNvbWUgdGhlc2UgbWV0aG9kcyBhcmUgdmVyeSBzbG93Lg0KDQpPSy4gU28gSU1P
IHRoaXMgbWV0aG9kIHdvdWxkIGluaGVyZW50bHkgaW5kdWNlcyBsYXJnZXIgZGlzcnVwdGlvbiBj
YXVzZWQgYnkgc3VibmV0IGNoYW5nZXMgdGhhbiBNb2JpbGUgSVAuDQoNCj4gYXMgbW9iaWxpdHkg
aXMgZW50aXJlbHkgaGFuZGxlZCBieSAgdGhlIGVuZCBub2RlcywgdGhlIG5ldHdvcmsgZG9lcyBu
b3QNCj4gcmVhbGx5IG5lZWQgdG8gZ2V0IGludm9sdmUgKGkuZS4gcmVndWxhciByb3V0aW5nDQo+
IGhhbmRsZXMgYWxsIHBhY2tldHMpLg0KPiANCj4gPjMuIEl0IHNlZW1zIHlvdSBhcmUgY29uc2lk
ZXJpbmcgdGhlIGNhc2UgdGhhdCB0aGUgTU4gY2FuIG9ubHkgY29tbXVuaWNhdGUNCj4gPndpdGgg
b25lIGFjY2VzcyBzdWJuZXQgYXQgYSB0aW1lLiBUaGVyZWZvcmUsIHRoZSBDTiByZWNlaXZpbmcg
U3VibmV0IENoYW5nZQ0KPiA+Q2hhbGxlbmdlIHJlc3BvbnNlcyBmcm9tIGJvdGggb2xkIGFuZCBu
ZXcgc3VibmV0cyBjb3VsZCBiZSB2aWV3ZWQgYXMNCj4gPnNwb29maW5nLiBXaGF0IGlmIHRoZSBN
TiBjYW4gc2ltdWx0YW5lb3VzbHkgY29tbXVuaWNhdGUgd2l0aCBib3RoIG5ldyBhbmQNCj4gPm9s
ZCBhY2Nlc3Mgc3VibmV0cyBhdCBsZWFzdCBkdXJpbmcgaGFuZG92ZXJzPyBBcmUgeW91IGFzc3Vt
aW5nIHRoZSBNTiBhbHdheXMNCj4gPnNlbmRzIG9ubHkgb25lIFN1Ym5ldCBDaGFuZ2UgQ2hhbGxl
bmdlIHJlc3BvbnNlIGluIHRoaXMgY2FzZT8NCj4gPiAgDQo+ID4NCj4gdGhlcmUgaXMgbm90IHJl
YWxseSBhbnkgcmVhc29uIHdoeSB0aGUgTU4gbmVlZHMgdG8gYmUgY29ubmVjdGVkIHRvIG9ubHkN
Cj4gb25lIHN1Ym5ldC4gICBpIGRvIG5vdCB0aGluayB0aGVyZSBpcyBhbnkNCj4gcmVhc29uIHdo
eSB0aGUgTU4gY2FuIG5vdCB0YWxrIHRvIGJvdGggb2xkIGFuZCBuZXcgLCBhbHRob3VnaCBhdCB0
aGUNCj4gcG9pbnQgdGhlIGRyYWZ0IGRvZXMgbm90IGFkZHJlc3MgdGhhdC4NCg0KQWxyaWdodC4g
SSB0aGluayBpdCB3b3VsZCBiZSBnb29kIHRvIHNwZWNpZnkgdGhhdCB0aGUgTU4gbXVzdCBvbmx5
IHJldHVybiBvbmUgU3VibmV0IENoYW5nZSBDaGFsbGVuZ2UgcmVzcG9uc2UgKHNlbnQgZnJvbSB0
aGUgbmV3IHN1Ym5ldCkuDQogDQo+ID40LiBXaXRob3V0IHRoZSBuZXR3b3JrIGFzc2lzdGFuY2Us
IGhvdyBkbyB5b3Ugc3VwcG9zZSB0byBoYW5kbGUgdGhvc2UNCj4gPm1pcy1yb3V0ZWQgcGFja2V0
cyB0byB0aGUgb2xkIHN1Ym5ldCBhZnRlciB0aGUgTU4gY29ubmVjdHMgdG8gdGhlIG5ldw0KPiA+
c3VibmV0Pw0KPiA+ICANCj4gPg0KPiB0aGlzIGNhbiBiZSBoYW5kbGVkIGJ5IGJ1ZmZlcmluZyBw
YWNrZXRzIGF0IHRoZSBzZW5kZXIgLSB3aWxsIGJlIGFkZGVkDQo+IGluIHRoZSBuZXh0IHZlcnNp
b24gb2YgdGhlIGRyYWZ0Lg0KDQpIb3cgZG9lcyB0aGUgc2VuZGVyIGtub3cgd2hlbiB0byBzdGFy
dCBidWZmZXJpbmc/IEl0IG5ldmVyIGtub3dzIHRoZSBNTidzIHN1Ym5ldCBjaGFuZ2UgdW50aWwg
dGhlIE1OIHRlbGxzIGl0LiBBbmQgdGhlIGxvbmcgdGltZSBuZWVkZWQgZm9yIHN1Ym5ldCBjaGFu
Z2UgZGV0ZWN0aW9uIGNvdWxkIGxlYWQgdG8gYSBsYXJnZSBudW1iZXIgb2YgZGF0YSB0byBiZSBt
aXNyb3V0ZWQsIGJlZm9yZSB0aGUgc2VuZGVyIGlzIGF3YXJlIG9mIHRoYXQuIElmIHRoZSBzZW5k
ZXIgYWx3YXlzIGJ1ZmZlcnMgYSBudW1iZXIgb2Ygc2VudCBwYWNrZXRzLCBpdCBzdGlsbCBkb2Vz
IG5vdCBrbm93IHdoaWNoIHBhY2tldCBpcyBsb3N0IGFuZCB3aGljaCBpcyBub3QuDQoNClRoYW5r
IHlvdSBmb3IgeW91ciBhbnN3ZXJzLiBBbmQgbG9vayBmb3J3YXJkIHRvIHlvdXIgbmV4dCByZXZp
c2lvbi4NCg0KSmVlDQoNCj4gYnVmZmVyaW5nIGlzIG5vdCByZXF1aXJlZCBpZiBvbmx5IFRDUCB0
eXBlIG9mIHRyYWZmaWMgaXMgc3VwcG9ydGVkLg0KPiANCj4gPlRoZSBJRCBsb29rcyBsaWtlIGEg
c2ltcGxlIGludGVyZXN0aW5nIGlkZWEsIGJ1dCBpdCBzZWVtcyBhIGxvdCBvZiBpc3N1ZXMNCj4g
PmFyZSB3YWl0aW5nIHRvIGJlIGNvbnNpZGVyZWQuIE1heWJlIHlvdSB0aGluayBpdCBjb3VsZCBi
ZSB0b28gZWFybGx5Pw0KPiA+ICANCj4gPg0KPiB0aGFua3MgZm9yIHlvdXIgY29tbWVudHMgLSB3
aWxsIGFkZHJlc3MgdGhlc2UgaXNzdWVzIGluIHRoZSBuZXh0IHJldmlzaW9uLg0KPiANCj4gPkpl
ZQ0KPiA+DQo+ID4tLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KPiA+RnJvbTogInN1YnJh
dGEgZ29zd2FtaSIgPHNnb3N3YW1pQHVtaWNoLmVkdT4NCj4gPlRvOiA8bWlwNEBpZXRmLm9yZz4N
Cj4gPlNlbnQ6IFRodXJzZGF5LCBGZWJydWFyeSAxMCwgMjAwNSA3OjM5IFBNDQo+ID5TdWJqZWN0
OiBbTWlwNF0gTmV3IElEOiBFbmQgTm9kZSBiYXNlZCBJUCBNb2JpbGl0eQ0KPiA+DQo+ID4NCj4g
PiAgDQo+ID4NCj4gPj5BIG5ldyBJbnRlcm5ldCBEcmFmdCBpcyBhdmFpbGFibGUgb24gbW9iaWxp
dHkgc3VwcG9ydCBpbiBJUCBuZXR3b3Jrcy4NCj4gPj4NCj4gPj5UaXRsZTogSVB2NCBNb2JpbGl0
eSB0aHJvdWdoIFBlZXIgU2lnbmFsaW5nDQo+ID4+DQo+ID4+SUQ6IGRyYWZ0LWdvc3dhbWktbWlw
NC1wZWVyLXNpZ25hbGluZy0wMC50eHQNCj4gPj4NCj4gPj5BYnN0cmFjdDogIFRoaXMgZG9jdW1l
bnQgZGVzY3JpYmVzIGEgd2F5IHRvIHBlcmZvcm0gbW9iaWxpdHkgaW4gSVB2NA0KPiA+Pihwb3Rl
bnRpYWxseSBJUHY2KSB3aXRob3V0IHJlcXVpcmluZyBhbnkgbmV3IGVudGl0eSBpbiBuZXR3b3Jr
cw0KPiA+PmluZnJhc3RydWN0dXJlIChlLmcuIEhvbWUgQWdlbnQsIEZvcmVpZ24gQWdlbnQsIGV0
Yy4pLiBJbnN0ZWFkIG9mIHVzaW5nDQo+ID4+aW5mcmFzdHJ1Y3R1cmUgZW50aXRpZXMgdGhpcyBt
ZXRob2QgZGVsZWdhdGVzIGFsbCB0aGUgbW9iaWxpdHkgZnVuY3Rpb24NCj4gPj50byB0aGUgZW5k
IG5vZGVzLiBUaGUgbWV0aG9kIHJlbGllcyBvbiBzb3VyY2UgYW5kIGRlc3RpbmF0aW9uIGFkZHJl
c3MNCj4gPj50cmFuc2xhdGlvbiBhdCB0aGUgZW5kIG5vZGVzLCBhbmQgc2lnbmFsaW5nIGJldHdl
ZW4gZW5kIG5vZGVzIHRvIHBlcmZvcm0NCj4gPj5oYW5kIG9mZnMgLSBhbGwgdGhlc2UgZnVuY3Rp
b24gY2FuIGJlIGVuY2Fwc3VsYXRlZCBpbiBhbiBlbnRpdHkgY2FsbGVkDQo+ID4+TW9iaWxpdHkg
QWdlbnQgKE1BKSBpbiB0aGUgZW5kIG5vZGVzLg0KPiA+Pg0KPiA+PlVSTDoNCj4gPj5odHRwczov
L2RhdGF0cmFja2VyLmlldGYub3JnL3B1YmxpYy9pZGluZGV4LmNnaT9jb21tYW5kPWlkX2RldGFp
bCZpZD0xMjc4OA0KPiA+Pg0KPiA+Pg0KPiA+Pi0tIA0KPiA+Pk1pcDQgbWFpbGluZyBsaXN0OiBN
aXA0QGlldGYub3JnDQo+ID4+ICAgIFdlYiBpbnRlcmZhY2U6IGh0dHBzOi8vd3d3MS5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL21pcDQNCj4gPj4gICAgIENoYXJ0ZXIgcGFnZTogaHR0cDovL3d3
dy5pZXRmLm9yZy9odG1sLmNoYXJ0ZXJzL21pcDQtY2hhcnRlci5odG1sDQo+ID4+U3VwcGxlbWVu
dGFsIHNpdGU6IGh0dHA6Ly93d3cubWlwNC5vcmcvDQo+ID4+DQo+ID4+ICAgIA0KPiA+Pg0KPiA+
DQo+ID4NCj4gPiAgDQo+ID4NCj4gDQo+IA0KPiANCj4gLS0gDQo+IE1pcDQgbWFpbGluZyBsaXN0
OiBNaXA0QGlldGYub3JnDQo+ICAgICBXZWIgaW50ZXJmYWNlOiBodHRwczovL3d3dzEuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby9taXA0DQo+ICAgICAgQ2hhcnRlciBwYWdlOiBodHRwOi8vd3d3
LmlldGYub3JnL2h0bWwuY2hhcnRlcnMvbWlwNC1jaGFydGVyLmh0bWwNCj4gU3VwcGxlbWVudGFs
IHNpdGU6IGh0dHA6Ly93d3cubWlwNC5vcmcvDQo+IA==

--=======AVGMAIL-4240785E5935=======
Content-Type: text/plain; x-avg=cert; charset=iso-8859-1
Content-Disposition: inline
Content-Description: "AVG certification"
Content-Transfer-Encoding: quoted-printable

Internal Virus Database is out-of-date.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.6.10 - Release Date: 2005-1-10

--=======AVGMAIL-4240785E5935=======
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--=======AVGMAIL-4240785E5935=======--



From mip4-bounces@ietf.org  Tue Mar 22 14:57:23 2005
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 OAA24347
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 14:57:23 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDpaY-0001ej-TU
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 15:02:55 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDpUb-0004ve-5r; Tue, 22 Mar 2005 14:56:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDpUa-0004vY-4H
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 14:56:44 -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 OAA24197
	for <mip4@ietf.org>; Tue, 22 Mar 2005 14:56:42 -0500 (EST)
Received: from av2-2-sn3.vrr.skanova.net ([81.228.9.108])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDpZt-0001cq-Jm
	for mip4@ietf.org; Tue, 22 Mar 2005 15:02:14 -0500
Received: by av2-2-sn3.vrr.skanova.net (Postfix, from userid 502)
	id A481937E4D; Tue, 22 Mar 2005 20:56:33 +0100 (CET)
Received: from smtp1-2-sn3.vrr.skanova.net (smtp1-2-sn3.vrr.skanova.net
	[81.228.9.178]) by av2-2-sn3.vrr.skanova.net (Postfix) with ESMTP
	id 943BF37E47; Tue, 22 Mar 2005 20:56:33 +0100 (CET)
Received: from shiraz.levkowetz.com (h195n1fls311o871.telia.com
	[213.64.174.195])
	by smtp1-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 7D99338009;
	Tue, 22 Mar 2005 20:56:33 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.44)
	id 1DDpUP-0006L9-CC; Tue, 22 Mar 2005 20:56:33 +0100
Message-ID: <42407871.9080505@levkowetz.com>
Date: Tue, 22 Mar 2005 20:56:33 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Karim El-Malki (AL/EAB)" <karim.el-malki@ericsson.com>
Subject: Re: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4
References: <24521B9781EAC745A4BE65966F69C9BE212ABC@esealmw115.eemea.ericsson.se>
In-Reply-To: <24521B9781EAC745A4BE65966F69C9BE212ABC@esealmw115.eemea.ericsson.se>
X-Enigmail-Version: 0.89.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7bit
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit

Hi Karim,

    Just one point here -

on 2005-03-22 8:14 pm Karim El-Malki (AL/EAB) said the following:
> I agree with what you are saying regarding L2 triggers and
> deployment. However I have a comment on the technical
> argument and the FMIP/LLH discussion. The issue is not
> whether FMIP is superior to LLH or viceversa. My argument
> is that they are basically the same thing and use the same
> set of messages between MN and FA: proxy router solicitation,
> proxy router advertisement, registration request/FBU.
> I can't see how one can be better than the other. I'm also
> not surprised since FMIPv4 is a v6-ification on FMIPv6 while
> FMIPv6 and LLH specs were made similar in the first place.

No, the similarity is not surprising, and more importantly, we're
not saying one is inherently better than the other.  If that was
the case, there would be no sense in having both head for
experimental.

Quite to the contrary, we should hope to gain experience with both,
to increase our understanding and work towards something which
may later be standardised.


	Henrik


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


From mip4-bounces@ietf.org  Tue Mar 22 14:57:55 2005
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 OAA24413
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 14:57:55 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDpb4-0001fl-V3
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 15:03:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDpVZ-0005GL-KD; Tue, 22 Mar 2005 14:57:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDpVY-0005Fu-5N
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 14:57:44 -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 OAA24388
	for <mip4@ietf.org>; Tue, 22 Mar 2005 14:57:42 -0500 (EST)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDpas-0001fF-E0
	for mip4@ietf.org; Tue, 22 Mar 2005 15:03:14 -0500
Message-ID: <035601c52f19$90085440$0f6115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Henrik Levkowetz" <henrik@levkowetz.com>
References: <1B631E11D496D711BB2800065BFCB6A10C977920@il02exm13>
	<025c01c52f06$413838c0$0f6115ac@dcml.docomolabsusa.com>
	<42407765.9050900@levkowetz.com>
Subject: Re: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4
Date: Tue, 22 Mar 2005 11:58:40 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit

(raised hand).

            jak

----- Original Message ----- 
From: "Henrik Levkowetz" <henrik@levkowetz.com>
To: "James Kempf" <kempf@docomolabs-usa.com>
Cc: <mip4@ietf.org>
Sent: Tuesday, March 22, 2005 11:52 AM
Subject: Re: [Mip4] RE: Differences between Low Latency Handovers and FMIP
v4


> on 2005-03-22 6:40 pm James Kempf said the following:
>
> <snip a lot of stuff on which I basically agree>
>
> > Anyway, if this WG was serious about its charter to focus on deployment,
it
> > would start up an activity to standardize WLAN switching "IP mobility".
>
> Interesting point.
>
> If we do propose to take this up in the new charter proposal, do we
> have people who would be willing to spend some time and energy on
> this?
>
> Henrik
>
>



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


From mip4-bounces@ietf.org  Tue Mar 22 15:07:13 2005
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 PAA25487
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 15:07:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDpk5-00021a-T4
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 15:12:46 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDpdD-0006QZ-4r; Tue, 22 Mar 2005 15:05:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDpdB-0006QU-Bu
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 15:05:37 -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 PAA25244
	for <mip4@ietf.org>; Tue, 22 Mar 2005 15:05:35 -0500 (EST)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDpiT-0001wq-UR
	for mip4@ietf.org; Tue, 22 Mar 2005 15:11:07 -0500
Message-ID: <036101c52f1a$a8a7c6b0$0f6115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Rajeev Koodli" <rajeev@iprg.nokia.com>
References: <1B631E11D496D711BB2800065BFCB6A10C977920@il02exm13>
	<025c01c52f06$413838c0$0f6115ac@dcml.docomolabsusa.com>
	<424074B0.9010800@iprg.nokia.com>
Subject: Re: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4
Date: Tue, 22 Mar 2005 12:06:31 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: 7bit
Cc: mip4@ietf.org, Narayanan Vidya-CVN065 <vidya@motorola.com>,
        "'Karim El-Malki \\\(AL/EAB\\\)'" <karim.el-malki@ericsson.com>
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit

Hi Rajeev,

> >Unfortunately, vendors would like to keep it that way, since having a
> >standardized solution means that enterprise customers and service
providers
> >would be free to mix and match solutions and less likely to go single
> >supplier. So FMIP is likely to be of limited interest for WLAN
deployments
> >going forward. Perhaps 3GPP2 is interested in it? Though they already
have
> >
> >
> On the contrary, wouldn't you expect the enterprises to start demanding
> interoperability
> between boxes? If vendors have "holds" on enterprises for their boxes
> alone, that does not
> sound like a way going forward.
>

Well, one would hope.

> >Anyway, if this WG was serious about its charter to focus on deployment,
it
> >would start up an activity to standardize WLAN switching "IP mobility".
> >
> >
> >
> Doesn't this mean tunneling?  A switch tunneling an L2 frame in L3
> sounds sub-optimal
> since it needs to "go back" through the router to reach the IP network,
> and eventually the
> destination router and the switch. Anyway, why is there a need for
> standardization here?
>

There's a bit  more of a dogleg on the routing than on something like FMIP.
With FMIP, the dogleg is from the crossover aggregation router between the
previous and new ARs and the previous and new ARs. With the WLAN switches,
there's that and between the switch and previous AR.

As for what's to standardize, essentially, these protocols work like
Postreg. So there would need to be some agreement about the inter-switch
signaling to set up the tunnel, and the actual tunnel type. I don't know
offhand what kind of tunnel is used, I suspect each switch might use a
different tunnel type.

            jak



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


From mip4-bounces@ietf.org  Tue Mar 22 15:09:36 2005
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 PAA25873
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 15:09:36 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDpmN-000255-99
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 15:15:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDpgD-0006s3-Mz; Tue, 22 Mar 2005 15:08:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDpgC-0006ry-22
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 15:08:44 -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 PAA25684
	for <mip4@ietf.org>; Tue, 22 Mar 2005 15:08:42 -0500 (EST)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDplW-00022m-Do
	for mip4@ietf.org; Tue, 22 Mar 2005 15:14:14 -0500
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j2MKbvo29024;
	Tue, 22 Mar 2005 12:37:57 -0800
X-mProtect: <200503222037> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp141217.americas.nokia.com (172.18.141.217,
	claiming to be "[172.18.141.217]")
	by darkstar.iprg.nokia.com smtpd61Ucf7; Tue, 22 Mar 2005 12:37:54 PST
Message-ID: <42407B0E.40700@iprg.nokia.com>
Date: Tue, 22 Mar 2005 12:07:42 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4
References: <1B631E11D496D711BB2800065BFCB6A10C977920@il02exm13>	<025c01c52f06$413838c0$0f6115ac@dcml.docomolabsusa.com>
	<42407765.9050900@levkowetz.com>
In-Reply-To: <42407765.9050900@levkowetz.com>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813
Cc: James Kempf <kempf@docomolabs-usa.com>, 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>
Content-Type: multipart/mixed; boundary="===============1252882061=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c

This is a multi-part message in MIME format.
--===============1252882061==
Content-Type: multipart/alternative;
	boundary="------------070001040705020303090502"

This is a multi-part message in MIME format.
--------------070001040705020303090502
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


Hello Henrik,

I believe that we should have a single solution for subnet
mobility. And, you may be aware that MIPSHOP is
considering "AAA Keys for Handover" as one of the
mechanisms to establish MN - AR security association.
We could get the keys for IPv4 as well.
In addition, there was discussion about extending the "SEND-based
key derivation for handover" for IPv4 as well. (Disclaimer: James and
myself are co-authors on this draft).

So, we could have a PS solution for IPv4 subnet mobility, just
as MIPSHOP is attempting to define one.

My 2 cents..

-Rajeev



Henrik Levkowetz wrote:

>on 2005-03-22 6:40 pm James Kempf said the following:
>
><snip a lot of stuff on which I basically agree>
>
>  
>
>>Anyway, if this WG was serious about its charter to focus on deployment, it
>>would start up an activity to standardize WLAN switching "IP mobility".
>>    
>>
>
>Interesting point.  
>
>If we do propose to take this up in the new charter proposal, do we
>have people who would be willing to spend some time and energy on
>this?
>
>	Henrik
>
>
>  
>

--------------070001040705020303090502
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
Hello Henrik,<br>
<br>
I believe that we should have a single solution for subnet<br>
mobility. And, you may be aware that MIPSHOP is <br>
considering "AAA Keys for Handover" as one of the<br>
mechanisms to establish MN - AR security association.<br>
We could get the keys for IPv4 as well. <br>
In addition, there was discussion about extending the "SEND-based<br>
key derivation for handover" for IPv4 as well. (Disclaimer: James and<br>
myself are co-authors on this draft).<br>
<br>
So, we could have a PS solution for IPv4 subnet mobility, just <br>
as MIPSHOP is attempting to define one.<br>
<br>
My 2 cents..<br>
<br>
-Rajeev<br>
<br>
<br>
<br>
Henrik Levkowetz wrote:<br>
<blockquote cite="mid42407765.9050900@levkowetz.com" type="cite">
  <pre wrap="">on 2005-03-22 6:40 pm James Kempf said the following:

&lt;snip a lot of stuff on which I basically agree&gt;

  </pre>
  <blockquote type="cite">
    <pre wrap="">Anyway, if this WG was serious about its charter to focus on deployment, it
would start up an activity to standardize WLAN switching "IP mobility".
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Interesting point.  

If we do propose to take this up in the new charter proposal, do we
have people who would be willing to spend some time and energy on
this?

	Henrik


  </pre>
</blockquote>
</body>
</html>

--------------070001040705020303090502--


--===============1252882061==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1252882061==--



From mip4-bounces@ietf.org  Tue Mar 22 15:16:43 2005
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 PAA27381
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 15:16:43 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDptG-0002R3-Ln
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 15:22:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDpkp-0007dv-G8; Tue, 22 Mar 2005 15:13:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDpkn-0007dd-Es
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 15:13:29 -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 PAA26660
	for <mip4@ietf.org>; Tue, 22 Mar 2005 15:13:27 -0500 (EST)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDpq6-0002Dw-Oh
	for mip4@ietf.org; Tue, 22 Mar 2005 15:19:00 -0500
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j2MKhI905310;
	Tue, 22 Mar 2005 12:43:18 -0800
X-mProtect: <200503222043> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp141217.americas.nokia.com (172.18.141.217,
	claiming to be "[172.18.141.217]")
	by darkstar.iprg.nokia.com smtpddA8I37; Tue, 22 Mar 2005 12:43:16 PST
Message-ID: <42407C50.9060508@iprg.nokia.com>
Date: Tue, 22 Mar 2005 12:13:04 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
Subject: Re: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4
References: <1B631E11D496D711BB2800065BFCB6A10C977920@il02exm13>	<025c01c52f06$413838c0$0f6115ac@dcml.docomolabsusa.com>	<424074B0.9010800@iprg.nokia.com>
	<036101c52f1a$a8a7c6b0$0f6115ac@dcml.docomolabsusa.com>
In-Reply-To: <036101c52f1a$a8a7c6b0$0f6115ac@dcml.docomolabsusa.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit
Cc: mip4@ietf.org, Narayanan Vidya-CVN065 <vidya@motorola.com>,
        "'Karim El-Malki \\\(AL/EAB\\\)'" <karim.el-malki@ericsson.com>
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit



James Kempf wrote:

>As for what's to standardize, essentially, these protocols work like
>Postreg. So there would need to be some agreement about the inter-switch
>signaling to set up the tunnel, and the actual tunnel type. I don't know
>offhand what kind of tunnel is used, I suspect each switch might use a
>different tunnel type.
>
>  
>
Okay. Why do we need to standardize inter-switch communication? Are you
considering the switch also as a L3 device from a MIP MN perspective?

-Rajeev

>            jak
>
>
>
>  
>

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


From mip4-bounces@ietf.org  Tue Mar 22 15:18:01 2005
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 PAA27764
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 15:18:01 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDpuV-0002Wt-G2
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 15:23:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDpmt-0007rw-R6; Tue, 22 Mar 2005 15:15:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDpmr-0007rr-G3
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 15:15:37 -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 PAA27024
	for <mip4@ietf.org>; Tue, 22 Mar 2005 15:15:35 -0500 (EST)
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDpsB-0002Jh-49
	for mip4@ietf.org; Tue, 22 Mar 2005 15:21:08 -0500
Received: from esealmw126.eemea.ericsson.se ([153.88.254.123])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j2MKFLfw000105; Tue, 22 Mar 2005 21:15:26 +0100 (MET)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 22 Mar 2005 21:15:22 +0100
Received: from esealmw115.eemea.ericsson.se ([153.88.200.6]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 22 Mar 2005 21:15:22 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4
Date: Tue, 22 Mar 2005 21:15:22 +0100
Message-ID: <24521B9781EAC745A4BE65966F69C9BE212ABD@esealmw115.eemea.ericsson.se>
Thread-Topic: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4
Thread-index: AcUvFKD/RMJfbts9SbyKill9b3RwQwABuD0T
From: "Karim El-Malki \(AL/EAB\)" <karim.el-malki@ericsson.com>
To: "Narayanan Vidya-CVN065 " <vidya@motorola.com>,
        "James Kempf " <kempf@docomolabs-usa.com>,
        "Rajeev Koodli " <rajeev@iprg.nokia.com>
X-OriginalArrivalTime: 22 Mar 2005 20:15:22.0629 (UTC)
	FILETIME=[E074A350:01C52F1B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 515708a075ffdf0a79d1c83b601e2afd
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 578c2c9d0cb01ffe6e1ca36540edd070
Content-Transfer-Encoding: quoted-printable

As I wrote in a previous emaul to Rajeev, the reason why it
was left out of LLH is that there was an existing mechanism
for this in the route optv4 spec: PFANE (previous FA notification
extension).
/Karim

-----Original Message-----
From: Narayanan Vidya-CVN065
To: Karim El-Malki (AL/EAB); James Kempf; Rajeev Koodli
Cc: mip4@ietf.org
Sent: 22/03/2005 20:23
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and =
FMIP v4

It seems to me that the one thing that is missing from LLH is a method
of doing mobile initiated post-reg. This is provided by FMIP.=20

Vidya

-----Original Message-----
From: Karim El-Malki \(AL/EAB\) [mailto:karim.el-malki@ericsson.com]=20
Sent: Tuesday, March 22, 2005 1:14 PM
To: James Kempf ; Narayanan Vidya-CVN065; Rajeev Koodli=20
Cc: mip4@ietf.org
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and
FMIP v4


I agree with what you are saying regarding L2 triggers and deployment.
However I have a comment on the technical argument and the FMIP/LLH
discussion. The issue is not whether FMIP is superior to LLH or
viceversa. My argument is that they are basically the same thing and use
the same set of messages between MN and FA: proxy router solicitation,
proxy router advertisement, registration request/FBU. I can't see how
one can be better than the other. I'm also not surprised since FMIPv4 is
a v6-ification on FMIPv6 while FMIPv6 and LLH specs were made similar in
the first place. /Karim

-----Original Message-----
From: James Kempf
To: Narayanan Vidya-CVN065; Karim El-Malki (AL/EAB); Rajeev Koodli
Cc: mip4@ietf.org
Sent: 22/03/2005 18:40
Subject: Re: [Mip4] RE: Differences between Low Latency Handovers and
FMIP v4

I think this whole discussion about L2 triggers and LLH is a red
herring. People are taking the wording "L2 trigger" too literally. It
doesn't actually have to be a protocol message in the L2 protocol, it
just must be indication that handover has occured or will occur. The
handover indication doesn't have to include all the L3 information in
Table 1 in one L2 message. It can be deduced. For example, using
something like CARD or even the RtPrxy messages, the MN can build up a
table of AP L2 address to FA address map, and use that. I believe that
is what Karim means when he says that FMIP also needs this kind of
information. Unless an FMIP MN has some way to know that a handover has
occured or will occur, there's no FBU. And unless it has some
information about what new subnet the MN is in or will be, it can't put
that information into the FBU to tell the old FA where to send packets.

I still believe there's value for FMIPv4, believe it is superior to LLH
if host based all-L3 handover optimization is required, and support work
on it; however, this whole argument of FMIP v.s. LLH strikes me as being
something like the medieval argument about how many angles can dance on
the head of a pin. Wireless LAN deployments are increasingly going in
the direction of wireless LAN switches (60% of new purchases and
practically all upgrades), and these switches already have
nonstandardized solutions for "IP Mobility", which, in effect, means
tunneling L2 frames in L3 between subnets. Unfortunately, vendors would
like to keep it that way, since having a standardized solution means
that enterprise customers and service providers would be free to mix and
match solutions and less likely to go single supplier. So FMIP is likely
to be of limited interest for WLAN deployments going forward. Perhaps
3GPP2 is interested in it? Though they already have their own solution
in the A!
 10/A11 interface, which looks strikingly like the solution adopted by
the WLAN switch vendors.

Anyway, if this WG was serious about its charter to focus on deployment,
it would start up an activity to standardize WLAN switching "IP
mobility".

            jak


----- Original Message -----=20
From: "Narayanan Vidya-CVN065" <vidya@motorola.com>
To: "'Karim El-Malki \(AL/EAB\)'" <karim.el-malki@ericsson.com>; "Rajeev
Koodli" <rajeev@iprg.nokia.com>
Cc: <mip4@ietf.org>
Sent: Monday, March 21, 2005 5:56 PM
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and
FMIP v4


> Karim,
> I have a rather stupid question. All the triggers listed in table 1 of
LLH
list some L3 parameter or another that needs to be present in the
trigger. This suggests to me that any kind of L2 trigger that is needed
for LLH (Pre-reg or post-reg) requires the presence of the appropriate
parameter listed in the "Parameters" row of the table.
>
> Am I missing something here?
>
> Vidya
>
> -----Original Message-----
> From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf
Of
Karim El-Malki \(AL/EAB\)
> Sent: Monday, March 21, 2005 5:20 PM
> To: Rajeev Koodli
> Cc: mip4@ietf.org
> Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and
FMIPv4
>
>
> >>I understand your point that you took FMIPv6 and applied
> >>it to v4 to make FMIPv4. But that doesn't make it substantially=20
> >>different from Low Latency. Your spec does use link-layer triggers
to
> >>be able to send the RtSolPr. An interface coming up in the MN is
used
> >>just the same in Low Latency and is defined as a mobile trigger in
Low
> >>Latency (L2-LU). PRE-REG involves the MN getting such a mobile=20
> >>trigger and sending a PrRtSol and receiving a PrRtAdv. What's the=20
> >>difference compared to your spec?
> >>
> >>
> >As I explained below (and also itemized in the List below), the=20
> >essential difference is that LLH requires L2 to provide L3
information
> >(nFA, MN IP addresses, their MAC addresses etc.) via various L2-*T
type
> >of triggers.
> >This is a Big difference for us since we do not wish to change L2 to=20
> >implement fast handovers. Both FMIPv6 and FMIPv4 work without=20
> >requiring such changes to L2.
>
> That's not correct.
> Let's take the case where the L3 handoff is initiated before L2=20
> handoff. Taking WLAN for example, in LLH the MN gets info from L2
(e.g.
AP scan) and sends a PrRtSol to get a PrRtAdv containing information of
the subnet it may move to. I can't see any change required to L2. Where
is the difference compared to what you have described? The only
difference is that we definied all "handoff hints" as L2 triggers, just
as a result of the AP scan is defined as a mobile trigger. The LLH spec
doesn't mandate the presence of all trigger types in all cases. It
depends on what the L2 has to offer.
>
> >>The messages are even called the same. Nothing special
> >>or L2-dependent about this L2 trigger. For example PRE-REG
> >>
> >>
> >Well, the essential difference is what requirements LLH imposes on L2

> >triggers. Table 1 in LLH specifies what information is expected from
L2
> >triggers including the nFA, MN IP addresses from the various L2-*T=20
> >triggers.
>
> LLH can work with different types of L2 triggers (which is very
different
from requiring L2 changes) and supports the case you have described in
FMIPv4. Table 1 specifies the different types of triggers that LLH can
utilise. Note that it includes very simple triggers that work even on
WLAN. It is wrong to say that all triggers in Table 1 are required on
all L2s for LLH to work.
>
> >>can be applied to WLAN using AP scans. I don't think that the=20
> >>difference in packet formats makes it a substantially different spec

> >>from low latency.  Also, the other case you are considering involves

> >>an L3 handoff that happens after the MN attaches to the new link.=20
> >>This cannot really be considered a "fast" handoff, which would=20
> >>instead be where the handoff happens before or in parallel with the
L2
> >>handoff.
> >>
> >>
> >Perhaps you have missed something.. The FMIP design allows movement=20
> >detection and router/FA discovery phases to be done prior to L2=20
> >handover. The "reactive" handover we refer to is the one where the
FBU
> >is sent from the
> >new link. But, the MN uses the neighborhood information via Proxy
Router
> >messages to determine movement detection and router/FA config=20
> >information of the new subnet. So, your description above is not=20
> >accurate.
>
> Note that I first addressed the L3-movement-before-L2 (where I am
saying
that FMIPv4 is no different from LLH) and then I wrote "the other case
you are considering....". Am I incorrect in saying that FMIPv4 also
supports the L3-handoff-after-L2-handoff case? I think I had read that
case in FMIPv4 (i.e. FBU sent from new link). That's why I had asked
about PFANE.
>
> >>This L3-handoff-after-L2-handoff was already covered in the route=20
> >>optv4 spec using PFANE. You may have missed the question so I'll=20
> >>repeat it: did you consider the PFANE? Why aren't you just reusing
the
> >>PFANE (Previous FA Notification
> >>Extension) work for that scenario?
> >>
> >>
> >Please see above. The key difference with respect to Previous FA
(what
> >used to be Previous AR
> >notification in v6) Notification is that you don't incur delays due
to
> >movement detection and
> >router/FA discovery.
>
> If you are only considering the L3-handoff-before-L2-handoff case then
there are very little differences between FMIPv4 and LLH for the reasons
given above.
>
> >So, apart from the independence from L2 to provide L3 information,
the
> >other crucial difference is the decoupling of neighborhood discovery=20
> >from the actual handover signaling. This not only reduces the number=20
> >of signaling messages
> >during the handover itself, but also makes the reactive fast
handovers
> >possible.
>
> Again I can't see the crucial difference from LLH.
> The ND messages are basically the same (even almost called the same):
PrRtSol and PrRtAdv. LLH uses standard MIPv4 naming (Registration
Request and Reply) while FMIPv4 achieves the same result but calls this
an FBU. Tunnelling between FAs is supported in both specs. LLH
furthermore supports anticipated HA updating or "local" HA updating
(regional registrations). It seems to me that to make things "faster"
one would want to update the local/global HA directly if possible since
FA-FA routing can be inefficient in a tree-like network structure
compared to updating a local HA. I am curious to understand why you have
eliminated that option in FMIPv4 compared to LLH. Measurements performed
on FMIPv6+HMIPv6 integration prove that it makes sense to combine
local/global HA updating with the FMIP mechanism. /Karim
>
> --
> 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/
>


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


From mip4-bounces@ietf.org  Tue Mar 22 15:29:37 2005
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 PAA29252
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 15:29:37 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDq5k-0002zI-HK
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 15:35:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDpzb-00029e-EB; Tue, 22 Mar 2005 15:28:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDpza-00029Z-3H
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 15:28:46 -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 PAA29103
	for <mip4@ietf.org>; Tue, 22 Mar 2005 15:28:44 -0500 (EST)
Received: from av1-1-sn3.vrr.skanova.net ([81.228.9.105])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDq4u-0002xC-OL
	for mip4@ietf.org; Tue, 22 Mar 2005 15:34:17 -0500
Received: by av1-1-sn3.vrr.skanova.net (Postfix, from userid 502)
	id D05D937EA3; Tue, 22 Mar 2005 21:28:36 +0100 (CET)
Received: from smtp1-1-sn3.vrr.skanova.net (smtp1-1-sn3.vrr.skanova.net
	[81.228.9.177]) by av1-1-sn3.vrr.skanova.net (Postfix) with ESMTP
	id C26F337E42; Tue, 22 Mar 2005 21:28:36 +0100 (CET)
Received: from shiraz.levkowetz.com (h195n1fls311o871.telia.com
	[213.64.174.195])
	by smtp1-1-sn3.vrr.skanova.net (Postfix) with ESMTP id ABF4E38025;
	Tue, 22 Mar 2005 21:28:36 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.44)
	id 1DDpzQ-0003QZ-8W; Tue, 22 Mar 2005 21:28:36 +0100
Message-ID: <42407FF3.3030808@levkowetz.com>
Date: Tue, 22 Mar 2005 21:28:35 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Rajeev Koodli <rajeev@iprg.nokia.com>
Subject: Re: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4
References: <1B631E11D496D711BB2800065BFCB6A10C977920@il02exm13>	<025c01c52f06$413838c0$0f6115ac@dcml.docomolabsusa.com>
	<42407765.9050900@levkowetz.com> <42407B0E.40700@iprg.nokia.com>
In-Reply-To: <42407B0E.40700@iprg.nokia.com>
X-Enigmail-Version: 0.89.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: 7bit
Cc: James Kempf <kempf@docomolabs-usa.com>, 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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Content-Transfer-Encoding: 7bit

Ok. So I see there is some interest, and somebody willing to do work
in the area.  I will have to check with Gab and the ADs to make sure
we agree on where the work should be done, if we take it up.

	Henrik


on 2005-03-22 9:07 pm Rajeev Koodli said the following:
> Hello Henrik,
> 
> I believe that we should have a single solution for subnet
> mobility. And, you may be aware that MIPSHOP is
> considering "AAA Keys for Handover" as one of the
> mechanisms to establish MN - AR security association.
> We could get the keys for IPv4 as well.
> In addition, there was discussion about extending the "SEND-based
> key derivation for handover" for IPv4 as well. (Disclaimer: James and
> myself are co-authors on this draft).
> 
> So, we could have a PS solution for IPv4 subnet mobility, just
> as MIPSHOP is attempting to define one.
> 
> My 2 cents..
> 
> -Rajeev
> 
> 
> 
> Henrik Levkowetz wrote:
> 
>>on 2005-03-22 6:40 pm James Kempf said the following:
>>
>><snip a lot of stuff on which I basically agree>
>>
>>  
>>
>>>Anyway, if this WG was serious about its charter to focus on deployment, it
>>>would start up an activity to standardize WLAN switching "IP mobility".
>>>    
>>>
>>
>>Interesting point.  
>>
>>If we do propose to take this up in the new charter proposal, do we
>>have people who would be willing to spend some time and energy on
>>this?
>>
>>	Henrik
>>
>>
>>  
>>
> 


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


From mip4-bounces@ietf.org  Tue Mar 22 15:46:23 2005
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 PAA01175
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 15:46:23 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDqM0-0003mn-2g
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 15:51:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDqFF-0005Ts-JO; Tue, 22 Mar 2005 15:44:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDqFD-0005Tf-Hz
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 15:44:57 -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 PAA01029
	for <mip4@ietf.org>; Tue, 22 Mar 2005 15:44:53 -0500 (EST)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDqKX-0003h5-Aq
	for mip4@ietf.org; Tue, 22 Mar 2005 15:50:26 -0500
Message-ID: <037f01c52f20$26c104d0$0f6115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Rajeev Koodli" <rajeev@iprg.nokia.com>
References: <1B631E11D496D711BB2800065BFCB6A10C977920@il02exm13>	<025c01c52f06$413838c0$0f6115ac@dcml.docomolabsusa.com>	<424074B0.9010800@iprg.nokia.com><036101c52f1a$a8a7c6b0$0f6115ac@dcml.docomolabsusa.com>
	<42407C50.9060508@iprg.nokia.com>
Subject: Re: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4
Date: Tue, 22 Mar 2005 12:45:51 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit
Cc: mip4@ietf.org, Narayanan Vidya-CVN065 <vidya@motorola.com>,
        "'Karim El-Malki \\\(AL/EAB\\\)'" <karim.el-malki@ericsson.com>
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit

> Okay. Why do we need to standardize inter-switch communication? Are you
> considering the switch also as a L3 device from a MIP MN perspective?
>

The fact that handover optimization was done at a switch rather than at the
router had mainly to do with practical considerations about how to bring a
product out best, I suspect. It allows one to install switches below one's
existing routers, without having to modify the routers. Thus, an easier
sale.

>From the MIP perspective, I think the FA is the place to define the
function. But I'm not sure, though now that I think of it, whether the
switch vendors would even be interested in working in MIP4. Most of their
efforts are focussed on CAPWAP, and I think they might rather want to have
the handover optimization functionality defined at the Access Controller
(AC, a functional entity that controls the access points), if they want it
at all (I think they might agree from a technical standpoint that it would
be nice).

Having the switch vendors involved is necessary, otherwise nobody will
implement it, just as has been the case with all the other proposed handover
optimization technologies up until now.

            jak




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


From mip4-bounces@ietf.org  Tue Mar 22 15:49:53 2005
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 PAA01434
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 15:49:52 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDqPM-0003qa-Kv
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 15:55:25 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDqIp-0006J2-RI; Tue, 22 Mar 2005 15:48:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDqIo-0006Ix-KF
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 15:48:38 -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 PAA01361
	for <mip4@ietf.org>; Tue, 22 Mar 2005 15:48:36 -0500 (EST)
Received: from mail.flarion.com ([63.103.94.23]
	helo=ftmailgfi1.flariontech.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDqO9-0003ot-HD
	for mip4@ietf.org; Tue, 22 Mar 2005 15:54:09 -0500
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	ftmailgfi1.flariontech.com with Microsoft
	SMTPSVC(5.0.2195.6713); Tue, 22 Mar 2005 15:48:28 -0500
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4
Date: Tue, 22 Mar 2005 15:48:28 -0500
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBC6BC@ftmailserver.flariontech.com>
Thread-Topic: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4
Thread-Index: AcUvGV4ihIeWdN9oRweHUuwHMsiWRAABpJWQ
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Henrik Levkowetz" <henrik@levkowetz.com>,
        "Karim El-Malki \(AL/EAB\)" <karim.el-malki@ericsson.com>
X-OriginalArrivalTime: 22 Mar 2005 20:48:28.0679 (UTC)
	FILETIME=[803BD170:01C52F20]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: quoted-printable

Hi Henrik,=20

Jumping in to add 2 cents below

 > on 2005-03-22 8:14 pm Karim El-Malki (AL/EAB) said the following:
 > > I agree with what you are saying regarding L2 triggers and
 > > deployment. However I have a comment on the technical
 > > argument and the FMIP/LLH discussion. The issue is not
 > > whether FMIP is superior to LLH or viceversa. My argument
 > > is that they are basically the same thing and use the same
 > > set of messages between MN and FA: proxy router solicitation,
 > > proxy router advertisement, registration request/FBU.
 > > I can't see how one can be better than the other. I'm also
 > > not surprised since FMIPv4 is a v6-ification on FMIPv6 while
 > > FMIPv6 and LLH specs were made similar in the first place.
 >=20
 > No, the similarity is not surprising, and more importantly, we're
 > not saying one is inherently better than the other.  If that was
 > the case, there would be no sense in having both head for
 > experimental.
 >=20
 > Quite to the contrary, we should hope to gain experience with both,
 > to increase our understanding and work towards something which
 > may later be standardised.

=3D> I understand we'd want to do that when we see two (or more)
proposals doing things differently and/or are suited to different
environments, and/or are making different assumptions.
The only things I see different here are:
1. Packtization of information (and different names)
2. Allowing IP handover after L2 handover.

I don't see how 1) is worth pursuing, but 2) would be interesting.
For 2), why don't we revive PFANE from the route opt draft. It seems
like the most useful part of that old draft.

Hesham

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

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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


From mip4-bounces@ietf.org  Tue Mar 22 16:52:31 2005
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 QAA11935
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 16:52:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDrO1-0007zv-8a
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 16:58:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDrDu-0008K5-2t; Tue, 22 Mar 2005 16:47:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDrDr-0008K0-KW
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 16:47:36 -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 QAA11480
	for <mip4@ietf.org>; Tue, 22 Mar 2005 16:47:33 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDrJC-0007ni-VM
	for mip4@ietf.org; Tue, 22 Mar 2005 16:53:07 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-2.cisco.com with ESMTP; 22 Mar 2005 13:47:26 -0800
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j2MLlIDv012452;
	Tue, 22 Mar 2005 13:47:21 -0800 (PST)
Received: from kleung-w2k01.cisco.com (dhcp-128-107-163-236.cisco.com
	[128.107.163.236]) by mira-sjc5-b.cisco.com (MOS 3.4.5-GR)
	with ESMTP id BDE79645; Tue, 22 Mar 2005 13:47:20 -0800 (PST)
Message-Id: <4.3.2.7.2.20050322134204.028b3e18@mira-sjcm-2.cisco.com>
X-Sender: kleung@mira-sjcm-2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 22 Mar 2005 13:47:20 -0800
To: "Soliman, Hesham" <H.Soliman@flarion.com>
From: Kent Leung <kleung@cisco.com>
Subject: RE: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBC6BC@ftmailserver.flar
	iontech.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: mip4@ietf.org, Henrik Levkowetz <henrik@levkowetz.com>,
        "Karim El-Malki \(AL/EAB\)" <karim.el-malki@ericsson.com>
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135

Adding my 2 cents too.  See "KL>" below.

>If we do propose to take this up in the new charter proposal, do we
>have people who would be willing to spend some time and energy on
>this?
>
>         Henrik

KL> Count me in.


At 03:48 PM 3/22/2005 -0500, Soliman, Hesham wrote:
>Hi Henrik,
>
>Jumping in to add 2 cents below
>
>  > on 2005-03-22 8:14 pm Karim El-Malki (AL/EAB) said the following:
>  > > I agree with what you are saying regarding L2 triggers and
>  > > deployment. However I have a comment on the technical
>  > > argument and the FMIP/LLH discussion. The issue is not
>  > > whether FMIP is superior to LLH or viceversa. My argument
>  > > is that they are basically the same thing and use the same
>  > > set of messages between MN and FA: proxy router solicitation,
>  > > proxy router advertisement, registration request/FBU.
>  > > I can't see how one can be better than the other. I'm also
>  > > not surprised since FMIPv4 is a v6-ification on FMIPv6 while
>  > > FMIPv6 and LLH specs were made similar in the first place.
>  >
>  > No, the similarity is not surprising, and more importantly, we're
>  > not saying one is inherently better than the other.  If that was
>  > the case, there would be no sense in having both head for
>  > experimental.
>  >
>  > Quite to the contrary, we should hope to gain experience with both,
>  > to increase our understanding and work towards something which
>  > may later be standardised.
>
>=> I understand we'd want to do that when we see two (or more)
>proposals doing things differently and/or are suited to different
>environments, and/or are making different assumptions.
>The only things I see different here are:
>1. Packtization of information (and different names)
>2. Allowing IP handover after L2 handover.
>
>I don't see how 1) is worth pursuing, but 2) would be interesting.
>For 2), why don't we revive PFANE from the route opt draft. It seems
>like the most useful part of that old draft.


KL> PFANE is good to have.  Also the BU and BAck messages to
set up tunnel between FAs is good.  As I said before, I'm keen to
keep the solution in line of MIPv4 (FMIPv4 on FAs only).

Kent

--
      |           |                   Kent Leung
     :|:         :|:                  IP Mobility Development
    :|||:       :|||:                 Internet Technologies Division
   :|||||||:   :|||||||:              Voice: 408.526.5030
.:|||||||||:.:|||||||||:.             Fax:   408.525.1653
  c i s c o S y s t e m s             Email: kleung@cisco.com

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


From mip4-bounces@ietf.org  Tue Mar 22 17:54:51 2005
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 RAA16691
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 17:54:51 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDsMM-0001dq-C6
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 18:00:26 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDsEt-0001yW-OS; Tue, 22 Mar 2005 17:52:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDsEs-0001y7-4q
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 17:52:42 -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 RAA16496
	for <mip4@ietf.org>; Tue, 22 Mar 2005 17:52:39 -0500 (EST)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDsKC-0001Wq-Vl
	for mip4@ietf.org; Tue, 22 Mar 2005 17:58:14 -0500
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j2MNMUk04597;
	Tue, 22 Mar 2005 15:22:30 -0800
X-mProtect: <200503222322> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp141217.americas.nokia.com (172.18.141.217,
	claiming to be "[172.18.141.217]")
	by darkstar.iprg.nokia.com smtpdW4MOAx; Tue, 22 Mar 2005 15:22:29 PST
Message-ID: <4240A1A1.70309@iprg.nokia.com>
Date: Tue, 22 Mar 2005 14:52:17 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Kent Leung <kleung@cisco.com>
Subject: Re: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4
References: <4.3.2.7.2.20050322134204.028b3e18@mira-sjcm-2.cisco.com>
In-Reply-To: <4.3.2.7.2.20050322134204.028b3e18@mira-sjcm-2.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit
Cc: "Soliman, Hesham" <H.Soliman@flarion.com>, mip4@ietf.org,
        Henrik Levkowetz <henrik@levkowetz.com>,
        "Karim El-Malki \(AL/EAB\)" <karim.el-malki@ericsson.com>
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit


Hi Kent,


Kent Leung wrote:

> KL> PFANE is good to have.  Also the BU and BAck messages to
> set up tunnel between FAs is good.  As I said before, I'm keen to
> keep the solution in line of MIPv4 (FMIPv4 on FAs only).
>
FMIPv4 has the PFANE-type reactive handover; it is also better because
movement detection and agent discovery delays are effectively eliminated
due to performing neighborhood discovery (out of handover critical timing)
on the previous link.

Regards,

-Rajeev

> Kent
>
> -- 
>      |           |                   Kent Leung
>     :|:         :|:                  IP Mobility Development
>    :|||:       :|||:                 Internet Technologies Division
>   :|||||||:   :|||||||:              Voice: 408.526.5030
> .:|||||||||:.:|||||||||:.             Fax:   408.525.1653
>  c i s c o S y s t e m s             Email: kleung@cisco.com
>

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


From mip4-bounces@ietf.org  Tue Mar 22 18:25:34 2005
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 SAA20279
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 18:25:34 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDsq5-0002ff-2c
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 18:31:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDsj6-00075c-Ek; Tue, 22 Mar 2005 18:23:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDsj4-00075U-Sc
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 18:23:54 -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 SAA20107
	for <mip4@ietf.org>; Tue, 22 Mar 2005 18:23:52 -0500 (EST)
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.33)
	id 1DDsoR-0002Wb-5B
	for mip4@ietf.org; Tue, 22 Mar 2005 18:29:27 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-3.cisco.com with ESMTP; 22 Mar 2005 15:23:46 -0800
X-IronPort-AV: i="3.91,112,1110182400"; 
	d="scan'208"; a="239069174:sNHT28069744"
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j2MNNagE010649;
	Tue, 22 Mar 2005 15:23:36 -0800 (PST)
Received: from kleung-w2k01.cisco.com (dhcp-128-107-163-236.cisco.com
	[128.107.163.236]) by mira-sjc5-b.cisco.com (MOS 3.4.5-GR)
	with ESMTP id BDE91781; Tue, 22 Mar 2005 15:23:41 -0800 (PST)
Message-Id: <4.3.2.7.2.20050322151346.029d1200@mira-sjcm-2.cisco.com>
X-Sender: kleung@mira-sjcm-2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 22 Mar 2005 15:23:41 -0800
To: Rajeev Koodli <rajeev@iprg.nokia.com>
From: Kent Leung <kleung@cisco.com>
Subject: Re: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4
In-Reply-To: <4240A1A1.70309@iprg.nokia.com>
References: <4.3.2.7.2.20050322134204.028b3e18@mira-sjcm-2.cisco.com>
	<4.3.2.7.2.20050322134204.028b3e18@mira-sjcm-2.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: "Soliman, Hesham" <H.Soliman@flarion.com>, mip4@ietf.org,
        Henrik Levkowetz <henrik@levkowetz.com>,
        "Karim El-Malki \(AL/EAB\)" <karim.el-malki@ericsson.com>
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3

Hi Rajeev.

My personal take on this is that the early agent discovery is unnecessary
in the overall latency.  The return on investment of the new messaging and
operation is minimal.  I think having the agent advertisement sent by the
new FA after access authorization will provide fast handover.  The time for
MN to learn about FA can be sub-msec range.  With PFANE and BU/BA,
the packets in transit are no lost during registration period to acheive
the smooth handover.  It is my opinion that we can achieve good optimization
with some basic messages and extension, without adding much complexity
to the mobility agents.

Kent

At 02:52 PM 3/22/2005 -0800, Rajeev Koodli wrote:

>Hi Kent,
>
>
>Kent Leung wrote:
>
>>KL> PFANE is good to have.  Also the BU and BAck messages to
>>set up tunnel between FAs is good.  As I said before, I'm keen to
>>keep the solution in line of MIPv4 (FMIPv4 on FAs only).
>FMIPv4 has the PFANE-type reactive handover; it is also better because
>movement detection and agent discovery delays are effectively eliminated
>due to performing neighborhood discovery (out of handover critical timing)
>on the previous link.
>
>Regards,
>
>-Rajeev
>
>>Kent
>>
>>--
>>      |           |                   Kent Leung
>>     :|:         :|:                  IP Mobility Development
>>    :|||:       :|||:                 Internet Technologies Division
>>   :|||||||:   :|||||||:              Voice: 408.526.5030
>>.:|||||||||:.:|||||||||:.             Fax:   408.525.1653
>>  c i s c o S y s t e m s             Email: kleung@cisco.com

--
      |           |                   Kent Leung
     :|:         :|:                  IP Mobility Development
    :|||:       :|||:                 Internet Technologies Division
   :|||||||:   :|||||||:              Voice: 408.526.5030
.:|||||||||:.:|||||||||:.             Fax:   408.525.1653
  c i s c o S y s t e m s             Email: kleung@cisco.com

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


From mip4-bounces@ietf.org  Tue Mar 22 18:39:03 2005
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 SAA21522
	for <mip4-web-archive@ietf.org>; Tue, 22 Mar 2005 18:39:03 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DDt38-000357-Nr
	for mip4-web-archive@ietf.org; Tue, 22 Mar 2005 18:44:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DDsvX-00011V-6j; Tue, 22 Mar 2005 18:36:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DDsvV-00011K-90
	for mip4@megatron.ietf.org; Tue, 22 Mar 2005 18:36:45 -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 SAA21351
	for <mip4@ietf.org>; Tue, 22 Mar 2005 18:36:42 -0500 (EST)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDt0q-000320-GK
	for mip4@ietf.org; Tue, 22 Mar 2005 18:42:18 -0500
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j2N05UM15805;
	Tue, 22 Mar 2005 16:05:30 -0800
X-mProtect: <200503230005> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp141138.americas.nokia.com (172.18.141.138,
	claiming to be "[172.18.141.138]")
	by darkstar.iprg.nokia.com smtpdM9UkTE; Tue, 22 Mar 2005 16:05:29 PST
Message-ID: <4240AACB.70605@iprg.nokia.com>
Date: Tue, 22 Mar 2005 15:31:23 -0800
From: Charlie P <charliep@iprg.nokia.com>
Organization: NOKIA
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.1) Gecko/20040707
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Kent Leung <kleung@cisco.com>
Subject: Re: [Mip4] RE: Differences between Low Latency Handovers and FMIP v4
References: <4.3.2.7.2.20050322134204.028b3e18@mira-sjcm-2.cisco.com>	<4.3.2.7.2.20050322134204.028b3e18@mira-sjcm-2.cisco.com>
	<4.3.2.7.2.20050322151346.029d1200@mira-sjcm-2.cisco.com>
In-Reply-To: <4.3.2.7.2.20050322151346.029d1200@mira-sjcm-2.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: 7bit


Hello Kent,

Kent Leung wrote:

>
> My personal take on this is that the early agent discovery is unnecessary
> in the overall latency.  The return on investment of the new messaging 
> and
> operation is minimal.  I think having the agent advertisement sent by the
> new FA after access authorization will provide fast handover.  The 
> time for
> MN to learn about FA can be sub-msec range.

This would be a specification written for very particular systems that
had the hardware characteristics you see.  Other people have been
persuaded that the only possible solution was make-before-break.
I am much in favor of a more widely applicable layer-3 solution,
particularly because it enables better performance in systems with
multiple physical media available for Internet connectivity.


>   With PFANE and BU/BA,
> the packets in transit are no lost during registration period to acheive
> the smooth handover.

I don't think this is correct.  But I will agree that the motivation for
PFANE was to minimize packet loss (and of course eliminate if it
happens to be a good day).

>   It is my opinion that we can achieve good optimization
> with some basic messages and extension, without adding much complexity
> to the mobility agents.

We should structure the solution so that, in the case you envision,
the minimal implementation is enabled by the specification.

Regards,
Charlie P.

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


From mip4-bounces@ietf.org  Wed Mar 23 20:09:09 2005
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 UAA16448
	for <mip4-web-archive@ietf.org>; Wed, 23 Mar 2005 20:09:09 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DEGw6-0006RK-HU
	for mip4-web-archive@ietf.org; Wed, 23 Mar 2005 20:14:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DEGni-0000xV-TK; Wed, 23 Mar 2005 20:06:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DEGnh-0000xQ-20
	for mip4@megatron.ietf.org; Wed, 23 Mar 2005 20:06:17 -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 UAA16251
	for <mip4@ietf.org>; Wed, 23 Mar 2005 20:06:13 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DEGtF-0006M6-VT
	for mip4@ietf.org; Wed, 23 Mar 2005 20:12:03 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-2.cisco.com with ESMTP; 23 Mar 2005 17:06:07 -0800
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j2O164ZV021146;
	Wed, 23 Mar 2005 17:06:04 -0800 (PST)
Received: from kleung-w2k01.cisco.com (dhcp-128-107-163-171.cisco.com
	[128.107.163.171]) by mira-sjc5-b.cisco.com (MOS 3.4.5-GR)
	with ESMTP id BDG13563; Wed, 23 Mar 2005 17:06:01 -0800 (PST)
Message-Id: <4.3.2.7.2.20050323141202.0246aa88@mira-sjcm-2.cisco.com>
X-Sender: kleung@mira-sjcm-2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 23 Mar 2005 17:06:00 -0800
To: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
From: Kent Leung <kleung@cisco.com>
Subject: Re: [Mip4] draft on RADIUS support for Mobile IP
In-Reply-To: <EBF631554F9CD7118D0B00065BF34DCB09EA1812@il27exm03.cig.mot .com>
Mime-Version: 1.0
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 7a3b79fd9d7bf2ef1762376a62c51ec4
Cc: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>,
        "'kchowdhury@starentnetworks.com'" <kchowdhury@starentnetworks.com>,
        "'mip4@ietf.org'" <mip4@ietf.org>,
        "'avi@bridgewatersystems.com'" <avi@bridgewatersystems.com>
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>
Content-Type: multipart/mixed; boundary="===============1715789292=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 8bebc843ecf489bb7d907f63ccb001af

--===============1715789292==
Content-Type: multipart/alternative;
	boundary="=====================_114732086==_.ALT"

--=====================_114732086==_.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

Hi Madjid et al.,

The draft looks pretty good overall.  Some comments.

1) Please reference draft-ietf-mobileip-rfc3012bis-06.txt in document.

2) Since the User-Name AVP will be populated with MN-NAI or MN-HoA,
     why are the MIP-MN-NAI and MIP-MN-HoA AVPs needed?  If all AVPs
     are supported, then how is the combination of them prioritized for
     user lookup?

3) For CCoA mode Authenticator calculation, refer to 3012bis.  The Challenge
     is non-zero.  The MFCE is part of the RRQ sent from MN to HA.

4) In 3.1 HA process RRQ section, since the NAS-IP and HA-IP addresses
     may be different, shouldn't the MIP-HA-IP address or MIP-HA-NAI always
     be included in the Access-Req?  The NAS-IP and the RADIUS server have
     a shared secret to protect communication between them
     (Message-Authenticator).  The MIP-HA identifier serves a different
     function (e.g. possibly tag for HoA assignment).

5) General comments for clarity on labels.  XXX-REP to XXX-REPLAY,
     XXX-LIFE to XXX-LIFETIME, XXX-ALGID to XXX-ALGORID.

6) Typo in "The HA receives the RADIUS Access Accept" bullet.  Remove
     "using and MN to HA MSAs".

7) Same 3.1 section, "The MN extracts" bullet, specify how the MN-HA key
     is derived (or reference [MIPKEYS]).

8) Figure 2a, label 1, 2, 3, etc. on the flow would be useful.

9) Sect 3.2 "The FA checks" bullet, missing ")" for MIP-FA-IP 
address.  Same issue
     with NAS-IP and MIP-FA-IP address as above.  Should have FA-IP identifier
     (either MIP-FA-IP-address or MIP-FA-NAI) in case HA in foreign network
     assignment happens.  Also, why is the MIP-FA-NAI  added only if HA 
address is
     all 1s or 0s?  The value of MIP-HA-IP-address can be set to HA field 
in RRQ.

10) "The AAAH compares this value" bullet, I think having a new MIP-FA-HA-nonce
      is good to associate the 2 Access-Requests (one from FA, and other 
from HA)
      to set up the FA-HA MSA.  Also, the MIP-MN-FA-nonce is missing in the 
list for
      Access-Request.

11) "The FA retrieves the MN-FA key" bullet, typo "Access-Request" should be
       "Access-Accept".

12) "Upon receiving the reg" bullet, same issue with NAS-IP and MIP-HA 
identifier.
      Also, why are MIP-FA-to-HA-SPI and MIP-FA-HA-Authenticator AVPs included?
      See my opinion below.  May also want to have MIP-MN-FA-NAI as the FA
      identifier to index the MSA.  Another point to capture is the case 
when the
      FA-HA MSA exists (e.g. created by another MN which registered previously
      between the FA and HA).  Then the HA just authenticate the FHAE first
      before sending Access-Request to AAA server.

13) "The AAAH finds the FA-HA MSA" bullet, I think AAA should only be
      responsible to authenticate the MN and provide the keys to the HA, which
      is responsible to authenticate FHAE and MHAE (if there).  So AAA server
      should authenticate MN using the MIP-MN-AAA-SPI and
      MIP-MN-AAA-Authenticator.  Also, if the AAA server receives the 
MIP-FA-HA-nonce,
      it can find the right FA-HA MSA to provide to HA.

14) Same bullet as above, why does the Access-Accept include the MIP-MN-FA-XXX
       AVPs?  These were already delivered to the FA in the RADIUS exchange 
between
       FA and AAAF.

15) "The HA retreives the key materials" bullet, I don't think HA should be 
putting
       MN-FA-nonce.  HA should only put the MN-HA-nonce in the KeyGenReplyExt
       protected by MHAE.

16) "The FA relays the RRP" bullet, I think the FA should put the 
MN-FA-nonce in
       the appended KeyGenReplyExt protected by MFAE before sending to MN.

17) Sect 4.2, "the HA and FA may send their own IP addresses inside NAS-IP
       instead of MIP-[HA|FA]-IP-address".  I think the MIP-[HA|FA] 
identifiers should
       always be in the Access Req.

18) Sect 5, MIP-HA-IP address, why "the FA this attribute MAY not be used in
       the Access-Request"?  The HA address could be helpful to for setting 
up FA-HA
       MSA.

19) MIP-MN-AAA-SPI, String should be unsigned32 and Length should be 6.

20) Mobile IPv4 feature vector, if mapping to DIAMETER, then this should be 
unsigned32.
      The "8-bit flag vector" should be called "bitflag vector" as current 
allocation is already
      over 8 bits.  :)  Length would be 6.

21) Why bit 8 Foreign-Home-Agent-Available not supported?  This could be set by
       FA to notify to AAAH that AAAL can assign the HA when relaying the 
Access-Accept.
       I'm not clear on usage of bit 2 
Home-Address-Allocatable-Only-in-Home-Realm.
       Also, I'm not sure why we don't have bitflag to indicate if the 
Access-Request is
       sent by FA or HA?  That might clarify some operations on the AAA server?
       Let's say the Access-Request contains the NAS-IP for authentication 
between NAS
       and AAA server and FA and HA identifiers to set up MSA, shouldn't 
AAA need to
       know which is FA or HA to set up the directional SPI for MSA?

22) MIP-MN-to-HA SPI and MIP-HA-to-MN-SPI , String should be unsigned32 and 
length is 6.

23) MIP-MN-HA-ALGID, not clear how algorithm identifier is mapped?  We have 
keyed MD5
       and HMAC-MD5.  Having a string doesn't make sense.  Maybe unsigned8 
and specify
       1 for keyed MD5 and 2 for HMAC-MD5?

24) MIP-MN-HA-REP, same issue with string.  Maybe unsigned8 and specifiy 1 for
       timestamp (with field for replay range) and 2 for nonce?

25) MIP-MN-HA-MSA-LIFE, integer should be unsigned32 and length is 
6.  Should we
      allow 0xFFFFFFFF to mean infinite lifetime for MSA?  This means the 
MSA remains
      for lifetime of one registration session (MSA deleted when 
registration ends).

26) Remove bunch of AVPs above the format of FA to HA SPI.

27) FA to HA SPI and HA to FA SPI, string is unsigned32 and length is 6.

28) Would like to add new MIP-FA-HA-nonce AVP.

29) In 5.1, attribute list is missing MIP-FA-NAI, MIP-MN-HA SPI and 
MIP-HA-to-MN-SPI
       should change "HA" to "FA" before "Encrypted", missing 
Encrypted[MIP-MN-FA-key],
       new MIP-FA-HA-nonce, duplicate MIP-MN-HA-MSA-LIFE.

30) Sect 8, "We recommend that the AAAH also authenticates the nonce reply
      extensions with the AAA SA it shares with the MN".  This is for MITM 
attack for
      msg from AAAH to HA/FA.  Doesn't the Message-Authenticator protect 
tampering
      with the nonce value?

Kent

At 06:56 PM 2/7/2005 -0600, Nakhjiri Madjid-MNAKHJI1 wrote:

>Hi folks,
>
>
>
>Just wanted to let you know that we just submitted a draft proposing an 
>specification for support of RADIUS for Mobile IP key management 
>procedures. The draft goes through two cases of co-located mobile nodes 
>and nodes behind an FA and describes RADIUS messaging and attributes for 
>each case. Since the draft deals with both Mobile IPv4 and RADIUS, it 
>needs to be examined by both groups. We know that this is really more an 
>extension to RADIUS than to Mobile IP and should be standardized by RADIUS 
>groups, but we would like to make sure that we got the Mobile IP parts 
>right first J.
>
>
>
>So comments and guidance are very welcome.
>
>
>
>Thanks and Regards,
>
>
>
>Madjid Nakhjiri, Kuntal Chowdhury, Avi Lior
>
>
>
>
>
>The draft can be found at
>
>
>
><http://www.ietf.org/internet-drafts/draft-nakhjiri-radius-mip4-00.txt>http://www.ietf.org/internet-drafts/draft-nakhjiri-radius-mip4-00.txt
>
>
>
>
>
>Abstract
>
>
>
>    Mobile IPv4 specifies mechanisms that need assistance from a AAA
>
>    server and a AAA infrastructure. Examples of such mechanisms are
>
>    those providing key management and authentication services during a
>
>    mobile node's registration process with MN-AAA authentication
>
>    extension. Although Diameter Mobile IP application is being specified
>
>    to support the needs of Mobile IPv4 from the AAA infrastructure's
>
>    point of view, such support does not exist within RADIUS framework.
>
>    This document defines the RADIUS attributes that provide support for
>
>    Mobile IPv4 operation.
>
>
>
>
>--
>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/

--
      |           |                   Kent Leung
     :|:         :|:                  IP Mobility Development
    :|||:       :|||:                 Internet Technologies Division
   :|||||||:   :|||||||:              Voice: 408.526.5030
.:|||||||||:.:|||||||||:.             Fax:   408.525.1653
  c i s c o S y s t e m s             Email: kleung@cisco.com 
--=====================_114732086==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
Hi Madjid et al.,<br>
<br>
The draft looks pretty good overall.&nbsp; Some comments.<br>
<br>
1) Please reference draft-ietf-mobileip-rfc3012bis-06.txt in
document.<br>
<br>
2) Since the User-Name AVP will be populated with MN-NAI or MN-HoA,<br>
&nbsp;&nbsp;&nbsp; why are the MIP-MN-NAI and MIP-MN-HoA AVPs
needed?&nbsp; If all AVPs<br>
&nbsp;&nbsp;&nbsp; are supported, then how is the combination of them
prioritized for<br>
&nbsp;&nbsp;&nbsp; user lookup?<br>
<br>
3) For CCoA mode Authenticator calculation, refer to 3012bis.&nbsp; The
Challenge<br>
&nbsp;&nbsp;&nbsp; is non-zero.&nbsp; The MFCE is part of the RRQ sent
from MN to HA.<br>
<br>
4) In 3.1 HA process RRQ section, since the NAS-IP and HA-IP addresses
<br>
&nbsp;&nbsp;&nbsp; may be different, shouldn't the MIP-HA-IP address or
MIP-HA-NAI always <br>
&nbsp;&nbsp;&nbsp; be included in the Access-Req?&nbsp; The NAS-IP and
the RADIUS server have<br>
&nbsp;&nbsp;&nbsp; a shared secret to protect communication between them
<br>
&nbsp;&nbsp;&nbsp; (Message-Authenticator).&nbsp; The MIP-HA identifier
serves a different<br>
&nbsp;&nbsp;&nbsp; function (e.g. possibly tag for HoA assignment).<br>
<br>
5) General comments for clarity on labels.&nbsp; XXX-REP to XXX-REPLAY,
<br>
&nbsp;&nbsp;&nbsp; XXX-LIFE to XXX-LIFETIME, XXX-ALGID to
XXX-ALGORID.<br>
&nbsp;&nbsp;&nbsp; <br>
6) Typo in &quot;The HA receives the RADIUS Access Accept&quot;
bullet.&nbsp; Remove<br>
&nbsp;&nbsp;&nbsp; &quot;using and MN to HA MSAs&quot;.<br>
<br>
7) Same 3.1 section, &quot;The MN extracts&quot; bullet, specify how the
MN-HA key<br>
&nbsp;&nbsp;&nbsp; is derived (or reference [MIPKEYS]).<br>
<br>
8) Figure 2a, label 1, 2, 3, etc. on the flow would be useful.<br>
<br>
9) Sect 3.2 &quot;The FA checks&quot; bullet, missing &quot;)&quot; for
MIP-FA-IP address.&nbsp; Same issue<br>
&nbsp;&nbsp;&nbsp; with NAS-IP and MIP-FA-IP address as above.&nbsp;
Should have FA-IP identifier<br>
&nbsp;&nbsp;&nbsp; (either MIP-FA-IP-address or MIP-FA-NAI) in case HA in
foreign network <br>
&nbsp;&nbsp;&nbsp; assignment happens.&nbsp; Also, why is the
MIP-FA-NAI&nbsp; added only if HA address is <br>
&nbsp;&nbsp;&nbsp; all 1s or 0s?&nbsp; The value of MIP-HA-IP-address can
be set to HA field in RRQ.<br>
<br>
10) &quot;The AAAH compares this value&quot; bullet, I think having a new
MIP-FA-HA-nonce<br>
&nbsp;&nbsp;&nbsp;&nbsp; is good to associate the 2 Access-Requests (one
from FA, and other from HA)<br>
&nbsp;&nbsp;&nbsp;&nbsp; to set up the FA-HA MSA.&nbsp; Also, the
MIP-MN-FA-nonce is missing in the list for<br>
&nbsp;&nbsp;&nbsp;&nbsp; Access-Request.<br>
<br>
11) &quot;The FA retrieves the MN-FA key&quot; bullet, typo
&quot;Access-Request&quot; should be<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;Access-Accept&quot;.<br>
<br>
12) &quot;Upon receiving the reg&quot; bullet, same issue with NAS-IP and
MIP-HA identifier.<br>
&nbsp;&nbsp;&nbsp;&nbsp; Also, why are MIP-FA-to-HA-SPI and
MIP-FA-HA-Authenticator AVPs included?<br>
&nbsp;&nbsp;&nbsp;&nbsp; See my opinion below.&nbsp; May also want to
have MIP-MN-FA-NAI as the FA<br>
&nbsp;&nbsp;&nbsp;&nbsp; identifier to index the MSA.&nbsp; Another point
to capture is the case when the<br>
&nbsp;&nbsp;&nbsp;&nbsp; FA-HA MSA exists (e.g. created by another MN
which registered previously<br>
&nbsp;&nbsp;&nbsp;&nbsp; between the FA and HA).&nbsp; Then the HA just
authenticate the FHAE first<br>
&nbsp;&nbsp;&nbsp;&nbsp; before sending Access-Request to AAA
server.<br>
<br>
13) &quot;The AAAH finds the FA-HA MSA&quot; bullet, I think AAA should
only be<br>
&nbsp;&nbsp;&nbsp;&nbsp; responsible to authenticate the MN and provide
the keys to the HA, which<br>
&nbsp;&nbsp;&nbsp;&nbsp; is responsible to authenticate FHAE and MHAE (if
there).&nbsp; So AAA server<br>
&nbsp;&nbsp;&nbsp;&nbsp; should authenticate MN using the MIP-MN-AAA-SPI
and <br>
&nbsp;&nbsp;&nbsp;&nbsp; MIP-MN-AAA-Authenticator.&nbsp; Also, if the AAA
server receives the MIP-FA-HA-nonce,<br>
&nbsp;&nbsp;&nbsp;&nbsp; it can find the right FA-HA MSA to provide to
HA.&nbsp; <br>
<br>
14) Same bullet as above, why does the Access-Accept include the
MIP-MN-FA-XXX<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AVPs?&nbsp; These were already delivered
to the FA in the RADIUS exchange between<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FA and AAAF.<br>
<br>
15) &quot;The HA retreives the key materials&quot; bullet, I don't think
HA should be putting<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MN-FA-nonce.&nbsp; HA should only put the
MN-HA-nonce in the KeyGenReplyExt<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; protected by MHAE.<br>
<br>
16) &quot;The FA relays the RRP&quot; bullet, I think the FA should put
the MN-FA-nonce in<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the appended KeyGenReplyExt protected by
MFAE before sending to MN.<br>
<br>
17) Sect 4.2, &quot;the HA and FA may send their own IP addresses inside
NAS-IP<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; instead of
MIP-[HA|FA]-IP-address&quot;.&nbsp; I think the MIP-[HA|FA] identifiers
should<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; always be in the Access Req.<br>
<br>
18) Sect 5, MIP-HA-IP address, why &quot;the FA this attribute MAY not be
used in<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the Access-Request&quot;?&nbsp; The HA
address could be helpful to for setting up FA-HA<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MSA.<br>
<br>
19) MIP-MN-AAA-SPI, String should be unsigned32 and Length should be
6.<br>
<br>
20) Mobile IPv4 feature vector, if mapping to DIAMETER, then this should
be unsigned32.<br>
&nbsp;&nbsp;&nbsp;&nbsp; The &quot;8-bit flag vector&quot; should be
called &quot;bitflag vector&quot; as current allocation is already<br>
&nbsp;&nbsp;&nbsp;&nbsp; over 8 bits.&nbsp; :)&nbsp; Length would be
6.&nbsp; <br>
<br>
21) Why bit 8 Foreign-Home-Agent-Available not supported?&nbsp; This
could be set by<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FA to notify to AAAH that AAAL can assign
the HA when relaying the Access-Accept.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I'm not clear on usage of bit 2
Home-Address-Allocatable-Only-in-Home-Realm.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Also, I'm not sure why we don't have
bitflag to indicate if the Access-Request is<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; sent by FA or HA?&nbsp; That might clarify
some operations on the AAA server?<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Let's say the Access-Request contains the
NAS-IP for authentication between NAS<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and AAA server and FA and HA identifiers
to set up MSA, shouldn't AAA need to<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; know which is FA or HA to set up the
directional SPI for MSA?<br>
<br>
22) MIP-MN-to-HA SPI and MIP-HA-to-MN-SPI , String should be unsigned32
and length is 6.<br>
<br>
23) MIP-MN-HA-ALGID, not clear how algorithm identifier is mapped?&nbsp;
We have keyed MD5<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and HMAC-MD5.&nbsp; Having a string
doesn't make sense.&nbsp; Maybe unsigned8 and specify<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1 for keyed MD5 and 2 for HMAC-MD5?<br>
<br>
24) MIP-MN-HA-REP, same issue with string.&nbsp; Maybe unsigned8 and
specifiy 1 for<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; timestamp (with field for replay range)
and 2 for nonce?<br>
<br>
25) MIP-MN-HA-MSA-LIFE, integer should be unsigned32 and length is
6.&nbsp; Should we<br>
&nbsp;&nbsp;&nbsp;&nbsp; allow 0xFFFFFFFF to mean infinite lifetime for
MSA?&nbsp; This means the MSA remains<br>
&nbsp;&nbsp;&nbsp;&nbsp; for lifetime of one registration session (MSA
deleted when registration ends).<br>
<br>
26) Remove bunch of AVPs above the format of FA to HA SPI.<br>
<br>
27) FA to HA SPI and HA to FA SPI, string is unsigned32 and length is
6.<br>
<br>
28) Would like to add new MIP-FA-HA-nonce AVP.<br>
<br>
29) In 5.1, attribute list is missing MIP-FA-NAI, MIP-MN-HA SPI and
MIP-HA-to-MN-SPI<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; should change &quot;HA&quot; to
&quot;FA&quot; before &quot;Encrypted&quot;, missing
Encrypted[MIP-MN-FA-key],<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; new MIP-FA-HA-nonce, duplicate
MIP-MN-HA-MSA-LIFE.<br>
<br>
30) Sect 8, &quot;We recommend that the AAAH also authenticates the nonce
reply<br>
&nbsp;&nbsp;&nbsp;&nbsp; extensions with the AAA SA it shares with the
MN&quot;.&nbsp; This is for MITM attack for<br>
&nbsp;&nbsp;&nbsp;&nbsp; msg from AAAH to HA/FA.&nbsp; Doesn't the
Message-Authenticator protect tampering<br>
&nbsp;&nbsp;&nbsp;&nbsp; with the nonce value?<br>
<br>
Kent<br>
<br>
At 06:56 PM 2/7/2005 -0600, Nakhjiri Madjid-MNAKHJI1 wrote:<br>
<br>
<blockquote type=cite cite><font face="arial" size=2>Hi folks,<br>
</font><br>
<font face="arial" size=2>&nbsp;<br>
</font><br>
<font face="arial" size=2>Just wanted to let you know that we just
submitted a draft proposing an specification for support of RADIUS for
Mobile IP key management procedures. The draft goes through two cases of
co-located mobile nodes and nodes behind an FA and describes RADIUS
messaging and attributes for each case. Since the draft deals with both
Mobile IPv4 and RADIUS, it needs to be examined by both groups. We know
that this is really more an extension to RADIUS than to Mobile IP and
should be standardized by RADIUS groups, but we would like to make sure
that we got the Mobile IP parts right first
</font><font face="wingdings" size=2>J</font><font face="arial" size=2>.<br>
</font><br>
<font face="arial" size=2>&nbsp;<br>
</font><br>
<font face="arial" size=2>So comments and guidance are very 
welcome.<br>
</font><br>
<font face="arial" size=2>&nbsp;<br>
</font><br>
<font face="arial" size=2>Thanks and Regards,<br>
</font><br>
<font face="arial" size=2>&nbsp;<br>
</font><br>
<font face="arial" size=2>Madjid Nakhjiri, Kuntal Chowdhury, Avi
Lior<br>
</font><br>
<font face="arial" size=2>&nbsp;<br>
</font><br>
<font face="arial" size=2>&nbsp;<br>
</font><br>
<font face="arial" size=2>The draft can be found at <br>
</font><br>
<font face="arial" size=2>&nbsp;<br>
</font><br>
<font face="arial" size=2><a href="http://www.ietf.org/internet-drafts/draft-nakhjiri-radius-mip4-00.txt">http://www.ietf.org/internet-drafts/draft-nakhjiri-radius-mip4-00.txt</a><br>
</font><br>
<font face="arial" size=2>&nbsp;<br>
</font><br>
<font face="Courier New, Courier" size=2>&nbsp;&nbsp;&nbsp; <br>
</font><br>
<font face="Courier New, Courier" size=2>Abstract <br>
</font><br>
<font face="Courier New, Courier" size=2>&nbsp;&nbsp;&nbsp; <br>
</font><br>
<font face="Courier New, Courier" size=2>&nbsp;&nbsp; Mobile IPv4
specifies mechanisms that need assistance from a AAA <br>
</font><br>
<font face="Courier New, Courier" size=2>&nbsp;&nbsp; server and a AAA
infrastructure. Examples of such mechanisms are <br>
</font><br>
<font face="Courier New, Courier" size=2>&nbsp;&nbsp; those providing key
management and authentication services during a <br>
</font><br>
<font face="Courier New, Courier" size=2>&nbsp;&nbsp; mobile node's
registration process with MN-AAA authentication <br>
</font><br>
<font face="Courier New, Courier" size=2>&nbsp;&nbsp; extension. Although
Diameter Mobile IP application is being specified <br>
</font><br>
<font face="Courier New, Courier" size=2>&nbsp;&nbsp; to support the
needs of Mobile IPv4 from the AAA infrastructure's <br>
</font><br>
<font face="Courier New, Courier" size=2>&nbsp;&nbsp; point of view, such
support does not exist within RADIUS framework. <br>
</font><br>
<font face="Courier New, Courier" size=2>&nbsp;&nbsp; This document
defines the RADIUS attributes that provide support for <br>
</font><br>
<font face="Courier New, Courier" size=2>&nbsp;&nbsp; Mobile IPv4
operation. <br>
</font><br>
<font face="arial" size=2>&nbsp;<br>
</font><br>
<font face="arial" size=2>&nbsp;<br>
</font>-- <br>
Mip4 mailing list: Mip4@ietf.org<br>
&nbsp;&nbsp;&nbsp; Web interface:
<a href="https://www1.ietf.org/mailman/listinfo/mip4" eudora="autourl">https://www1.ietf.org/mailman/listinfo/mip4</a><br>
&nbsp;&nbsp;&nbsp;&nbsp; Charter page:
<a href="http://www.ietf.org/html.charters/mip4-charter.html" eudora="autourl">http://www.ietf.org/html.charters/mip4-charter.html</a><br>
Supplemental site:
<a href="http://www.mip4.org/" eudora="autourl">http://www.mip4.org/</a></blockquote><br>
<div>--</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Kent Leung</div>
<div>&nbsp;&nbsp;&nbsp;
:|:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
:|:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
IP Mobility Development</div>
<div>&nbsp;&nbsp; :|||:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
:|||:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Internet Technologies Division</div>
<div>&nbsp; :|||||||:&nbsp;&nbsp;
:|||||||:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Voice: 408.526.5030</div>
<div>.:|||||||||:.:|||||||||:.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Fax:&nbsp;&nbsp; 408.525.1653</div>
&nbsp;c i s c o S y s t e m
s&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Email: kleung@cisco.com
</html>

--=====================_114732086==_.ALT--


--===============1715789292==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1715789292==--



From mip4-bounces@ietf.org  Sat Mar 26 11:25:06 2005
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 LAA09039
	for <mip4-web-archive@ietf.org>; Sat, 26 Mar 2005 11:25:06 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DFEC7-00034S-CS
	for mip4-web-archive@ietf.org; Sat, 26 Mar 2005 11:31:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DFE5D-0008RR-UT; Sat, 26 Mar 2005 11:24:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DEWkM-00042b-5j
	for mip4@megatron.ietf.org; Thu, 24 Mar 2005 13:07:54 -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 NAA10359
	for <mip4@ietf.org>; Thu, 24 Mar 2005 13:07:51 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DEWq4-000402-Ty
	for mip4@ietf.org; Thu, 24 Mar 2005 13:13:49 -0500
Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id j2OI7Nm12391; Thu, 24 Mar 2005 13:07:23 -0500 (EST)
Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GH4X0AKB>; Thu, 24 Mar 2005 13:07:24 -0500
Message-ID: <E3F9D87C63E2774390FE67C924EC99BB07DB4E3B@zrc2hxm1.corp.nortel.com>
From: "Jayshree Bharatia" <jayshree@nortel.com>
To: "'Kent Leung'" <kleung@cisco.com>,
        "'Nakhjiri Madjid-MNAKHJI1'"
	<Madjid.Nakhjiri@motorola.com>
Subject: RE: [Mip4] draft on RADIUS support for Mobile IP
Date: Thu, 24 Mar 2005 13:07:13 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5bfa71b340354e384155def5e70b13b
X-Mailman-Approved-At: Sat, 26 Mar 2005 11:24:18 -0500
Cc: "'kchowdhury@starentnetworks.com'" <kchowdhury@starentnetworks.com>,
        "'mip4@ietf.org'" <mip4@ietf.org>,
        "'avi@bridgewatersystems.com'" <avi@bridgewatersystems.com>
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 83e9494d829b08cc3f644ef6ac1b9bd4

Hi Kent,

Regarding point 1 of your comments, this RADIUS draft can refer to the
latest version of RFC3012bis document (draft-ietf-mip4-rfc3012bis-03.txt). 

Regards,
Jayshree
-----Original Message-----
From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of Kent
Leung
Sent: Wednesday, March 23, 2005 7:06 PM
To: Nakhjiri Madjid-MNAKHJI1
Cc: Nakhjiri Madjid-MNAKHJI1; 'kchowdhury@starentnetworks.com';
'mip4@ietf.org'; 'avi@bridgewatersystems.com'
Subject: Re: [Mip4] draft on RADIUS support for Mobile IP


Hi Madjid et al.,

The draft looks pretty good overall.  Some comments.

1) Please reference draft-ietf-mobileip-rfc3012bis-06.txt in document.

2) Since the User-Name AVP will be populated with MN-NAI or MN-HoA,
    why are the MIP-MN-NAI and MIP-MN-HoA AVPs needed?  If all AVPs
    are supported, then how is the combination of them prioritized for
    user lookup?

3) For CCoA mode Authenticator calculation, refer to 3012bis.  The Challenge
    is non-zero.  The MFCE is part of the RRQ sent from MN to HA.

4) In 3.1 HA process RRQ section, since the NAS-IP and HA-IP addresses 
    may be different, shouldn't the MIP-HA-IP address or MIP-HA-NAI always 
    be included in the Access-Req?  The NAS-IP and the RADIUS server have
    a shared secret to protect communication between them 
    (Message-Authenticator).  The MIP-HA identifier serves a different
    function (e.g. possibly tag for HoA assignment).

5) General comments for clarity on labels.  XXX-REP to XXX-REPLAY, 
    XXX-LIFE to XXX-LIFETIME, XXX-ALGID to XXX-ALGORID.
    
6) Typo in "The HA receives the RADIUS Access Accept" bullet.  Remove
    "using and MN to HA MSAs".

7) Same 3.1 section, "The MN extracts" bullet, specify how the MN-HA key
    is derived (or reference [MIPKEYS]).

8) Figure 2a, label 1, 2, 3, etc. on the flow would be useful.

9) Sect 3.2 "The FA checks" bullet, missing ")" for MIP-FA-IP address.  Same
issue
    with NAS-IP and MIP-FA-IP address as above.  Should have FA-IP
identifier
    (either MIP-FA-IP-address or MIP-FA-NAI) in case HA in foreign network 
    assignment happens.  Also, why is the MIP-FA-NAI  added only if HA
address is 
    all 1s or 0s?  The value of MIP-HA-IP-address can be set to HA field in
RRQ.

10) "The AAAH compares this value" bullet, I think having a new
MIP-FA-HA-nonce
     is good to associate the 2 Access-Requests (one from FA, and other from
HA)
     to set up the FA-HA MSA.  Also, the MIP-MN-FA-nonce is missing in the
list for
     Access-Request.

11) "The FA retrieves the MN-FA key" bullet, typo "Access-Request" should be
      "Access-Accept".

12) "Upon receiving the reg" bullet, same issue with NAS-IP and MIP-HA
identifier.
     Also, why are MIP-FA-to-HA-SPI and MIP-FA-HA-Authenticator AVPs
included?
     See my opinion below.  May also want to have MIP-MN-FA-NAI as the FA
     identifier to index the MSA.  Another point to capture is the case when
the
     FA-HA MSA exists (e.g. created by another MN which registered
previously
     between the FA and HA).  Then the HA just authenticate the FHAE first
     before sending Access-Request to AAA server.

13) "The AAAH finds the FA-HA MSA" bullet, I think AAA should only be
     responsible to authenticate the MN and provide the keys to the HA,
which
     is responsible to authenticate FHAE and MHAE (if there).  So AAA server
     should authenticate MN using the MIP-MN-AAA-SPI and 
     MIP-MN-AAA-Authenticator.  Also, if the AAA server receives the
MIP-FA-HA-nonce,
     it can find the right FA-HA MSA to provide to HA.  

14) Same bullet as above, why does the Access-Accept include the
MIP-MN-FA-XXX
      AVPs?  These were already delivered to the FA in the RADIUS exchange
between
      FA and AAAF.

15) "The HA retreives the key materials" bullet, I don't think HA should be
putting
      MN-FA-nonce.  HA should only put the MN-HA-nonce in the KeyGenReplyExt
      protected by MHAE.

16) "The FA relays the RRP" bullet, I think the FA should put the
MN-FA-nonce in
      the appended KeyGenReplyExt protected by MFAE before sending to MN.

17) Sect 4.2, "the HA and FA may send their own IP addresses inside NAS-IP
      instead of MIP-[HA|FA]-IP-address".  I think the MIP-[HA|FA]
identifiers should
      always be in the Access Req.

18) Sect 5, MIP-HA-IP address, why "the FA this attribute MAY not be used in
      the Access-Request"?  The HA address could be helpful to for setting
up FA-HA
      MSA.

19) MIP-MN-AAA-SPI, String should be unsigned32 and Length should be 6.

20) Mobile IPv4 feature vector, if mapping to DIAMETER, then this should be
unsigned32.
     The "8-bit flag vector" should be called "bitflag vector" as current
allocation is already
     over 8 bits.  :)  Length would be 6.  

21) Why bit 8 Foreign-Home-Agent-Available not supported?  This could be set
by
      FA to notify to AAAH that AAAL can assign the HA when relaying the
Access-Accept.
      I'm not clear on usage of bit 2
Home-Address-Allocatable-Only-in-Home-Realm.
      Also, I'm not sure why we don't have bitflag to indicate if the
Access-Request is
      sent by FA or HA?  That might clarify some operations on the AAA
server?
      Let's say the Access-Request contains the NAS-IP for authentication
between NAS
      and AAA server and FA and HA identifiers to set up MSA, shouldn't AAA
need to
      know which is FA or HA to set up the directional SPI for MSA?

22) MIP-MN-to-HA SPI and MIP-HA-to-MN-SPI , String should be unsigned32 and
length is 6.

23) MIP-MN-HA-ALGID, not clear how algorithm identifier is mapped?  We have
keyed MD5
      and HMAC-MD5.  Having a string doesn't make sense.  Maybe unsigned8
and specify
      1 for keyed MD5 and 2 for HMAC-MD5?

24) MIP-MN-HA-REP, same issue with string.  Maybe unsigned8 and specifiy 1
for
      timestamp (with field for replay range) and 2 for nonce?

25) MIP-MN-HA-MSA-LIFE, integer should be unsigned32 and length is 6.
Should we
     allow 0xFFFFFFFF to mean infinite lifetime for MSA?  This means the MSA
remains
     for lifetime of one registration session (MSA deleted when registration
ends).

26) Remove bunch of AVPs above the format of FA to HA SPI.

27) FA to HA SPI and HA to FA SPI, string is unsigned32 and length is 6.

28) Would like to add new MIP-FA-HA-nonce AVP.

29) In 5.1, attribute list is missing MIP-FA-NAI, MIP-MN-HA SPI and
MIP-HA-to-MN-SPI
      should change "HA" to "FA" before "Encrypted", missing
Encrypted[MIP-MN-FA-key],
      new MIP-FA-HA-nonce, duplicate MIP-MN-HA-MSA-LIFE.

30) Sect 8, "We recommend that the AAAH also authenticates the nonce reply
     extensions with the AAA SA it shares with the MN".  This is for MITM
attack for
     msg from AAAH to HA/FA.  Doesn't the Message-Authenticator protect
tampering
     with the nonce value?

Kent

At 06:56 PM 2/7/2005 -0600, Nakhjiri Madjid-MNAKHJI1 wrote:


Hi folks,

 

Just wanted to let you know that we just submitted a draft proposing an
specification for support of RADIUS for Mobile IP key management procedures.
The draft goes through two cases of co-located mobile nodes and nodes behind
an FA and describes RADIUS messaging and attributes for each case. Since the
draft deals with both Mobile IPv4 and RADIUS, it needs to be examined by
both groups. We know that this is really more an extension to RADIUS than to
Mobile IP and should be standardized by RADIUS groups, but we would like to
make sure that we got the Mobile IP parts right first J.

 

So comments and guidance are very welcome.

 

Thanks and Regards,

 

Madjid Nakhjiri, Kuntal Chowdhury, Avi Lior

 

 

The draft can be found at 

 

http://www.ietf.org/internet-drafts/draft-nakhjiri-radius-mip4-00.txt

 

    

Abstract 

    

   Mobile IPv4 specifies mechanisms that need assistance from a AAA 

   server and a AAA infrastructure. Examples of such mechanisms are 

   those providing key management and authentication services during a 

   mobile node's registration process with MN-AAA authentication 

   extension. Although Diameter Mobile IP application is being specified 

   to support the needs of Mobile IPv4 from the AAA infrastructure's 

   point of view, such support does not exist within RADIUS framework. 

   This document defines the RADIUS attributes that provide support for 

   Mobile IPv4 operation. 

 

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


--
     |           |                   Kent Leung
    :|:         :|:                  IP Mobility Development
   :|||:       :|||:                 Internet Technologies Division
  :|||||||:   :|||||||:              Voice: 408.526.5030
.:|||||||||:.:|||||||||:.             Fax:   408.525.1653
 c i s c o S y s t e m s             Email: kleung@cisco.com 

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


From mip4-bounces@ietf.org  Sat Mar 26 11:25:49 2005
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 LAA09220
	for <mip4-web-archive@ietf.org>; Sat, 26 Mar 2005 11:25:49 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DFECo-00035S-MZ
	for mip4-web-archive@ietf.org; Sat, 26 Mar 2005 11:32:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DFE5l-0008Te-9d; Sat, 26 Mar 2005 11:24:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DEmwv-0001Q9-2B
	for mip4@megatron.ietf.org; Fri, 25 Mar 2005 06:26:00 -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 GAA14895
	for <mip4@ietf.org>; Fri, 25 Mar 2005 06:25:52 -0500 (EST)
Received: from kronos.cti.gr ([150.140.1.25])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DEn2j-00044T-D6
	for mip4@ietf.org; Fri, 25 Mar 2005 06:31:59 -0500
Received: (qmail 50750 invoked from network); 25 Mar 2005 11:25:47 -0000
Received: from hermes.cti.gr (150.140.7.30)
	by kronos.cti.gr with SMTP; 25 Mar 2005 11:25:47 -0000
Received: (qmail 5935 invoked by uid 41021); 25 Mar 2005 11:23:17 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
	by localhost with SMTP; 25 Mar 2005 11:23:17 -0000
Date: Fri, 25 Mar 2005 13:23:17 +0200 (EET)
From: Ioannis Chatzigiannakis <ichatz@cti.gr>
To: THEORYNT@listserv.uic.edu, THEORYNT@listserv.nodak.edu,
        dmanet@zpr.uni-koeln.de, disc-announce@listes.epfl.ch, podc@acm.org,
        tccc@cs.columbia.edu, bahl@acm.org, manet@ietf.org,
        ans-research@ietf.org, lbs@lists.thinkburst.com,
        mobile-ip@sunroof.eng.sun.com, www-mobile@w3.org,
        nrg-list@eecs.umich.edu, netdev@nuclecu.unam.mx, davis@iastate.edu,
        t.moors@unsw.edu.au, sigcomm-members@acm.org,
        ukubinet-announce@doc.ic.ac.uk, ns-announce@isi.edu, MOBICOM@acm.org,
        SIGMOB@acm.org, fokus-user@fokus.fraunhofer.de, reres@laas.fr,
        manet@ietf.org, mip4@ietf.org
Message-ID: <Pine.GSO.4.60.0503251321001.5867@hermes.cti.gr>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d2b46e3b2dfbff2088e0b72a54104985
X-Mailman-Approved-At: Sat, 26 Mar 2005 11:24:49 -0500
Subject: [Mip4] CFP- 3rd IEEE MobiWac 2005
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0770535483960d190d4a0d020e7060bd

              Apologies if you receive multiple copies
-----------------------------------------------------------------------

                       3rd MobiWac 2005

                  IEEE International Workshop on
              Mobility Management and Wireless Access

              URL: http://www.cs.unibo.it/mobiwac2005

          To be held in conjunction with WIRELESSCOM 2005
   (International Conference on Wireless Networks, Communications,
                       and Mobile Computing)
                June 13-16, 2005, Maui, Hawaii, USA

------------------------------------------------------------------------
               Submission Deadline: April 5th, 2005.
------------------------------------------------------------------------

Following the success of MobiWac events in Forth Worth and Philadelphia,
the 3rd Workshop on Mobility Management and Wireless Access Protocols
(MobiWAC 2005) will be held in conjunction with WIRELESSCOM 2005 in
Maui, Hawaii, on June 13-16, 2005.

                               SCOPE


Wireless communications technology is enjoying its fastest growth period 
in history.  This unprecedented growth continues to affect the way that we 
live, work and play.  Yet solutions for mobile wireless access are still 
in the early stages of development. The MobiWAC workshop solicits papers 
from researchers and practitioners that address architectures, 
technologies and protocols for mobile computing and wireless access. 
Topics of particular interest include mobility and location management, 
ubiquitous and ad hoc access, awareness, mobile computational ambient 
agents, natural interaction and seamless access. The workshop will include 
contributed technical papers, invited papers, panel discussions and tools 
demonstrations. The proceedings will be published by IEEE CS-press.


                               TOPICS

Authors are encouraged to submit both theoretical and practical results of
significance on all aspects of wireless and mobile access technologies
with an emphasis on mobility management and wireless access.

The scope of this workshop includes, but is not limited, to:

- Wireless/Mobile Access Protocols
- Wireless Web Access
- Fault Tolerance in Wireless Access Networks
- Application development for embedded electronics and mobile devices
       (with J2ME, Wireless Devices, etc.)
- Wireless Multimedia Protocols
- Design and architecture of wireless communication and mobile computing
- Mobile service and QoS management
- Localization and tracking of mobile users
- Pervasive Computing
- Ubiquitous and mobile access
- Security, trust management and privacy issues
- Awareness-dependent wireless applications
- Interactive applications
- Context-awareness
- Wireless, ad hoc and sensor access devices.
- Wireless internet access technologies
- Mobile commerce technologies
- Analysis of correctness and efficiency of protocols
- Modeling of wireless devices and networks
- Innovative approaches to simulation
- Testbeds for experimental analysis
- Wireless Communication and Radio Management
- Mobile database management
- Channel and Ressource Allocation
- Energy and Power Management

                              SUBMISSIONS

Papers should be written in English and should not exceed 20 pages.
Papers must be unpublished and must not be submitted for publication
elsewhere.

Authors are encouraged to submit papers in postscript or pdf format.
Information for paper submission can be found on the MobiWac webpage:
                 http://www.cs.unibo.it/mobiwac2005
Each submission must be accompanied by the following information:
- a short abstract,
- a complete list of authors and their affiliations,
- a contact person for correspondence,
- postal and e-mail addresses

For more information, please contact the PC Co-Chairs: Luciano Bononi
(bononi@cs.unibo.it) or Teresa Dahlberg (tdahlber@uncc.edu)


                            IMPORTANT DATES

Submission Deadline: April 5th, 2005.
Notification of Acceptance: May 5th, 2005
Camera Ready version due: TBA



                          ORGANIZING COMMITTEE

General Co-Chairs:

   Azzedine Boukerche,                Sotiris Nikoletseas
   SITE, University of Ottawa         CTI/University of Patras, Greece
   Email: boukerch@site.uottwa.ca     Email: nikole@cti.gr

Program Co-Chairs:

   Teresa A. Dahlberg                 Luciano Bononi
   University of North Carolina       University of Bologna, Italy
   at Charlotte                       Email: bononi@cs.unibo.it
   Email: tdahlber@uncc.edu

Technical Program Committee:

Regina Aurajo, Federal University fo Sao Carlos, Brazil
Nick Bambos, Stanford University, USA
Stefano Basagni, Northeastern University, USA
Luciano Bononi, University of Bologna, Italy (co-chair)
Ioannis Chatzigiannakis, Computer Technology Institute, Greece
Teresa H. Dahlberg, University of North Carolina at Charlotte, USA 
(co-chair)
Sajal Das, University of Texas at Arlington, USA
Afonso Ferreira, CNRS, I3S & Inria Sophia Antipolis, France
Alois Ferscha, Johannes Kepler University of Linz, Austria
Chalermek Intanagonwiwat, Chulalongkorn U., Thailand
Helen Karatza, Aristotle University of Thessaloniki, Greece
Manolis Koubarakis, Technical University of Crete, Greece
Michela Meo, Politecnico di Torino, Italy
Mirela Sechi Moretti Annoni Notare, Barddal University, Brazil
Farid Nait-Abdesselam, University of Lille, France
Sotiris Nikoletseas, University of Patras and CTI, Greece
Paddy Nixon, University of Strathclyde, UK
Stephan Olariu, Old Dominion University, USA
Mohamed Ould-Khaoua, University of Glasgow, UK
Evaggelia Pitoura, University of Ioannina, Greece
Jose Rolim, University of Geneva, Switzerland
Salvatore Mario Rotolo, STMicroelectronics, Italy
Christian Schindelhauer, University of Paderborn, Germany
David Tipper, University of Pittsburgh, USA
Manos Varvarigos, University of Patras and CTI, Greece
Yu Wang, University of North Carolina at Charlotte, USA
Peter Widmayer, ETH Zurich, Switzerland
Albert Y. Zomaya, University of Sydney, AU



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


From mip4-bounces@ietf.org  Mon Mar 28 12:30:44 2005
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 MAA19679
	for <mip4-web-archive@ietf.org>; Mon, 28 Mar 2005 12:30:44 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DFyBA-0007J3-Mw
	for mip4-web-archive@ietf.org; Mon, 28 Mar 2005 12:37:33 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DFy0S-0005Qi-Lj; Mon, 28 Mar 2005 12:26:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DFy0P-0005OJ-NT
	for mip4@megatron.ietf.org; Mon, 28 Mar 2005 12:26:26 -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 MAA18829
	for <mip4@ietf.org>; Mon, 28 Mar 2005 12:26:22 -0500 (EST)
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.33)
	id 1DFy6w-0006x9-CX
	for mip4@ietf.org; Mon, 28 Mar 2005 12:33:11 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 28 Mar 2005 09:26:15 -0800
X-IronPort-AV: i="3.91,128,1110182400"; 
	d="scan'208,217"; a="241765709:sNHT119735030"
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j2SHQ2Dr005252;
	Mon, 28 Mar 2005 09:26:03 -0800 (PST)
Received: from kleung-w2k01.cisco.com (dhcp-171-71-202-221.cisco.com
	[171.71.202.221]) by mira-sjc5-b.cisco.com (MOS 3.4.5-GR)
	with ESMTP id BDJ55633; Mon, 28 Mar 2005 09:26:04 -0800 (PST)
Message-Id: <4.3.2.7.2.20050325154955.02d03e80@mira-sjcm-2.cisco.com>
X-Sender: kleung@mira-sjcm-2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 25 Mar 2005 16:30:11 -0800
To: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
From: Kent Leung <kleung@cisco.com>
Subject: RE: [Mip4] draft on RADIUS support for Mobile IP
In-Reply-To: <EBF631554F9CD7118D0B00065BF34DCB18379520@il27exm03.cig.mot .com>
Mime-Version: 1.0
X-Spam-Score: 1.2 (+)
X-Scan-Signature: e02509f7a15c0aaea12155beed3396f0
Cc: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>,
        kchowdhury@starentnetworks.com, mip4@ietf.org,
        avi@bridgewatersystems.com
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>
Content-Type: multipart/mixed; boundary="===============0442212993=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 1.2 (+)
X-Scan-Signature: b8a1197ccd66a793eeb911fe8a37f5bd

--===============0442212993==
Content-Type: multipart/alternative;
	boundary="=====================_257923344==_.ALT"

--=====================_257923344==_.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

Hi Madjid.  Comments inline.


At 04:56 PM 3/25/2005 -0600, Nakhjiri Madjid-MNAKHJI1 wrote:

>Hi Kent,
>
>
>
>Really appreciate the thorough read and useful comments. You are hitting 
>on many issues that we wanted this group to look at.
>
>I am making the mods to the draft as I am responding to you, so in this 
>email I will not get to respond to all of your comments. I will send 
>another email later on to the comments I am not responding to now.
>
>
>
>I can send you the modified draft over a direct link if you like.
>
>
>
>Regards,
>
>
>
>Madjid
>
>
>
>-----Original Message-----
>From: Kent Leung [mailto:kleung@cisco.com]
>Sent: Wednesday, March 23, 2005 7:06 PM
>To: Nakhjiri Madjid-MNAKHJI1
>Cc: mip4@ietf.org; Nakhjiri Madjid-MNAKHJI1; 
>kchowdhury@starentnetworks.com; avi@bridgewatersystems.com
>Subject: Re: [Mip4] draft on RADIUS support for Mobile IP
>
>
>
>Hi Madjid et al.,
>
>The draft looks pretty good overall.  Some comments.
>
>Madjid>>Thanks
>
>
>1) Please reference draft-ietf-mobileip-rfc3012bis-06.txt in document.
>
>Madjid>>I have 03 on rfc3012bis, I think you meant 06 of the key draft, 
>which is now RFC. Anyway, both references are updated now.
>
>
>2) Since the User-Name AVP will be populated with MN-NAI or MN-HoA,
>     why are the MIP-MN-NAI and MIP-MN-HoA AVPs needed?  If all AVPs
>     are supported, then how is the combination of them prioritized for
>     user lookup?
>
>Madjid>> We were trying to cover the case, when the user does not have an 
>HoA and wants to request one from the AAA server or HA. So both NAI and 
>HoA can be used but we do not use both AVPs, only one will be used as the 
>value for User-Name, so prioritization there. I changed to text so it 
>reads properly now.
>
>The values insides parentheses following the attributes represent various 
>alternatives for attribute values. In other words, for User-Name attribute 
>either MIP-MN-HoA or MIP-MN-NAI can be used, depending on whether the MN 
>has included an HoA or an NAI as identifier at the time of registration or 
>includes its NAI to indicate to the HA and AAA server that it requires an 
>HoA assignment. However, only one alternative will be included in the 
>User-Name attribute. Attributes included inside "<>" are optional. The HA 
>includes its own IP address as the value for NAS IP attribute.


Ah, originally I interpreted attributes inside parentheses as optional AVPs 
to the
message.  Now it's clearer these are the optional values.  But raises the
next issue for "NAS-IP (MIP-HA-IP address or MIP-HA-NAI)".  The NAS-IP
AVP may not be able to fit MIP-HA-NAI value.



>I am not quite sure whether we need the MIP-MN-NAI and MIP-MN-HoA as new 
>attributes or just as values for the existing User-name attribute. 
>Something to find out from RADEXT.

I'm fine with User-Name AVP with values from MIP-MN-NAI or MIP-MN-HoA.
The NAS-IP AVP threw me off since it had NAI which usually don't fit in
4 byte field.  So I assume that the parentheses meant additional AVPs.



>3) For CCoA mode Authenticator calculation, refer to 3012bis.  The Challenge
>     is non-zero.  The MFCE is part of the RRQ sent from MN to HA.
>
>Madjid>> Well, this is an area where 3012bis has problem. The challenge 
>that the MN uses in MFCE can only come from the challenge extension inside 
>agent advertisement from FAs (section 2). 3012bis does not define where 
>the challenge come from if there is no FA (CcoA mode). So we had to 
>replace the challenge with zero to be able to complete the MD5 hashing of 
>RRQ for RADIUS as described in 3012bis.
>


3012bis said outside of scope.  The challenge value may be 0 or non-zero.
But the MFCE is required.  One method is the MN generates the challenge
value.



>4) In 3.1 HA process RRQ section, since the NAS-IP and HA-IP addresses
>     may be different, shouldn't the MIP-HA-IP address or MIP-HA-NAI always
>     be included in the Access-Req?  The NAS-IP and the RADIUS server have
>     a shared secret to protect communication between them
>     (Message-Authenticator).  The MIP-HA identifier serves a different
>     function (e.g. possibly tag for HoA assignment).
>
>
>
>Madjid>>If the HA is the NAS, then the HA IP can be included in NAS IP, 
>but if FA is the NAS, then HA IP needs to go separartely. One thing we 
>were trying to support was a case when the MN does not know the IP address 
>of the HA and puts zeros in the RRQ fields to request for HA allocation. 
>So I added the following text to that section.
>
>


Even if the HA is the NAS, the HA IP address and NAS IP address may be 
different.
Maybe this needs to be mentioned?  Only in the case that HA IP address is 
the same
as NAS IP address, then MIP-HA-IP is not needed.



>If the HA does not find its own IP address inside the RRQ from the MN, the 
>HA needs to set the value of "Home-Agent-Requested" inside 
>MIP-feature-vector to indicate to the AAA server that MN has requested an 
>HA assignment.
>This is definitely a case where the HA can put its own IP address in NAS IP.
>
>
>
>5) General comments for clarity on labels.  XXX-REP to XXX-REPLAY,
>     XXX-LIFE to XXX-LIFETIME, XXX-ALGID to XXX-ALGORID.
>
>
>Madjid>>Done.
>
>
>6) Typo in "The HA receives the RADIUS Access Accept" bullet.  Remove
>     "using and MN to HA MSAs".
>Madjid>>Thanks, done.
>7) Same 3.1 section, "The MN extracts" bullet, specify how the MN-HA key
>     is derived (or reference [MIPKEYS]).
>Madjid>>added the reference.
>8) Figure 2a, label 1, 2, 3, etc. on the flow would be useful.
>Madjid>> I guess my laziness caught up with meJ Done.
>
>
>9) Sect 3.2 "The FA checks" bullet, missing ")" for MIP-FA-IP 
>address.  Same issue
>     with NAS-IP and MIP-FA-IP address as above.  Should have FA-IP identifier
>     (either MIP-FA-IP-address or MIP-FA-NAI) in case HA in foreign network
>     assignment happens.  Also, why is the MIP-FA-NAI  added only if HA 
> address is
>     all 1s or 0s?  The value of MIP-HA-IP-address can be set to HA field 
> in RRQ.
>Madjid>>  ")" fixed. FA-IP is now inside NAS-IP. If MN does not have an 
>HA, we need to do something, not sure if MIP-FA-NAI is good either.
>
>

I think the FA-IP may be different than NAS-IP.  It doesn't hurt to have 
MIP-FA-NAI,
which can identify the FA which may be useful for dynamic HA assignment
in foreign network.




>10) "The AAAH compares this value" bullet, I think having a new 
>MIP-FA-HA-nonce
>      is good to associate the 2 Access-Requests (one from FA, and other 
> from HA)
>      to set up the FA-HA MSA.  Also, the MIP-MN-FA-nonce is missing in 
> the list for
>      Access-Request.
>Madjid>> Not sure what purpose nonce would serve here, based on your other 
>comments below I think the FA-HA-SPI serves the same purpose. See my 
>comments below and let me know if you agree.


The key is to identify the FA-HA MSA on the RADIUS server.  I think
FA id, HA id, and FA-HA-SPI is sufficient.


>Added the MN-FA nonce, thanks,
>
>
>
>
>11) "The FA retrieves the MN-FA key" bullet, typo "Access-Request" should be
>       "Access-Accept".
>
>Madjid>>thanks again.
>
>
>12) "Upon receiving the reg" bullet, same issue with NAS-IP and MIP-HA 
>identifier.
>      Also, why are MIP-FA-to-HA-SPI and MIP-FA-HA-Authenticator AVPs 
> included?
>      See my opinion below.  May also want to have MIP-MN-FA-NAI as the FA
>      identifier to index the MSA.  Another point to capture is the case 
> when the
>      FA-HA MSA exists (e.g. created by another MN which registered previously
>      between the FA and HA).  Then the HA just authenticate the FHAE first
>      before sending Access-Request to AAA server.
>
>Madjid>> fixed NAS-IP (I think). Because, by now only FA got its keys. HA 
>does not have them yet.
>
>I thought the FA-to-HA-SPI will serve as an index for the AAA to find the 
>key that it has generated for FA-HA. So whether it uses SPI or FA-NAI for 
>lookup is something we need to agree on. And this is why I think a new 
>FA-HA-nonce not needed.


Agree with using FA id, HA id, and SPI to index the MSA.  But
why is the MIP-FA-HA-Authenticator in the msg?



>It will confuse the reader, since in the [MIPKEYS] the MN uses the nonce 
>to generate keys.
>
>I added your last comment on FHAE, good point.
>
>
>13) "The AAAH finds the FA-HA MSA" bullet, I think AAA should only be
>      responsible to authenticate the MN and provide the keys to the HA, which
>      is responsible to authenticate FHAE and MHAE (if there).  So AAA server
>      should authenticate MN using the MIP-MN-AAA-SPI and
>      MIP-MN-AAA-Authenticator.  Also, if the AAA server receives the 
> MIP-FA-HA-nonce,
>      it can find the right FA-HA MSA to provide to HA.
>
>Madjid>> well, the framework is trying to accommodate FA-HA MSA 
>establishment, so that "finds the MSA" thing is just so that the AAA can 
>locate the keys that it gave to FA and give them to HA. Did we give the 
>impression that the AAA server also verifies the FHAE?

Yes.  When I saw the MIP-FA-HA-Authenticator, I assume that was used for
authentication.  If only to look up MSA, the triplet will suffice.


>14) Same bullet as above, why does the Access-Accept include the MIP-MN-FA-XXX
>       AVPs?  These were already delivered to the FA in the RADIUS 
> exchange between
>       FA and AAAF.
>
>Because, my impression was that the HA builds both the MN-HA-nonce reply 
>and MN-FA-nonce reply when it is building the RRP and before signing the 
>MN-HA-AE. In that case the HA would need  that info, even though it was 
>delivered to FA before.


I got that same impression.  But this doesn't see right to me since the
key nonce are protected by MHAE from HA, and MFAE from FA.  So
not sure why HA needs to handle MN-FA nonce.  Have to check the
draft to confirm.



>15) "The HA retreives the key materials" bullet, I don't think HA should 
>be putting
>       MN-FA-nonce.  HA should only put the MN-HA-nonce in the KeyGenReplyExt
>       protected by MHAE.
>Madjid>> same as above.
>16) "The FA relays the RRP" bullet, I think the FA should put the 
>MN-FA-nonce in
>       the appended KeyGenReplyExt protected by MFAE before sending to MN.
>Madjid>> same as above.
>
>


What does keygen draft say?



>
>
>OK, I think I need to start leaving for the weakend now, I will respond to 
>your other comments later as I will fix the rest of the draft.

OK.

Kent


--
      |           |                   Kent Leung
     :|:         :|:                  IP Mobility Development
    :|||:       :|||:                 Internet Technologies Division
   :|||||||:   :|||||||:              Voice: 408.526.5030
.:|||||||||:.:|||||||||:.             Fax:   408.525.1653
  c i s c o S y s t e m s             Email: kleung@cisco.com 
--=====================_257923344==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
Hi Madjid.&nbsp; Comments inline.<br>
<br>
<br>
At 04:56 PM 3/25/2005 -0600, Nakhjiri Madjid-MNAKHJI1 wrote:<br>
<br>
<blockquote type=cite cite><font face="arial" size=2 color="#000080">Hi
Kent,<br>
</font><br>
<font face="arial" size=2 color="#000080">&nbsp;<br>
</font><br>
<font face="arial" size=2 color="#000080">Really appreciate the thorough
read and useful comments. You are hitting on many issues that we wanted
this group to look at.<br>
</font><br>
<font face="arial" size=2 color="#000080">I am making the mods to the
draft as I am responding to you, so in this email I will not get to
respond to all of your comments. I will send another email later on to
the comments I am not responding to now.<br>
</font><br>
<font face="arial" size=2 color="#000080">&nbsp;<br>
</font><br>
<font face="arial" size=2 color="#000080">I can send you the modified
draft over a direct link if you like.<br>
</font><br>
<font face="arial" size=2 color="#000080">&nbsp;<br>
</font><br>
<font face="arial" size=2 color="#000080">Regards,<br>
</font><br>
<font face="arial" size=2 color="#000080">&nbsp;<br>
</font><br>
<font face="arial" size=2 color="#000080">Madjid<br>
</font><br>
<font face="arial" size=2 color="#000080">&nbsp;<br>
</font><br>
<font face="tahoma" size=2>-----Original Message-----<br>
<b>From:</b> Kent Leung
[<a href="mailto:kleung@cisco.com" eudora="autourl">mailto:kleung@cisco.com</a>]
<br>
<b>Sent:</b> Wednesday, March 23, 2005 7:06 PM<br>
<b>To:</b> Nakhjiri Madjid-MNAKHJI1<br>
<b>Cc:</b> mip4@ietf.org; Nakhjiri Madjid-MNAKHJI1;
kchowdhury@starentnetworks.com; avi@bridgewatersystems.com<br>
<b>Subject:</b> Re: [Mip4] draft on RADIUS support for Mobile IP<br>
</font><br>
<font face="Times New Roman, Times">&nbsp;<br>
</font><br>
<font face="Times New Roman, Times">Hi Madjid et al.,<br>
<br>
The draft looks pretty good overall.&nbsp; Some comments.<br>
<br>
</font><font face="arial" size=2 color="#000080">Madjid&gt;&gt;Thanks<br>
</font><br>
<font face="Times New Roman, Times"><br>
1) Please reference draft-ietf-mobileip-rfc3012bis-06.txt in
document.<br>
<br>
</font><font face="arial" size=2 color="#000080">Madjid&gt;&gt;I have 03
on rfc3012bis, I think you meant 06 of the key draft, which is now RFC.
Anyway, both references are updated now. <br>
</font><br>
<font face="Times New Roman, Times"><br>
2) Since the User-Name AVP will be populated with MN-NAI or MN-HoA,<br>
&nbsp;&nbsp;&nbsp; why are the MIP-MN-NAI and MIP-MN-HoA AVPs
needed?&nbsp; If all AVPs<br>
&nbsp;&nbsp;&nbsp; are supported, then how is the combination of them
prioritized for<br>
&nbsp;&nbsp;&nbsp; user lookup?<br>
<br>
</font><font face="arial" size=2 color="#000080">Madjid&gt;&gt; We were
trying to cover the case, when the user does not have an HoA and wants to
request one from the AAA server or HA. So both NAI and HoA can be used
but we do not use both AVPs, only one will be used as the value for
User-Name, so prioritization there. I changed to text so it reads
properly now. <br>
</font><br>
<font face="Times New Roman, Times" color="#FF0000">The values insides
parentheses following the attributes represent various alternatives for
attribute values. In other words, for User-Name attribute either
MIP-MN-HoA or MIP-MN-NAI can be used, depending on whether the MN has
included an HoA or an NAI as identifier at the time of registration or
includes its NAI to indicate to the HA and AAA server that it requires an
HoA assignment. However, only one alternative will be included in the
User-Name attribute. Attributes included inside &quot;&lt;&gt;&quot; are
optional.</font> <font color="#FF0000">The HA includes its own IP address
as the value for NAS IP attribute.<br>
</font></blockquote><br>
<br>
Ah, originally I interpreted attributes inside parentheses as optional
AVPs to the<br>
message.&nbsp; Now it's clearer these are the optional values.&nbsp; But
raises the<br>
next issue for &quot;NAS-IP (MIP-HA-IP address or
MIP-HA-NAI)&quot;.&nbsp; The NAS-IP<br>
AVP may not be able to fit MIP-HA-NAI value.<br>
<br>
<br>
<br>
<blockquote type=cite cite><font face="arial" size=2 color="#000080">I am
not quite sure whether we need the MIP-MN-NAI and MIP-MN-HoA as new
attributes or just as values for the existing User-name attribute.
Something to find out from RADEXT. <br>
</font></blockquote><br>
I'm fine with User-Name AVP with values from MIP-MN-NAI or
MIP-MN-HoA.<br>
The NAS-IP AVP threw me off since it had NAI which usually don't fit
in<br>
4 byte field.&nbsp; So I assume that the parentheses meant additional
AVPs.<br>
<br>
<br>
<br>
<blockquote type=cite cite><font face="Times New Roman, Times">3) For
CCoA mode Authenticator calculation, refer to 3012bis.&nbsp; The
Challenge<br>
&nbsp;&nbsp;&nbsp; is non-zero.&nbsp; The MFCE is part of the RRQ sent
from MN to HA.<br>
<br>
</font><font face="arial" size=2 color="#000080">Madjid&gt;&gt; Well,
this is an area where 3012bis has problem. The challenge that the MN uses
in MFCE can only come from the challenge extension inside agent
advertisement from FAs (section 2). 3012bis does not define where the
challenge come from if there is no FA (CcoA mode). So we had to replace
the challenge with zero to be able to complete the MD5 hashing of RRQ for
RADIUS as described in 3012bis.<br>
</font><br>
<font face="Times New Roman, Times"></font></blockquote><br>
<br>
3012bis said outside of scope.&nbsp; The challenge value may be 0 or
non-zero.<br>
But the MFCE is required.&nbsp; One method is the MN generates the
challenge<br>
value.<br>
<br>
<br>
<br>
<blockquote type=cite cite><font face="Times New Roman, Times">4) In 3.1
HA process RRQ section, since the NAS-IP and HA-IP addresses <br>
&nbsp;&nbsp;&nbsp; may be different, shouldn't the MIP-HA-IP address or
MIP-HA-NAI always <br>
&nbsp;&nbsp;&nbsp; be included in the Access-Req?&nbsp; The NAS-IP and
the RADIUS server have<br>
&nbsp;&nbsp;&nbsp; a shared secret to protect communication between them
<br>
&nbsp;&nbsp;&nbsp; (Message-Authenticator).&nbsp; The MIP-HA identifier
serves a different<br>
&nbsp;&nbsp;&nbsp; function (e.g. possibly tag for HoA assignment).<br>
<br>
</font><font face="arial" size=2 color="#000080">&nbsp;<br>
</font><br>
<font face="Times New Roman, Times" color="#000080">Madjid&gt;&gt;If the
HA is the NAS, then the HA IP can be included in NAS IP, but if FA is the
NAS, then HA IP needs to go separartely. One thing we were trying to
support was a case when the MN does not know the IP address of the HA and
puts zeros in the RRQ fields to request for HA allocation. So I added the
following text to that section.<br>
</font><br>
<font face="Times New Roman, Times" color="#000080">&nbsp;</font></blockquote><br>
<br>
Even if the HA is the NAS, the HA IP address and NAS IP address may be
different.<br>
Maybe this needs to be mentioned?&nbsp; Only in the case that HA IP
address is the same<br>
as NAS IP address, then MIP-HA-IP is not needed.<br>
<br>
<br>
<br>
<blockquote type=cite cite><font face="Times New Roman, Times" color="#FF0000">If
the HA does not find its own IP address inside the RRQ from the MN, the
HA needs to set the value of &quot;Home-Agent-Requested&quot; inside
MIP-feature-vector to indicate to the AAA server that MN has requested an
HA assignment</font>.<br>
<font color="#000080">This is definitely a case where the HA can put its
own IP address in NAS IP.<br>
</font><br>
<font face="arial" size=2 color="#000080">&nbsp;<br>
</font><br>
<font face="Times New Roman, Times">5) General comments for clarity on
labels.&nbsp; XXX-REP to XXX-REPLAY, <br>
&nbsp;&nbsp;&nbsp; XXX-LIFE to XXX-LIFETIME, XXX-ALGID to
XXX-ALGORID.<br>
&nbsp;&nbsp;&nbsp; <br>
</font><br>
<font face="arial" size=2 color="#000080">Madjid&gt;&gt;Done.<br>
</font><br>
<font face="Times New Roman, Times"><br>
6) Typo in &quot;The HA receives the RADIUS Access Accept&quot;
bullet.&nbsp; Remove<br>
&nbsp;&nbsp;&nbsp; &quot;using and MN to HA MSAs&quot;.<br>
</font><font face="Times New Roman, Times" color="#000080">Madjid&gt;&gt;Thanks,
done.</font><font face="Times New Roman, Times"><br>
7) Same 3.1 section, &quot;The MN extracts&quot; bullet, specify how the
MN-HA key<br>
&nbsp;&nbsp;&nbsp; is derived (or reference [MIPKEYS]).<br>
</font><font face="Times New Roman, Times" color="#000080">Madjid&gt;&gt;added
the reference.</font><font face="Times New Roman, Times"><br>
8) Figure 2a, label 1, 2, 3, etc. on the flow would be useful.<br>
</font><font face="Times New Roman, Times" color="#000080">Madjid&gt;&gt;
I guess my laziness caught up with
me</font><font face="wingdings" color="#000080">J</font> Done.<br>
<br>
<font face="Times New Roman, Times"><br>
9) Sect 3.2 &quot;The FA checks&quot; bullet, missing &quot;)&quot; for
MIP-FA-IP address.&nbsp; Same issue<br>
&nbsp;&nbsp;&nbsp; with NAS-IP and MIP-FA-IP address as above.&nbsp;
Should have FA-IP identifier<br>
&nbsp;&nbsp;&nbsp; (either MIP-FA-IP-address or MIP-FA-NAI) in case HA in
foreign network <br>
&nbsp;&nbsp;&nbsp; assignment happens.&nbsp; Also, why is the
MIP-FA-NAI&nbsp; added only if HA address is <br>
&nbsp;&nbsp;&nbsp; all 1s or 0s?&nbsp; The value of MIP-HA-IP-address can
be set to HA field in RRQ.<br>
</font><font face="Times New Roman, Times" color="#000080">Madjid&gt;&gt;&nbsp;
&quot;)&quot; fixed. FA-IP is now inside NAS-IP. If MN does not have an
HA, we need to do something, not sure if MIP-FA-NAI is good either. 
<br>
</font><br>
<font face="arial" size=2 color="#000080">&nbsp;</font></blockquote><br>
I think the FA-IP may be different than NAS-IP.&nbsp; It doesn't hurt to
have MIP-FA-NAI,<br>
which can identify the FA which may be useful for dynamic HA
assignment<br>
in foreign network.<br>
<br>
<br>
<br>
<br>
<blockquote type=cite cite><font face="Times New Roman, Times">10)
&quot;The AAAH compares this value&quot; bullet, I think having a new
MIP-FA-HA-nonce<br>
&nbsp;&nbsp;&nbsp;&nbsp; is good to associate the 2 Access-Requests (one
from FA, and other from HA)<br>
&nbsp;&nbsp;&nbsp;&nbsp; to set up the FA-HA MSA.&nbsp; Also, the
MIP-MN-FA-nonce is missing in the list for<br>
&nbsp;&nbsp;&nbsp;&nbsp; Access-Request.<br>
</font><font face="Times New Roman, Times" color="#000080">Madjid&gt;&gt;
Not sure what purpose nonce would serve here, based on your other
comments below I think the FA-HA-SPI serves the same purpose. See my
comments below and let me know if you agree.<br>
</font></blockquote><br>
<br>
The key is to identify the FA-HA MSA on the RADIUS server.&nbsp; I
think<br>
FA id, HA id, and FA-HA-SPI is sufficient.<br>
<br>
<br>
<blockquote type=cite cite><font face="Times New Roman, Times" color="#000080">Added
the MN-FA nonce, thanks,<br>
</font><br>
<font face="arial" size=2 color="#000080">&nbsp;<br>
</font><br>
<font face="Times New Roman, Times"><br>
11) &quot;The FA retrieves the MN-FA key&quot; bullet, typo
&quot;Access-Request&quot; should be<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;Access-Accept&quot;.<br>
<br>
</font><font face="arial" size=2 color="#000080">Madjid&gt;&gt;thanks
again.<br>
</font><br>
<font face="Times New Roman, Times"><br>
12) &quot;Upon receiving the reg&quot; bullet, same issue with NAS-IP and
MIP-HA identifier.<br>
&nbsp;&nbsp;&nbsp;&nbsp; Also, why are MIP-FA-to-HA-SPI and
MIP-FA-HA-Authenticator AVPs included?<br>
&nbsp;&nbsp;&nbsp;&nbsp; See my opinion below.&nbsp; May also want to
have MIP-MN-FA-NAI as the FA<br>
&nbsp;&nbsp;&nbsp;&nbsp; identifier to index the MSA.&nbsp; Another point
to capture is the case when the<br>
&nbsp;&nbsp;&nbsp;&nbsp; FA-HA MSA exists (e.g. created by another MN
which registered previously<br>
&nbsp;&nbsp;&nbsp;&nbsp; between the FA and HA).&nbsp; Then the HA just
authenticate the FHAE first<br>
&nbsp;&nbsp;&nbsp;&nbsp; before sending Access-Request to AAA
server.<br>
<br>
</font><font face="arial" size=2 color="#000080">Madjid&gt;&gt; fixed
NAS-IP (I think). Because, by now only FA got its keys. HA does not have
them yet.<br>
</font><br>
<font face="arial" size=2 color="#000080">I thought the FA-to-HA-SPI will
serve as an index for the AAA to find the key that it has generated for
FA-HA. So whether it uses SPI or FA-NAI for lookup is something we need
to agree on. And this is why I think a new FA-HA-nonce not needed.
</font></blockquote><br>
<br>
Agree with using FA id, HA id, and SPI to index the MSA.&nbsp; But<br>
why is the MIP-FA-HA-Authenticator in the msg?<br>
<br>
<br>
<br>
<blockquote type=cite cite><font face="arial" size=2 color="#000080">It
will confuse the reader, since in the [MIPKEYS] the MN uses the nonce to
generate keys. <br>
</font><br>
<font face="arial" size=2 color="#000080">I added your last comment on
FHAE, good point.<br>
</font><br>
<font face="Times New Roman, Times"><br>
13) &quot;The AAAH finds the FA-HA MSA&quot; bullet, I think AAA should
only be<br>
&nbsp;&nbsp;&nbsp;&nbsp; responsible to authenticate the MN and provide
the keys to the HA, which<br>
&nbsp;&nbsp;&nbsp;&nbsp; is responsible to authenticate FHAE and MHAE (if
there).&nbsp; So AAA server<br>
&nbsp;&nbsp;&nbsp;&nbsp; should authenticate MN using the MIP-MN-AAA-SPI
and <br>
&nbsp;&nbsp;&nbsp;&nbsp; MIP-MN-AAA-Authenticator.&nbsp; Also, if the AAA
server receives the MIP-FA-HA-nonce,<br>
&nbsp;&nbsp;&nbsp;&nbsp; it can find the right FA-HA MSA to provide to
HA.&nbsp; <br>
<br>
</font><font face="arial" size=2 color="#000080">Madjid&gt;&gt; well, the
framework is trying to accommodate FA-HA MSA establishment, so that
&quot;finds the MSA&quot; thing is just so that the AAA can locate the
keys that it gave to FA and give them to HA. Did we give the impression
that the AAA server also verifies the FHAE? <br>
</font></blockquote><br>
Yes.&nbsp; When I saw the MIP-FA-HA-Authenticator, I assume that was used
for <br>
authentication.&nbsp; If only to look up MSA, the triplet will
suffice.<br>
<br>
<br>
<blockquote type=cite cite><font face="Times New Roman, Times">14) Same
bullet as above, why does the Access-Accept include the
MIP-MN-FA-XXX<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AVPs?&nbsp; These were already delivered
to the FA in the RADIUS exchange between<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FA and AAAF.<br>
<br>
</font><font face="arial" size=2 color="#000080">Because, my impression
was that the HA builds both the MN-HA-nonce reply and MN-FA-nonce reply
when it is building the RRP and before signing the MN-HA-AE. In that case
the HA would need&nbsp; that info, even though it was delivered to FA
before.<br>
</font></blockquote><br>
<br>
I got that same impression.&nbsp; But this doesn't see right to me since
the<br>
key nonce are protected by MHAE from HA, and MFAE from FA.&nbsp; So<br>
not sure why HA needs to handle MN-FA nonce.&nbsp; Have to check 
the<br>
draft to confirm.<br>
<br>
<br>
<br>
<blockquote type=cite cite><font face="Times New Roman, Times">15)
&quot;The HA retreives the key materials&quot; bullet, I don't think HA
should be putting<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MN-FA-nonce.&nbsp; HA should only put the
MN-HA-nonce in the KeyGenReplyExt<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; protected by MHAE.<br>
</font><font face="Times New Roman, Times" color="#000080">Madjid&gt;&gt;
same as above.</font><font face="Times New Roman, Times"><br>
16) &quot;The FA relays the RRP&quot; bullet, I think the FA should put
the MN-FA-nonce in<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the appended KeyGenReplyExt protected by
MFAE before sending to MN.<br>
</font><font face="Times New Roman, Times" color="#000080">Madjid&gt;&gt;
same as above.<br>
</font><br>
<font face="Times New Roman, Times" color="#000080">&nbsp;</font></blockquote><br>
<br>
What does keygen draft say?<br>
<br>
<br>
<br>
<blockquote type=cite cite><font face="Times New Roman, Times" color="#000080">&nbsp;<br>
</font><br>
<font face="Times New Roman, Times" color="#000080">OK, I think I need to
start leaving for the weakend now, I will respond to your other comments
later as I will fix the rest of the draft.<br>
</font></blockquote><br>
OK.<br>
<br>
Kent<br>
<br>
<br>
<div>--</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Kent Leung</div>
<div>&nbsp;&nbsp;&nbsp;
:|:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
:|:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
IP Mobility Development</div>
<div>&nbsp;&nbsp; :|||:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
:|||:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Internet Technologies Division</div>
<div>&nbsp; :|||||||:&nbsp;&nbsp;
:|||||||:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Voice: 408.526.5030</div>
<div>.:|||||||||:.:|||||||||:.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Fax:&nbsp;&nbsp; 408.525.1653</div>
&nbsp;c i s c o S y s t e m
s&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Email: kleung@cisco.com
</html>

--=====================_257923344==_.ALT--


--===============0442212993==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0442212993==--



From mip4-bounces@ietf.org  Mon Mar 28 15:44:02 2005
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 PAA10129
	for <mip4-web-archive@ietf.org>; Mon, 28 Mar 2005 15:44:02 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DG1CF-0006MV-Ts
	for mip4-web-archive@ietf.org; Mon, 28 Mar 2005 15:50:52 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DG0vt-0006IJ-2K; Mon, 28 Mar 2005 15:33:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DG0vq-0006H8-CN
	for mip4@megatron.ietf.org; Mon, 28 Mar 2005 15:33:54 -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 PAA08933
	for <mip4@ietf.org>; Mon, 28 Mar 2005 15:33:52 -0500 (EST)
Received: from carrierpigeon.cs.umd.edu ([128.8.129.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DG12O-00061D-J9
	for mip4@ietf.org; Mon, 28 Mar 2005 15:40:42 -0500
Received: from MINDLAP2 (mindlap2.cs.umd.edu [172.16.0.37])
	(authenticated bits=0)
	by carrierpigeon.cs.umd.edu (8.12.10/8.12.5) with ESMTP id
	j2SKXata023787
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <mip4@ietf.org>; Mon, 28 Mar 2005 15:33:43 -0500 (EST)
Message-Id: <200503282033.j2SKXata023787@carrierpigeon.cs.umd.edu>
From: "Moustafa Youssef" <moustafa@cs.umd.edu>
To: <mip4@ietf.org>
Date: Mon, 28 Mar 2005 15:33:28 -0500
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0064_01C533AB.847F0BF0"
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-MS-TNEF-Correlator: 0000000006F61F65A15E334E985099AB7E0DC8D324692200
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 03169bfe4792634a390035a01a6c6d2f
Subject: [Mip4] Deadline approaching: IEEE WirelessCom Symposium on Mobile
	Computing, 2005
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e472ca43d56132790a46d9eefd95f0a5

This is a multi-part message in MIME format.

------=_NextPart_000_0064_01C533AB.847F0BF0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

(Our apologies if you receive multiple copies of this CFP)
-------------------------------------------------------------
                    Call for Papers
              Symposium on Mobile Computing
  http://www.csee.umbc.edu/~younis/WC_MobCom05.htm
                       as part of 
                IEEE WirelessCom 2005
Sheraton Maui Resort, Kaanapali Beach, Maui, Hawaii, USA
           http://sa1.sice.umkc.edu/wc05/ 
                   June 13-16, 2005
  Technical Sponsorship: IEEE TCCC, TCPC, and SSCTC


Recent years have witnessed an enormous growth in the development and
applications of mobile computing environments and devices. Many
practitioners envision a future empowered with context and location aware
computation and communication infrastructure that allow users to access data
and receive service at any place and any time. Compared to conventional
platforms, the mobility of computing nodes introduces many challenges to the
design of almost all systems components. 

This symposium will foster a forum for discussing and presenting recent
research results on mobile computer systems. Original papers are invited in
the broader area of mobile computing. Papers must report high-quality and
previously unpublished work. Topics of interest include, but are not limited
to, the following:

* Architecture and infrastructure support	
* Middleware and operating systems services
* Development platforms and environments
* Adaptive resource management schemes
* Pervasive and Context-aware Computing
* Performance metrics and studies
* Power aware computation and communication
* Data consistency and synchronization protocols
* Fault-tolerant architectural and operation models
* Wearable computing devices and systems
* Time constrained mobile systems
* Robust ad-hoc networking techniques
* Efficient localization techniques
* Wireless sensor networks
* Mobile peer to peer systems
* Quality of service provisioning
* Context-conscious computing
* Web caching and services
* Emerging applications and systems
* Mobile agents
* Mobile commerce
* Security and privacy issues


Submission Guidelines
---------------------
Original papers are solicited and must represent high-quality and previously
unpublished work, not currently under review by another conference or
journal. Prospective authors should submit their paper electronically
through https://msrcmt.research.microsoft.com/WirelessCom2005. All papers
are limited to 6 pages in standard IEEE double-column format. 

Important Dates
---------------
Paper Submission Deadline: 	March 31, 2005 (extended)
Notification of Acceptance: 	April 22, 2005
Camera-Ready Papers: 	May 1, 2005

Symposium Co-Chairs
-------------------
Mohamed Younis
Department of Computer Science and Electrical Engineering University of
Maryland Baltimore County, 1000 Hilltop Circle, Baltimore, MD 21250
Voice: (410) 455-3968,    FAX: (410) 455-3968
E-mail: younis@csee.umbc.edu 

Hesham El-Rewini
Department of Computer Science and Engineering
Southern Methodist University
3145 Dyer Street, Dallas, TX 75205
Voice: (214) 768-3278,	FAX: (214) 768-3085
E-mail: rewini@engr.smu.edu


Publicity Chair
----------------
Moustafa Youssef
Department of Computer Science
University of Maryland at College Park,
College Park, MD 20742
Voice: (301) 405-0341,    FAX: (301) 405-6707
E-mail: moustafa@cs.umd.edu

------=_NextPart_000_0064_01C533AB.847F0BF0
Content-Type: application/ms-tnef;
	name="winmail.dat"
Content-Disposition: attachment;
	filename="winmail.dat"
Content-Transfer-Encoding: base64

eJ8+IigUAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy
b3NvZnQgTWFpbC5Ob3RlADEIAQOQBgBECgAAEQAAAAsAAQ4AAAAAAgEKDgEAAAAYAAAAAAAAAAb2
H2WhXjNOmFCZq34NyNPCgAAAAwAUDgEAAAALAB8OAQAAAAIB+A8BAAAAEAAAAAb2H2WhXjNOmFCZ
q34NyNMCAfoPAQAAABAAAAAG9h9loV4zTphQmat+DcjTAwD+DwUAAAACAQkQAQAAALYIAACyCAAA
nw8AAExaRnUyh6wqAwAKAHJjcGcxMjXiMgNDdGV4BUEBAwH3/wqAAqQD5AcTAoAP8wBQBFY/CFUH
shElDlEDAQIAY2jhCsBzZXQyBgAGwxEl9jMERhO3MBIsETMI7wn3tjsYHw4wNREiDGBjAFAzCwkB
ZDM2FlALpiAook8IcCBhcBehZwiQUwQgBpAgeQhgIBggYwBlaXZlIG11bFp0BSBsHrAFoHAdom8Z
HfB0aAQAEiBGUCn7CqIKgC0g/yIPIx8jtyCU9iAlLyVQQwdAAyACEAXA9lAdQASQcyTPJVEGsR1Q
GQCQdW0fwAOgTW9iLwMQHrAIUCiwdR8AbmcFJ1ZoAkBwOi8vd0krUC5jFBBlLikAYsRjLgmAdS9+
HhEDAGBzL1dDXylhKdEwtDUuKuBtJ18uqmEEIJ8KsQVAH9Et7y6jSUUx0HggV2kYIB8wBBAp0SAn
AdAtgCCUU2gEkGF0cSkyYXVpB/AHkBfBLHggS2EAcB1AB0A0MEI6ZQDQaDSwNAI0sEhhxncLcDYR
VVNBMG8q5bBzYTEuDdErwmssFLR3Yy2ALzBfOndKLKDBHrAxMy0xNjSwMtjVOnBUBZBoAwBjB0AG
AHcdUACABbBzIBArEDG0VG5DPtA0sD7AUD7xAHBk+QYAU0M+wCCUQBo0UB5w3wIwHgA1gBQAKtBh
HqED8N50O6AEEAmAP3EgCfAFsM0EYHUEIAnAb3cgAB3QvwOgIAAesAEAHqAXsHAHgP9BcT+CHUAL
UD1RHwA9wR/C3wRgKYMFoCn1QxF2MiACIJ9FAgQgP4JEkTjBcy4z8exueS/QM6BjHwBGAich90eT
AJApMWEmoCoQCHAesPplKLF3BJBCwUJRRAAFoP8CMA7CP4IXsEXkHTA2YEth/0cETXU/kUcBHtA9
Qk2DC4DzA1AvsHRyGtBLQyAAM7D3HTAmgEPQIEOASjIzwB0w9mNI8QQgZDOwSwA/gh5W/1HBSNId
MEUySXELYFQSRWL/SWEfAAeASSAp0k3xP6BSEf9MgR6gAjBGET1xC1EAMENB/nM0sERSRpNCYElw
H9FHCP9DMAEAHcECMANgLEBI8R7A70lSE9EmgAnwZweRUhFEVP0AkGcDoB/RB0AEYFBgUUL9U7B5
UGBLkAQgRwJKEUgx+0kgQBpUIBJdoCi2A/Amg19dwR0hJqIpASayZAQAY/9DgACQR3E/gkmQB5BW
8kdx/x5SQXFjEgrAE9BkEh7hH7HfA6BGmxKBXaVJIE8FEB2Q/1dDJwMdMEthC4BHwA6wP6D1RCVi
A2BhBIFn4ksARm//KkBJICb0HsFdMRggHVAwAcEgEGdoLXF1NTFY0fdixUfAQ3FsSXAsoCoAAmCv
BAAzgEwRBbBrSSBUH3G/K5AfwloxS+FdMQuAYwpA+wEANLBiKhBn40MwBUA1QH5taGMzwFgUAhBR
YioxOv1AGioQwRPQaGFQpD+CUB0/ZNBFoBfBDII55XQwTWn8ZGQfME3jP4IfcDOSR2LvXaZTxSdF
dDBERKlXhz9z/0eqc9dSsAUwHpJjEQhhVBH9A4FhW6BFAwTwM4AHgXPWflBT0S+wHpI/gghQTKMt
/03UKd2AI1fCAHB+chQgBRD/b5E/glBgcMAdoX/HS8JNz/9O3wIgeidSwkyBAJBdwXCQl20kXaBw
kGhH4Wl6TXTfSZBxoE1QBvB6F0Y0EB7w/i0zwB8wM6BFInRoPXF4SfdlMwEAi1hXQbEBoEbbSLX/
iZVdw3PWB2KI01BwC3FCwR9GlZF9CABxEF0yZC1o/01QWcAUIG7yR2J0oT0xbMD9eghFASAN4AiQ
QXFNQjVA/4p1lm8yB1OxPdKVpnoXKWXfJxASgVIRnIORfVFs1R/R/1PGiuFKlIJpgSaI4pfAQ3J/
RwePCHbwPWB0cWKVea5F/QeAcmchYqFFqpE/m/d+0f982SllTzIEkB5wc9YGYGJA/wUQbRcekADQ
SXAEAZbXq+reU25gcfBiYSkxRzQgjsH/kyEnRSO/JIhm/3YiBvCXsf9ocj+Ca7ZjFGxvbX9uiTSw
/3GSqlEYIAIwtQNpYrSSB9HeYrQicaAzgUxyZkvhg5K9BbFqCGFXQWshA2BzJxB/ScGAsioQlXBB
0T4QCGBs/4RxrRIFQERRMiBndEMQHzC/ScCKMj1htQEgAANgdbOQvSrTcyshV/BkcA6gLmQm/i5x
8AUAKNAf0L9ARwEs4HcyKDLSSSBBJoFniXHYIP42L9FbokQhUGA/gQsRMbTeZAhgj9GhIQpAbQOg
g0P7v0Be20kosQAgjKKIka4//yRqJvMGAK0YeqBpUK4CPlDndsM0AGRyMzE8JBzgDsHrCfABAGQg
hU5xoAaQT5a9H9FBUlEFMIOCy2VBqwE5AyAyMjwqJmCk8WEt/zRQaVBJcCb0y2dJcMxFrEvzKKcI
UC1DE+AyIMgfJD3vKWAT4AeAP6BZLJPVVHqgfy/iRQMf0SnUygKXwlTlRXu9Ez1TRSpAkyEGcUdx
Vd8DAB6gFABYxcvReQtgP5H+QgdAVZEFsIHiLKBY0DSwtjEy4BZQSGChM8BwEiDfMiBwoHDh3Zc1
wUQywA4hMwFA1WNWbzjBPlAoNBHesCkgNBpgLTM5jDY4NLA6cUZBWOHuedVURS0AwAMQPlAshED7
K5te20gHkNdh2qHRcXMh/wCg2D/ZT9pV23gzFQhguGL/KUEUIJVwYhEFQNwo1VTMMP/iYHqQQaDK
EVBwCeA0oYiQxyaAL7A/AVggNw5AMvZr4Zbg4DTiQDfiwOKQMp434tB2w+M08SgwODMF1+TGGCDo
EkBbgXI4oB7Q/ywiq+/JwG5iseFJcNTz1V9z1ptrwWFmSwDXwUKhZv/oX+lvqZbcL900USEIUFth
P1ugJuG2EdC1/rrgozA3bjQOUOFL80Ax4kEtgC2cMDPiEOLpAhc2NwDwX+RsQ2L5ouWhK9Fk9Vh9
AQbgAAADAA00/T8DAAMADzT9PwMAAgEUNAEAAAAQAAAATklUQfm/uAEAqgA32W4AAAIBfwABAAAA
MQAAADAwMDAwMDAwMDZGNjFGNjVBMTVFMzM0RTk4NTA5OUFCN0UwREM4RDMyNDY5MjIwMAAAAAAD
AAYQ7ZwQcQMABxDYCgAAAwAQEAAAAAADABEQAAAAAB4ACBABAAAAZQAAAChPVVJBUE9MT0dJRVNJ
RllPVVJFQ0VJVkVNVUxUSVBMRUNPUElFU09GVEhJU0NGUCktLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0AAAAA444=

------=_NextPart_000_0064_01C533AB.847F0BF0
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

------=_NextPart_000_0064_01C533AB.847F0BF0--




From mip4-bounces@ietf.org  Tue Mar 29 18:03:37 2005
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 SAA05545
	for <mip4-web-archive@ietf.org>; Tue, 29 Mar 2005 18:03:37 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DGPr6-00030D-It
	for mip4-web-archive@ietf.org; Tue, 29 Mar 2005 18:10:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DGPiX-0003Fs-Px; Tue, 29 Mar 2005 18:01:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DGPiV-0003Fl-D8
	for mip4@megatron.ietf.org; Tue, 29 Mar 2005 18:01:48 -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 SAA05422
	for <mip4@ietf.org>; Tue, 29 Mar 2005 18:01:44 -0500 (EST)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DGPpI-0002wl-0s
	for mip4@ietf.org; Tue, 29 Mar 2005 18:08:48 -0500
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (Motorola/Motgate8) with ESMTP id j2TN3s24009773
	for <mip4@ietf.org>; Tue, 29 Mar 2005 16:03:54 -0700 (MST)
Received: from il27exm03.cig.mot.com (il27exm03.cig.mot.com [10.17.193.4])
	by il06exr01.mot.com (8.13.1/8.13.0) with ESMTP id j2TN3S5p007727
	for <mip4@ietf.org>; Tue, 29 Mar 2005 17:03:28 -0600 (CST)
Received: by il27exm03.cig.mot.com with Internet Mail Service (5.5.2657.72)
	id <GP0XHH1V>; Tue, 29 Mar 2005 17:01:35 -0600
Message-ID: <EBF631554F9CD7118D0B00065BF34DCB18379544@il27exm03.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'Kent Leung'" <kleung@cisco.com>
Subject: RE: [Mip4] draft on RADIUS support for Mobile IP
Date: Tue, 29 Mar 2005 17:01:34 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 0f3de74e534ea82d41273d2b8504db1c
Cc: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>,
        kchowdhury@starentnetworks.com, mip4@ietf.org,
        avi@bridgewatersystems.com
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>
Content-Type: multipart/mixed; boundary="===============0600860087=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 8136d1e28e0aab8a4e130297ed2e1fc4

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============0600860087==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C534B3.40D7B658"

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C534B3.40D7B658
Content-Type: text/plain

Hi Kent, 

 

Sending comments to the rest of your questions. 

 

-----Original Message-----
From: Kent Leung [mailto:kleung@cisco.com] 
Sent: Wednesday, March 23, 2005 7:06 PM
To: Nakhjiri Madjid-MNAKHJI1
Cc: mip4@ietf.org; Nakhjiri Madjid-MNAKHJI1; kchowdhury@starentnetworks.com; avi@bridgewatersystems.com
Subject: Re: [Mip4] draft on RADIUS support for Mobile IP

 

<snip>

17) Sect 4.2, "the HA and FA may send their own IP addresses inside NAS-IP
      instead of MIP-[HA|FA]-IP-address".  I think the MIP-[HA|FA] identifiers should
      always be in the Access Req.

 

Madjid>>That would make sense to Mobile IP folks, but I am not if RADIUS folks would be happy if their message needs to carry two attributes with different names carrying the same info. Here is a question: Diameter has the notion of "applications", Mobile IP is an application for Diameter. If the server knows you are running the Mobile IP application, then depending on the message, it knows it is coming from a client that is also a mobile IP agent. In RADIUS you cannot define new messages, so we need to ask the question of whether the RADIUS server needs to know if a NAS is an FA or an HA. If we decide that distinguishing of FA and HA is important for the operations here (I think it is, then we need to change this statement. I put a comment in that effect there.

(By receiving the Mobile IP related RADIUS attributes, the server will know that it is receiving Access Requests from a NAS that is also a Mobile IP agent. If it is shown that the RADIUS server need to be able to distinguish an FA and an HA, then the MIP-HA-IP-address or MIP-FA-IP-address attributes need to also be included)

what do you think?

18) Sect 5, MIP-HA-IP address, why "the FA this attribute MAY not be used in
      the Access-Request"?  The HA address could be helpful to for setting up FA-HA
      MSA.

 

Madjid>> based on what we just said, I cannot remember why we added that statement. I will mark it for now and if it is needed, I remove the text.

 



19) MIP-MN-AAA-SPI, String should be unsigned32 and Length should be 6.
Madjid>>thanks, good point. Changed all the SPIs accordingly.


20) Mobile IPv4 feature vector, if mapping to DIAMETER, then this should be unsigned32.
     The "8-bit flag vector" should be called "bitflag vector" as current allocation is already
     over 8 bits.  :)  Length would be 6.  



Madjid>>checked the Diameter MIP, true. Changed accordingly. Thanks. 

 

Why not unsigned8, by the way?


21) Why bit 8 Foreign-Home-Agent-Available not supported?  This could be set by
      FA to notify to AAAH that AAAL can assign the HA when relaying the Access-Accept.
      I'm not clear on usage of bit 2 Home-Address-Allocatable-Only-in-Home-Realm.
      Also, I'm not sure why we don't have bitflag to indicate if the Access-Request is
      sent by FA or HA?  That might clarify some operations on the AAA server?
      Let's say the Access-Request contains the NAS-IP for authentication between NAS
      and AAA server and FA and HA identifiers to set up MSA, shouldn't AAA need to
      know which is FA or HA to set up the directional SPI for MSA?



Madjid>>We are not against any of that, we were just keeping things simple until we make sure  our suggested operation suggested that. Come to think about it, no harm in defining the attributes before hand. Done.


22) MIP-MN-to-HA SPI and MIP-HA-to-MN-SPI , String should be unsigned32 and length is 6.
Madjid>>done.
23) MIP-MN-HA-ALGID, not clear how algorithm identifier is mapped?  We have keyed MD5
      and HMAC-MD5.  Having a string doesn't make sense.  Maybe unsigned8 and specify
      1 for keyed MD5 and 2 for HMAC-MD5?



Madjid>>The strings are the products of cut and paste before the deadline phenomenon :-)

Will change to unsigned8. do you want a table with identifier values? Isn't SHA1 becoming popular now?

Should I have separate values for HMAC-MD5 and MD5? Do people do MD5 alone?


24) MIP-MN-HA-REP, same issue with string.  Maybe unsigned8 and specifiy 1 for
      timestamp (with field for replay range) and 2 for nonce?

 

Madjid>>done.



25) MIP-MN-HA-MSA-LIFE, integer should be unsigned32 and length is 6.  Should we
     allow 0xFFFFFFFF to mean infinite lifetime for MSA?  This means the MSA remains
     for lifetime of one registration session (MSA deleted when registration ends).



Madjid>>done. Not sure about the infinite lifetime. I am wondering in general who determines and enforces these lifetimes? How do you know whether an MSA belongs to this session or the previous one? And why would the MSA be valid only for one registration?


26) Remove bunch of AVPs above the format of FA to HA SPI.



Madjid>> not sure if I follow??


27) FA to HA SPI and HA to FA SPI, string is unsigned32 and length is 6.
Madjid>>done.


28) Would like to add new MIP-FA-HA-nonce AVP.
Madjid>>see my previous comments on FA-HA nonce versus FA-HA SPI.


29) In 5.1, attribute list is missing MIP-FA-NAI,

Madjid>> added

MIP-MN-HA SPI and MIP-HA-to-MN-SPI should change "HA" to "FA" 

Madjid>>good catch on my cut and pastes. Thanks.

 

before "Encrypted", missing Encrypted[MIP-MN-FA-key],

Madjid>>done.


      new MIP-FA-HA-nonce, duplicate MIP-MN-HA-MSA-LIFE.



Madjid>>previous comment. Fixed duplicate.


30) Sect 8, "We recommend that the AAAH also authenticates the nonce reply
     extensions with the AAA SA it shares with the MN".  This is for MITM attack for
     msg from AAAH to HA/FA.  Doesn't the Message-Authenticator protect tampering
     with the nonce value?
Madjid>> only from HA to MN, not over RADIUS from AAAH to MIP agents, at least, I think this is what I meant.


Kent

At 06:56 PM 2/7/2005 -0600, Nakhjiri Madjid-MNAKHJI1 wrote:




Hi folks,

 

Just wanted to let you know that we just submitted a draft proposing an specification for support of RADIUS for Mobile IP key management procedures. The draft goes through two cases of co-located mobile nodes and nodes behind an FA and describes RADIUS messaging and attributes for each case. Since the draft deals with both Mobile IPv4 and RADIUS, it needs to be examined by both groups. We know that this is really more an extension to RADIUS than to Mobile IP and should be standardized by RADIUS groups, but we would like to make sure that we got the Mobile IP parts right first :-).

 

So comments and guidance are very welcome.

 

Thanks and Regards,

 

Madjid Nakhjiri, Kuntal Chowdhury, Avi Lior

 

 

The draft can be found at 

 

http://www.ietf.org/internet-drafts/draft-nakhjiri-radius-mip4-00.txt <http://www.ietf.org/internet-drafts/draft-nakhjiri-radius-mip4-00.txt> 

 

    

Abstract 

    

   Mobile IPv4 specifies mechanisms that need assistance from a AAA 

   server and a AAA infrastructure. Examples of such mechanisms are 

   those providing key management and authentication services during a 

   mobile node's registration process with MN-AAA authentication 

   extension. Although Diameter Mobile IP application is being specified 

   to support the needs of Mobile IPv4 from the AAA infrastructure's 

   point of view, such support does not exist within RADIUS framework. 

   This document defines the RADIUS attributes that provide support for 

   Mobile IPv4 operation. 

 

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

 

--

     |           |                   Kent Leung

    :|:         :|:                  IP Mobility Development

   :|||:       :|||:                 Internet Technologies Division

  :|||||||:   :|||||||:              Voice: 408.526.5030

.:|||||||||:.:|||||||||:.             Fax:   408.525.1653

 c i s c o S y s t e m s             Email: kleung@cisco.com 


------_=_NextPart_001_01C534B3.40D7B658
Content-Type: text/html
Content-Transfer-Encoding: base64

PGh0bWw+DQoNCjxoZWFkPg0KPE1FVEEgSFRUUC1FUVVJVj0iQ29udGVudC1UeXBlIiBDT05URU5U
PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXMtYXNjaWkiPg0KDQoNCjxtZXRhIG5hbWU9R2VuZXJhdG9y
IGNvbnRlbnQ9Ik1pY3Jvc29mdCBXb3JkIDEwIChmaWx0ZXJlZCkiPg0KDQo8c3R5bGU+DQo8IS0t
DQogLyogRm9udCBEZWZpbml0aW9ucyAqLw0KIEBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6V2lu
Z2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseTpUYWhvbWE7DQoJcGFub3NlLTE6MiAxMSA2IDQgMyA1IDQgNCAyIDQ7fQ0KIC8q
IFN0eWxlIERlZmluaXRpb25zICovDQogcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z
b05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iO30NCmE6bGluaywgc3Bh
bi5Nc29IeXBlcmxpbmsNCgl7Y29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5l
O30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXtjb2xvcjpibHVlOw0K
CXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcNCgl7Zm9udC1m
YW1pbHk6QXJpYWw7DQoJY29sb3I6bmF2eTt9DQpAcGFnZSBTZWN0aW9uMQ0KCXtzaXplOjguNWlu
IDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4yNWluIDEuMGluIDEuMjVpbjt9DQpkaXYuU2VjdGlv
bjENCgl7cGFnZTpTZWN0aW9uMTt9DQotLT4NCjwvc3R5bGU+DQoNCjwvaGVhZD4NCg0KPGJvZHkg
bGFuZz1FTi1VUyBsaW5rPWJsdWUgdmxpbms9Ymx1ZT4NCg0KPGRpdiBjbGFzcz1TZWN0aW9uMT4N
Cg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxmb250IHNpemU9MiBjb2xvcj1uYXZ5IGZhY2U9QXJpYWw+
PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToNCjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDtjb2xvcjpu
YXZ5Jz5IaSBLZW50LCA8L3NwYW4+PC9mb250PjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxm
b250IHNpemU9MiBjb2xvcj1uYXZ5IGZhY2U9QXJpYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToN
CjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDtjb2xvcjpuYXZ5Jz4mbmJzcDs8L3NwYW4+PC9mb250
PjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxmb250IHNpemU9MiBjb2xvcj1uYXZ5IGZhY2U9
QXJpYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToNCjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDtj
b2xvcjpuYXZ5Jz5TZW5kaW5nIGNvbW1lbnRzIHRvIHRoZSByZXN0IG9mIHlvdXINCnF1ZXN0aW9u
cy4gPC9zcGFuPjwvZm9udD48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48Zm9udCBzaXplPTIg
Y29sb3I9bmF2eSBmYWNlPUFyaWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6DQoxMC4wcHQ7Zm9u
dC1mYW1pbHk6QXJpYWw7Y29sb3I6bmF2eSc+Jm5ic3A7PC9zcGFuPjwvZm9udD48L3A+DQoNCjxw
IGNsYXNzPU1zb05vcm1hbD48Zm9udCBzaXplPTIgZmFjZT1UYWhvbWE+PHNwYW4gc3R5bGU9J2Zv
bnQtc2l6ZToxMC4wcHQ7DQpmb250LWZhbWlseTpUYWhvbWEnPi0tLS0tT3JpZ2luYWwgTWVzc2Fn
ZS0tLS0tPGJyPg0KPGI+PHNwYW4gc3R5bGU9J2ZvbnQtd2VpZ2h0OmJvbGQnPkZyb206PC9zcGFu
PjwvYj4gS2VudCBMZXVuZw0KW21haWx0bzprbGV1bmdAY2lzY28uY29tXSA8YnI+DQo8Yj48c3Bh
biBzdHlsZT0nZm9udC13ZWlnaHQ6Ym9sZCc+U2VudDo8L3NwYW4+PC9iPiBXZWRuZXNkYXksIE1h
cmNoIDIzLCAyMDA1DQo3OjA2IFBNPGJyPg0KPGI+PHNwYW4gc3R5bGU9J2ZvbnQtd2VpZ2h0OmJv
bGQnPlRvOjwvc3Bhbj48L2I+IE5ha2hqaXJpIE1hZGppZC1NTkFLSEpJMTxicj4NCjxiPjxzcGFu
IHN0eWxlPSdmb250LXdlaWdodDpib2xkJz5DYzo8L3NwYW4+PC9iPiBtaXA0QGlldGYub3JnOyBO
YWtoamlyaQ0KTWFkamlkLU1OQUtISkkxOyBrY2hvd2RodXJ5QHN0YXJlbnRuZXR3b3Jrcy5jb207
IGF2aUBicmlkZ2V3YXRlcnN5c3RlbXMuY29tPGJyPg0KPGI+PHNwYW4gc3R5bGU9J2ZvbnQtd2Vp
Z2h0OmJvbGQnPlN1YmplY3Q6PC9zcGFuPjwvYj4gUmU6IFtNaXA0XSBkcmFmdCBvbg0KUkFESVVT
IHN1cHBvcnQgZm9yIE1vYmlsZSBJUDwvc3Bhbj48L2ZvbnQ+PC9wPg0KDQo8cCBjbGFzcz1Nc29O
b3JtYWw+PGZvbnQgc2l6ZT0zIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+PHNwYW4gc3R5bGU9J2Zv
bnQtc2l6ZToNCjEyLjBwdCc+Jm5ic3A7PC9zcGFuPjwvZm9udD48L3A+DQoNCjxwIGNsYXNzPU1z
b05vcm1hbD48Zm9udCBzaXplPTMgY29sb3I9bmF2eSBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPjxz
cGFuDQpzdHlsZT0nZm9udC1zaXplOjEyLjBwdDtjb2xvcjpuYXZ5Jz4mbHQ7c25pcCZndDs8L3Nw
YW4+PC9mb250Pjxicj4NCjxicj4NCjE3KSBTZWN0IDQuMiwgJnF1b3Q7dGhlIEhBIGFuZCBGQSBt
YXkgc2VuZCB0aGVpciBvd24gSVAgYWRkcmVzc2VzIGluc2lkZSBOQVMtSVA8YnI+DQombmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgaW5zdGVhZCBvZiBNSVAtW0hBfEZBXS1JUC1hZGRyZXNz
JnF1b3Q7LiZuYnNwOyBJDQp0aGluayB0aGUgTUlQLVtIQXxGQV0gaWRlbnRpZmllcnMgc2hvdWxk
PGJyPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGFsd2F5cyBiZSBpbiB0aGUgQWNj
ZXNzIFJlcS48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48Zm9udCBzaXplPTIgY29sb3I9bmF2
eSBmYWNlPUFyaWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6DQoxMC4wcHQ7Zm9udC1mYW1pbHk6
QXJpYWw7Y29sb3I6bmF2eSc+Jm5ic3A7PC9zcGFuPjwvZm9udD48L3A+DQoNCjxwIGNsYXNzPU1z
b05vcm1hbD48Zm9udCBzaXplPTIgY29sb3I9bmF2eSBmYWNlPUFyaWFsPjxzcGFuIHN0eWxlPSdm
b250LXNpemU6DQoxMC4wcHQ7Zm9udC1mYW1pbHk6QXJpYWw7Y29sb3I6bmF2eSc+TWFkamlkJmd0
OyZndDtUaGF0IHdvdWxkIG1ha2Ugc2Vuc2UgdG8NCk1vYmlsZSBJUCBmb2xrcywgYnV0IEkgYW0g
bm90IGlmIFJBRElVUyBmb2xrcyB3b3VsZCBiZSBoYXBweSBpZiB0aGVpciBtZXNzYWdlDQpuZWVk
cyB0byBjYXJyeSB0d28gYXR0cmlidXRlcyB3aXRoIGRpZmZlcmVudCBuYW1lcyBjYXJyeWluZyB0
aGUgc2FtZSBpbmZvLiBIZXJlDQppcyBhIHF1ZXN0aW9uOiBEaWFtZXRlciBoYXMgdGhlIG5vdGlv
biBvZiAiYXBwbGljYXRpb25zIiwgTW9iaWxlIElQDQppcyBhbiBhcHBsaWNhdGlvbiBmb3IgRGlh
bWV0ZXIuIElmIHRoZSBzZXJ2ZXIga25vd3MgeW91IGFyZSBydW5uaW5nIHRoZSBNb2JpbGUNCklQ
IGFwcGxpY2F0aW9uLCB0aGVuIGRlcGVuZGluZyBvbiB0aGUgbWVzc2FnZSwgaXQga25vd3MgaXQg
aXMgY29taW5nIGZyb20gYQ0KY2xpZW50IHRoYXQgaXMgYWxzbyBhIG1vYmlsZSBJUCBhZ2VudC4g
SW4gUkFESVVTIHlvdSBjYW5ub3QgZGVmaW5lIG5ldyBtZXNzYWdlcywNCnNvIHdlIG5lZWQgdG8g
YXNrIHRoZSBxdWVzdGlvbiBvZiB3aGV0aGVyIHRoZSBSQURJVVMgc2VydmVyIG5lZWRzIHRvIGtu
b3cgaWYgYQ0KTkFTIGlzIGFuIEZBIG9yIGFuIEhBLiBJZiB3ZSBkZWNpZGUgdGhhdCBkaXN0aW5n
dWlzaGluZyBvZiBGQSBhbmQgSEEgaXMNCmltcG9ydGFudCBmb3IgdGhlIG9wZXJhdGlvbnMgaGVy
ZSAoSSB0aGluayBpdCBpcywgdGhlbiB3ZSBuZWVkIHRvIGNoYW5nZSB0aGlzDQpzdGF0ZW1lbnQu
IEkgcHV0IGEgY29tbWVudCBpbiB0aGF0IGVmZmVjdCB0aGVyZS48L3NwYW4+PC9mb250PjwvcD4N
Cg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxmb250IHNpemU9MyBmYWNlPSJUaW1lcyBOZXcgUm9tYW4i
PjxzcGFuIHN0eWxlPSdmb250LXNpemU6DQoxMi4wcHQnPig8Zm9udCBjb2xvcj1yZWQ+PHNwYW4g
c3R5bGU9J2NvbG9yOnJlZCc+QnkgcmVjZWl2aW5nIHRoZSBNb2JpbGUgSVANCnJlbGF0ZWQgUkFE
SVVTIGF0dHJpYnV0ZXMsIHRoZSBzZXJ2ZXIgd2lsbCBrbm93IHRoYXQgaXQgaXMgcmVjZWl2aW5n
IEFjY2Vzcw0KUmVxdWVzdHMgZnJvbSBhIE5BUyB0aGF0IGlzIGFsc28gYSBNb2JpbGUgSVAgYWdl
bnQuIElmIGl0IGlzIHNob3duIHRoYXQgdGhlIFJBRElVUw0Kc2VydmVyIG5lZWQgdG8gYmUgYWJs
ZSB0byBkaXN0aW5ndWlzaCBhbiBGQSBhbmQgYW4gSEEsIHRoZW4gdGhlDQpNSVAtSEEtSVAtYWRk
cmVzcyBvciBNSVAtRkEtSVAtYWRkcmVzcyBhdHRyaWJ1dGVzIG5lZWQgdG8gYWxzbyBiZSBpbmNs
dWRlZDwvc3Bhbj48L2ZvbnQ+KTwvc3Bhbj48L2ZvbnQ+PC9wPg0KDQo8cCBjbGFzcz1Nc29Ob3Jt
YWw+PGZvbnQgc2l6ZT0zIGNvbG9yPW5hdnkgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj48c3Bhbg0K
c3R5bGU9J2ZvbnQtc2l6ZToxMi4wcHQ7Y29sb3I6bmF2eSc+d2hhdCBkbyB5b3UgdGhpbms/PC9z
cGFuPjwvZm9udD48YnI+DQo8YnI+DQoxOCkgU2VjdCA1LCBNSVAtSEEtSVAgYWRkcmVzcywgd2h5
ICZxdW90O3RoZSBGQSB0aGlzIGF0dHJpYnV0ZSBNQVkgbm90IGJlIHVzZWQNCmluPGJyPg0KJm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHRoZSBBY2Nlc3MtUmVxdWVzdCZxdW90Oz8mbmJz
cDsgVGhlIEhBIGFkZHJlc3MNCmNvdWxkIGJlIGhlbHBmdWwgdG8gZm9yIHNldHRpbmcgdXAgRkEt
SEE8YnI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgTVNBLjwvcD4NCg0KPHAgY2xh
c3M9TXNvTm9ybWFsPjxmb250IHNpemU9MiBjb2xvcj1uYXZ5IGZhY2U9QXJpYWw+PHNwYW4gc3R5
bGU9J2ZvbnQtc2l6ZToNCjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDtjb2xvcjpuYXZ5Jz4mbmJz
cDs8L3NwYW4+PC9mb250PjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxmb250IHNpemU9MiBj
b2xvcj1uYXZ5IGZhY2U9QXJpYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToNCjEwLjBwdDtmb250
LWZhbWlseTpBcmlhbDtjb2xvcjpuYXZ5Jz5NYWRqaWQmZ3Q7Jmd0OyBiYXNlZCBvbiB3aGF0IHdl
IGp1c3Qgc2FpZCwNCkkgY2Fubm90IHJlbWVtYmVyIHdoeSB3ZSBhZGRlZCB0aGF0IHN0YXRlbWVu
dC4gSSB3aWxsIG1hcmsgaXQgZm9yIG5vdyBhbmQgaWYgaXQNCmlzIG5lZWRlZCwgSSByZW1vdmUg
dGhlIHRleHQuPC9zcGFuPjwvZm9udD48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48Zm9udCBz
aXplPTIgY29sb3I9bmF2eSBmYWNlPUFyaWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6DQoxMC4w
cHQ7Zm9udC1mYW1pbHk6QXJpYWw7Y29sb3I6bmF2eSc+Jm5ic3A7PC9zcGFuPjwvZm9udD48L3A+
DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48Zm9udCBzaXplPTMgZmFjZT0iVGltZXMgTmV3IFJvbWFu
Ij48c3BhbiBzdHlsZT0nZm9udC1zaXplOg0KMTIuMHB0Jz48YnI+DQo8YnI+DQoxOSkgTUlQLU1O
LUFBQS1TUEksIFN0cmluZyBzaG91bGQgYmUgdW5zaWduZWQzMiBhbmQgTGVuZ3RoIHNob3VsZCBi
ZSA2Ljxicj4NCjxmb250IGNvbG9yPW5hdnk+PHNwYW4gc3R5bGU9J2NvbG9yOm5hdnknPk1hZGpp
ZCZndDsmZ3Q7dGhhbmtzLCBnb29kIHBvaW50Lg0KQ2hhbmdlZCBhbGwgdGhlIFNQSXMgYWNjb3Jk
aW5nbHkuPC9zcGFuPjwvZm9udD48L3NwYW4+PC9mb250PjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9y
bWFsPjxmb250IHNpemU9MyBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPjxzcGFuIHN0eWxlPSdmb250
LXNpemU6DQoxMi4wcHQnPjxicj4NCjIwKSBNb2JpbGUgSVB2NCBmZWF0dXJlIHZlY3RvciwgaWYg
bWFwcGluZyB0byBESUFNRVRFUiwgdGhlbiB0aGlzIHNob3VsZCBiZQ0KdW5zaWduZWQzMi48YnI+
DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgVGhlICZxdW90OzgtYml0IGZsYWcgdmVjdG9yJnF1
b3Q7IHNob3VsZCBiZSBjYWxsZWQNCiZxdW90O2JpdGZsYWcgdmVjdG9yJnF1b3Q7IGFzIGN1cnJl
bnQgYWxsb2NhdGlvbiBpcyBhbHJlYWR5PGJyPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IG92
ZXIgOCBiaXRzLiZuYnNwOyA6KSZuYnNwOyBMZW5ndGggd291bGQgYmUgNi4mbmJzcDsgPGJyPg0K
PGJyPg0KPC9zcGFuPjwvZm9udD48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48Zm9udCBzaXpl
PTIgY29sb3I9bmF2eSBmYWNlPUFyaWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6DQoxMC4wcHQ7
Zm9udC1mYW1pbHk6QXJpYWw7Y29sb3I6bmF2eSc+TWFkamlkJmd0OyZndDtjaGVja2VkIHRoZSBE
aWFtZXRlciBNSVAsDQp0cnVlLiBDaGFuZ2VkIGFjY29yZGluZ2x5LiBUaGFua3MuIDwvc3Bhbj48
L2ZvbnQ+PC9wPg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PGZvbnQgc2l6ZT0yIGNvbG9yPW5hdnkg
ZmFjZT1BcmlhbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOg0KMTAuMHB0O2ZvbnQtZmFtaWx5OkFy
aWFsO2NvbG9yOm5hdnknPiZuYnNwOzwvc3Bhbj48L2ZvbnQ+PC9wPg0KDQo8cCBjbGFzcz1Nc29O
b3JtYWw+PGZvbnQgc2l6ZT0yIGNvbG9yPW5hdnkgZmFjZT1BcmlhbD48c3BhbiBzdHlsZT0nZm9u
dC1zaXplOg0KMTAuMHB0O2ZvbnQtZmFtaWx5OkFyaWFsO2NvbG9yOm5hdnknPldoeSBub3QgdW5z
aWduZWQ4LCBieSB0aGUgd2F5Pzwvc3Bhbj48L2ZvbnQ+PC9wPg0KDQo8cCBjbGFzcz1Nc29Ob3Jt
YWw+PGZvbnQgc2l6ZT0zIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+PHNwYW4gc3R5bGU9J2ZvbnQt
c2l6ZToNCjEyLjBwdCc+PGJyPg0KMjEpIFdoeSBiaXQgOCBGb3JlaWduLUhvbWUtQWdlbnQtQXZh
aWxhYmxlIG5vdCBzdXBwb3J0ZWQ/Jm5ic3A7IFRoaXMgY291bGQgYmUNCnNldCBieTxicj4NCiZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBGQSB0byBub3RpZnkgdG8gQUFBSCB0aGF0IEFB
QUwgY2FuIGFzc2lnbiB0aGUgSEENCndoZW4gcmVsYXlpbmcgdGhlIEFjY2Vzcy1BY2NlcHQuPGJy
Pg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IEknbSBub3QgY2xlYXIgb24gdXNhZ2Ug
b2YgYml0IDINCkhvbWUtQWRkcmVzcy1BbGxvY2F0YWJsZS1Pbmx5LWluLUhvbWUtUmVhbG0uPGJy
Pg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IEFsc28sIEknbSBub3Qgc3VyZSB3aHkg
d2UgZG9uJ3QgaGF2ZSBiaXRmbGFnIHRvDQppbmRpY2F0ZSBpZiB0aGUgQWNjZXNzLVJlcXVlc3Qg
aXM8YnI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgc2VudCBieSBGQSBvciBIQT8m
bmJzcDsgVGhhdCBtaWdodCBjbGFyaWZ5IHNvbWUNCm9wZXJhdGlvbnMgb24gdGhlIEFBQSBzZXJ2
ZXI/PGJyPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IExldCdzIHNheSB0aGUgQWNj
ZXNzLVJlcXVlc3QgY29udGFpbnMgdGhlIE5BUy1JUA0KZm9yIGF1dGhlbnRpY2F0aW9uIGJldHdl
ZW4gTkFTPGJyPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGFuZCBBQUEgc2VydmVy
IGFuZCBGQSBhbmQgSEEgaWRlbnRpZmllcnMgdG8gc2V0DQp1cCBNU0EsIHNob3VsZG4ndCBBQUEg
bmVlZCB0bzxicj4NCiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBrbm93IHdoaWNoIGlz
IEZBIG9yIEhBIHRvIHNldCB1cCB0aGUgZGlyZWN0aW9uYWwNClNQSSBmb3IgTVNBPzxicj4NCjxi
cj4NCjwvc3Bhbj48L2ZvbnQ+PC9wPg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PGZvbnQgc2l6ZT0y
IGNvbG9yPW5hdnkgZmFjZT1BcmlhbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOg0KMTAuMHB0O2Zv
bnQtZmFtaWx5OkFyaWFsO2NvbG9yOm5hdnknPk1hZGppZCZndDsmZ3Q7V2UgYXJlIG5vdCBhZ2Fp
bnN0IGFueSBvZg0KdGhhdCwgd2Ugd2VyZSBqdXN0IGtlZXBpbmcgdGhpbmdzIHNpbXBsZSB1bnRp
bCB3ZSBtYWtlIHN1cmUmbmJzcDsgb3VyIHN1Z2dlc3RlZA0Kb3BlcmF0aW9uIHN1Z2dlc3RlZCB0
aGF0LiBDb21lIHRvIHRoaW5rIGFib3V0IGl0LCBubyBoYXJtIGluIGRlZmluaW5nIHRoZQ0KYXR0
cmlidXRlcyBiZWZvcmUgaGFuZC4gRG9uZS48L3NwYW4+PC9mb250PjwvcD4NCg0KPHAgY2xhc3M9
TXNvTm9ybWFsPjxmb250IHNpemU9MyBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPjxzcGFuIHN0eWxl
PSdmb250LXNpemU6DQoxMi4wcHQnPjxicj4NCjIyKSBNSVAtTU4tdG8tSEEgU1BJIGFuZCBNSVAt
SEEtdG8tTU4tU1BJICwgU3RyaW5nIHNob3VsZCBiZSB1bnNpZ25lZDMyIGFuZA0KbGVuZ3RoIGlz
IDYuPGJyPg0KPGZvbnQgY29sb3I9bmF2eT48c3BhbiBzdHlsZT0nY29sb3I6bmF2eSc+TWFkamlk
Jmd0OyZndDtkb25lLjwvc3Bhbj48L2ZvbnQ+PGJyPg0KMjMpIE1JUC1NTi1IQS1BTEdJRCwgbm90
IGNsZWFyIGhvdyBhbGdvcml0aG0gaWRlbnRpZmllciBpcyBtYXBwZWQ/Jm5ic3A7IFdlDQpoYXZl
IGtleWVkIE1ENTxicj4NCiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBhbmQgSE1BQy1N
RDUuJm5ic3A7IEhhdmluZyBhIHN0cmluZyBkb2Vzbid0IG1ha2UNCnNlbnNlLiZuYnNwOyBNYXli
ZSB1bnNpZ25lZDggYW5kIHNwZWNpZnk8YnI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsgMSBmb3Iga2V5ZWQgTUQ1IGFuZCAyIGZvciBITUFDLU1ENT88YnI+DQo8YnI+DQo8L3NwYW4+
PC9mb250PjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxmb250IHNpemU9MiBjb2xvcj1uYXZ5
IGZhY2U9QXJpYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToNCjEwLjBwdDtmb250LWZhbWlseTpB
cmlhbDtjb2xvcjpuYXZ5Jz5NYWRqaWQmZ3Q7Jmd0O1RoZSBzdHJpbmdzIGFyZSB0aGUgcHJvZHVj
dHMNCm9mIGN1dCBhbmQgcGFzdGUgYmVmb3JlIHRoZSBkZWFkbGluZSBwaGVub21lbm9uIDwvc3Bh
bj48L2ZvbnQ+PGZvbnQgc2l6ZT0yDQpjb2xvcj1uYXZ5IGZhY2U9V2luZ2RpbmdzPjxzcGFuIHN0
eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OldpbmdkaW5nczsNCmNvbG9yOm5hdnkn
Pko8L3NwYW4+PC9mb250PjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxmb250IHNpemU9MiBj
b2xvcj1uYXZ5IGZhY2U9QXJpYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToNCjEwLjBwdDtmb250
LWZhbWlseTpBcmlhbDtjb2xvcjpuYXZ5Jz5XaWxsIGNoYW5nZSB0byB1bnNpZ25lZDguIGRvIHlv
dSB3YW50IGENCnRhYmxlIHdpdGggaWRlbnRpZmllciB2YWx1ZXM/IElzbid0IFNIQTEgYmVjb21p
bmcgcG9wdWxhciBub3c/PC9zcGFuPjwvZm9udD48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48
Zm9udCBzaXplPTIgY29sb3I9bmF2eSBmYWNlPUFyaWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6
DQoxMC4wcHQ7Zm9udC1mYW1pbHk6QXJpYWw7Y29sb3I6bmF2eSc+U2hvdWxkIEkgaGF2ZSBzZXBh
cmF0ZSB2YWx1ZXMgZm9yIEhNQUMtTUQ1DQphbmQgTUQ1PyBEbyBwZW9wbGUgZG8gTUQ1IGFsb25l
Pzwvc3Bhbj48L2ZvbnQ+PC9wPg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PGZvbnQgc2l6ZT0zIGZh
Y2U9IlRpbWVzIE5ldyBSb21hbiI+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToNCjEyLjBwdCc+PGJy
Pg0KMjQpIE1JUC1NTi1IQS1SRVAsIHNhbWUgaXNzdWUgd2l0aCBzdHJpbmcuJm5ic3A7IE1heWJl
IHVuc2lnbmVkOCBhbmQgc3BlY2lmaXkgMQ0KZm9yPGJyPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7IHRpbWVzdGFtcCAod2l0aCBmaWVsZCBmb3IgcmVwbGF5IHJhbmdlKSBhbmQgMg0K
Zm9yIG5vbmNlPzwvc3Bhbj48L2ZvbnQ+PC9wPg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PGZvbnQg
c2l6ZT0yIGNvbG9yPW5hdnkgZmFjZT1BcmlhbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOg0KMTAu
MHB0O2ZvbnQtZmFtaWx5OkFyaWFsO2NvbG9yOm5hdnknPiZuYnNwOzwvc3Bhbj48L2ZvbnQ+PC9w
Pg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PGZvbnQgc2l6ZT0yIGNvbG9yPW5hdnkgZmFjZT1Bcmlh
bD48c3BhbiBzdHlsZT0nZm9udC1zaXplOg0KMTAuMHB0O2ZvbnQtZmFtaWx5OkFyaWFsO2NvbG9y
Om5hdnknPk1hZGppZCZndDsmZ3Q7ZG9uZS48L3NwYW4+PC9mb250PjwvcD4NCg0KPHAgY2xhc3M9
TXNvTm9ybWFsPjxmb250IHNpemU9MyBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPjxzcGFuIHN0eWxl
PSdmb250LXNpemU6DQoxMi4wcHQnPjxicj4NCjxicj4NCjI1KSBNSVAtTU4tSEEtTVNBLUxJRkUs
IGludGVnZXIgc2hvdWxkIGJlIHVuc2lnbmVkMzIgYW5kIGxlbmd0aCBpcyA2LiZuYnNwOw0KU2hv
dWxkIHdlPGJyPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGFsbG93IDB4RkZGRkZGRkYgdG8g
bWVhbiBpbmZpbml0ZSBsaWZldGltZSBmb3INCk1TQT8mbmJzcDsgVGhpcyBtZWFucyB0aGUgTVNB
IHJlbWFpbnM8YnI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZm9yIGxpZmV0aW1lIG9mIG9u
ZSByZWdpc3RyYXRpb24gc2Vzc2lvbiAoTVNBIGRlbGV0ZWQNCndoZW4gcmVnaXN0cmF0aW9uIGVu
ZHMpLjxicj4NCjxicj4NCjwvc3Bhbj48L2ZvbnQ+PC9wPg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+
PGZvbnQgc2l6ZT0yIGNvbG9yPW5hdnkgZmFjZT1BcmlhbD48c3BhbiBzdHlsZT0nZm9udC1zaXpl
Og0KMTAuMHB0O2ZvbnQtZmFtaWx5OkFyaWFsO2NvbG9yOm5hdnknPk1hZGppZCZndDsmZ3Q7ZG9u
ZS4gTm90IHN1cmUgYWJvdXQgdGhlDQppbmZpbml0ZSBsaWZldGltZS4gSSBhbSB3b25kZXJpbmcg
aW4gZ2VuZXJhbCB3aG8gZGV0ZXJtaW5lcyBhbmQgZW5mb3JjZXMgdGhlc2UNCmxpZmV0aW1lcz8g
SG93IGRvIHlvdSBrbm93IHdoZXRoZXIgYW4gTVNBIGJlbG9uZ3MgdG8gdGhpcyBzZXNzaW9uIG9y
IHRoZQ0KcHJldmlvdXMgb25lPyBBbmQgd2h5IHdvdWxkIHRoZSBNU0EgYmUgdmFsaWQgb25seSBm
b3Igb25lIHJlZ2lzdHJhdGlvbj88L3NwYW4+PC9mb250PjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9y
bWFsPjxmb250IHNpemU9MyBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPjxzcGFuIHN0eWxlPSdmb250
LXNpemU6DQoxMi4wcHQnPjxicj4NCjI2KSBSZW1vdmUgYnVuY2ggb2YgQVZQcyBhYm92ZSB0aGUg
Zm9ybWF0IG9mIEZBIHRvIEhBIFNQSS48YnI+DQo8YnI+DQo8L3NwYW4+PC9mb250PjwvcD4NCg0K
PHAgY2xhc3M9TXNvTm9ybWFsPjxmb250IHNpemU9MiBjb2xvcj1uYXZ5IGZhY2U9QXJpYWw+PHNw
YW4gc3R5bGU9J2ZvbnQtc2l6ZToNCjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDtjb2xvcjpuYXZ5
Jz5NYWRqaWQmZ3Q7Jmd0OyBub3Qgc3VyZSBpZiBJIGZvbGxvdz8/PC9zcGFuPjwvZm9udD48L3A+
DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48Zm9udCBzaXplPTMgZmFjZT0iVGltZXMgTmV3IFJvbWFu
Ij48c3BhbiBzdHlsZT0nZm9udC1zaXplOg0KMTIuMHB0Jz48YnI+DQoyNykgRkEgdG8gSEEgU1BJ
IGFuZCBIQSB0byBGQSBTUEksIHN0cmluZyBpcyB1bnNpZ25lZDMyIGFuZCBsZW5ndGggaXMgNi48
YnI+DQo8Zm9udCBjb2xvcj1uYXZ5PjxzcGFuIHN0eWxlPSdjb2xvcjpuYXZ5Jz5NYWRqaWQmZ3Q7
Jmd0O2RvbmUuPC9zcGFuPjwvZm9udD48L3NwYW4+PC9mb250PjwvcD4NCg0KPHAgY2xhc3M9TXNv
Tm9ybWFsPjxmb250IHNpemU9MyBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPjxzcGFuIHN0eWxlPSdm
b250LXNpemU6DQoxMi4wcHQnPjxicj4NCjI4KSBXb3VsZCBsaWtlIHRvIGFkZCBuZXcgTUlQLUZB
LUhBLW5vbmNlIEFWUC48YnI+DQo8Zm9udCBjb2xvcj1uYXZ5PjxzcGFuIHN0eWxlPSdjb2xvcjpu
YXZ5Jz5NYWRqaWQmZ3Q7Jmd0O3NlZSBteSBwcmV2aW91cw0KY29tbWVudHMgb24gRkEtSEEgbm9u
Y2UgdmVyc3VzIEZBLUhBIFNQSS48L3NwYW4+PC9mb250Pjwvc3Bhbj48L2ZvbnQ+PC9wPg0KDQo8
cCBjbGFzcz1Nc29Ob3JtYWw+PGZvbnQgc2l6ZT0zIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+PHNw
YW4gc3R5bGU9J2ZvbnQtc2l6ZToNCjEyLjBwdCc+PGJyPg0KMjkpIEluIDUuMSwgYXR0cmlidXRl
IGxpc3QgaXMgbWlzc2luZyBNSVAtRkEtTkFJLDwvc3Bhbj48L2ZvbnQ+PC9wPg0KDQo8cCBjbGFz
cz1Nc29Ob3JtYWw+PGZvbnQgc2l6ZT0yIGNvbG9yPW5hdnkgZmFjZT1BcmlhbD48c3BhbiBzdHls
ZT0nZm9udC1zaXplOg0KMTAuMHB0O2ZvbnQtZmFtaWx5OkFyaWFsO2NvbG9yOm5hdnknPk1hZGpp
ZCZndDsmZ3Q7IGFkZGVkPC9zcGFuPjwvZm9udD48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48
Zm9udCBzaXplPTMgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj48c3BhbiBzdHlsZT0nZm9udC1zaXpl
Og0KMTIuMHB0Jz5NSVAtTU4tSEEgU1BJIGFuZCBNSVAtSEEtdG8tTU4tU1BJIHNob3VsZCBjaGFu
Z2UgJnF1b3Q7SEEmcXVvdDsgdG8NCiZxdW90O0ZBJnF1b3Q7IDwvc3Bhbj48L2ZvbnQ+PC9wPg0K
DQo8cCBjbGFzcz1Nc29Ob3JtYWw+PGZvbnQgc2l6ZT0yIGNvbG9yPW5hdnkgZmFjZT1BcmlhbD48
c3BhbiBzdHlsZT0nZm9udC1zaXplOg0KMTAuMHB0O2ZvbnQtZmFtaWx5OkFyaWFsO2NvbG9yOm5h
dnknPk1hZGppZCZndDsmZ3Q7Z29vZCBjYXRjaCBvbiBteSBjdXQgYW5kDQpwYXN0ZXMuIFRoYW5r
cy48L3NwYW4+PC9mb250PjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxmb250IHNpemU9MiBj
b2xvcj1uYXZ5IGZhY2U9QXJpYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToNCjEwLjBwdDtmb250
LWZhbWlseTpBcmlhbDtjb2xvcjpuYXZ5Jz4mbmJzcDs8L3NwYW4+PC9mb250PjwvcD4NCg0KPHAg
Y2xhc3M9TXNvTm9ybWFsPjxmb250IHNpemU9MyBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPjxzcGFu
IHN0eWxlPSdmb250LXNpemU6DQoxMi4wcHQnPmJlZm9yZSAmcXVvdDtFbmNyeXB0ZWQmcXVvdDss
IG1pc3NpbmcgRW5jcnlwdGVkW01JUC1NTi1GQS1rZXldLDwvc3Bhbj48L2ZvbnQ+PC9wPg0KDQo8
cCBjbGFzcz1Nc29Ob3JtYWw+PGZvbnQgc2l6ZT0yIGNvbG9yPW5hdnkgZmFjZT1BcmlhbD48c3Bh
biBzdHlsZT0nZm9udC1zaXplOg0KMTAuMHB0O2ZvbnQtZmFtaWx5OkFyaWFsO2NvbG9yOm5hdnkn
Pk1hZGppZCZndDsmZ3Q7ZG9uZS48L3NwYW4+PC9mb250PjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9y
bWFsPjxmb250IHNpemU9MyBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPjxzcGFuIGxhbmc9SVQNCnN0
eWxlPSdmb250LXNpemU6MTIuMHB0Jz48YnI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsgbmV3IE1JUC1GQS1IQS1ub25jZSwgZHVwbGljYXRlDQpNSVAtTU4tSEEtTVNBLUxJRkUuPGJy
Pg0KPGJyPg0KPC9zcGFuPjwvZm9udD48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48Zm9udCBz
aXplPTIgY29sb3I9bmF2eSBmYWNlPUFyaWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6DQoxMC4w
cHQ7Zm9udC1mYW1pbHk6QXJpYWw7Y29sb3I6bmF2eSc+TWFkamlkJmd0OyZndDtwcmV2aW91cyBj
b21tZW50LiBGaXhlZCBkdXBsaWNhdGUuPC9zcGFuPjwvZm9udD48L3A+DQoNCjxwIGNsYXNzPU1z
b05vcm1hbD48Zm9udCBzaXplPTMgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj48c3BhbiBzdHlsZT0n
Zm9udC1zaXplOg0KMTIuMHB0Jz48YnI+DQozMCkgU2VjdCA4LCAmcXVvdDtXZSByZWNvbW1lbmQg
dGhhdCB0aGUgQUFBSCBhbHNvIGF1dGhlbnRpY2F0ZXMgdGhlIG5vbmNlIHJlcGx5PGJyPg0KJm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGV4dGVuc2lvbnMgd2l0aCB0aGUgQUFBIFNBIGl0IHNoYXJl
cyB3aXRoIHRoZQ0KTU4mcXVvdDsuJm5ic3A7IFRoaXMgaXMgZm9yIE1JVE0gYXR0YWNrIGZvcjxi
cj4NCiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBtc2cgZnJvbSBBQUFIIHRvIEhBL0ZBLiZuYnNw
OyBEb2Vzbid0IHRoZQ0KTWVzc2FnZS1BdXRoZW50aWNhdG9yIHByb3RlY3QgdGFtcGVyaW5nPGJy
Pg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHdpdGggdGhlIG5vbmNlIHZhbHVlPzxicj4NCjxm
b250IGNvbG9yPW5hdnk+PHNwYW4gc3R5bGU9J2NvbG9yOm5hdnknPk1hZGppZCZndDsmZ3Q7IG9u
bHkgZnJvbSBIQSB0byBNTiwNCm5vdCBvdmVyIFJBRElVUyBmcm9tIEFBQUggdG8gTUlQIGFnZW50
cywgYXQgbGVhc3QsIEkgdGhpbmsgdGhpcyBpcyB3aGF0IEkNCm1lYW50Ljwvc3Bhbj48L2ZvbnQ+
PC9zcGFuPjwvZm9udD48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48Zm9udCBzaXplPTMgZmFj
ZT0iVGltZXMgTmV3IFJvbWFuIj48c3BhbiBzdHlsZT0nZm9udC1zaXplOg0KMTIuMHB0Jz48YnI+
DQo8L3NwYW4+PC9mb250PjxzcGFuIGxhbmc9REE+S2VudDxicj4NCjxicj4NCkF0IDA2OjU2IFBN
IDIvNy8yMDA1IC0wNjAwLCA8L3NwYW4+PHNwYW4gbGFuZz1EQT5OYWtoamlyaSBNYWRqaWQtTU5B
S0hKSTE8L3NwYW4+PHNwYW4NCmxhbmc9REE+IHdyb3RlOjxicj4NCjxicj4NCjxicj4NCjwvc3Bh
bj48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48Zm9udCBzaXplPTIgZmFjZT1BcmlhbD48c3Bh
biBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDsNCmZvbnQtZmFtaWx5OkFyaWFsJz5IaSBmb2xrcyw8
YnI+DQo8L3NwYW4+PC9mb250Pjxicj4NCjxmb250IHNpemU9MiBmYWNlPUFyaWFsPjxzcGFuIHN0
eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OkFyaWFsJz4mbmJzcDs8YnI+DQo8L3Nw
YW4+PC9mb250Pjxicj4NCjxmb250IHNpemU9MiBmYWNlPUFyaWFsPjxzcGFuIHN0eWxlPSdmb250
LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OkFyaWFsJz5KdXN0DQp3YW50ZWQgdG8gbGV0IHlvdSBr
bm93IHRoYXQgd2UganVzdCBzdWJtaXR0ZWQgYSBkcmFmdCBwcm9wb3NpbmcgYW4NCnNwZWNpZmlj
YXRpb24gZm9yIHN1cHBvcnQgb2YgUkFESVVTIGZvciBNb2JpbGUgSVAga2V5IG1hbmFnZW1lbnQg
cHJvY2VkdXJlcy4NClRoZSBkcmFmdCBnb2VzIHRocm91Z2ggdHdvIGNhc2VzIG9mIGNvLWxvY2F0
ZWQgbW9iaWxlIG5vZGVzIGFuZCBub2RlcyBiZWhpbmQgYW4NCkZBIGFuZCBkZXNjcmliZXMgUkFE
SVVTIG1lc3NhZ2luZyBhbmQgYXR0cmlidXRlcyBmb3IgZWFjaCBjYXNlLiBTaW5jZSB0aGUgZHJh
ZnQNCmRlYWxzIHdpdGggYm90aCBNb2JpbGUgSVB2NCBhbmQgUkFESVVTLCBpdCBuZWVkcyB0byBi
ZSBleGFtaW5lZCBieSBib3RoIGdyb3Vwcy4NCldlIGtub3cgdGhhdCB0aGlzIGlzIHJlYWxseSBt
b3JlIGFuIGV4dGVuc2lvbiB0byBSQURJVVMgdGhhbiB0byBNb2JpbGUgSVAgYW5kDQpzaG91bGQg
YmUgc3RhbmRhcmRpemVkIGJ5IFJBRElVUyBncm91cHMsIGJ1dCB3ZSB3b3VsZCBsaWtlIHRvIG1h
a2Ugc3VyZSB0aGF0IHdlDQpnb3QgdGhlIE1vYmlsZSBJUCBwYXJ0cyByaWdodCBmaXJzdCA8L3Nw
YW4+PC9mb250Pjxmb250IHNpemU9MiBmYWNlPVdpbmdkaW5ncz48c3Bhbg0Kc3R5bGU9J2ZvbnQt
c2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6V2luZ2RpbmdzJz5KPC9zcGFuPjwvZm9udD48Zm9udCBz
aXplPTINCmZhY2U9QXJpYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1p
bHk6QXJpYWwnPi48YnI+DQo8L3NwYW4+PC9mb250Pjxicj4NCjxmb250IHNpemU9MiBmYWNlPUFy
aWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OkFyaWFsJz4mbmJz
cDs8YnI+DQo8L3NwYW4+PC9mb250Pjxicj4NCjxmb250IHNpemU9MiBmYWNlPUFyaWFsPjxzcGFu
IHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OkFyaWFsJz5Tbw0KY29tbWVudHMg
YW5kIGd1aWRhbmNlIGFyZSB2ZXJ5IHdlbGNvbWUuPGJyPg0KPC9zcGFuPjwvZm9udD48YnI+DQo8
Zm9udCBzaXplPTIgZmFjZT1BcmlhbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250
LWZhbWlseTpBcmlhbCc+Jm5ic3A7PGJyPg0KPC9zcGFuPjwvZm9udD48YnI+DQo8Zm9udCBzaXpl
PTIgZmFjZT1BcmlhbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpB
cmlhbCc+VGhhbmtzDQphbmQgUmVnYXJkcyw8YnI+DQo8L3NwYW4+PC9mb250Pjxicj4NCjxmb250
IHNpemU9MiBmYWNlPUFyaWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OkFyaWFsJz4mbmJzcDs8YnI+DQo8L3NwYW4+PC9mb250Pjxicj4NCjxmb250IHNpemU9MiBm
YWNlPUFyaWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OkFyaWFs
Jz5NYWRqaWQNCk5ha2hqaXJpLCBLdW50YWwgQ2hvd2RodXJ5LCBBdmkgTGlvcjxicj4NCjwvc3Bh
bj48L2ZvbnQ+PGJyPg0KPGZvbnQgc2l6ZT0yIGZhY2U9QXJpYWw+PHNwYW4gc3R5bGU9J2ZvbnQt
c2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6QXJpYWwnPiZuYnNwOzxicj4NCjwvc3Bhbj48L2ZvbnQ+
PGJyPg0KPGZvbnQgc2l6ZT0yIGZhY2U9QXJpYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMC4w
cHQ7Zm9udC1mYW1pbHk6QXJpYWwnPiZuYnNwOzxicj4NCjwvc3Bhbj48L2ZvbnQ+PGJyPg0KPGZv
bnQgc2l6ZT0yIGZhY2U9QXJpYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1m
YW1pbHk6QXJpYWwnPlRoZQ0KZHJhZnQgY2FuIGJlIGZvdW5kIGF0IDxicj4NCjwvc3Bhbj48L2Zv
bnQ+PGJyPg0KPGZvbnQgc2l6ZT0yIGZhY2U9QXJpYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZTox
MC4wcHQ7Zm9udC1mYW1pbHk6QXJpYWwnPiZuYnNwOzxicj4NCjwvc3Bhbj48L2ZvbnQ+PGJyPg0K
PGZvbnQgc2l6ZT0yIGZhY2U9QXJpYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9u
dC1mYW1pbHk6QXJpYWwnPjxhDQpocmVmPSJodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRy
YWZ0cy9kcmFmdC1uYWtoamlyaS1yYWRpdXMtbWlwNC0wMC50eHQiPmh0dHA6Ly93d3cuaWV0Zi5v
cmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LW5ha2hqaXJpLXJhZGl1cy1taXA0LTAwLnR4dDwvYT48
YnI+DQo8L3NwYW4+PC9mb250Pjxicj4NCjxmb250IHNpemU9MiBmYWNlPUFyaWFsPjxzcGFuIHN0
eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OkFyaWFsJz4mbmJzcDs8YnI+DQo8L3Nw
YW4+PC9mb250Pjxicj4NCjxmb250IHNpemU9MiBmYWNlPSJDb3VyaWVyIE5ldyI+PHNwYW4gc3R5
bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Iic+Jm5ic3A7Jm5i
c3A7Jm5ic3A7DQo8YnI+DQo8L3NwYW4+PC9mb250Pjxicj4NCjxmb250IHNpemU9MiBmYWNlPSJD
b3VyaWVyIE5ldyI+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6IkNv
dXJpZXIgTmV3Iic+QWJzdHJhY3QNCjxicj4NCjwvc3Bhbj48L2ZvbnQ+PGJyPg0KPGZvbnQgc2l6
ZT0yIGZhY2U9IkNvdXJpZXIgTmV3Ij48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250
LWZhbWlseToiQ291cmllciBOZXciJz4mbmJzcDsmbmJzcDsmbmJzcDsNCjxicj4NCjwvc3Bhbj48
L2ZvbnQ+PGJyPg0KPGZvbnQgc2l6ZT0yIGZhY2U9IkNvdXJpZXIgTmV3Ij48c3BhbiBzdHlsZT0n
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToiQ291cmllciBOZXciJz4mbmJzcDsmbmJzcDsN
Ck1vYmlsZSBJUHY0IHNwZWNpZmllcyBtZWNoYW5pc21zIHRoYXQgbmVlZCBhc3Npc3RhbmNlIGZy
b20gYSBBQUEgPGJyPg0KPC9zcGFuPjwvZm9udD48YnI+DQo8Zm9udCBzaXplPTIgZmFjZT0iQ291
cmllciBOZXciPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJDb3Vy
aWVyIE5ldyInPiZuYnNwOyZuYnNwOw0Kc2VydmVyIGFuZCBhIEFBQSBpbmZyYXN0cnVjdHVyZS4g
RXhhbXBsZXMgb2Ygc3VjaCBtZWNoYW5pc21zIGFyZSA8YnI+DQo8L3NwYW4+PC9mb250Pjxicj4N
Cjxmb250IHNpemU9MiBmYWNlPSJDb3VyaWVyIE5ldyI+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZTox
MC4wcHQ7Zm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Iic+Jm5ic3A7Jm5ic3A7DQp0aG9zZSBwcm92
aWRpbmcga2V5IG1hbmFnZW1lbnQgYW5kIGF1dGhlbnRpY2F0aW9uIHNlcnZpY2VzIGR1cmluZyBh
IDxicj4NCjwvc3Bhbj48L2ZvbnQ+PGJyPg0KPGZvbnQgc2l6ZT0yIGZhY2U9IkNvdXJpZXIgTmV3
Ij48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToiQ291cmllciBOZXci
Jz4mbmJzcDsmbmJzcDsNCm1vYmlsZSBub2RlJ3MgcmVnaXN0cmF0aW9uIHByb2Nlc3Mgd2l0aCBN
Ti1BQUEgYXV0aGVudGljYXRpb24gPGJyPg0KPC9zcGFuPjwvZm9udD48YnI+DQo8Zm9udCBzaXpl
PTIgZmFjZT0iQ291cmllciBOZXciPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQt
ZmFtaWx5OiJDb3VyaWVyIE5ldyInPiZuYnNwOyZuYnNwOw0KZXh0ZW5zaW9uLiBBbHRob3VnaCBE
aWFtZXRlciBNb2JpbGUgSVAgYXBwbGljYXRpb24gaXMgYmVpbmcgc3BlY2lmaWVkIDxicj4NCjwv
c3Bhbj48L2ZvbnQ+PGJyPg0KPGZvbnQgc2l6ZT0yIGZhY2U9IkNvdXJpZXIgTmV3Ij48c3BhbiBz
dHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToiQ291cmllciBOZXciJz4mbmJzcDsm
bmJzcDsNCnRvIHN1cHBvcnQgdGhlIG5lZWRzIG9mIE1vYmlsZSBJUHY0IGZyb20gdGhlIEFBQSBp
bmZyYXN0cnVjdHVyZSdzIDxicj4NCjwvc3Bhbj48L2ZvbnQ+PGJyPg0KPGZvbnQgc2l6ZT0yIGZh
Y2U9IkNvdXJpZXIgTmV3Ij48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWls
eToiQ291cmllciBOZXciJz4mbmJzcDsmbmJzcDsNCnBvaW50IG9mIHZpZXcsIHN1Y2ggc3VwcG9y
dCBkb2VzIG5vdCBleGlzdCB3aXRoaW4gUkFESVVTIGZyYW1ld29yay4gPGJyPg0KPC9zcGFuPjwv
Zm9udD48YnI+DQo8Zm9udCBzaXplPTIgZmFjZT0iQ291cmllciBOZXciPjxzcGFuIHN0eWxlPSdm
b250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyInPiZuYnNwOyZuYnNwOw0K
VGhpcyBkb2N1bWVudCBkZWZpbmVzIHRoZSBSQURJVVMgYXR0cmlidXRlcyB0aGF0IHByb3ZpZGUg
c3VwcG9ydCBmb3IgPGJyPg0KPC9zcGFuPjwvZm9udD48YnI+DQo8Zm9udCBzaXplPTIgZmFjZT0i
Q291cmllciBOZXciPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJD
b3VyaWVyIE5ldyInPiZuYnNwOyZuYnNwOw0KTW9iaWxlIElQdjQgb3BlcmF0aW9uLiA8YnI+DQo8
L3NwYW4+PC9mb250Pjxicj4NCjxmb250IHNpemU9MiBmYWNlPUFyaWFsPjxzcGFuIHN0eWxlPSdm
b250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OkFyaWFsJz4mbmJzcDs8YnI+DQo8L3NwYW4+PC9m
b250Pjxicj4NCjxmb250IHNpemU9MiBmYWNlPUFyaWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6
MTAuMHB0O2ZvbnQtZmFtaWx5OkFyaWFsJz4mbmJzcDs8YnI+DQo8L3NwYW4+PC9mb250Pi0tIDxi
cj4NCk1pcDQgbWFpbGluZyBsaXN0OiBNaXA0QGlldGYub3JnPGJyPg0KJm5ic3A7Jm5ic3A7Jm5i
c3A7IFdlYiBpbnRlcmZhY2U6IDxhDQpocmVmPSJodHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9taXA0IiBldWRvcmE9YXV0b3VybD5odHRwczovL3d3dzEuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby9taXA0PC9hPjxicj4NCiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBDaGFy
dGVyIHBhZ2U6IDxhDQpocmVmPSJodHRwOi8vd3d3LmlldGYub3JnL2h0bWwuY2hhcnRlcnMvbWlw
NC1jaGFydGVyLmh0bWwiIGV1ZG9yYT1hdXRvdXJsPmh0dHA6Ly93d3cuaWV0Zi5vcmcvaHRtbC5j
aGFydGVycy9taXA0LWNoYXJ0ZXIuaHRtbDwvYT48YnI+DQpTdXBwbGVtZW50YWwgc2l0ZTogPGEg
aHJlZj0iaHR0cDovL3d3dy5taXA0Lm9yZy8iIGV1ZG9yYT1hdXRvdXJsPmh0dHA6Ly93d3cubWlw
NC5vcmcvPC9hPjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxmb250IHNpemU9MyBmYWNlPSJU
aW1lcyBOZXcgUm9tYW4iPjxzcGFuIHN0eWxlPSdmb250LXNpemU6DQoxMi4wcHQnPiZuYnNwOzwv
c3Bhbj48L2ZvbnQ+PC9wPg0KDQo8ZGl2Pg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PGZvbnQgc2l6
ZT0zIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToNCjEyLjBw
dCc+LS08L3NwYW4+PC9mb250PjwvcD4NCg0KPC9kaXY+DQoNCjxkaXY+DQoNCjxwIGNsYXNzPU1z
b05vcm1hbD48Zm9udCBzaXplPTMgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj48c3BhbiBzdHlsZT0n
Zm9udC1zaXplOg0KMTIuMHB0Jz4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsNCnwmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsNCnwmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsNCktlbnQgTGV1
bmc8L3NwYW4+PC9mb250PjwvcD4NCg0KPC9kaXY+DQoNCjxkaXY+DQoNCjxwIGNsYXNzPU1zb05v
cm1hbD48Zm9udCBzaXplPTMgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj48c3BhbiBzdHlsZT0nZm9u
dC1zaXplOg0KMTIuMHB0Jz4mbmJzcDsmbmJzcDsmbmJzcDsgOnw6Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQo6fDombmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsNCklQIE1vYmlsaXR5IERldmVsb3BtZW50PC9zcGFuPjwv
Zm9udD48L3A+DQoNCjwvZGl2Pg0KDQo8ZGl2Pg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PGZvbnQg
c2l6ZT0zIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToNCjEy
LjBwdCc+Jm5ic3A7Jm5ic3A7IDp8fHw6Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7DQo6fHx8OiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOw0KSW50ZXJu
ZXQgVGVjaG5vbG9naWVzIERpdmlzaW9uPC9zcGFuPjwvZm9udD48L3A+DQoNCjwvZGl2Pg0KDQo8
ZGl2Pg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PGZvbnQgc2l6ZT0zIGZhY2U9IlRpbWVzIE5ldyBS
b21hbiI+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToNCjEyLjBwdCc+Jm5ic3A7IDp8fHx8fHx8OiZu
YnNwOyZuYnNwOw0KOnx8fHx8fHw6Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQpWb2ljZTogNDA4LjUy
Ni41MDMwPC9zcGFuPjwvZm9udD48L3A+DQoNCjwvZGl2Pg0KDQo8ZGl2Pg0KDQo8cCBjbGFzcz1N
c29Ob3JtYWw+PGZvbnQgc2l6ZT0zIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+PHNwYW4gc3R5bGU9
J2ZvbnQtc2l6ZToNCjEyLjBwdCc+Ljp8fHx8fHx8fHw6Ljp8fHx8fHx8fHw6LiZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOw0KRmF4OiZuYnNwOyZuYnNwOyA0MDguNTI1LjE2NTM8L3NwYW4+PC9mb250PjwvcD4NCg0K
PC9kaXY+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48Zm9udCBzaXplPTMgZmFjZT0iVGltZXMgTmV3
IFJvbWFuIj48c3BhbiBzdHlsZT0nZm9udC1zaXplOg0KMTIuMHB0Jz4mbmJzcDtjIGkgcyBjIG8g
UyB5IHMgdCBlIG0NCnMmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsNCkVtYWlsOiBrbGV1bmdAY2lzY28uY29tIDwv
c3Bhbj48L2ZvbnQ+PC9wPg0KDQo8L2Rpdj4NCg0KPC9ib2R5Pg0KDQo8L2h0bWw+DQo=

------_=_NextPart_001_01C534B3.40D7B658--


--===============0600860087==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0600860087==--



From mip4-bounces@ietf.org  Tue Mar 29 18:56:29 2005
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 SAA11869
	for <mip4-web-archive@ietf.org>; Tue, 29 Mar 2005 18:56:29 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DGQgH-0004pG-Ab
	for mip4-web-archive@ietf.org; Tue, 29 Mar 2005 19:03:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DGQY9-00053l-10; Tue, 29 Mar 2005 18:55:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DGQY6-00052B-Pe
	for mip4@megatron.ietf.org; Tue, 29 Mar 2005 18:55:06 -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 SAA11789
	for <mip4@ietf.org>; Tue, 29 Mar 2005 18:55:03 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DGQet-0004lY-Kj
	for mip4@ietf.org; Tue, 29 Mar 2005 19:02:08 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-2.cisco.com with ESMTP; 29 Mar 2005 15:54:57 -0800
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j2TNsqgE029574;
	Tue, 29 Mar 2005 15:54:52 -0800 (PST)
Received: from kleung-w2k01.cisco.com (dhcp-128-107-176-202.cisco.com
	[128.107.176.202]) by mira-sjc5-b.cisco.com (MOS 3.4.5-GR)
	with ESMTP id BDL15131; Tue, 29 Mar 2005 15:54:52 -0800 (PST)
Message-Id: <4.3.2.7.2.20050329152316.022c8d50@mira-sjcm-2.cisco.com>
X-Sender: kleung@mira-sjcm-2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 29 Mar 2005 15:54:52 -0800
To: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
From: Kent Leung <kleung@cisco.com>
Subject: RE: [Mip4] draft on RADIUS support for Mobile IP
In-Reply-To: <EBF631554F9CD7118D0B00065BF34DCB18379544@il27exm03.cig.mot .com>
Mime-Version: 1.0
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 2e8a07f64def4bd8598257bc442beb9d
Cc: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>,
        kchowdhury@starentnetworks.com, mip4@ietf.org,
        avi@bridgewatersystems.com
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>
Content-Type: multipart/mixed; boundary="===============1903675047=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 81ca0cebdb446e1ff4e2b634791f24a9

--===============1903675047==
Content-Type: multipart/alternative;
	boundary="=====================_73646708==_.ALT"

--=====================_73646708==_.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

Hi Madjid.  Comments below.

At 05:01 PM 3/29/2005 -0600, Nakhjiri Madjid-MNAKHJI1 wrote:

>Hi Kent,
>
>
>
>Sending comments to the rest of your questions.
>
>
>
>-----Original Message-----
>From: Kent Leung [mailto:kleung@cisco.com]
>Sent: Wednesday, March 23, 2005 7:06 PM
>To: Nakhjiri Madjid-MNAKHJI1
>Cc: mip4@ietf.org; Nakhjiri Madjid-MNAKHJI1; 
>kchowdhury@starentnetworks.com; avi@bridgewatersystems.com
>Subject: Re: [Mip4] draft on RADIUS support for Mobile IP
>
>
>
><snip>
>
>17) Sect 4.2, "the HA and FA may send their own IP addresses inside NAS-IP
>       instead of MIP-[HA|FA]-IP-address".  I think the MIP-[HA|FA] 
> identifiers should
>       always be in the Access Req.
>
>
>
>Madjid>>That would make sense to Mobile IP folks, but I am not if RADIUS 
>folks would be happy if their message needs to carry two attributes with 
>different names carrying the same info. Here is a question: Diameter has 
>the notion of "applications", Mobile IP is an application for Diameter. If 
>the server knows you are running the Mobile IP application, then depending 
>on the message, it knows it is coming from a client that is also a mobile 
>IP agent. In RADIUS you cannot define new messages, so we need to ask the 
>question of whether the RADIUS server needs to know if a NAS is an FA or 
>an HA. If we decide that distinguishing of FA and HA is important for the 
>operations here (I think it is, then we need to change this statement. I 
>put a comment in that effect there.
>
>(By receiving the Mobile IP related RADIUS attributes, the server will 
>know that it is receiving Access Requests from a NAS that is also a Mobile 
>IP agent. If it is shown that the RADIUS server need to be able to 
>distinguish an FA and an HA, then the MIP-HA-IP-address or 
>MIP-FA-IP-address attributes need to also be included)
>
>what do you think?


The HA or FA identifiers include MIP-HA-NAI and MIP-FA-NAI, right?  These 
would not fit
into the NAS-IP AVP.  I think this text is fine as long as NAI is in there too.



>18) Sect 5, MIP-HA-IP address, why "the FA this attribute MAY not be used in
>       the Access-Request"?  The HA address could be helpful to for 
> setting up FA-HA
>       MSA.
>
>
>
>Madjid>> based on what we just said, I cannot remember why we added that 
>statement. I will mark it for now and if it is needed, I remove the text.
>
>
>
>
>
>19) MIP-MN-AAA-SPI, String should be unsigned32 and Length should be 6.
>Madjid>>thanks, good point. Changed all the SPIs accordingly.
>
>
>20) Mobile IPv4 feature vector, if mapping to DIAMETER, then this should 
>be unsigned32.
>      The "8-bit flag vector" should be called "bitflag vector" as current 
> allocation is already
>      over 8 bits.  :)  Length would be 6.
>
>Madjid>>checked the Diameter MIP, true. Changed accordingly. Thanks.
>
>
>
>Why not unsigned8, by the way?


There's already over 8 bits assigned.  And when someone creates RADIUS/DIAMETER
gateway, it's better to have same size fields. :)



>21) Why bit 8 Foreign-Home-Agent-Available not supported?  This could be 
>set by
>       FA to notify to AAAH that AAAL can assign the HA when relaying the 
> Access-Accept.
>       I'm not clear on usage of bit 2 
> Home-Address-Allocatable-Only-in-Home-Realm.
>       Also, I'm not sure why we don't have bitflag to indicate if the 
> Access-Request is
>       sent by FA or HA?  That might clarify some operations on the AAA 
> server?
>       Let's say the Access-Request contains the NAS-IP for authentication 
> between NAS
>       and AAA server and FA and HA identifiers to set up MSA, shouldn't 
> AAA need to
>       know which is FA or HA to set up the directional SPI for MSA?
>
>Madjid>>We are not against any of that, we were just keeping things simple 
>until we make sure  our suggested operation suggested that. Come to think 
>about it, no harm in defining the attributes before hand. Done.
>
>
>22) MIP-MN-to-HA SPI and MIP-HA-to-MN-SPI , String should be unsigned32 
>and length is 6.
>Madjid>>done.
>23) MIP-MN-HA-ALGID, not clear how algorithm identifier is mapped?  We 
>have keyed MD5
>       and HMAC-MD5.  Having a string doesn't make sense.  Maybe unsigned8 
> and specify
>       1 for keyed MD5 and 2 for HMAC-MD5?
>
>Madjid>>The strings are the products of cut and paste before the deadline 
>phenomenon J
>
>Will change to unsigned8. do you want a table with identifier values? 
>Isn't SHA1 becoming popular now?
>
>Should I have separate values for HMAC-MD5 and MD5? Do people do MD5 alone?
>


Yes, keyed MD5 was in RFC 2002 and HMAC-MD5 was in RFC 3344.  SHA1 is
not defined in any MIPv4 RFC.


>24) MIP-MN-HA-REP, same issue with string.  Maybe unsigned8 and specifiy 1 for
>       timestamp (with field for replay range) and 2 for nonce?
>
>
>
>Madjid>>done.
>
>
>
>25) MIP-MN-HA-MSA-LIFE, integer should be unsigned32 and length is 
>6.  Should we
>      allow 0xFFFFFFFF to mean infinite lifetime for MSA?  This means the 
> MSA remains
>      for lifetime of one registration session (MSA deleted when 
> registration ends).
>
>Madjid>>done. Not sure about the infinite lifetime. I am wondering in 
>general who determines and enforces these lifetimes? How do you know 
>whether an MSA belongs to this session or the previous one? And why would 
>the MSA be valid only for one registration?
>


Generally, the MSA between MN and HA has infinite lifetime, as there are
not standards mechanism to rekey.  So there is no need for enforcement
for lifetime.

A session exists when there is a mobility binding, which is renewed by
re-registrations.  So once the mobility binding goes away, the session
is over.  The reason why MSA is valid for one session is to enforce
AAA authorization when a new session is started.  This means starting
a new session requires AAA authentication/authorization again.

I was thinking about having another option for AAA to tell HA to keep it
forever.  But not sure why the MSA should remain between sessions.
Maybe we could use lifetime = 0 to serve this purpose?


>26) Remove bunch of AVPs above the format of FA to HA SPI.
>
>Madjid>> not sure if I follow??
>


hmm, can't remember why either.


>27) FA to HA SPI and HA to FA SPI, string is unsigned32 and length is 6.
>Madjid>>done.
>
>
>28) Would like to add new MIP-FA-HA-nonce AVP.
>Madjid>>see my previous comments on FA-HA nonce versus FA-HA SPI.
>
>
>29) In 5.1, attribute list is missing MIP-FA-NAI,
>
>Madjid>> added
>
>MIP-MN-HA SPI and MIP-HA-to-MN-SPI should change "HA" to "FA"
>
>Madjid>>good catch on my cut and pastes. Thanks.
>
>
>
>before "Encrypted", missing Encrypted[MIP-MN-FA-key],
>
>Madjid>>done.
>
>
>       new MIP-FA-HA-nonce, duplicate MIP-MN-HA-MSA-LIFE.
>
>Madjid>>previous comment. Fixed duplicate.
>
>
>30) Sect 8, "We recommend that the AAAH also authenticates the nonce reply
>      extensions with the AAA SA it shares with the MN".  This is for MITM 
> attack for
>      msg from AAAH to HA/FA.  Doesn't the Message-Authenticator protect 
> tampering
>      with the nonce value?
>Madjid>> only from HA to MN, not over RADIUS from AAAH to MIP agents, at 
>least, I think this is what I meant.
>

Oh well, I'm still not clear.  The Message-Authenticator AVP should
protect the nonce value between AAAH and MIP agents.  The MHAE
or MFAE should protect the nonce value between MN and HA or
MN and FA, respectively.  So what does AAAH also authenticates
the nonce reply with SA with MN?  The nonce will be use to derive
MHAE/MFAE key for authenticating RRP, which means that nonce
could not have been tempered with.  I'm missing something probably?

Thanks.

Kent


--
      |           |                   Kent Leung
     :|:         :|:                  IP Mobility Development
    :|||:       :|||:                 Internet Technologies Division
   :|||||||:   :|||||||:              Voice: 408.526.5030
.:|||||||||:.:|||||||||:.             Fax:   408.525.1653
  c i s c o S y s t e m s             Email: kleung@cisco.com 
--=====================_73646708==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
Hi Madjid.&nbsp; Comments below.<br>
<br>
At 05:01 PM 3/29/2005 -0600, Nakhjiri Madjid-MNAKHJI1 wrote:<br>
<br>
<blockquote type=cite cite><font face="arial" size=2 color="#000080">Hi
Kent, <br>
</font><br>
<font face="arial" size=2 color="#000080">&nbsp;<br>
</font><br>
<font face="arial" size=2 color="#000080">Sending comments to the rest of
your questions. <br>
</font><br>
<font face="arial" size=2 color="#000080">&nbsp;<br>
</font><br>
<font face="tahoma" size=2>-----Original Message-----<br>
<b>From:</b> Kent Leung
[<a href="mailto:kleung@cisco.com" eudora="autourl">mailto:kleung@cisco.com</a>]
<br>
<b>Sent:</b> Wednesday, March 23, 2005 7:06 PM<br>
<b>To:</b> Nakhjiri Madjid-MNAKHJI1<br>
<b>Cc:</b> mip4@ietf.org; Nakhjiri Madjid-MNAKHJI1;
kchowdhury@starentnetworks.com; avi@bridgewatersystems.com<br>
<b>Subject:</b> Re: [Mip4] draft on RADIUS support for Mobile IP<br>
</font><br>
<font face="Times New Roman, Times">&nbsp;<br>
</font><br>
<font face="Times New Roman, Times" color="#000080">&lt;snip&gt;</font><br>
<br>
17) Sect 4.2, &quot;the HA and FA may send their own IP addresses inside
NAS-IP<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; instead of
MIP-[HA|FA]-IP-address&quot;.&nbsp; I think the MIP-[HA|FA] identifiers
should<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; always be in the Access Req.<br>
<br>
<font face="arial" size=2 color="#000080">&nbsp;<br>
</font><br>
<font face="arial" size=2 color="#000080">Madjid&gt;&gt;That would make
sense to Mobile IP folks, but I am not if RADIUS folks would be happy if
their message needs to carry two attributes with different names carrying
the same info. Here is a question: Diameter has the notion of
&quot;applications&quot;, Mobile IP is an application for Diameter. If
the server knows you are running the Mobile IP application, then
depending on the message, it knows it is coming from a client that is
also a mobile IP agent. In RADIUS you cannot define new messages, so we
need to ask the question of whether the RADIUS server needs to know if a
NAS is an FA or an HA. If we decide that distinguishing of FA and HA is
important for the operations here (I think it is, then we need to change
this statement. I put a comment in that effect there.<br>
</font><br>
<font face="Times New Roman, Times">(</font><font face="Times New Roman, Times" color="#FF0000">By
receiving the Mobile IP related RADIUS attributes, the server will know
that it is receiving Access Requests from a NAS that is also a Mobile IP
agent. If it is shown that the RADIUS server need to be able to
distinguish an FA and an HA, then the MIP-HA-IP-address or
MIP-FA-IP-address attributes need to also be
included</font><font face="Times New Roman, Times">)<br>
</font><br>
<font face="Times New Roman, Times" color="#000080">what do you
think?</font><br>
</blockquote><br>
<br>
The HA or FA identifiers include MIP-HA-NAI and MIP-FA-NAI, right?&nbsp;
These would not fit<br>
into the NAS-IP AVP.&nbsp; I think this text is fine as long as NAI is in
there too.<br>
<br>
<br>
<br>
<blockquote type=cite cite>18) Sect 5, MIP-HA-IP address, why &quot;the
FA this attribute MAY not be used in<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the Access-Request&quot;?&nbsp; The HA
address could be helpful to for setting up FA-HA<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MSA.<br>
<br>
<font face="arial" size=2 color="#000080">&nbsp;<br>
</font><br>
<font face="arial" size=2 color="#000080">Madjid&gt;&gt; based on what we
just said, I cannot remember why we added that statement. I will mark it
for now and if it is needed, I remove the text.<br>
</font><br>
<font face="arial" size=2 color="#000080">&nbsp;<br>
</font><br>
<font face="Times New Roman, Times"><br>
<br>
19) MIP-MN-AAA-SPI, String should be unsigned32 and Length should be
6.<br>
</font><font face="Times New Roman, Times" color="#000080">Madjid&gt;&gt;thanks,
good point. Changed all the SPIs accordingly.<br>
</font><br>
<font face="Times New Roman, Times"><br>
20) Mobile IPv4 feature vector, if mapping to DIAMETER, then this should
be unsigned32.<br>
&nbsp;&nbsp;&nbsp;&nbsp; The &quot;8-bit flag vector&quot; should be
called &quot;bitflag vector&quot; as current allocation is already<br>
&nbsp;&nbsp;&nbsp;&nbsp; over 8 bits.&nbsp; :)&nbsp; Length would be
6.&nbsp; <br>
<br>
</font><font face="arial" size=2 color="#000080">Madjid&gt;&gt;checked
the Diameter MIP, true. Changed accordingly. Thanks. <br>
</font><br>
<font face="arial" size=2 color="#000080">&nbsp;<br>
</font><br>
<font face="arial" size=2 color="#000080">Why not unsigned8, by the
way?<br>
</font></blockquote><br>
<br>
There's already over 8 bits assigned.&nbsp; And when someone creates
RADIUS/DIAMETER<br>
gateway, it's better to have same size fields. :)<br>
<br>
<br>
<br>
<blockquote type=cite cite><font face="Times New Roman, Times">21) Why
bit 8 Foreign-Home-Agent-Available not supported?&nbsp; This could be set
by<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FA to notify to AAAH that AAAL can assign
the HA when relaying the Access-Accept.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I'm not clear on usage of bit 2
Home-Address-Allocatable-Only-in-Home-Realm.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Also, I'm not sure why we don't have
bitflag to indicate if the Access-Request is<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; sent by FA or HA?&nbsp; That might clarify
some operations on the AAA server?<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Let's say the Access-Request contains the
NAS-IP for authentication between NAS<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and AAA server and FA and HA identifiers
to set up MSA, shouldn't AAA need to<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; know which is FA or HA to set up the
directional SPI for MSA?<br>
<br>
</font><font face="arial" size=2 color="#000080">Madjid&gt;&gt;We are not
against any of that, we were just keeping things simple until we make
sure&nbsp; our suggested operation suggested that. Come to think about
it, no harm in defining the attributes before hand. Done.<br>
</font><br>
<font face="Times New Roman, Times"><br>
22) MIP-MN-to-HA SPI and MIP-HA-to-MN-SPI , String should be unsigned32
and length is 6.<br>
</font><font face="Times New Roman, Times" color="#000080">Madjid&gt;&gt;done.</font><font face="Times New Roman, Times"><br>
23) MIP-MN-HA-ALGID, not clear how algorithm identifier is mapped?&nbsp;
We have keyed MD5<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and HMAC-MD5.&nbsp; Having a string
doesn't make sense.&nbsp; Maybe unsigned8 and specify<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1 for keyed MD5 and 2 for HMAC-MD5?<br>
<br>
</font><font face="arial" size=2 color="#000080">Madjid&gt;&gt;The
strings are the products of cut and paste before the deadline phenomenon
</font><font face="wingdings" size=2 color="#000080">J<br>
</font><br>
<font face="arial" size=2 color="#000080">Will change to unsigned8. do
you want a table with identifier values? Isn't SHA1 becoming popular
now?<br>
</font><br>
<font face="arial" size=2 color="#000080">Should I have separate values
for HMAC-MD5 and MD5? Do people do MD5 alone?<br>
</font><br>
<font face="Times New Roman, Times"></font></blockquote><br>
<br>
Yes, keyed MD5 was in RFC 2002 and HMAC-MD5 was in RFC 3344.&nbsp; SHA1
is<br>
not defined in any MIPv4 RFC.<br>
<br>
<br>
<blockquote type=cite cite><font face="Times New Roman, Times">24)
MIP-MN-HA-REP, same issue with string.&nbsp; Maybe unsigned8 and specifiy
1 for<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; timestamp (with field for replay range)
and 2 for nonce?<br>
</font><br>
<font face="arial" size=2 color="#000080">&nbsp;<br>
</font><br>
<font face="arial" size=2 color="#000080">Madjid&gt;&gt;done.<br>
</font><br>
<font face="Times New Roman, Times"><br>
<br>
25) MIP-MN-HA-MSA-LIFE, integer should be unsigned32 and length is
6.&nbsp; Should we<br>
&nbsp;&nbsp;&nbsp;&nbsp; allow 0xFFFFFFFF to mean infinite lifetime for
MSA?&nbsp; This means the MSA remains<br>
&nbsp;&nbsp;&nbsp;&nbsp; for lifetime of one registration session (MSA
deleted when registration ends).<br>
<br>
</font><font face="arial" size=2 color="#000080">Madjid&gt;&gt;done. Not
sure about the infinite lifetime. I am wondering in general who
determines and enforces these lifetimes? How do you know whether an MSA
belongs to this session or the previous one? And why would the MSA be
valid only for one registration?<br>
</font><br>
<font face="Times New Roman, Times"></font></blockquote><br>
<br>
Generally, the MSA between MN and HA has infinite lifetime, as there
are<br>
not standards mechanism to rekey.&nbsp; So there is no need for
enforcement<br>
for lifetime.<br>
<br>
A session exists when there is a mobility binding, which is renewed
by<br>
re-registrations.&nbsp; So once the mobility binding goes away, the
session<br>
is over.&nbsp; The reason why MSA is valid for one session is to
enforce<br>
AAA authorization when a new session is started.&nbsp; This means
starting<br>
a new session requires AAA authentication/authorization again.<br>
<br>
I was thinking about having another option for AAA to tell HA to keep
it<br>
forever.&nbsp; But not sure why the MSA should remain between
sessions.<br>
Maybe we could use lifetime = 0 to serve this purpose?<br>
<br>
<br>
<blockquote type=cite cite><font face="Times New Roman, Times">26) Remove
bunch of AVPs above the format of FA to HA SPI.<br>
<br>
</font><font face="arial" size=2 color="#000080">Madjid&gt;&gt; not sure
if I follow??<br>
</font><br>
<font face="Times New Roman, Times"></font></blockquote><br>
<br>
hmm, can't remember why either.<br>
<br>
<br>
<blockquote type=cite cite><font face="Times New Roman, Times">27) FA to
HA SPI and HA to FA SPI, string is unsigned32 and length is 6.<br>
</font><font face="Times New Roman, Times" color="#000080">Madjid&gt;&gt;done.<br>
</font><br>
<font face="Times New Roman, Times"><br>
28) Would like to add new MIP-FA-HA-nonce AVP.<br>
</font><font face="Times New Roman, Times" color="#000080">Madjid&gt;&gt;see
my previous comments on FA-HA nonce versus FA-HA SPI.<br>
</font><br>
<font face="Times New Roman, Times"><br>
29) In 5.1, attribute list is missing MIP-FA-NAI,<br>
</font><br>
<font face="arial" size=2 color="#000080">Madjid&gt;&gt; added<br>
</font><br>
<font face="Times New Roman, Times">MIP-MN-HA SPI and MIP-HA-to-MN-SPI
should change &quot;HA&quot; to &quot;FA&quot; <br>
</font><br>
<font face="arial" size=2 color="#000080">Madjid&gt;&gt;good catch on my
cut and pastes. Thanks.<br>
</font><br>
<font face="arial" size=2 color="#000080">&nbsp;<br>
</font><br>
<font face="Times New Roman, Times">before &quot;Encrypted&quot;, missing
Encrypted[MIP-MN-FA-key],<br>
</font><br>
<font face="arial" size=2 color="#000080">Madjid&gt;&gt;done.<br>
</font><br>
<font face="Times New Roman, Times"><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; new MIP-FA-HA-nonce, duplicate
MIP-MN-HA-MSA-LIFE.<br>
<br>
</font><font face="arial" size=2 color="#000080">Madjid&gt;&gt;previous
comment. Fixed duplicate.<br>
</font><br>
<font face="Times New Roman, Times"><br>
30) Sect 8, &quot;We recommend that the AAAH also authenticates the nonce
reply<br>
&nbsp;&nbsp;&nbsp;&nbsp; extensions with the AAA SA it shares with the
MN&quot;.&nbsp; This is for MITM attack for<br>
&nbsp;&nbsp;&nbsp;&nbsp; msg from AAAH to HA/FA.&nbsp; Doesn't the
Message-Authenticator protect tampering<br>
&nbsp;&nbsp;&nbsp;&nbsp; with the nonce value?<br>
</font><font face="Times New Roman, Times" color="#000080">Madjid&gt;&gt;
only from HA to MN, not over RADIUS from AAAH to MIP agents, at least, I
think this is what I meant.<br>
</font><br>
<font face="Times New Roman, Times"></font></blockquote><br>
Oh well, I'm still not clear.&nbsp; The Message-Authenticator AVP
should<br>
protect the nonce value between AAAH and MIP agents.&nbsp; The MHAE<br>
or MFAE should protect the nonce value between MN and HA or<br>
MN and FA, respectively.&nbsp; So what does AAAH also authenticates<br>
the nonce reply with SA with MN?&nbsp; The nonce will be use to
derive<br>
MHAE/MFAE key for authenticating RRP, which means that nonce<br>
could not have been tempered with.&nbsp; I'm missing something
probably?<br>
<br>
Thanks.<br>
<br>
Kent<br>
<br>
<br>
<div>--</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Kent Leung</div>
<div>&nbsp;&nbsp;&nbsp;
:|:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
:|:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
IP Mobility Development</div>
<div>&nbsp;&nbsp; :|||:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
:|||:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Internet Technologies Division</div>
<div>&nbsp; :|||||||:&nbsp;&nbsp;
:|||||||:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Voice: 408.526.5030</div>
<div>.:|||||||||:.:|||||||||:.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Fax:&nbsp;&nbsp; 408.525.1653</div>
&nbsp;c i s c o S y s t e m
s&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Email: kleung@cisco.com
</html>

--=====================_73646708==_.ALT--


--===============1903675047==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1903675047==--



From mip4-bounces@ietf.org  Thu Mar 31 13:29:44 2005
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 NAA19899
	for <mip4-web-archive@ietf.org>; Thu, 31 Mar 2005 13:29:43 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DH4XU-0001Tx-N6
	for mip4-web-archive@ietf.org; Thu, 31 Mar 2005 13:37:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DH4JC-0006PS-V6; Thu, 31 Mar 2005 13:22:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DGkDs-0005WS-4a; Wed, 30 Mar 2005 15:55:32 -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 PAA12630;
	Wed, 30 Mar 2005 15:55:30 -0500 (EST)
From: sudhir.dixit@nokia.com
Received: from mgw-x2.nokia.com ([131.228.20.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DGkKq-0003BI-Ei; Wed, 30 Mar 2005 16:02:45 -0500
Received: from esdks002.ntc.nokia.com (esdks002.ntc.nokia.com [172.21.138.121])
	by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	j2UKshg19732; Wed, 30 Mar 2005 23:54:44 +0300 (EET DST)
X-Scanned: Wed, 30 Mar 2005 23:54:27 +0300 Nokia Message Protector V1.3.34
	2004121512 - RELEASE
Received: (from root@localhost)
	by esdks002.ntc.nokia.com (8.12.9/8.12.9) id j2UKsRRB009727;
	Wed, 30 Mar 2005 23:54:27 +0300
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks002.ntc.nokia.com 00CZXirt; Wed, 30 Mar 2005 23:54:26 EEST
Received: from daebh001.NOE.Nokia.com (daebh001.americas.nokia.com
	[10.241.35.121])
	by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	j2UKsFU19216; Wed, 30 Mar 2005 23:54:15 +0300 (EET DST)
Received: from bsebe001.NOE.Nokia.com ([172.19.160.13]) by
	daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 30 Mar 2005 14:54:14 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 30 Mar 2005 15:54:12 -0500
Message-ID: <DC504E9C3384054C8506D3E6BB01246003929C40@bsebe001.americas.nokia.com>
Thread-Topic: [ontc] Call for Papers - COMSWARE 2006
Thread-Index: AcU0ksSL2E2HoTWaQkawcRbdp3aRPAA1vXwg
To: <sudhir.dixit@nokia.com>
X-OriginalArrivalTime: 30 Mar 2005 20:54:14.0672 (UTC)
	FILETIME=[A1C42900:01C5356A]
X-Spam-Score: 1.4 (+)
X-Scan-Signature: 32a65c0bf5eb4ec26489239c7cdd0636
X-Mailman-Approved-At: Thu, 31 Mar 2005 13:22:21 -0500
Subject: [Mip4] Call for Papers and Proposals for Tutorials and Panels
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>
Content-Type: multipart/mixed; boundary="===============1079762840=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 2.8 (++)
X-Scan-Signature: 9c7d7a899dc8f3389bf7ace6f0ad8e29

This is a multi-part message in MIME format.

--===============1079762840==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C5356A.A0B64840"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C5356A.A0B64840
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

(Our apologies if you receive multiple copies of this document)
  <outbind://49/cid:868394014@11032005-29F5>=20

=20
Wireless Personal Multimedia Communications
(WPMC'05)
 Sept 18-22, 2005 - Aalborg, Denmark

=20
Share your achievements within wireless with the rest of the world:



Submit a paper
  a tutorial, and/or a panel proposal


Deadline for abstract submission:  April 15 , 2005

To submit, follow instructions given at  <http://www.iws2005.org/> =
www.iws2005.org


Wireless Personal Multimedia Communications (WPMC) this year  is  a part =
of the First International Wireless Summit (IWS)

1000 participants are expected . Up to 8 parellel sessions including =
panel and invited paper sessions, selected tutorials and industrial =
exhibition.=20
=20
Call for Papers - Deadline extended!=20

The Organizing Committee for WPMC'05 invites you to submit extended =
abstracts on the following topics (but not limited to) by electronic =
submission in PDF format.

*	Track I: Antenna and Propagation=20

*	Track II: Transmission Technology=20

*	Track III: Digital Signal Processing=20

*	Track IV: Wireless Access=20

*	Track V: Multimedia, Networks and Systems=20

*	Track VI: Wireless Security=20

*	Track VII: Wireless Sensors and Data Fusion=20

*	Track VIII: Modeling and Simulation=20

*	Track IX: Satellite and Navigation=20

*	Track X: Other topics

 <http://www.iws2005.org/default.asp?menu=3D157>=20

Description of tracks.

Introduction <http://www.iws2005.org/default.asp?menu=3D153>  of =
abstract submission.

Award papers:
Six papers will be selected for the "Best Paper Award" among the =
contributed papers and there will also be the "Best Student Award".

Wireless Personal Communication:
An International Journal
Twenty papers including the Award Papers will be selected for =
publication in a special issue: "Latest Trends in Wireless =
Communication".

Special Sessions:
Special Sessions on "Hot Topics" will be organized. Especially, there =
will be special sessions on Wireless Security and Sensors.

Panel Sessions & Tutorials:
Interested persons are invited to submit proposals for panel sessions =
and/or halfday/fullday tutorials to the IWS Secretariat no later than =
March 31, 2005.

Proposals for tutorials and panel sessions with the following documents =
should be send to the organisers at email: organisers@iws2005.org :=20

1. For Tutorials:=20
   a. Short CV of the speaker=20
   b. Title and abstract of the tutorial
   c. Halfday or fullday tutorial
=20
2. For Panels:=20
   a.  Short CV of the panel organizer=20
   b. Short CVs of the speakers=20
   c. Title and abstract of the panel=20
   d. Title and abstract from the speakers=20

Deadline:
Extended abstracts (up to 1500 words): (Extended deadline )   April 15, =
2005

Notification of acceptance: May 15, 2005

Full paper submission: June 20, 2005


Looking forward to seeing you in Aalborg in September 2005.

Leif Heinzl
WPMC'05 TPC Chair

Neeli  Prasad

WPMC ' 05 Co-Chair =20


=20

------_=_NextPart_001_01C5356A.A0B64840
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 6.00.2800.1492" name=3DGENERATOR>
<STYLE>@font-face {
	font-family: Georgia;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.emailstyle17 {
	FONT-WEIGHT: normal; COLOR: windowtext; FONT-STYLE: normal; =
FONT-FAMILY: Georgia; TEXT-DECORATION: none
}
SPAN.EmailStyle18 {
	FONT-WEIGHT: normal; COLOR: windowtext; FONT-STYLE: normal; =
FONT-FAMILY: Georgia; TEXT-DECORATION: none
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV><FONT face=3DGeorgia size=3D2><SPAN=20
style=3D"FONT-SIZE: 11pt; FONT-FAMILY: Georgia"><STRONG>(Our apologies =
if you=20
receive multiple copies of this document)</STRONG></SPAN></FONT></DIV>
<DIV class=3DSection1><FONT face=3DGeorgia size=3D2><SPAN=20
style=3D"FONT-SIZE: 11pt; FONT-FAMILY: Georgia">
<DIV align=3Dright><IMG height=3D69 alt=3D""=20
src=3D"outbind://49/cid:868394014@11032005-29F5"=20
width=3D146><BR></DIV><BIG><BIG><FONT color=3D#3333ff><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>
<DIV>&nbsp;</DIV></FONT></FONT></BIG></BIG>
<DIV align=3Dcenter><FONT size=3D6><FONT face=3D"Arial Black"><FONT=20
size=3D3><B><BIG><BIG><FONT color=3D#3333ff>Wireless Personal Multimedia =

Communications<BR></FONT></BIG></BIG></B><B><BIG><BIG><FONT=20
color=3D#3333ff>(WPMC'05)</FONT></BIG></BIG></B></FONT><BR><B><BIG><BIG><=
FONT=20
color=3D#3333ff>&nbsp;<FONT size=3D4>Sept 18-22, 2005 - Aalborg,=20
Denmark</FONT></FONT></BIG></BIG></B><BR></FONT></FONT></DIV><BIG><BIG><F=
ONT=20
color=3D#3333ff><FONT face=3DArial color=3D#0000ff size=3D2>
<DIV>&nbsp;</DIV></FONT></FONT></BIG></BIG>
<DIV align=3Dcenter><FONT size=3D4><B><BIG><BIG><FONT =
color=3D#3333ff><FONT=20
face=3D"Helvetica, Arial, sans-serif"><SMALL><FONT color=3D#000000>Share =
your=20
achievements within wireless with the rest of the=20
world:</FONT></SMALL></FONT></FONT></BIG></BIG></B><BR></FONT></DIV><BIG>=
<BIG><FONT=20
color=3D#3333ff><FONT face=3D"Helvetica, Arial, sans-serif"><SMALL><FONT =

color=3D#000000>
<DIV><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT><BR></DIV></FONT></SMALL></FONT></FONT></BIG></BIG>
<DIV align=3Dcenter><B><BIG><BIG><FONT face=3D"Helvetica, Arial, =
sans-serif"=20
color=3D#0000ff><SMALL><BIG>Submit a paper<BR>&nbsp; a tutorial, and/or =
a panel=20
proposal</BIG></SMALL></FONT></BIG></BIG></B><BR></DIV><BIG><BIG><FONT=20
color=3D#3333ff><FONT face=3D"Helvetica, Arial, sans-serif"><SMALL><FONT =

color=3D#000000>
<DIV><BR><STRONG>Deadline for abstract submission:&nbsp;</STRONG><SPAN=20
class=3D703464720-30032005><FONT face=3DArial =
color=3D#0000ff>&nbsp;<STRONG><FONT=20
face=3DHelvetica color=3D#000000>April=20
15</FONT></STRONG>&nbsp;</FONT></SPAN><STRONG>,=20
2005</STRONG></FONT><BR><BR><STRONG><FONT color=3D#000000>To submit, =
follow=20
instructions given at</FONT> </STRONG><FONT color=3D#ff0000><BIG><A=20
class=3Dmoz-txt-link-abbreviated =
href=3D"http://www.iws2005.org/"><STRONG><FONT=20
size=3D4>www.iws2005.org</FONT></STRONG></A><BR><BR><SMALL><FONT =
color=3D#000000=20
size=3D4></DIV></FONT></SMALL></BIG></FONT></SMALL></FONT></FONT></BIG></=
BIG><FONT=20
face=3D"Helvetica, Arial, sans-serif">
<DIV>Wireless Personal Multimedia Communications (WPMC) this =
year&nbsp;<SPAN=20
class=3D703464720-30032005><FONT face=3DArial color=3D#0000ff =
size=3D2>&nbsp;is=20
&nbsp;</FONT></SPAN>a part of the First International Wireless Summit=20
(IWS)<BR><BR>1000 participants are expected . Up to 8 parellel sessions=20
including panel and invited paper sessions, selected tutorials and =
industrial=20
exhibition.<SPAN class=3D703464720-30032005><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>&nbsp;</FONT></SPAN></DIV>
<DIV><SPAN class=3D703464720-30032005></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D703464720-30032005><STRONG><FONT size=3D4>Call for=20
Papers</FONT></STRONG>&nbsp;<FONT size=3D4><STRONG>- Deadline=20
extended!</STRONG></FONT>
<P>The Organizing Committee for WPMC'05 invites you to submit extended =
abstracts=20
on the following topics (but not limited to) by electronic submission in =
PDF=20
format.</P>
<UL>
  <LI><STRONG>Track I: Antenna and Propagation</STRONG>=20
  <LI><STRONG>Track II: Transmission Technology</STRONG>=20
  <LI><STRONG>Track III: Digital Signal Processing</STRONG>=20
  <LI><STRONG>Track IV: Wireless Access</STRONG>=20
  <LI><STRONG>Track V: Multimedia, Networks and Systems</STRONG>=20
  <LI><STRONG>Track VI: Wireless Security</STRONG>=20
  <LI><STRONG>Track VII: Wireless Sensors and Data Fusion</STRONG>=20
  <LI><STRONG>Track VIII: Modeling and Simulation</STRONG>=20
  <LI><STRONG>Track IX: Satellite and Navigation</STRONG>=20
  <LI><STRONG>Track X: Other topics</STRONG></LI></UL><A=20
href=3D"http://www.iws2005.org/default.asp?menu=3D157">
<P>Description of tracks.</P>
<P></A><A=20
href=3D"http://www.iws2005.org/default.asp?menu=3D153">Introduction&nbsp;=
of abstract=20
submission.</A><BR><BR><STRONG>Award papers:</STRONG><BR>Six papers will =
be=20
selected for the "Best Paper Award" among the contributed papers and =
there will=20
also be the "Best Student Award".</P>
<P><STRONG>Wireless Personal Communication:<BR>An International=20
Journal<BR></STRONG>Twenty papers including the Award Papers will be =
selected=20
for publication in a special issue: "Latest Trends in Wireless=20
Communication".</P>
<P><STRONG>Special Sessions:<BR></STRONG>Special Sessions on "Hot =
Topics" will=20
be organized. Especially, there will be special sessions on Wireless =
Security=20
and Sensors.</P>
<P><STRONG>Panel Sessions &amp; Tutorials:<BR></STRONG>Interested =
persons are=20
invited to submit proposals for panel sessions and/or halfday/fullday =
tutorials=20
to the IWS Secretariat no later than March 31, 2005.</P>
<P>Proposals for tutorials and panel sessions with the following =
documents=20
should be send to the organisers at email: <FONT color=3D#3333ff><A=20
class=3Dmoz-txt-link-abbreviated=20
href=3D"mailto:organisers@iws2005.org">organisers@iws2005.org</A></FONT> =
:=20
<BR><BR>1. For Tutorials: <BR>&nbsp;&nbsp; a. Short CV of the speaker=20
<BR>&nbsp;&nbsp; b. Title and abstract of the tutorial<BR>&nbsp;&nbsp; =
c.=20
Halfday or fullday tutorial<BR>&nbsp;<BR>2. For Panels: <BR>&nbsp;&nbsp; =

a.&nbsp; Short CV of the panel organizer <BR>&nbsp;&nbsp; b. Short CVs =
of the=20
speakers <BR>&nbsp;&nbsp; c. Title and abstract of the panel =
<BR>&nbsp;&nbsp; d.=20
Title and abstract from the speakers =
<BR><BR><STRONG>Deadline:<BR></STRONG><FONT=20
size=3D3><SPAN class=3D703464720-30032005><FONT face=3DArial =
color=3D#0000ff><FONT=20
face=3DHelvetica color=3D#000000>Extended abstracts (up to 1500 words):=20
(</FONT></FONT></SPAN>Extended deadline<FONT face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D703464720-30032005>&nbsp;)&nbsp;</SPAN><SPAN=20
class=3D703464720-30032005>&nbsp;</SPAN></FONT></FONT></FONT> April 15,=20
2005</FONT></P>
<P><FONT size=3D3>Notification of acceptance: </FONT><FONT size=3D3>May =
15,=20
2005<BR><BR>Full paper submission: June 20,=20
2005</FONT></P></SPAN></FONT><SMALL><BIG><BIG><FONT =
color=3D#3333ff><FONT=20
face=3D"Helvetica, Arial, sans-serif"><SMALL><FONT=20
color=3D#ff0000><BIG><BR><SMALL><FONT color=3D#000000>Looking forward to =
seeing you=20
in Aalborg in September 2005.<BR><BR>Leif Heinzl<BR>WPMC'05 TPC=20
Chair<BR><BR>Neeli&nbsp;=20
Prasad<BR></DIV></FONT></SMALL></BIG></FONT></SMALL></FONT></FONT></BIG><=
/BIG></SMALL>
<DIV align=3Dleft><SMALL><BIG><BIG><FONT color=3D#3333ff><FONT=20
face=3D"Helvetica, Arial, sans-serif"><SMALL><FONT =
color=3D#ff0000><BIG><SMALL><FONT=20
color=3D#000000>WPMC<SPAN class=3D703464720-30032005><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>&nbsp;'&nbsp;</FONT></SPAN>05 Co-Chair&nbsp;=20
<BR><BR></FONT></SMALL></BIG></FONT></SMALL></FONT></FONT></BIG></BIG></S=
MALL></DIV>
<DIV align=3Dleft><FONT=20
color=3D#0000ff></FONT>&nbsp;</DIV></SPAN></FONT></DIV></BODY></HTML>

------_=_NextPart_001_01C5356A.A0B64840--


--===============1079762840==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1079762840==--



From mip4-bounces@ietf.org  Thu Mar 31 18:54:51 2005
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 SAA26254
	for <mip4-web-archive@ietf.org>; Thu, 31 Mar 2005 18:54:51 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DH9cC-00072V-TB
	for mip4-web-archive@ietf.org; Thu, 31 Mar 2005 19:02:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DH9TG-0001nU-UN; Thu, 31 Mar 2005 18:53:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DH9TE-0001mw-8O
	for mip4@megatron.ietf.org; Thu, 31 Mar 2005 18:53:04 -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 SAA26133
	for <mip4@ietf.org>; Thu, 31 Mar 2005 18:53:00 -0500 (EST)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DH9aP-0006zq-RC
	for mip4@ietf.org; Thu, 31 Mar 2005 19:00:30 -0500
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (Motorola/Motgate8) with ESMTP id j2VNtJ24010803
	for <mip4@ietf.org>; Thu, 31 Mar 2005 16:55:19 -0700 (MST)
Received: from il27exm03.cig.mot.com (il27exm03.cig.mot.com [10.17.193.4])
	by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id j2VNsgiZ017181
	for <mip4@ietf.org>; Thu, 31 Mar 2005 17:54:42 -0600 (CST)
Received: by il27exm03.cig.mot.com with Internet Mail Service (5.5.2657.72)
	id <GP0X2WV2>; Thu, 31 Mar 2005 17:52:59 -0600
Message-ID: <EBF631554F9CD7118D0B00065BF34DCB1837955C@il27exm03.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'Kent Leung'" <kleung@cisco.com>
Subject: RE: [Mip4] draft on RADIUS support for Mobile IP
Date: Thu, 31 Mar 2005 17:52:50 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
X-Spam-Score: 3.2 (+++)
X-Scan-Signature: 8eeb555810cda1f2c5989480370dc4ca
Cc: kchowdhury@starentnetworks.com, mip4@ietf.org, avi@bridgewatersystems.com
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>
Content-Type: multipart/mixed; boundary="===============1401254965=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 3.2 (+++)
X-Scan-Signature: bdfdd9dd835c9bb499f7c92933fef080

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============1401254965==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C5364C.BF4B7AB8"

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C5364C.BF4B7AB8
Content-Type: text/plain

Hi Kent,

 

I think the issue with NAI not fitting into the NAS_IP can be solved by simply adding optional 

MIP-FA-NAI and MIP-HA-NAI whenever needed. So the NAS_IP only carries the IP address of the MIP agent that carries the RADIUS Access Request. I think we should keep the optional NAIs there if RADIUS requires them.

Here is the suggested text that was added:

If the HA IP address is available from RRQ, the FA includes it inside MIP-HA-IP-address attribute. Otherwise the FA inserts the HA NAI from the RRQ inside the MIP-HA_ID attribute. Note that at least one of MIP-HA-IP-address and MIP-HA-NAI must be present for identification of the HA at the AAA server. If the NAIs are required for RADIUS routing, the FA include its own NAI inside the MIP-FA-ID and HA NAI inside MIP-HA-NAI. The following attributes are included in this request:

RADIUS-Access Request {

User-Name (MIP-MN-HoA or MIP-MN-NAI)

NAS-IP (MIP-FA-IP-address)

<MIP-HA-IP-address>(if available), 

<MIP-HA-NAI> if HA address all 1s or 0s)

<MIP-FA-ID> if the HA address is all 1s or all 0s),

.....

 

 

see other inline comments.




3) For CCoA mode Authenticator calculation, refer to 3012bis.  The Challenge
    is non-zero.  The MFCE is part of the RRQ sent from MN to HA.

Madjid>> Well, this is an area where 3012bis has problem. The challenge that the MN uses in MFCE can only come from the challenge extension inside agent advertisement from FAs (section 2). 3012bis does not define where the challenge come from if there is no FA (CcoA mode). So we had to replace the challenge with zero to be able to complete the MD5 hashing of RRQ for RADIUS as described in 3012bis.

3012bis said outside of scope.  The challenge value may be 0 or non-zero.
But the MFCE is required.  One method is the MN generates the challenge
value.

Madjid>>>>I see, we just taught the implementation would be easier if a CcoA MN inserts zeros. Not sure what a challenge generated by MN achieves? You do have the time stamp to protect the HA from replays.



 


Even if the HA is the NAS, the HA IP address and NAS IP address may be different.
Maybe this needs to be mentioned?  Only in the case that HA IP address is the same
as NAS IP address, then MIP-HA-IP is not needed.

Madjid>>>> added preliminary text for this, but why would HA IP<>NAS IP?

 


I think the FA-IP may be different than NAS-IP.  It doesn't hurt to have MIP-FA-NAI,
which can identify the FA which may be useful for dynamic HA assignment
in foreign network.

Madjid>>>> added, but same question as before?




12) "Upon receiving the reg" bullet, same issue with NAS-IP and MIP-HA identifier.
     Also, why are MIP-FA-to-HA-SPI and MIP-FA-HA-Authenticator AVPs included?
     See my opinion below.  May also want to have MIP-MN-FA-NAI as the FA
     identifier to index the MSA.  Another point to capture is the case when the
     FA-HA MSA exists (e.g. created by another MN which registered previously
     between the FA and HA).  Then the HA just authenticate the FHAE first
     before sending Access-Request to AAA server.

Madjid>> fixed NAS-IP (I think). Because, by now only FA got its keys. HA does not have them yet.

I thought the FA-to-HA-SPI will serve as an index for the AAA to find the key that it has generated for FA-HA. So whether it uses SPI or FA-NAI for lookup is something we need to agree on. And this is why I think a new FA-HA-nonce not needed. 



Agree with using FA id, HA id, and SPI to index the MSA.  But
why is the MIP-FA-HA-Authenticator in the msg?

Madjid>>>> You are right, I deleted it.

13) "The AAAH finds the FA-HA MSA" bullet, I think AAA should only be
     responsible to authenticate the MN and provide the keys to the HA, which
     is responsible to authenticate FHAE and MHAE (if there).  So AAA server
     should authenticate MN using the MIP-MN-AAA-SPI and 
     MIP-MN-AAA-Authenticator.  Also, if the AAA server receives the MIP-FA-HA-nonce,
     it can find the right FA-HA MSA to provide to HA.  

Madjid>> well, the framework is trying to accommodate FA-HA MSA establishment, so that "finds the MSA" thing is just so that the AAA can locate the keys that it gave to FA and give them to HA. Did we give the impression that the AAA server also verifies the FHAE? 


Yes.  When I saw the MIP-FA-HA-Authenticator, I assume that was used for 
authentication.  If only to look up MSA, the triplet will suffice.

Madjid>>>>MFHAuth deleted.



14) Same bullet as above, why does the Access-Accept include the MIP-MN-FA-XXX
      AVPs?  These were already delivered to the FA in the RADIUS exchange between
      FA and AAAF.

Because, my impression was that the HA builds both the MN-HA-nonce reply and MN-FA-nonce reply when it is building the RRP and before signing the MN-HA-AE. In that case the HA would need  that info, even though it was delivered to FA before.



I got that same impression.  But this doesn't see right to me since the
key nonce are protected by MHAE from HA, and MFAE from FA.  So
not sure why HA needs to handle MN-FA nonce.  Have to check the
draft to confirm.

Madjid>>>>Appreciate it.




Regards,

 

Madjid 


------_=_NextPart_001_01C5364C.BF4B7AB8
Content-Type: text/html
Content-Transfer-Encoding: base64

PGh0bWw+DQoNCjxoZWFkPg0KPE1FVEEgSFRUUC1FUVVJVj0iQ29udGVudC1UeXBlIiBDT05URU5U
PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXMtYXNjaWkiPg0KDQoNCjxtZXRhIG5hbWU9R2VuZXJhdG9y
IGNvbnRlbnQ9Ik1pY3Jvc29mdCBXb3JkIDEwIChmaWx0ZXJlZCkiPg0KDQo8c3R5bGU+DQo8IS0t
DQogLyogRm9udCBEZWZpbml0aW9ucyAqLw0KIEBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6V2lu
Z2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseTpCYXRhbmc7DQoJcGFub3NlLTE6MiAzIDYgMCAwIDEgMSAxIDEgMTt9DQpAZm9u
dC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJcQEJhdGFuZyI7DQoJcGFub3NlLTE6MiAzIDYgMCAwIDEg
MSAxIDEgMTt9DQogLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCiBwLk1zb05vcm1hbCwgbGkuTXNv
Tm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAw
MXB0Ow0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiI7
fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXtjb2xvcjpibHVlOw0KCXRleHQtZGVjb3Jh
dGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJ
e2NvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5
bGUxNw0KCXtmb250LWZhbWlseTpBcmlhbDsNCgljb2xvcjpuYXZ5O30NCnAuUkZDVGV4dCwgbGku
UkZDVGV4dCwgZGl2LlJGQ1RleHQNCgl7bWFyZ2luLXRvcDowaW47DQoJbWFyZ2luLXJpZ2h0OjBp
bjsNCgltYXJnaW4tYm90dG9tOjBpbjsNCgltYXJnaW4tbGVmdDouM2luOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglsaW5lLWhlaWdodDoxMi4wcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglm
b250LWZhbWlseToiQ291cmllciBOZXciO30NCkBwYWdlIFNlY3Rpb24xDQoJe3NpemU6OC41aW4g
MTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjI1aW4gMS4waW4gMS4yNWluO30NCmRpdi5TZWN0aW9u
MQ0KCXtwYWdlOlNlY3Rpb24xO30NCiAvKiBMaXN0IERlZmluaXRpb25zICovDQogb2wNCgl7bWFy
Z2luLWJvdHRvbTowaW47fQ0KdWwNCgl7bWFyZ2luLWJvdHRvbTowaW47fQ0KLS0+DQo8L3N0eWxl
Pg0KDQo8L2hlYWQ+DQoNCjxib2R5IGxhbmc9RU4tVVMgbGluaz1ibHVlIHZsaW5rPWJsdWU+DQoN
CjxkaXYgY2xhc3M9U2VjdGlvbjE+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48Zm9udCBzaXplPTIg
Y29sb3I9bmF2eSBmYWNlPUFyaWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6DQoxMC4wcHQ7Zm9u
dC1mYW1pbHk6QXJpYWw7Y29sb3I6bmF2eSc+SGkgS2VudCw8L3NwYW4+PC9mb250PjwvcD4NCg0K
PHAgY2xhc3M9TXNvTm9ybWFsPjxmb250IHNpemU9MiBjb2xvcj1uYXZ5IGZhY2U9QXJpYWw+PHNw
YW4gc3R5bGU9J2ZvbnQtc2l6ZToNCjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDtjb2xvcjpuYXZ5
Jz4mbmJzcDs8L3NwYW4+PC9mb250PjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxmb250IHNp
emU9MiBjb2xvcj1uYXZ5IGZhY2U9QXJpYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToNCjEwLjBw
dDtmb250LWZhbWlseTpBcmlhbDtjb2xvcjpuYXZ5Jz5JIHRoaW5rIHRoZSBpc3N1ZSB3aXRoIE5B
SSBub3QgZml0dGluZw0KaW50byB0aGUgTkFTX0lQIGNhbiBiZSBzb2x2ZWQgYnkgc2ltcGx5IGFk
ZGluZyBvcHRpb25hbCA8L3NwYW4+PC9mb250PjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxm
b250IHNpemU9MiBjb2xvcj1uYXZ5IGZhY2U9QXJpYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToN
CjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDtjb2xvcjpuYXZ5Jz5NSVAtRkEtTkFJIGFuZCBNSVAt
SEEtTkFJIHdoZW5ldmVyIG5lZWRlZC4NClNvIHRoZSBOQVNfSVAgb25seSBjYXJyaWVzIHRoZSBJ
UCBhZGRyZXNzIG9mIHRoZSBNSVAgYWdlbnQgdGhhdCBjYXJyaWVzIHRoZQ0KUkFESVVTIEFjY2Vz
cyBSZXF1ZXN0LiBJIHRoaW5rIHdlIHNob3VsZCBrZWVwIHRoZSBvcHRpb25hbCBOQUlzIHRoZXJl
IGlmIFJBRElVUw0KcmVxdWlyZXMgdGhlbS48L3NwYW4+PC9mb250PjwvcD4NCg0KPHAgY2xhc3M9
TXNvTm9ybWFsPjxmb250IHNpemU9MiBjb2xvcj1uYXZ5IGZhY2U9QXJpYWw+PHNwYW4gc3R5bGU9
J2ZvbnQtc2l6ZToNCjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDtjb2xvcjpuYXZ5Jz5IZXJlIGlz
IHRoZSBzdWdnZXN0ZWQgdGV4dCB0aGF0IHdhcyBhZGRlZDo8L3NwYW4+PC9mb250PjwvcD4NCg0K
PHAgY2xhc3M9UkZDVGV4dCBzdHlsZT0nbWFyZ2luLWxlZnQ6MGluJz48Zm9udCBzaXplPTMgY29s
b3I9cmVkDQpmYWNlPSJDb3VyaWVyIE5ldyI+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMi4wcHQ7
Y29sb3I6cmVkJz5JZiB0aGUgSEEgSVANCmFkZHJlc3MgaXMgYXZhaWxhYmxlIGZyb20gUlJRLCB0
aGUgRkEgaW5jbHVkZXMgaXQgaW5zaWRlIE1JUC1IQS1JUC1hZGRyZXNzDQphdHRyaWJ1dGUuIE90
aGVyd2lzZSB0aGUgRkEgaW5zZXJ0cyB0aGUgSEEgTkFJIGZyb20gdGhlIFJSUSBpbnNpZGUgdGhl
DQpNSVAtSEFfSUQgYXR0cmlidXRlLiBOb3RlIHRoYXQgYXQgbGVhc3Qgb25lIG9mIE1JUC1IQS1J
UC1hZGRyZXNzIGFuZCBNSVAtSEEtTkFJDQptdXN0IGJlIHByZXNlbnQgZm9yIGlkZW50aWZpY2F0
aW9uIG9mIHRoZSBIQSBhdCB0aGUgQUFBIHNlcnZlci4gSWYgdGhlIE5BSXMgYXJlDQpyZXF1aXJl
ZCBmb3IgUkFESVVTIHJvdXRpbmcsIHRoZSBGQSBpbmNsdWRlIGl0cyBvd24gTkFJIGluc2lkZSB0
aGUgTUlQLUZBLUlEDQphbmQgSEEgTkFJIGluc2lkZSBNSVAtSEEtTkFJLjwvc3Bhbj48L2ZvbnQ+
IFRoZSBmb2xsb3dpbmcgYXR0cmlidXRlcyBhcmUNCmluY2x1ZGVkIGluIHRoaXMgcmVxdWVzdDo8
L3A+DQoNCjxwIGNsYXNzPVJGQ1RleHQgc3R5bGU9J21hcmdpbi1sZWZ0OjEuOGluJz48Zm9udCBz
aXplPTMgZmFjZT0iQ291cmllciBOZXciPjxzcGFuDQpzdHlsZT0nZm9udC1zaXplOjEyLjBwdCc+
UkFESVVTLUFjY2VzcyBSZXF1ZXN0IHs8L3NwYW4+PC9mb250PjwvcD4NCg0KPHAgY2xhc3M9UkZD
VGV4dCBzdHlsZT0nbWFyZ2luLWxlZnQ6MS44aW4nPjxmb250IHNpemU9MyBmYWNlPSJDb3VyaWVy
IE5ldyI+PHNwYW4NCnN0eWxlPSdmb250LXNpemU6MTIuMHB0Jz5Vc2VyLU5hbWUgKE1JUC1NTi1I
b0Egb3IgTUlQLU1OLU5BSSk8L3NwYW4+PC9mb250PjwvcD4NCg0KPHAgY2xhc3M9UkZDVGV4dCBz
dHlsZT0nbWFyZ2luLWxlZnQ6MS44aW4nPjxmb250IHNpemU9MyBmYWNlPSJDb3VyaWVyIE5ldyI+
PHNwYW4NCnN0eWxlPSdmb250LXNpemU6MTIuMHB0Jz5OQVMtSVAgKE1JUC1GQS1JUC1hZGRyZXNz
KTwvc3Bhbj48L2ZvbnQ+PC9wPg0KDQo8cCBjbGFzcz1SRkNUZXh0IHN0eWxlPSdtYXJnaW4tbGVm
dDoxLjhpbic+PGZvbnQgc2l6ZT0zIGNvbG9yPXJlZA0KZmFjZT0iQ291cmllciBOZXciPjxzcGFu
IHN0eWxlPSdmb250LXNpemU6MTIuMHB0O2NvbG9yOnJlZCc+Jmx0O01JUC1IQS1JUC1hZGRyZXNz
Jmd0Ozwvc3Bhbj48L2ZvbnQ+KGlmDQphdmFpbGFibGUpLCA8L3A+DQoNCjxwIGNsYXNzPVJGQ1Rl
eHQgc3R5bGU9J21hcmdpbi1sZWZ0OjEuOGluJz48Zm9udCBzaXplPTMgY29sb3I9cmVkDQpmYWNl
PSJDb3VyaWVyIE5ldyI+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMi4wcHQ7Y29sb3I6cmVkJz4m
bHQ7TUlQLUhBLU5BSSZndDs8L3NwYW4+PC9mb250Pg0KaWYgSEEgYWRkcmVzcyBhbGwgMXMgb3Ig
MHMpPC9wPg0KDQo8cCBjbGFzcz1SRkNUZXh0IHN0eWxlPSdtYXJnaW4tbGVmdDoxLjhpbic+PGZv
bnQgc2l6ZT0zIGZhY2U9IkNvdXJpZXIgTmV3Ij48c3Bhbg0Kc3R5bGU9J2ZvbnQtc2l6ZToxMi4w
cHQnPiZsdDs8Zm9udCBjb2xvcj1yZWQ+PHNwYW4gc3R5bGU9J2NvbG9yOnJlZCc+TUlQLUZBLUlE
PC9zcGFuPjwvZm9udD4mZ3Q7DQppZiB0aGUgSEEgYWRkcmVzcyBpcyBhbGwgMXMgb3IgYWxsIDBz
KSw8L3NwYW4+PC9mb250PjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtYXJnaW4t
bGVmdDoxLjNpbjt0ZXh0LWluZGVudDouNWluJz48Zm9udCBzaXplPTINCmNvbG9yPW5hdnkgZmFj
ZT1BcmlhbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDsN
CmNvbG9yOm5hdnknPi4uLi4uPC9zcGFuPjwvZm9udD48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1h
bD48Zm9udCBzaXplPTIgY29sb3I9bmF2eSBmYWNlPUFyaWFsPjxzcGFuIHN0eWxlPSdmb250LXNp
emU6DQoxMC4wcHQ7Zm9udC1mYW1pbHk6QXJpYWw7Y29sb3I6bmF2eSc+Jm5ic3A7PC9zcGFuPjwv
Zm9udD48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48Zm9udCBzaXplPTIgY29sb3I9bmF2eSBm
YWNlPUFyaWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6DQoxMC4wcHQ7Zm9udC1mYW1pbHk6QXJp
YWw7Y29sb3I6bmF2eSc+Jm5ic3A7PC9zcGFuPjwvZm9udD48L3A+DQoNCjxwIGNsYXNzPU1zb05v
cm1hbD48Zm9udCBzaXplPTMgY29sb3I9bmF2eSBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPjxzcGFu
DQpzdHlsZT0nZm9udC1zaXplOjEyLjBwdDtjb2xvcjpuYXZ5Jz5zZWUgb3RoZXIgaW5saW5lIGNv
bW1lbnRzLjwvc3Bhbj48L2ZvbnQ+PGJyPg0KPGJyPg0KPGJyPg0KPC9wPg0KDQo8cCBjbGFzcz1N
c29Ob3JtYWw+PGZvbnQgc2l6ZT0zIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+PHNwYW4gc3R5bGU9
J2ZvbnQtc2l6ZToNCjEyLjBwdCc+MykgRm9yIENDb0EgbW9kZSBBdXRoZW50aWNhdG9yIGNhbGN1
bGF0aW9uLCByZWZlciB0byAzMDEyYmlzLiZuYnNwOyBUaGUNCkNoYWxsZW5nZTxicj4NCiZuYnNw
OyZuYnNwOyZuYnNwOyBpcyBub24temVyby4mbmJzcDsgVGhlIE1GQ0UgaXMgcGFydCBvZiB0aGUg
UlJRIHNlbnQgZnJvbSBNTg0KdG8gSEEuPGJyPg0KPGJyPg0KPC9zcGFuPjwvZm9udD48Zm9udCBz
aXplPTIgY29sb3I9bmF2eSBmYWNlPUFyaWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0
Ow0KZm9udC1mYW1pbHk6QXJpYWw7Y29sb3I6bmF2eSc+TWFkamlkJmd0OyZndDsgV2VsbCwgdGhp
cyBpcyBhbiBhcmVhIHdoZXJlDQozMDEyYmlzIGhhcyBwcm9ibGVtLiBUaGUgY2hhbGxlbmdlIHRo
YXQgdGhlIE1OIHVzZXMgaW4gTUZDRSBjYW4gb25seSBjb21lIGZyb20NCnRoZSBjaGFsbGVuZ2Ug
ZXh0ZW5zaW9uIGluc2lkZSBhZ2VudCBhZHZlcnRpc2VtZW50IGZyb20gRkFzIChzZWN0aW9uIDIp
Lg0KMzAxMmJpcyBkb2VzIG5vdCBkZWZpbmUgd2hlcmUgdGhlIGNoYWxsZW5nZSBjb21lIGZyb20g
aWYgdGhlcmUgaXMgbm8gRkEgKENjb0ENCm1vZGUpLiBTbyB3ZSBoYWQgdG8gcmVwbGFjZSB0aGUg
Y2hhbGxlbmdlIHdpdGggemVybyB0byBiZSBhYmxlIHRvIGNvbXBsZXRlIHRoZQ0KTUQ1IGhhc2hp
bmcgb2YgUlJRIGZvciBSQURJVVMgYXMgZGVzY3JpYmVkIGluIDMwMTJiaXMuPC9zcGFuPjwvZm9u
dD48YnI+DQo8YnI+DQozMDEyYmlzIHNhaWQgb3V0c2lkZSBvZiBzY29wZS4mbmJzcDsgVGhlIGNo
YWxsZW5nZSB2YWx1ZSBtYXkgYmUgMCBvciBub24temVyby48YnI+DQpCdXQgdGhlIE1GQ0UgaXMg
cmVxdWlyZWQuJm5ic3A7IE9uZSBtZXRob2QgaXMgdGhlIE1OIGdlbmVyYXRlcyB0aGUgY2hhbGxl
bmdlPGJyPg0KdmFsdWUuPGJyPg0KPGJyPg0KPGZvbnQgY29sb3I9bmF2eT48c3BhbiBzdHlsZT0n
Y29sb3I6bmF2eSc+TWFkamlkJmd0OyZndDsmZ3Q7Jmd0O0kgc2VlLCB3ZSBqdXN0DQp0YXVnaHQg
dGhlIGltcGxlbWVudGF0aW9uIHdvdWxkIGJlIGVhc2llciBpZiBhIENjb0EgTU4gaW5zZXJ0cyB6
ZXJvcy4gTm90IHN1cmUNCndoYXQgYSBjaGFsbGVuZ2UgZ2VuZXJhdGVkIGJ5IE1OIGFjaGlldmVz
PyBZb3UgZG8gaGF2ZSB0aGUgdGltZSBzdGFtcCB0bw0KcHJvdGVjdCB0aGUgSEEgZnJvbSByZXBs
YXlzLjwvc3Bhbj48L2ZvbnQ+PGJyPg0KPGJyPg0KPC9wPg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+
PGZvbnQgc2l6ZT0yIGNvbG9yPW5hdnkgZmFjZT1BcmlhbD48c3BhbiBzdHlsZT0nZm9udC1zaXpl
Og0KMTAuMHB0O2ZvbnQtZmFtaWx5OkFyaWFsO2NvbG9yOm5hdnknPiZuYnNwOzwvc3Bhbj48L2Zv
bnQ+PC9wPg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PGZvbnQgc2l6ZT0zIGZhY2U9IlRpbWVzIE5l
dyBSb21hbiI+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToNCjEyLjBwdCc+PGJyPg0KRXZlbiBpZiB0
aGUgSEEgaXMgdGhlIE5BUywgdGhlIEhBIElQIGFkZHJlc3MgYW5kIE5BUyBJUCBhZGRyZXNzIG1h
eSBiZQ0KZGlmZmVyZW50Ljxicj4NCk1heWJlIHRoaXMgbmVlZHMgdG8gYmUgbWVudGlvbmVkPyZu
YnNwOyBPbmx5IGluIHRoZSBjYXNlIHRoYXQgSEEgSVAgYWRkcmVzcyBpcw0KdGhlIHNhbWU8YnI+
DQphcyBOQVMgSVAgYWRkcmVzcywgdGhlbiBNSVAtSEEtSVAgaXMgbm90IG5lZWRlZC48YnI+DQo8
YnI+DQo8Zm9udCBjb2xvcj1uYXZ5PjxzcGFuIHN0eWxlPSdjb2xvcjpuYXZ5Jz5NYWRqaWQmZ3Q7
Jmd0OyZndDsmZ3Q7IGFkZGVkIHByZWxpbWluYXJ5DQp0ZXh0IGZvciB0aGlzLCBidXQgd2h5IHdv
dWxkIEhBIElQJmx0OyZndDtOQVMgSVA/PC9zcGFuPjwvZm9udD48YnI+DQo8YnI+DQo8L3NwYW4+
PC9mb250Pjxmb250IHNpemU9MiBjb2xvcj1uYXZ5IGZhY2U9QXJpYWw+PHNwYW4gc3R5bGU9J2Zv
bnQtc2l6ZToxMC4wcHQ7DQpmb250LWZhbWlseTpBcmlhbDtjb2xvcjpuYXZ5Jz4mbmJzcDs8L3Nw
YW4+PC9mb250PjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxmb250IHNpemU9MyBmYWNlPSJU
aW1lcyBOZXcgUm9tYW4iPjxzcGFuIHN0eWxlPSdmb250LXNpemU6DQoxMi4wcHQnPjxicj4NCkkg
dGhpbmsgdGhlIEZBLUlQIG1heSBiZSBkaWZmZXJlbnQgdGhhbiBOQVMtSVAuJm5ic3A7IEl0IGRv
ZXNuJ3QgaHVydCB0byBoYXZlDQpNSVAtRkEtTkFJLDxicj4NCndoaWNoIGNhbiBpZGVudGlmeSB0
aGUgRkEgd2hpY2ggbWF5IGJlIHVzZWZ1bCBmb3IgZHluYW1pYyBIQSBhc3NpZ25tZW50PGJyPg0K
aW4gZm9yZWlnbiBuZXR3b3JrLjxicj4NCjxicj4NCjxmb250IGNvbG9yPW5hdnk+PHNwYW4gc3R5
bGU9J2NvbG9yOm5hdnknPk1hZGppZCZndDsmZ3Q7Jmd0OyZndDsgYWRkZWQsIGJ1dA0Kc2FtZSBx
dWVzdGlvbiBhcyBiZWZvcmU/PC9zcGFuPjwvZm9udD48YnI+DQo8YnI+DQo8YnI+DQo8YnI+DQo8
YnI+DQoxMikgJnF1b3Q7VXBvbiByZWNlaXZpbmcgdGhlIHJlZyZxdW90OyBidWxsZXQsIHNhbWUg
aXNzdWUgd2l0aCBOQVMtSVAgYW5kDQpNSVAtSEEgaWRlbnRpZmllci48YnI+DQombmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsgQWxzbywgd2h5IGFyZSBNSVAtRkEtdG8tSEEtU1BJIGFuZCBNSVAtRkEt
SEEtQXV0aGVudGljYXRvcg0KQVZQcyBpbmNsdWRlZD88YnI+DQombmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsgU2VlIG15IG9waW5pb24gYmVsb3cuJm5ic3A7IE1heSBhbHNvIHdhbnQgdG8gaGF2ZQ0K
TUlQLU1OLUZBLU5BSSBhcyB0aGUgRkE8YnI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgaWRl
bnRpZmllciB0byBpbmRleCB0aGUgTVNBLiZuYnNwOyBBbm90aGVyIHBvaW50IHRvDQpjYXB0dXJl
IGlzIHRoZSBjYXNlIHdoZW4gdGhlPGJyPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IEZBLUhB
IE1TQSBleGlzdHMgKGUuZy4gY3JlYXRlZCBieSBhbm90aGVyIE1OIHdoaWNoDQpyZWdpc3RlcmVk
IHByZXZpb3VzbHk8YnI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgYmV0d2VlbiB0aGUgRkEg
YW5kIEhBKS4mbmJzcDsgVGhlbiB0aGUgSEEganVzdA0KYXV0aGVudGljYXRlIHRoZSBGSEFFIGZp
cnN0PGJyPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGJlZm9yZSBzZW5kaW5nIEFjY2Vzcy1S
ZXF1ZXN0IHRvIEFBQSBzZXJ2ZXIuPGJyPg0KPGJyPg0KPC9zcGFuPjwvZm9udD48Zm9udCBzaXpl
PTIgY29sb3I9bmF2eSBmYWNlPUFyaWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0Ow0K
Zm9udC1mYW1pbHk6QXJpYWw7Y29sb3I6bmF2eSc+TWFkamlkJmd0OyZndDsgZml4ZWQgTkFTLUlQ
IChJIHRoaW5rKS4gQmVjYXVzZSwNCmJ5IG5vdyBvbmx5IEZBIGdvdCBpdHMga2V5cy4gSEEgZG9l
cyBub3QgaGF2ZSB0aGVtIHlldC48YnI+DQo8L3NwYW4+PC9mb250Pjxicj4NCjxmb250IHNpemU9
MiBjb2xvcj1uYXZ5IGZhY2U9QXJpYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9u
dC1mYW1pbHk6DQpBcmlhbDtjb2xvcjpuYXZ5Jz5JIHRob3VnaHQgdGhlIEZBLXRvLUhBLVNQSSB3
aWxsIHNlcnZlIGFzIGFuIGluZGV4IGZvciB0aGUgQUFBDQp0byBmaW5kIHRoZSBrZXkgdGhhdCBp
dCBoYXMgZ2VuZXJhdGVkIGZvciBGQS1IQS4gU28gd2hldGhlciBpdCB1c2VzIFNQSSBvcg0KRkEt
TkFJIGZvciBsb29rdXAgaXMgc29tZXRoaW5nIHdlIG5lZWQgdG8gYWdyZWUgb24uIEFuZCB0aGlz
IGlzIHdoeSBJIHRoaW5rIGENCm5ldyBGQS1IQS1ub25jZSBub3QgbmVlZGVkLiA8L3NwYW4+PC9m
b250PjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxmb250IHNpemU9MyBmYWNlPSJUaW1lcyBO
ZXcgUm9tYW4iPjxzcGFuIHN0eWxlPSdmb250LXNpemU6DQoxMi4wcHQnPjxicj4NCjxicj4NCkFn
cmVlIHdpdGggdXNpbmcgRkEgaWQsIEhBIGlkLCBhbmQgU1BJIHRvIGluZGV4IHRoZSBNU0EuJm5i
c3A7IEJ1dDxicj4NCndoeSBpcyB0aGUgTUlQLUZBLUhBLUF1dGhlbnRpY2F0b3IgaW4gdGhlIG1z
Zz88YnI+DQo8YnI+DQo8Zm9udCBjb2xvcj1uYXZ5PjxzcGFuIHN0eWxlPSdjb2xvcjpuYXZ5Jz5N
YWRqaWQmZ3Q7Jmd0OyZndDsmZ3Q7IFlvdSBhcmUgcmlnaHQsDQpJIGRlbGV0ZWQgaXQuPC9zcGFu
PjwvZm9udD48YnI+DQo8YnI+DQoxMykgJnF1b3Q7VGhlIEFBQUggZmluZHMgdGhlIEZBLUhBIE1T
QSZxdW90OyBidWxsZXQsIEkgdGhpbmsgQUFBIHNob3VsZCBvbmx5IGJlPGJyPg0KJm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7IHJlc3BvbnNpYmxlIHRvIGF1dGhlbnRpY2F0ZSB0aGUgTU4gYW5kIHBy
b3ZpZGUgdGhlDQprZXlzIHRvIHRoZSBIQSwgd2hpY2g8YnI+DQombmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsgaXMgcmVzcG9uc2libGUgdG8gYXV0aGVudGljYXRlIEZIQUUgYW5kIE1IQUUgKGlmDQp0
aGVyZSkuJm5ic3A7IFNvIEFBQSBzZXJ2ZXI8YnI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsg
c2hvdWxkIGF1dGhlbnRpY2F0ZSBNTiB1c2luZyB0aGUgTUlQLU1OLUFBQS1TUEkgYW5kIDxicj4N
CiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBNSVAtTU4tQUFBLUF1dGhlbnRpY2F0b3IuJm5ic3A7
IEFsc28sIGlmIHRoZSBBQUENCnNlcnZlciByZWNlaXZlcyB0aGUgTUlQLUZBLUhBLW5vbmNlLDxi
cj4NCiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBpdCBjYW4gZmluZCB0aGUgcmlnaHQgRkEtSEEg
TVNBIHRvIHByb3ZpZGUgdG8NCkhBLiZuYnNwOyA8YnI+DQo8YnI+DQo8L3NwYW4+PC9mb250Pjxm
b250IHNpemU9MiBjb2xvcj1uYXZ5IGZhY2U9QXJpYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZTox
MC4wcHQ7DQpmb250LWZhbWlseTpBcmlhbDtjb2xvcjpuYXZ5Jz5NYWRqaWQmZ3Q7Jmd0OyB3ZWxs
LCB0aGUgZnJhbWV3b3JrIGlzIHRyeWluZyB0bw0KYWNjb21tb2RhdGUgRkEtSEEgTVNBIGVzdGFi
bGlzaG1lbnQsIHNvIHRoYXQgJnF1b3Q7ZmluZHMgdGhlIE1TQSZxdW90OyB0aGluZyBpcw0KanVz
dCBzbyB0aGF0IHRoZSBBQUEgY2FuIGxvY2F0ZSB0aGUga2V5cyB0aGF0IGl0IGdhdmUgdG8gRkEg
YW5kIGdpdmUgdGhlbSB0bw0KSEEuIERpZCB3ZSBnaXZlIHRoZSBpbXByZXNzaW9uIHRoYXQgdGhl
IEFBQSBzZXJ2ZXIgYWxzbyB2ZXJpZmllcyB0aGUgRkhBRT8gPC9zcGFuPjwvZm9udD48L3A+DQoN
CjxwIGNsYXNzPU1zb05vcm1hbD48Zm9udCBzaXplPTMgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj48
c3BhbiBzdHlsZT0nZm9udC1zaXplOg0KMTIuMHB0Jz48YnI+DQpZZXMuJm5ic3A7IFdoZW4gSSBz
YXcgdGhlIE1JUC1GQS1IQS1BdXRoZW50aWNhdG9yLCBJIGFzc3VtZSB0aGF0IHdhcyB1c2VkIGZv
ciA8YnI+DQphdXRoZW50aWNhdGlvbi4mbmJzcDsgSWYgb25seSB0byBsb29rIHVwIE1TQSwgdGhl
IHRyaXBsZXQgd2lsbCBzdWZmaWNlLjxicj4NCjxicj4NCjxmb250IGNvbG9yPW5hdnk+PHNwYW4g
c3R5bGU9J2NvbG9yOm5hdnknPk1hZGppZCZndDsmZ3Q7Jmd0OyZndDtNRkhBdXRoDQpkZWxldGVk
Ljwvc3Bhbj48L2ZvbnQ+PGJyPg0KPGJyPg0KPC9zcGFuPjwvZm9udD48L3A+DQoNCjxwIGNsYXNz
PU1zb05vcm1hbD48Zm9udCBzaXplPTMgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj48c3BhbiBzdHls
ZT0nZm9udC1zaXplOg0KMTIuMHB0Jz4xNCkgU2FtZSBidWxsZXQgYXMgYWJvdmUsIHdoeSBkb2Vz
IHRoZSBBY2Nlc3MtQWNjZXB0IGluY2x1ZGUgdGhlDQpNSVAtTU4tRkEtWFhYPGJyPg0KJm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IEFWUHM/Jm5ic3A7IFRoZXNlIHdlcmUgYWxyZWFkeSBk
ZWxpdmVyZWQgdG8gdGhlDQpGQSBpbiB0aGUgUkFESVVTIGV4Y2hhbmdlIGJldHdlZW48YnI+DQom
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgRkEgYW5kIEFBQUYuPGJyPg0KPGJyPg0KPC9z
cGFuPjwvZm9udD48Zm9udCBzaXplPTIgY29sb3I9bmF2eSBmYWNlPUFyaWFsPjxzcGFuIHN0eWxl
PSdmb250LXNpemU6MTAuMHB0Ow0KZm9udC1mYW1pbHk6QXJpYWw7Y29sb3I6bmF2eSc+QmVjYXVz
ZSwgbXkgaW1wcmVzc2lvbiB3YXMgdGhhdCB0aGUgSEEgYnVpbGRzDQpib3RoIHRoZSBNTi1IQS1u
b25jZSByZXBseSBhbmQgTU4tRkEtbm9uY2UgcmVwbHkgd2hlbiBpdCBpcyBidWlsZGluZyB0aGUg
UlJQDQphbmQgYmVmb3JlIHNpZ25pbmcgdGhlIE1OLUhBLUFFLiBJbiB0aGF0IGNhc2UgdGhlIEhB
IHdvdWxkIG5lZWQmbmJzcDsgdGhhdA0KaW5mbywgZXZlbiB0aG91Z2ggaXQgd2FzIGRlbGl2ZXJl
ZCB0byBGQSBiZWZvcmUuPC9zcGFuPjwvZm9udD48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48
Zm9udCBzaXplPTMgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj48c3BhbiBzdHlsZT0nZm9udC1zaXpl
Og0KMTIuMHB0Jz48YnI+DQo8YnI+DQpJIGdvdCB0aGF0IHNhbWUgaW1wcmVzc2lvbi4mbmJzcDsg
QnV0IHRoaXMgZG9lc24ndCBzZWUgcmlnaHQgdG8gbWUgc2luY2UgdGhlPGJyPg0Ka2V5IG5vbmNl
IGFyZSBwcm90ZWN0ZWQgYnkgTUhBRSBmcm9tIEhBLCBhbmQgTUZBRSBmcm9tIEZBLiZuYnNwOyBT
bzxicj4NCm5vdCBzdXJlIHdoeSBIQSBuZWVkcyB0byBoYW5kbGUgTU4tRkEgbm9uY2UuJm5ic3A7
IEhhdmUgdG8gY2hlY2sgdGhlPGJyPg0KZHJhZnQgdG8gY29uZmlybS48YnI+DQo8YnI+DQo8Zm9u
dCBjb2xvcj1uYXZ5PjxzcGFuIHN0eWxlPSdjb2xvcjpuYXZ5Jz5NYWRqaWQmZ3Q7Jmd0OyZndDsm
Z3Q7QXBwcmVjaWF0ZSBpdC48L3NwYW4+PC9mb250Pjxicj4NCjxicj4NCjxicj4NCjwvc3Bhbj48
L2ZvbnQ+PC9wPg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PGZvbnQgc2l6ZT0zIGNvbG9yPW5hdnkg
ZmFjZT0iVGltZXMgTmV3IFJvbWFuIj48c3Bhbg0Kc3R5bGU9J2ZvbnQtc2l6ZToxMi4wcHQ7Y29s
b3I6bmF2eSc+UmVnYXJkcyw8L3NwYW4+PC9mb250PjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFs
Pjxmb250IHNpemU9MyBjb2xvcj1uYXZ5IGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+PHNwYW4NCnN0
eWxlPSdmb250LXNpemU6MTIuMHB0O2NvbG9yOm5hdnknPiZuYnNwOzwvc3Bhbj48L2ZvbnQ+PC9w
Pg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PGZvbnQgc2l6ZT0zIGNvbG9yPW5hdnkgZmFjZT0iVGlt
ZXMgTmV3IFJvbWFuIj48c3Bhbg0Kc3R5bGU9J2ZvbnQtc2l6ZToxMi4wcHQ7Y29sb3I6bmF2eSc+
TWFkamlkPC9zcGFuPjwvZm9udD4gPC9wPg0KDQo8L2Rpdj4NCg0KPC9ib2R5Pg0KDQo8L2h0bWw+
DQo=

------_=_NextPart_001_01C5364C.BF4B7AB8--


--===============1401254965==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1401254965==--



From mip4-bounces@ietf.org  Thu Mar 31 23:18:00 2005
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 XAA15062
	for <mip4-web-archive@ietf.org>; Thu, 31 Mar 2005 23:18:00 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DHDiu-0007cX-Os
	for mip4-web-archive@ietf.org; Thu, 31 Mar 2005 23:25:32 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DHDZ0-0006MN-F9; Thu, 31 Mar 2005 23:15:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DHDYT-0006DQ-KK
	for mip4@megatron.ietf.org; Thu, 31 Mar 2005 23:14:45 -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 XAA14909
	for <mip4@ietf.org>; Thu, 31 Mar 2005 23:14:43 -0500 (EST)
Received: from palrel13.hp.com ([156.153.255.238])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHDfh-0007TN-UD
	for mip4@ietf.org; Thu, 31 Mar 2005 23:22:15 -0500
Received: from athira.india.hp.com (athira.india.hp.com [15.42.231.28])
	by palrel13.hp.com (Postfix) with ESMTP id 3879E1CEDE9B
	for <mip4@ietf.org>; Thu, 31 Mar 2005 20:14:40 -0800 (PST)
Received: (from chaitra@localhost)
	by athira.india.hp.com (8.9.3 (PHNE_25184)/8.9.3 SMKit7.02) id KAA12162
	for mip4@ietf.org; Fri, 1 Apr 2005 10:03:48 +0530 (IST)
From: Chaitra M R <chaitra@india.hp.com>
Message-Id: <200504010433.KAA12162@athira.india.hp.com>
To: mip4@ietf.org
Date: Fri, 1 Apr 2005 10:03:48 +0530 (IST)
X-Mailer: ELM []
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit
Subject: [Mip4] A query about CCOA..
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit

Hi All,

  Sorry if this  question  sounds  naive.  I am new into the  mobility
  realm and hence have many doubts. Please bear with me.

  This  doubt  is  about  co-located  care  of  address.  From  what I
  understand,  using  co-located   address  does  not  necessiate  the
  services of FA right?

  Given that the foreign  network on to which the MN has moved doesn't
  have an FA and the MN uses  CCOA,  how can a mobile  node  determine
  that it has moved to a foreign network?

Regards,
Chaitra

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


From mip4-bounces@ietf.org  Thu Mar 31 23:56:08 2005
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 XAA18035
	for <mip4-web-archive@ietf.org>; Thu, 31 Mar 2005 23:56:08 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DHEJp-0000ag-Fs
	for mip4-web-archive@ietf.org; Fri, 01 Apr 2005 00:03:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DHE9g-0003HT-3M; Thu, 31 Mar 2005 23:53:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DHE9e-0003HG-26
	for mip4@megatron.ietf.org; Thu, 31 Mar 2005 23:53:10 -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 XAA17793
	for <mip4@ietf.org>; Thu, 31 Mar 2005 23:53:07 -0500 (EST)
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.33)
	id 1DHEGt-0000IS-4O
	for mip4@ietf.org; Fri, 01 Apr 2005 00:00:40 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 31 Mar 2005 20:52:59 -0800
X-IronPort-AV: i="3.91,139,1110182400"; 
	d="scan'208"; a="243969254:sNHT25660682"
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j314qvDr000333;
	Thu, 31 Mar 2005 20:52:57 -0800 (PST)
Received: from kleung-w2k01.cisco.com (sjc-vpn6-815.cisco.com [10.21.123.47])
	by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with ESMTP id BDN69803;
	Thu, 31 Mar 2005 20:51:47 -0800 (PST)
Message-Id: <4.3.2.7.2.20050331203755.030ae968@mira-sjcm-2.cisco.com>
X-Sender: kleung@mira-sjcm-2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 31 Mar 2005 20:48:08 -0800
To: Chaitra M R <chaitra@india.hp.com>
From: Kent Leung <kleung@cisco.com>
Subject: Re: [Mip4] A query about CCOA..
In-Reply-To: <200504010433.KAA12162@athira.india.hp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
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>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336

Hi Chaitra.  The doubts are legitimate as I don't think RFC 3344 covers
the specifics of move detection in CCoA mode.  However, CCoA mode
requires the MN to obtain an IP address on the access network.
Typically this is DHCP or PPP/IPCP.  Both provide the subnet prefix
which allows the MN to detect if it has changed subnet.  In addition,
the IP address would have also changed as well in this case.

Hope that helps.

Kent

At 10:03 AM 4/1/2005 +0530, Chaitra M R wrote:
>Hi All,
>
>   Sorry if this  question  sounds  naive.  I am new into the  mobility
>   realm and hence have many doubts. Please bear with me.
>
>   This  doubt  is  about  co-located  care  of  address.  From  what I
>   understand,  using  co-located   address  does  not  necessiate  the
>   services of FA right?
>
>   Given that the foreign  network on to which the MN has moved doesn't
>   have an FA and the MN uses  CCOA,  how can a mobile  node  determine
>   that it has moved to a foreign network?
>
>Regards,
>Chaitra
>
>--
>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/

--
      |           |                   Kent Leung
     :|:         :|:                  IP Mobility Development
    :|||:       :|||:                 Internet Technologies Division
   :|||||||:   :|||||||:              Voice: 408.526.5030
.:|||||||||:.:|||||||||:.             Fax:   408.525.1653
  c i s c o S y s t e m s             Email: kleung@cisco.com

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


