Re: Best way to deal with bad advertisements?
Just to add a bit to that, the US Government could force providers to peer with all providers meeting certain requirements (enter telco history) but I think there would be difficulty requiring them to peer with non-US companies.
Actually the US Government already has such a policy. Buried deep inside the original NSF NAP solicitation was the requirement any provider must peer with any other provider connected to all three priority NAPs, or it would not qualify as an NSP for NSF connection grants. There was no requirement for minimum connection speed to a NAP or between the NAPs to qualify as an NSP. This was to keep the old NSF mid-level networks from losing connectivity with each other if they happened to choose different NSPs. I'm guessing the NSF connection program has wound down by now, so this isn't that much of a factor any more. But there is no reason why the same conditions couldn't be imposed on other government funds for network connectivity. Nor is there anything preventing other customers from choosing their provider on the same basis, or putting similar conditions in their contracts. If customers don't realize that different providers have different interconnection policies, they may not know its something they should consider. I used to recommend UUNET to customers in part because they peered with lots of other providers. Markets are usually better at sorting these things out than governments, as long as the consumer has all the information to make a decision. But if you like involving government, the big providers usually have more restrictions on them because they like getting government money. vBNS and ICM are two examples that could lead to interesting peering requirements from the government on the providers. -- Sean Donelan, Data Research Associates, Inc, St. Louis, MO Affiliation given for identification not representation
On Mon, 30 Sep 1996, Sean Donelan wrote:
Actually the US Government already has such a policy. Buried deep inside the original NSF NAP solicitation was the requirement any provider must peer with any other provider connected to all three priority NAPs, or it would not qualify as an NSP for NSF connection grants. There was no requirement for minimum connection speed to a NAP or between the NAPs to qualify as an NSP.
That is the only problem I have with a few peering requirements. There should be no reason that a I should need DS3 network from day one. I am fine with providers making me go to MAE-East, MAE-West, PACBELL, Ameritech, and Sprint NAP. I do have a problem with them saying this all needs to be connected via DS3. If it was say connected via frac DS3 or say MFS 10 meg service it should make no difference to the peers. Why should a new NSP pay for a DS3 when they need only 10 meg? Nathan Stratton CEO, NetRail, Inc. Tracking the future today! --------------------------------------------------------------------------- Phone (703)524-4800 NetRail, Inc. Fax (703)534-5033 2007 N. 15 St. Suite 5 Email sales@netrail.net Arlington, Va. 22201 WWW http://www.netrail.net/ Access: (703) 524-4802 guest --------------------------------------------------------------------------- "Therefore do not worry about tomorrow, for tomorrow will worry about itself. Each day has enough trouble of its own." Matthew 6:34
This was to keep the old NSF mid-level networks from losing connectivity with each other if they happened to choose different NSPs. I'm guessing the NSF connection program has wound down by now, so this isn't that much of a factor any more.
Erm, rather a large number of entities still receive NSF connection funding. It's rather amusing what some of them do with it. :-) -alan
participants (3)
-
alan@mindvision.com
-
Nathan Stratton
-
Sean Donelan