Home / Blogs

Call for “ISP Point of Contact” Database for Neutrality “Event” Concerns

When I initiated NNSquad (Network Neutrality Squad), one of my primary concerns was that many seemingly reportable “events” that can occur on the Internet—and that might seem on their face to be network neutrality “violations”—might actually be caused by innocent technical issues related to ISP operations, testing anomalies, or misinterpretation of test or otherwise observed data. Analysis of these situations—which may invoke security and privacy concerns—can be quite complex, and without a reasonably complete picture of events can also be considerably problematic.

It is particularly troubling that there generally is no routine mechanism available for early contact by neutrality researchers with appropriate high level ISP representatives during investigations of network issues that may relate to neutrality concerns. Wide publication of possibly alarming test results followed by ISP denials in innocent cases is decidedly suboptimal for everyone.

While it’s impossible to deny that there is considerable antagonism and distrust between some ISPs and elements of the Internet community, I strongly believe that there would be major positive benefit for all parties if better communications between these groups was available.

I hereby offer NNSquad’s services to establish a database of individuals who would be the designated ISP point of contacts in cases of detected network events that are suggestive of possible network neutrality concerns in a broad sense.

This would not be a public list, but would rather be maintained for the use of legitimate researchers and analysts working in this field, who would be able to query associated ISPs directly for their input in the course of event analysis.

The existence of such a database would not obligate anyone to use the database to contact ISPs in advance of major notice publications, nor would it obligate ISPs to provide any information in response to related queries. However, I feel that the responsible handling of these investigations would behoove all relevant parties to participate.

Inclusion in this database will be open to all ISPs globally of any size, large or small. Assuming sufficient interest, the database will ultimately be Web browser-based with a self-service portal to allow ISPs to keep their own contact information up to date.

I don’t view this proposal as any sort of panacea, but I do think that it could help to avoid unnecessary misunderstandings and confusion in many innocent situations, and the whole area of network neutrality is complex enough without such situations making life more difficult for everybody involved.

Interested ISP representatives and any other parties can contact me directly for more information and discussion. Let’s see if we can make this fly!

Thanks very much.

Filed Under


J.D. Falk  –  Apr 9, 2008 12:21 AM

You’re not the first to think of this.

Jared Mauch’s NOC list was one of the few successful projects along these lines.  I’m not sure how current it is, though.

Another is the Packet Clearing House’s INOC-DBA, which I understand is still active.

On the anti-abuse side, MAAWG members share an internal database of other members’ contact information; the APWG has a similar database, as do LAP and CNSA.  Occasionally there’s discussion of trying to merge these, but they have somewhat different purposes and requirements.

The core question, however, is whether these network operators are prepared to handle calls from NNsquad.  Most probably aren’t, no matter how high level you get—not because they’re evil, but because they have other priorities—like keeping the network operational.

Suresh Ramasubramanian  –  Apr 9, 2008 3:31 PM

As I already told you, Lauren, you wont get ISPs to give you the time of day. You tend to mistake routing outages for network neutrality issues, and you tend to treat ISPs as your enemies.

No better way to make them avoid you like the plague. Or perhaps rebut your IP posts if they feel like it, and if someone else hasnt done so already.

Comment Title:

  Notify me of follow-up comments

We encourage you to post comments and engage in discussions that advance this post through relevant opinion, anecdotes, links and data. If you see a comment that you believe is irrelevant or inappropriate, you can report it using the link at the end of each comment. Views expressed in the comments do not represent those of CircleID. For more information on our comment policy, see Codes of Conduct.

CircleID Newsletter The Weekly Wrap

More and more professionals are choosing to publish critical posts on CircleID from all corners of the Internet industry. If you find it hard to keep up daily, consider subscribing to our weekly digest. We will provide you a convenient summary report once a week sent directly to your inbox. It's a quick and easy read.

I make a point of reading CircleID. There is no getting around the utility of knowing what thoughtful people are thinking and saying about our industry.

Co-designer of the TCP/IP Protocols & the Architecture of the Internet




Sponsored byDNIB.com


Sponsored byVerisign

New TLDs

Sponsored byRadix

IPv4 Markets

Sponsored byIPv4.Global

Domain Names

Sponsored byVerisign

Threat Intelligence

Sponsored byWhoisXML API

Brand Protection

Sponsored byCSC