RFC 8302 on Transparent Interconnection of Lots of Links (TRILL): ARP and Neighbor Discovery (ND) Optimization
rfc-editor@rfc-editor.org Sat, 06 January 2018 00:02 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE74612DA18; Fri, 5 Jan 2018 16:02:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 CIa6M0GUQucg; Fri, 5 Jan 2018 16:02:44 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9FA8E12DA09; Fri, 5 Jan 2018 16:02:40 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id B138CB81EDB; Fri, 5 Jan 2018 16:02:23 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8302 on Transparent Interconnection of Lots of Links (TRILL): ARP and Neighbor Discovery (ND) Optimization
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, trill@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180106000223.B138CB81EDB@rfc-editor.org>
Date: Fri, 05 Jan 2018 16:02:23 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/QSK33TCii1H71UdnvCAfRXzzx50>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
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: Sat, 06 Jan 2018 00:02:53 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8302
Title: Transparent Interconnection of Lots of
Links (TRILL): ARP and Neighbor Discovery
(ND) Optimization
Author: Y. Li,
D. Eastlake 3rd,
L. Dunbar,
R. Perlman,
M. Umair
Status: Standards Track
Stream: IETF
Date: January 2018
Mailbox: liyizhou@huawei.com,
d3e3e3@gmail.com,
ldunbar@huawei.com,
radia@alum.mit.edu,
mohammed.umair2@gmail.com
Pages: 18
Characters: 41883
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-trill-arp-optimization-09.txt
URL: https://www.rfc-editor.org/info/rfc8302
DOI: 10.17487/RFC8302
This document describes mechanisms to optimize the Address Resolution
Protocol (ARP) and Neighbor Discovery (ND) traffic in a Transparent
Interconnection of Lots of Links (TRILL) campus. TRILL switches
maintain a cache of IP / Media Access Control (MAC) address / Data
Label bindings that are learned from ARP/ND requests and responses
that pass through them. In many cases, this cache allows an edge
Routing Bridge (RBridge) to avoid flooding an ARP/ND request by
either responding to it directly or encapsulating it and unicasting
it. Such optimization reduces packet flooding over a TRILL campus.
This document is a product of the Transparent Interconnection of Lots of Links Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. 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/retrieve/bulk
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