This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| RFC 4861 | |
|---|---|
| Title | RFC 4861 |
| Series | Request for Comments |
| Number | 4861 |
| Year | 2007 |
| Status | Proposed Standard |
| Authors | N. Montemurro, T. Narten, E. Nordmark |
| Related | IPv6, Neighbor Discovery Protocol, ICMPv6 |
RFC 4861
RFC 4861 specifies the Neighbor Discovery Protocol for IPv6, defining mechanisms for address resolution, neighbor reachability, duplicate address detection, router discovery, and address autoconfiguration. It updates prior standards and integrates with the Internet Protocol version 6 architecture, influencing implementations across operating systems and network equipment vendors. The document sits within the standards-track RFC series produced by the Internet Engineering Task Force and informs protocol behavior used in global internetworking.
RFC 4861 updates and clarifies procedures originally defined in earlier IETF workstreams and informs implementers such as kernel teams at Linux distributions, networking groups within Cisco Systems, and protocol engineers at Juniper Networks. It is part of the IETF standards trajectory alongside documents from the Internet Engineering Task Force and the Internet Architecture Board. The specification addresses interactions with protocols and systems such as ICMPv6, IPv6, and link-layer technologies employed by vendors like Intel Corporation and Broadcom Corporation.
The purpose of RFC 4861 is to consolidate Neighbor Discovery behavior for IPv6 following operational experience from deployments in environments managed by organizations like ARIN, RIPE NCC, and APNIC. It responds to design considerations discussed in IETF working groups including the IPv6 Maintenance (6man) Working Group and relates to operational guidance produced by entities such as NIST and standards activities in IEEE 802. The protocol addresses practical needs faced by implementers at Microsoft and open-source communities like the FreeBSD and NetBSD projects, ensuring interoperability among routers produced by Huawei and Hewlett-Packard Enterprise.
Neighbor Discovery, as defined in RFC 4861, operates over IPv6 and relies on ICMPv6 messages to perform functions historically handled by ARP in IPv4 networks. The protocol supports mechanisms for router advertisement and solicitation employed by devices ranging from Apple Inc. laptops to enterprise switches by Arista Networks. It defines state machines and message exchanges that influence stack implementations in projects like OpenBSD and network stacks used by embedded vendors such as Qualcomm.
RFC 4861 specifies message types including Router Solicitation, Router Advertisement, Neighbor Solicitation, Neighbor Advertisement, and Redirect, each carried in ICMPv6 payloads. Message formats incorporate options such as the source link-layer address and target link-layer address options used by implementations from Cisco Systems and Juniper Networks. The specification also integrates with standards developed by IEEE for link-layer addresses and aligns with address allocation practices overseen by regional registries including LACNIC.
Procedures defined include duplicate address detection, neighbor unreachability detection, address resolution, and router selection. These procedures inform behavior in client platforms like Android (operating system), server operating systems such as Red Hat Enterprise Linux, and virtualized environments orchestrated by VMware. Router advertisement timing, prefix information options, and lifetime semantics are detailed to ensure compatibility with routing platforms from Cisco Systems, cloud providers like Amazon Web Services, and carrier networks operated by companies such as Verizon Communications.
RFC 4861 discusses threats including spoofing, neighbor cache poisoning, and denial-of-service, recommending mitigations that include Secure Neighbor Discovery extensions developed in related IETF workstreams and integration with cryptographic mechanisms advocated by IETF Security Area participants. Security guidance is relevant to implementations in platforms maintained by Google and secure modules developed by firms like Fortinet. The document’s security considerations influenced subsequent specifications and operational practices adopted by entities such as CERT Coordination Center and national cybersecurity agencies.
Implementations of the Neighbor Discovery Protocol as specified in RFC 4861 appear in operating systems and network device firmware produced by Microsoft, Apple Inc., Canonical (company), and open-source projects including Linux kernel networking, OpenWrt, and FreeBSD. Deployment experience from service providers like AT&T and content networks such as Cloudflare informed errata and clarifications. The protocol’s behavior impacts configuration tools and management systems used by network operators trained via organizations such as The Open Group and certified by programs like Cisco Networking Academy.
RFC 4861 established a common foundation for IPv6 neighbor operations, shaping subsequent related work including security enhancements and practical interoperability tests run by consortiums like the IPv6 Forum. Its influence extends to academic research at institutions such as MIT and Stanford University and to commercial IPv6 adoption tracked by bodies like IETF and regional registries. The document’s legacy persists in modern network stacks, router firmware, and cloud networking fabrics implemented by providers like Google Cloud Platform and Microsoft Azure, and continues to inform protocol evolution in the Internet standards community.
Category:Internet standards