Subject: [trill] New Version Notification for draft-hao-trill-centralized-replication-00.txt

From: Haoweiguo <[email-masked]>
Date: Wed, 11 Dec 2013 07:03:01 +0000

Dear all,
I have just posted a new draft of  "Centralized Replication for BUM traffic in active-active edge connection".
The solution in this draft can solve RPF check failure issue introduced by pseudonickname concept.
Your reading and comments are welcomed!
thanks
weiguo

________________________________________
发件人: [email-masked] [[email-masked]]
发送时间: 2013年12月11日 14:59
收件人: Haoweiguo; Liyizhou; hantao 00223943; Haoweiguo; Liyizhou
主题: New Version Notification for draft-hao-trill-centralized-replication-00.txt

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

Filename:        draft-hao-trill-centralized-replication
Revision:        00
Title:           Centralized Replication for BUM traffic in active-active edge connection
Creation date:   2013-12-11
Group:           Individual Submission
Number of pages: 14
URL:             http://www.ietf.org/internet-drafts/draft-hao-trill-centralized-replication-00.txt
Status:          http://datatracker.ietf.org/doc/draft-hao-trill-centralized-replication
Htmlized:        http://tools.ietf.org/html/draft-hao-trill-centralized-replication-00

Abstract:
   In TRILL active-active access scenario, RPF check failure issue may
   occur when pseduonode nickname mechanism in [TRILLPN] is used. This
   draft is to solve RPF check failure issue through centralized
   replication for BUM traffic solution. The basic idea is that all
   ingress RBs send BUM traffic to a centralized node through unicast
   TRILL encapsulation, the centralized node decapsulates the unicast
   TRILL packet. Then the centralized node searches its multicast
   forwarding table to replicates a copy of the BUM traffic to
   destination RBs through TRILL unicast encapsulation. Through
   centralized replication solution, only unicast forwarding behavior is
   required between edge RB and centralized RB, so no RPF check function
   is required on any device in TRILL campus through centralized
   replication solution and no RPF check failure issue occurs.

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.

The IETF Secretariat