Re: [Seamoby] DoCoMo Implementation Issues with CTP
"Raghu" <dendukuri@docomolabs-usa.com> Fri, 20 February 2004 02:15 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 VAA11790 for <seamoby-archive@odin.ietf.org>; Thu, 19 Feb 2004 21:15:59 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Au0CS-0006jD-3I for seamoby-archive@odin.ietf.org; Thu, 19 Feb 2004 21:15:32 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1K2FWRJ025857 for seamoby-archive@odin.ietf.org; Thu, 19 Feb 2004 21:15:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Au0CS-0006iy-06 for seamoby-web-archive@optimus.ietf.org; Thu, 19 Feb 2004 21:15:32 -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 VAA11778 for <seamoby-web-archive@ietf.org>; Thu, 19 Feb 2004 21:15:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Au0CP-0006n9-00 for seamoby-web-archive@ietf.org; Thu, 19 Feb 2004 21:15:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Au0BT-0006kp-00 for seamoby-web-archive@ietf.org; Thu, 19 Feb 2004 21:14:31 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1Au0Az-0006ih-00 for seamoby-web-archive@ietf.org; Thu, 19 Feb 2004 21:14:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Au0B0-0006Ui-AK; Thu, 19 Feb 2004 21:14:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Au0Ab-0006Tc-Mm for seamoby@optimus.ietf.org; Thu, 19 Feb 2004 21:13:37 -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 VAA11730 for <seamoby@ietf.org>; Thu, 19 Feb 2004 21:13:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Au0AZ-0006i4-00 for seamoby@ietf.org; Thu, 19 Feb 2004 21:13:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Au09d-0006fp-00 for seamoby@ietf.org; Thu, 19 Feb 2004 21:12:37 -0500
Received: from key1.docomolabs-usa.com ([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser) by ietf-mx with esmtp (Exim 4.12) id 1Au09R-0006d5-00 for seamoby@ietf.org; Thu, 19 Feb 2004 21:12:25 -0500
Message-ID: <025301c3f756$ce90a560$1c6015ac@dcldendukuri>
From: Raghu <dendukuri@docomolabs-usa.com>
To: Rajeev Koodli <rajeev@iprg.nokia.com>
Cc: seamoby@ietf.org
References: <059c01c3f5a4$63e9e360$936015ac@dclkempt40> <40341585.127EE1A7@iprg.nokia.com> <023601c3f744$49c01df0$1c6015ac@dcldendukuri> <40355C74.22D0A058@iprg.nokia.com> <024601c3f750$0902ab00$1c6015ac@dcldendukuri> <40356445.C6D3270@iprg.nokia.com>
Subject: Re: [Seamoby] DoCoMo Implementation Issues with CTP
Date: Thu, 19 Feb 2004 18:11:09 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
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.0 required=5.0 tests=none 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. > IP Dest is the confusing part, I guess clarification in the draft, helps. Question based on your suggestion, When Context trigger is generated, pAR sends PCTD to nAR. Let us say, IP Dest = NAR's IP (IPv4) is used and IP Src = PAR's IP (IPv4) is used to send PCTD to nAR When MN sends CTAR with PAR= IPv6 to nAR, How does nAR verify and enable the contexts ? > 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. > This description in the draft may clarify things, but how to identify the IP version AR in CT messages. I guess another V flag for AR might simply things. 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