RFC 7586 on The Scalable Address Resolution Protocol (SARP) for Large Data Centers
rfc-editor@rfc-editor.org Mon, 22 June 2015 18:36 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C83F21A1A3D for <ietf-announce@ietfa.amsl.com>; Mon, 22 Jun 2015 11:36:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.013
X-Spam-Level:
X-Spam-Status: No, score=-100.013 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 646x9fxtMsot for <ietf-announce@ietfa.amsl.com>; Mon, 22 Jun 2015 11:36:02 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 5173E1A19E5 for <ietf-announce@ietf.org>; Mon, 22 Jun 2015 11:36:02 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 07C71180452; Mon, 22 Jun 2015 11:33:17 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7586 on The Scalable Address Resolution Protocol (SARP) for Large Data Centers
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150622183317.07C71180452@rfc-editor.org>
Date: Mon, 22 Jun 2015 11:33:17 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/ZUwmdbwxa2PHjplTgkM8Cdn9IwM>
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Jun 2015 18:36:03 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7586
Title: The Scalable Address Resolution Protocol
(SARP) for Large Data Centers
Author: Y. Nachum, L. Dunbar,
I. Yerushalmi, T. Mizrahi
Status: Experimental
Stream: Independent
Date: June 2015
Mailbox: youval.nachum@gmail.com,
ldunbar@huawei.com,
yilan@marvell.com,
talmi@marvell.com
Pages: 21
Characters: 44538
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-nachum-sarp-11.txt
URL: https://www.rfc-editor.org/info/rfc7586
DOI: http://dx.doi.org/10.17487/RFC7586
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.
EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community. It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC