RE: [MIP-QOS] Requirements.

["ext Phil Roberts" <PRoberts@MEGISTO.com>]

We have to be a little careful about getting too far away from connections
to MIP.  There is the issue of providing some context to the discussion, but
remember our task is to produce a draft that is MIP QoS Requirements.

And some of the below sounds like you're eager to drift into the solution
space, which is definitely out of scope.


> -----Original Message-----
> From: ext Shahrier, Sharif M. 
> [mailto:Sharif.Shahrier@InterDigital.com]
> Sent: Thursday, April 19, 2001 5:12 PM
> To: 'mip-qos@research.nokia.com'
> Subject: RE: [MIP-QOS] Requirements.
> 
> 
> 
> 
> I request a few requirements:
> 
> 1. The QoS information about an IP flow is maintained in a context.
> 2. The context is attached to an AR, which is associated with a MN.
> 3. When MN handoffs to a different AR, attempt is made to 
> transfer context
> seamlessly.
> 4. If seamless transfer occurs, then ok.
> 5. If seamless transfer doesn't occur, negotiate QoS 
> parameters with target
> AR.
> 6. Handover to target AR occur.
> 
> Note that the QoS information about an IP flow is maintained 
> in a context,
> and is
> transferred to a new AR during context transfer.
> 
> 
> 
> Now, it can be argued that the SEAMOBY group is dealing with "context
> transfer". 
> This is correct
> 
> 
> , they will ultimately develop a protocol for context transfer. 
> 
> This is implicit when the context transfers happen above.
> 
> -Sharif
> 
>