- NLNOG - mailman3.nlnog.net

2nd call for presentations RIPE 74
by Benno Overeinder 05 Mar '17

05 Mar '17

Dear colleagues, Please note the approaching deadline of *12 March 2017* for RIPE 74 plenary programme submissions. You can find the CFP for RIPE 74 below or at https://ripe74.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. Kind regards, Benno Overeinder RIPE PC Chair https://ripe74.ripe.net/programme/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 74 will take place from 8-12 May 2017 in Budapest, Hungary. 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 74. See the full descriptions of the different presentation formats, https://ripe74.ripe.net/submit-topic/presentation-formats/. Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 12 March 2017. Proposals submitted after this date will be considered depending on the remaining available space in the programme. The PC is looking for presentations covering 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) Submissions 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 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 - Lightning talks: 10 minutes total for both presentation and any discussion The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe74.ripe.net/submit-topic/submission-form/. - Lightning talks should also be submitted using the meeting submission system (https://ripe74.ripe.net/submit-topic/submission-form/) and can be submitted any time up to and including the meeting week. Allocation of lightning talks will start a few days before the meeting, and will continue throughout the meeting. During the meeting, they may be announced on the day before the talk or even on the same day as the talk. - Lightning talks should also be submitted using the meeting submission system (https://ripe74.ripe.net/submit-topic/submission-form/) 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. - Due to potential technical issues, presenters/panellists should be physically present at the RIPE Meeting. If you have any questions or requests concerning content submissions, please email pc [at] ripe [dot] net. -- Benno J. Overeinder NLnet Labs http://www.nlnetlabs.nl/

1 0

IANA IPv4 Recovered Address Space registry updated
by Paula Wang 01 Mar '17

01 Mar '17

