3 ms·
Could you expand on the flaws and why are they problematic?
by nazgul17 9y ago
Could you expand on the flaws and why are they problematic?
- zkms 9y agohttps://www.sinog.si/wp-content/uploads/2017/05/SINOG4_Job_Snijders_IPv6_Panel-1.pdf https://www.sinog.si/wp-content/uploads/2017/05/SINOG4_Job_S... and https://www.troopers.de/wp-content/uploads/2013/11/TROOPERS14-Why_IPv6_Security_is_so_hard-Structural_Deficits_of_IPv6_and_their_Implications-Enno_Rey.pdf https://www.troopers.de/wp-content/uploads/2013/11/TROOPERS1... and https://www.sinog.si/wp-content/uploads/2017/05/SINOG-IPv6-Keynote2_Ole.pdf https://www.sinog.si/wp-content/uploads/2017/05/SINOG-IPv6-K... are worth reading. TL;DR: * Multicast and mobility are shits * NDP an overcomplicated shit * The SLAAC / DCHPv6 thing is a ripe mess * getting IPv6 provider-independent space is too hard * extension headers are tricky, slow to parse, a source of tricky security issues, and thus are almost completely unused on the Internet in general Basically almost all the moving parts in ipv6 (beyond the wire format and its 128-bit addresses) that aren't dangerously convoluted / mostly unused are pretty much just NIH'd reimplementations of the corresponding IPv4 protocols (like ARP, say).
- lmm 9y agoProvider-independent space ought to be impossible - addresses should be addresses. If you want multiple routing paths to you, get an AS number and participate in actual global routing. Otherwise, accept that when you move your address will change.