re: Sprints definition on NAPs (question)

The other question that should be asked (and I hope some folks have looked at
this) is whether this rule is in fact arbitrary. If there is no sound
ENGINEERING reason, it may constitute "restraint of trade" under Chapter 2 of
the Sherman Act (if memory serves). These types of problems can be quite
nasty, involving treble punitive damages.

I have never been a lawyer (or played one on TV :-), but I can recall
handling disbursement of suit awards while a programmer in a bank Trust

Ya, but Sprint has more money then us, and money wins. :slight_smile:

Nathan Stratton CEO, NetRail, Inc. Tracking the future today!

More importantly, Sprint (or any "larger" carrier) has content, and
customers that YOU (being a "smaller" ISP) want to provide to your
customers. Typically the larger folks are happy to get to ISP #1 via
their single transit route because there's less load on their routers
(being border or otherwise), fewer paths, etc.

However, for ISP #1 it's a different story -- if they were to peer with
the carrier life would potentially be better for them, whereas it affects
the carrier minimally in most cases. Lots of ISPs currently do not peer
with the carriers at exchange points, and simply buy transit from one;
making them dependant on that carrier <-> customer relationship.

In a perfect world, everyone would peer directly with everyone else,
however this is not the case. Carriers by nature invest substantially in
backbone infrastructure that smaller ISPs do not, to most this gives them
good reason not to provide "equal access" to ISPs that have not invested
similarly in infrastructure.


The original poster, Marcos Della, mentioned he couldn't get any info out
of Sprint's *SALES* dept. This is half the problem. Peering is an
engineering issue far more than a sales issue and you will never get
anywhere talking to the sales dept.

Of course, the engineering dept. is too bust doing engineering to take
time out to talk to you and hold your hand, so what do you do?

Well, it's like applying for a job. Research the company, research the
position, then find the right person to send your application to. In this
case it is more like, research the technology (BGP etc...), research
the concept of peering at a NAP, and find the right engineers to talk to.

The last part is the easiest, because all you need to do is attend a few
NANOG meetings in person. A nice side effect is that the speakers at the
NANOG meetings will educate you in some of the things you need to know and
help you find out what you don't know yet. Basically, if there is anything
that you don't understand from one of the presentations, that indicates an
area in which you need to do further study in order to reach an acceptable
level of competence.

Just remember the plain English meaning of the word "peer". It refers to
an individual who is at the same level as you. Same level of power (CEO
vs. engineer), same level of skill (PhD vs undergrad) and so on.

Michael Dillon Voice: +1-604-546-8022
Memra Software Inc. Fax: +1-604-546-3049 E-mail: