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

["ext Gwendal Le Grand" <Gwendal.Le-Grand@lip6.fr>]

Jak,


I don't totally agree with your three "seperate" issues :

> 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?


It seems to me that the answer is micro mobility.


> 2) How to match up the above with a DiffSrv like core, like Diff-edge?

Same answer here. I would use Intserv in the micro mobility domain (to
handle high mobility) and Diffserv in the core.
The problem is
	- to define the right QoS classes (what is guarantees are required for what
servcies)
	- to map them properly between Intserv and Diffserv.


> 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?

I'd say Micro mobility again !


Finally, i'd like to point out that it seems to me one issue is not being
discussed : a call which is initiated in a cell may have some bandwidth
guarantee in a cell (domain ?). Howerver, when the mobile terminal roams, it
may move into an area which cannot offer the same bandwidth to the
terminal(because the bandwidth has been allocated to users with the same
priority level). There are 2 issues :
	- degrade the QoS for the user or connect through another path if this path
exists (which has been mentioned)
	- make sure that this does not happen to often (maybe by distinguishing
handoffs and new calls as it is done in most cellular systems)

Gwendal