Timeline for Why is an IPv6 interface required to have a link-local address?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 9, 2020 at 11:36 | vote | accept | sjy | ||
| Dec 7, 2020 at 0:27 | history | edited | Ron Maupin♦ | edited tags | |
| Dec 7, 2020 at 0:25 | answer | added | Ron Maupin♦ | timeline score: 3 | |
| Jun 28, 2020 at 16:35 | comment | added | Ron Maupin♦ | DHCPv6 is very different than DHCPv4: "The availability of these features means that a client can use its link-local address and a well-known multicast address to discover and communicate with DHCP servers or relay agents on its link." IPv6 Link-Local addressing is used for many things, and the question of , "Why?" needs to be asked of the IETF (you can find the authors on the RFCs). Anyone here answering will just be guessing and speculating, which is off-topic here. | |
| Jun 28, 2020 at 12:37 | comment | added | Ricky | Because they are required for the internal functioning of various protocol components. No one RFC lists all of those various components. It's a fundamental part of the protocol, so it's always available for anything one can dream up. One simple case: routing is always done to the link-local address of the RA origin. (static routes are up to the user.) | |
| Jun 28, 2020 at 9:57 | history | asked | sjy | CC BY-SA 4.0 |