Re: [Mipshop] home addr option doubt

Rajeev Koodli <rajeev@iprg.nokia.com> Thu, 07 April 2005 21:51 UTC

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 RAA11731 for <mipshop-web-archive@ietf.org>; Thu, 7 Apr 2005 17:51:18 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJf2v-0004FE-Fs for mipshop-web-archive@ietf.org; Thu, 07 Apr 2005 18:00:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJemz-0005DD-4i; Thu, 07 Apr 2005 17:43:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJemx-0005D8-DN for mipshop@megatron.ietf.org; Thu, 07 Apr 2005 17:43:47 -0400
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 RAA11070 for <mipshop@ietf.org>; Thu, 7 Apr 2005 17:43:44 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJevZ-0003zk-LL for mipshop@ietf.org; Thu, 07 Apr 2005 17:52:43 -0400
Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j37LE1g13336; Thu, 7 Apr 2005 14:14:01 -0700
X-mProtect: <200504072114> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (172.18.141.46, claiming to be "[127.0.0.1]") by darkstar.iprg.nokia.com smtpdPWasce; Thu, 07 Apr 2005 14:13:59 PDT
Message-ID: <4255A974.3000004@iprg.nokia.com>
Date: Thu, 07 Apr 2005 14:43:16 -0700
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: emcho@clarinet.u-strasbg.fr
Subject: Re: [Mipshop] home addr option doubt
References: <4253D958.7000101@clarinet.u-strasbg.fr> <42548E71.2070807@iprg.nokia.com> <42550D8E.7030200@clarinet.u-strasbg.fr>
In-Reply-To: <42550D8E.7030200@clarinet.u-strasbg.fr>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Content-Transfer-Encoding: 7bit
Cc: mipshop@ietf.org, Vijay Devarapalli <vijayd@iprg.nokia.com>
X-BeenThere: mipshop@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mipshop.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mipshop>, <mailto:mipshop-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mipshop@ietf.org>
List-Help: <mailto:mipshop-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mipshop>, <mailto:mipshop-request@ietf.org?subject=subscribe>
Sender: mipshop-bounces@ietf.org
Errors-To: mipshop-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
Content-Transfer-Encoding: 7bit

Hello Emil,

the "Home Address Option" is borrowed from MIPv6, and hence
is always included with the FBU.

What would you like to see clarified?
"Home Address Option" => "Home Address Destination Option" in 6.3.1?
This might be possible in the final proof-reading, if not we can address it
in the next avatar.

Thanks,

-Rajeev


Emil Ivov wrote:

> Thanks for the reply Vijay,
>
> Don't you guys think that it might be handy to have a few words on 
> that in the draft? It might be just me, but it didn't  seem that 
> obvious when I read it.
>
> Emil
>
> Vijay Devarapalli wrote:
>
>> Emil Ivov wrote:
>>
>>> Hello,
>>>
>>> We had a little trouble understanding the exact place where a Home
>>> Address option is to be included.
>>>
>>> All that Section 6.3.1 of draft-ietf-mipshop-fast-mipv6-03.txt says is:
>>> The FBU MUST also include the Home Address Option and the Home
>>> Address is PCoA.
>>>
>>> One way to do it would be to include the Home Address Option as an
>>> option of the FBU itself.
>>>     If that is the case shouldn't this be clarified a bit more? It 
>>> could
>>> probably also be included in the  "Mobility Options" part of the 
>>> message
>>> format together with:
>>>
>>>       MUST contain alternate CoA option set to NCoA IP
>>>       address when FBU is sent from PAR's link.
>>>
>>> Another way to send the HAO would be to include it in a destination
>>> options header as with BUs?
>>
>>
>>
>> section 6.3.1 is talking about the Home Address Option in a destination
>> options header. not as a mobility option.
>>
>>>     If this is the case how should it be transported when an FBU is
>>> encapsulated in an FNA? As a destination option of the FNA, or should
>>> the AR addit when resending the FBU?
>>
>>
>>
>> the FBU will be an IP packet inside the FNA. the payload proto field
>> in FNA will be set to IPv6. here is the packet format
>>
>>   IPv6 hdr (src=nCoA, dst=NAR)
>>   Mobility Hdr
>>       FNA
>>   IPv6 hdr (src=nCoA, dst=PAR)
>>   Dst Opts hdr
>>       Home Address option (pCoA)
>>   Mobility Hdr
>>       FBU
>>
>> the NAR first processes the FNA part of the packet. if nCoA is valid,
>> it forwards the inner IP packet to the PAR.
>>
>>   IPv6 hdr (src=nCoA, dst=PAR)
>>   Dst Opts hdr
>>       Home Address option (pCoA)
>>   Mobility Hdr
>>       FBU
>>
>> Vijay
>>
>> _______________________________________________
>> Mipshop mailing list
>> Mipshop@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mipshop
>>
>
> _______________________________________________
> Mipshop mailing list
> Mipshop@ietf.org
> https://www1.ietf.org/mailman/listinfo/mipshop



_______________________________________________
Mipshop mailing list
Mipshop@ietf.org
https://www1.ietf.org/mailman/listinfo/mipshop