RE: [MIP-QOS] Re: MIP-QOS -- Scope of discussions

[Hemant.Chaskar@nokia.com]

I repeat, as a generic requirement, we can say that:

"A QoS mechanism MUST interoperate with heterogeneous QoS domains (DiffServ,
IntServ, MPLS) in the end to end path" and

leave it to the designer of the solution to describe how his/her solution
indeed meets the above requirement.

> -----Original Message-----
> From: ext James Kempf [mailto:James.Kempf@sun.COM]
> Sent: 17. April 2001 20:16
> To: mip-qos@research.nokia.com
> Subject: RE: [MIP-QOS] Re: MIP-QOS -- Scope of discussions
> 
> 
> Fred,
> 
> Re. RSVP v.s. Diffsrv, 	in cellular networks, the radio 
> access network
> is always oversubscribed because the air is always in scarce supply.
> Thus there is a part of the network that has Intsrv like requirements
> but these are not end to end. They are only in the access network.
> Thus, I have some trouble seeing why RSVP is needed end to end, and
> I think it is somewhat heavyweight even for the access network,
> since the signalling in the handoff case is very subotimal (please
> see Michael Thomas's draft on this). Note that I am not saying that
> the IP QoS signalling should directly cause the radio QoS to
> get established (that is a separate, and very interesting topic
> on its own) but just simply that there needs to be signalling that
> allows RSVP-like reservations hooked to the radio QoS mechanism.
> 
> In the core network, Diffsrv works fine, if the service provider
> is willing to overprovision and give up the "all circuits are 
> busy" message
> that comes a part of end to end QoS. Most service providers seem
> pretty tied to having end to end QoS, though reestablishing that
> on handover is really costly.
> 
> So I think there are three separate issues here:
> 
> 1) How to get signalling that is handover friendly and provides Intsrv
> like properties in the radio access network without requiring the
> entire network to be Intsrv?
> 
> 2) How to match up the above with a DiffSrv like core, like Diff-edge?
> 
> 3) How to do handover friendly, end to end QoS for those service
> providers that don't want to overprovision and want to provide
> the "all circuits" message?
> 
> 		jak>