From: "RIPE NCC Webmaster" To: "Rene Wilhelm" Cc: Subject: [ris-int] Re: RRC12 announcement on www.ripe.net Date: 23 July 2004 13:25 Rene Wilhelm writes: * * I didn't keep track of it myself, but an external user noticed * this announcement on www.ripe.net yesterday, JULY 22. The date * seems wrong :( Damn.. I changed it to 20 July. * * RIPE NCC Announcements * * [22 June 2004] * RIPE NCC Remote Route Collector Deployed at German Internet Exchange (DE-CIX * ) * * * I was also wondering if it wouldn't be better to make the link * point to a page with the announcement that was send out to ris-users, * (copied below) rather than jump deep down into the RIS web tree. * The announcement puts things more into context with a paragraph * summarizing the project and pointers to more RIS info at the end. * The http://www.ripe.net/ris/rrc12.html page seems more * targeted at people who already familiar with RIS and just * want to learn where the box is, what the peering policy and * peering details are. * OK, maybe you, Arife or Matthew can make a page in ris/news with the content of the announcement? We don't really want to link to messages in mail archives.. -J * * -- Rene * * * > From: ris-users-admin@ripe.net * > [mailto:ris-users-admin@ripe.net] On Behalf Of Matthew Williams * > Sent: 07 July 2004 19:11 * > To: ris-users@ripe.net * > Subject: ANNOUNCEMENT: New RIS Remote Route Collector at * > DE-CIX (RRC12) * > * > [Apologies for duplicate mails] * > * > Dear All, * > * > The RIPE NCC is pleased to announce that the RIS Project's * > twelth* Remote Route Collector, RRC12, is now ready to peer * > with members at the German Internet Exchange (DE-CIX). * > * > RRC12 is located at the German Internet Exchange (DE-CIX), * > and has been operational since July 2004. The RRC has an * > interface on the shared DE-CIX fabric, running both IPv4 and * > IPv6, and collects routing information from all exchange * > members, who are willing to peer with us. * > * > The use of TCP MD5 Signatures on IPv4 BGP sessions is * > supported on all RIS Route Collectors. MD5, however, is not * > supported on IPv6 sessions. * > * > Details: * > -------- * > - Peering address: 80.81.192.152 (IPv4); 2001:7f8::316e:0:1 (IPv6) * > - Autonomous system: 12654 * > - Policy: http://www.ripe.net/ris/rrc12.html * > - Peering requests: * > * Email: rispeering@ripe.net * > * Web form at URL: http://www.ris.ripe.net/cgi-bin/peerreg.cgi * > * > The Routing Information Service (RIS), which started as a * > modest RIPE NCC project in 1999, has gradually grown to over * > 300 IPv4 and IPv6 peers at now twelve* data collection points * > in Europe, Japan and North America. Our mission is to collect * > BGP routing information over a function of time, and make it * > available to the Internet community. In essence, this means * > devising tools that can help ISPs debug problems over time * > without being limited to one BGP view and providing RIS raw * > data regarding the Internet's historical development. * > * > Useful Links: * > ------------- * > RIS Info: http://www.ripe.net/ris/ * > RIS Tools: http://www.ripe.net/ris/query.html * > List of RRC Locations: http://www.ris.ripe.net/cgi-bin/rrcstatus.cgi * > * > Please send your comments to ris-int@ripe.net. * > * > Best regards, * > The RIS Team * > * > *) RRC09 has been decommissioned * > * > --- * > > Matthew Williams (MW243-RIPE) * > > Customer Liaison Engineer * > > RIPE NCC - http://www.ripe.net/np/ *