Re: [trill] New Version Notification for draft-ietf-trill-centralized-replication-01.txt

Haoweiguo <> Tue, 10 February 2015 05:43 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id D55B21A8F3D for <>; Mon, 9 Feb 2015 21:43:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.217
X-Spam-Status: No, score=-3.217 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FS_REPLICA=0.994, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id vaTOo6XnJHmn for <>; Mon, 9 Feb 2015 21:43:47 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 64C501A8BBD for <>; Mon, 9 Feb 2015 21:43:46 -0800 (PST)
Received: from (EHLO ([]) by (MOS 4.3.7-GA FastPath queued) with ESMTP id BPC51751; Tue, 10 Feb 2015 05:43:44 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Tue, 10 Feb 2015 05:43:43 +0000
Received: from ([]) by ([]) with mapi id 14.03.0158.001; Tue, 10 Feb 2015 13:43:30 +0800
From: Haoweiguo <>
To: "" <>
Thread-Topic: New Version Notification for draft-ietf-trill-centralized-replication-01.txt
Thread-Index: AQHQRPPmSCXcUJL5C0CpI3GIs2kR9pzpXfiP
Date: Tue, 10 Feb 2015 05:43:29 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US, zh-CN
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Cc: Muhammad Durrani <>, Sujay Gupta <>, Andrew Qu <>, Liyizhou <>, hantao 00223943 <>
Subject: Re: [trill] New Version Notification for draft-ietf-trill-centralized-replication-01.txt
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Developing a hybrid router/bridge." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 10 Feb 2015 05:43:49 -0000

Hi All,
We have just posted a updated version(01) of draft-ietf-trill-centralized-replication. In this draft, CMT and centralized replication co-existing method is provided in Section 9. Section11 is changed to introduce "C"flag in Nickname Flags APPsub-TLV.
Any comments and suggestions are appriciated.

From: []
Sent: Tuesday, February 10, 2015 13:38
To: Andrew Qu; Liyizhou; Muhammad Durrani; Haoweiguo; Sujay Gupta; Sujay Gupta; hantao 00223943; hantao 00223943; Liyizhou; Andrew Qu; Muhammad Durrani; Haoweiguo
Subject: New Version Notification for draft-ietf-trill-centralized-replication-01.txt

A new version of I-D, draft-ietf-trill-centralized-replication-01.txt
has been successfully submitted by Weiguo Hao and posted to the
IETF repository.

Name:           draft-ietf-trill-centralized-replication
Revision:       01
Title:          Centralized Replication for BUM traffic in active-active edge connection
Document date:  2015-02-10
Group:          trill
Pages:          14

   In TRILL active-active access scenario, RPF check failure issue may
   occur when pseudo-nickname mechanism in [TRILLPN] is used. This
   draft describes a solution to the RPF check failure issue through
   centralized replication for BUM (Broadcast, Unknown unicast,
   Mutlicast) traffic. The solution has all ingress RBs send BUM
   traffic to a centralized node via unicast TRILL encapsulation. When
   the centralized node receives the BUM traffic, it decapsulates the
   traffic and forwards the BUM traffic to all destination RBs using a
   distribution tree established via the TRILL base protocol. To avoid
   RPF check failure on a RBridge sitting between the ingress RBridge
   and the centralized replication node, some change of RPF calculation
   algorithm is required. RPF calculation on each RBridge should use
   the centralized node as ingress RB instead of the real ingress
   RBridge of RBv to perform the calculation.

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

The IETF Secretariat