<?xml version='1.0' encoding='utf-8' ?>
<!-- Made with love by pretalx v2026.1.2. -->
<schedule>
    <generator name="pretalx" version="2026.1.2" />
    <version>1.7</version>
    <conference>
        <title>DENOG18</title>
        <acronym>denog18</acronym>
        <start>2026-11-15</start>
        <end>2026-11-17</end>
        <days>3</days>
        <timeslot_duration>00:05</timeslot_duration>
        <base_url>https://cfp.denog.de</base_url>
        
        <time_zone_name>Europe/Berlin</time_zone_name>
        
        
    </conference>
    <day index='1' date='2026-11-15' start='2026-11-15T04:00:00+01:00' end='2026-11-16T03:59:00+01:00'>
        <room name='Workshop Room #1#' guid='1b2bc746-8e1f-5881-898f-7ebd54d5b0c8'>
            <event guid='2ecbea73-f6e3-53f9-ab63-8d3e6c0c0d33' id='7' code='M9H8P7'>
                <room>Workshop Room #1#</room>
                <title>BGP for networks who peer</title>
                <subtitle></subtitle>
                <type>Workshop</type>
                <date>2026-11-15T11:00:00+01:00</date>
                <start>11:00</start>
                <duration>06:00</duration>
                <abstract>Workshop about the basics of BGP. Topics include:
* Prefixes and Autonomous Systems
* Why you also need an IGP (like OSPF, IS-IS)
* iBGP: BGP within your network
* eBGP: Talking to your neighbours
* Multihoming and Peering
* BGP Best Path Selection

Bonus-Topics, if time permits:
* BGP Communities
* BGP Security

Lab experiments will be done using FRRouting, so participants do need a laptop. No special software is needed, but make sure your web-browser can access a HTTPS page on ports 7002-7099.</abstract>
                <slug>denog18-7-bgp-for-networks-who-peer</slug>
                <track></track>
                
                <persons>
                    <person id='6'>Wolfgang Tremmel</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>true</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/M9H8P7/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/M9H8P7/feedback/</feedback_url>
            </event>
            
        </room>
        <room name='Workshop Room  #2#' guid='08b2fe90-b8a1-5330-9d9b-4fc1fc7477e3'>
            <event guid='b16a4e02-f0ab-537e-894b-b85af434df98' id='11' code='TEXXSQ'>
                <room>Workshop Room  #2#</room>
                <title>BGP Workshop 5.0</title>
                <subtitle></subtitle>
                <type>Workshop</type>
                <date>2026-11-15T11:00:00+01:00</date>
                <start>11:00</start>
                <duration>06:00</duration>
                <abstract>Want to perform the bgp handshake in real life based on a realistic topology? We got you covered ... in this workshop for intermediates we will dive into some network basics of bgp driven networks and also explore route filtering best practices (mainly for the DfZ = default free zone).

After some theory every attendee will receive one network node to configure. The fellow participants will be your peers. You will depend on the peers to reach your goals.

Teams work together in small groups. One group jointly manages an AS consisting of 3 routers and a customer downlink router. Troubleshooting takes place across groups in order to verify the corresponding availability within the lab topology.

Warning: You will have to socialise with the peers around you!

Topics Covered:
- Introduction into Internet/Routing Hierarchy
- Routing/Announcement Basics/Strategy
- Route Filtering
- Lab Introduction

Pre-requisites:
- Network Fundamentals, user level UNIX and maybe some system administration,
- Some use of network design preferably TCP/IP-based is also helpful.
- Dynamic routing Fundamentals (BGP, ISIS/OSPF is a plus)
- Participants must have technical hands on experience of routers.

Some experience with EOS or a comparable CLI will be helpful.</abstract>
                <slug>denog18-11-bgp-workshop-5-0</slug>
                <track></track>
                
                <persons>
                    <person id='11'>Vincentz Petzholtz</person><person id='12'>Peter Sievers</person><person id='13'>Sebastian Graf</person><person id='101'>Benedikt Heuser</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>true</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/TEXXSQ/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/TEXXSQ/feedback/</feedback_url>
            </event>
            
        </room>
        <room name='Workshop Room #3#' guid='caecb304-fcb6-57a5-a120-61ca0b7569be'>
            <event guid='26797346-056b-5d79-b4b8-82e57951f52c' id='10' code='ASK3LK'>
                <room>Workshop Room #3#</room>
                <title>poor man - great wifi</title>
                <subtitle></subtitle>
                <type>Workshop</type>
                <date>2026-11-15T11:00:00+01:00</date>
                <start>11:00</start>
                <duration>06:00</duration>
                <abstract>How hard can it be to NOT use wires? Sometimes pretty hard! But it doesn&apos;t need to be!

In this workshop you will learn what needs to be done to have a great wireless network. 
And how you can achieve that without getting bankrupt.</abstract>
                <slug>denog18-10-poor-man-great-wifi</slug>
                <track></track>
                
                <persons>
                    <person id='10'>Ulf Weikert</person>
                </persons>
                <language>en</language>
                <description>For the better half of a decade I have been doing professional work around wifi. 
WLAN on a campus or office complex, logistic warehouses, hospitals etc. have been my bread and butter for more than 5 years. 
With a change in employment my responsibilities shifted, but the passion never died. And for the last couple of years I helped with wifi deployments on smaller gigs like Nordlicht Demoparty, medium festivals like Stemweder Open Air and bigger events like Chaos Communication Congress or WHY2025. 

In this workshop I will give an overview and introduction of what is possible with today&apos;s free (and maybe open source) tools for getting great reliable wifi at home. 

My goal for the full day workshop is for you to; 

- being able to differentiate between good wifi and bad wifi
- being able to articulate your requirements for your own wifi environment
- being able to better put the big players in the market into context
- being able to successfully implement small projects (e.g. wifi at your or your friends home)
- being able to better work as an intermediary for wifi consultants in case your project got bigger

The main focus will be on practical applications. With a short sidequest on the theoretical side. 

While all of this is applicable in a broader context, we will NOT dive deep into every single nuance of wifi tuning. The tradeoff in this workshop will be to invest less of hard cash for a bit more of personal work hours.</description>
                <recording>
                    <license></license>
                    <optout>true</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/ASK3LK/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/ASK3LK/feedback/</feedback_url>
            </event>
            
        </room>
        <room name='Workshop Room #4#' guid='5c97f066-2f4e-5707-8ae6-6802ba352437'>
            <event guid='c962949c-8f4e-58aa-9168-fb3e3c8f7020' id='75' code='CEXYQV'>
                <room>Workshop Room #4#</room>
                <title>OpenPGP Key Management Hopefully Done Right</title>
                <subtitle></subtitle>
                <type>Workshop</type>
                <date>2026-11-15T11:00:00+01:00</date>
                <start>11:00</start>
                <duration>05:00</duration>
                <abstract>This workshop gives an overview about modern management of OpenPGP Keys. Online documentation suggests that you have an offline key and subkeys, the latter preferably on a hardware device. But there is hardly one place where there are hands-on instructions to create those. This workshop intends to have participants aquire that experience.</abstract>
                <slug>denog18-75-openpgp-key-management-hopefully-done-right</slug>
                <track></track>
                
                <persons>
                    <person id='72'>Marc Haber</person>
                </persons>
                <language>en</language>
                <description>This workshop will not give more than a &quot;you know that already&quot; appraoch to public key cryptography. It will begin with OpenPGP basics. The speaker is a Debian Developer, so his main application of OpenPGP is signing things, but of course encryption will be handled as well. The practical exercises will be done on Linux.

The participants will get an overview about what are best practises regarding OpenPGP keys:
- an offline (certification only) primary key that will never see the internet and
- subkeys (signature, encryption, authentication) that will be created on the offline system and then transfered to a OpenPGP Smart Card (such as a Yubikey).
- how to build and use an offline, immutable Linux system (based on Debian Live on a Raspberry Pi 4)
- Introduction to OpenPGP Smart Cards
The workshop will also suggest workarounds for the numerous gotchas the speaker experienced on his own journey to OpenPGP best practises.

Af the end of the talk, participants will have a primary key with subkeys and will have had the experience of exchanging keys, signatures and encrypted messages via a pad. It is suggested to throw away all key material after the workshop and to start over again in a quiet place with lots of concentration about doing things right.</description>
                <recording>
                    <license></license>
                    <optout>true</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/CEXYQV/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/CEXYQV/feedback/</feedback_url>
            </event>
            
        </room>
        <room name='Workshop Room #5#' guid='455681bd-663a-5ad9-8644-dd2ce023aa0c'>
            <event guid='76a555c0-fdc8-55fa-b599-e2df5afbb831' id='81' code='PJYNNC'>
                <room>Workshop Room #5#</room>
                <title>WDM Basics</title>
                <subtitle></subtitle>
                <type>Workshop</type>
                <date>2026-11-15T10:30:00+01:00</date>
                <start>10:30</start>
                <duration>02:00</duration>
                <abstract>Modern optics incorporate WDM technology out of the box, 100G-LR4, 100G-CWDM4 and other variants are common to everyone. But what does that mean and how does CWDM and DWDM work, if not already in a box.</abstract>
                <slug>denog18-81-wdm-basics</slug>
                <track></track>
                
                <persons>
                    <person id='38'>Nicola &apos;nicoduck&apos; von Thadden</person>
                </persons>
                <language>en</language>
                <description>I&apos;ll give an overview about different WDM types, channels and hardware. I&apos;ll also bring some devices to show, but I currently do not think it will be a hand-on session on some switches (that could change, if there is a benefit, which I currently do not see).</description>
                <recording>
                    <license></license>
                    <optout>true</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/PJYNNC/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/PJYNNC/feedback/</feedback_url>
            </event>
            <event guid='eee193c1-abf4-5ac8-b173-f35131e4b7ce' id='60' code='KGB9PT'>
                <room>Workshop Room #5#</room>
                <title>From Netbox to Network - A Hands-On ISP Automation Workshop for Beginners</title>
                <subtitle></subtitle>
                <type>Workshop</type>
                <date>2026-11-15T13:30:00+01:00</date>
                <start>13:30</start>
                <duration>03:30</duration>
                <abstract>How can network infrastructure be described centrally, versioned consistently, and deployed automatically?

In this hands-on introductory workshop, participants build and automate a small service provider network using NetBox, Git, Ansible, and a virtual lab environment.

Working in small teams, they use **NetBox** as the Source of Truth for devices, interfaces, IP addresses, and routing information. The structured data is then transformed into network configurations using Jinja2 templates and deployed through an automated workflow.

The workshop focuses on the practical interaction between network data, templates, version control, and automation. Participants will learn about network data modeling in NetBox, create and modify existing data and templates, execute the deployment process, and validate the resulting configurations.

