July 2004 - Ris-int - mailman.ripe.net

Re: [ris-int] FW: NCC#2004073298 Re: rrc01:PEERING 8210
by Rene Wilhelm 23 Jul '04

23 Jul '04

>> Why does the autoresponse have to come from an unread email account? > For RIPE DBM we do this to avoid mail loops (I think - Oleg knows more about > these mysteries than I do). ah, right! loops should indeed be avoided in automated response systems, mail servers could quickly come to a grinding halt. (IIRC, NCC has had it's shares of loop problems with the hostmaster robot in the past) > For hostmasters, the "From:" is actually <hostmaster(a)ripe.net>. I guess it > makes sense for the "From:" to be <ris(a)ripe.net> in this case. If it cannot create loops, from (or reply-to for that matter) <ris(a)ripe.net> would be great for tickets coming in to ris. -- Rene

1 0

FW: NCC#2004073298 Re: rrc01:PEERING 8210
by Matthew Williams 23 Jul '04

23 Jul '04

Peering requests hasn't worked very well in the past. Good work :) Cheers, Matthew > -----Original Message----- > From: RIPE NCC Acknowledgements [mailto:hm-ack@ripe.net] > Sent: 23 July 2004 14:48 > To: RIS Peering Request > Subject: NCC#2004073298 Re: rrc01:PEERING 8210 > > > Greetings, > > This message has been automatically generated in response to the > e-mail: > > To: RIS Peerings<rispeering(a)ripe.net> > From: RIS Peering Request <risops(a)ripe.net> > Date: Fri, 23 Jul 2004 12:47:44 GMT > Message-ID: <200407231247.i6NCli3U013164(a)halfweg.ripe.net> > Subject: rrc01:PEERING 8210 > > There is no need to reply to this message right now. Your > ticket has been assigned an ID of "NCC#2004073298". Please > include this string in the subject line of any further > correspondence on this matter. > > For more information about the RIPE NCC RIS Project, please > refer to http://www.ripe.net/ris/. > > Thank you, > > RIPE NCC Software Department >

5 6

RIS move status
by Henk Uijterwaal (RIPE NCC) 23 Jul '04

23 Jul '04

Arife, Can I have a few minutes on Monday's agenda to go over the status of the move, see attached MPP file with details? Thx, Henk ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent).

3 2

FW: [ris-int] Re: RRC12 announcement on www.ripe.net
by Matthew Williams 23 Jul '04

23 Jul '04

Hi Adrian, Rene came up with the idea to link announcements to a little RIS intro page with a few links. Is that something you can help us with? Cheers, Matthew > -----Original Message----- > From: ris-int-admin(a)ripe.net [mailto:ris-int-admin@ripe.net] > On Behalf Of RIPE NCC Webmaster > Sent: 23 July 2004 15:49 > To: Matthew Williams > Cc: ris-int(a)ripe.net; 'Rene Wilhelm' > Subject: Re: [ris-int] Re: RRC12 announcement on www.ripe.net > > > > "Matthew Williams" <matthew(a)ripe.net> writes: > * > 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.. > * > * Sure, we could do that. Mind you, what is Adrian up to > nowadays? Great opportun > * ity to dig into the RIS aspect of IS... ;) > > Talk to Adrian. BTW, if you want him to change RIS pages, > make sure you add him to the projects group. > > -J > > * > * Cheers, > * Matthew > * > * > -----Original Message----- > * > From: ris-int-admin(a)ripe.net [mailto:ris-int-admin@ripe.net] > * > On Behalf Of RIPE NCC Webmaster > * > Sent: 23 July 2004 13:25 > * > To: Rene Wilhelm > * > Cc: ris-int(a)ripe.net > * > Subject: [ris-int] Re: RRC12 announcement on www.ripe.net > * > > * > > * > > * > Rene Wilhelm <wilhelm(a)ripe.net> 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(a)ripe.net > * > * > [mailto:ris-users-admin@ripe.net] On Behalf Of > Matthew Williams > * > * > Sent: 07 July 2004 19:11 > * > * > To: ris-users(a)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(a)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(a)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/ > * > * > * > > * >

