Re: Reg: Quality of Service routing
"Raghu V.V.J Vadapalli" <iprsvp@yahoo.com> Tue, 22 December 1998 00:48 UTC
Received: from ns.newbridge.com (ns.newbridge.com [192.75.23.67]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14527 for <qosr-archive@odin.ietf.org>; Mon, 21 Dec 1998 19:48:15 -0500 (EST)
Received: (from smtpd@localhost) by ns.newbridge.com (8.8.8/8.6.12) id PAA07135 for qosr-archive@odin.ietf.org; Mon, 21 Dec 1998 15:57:20 -0500 (EST)
Received: from portal1.newbridge.com(192.75.23.76), claiming to be "kanata-mh1.ca.newbridge.com" via SMTP by ns.newbridge.com, id smtpdVDBa17598; Mon Dec 21 15:18:25 1998
Received: from qmaster.ca.newbridge.com by kanata-mh1.ca.newbridge.com with ESMTP; Mon, 21 Dec 1998 15:06:15 -0500
Received: (from majordom@localhost) by qmaster.ca.newbridge.com. (8.8.8/8.8.8) id OAA23377 for qosr-outgoing; Mon, 21 Dec 1998 14:50:47 -0500 (EST)
Received: from distmaster.ca.newbridge.com (distmaster.ca.newbridge.com [138.120.118.27]) by qmaster.ca.newbridge.com. (8.8.8/8.8.8) with SMTP id NAA04820 for <qosr@qmaster>; Sun, 20 Dec 1998 13:49:49 -0500 (EST)
Received: from kanata-mh1.ca.newbridge.com by distmaster.ca.newbridge.com (SMI-8.6/SMI-SVR4) id NAA03434; Sun, 20 Dec 1998 13:49:25 -0500
Received: from [138.120.118.49] by kanata-mh1.ca.newbridge.com with ESMTP; Sun, 20 Dec 1998 13:49:16 -0500
Received: (from smtpd@localhost) by ns.newbridge.com (8.8.8/8.6.12) id NAA09322 for qosr@newbridge.com; Sun, 20 Dec 1998 13:49:16 -0500 (EST)
Received: from send104.yahoomail.com(205.180.60.122) via SMTP by ns.newbridge.com, id smtpdAAAa09317; Sun Dec 20 13:49:10 1998
Message-Id: <19981220184934.18493.rocketmail@send104.yahoomail.com>
Received: from [209.94.102.60] by send104.yahoomail.com; Sun, 20 Dec 1998 10:49:34 PST
Date: Sun, 20 Dec 1998 10:49:34 -0800
From: "Raghu V.V.J Vadapalli" <iprsvp@yahoo.com>
Subject: Re: Reg: Quality of Service routing
To: Antoni Przygienda <prz@dnrc.bell-labs.com>
Cc: routing quality <qosr@newbridge.com>, Internet Protocol <ipng@sunroof.eng.sun.com>, MultiProtocol Label Switching <mpls@external.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-qosr@newbridge.com
Precedence: bulk
Content-Transfer-Encoding: 7bit
But the end-2-end delay = propagation time + proce. time. Right. The processing time of packet is more in the present networks due to lack of BW at all instants of time. So you need some I/O Q which will increase the total proc. time and hence the end-2-end delay. We want to process the packets based on the QoS requirements b'cos we don't have enough BW. Is there any other reason which increases the proc. time of a packet at a node. So in that case end-2-end delay ~ Propagation time. Which helps us in meeting the end-2-end delay requirement. Waiting for the expert comments... With Regards -Raghu. ---Antoni Przygienda <prz@dnrc.bell-labs.com> wrote: > > Raghu V.V.J Vadapalli wrote: > > > > Dear All, > > > > I have one basic question regarding QoS routing. > > > > Do we need QoS routing if we have enough infinite (I mean > > large ) bandwidth. > > > > >From my poor knowledge: > > > > We need QoS routing b'cos we have limited BW and we want > > to give priority to QoS flows. If some one comes with > > a Tx system which supports 100s Gb/s,(say 128 channel WDM system) > > Do we need to support the "special" status for the QoS flows. > > May in that case the memory at the routers will be > > bottleneck. > > > > Am I missing something. > > With Regards > > -Raghu. > > > > > > I am not aware that you can generally trade bandwidth for delay > (said simply: if you have end-2-end delay constraints to meet & sum of > your link propagation delays exceeds it, there is little you can do) > so having arbitrary amounts > of bandwidth does not necessarily solve the end-2-end delay problem. > > > > thank you > > --- tony > == ------------------------------------------------------------ _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com
- Re: Reg: Quality of Service routing Roch Guerin
- Re: Reg: Quality of Service routing Masilamany Raguparan
- Re: Reg: Quality of Service routing Parag M Panse
- Re: (IPng 6937) Re: Reg: Quality of Service routi… Matt Crawford
- Re: Reg: Quality of Service routing Antoni Przygienda
- Re: Reg: Quality of Service routing Barry Dykes
- Reg: Quality of Service routing Raghu V.V.J Vadapalli
- Re: Reg: Quality of Service routing Bala Rajagopalan
- Re: (IPng 6939) Re: Reg: Quality of Service routi… Lloyd Wood
- Re: Reg: Quality of Service routing Daniel Awduche
- Re: Reg: Quality of Service routing Raghu V.V.J Vadapalli
- Re: Reg: Quality of Service routing Qingming Ma
- Re: Reg: Quality of Service routing Richard Carlson
- Re: Reg: Quality of Service routing Antoni Przygienda
- Re: Reg: Quality of Service routing Bob O'Hara