<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>RE: [rbak-nsp] SE800 QoS profiles</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>The way this is normally solved, without your LNS knowing their bandwidth and without having to revert to changing the user's QoS profile dynamically with every re-sync based on this, is to create your product (based on the telco product) by shaping down to maxima (i.e all users who want QoS can have no more than a 2Mbit line)<BR>
and rejecting unsuitable minima (that unless users can sync at at least 2Mbit they can't have QoS)<BR>
This way you create a uniform product, albeit restricted to 2Mbit , everybody who can sync at 2Mbit and above are shaped down to 2Mbit (and then have predictable QoS parameters) and everybody who can't achieve 2Mbit can't get the service (unless you want to have a 1Mbit product as well)<BR>
<BR>
Since your provider is unlikley to prioritise traffic in their network, nor even offer an SLA, the very act of prodividing a DSL QoS product should occur in a tightly controlled environment (if at all), try taking a look at your competitors, I'm sure you will see that they do the same.<BR>
<BR>
<BR>
------------------------------------------------<BR>
David Freedman<BR>
Group Network Engineering<BR>
Claranet Limited<BR>
<A HREF="http://www.clara.net">http://www.clara.net</A><BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: redback-nsp-bounces@puck.nether.net on behalf of Ian Calderbank<BR>
Sent: Fri 9/4/2009 22:58<BR>
To: redback-nsp@puck.nether.net<BR>
Subject: Re: [rbak-nsp] SE800 QoS profiles<BR>
<BR>
Hi jim,<BR>
whoever you spoke to is mistaken or misunderstood your question. certainly<BR>
in the context of a BT 20CN iistream dsl environment (which I guess you are<BR>
talking about) you need to know what the DSL line speed is in order for voip<BR>
prioritisation to work , as BT won't do anything for you in their network.<BR>
So If you don't (know the line speed) the only workaround is a lowest common<BR>
denominator value.<BR>
<BR>
I'm actually working on this with a UK ISP at the mo.<BR>
<BR>
ta<BR>
Ian<BR>
<BR>
--------<BR>
Calderbank Consulting Ltd<BR>
ian@calderbankconsulting.co.uk<BR>
<BR>
> Message: 1<BR>
> Date: Fri, 04 Sep 2009 15:30:16 +0100<BR>
> From: Jim Tyrrell <jim@scusting.com><BR>
> To: redback-nsp@puck.nether.net<BR>
> Subject: [rbak-nsp] SE800 QoS profiles<BR>
> Message-ID: <4AA12478.1070206@scusting.com><BR>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed<BR>
><BR>
> Hi,<BR>
><BR>
> I want to create and apply some QoS profiles so that protocols such as<BR>
> VOIP get priority on certain users connections. ie If the user has an<BR>
> 8Mb connection then VOIP should get priority over all their other<BR>
> traffic up to say 6Mb. But if the user had a 2Mb line we may want VOIP<BR>
> to get priority up to 1.5Mb against the users other traffic.<BR>
><BR>
> Our users have DSL connections and sync anywhere between 512k and 24Mb<BR>
> but we dont necessarily know what all the users sync speeds are. So my<BR>
> question is, do we need to know what the end users actual line speed is<BR>
> in order to apply QoS and prioritise their various protocols? I was<BR>
> told by a Redback engineer that you dont need to know the end user line<BR>
> speed as you can just use rate percentage in the qos profile?<BR>
><BR>
> Is this right as I dont see how the SE800 could prioritise traffic<BR>
> without knowing what the upper limit is? The SE800 is sending the<BR>
> traffic to the user in an L2TP tunnel though a GigE card so surely it<BR>
> would need to know the user has a line rate of 8Mb so that when overall<BR>
> traffic for the specific user starts hitting that limit it needs to<BR>
> start dropping/queue the lower priority packets? Otherwise as far as<BR>
> the Redback is concerned wouldnt the upper limit be the GigE port?<BR>
><BR>
> Thanks.<BR>
><BR>
> Jim.<BR>
><BR>
><BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>