- NLNOG - mailman3.nlnog.net

Fwd: [PDB Announce] Want to work as freelancer for PeeringDB Product Committee or know someone who could/should?
by Arnold Nipper 08 Feb '19

08 Feb '19

If you are interested or know someone who is. Greetings Arnold -------- Weitergeleitete Nachricht -------- Betreff: [PDB Announce] Want to work as freelancer for PeeringDB Product Committee or know someone who could/should? Datum: Tue, 29 Jan 2019 19:10:26 +0100 Von: Eric Loos <eric(a)ipergy.net> An: pdb-announce(a)lists.peeringdb.com PeeringDB is a non-profit member-based organization focussed on delivering a reference database service to the internet peering community that facilitates the building and maintenance of interconnections, a reference for data center locations, and contact information for networks, IXs, data centers and more globally. To deliver more value to the community, the PeeringDB Board of Directors has freed up funds for a part-time contractor product manager resource. With this announcement we are soliciting offers from the community first to fill this position. The product manager will work within the PeeringDB Product Committee under direction of the Product Committee Chair. The responsibilities of the product manager include, but are not limited to: * Participate in monthly calls with the Product Committee * Actively follow up action points * Organize customer focus group sessions * Facilitate the creation of an ongoing roadmap for PeeringDB and provide this as input to the Outreach Committee (1 year roadmap) * Shepherd the discussions of issues on Github and ensure resolution of issues that require decisions * Request quotes for the implementation of features and request the necessary approvals * Manage implementation and rollout of new features * Maintain the PeeringDB software release schedule * Keep Product Committee related documents on docs.peeringdb.com <http://docs.peeringdb.com> up to date * Ensure that the the PeeringDB Acceptable Use Policy and Privacy Policy are consistently applied * In addition, due to the recent open sourcing of the underlying software, the product manager shall describe the way user contributed code can make it into the main release, the product manager will document the release process in collaboration with the board, using Github issues as the tracking system. The engagement would be for approximately 16 hours a week during the initial three months and 5 hours per week after this, for an initial contract length of 12 months. There are no specific location requirements, however the Product Committee members are based in Western Europe and both East/West coast USA, candidates should take this in mind with regards to calls and communications. Experience with industry events like APRICOT, AfPIF, NANOG, GPF, EPF or similar events considered a plus PeeringDB does not and shall not discriminate on the basis of race, color, religion (creed), gender, gender expression, age, national origin (ancestry), disability, marital status, sexual orientation, or military status, in any of its activities or operations. These activities include, but are not limited to, hiring and firing of staff, selection of volunteers and vendors, and provision of services. We are committed to providing an inclusive and welcoming environment for all members of our staff, clients, volunteers, subcontractors, vendors, and clients. Performance Indicators for initial contract period: * Deliver a roadmap that has been agreed with the Product Committee within the initial 3 months of the engagement * Organize at least one customer focus session within the first 6 months and 1 subsequently every year * Keep the age of issues within decision and for review queues on github to a maximum of 30 days. * Ensure that new issues are triaged within one business day Please send your resume and application letter to eric(a)peeringdb.com <mailto:eric@peeringdb.com> or reach out if you have questions! Eric Loos Chair PeeringDB Product Committee -- Arnold Nipper email: arnold(a)nipper.de mobile: +49 172 2650958

1 0

Spoofer Report for NLNOG for Jan 2019
by CAIDA Spoofer Project 08 Feb '19

08 Feb '19

In response to feedback from operational security communities, CAIDA's source address validation measurement project (https://spoofer.caida.org) is automatically generating monthly reports of ASes originating prefixes in BGP for systems from which we received packets with a spoofed source address. We are publishing these reports to network and security operations lists in order to ensure this information reaches operational contacts in these ASes. This report summarises tests conducted within nld. Inferred improvements during Jan 2019: none inferred Source Address Validation issues inferred during Jan 2019: ASN Name First-Spoofed Last-Spoofed 28878 SIGNET 2018-06-27 2019-01-30 201290 BlackGATE 2018-10-16 2019-01-28 8737 PT 2019-01-16 2019-01-24 33915 TNF 2019-01-28 2019-01-28 Further information for these tests where we received spoofed packets is available at: https://spoofer.caida.org/recent_tests.php?country_include=nld&no_block=1 Please send any feedback or suggestions to spoofer-info(a)caida.org

