netdev
[Top] [All Lists]

Re: Diffserv and NetApplications

To: cw@xxxxxxxx (Chris Wedgwood)
Subject: Re: Diffserv and NetApplications
From: anand@xxxxxxxxxxxxxxxxx (SVR Anand)
Date: Mon, 16 Jul 2001 18:48:07 +0530 (GMT+05:30)
Cc: netdev@xxxxxxxxxxx
In-reply-to: <20010715161211.J7624@xxxxxxxxxxxxx> from "Chris Wedgwood" at Jul 15, 2001 04:12:11 PM
Sender: owner-netdev@xxxxxxxxxxx
Chris Wedgwood,

Thanks for your reply. I would certainly be happy to visit the sites that have
tcp/udp applications using diffserv QoS mechanism. Can you please pass it on ?
I searched on Google without much success :(

With respect to your other point of the practicality of the proposed QoS, all
I have to say is that it is atleast good to have QoS provisioning rather than
not having at all. Those who can make use of it, let them use it. What I am
suggesting is an augmentation to what is already available rather than a 
replacement.

At least in one case, I can clearly see advantage of adaptively using diffserv 
dscp values in the http servers to serve the urls in an intelligent and 
responsive way to its clients. The critiria for choosing these values can be 
part of server configuration, or run-time. Now, if the network wants to remark
or drop the packets, let it. The server conveyed its priorities.

What is the big point of having architecture, and no one to use it ? Don't you
think we have to make a beginning somewhere ? Since you pointed out that there
are indeed applications that takes advantage of QoS (if it exists! :)) I will
try to hunt for them.

Regards
Anand


> 
> On Fri, Jul 13, 2001 at 09:52:41PM +0530, SVR Anand wrote:
> 
>     Considering diffserv as QoS supporting mechanism, I am
>     contemplating on the possibility of making some of the known
>     netapplications like http, telnet, ftp and so on, inherently
>     diffserv aware.
> 
> MAny already are, I believe telnet and ssh are for example.
> 
>     By this I mean the applications automatically send
>     out their packets out of the box with appropriate dscp values
>     depending on their QoS requirements. While tc is one way of
>     achieving the same result, it is an external mechanism requiring a
>     seperate agent to configure diffserv.
> 
>     My wish is, all the future netapps
>     from Linux should take advantage of QoS as applicable, naturally.
> 
> As I said, some (many) already do... QoS means different things to
> different people.  Nice idea in theory, in reality its not worth much
> to acheive what you want.
> 
> 
> 
> 
>   --cw
> 


<Prev in Thread] Current Thread [Next in Thread>