- NLNOG - mailman3.nlnog.net

atom86: invalid==reject (RPKI)
by Robert Heuvel 19 Sep '18

19 Sep '18

Beste NLNOG-ers, Circa drie weken geleden heeft atom86 invalid==reject (RPKI) geïmplementeerd op haar peers en upstreams. Mijn gewaardeerde collega Ralph Dirkse heeft hier een niet te technisch artikel voor gemaakt en op LinkedIn geplaatst: https://www.linkedin.com/pulse/atom86-leveraging-rpki-make-internet-safer-p… We vertrouwen erop dat velen ons zullen volgen om het internet een veiligere plek te maken ;) Mvg, Robert Heuvel atom86 +31 624590510 +31 207506500 Boeing Avenue 271 1119 PD Schiphol-Rijk

4 5

Spoofer Report for NLNOG for Aug 2018
by CAIDA Spoofer Project 08 Sep '18

08 Sep '18

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 Aug 2018: none inferred Source Address Validation issues inferred during Aug 2018: ASN Name First-Spoofed Last-Spoofed 30823 COMBAHTON 2016-02-16 2018-08-30 6830 LGI-UPC 2016-04-01 2018-08-24 44858 PROXSYS 2018-03-26 2018-08-16 28878 SIGNET 2018-06-27 2018-08-06 16243 VIRTU 2018-08-09 2018-08-13 47886 EQUINIX-NL-ASN 2018-08-09 2018-08-13 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

Last call for presentations and Draft programme for RIPE 77
by Benno Overeinder 07 Sep '18

07 Sep '18

Colleagues, A list of currently accepted RIPE 77 presentations is now published at: https://ripe77.ripe.net/programme/meeting-plan/plenary/ There are still plenary, BoF, tutorial and workshop slots remaining for the final RIPE 77 programme and RIPE Programme Committee will accept new proposals until *21 September 2018*. This is our last call for you to submit your proposals. You can find the CFP for RIPE 77 below or at https://ripe77.ripe.net/submit-topic/cfp/, for your proposals for plenary session presentations, tutorials, workshops, BoFs (Birds of a Feather sessions) and lightning talks. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings, see the "Speakers" paragraph in CFP for more information. Kind regards, Benno Overeinder RIPE PC Chair https://ripe77.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 77 will take place from 15-19 October in Amsterdam, The Netherlands* 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 77. See the full descriptions of the different presentation formats: https://ripe77.ripe.net/submit-topic/presentation-formats/ Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than *21 September 2018*. 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. 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. Also note that, on an individual basis, participants can apply for a RIPE Fellowship or RACI 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 ---- 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://ripe77.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://ripe77.ripe.net/submit-topic/ - Lightning talks should also be submitted using the meeting submission system (https://ripe77.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. Registrations for RIPE 77 will open mid-July. Childcare places are limited, so please be quick to reserve a spot for your child! Read about the experiences of our next generation of engineers at: https://labs.ripe.net/Members/agowland/ripe-meeting-diversity-efforts-on-si… 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

Re: [NLNOG] atom86: invalid==reject (RPKI)
by Paul Hoogsteder 04 Sep '18

04 Sep '18

Hallo Robert, filteren jullie alleen invalid prefixes die binnenkomen "vanaf het Internet", of ook van jullie klanten? Groet, Paul Hoogsteder Meanie AS31019 > Beste NLNOG-ers, > > Circa drie weken geleden heeft atom86 invalid==reject (RPKI) > geïmplementeerd op haar peers en upstreams. > > Mijn gewaardeerde collega Ralph Dirkse heeft hier een niet te technisch artikel voor gemaakt en op LinkedIn geplaatst: > https://www.linkedin.com/pulse/atom86-leveraging-rpki-make-internet-safer-p… > > We vertrouwen erop dat velen ons zullen volgen om het internet een veiligere plek te maken ;) > > Mvg, > > Robert Heuvel > atom86 > > +31 624590510 > +31 207506500 > Boeing Avenue 271 > 1119 PD Schiphol-Rijk > > _______________________________________________ > NLNOG mailing list > NLNOG(a)nlnog.net > http://mailman.nlnog.net/listinfo/nlnog >

3 4

Re: [NLNOG] atom86: invalid==reject (RPKI)
by Robert Heuvel 04 Sep '18

04 Sep '18

