[trill] I-D Action: draft-ietf-trill-centralized-replication-13.txt

internet-drafts@ietf.org Thu, 25 January 2018 08:25 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: trill@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151686870314.15842.4492839976381891677@ietfa.amsl.com>
Date: Thu, 25 Jan 2018 00:25:03 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/cR7-HEAt8ovmJ1n7R3rG3FS3ffQ>
Subject: [trill] I-D Action: draft-ietf-trill-centralized-replication-13.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Transparent Interconnection of Lots of Links WG of the IETF.

        Title           : Centralized Replication for Active-Active BUM Traffic
        Authors         : Weiguo Hao
                          Yizhou Li
                          Muhammad Durrani
                          Sujay Gupta
                          Andrew Qu
	Filename        : draft-ietf-trill-centralized-replication-13.txt
	Pages           : 17
	Date            : 2018-01-25

Abstract:
   In TRILL active-active access, an RPF (Reverse Path Forwarding) check
   failure issue may occur when using the pseudo-nickname mechanism
   specified in RFC 7781. This draft describes a solution to resolve
   this RPF check failure issue through centralized replication. All
   ingress RBridges send BUM (Broadcast, Unknown unicast and Multicast)
   traffic to a centralized node with unicast TRILL encapsulation.
   When the centralized node receives the BUM traffic, it decapsulates
   the packets and forwards them to their destination RBridges using
   a distribution tree established as per TRILL base protocol RFC 6325.
   To avoid RPF check failure on a RBridge sitting between the ingress
   RBridge and the centralized replication node, some change in the
   RPF calculation algorithm is required. RPF checks on each RBridge
   MUST be calculated as if the centralized node was the ingress
   RBridge, instead of being calculated using the actual ingress
   RBridge. This document updates RFC 6325.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-trill-centralized-replication/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-trill-centralized-replication-13
https://datatracker.ietf.org/doc/html/draft-ietf-trill-centralized-replication-13

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-trill-centralized-replication-13


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

[trill] I-D Action: draft-ietf-trill-centralized-… internet-drafts