Subject: [trill] Problem Statement: TRILL Active/Active Edge

From: Mingui Zhang <[email-masked]>
Date: Tue, 19 Feb 2013 00:36:13 +0000

Dear All,

The Problem-Statement draft has been submitted as promised. This draft aims to make clear what problems need be addressed after active/active edge is introduced to TRILL. 

Whether we have left anything out, whether the ideas in the document are accurate? We'd happy to receive your comments.

Thanks,
Mingui

A new version of I-D, draft-zhang-trill-aggregation-03.txt
has been successfully submitted by Mingui Zhang and posted to the IETF repository.

Filename:	 draft-zhang-trill-aggregation
Revision:	 03
Title:		 Problem Statement: TRILL Active/Active Edge
Creation date:	 2013-02-18
Group:		 Individual Submission
Number of pages: 12
URL:             http://www.ietf.org/internet-drafts/draft-zhang-trill-aggregation-03.txt
Status:          http://datatracker.ietf.org/doc/draft-zhang-trill-aggregation
Htmlized:        http://tools.ietf.org/html/draft-zhang-trill-aggregation-03
Diff:            http://www.ietf.org/rfcdiff?url2=draft-zhang-trill-aggregation-03

Abstract:
   This document specifies TRILL active/active edge which allows
   multiple RBridges concurrently forward data frames of the same VLAN
   on links bundled by Link Aggregation. With this kind of connection,
   end nodes may increase the bandwidth and reliability of the access at
   the edge of TRILL campuses. It's required that no loop or duplication
   is caused by this new connection type. Besides this basic
   requirement, this document outlines other potential issues associated
   with TRILL active/active edge and investigates how these issues may
   be addressed.

The IETF Secretariat