Good Afternoon. In the spirit of cooperation and sharing, attached is the first draft of the RA Peering Agreement. It can be used regardless of number of hops required to access any specific RS run by the RA. Comments are welcome. The Routing Arbiter Peering Agreement........................ 08Nov1994 The Routing Arbiter will peer with and accept all routes from any NSP or any other party. Announcements from the RA are subject to specific NSP policy constraints as registered in the Global Routing Registry as seen by the RA.db. The Routing Arbiter agrees to perform this function, assuming no liability on the the part of the RA for any service that it chooses to render to the Internet community. --bill
In message <199411090013.AA29062@zed.isi.edu>, bmanning@ISI.EDU writes:
The Routing Arbiter will peer with and accept all routes from any NSP or any other party. Announcements from the RA are subject to specific NSP policy constraints as registered in the Global Routing Registry as seen by the RA.db .
You do mean on request, right? You don't want your RS loaded down with someone's host routes that misconfigured their terminal servers serving SLIP and PPP customers, leaked their subnet routes or made some other mistake. Curtis
participants (2)
-
bmanning＠ISI.EDU -
Curtis Villamizar