RE: [Seamoby] delay data requested

Phillip Neumiller <PNeumiller@meshnetworks.com> Wed, 09 January 2002 19:25 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13128 for <seamoby-archive@odin.ietf.org>; Wed, 9 Jan 2002 14:25:31 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA16338; Wed, 9 Jan 2002 14:07:42 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA16308 for <seamoby@optimus.ietf.org>; Wed, 9 Jan 2002 14:07:40 -0500 (EST)
Received: from meshpdc.meshnetworks.com ([205.245.27.196]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12331 for <seamoby@ietf.org>; Wed, 9 Jan 2002 14:07:37 -0500 (EST)
Received: by meshpdc.meshnetworks.com with Internet Mail Service (5.5.2653.19) id <Z720RP1N>; Wed, 9 Jan 2002 14:07:24 -0500
Message-ID: <0DF9FBC42474A24CA50F7A27FB08E04861667E@meshpdc.meshnetworks.com>
From: Phillip Neumiller <PNeumiller@meshnetworks.com>
To: "'Shahrier, Sharif M.'" <Sharif.Shahrier@interdigital.com>, "'mobileip@sunroof.eng.sun.com'" <mobileip@sunroof.eng.sun.com>
Cc: seamoby@ietf.org
Subject: RE: [Seamoby] delay data requested
Date: Wed, 09 Jan 2002 14:07:18 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19940.DBE1A780"
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org

Hi Shahrier,
 
This is a very good question.
 
1).  Since CT has to support inter-domain transfers, I would suspect these
would take 
      longer than intra-domain.  Then again, I am not sure if you are
referring to SeaMoby
      CT or something else???  The way the CT requirements read there is a
built in
      dependency on forming  a security association with the newAR before a
CT can
      take place, so that can also delay things considerably I imagine.
 
2).  In the best case, your ARs are joined on a fixed network with very low
latency
      probably << 1 ms I would imagine.
 
I am sure others will have some thoughts on this.  I am not sure if I
understood your
question though.
 
Best regards,
 
Phil
 

--
Mesh Networks, Inc. (www.meshnetworks.com)
Phillip D. Neumiller, Staff Scientist
pneumiller@meshnetworks.com PH: 1-407-659-5387 

-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@interdigital.com]
Sent: Wednesday, January 09, 2002 11:36 AM
To: 'mobileip@sunroof.eng.sun.com'
Cc: seamoby@ietf.org; Shahrier, Sharif M.
Subject: RE: [Seamoby] delay data requested


I am trying to do some calculations on the packet transfer delay between a
pair of ARs. I would like to know what is the raw delay (approx.) to
transfer a 32-bit word from the oldAR to the newAR. I expect this
information was used in some way in the calutations of handover protocols.
If someone can help, I would be grateful, if you can send me a direct
e-mail, as well as posting onto the list.
Thanks.
 
-Sharif.

****************************************************************************
This e-mail is intended only for the addressee named above and may contain
confidential, proprietary or privileged information. If you are not the
named addressee or the person responsible for delivering the message to the
named addressee, please inform us promptly by reply e-mail, then delete the
e-mail and destroy any printed copy. The contents should not be disclosed to
anyone and no copies should be made. We take reasonable precautions to
ensure that our emails are virus free. However we accept no responsibility
for any virus transmitted by us and recommend that you subject any incoming
e-mail to your own virus checking procedures.