Paul, Zoals Ralph reeds heeft gemailed (maar response moet nog goedgekeurd worden door NLNOG moderator...): "Voor klanten filteren we middels een prefix filter dus valideren is dan eigenlijk niet nodig. Toch valideren we klant prefixes wel echter zonder de reject." R. -----Original Message----- From: Paul Hoogsteder <paul(a)meanie.nl> Sent: Tuesday, September 4, 2018 1:43 PM To: Robert Heuvel <RHeuvel(a)atom86.net> Cc: nlnog(a)nlnog.net Subject: Re: [NLNOG] atom86: invalid==reject (RPKI) Hallo Robert, filteren jullie alleen invalid prefixes die binnenkomen "vanaf het Internet", of ook van jullie klanten? Groet, Paul Hoogsteder Meanie AS31019 > Beste NLNOG-ers, > > Circa drie weken geleden heeft atom86 invalid==reject (RPKI) > geïmplementeerd op haar peers en upstreams. > > Mijn gewaardeerde collega Ralph Dirkse heeft hier een niet te > technisch artikel voor gemaakt en op LinkedIn geplaatst: > https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww > .linkedin.com%2Fpulse%2Fatom86-leveraging-rpki-make-internet-safer-pla > ce-ralph-dirkse%2F%3Fpublished%3Dt&data=02%7C01%7C%7C9fc999fedbf34 > b72d81908d6125b947e%7Cdb27021b05df420391f71dc8f2fa0f3b%7C1%7C0%7C63671 > 6581889456888&sdata=5JXJIk5OOL0vJ6U5vic7a1WyN5dISWyqUpm%2BwvkBXBQ% > 3D&reserved=0 > > We vertrouwen erop dat velen ons zullen volgen om het internet een > veiligere plek te maken ;) > > Mvg, > > Robert Heuvel > atom86 > > +31 624590510 > +31 207506500 > Boeing Avenue 271 > 1119 PD Schiphol-Rijk > > _______________________________________________ > NLNOG mailing list > NLNOG(a)nlnog.net > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmail > man.nlnog.net%2Flistinfo%2Fnlnog&data=02%7C01%7C%7C9fc999fedbf34b7 > 2d81908d6125b947e%7Cdb27021b05df420391f71dc8f2fa0f3b%7C1%7C0%7C6367165 > 81889456888&sdata=dsRafkvklAfP%2BDfHSfGYoz%2FjzJonnNs3VQxO1K7WgAA% > 3D&reserved=0 >

1 0

2nd call for presentations RIPE 77
by Benno Overeinder 20 Aug '18

20 Aug '18

RIPE 77 Meeting dit najaar weer in Amsterdam! Groeten, -- Benno Dear colleagues, Please note the approaching deadline of *26 August 2018* for RIPE 77 plenary programme submissions. You can find the CFP for RIPE 77 below or at https://ripe77.ripe.net/submit-topic/cfp/, for your proposals for plenary session presentations, tutorials, workshops, BoFs (Birds of a Feather sessions) and lightning talks. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings, see the "Speakers" paragraph in CFP for more information. Kind regards, Benno Overeinder RIPE PC Chair https://ripe77.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 77 will take place from 15-19 October in Amsterdam, The Netherlands* 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 77. See the full descriptions of the different presentation formats: https://ripe77.ripe.net/submit-topic/presentation-formats/ Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than *26 August 2018*. 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. 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. Also note that, on an individual basis, participants can apply for a RIPE Fellowship or RACI 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 ---- 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://ripe77.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://ripe77.ripe.net/submit-topic/ - Lightning talks should also be submitted using the meeting submission system (https://ripe77.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. Registrations for RIPE 77 will open mid-July. Childcare places are limited, so please be quick to reserve a spot for your child! Read about the experiences of our next generation of engineers at: https://labs.ripe.net/Members/agowland/ripe-meeting-diversity-efforts-on-si… 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

Fw: celebrating 10 years of routing insecurity
by Job Snijders 10 Aug '18

10 Aug '18

