BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//cfp.denog.de//denog18//speaker//RQ9JT9
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-SYTTEC@cfp.denog.de
DTSTART;TZID=CET:20261116T170000
DTEND;TZID=CET:20261116T171500
DESCRIPTION:What actually changes in your network when you stop treating IP
 v4 as infrastructure and start treating it as a service?\n\ndraft-vanmook-
 intarea-ipv6-resolved-gateway (presented at IETF 126\, WG adoption call pe
 nding) defines a single sentinel gateway address\, provisionally 192.0.0.1
 1 (requested from the IANA Special-Purpose Registry\, not yet assigned)\, 
 handed out as the ordinary DHCPv4 default gateway. Updated hosts resolve t
 heir first hop from the IPv6 neighbour cache\; unmodified hosts ARP for th
 e sentinel once and the router answers. That's the whole mechanism. Everyt
 hing downstream of it is the interesting part.\n\nThis talk is about what 
 that does to a running network: no IPv4 subnets anywhere\, no ARP\, no FHR
 P\, IPv4 address pools that go flat — any /32 works anywhere in the foot
 print\, nothing stranded by subnet sizing. The core forwards v4-via-v6 (RF
 C 8950) with no IPv4 configured on any router interface.\n\nOn the impleme
 ntation 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 unmodifi
 ed-host behaviour across seven operating systems\; and vendor configuratio
 n examples for IOS XR\, JunOS\, SR OS\, EOS and RouterOS. On the router si
 de\, three working deployment models: a single-gateway reference\, an acti
 ve/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 man
 agement network at all.\n\nPlus the failure modes\, the ND health prerequi
 sites\, and what breaks when you get it wrong.\n\nNo tunnels. No translati
 on. No flag day. Keep the shape\, change what it means.
DTSTAMP:20261005T184956Z
LOCATION:Saal A
SUMMARY:Killing ARP: running IPv4 as a service on an IPv6-only network - Re
 mco van Mook
URL:https://cfp.denog.de/denog18/talk/SYTTEC/
END:VEVENT
END:VCALENDAR