1 0

pizza sessie beschikbaarheid
by Peter Spekreijse 20 Jan '19

20 Jan '19

Hoi! Met enige regelmaat reis ik vanuit Twente naar het westen van het land voor bijeenkomsten van NLNOG, ColoClue of NLUUG. Ik vind het jammer dat we in Twente niet zoiets hebben, we willen dat vanuit ons bedrijf faciliteren. Wil jij met vakmensen brainstormen, vraagstukken bespreken onder het genot van een pizza? Op 30 januari organiseren wij vanuit Root een pizzasessie voor engineers, systeem-, en functioneel beheerders met als thema: Hoe kom ik van een beschikbaarheid van 99,9% naar 99,999%? Interesse? http://ow.ly/bALs30nkRIU Groet, -- Peter Spekreijse Spekreijse Beheer BV E: peter(a)spekreijse.net T: +31.742669757 M: +31.641922460 W: http://peter.spekreijse.net KVK: 08107102 PGP: 6100 8D08 B0CD D8C9 52DA 74A7 845D 990C C083 FA95

1 0

Call for presentations RIPE 78
by Benno Overeinder 10 Jan '19

10 Jan '19

Dear colleagues, Please find the CFP for RIPE 78 below or at: https://ripe78.ripe.net/submit-topic/cfp/. The deadline for submissions is *3 March 2019*. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings. However, on an individual basis, participants can apply for a RIPE Fellowship or RACI, see the "Speakers" paragraph in CFP for more information. Kind regards, Benno Overeinder RIPE PC Chair https://ripe78.ripe.net/ripe-pc/ -------------------->>><<<-------------------- Call for Presentations A RIPE Meeting is an open event where Internet Service Providers, network operators and other interested parties get together. Although the meeting is mostly technical, it is also a chance for people to meet and network with others in their field. *RIPE 78 will take place from 20-24 May in Reykjavik, Iceland* The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary sessions, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 78. See the full descriptions of the different presentation formats: https://ripe78.ripe.net/submit-topic/presentation-formats/ Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than *3 March 2019*. Proposals submitted after this date will be considered depending on the slots still available in the programme. The PC is looking for presentations covering the topics of network engineering and operations, including but not limited to: - IPv6 deployment - Managing IPv4 scarcity - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange - Connected Things (aka. Internet of Things - IoT) ---- Speakers ---- Presenters, RIPE Working Group Chairs and the RIPE Programme Committee are required to cover their own costs to attend a RIPE Meeting (meeting ticket, travel and accommodation). We have various ticket options available depending on your needs. Please note that participants can apply for a RIPE Fellowship or RACI, on an individual basis, to develop their professional or academic career. For more information, please visit: https://www.ripe.net/participate/ripe/ripe-fellowship https://www.ripe.net/participate/ripe/raci In extraordinary circumstances, the RIPE Chair can waive the meeting fee for presenters. These requests are dealt with on a case-by-case basis via pc(a)ripe.net. ---- Submissions ---- Presenters should be clear on whether they wish to submit a presentation for a plenary or working group (WG) session. At present, most working groups will solicit policy proposals, discussion points or other content directly via their mailing lists. If you’re not sure what kind of session you should be presenting at, please visit: https://ripe78.ripe.net/plenary-or-wg/ RIPE Meeting attendees are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. Repeated audience feedback shows that the most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and should not attempt a product demonstration. Presenters should indicate how much time they will require. In general, the time allocated for the different presentation formats is as follows: - Plenary presentations: 20-25 minutes presentation with 5-10 minutes discussion - Tutorials: up to two hours (Monday morning) - Workshops: one hour (during evening sessions) to two hours (Monday morning) - BoFs: approximately one hour (during evening sessions) - Lightning talks: 10 minutes in total for both the presentation and any discussion The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe78.ripe.net/submit-topic/ - Lightning talks should also be submitted using the meeting submission system (https://ripe78.ripe.net/submit-topic/) and can be submitted any time up to and including the meeting week. The allocation of lightning talks will be announced on short notice, in some cases on the same day but often one day prior to the time slot allocated. - Presenters who propose a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. - All presentation proposals will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For panels, proposals must contain a clear description, as well as the names of invited panellists, presenters and moderators. ---- Diversity and Inclusion - On-Site Childcare and the RIPE Meeting Code of Conduct ---- Did you know that RIPE Meetings now have on-site childcare? You can reserve a spot for your child (age 6 months - 10 years) during the registration process for the meeting. Childcare places are limited, so please be quick to reserve a spot for your child while registering for the meeting. More information at: https://ripe78.ripe.net/on-site/on-site-childcare/ Ensuring that RIPE Meeting values are upheld and that attendees experience a professional, respectful and safe meeting is a priority. Please do read the RIPE Meeting Code of Conduct: https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-code-o… --- If you have any questions or requests concerning content submissions, please email pc(a)ripe.net.