FYI :-) ----- Forwarded message from Job Snijders <job(a)ntt.net> ----- Date: Fri, 10 Aug 2018 12:30:38 +0000 From: Job Snijders <job(a)ntt.net> To: nanog(a)nanog.org Subject: celebrating 10 years of routing insecurity Dear all, Today marks the 10th anniversary of the famous Kapela-Pilosov Man-in-the-middle BGP attack! It is a fantastic and innovative attack that would be worthy of referencing in the next Mr Robot season. :-) video: https://www.youtube.com/watch?v=S0BM6aB90n8 slide: https://www.defcon.org/images/defcon-16/dc16-presentations/defcon-16-piloso… So, what is the state of routing security anno 2018? It seems that as an industry we're on an upwards trajectory: various IRR registries are locking themselves down to prevent creation of unauthorized route(6) objects, new filter generation tools are becoming available, RPKI based BGP Origin Validation is slowly seeing more and more deployment, and the concept of blocking route announcements with improbable AS_PATHs is gaining popularity as well. Let's see where we are 10 years from now! Kind regards, Job ----- End forwarded message -----

1 0

Open consultaties Forum Standaardisatie
by Marco Hogewoning 10 Aug '18

10 Aug '18

All, [apologies to the non Dutch, but as this concerns Dutch government and all base documents are in Dutch as well] Voor wie ze niet kent, het Forum Standaardisatie bepaald welke standaarden de Nederlandse overheid moet gebruiken of afdwingen in aanbestedingen, hieronder vallen uiteraard ook een groot aantal IT and Internet standaarden. Deze standaarden, bijvoorbeeld IPv6, kunnen geplaatst worden op een zgn pas-toe-of-leg-uit lijst, of zelfs simpelweg benoemd worden tot verplichte standaard. Eens in de zoveel tijd wordt de lijst herzien en waar nodig aangepast, bijvoorbeeld om nieuwe versies te introduceren of gedateerde standaarden te verwijderen. Zulke wijzigingen worden gemaakt op basis van observaties of feedback van de betrokken industrie en vergezeld van een rapport met het advies van relevante experts (zelf ooit meegeschreven aan de IPv6 evaluatie). Hierna volgt een openbare consultatie, waarbij iedereen zijn of haar visie kan geven of een bepaalde standaard daadwerkelijk toegevoegd (of afgevoerd moet worden). Er loopt op dit moment een vrij uitgebreide consultatie ronde, met deadline 10 september, waar ook een aantal voor de Internet community belangrijke standaarden onder staan: - Toepassing van TLS 1.3 als vervanging van 1.2 - Uitbreiding van het toepassen van DANE en STARTTLS - Toepassing van S/MIME voor email ondertekening Mocht je nu of in de toekomst zakendoen met de Nederlandse overheid kan het zijn dat je gevraagd wordt deze standaarden te ondersteunen, en dan zou ik zeker even kijken of het nuttig is om input te leveren. Of misschien heb je veel ervaring met een van deze standaarden en wil je die expertise delen. Grijp je kans om je mening te geven, lees de rapporten en geef feedback. De lijst met standaarden en het proces staan beschreven op https://www.forumstandaardisatie.nl/thema/openbare-consultatie en daar vindt je ook het adres waar je je commentaar naartoe kan sturen. Groet, MarcoH (die gevraagd was om dit onder de aandacht te brengen van relevante stakeholders) -- "Life is like riding a bicycle. To keep your balance you must keep moving" -- Albert Einstein

2 2

NLNOGday 2018: We're sold out!
by Nathalie Trenaman 10 Aug '18

10 Aug '18

Hi all, We just (1 minute ago) reached that point where all 200 tickets for NLNOGday 2018 are gone! The location is set, the program is almost finished and it’s going to be a fun and inspiring day again. If you still want to attend but didn’t register yet, please drop an e-mail to events(a)nlnog.net <mailto:events@nlnog.net> and we’ll add you to the waiting list. In case you already know you can’t make it to NLNOGday on the 7th of September, also please let us know, so we can pass your ticket to someone else. This has worked very well last year, we ended up with no-one on the waiting list and very few no-shows. All information about the program and location can be found here: https://nlnog.net/nlnog-day-2018/ <https://nlnog.net/nlnog-day-2018/> Looking forward to see you all on the 7th of September! Cheers, Nathalie

2 1

Spoofer Report for NLNOG for Jul 2018
by CAIDA Spoofer Project 08 Aug '18

08 Aug '18

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 Jul 2018: none inferred Source Address Validation issues inferred during Jul 2018: ASN Name First-Spoofed Last-Spoofed 28878 SIGNET 2018-06-27 2018-07-11 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