BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//cfp.denog.de//denog18//speaker//EKBRCX
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-V7Y3X9@cfp.denog.de
DTSTART;TZID=CET:20261116T164500
DTEND;TZID=CET:20261116T170000
DESCRIPTION:Routing IPv4 packets using IPv6 next-hops has been around for s
 ome time now. It offers great opportunities to reduce IPv4 address usage i
 n the distribution and access layer\, and enables providing IPv4 as a pure
  add-on\, keeping a clean IPv6 address structure underneath.\n\nDespite it
 s benefits\, major challenges for deploying IPv4-with-IPv6 next-hops in pr
 actice persist. While\, e.g.\, BGP supports such routes using RFC8950\, ma
 ny other IGPs still lack support. Other major issues are 'the last mile'\,
  i.e.\, auto-configuring clients (or\, for this use-case\, more likely ser
 vers)\, and the impact of  IPv4-with-IPv6 next-hop usage on traceroutes.\n
 \nIn 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 l
 egacy Layer-2 infrastructure\, e.g.\, LACP.
DTSTAMP:20261005T184746Z
LOCATION:Saal A
SUMMARY:IPv4-with-IPv6 Next-Hops: At least faster progress than Linux on th
 e Desktop - Tobias Fiebig
URL:https://cfp.denog.de/denog18/talk/V7Y3X9/
END:VEVENT
END:VCALENDAR