[CII] [bmanning at vacation.karoshi.com: Re: terms and conditions]

John Osmon josmon at rigozsaurus.com
Mon Nov 30 07:52:25 UTC 2009


On Sat, Nov 28, 2009 at 08:17:09PM -0500, Dotzero wrote:
> > On Fri, Nov 27, 2009 at 10:36:55PM -0700, John Osmon wrote:
> >>
> >> "My network, my rules."  But I'll always prempt traffic on my net
> >> for health/safety.  Kinda seems like my duty to the society that I live
> >> within...
> 
> What do you mean by "preempt". Are you carrying traffic from other
> networks and destined for other networks or are you talking about
> preventing traffic from your network going to 3rd party networks? What
> is the general nature of traffic on your net?

I'm not operating a network at the momment, but I have during other
stages of my career.  Mostly, I've dealt with rurual areas, and
have relied on other carriers for backhaul.  However, if, at any time,
someone would have shown me that some form of health/safety were 
in need, I would have setup QOS to ensure that health/safety traffic
had absolute priority over other traffic.
 
> I deal with corporate networks and ecommerce sites. Our triage would
> be to cut traffic when we are putting others at potential risk or if
> there is significant potential risk to the integrity of our systems
> and networks. While we have a lot of horsepower we would not be
> considered CII by most people.

I can see the logic of your reasoning.

Let's consider a situation where you have a BGP connection to a local ISP
in a region.  If that ISP had "critical" traffic that needed to get
somewhere, and you had the ability to deliver it -- would you be willing
to give that "critical" traffic priroity on your network if it caused
congestion for you "normal" traffic?

If you were to answer "yes," I would include you as CII for that region.

Hopefully, you'd have a different physical path from the ISP that had
"critical" traffic.  However, even if you don't have path diversity, 
your equipment diversity might be enough to handle the "critical"
information.



More information about the CII mailing list