RE: [MIP-QOS] RE: MIP-QOS -- Scope of disc ussions

[Hemant.Chaskar@nokia.com]

Seamless Mobility Working Group, a complementary WG to Mobile IP.

-----Original Message-----
From: ext Murray Philip [mailto:PMURRAY@dera.gov.uk]
Sent: 17. April 2001 10:37
To: 'mip-qos@research.nokia.com'
Subject: [MIP-QOS] RE: MIP-QOS -- Scope of disc ussions



Hi

Just a quick question.  What is SeaMoby?

Cheers
Phil

-----Original Message-----
From: Hemant.Chaskar@nokia.com [mailto:Hemant.Chaskar@nokia.com]
Sent: 17 April 2001 14:56
To: mip-qos@research.nokia.com
Subject: RE: [MIP-QOS] RE: MIP-QOS -- Scope of discussions


Hi:

Couple of remarks: 

>I think a requirement should be that when a transmission is instigated
>it should be active with QoS provided as quickly as possible.  By this
I
>mean that if an optimum route is not initially used from the
>correspondent node to the mobile node, then the link via the home agent
>should provide QoS.  The direct route from the correspondent node being
>established and taking over the transmisson, and consistent QoS as soon
>as possible.

I agree, the QoS mechanism must be smart enough to establish QoS on
optimized as well as non-optimized path and later release one of them.

>I also think we need to make clear what levels of mobility we are
>looking to support, i.e. how often are routes going to change.

The problem statement does _not_ intend to limit the extent of mobility.
Any
handover from one AR to another will be considered as mobility. Such
handover could be between physically and logically adjacent routers or
between physically but not logically adjacent routers (example: handover
from cellular to indoor LAN which could be supported by different
service
providers). Thus route change upon handover could be limited to a small
segment of network path near the access router or could have end-to-end
impact.

Regarding _frequency_ of route changes due to handover alone, I do not
have
quantitative answer. I have not seen that number in may other documents
related to handovers between access routers in Mobile IP and SeaMoby as
well, where in my opinion it should appear first. I have heard one
service
provider in 3GPP2 mentioning that there could be as many as 10 handovers
during a voice call in a dense busy area like NewYork city. But I have
not
seen any formal experimental numbers on that. Having said that, the best
bet
for us will be to refrain from quoting any number like that. 

Regards,
Hemant



-- 
The Information contained in this E-Mail and any subsequent
correspondence
is private and is intended solely for the intended recipient(s).
For those other than the recipient any disclosure, copying,
distribution, 
or any action taken or omitted to be taken in reliance on such
information
is
prohibited and may be unlawful.


-- 
The Information contained in this E-Mail and any subsequent correspondence
is private and is intended solely for the intended recipient(s).
For those other than the recipient any disclosure, copying, distribution, 
or any action taken or omitted to be taken in reliance on such information
is
prohibited and may be unlawful.