[2842] in North American Network Operators' Group
Re: Peering Policies and Route Servers
daemon@ATHENA.MIT.EDU (Curtis Villamizar)
Mon May 6 10:37:22 1996
To: Andrew Partan <asp@partan.com>
cc: epg@merit.edu (Elise Gerich), paul@vix.com, nanog@merit.edu
Reply-To: curtis@ans.net
In-reply-to: Your message of "Thu, 02 May 1996 00:57:21 EDT."
<199605020457.AAA00182@home.partan.com>
Date: Mon, 06 May 1996 10:22:23 -0400
From: Curtis Villamizar <curtis@ans.net>
In message <199605020457.AAA00182@home.partan.com>, Andrew Partan writes:
> > The RA has implemented requirements that providers have when a
> > provider communicates what is needed. I can't find any messages
> > from Sean indicating what he would like to express but can't.
> > The RA team is always willing to work with providers to meet
> > their needs.
>
> There is one thing that the RS can't do.
>
> If A & B are doing 3rd party peering via the RS, the fact that the
> A/RS peering is up & working and that the B/RS peering is up &
> working unfortunately does not tell you if A & B can exchange
> packets.
>
> If A & B are peering directly, then the fact that the peering is
> up also tells you that they can exchange packets.
>
> Luckily this sort of breakage does not happen very often.
> Unluckily, if it does break, if can be really hard to diagnose.
> --asp@partan.com (Andrew Partan)
Just because you don't BGP peer doesn't mean you should monitor
reachability to your third party peers. The BGP mib is handy, but
this is nothing a ping test can't detect. Too bad there is no LQM on
broadcast media.
Curtis
