RFC 6583: Operational Neighbor Discovery Problems

In IPv4, subnets are generally small, made just large enough to cover the actual number of machines on the subnet. In contrast, the default IPv6 subnet size…

Read RFC 6583 on the RFC Editor

Outgoing relationships (5 related RFCs)

Normative reference — RFC 4861: Neighbor Discovery for IP version 6 (IPv6)
Normative reference — RFC 4862: IPv6 Stateless Address Autoconfiguration
Normative reference — RFC 6164: Using 127-Bit IPv6 Prefixes on Inter-Router Links
Informative reference — RFC 4732: Internet Denial-of-Service Considerations
Informative reference — RFC 5157: IPv6 Implications for Network Scanning

Incoming relationships (12 related RFCs)

Normatively referenced by — RFC 9386: IPv6 Deployment Status
Normatively referenced by — RFC 8161: Benchmarking the Neighbor Discovery Protocol
Informatively referenced by — RFC 7707: Network Reconnaissance in IPv6 Networks
Informatively referenced by — RFC 9099: Operational Security Considerations for IPv6 Networks
Informatively referenced by — RFC 6820: Address Resolution Problems in Large Data Center Networks
Informatively referenced by — RFC 7421: Analysis of the 64-bit Boundary in IPv6 Addressing
Informatively referenced by — RFC 7381: Enterprise IPv6 Deployment Guidelines
Informatively referenced by — RFC 9131: Gratuitous Neighbor Discovery: Creating Neighbor Cache Entries on First-Hop Routers
Informatively referenced by — RFC 7048: Neighbor Unreachability Detection Is Too Impatient
Informatively referenced by — RFC 7814: Virtual Subnet: A BGP/MPLS IP VPN-Based Subnet Extension Solution
Informatively referenced by — RFC 9365: IPv6 Wireless Access in Vehicular Environments (IPWAVE): Problem Statement and Use Cases
Informatively referenced by — RFC 9898: Neighbor Discovery Considerations in IPv6 Deployments