- connect-wg - mailman.ripe.net

AS34991 -- hijacked
by Ronald F. Guilmette 06 Jun '17

06 Jun '17

Is there any chance that any of you might be persuaded to have a word or two with either or both of the upstreams for AS34991, specifically with respect to the fact that that whole and entire AS has quite obviously been hijacked, and that it is currently being used and abused to announce a total of 20 completely and transparently bogus routes into various bits of IPv4 space that are allocated to various parties within the nation of Columbia, including but not limited to the National University thereof? I have already attempted to make contact with both upstreams in this case with no success and no reply so far, perhaps because I am not a european, or perhaps because I myself am not a network operator, or perhaps because I do not speak (or write) bulgarian. Below is a listing of the currently hijacked routes. Please note that the hijacker in this case quite obviously planned this all, quite carefully, and in advance of the actual hijackings, and he tried (and succeded!) to effectively legitimize all of these bogus route announcement via the simple and easy ruse of also pre-creating a set of matching, and equally bogus route objects within the RIPE data base. (As I learned the last time a case like this came up, the RIPE community, in its infinite wisdom, had made it so easy to create such route objects in the data base, with no authority or authorization whatsoever, that any baboon with a keyboard and a pulse may easily do so.) Of course, as the more observant among you may note, the domain name used for the contact email address for AS34991 has recently been re-registered, presumably after having lapsed. This indicates rather clearly, I think, that it is not merely the IPv4 blocks listed below that have been and are being hijacked, but also the AS34991 ASN itself. covfefe P.S. For the record, yes, some of the hijacked blocks in this case have already been sub-leased out to snowshoe spammers, and are being actively used for snowshoe spamming as we speak. ===================================================================== 152.204.132.0/24 -- Columbia 152.204.133.0/24 -- Columbia 152.231.25.0/24 -- Columbia 152.231.28.0/24 -- Columbia 168.176.187.0/24 -- Columbia, National University of 168.176.192.0/24 -- Columbia, National University of 168.176.194.0/24 -- Columbia, National University of 168.176.218.0/24 -- Columbia, National University of 168.176.219.0/24 -- Columbia, National University of 179.1.71.0/24 -- Columbia 181.57.40.0/24 -- Columbia 186.113.13.0/24 -- Columbia 186.113.15.0/24 -- Columbia 186.147.230.0/24 -- Columbia 190.90.31.0/24 -- Columbia 190.90.88.0/24 -- Columbia 200.1.65.0/24 -- Columbia 200.14.44.0/24 -- Columbia 200.24.3.0/24 -- Columbia 200.24.5.0/24 -- Columbia

1 0

Draft agenda for Connect-WG @ RIPE 74
by Florence Lavroff 08 May '17

08 May '17

Dear friends of the Connect WG, Still 2 weeks to go before we gather again in Budapest ! We are pleased to send you our draft agenda for the coming session of Wednesday, May 10th 2017, 11 AM : 1. Introduction + agenda presentation 2. IXP-tools code sprint, 5-6. April 2017, Amsterdam - Vesna Manojlovic, Emile Aben, RIPE NCC (15 min) 3. IXP database - Bijal Sanghani - Euro-IX (10 min) 4. *TENTATIVE* IXP Automation Made Easy with New Open-Source Tool - Pier Carlo Chiedi (10 min) 5. Latest trends in DC optics - Christian Urricariet - Finisar (10 min) 6. BGP shutdown communication - Job Snijders - NTT (10 min) 7. New way of DDoS mitigation in IXPs, Zbynek Pospichal, NIX.CZ (10 min) 8. IXP Roman-IX - Will van Gulik (3 min) 9. Asteroids - Nurani Nimpuno, Andy Davidson (3min) 10. Feedback about the session 11. Closure Kind regards, Co-chairs, Florence and Remco -- Florence Lavroff / lavroff(a)google.com / +31 6 11 01 55 80 Peering and Content Distribution / Google EMEA

1 1

Follow Up to IXP Tools Hackathon: Code Sprint
by Vesna Manojlovic 10 Apr '17

