<?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 (opus)</title>
    <link>https://media.ccc.de/c/denog18</link>
    <description> This feed contains all events from denog18 as opus</description>
    <copyright>see video outro</copyright>
    <lastBuildDate>Mon, 16 Nov 2026 23:25:07 -0000</lastBuildDate>
    <image>
      <url>https://static.media.ccc.de/media/events/denog/denog18/logo.png</url>
      <title>Chaos Computer Club - DENOG18 (opus)</title>
      <link>https://media.ccc.de/c/denog18</link>
    </image>
    <item>
      <title>IPv4 as a service on an IPv6-only network (denog18)</title>
      <link>https://media.ccc.de/v/denog18-99-ipv4-as-a-service-on-an-ipv6-only-network</link>
      <description>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 &#39;the last mile&#39;, 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.

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&#39;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 — 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 — 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.

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://cfp.denog.de/denog18/talk/V7Y3X9/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/denog/denog18/opus/denog18-a-99-eng-IPv4_as_a_service_on_an_IPv6-only_network_opus.opus"
        length="22483623"
        type="audio/opus"/>
      <pubDate>Mon, 16 Nov 2026 16:45:00 +0100</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/denog/denog18/opus/denog18-a-99-eng-IPv4_as_a_service_on_an_IPv6-only_network_opus.opus?1794871322</guid>
      <dc:identifier>a4851425-8572-5a1a-99f8-2ea109466818</dc:identifier>
      <dc:date>2026-11-16T16:45:00+01:00</dc:date>
      <itunes:author>Tobias Fiebig, Remco van Mook</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>V7Y3X9, 2026, denog18, Saal A, denog18-eng, Day 2</itunes:keywords>
      <itunes:summary>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 &#39;the last mile&#39;, 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.

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&#39;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 — 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 — 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.

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://cfp.denog.de/denog18/talk/V7Y3X9/
</itunes:summary>
      <itunes:duration>00:30:39</itunes:duration>
      <itunes:image href="https://static.media.ccc.de/media/events/denog/denog18/99-a4851425-8572-5a1a-99f8-2ea109466818.jpg"/>
    </item>
    <item>
      <title>Teach Networking!? (denog18)</title>
      <link>https://media.ccc.de/v/denog18-94-teach-networking</link>
      <description>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’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&#39;ve been teaching the basics of networking for several years now, and I&#39;d like to share my experience with you.

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://cfp.denog.de/denog18/talk/E7UDUC/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/denog/denog18/opus/denog18-a-94-eng-Teach_Networking_opus.opus"
        length="9858959"
        type="audio/opus"/>
      <pubDate>Mon, 16 Nov 2026 15:35:00 +0100</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/denog/denog18/opus/denog18-a-94-eng-Teach_Networking_opus.opus?1794871037</guid>
      <dc:identifier>d5597601-9fbd-5bd9-9911-bcdb2140141f</dc:identifier>
      <dc:date>2026-11-16T15:35:00+01:00</dc:date>
      <itunes:author>Vanessa Gaube</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>E7UDUC, 2026, denog18, Saal A, denog18-eng, Day 2</itunes:keywords>
      <itunes:summary>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’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&#39;ve been teaching the basics of networking for several years now, and I&#39;d like to share my experience with you.

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://cfp.denog.de/denog18/talk/E7UDUC/
</itunes:summary>
      <itunes:duration>00:12:25</itunes:duration>
      <itunes:image href="https://static.media.ccc.de/media/events/denog/denog18/94-d5597601-9fbd-5bd9-9911-bcdb2140141f.jpg"/>
    </item>
    <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/opus/denog18-a-85-eng-IPv6_routing_loops_--_A_call_to_fix_router_configurations_opus.opus"
        length="6737488"
        type="audio/opus"/>
      <pubDate>Mon, 16 Nov 2026 15:25:00 +0100</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/denog/denog18/opus/denog18-a-85-eng-IPv6_routing_loops_--_A_call_to_fix_router_configurations_opus.opus?1794870938</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/opus/denog18-a-84-eng-ICMP_trickery_in_reduced-IPv4_networks_opus.opus"
        length="7688534"
        type="audio/opus"/>
      <pubDate>Mon, 16 Nov 2026 15:15:00 +0100</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/denog/denog18/opus/denog18-a-84-eng-ICMP_trickery_in_reduced-IPv4_networks_opus.opus?1794870662</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/opus/denog18-a-68-eng-QoE-riosities_of_2026_-_What_we_saw_on_the_Internet_this_year_opus.opus"
        length="16259338"
        type="audio/opus"/>
      <pubDate>Mon, 16 Nov 2026 14:40:00 +0100</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/denog/denog18/opus/denog18-a-68-eng-QoE-riosities_of_2026_-_What_we_saw_on_the_Internet_this_year_opus.opus?1794870390</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/opus/denog18-a-45-eng-EVPN_-_One_Control_Plane_to_Rule_Them_All_opus.opus"
        length="17498437"
        type="audio/opus"/>
      <pubDate>Mon, 16 Nov 2026 11:05:00 +0100</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/denog/denog18/opus/denog18-a-45-eng-EVPN_-_One_Control_Plane_to_Rule_Them_All_opus.opus?1794870378</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/opus/denog18-a-51-eng-Retrofitting_API_into_a_routing_software_opus.opus"
        length="18789132"
        type="audio/opus"/>
      <pubDate>Mon, 16 Nov 2026 10:30:00 +0100</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/denog/denog18/opus/denog18-a-51-eng-Retrofitting_API_into_a_routing_software_opus.opus?1794870354</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 opus</itunes:summary>
  </channel>
</rss>