<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
  xmlns:content="http://purl.org/rss/1.0/modules/content/"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
  xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Chaos Computer Club - DENOG18 (low quality webm)</title>
    <link>https://media.ccc.de/c/denog18</link>
    <description> This feed contains all events from denog18 as webm</description>
    <copyright>see video outro</copyright>
    <lastBuildDate>Mon, 16 Nov 2026 23:25:10 -0000</lastBuildDate>
    <image>
      <url>https://static.media.ccc.de/media/events/denog/denog18/logo.png</url>
      <title>Chaos Computer Club - DENOG18 (low quality webm)</title>
      <link>https://media.ccc.de/c/denog18</link>
    </image>
    <item>
      <title>IPv6 routing loops -- A call to fix router configurations. (denog18)</title>
      <link>https://media.ccc.de/v/denog18-85-ipv6-routing-loops-a-call-to-fix-router-configurations</link>
      <description>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.

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://cfp.denog.de/denog18/talk/PRRFUN/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/denog/denog18/webm-sd/denog18-a-85-eng-IPv6_routing_loops_--_A_call_to_fix_router_configurations_webm-sd.webm"
        length="28850761"
        type="video/webm"/>
      <pubDate>Mon, 16 Nov 2026 15:25:00 +0100</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/denog/denog18/webm-sd/denog18-a-85-eng-IPv6_routing_loops_--_A_call_to_fix_router_configurations_webm-sd.webm?1794871291</guid>
      <dc:identifier>f3c2ec95-4a3a-57c5-87e2-2894714a6c41</dc:identifier>
      <dc:date>2026-11-16T15:25:00+01:00</dc:date>
      <itunes:author>Maynard Koch</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>PRRFUN, 2026, denog18, Saal A, denog18-eng, Day 2</itunes:keywords>
      <itunes:summary>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.

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://cfp.denog.de/denog18/talk/PRRFUN/
</itunes:summary>
      <itunes:duration>00:08:46</itunes:duration>
      <itunes:image href="https://static.media.ccc.de/media/events/denog/denog18/85-f3c2ec95-4a3a-57c5-87e2-2894714a6c41.jpg"/>
    </item>
    <item>
      <title>ICMP trickery in &quot;reduced-IPv4&quot; networks (denog18)</title>
      <link>https://media.ccc.de/v/denog18-84-icmp-trickery-in-reduced-ipv4-networks</link>
      <description>Did you think IPv6 transition technologies were too easy? &quot;one more&quot; wasn&#39;t enough choices? Did you ever have to debug one of these &quot;simple&quot; setups? Come join for a walk through ICMP (v4 and v6) behavior and features!

This presentation will go through the various edge cases and overlaps between ICMPv4 and ICMPv6 in transition/IPv4 phase-out setups. One of these is likely applicable to most of us — hopefully you&#39;re not a poor soul for whom _all_ apply!

A rough outline:
- RFC 4884 and historic context: ICMP in MPLS networks
- convincing your tools to not hide the goods from you
- ICMP translation in NAT64 devices
- midpath ICMPv6 into NAT64
- 192.0.0.8 is love, 192.0.0.8 is life
- ICMPv4 on RFC 8950 devices
- Good thing nobody needs PMTUD, right?

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://cfp.denog.de/denog18/talk/ZQEANK/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/denog/denog18/webm-sd/denog18-a-84-eng-ICMP_trickery_in_reduced-IPv4_networks_webm-sd.webm"
        length="38666961"
        type="video/webm"/>
      <pubDate>Mon, 16 Nov 2026 15:15:00 +0100</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/denog/denog18/webm-sd/denog18-a-84-eng-ICMP_trickery_in_reduced-IPv4_networks_webm-sd.webm?1794871263</guid>
      <dc:identifier>8fcb2099-0da2-5d57-9971-57c7dcfde062</dc:identifier>
      <dc:date>2026-11-16T15:15:00+01:00</dc:date>
      <itunes:author>David &#39;equinox&#39; Lamparter</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>ZQEANK, 2026, denog18, Saal A, denog18-eng, Day 2</itunes:keywords>
      <itunes:summary>Did you think IPv6 transition technologies were too easy? &quot;one more&quot; wasn&#39;t enough choices? Did you ever have to debug one of these &quot;simple&quot; setups? Come join for a walk through ICMP (v4 and v6) behavior and features!

This presentation will go through the various edge cases and overlaps between ICMPv4 and ICMPv6 in transition/IPv4 phase-out setups. One of these is likely applicable to most of us — hopefully you&#39;re not a poor soul for whom _all_ apply!

