IETF Logo Mail Archive

Re: [trill] ESADI 1. Simplify ESADI Neighbor determination

zhai.hongjun@zte.com.cn Wed, 09 January 2013 03:15 UTC

Return-Path: <zhai.hongjun@zte.com.cn>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1184E1F0CAF; Tue, 8 Jan 2013 19:15:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -95.51
X-Spam-Level:
X-Spam-Status: No, score=-95.51 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, USER_IN_WHITELIST=-100, WEIRD_QUOTING=1.396]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zfacdKik9qg7; Tue, 8 Jan 2013 19:15:40 -0800 (PST)
Received: from zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id C043C1F0C5F; Tue, 8 Jan 2013 19:15:39 -0800 (PST)
Received: from zte.com.cn (unknown [192.168.168.119]) by Websense Email Security Gateway with ESMTP id E511819387A2; Wed, 9 Jan 2013 11:15:27 +0800 (CST)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Websense Email Security Gateway with ESMTPS id 508507033D1; Wed, 9 Jan 2013 11:05:16 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id r093FGbr055191; Wed, 9 Jan 2013 11:15:16 +0800 (GMT-8) (envelope-from zhai.hongjun@zte.com.cn)
In-Reply-To: <CAHD03N_kFtW12cDSTbL1FYq1n8fWzrWho2t=LSHK1ESoPzWOuA@mail.gmail.com>
To: Ayan Banerjee <ayabaner@gmail.com>
MIME-Version: 1.0
X-KeepSent: 8321E15A:57F0D3DF-48257AEE:0010C37F; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF8321E15A.57F0D3DF-ON48257AEE.0010C37F-48257AEE.00122CC4@zte.com.cn>
From: zhai.hongjun@zte.com.cn
Date: Wed, 09 Jan 2013 11:15:17 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2013-01-09 11:15:13, Serialize complete at 2013-01-09 11:15:13
Content-Type: multipart/alternative; boundary="=_alternative 00122CC148257AEE_="
X-MAIL: mse01.zte.com.cn r093FGbr055191
Cc: Donald Eastlake <d3e3e3@gmail.com>, trill-bounces@ietf.org, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] ESADI 1. Simplify ESADI Neighbor determination
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/trill>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2013 03:15:41 -0000

I agree.


Best Regards,
Zhai Hongjun
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
 Protocol Development Dept.VI, Central R&D Institute, ZTE Corporation
 No. 68, Zijinghua Road, Yuhuatai District, Nanjing, P.R.China, 210012
 
 Zhai Hongjun
 
 Tel: +86-25-52877345
 Email: zhai.hongjun@zte.com.cn
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""





Ayan Banerjee <ayabaner@gmail.com> 
发件人:  trill-bounces@ietf.org
2013-01-09 04:51

收件人
Donald Eastlake <d3e3e3@gmail.com>
抄送
"trill@ietf.org" <trill@ietf.org>
主题
Re: [trill] ESADI 1. Simplify ESADI Neighbor determination






This would be a nice change to have, since the intent to participate is 
already present in the LSP on the core instance. 

Thanks,
Ayan


On Mon, Jan 7, 2013 at 7:25 PM, Donald Eastlake <d3e3e3@gmail.com> wrote:
1. Simplify ESADI Neighbor determination

      The current draft requires that RBridge RB1 consider RB2 an ESADI
      neighbor for VLAN-X only if three conditions are met: (1) RB2 is
      data reachable from RB1, (2) RB2 has the ESADI participation bit
      on in its Interested VLANs sub-TLV for VLAN-X, and (3) RB1 is
      holding ESADI-LSP fragment zero for RB2. This last requirement (3)
      increases the state complexity of ESADI and the suggestion is
      that it be eliminated. If RB1 does not hold an ESADI-LSP fragment
      zero with an ESADI Parameters APPsub-TLV in it for RB2, then it
      treats RB2 as having default priority and CSNP time.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com
_______________________________________________
trill mailing list
trill@ietf.org
https://www.ietf.org/mailman/listinfo/trill
_______________________________________________
trill mailing list
trill@ietf.org
https://www.ietf.org/mailman/listinfo/trill

v2.23.0 | Report a Bug | By Email