Re: about QoS context

Hi,

when a packet comes up an interface, forwarding treatment (i.e., QoS) is
afforded before the packet is routed. So, the packet is classified, metered
(re)marked in Diffserv. There are two kinds of classifications recognized in
Diffserv: multi-field and behavior aggregate. The former classification uses
more than just the Diffserv Codepoint, for instance the IP addresses and
port-pair.
Also, traffic shaping at the edge is critical for Diffserv.
On an access link, all the above operations (classification, metering and
marking)
introduce state.

Some stuff on this at http://people.nokia.net/~rajeev/Berkeley.ppt

-Rajeev


[email protected] wrote:

> Hi everybody,
>
> I'm sorry for my intervention. I'm currently studying the context transfer
> approach; I find that in most of the literature, QoS is mentioned as a
> potential candidate service. As you know there are two well known different
> approaches: Diffserv and Intserv, but neither of them seems to match the idea
> of the control transfer protocol. Diffserv doesn?t keep any information
> specifically related to the MN, on the other hand, Intserv does keep state
> information but not only in the access routers but in the entire path.
> I?d like to know if I?m missing or misunderstanding something. (or if I?m
> totally lost)
> I?ll appreciate your comments.
> Thanks a lot in advance for your time.
>
> Christian G.
>
> _______________________________________________
> Seamoby mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/seamoby