nanog mailing list archives
Re: Peering Policies and Route Servers
From: Andrew Partan <asp () partan com>
Date: Thu, 2 May 1996 00:57:21 -0400 (EDT)
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) - - - - - - - - - - - - - - - - -
Current thread:
- Re: Peering Policies and Route Servers Stephen Wolff (May 01)
- <Possible follow-ups>
- Re: Peering Policies and Route Servers Justin W. Newton (May 01)
- Re: Peering Policies and Route Servers Andrew Partan (May 01)
- Re: Peering Policies and Route Servers Erik E. Fair (May 01)
- Re: Peering Policies and Route Servers Andrew Partan (May 01)
- Re: Peering Policies and Route Servers Avi Freedman (May 02)
- Re: Peering Policies and Route Servers Jessica Yu (May 02)
- Re: Peering Policies and Route Servers Marten Terpstra (May 02)
- Re: Peering Policies and Route Servers Curtis Villamizar (May 06)
- Re: Peering Policies and Route Servers Erik E. Fair (May 01)
- Re: Peering Policies and Route Servers Paul Ferguson (May 02)
- Re: Peering Policies and Route Servers Steven J. Richardson (May 02)
- Re: Peering Policies and Route Servers David . Kessens (May 03)
- Re: Peering Policies and Route Servers Paul Ferguson (May 02)