BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//cfp.denog.de//denog18//speaker//RPFYMS
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-denog18-8YL9JB@cfp.denog.de
DTSTART;TZID=CET:20261116T140500
DTEND;TZID=CET:20261116T143500
DESCRIPTION:Network operators share a vocabulary built on VRFs\, EVPN-VXLAN
 \, and BGP underlays. What doesn't travel is how it gets written down. Eve
 ry vendor and orchestrator has its own dialect\, and most automation tools
  still push device-specific config from an orchestrator down to all involv
 ed devices. Translation\, not domain-specific problems\, becomes a bottlen
 eck.\n\nWe build _Wire-API_ with a different model in mind: Instead of tar
 geting devices\, operators declare the state they want and controllers wor
 k out which devices are affected and what config to push. In the case of a
 n EVPN fabric for example: describe it with objects like `Network`\, `Rout
 ingDomain`\, and `ExternalConnection`\, and adding a network becomes one o
 bject rather than a coordinated change across every leaf and firewall that
  participates. The shift is in what gets declared: desired state instead o
 f a device's running config. From there\, drift correction and HA-aware ma
 intenance stop being separate runbooks and become properties of the reconc
 ile loop\, and the same model extends to anything else on the network expr
 essed as intent.\n\nThe core is Kubernetes. _Wire-API_ is a set of CRDs an
 d controllers that reuse the contract that made Kubernetes work in "comput
 e"—declared state\, continuous reconciliation\, honest status—and appl
 y it to the network domain.\n\nThe presentation argues for the _Wire-API_ 
 model and walks through a live EVPN-VXLAN example—one intent object\, ve
 ndor-specific config on Cisco NX-OS and Nokia SR Linux—then covers desig
 n decisions and partial-failure handling. Wire-API already operates produc
 tion fabrics across multiple availability zones\; the model works today ev
 en as the framework continues to grow.\n\n_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.
DTSTAMP:20261005T184810Z
LOCATION:Saal B
SUMMARY:Wire-API: fleet-wide\, vendor-neutral network automation - Enric Pu
 jol\, Sebastian
URL:https://cfp.denog.de/denog18/talk/8YL9JB/
END:VEVENT
END:VCALENDAR