10 Apr '17

Dear colleagues, As a part of the RIPE NCC's ongoing engagement with the Internet Exchange Points (IXPs), last week we have organised a code sprint - a two-day meeting, in Amsterdam. Researchers and IXP developers got together to continue work on the projects started during the IXP Tools hackathon. This article is a short summary of their achievements: https://labs.ripe.net/Members/becha/follow-up-to-ixp-tools-hackathon-code-s… Look out for detailed descriptions of all these projects in future RIPE Labs articles. Regards, Vesna Manojlovic RIPE NCC

1 0

[connect-wg] Call for presentations Connect-WG @ RIPE 74
by Florence Lavroff 24 Mar '17

24 Mar '17

Dear friends of the Connect-WG, It is less than 2 months to RIPE 74 ! Our next Connect-WG session will take place on Wednesday, May 10th in Budapest. If there is any topic you’d like to present during the Working Group, please let us know (connect-wg-chairs(a)ripe.net) and we’ll update our session agenda accordingly. Looking forward to seeing you all soon, Kind regards, Florence and Remco Connect-WG co-chairs -- Florence Lavroff / lavroff(a)google.com / +31 6 11 01 55 80 Peering and Content Distribution / Google EMEA

2 1

New on RIPE Labs: IXP Automation Made Easy with New Open-Source Tool
by Mirjam Kuehne 20 Mar '17

20 Mar '17

Dear colleagues, Please find a new article on RIPE Labs describing a new open source tool for IXPs developed by Pier Carlo Chiodi: https://labs.ripe.net/Members/pier_carlo_chiodi/ixp-automation-made-easy-wi… Kind regards, Mirjam Kuhne RIPE NCC

1 0

Fwd: draft-iops-grow-bgp-session-culling-00
by Job Snijders 13 Mar '17

13 Mar '17

This work might interest some of you. Let us know your feedback! https://tools.ietf.org/html/draft-iops-grow-bgp-session-culling <https://tools.ietf.org/html/draft-iops-grow-bgp-session-culling-00> ---------- Forwarded message --------- From: Job Snijders <job(a)ntt.net> Date: Sun, 12 Mar 2017 at 23:16 Subject: draft-iops-grow-bgp-session-culling-00 To: <grow(a)ietf.org>, <draft-iops-grow-bgp-session-culling(a)ietf.org> Dear GROW, With this BCP Internet-Draft we hope to draw some attention to good practises which can be applied by IP networks or IXPs to mitigate negative impact caused by maintenance operations on lower layer networks. The idea is to promote the concept of breaking the control-plane in a controlled fashion, before actually breaking the data-plane. Regarding the "Voluntary BGP Session Teardown Recommendations" - we all too often see operators do the equivalent of 'yanking the cable out of its socket' while not allowing any time for reconvergence. As far as I am aware, there is no documentation which recommends to shutdown BGP sessions and allow for some time for the traffic to subside due to rerouting, and then commence with the maintenance. Some background on the "Involuntary BGP Session Teardown Recommendations": a number of years ago an (at the time novel) approach was presented on how to reduce the negative impact of IXP maintenance. Since then the idea gained popularity and is applied at more and more IXPs. The video + pdf are available here: https://ripe67.ripe.net/archives/video/116/ The approaches outlined in this document may not be required in every network topology, for instance some IXPs have fantastic 'make before break' methodologies accomplished through a layer of photonic switches. I'd like to ask the chairs for a 10 minute slot in GROW's session a IETF 98 to present on this draft. Kind regards, Job ps. Some may point out that this is a rampant layering violation, to which I will say: "yes". ;-) ----- Forwarded message from internet-drafts(a)ietf.org ----- Date: Sun, 12 Mar 2017 14:00:18 -0700 From: internet-drafts(a)ietf.org To: i-d-announce(a)ietf.org Subject: I-D Action: draft-iops-grow-bgp-session-culling-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Mitigating Negative Impact of Maintenance through BGP Session Culling Authors : Will Hargrave Matt Griswold Job Snijders Nick Hilliard Filename : draft-iops-grow-bgp-session-culling-00.txt Pages : 9 Date : 2017-03-12 Abstract: This document outlines an approach to mitigate negative impact on networks resulting from maintenance activities. It includes guidance for both IP networks and Internet Exchange Points (IXPs). The approach is to ensure BGP-4 sessions affected by the maintenance are forcefully torn down before the actual maintenance activities commence. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-iops-grow-bgp-session-culling/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-iops-grow-bgp-session-culling-00 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ I-D-Announce mailing list I-D-Announce(a)ietf.org https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt ----- End forwarded message -----

