Re: [Seamoby] DoCoMo Implementation Issues with CTP
Rajeev Koodli <rajeev@iprg.nokia.com> Fri, 20 February 2004 02:37 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 VAA12590 for <seamoby-archive@odin.ietf.org>; Thu, 19 Feb 2004 21:37:05 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Au0Wr-00083I-Qt for seamoby-archive@odin.ietf.org; Thu, 19 Feb 2004 21:36:37 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1K2abdx030948 for seamoby-archive@odin.ietf.org; Thu, 19 Feb 2004 21:36:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Au0Wr-000835-N5 for seamoby-web-archive@optimus.ietf.org; Thu, 19 Feb 2004 21:36: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 VAA12572 for <seamoby-web-archive@ietf.org>; Thu, 19 Feb 2004 21:36:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Au0Wo-0000L5-00 for seamoby-web-archive@ietf.org; Thu, 19 Feb 2004 21:36:34 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Au0Vx-0000I1-00 for seamoby-web-archive@ietf.org; Thu, 19 Feb 2004 21:35:42 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1Au0VI-0000Eh-00 for seamoby-web-archive@ietf.org; Thu, 19 Feb 2004 21:35:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Au0VK-0007pe-Lk; Thu, 19 Feb 2004 21:35:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Au0Uv-0007op-2S for seamoby@optimus.ietf.org; Thu, 19 Feb 2004 21:34: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 VAA12516 for <seamoby@ietf.org>; Thu, 19 Feb 2004 21:34:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Au0Us-0000DJ-00 for seamoby@ietf.org; Thu, 19 Feb 2004 21:34:34 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Au0U4-0000AZ-00 for seamoby@ietf.org; Thu, 19 Feb 2004 21:33:45 -0500
Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1Au0TV-00004r-00 for seamoby@ietf.org; Thu, 19 Feb 2004 21:33:09 -0500
Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i1K2Wca18367; Thu, 19 Feb 2004 18:32:38 -0800
X-mProtect: <200402200232> 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 smtpdUukRLY; Thu, 19 Feb 2004 18:32:36 PST
Message-ID: <403571BA.47BE98BB@iprg.nokia.com>
Date: Thu, 19 Feb 2004 18:32:26 -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> <40356445.C6D3270@iprg.nokia.com> <02
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
Raghu wrote: > 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 ? > Well, CTAR includes MN's IP(v4,v6) addresses. So does PCTD. So, nAR can still match the contexts. Since the token does not include PAR's address, verification can still be done. > > > 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. > Perhaps this is not necessary. (See above) -Rajeev > > > regards, > Raghu > > _______________________________________________ > Seamoby mailing list > Seamoby@ietf.org > https://www1.ietf.org/mailman/listinfo/seamoby _______________________________________________ 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