[swinog] Call for presentations and RIPE 79
Dear colleagues, Please find the CFP for RIPE 79 below or at: https://ripe79.ripe.net/submit-topic/cfp/. The deadline for submissions is *16 August 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, Franziska Lichtblau RIPE PC Chair https://ripe79.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 79 will take place from 14-18 October in Rotterdam, 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 79. See the full descriptions of the different presentation formats: https://ripe79.ripe.net/submit-topic/presentation-forma ts/ Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than *16 August 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 p...@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://ripe79.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://ripe79.ripe.net/submit-topic/ - Lightning talks should also be submitted using the meeting submission system (https://ripe79.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 d
[swinog] Call for presentations RIPE 76
Dear all, Please find the CFP for RIPE 76 below or at: https://ripe76.ripe.net/submit-topic/cfp/. The deadline for submissions is *11 March 2018*. 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, Franziska Lichtblau RIPE PC Member https://ripe76.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 76 will take place from 14-18 May in Marseille, France. 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 76. See the full descriptions of the different presentation formats, https://ripe76.ripe.net/submit-topic/presentation-formats/. Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than *11 March 2018*. 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) 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 p...@ripe.net. Also note that, on an individual basis, participants can apply for a RIPE Fellowship to develop their professional or academic career. For more information, please visit: https://www.ripe.net/participate/ripe/ripe-fellowship 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://ripe76.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 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 total for both presentation and any discussion The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe76.ripe.net/submit-topic/ - Lightning talks should also be submitted using the meeting submission system (https://ripe76.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. If you have any questions or requests concerning content submissions, please email p...@ripe.net. -- 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 B
Re: [swinog] Research project and survey: Network filtering and IP spoofing
On Wed, Mar 01, 2017 at 12:50:49PM +0100, Jeroen Massar wrote: > On 2017-03-01 11:59, Franziska Lichtblau wrote: > [..] > >> Oh, and indeed, Switzerland is a bad place for BCP38, most networks > >> allow spoofing on both IPv4 and IPv6. > > > > Which is "kinda good" for me cause only answers from people who are > > implementing > > all of that won't help us much understanding whats going on ;) > > That is not "kinda good" as it means that spoofing can happen easily and > those kind of attacks are much harder to trace than ones that do proper > full TCP (or heck UDP). You got me wrong there. I didn't mean to say it's good that the possibility for spoofing is out there. What I meant to convey was, that if I only speak to operators or regions where a ''perfect'' level of filtering is applied I will not get meaningful insights about why it is not done everywhere and how we can improve on that. That's one of the biggest challenges - to actually talk to the people who are not doing as we all would want them to. > But with this whole Mirai thing and hundreds of thousands of hosts being > compromised of end-sites or Wordpress/Joomla/etc on servers with proper > upstream connectivity, it really does not matter, as spoofing is not > even really needed to properly DDoS any network, unless we are talking > about distributed or properly anycasted networks. That is completely true. But that's a completely different problem (which I used to work on very superficially). One that I'd actually like to see fixed, but I'm not sure what a research perspective (which is the one I can offer) can help there. I'm totally open to suggestions. > Eyeball networks though are both the source of many problems and when > miscreants figure out they can take down an eyeball network (which > cannot be protected with tricks like anycast and throwing more resources > at it, as pipe full == pipe full... *not a hint* ;) ) and ransom those > networks, lots of fun will happen. There are things you can not not think once you've thought about them once ;) I agree - there's lots of potential fun out there > The fun part is then also that those networks will just not work, they > will also get overloaded call centers which is amazing from a money > perspective thus it will do a lot of damage. > > But maybe then those eyeball networks finally will start taking action > in cleaning up their userbase, thus IMHO, it can't happen early enough > as then we finally will have a proper Internet where that nonsense gets > taken care of instead of just ignored... The problem is always, that people need incentives - there's a good amount of people that you can get with the global idea of a well working community... but sadly not all of them. That's one of the reasons why we ask what are the incentives of people who try to keep their network clean and now we can lower the bars for those who are not yet there. Greets, Franziska -- 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 signature.asc Description: PGP signature ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] Research project and survey: Network filtering and IP spoofing
On Wed, Mar 01, 2017 at 11:22:44AM +0100, Jeroen Massar wrote: > On 2017-03-01 09:58, Franziska Lichtblau wrote: > > 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/ > > You are missing the option for: > > "hardware does not support it at line rate" > > Which is the most important excuse by the larger networks to not enable > BCP38/SAVE[1]/MANRS[2]. Good point! I hope people suffering from that will tell us that with the open option, but you're right we should have considered that. > Most smaller shops, where the traffic conditions fit inside the hardware > budget, just do not care enough unfortunately... That was my feeling. > Oh, and indeed, Switzerland is a bad place for BCP38, most networks > allow spoofing on both IPv4 and IPv6. Which is "kinda good" for me cause only answers from people who are implementing all of that won't help us much understanding whats going on ;) Thank you! Franziska -- 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 signature.asc Description: PGP signature ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