1 0

Research project and survey: Network filtering and IP spoofing
by Franziska Lichtblau 01 Mar '17

01 Mar '17

Hi, we are a team of researchers from TU Berlin [1] working on a measurement project to assess the ramifications of traffic with spoofed source IP addresses in the Internet. This is a follow-up to the talk I gave in this WG in Madrid. As I got a lot of positive and encouraging feedback after my talk we are continuing this project. To better understand the operational challenges that you as network operators face when deploying (or not deploying) source IP address filtering techniques, we'd like to invite you to participate in our survey. If you could spare 5 minutes of your time, we'd be delighted if you could fill out our survey form and tell us about your current practices regarding network filtering. To participate, please visit: [2] http://filteringsurvey.inet.tu-berlin.de/ If you have any concerns or questions, you can reply on-list or contact us via [3] filtering-survey(a)inet.tu-berlin.de. We will only publish anonymized results of this study and once we've analyzed your feedback we'll publish a digest of the results on-list if you're interested. As you are probably subscribed to more network operator lists and WG lists you might encounter this mail multiple times. We apologize for cross-posting, but in order to get results that will give us meaningful insights we need the broadest coverage we can get. Thank you very much for your support! Franziska Lichtblau [1] www.inet.tu-berlin.de [2] http://filteringsurvey.inet.tu-berlin.de/ [3] filtering-survey(a)inet.tu-berlin.de -- Franziska Lichtblau, M.A. building MAR, 4th floor, room 4.004 Fachgebiet INET - Sekr. MAR 4-4 phone: +49 30 314 757 33 Technische Universität Berlin gpg-fp: 4FA0 F1BC 8B9A 7F64 797C Marchstrasse 23 - 10587 Berlin 221C C6C6 2786 91EC 5CD5

1 0

Updated NOG wiki
by Michael Oghia 08 Feb '17

08 Feb '17

Dear colleagues, I went through and updated the NOG Wikipedia page this morning. Feel free to add resources/links, or additional NOGs that are not listed: https://en.wikipedia.org/wiki/Internet_Network_Operators%27_Groups Best, -Michael __________________ Michael J. Oghia iGmena <http://igmena.org/> communications manager Independent #netgov consultant & editor Belgrade, Serbia Skype: mikeoghia Twitter <https://www.twitter.com/MikeOghia> *|* LinkedIn <https://www.linkedin.com/in/mikeoghia>

1 0

New on RIPE Labs: IXP Hackathon Results
by Mirjam Kuehne 01 Nov '16

01 Nov '16

Dear colleagues, Please find a summary of the IXP hackathon that took place before RIPE 73 on RIPE Labs: https://labs.ripe.net/Members/becha/ixp-tools-hackathon-results It lists all the projects including slides and links to the code. Kind regards, Mirjam Kuehne RIPE NCC

1 0

PeeringDB Product Committee Charter Survey / RIPE Connect-WG
by Arnold Nipper 18 Oct '16

18 Oct '16

Hello PeeringDB users / hello RIPE connect-wg, the PeeringDB Product Committee (PC, [0]) is charged with steering the future product development and running the market outreach efforts to continuously improve the value that PeeringDB delivers to the networks registered with PeeringDB, and the broader community. We're looking for feedback and input from the community on our charter proposal. Please take this short survey [1]. Your input and comments are appreciated! [0] http://docs.peeringdb.com/gov/ [1] https://www.surveymonkey.com/r/JN36DT2 Greetings Arnold -- Arnold Nipper

1 1