[28199] in North American Network Operators' Group
Re: Peering Table Question
daemon@ATHENA.MIT.EDU (Larry Snyder)
Wed Apr 19 20:19:19 2000
From: Larry Snyder <larrys@lexis-nexis.com>
Message-Id: <200004200014.UAA02619@ra.lexis-nexis.com>
Date: Wed, 19 Apr 2000 20:14:38 -0400 (EDT)
To: jsb@UU.NET
Cc: nanog@merit.edu
In-Reply-To: <Pine.GSO.4.20.0004191923510.3154-100000@neserve0.corp.us.uu.net>
MIME-Version: 1.0
Content-Type: text/plain
Errors-To: owner-nanog-outgoing@merit.edu
To someone troubleshooting a routing or performance problem, it might
look operational. A large file of baseline traceroutes could replace
the benefits of disclosure, I suppose.
Lawyers - 1 Tekkies - 0
my .02
-ls-
Jeff Barrows <jsb@UU.NET> wrote:
>
>
> Sean -
>
> We sign and comply with mutual non-disclosure agreements
> that inhibit my ability to share that information with you.
>
> This is not a technical issue.
>
> I look forward to viewing your backhoe reports.
>
> - jsb
>
> --
> Jeff Barrows
> Director, Internetwork Engineering
> UUNET, an MCI-Worldcom Company
>
>
> > Date: 19 Apr 2000 13:30:38 -0700
> > From: Sean Donelan <sean@donelan.com>
> > To: nanog@merit.edu
> > Subject: Re: Peering Table Question
> >
> > On Wed, 19 April 2000, Jeff Barrows wrote:
> > > One shouldn't necessarily believe any third-party web
> > > pages, documents, articles, or verbal statements about
> > > which networks any given network is peered with.
> > >
> > > Though I have seen many articles, web pages, and other
> > > tables that detail which networks are 'peering,' I
> > > have never seen an accurate representation of this
> > > type of data from a third party.
> >
> > Then I hope you would step forward and show us the best practice
> > for making accurate information available about which networks
> > any given network peers with starting with yours. I look forward
> > to viewing the information about your network peering on your website
> > or IRR or whatever method you decide to use.
>
