- NLNOG - NLNOG

Spoofer Report for NLNOG for Jan 2020
by CAIDA Spoofer Project 08 Feb '20

08 Feb '20

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 2020: none inferred Source Address Validation issues inferred during Jan 2020: ASN Name First-Spoofed Last-Spoofed 8220 COLT 2016-11-10 2020-01-24 28685 ASN-ROUTIT 2017-03-26 2020-01-29 62240 Clouvider 2017-10-20 2020-01-30 1136 KPN 2019-09-04 2020-01-29 8587 Infracom 2019-10-28 2020-01-30 209299 VITOX-TELECOM 2019-12-15 2020-01-24 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

Attuor: Scalable monitoring
by Mark Schouten 23 Jan '20

23 Jan '20

Hi, Zoals sommigen van jullie misschien wel eens meegekregen hebben hebben wij een jaar of twee geleden Sensu geimplementeerd voor monitoring. Een heel cool product, maar helaas is het een tikkie om zeep geholpen om 'Enterprise' te worden. Hierdoor heb ik mijn plan van twee jaar geleden weer uit de doos getrokken, namelijk het zelf schrijven van een monitoring tool. Ik denk te hebben opgemerkt in de afgelopen jaren dat er wel meer mensen moeite hebben met kiezen wat er nou lekker werkt en handig te implementeren is. Daarnaast kunnen wij zelf best wel wat, maar weet ik dat er mensen zijn die veel betere code schrijven dan wij. Ik heb daarom een PoC van Attuor geschreven en d'r een Open Source-stempel op gezet (GPLv3) en gooi het bij deze in de NLnog-groep (en Blog [1] en LinkedIn en Twitter). Ik ga er verder mee aan de slag en ik zou het tof vinden om hulp/feedback te krijgen over hoe verder en beter. Je vind de code primair op [1] maar het wordt ook gesynced naar [2]. [1]: https://www.tuxis.nl/blog/attuor-scalable-monitoring-20200121/ [2]: https://gitlab.tuxis.nl/oss_public/attuor [3]: https://github.com/tuxis-ie/Attuor -- Mark Schouten <mark(a)tuxis.nl> Tuxis, Ede, https://www.tuxis.nl T: +31 318 200208

3 5

Call for Presentations RIPE 80
by Jelte Jansen 22 Jan '20

22 Jan '20

Dear colleagues, Please find the CFP for RIPE 80 below or at: https://ripe80.ripe.net/submit-topic/cfp/. The deadline for submissions is *23 February 2020*. 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, Jelte Jansen RIPE PC Member https://ripe80.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 80 will take place from 11-15 May in Berlin, Germany* 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 80. See the full descriptions of the different presentation formats: https://ripe80.ripe.net/submit-topic/presentation-formats/ Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than *23 February 2020*. 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://ripe80.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://ripe80.ripe.net/submit-topic/ - Lightning talks should also be submitted using the meeting submission system (https://ripe80.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://ripe80.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/ri pe-meeting-code-of-conduct --- If you have any questions or requests concerning content submissions, please [10]email pc(a)ripe.net.

1 0

Fwd: [uknof] MacBook Pro Keys
by Pim van Stam 15 Jan '20

15 Jan '20

Kan iemand deze man helpen? Toetsen vd Mac afgevallen en zoekt een goede winkel in A’dam Ik ben niet zo thuis in Amsterdam Groet, Pim > Begin forwarded message: > > From: Mark Tinka <mark.tinka(a)seacom.mu <mailto:mark.tinka@seacom.mu>> > Subject: [uknof] MacBook Pro Keys > Date: 15 January 2020 at 15:09:56 GMT > To: UKNOF Mailing List <uknof(a)lists.uknof.org.uk <mailto:uknof@lists.uknof.org.uk>> > > Hi all. > > Apologies for the off-topic post and for asking about the wrong country, but I'll be in Amsterdam next week for a couple of days, and am in need of keys for a mid-2017 15-inch Apple MacBook Pro Touch Bar. > > Many of the keys on my unit have failed their hinge slots, and the only replacement options in South Africa are the whole keyboard or unibody chassis. I just need the keys since the underlying (butterfly) mechanism is fine on all affected keys. It's just the hinge slots that fail over time and end up wedging the entire system, manifesting as a sticky or unresponsive key. > > Private replies on which shops I can walk into in Amsterdam are most welcome. > > And once again, apologies for the noise. Thanks. > > Mark.

1 0

Abuse overzicht 2019
by Jurrian van Iersel 13 Jan '20

13 Jan '20