1 0

Spoofer Report for NLNOG for Dec 2018
by CAIDA Spoofer Project 08 Jan '19

08 Jan '19

In response to feedback from operational security communities, CAIDA's source address validation measurement project (https://spoofer.caida.org) is automatically generating monthly reports of ASes originating prefixes in BGP for systems from which we received packets with a spoofed source address. We are publishing these reports to network and security operations lists in order to ensure this information reaches operational contacts in these ASes. This report summarises tests conducted within nld. Inferred improvements during Dec 2018: none inferred Source Address Validation issues inferred during Dec 2018: ASN Name First-Spoofed Last-Spoofed 28685 ASN-ROUTIT 2017-03-26 2018-12-14 20847 PREVIDER 2018-04-17 2018-12-12 28878 SIGNET 2018-06-27 2018-12-17 201290 BlackGATE 2018-10-16 2018-12-17 393437 KLAYER 2018-12-21 2018-12-21 13020 CCCV 2018-12-26 2018-12-29 Further information for these tests where we received spoofed packets is available at: https://spoofer.caida.org/recent_tests.php?country_include=nld&no_block=1 Please send any feedback or suggestions to spoofer-info(a)caida.org

1 0

NLNOG Nieuwjaarsborrel
by Nathalie Trenaman 08 Jan '19

08 Jan '19

[ English TL;DR: Friday January 18th, 2019 we'll congregate in Utrecht to celebrate the new year! Please register at the below URL. ] Beste allemaal, De kerstboom is de deur uit, de network freeze is over en dat betekent dat het weer bijna tijd is voor de traditionele NLNOG nieuwjaarsborrel! Volgende week vrijdag is het al zover en we hebben weer een mooie locatie in het centrum van Utrecht uitgezocht. We hopen jullie allemaal weer te zien en te horen wat jullie plannen zijn voor 2019 onder het genot van een drankje en natuurlijk bitterballen. Details: -------- Tijd: vanaf 19:00 Datum: 18 januari 2019 Plaats: Winkel van Sinkel, Oudegracht 158, Utrecht https://www.dewinkelvansinkel.nl/ De nieuwjaarsborrel word dit jaar mede mogelijk gemaakt door maar liefst 21 (!) sponsoren: Prefix Broker - Juniper Networks - RIPE NCC - AMS-IX - Cybersprint - KPN B.V. - PowerDNS - NTT Communications - PCextreme - NetFlix - LONAP - i3D.net - Duocast - NLnet Labs - Arista - NL-IX - Triple - Alturna Networks - Solid Optics - Speed IX - Asteroid International Aanmelden: ---------- Hoe meer zielen, hoe meer vreugd, dus neem ook eens een collega mee. Vergeet je niet even aan te melden: https://nlnognewyear2019.eventbrite.nl/ <https://nlnognewyear2019.eventbrite.nl/> Tot dan! Thomas, Melchior, Niels, Job, Nathalie

1 0

Verkiezing van Netwerk engineer van het jaar.
by Marco van den Akker 07 Jan '19

07 Jan '19

Hi allen. Vanuit TiNC Works! (www.tinc.works) willen we graag een positieve impuls geven aan de noodzakelijke roep om meer netwerk engineers. En daarom heb ik bedacht om een verkiezing te organiseren. Nu zou ik graag jullie input hebben, welke onderdelen er allemaal in de verkiezing moeten terugkomen. Zie het als een soort badpakkenronde. :) Ik had het volgende bedacht, maar laat me graag verrassen; Network Engineer of the Year Network Project Team Network Design In alle drie kan je een persoon of meerdere personen nomineren. Het idee erachter is, dat iedereen TiNC Works! gaat gebruiken. :) Onee. Het idee is om meer awareness te creeeren voor het vak netwerk beheerder. Het is vandaag de dag (en dat is misschien mijn beeld/ervaring) dat netwerk engineers te veel worden verward met Cloud netwerk Architecten. Verneem graag jullie aan en opmerkingen. En wees gerust, ik kan tegen een stootje. :) -- With enthusiastic greetings, Marco van den Akker VP of nearly everything TiNC Works!

