From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 9E985A0C41; Tue, 30 Nov 2021 16:21:20 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 825D241177; Tue, 30 Nov 2021 16:21:16 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A33D241142; Tue, 30 Nov 2021 16:21:14 +0100 (CET) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mails.dpdk.org (Postfix) with ESMTP id AFFFC41140 for ; Tue, 30 Nov 2021 16:21:13 +0100 (CET) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id F11205C006A; Tue, 30 Nov 2021 10:21:11 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Tue, 30 Nov 2021 10:21:11 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:subject:date:message-id:mime-version :content-transfer-encoding:content-type; s=fm2; bh=ZAkZAnB+/Gf/X gIZKa8PlcaR1xqHQmWAe/jztu2tD54=; b=MfeWT3CLvnW6iLh7kZpP/fWWcjCVU 4tlqPo6IPZVdYG1JNlX/jq+AkH1z3PLBIZG0RRQWgxaRcZOQ+B3LpIk4Ziuniu1y Ac7UtHrY5sd4JL6+l7tVY72aM2hb4YP2Tmes4OALBV51MeXBzSILWxSfUFy3Zl8h zQd2u8ccZrq+E+730Jf4DY63jt+1f4earzXxLE7vYLPoIxzcLLnB/K0sFzM2MK2I hwSyWkTy9NZ/t7xtTyCCPbNqQz+T9/uEZ7FHLcbJ2Ss2KoF7Kqv9YC4r/14CEPRf /0rE7XQmQZKO81qqb8k3/2wG8zxGsStxW+IhlTshEL/kzYWyuCncHe+og== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=ZAkZAn B+/Gf/XgIZKa8PlcaR1xqHQmWAe/jztu2tD54=; b=Keu2nHr2MBMkO1NWe/kW87 EPCVaqoDHqpZ5p9N92EISEorfg5mK0VAnmbWjtaFQUkzbLzaloKdpH6apUQGnemf BWFpspEF5apgwG47Tu0FOK/6Qc8leyXuxf45l/v4xdqw5SkeS9fs6SyPAMK1SIIm UV1/iDE0m8IJwDJMT3CdBYHlhdnXHow2DljRLdVmTW5la1IGgEvhYoDDOhJHFTt1 CpEdcxyLNUuKtMPn9QvzI9/WCI5JulOOYuATFcCcxY2fN86BvIHe/A20qh0fqg4z jRQKAzw6azRhAoxv3g7AnDgLpcx66e/ybRXOJxksSNGMnqkdjpWEdrCeGfo3rIgg == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddriedugdejiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhephffvufffkfgggfgtsehtqhertddttd ejnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehmohhn jhgrlhhonhdrnhgvtheqnecuggftrfgrthhtvghrnhepgffhtdffhffhhfdvveeiiedvud egkeetffegfeetteeitdfghfduieekudeuhfeunecuffhomhgrihhnpehfohhsuggvmhdr ohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe hthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Tue, 30 Nov 2021 10:21:11 -0500 (EST) From: Thomas Monjalon To: announce@dpdk.org Subject: FOSDEM 2022 Networking Devroom CFP Date: Tue, 30 Nov 2021 16:21:09 +0100 Message-ID: <14652304.tv2OnDr8pf@thomas> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-BeenThere: announce@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list X-BeenThere: dev@dpdk.org List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org The FOSDEM Networking team is excited to announce that the call for proposa= ls is now open for the Networking devroom at [FOSDEM 2022]. =46OSDEM is a free event for engineers to meet, share ideas and collaborate. Please note that, due to Covid-19, FOSDEM will be held virtually again next= year on the 5th and 6th of February, 2022. All presentations will be pre-recorded with live chat during each presentation and live Q&A after each presentatio= n. [FOSDEM 2022] https://fosdem.org/2022/ Important Dates =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Sunday 12th December Submission deadline Friday 24th December Announcement of selected talks Friday 28th January Recorded Presentation and slide upload deadline 5 & 6th February Conference dates (online) About the devroom =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D The FOSDEM Networking devroom hosts a diversity of talks covering Open Source networking projects and technologies. The scope of the Networking devroom is broad and targets those software developers engaged in network design, monitoring, management and software development with Open Source tools. We typically host a variety of talks on Networking topics including: - Network monitoring (inventory, discovery & telemetry), - Network management (enterprise, carrier-grade, cloud, IoT) - Networking protocols (the full alphabet soup) - Security (IPS, IDS, protocols) - Authentication - Development tools (libraries, SDKs, plugins) - Network stacks Suggested Topics: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D If it moves network packets, monitors, or interacts with, or supervises entities that moves network packets, it is likely a topic the devroom is interested in. A very /non-exhaustive/ list of the projects and topics we would love to see on the schedule are: Monitoring Nagios, Icinga2, Naemon, NTop, SNAS, Graphana, Prometheus,= collectd Frameworks DPDK, eBPF, XDP, FD.io, PANDA Switching Snabb, OpenvSwitch, Tungsten Fabric, Lagopus, FastClick Stacks Linux, *BSD, F-Stack Controllers Istio, Envoy, Network Service Mesh, OpenDayLight, Calico, = Contiv Edge Akraino, Openness Routing FRRouting, BIRD, Go-BGP Management ONAP, Ganglia, NetSNMP, PNDA.io Security Suricata, Snort Tooling VSPerf, TRex, Moongen, Scapy, Warp17 Talks should be aimed at a technical audience, but should not assume that attendees are already familiar with your project or how it solves a given problem. Talk proposals may cover very specific solutions to a problem, or may be a higher level project overview for lesser known projects. Code of Conduct =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D [FOSDEM Code of Conduct]: We'd like to remind all speakers and attendees that all of the presentat= ions and discussions in our devroom are held under the guidelines set in the = CoC and we expect attendees, speakers, and volunteers to follow the CoC at a= ll times. If you submit a proposal and it is accepted, you will be required to con= firm that you accept the FOSDEM CoC. If you have any questions about the CoC = or wish to have one of the devroom organizers review your presentation slid= es or any other content for CoC compliance, please email us and we will do our= best to assist you. [FOSDEM Code of Conduct] https://fosdem.org/2022/practical/conduct/ Proposals: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Proposals should be made through the [FOSDEM Pentabarf submission tool]. You do not need to create a new Pentabarf account if you already have one from a past year. Please select the "Network" as the *track* and ensure you include the following information when submitting a proposal: Section Field Notes ------------------------------------------------------------------------= =2D-------------------------------- Person Name(s) Your first, last and public names. Person Abstract A short bio. Person Photo Please provide a photo. Event Event Title *This is the title of your talk* - please be desc= riptive to encourage attendance. Event Abstract Short abstract of one or two paragraphs. Event Duration Please indicate the length of your talk; 15 min, = 30 min or 45 min If your talk is accepted, the deadline to upload your slides and a pre-recorded version of your talk is Friday 28th January. FOSDEM will be held on the weekend of February 5th & 6th, 2022. Please also join the devroom=E2=80=99s mailing list, which is the official communication channel for the devroom: [network-devroom@lists.fosdem.org] (subscription page) [FOSDEM Pentabarf submission tool] https://penta.fosdem.org/submission/FOSDEM22 [network-devroom@lists.fosdem.org] https://lists.fosdem.org/listinfo/network-devroom Team: =3D=3D=3D=3D=3D Ray Kinsella Stephan Schmidt Thomas Monjalon Emma Foley Alexander Biehl Charles Eckel