[e2e] QoS vs Bandwidth Overprovisioning

Ping Pan pingpan at juniper.net
Wed Apr 25 14:07:01 PDT 2001


demir wrote:
> 
> We know that there are some
> applications are not satisfied with thise service. As a result, if one who
> wants to support them should use more sophisticated QoS
> architecture. There are factors, i.e., scalability, deployment, security,
> economical,  that prevented us from using/deploying these QoS
> architectures. The problem in designing a QoS architecture is how we could
> optimize network resources for demanding traffic and what the desired QoS
> is (how we define the QoS; resulting with related services). To me,
> "best-effort" Internet, "Intserv" and "diffserv" architectures, all, are
> emerged with all these factors in mind; leading different/various
> mechanisms to be integrated to create different/various QoS architectures.
> 

I doubt there is much disagreement from your above statement. One of the
key issues is how to solve the problem (or from which direction should
we deal with the problem). I'm an engineer, so sorry about my ignorant
on architecture and religion. IHMO, much of the work in the past has
been focused on QoS requirements and solutions from the end-user point
of view. Granted that end-to-end has been very successful, but we have
to realize that today's Internet is very different now (like it or not).
It's a big business, so instead of designing something that can only
satisfy end users, any deployable solution must first satisfy network
and service providers. When you talk about optimizing network resources,
the question is not whether you can come up with some beautiful
equations, rather where do you want the resources to be optimized? At
core? At edge? Would it work if the networks run different routing
protocols with different policies? When you say scalability, what is not
scaling in the first place? There was an argument on memory and hardware
scaling, thanks to Moore's Law, we don't have such problem yet. I would
think that the real scaling issue for providers is manageability.

I read a paper from Dave Clark recently on rethinking e2e argument. It
was very very good (sorry, I don't have the pointer.) 

2 cents,

- Ping



More information about the end2end-interest mailing list