The workshop is explicitly designed not only for participants who already have experience with NetBox or network automation, but also for curious network engineers who want to gain their first practical experience in a guided and approachable environment. It provides an opportunity to explore the concepts hands-on, understand how the individual components interact, and experience a complete automation workflow without having to build the underlying lab platform themselves.

After this workshop, participants should be able to explain the role of a Source of Truth within a network automation workflow, model and maintain basic network data in NetBox, understand how Git, Jinja2, and Ansible work together.

Most importantly, they will leave with a practical understanding of how Source-of-Truth-driven automation can provide a foundation for more reproducible, consistent, and scalable network operations in their own environments.

This workshop is not a comprehensive NetBox, Ansible, Jinja2 or Python training, nor does it present a production-ready automation platform. Instead, it offers a guided introduction to the core principles of Source-of-Truth-driven network automation and demonstrates how the individual components work together in a simplified end-to-end workflow.

#### Topics Covered:
- Introduction to Network Source of Truth
- Netbox Data Model
- Possible Deployment Pipelines
- Jinja2 configuration templating

####  Prerequisits:
- No previous experience with NetBox or network automation is required.
- No extensive programming experience is required.
- Basic knowledge of IP networking and routing is recommended.

The lab environment and all required tools are provided.
Participents are expected to bring 
- Their own laptop with a working Browser and ssh client</abstract>
                <slug>denog18-60-from-netbox-to-network-a-hands-on-isp-automation-workshop-for-beginners</slug>
                <track></track>
                
                <persons>
                    <person id='60'>Michael Fischer</person><person id='62'>Johannes St&#246;rmer</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>true</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/KGB9PT/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/KGB9PT/feedback/</feedback_url>
            </event>
            
        </room>
        <room name='Workshop Room #6#' guid='86e4d8e2-2460-5e91-891b-d95e9a868167'>
            <event guid='290f66fd-23d0-54a7-a23b-1fe5a9fd1633' id='91' code='YYFF9Y'>
                <room>Workshop Room #6#</room>
                <title>Build It. Test It. Fix It. &#8211; Datacenter-Verkabelung inklusive Messung und Fehlersuche</title>
                <subtitle></subtitle>
                <type>Workshop</type>
                <date>2026-11-15T11:00:00+01:00</date>
                <start>11:00</start>
                <duration>05:00</duration>
                <abstract>Dieser praxisorientierte Workshop vermittelt den Aufbau, die Installation und die Qualifizierung moderner passiver Netzwerkinfrastrukturen in einer realit&#228;tsnahen Datacenter-Umgebung.
Die Teilnehmer planen, installieren und pr&#252;fen eigenst&#228;ndig eine strukturierte Verkabelung. Vom mechanischen Aufbau &#252;ber das Spleissen und Patchen bis hin zur professionellen Abnahmemessung werden alle wesentlichen Arbeitsschritte praxisnah durchgef&#252;hrt.
Ziel des Workshops ist es, den Teilnehmern nicht nur theoretisches Wissen zu vermitteln, sondern ihnen die M&#246;glichkeit zu geben, typische Aufgaben aus dem Rechenzentrums-Umfeld selbstst&#228;ndig durchzuf&#252;hren sowie moderne Mess- und Pr&#252;ftechnologien in realen Anwendungsszenarien kennenzulernen.</abstract>
                <slug>denog18-91-build-it-test-it-fix-it-datacenter-verkabelung-inklusive-messung-und-fehlersuche</slug>
                <track></track>
                
                <persons>
                    <person id='84'>Marc R&#252;hl</person><person id='109'>Juergen Rummelsberger</person><person id='110'>Robin Bartelsen</person>
                </persons>
                <language>en</language>
                <description>Workshop-Konzept
Im Mittelpunkt des Workshops steht der eigenst&#228;ndige Aufbau eines passiven Netzwerks in einer realit&#228;tsnahen Datacenter-Umgebung. Die Teilnehmer &#252;bernehmen typische Aufgaben aus den Bereichen Spleissen, Verkabelung und Installation. Nach dem erfolgreichen Aufbau werden s&#228;mtliche Verbindungen professionell gepr&#252;ft, analysiert und dokumentiert.
Dabei f&#252;hren die Teilnehmer typische Abnahme-, Qualifizierungs- und Fehlersuchma&#223;nahmen durch, wie sie im t&#228;glichen Betrieb moderner Rechenzentren und Unternehmensnetzwerke erforderlich sind.
Gemeinsam mit ConnectCom und EXFO stellen wir die erforderliche Infrastruktur, moderne Messtechnik sowie das Expertenwissen f&#252;r einen erfolgreichen Infrastrukturaufbau bereit. Die Umsetzung erfolgt anhand eines vorgegebenen Verkabelungs- und Dokumentationskonzepts.
 
Die praktischen Aufgaben umfassen unter anderem:
&#8226;	Spleissen von Glasfaserverbindungen in Patchfeldern
&#8226;	Anschlie&#223;en von Netzwerkkabeln
&#8226;	Montage von Patchfeldern und Infrastrukturkomponenten
&#8226;	Patchen von Glasfaser- und Kupferverbindungen
&#8226;	Aufbau einer strukturierten passiven Verkabelung
&#8226;	Inspektion und Bewertung von Steckverbindungen
&#8226;	D&#228;mpfungsmessungen der installierten Strecken
&#8226;	Durchf&#252;hrung von IOLM-Messungen zur Streckenanalyse und Fehlerlokalisierung
&#8226;	Systematische Fehlersuche und Fehlerbehebung
&#8226;	Dokumentation der aufgebauten Infrastruktur und der Messergebnisse
 
Mehrwert f&#252;r die Teilnehmer
&#8226;	Praxisnahe Hands-on-Erfahrung statt reiner Theorie
&#8226;	Eigenst&#228;ndiger Aufbau einer passiven Netzwerkinfrastruktur
&#8226;	Kennenlernen aktueller Glasfaser- und Messtechnik
&#8226;	Durchf&#252;hrung realer Aufbau-, Pr&#252;f- und Abnahmeverfahren
&#8226;	Systematische Fehlersuche, Analyse und Fehlerbehebung
&#8226;	Erfahrungs- und Wissensaustausch mit Experten
&#8226;	Verst&#228;ndnis f&#252;r Planung, Installation, Qualifizierung und Dokumentation moderner Netzwerk- und Datacenter-Infrastrukturen</description>
                <recording>
                    <license></license>
                    <optout>true</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/YYFF9Y/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/YYFF9Y/feedback/</feedback_url>
            </event>
            
        </room>
        <room name='Workshop Room #7#' guid='be7700ca-5341-5a90-83c7-c80d0696850d'>
            <event guid='f9dec52b-31d7-5f99-9306-56d4289a4441' id='64' code='JXFHES'>
                <room>Workshop Room #7#</room>
                <title>Mastering gRPC for Network Management, Monitoring and Automation</title>
                <subtitle></subtitle>
                <type>Workshop</type>
                <date>2026-11-15T11:00:00+01:00</date>
                <start>11:00</start>
                <duration>06:00</duration>
                <abstract>In this workshop session, we will explore how the high-performance protocol gRPC can be used to interact with a modern network OS: monitoring, configuration, operations, and even beyond!

## Content

The workshop will touch on what gRPC is, and which gRPC services are available for managing networks. We will try out the full suite of gNxI protocols using open source tools, namely:
- **gNMI**: used for network management and monitoring
- **gNOI**: for operational tasks, like image upgrades and reboots
- **gNSI**: security-related tasks, e.g. gRPC access policy and certificate rotation
- **gRIBI**: manipulating the RIB programmatically, injecting routes on-demand

## Prerequisites

We will be providing participants with a VM pre-loaded with all necessary tools and network topology.

**No previous programming or gRPC experience required for this beginner-friendly workshop!**</abstract>
                <slug>denog18-64-mastering-grpc-for-network-management-monitoring-and-automation</slug>
                <track></track>
                <logo>/media/denog18/submissions/JXFHES/image_vJ73ojc.webp</logo>
                <persons>
                    <person id='65'>Gordon Gid&#243;falvy</person><person id='105'>Florian Schwarz</person><person id='106'>Mathis Bramkamp</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>true</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/JXFHES/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/JXFHES/feedback/</feedback_url>
            </event>
            
        </room>
        <room name='Workshop Room #8#' guid='2ce984b1-ae8f-5e13-a5b6-cfe859690eeb'>
            <event guid='1590d1a0-5703-5cdc-9d2b-5086292e3013' id='80' code='MWJXKM'>
                <room>Workshop Room #8#</room>
                <title>Behind the Label: How MPLS Network Transport Really Works</title>
                <subtitle></subtitle>
                <type>Workshop</type>
                <date>2026-11-15T11:00:00+01:00</date>
                <start>11:00</start>
                <duration>06:00</duration>
                <abstract>MPLS once was the center of attention in many network talks, workshops and training. Still today it is a predominant technology in use in many networks.

However, those who joined the network community in the past years or almost a decade now from enterprise and datacenter angles, have found very little opportunity to dive into the topic of MPLS. Many perceive the communities still working with expert level MPLS topics hard to engage with.

This workshop tries to go back in time and provide a guided journey through the development of MPLS and how it evolved over the years. It wants to cover original ideas, what became of them and how various protocols over time solved problems of their time and ultimately resulted in the most modern use of MPLS and related technologies for those who were not around when all this was heavily discussed in every other training course.

This workshop is addressed to absolute beginners and those who heard little about MPLS and have a few working assumptions but no solid background.
It does not aim to go to expert level, rather give a solid structure and overview so that context exists for the concepts in play.

The talk will mainly focus on the history, theories and how protocol implemented them as well as some hands-on components of label exchange and packet forwarding in groups while applying various protocols.

Participants should be beginner level or completely new to MPLS.
Basic knowledge of networking concepts is recommended.</abstract>
                <slug>denog18-80-behind-the-label-how-mpls-network-transport-really-works</slug>
                <track></track>
                
                <persons>
                    <person id='76'>Christian Giese</person><person id='77'>Elmar Kirchner</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>true</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/MWJXKM/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/MWJXKM/feedback/</feedback_url>
            </event>
            
        </room>
        <room name='Workshop Room #9#' guid='4cea81f5-47d4-5f9b-9cba-525a5b09901b'>
            <event guid='d094a653-d5be-580e-8d45-b426e3e2e5cb' id='108' code='QWSNGK'>
                <room>Workshop Room #9#</room>
                <title>advanced SSH</title>
                <subtitle></subtitle>
                <type>Workshop</type>
                <date>2026-11-15T10:30:00+01:00</date>
                <start>10:30</start>
                <duration>04:00</duration>
                <abstract>You already know how to generate keys and authenticate securely. But SSH can do so much more. In this advanced workshop, we&apos;ll explore the powerful features that transform SSH from a simple login tool into an essential part of your workflow&#8212;port forwarding, proxy jumping, SSH certificates, control channel reuse, and crafting bulletproof ssh_config files. Walk out with the techniques that turn SSH from a necessity into a superpower.</abstract>
                <slug>denog18-108-advanced-ssh</slug>
                <track></track>
                
                <persons>
                    <person id='98'>Felix Sch&#252;ren</person>
                </persons>
                <language>en</language>
                <description>Many SSH users hit the same frustrations: managing dozens of hosts with repetitive parameters, struggling with multi-hop networks, or wasting time on repeated connection overhead. This workshop directly addresses these pain points.

