<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.gmailquote
{mso-style-name:gmail_quote;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Tahoma","sans-serif";
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:blue'>The key thing is that it can’t be too complicated for the
subscriber. What you’ve described is already too difficult for the
masses to consume. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:blue'>The scavenger class, as has been described in other postings, is probably
the simplest way to implement things. Let the application developers take
care of the traffic marking and expose priorities in the GUI, and the marketing
from the MSO needs to be “$xx.xx per month for general use internet, with
unlimited bulk traffic for $y.yy”. Of course, the MSOs wouldn’t
say that the first category excludes bulk traffic, or mention caps or upstream
limitations or P2P control because that would be bad for marketing. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:blue'>Frank<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:blue'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Dorn Hetzel
[mailto:dhetzel@gmail.com] <br>
<b>Sent:</b> Wednesday, October 24, 2007 8:12 AM<br>
<b>To:</b> Joe Greco<br>
<b>Cc:</b> frnkblk@iname.com; nanog@merit.edu<br>
<b>Subject:</b> Re: BitTorrent swarms have a deadly bite on broadband nets<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>How about a system where I tell
my customers that for a given plan X at price Y they get U bytes of "high
priority" upload per month (or day or whatever) and after that all their
traffic is low priority until the next cycle starts. <br>
<br>
Now here's the fun part. They can mark the priority on the packets they
send (diffserv/TOS) and decide what they want treated as high priority and what
they want treated as not-so-high priority.<br>
<br>
If I'm a low usage customer with no p2p applications, maybe I can mark ALL my
traffic high priority all month long and not run over my limit. If I run
p2p, I can choose to set my p2p software to send all it's traffic marked low
priority if I want to, and save my high priority traffic quote for more important
stuff. <br>
<br>
Maybe the default should be high priority so that customers who do nothing but
are light users get the best service.<br>
<br>
low priority upstream traffic gets dropped in favor of high priority, but users
decide what's important to them. <br>
<br>
If I want all my stuff to be high priority, maybe there's a metered plan I can
sign up for so I don't have any hard cap on high priority traffic each month
but I pay extra over a certain amount.<br>
<br>
This seems like it would be reasonable and fair and p2p wouldn't have to be singled
out. <br>
<br>
Any thoughts?<o:p></o:p></p>
<div>
<p class=MsoNormal><span class=gmailquote>On 10/22/07, <b>Joe Greco</b> <<a
href="mailto:jgreco@ns.sol.net">jgreco@ns.sol.net</a>> wrote:</span><o:p></o:p></p>
<p class=MsoNormal><br>
> I wonder how quickly applications and network gear would implement QoS<br>
> support if the major ISPs offered their subscribers two queues: a default<br>
> queue, which handled regular internet traffic but squashed P2P, and then a
<br>
> separate queue that allowed P2P to flow uninhibited for an extra $5/month,<br>
> but then ISPs could purchase cheaper bandwidth for that.<br>
><br>
> But perhaps at the end of the day Andrew O. is right and it's best off to <br>
> have a single queue and throw more bandwidth at the problem.<br>
<br>
A system that wasn't P2P-centric could be interesting, though making it<br>
P2P-centric would be easier, I'm sure. ;-)<br>
<br>
The idea that Internet data flows would ever stop probably doesn't work <br>
out well for the average user.<br>
<br>
What about a system that would /guarantee/ a low amount of data on a low<br>
priority queue, but would also provide access to whatever excess capacity<br>
was currently available (if any)? <br>
<br>
We've already seen service providers such as Virgin UK implementing things<br>
which essentially try to do this, where during primetime they'll limit the<br>
largest consumers of bandwidth for 4 hours. The method is completely
<br>
different, but the end result looks somewhat similar. The recent<br>
discussion of AU service providers also talks about providing a baseline<br>
service once you've exceeded your quota, which is a simplified version of <br>
this.<br>
<br>
Would it be better for networks to focus on separating data classes and<br>
providing a product that's actually capable of quality-of-service style<br>
attributes?<br>
<br>
Would it be beneficial to be able to do this on an end-to-end basis (which <br>
implies being able to QoS across ASN's)?<br>
<br>
The real problem with the "throw more bandwidth" solution is that at
some<br>
point, you simply cannot do it, since the available capacity on your last<br>
mile simply isn't sufficient for the numbers you're selling, even if you <br>
are able to buy cheaper upstream bandwidth for it.<br>
<br>
Perhaps that's just an argument to fix the last mile.<br>
<br>
... JG<br>
--<br>
Joe Greco - <a href="http://sol.net">sol.net</a> Network Services - Milwaukee,
WI - <a href="http://www.sol.net">http://www.sol.net</a><br>
"We call it the 'one bite at the apple' rule. Give me one chance [and] then
I<br>
won't contact you again." - Direct Marketing Ass'n position on e-mail
spam(CNN) <br>
With 24 million small businesses in the US alone, that's way too many apples.<o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>