Hi, An update has been made to the IANA IPv4 Recovered Address Space registry according to the Global Policy for Post Exhaustion IPv4 Allocation Mechanisms by the IANA (https://www.icann.org/resources/pages/allocation-ipv4-post-exhaustion-2012-…) The list of allocations can be found at: https://www.iana.org/assignments/ipv4-recovered-address-space/ Kind regards, Paula Wang IANA Services Specialist PTI

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. 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 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

Join RIPE NCC DNS Measurements hackathon, 20-21. April 2017, Amsterdam
by Vesna Manojlovic 08 Feb '17

08 Feb '17

Dear colleagues, The fifth RIPE NCC hackathon will take place on Thursday and Friday, 20-21 April 2017, in Amsterdam. We're looking for front-end developers, UI designers, DNS operators, researchers and other enthusiastic participants, to help us develop new tools and visualizations based on DNS measurements data. All source code developed during the hackathon will be publicly licensed and available on GitHub, and will be free for the entire community to use. -------------------- How to Apply -------------------- Interested? Apply online today! https://atlas.ripe.net/hackathon/dns-measurements/#!application-form *The application deadline is 26 February 2017* We look forward to seeing you there! Find out more in this RIPE Labs article: https://labs.ripe.net/Members/alun_davies/dns-measurements-hackathon-2017 Regards, Vesna Manojlovic RIPE NCC Community Builder -- All previous events: https://labs.ripe.net/hackathons

1 0

RIPE NCC Member lunch
by Nathalie Trenaman 01 Feb '17

01 Feb '17

Hoi allemaal, Even een mail met mijn RIPE NCC pet op. Op 17 Februari organiseert RIPE NCC een member lunch in Amsterdam. Dit is een gelegenheid om in een informele setting kennis te maken en je mening te geven over zaken die betrekking hebben op RIPE en RIPE NCC. Ben je nog niet zo lang lid, en heb je vragen over de policies, IPv4, IPv6, RIPE Atlas of een van onze andere diensten, of ben je juist al lang lid en heb je tips, suggesties of zelfs klachten? We horen ze graag tijdens de lunch. De lunch is natuurlijk gratis (nouja, included in je membership fee). We hebben plek voor een man of 35, en er zijn op dit moment 11 inschrijvingen. We hopen veel van jullie op de 17e te begroeten, en als je het leuk vind, kan ik je daarna nog even ons nieuwe kantoor laten zien. Inschrijven kan hier: https://www.ripe.net/participate/member-support/member-lunches <https://www.ripe.net/participate/member-support/member-lunches> Groet, Nathalie Künneke-Trenaman IPv6 Program Manager RIPE NCC

1 0

Call for presentations RIPE 74
by Benno Overeinder 24 Jan '17

24 Jan '17

Dear colleagues, Please find the CFP for RIPE 74 below or at https://ripe74.ripe.net/submit-topic/cfp/. The deadline for submissions is *12 March 2017*. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings. Kind regards, Benno Overeinder RIPE PC Chair https://ripe74.ripe.net/programme/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 74 will take place from 8-12 May 2017 in Budapest, Hungary. 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 74. See the full descriptions of the different presentation formats, https://ripe74.ripe.net/submit-topic/presentation-formats/. Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 12 March 2017. Proposals submitted after this date will be considered depending on the remaining available space in the programme. The PC is looking for presentations covering 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) Submissions 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 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 - Lightning talks: 10 minutes total for both presentation and any discussion The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe74.ripe.net/submit-topic/submission-form/. - Lightning talks should also be submitted using the meeting submission system (https://ripe74.ripe.net/submit-topic/submission-form/) and can be submitted any time up to and including the meeting week. Allocation of lightning talks will start a few days before the meeting, and will continue throughout the meeting. During the meeting, they may be announced on the day before the talk or even on the same day as the talk. - Lightning talks should also be submitted using the meeting submission system (https://ripe74.ripe.net/submit-topic/submission-form/) 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. - Due to potential technical issues, presenters/panellists should be physically present at the RIPE Meeting. If you have any questions or requests concerning content submissions, please email pc [at] ripe [dot] net. -- Benno J. Overeinder NLnet Labs http://www.nlnetlabs.nl/

1 0

Nog 2 weken! (en 1 dag)
by Nathalie Trenaman 05 Jan '17

05 Jan '17

Beste NLNOGers, Allereerst de beste wensen allemaal. Zoals Job in November al aankondigde, is er ook dit jaar weer een traditionele en altijd gezellige NLNOG Nieuwjaarsborrel. We hebben al 99 (!) aanmeldingen! Word jij de 100e borrelaar? Nog even: Details: -------- Tijd: vanaf 19:00 Datum: 20 januari 2017 Plaats: Stairway to Heaven, Mariaplaats 11/12 in Utrecht (vlakbij Utrecht CS) http://www.stairway.nl/ <http://www.stairway.nl/> De nieuwjaarsborrel word dit jaar mede mogelijk gemaakt door PowerDNS, NTT Communications, Cybersprint en SIDN. Aanmelden: ---------- Hoe meer zielen, hoe meer vreugd, dus neem ook eens een collega mee die nog nooit van NLNOG heeft gehoord ;-) Vergeet je niet even aan te melden: http://nlnog.com/nieuwjaarsborrel2017/ <http://nlnog.com/nieuwjaarsborrel2017/> Tot de 20e! Job, Niels, Sander, Thomas en Nathalie

1 0

FW: Forwarding issues related to MACs starting with a 4 or a 6 (Was: [c-nsp] Wierd MPLS/VPLS issue)
by Job Snijders 05 Dec '16

05 Dec '16

Alloah, TL;DR: Cisco Nexus 92160 switches kunnen packets met bepaalde specifieke payloads niet forwarden. Er komt geen software fix, de ASIC is niet goed gedesigned. Stel je hebt twee routers aan elkaar geknoopt via een VLAN over zo'n Nexus 9000 switch, en je doet VPLS tussen deze routers, dan kan het zijn dat packets waarbij de payload een ethernet frame binnen die VPLS instance is, waarbij het destination MAC begint met een 4 of een 6, gedropped worden. Als je precies weet wat voor payloads je stuurt over deze switches dan kun je er wel omheen werken (in een enterprise omgeving bijvoorbeeld), maar als je als service provider VLANs van A naar B verkoopt dan weet je natuurlijk niet wat de klant over het circuit gaat sturen, en dan kan dit flink bijten. Met vriendelijke groeten, Job ----- Forwarded message from Job Snijders <job(a)instituut.net> ----- Date: Fri, 2 Dec 2016 15:32:13 +0100 From: Job Snijders <job(a)instituut.net> To: nanog(a)nanog.org Subject: Forwarding issues related to MACs starting with a 4 or a 6 (Was: [c-nsp] Wierd MPLS/VPLS issue) Hi all, Ever since the IEEE started allocating OUIs (MAC address ranges) in a randomly distributed fashion rather then sequentially, the operator community has suffered enormously. Time after time issues pop up related to MAC addresses that start with a 4 or a 6. I believe IEEE changed their strategy to attempt to purposefully higher the chance of collisions with MAC squatters, to encourage people to register and pay the fee. The forwarded email at the bottom is yet another example of a widely deployed, but fundamentally broken ASIC. The switch can't forward VPLS frames which contain a payload where the inner packet is destined to a MAC starting with a 4 or a 6. This is with the switch operating in pure layer-2 mode, it doesn't know what MPLS or VPLS even are. The switch is dropping packets on the floor, based on their _payload_. Try selling such circuits to customers "discounted layer-2 service, some flows might not be forwarded". Had IEEE continued the sequential OUI allocations, it probably would've taken many years before we ever reached MACs starting with a 4 or a 6, but instead, in 2012 the first linecards started rolling out of factories with MACs burned in which start with a 4 or a 6, and this took some vendors by surpise. There have been quite some issues, both in hardware and software: Brocade produced a 24x10GE linecard to the market in 2013/2014, with limited FIB scale, meant for a BGP-free MPLS core, but the card can't keep flows together on LACP bundles if the inner packets in a pseudowire were destined for a 4 or 6 MAC. The result: out of order delivery, hurting performance. Cisco ASR 9k's had a bug where if a payload started with a 6, it assumed it would be an IPv6 packet, compare the calculated packet-length with the packet-length in the packet and obviously fail because an ethernet packet is not an IPv6 packet. The result: packets dropped on the floor. (Fixed in 4.3(0.32)I) The Nexus 9000 issue described at the top of this mail. Brocade IronWare had an issue related to packet reordering for flows inside pseudowires, fixed in 2013/2014. There are probably many more examples out there in the wild, slowly driving operators insane. At this moment, some issues related to MACs starting with a 4 or a 6 can be mitigated if you enable Pseudowire Control-Word (RFC 4385) _AND_ Flow-Aware Transport (RFC 6391). You need both to mitigate certain issues in multi-vendor networks (for instance if you have Cisco edge + Juniper core). But what to do when the ASIC won't forward the payload? As ISP you often don't control the payload. Unfortunatly, I don't think we've seen the end of this. The linecards bought in 2012 will trickle down to the grey/second-hand market about now, often without accompanying support contracts. In a world with increased complexity in our interconnectedness, and lack of visibility into the underlaying infrastructure (think remote peering, cloud connectivity, resellers reselling layer-2) it will hurt when some flows inexplicably fail to arrive. Dear IEEE, please pause assigning MAC addresses that start with a 4 or a 6 for the next 6 years. Or at least, next time you change the policy, consult the operational community. This 4/6 MAC issue was well documented in BCP128 back in 2007. The control-word drafts mentioned that there would be dragons related to 4 and 6 back in 2004. Dear Vendors, take this issue more serious. Realise that for operators these issues are _extremely_ hard to debug, this is an expensive time sink. Some of these issues are only visible under very specific, rare circumstances, much like chasing phantoms. So take every vague report of "mysterious" packetloss, or packet reordering at face value and immediately dispatch smart people to delve into whether your software or hardware makes wrong assumptions based on encountering a 4 or a 6 somewhere in the frame. And you, my fellow operators, please continue to publicly document these issues and possible workarounds. Kind regards, Job resources: c-nsp thread "Wierd MPLS/VPLS issue": https://puck.nether.net/pipermail/cisco-nsp/2016-December/thread.html https://www.nanog.org/meetings/nanog57/presentations/Tuesday/tues.general.S… BCP128: https://tools.ietf.org/html/bcp128 ----- Forwarded message from Simon Lockhart <simon(a)slimey.org> ----- Date: Fri, 2 Dec 2016 11:44:21 +0000 From: Simon Lockhart <simon(a)slimey.org> To: cisco-nsp(a)puck.nether.net Subject: Re: [c-nsp] Wierd MPLS/VPLS issue On Wed Nov 23, 2016 at 12:01:20PM +0000, Simon Lockhart wrote: > On Fri Nov 04, 2016 at 03:40:05PM +0000, Simon Lockhart wrote: > > To me, everything *looks* right, it's just that some VPLS traffic traversing > > the new link gets lost. > > For those who are interested... > > Well, I finally got to the bottom of this, and have pushed it to Cisco TAC > for a fix... Cisco TAC finally accepted the issue. Bug CSCvc33783 has been logged. Nexus BU has investigated. Response is... "[...] unfortunately this is an ASIC limitation on the Nexus 9000 switches and is therefore not fixable." If you want a Layer 2 switch that will forward all valid Ethernet frames, I'd suggest avoiding the Nexus 9000 range... Simon _______________________________________________ cisco-nsp mailing list cisco-nsp(a)puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ----- End forwarded message ----- ----- End forwarded message -----

3 2

FW: Forwarding issues related to MACs starting with a 4 or a 6 (Was: [c-nsp] Wierd MPLS/VPLS issue)
by Job Snijders 02 Dec '16

02 Dec '16

Hoera, het bleek toch geen ASIC probleem te zijn, initiele diagnose was verkeerd. Dat scheelt toch maar weer :-) ----- Forwarded message from "Sukumar Subburayan (sukumars)" <sukumars(a)cisco.com> ----- Date: Fri, 2 Dec 2016 21:23:24 +0000 From: "Sukumar Subburayan (sukumars)" <sukumars(a)cisco.com> To: Job Snijders <job(a)instituut.net>, Leo Bicknell <bicknell(a)ufp.org>, Nick Hilliard <nick(a)foobar.org>, "nanog(a)nanog.org" <nanog(a)nanog.org> Subject: Re: Forwarding issues related to MACs starting with a 4 or a 6 (Was: [c-nsp] Wierd MPLS/VPLS issue) All, I just want to come back on behalf of Cisco on this. We just investigated this issue and the issue is not an ASIC bug, but a flag set wrong by SW. We will reach out to the original customer through TAC who posted this in NSP to resolve this issue. sukumar

1 0

NLNOG New Years Drink 2017
by Job Snijders 21 Nov '16

21 Nov '16

Ohai NLNOG community! [ English TL;DR: Friday January 20th, 2017 we'll congregate in Utrecht to celebrate the new year! Please register at the below URL. ] Het is weer bijna zover! De immer legendarische NLNOG Nieuwjaarsborrel komt eraan. Een prima traditie om met vrienden en collega's het nieuwe jaar in te luiden met een biertje en een bittergarnituur. Details: -------- Tijd: vanaf 19:00 Datum: 20 januari 2017 Plaats: Stairway to Heaven, Mariaplaats 11/12 in Utrecht (vlakbij Utrecht CS) http://www.stairway.nl/ De nieuwjaarsborrel word dit jaar mede mogelijk gemaakt door PowerDNS en NTT Communications! Aanmelden: ---------- Hoe meer zielen, hoe meer vreugd, dus neem ook eens een collega mee die nog nooit van NLNOG heeft gehoord ;-) Vergeet je niet even aan te melden: http://nlnog.com/nieuwjaarsborrel2017/ Alvast hele fijne dagen en we hopen jullie allemaal te zien op 20 januari. Namens het bestuur, Job

1 0