We&apos;ll start by diagnosing the problems in a typical ssh_config, then systematically solve them through five core techniques:

Port Forwarding &#8212; Local and remote variants for securely accessing databases on private networks and exposing local services to remote machines. You&apos;ll understand when to use each and why it matters for security.

Proxy Jumping &#8212; Build practical multi-hop scenarios (2-3 hops) and see how ProxyJump eliminates the bastion-host dance.

SSH Certificates &#8212; A game-changer for teams managing multiple servers. We&apos;ll cover generation, deployment, and why they&apos;re superior to key-per-host approaches.

Control Channel Reuse &#8212; Understand connection multiplexing and how ControlMaster/ControlPath cuts SSH connection overhead dramatically.

ssh_config Mastery &#8212; Build a comprehensive config from scratch using Host patterns, wildcard matching, conditional includes, and automation that grows with your infrastructure.

By the end, you&apos;ll have working examples you can adapt immediately.</description>
                <recording>
                    <license></license>
                    <optout>true</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/QWSNGK/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/QWSNGK/feedback/</feedback_url>
            </event>
            <event guid='c365b57f-1ce8-5113-a858-c010c4fda1ed' id='70' code='TGXGP9'>
                <room>Workshop Room #9#</room>
                <title>From Networks to Products: Breaking the Consulting Mold (2026 edition)</title>
                <subtitle></subtitle>
                <type>Workshop</type>
                <date>2026-11-15T15:00:00+01:00</date>
                <start>15:00</start>
                <duration>02:00</duration>
                <abstract>The network engineering industry is rich with technical talent but remains surprisingly underrepresented in the world of product-driven startups. In 2025 Thomas Weible (CTO and Co-Founder, FLEXOPTIX) and Moritz Frenzel (CEO and Co-Founder, EdgeOps) started to share their entrepreneurial journeys, each shaped by a deep technical background and a commitment to building products instead of pursuing the traditional consulting route.

One year later at EdgeOps (Y 2) and FLEXOPTIX (Y 18) a lot of things did happen in their product companies. The session offers an exciting journey surging awesome highlights and annoying pitfalls we&apos;ve experienced in the last year timeframe. If you weren&apos;t convinced in the first edition of this workshop in 2025, maybe now?

This workshop aims to inspire and equip engineers, founders, and future entrepreneurs with the confidence and perspective to transition from services to products, still shifting from billing hours to building something that lasts, while also fostering connections between existing and aspiring founders. 

On more thing, Bernd Sontheimer (formerly sdt.net, now TNG) committed to share his experiences of the merge and acquisition process in 2023.</abstract>
                <slug>denog18-70-from-networks-to-products-breaking-the-consulting-mold-2026-edition</slug>
                <track></track>
                
                <persons>
                    <person id='68'>Thomas Weible</person><person id='102'>Moritz Frenzel</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>true</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/TGXGP9/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/TGXGP9/feedback/</feedback_url>
            </event>
            
        </room>
        <room name='Workshop Room #10#' guid='7974ed97-9401-5791-beaf-a41accab2fdb'>
            <event guid='e74b15d5-d3d5-5069-8892-7cc9694364aa' id='115' code='EA73XB'>
                <room>Workshop Room #10#</room>
                <title>Death to Perfectionism: Get unstuck!</title>
                <subtitle></subtitle>
                <type>Workshop</type>
                <date>2026-11-15T11:00:00+01:00</date>
                <start>11:00</start>
                <duration>02:00</duration>
                <abstract>_&#8220;I&#8217;m a perfectionist&#8221;_ is a popular humble brag answer to the classic interview question _&#8220;What&#8217;s your biggest weakness?&#8221;_ &#8211; a weakness that conveniently sounds like a strength. While perfectionism lures us in with its promise to help, most of us know that it can have some very real downsides.

In this **hands-on workshop**, we&#8217;ll unpack what we actually mean when we talk about &#8220;perfectionism&#8221;, where it might be helpful &#8211; and where it starts getting in our way. We&#8217;ll explore how perfectionism can show up as procrastination, overthinking, endless tweaking, fear of getting things wrong, or simply never feeling like something is good enough. Most importantly, we&#8217;ll look at practical tools and exercises to help break those patterns and make it easier to take action, even when things aren&#8217;t perfect.

The aim isn&#8217;t to lower your standards &#8211; it&#8217;s to become more intentional about when high standards are useful, and when they&#8217;re holding you back.</abstract>
                <slug>denog18-115-death-to-perfectionism-get-unstuck</slug>
                <track></track>
                
                <persons>
                    <person id='107'>Susi Bauer</person>
                </persons>
                <language>en</language>
                <description>## What You&#8217;ll Learn:

- **Spotting Perfectionism in Disguise**: Recognise the less obvious ways perfectionism can show up &#8211; from procrastination and over-preparing to endlessly tweaking work that was already good enough.
- **Understanding the Cost:** Explore how perfectionism can affect productivity, confidence, creativity, decision-making, and our willingness to take risks or try something new.
- **Getting Out of the Overthinking Loop**: Learn practical techniques for making decisions, getting started, and taking action before you feel completely ready.
- **Redefining &#8220;Good Enough&#8221;**: Learn how to set more useful definitions of done, rather than relying on an impossible feeling of &#8220;perfect&#8221;.
- **Taking Imperfect Action**: Leave with a small, concrete action you can put into practice straight away &#8211; because sometimes the best way to beat perfectionism is to start.

## Why Attend?
This workshop is for anyone who has ever spent far too long tweaking something that was probably fine already, put something off because they didn&#8217;t know how to do it &#8220;right&#8221;, or found themselves stuck trying to make the perfect decision.
You&#8217;ll leave with a better understanding of your own perfectionist patterns and a toolbox of practical strategies for getting unstuck. Because the goal isn&#8217;t to stop caring about doing good work &#8211; it&#8217;s to make sure that the pursuit of perfect doesn&#8217;t stop you from doing the work at all.</description>
                <recording>
                    <license></license>
                    <optout>true</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/EA73XB/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/EA73XB/feedback/</feedback_url>
            </event>
            
        </room>
        
    </day>
    <day index='2' date='2026-11-16' start='2026-11-16T04:00:00+01:00' end='2026-11-17T03:59:00+01:00'>
        <room name='Saal A' guid='267308ca-4507-59fc-b41e-852c1f9b0e91'>
            <event guid='f7348701-689c-5d9d-9088-914c529fbb4c' id='109' code='AVHF39'>
                <room>Saal A</room>
                <title>Newcomer Sessions</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-16T09:30:00+01:00</date>
                <start>09:30</start>
                <duration>00:20</duration>
                <abstract>Welcome to your first DENOG conference. In this session, we will guide you through the community, the event and everything DENOG!</abstract>
                <slug>denog18-109-newcomer-sessions</slug>
                <track></track>
                
                <persons>
                    <person id='97'>Patrick Bu&#223;mann</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/AVHF39/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/AVHF39/feedback/</feedback_url>
            </event>
            <event guid='91bda3c1-9cb8-5751-b345-4858c7ce4349' id='104' code='UB3PVV'>
                <room>Saal A</room>
                <title>DENOG18 Opening</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-16T10:00:00+01:00</date>
                <start>10:00</start>
                <duration>00:30</duration>
                <abstract>Welcome to DENOG18!</abstract>
                <slug>denog18-104-denog18-opening</slug>
                <track></track>
                
                <persons>
                    <person id='97'>Patrick Bu&#223;mann</person>
                </persons>
                <language>en</language>
                <description>Welcome to DENOG18!</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/UB3PVV/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/UB3PVV/feedback/</feedback_url>
            </event>
            <event guid='9ce903d0-d8bc-5624-9ed1-c62f3a64a955' id='51' code='3BJJKY'>
                <room>Saal A</room>
                <title>Retrofitting API into a routing software</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-16T10:30:00+01:00</date>
                <start>10:30</start>
                <duration>00:30</duration>
                <abstract>Configuring a router via text CLI and configuration file editing is not very 2026. In BIRD, we are trying to catch the departing train and implement a CORECONF variant of an IETF-standardized YANG-based API. We&apos;ve created a prototype but getting things right is harder than it seems. This is a report on what has already gone wrong and what is expected to fail in the future.</abstract>
                <slug>denog18-51-retrofitting-api-into-a-routing-software</slug>
                <track></track>
                
                <persons>
                    <person id='46'>Maria Matejka</person>
                </persons>
                <language>en</language>
                <description>While a standardized API looks simple on surface, the reality is much more convoluted. There are three standards for communication, NETCONF, RESTCONF and emerging CORECONF, each of these with slightly different semantics. Lots of the YANG modules are not yet finalized and implementation specifics  are leaking into them from their authors. In the best case, we end up with the implementations slightly differing in what is implemented, and being mostly compatible for automated access. Yet, the actual future may be much more dire, with the users having to cater for three different protocols and vastly diverse implementation status of the standardized API. All of that is spiced up by performance challenges.

With BIRD, we are kinda late to the party. Everybody has some API working. That brings a disadvantage on the market, but it also allows us to study the previous attempts, see possible problems and implement our API to our standards, including high performance and stability. We can also see emerging compatibility issues and there are some attempts to develop proxies and convertors to bridge the gaps.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/3BJJKY/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/3BJJKY/feedback/</feedback_url>
            </event>
            <event guid='a07810fc-09c0-5ef5-b1cf-cbc3f69cdf34' id='45' code='VCQLXW'>
                <room>Saal A</room>
                <title>EVPN - One Control Plane to Rule Them All</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-16T11:05:00+01:00</date>
                <start>11:05</start>
                <duration>00:30</duration>
                <abstract>Modern service provider networks are evolving rapidly: transports like VXLAN, MPLS, Segment Routing and SRv6 are being used while many legacy control plane protocols are still in operation. This often results in unnecessary complexity, multiple signalling mechanisms and operational overhead.