1 0

NL abuse-overzicht 2018
by Jurrian van Iersel 27 Dec '18

27 Dec '18

Beste NLNOG-leden, Met het einde van het jaar in zicht is het weer de periode van jaaroverzichten en cijfertjes. Dit keer wou ik ook graag een duit in het zakje doen. De meesten van jullie zullen weten dat ik hobby-project heb waarbij ik abuse-informatie verzamel en meldt bij de betreffende ISP (zo niet, kijk de presentatie op NLNOG-dag 2017 even terug: https://youtu.be/Mt-KfNQG1oQ) Hoewel de statistici het dataset vast te klein en onbetrouwbaar vinden, wil ik hier toch een klein overzicht over 2018 voor Nederland maken. In onderstaande overzichten wordt naar incidenten gekeken waar het ip-adres op dat moment geregistreerd stond in Nederland; voor het ASN wordt de gene gebruikt die de IP-range op dat moment adverteerde. Ik noem bewust geen namen of ASN, zodat niemand zich persoonlijk aangesproken hoeft te voelen. Als we naar het aantal incidenten per ASN kijken, zal het niemand verbazen dat de eerste plaats vergeven wordt aan een bulletproof hoster. Ook op de zesde plaats treffen we zo’n partij aan. Opvallend genoeg bestaat de rest van de top 10 alleen uit hostingproviders (shared hosting, VPS en colocatie). De eerste accessprovider treffen we pas op de elfde plaats. Hieruit zouden we voorzichtig de conclusie kunnen trekken dat besmette PC’s bij argeloze thuisgebruikers niet meer het grootste gevaar zijn, maar dat slecht beveiligde servers (zowel virtueel als fysiek) een grotere bedreiging op vormen. Als we naar het type incidenten over het totaal (hosting + access) kijken, dan springen er 4 types bovenuit: opeenvolgend zijn dat SSH-login pogingen, SMTP-authenticatie pogingen, pogingen SIP te misbruiken en portscans. Met name TCP-poorten 7000 en 6666 zijn populair bij de portscans. Kijken we alleen naar de hosting-aanbieders uit de top 10 (bulletproof-partijen uitgesloten), dan is de volgorde SSH-login pogingen, pogingen SIP te misbruiken, Portscans en SMTP-authenticatie pogingen. Overigens moet bij het SIP-verkeer opgemerkt worden dat het UDP-verkeer is, waarbij het source-address eenvoudig te spoofen is. Anderzijds levert SIP-communicatie niet veel verkeer op, waardoor het niet interessant is voor een DDoS en is het misbruiken voor telefonie-fraude waarschijnlijker omdat dit veel lucratiever is. Concluderend zouden we kunnen stellen dat het goed gaat met de beveiliging door thuisgebruikers, waar adequaat handelen door de accessproviders een belangrijk onderdeel is. Voor de hosters is een belerend vingertje meer op de plaats; misbruik en gecompromitteerde servers zouden makkelijk gedetecteerd kunnen worden met de juiste beveiligingstools. Misschien moet de branche hier in 2019 eens (gezamenlijk) nadenken over een handelswijze bij incidenten. Waar accessproviders vaak vrij snel overgaan tot blokkades tot de problemen zijn opgelost, krijgen hostingklanten vaak 24 tot 48 uur de tijd op het probleem op te lossen voor er geblokkeerd wordt, terwijl in deze periode het abuse doorgaat. Ook in het kader van de GDPR / AVG lijkt het mij verstandiger sneller tot blokkade over te gaan als derden controle hebben over systemen met gegevens. Ik wens iedereen fijne feestdagen en een goed, gezond abuse-vrij 2019! Jurrian van Iersel

5 7

Fwd: BGP Experiment
by Job Snijders 20 Dec '18

20 Dec '18

For your information! ---------- Forwarded message --------- From: Italo Cunha <cunha(a)dcc.ufmg.br> Date: Thu, Dec 20, 2018 at 6:39 PM Subject: BGP Experiment To: NANOG <nanog(a)nanog.org>, DISCO experiment mailing list <disco-experiment(a)googlegroups.com> NANOG, We would like to inform you of an experiment to evaluate alternatives for speeding up adoption of BGP route origin validation (research paper with details [A]). Our plan is to announce prefix 184.164.224.0/24 with a valid standards-compliant unassigned BGP attribute from routers operated by the PEERING testbed [B, C]. The attribute will have flags 0xe0 (optional transitive [rfc4271, S4.3]), type 0xff (reserved for development), and size 0x20 (256bits). Our collaborators recently ran an equivalent experiment with no complaints or known issues [A], and so we do not anticipate any arising. Back in 2010, an experiment using unassigned attributes by RIPE and Duke University caused disruption in Internet routing due to a bug in Cisco routers [D, CVE-2010-3035]. Since then, this and other similar bugs have been patched [e.g., CVE-2013-6051], and new BGP attributes have been assigned (BGPsec-path) and adopted (large communities). We have successfully tested propagation of the announcements on Cisco IOS-based routers running versions 12.2(33)SRA and 15.3(1)S, Quagga 0.99.23.1 and 1.1.1, as well as BIRD 1.4.5 and 1.6.3. We plan to announce 184.164.224.0/24 from 8 PEERING locations for a predefined period of 15 minutes starting 14:30 GMT, from Monday to Thursday, between the 7th and 22nd of January, 2019 (full schedule and locations [E]). We will stop the experiment immediately in case any issues arise. Although we do not expect the experiment to cause disruption, we welcome feedback on its safety and especially on how to make it safer. We can be reached at disco-experiment(a)googlegroups.com. Amir Herzberg, University of Connecticut Ethan Katz-Bassett, Columbia University Haya Shulman, Fraunhofer SIT Ítalo Cunha, Universidade Federal de Minas Gerais Michael Schapira, Hebrew University of Jerusalem Tomas Hlavacek, Fraunhofer SIT Yossi Gilad, MIT [A] https://conferences.sigcomm.org/hotnets/2018/program.html [B] http://peering.usc.edu [C] https://goo.gl/AFR1Cn [D] https://labs.ripe.net/Members/erik/ripe-ncc-and-duke-university-bgp-experim… [E] https://goo.gl/nJhmx1

1 0

feedback gezocht: maximum prefix limits (inbound / outbound) draft
by Job Snijders 20 Dec '18

20 Dec '18

Beste NLNOGers, Melchior en ik proberen te specifieren welke varianten van BGP maximum prefix limits er bestaan, en promoten een nieuw type limiet, de 'outbound maximum prefix limit' - met als doel het mogelijk te maken dat sessies automatisch uitgezet worden als je zelf een full table naar een peer leaked. We wouden de Internet-Draft hier circuleren voor feedback voordat we het naar IETF sturen. Het document is hier te lezen: https://raw.githubusercontent.com/bgp/draft-grow-maxprefix/master/draft-sa-… Feedback qua terminologie, spelling, grammatica, zinsbouw - allemaal welkom! Met vriendelijke groeten, Job

9 15