Re: [Seamoby] DoCoMo Implementation Issues with CTP
Rajeev Koodli <rajeev@iprg.nokia.com> Fri, 20 February 2004 01:46 UTC
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10703 for <seamoby-archive@odin.ietf.org>; Thu, 19 Feb 2004 20:46:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Atzk4-0004P4-7u for seamoby-archive@odin.ietf.org; Thu, 19 Feb 2004 20:46:12 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1K1kCdP016920 for seamoby-archive@odin.ietf.org; Thu, 19 Feb 2004 20:46:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Atzk4-0004Op-3t for seamoby-web-archive@optimus.ietf.org; Thu, 19 Feb 2004 20:46:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10627 for <seamoby-web-archive@ietf.org>; Thu, 19 Feb 2004 20:46:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Atzk1-0004xo-00 for seamoby-web-archive@ietf.org; Thu, 19 Feb 2004 20:46:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Atzia-0004nz-00 for seamoby-web-archive@ietf.org; Thu, 19 Feb 2004 20:44:41 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1AtziH-0004k8-01 for seamoby-web-archive@ietf.org; Thu, 19 Feb 2004 20:44:21 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by mx2.foretec.com with esmtp (Exim 4.24) id 1AtzcB-0006LO-9s for seamoby-web-archive@ietf.org; Thu, 19 Feb 2004 20:38:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtzcA-0003rl-CW; Thu, 19 Feb 2004 20:38:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Atzbf-0003jn-Uq for seamoby@optimus.ietf.org; Thu, 19 Feb 2004 20:37:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10357 for <seamoby@ietf.org>; Thu, 19 Feb 2004 20:37:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Atzbd-0004K5-00 for seamoby@ietf.org; Thu, 19 Feb 2004 20:37:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Atzam-0004Hm-00 for seamoby@ietf.org; Thu, 19 Feb 2004 20:36:36 -0500
Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1AtzZy-0004Bt-00 for seamoby@ietf.org; Thu, 19 Feb 2004 20:35:46 -0500
Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i1K1ZFH24843; Thu, 19 Feb 2004 17:35:15 -0800
X-mProtect: <200402200135> Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdEAa6wZ; Thu, 19 Feb 2004 17:35:11 PST
Message-ID: <40356445.C6D3270@iprg.nokia.com>
Date: Thu, 19 Feb 2004 17:35:01 -0800
From: Rajeev Koodli <rajeev@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: Raghu <dendukuri@docomolabs-usa.com>
CC: seamoby@ietf.org
Subject: Re: [Seamoby] DoCoMo Implementation Issues with CTP
References: <059c01c3f5a4$63e9e360$936015ac@dclkempt40> <40341585.127EE1A7@iprg.nokia.com> <023601c3f744$49c01df0$1c6015ac@dcldendukuri> <40355C74.22D0A058@iprg.nokia.com> <024601c3f750$0902ab00$1c6015ac@dcldendukuri>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>, <mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>, <mailto:seamoby-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
> > I understand your point, but > I request you to explain how the implementation should be > in the following scenario ? > > When MN moves, MN sends CTAR to nAR, > nAR needs to extract IP information from CTAR and send a CTREQ to oAR. > When both(IPv4 & IPv6) are present in CTAR, What is the behaviour of nAR ? > In CTREQ, set `V' to 10, include both IPv4 and IPv6 addresses in "Mobile Node's Previous IP Address" field, construct IP Dest = PAR's IP (v4 _or_ v6) address provided in CTAR IP Src = NAR's IP (v4 or v6) address. Is the confusion in whether `V' bits also refer to PAR and NAR addresses ? If so, we should clarify that they refer to MN's IP addresses only, and that the router address must be either IPv4 or IPv6 but not both. -Rajeev > > regards, > Raghu _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby
- [Seamoby] DoCoMo Implementation Issues with CTP James Kempf
- RE: [Seamoby] DoCoMo Implementation Issues with C… john.loughney
- Re: [Seamoby] DoCoMo Implementation Issues with C… Rajeev Koodli
- Re: [Seamoby] DoCoMo Implementation Issues with C… Raghu
- Re: [Seamoby] DoCoMo Implementation Issues with C… Rajeev Koodli
- Re: [Seamoby] DoCoMo Implementation Issues with C… Raghu
- Re: [Seamoby] DoCoMo Implementation Issues with C… Rajeev Koodli
- Re: [Seamoby] DoCoMo Implementation Issues with C… Raghu
- Re: [Seamoby] DoCoMo Implementation Issues with C… Rajeev Koodli
- Re: [Seamoby] DoCoMo Implementation Issues with C… Raghu
- RE: [Seamoby] DoCoMo Implementation Issues with C… Soliman Hesham
- Re: [Seamoby] DoCoMo Implementation Issues with C… Raghu
- RE: [Seamoby] DoCoMo Implementation Issues with C… Soliman Hesham
- Re: [Seamoby] DoCoMo Implementation Issues with C… James Kempf
- Re: [Seamoby] DoCoMo Implementation Issues with C… James Kempf
- Re: [Seamoby] DoCoMo Implementation Issues with C… James Kempf
- Re: [Seamoby] DoCoMo Implementation Issues with C… Rajeev Koodli
- Re: [Seamoby] DoCoMo Implementation Issues with C… Raghu
- Re: [Seamoby] DoCoMo Implementation Issues with C… Rajeev Koodli
- Re: [Seamoby] DoCoMo Implementation Issues with C… Rajeev Koodli
- Re: [Seamoby] DoCoMo Implementation Issues with C… Raghu
- Re: [Seamoby] DoCoMo Implementation Issues with C… Rajeev Koodli
- Re: [Seamoby] DoCoMo Implementation Issues with C… Raghu
- Re: [Seamoby] DoCoMo Implementation Issues with C… Rajeev Koodli
- Re: [Seamoby] DoCoMo Implementation Issues with C… Raghu
- Re: [Seamoby] DoCoMo Implementation Issues with C… James Kempf
- Re: [Seamoby] DoCoMo Implementation Issues with C… Rajeev Koodli
- Re: [Seamoby] DoCoMo Implementation Issues with C… James Kempf