In this talk, I&#8217;ll explore how BGP EVPN has evolved into a transport-agnostic control plane capable of unifying services across MPLS, VXLAN, SR, and SRv6. The goal is simple: move away from fragmented legacy protocols and toward a single, scalable control plane for L2 and L3 services.

We&#8217;ll look at recent EVPN innovations and discuss how service providers can benefit from simplifying their architectures while preparing their networks for future transport technologies.</abstract>
                <slug>denog18-45-evpn-one-control-plane-to-rule-them-all</slug>
                <track></track>
                
                <persons>
                    <person id='42'>Patrick Prangl</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/VCQLXW/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/VCQLXW/feedback/</feedback_url>
            </event>
            <event guid='c1a19df1-f28f-5575-902c-c7d183846978' id='93' code='YTBLUH'>
                <room>Saal A</room>
                <title>EVPN for humans</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-16T11:40:00+01:00</date>
                <start>11:40</start>
                <duration>00:30</duration>
                <abstract>EVPN is everywhere, be it datacenter, service provider or campus - and every vendor says you need it. But EVPN rightfully has a reputation problem. It is rarely truly understood, even by vendors themselves, and often treated as a black box. The RFCs read like tax law, and the quality of vendor documentation doesn&#8217;t help either.
This talk aims to be nothing less than a gentle introduction and a deep dive into EVPN at the same time. 
We&#8216;ll explore the abstract concepts and frequently misused terminology in order to build an intuitive mental model. 
We will also look into the often overlooked origins of EVPN, which explain many of its design decisions and behaviours.

Finally, we&#8217;ll take a look at tricky mechanisms like Anycast Gateways and Multihoming, so your next EVPN debugging session doesn&#8217;t become another unplanned nightshift.</abstract>
                <slug>denog18-93-evpn-for-humans</slug>
                <track></track>
                
                <persons>
                    <person id='85'>Robin Christ</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/YTBLUH/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/YTBLUH/feedback/</feedback_url>
            </event>
            <event guid='8f04f108-2e87-5094-8fab-aee37e5aa57b' id='66' code='FUCBPB'>
                <room>Saal A</room>
                <title>Beyond Bandwidth: Why it doesn&apos;t solve user experience in Wi-Fi, WAN, and LAN Environments</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-16T14:05:00+01:00</date>
                <start>14:05</start>
                <duration>00:30</duration>
                <abstract>This talk examines latency as an end-to-end property of enterprise networks, not just a wireless problem. While wireless networks often receive the most attention, the actual user experience is shaped by the interaction between radio conditions, roaming, access layer design, switching behavior, QoS handling, and overall WAN &amp; LAN architecture.
Using Wi-Fi 7 as a current reference point, the session shows why bandwidth alone is not a meaningful success metric and why latency, jitter, and responsiveness must be evaluated across the full network path. The goal is to provide network operators and engineers with a practical lens for understanding where user experience breaks down &#8212; and how to design networks that behave well under real operational conditions.</abstract>
                <slug>denog18-66-beyond-bandwidth-why-it-doesn-t-solve-user-experience-in-wi-fi-wan-and-lan-environments</slug>
                <track></track>
                
                <persons>
                    <person id='66'>Falk Bachmann</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/FUCBPB/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/FUCBPB/feedback/</feedback_url>
            </event>
            <event guid='e233064e-3a79-5697-8041-03267c0ef282' id='68' code='ZCXTKW'>
                <room>Saal A</room>
                <title>QoE-riosities of 2026 - What we saw on the Internet this year</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-16T14:40:00+01:00</date>
                <start>14:40</start>
                <duration>00:30</duration>
                <abstract>While everyone talked about the DENIC outage this year, we monitored the critical stuff higher up the stack. The football world championship was a challenge for streamers and network operators. So, how did they actually perform under pressure? Beyond live events, we put different access technologies to the test in our lab to analyze how factors like latency, jitter, and bandwidth caps directly impact Quality of Experience (QoE) on the web and beyond. Let&apos;s have a data-driven look at the Unexpected of 2026.</abstract>
                <slug>denog18-68-qoe-riosities-of-2026-what-we-saw-on-the-internet-this-year</slug>
                <track></track>
                
                <persons>
                    <person id='67'>Alexander Dethof</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/ZCXTKW/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/ZCXTKW/feedback/</feedback_url>
            </event>
            <event guid='f3c2ec95-4a3a-57c5-87e2-2894714a6c41' id='85' code='PRRFUN'>
                <room>Saal A</room>
                <title>IPv6 routing loops -- A call to fix router configurations.</title>
                <subtitle></subtitle>
                <type>Lightning Talk</type>
                <date>2026-11-16T15:25:00+01:00</date>
                <start>15:25</start>
                <duration>00:10</duration>
                <abstract>Routing loops and the amplification of looping packets are known problems on the IPv6 Internet.
In a recent measurement study, we found that both problems are still present, potentially harming Internet stability.
Although routing loops are often easy to fix, they receive limited attention from the network operator community.
Since 2025, we aim to raise awareness of routing loops and amplification at network operator events.
In 2026, we started to weekly measure the deployment of routing loops and amplifications on the IPv6 Internet.
In this talk, we present how community outreach has helped significantly reduce the impact of these network misconfigurations. We further provide an update on the current state of these issues on the IPv6 Internet with a particular focus on the RIPE and DE region.
We hope these misconfigurations will eventually disappear and encourage the DENOG community to spread the word, check their networks, and help eliminate routing loops from the IPv6 Internet.
Until then, we will continue measuring, reporting, and raising awareness.
To assist in resolving these problems, we have made our findings publicly available at https://ipv6-sra.realmv6.org/routingloops, allowing operators to check whether their networks are affected by routing loops.</abstract>
                <slug>denog18-85-ipv6-routing-loops-a-call-to-fix-router-configurations</slug>
                <track></track>
                
                <persons>
                    <person id='81'>Maynard Koch</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/PRRFUN/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/PRRFUN/feedback/</feedback_url>
            </event>
            <event guid='d5597601-9fbd-5bd9-9911-bcdb2140141f' id='94' code='E7UDUC'>
                <room>Saal A</room>
                <title>Teach Networking!?</title>
                <subtitle></subtitle>
                <type>Lightning Talk</type>
                <date>2026-11-16T15:35:00+01:00</date>
                <start>15:35</start>
                <duration>00:10</duration>
                <abstract>There are many ways for career starters to get into IT: apprenticeships, university degrees, dual study programs, or through self-study.
But how do they learn networking and IT infrastructure?

With this lightning talk, I&#8217;d like to inspire you to teach young people how networking works!

What are the most difficult topics to explain? What about practical experience?
I&apos;ve been teaching the basics of networking for several years now, and I&apos;d like to share my experience with you.</abstract>
                <slug>denog18-94-teach-networking</slug>
                <track></track>
                
                <persons>
                    <person id='22'>Vanessa Gaube</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/E7UDUC/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/E7UDUC/feedback/</feedback_url>
            </event>
            <event guid='a4851425-8572-5a1a-99f8-2ea109466818' id='99' code='V7Y3X9'>
                <room>Saal A</room>
                <title>IPv4-with-IPv6 Next-Hops: At least faster progress than Linux on the Desktop</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-16T16:45:00+01:00</date>
                <start>16:45</start>
                <duration>00:15</duration>
                <abstract>Routing IPv4 packets using IPv6 next-hops has been around for some time now. It offers great opportunities to reduce IPv4 address usage in the distribution and access layer, and enables providing IPv4 as a pure add-on, keeping a clean IPv6 address structure underneath.

Despite its benefits, major challenges for deploying IPv4-with-IPv6 next-hops in practice persist. While, e.g., BGP supports such routes using RFC8950, many other IGPs still lack support. Other major issues are &apos;the last mile&apos;, i.e., auto-configuring clients (or, for this use-case, more likely servers), and the impact of  IPv4-with-IPv6 next-hop usage on traceroutes.

In this talk, we will go over some current developments in these areas, which should make IPv4-with-IPv6 next-hops a viable option for practical deployments in the coming years. We will also expand further on possible deployment scenarios, where IPv4-with-IPv6 next-hops can remove further legacy Layer-2 infrastructure, e.g., LACP.</abstract>
                <slug>denog18-99-ipv4-with-ipv6-next-hops-at-least-faster-progress-than-linux-on-the-desktop</slug>
                <track></track>
                
                <persons>
                    <person id='90'>Tobias Fiebig</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/V7Y3X9/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/V7Y3X9/feedback/</feedback_url>
            </event>
            <event guid='fe935e26-4678-5f57-a183-c05f8cea52b3' id='89' code='SYTTEC'>
                <room>Saal A</room>
                <title>Killing ARP: running IPv4 as a service on an IPv6-only network</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-16T17:00:00+01:00</date>
                <start>17:00</start>
                <duration>00:15</duration>
                <abstract>What actually changes in your network when you stop treating IPv4 as infrastructure and start treating it as a service?

draft-vanmook-intarea-ipv6-resolved-gateway (presented at IETF 126, WG adoption call pending) defines a single sentinel gateway address, provisionally 192.0.0.11 (requested from the IANA Special-Purpose Registry, not yet assigned), handed out as the ordinary DHCPv4 default gateway. Updated hosts resolve their first hop from the IPv6 neighbour cache; unmodified hosts ARP for the sentinel once and the router answers. That&apos;s the whole mechanism. Everything downstream of it is the interesting part.

This talk is about what that does to a running network: no IPv4 subnets anywhere, no ARP, no FHRP, IPv4 address pools that go flat &#8212; any /32 works anywhere in the footprint, nothing stranded by subnet sizing. The core forwards v4-via-v6 (RFC 8950) with no IPv4 configured on any router interface.

On the implementation side: host implementations for Linux (userspace daemon and native systemd-networkd), FreeBSD, macOS and Windows, with prebuilt packages; a namespace conformance lab with a zero-ARP assertion; verified unmodified-host behaviour across seven operating systems; and vendor configuration examples for IOS XR, JunOS, SR OS, EOS and RouterOS. On the router side, three working deployment models: a single-gateway reference, an active/active anycast VRRP pair, and a BGP-orchestrated multi-gateway fabric &#8212; fungible gateways, host /32s injected from inventory, and the entire DHCPv4 path carried as IPv4 values over IPv6 next-hops, with no IPv4 management network at all.

Plus the failure modes, the ND health prerequisites, and what breaks when you get it wrong.