Beste NLNOG'ers, Net als vorig jaar heb ik ook dit jaar weer een jaaroverzicht gemaakt van de abuse-incidenten in Nederland in 2019. Het overzicht is te vinden op https://www.linkedin.com/pulse/jaaroverzicht-computermisbruik-nederland-201…. De publicatie is dit jaar iets later en op een iets andere manier, nl. als artikel op LinkedIn. Reden hiervoor is dat ze het op m'n werk leuk vonden een LinkedIn-challenge op basis van de Social Selling Index te houden; het artikel hier publiceren scheelt mij weer een artikel schrijven ;) Aangezien in de enige met een technische functie ben die deelneemt, zou het fijn zijn als je het artikel ook nog even zou kunnen liken, sharen, enz. zodat ik de marketing- en sales-mensen iets makkelijker kan verslaan (en kan roepen dat technisch inhoudelijke artikelen beter zijn dan plaatjes en filmpjes vol technisch incorrect geblaat). Met vriendelijke groet, Jurrian van Iersel

2 2

Reminder: NLNOG New Years Drinks
by Nathalie Trenaman 09 Jan '20

09 Jan '20

Hi NLNOG people! We’re just one week and one day away from our legendary New Years Drinks! So far, 135 colleagues have signed up and extra bitterballen have been ordered ;) But there is still space for more of you. If you haven’t done so yet, please sign up here: https://www.eventbrite.nl/e/tickets-nlnog-new-years-drink-2020-85230323191 <https://www.eventbrite.nl/e/tickets-nlnog-new-years-drink-2020-85230323191> But if you registered, and you already know you can’t join us, please cancel your ticket in Eventbrite or let us know. Last year, the most ordered drink was…..coffee :D So we made sure there will be enough coffee :-) (and other drinks of course) You’re welcome from 19:00 at http://www.mammoni.nl/ <http://www.mammoni.nl/> Mariaplaats 14. We won’t serve dinner, so you might want to grab some food before you come. There is no restaurant in our venue. Looking forward to see you all next week! The NLNOG Crew Melchior, Niels, Job, Thomas and Nathalie

1 0

Spoofer Report for NLNOG for Dec 2019
by CAIDA Spoofer Project 08 Jan '20

08 Jan '20

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 2019: ASN Name Fixed-By 6830 LGI-UPC 2019-12-30 Further information for the inferred remediation is available at: https://spoofer.caida.org/remedy.php Source Address Validation issues inferred during Dec 2019: ASN Name First-Spoofed Last-Spoofed 28878 SIGNET 2018-06-27 2019-12-19 8587 Infracom 2019-10-28 2019-12-24 39647 REDHOSTING 2019-12-02 2019-12-03 209299 VITOX-TELECOM 2019-12-15 2019-12-15 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

Fwd: [nog-org] Fwd: [routing-wg] De-bogonising 2a10::/12
by Chriztoffer Hansen 08 Jan '20

08 Jan '20

Now forwarded. > https://www.ripe.net/participate/mail/forum/routing-wg/PDM2OTU0RkJFLUU0OEUt… ---------- Forwarded message --------- From: Nikolas Pediaditis <npediaditi(a)ripe.net> Date: Wed, 8 Jan 2020 at 14:28 Subject: [nog-org] Fwd: [routing-wg] De-bogonising 2a10::/12 To: <nog-org(a)ripe.net> Dear colleagues, Earlier today we sent the bellow announcement to several mailing lists. Could you please pass it on to your respective NOG’s mailing lists as well? Thank you in advance! Best regards, Nikolas Pediaditis RIPE NCC Begin forwarded message: From: Nikolas Pediaditis <npediaditi(a)ripe.net> Subject: [routing-wg] De-bogonising 2a10::/12 Date: 8 January 2020 at 12:17:43 CET To: routing-wg(a)ripe.net, Menog(a)menog.net, afnog(a)afnog.org, nanog(a)nanog.org, lacnog(a)lacnic.net, discuss(a)enog.org, sanog-request(a)sanog.org Dear colleagues, A few months ago the RIPE NCC became the first RIR to receive an additional /12 IPv6 allocation (2a10::/12) from IANA. We will soon begin to delegate space from this IPv6 block to LIRs. Prior to this, in order to improve routability and minimise the risk of filtering, the RIPE NCC will perform several de-bogonising activities in the next few weeks. We plan to start announcing the full /12, as well as a few /32 or longer blocks out of 2a10::/12 from AS12654 (RIPE Routing Information System (RIS)), within the next few days. We will analyse data from RIS and RIPE Atlas and we plan to write up an analysis around this effort. We want to remind everybody to update their bogon filters and allow routes originating from 2a10::/12 in their network. Kind regards, Nikolas Pediaditis Registration Services and Policy Development Manager RIPE NCC _______________________________________________ nog-org mailing list nog-org(a)ripe.net https://lists.ripe.net/mailman/listinfo/nog-org

