9 ipv6-routing
Download as PPTX, PDF1 like2,896 views
This document summarizes key topics related to IPv6 and routing in IP networks. It discusses IPv6 addressing architecture, including unicast addresses, link-local addresses, and multicast addresses. It also covers IPv6 packet format, extension headers, fragmentation, and ICMPv6. The document then discusses routing within IP networks, including IPv6 subnets, routing organization with autonomous systems, and interdomain routing protocols.
9 ipv6-routing
- 1. Week 9 IPv6 Routing in IP networks
- 2. Agenda • IPv6 • Addressing architecture • Packets • ICMPv6 • Routing in IP networks
- 3. IPv6 unicast addresses interface ID 128 bits N bits M bits 128-N-M bits Usually 64 bits Based on MAC Address global routing prefix subnet ID Can be used to identify the ISP responsible for this address A subnet in this ISP or a customer of this ISP
- 4. IPv6 link-local • Used by daevdiceds rone ssamsee LAsN to exchange IPv6 packets when they don't have/need globally routable address • Each host/router must generate one link local address for each of its interfaces • Each IPv6 host uses several IPv6 addresses interface ID 128 bits 10 bits 54 bits 64 bits FE80 0000000000.....00000000000
- 5. IPv6 Multicast • An IPv6 multicast address identifies a group a receivers Group ID 128 bits 8 bits 4 bits 4 bits 112 bits 11111111 flags scope Node local-scope Link-local scope Subnet local-scope Site local-scope Organisation local-scope Global scope Permanent Address Temporary Address • All hosts : FF02::1 • All routers : FF02::2
- 6. Agenda • IPv6 • Addressing architecture • Packets • ICMPv6 • Routing in IP networks
- 7. IPv6 packet format 32 bits Ver Tclass Flow Label NxtHdr Hop Limit Payload Length Source IPv6 address (128 bits) Destination IPv6 address (128 bits) Version=6 Traffic class Size of packet content in bytes Unclear utilisation Same as TTL Used to identify the type of the next header found in the packet payload
- 8. Sample IPv6 packets Payload Length Payload Length Sequence number Acknowledgment number THL Reserved Flags Window • Identification of a transport (UDP/TCP) flow • IPv6 source/destination, Source/Destination ports 32 bits Ver Tclass Flow Label NxtHdr Hop Limit Source IPv6 address (128 bits) Destination IPv6 address (128 bits) Source port Destination port Length Checksum UDP 32 bits Ver Tclass Flow Label NxtHdr Hop Limit Source IPv6 address (128 bits) Destination IPv6 address (128 bits) Source port Destination port Checksum Urgent pointer TCP UDP TCP
- 9. Packet forwarding • IPv6 uses longest match • Example Destination Gateway ::/0 fe80::dead:beef ::1 ::1 2a02:2788:2c4:16f::/64 eth0 2001:6a8:3080::/48 fe80::bad:cafe 2001:6a8:2d80::/48 fe80::bad:bad 2001:6a8::/32 fe80::aaaa:bbbb Packets to 2001:6a8:3080::1234, 2001:1890:123a::1:1e, 2001:6a8:3880:40::2
- 10. Extension headers • Hop-by-Hop Options • Routing (Type 0 and Type 2) • Fragment • Destination Options • Authentication • Encapsulating Security Payload • Each header must be encoded as n*64 bits
- 11. Packet fragmentation • How to handle this network ? R1 R2 MTU:1500 MTU:1400 MTU:1300
- 12. Packet fragmentation • IPv4 used packet fragmentation on routers • All hosts must handle 576+ bytes packets • experience showed fragmentation is costly for routers and difficult to implement in hardware • PathMTU discovery • widely implemented in TCP stacks
- 13. P• aIPvc6 kreequtir efsr thaatg evmerye linnk tina thtei on internet have an MTU of 1280 octets or more • Routers do not perform fragmentation • Only end hosts perform fragmentation and reassembly by using the fragmentation header • But PathMTU discovery should avoid fragmentation most of the time
- 14. A fragmented packet First fragment Second (and last) fragment 32 bits Ver Tclass Flow Label NxtHdr Hop Limit Payload Length Source IPv6 address (128 bits) Destination IPv6 address (128 bits) Source port Destination port Length Checksum UDP (first part) 44:fragment Nxt Hdr Zero Frag. Offset 0 M Fragment identification = 1234 UDP 32 bits Ver Tclass Flow Label NxtHdr Hop Limit Payload Length Source IPv6 address (128 bits) Destination IPv6 address (128 bits) 44:fragment Nxt Hdr Zero Frag. Offset 0 M Fragment identification = 1234 True None False (end of UDP segment)
- 15. Agenda • IPv6 • Addressing architecture • Packets • ICMPv6 • Routing in IP networks
- 16. ICMPv6 • Types of ICMPv6 messages • Destination (addr,net,port) unreachable • Packet too big • Used for PathMTU discovery • Time expired (Hop limit exhausted) • Echo request and echo reply • Multicast group membership • Router advertisments, Neighbor discovery • Autoconfiguration
- 17. ICMPv6 packet • Type • ICMPv6 error messages • 1 Destination Unreachable • 3 Time Exceeded • 2 Packet Too Big • 4 Parameter Problem • ICMPv6 informational messages: • 128 Echo Request • 129 Echo Reply Ver Tclass Flow Label NxtHdr Hop Limit Payload Length Source IPv6 address (128 bits) Destination IPv6 address (128 bits) Type Code Checksum Message body 58 for ICMPv6 Covers ICMPv6 message and part of IPv6 header
- 18. traceroute6 in details • Source sends UDP segments with increasing hop limit • Intermediate routers reply with ICMP Time Exceeded messages
- 19. traceroute6 traceroute6 to star.c10r.facebook.com (2a03:2880:2130:cf05:face:b00c::1) from 2001:6a8:3080:2:451c:db2:a92f:3d50, 64 hops max, 12 byte packets 1 2001:6a8:3080:2::1 0.329 ms 2 2001:6a8:3000:8000::1 0.582 ms 3 2001:6a8:0:6009::1 1.505 ms 4 2001:7f8:1::a503:2934:1 8.167 ms 5 2620:0:1cff:dead:beef::34c 8.091 ms 6 2620:0:1cff:dead:beef::2d9 13.922 ms 7 2620:0:1cff:dead:beef::2dc 108.487 ms 8 2620:0:1cff:dead:beef::9a7 106.722 ms 9 2620:0:1cff:dead:beef::12a8 103.758 ms 10 2620:0:1cff:dead:beef::999 105.648 ms
- 20. traceroute 2001:db8:7/48 A’s routing table destination interface/NH ::/0 2001:db8:7::B 2001:db8:7/48 2001:db8:4::C 2001:db8:1/48 West 2001:db8:4/48 East 2001:db8:7/48 North B’s routing table destination interface/NH ::/0 2001:db8:5::C 2001:db8:2/47 2001:db8:6::E 2001:db8:5/48 South 2001:db8:6/48 East 2001:db8:7/48 West C’s routing table destination interface/NH 2001:db8:1/48 2001:db8:5::B 2001:db8:2/47 2001:db8:3::E 2001:db8:2/48 2001:db8:5::B 2001:db8:3/48 East 2001:db8:4/48 West 2001:db8:5/48 North 2001:db8:6/47 2001:db8:5::B E’s routing table destination interface/NH ::/0 2001:db8:6::B 2001:db8:2/48 East 2001:db8:3/48 West 2001:db8:6/48 North RA RB RC RE 2001:db8:1/48 2001:db8:6/48 2001:db8:5/48 2001:db8:4/48 2001:db8:3/48 2001:db8:2/48
- 21. Agenda • IPv6 • Routing in IP networks • IPv6 subnets • Routing organization • Interdomain routing
- 22. Datalink layer service • Each device is identified by a 48 bits MAC address in the datalink layer • Ethernet, WiFi • Unicast transmission • Multicast transmission
- 23. IPv6 subnet • A subnet gathers hosts and routers that can directly exchange frames without passing through an intermediate route 2001:db8:1234:5678::1 R 2001:db8:1234:5678::/64 2001:db8:1234:5678::AA 2001:db8:1234:5678::BB 2001:db8:1234:5678::CC
- 24. Issues • How to easily assign IPv6 addresses to hosts ? • Manual configuration is not viable • How to map IPv6 addresses onto the corresponding MAC addresses ?
- 25. IPv6 over Ethernet IPv6: 2001:0:0:0:8::A Eth : A 2001:0:0:0:8::A wants to send a packet to 2001:0:0:0:8::C 1 2 Neighbor solicitation: Addr Eth 2001:0:0:0:8::C ? sent to IPv6 multicast address 3 IPv6: 2001:0:0:0:8::E Eth : E Ipv6: 2001:0:0:0:8::C Eth : C Ipv6: 2001:0:0:0:8::C Eth : C IPv6: 2001:0:0:0:8::E Eth : E IPv6: 2001:0:0:0:8::A Eth : A IPv6: 2001:0:0:0:8::C Neighbor advertisement: 2001:0:0:0:8::C is reachable via Ethernet Add : C Eth : C IPv6: 2001:0:0:0:8::E Eth : E IPv6: 2001:0:0:0:8::A Eth : A
- 26. Agenda • IPv6 • Routing in IP networks • IPv6 subnets • Routing organization • Interdomain routing
- 27. Internet organisation • Internet is an internetwork with a large number of Autonomous Systems (AS) • an AS is a set of routers that are managed by the same administrative entity • Autonomous Systems are interconnected to allow the transmission of IP packets from any source to any destination • On the Internet, most packets need to travel through several transit Autonomous Systems
- 28. Types of domains • Transit domain • A transit domain allows external domains to use its infrastructure to send packets to other domains S1 • Examples T1 T2 T3 S2 S3 S4 • UUNet, OpenTransit, GEANT, Internet2, RENATER, EQUANT, BT, Telia, Level3,...
- 29. Stub domains A stub domain does not allow external domains to use its infrastructure to send packets to other domains T1 T2 T3 S1 S2 S3 S4 A stub is connected to at least one transit domain Content-rich stub domain : Yahoo, Google, MSN, TF1, BBC,... Access-rich stub domain : ISPs providing Internet access via CATV, ADSL, ...
- 30. Belnet Source : http://www.belnet.be
- 31. GEANT Source : http://www.belnet.be
- 33. Internet routing • Interior Gateway Protocol (IGP) • Routing of IP packets inside each domain • Only knows topology of its domain Domain1 Domain4 • Exterior Gateway Protocol (EGP) • Routing of IP packets between domains • Each domain is considered as a blackbox Domain2 Domain3
- 34. Intradomain routing • Static routing • Only useful in very small domains • Distance vector routing • Routing Information Protocol (RIP) • Link-state routing • Open Shortest Path First (OSPF) • Intermediate System- Intermediate-System (IS-IS)
- 35. Intradomain routing • Goal • Allow routers to transmit IP packets along the best path towards their destination • best usually means the shortest path • Shortest measured in seconds or hops • sometimes best means the less loaded path • Alternate routes in case of failures • Behaviour • All routers exchange routing information
- 36. Agenda • IPv6 • Routing in IP networks • IPv6 subnets • Routing organization • Interdomain routing
- 37. Interdomain routing • Goals • Allow to transmit IP packets along the best path towards their destination through several transit domains while taking into account their routing policies of each domain without knowing their detailed topology • From an interdomain viewpoint, best path often means cheapest path • Each domain is free to specify inside its routing policy the domains for which it agrees to provide a transit service and the method it uses to select the best path to reach each destination
- 38. Interdomain links • Private link • Usually a leased line between two routers belonging to the two connected domains R1 R2 DomainA DomainB
- 39. Interconnection exchanges • How to efficiently connect several domains together ? R1 R2 R3 R4 Physical link Interdomain link
- 40. Routing policies • In theory BGP allows each domain to define its own routing policy... • In practice there are two common policies • customer-provider peering • Customer c buys Internet connectivity from provider P • shared-cost peering • Domains x and y agree to exchange packets without any payment
- 41. Customer-provider Customer Provider peering AS1 AS2 $ $ $ AS3 AS4 $ • Principle $ AS7 • Customer sends to its provider internal routes and routes learned from its customers • Provider will advertise those routes to the entire Internet to allow anyone to reach the Customer • Provider sends to its customers all known routes • Customer will reach anyone on the Internet
- 42. Customer-provider peering : example AS1 AS2 $ $ $ AS3 AS4 • AS7-AS4 peering link $ • AS7 advertises its routes to AS4 $ AS 7 • AS4 advertises to AS7 all its routes • AS4-AS2 peering link Customer-provider • AS4 advertises its own routes and those of its customers (AS7) • AS2 advertises to AS2 all known routes
- 43. Shared-cost peering AS1 AS2 AS3 AS4 $ AS7 Customer-provider $ $ $ $ Shared-cost • Principle • PeerX sends to PeerY its internal routes and the routes learned from its own customers • PeerY sends to PeerX its internal routes and the routes learned from its own customers
- 44. Routing policies • A domain specifies its routing policy by defining two sets of filters for each peer • Import filter • Specifies which routes can be accepted by the router among all the received routes from a given peer • Export filter • Specifies which routes can be advertised by the router to a given peer
- 45. Routing policies AS1 AS2 AS3 AS4 $ AS7 Customer-provider $ $ $ $ Shared-cost Import policy for AS4 Import: from AS3 accept AS3 import: from AS7 accept AS7 import: from AS1 accept ANY import: from AS2 accept ANY Export policy for AS4 export: to AS3 announce AS4 AS7 export: to AS7 announce ANY export: to AS1 announce AS4 AS7 export: to AS2 announce AS4 AS7 Import policy for AS7 Import: from AS4 accept ANY Export policy for AS4 export: to AS4 announce AS7
Editor's Notes
- #4: Today, the default encoding for global unicast addresses is to use : 48 bits for the global routing prefix (first three bits are set to 001) 16 bits for the subnet ID 64 bits for the interface ID
- #5: Site-local addresses were defined in the first IPv6 specifications, but they are now deprecated and should not be used. Recently “private” addresses have been defined as Unique Local IPv6 Addresses as a way to allow entreprise to obtain IPv6 addresses without being forced to request them from providers or RIRs. The way to choose such a ULA prefix is defined in : R. Hinden, B. Haberman, Unique Local IPv6 Unicast Addresses, RFC4193, October 2005 Recently, the case for a registration of such addresses has been proposed, see : R. Hinden, G. Huston, T. Narten, Centrally Assigned Unique Local IPv6 Unicast Addresses, internet draft, <draft-ietf-ipv6-ula-central-02.txt>, work in progress, June 2007 See also http://www.ripe.net/ripe/policies/proposals/2007-05.html -
- #6: The full list of well known IPv6 multicast groups is available from http://www.iana.org/assignments/ipv6-multicast-addresses Examples include Node-Local Scope ---------------- FF01:0:0:0:0:0:0:1 All Nodes Address [RFC4291] FF01:0:0:0:0:0:0:2 All Routers Address [RFC4291] Link-Local Scope ---------------- FF02:0:0:0:0:0:0:1 All Nodes Address [RFC4291] FF02:0:0:0:0:0:0:2 All Routers Address [RFC4291] FF02:0:0:0:0:0:0:5 OSPFIGP [RFC2328,Moy] FF02:0:0:0:0:0:0:6 OSPFIGP Designated Routers [RFC2328,Moy] FF02:0:0:0:0:0:0:9 RIP Routers [RFC2080] FF02:0:0:0:0:0:0:A EIGRP Routers [Farinacci] FF02:0:0:0:0:0:1:2 All-dhcp-agents [RFC3315] Site-Local Scope ---------------- FF05:0:0:0:0:0:0:2 All Routers Address [RFC4291] FF05:0:0:0:0:0:1:3 All-dhcp-servers [RFC3315] Variable Scope Multicast Addresses ---------------------------------- The IPv6 multicast addresses with variable scope are listed below. FF0X:0:0:0:0:0:0:0 Reserved Multicast Address [RFC4291] FF0X:0:0:0:0:0:0:101 Network Time Protocol (NTP) [RFC1119,DLM1] FF0X:0:0:0:0:0:0:103 Rwhod [SXD] FF0X:0:0:0:0:0:0:10A IETF-1-LOW-AUDIO [SC3] FF0X:0:0:0:0:0:0:10B IETF-1-AUDIO [SC3] FF0X:0:0:0:0:0:0:10C IETF-1-VIDEO [SC3] FF0X:0:0:0:0:0:0:10D IETF-2-LOW-AUDIO [SC3] FF0X:0:0:0:0:0:0:10E IETF-2-AUDIO [SC3] FF0X:0:0:0:0:0:0:10F IETF-2-VIDEO [SC3]
- #7: The allocated anycast addresses are references in http://www.iana.org/assignments/ipv6-anycast-addresses
- #9: The IPv6 packet format is described in S. Deering, B. Hinden, Internet Protocol, Version 6 (IPv6) Specification , RFC2460, Dec 1998 Several documents have been written about the usage of the Flow label. The last one is J. Rajahalme, A. Conta, B. Carpenter, S. Deering, IPv6 Flow Label Specification, RFC3697, 2004 However, this proposal is far from being widely used and deployed.
- #10: IPv6 does not require changes to TCP and UDP for IPv4. The only modification is the computation of the checksum field of the UDP and TCP headers since this checksum is computed by concerning a pseudo header that contains the source and destination IP addresses.
- #13: An example hop-by-hop option is the router alert option defined in A. Jackson, C. Partridge, IPv6 Router Alert Option RFC2711, 1999
- #14: The Type 0 Routing header is specified in RFC2460 Two other types of routing headers have been defined. Type 1 is experimental and never used. Type 2 is specific for Mobile IPv6 that will be covered later.
- #16: The type 0 routing header was deprecated in J. Abley, P. Savola, G. Neville-Neil, Deprecation of Type 0 Routing Headers in IPv6 RFC5095, Dec. 2007 For more information about the security issues with this header, see Biondi, P. and A. Ebalard, "IPv6 Routing Header Security", CanSecWest Security Conference 2007, April 2007. http://www.secdev.org/conf/IPv6_RH_security-csw07.pdf
- #20: The Len field encodes the size of the data field in bytes. Furthermore, special options have been defined to allow hosts using the options to pad the size of vairable length options to multiples of 64 bits. Pad1 option (alignment requirement: none) +-+-+-+-+-+-+-+-+ | 0 | +-+-+-+-+-+-+-+-+ NOTE! the format of the Pad1 option is a special case -- it does not have length and value fields. The Pad1 option is used to insert one octet of padding into the Options area of a header. If more than one octet of padding is required, the PadN option, described next, should be used, rather than multiple Pad1 options. Deering & Hinden Standards Track [Page 10] RFC 2460 IPv6 Specification December 1998 PadN option (alignment requirement: none) +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- - - - - - - - - | 1 | Opt Data Len | Option Data +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- - - - - - - - - The PadN option is used to insert two or more octets of padding into the Options area of a header. For N octets of padding, the Opt Data Len field contains the value N-2, and the Option Data consists of N-2 zero-valued octets.
- #21: As of today, it is unclear whether the jumbogram option has been implemented in practice. Using it requires link layer technologies that are able to support frames larger than 64 KBytes. The jumbogram option has been defined in D. Borman, S. Deering, B. Hinden, IPv6 Jumbograms, RFC2675, August 1999 The Kame (http://www.kame.net) implementation on FreeBSD supports this option, but there is no link-layer that supports large frames.
- #23: Path MTU discovery is defined in J. Mogul, S. Deering, Path MTU Discovery, RFC1191, 1996 and in J. McCann, S. Deering, J. Mogul, Path MTU Discovery for IP version 6, RFC1981, 1996 for IPv6
- #25: In IPv6, the fragment identification field is much larger than in IPv4. Furthermore, it is only used in packets that really need fragmentation. IPv6 header does not contain a fragmentation information for each unfragmented packet unlike IPv4.
- #26: IPv6 does not require changes to TCP and UDP for IPv4. The only modification is the computation of the checksum field of the UDP and TCP headers since this checksum is computed by concerning a pseudo header that contains the source and destination IP addresses.
- #28: ICMPv6 is defined in : A. Conta, S. Deering, M. Gupta, Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification, RFC4443, March 2006
- #29: ICMPv6 uses a next header value of 58 inside IPv6 packets
- #35: The IPv6 packet format is described in S. Deering, B. Hinden, Internet Protocol, Version 6 (IPv6) Specification , RFC2460, Dec 1998 Several documents have been written about the usage of the Flow label. The last one is J. Rajahalme, A. Conta, B. Carpenter, S. Deering, IPv6 Flow Label Specification, RFC3697, 2004 However, this proposal is far from being widely used and deployed.
- #40: The transmission of IPv6 packets over Ethernet is defined in : M. Crawford, Transmission of IPv6 Packets over Ethernet Networks, RFC2464, December 1998 Note that in contrast with ARP used by IPv4, ICMPv6 neighbour solicitation messages are sent to a multicast ethernet address and not to the broadcast ethernet address. This implies that only the IPv6 enabled hosts on the LAN will receive the ICMPv6 message.
- #46: Source http://www.dante.net
- #47: Source http://www.uu.net
- #53: For more information on the organization of the Internet, see : G. Huston, Peerings and settlements, Internet Protocol Journal, Vol. 2, N1 et 2, 1999, http://www.cisco.com/warp/public/759/ipj_Volume2.html For more information on interconnection points or Internet exchanges, see : http://www.euro-ix.net/ http://www.ripe.net/ripe/wg/eix/index.html http://www.ep.net/ep-main.html
- #59: On link AS7-AS4 AS7 advertises its own routes to AS4 AS4 advertises to AS7 the routes that allow to reach the entire Internet On link AS4-AS2 AS4 advertises its own routes and the routes belonging to AS7 AS2 advertises the routes that allow to reach the entire Internet
- #61: On link AS3-AS4 AS3 advertises its internal routes AS4 advertises its internal routes and the routes learned from AS7 (its customer) On link AS1-AS2 AS1 advertises its internal routes and the routes received from AS3 and AS4 (its customers) AS2 advertises its internal routes and the routes learned from AS74(its customer)
- #62: RFC 2622 Routing Policy Specification Language (RPSL). C. Alaettinoglu, C. Villamizar, E. Gerich, D. Kessens, D. Meyer, T. Bates, D. Karrenberg, M. Terpstra. June 1999. RFC 2650 Using RPSL in Practice. D. Meyer, J. Schmitz, C. Orange, M. Prior, C. Alaettinoglu. August 1999. Internet Routing Registries contain the routing policies of various ISPs, see : http://www.ripe.net/ripencc/pub-services/whois.html http://www.arin.net/whois/index.html http://www.apnic.net/apnic-bin/whois.pl
- #67: The ICMPv6 neighbour discovery messages are sent with HopLimit=255 The role of the R, S and O flags is described as follows in RFC4861 R Router flag. When set, the R-bit indicates that the sender is a router. The R-bit is used by Neighbor Unreachability Detection to detect a router that changes to a host. S Solicited flag. When set, the S-bit indicates that the advertisement was sent in response to a Neighbor Solicitation from the Destination address. The S-bit is used as a reachability confirmation for Neighbor Unreachability Detection. It MUST NOT be set in multicast advertisements or in unsolicited unicast advertisements. O Override flag. When set, the O-bit indicates that the advertisement should override an existing cache entry and update the cached link-layer address. When it is not set the advertisement will not update a cached link-layer address though it will update an existing Neighbor Cache entry for which no link-layer address is known. It SHOULD NOT be set in solicited advertisements for anycast addresses and in solicited proxy advertisements. It SHOULD be set in other solicited advertisements and in unsolicited advertisements.
- #68: When the M bit is set to true, this indicates that IPv6 addresses should be obtained from DHCPv6 When the O bit is set to true, this indicates that the hosts can obtain additional information (e.g. address of DNS resolver) from DHCPv6 The router advertisements messages can also be sent in unicast in response to solicitations from hosts. A host can obtain a router advertisement by sending a router solicitation which is an ICMPv6 message containing only the router solicitation message (type 133).
- #69: The two L and A bits are defined as follows : L 1-bit on-link flag. When set, indicates that this prefix can be used for on-link determination. When not set the advertisement makes no statement about on-link or off-link properties of the prefix. In other words, if the L flag is not set a host MUST NOT conclude that an address derived from the prefix is off-link. That is, it MUST NOT update a previous indication that the address is on-link. A 1-bit autonomous address-configuration flag. When set indicates that this prefix can be used for stateless address configuration. Other options have been defined for the router advertisements. For example, the RDNSS option defined in J. Jeong, S. Park, L. Beloeil, S. Madanapalli, IPv6 Router Advertisement Option for DNS Configuration, RFC 5006, Sept. 2007 allows a router to advertise the IPv6 address of the DNS resolver to be used by hosts on the LAN.
- #70: This utilisation of ICMPv6 Neighbour solicitation is called Duplicate Address Detection. It is used everytime a host obtains a new IPv6 address and is required to ensure that a host is not using the same IPv6 address as another host on the same LAN.
- #72: IPv6 is supposed to easily support renumbering and IPv6 router advertisements are one of the ways to perform this renumbering by allowing hosts to update their IPv6 addresses upon reception of new router advertisement messages. However, in practice renumbering an IPv6 network is not easily because IPv6 addresses are manually encoded in too many configuration files, see e.g. : F. Baker, E. Lear, R. Droms, Procedures for Renumbering an IPv6 Network without a Flag Day, RFC4192, 2005
- #73: This extension to support privacy-aware IPv6 addresses is defined in T. Narten, R. Draves, S. Krishnan, Privacy Extensions for Stateless Address Autoconfiguration in IPv6, RFC4941, Sept. 2007