1 0

RRC12 announcement on www.ripe.net
by Rene Wilhelm 23 Jul '04

23 Jul '04

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 :( 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. -- Rene > From: ris-users-admin(a)ripe.net > [mailto:ris-users-admin@ripe.net] On Behalf Of Matthew Williams > Sent: 07 July 2004 19:11 > To: ris-users(a)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(a)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(a)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/

3 3

ris@ripe.net e-mail are ticketized from now on.
by Arife Vural 23 Jul '04

23 Jul '04

Hi guys, ris e-mails are ticketized from now on. ris is staying as mailinglist, and one copy of the e-mail is going to RIS ticketing que. People who are in the ris list will continue get the all ris e-mails. If you do not want, ask OPS to remove your e-mail address. But, please if you like to reply any of those e-mails, use XRTT. Otherwise, we loose control who replied which e-mail and so. Arife

1 0

MSK-IX RRC
by Matthew Williams 23 Jul '04

23 Jul '04

Just thinking out loud: In order to circumvent excessive $$$ at Russian customs, wouldn't it be smarter to have the IXP order a Dell PowerEdge to OPS requirements and ship your nifty little CD instead? Would that work or should we just go down the normal route. I will naturally have to ask the IXP as well. Cheers, Matthew

3 5

Other RIS things ...
by Matthew Williams 23 Jul '04

23 Jul '04

Hi Arife, Mae-West doesn't seem to be picking up in peers (4 - and according to Hong-Wei, no full feeds). It was some time ago since you tried to get their attention (nanog in miami?). After the good experiences at the NYIIX, shall we try LAIX? What do you think? BC thought that we should wait until the end of the year, but that requires giving gebert, bechly and pucik a little push (again). BTW, have you thought about cleaning up active bgp session or it that ops work? If they already have tools to monitor anycast and 3333 sessions then maybe the RIS could just plug into that. Cheers, Matthew +++ RRC00 ----- 195.66.224.112 4 3549 0 0 0 0 0 never Active | 195.69.144.85 4 3257 0 0 0 0 0 never Connect | RRC01 ----- 195.66.224.40 4 15861 0 0 0 0 0 never Active | 195.66.224.41 4 5604 0 0 0 0 0 never Active | 195.66.224.48 4 1299 0 0 0 0 0 never Active | 195.66.224.117 4 12513 0 0 0 0 0 never Active | 195.66.224.168 4 20940 0 10123 0 0 0 never Active | 195.66.226.10 4 2856 86 9 0 0 0 03w5d22h Connect | 195.66.226.11 4 2856 85 9 0 0 0 03w5d22h Connect | 195.66.226.40 4 15861 0 0 0 0 0 never Active | 195.66.226.47 4 8272 0 0 0 0 0 never Active | 195.66.226.103 4 2818 442 299 0 0 0 2d15h56m Active | 195.66.226.119 4 12390 0 0 0 0 0 never Connect | RRC02 ----- 194.68.129.164 4 13237 0 0 0 0 0 never Active | 194.68.129.173 4 6774 0 0 0 0 0 never Connect | 194.68.129.186 4 20766 356 355376 0 0 0 4d15h53m Idle | 194.68.129.225 4 5462 0 0 0 0 0 never Active | 194.68.129.252 4 2686 0 0 0 0 0 never Active | Etc....

4 4

myASN SQL queries
by Arife Vural 22 Jul '04

22 Jul '04

Hi Alexis, Today, when I looked at mySQL logs, I saw the one of myASN query and it returns almost all the entries in table. I do not know that was the intention or not. But, when we meet up for handover, I would like to go over those SQLs with you whether we can do any optimization or not. BTW, I hope tomorrow morning is OK for you. I have not got a reply from you yet. Arife

1 0

myASN transition on Wed, 14.00
by Arife Vural 21 Jul '04

21 Jul '04

Hi guys, What about working myASN transition on Wed, 14.00? Arife

4 6