1 0

Re: [NLNOG] Fwd: [arin-ppml] DoD to sell 13 x /8 of its IPv4 Blocks over the next 10 years
by michael＠masterwayz.nl 20 Dec '19

20 Dec '19

Hi, Mijn eerste post hier in the mailing list, dus als ik iets verkeerd doe dan hoor ik het graag. Zelf denk ik niet dat DoD uit hun zelf 13 /8s gaan verkopen, anders hadden ze dat uit hun zelf al wel gedaan. Nu vraag ik mij wel af wat hun met zo veel /8s moeten. Volgens mij worden sommige /8s niet eens gebruikt, zonde van de addressen eigenlijk. Wel bedankt voor het laten weten! Michael -----Original Message----- From: NLNOG <nlnog-bounces(a)nlnog.net> On Behalf Of Sabri Berisha Sent: Thursday, 19 December 2019 23:07 To: Job Snijders <job(a)ntt.net> Cc: nlnog <nlnog(a)nlnog.net> Subject: Re: [NLNOG] Fwd: [arin-ppml] DoD to sell 13 x /8 of its IPv4 Blocks over the next 10 years Hi, Dat niet in de wet staat dat het moet zegt niet dat de DoD het niet mag doen. Zie 32CFR 273.7: https://www.law.cornell.edu/cfr/text/32/273.7 De vraag is of ze het willen zonder dat ze gedwongen worden. Ik denk dat het logisch is; met de huidige druk om ipv6 uit te rollen denk ik dat de prijs voor v4 heel hard richting de top gaat, en vervolgens vanaf een cliff rolt en niks meer waard gaat zijn. Thanks, Sabri ----- On Dec 19, 2019, at 6:17 AM, Job Snijders job(a)ntt.net wrote: > Oh, het is weer van de baan.. > > ---------------------------------------------------------------------- > ---------- > > Date: Thu, 19 Dec 2019 15:05:34 +0100 > From: Bill Woodcock <woody(a)pch.net> > To: hostmaster(a)uneedus.com > Cc: "arin-ppml(a)arin.net" <arin-ppml(a)arin.net> > Subject: Re: [arin-ppml] DoD to sell 13 x /8 of its IPv4 Blocks over the next > 10 years and need for ARIN-2019-19 > > Apparently it was in the House Bill, but was removed in the Senate > version, and didn’t make it through conference. > > -Bill > _______________________________________________ > NLNOG mailing list > NLNOG(a)nlnog.net > http://mailman.nlnog.net/listinfo/nlnog _______________________________________________ NLNOG mailing list NLNOG(a)nlnog.net http://mailman.nlnog.net/listinfo/nlnog

3 2

Fwd: [arin-ppml] DoD to sell 13 x /8 of its IPv4 Blocks over the next 10 years
by Job Snijders 19 Dec '19

19 Dec '19

FYI ---------- Forwarded message --------- From: Fernando Frediani <fhfrediani(a)gmail.com> Date: Thu, Dec 19, 2019 at 12:32 Subject: [arin-ppml] DoD to sell 13 x /8 of its IPv4 Blocks over the next 10 years To: arin-ppml(a)arin.net <arin-ppml(a)arin.net> I believe these are relevant news to this list https://www.congress.gov/bill/116th-congress/senate-bill/1790/text#toc-H373… "IPv6 strategy made it into NDAA 2020, requiring DOD to sell 13 x /8s (1) IN GENERAL.—Not later than 10 years after the date of the enactment of this Act, the Secretary of Defense shall sell all of the IPv4 addresses described in subsection (b) at fair market value." Finally is happening. I imagined that one day they would return something, but decided to sell. However, looking at the good side, this makes all this wasted space to become utilized. A few questions that arise are: how will this selling process happen, if directly, through brokers, if there will be any mechanism to distribute this selling among each one of all 5 RIRs or if it will be opened in the model "first come, first served" And before something says, I don't believe this will make any big difference to IPv6 implementation to advance or delay it significantly. Even talking about more than 200 million IPv4 addresses, I don't think this will change much this scenario if they are put directly at end users disposition. Finally, an important detail to highlight in the report is: "(D) *The plan of the Secretary to transition all Department addresses to IPv6.*" Let's see who will be the big buyers and how will this affect the IPv4 value for the next years. Regards Fernando Frediani _______________________________________________ ARIN-PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List (ARIN-PPML(a)arin.net) Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-ppml Please contact info(a)arin.net if you experience any issues.

5 5