No tunnels. No translation. No flag day. Keep the shape, change what it means.</abstract>
                <slug>denog18-89-killing-arp-running-ipv4-as-a-service-on-an-ipv6-only-network</slug>
                <track></track>
                
                <persons>
                    <person id='83'>Remco van Mook</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/SYTTEC/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/SYTTEC/feedback/</feedback_url>
            </event>
            <event guid='d6b91b90-1ba8-57cd-bfb7-c4ebd9c956b8' id='106' code='EQ7KVJ'>
                <room>Saal A</room>
                <title>Day 1 Closing</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-16T17:40:00+01:00</date>
                <start>17:40</start>
                <duration>00:10</duration>
                <abstract>That&apos;s a wrap on Day1, time for the social!</abstract>
                <slug>denog18-106-day-1-closing</slug>
                <track></track>
                
                <persons>
                    <person id='5'>Tim Kleefass</person>
                </persons>
                <language>en</language>
                <description>That&apos;s a wrap on Day1, time for the social!</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/EQ7KVJ/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/EQ7KVJ/feedback/</feedback_url>
            </event>
            
        </room>
        <room name='Saal B' guid='47a2568d-ddfd-50c6-80a6-2cd2b6d94857'>
            <event guid='e3ac8023-a86e-57c0-8c0d-e602feb30b05' id='61' code='97DCW3'>
                <room>Saal B</room>
                <title>Geoinformation Systems &amp; Internet Infrastructure</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-16T10:30:00+01:00</date>
                <start>10:30</start>
                <duration>00:30</duration>
                <abstract>KML, KMZ, DXF - hat wahrscheinlich schon jede:r mal in der Hand gehabt, nach dem man redundante Leitungen bestellt hat. Aber was macht man eigentlich sinnvolles damit?

KML, KMZ, DXF - everyone knows or used those file formats, at least after asking the carrier where the redundant circuits are. But is there anything useful you can do with those files?</abstract>
                <slug>denog18-61-geoinformation-systems-internet-infrastructure</slug>
                <track></track>
                <logo>/media/denog18/submissions/97DCW3/image_jBkNhBm.webp</logo>
                <persons>
                    <person id='63'>Dominik Bay</person>
                </persons>
                <language>en</language>
                <description>Geoinformationsdaten sind eine der Grundlagen f&#252;r stabil funktionierende Infrastruktur. Egal ob Glasfasern im Boden, Glasfasern an Hochspannungsmasten oder Richtfunkstrecken. Wie funktioniert die Trassenplanung- und Instandhaltung, und welche Vorteile habe ich als Nutzer:in um meinen Netz zu verstehen und den Netzbetrieb zu optimieren?

Geo information data are the basis for reliable infrastructure. Not only for fiber in the ground, but even fiber on power lines or microwave links are planned this way. How does the planning of new fiber routes and their maintenance work, and which benefits do I get from geo data for my own network?</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/97DCW3/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/97DCW3/feedback/</feedback_url>
            </event>
            <event guid='0634345d-fc3c-55aa-ab3d-3c86489aa690' id='54' code='XPH3W7'>
                <room>Saal B</room>
                <title>IPv6 in firmware: Still booting in the wrong decade</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-16T11:05:00+01:00</date>
                <start>11:05</start>
                <duration>00:30</duration>
                <abstract>Every server depends on firmware to boot and most also rely on firmware for remote management. U-Boot, EDK2 (UEFI), OpenBMC, you name it. And they all share the same issue: IPv6 support ranges from half-baked to non-existent. Why is this still the case in 2026?

In this talk I&apos;ll go into two areas of server firmware that operatores rarely look at closely: the one that boots the server, and the one that allows out-of-band management via the Baseboard Management Controller (BMC).

On the boot side: Do PXE and HTTP boot actually work over IPv6? And what unexpected side effects do you might see?

On the management side: How does IPv6 support look on a BMC today, and what&apos;s still broken?

Nobody&apos;s going to fix what nobody complains about. Let&apos;s find out how broken this is and what we can do about it.</abstract>
                <slug>denog18-54-ipv6-in-firmware-still-booting-in-the-wrong-decade</slug>
                <track></track>
                
                <persons>
                    <person id='54'>sinuscosinustan</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/XPH3W7/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/XPH3W7/feedback/</feedback_url>
            </event>
            <event guid='b846a888-846c-56fa-bd3b-f935dac25fc8' id='86' code='8YL9JB'>
                <room>Saal B</room>
                <title>Wire-API: fleet-wide, vendor-neutral network automation</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-16T14:05:00+01:00</date>
                <start>14:05</start>
                <duration>00:30</duration>
                <abstract>Network operators share a vocabulary built on VRFs, EVPN-VXLAN, and BGP underlays. What doesn&apos;t travel is how it gets written down. Every vendor and orchestrator has its own dialect, and most automation tools still push device-specific config from an orchestrator down to all involved devices. Translation, not domain-specific problems, becomes a bottleneck.

We build _Wire-API_ with a different model in mind: Instead of targeting devices, operators declare the state they want and controllers work out which devices are affected and what config to push. In the case of an EVPN fabric for example: describe it with objects like `Network`, `RoutingDomain`, and `ExternalConnection`, and adding a network becomes one object rather than a coordinated change across every leaf and firewall that participates. The shift is in what gets declared: desired state instead of a device&apos;s running config. From there, drift correction and HA-aware maintenance stop being separate runbooks and become properties of the reconcile loop, and the same model extends to anything else on the network expressed as intent.

The core is Kubernetes. _Wire-API_ is a set of CRDs and controllers that reuse the contract that made Kubernetes work in &quot;compute&quot;&#8212;declared state, continuous reconciliation, honest status&#8212;and apply it to the network domain.

The presentation argues for the _Wire-API_ model and walks through a live EVPN-VXLAN example&#8212;one intent object, vendor-specific config on Cisco NX-OS and Nokia SR Linux&#8212;then covers design decisions and partial-failure handling. Wire-API already operates production fabrics across multiple availability zones; the model works today even as the framework continues to grow.

_Wire-API_ is Apache-2.0 and is being contributed to the NeoNephos Foundation (Linux Foundation Europe) as part of the ApeiroRA workstream under the EU IPCEI-CIS program.</abstract>
                <slug>denog18-86-wire-api-fleet-wide-vendor-neutral-network-automation</slug>
                <track></track>
                
                <persons>
                    <person id='82'>Enric Pujol</person><person id='99'>Sebastian Wagner</person>
                </persons>
                <language>en</language>
                <description>Here is the link to the GitHub resources:
https://github.com/ironcore-dev/network-operator
And the detailed description on the website:
https://ironcore.dev/network-operator/</description>
                <recording>
                    <license></license>
                    <optout>true</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/8YL9JB/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/8YL9JB/feedback/</feedback_url>
            </event>
            <event guid='b971519f-c421-58ae-8725-2bdb78b4afbd' id='50' code='KPYWEU'>
                <room>Saal B</room>
                <title>Modular Nokia SR OS automation from scratch</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-16T14:40:00+01:00</date>
                <start>14:40</start>
                <duration>00:30</duration>
                <abstract>Existing automation solutions are usually monolithic and require you to migrate all of your existing infrastructure at once to the automation. I wanted to introduce automation step by step and wanted to continue to use our existing sources of truth. So I have built a modular automation solution that allows us to build a completely separated automation module for everything we want to automate in our network.</abstract>
                <slug>denog18-50-modular-nokia-sr-os-automation-from-scratch</slug>
                <track></track>
                
                <persons>
                    <person id='45'>Jennifer Graul</person>
                </persons>
                <language>en</language>
                <description>Existing automation solutions are usually monolithic and require you to migrate all of your existing infrastructure at once to the automation. But I wanted to continue using our existing sources of truth and wanted to introduce automation in our network step by step and not in one big step.

Additionally, there is the security perspective: do you really want to grant an automation solution that you don&apos;t fully understand internally unrestricted access to all of your routers?

The solution: modular network automation from scratch: write a module for any aspect you want to automate in your network. Want to automate your peerings with Peering-Manager? Write a module for it. Want to automate your base router interfaces with NetBox? Write a module for it.

The modules itself are isolated from each other in the configuration by using one config group for each module (basically a separate config tree for each module). This by design eliminates the possibility of collisions between modules and makes consecutive deployments easier by fully replacing the config group on each run. It additionally allows you to minimize the permissions of an automation user to the absolute required minimum by only granting them access to the config group. Furthermore, the use of config groups allows you to override the automation on any given time in the main config tree or even exclude some parts of the main config tree from it.

Although this solution was developed for Nokia SR OS, it can in principle be extended to any platform that is transactional and supports something like config groups.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/KPYWEU/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/KPYWEU/feedback/</feedback_url>
            </event>
            <event guid='c750e19a-36dc-573a-93a5-1a04371693da' id='82' code='MRZYPH'>
                <room>Saal B</room>
                <title>You can&apos;t make everybody equally happy - Measuring Anycast with AI as the Third Member of a Two-Person Team</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-16T15:15:00+01:00</date>
                <start>15:15</start>
                <duration>00:30</duration>
                <abstract>Anycast is easy to explain and notoriously difficult to observe. Announce the same IP address from multiple locations, allow BGP to choose a path, and traffic should reach the &quot;nearest&quot; instance, although BGP&apos;s idea of nearest often has little to do with geography.

ProVision (formerly 6connect) operates an anycast DNS platform spanning six prefixes, 39 BGP nodes, 13 regions, and five continents. For years, we knew the platform worked because queries were answered. What we could not prove was how it worked: which users reached which nodes, how quickly packets arrived, and where traffic quietly disappeared.

This presentation tells the story of how we turned one of anycast&apos;s most frustrating behaviors-ICMP replies returning to the &quot;wrong&quot; node-into a measurement. That insight grew into an automated pipeline running 117,000 probes per second across 2.6 million targets, measuring latency, loss, jitter, routing behavior, path MTU failures, ECMP paths, and visibility at 845 Internet Exchanges.

It is also the story of how two network engineers who are not full-time developers built the system through intensive collaboration with AI coding models. AI supplied much of the implementation capacity; the humans supplied decades of network intuition, architectural direction, validation, and the authority to say when the code was confidently wrong.</abstract>
                <slug>denog18-82-you-can-t-make-everybody-equally-happy-measuring-anycast-with-ai-as-the-third-member-of-a-two-person-team</slug>
                <track></track>
                
                <persons>
                    <person id='78'>Jan Zorz</person>
                </persons>
                <language>en</language>
                <description>Anycast underpins critical Internet services, including DNS, content delivery networks, and DDoS mitigation platforms. The model appears simple: announce the same IP address from multiple locations and allow BGP to direct traffic toward the best available path, but the operational reality is far less transparent.

