[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
Just to second Rajeev's point, the important context to transfer would be
related to packet classification state, packet metering state, traffic
shaping state, etc.
Essentially what you want to do is transfer the needed contexts so that
when an IP flow is seen a the nAR, the packets are handled they same
way they were at the pAR w.r.t. QoS.
John
> -----Original Message-----
>
> 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 <a href="http://people.nokia.net/~rajeev/Berkeley.ppt";>http://people.nokia.net/~rajeev/Berkeley.ppt</a>
>
> -Rajeev
>
>
> cpgarcia at cicese.mx 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
> > Seamoby at ietf.org
> > <a href="https://www1.ietf.org/mailman/listinfo/seamoby";>https://www1.ietf.org/mailman/listinfo/seamoby</a>
>
>
> _______________________________________________
> Seamoby mailing list
> Seamoby at ietf.org
> <a href="https://www1.ietf.org/mailman/listinfo/seamoby";>https://www1.ietf.org/mailman/listinfo/seamoby</a>
>
_______________________________________________
Seamoby mailing list
Seamoby at ietf.org
<a href="https://www1.ietf.org/mailman/listinfo/seamoby";>https://www1.ietf.org/mailman/listinfo/seamoby</a>
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--X-Follow-Ups-End-->
<!--X-References-->
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg02756.html">Re: [Seamoby] about QoS context</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg02758.html">Re: [Seamoby] Status of Seamoby drafts</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg02754.html">RE: [Seamoby] about QoS context</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#02757"><strong>Date</strong></a></li>
<li><a href="threads.html#02757"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>