RFC 7586: The Scalable Address Resolution Protocol (SARP) for Large Data Centers
In plain English — editorial summary, not part of the RFC
This document introduces the Scalable Address Resolution Protocol (SARP), an architecture that uses proxy gateways to scale large data center networks. SARP is based on fast proxies that significantly reduce switches' Filtering Database (FDB) table sizes and reduce impact of ARP and Neighbor Discovery (ND) on network elements in an environment where hosts within one subnet (or VLAN) can spread over various locations. SARP is targeted for massive data centers with a significant number of Virtual Machines (VMs) that can move across various physical locations.
Document record
- Document ID
- RFC7586
- Published
- June 2015
- Authors
- Y. Nachum; L. Dunbar; I. Yerushalmi; T. Mizrahi
- Status
- EXPERIMENTAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 21
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6820Address Resolution Problems in Large Data Center NetworksCurrent
January 2013
- RFC 8743Multiple Access Management Services Multi-Access Management Services (MAMS)Current
March 2020
- RFC 4562MAC-Forced Forwarding: A Method for Subscriber Separation on an Ethernet Access NetworkCurrent
June 2006
- RFC 7755SIIT-DC: Stateless IP/ICMP Translation for IPv6 Data Center EnvironmentsCurrent
February 2016
- RFC 7756Stateless IP/ICMP Translation for IPv6 Internet Data Center Environments (SIIT-DC): Dual Translation ModeCurrent
February 2016
- RFC 7239Forwarded HTTP ExtensionCurrent
June 2014
- RFC 7956Transparent Interconnection of Lots of Links (TRILL) Distributed Layer 3 GatewayCurrent
September 2016
- RFC 8041Use Cases and Operational Experience with Multipath TCPCurrent
January 2017
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?