BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//cfp.denog.de//denog18//speaker//QAWRPJ
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-XPH3W7@cfp.denog.de
DTSTART;TZID=CET:20261116T110500
DTEND;TZID=CET:20261116T113500
DESCRIPTION: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?\n\nIn this talk I'll
  go into two areas of server firmware that operatores rarely look at close
 ly: the one that boots the server\, and the one that allows out-of-band ma
 nagement via the Baseboard Management Controller (BMC).\n\nOn the boot sid
 e: Do PXE and HTTP boot actually work over IPv6? And what unexpected side 
 effects do you might see?\n\nOn the management side: How does IPv6 support
  look on a BMC today\, and what's still broken?\n\nNobody's going to fix w
 hat nobody complains about. Let's find out how broken this is and what we 
 can do about it.
DTSTAMP:20261005T184939Z
LOCATION:Saal B
SUMMARY:IPv6 in firmware: Still booting in the wrong decade - sinuscosinust
 an
URL:https://cfp.denog.de/denog18/talk/XPH3W7/
END:VEVENT
END:VCALENDAR