North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: TransAtlantic Cable Break

  • From: Robert Blayzor
  • Date: Sun Jun 24 13:14:45 2007
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta;; h=Received:Date:From:To:Subject; b=BohngAQEExnWad0R8B6dNIQ72H0eSfFQ4IJhVE+H/E/TyqDReB1rxKUvVyP3DseKQJT3smkMjjeybzSuI4zC/mVLQWZK8UrhwMz0CttkR4mJEc53jLgffnUNHXM1QM1aBF3gn1cbJ+Cy/IIBTJBf1b/9KC8K5tGntWT+qBWD1Qk=;

Chris L. Morrow wrote:
> Then there's the interesting: "How do you classify 'to be dropped'
> traffic?" Simon suggests nntp or BitTorrent could be put into a lower
> class queue, I'm curious as to how you'd classify traffic which is
> port-agile such as BitTorrent though. In theory that sounds like a grand
> plan, in practice it isn't simple...

It really depends on the network.  Not all networks are the same.  Case
in point we have some network that carries a lot of video.  Obviously we
want all the channels to get from point A to point B, but there are
services that really can be classed as "best effort"; like the VOD
stuff.  In most cases if VOD becomes unavailable, "so what".  You can
always watch it later when it's available again.  Of course you want
those types of services to always be available, but sometimes spending
the $$$ to make that kind of thing four or five nines isn't built into
the business case.

Robert Blayzor
[email protected]

YOUR PC's broken and I'VE got a problem?
 -- The BOFH Slogan