ProVision (formerly 6connect operates an anycast DNS platform built around six prefixes announced by 39 BGP nodes in 13 regions across five continents. The platform answered queries reliably, yet ordinary service monitoring could reveal only part of the story. It could tell us that a DNS request succeeded, but not always which node handled it, whether BGP selected the node we expected, how latency differed across the catchment, or where packets were being lost without causing a visible outage.

Measuring the network from inside the platform created a chicken-and-egg problem. Anycast is designed to make many distributed instances appear to be one destination, so the topology we wanted to study was the same topology the service was designed to conceal. We could not simply ask the Internet which node it would reach. We needed a way to make the network reveal its own routing decisions.

The breakthrough came from a behavior that initially appeared to undermine the measurements. We sent probes from the production anycast source addresses and observed that ICMP errors frequently returned to the &quot;wrong&quot; node rather than the node that originated the probe. That wrong node was the answer.

The node receiving the ICMP response was the node BGP had selected as the return path for the router generating it. By recording those responses across the network, we could begin mapping real anycast catchments from the perspective of the infrastructure itself. The apparent flaw became the core measurement primitive. From that insight, we built a fully automated daily measurement pipeline capable of:

Running 117,000 probes per second across 2.6 million targets Measuring round-trip time, packet loss, and jitter for 1.4 million addresses Detecting path MTU discovery black holes Performing ECMP-aware traceroutes Correlating active measurements with BGP monitoring Measuring platform visibility at 845 Internet Exchanges

Attendees will leave with a practical understanding of why anycast is so difficult to measure, how asymmetric ICMP routing can reveal real BGP catchments, and what it takes to turn that observation into a large-scale monitoring system. They will also see a grounded example of AI-assisted engineering in which coding models expanded the capacity of a very small team without replacing the network judgment required to build something trustworthy.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/MRZYPH/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/MRZYPH/feedback/</feedback_url>
            </event>
            <event guid='958af442-e7cc-578e-b103-03e7a28bd567' id='53' code='SUN8ER'>
                <room>Saal B</room>
                <title>How Deutsche Telekom built a Carrier-Grade virtual PoP in AWS</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-16T16:45:00+01:00</date>
                <start>16:45</start>
                <duration>00:30</duration>
                <abstract>Physical points of presence (PoPs) are expensive to deploy and often limit how quickly service providers can respond to customer demand in new regions. To address this challenge, Deutsche Telekom developed a virtual PoP architecture that extends carrier-grade MPLS L3VPN services into AWS.

This talk presents the technical architecture behind the solution, including AWS Direct Connect Gateway, Cisco 8000v virtual routers, MP-BGP, and VPNv4/VPNv6 integration. We explain the design decisions, operational considerations, and routing principles that enabled the realization of a cloud-based PoP.

Attendees will learn how cloud infrastructure can be integrated into a traditional service provider network while maintaining routing control, operational standards, and rapid service deployment.</abstract>
                <slug>denog18-53-how-deutsche-telekom-built-a-carrier-grade-virtual-pop-in-aws</slug>
                <track></track>
                
                <persons>
                    <person id='51'>Gabor Adam</person><person id='52'>Holger Th&#246;sink</person><person id='53'>Adam Orosz</person>
                </persons>
                <language>en</language>
                <description>Customer demand increasingly requires network services in regions where no physical Point of Presence exists. Building new PoPs is costly and time-consuming, making it difficult to respond to short-term requests.

In this session, we present how Deutsche Telekom designed a vPoP architecture running in AWS that extends our MPLS backbone into cloud regions while preserving carrier-grade routing and operational principles.

We will discuss the architecture, including AWS Direct Connect Gateway, Cisco 8000v virtual routers, MP-BGP (VPNv4/VPNv6), IPv4/IPv6 routing, management separation, and throughput considerations. Particular attention will be given to the design choices that enabled regional routing while avoiding AWS transit and maintaining full control over the routing domain.

The talk also covers the practical experience gained during the project, including proof of concept implementation, operational challenges, automation aspects, and lessons learned from integrating cloud infrastructure into a service provider environment.

The session is aimed at network operators, architects, and engineers interested in MPLS, BGP, cloud networking, and carrier-grade network design. Attendees will gain practical insights into extending traditional backbone services into hyperscaler environments.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/SUN8ER/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/SUN8ER/feedback/</feedback_url>
            </event>
            
        </room>
        
    </day>
    <day index='3' date='2026-11-17' start='2026-11-17T04:00:00+01:00' end='2026-11-18T03:59:00+01:00'>
        <room name='Saal A' guid='267308ca-4507-59fc-b41e-852c1f9b0e91'>
            <event guid='81f81d82-f486-5c72-913c-abfecfa607e9' id='69' code='J3QAZC'>
                <room>Saal A</room>
                <title>Democratizing layer 1 telemetry: Open Source Switch OS and VDM for predictive network maintenance</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-17T09:30:00+01:00</date>
                <start>09:30</start>
                <duration>00:30</duration>
                <abstract>As network architectures transition towards open, disaggregated hardware, Open Source Switch Operating Systems (like SONiC) have unlocked unprecedented access to hardware telemetry. Concurrently modern transceivers offer advanced Vendor Digital Monitoring (VDM) capabilities that go far beyond classic Digital Diagnostic Monitoring (DDM). However the industry still struggles to utilize this data for proactive operations.

This presentation demonstrates how to leverage open VDM interfaces within Open Source Switch OS architectures to establish a continuous, high-frequency telemetry pipeline. By analyzing realtime physical layer metrics - such as pre-FEC bit error rates, laser bias current shifts and optical signal degradation - we showcase how to move from reactive troubleshooting to predictive maintenance. Attendees will learn how open software paradigms enable operators to detect impending Layer 1 failures before packet loss occurs ensuring maximum network uptime without vendor lock-in.</abstract>
                <slug>denog18-69-democratizing-layer-1-telemetry-open-source-switch-os-and-vdm-for-predictive-network-maintenance</slug>
                <track></track>
                
                <persons>
                    <person id='68'>Thomas Weible</person><person id='96'>Dr. Gerhard Stein</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/J3QAZC/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/J3QAZC/feedback/</feedback_url>
            </event>
            <event guid='34a6b85f-49b7-5698-a2ad-16d24c780d12' id='72' code='E7HWCA'>
                <room>Saal A</room>
                <title>Enjoying BMP with Rotonda in 600 seconds</title>
                <subtitle></subtitle>
                <type>Lightning Talk</type>
                <date>2026-11-17T10:05:00+01:00</date>
                <start>10:05</start>
                <duration>00:10</duration>
                <abstract>With BMP (BGP Monitoring Protocol) readily available on all major routing
platforms, operators have the opportunity to get a view of their networks
that&apos;s more comprehensive than ever before.
Crucially, one needs to collect all this information and make sense of
it, ideally without having to invest too much time. In this lightning talk, we
present Rotonda, enabling operators to do just that: get started with BMP
effortlessly, while providing the scalability and flexibility to monitor any
network, any use case.

Rotonda is free and open source route collection and analysis software
developed by NLnet Labs. We&apos;ll introduce BMP, highlight and showcase the main
features of Rotonda, and hopefully spark interest to continue the conversation
afterwards.</abstract>
                <slug>denog18-72-enjoying-bmp-with-rotonda-in-600-seconds</slug>
                <track></track>
                
                <persons>
                    <person id='70'>Luuk Hendriks</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/E7HWCA/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/E7HWCA/feedback/</feedback_url>
            </event>
            <event guid='99be1705-2c70-5884-9eb1-6ce7e7114b45' id='67' code='JRR8WV'>
                <room>Saal A</room>
                <title>OpenRoaming Explained: What It Solves and Why Operators Should Care</title>
                <subtitle></subtitle>
                <type>Lightning Talk</type>
                <date>2026-11-17T10:15:00+01:00</date>
                <start>10:15</start>
                <duration>00:10</duration>
                <abstract>OpenRoaming promises seamless and secure Wi-Fi access, but what does it mean for real network operations? This short talk explains the technology, the federation model, and the practical benefits and limitations of OpenRoaming from an operator&#8217;s point of view. Using real-world examples, it shows where OpenRoaming fits, where it does not, and why it is becoming relevant for public, enterprise, and venue networks.</abstract>
                <slug>denog18-67-openroaming-explained-what-it-solves-and-why-operators-should-care</slug>
                <track></track>
                
                <persons>
                    <person id='66'>Falk Bachmann</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/JRR8WV/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/JRR8WV/feedback/</feedback_url>
            </event>
            <event guid='2206d1e0-f84d-5c45-9bcf-5e24faaf4551' id='97' code='KXMLXN'>
                <room>Saal A</room>
                <title>Route Filtering at Scale</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-17T10:40:00+01:00</date>
                <start>10:40</start>
                <duration>00:30</duration>
                <abstract>BGP routing security relies on many technologies, both old and new, such as IRR-based Route Filters and RPKI Technologies like Route Origin Authorizations (ROAs) or Autonomous System Provider Authorization (ASPA-s). While these technologies are well-known, they are still used together, and accurate route filter generation remains a challenging task with significant operational implications for large-scale router filter generation at major tier-1 ISPs.

We show that AS-Set documentation in RIR databases is still critical yet systematically overlooked. We evaluate the scope and patterns of these issues - including missing documentation, AS-Set explosive expansion, and cyclic dependencies - demonstrating that accurate AS-Set documentation remains a foundational requirement for operational filtering.

We present the toolchain and technologies like Route Query Specification (RQSpec) we use for route filter generation at scale, compensating for the complexity introduced by poor documentation.</abstract>
                <slug>denog18-97-route-filtering-at-scale</slug>
                <track></track>
                
                <persons>
                    <person id='88'>Fedor Vompe</person><person id='92'>Sebastian Becker</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/KXMLXN/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/KXMLXN/feedback/</feedback_url>
            </event>
            <event guid='bcdc5683-0b61-5c16-8649-bcb8b979e672' id='31' code='DRTW8K'>
                <room>Saal A</room>
                <title>AI&#8217;s impact on bandwidth and automation in optical networks</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-17T11:15:00+01:00</date>
                <start>11:15</start>
                <duration>00:30</duration>
                <abstract>Overview of AI&apos;s impact on the optical industry and why scale across will driving an insane bandwidth increase in optical networks.  
The presentation will also cover how we expect that AI agents will impact how service providers manage &amp; automate their networks in a near future.</abstract>
                <slug>denog18-31-ai-s-impact-on-bandwidth-and-automation-in-optical-networks</slug>
                <track></track>
                
                <persons>
                    <person id='35'>Kent Lidstrom</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/DRTW8K/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/DRTW8K/feedback/</feedback_url>
            </event>
            <event guid='d1750d4b-98d2-519d-8af5-94ec4842e363' id='83' code='BSEFX3'>
                <room>Saal A</room>
                <title>FSO essentials</title>
                <subtitle></subtitle>
                <type>Lightning Talk</type>
                <date>2026-11-17T11:45:00+01:00</date>
                <start>11:45</start>
                <duration>00:10</duration>
                <abstract>Free-Space Optical (FSO) communication is a wireless technology that uses laser beams to provide high-speed data transmission between two locations with a clear line of sight.
 This presentation introduces the evolution of FSO from large-scale experimental systems in the 1970s to modern commercial and mission-critical applications such as satellite, military, and drone communications.
 Advances in optical components, sensors, control technologies, and software have significantly improved system performance, reliability, and usability.
 Current FSO systems are compact, lightweight, support automatic tracking, and typically achieve data rates of 25 Gbps.</abstract>
                <slug>denog18-83-fso-essentials</slug>
                <track></track>
                <logo>/media/denog18/submissions/BSEFX3/image_tcbSOOC.webp</logo>
                <persons>
                    <person id='79'>Takaya Nakagawa</person>
                </persons>
                <language>en</language>
                <description>Contents
- What is FSO
- History of FSO 
- Current FSO Technology
- Progress in Enabling Technologies
- Key Features of Today&apos;s FSO System
- Things to Keep in Mind When Using Lasers</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/BSEFX3/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/BSEFX3/feedback/</feedback_url>
            </event>
            <event guid='2156a7bc-36f3-5447-9b83-1f8998416378' id='110' code='LEHAXX'>
                <room>Saal A</room>
                <title>IXP Update</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-17T13:00:00+01:00</date>
                <start>13:00</start>
                <duration>00:30</duration>
                <abstract>News from IXPs in Germany
As introduced 2021 we collect some parameters from all IXPs, which are active in Germany.
This talk aggregates the Updates for all the IXPs in a common format and will be presented in a neutral way.</abstract>
                <slug>denog18-110-ixp-update</slug>
                <track></track>
                
                <persons>
                    <person id='5'>Tim Kleefass</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/LEHAXX/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/LEHAXX/feedback/</feedback_url>
            </event>
            <event guid='a5c403a5-b258-5f96-9670-78360f3d5a5e' id='95' code='EMHXW7'>
                <room>Saal A</room>
                <title>Maybe it is time to consider layer 3 internet exchanges</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-17T13:35:00+01:00</date>
                <start>13:35</start>
                <duration>00:30</duration>
                <abstract>Internet exchanges have presented as shared layer 2 networks for thirty years. I will show the mechanisms that silently blackhole exchange traffic or forward it to the wrong port: missing or incorrect neighbour entries, and unknown unicast flooding. In each case BGP stays established to the route servers and nothing reports a fault.

A large exchange stated in writing that it gives no guarantee traffic sent to a peering LAN goes to, and only to, the port of the network it was meant for, and that it knows of no exchange that does. I do not know how many members expect that answer.

The rest of the industry has spent years dismantling large layer 2 domains in favour of routed ones. Perhaps it is time for internet exchanges to forward at layer 3, rather than running a layer 2 forwarding domain with a route server making routing decisions.

In many cases this needs no new hardware. The switches already used to build exchange fabrics forward at layer 2 and at layer 3 at line rate. Route scale is where careful consideration is needed.

The shape of a layer 3 internet exchange switch is already commonplace: each PNI switch a CDN or ISP operates is a routed exchange with several settlement-free peers and one customer on it.

Running at layer 3 gives participants complete isolation between ports, the same model that already applies to every other upstream connection that networks buy. RTBH works at the exchange rather than depending on a peer to honour it. Debugging becomes possible from the participant side, because traceroute shows the exchange hop.</abstract>
                <slug>denog18-95-maybe-it-is-time-to-consider-layer-3-internet-exchanges</slug>
                <track></track>
                
                <persons>
                    <person id='86'>James Rice</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/EMHXW7/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/EMHXW7/feedback/</feedback_url>
            </event>
            <event guid='d6452881-0a34-5a7a-9326-0df4740acfb3' id='98' code='XBCBZT'>
                <room>Saal A</room>
                <title>The New Botnet Era: Rethinking Your DDoS Strategy</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-17T14:10:00+01:00</date>
                <start>14:10</start>
                <duration>00:30</duration>
                <abstract>DDoS defense strategies must evolve because modern botnet campaigns combine high-volume, direct-path pressure with stealthier tailored attack components that attempt to overload and evade mitigation systems. 

In the past, most DDoS attacks were easier for ISPs to identify and block. The hardest cases were botnet-based Layer 7 attacks because they were more difficult to detect and mitigate. 

Successfully blocking DDoS attacks today requires more than the techniques that worked in the past. Over the past months, botnet size and firepower have increased dramatically. These botnets now drive some of the largest and most effective attacks, not only against individual applications but also against entire network infrastructures, cloud providers, and CDNs. 

At the end of 2025, we observed record-breaking attacks. This talk explains why we believe those attacks happened, why they continue, and what they reveal about the evolution of botnet-driven DDoS campaigns. 

Multi-terabit attacks have become much more common, but it is not just the volume of DDoS traffic that is taking down web sites and other targets around the world. The real problem is the tailored, targeted, and dynamic attack components that knock servers offline while remaining below the visibility threshold of many traditional defenses.  
Today&#8217;s large-scale, direct-path attacks increasingly include multiple attack vectors, blending volumetric, state-exhaustion and application-layer components. These botnet-based attacks are designed to overload mitigation capabilities and resources.  
  
This talk explains what enabled the expansion of botnets behind today&#8217;s attack campaigns and where these new bots are located. For network operators, this matters because these bots now require inbound, outbound, and cross-bound DDoS detection and mitigation.  
These insights are based on ATLAS, our worldwide DDoS monitoring system.  
Attendees will leave with a clearer understanding of why botnet-driven DDoS campaigns now demand mitigation strategies that account for visible volumetric pressure and lower-profile attack components at the same time.</abstract>
                <slug>denog18-98-the-new-botnet-era-rethinking-your-ddos-strategy</slug>
                <track></track>
                
                <persons>
                    <person id='89'>Stefan Meinders</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/XBCBZT/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/XBCBZT/feedback/</feedback_url>
            </event>
            <event guid='448f4283-d058-5adc-a078-b4d08058ef5b' id='9' code='U3Q97T'>
                <room>Saal A</room>
                <title>Network Automation for the Modern Age</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-17T14:45:00+01:00</date>
                <start>14:45</start>
                <duration>00:30</duration>
                <abstract>In the last two decades network automation has gone from a fringe concept reserved for global players to the industry standard at almost every system size. The tooling and concepts have evolved and grown, and an ecosystem has formed and normalized around a few core systems.

In this talk, we want to propose a natural next step in the evolution from manual work over templating to driving the system with sources of truth. As the technological and business complexity of networks grows, the data model becomes more and more of a focal point of how we look at the reality of our system. We need to understand our data and our models better than ever before, and make our decisions based on how we model the world, without being constrained by the limits of our pre-fabricated documentation systems.

We will speak about what it means for an automation to be driven by your actual data model and how you conceptualize the network, motivated by an actual software system. Over the course of the talk, we will not just talk about concepts, but anchor our ideas in concrete implementation.

Nonetheless, this is not a talk about a solution. It&#8217;s a talk about an idea and an approach, and, hopefully, the start of a conversation.</abstract>
                <slug>denog18-9-network-automation-for-the-modern-age</slug>
                <track></track>
                
                <persons>
                    <person id='8'>Veit Heller</person>
                </persons>
                <language>en</language>
                <description>The talk builds on our previous work and talks around network automation and data modeling. We want to make the case that &#8220;source of truth&#8221; is a useful step, but not the end state: the more interesting question is whether the model itself can become the driver of automation.

The talk will use alembic (https://github.com/cyberwitchery/alembic) as the concrete anchor. We plan to show how a model-first system can represent network concepts, derive operational artifacts, and fit alongside existing DCIM/IPAM/source-of-truth tools without being constrained by their object model.

Expected structure:
- short history: from manual work to templates to source-of-truth automation
- why we end up with our own data model most of the time and what that means
- concrete examples from alembic
- trade-offs, open questions, and caveats

The talk is intended for network engineers, automation engineers, and people maintaining source-of-truth or orchestration systems.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/U3Q97T/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/U3Q97T/feedback/</feedback_url>
            </event>
            <event guid='ac44ce46-301d-5b70-aa5d-a86669ea4457' id='105' code='XXSCSP'>
                <room>Saal A</room>
                <title>DENOG18 Closing</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-17T15:30:00+01:00</date>
                <start>15:30</start>
                <duration>00:30</duration>
                <abstract>It&apos;s a wrap!</abstract>
                <slug>denog18-105-denog18-closing</slug>
                <track></track>
                
                <persons>
                    <person id='97'>Patrick Bu&#223;mann</person>
                </persons>
                <language>en</language>
                <description>It&apos;s a wrap!</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/XXSCSP/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/XXSCSP/feedback/</feedback_url>
            </event>
            
        </room>
        <room name='Saal B' guid='47a2568d-ddfd-50c6-80a6-2cd2b6d94857'>
            <event guid='6f28fe45-be47-538b-a8a8-837903a8ba97' id='49' code='39VKX7'>
                <room>Saal B</room>
                <title>Carrier-Scale TWAMP Monitoring with DPDK and Commodity x86 Servers</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-17T09:30:00+01:00</date>
                <start>09:30</start>
                <duration>00:30</duration>
                <abstract>Modern telco operators increasingly require continuous active performance monitoring across thousands or even tens of thousands of access nodes. While TWAMP has become the de facto standard for active IP performance measurements, implementing it at carrier scale is far from trivial.

This presentation explains how a carrier-scale TWAMP monitoring platform can be built using commodity x86 servers together with DPDK-based userspace packet processing that completely bypasses the Linux networking stack.

The talk discusses the architectural decisions required to support massive numbers of concurrent TWAMP sessions, including packet processing, session scheduling, timer management, CPU affinity, NUMA awareness and resource optimization.

Real benchmark results and operational experience from large-scale deployments demonstrate the achievable scalability and identify the practical limitations of this approach.

Attendees will gain practical insight into designing highly scalable active monitoring systems without relying on proprietary hardware appliances.</abstract>
                <slug>denog18-49-carrier-scale-twamp-monitoring-with-dpdk-and-commodity-x86-servers</slug>
                <track></track>
                
                <persons>
                    <person id='44'>Mario Jurcevic</person>
                </persons>
                <language>en</language>
                <description>**Why carrier-scale TWAMP is difficult**

Most existing TWAMP implementations are designed for relatively small deployments. Scaling active measurements to tens of thousands of simultaneously monitored access nodes introduces significant challenges in packet processing, timing accuracy, scheduling and resource management.

**Why DPDK**
The presentation explains why bypassing the Linux kernel networking stack is essential for achieving deterministic latency and high packet processing rates. It discusses how DPDK enables direct NIC access, reduces interrupt overhead and provides predictable packet forwarding performance.

**System architecture**
Topics include:
- Userspace packet processing architecture 
- DPDK forwarding engine and application-to-engine communication 
- TWAMP session management 
- Timestamping offload and packet pacing 
- Multi-core scalability on commodity x86 hardware


**Performance**
Real benchmark results will be presented, including:
- maximum number of concurrent TWAMP sessions
- packets per second
- CPU utilisation
- memory consumption
- scaling across multiple CPU cores
- practical deployment limits

**Operational lessons learned**
The presentation concludes with practical experience gained from deploying large-scale active monitoring systems in carrier environments, including common pitfalls, optimisation techniques and recommendations for future deployments.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/39VKX7/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/39VKX7/feedback/</feedback_url>
            </event>
            <event guid='a7119132-dd36-5f67-bd4e-f91d88d37655' id='43' code='YUWRSZ'>
                <room>Saal B</room>
                <title>You Want EGP? You Get EGP! - DENOG Mad Scientist Edition</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-17T10:05:00+01:00</date>
                <start>10:05</start>
                <duration>00:30</duration>
                <abstract>We are all well aware of BGP as our protocol to run the Internet. As we sometimes notice (e.g. in the Talk by Wolfgang Tremmel at DENOG17) BGP still has ties to its predecessor EGP and can still claim it learned things from that protocol (Sometimes for nefarious reasons).

Follow me on a journey to find out what we need to do in order to still run the EGP Protocol in 2026. How far back in time do we need to go in order to legitimately put the E into the Origin of BGP updates?

Why? Because We do what we must because we can!</abstract>
                <slug>denog18-43-you-want-egp-you-get-egp-denog-mad-scientist-edition</slug>
                <track></track>
                
                <persons>
                    <person id='40'>Tobias Heister</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/YUWRSZ/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/YUWRSZ/feedback/</feedback_url>
            </event>
            <event guid='145688b0-a96b-533d-b781-a2c7bd4bb2f5' id='100' code='G37JXN'>
                <room>Saal B</room>
                <title>Quo Vadis IPv6 in Germany?</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-17T10:40:00+01:00</date>
                <start>10:40</start>
                <duration>00:30</duration>
                <abstract>IPv6 deployment is well underway in Germany&#8212;some of it visible, much of it happening behind the scenes. So, what&#8217;s actually going on? How much progress has the public sector made? Where does our economy stand? And what does having IPv6 at home really means for users?

This talk provides an overview of IPv6 deployment across Germany. Here&#8217;s a little preview: we&#8217;re doing better than you might think.</abstract>
                <slug>denog18-100-quo-vadis-ipv6-in-germany</slug>
                <track></track>
                
                <persons>
                    <person id='91'>Wilhelm  Boeddinghaus</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/G37JXN/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/G37JXN/feedback/</feedback_url>
            </event>
            <event guid='4e69072a-613c-5a26-838d-52ec58244c6c' id='74' code='HJXTTT'>
                <room>Saal B</room>
                <title>Post Quantum Secure Networking</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-17T11:15:00+01:00</date>
                <start>11:15</start>
                <duration>00:30</duration>
                <abstract>Securing our Infrastructure against Cryptoanalysis with Quantum Computers

This talk gives an overview of the topic of post quantum cryptography. It explains the problem these algorithms try to solve, shows underlying mechanisms and takes a look at developments of the past few years. The presentation is intended as a summary of the of the topic from a network engineer&apos;s point of view: what&apos;s going to be on our schedules in the not too distant future? Which solutions are already available, which topics are still under discussion, and what will be required from our infrastructure by industry standards and  regulatory bodies?</abstract>
                <slug>denog18-74-post-quantum-secure-networking</slug>
                <track></track>
                
                <persons>
                    <person id='61'>Lara Hallaczek</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/HJXTTT/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/HJXTTT/feedback/</feedback_url>
            </event>
            <event guid='cece831a-87fc-5716-9172-21f3e849e0c2' id='42' code='J9DJVF'>
                <room>Saal B</room>
                <title>A Prosecutor in Another Country Wants Your Data in 8 Hours &#8212; Now What?</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-17T13:00:00+01:00</date>
                <start>13:00</start>
                <duration>00:30</duration>
                <abstract>Since 18 August 2026, a prosecutor in another EU country can demand your users&apos; data directly from you &#8212; ten days to comply, eight hours if they&apos;re in a hurry. No mutual legal assistance, no local court in between: just an order in your inbox and a clock. This talk is the E-Evidence Regulation for the people who actually run the infrastructure: which data you can be forced to produce, how fast, and whether the systems you already operate could even answer in time. A few months in, we&apos;ll look at what&apos;s working, what&apos;s on fire, and what you should have built before the first order arrives.</abstract>
                <slug>denog18-42-a-prosecutor-in-another-country-wants-your-data-in-8-hours-now-what</slug>
                <track></track>
                
                <persons>
                    <person id='39'>Mathias Handsche</person>
                </persons>
                <language>en</language>
                <description>Most coverage of the EU E-Evidence Regulation is written for lawyers. This one isn&apos;t. If you operate an ISP, a hosting platform, a cloud, or a registrar, you are the *addressee* of these orders &#8212; and the obligations are technical and time-boxed long before they&apos;re legal.

We&apos;ll start with the 90-second operator edition: European Production Orders (EPOC) and European Preservation Orders (EPOC-PR), who can issue them, which data categories are in play (subscriber, traffic, content), and the deadlines that turn this into an on-call problem rather than a policy memo. Then we get to the parts nobody warns you about: that you must designate an establishment or legal representative, that liability is joint and several with fines reaching into a percentage of global turnover, and that there&apos;s an actual machine interface behind all this &#8212; a decentralised IT system, a transport spec, a hard size limit, and a rollout that may not be finished when the orders start arriving.

The practical core is simpler than the crypto-heavy forensics literature suggests. Evidence just needs to be trustworthy: the right data, demonstrably unchanged, anchored in time, and traceable back to where it came from. You don&apos;t need a forensics lab for that &#8212; you need to know whether the logs and exports you already produce would survive someone asking &quot;how do you know this is genuine?&quot; We&apos;ll cover the idea at a level you can act on, then look at how it usually falls apart in practice: data that&apos;s already been rotated away, mutable logs, a screenshot instead of a record, no idea who pulled what or when.

We close with a field report from the first months of the regime &#8212; readiness across the EU, what early orders actually look like, and a pragmatic checklist so that when (not if) one lands in your inbox, you can produce the right data, in a defensible form, within the deadline &#8212; without it turning into a fire drill every time.

This session is for ISP, hosting, cloud, and registrar engineers, DevOps, abuse/LI-interface teams, and anyone who owns logging or will be the one woken up at 2 a.m. by an 8-hour emergency order. No legal background required; bring your healthy disrespect for bureaucracy.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/J9DJVF/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/J9DJVF/feedback/</feedback_url>
            </event>
            <event guid='b7bc39e7-9add-5a53-9868-90eb57b87907' id='40' code='EVWTHX'>
                <room>Saal B</room>
                <title>Do not look into beam with remaining eye</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-17T13:35:00+01:00</date>
                <start>13:35</start>
                <duration>00:30</duration>
                <abstract>Laser safety is important for everyone, yet knowledge widely differs on what&apos;s applicable and and required to do before conducting work on live fibers. This talk will give a brief introduction into laser classes in networking equipment and safety equipment.</abstract>
                <slug>denog18-40-do-not-look-into-beam-with-remaining-eye</slug>
                <track></track>
                
                <persons>
                    <person id='38'>Nicola &apos;nicoduck&apos; von Thadden</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/EVWTHX/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/EVWTHX/feedback/</feedback_url>
            </event>
            <event guid='2ea57339-ccf6-51b3-9c56-0154c62aa0e1' id='30' code='3FWLT7'>
                <room>Saal B</room>
                <title>The Leak-Proof Routing Table: Mastering BGP Roles, ROAs, and ASPA</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-17T14:10:00+01:00</date>
                <start>14:10</start>
                <duration>00:30</duration>
                <abstract>The global routing system was built on a foundation of trust &#8212; often exploited by route leaks and hijacks. This session breaks down how a trio of complementary security mechanisms shifts the internet from a model of blind faith to strict verification. We will examine how BGP Roles and the Only-To-Customer (OTC) attribute proactively block leaks multiple hops from the source. Next, we will cover how RPKI Route Origin Authorizations (ROAs) secure the origin point, and how Autonomous System Provider Authorization (ASPA) ensures the entire AS_PATH remains valley-free. Attendees will leave understanding exactly how these tools turn the hope that &quot;BGP speakers behaved&quot; into proof that they did.</abstract>
                <slug>denog18-30-the-leak-proof-routing-table-mastering-bgp-roles-roas-and-aspa</slug>
                <track></track>
                
                <persons>
                    <person id='34'>Anton Elita</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/3FWLT7/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/3FWLT7/feedback/</feedback_url>
            </event>
            <event guid='f0214fb8-aef8-5882-9ab0-710dc3700bf1' id='27' code='E8TQM8'>
                <room>Saal B</room>
                <title>SRv6 in the Data Center: Crazy Ideas or Real Use Cases?</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-11-17T14:45:00+01:00</date>
                <start>14:45</start>
                <duration>00:30</duration>
                <abstract>SRv6 divides opinion &#8212; somewhere between visionary promises and the suspicion that it&apos;s yet another overly complex protocol the world doesn&apos;t need. This talk cuts through both extremes and uses concrete scenarios to show where SRv6 actually delivers today.

We start with a compact overview of SRv6 fundamentals: segment types, uSID encoding, and what structurally sets SRv6 apart from MPLS and VXLAN &#8212; and when those differences actually matter. Building on that, we examine three practical use cases: routing in the DC fabric (Clos/spine-leaf with BGP underlay), seamless data center interconnect without MPLS overlay complexity, and SRv6 as the transport plane for AI/GPU cluster fabrics with demanding requirements around load spreading and low latency.

The throughline: what is production-ready today, what remains theoretical &#8212; and where is the added complexity actually worth it?</abstract>
                <slug>denog18-27-srv6-in-the-data-center-crazy-ideas-or-real-use-cases</slug>
                <track></track>
                
                <persons>
                    <person id='30'>Andreas Roeder</person>
                </persons>
                <language>en</language>
                <description>The Goal of this talk is to give a Technology Introduction into SRv6 and how this will be applicable for DataCenter Usecases and compares towards existing Technologies like EVPN/VXLAN. The Goal is to educate the audience about this technology and provide examples of usecases.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://cfp.denog.de/denog18/talk/E8TQM8/</url>
                <feedback_url>https://cfp.denog.de/denog18/talk/E8TQM8/feedback/</feedback_url>
            </event>
            
        </room>
        
    </day>
    
</schedule>