A rough outline:
- RFC 4884 and historic context: ICMP in MPLS networks
- convincing your tools to not hide the goods from you
- ICMP translation in NAT64 devices
- midpath ICMPv6 into NAT64
- 192.0.0.8 is love, 192.0.0.8 is life
- ICMPv4 on RFC 8950 devices
- Good thing nobody needs PMTUD, right?

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://cfp.denog.de/denog18/talk/ZQEANK/
</itunes:summary>
      <itunes:duration>00:09:54</itunes:duration>
      <itunes:image href="https://static.media.ccc.de/media/events/denog/denog18/84-8fcb2099-0da2-5d57-9971-57c7dcfde062.jpg"/>
    </item>
    <item>
      <title>QoE-riosities of 2026 - What we saw on the Internet this year (denog18)</title>
      <link>https://media.ccc.de/v/denog18-68-qoe-riosities-of-2026-what-we-saw-on-the-internet-this-year</link>
      <description>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&#39;s have a data-driven look at the Unexpected of 2026.

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://cfp.denog.de/denog18/talk/ZCXTKW/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/denog/denog18/webm-sd/denog18-a-68-eng-QoE-riosities_of_2026_-_What_we_saw_on_the_Internet_this_year_webm-sd.webm"
        length="67888881"
        type="video/webm"/>
      <pubDate>Mon, 16 Nov 2026 14:40:00 +0100</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/denog/denog18/webm-sd/denog18-a-68-eng-QoE-riosities_of_2026_-_What_we_saw_on_the_Internet_this_year_webm-sd.webm?1794870638</guid>
      <dc:identifier>e233064e-3a79-5697-8041-03267c0ef282</dc:identifier>
      <dc:date>2026-11-16T14:40:00+01:00</dc:date>
      <itunes:author>Alexander Dethof</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>ZCXTKW, 2026, denog18, Saal A, denog18-eng, Day 2</itunes:keywords>
      <itunes:summary>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&#39;s have a data-driven look at the Unexpected of 2026.

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://cfp.denog.de/denog18/talk/ZCXTKW/
</itunes:summary>
      <itunes:duration>00:21:17</itunes:duration>
      <itunes:image href="https://static.media.ccc.de/media/events/denog/denog18/68-e233064e-3a79-5697-8041-03267c0ef282.jpg"/>
    </item>
    <item>
      <title>EVPN - One Control Plane to Rule Them All (denog18)</title>
      <link>https://media.ccc.de/v/denog18-45-evpn-one-control-plane-to-rule-them-all</link>
      <description>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’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’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.

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://cfp.denog.de/denog18/talk/VCQLXW/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/denog/denog18/webm-sd/denog18-a-45-eng-EVPN_-_One_Control_Plane_to_Rule_Them_All_webm-sd.webm"
        length="80515971"
        type="video/webm"/>
      <pubDate>Mon, 16 Nov 2026 11:05:00 +0100</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/denog/denog18/webm-sd/denog18-a-45-eng-EVPN_-_One_Control_Plane_to_Rule_Them_All_webm-sd.webm?1794870484</guid>
      <dc:identifier>a07810fc-09c0-5ef5-b1cf-cbc3f69cdf34</dc:identifier>
      <dc:date>2026-11-16T11:05:00+01:00</dc:date>
      <itunes:author>Patrick Prangl</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>VCQLXW, 2026, denog18, Saal A, denog18-eng, Day 2</itunes:keywords>
      <itunes:summary>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’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’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.

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://cfp.denog.de/denog18/talk/VCQLXW/
</itunes:summary>
      <itunes:duration>00:23:12</itunes:duration>
      <itunes:image href="https://static.media.ccc.de/media/events/denog/denog18/45-a07810fc-09c0-5ef5-b1cf-cbc3f69cdf34.jpg"/>
    </item>
    <item>
      <title>Retrofitting API into a routing software (denog18)</title>
      <link>https://media.ccc.de/v/denog18-51-retrofitting-api-into-a-routing-software</link>
      <description>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&#39;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.

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.

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://cfp.denog.de/denog18/talk/3BJJKY/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/denog/denog18/webm-sd/denog18-a-51-eng-Retrofitting_API_into_a_routing_software_webm-sd.webm"
        length="102171355"
        type="video/webm"/>
      <pubDate>Mon, 16 Nov 2026 10:30:00 +0100</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/denog/denog18/webm-sd/denog18-a-51-eng-Retrofitting_API_into_a_routing_software_webm-sd.webm?1794870359</guid>
      <dc:identifier>9ce903d0-d8bc-5624-9ed1-c62f3a64a955</dc:identifier>
      <dc:date>2026-11-16T10:30:00+01:00</dc:date>
      <itunes:author>Maria Matejka</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>3BJJKY, 2026, denog18, Saal A, denog18-eng, Day 2</itunes:keywords>
      <itunes:summary>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&#39;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.

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.

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://cfp.denog.de/denog18/talk/3BJJKY/
</itunes:summary>
      <itunes:duration>00:25:54</itunes:duration>
      <itunes:image href="https://static.media.ccc.de/media/events/denog/denog18/51-9ce903d0-d8bc-5624-9ed1-c62f3a64a955.jpg"/>
    </item>
    <generator>media.ccc.de / RSS 0.3.3</generator>
    <itunes:category text="Technology"/>
    <itunes:image href="https://static.media.ccc.de/media/events/denog/denog18/logo.png"/>
    <itunes:owner>
      <itunes:name>CCC media team</itunes:name>
      <itunes:email>media@c3voc.de</itunes:email>
    </itunes:owner>
    <itunes:author>CCC media team</itunes:author>
    <itunes:explicit>No</itunes:explicit>
    <itunes:keywords>CCC Congress Hacking Security Netzpolitik</itunes:keywords>
    <itunes:subtitle>A wide variety of video material distributed by the CCC. All content is taken from cdn.media.ccc.de and media.ccc.de</itunes:subtitle>
    <itunes:summary>A wide variety of video material distributed by the Chaos Computer Club. This feed contains all events from denog18 as webm</itunes:summary>
  </channel>
</rss>