
From zhai.hongjun@zte.com.cn  Fri Feb  1 00:30:51 2013
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 DDB2921F8479; Fri,  1 Feb 2013 00:30:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.999
X-Spam-Level: 
X-Spam-Status: No, score=-96.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 mBl9Pd6Kt7tV; Fri,  1 Feb 2013 00:30:51 -0800 (PST)
Received: from zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id 9450421F84B2; Fri,  1 Feb 2013 00:30:50 -0800 (PST)
Received: from zte.com.cn (unknown [192.168.168.119]) by Websense Email Security Gateway with ESMTP id 4B0BA116E137; Fri,  1 Feb 2013 16:30:22 +0800 (CST)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Websense Email Security Gateway with ESMTPS id 13398183B183; Fri,  1 Feb 2013 16:32:12 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id r118UJaB008779; Fri, 1 Feb 2013 16:30:19 +0800 (GMT-8) (envelope-from zhai.hongjun@zte.com.cn)
In-Reply-To: <CAFOuuo5rHyAuQ1C6AWoYnkbG3T-if9cm8kS4MzWHdxS06Z6A1A@mail.gmail.com>
To: Radia Perlman <radiaperlman@gmail.com>
MIME-Version: 1.0
X-KeepSent: 10A7CD42:BA5BB6D9-48257B05:002CFA0F; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF10A7CD42.BA5BB6D9-ON48257B05.002CFA0F-48257B05.002F1199@zte.com.cn>
From: zhai.hongjun@zte.com.cn
Date: Fri, 1 Feb 2013 16:30:24 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2013-02-01 16:30:11, Serialize complete at 2013-02-01 16:30:11
Content-Type: multipart/alternative; boundary="=_alternative 002F119548257B05_="
X-MAIL: mse01.zte.com.cn r118UJaB008779
Cc: trill-bounces@ietf.org, Anoop Ghanwani <anoop@alumni.duke.edu>, Ayan Banerjee <ayabaner@gmail.com>, Sam Aldrin <aldrin.ietf@gmail.com>, "Tissa Senevirathne \(tsenevir\)" <tsenevir@cisco.com>, "trill@ietf.org" <trill@ietf.org>, Donald Eastlake <d3e3e3@gmail.com>, Jon Hudson <jon.hudson@gmail.com>
Subject: Re: [trill] A tweak to option 2, if it's hard to upgrade VL guys to FGL-safe
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: Fri, 01 Feb 2013 08:30:52 -0000

This is a multipart message in MIME format.
--=_alternative 002F119548257B05_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

QXMgRkdMIGZyYW1lcyBhbmQgVkwgZnJhbWVzIGhhdmUgZGlmZmVyZW50IEV0aGVydHlwZSwgaXQg
aXMgZWFzeSBmb3IgDQpGR0wtc2FmZSBSQnJpZGdlcyB0byBkaWZmZXJlbnRpYXRlIHRoZSB0d28g
dHlwZXMgb2YgZnJhbWVzIGluIGRhdGEgcGxhbmUuIA0KQW5kIHRoZSB0d2Vha2VkIE9wdGlvbiAy
IGFsbG93cyBWTC1SQnJpZGdlcyBleGl0aW5nIGF0IHRoZSBlZGdlIG9mIGEgDQpuZXdvcmsgd2l0
aCBGR0wgbGlua3MgaWYgdGhlaXIgRkdMLXNhZmUgbmVpZ2hib3JzIGNhbiBkaWZmZXJlbnRpYXRl
IHRoZSANCnR3byB0eXBlIGZyYW1lcywgSSBhbSBoYXBweSB3aXRoIGl0Lg0KDQpTbywgSSBzdXBw
b3J0IHRoaXMgdHdlYWtlZCBvcHRpb24uDQoNCg0KQmVzdCBSZWdhcmRzLA0KWmhhaSBIb25nanVu
DQoiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIi
IiIiIiIiIiIiIiIiIiIiDQogUHJvdG9jb2wgRGV2ZWxvcG1lbnQgRGVwdC5WSSwgQ2VudHJhbCBS
JkQgSW5zdGl0dXRlLCBaVEUgQ29ycG9yYXRpb24NCiBOby4gNjgsIFppamluZ2h1YSBSb2FkLCBZ
dWh1YXRhaSBEaXN0cmljdCwgTmFuamluZywgUC5SLkNoaW5hLCAyMTAwMTINCiANCiBaaGFpIEhv
bmdqdW4NCiANCiBUZWw6ICs4Ni0yNS01Mjg3NzM0NQ0KIEVtYWlsOiB6aGFpLmhvbmdqdW5AenRl
LmNvbS5jbg0KIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIi
IiIiIiIiIiIiIiIiIiIiIiIiIiIiIiINCg0KDQoNCg0KDQpSYWRpYSBQZXJsbWFuIDxyYWRpYXBl
cmxtYW5AZ21haWwuY29tPiANCreivP7IyzogIHRyaWxsLWJvdW5jZXNAaWV0Zi5vcmcNCjIwMTMt
MDItMDEgMDU6NDcNCg0KytW8/sjLDQoiVGlzc2EgU2VuZXZpcmF0aG5lICh0c2VuZXZpcikiIDx0
c2VuZXZpckBjaXNjby5jb20+DQqzrcvNDQpBbm9vcCBHaGFud2FuaSA8YW5vb3BAYWx1bW5pLmR1
a2UuZWR1PiwgQXlhbiBCYW5lcmplZSANCjxheWFiYW5lckBnbWFpbC5jb20+LCBTYW0gQWxkcmlu
IDxhbGRyaW4uaWV0ZkBnbWFpbC5jb20+LCAidHJpbGxAaWV0Zi5vcmciIA0KPHRyaWxsQGlldGYu
b3JnPiwgRG9uYWxkIEVhc3RsYWtlIDxkM2UzZTNAZ21haWwuY29tPiwgSm9uIEh1ZHNvbiANCjxq
b24uaHVkc29uQGdtYWlsLmNvbT4NCtb3zOINClt0cmlsbF0gQSB0d2VhayB0byBvcHRpb24gMiwg
ICAgaWYgaXQncyBoYXJkIHRvIHVwZ3JhZGUgVkwgZ3V5cyB0byANCkZHTC1zYWZlDQoNCg0KDQoN
Cg0KDQpUaGUgb3RoZXIgdGhyZWFkIHdhcyBnZXR0aW5nIGEgYml0IGxvbmcsIHNvIEknbSBjaGFu
Z2luZyB0aGUgc3ViamVjdCBsaW5lLCANCnNpbmNlIGhlcmUgSSdtIHByb3Bvc2luZyBhIHR3ZWFr
IHRvIG9wdGlvbiAyIHRoYXQgd2lsbCBtYWtlIGl0IGxlc3MgDQpyZXN0cmljdGl2ZS4gIFRvIHJl
dmlldywgb3B0aW9uIDIgYXMgb3JpZ2luYWxseSBwcm9wb3NlZCBoYWQgdGhpcyANCnByb3BlcnR5
Og0KIA0KPj5XaXRoIG9wdGlvbiAyLCBhIFZMIGd1eSBjYW5ub3QgZXZlbiBiZSBhdCB0aGUgZWRn
ZSBvZiBhIG5ldHdvcmsgd2l0aCBGR0wgDQpsaW5rcyB1bmxlc3MgaXQgaXMgdXBncmFkZWQgdG8g
DQo+PkZHTC1zYWZlIEFORCBhZHZlcnRpc2VzIHRoYXQgaXQgaXMgRkdMLXNhZmUuICBPcHRpb24g
MiBzYXlzIGEgVkwgZ3V5IGlzIA0KY29tcGxldGVseSBvc3RyYXNpemVkIG9uY2UgDQo+PkZHTC1s
YWJlbGVkIGxpbmtzIGFyZSBpbnRyb2R1Y2VkLiAgVGhlcmUgaXMgTk8gY29leGlzdGVuY2Ugb2Yg
VkwgZ3V5cyANCmFuZCBGR0wtZ3V5cyBvbmNlIEZHTC1saW5rcyBhcmUNCiA+PmFkdmVydGlzZWQu
IA0KIA0KSGVyZSBpcyB0aGUgcHJvcG9zZWQgdHdlYWs6DQogDQpBbiBGR0wtc2FmZSBndXkgaGFz
IHR3byBjaG9pY2VzIG9mIHdoYXQgdG8gZG8gd2l0aCBhIFZMIG5laWdoYm9yIChvbmNlIEZHTCAN
CmxpbmtzIGFyZSBhZHZlcnRpc2VkKQ0KIA0KYSkgb3N0cmFzaXplIHRoZSBWTCBuZWlnaGJvciBj
b21wbGV0ZWx5IChhcyB3YXMgaW4gb3B0aW9uIDIpDQpiKSBhZHZlcnRpc2UgYSB2ZXJ5IGhpZ2gg
Y29zdCB0byB0aGUgVkwgbmVpZ2hib3IgQU5EIEFMU08gZGlzY2FyZCBhbnkgRkdMIA0KZnJhbWVz
IHRoYXQgd291bGQgYmUgZm9yd2FyZGVkIHRvIHRoYXQgVkwgbmVpZ2hib3IuDQogDQpJZiBhbiBG
R0wtc2FmZSBndXkgaXMgY2FwYWJsZSBvZiBkaWZmZXJlbnRpYXRpbmcgYmV0d2VlbiBGR0wgYW5k
IFZMIA0KZnJhbWVzLi4uZm9yd2FyZGluZyBWTCBidXQgZGlzY2FyZGluZyBGR0wgdG8gYSBWTCBu
ZWlnaGJvciwgdGhlbiB0aGlzIA0Kd291bGQgYWxsb3cgVkwgZ3V5cyB0byBiZSBhdCB0aGUgZWRn
ZSBhbmQgc3VjY2Vzc2Z1bGx5IHRhbGsgYWNyb3NzIGFuIEZHTCANCmNvcmUuDQogDQpJZiBhbiBG
R0wtc2FmZSBndXkgaXMgbm90IGNhcGFibGUgb2YgZGlmZmVyZW50aWF0aW5nIGJldHdlZW4gRkdM
IGFuZCBWTCANCmZyYW1lcywgdGhlbiB0aGUgVkwgZ3V5IHdpbGwgYmUgb3N0cmFzaXplZC4NCiAN
CkFzIGZvciB0cmFuc2l0Li4uaWYgYSBWTCBndXkgaXMgaW4gdGhlIGNvcmUsIGl0cyBGR0wgbmVp
Z2hib3JzIHdpbGwgcmVwb3J0IA0Kc3VjaCBoaWdoIGNvc3RzIHRvIGl0IHRoYXQgaWYgdGhlcmUg
aXMgYW55IEZHTCBwYXRoLCB0aGF0IHdpbGwgYmUgdGhlIG9uZSANCnRoYXQgaXMgY2hvc2VuLCBh
bmQgaWYgdGhlcmUgaXNuJ3QsIHRoZW4geW91J3JlIG5vIHdvcnNlIG9mZiB0aGFuIGlmIHRoZSAN
ClZMIGd1eSB3ZXJlIGNvbXBsZXRlbHkgb3N0cmFzaXplZC4uLi5pdCB3aWxsIGxvb2sgbGlrZSB0
aGVyZSBpcyBhIHBhdGgsIA0KYnV0IEZHTCBwYWNrZXRzIHdpbGwgYmUgbG9zdCBvbiB0aGUgcGF0
aC4NCiANCkFuZCBvZiBjb3Vyc2UsIHlvdSBzaG91bGRuJ3QgaGF2ZSB0aGUgVkwgZ3V5IGJlIHRo
ZSByb290IG9mIGEgbXVsdGljYXN0IA0KdHJlZSwgc2luY2UgbGluayBjb3N0cyB0byBpdCB3b24n
dCBhdm9pZCBpdCBiZWluZyBvbiB0aGUgcGF0aCBiZXR3ZWVuIEZHTCANCmd1eXMuDQogDQpSYWRp
YQ0KIA0KIF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQp0
cmlsbCBtYWlsaW5nIGxpc3QNCnRyaWxsQGlldGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL3RyaWxsDQoNCg0K
--=_alternative 002F119548257B05_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkFzIEZHTCBmcmFtZXMgYW5kIFZM
IGZyYW1lcyBoYXZlIGRpZmZlcmVudA0KRXRoZXJ0eXBlLCBpdCBpcyBlYXN5IGZvciBGR0wtc2Fm
ZSBSQnJpZGdlcyB0byBkaWZmZXJlbnRpYXRlIHRoZSB0d28gdHlwZXMNCm9mIGZyYW1lcyBpbiBk
YXRhIHBsYW5lLiBBbmQgdGhlIHR3ZWFrZWQgT3B0aW9uIDIgYWxsb3dzIFZMLVJCcmlkZ2VzIGV4
aXRpbmcNCmF0IHRoZSBlZGdlIG9mIGEgbmV3b3JrIHdpdGggRkdMIGxpbmtzIGlmIHRoZWlyIEZH
TC1zYWZlIG5laWdoYm9ycyBjYW4NCmRpZmZlcmVudGlhdGUgdGhlIHR3byB0eXBlIGZyYW1lcywg
SSBhbSBoYXBweSB3aXRoIGl0LjwvZm9udD4NCjxicj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0i
c2Fucy1zZXJpZiI+U28sIEkgc3VwcG9ydCB0aGlzIHR3ZWFrZWQgb3B0aW9uLjwvZm9udD4NCjxi
cj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KPGJyPg0KQmVzdCBSZWdhcmRz
LDxicj4NClpoYWkgSG9uZ2p1bjxicj4NCiZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZx
dW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90
OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZx
dW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90
OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZx
dW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90
OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZx
dW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90Ozxicj4NCiBQcm90
b2NvbCBEZXZlbG9wbWVudCBEZXB0LlZJLCBDZW50cmFsIFImYW1wO0QgSW5zdGl0dXRlLCBaVEUg
Q29ycG9yYXRpb248YnI+DQogTm8uIDY4LCBaaWppbmdodWEgUm9hZCwgWXVodWF0YWkgRGlzdHJp
Y3QsIE5hbmppbmcsIFAuUi5DaGluYSwgMjEwMDEyPGJyPg0KIDxicj4NCiBaaGFpIEhvbmdqdW48
YnI+DQogPGJyPg0KIFRlbDogKzg2LTI1LTUyODc3MzQ1PGJyPg0KIEVtYWlsOiB6aGFpLmhvbmdq
dW5AenRlLmNvbS5jbjxicj4NCiZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZx
dW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90
OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZx
dW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90
OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZx
dW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90
OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZx
dW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90Ozxicj4NCjxicj4N
CjwvZm9udD4NCjxicj4NCjxicj4NCjxicj4NCjx0YWJsZSB3aWR0aD0xMDAlPg0KPHRyIHZhbGln
bj10b3A+DQo8dGQgd2lkdGg9MzYlPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj48Yj5S
YWRpYSBQZXJsbWFuICZsdDtyYWRpYXBlcmxtYW5AZ21haWwuY29tJmd0OzwvYj4NCjwvZm9udD4N
Cjxicj48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+t6K8/sjLOiAmbmJzcDt0cmlsbC1i
b3VuY2VzQGlldGYub3JnPC9mb250Pg0KPHA+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYi
PjIwMTMtMDItMDEgMDU6NDc8L2ZvbnQ+DQo8dGQgd2lkdGg9NjMlPg0KPHRhYmxlIHdpZHRoPTEw
MCU+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZD4NCjxkaXYgYWxpZ249cmlnaHQ+PGZvbnQgc2l6ZT0x
IGZhY2U9InNhbnMtc2VyaWYiPsrVvP7IyzwvZm9udD48L2Rpdj4NCjx0ZD48Zm9udCBzaXplPTEg
ZmFjZT0ic2Fucy1zZXJpZiI+JnF1b3Q7VGlzc2EgU2VuZXZpcmF0aG5lICh0c2VuZXZpcikmcXVv
dDsNCiZsdDt0c2VuZXZpckBjaXNjby5jb20mZ3Q7PC9mb250Pg0KPHRyIHZhbGlnbj10b3A+DQo8
dGQ+DQo8ZGl2IGFsaWduPXJpZ2h0Pjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj6zrcvN
PC9mb250PjwvZGl2Pg0KPHRkPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj5Bbm9vcCBH
aGFud2FuaSAmbHQ7YW5vb3BAYWx1bW5pLmR1a2UuZWR1Jmd0OywNCkF5YW4gQmFuZXJqZWUgJmx0
O2F5YWJhbmVyQGdtYWlsLmNvbSZndDssIFNhbSBBbGRyaW4gJmx0O2FsZHJpbi5pZXRmQGdtYWls
LmNvbSZndDssDQomcXVvdDt0cmlsbEBpZXRmLm9yZyZxdW90OyAmbHQ7dHJpbGxAaWV0Zi5vcmcm
Z3Q7LCBEb25hbGQgRWFzdGxha2UgJmx0O2QzZTNlM0BnbWFpbC5jb20mZ3Q7LA0KSm9uIEh1ZHNv
biAmbHQ7am9uLmh1ZHNvbkBnbWFpbC5jb20mZ3Q7PC9mb250Pg0KPHRyIHZhbGlnbj10b3A+DQo8
dGQ+DQo8ZGl2IGFsaWduPXJpZ2h0Pjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj7W98zi
PC9mb250PjwvZGl2Pg0KPHRkPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj5bdHJpbGxd
IEEgdHdlYWsgdG8gb3B0aW9uIDIsICZuYnNwOw0KJm5ic3A7ICZuYnNwOyAmbmJzcDtpZiBpdCdz
IGhhcmQgdG8gdXBncmFkZSBWTCBndXlzIHRvIEZHTC1zYWZlPC9mb250PjwvdGFibGU+DQo8YnI+
DQo8dGFibGU+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZD4NCjx0ZD48L3RhYmxlPg0KPGJyPjwvdGFi
bGU+DQo8YnI+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0zPlRoZSBvdGhlciB0aHJlYWQgd2FzIGdl
dHRpbmcgYSBiaXQgbG9uZywgc28gSSdtIGNoYW5naW5nDQp0aGUgc3ViamVjdCBsaW5lLCBzaW5j
ZSBoZXJlIEknbSBwcm9wb3NpbmcgYSB0d2VhayB0byBvcHRpb24gMiB0aGF0Jm5ic3A7d2lsbA0K
bWFrZSBpdCBsZXNzIHJlc3RyaWN0aXZlLiZuYnNwOyBUbyByZXZpZXcsIG9wdGlvbiAyIGFzIG9y
aWdpbmFsbHkgcHJvcG9zZWQNCmhhZCB0aGlzIHByb3BlcnR5OjwvZm9udD4NCjxicj48Zm9udCBz
aXplPTM+Jm5ic3A7PC9mb250Pg0KPGJyPjxmb250IHNpemU9Mz4mZ3Q7Jmd0O1dpdGggb3B0aW9u
IDIsIGEgVkwgZ3V5IGNhbm5vdCBldmVuIGJlIGF0IHRoZQ0KZWRnZSBvZiBhIG5ldHdvcmsgd2l0
aCBGR0wgbGlua3MgdW5sZXNzIGl0IGlzIHVwZ3JhZGVkIHRvIDwvZm9udD4NCjxicj48Zm9udCBz
aXplPTM+Jmd0OyZndDtGR0wtc2FmZSBBTkQgYWR2ZXJ0aXNlcyB0aGF0IGl0IGlzIEZHTC1zYWZl
LiZuYnNwOw0KT3B0aW9uIDIgc2F5cyBhIFZMIGd1eSBpcyBjb21wbGV0ZWx5IG9zdHJhc2l6ZWQg
b25jZSA8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0zPiZndDsmZ3Q7RkdMLWxhYmVsZWQgbGlua3Mg
YXJlIGludHJvZHVjZWQuJm5ic3A7IFRoZXJlDQppcyBOTyBjb2V4aXN0ZW5jZSBvZiBWTCBndXlz
IGFuZCBGR0wtZ3V5cyBvbmNlJm5ic3A7RkdMLWxpbmtzIGFyZTwvZm9udD4NCjxicj48Zm9udCBz
aXplPTM+Jm5ic3A7Jmd0OyZndDthZHZlcnRpc2VkLiA8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0z
PiZuYnNwOzwvZm9udD4NCjxicj48Zm9udCBzaXplPTM+SGVyZSBpcyB0aGUgcHJvcG9zZWQgdHdl
YWs6PC9mb250Pg0KPGJyPjxmb250IHNpemU9Mz4mbmJzcDs8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6
ZT0zPkFuIEZHTC1zYWZlIGd1eSBoYXMgdHdvIGNob2ljZXMgb2Ygd2hhdCB0byBkbyB3aXRoIGEg
VkwNCm5laWdoYm9yIChvbmNlIEZHTCBsaW5rcyBhcmUgYWR2ZXJ0aXNlZCk8L2ZvbnQ+DQo8YnI+
PGZvbnQgc2l6ZT0zPiZuYnNwOzwvZm9udD4NCjxicj48Zm9udCBzaXplPTM+YSkgb3N0cmFzaXpl
IHRoZSBWTCBuZWlnaGJvciBjb21wbGV0ZWx5IChhcyB3YXMgaW4gb3B0aW9uDQoyKTwvZm9udD4N
Cjxicj48Zm9udCBzaXplPTM+YikgYWR2ZXJ0aXNlIGEgdmVyeSBoaWdoIGNvc3QgdG8gdGhlIFZM
IG5laWdoYm9yIEFORCBBTFNPDQpkaXNjYXJkIGFueSBGR0wgZnJhbWVzIHRoYXQgd291bGQgYmUg
Zm9yd2FyZGVkIHRvIHRoYXQgVkwgbmVpZ2hib3IuPC9mb250Pg0KPGJyPjxmb250IHNpemU9Mz4m
bmJzcDs8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0zPklmIGFuIEZHTC1zYWZlIGd1eSBpcyBjYXBh
YmxlIG9mIGRpZmZlcmVudGlhdGluZyBiZXR3ZWVuDQpGR0wgYW5kIFZMIGZyYW1lcy4uLmZvcndh
cmRpbmcgVkwgYnV0IGRpc2NhcmRpbmcgRkdMIHRvIGEgVkwgbmVpZ2hib3IsDQp0aGVuIHRoaXMg
d291bGQgYWxsb3cgVkwgZ3V5cyB0byBiZSBhdCB0aGUgZWRnZSBhbmQgc3VjY2Vzc2Z1bGx5IHRh
bGsgYWNyb3NzDQphbiBGR0wgY29yZS48L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0zPiZuYnNwOzwv
Zm9udD4NCjxicj48Zm9udCBzaXplPTM+SWYgYW4gRkdMLXNhZmUgZ3V5IGlzIG5vdCBjYXBhYmxl
IG9mIGRpZmZlcmVudGlhdGluZyBiZXR3ZWVuDQpGR0wgYW5kIFZMIGZyYW1lcywgdGhlbiB0aGUg
VkwgZ3V5IHdpbGwgYmUgb3N0cmFzaXplZC48L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0zPiZuYnNw
OzwvZm9udD4NCjxicj48Zm9udCBzaXplPTM+QXMgZm9yIHRyYW5zaXQuLi5pZiBhIFZMIGd1eSBp
cyBpbiB0aGUgY29yZSwgaXRzIEZHTCBuZWlnaGJvcnMNCndpbGwgcmVwb3J0IHN1Y2ggaGlnaCBj
b3N0cyB0byBpdCB0aGF0IGlmIHRoZXJlIGlzIGFueSBGR0wgcGF0aCwgdGhhdCB3aWxsDQpiZSB0
aGUgb25lIHRoYXQgaXMgY2hvc2VuLCBhbmQgaWYgdGhlcmUgaXNuJ3QsIHRoZW4geW91J3JlIG5v
IHdvcnNlIG9mZg0KdGhhbiBpZiB0aGUgVkwgZ3V5IHdlcmUgY29tcGxldGVseSBvc3RyYXNpemVk
Li4uLml0IHdpbGwgbG9vayBsaWtlIHRoZXJlDQppcyBhIHBhdGgsIGJ1dCBGR0wgcGFja2V0cyB3
aWxsIGJlIGxvc3Qgb24gdGhlIHBhdGguPC9mb250Pg0KPGJyPjxmb250IHNpemU9Mz4mbmJzcDs8
L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0zPkFuZCBvZiBjb3Vyc2UsIHlvdSBzaG91bGRuJ3QgaGF2
ZSB0aGUgVkwgZ3V5IGJlIHRoZSByb290DQpvZiBhIG11bHRpY2FzdCB0cmVlLCBzaW5jZSBsaW5r
IGNvc3RzIHRvIGl0IHdvbid0IGF2b2lkIGl0IGJlaW5nIG9uIHRoZQ0KcGF0aCBiZXR3ZWVuIEZH
TCBndXlzLjwvZm9udD4NCjxicj48Zm9udCBzaXplPTM+Jm5ic3A7PC9mb250Pg0KPGJyPjxmb250
IHNpemU9Mz5SYWRpYTwvZm9udD4NCjxicj48Zm9udCBzaXplPTM+Jm5ic3A7PC9mb250Pg0KPGJy
Pjxmb250IHNpemU9Mz4mbmJzcDs8L2ZvbnQ+PHR0Pjxmb250IHNpemU9Mj5fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCnRyaWxsIG1haWxpbmcgbGlz
dDxicj4NCnRyaWxsQGlldGYub3JnPGJyPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby90cmlsbDxicj4NCjwvZm9udD48L3R0Pg0KPGJyPg0K
--=_alternative 002F119548257B05_=--

From haoweiguo@huawei.com  Fri Feb  1 01:12:00 2013
Return-Path: <haoweiguo@huawei.com>
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 B81EA21F86C1 for <trill@ietfa.amsl.com>; Fri,  1 Feb 2013 01:12:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.85
X-Spam-Level: **
X-Spam-Status: No, score=2.85 tagged_above=-999 required=5 tests=[AWL=-0.200,  BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, J_CHICKENPOX_34=0.6, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
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 5T0jfeCLFMrn for <trill@ietfa.amsl.com>; Fri,  1 Feb 2013 01:11:58 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1CB8A21F8794 for <trill@ietf.org>; Fri,  1 Feb 2013 01:11:56 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id API19229; Fri, 01 Feb 2013 09:11:55 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 1 Feb 2013 09:11:15 +0000
Received: from NKGEML410-HUB.china.huawei.com (10.98.56.41) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 1 Feb 2013 09:11:54 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.101]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.01.0323.007; Fri, 1 Feb 2013 17:11:48 +0800
From: Haoweiguo <haoweiguo@huawei.com>
To: Radia Perlman <radiaperlman@gmail.com>, "Tissa Senevirathne (tsenevir)" <tsenevir@cisco.com>
Thread-Topic: [trill] Explaining three options for upgrading to FGL (fine-grained-labeling)
Thread-Index: AQHN//5pVF/dtg3w3USm/4yBhBkijJhktsGf
Date: Fri, 1 Feb 2013 09:11:48 +0000
Message-ID: <DD5FC8DE455C3348B94340C0AB5517334F65191F@nkgeml501-mbs.china.huawei.com>
References: <CAFOuuo67iBR2JkDtwPFCkrKHs3Fp4U_L1jkmNz5sfht6y05YMw@mail.gmail.com> <CA+-tSzx0E3J4i5Dvfbj4egruCeGi7z1se1Jn5RXtx3RedQLPdg@mail.gmail.com> <CAHD03N89RNX4=XxRZpD+Y2PCktYf-FtVjyYJ5oFS3dui3SsXaA@mail.gmail.com> <CAF4+nEG7YKGzGmObAMaOxackivjJsALymqHX=6PKBd5qU-Z+zQ@mail.gmail.com> <CA+-tSzz0=oh6iB1e-ESyeOx2sCvBFXeVpzuNbKmUVhRNLScDgQ@mail.gmail.com> <CAF4+nEFLrJL=CgX9e6on-cgz89ugmu93P6u5kmODhUia3H7RLg@mail.gmail.com> <1F5A81AE-4B3C-45FD-B431-9BA0011EB085@gmail.com> <DC8898F8-75C0-4535-BA61-C54279901332@gmail.com> <43DF00BE-B5F6-48B9-B313-8D179354C7B7@gmail.com> <A9B8F2D5-C3D7-4688-A76D-ED19EC47E59F@gmail.com> <FBEA3E19AA24F847BA3AE74E2FE19356288F6978@xmb-rcd-x08.cisco.com>, <CAFOuuo4jZMdvUU_2EzBj1MLp6k0e+AmW1+k1ai4Q_m4rA0ObMw@mail.gmail.com>
In-Reply-To: <CAFOuuo4jZMdvUU_2EzBj1MLp6k0e+AmW1+k1ai4Q_m4rA0ObMw@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.195.125.218]
Content-Type: multipart/alternative; boundary="_000_DD5FC8DE455C3348B94340C0AB5517334F65191Fnkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: Anoop Ghanwani <anoop@alumni.duke.edu>, Ayan Banerjee <ayabaner@gmail.com>, Sam Aldrin <aldrin.ietf@gmail.com>, "trill@ietf.org" <trill@ietf.org>, Donald Eastlake <d3e3e3@gmail.com>, Jon Hudson <jon.hudson@gmail.com>
Subject: [trill] =?gb2312?b?tPC4tDogIEV4cGxhaW5pbmcgdGhyZWUgb3B0aW9ucyBm?= =?gb2312?b?b3IgdXBncmFkaW5nIHRvIEZHTAkoZmluZS1ncmFpbmVkLWxhYmVsaW5nKQ==?=
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: Fri, 01 Feb 2013 09:12:01 -0000

--_000_DD5FC8DE455C3348B94340C0AB5517334F65191Fnkgeml501mbschi_
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64

SGkgUmFkaWEsDQoNCkkgYWdyZWUgd2l0aCB5b3VyIGRlZmluaXRpb24gb2YgIlNhZmUgRkdMIixi
dXQgSSBoYXZlIGEgcHJvYmxlbSBhYm91dCB0aGUgZm9sbG93aW5nIHBvaW50Og0KDQoNCg0KYikg
bXVsdGljYXN0IHBydW5pbmc6IGl0J3MgT0sgbm90IHRvIGRvIHBydW5pbmcgYXQgYWxsLCBvciB0
byBhY3R1YWxseSBsb29rIGF0IGFsbCAyNCBiaXRzIG9mIHRoZSBGR0wgYW5kIHBydW5lIGFzIGEg
cHJvcGVyIEZHTCBndXkgd291bGQgZG8uICBCdXQgYW4gZXhhbXBsZSBvZiB3aGF0IHlvdSBjYW5O
T1QgZG8gaXMgbG9vayBhdCB0aGUgZmlyc3QgMTIgYml0cyBvZiBGR0wsIHByZXRlbmQgaXQncyB0
aGUgc2FtZSBhcyBWTCwgYW5kIGRlbGV0ZSB0aGUgbXVsdGljYXN0IHBhY2tldCBiZWNhdXNlIG5v
Ym9keSBkb3duc3RyZWFtIGlzIGxpc3RlbmluZyB0byB0aGF0IDEyIGJpdCBWTCB2YWx1ZQ0KDQpb
d2VpZ3VvXTpJZiBhIHN3aXRjaCBwZXJmb3JtcyBwcnVuaW5nIGJ5IGZpcnN0IDEyIGJpdHMgb2Yg
RkdMLCBjYW4gdGhlIHN3aXRjaCBjYWxsZWQgIlNhZmUgRkdMIiBzd2l0Y2g/IElmIGRvd25zdHJl
YW0gaGF2ZSBvbmUgVkwgc3dpdGNoIHdpdGggVkxBTiBpcyBlcXVhbCB0byBmaXJzdCAxMiBiaXRz
IG9mIEZHTCx0aGVuIHRoZSBzd2l0Y2ggd2lsbCBmb3J3YXJkIG11bHRpY2FzdCBkYXRhIGZyYW1l
IHRvIGRvd25zdHJlYW0gVkwgc3dpdGNoLg0KdGhhbmtzDQp3ZWlndW8NCl9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fDQq3orz+yMs6IFJhZGlhIFBlcmxtYW4gW3JhZGlhcGVybG1hbkBn
bWFpbC5jb21dDQq3osvNyrG85DogMjAxM8TqMtTCMcjVIDQ6MjQNCrW9OiBUaXNzYSBTZW5ldmly
YXRobmUgKHRzZW5ldmlyKQ0KQ2M6IEFub29wIEdoYW53YW5pOyBBeWFuIEJhbmVyamVlOyBTYW0g
QWxkcmluOyB0cmlsbEBpZXRmLm9yZzsgRG9uYWxkIEVhc3RsYWtlOyBKb24gSHVkc29uDQrW98zi
OiBSZTogW3RyaWxsXSBFeHBsYWluaW5nIHRocmVlIG9wdGlvbnMgZm9yIHVwZ3JhZGluZyB0byBG
R0wgKGZpbmUtZ3JhaW5lZC1sYWJlbGluZykNCg0KVGlzc2Egc2FpZDoNCj4+IGhvdyBjYW4geW91
IG1ha2Ugc3VyZSBhbGwgb2YgdGhlIHNvIGNhbGxlZCAiU2FmZSBGR0wiIGhhdmUgY29uc2lzdGVu
dCBiZWhhdmlvcg0KDQoiU2FmZSBGR0wiIG5lZWQgbm90IGFsbCBoYXZlIHRoZSBzYW1lIGJlaGF2
aW9yIGFzIGVhY2ggb3RoZXIuLi50aGV5IGp1c3QgaGF2ZSB0byBkbyAibm90aGluZyBiYWQiIHdp
dGggYW4gRkdMIGZyYW1lLiAgSXQncyB3b3J0aCBzdW1tYXJpemluZyAoYWdhaW4pIHdoYXQgaXQg
bWVhbnMgdG8gYmUgIkZHTC1zYWZlIiwgd2hpY2ggYWxsb3dzIHlvdSB0byBjb2V4aXN0IHNhZmVs
eSB3aXRoIEZHTCBmcmFtZXMuICBUbyBiZSBGR0wtc2FmZSB5b3UgbXVzdCBkbyB0aGUgZm9sbG93
aW5nOg0KDQphKSB1bmljYXN0OiB5b3UgTVVTVCBOT1QgZHJvcCBhIHBhY2tldCBiZWNhdXNlIG9m
IHNlZWluZyB0aGUgdW5yZWNvZ25pemVkIEZHTCB0YWcuICBZb3UgYWxzbyBNVVNUIE5PVCBnZXQg
Y29uZnVzZWQgYW5kIGRvIGZsb3cgaGFzaGluZyBpbXByb3Blcmx5IChjaG9vc2luZyBkaWZmZXJl
bnQgcGF0aHMgZm9yIHBhY2tldHMgZm9yIHRoZSBzYW1lIGZsb3cpLg0KDQpiKSBtdWx0aWNhc3Qg
cHJ1bmluZzogaXQncyBPSyBub3QgdG8gZG8gcHJ1bmluZyBhdCBhbGwsIG9yIHRvIGFjdHVhbGx5
IGxvb2sgYXQgYWxsIDI0IGJpdHMgb2YgdGhlIEZHTCBhbmQgcHJ1bmUgYXMgYSBwcm9wZXIgRkdM
IGd1eSB3b3VsZCBkby4gIEJ1dCBhbiBleGFtcGxlIG9mIHdoYXQgeW91IGNhbk5PVCBkbyBpcyBs
b29rIGF0IHRoZSBmaXJzdCAxMiBiaXRzIG9mIEZHTCwgcHJldGVuZCBpdCdzIHRoZSBzYW1lIGFz
IFZMLCBhbmQgZGVsZXRlIHRoZSBtdWx0aWNhc3QgcGFja2V0IGJlY2F1c2Ugbm9ib2R5IGRvd25z
dHJlYW0gaXMgbGlzdGVuaW5nIHRvIHRoYXQgMTIgYml0IFZMIHZhbHVlDQoNCmMpIGVncmVzcyBv
ZiBlaXRoZXIgdW5pY2FzdCBvciBtdWx0aWNhc3Q6ICB5b3UgTVVTVCBOT1QgZWdyZXNzIGFuIEZH
TCBmcmFtZSBvbnRvIGEgbGluayB0aGF0IGlzIG5vdCBzdXBwb3NlZCB0byBnZXQgdGhhdCBGR0wg
dmFsdWUNCg0KZCkgeW91IGhhdmUgdG8gYWR2ZXJ0aXNlIHRoYXQgeW91IGFyZSBGR0wtc2FmZS4u
Lm90aGVyd2lzZSBvdGhlciBSQnMgd2lsbCBhc3N1bWUgeW91IGFyZSBWTCAoIkZHTC11bnNhZmUi
KQ0KDQotLS0tLS0tLS0NCkFsc28sIFRJc3NhIHNhaWQ6DQo+PkRvIHlvdSBhZ3JlZSBpZiB3ZSBz
YXksIEZHTCB3aWxsIGFsd2F5cyBiZSBjb3JlIG9mIHRoZSBuZXR3b3JrLCBhbmQgVkwgd2lsbCBi
ZSBhdCB0aGUgZWRnZSBvZiB0aGUgbmV0d29yayA/DQoNCldpdGggb3B0aW9uIDIsIGEgVkwgZ3V5
IGNhbm5vdCBldmVuIGJlIGF0IHRoZSBlZGdlIG9mIGEgbmV0d29yayB3aXRoIEZHTCBsaW5rcyB1
bmxlc3MgaXQgaXMgdXBncmFkZWQgdG8gRkdMLXNhZmUgQU5EIGFkdmVydGlzZXMgdGhhdCBpdCBp
cyBGR0wtc2FmZS4gIE9wdGlvbiAyIHNheXMgYSBWTCBndXkgaXMgY29tcGxldGVseSBvc3RyYXNp
emVkIG9uY2UgRkdMLWxhYmVsZWQgbGlua3MgYXJlIGludHJvZHVjZWQuICBUaGVyZSBpcyBOTyBj
b2V4aXN0ZW5jZSBvZiBWTCBndXlzIGFuZCBGR0wtbGlua3MuIFRoZSBvbmx5IGtpbmRzIG9mIGNv
ZXhpc3RlbmNlIGluIG9wdGlvbiAyIGFyZToNCg0KYSkgVkwgYW5kIEZHTC1zYWZlIFJCcmlkZ2Us
IGJ1dCBubyBhY3R1YWwgRkdMIGxpbmtzIHlldC4NCmIpIEZHTC1zYWZlIGd1eXMsIGV2ZW4gaWYg
c29tZSBvZiB0aGVtIGRvbid0IHJlYWxseSB1bmRlcnN0YW5kIEZHTCwgYnV0IGp1c3QgZG9uJ3Qg
ZG8gImFueXRoaW5nIGJhZCIgd2l0aCBpdCwgYW5kIEZHTCBmcmFtZXMuDQoNClNvLi4uYWdhaW4u
Li50aGUgbWlncmF0aW9uIHBoYXNlcyBpbiBvcHRpb24gMiBhcmUNCjEpIFZMLW9ubHkgKHRvZGF5
J3MgZGVwbG95bWVudCksIHRoZW4NCjIpIEEgbWl4dHVyZSBvZiBWTCBhbmQgRkdMLXNhZmUsIHVu
dGlsDQozKSBFVkVSWW9uZSB1cGdyYWRlZCB0byBGR0wtc2FmZSwgdGhlbg0KNCkgRkdMLWxpbmtz
IGNhbiBiZSBpbnRyb2R1Y2VkLg0KDQoNCi0tLS0NCkFsc28sIFRpc3NhIHNhaWQ6DQo+PndoYXQg
YWJvdXQgc29tZSBkZXZpY2VzIHdobyBhcmUgbm90ICJzYWZlIEZHTCIgYW5kIHNvIG9uLCBhcmUg
d2Ugc2F5aW5nIGRvIG5vdCBidXkgbm8gc2FmZSBGR0wgZGV2aWNlcywgaWYgeW91IGRvIHRoYXQg
eW91IGNhbm5vdCBnZXQgRkdMIGludGVyb3AgPw0KDQpJZiBpdCdzIGltcG9ydGFudCB0byBoYXZl
IFZMIGd1eXMgYXMgdHJhbnNpdCwgYW5kIHRoZXkgY2Fubm90IGJlIHVwZ3JhZGVkIHRvIEZHTC1z
YWZlIGJlY2F1c2UgdXBncmFkaW5nIHJlcXVpcmVzIGEgaGFyZHdhcmUgY2hhbmdlIChpdCBpbnZv
bHZlcyBwYXJzaW5nIGRhdGEgcGFja2V0cyksIHRoZW4gd2UgYXJlIHN0dWNrIHdpdGggb3B0aW9u
IDMuICBJbiBvcHRpb24gMywgd2UgY2FuIGZvcmV2ZXIgaGF2ZSBWTCBndXlzIGF0IHRoZSBlZGdl
IHNwZWFraW5nIHRocm91Z2ggYW4gRkdMLXNhZmUgb3IgZnVsbC1GR0wgY29yZS4gIEluIG9wdGlv
biAyLCBhcyBJIHNhaWQsIHRoZXJlIGlzIG5vIGNvZXhpc3RlbmNlIG9mIFZMIGd1eXMsIGV2ZW4g
YXQgdGhlIGVkZ2UsIG9uY2UgRkdMIGxpbmtzIGFyZSBpbnRyb2R1Y2VkLiAgSW4gb3B0aW9uIDIs
IGEgVkwgZ3V5LCBldmVuIGF0IHRoZSBlZGdlLCB3aWxsIGJlIG9zdHJhc2l6ZWQgY29tcGxldGVs
eSBvbmNlIGFueW9uZSBhZHZlcnRpc2VzIGNvbm5lY3Rpdml0eSB0byBhbiBGR0wgbGluay4NCg0K
SSBwZXJzb25hbGx5IGxpa2Ugb3B0aW9uIDIsIGJlY2F1c2UgaXQncyBzaW1wbGUsIGJ1dCBhcyBF
aW5zdGVpbiBzYWlkICJtYWtlIHRoaW5ncyBhcyBzaW1wbGUgYXMgcG9zc2libGUsIGJ1dCBubyBz
aW1wbGVyIi4gIFdlIGhhdmUgdG8gbWFrZSBzdXJlIHRoYXQgZXZlcnlvbmUgdW5kZXJzdGFuZHMg
dGhlIGltcGxpY2F0aW9ucyBvZiBvcHRpb24gMiwgYW5kIGNhbiBsaXZlIHdpdGggdGhlbS4gIFRv
IHN1bW1hcml6ZSBhZ2FpbiAoc2luY2UgdGhlcmUgc2VlbXMgdG8gYmUgc29tZSBjb25mdXNpb24g
YWJvdXQgd2hhdCB0aGUgaW1wbGljYXRpb25zIG9mIG9wdGlvbiAyIGFyZSksDQoNCklmIHdlIGNh
biB1cGdyYWRlIGFsbCBleGlzdGluZyBWTCBpbXBsZW1lbnRhdGlvbnMgdG8gRkdMLXNhZmUgdGhy
b3VnaCBzb2Z0d2FyZSB1cGdyYWRlIG9ubHksIHRoZW4gb3B0aW9uIDIgcHJvdmlkZXMgc21vb3Ro
IG1pZ3JhdGlvbiBieSBjaGFuZ2luZyBBTEwgUkJyaWRnZXMgKGVkZ2UgYXMgd2VsbCBhcyB0cmFu
c2l0KSB0byBGR0wtc2FmZSwgYW5kIG9ubHkgYWZ0ZXIgQUxMIG9mIHRoZW0gYXJlIHVwZ3JhZGVk
LCB0aGVuIEZHTC1sYWJlbGVkIGxpbmtzIGNhbiBiZSBpbnRyb2R1Y2VkLiAgSWYgdGhlcmUgYXJl
IGFueSByZW1haW5pbmcgVkwgZ3V5cyBvbmNlIEZHTC1sYWJlbGVkIGxpbmtzIGFyZSBpbnRyb2R1
Y2VkLCB0aGUgVkwgZ3V5cyBhcmUgb3N0cmFzaXplZCwgZXZlbiBpZiB0aGV5IGFyZSBqdXN0IGF0
IHRoZSBlZGdlLg0KDQpJZiB3ZSBjYW5OT1QgdXBncmFkZSBhbGwgZXhpc3RpbmcgVkwgdG8gRkdM
LXNhZmUsIEFORCBpZiBpdCdzIGltcG9ydGFudCB0byBiZSBhYmxlIHRvIG1peCBWTCBndXlzIGlu
dG8gYSBuZXR3b3JrIHdpdGggRkdMIGZyYW1lcyAoc2F5LCBoYXZpbmcgVkwgZ3V5cyBhdCB0aGUg
ZWRnZSksIHRoZW4gb3B0aW9uIDMgYWxsb3dzIHRoaXMuDQoNClNvIGhvcGVmdWxseSBldmVyeW9u
ZSB1bmRlcnN0YW5kcyB0aGUgaW1wbGljYXRpb25zIG9mIG9wdGlvbiAyIGZ1bGx5IGJlZm9yZSB2
b3RpbmcuICBBcyBJIHNhaWQsIEkgZG9uJ3Qga25vdyBhYm91dCB3aGV0aGVyIHRoZXJlIGFyZSBW
TCBjaGlwcyB0aGF0IHdvdWxkIHJlcXVpcmUgYSBoYXJkd2FyZSB1cGdyYWRlIHRvIGJlY29tZSBG
R0wtc2FmZS4gIEFzc3VtaW5nIHRoZXJlIGFyZSBub25lLCB0aGVuIEknbSBxdWl0ZSBoYXBweSB3
aXRoIG9wdGlvbiAyLiAgIEFuZCBhY3R1YWxseSwgaXQgbG9va3MgbGlrZSBwZW9wbGUgYXJlIGNv
bnZlcmdpbmcgb24gb3B0aW9uIDIgKHRob3VnaCBJIGhvcGUgaXQncyBiYXNlZCBvbiBmdWxseSB1
bmRlcnN0YW5kaW5nIG9wdGlvbiAyKS4gIE5vdyBpcyB0aGUgdGltZSBmb3IgcGVvcGxlIHRvIHNw
ZWFrIHVwLCB0aGF0IGtub3cgb2YgcHJvYmxlbXMgdGhpcyB3b3VsZCBjYXVzZS4uLmZvciBpbnN0
YW5jZSwgbmVlZGluZyB0byBoYXZlIG5vbi11cGdyYWRhYmxlIFZMIGd1eXMgYXQgdGhlIGVkZ2Ug
Zm9yIGEgbG9uZyB0aW1lLg0KDQpSYWRpYQ0KDQoNCg==

--_000_DD5FC8DE455C3348B94340C0AB5517334F65191Fnkgeml501mbschi_
Content-Type: text/html; charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dgb2312">
<style id=3D"owaParaStyle">P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body fPStyle=3D"1" ocsi=3D"0">
<div style=3D"direction: ltr;font-family: Tahoma;color: #000000;font-size: =
10pt;">
<p>Hi Radia,</p>
<p>I agree with your definition of &quot;Safe FGL&quot;,but I have a proble=
m about the following point:</p>
<p>&nbsp;</p>
<div>b) multicast pruning: it's OK not to do pruning at all, or to actually=
 look at all 24 bits of the FGL and prune as a proper FGL guy would do. &nb=
sp;But an example of what you canNOT do is look at the first 12 bits of FGL=
, pretend it's the same as VL, and delete
 the multicast packet because nobody downstream is listening to that 12 bit=
 VL value</div>
<div>&nbsp;</div>
<div>[weiguo]:If a switch performs pruning by first 12 bits of FGL, can the=
 switch called &quot;Safe FGL&quot; switch? If downstream have one VL switc=
h with VLAN is equal to first 12 bits of FGL,then the switch will forward m=
ulticast data frame to downstream VL switch.</div>
<div>thanks</div>
<div>weiguo</div>
<div style=3D"FONT-FAMILY: Times New Roman; COLOR: #000000; FONT-SIZE: 16px=
">
<hr tabindex=3D"-1">
<div style=3D"DIRECTION: ltr" id=3D"divRpF593856"><font color=3D"#000000" s=
ize=3D"2" face=3D"Tahoma"><b>=B7=A2=BC=FE=C8=CB:</b> Radia Perlman [radiape=
rlman@gmail.com]<br>
<b>=B7=A2=CB=CD=CA=B1=BC=E4:</b> 2013=C4=EA2=D4=C21=C8=D5 4:24<br>
<b>=B5=BD:</b> Tissa Senevirathne (tsenevir)<br>
<b>Cc:</b> Anoop Ghanwani; Ayan Banerjee; Sam Aldrin; trill@ietf.org; Donal=
d Eastlake; Jon Hudson<br>
<b>=D6=F7=CC=E2:</b> Re: [trill] Explaining three options for upgrading to =
FGL (fine-grained-labeling)<br>
</font><br>
</div>
<div></div>
<div>Tissa said:
<div>&gt;&gt;&nbsp;how can you make sure all of the so called &quot;Safe FG=
L&quot; have consistent behavior<br>
<div><br>
</div>
<div>&quot;Safe FGL&quot; need not all have the <i><b>same</b></i> behavior=
 as each other...they just have to do &quot;nothing bad&quot; with an FGL f=
rame. &nbsp;It's worth summarizing (again) what it means to be &quot;FGL-sa=
fe&quot;, which allows you to coexist safely with FGL frames. &nbsp;To be
 FGL-safe you must do the following:</div>
<div>
<div><br>
</div>
<div>a) unicast: you MUST NOT drop a packet because of seeing the unrecogni=
zed FGL tag. &nbsp;You also MUST NOT get confused and do flow hashing impro=
perly (choosing different paths for packets for the same flow).</div>
<div><br>
</div>
<div>b) multicast pruning: it's OK not to do pruning at all, or to actually=
 look at all 24 bits of the FGL and prune as a proper FGL guy would do. &nb=
sp;But an example of what you canNOT do is look at the first 12 bits of FGL=
, pretend it's the same as VL, and delete
 the multicast packet because nobody downstream is listening to that 12 bit=
 VL value</div>
<div><br>
</div>
<div>c) egress of either unicast or multicast: &nbsp;you MUST NOT egress an=
 FGL frame onto a link that is not supposed to get that FGL value</div>
<div><br>
</div>
<div>d) you have to advertise that you are FGL-safe...otherwise other RBs w=
ill assume you are VL (&quot;FGL-unsafe&quot;)</div>
<div><br>
</div>
<div>---------</div>
<div>Also, TIssa said:</div>
<div>&gt;&gt;Do you agree if we say, FGL will always be core of the network=
, and VL will be at the edge of the network ?</div>
<div><br>
</div>
<div>With option 2, a VL guy <i><u>cannot even be at the edge of a network =
with FGL links</u></i> unless it is upgraded to FGL-safe AND advertises tha=
t it is FGL-safe. &nbsp;Option 2 says a VL guy is completely ostrasized onc=
e FGL-labeled links are introduced. &nbsp;There
 is NO coexistence of VL guys and FGL-links. The only kinds of coexistence =
in option 2 are:</div>
<div><br>
</div>
<div>a) VL and FGL-safe RBridge, but no actual FGL links yet.</div>
<div>b) FGL-safe guys, even if some of them don't really understand FGL, bu=
t just don't do &quot;anything bad&quot; with it, and FGL frames.</div>
<div><br>
</div>
<div>So...again...the migration phases in option 2 are</div>
<div>1) VL-only (today's deployment), then</div>
<div>2) A mixture of VL and FGL-safe, until</div>
<div>3) EVERYone upgraded to FGL-safe, then</div>
<div>4) FGL-links can be introduced.</div>
<div><br>
</div>
<div><br>
</div>
<div>----</div>
<div>Also, Tissa said:</div>
<div>&gt;&gt;what about some devices who are not &quot;safe FGL&quot; and s=
o on, are we saying do not buy no safe FGL devices, if you do that you cann=
ot get FGL interop ?&nbsp;</div>
<div><br>
</div>
<div><b><i><u>If</u></i></b> it's important to have VL guys as transit, and=
 they cannot be upgraded to FGL-safe because upgrading requires a hardware =
change (it involves parsing data packets), then we are stuck with option 3.=
 &nbsp;In option 3, we can forever have
 VL guys at the edge speaking through an FGL-safe or full-FGL core. &nbsp;I=
n option 2, as I said, there is
<i><u>no coexistence</u></i> of VL guys, <i><u>even at the edg</u></i>e, on=
ce FGL links are introduced. &nbsp;In option 2, a VL guy, even at the edge,=
 will be ostrasized completely once anyone advertises connectivity to an FG=
L link.</div>
<div><br>
</div>
<div>I personally like option 2, because it's simple, but as Einstein said =
&quot;make things as simple as possible, but no simpler&quot;. &nbsp;We hav=
e to make sure that everyone understands the implications of option 2, and =
can live with them. &nbsp;To summarize again (since
 there seems to be some confusion about what the implications of option 2 a=
re),</div>
<div><br>
</div>
<div>If we can upgrade all existing VL implementations to FGL-safe through =
software upgrade only, then option 2 provides smooth migration by changing =
ALL RBridges (edge as well as transit) to FGL-safe, and only after ALL of t=
hem are upgraded, then FGL-labeled
 links can be introduced. &nbsp;If there are any remaining VL guys once FGL=
-labeled links are introduced, the VL guys are ostrasized,
<i><u>even if they are just at the edge.</u></i></div>
<div><br>
</div>
<div>If we canNOT upgrade all existing VL to FGL-safe, AND if it's importan=
t to be able to mix VL guys into a network with FGL frames (say, having VL =
guys at the edge), then option 3 allows this.</div>
<div><br>
</div>
<div>So hopefully everyone understands the implications of option 2 fully b=
efore voting. &nbsp;As I said, I don't know about whether there are VL chip=
s that would require a hardware upgrade to become FGL-safe. &nbsp;Assuming =
there are none, then I'm quite happy with
 option 2. &nbsp; And actually, it looks like people are converging on opti=
on 2 (though I hope it's based on fully understanding option 2). &nbsp;Now =
is the time for people to speak up, that know of problems this would cause.=
..for instance, needing to have non-upgradable
 VL guys at the edge for a long time.</div>
<div><br>
</div>
<div>Radia</div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_DD5FC8DE455C3348B94340C0AB5517334F65191Fnkgeml501mbschi_--

From radiaperlman@gmail.com  Fri Feb  1 02:45:39 2013
Return-Path: <radiaperlman@gmail.com>
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 D754F21F8826 for <trill@ietfa.amsl.com>; Fri,  1 Feb 2013 02:45:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.949
X-Spam-Level: *
X-Spam-Status: No, score=1.949 tagged_above=-999 required=5 tests=[AWL=-3.947,  BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, J_CHICKENPOX_31=0.6, J_CHICKENPOX_34=0.6, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, NO_RELAYS=-0.001, SARE_SUB_ENC_GB2312=1.345]
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 pNlIFC8Knm0n for <trill@ietfa.amsl.com>; Fri,  1 Feb 2013 02:45:38 -0800 (PST)
Received: from mail-la0-x233.google.com (mail-la0-x233.google.com [IPv6:2a00:1450:4010:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id 09E8921F881E for <trill@ietf.org>; Fri,  1 Feb 2013 02:45:31 -0800 (PST)
Received: by mail-la0-f51.google.com with SMTP id fo13so2702934lab.38 for <trill@ietf.org>; Fri, 01 Feb 2013 02:45:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=jTv2qT3OF7sycH+5NpPATjSTmk0ZLSHdVPwuy2ZSRYo=; b=jIVcVAxvVOEP5JMu/+bblBt0fvevRX/Ovv2PkTN5oZZeTqS22yPdeOA7UrKtb7mO2N 6JPeXS3JMJW/TVHz2FJNDLeIoj3gp/GLLu+noBwqdJNwBSkl9yE229fFUY2VnVdGywgO lPTSw4ehWOjvBb7Q850aGtAnwVwuwg82nxga7BM4rTSydw01/263qtB0YEqQV/dDGVry Y3LrcIqPiTymTxPLb6nWd1yjRPJsn3eCqD3NfO8OwkeaFYwGTcbIcQxDXZZFPA5Q2IEy LGXy4RhhaJlSB528XSqjZqyMTe/MDn3GNCfD5J24J9QBPOz/63wSs4KOucPbmtLFDYUF NDWw==
MIME-Version: 1.0
X-Received: by 10.152.123.34 with SMTP id lx2mr10735956lab.52.1359715530865; Fri, 01 Feb 2013 02:45:30 -0800 (PST)
Received: by 10.112.64.17 with HTTP; Fri, 1 Feb 2013 02:45:30 -0800 (PST)
In-Reply-To: <DD5FC8DE455C3348B94340C0AB5517334F65191F@nkgeml501-mbs.china.huawei.com>
References: <CAFOuuo67iBR2JkDtwPFCkrKHs3Fp4U_L1jkmNz5sfht6y05YMw@mail.gmail.com> <CA+-tSzx0E3J4i5Dvfbj4egruCeGi7z1se1Jn5RXtx3RedQLPdg@mail.gmail.com> <CAHD03N89RNX4=XxRZpD+Y2PCktYf-FtVjyYJ5oFS3dui3SsXaA@mail.gmail.com> <CAF4+nEG7YKGzGmObAMaOxackivjJsALymqHX=6PKBd5qU-Z+zQ@mail.gmail.com> <CA+-tSzz0=oh6iB1e-ESyeOx2sCvBFXeVpzuNbKmUVhRNLScDgQ@mail.gmail.com> <CAF4+nEFLrJL=CgX9e6on-cgz89ugmu93P6u5kmODhUia3H7RLg@mail.gmail.com> <1F5A81AE-4B3C-45FD-B431-9BA0011EB085@gmail.com> <DC8898F8-75C0-4535-BA61-C54279901332@gmail.com> <43DF00BE-B5F6-48B9-B313-8D179354C7B7@gmail.com> <A9B8F2D5-C3D7-4688-A76D-ED19EC47E59F@gmail.com> <FBEA3E19AA24F847BA3AE74E2FE19356288F6978@xmb-rcd-x08.cisco.com> <CAFOuuo4jZMdvUU_2EzBj1MLp6k0e+AmW1+k1ai4Q_m4rA0ObMw@mail.gmail.com> <DD5FC8DE455C3348B94340C0AB5517334F65191F@nkgeml501-mbs.china.huawei.com>
Date: Fri, 1 Feb 2013 02:45:30 -0800
Message-ID: <CAFOuuo6=7OtsDW0UjRkhHpEaCaDs2n55Z7Au2Y_bY7nvDzkM5w@mail.gmail.com>
From: Radia Perlman <radiaperlman@gmail.com>
To: Haoweiguo <haoweiguo@huawei.com>
Content-Type: multipart/alternative; boundary=f46d0434bfea367c2804d4a77181
Cc: Anoop Ghanwani <anoop@alumni.duke.edu>, Ayan Banerjee <ayabaner@gmail.com>, Sam Aldrin <aldrin.ietf@gmail.com>, Donald Eastlake <d3e3e3@gmail.com>, "trill@ietf.org" <trill@ietf.org>, "Tissa Senevirathne \(tsenevir\)" <tsenevir@cisco.com>, Jon Hudson <jon.hudson@gmail.com>
Subject: Re: [trill] =?gb2312?b?tPC4tDogIEV4cGxhaW5pbmcgdGhyZWUgb3B0aW9ucyBm?= =?gb2312?b?b3IgdXBncmFkaW5nIHRvIEZHTCAoZmluZS1ncmFpbmVkLWxhYmVs?= =?gb2312?b?aW5nKQ==?=
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: Fri, 01 Feb 2013 10:45:40 -0000

--f46d0434bfea367c2804d4a77181
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

I think you were just misinterpreting what I wrote.  It is OK to let things
through that could be pruned.  It is *not* OK to falsely delete things.
The example I gave of interpreting the first FGL label as a VL label is
something that the RBridge MUST NOT do.

So we're not disagreeing.

Radia

On Fri, Feb 1, 2013 at 1:11 AM, Haoweiguo <haoweiguo@huawei.com> wrote:

>  Hi Radia,
>
> I agree with your definition of "Safe FGL",but I have a problem about the
> following point:
>
>
> b) multicast pruning: it's OK not to do pruning at all, or to actually
> look at all 24 bits of the FGL and prune as a proper FGL guy would do.  B=
ut
> an example of what you canNOT do is look at the first 12 bits of FGL,
> pretend it's the same as VL, and delete the multicast packet because nobo=
dy
> downstream is listening to that 12 bit VL value
>
> [weiguo]:If a switch performs pruning by first 12 bits of FGL, can the
> switch called "Safe FGL" switch? If downstream have one VL switch with VL=
AN
> is equal to first 12 bits of FGL,then the switch will forward multicast
> data frame to downstream VL switch.
> thanks
> weiguo
>  ------------------------------
> *=B7=A2=BC=FE=C8=CB:* Radia Perlman [radiaperlman@gmail.com]
> *=B7=A2=CB=CD=CA=B1=BC=E4:* 2013=C4=EA2=D4=C21=C8=D5 4:24
>
> *=B5=BD:* Tissa Senevirathne (tsenevir)
> *Cc:* Anoop Ghanwani; Ayan Banerjee; Sam Aldrin; trill@ietf.org; Donald
> Eastlake; Jon Hudson
> *=D6=F7=CC=E2:* Re: [trill] Explaining three options for upgrading to FGL
> (fine-grained-labeling)
>
>   Tissa said:
> >> how can you make sure all of the so called "Safe FGL" have consistent
> behavior
>
> "Safe FGL" need not all have the *same* behavior as each other...they
> just have to do "nothing bad" with an FGL frame.  It's worth summarizing
> (again) what it means to be "FGL-safe", which allows you to coexist safel=
y
> with FGL frames.  To be FGL-safe you must do the following:
>
> a) unicast: you MUST NOT drop a packet because of seeing the unrecognized
> FGL tag.  You also MUST NOT get confused and do flow hashing improperly
> (choosing different paths for packets for the same flow).
>
> b) multicast pruning: it's OK not to do pruning at all, or to actually
> look at all 24 bits of the FGL and prune as a proper FGL guy would do.  B=
ut
> an example of what you canNOT do is look at the first 12 bits of FGL,
> pretend it's the same as VL, and delete the multicast packet because nobo=
dy
> downstream is listening to that 12 bit VL value
>
> c) egress of either unicast or multicast:  you MUST NOT egress an FGL
> frame onto a link that is not supposed to get that FGL value
>
> d) you have to advertise that you are FGL-safe...otherwise other RBs will
> assume you are VL ("FGL-unsafe")
>
> ---------
> Also, TIssa said:
> >>Do you agree if we say, FGL will always be core of the network, and VL
> will be at the edge of the network ?
>
> With option 2, a VL guy *cannot even be at the edge of a network with FGL
> links* unless it is upgraded to FGL-safe AND advertises that it is
> FGL-safe.  Option 2 says a VL guy is completely ostrasized once FGL-label=
ed
> links are introduced.  There is NO coexistence of VL guys and FGL-links.
> The only kinds of coexistence in option 2 are:
>
> a) VL and FGL-safe RBridge, but no actual FGL links yet.
> b) FGL-safe guys, even if some of them don't really understand FGL, but
> just don't do "anything bad" with it, and FGL frames.
>
> So...again...the migration phases in option 2 are
> 1) VL-only (today's deployment), then
> 2) A mixture of VL and FGL-safe, until
> 3) EVERYone upgraded to FGL-safe, then
> 4) FGL-links can be introduced.
>
>
> ----
> Also, Tissa said:
> >>what about some devices who are not "safe FGL" and so on, are we saying
> do not buy no safe FGL devices, if you do that you cannot get FGL interop=
 ?
>
> *If* it's important to have VL guys as transit, and they cannot be
> upgraded to FGL-safe because upgrading requires a hardware change (it
> involves parsing data packets), then we are stuck with option 3.  In opti=
on
> 3, we can forever have VL guys at the edge speaking through an FGL-safe o=
r
> full-FGL core.  In option 2, as I said, there is *no coexistence* of VL
> guys, *even at the edg*e, once FGL links are introduced.  In option 2, a
> VL guy, even at the edge, will be ostrasized completely once anyone
> advertises connectivity to an FGL link.
>
> I personally like option 2, because it's simple, but as Einstein said
> "make things as simple as possible, but no simpler".  We have to make sur=
e
> that everyone understands the implications of option 2, and can live with
> them.  To summarize again (since there seems to be some confusion about
> what the implications of option 2 are),
>
> If we can upgrade all existing VL implementations to FGL-safe through
> software upgrade only, then option 2 provides smooth migration by changin=
g
> ALL RBridges (edge as well as transit) to FGL-safe, and only after ALL of
> them are upgraded, then FGL-labeled links can be introduced.  If there ar=
e
> any remaining VL guys once FGL-labeled links are introduced, the VL guys
> are ostrasized, *even if they are just at the edge.*
>
> If we canNOT upgrade all existing VL to FGL-safe, AND if it's important t=
o
> be able to mix VL guys into a network with FGL frames (say, having VL guy=
s
> at the edge), then option 3 allows this.
>
> So hopefully everyone understands the implications of option 2 fully
> before voting.  As I said, I don't know about whether there are VL chips
> that would require a hardware upgrade to become FGL-safe.  Assuming there
> are none, then I'm quite happy with option 2.   And actually, it looks li=
ke
> people are converging on option 2 (though I hope it's based on fully
> understanding option 2).  Now is the time for people to speak up, that kn=
ow
> of problems this would cause...for instance, needing to have non-upgradab=
le
> VL guys at the edge for a long time.
>
> Radia
>
>
>

--f46d0434bfea367c2804d4a77181
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: quoted-printable

<div>I think you were just misinterpreting what I wrote.&nbsp; It is OK to =
let things through that could be pruned.&nbsp; It is <em><u><strong>not</st=
rong></u></em> OK to falsely delete things.&nbsp; The example I gave of int=
erpreting the first FGL label as a VL label is something that the RBridge M=
UST NOT do.</div>

<div>&nbsp;</div>
<div>So we&#39;re not disagreeing.</div>
<div>&nbsp;</div>
<div>Radia<br><br></div>
<div class=3D"gmail_quote">On Fri, Feb 1, 2013 at 1:11 AM, Haoweiguo <span =
dir=3D"ltr">&lt;<a href=3D"mailto:haoweiguo@huawei.com" target=3D"_blank">h=
aoweiguo@huawei.com</a>&gt;</span> wrote:<br>
<blockquote style=3D"BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PA=
DDING-LEFT:1ex" class=3D"gmail_quote">
<div>
<div style=3D"FONT-FAMILY:Tahoma;DIRECTION:ltr;FONT-SIZE:10pt">
<p>Hi Radia,</p>
<p>I agree with your definition of &quot;Safe FGL&quot;,but I have a proble=
m about the following point:</p>
<div class=3D"im">
<p>&nbsp;</p>
<div>b) multicast pruning: it&#39;s OK not to do pruning at all, or to actu=
ally look at all 24 bits of the FGL and prune as a proper FGL guy would do.=
 &nbsp;But an example of what you canNOT do is look at the first 12 bits of=
 FGL, pretend it&#39;s the same as VL, and delete the multicast packet beca=
use nobody downstream is listening to that 12 bit VL value</div>

<div>&nbsp;</div></div>
<div>[weiguo]:If a switch performs pruning by first 12 bits of FGL, can the=
 switch called &quot;Safe FGL&quot; switch? If downstream have one VL switc=
h with VLAN is equal to first 12 bits of FGL,then the switch will forward m=
ulticast data frame to downstream VL switch.</div>

<div>thanks</div>
<div>weiguo</div>
<div style=3D"FONT-FAMILY:Times New Roman;FONT-SIZE:16px">
<hr>

<div style=3D"DIRECTION:ltr"><font color=3D"#000000" face=3D"Tahoma"><b>=B7=
=A2=BC=FE=C8=CB:</b> Radia Perlman [<a href=3D"mailto:radiaperlman@gmail.co=
m" target=3D"_blank">radiaperlman@gmail.com</a>]<br><b>=B7=A2=CB=CD=CA=B1=
=BC=E4:</b> 2013=C4=EA2=D4=C21=C8=D5 4:24=20
<div class=3D"im"><br><b>=B5=BD:</b> Tissa Senevirathne (tsenevir)<br><b>Cc=
:</b> Anoop Ghanwani; Ayan Banerjee; Sam Aldrin; <a href=3D"mailto:trill@ie=
tf.org" target=3D"_blank">trill@ietf.org</a>; Donald Eastlake; Jon Hudson<b=
r></div>
<b>=D6=F7=CC=E2:</b> Re: [trill] Explaining three options for upgrading to =
FGL (fine-grained-labeling)<br></font><br></div>
<div>
<div class=3D"h5">
<div></div>
<div>Tissa said:=20
<div>&gt;&gt;&nbsp;how can you make sure all of the so called &quot;Safe FG=
L&quot; have consistent behavior<br>
<div><br></div>
<div>&quot;Safe FGL&quot; need not all have the <i><b>same</b></i> behavior=
 as each other...they just have to do &quot;nothing bad&quot; with an FGL f=
rame. &nbsp;It&#39;s worth summarizing (again) what it means to be &quot;FG=
L-safe&quot;, which allows you to coexist safely with FGL frames. &nbsp;To =
be FGL-safe you must do the following:</div>

<div>
<div><br></div>
<div>a) unicast: you MUST NOT drop a packet because of seeing the unrecogni=
zed FGL tag. &nbsp;You also MUST NOT get confused and do flow hashing impro=
perly (choosing different paths for packets for the same flow).</div>
<div><br></div>
<div>b) multicast pruning: it&#39;s OK not to do pruning at all, or to actu=
ally look at all 24 bits of the FGL and prune as a proper FGL guy would do.=
 &nbsp;But an example of what you canNOT do is look at the first 12 bits of=
 FGL, pretend it&#39;s the same as VL, and delete the multicast packet beca=
use nobody downstream is listening to that 12 bit VL value</div>

<div><br></div>
<div>c) egress of either unicast or multicast: &nbsp;you MUST NOT egress an=
 FGL frame onto a link that is not supposed to get that FGL value</div>
<div><br></div>
<div>d) you have to advertise that you are FGL-safe...otherwise other RBs w=
ill assume you are VL (&quot;FGL-unsafe&quot;)</div>
<div><br></div>
<div>---------</div>
<div>Also, TIssa said:</div>
<div>&gt;&gt;Do you agree if we say, FGL will always be core of the network=
, and VL will be at the edge of the network ?</div>
<div><br></div>
<div>With option 2, a VL guy <i><u>cannot even be at the edge of a network =
with FGL links</u></i> unless it is upgraded to FGL-safe AND advertises tha=
t it is FGL-safe. &nbsp;Option 2 says a VL guy is completely ostrasized onc=
e FGL-labeled links are introduced. &nbsp;There is NO coexistence of VL guy=
s and FGL-links. The only kinds of coexistence in option 2 are:</div>

<div><br></div>
<div>a) VL and FGL-safe RBridge, but no actual FGL links yet.</div>
<div>b) FGL-safe guys, even if some of them don&#39;t really understand FGL=
, but just don&#39;t do &quot;anything bad&quot; with it, and FGL frames.</=
div>
<div><br></div>
<div>So...again...the migration phases in option 2 are</div>
<div>1) VL-only (today&#39;s deployment), then</div>
<div>2) A mixture of VL and FGL-safe, until</div>
<div>3) EVERYone upgraded to FGL-safe, then</div>
<div>4) FGL-links can be introduced.</div>
<div><br></div>
<div><br></div>
<div>----</div>
<div>Also, Tissa said:</div>
<div>&gt;&gt;what about some devices who are not &quot;safe FGL&quot; and s=
o on, are we saying do not buy no safe FGL devices, if you do that you cann=
ot get FGL interop ?&nbsp;</div>
<div><br></div>
<div><b><i><u>If</u></i></b> it&#39;s important to have VL guys as transit,=
 and they cannot be upgraded to FGL-safe because upgrading requires a hardw=
are change (it involves parsing data packets), then we are stuck with optio=
n 3. &nbsp;In option 3, we can forever have VL guys at the edge speaking th=
rough an FGL-safe or full-FGL core. &nbsp;In option 2, as I said, there is =
<i><u>no coexistence</u></i> of VL guys, <i><u>even at the edg</u></i>e, on=
ce FGL links are introduced. &nbsp;In option 2, a VL guy, even at the edge,=
 will be ostrasized completely once anyone advertises connectivity to an FG=
L link.</div>

<div><br></div>
<div>I personally like option 2, because it&#39;s simple, but as Einstein s=
aid &quot;make things as simple as possible, but no simpler&quot;. &nbsp;We=
 have to make sure that everyone understands the implications of option 2, =
and can live with them. &nbsp;To summarize again (since there seems to be s=
ome confusion about what the implications of option 2 are),</div>

<div><br></div>
<div>If we can upgrade all existing VL implementations to FGL-safe through =
software upgrade only, then option 2 provides smooth migration by changing =
ALL RBridges (edge as well as transit) to FGL-safe, and only after ALL of t=
hem are upgraded, then FGL-labeled links can be introduced. &nbsp;If there =
are any remaining VL guys once FGL-labeled links are introduced, the VL guy=
s are ostrasized, <i><u>even if they are just at the edge.</u></i></div>

<div><br></div>
<div>If we canNOT upgrade all existing VL to FGL-safe, AND if it&#39;s impo=
rtant to be able to mix VL guys into a network with FGL frames (say, having=
 VL guys at the edge), then option 3 allows this.</div>
<div><br></div>
<div>So hopefully everyone understands the implications of option 2 fully b=
efore voting. &nbsp;As I said, I don&#39;t know about whether there are VL =
chips that would require a hardware upgrade to become FGL-safe. &nbsp;Assum=
ing there are none, then I&#39;m quite happy with option 2. &nbsp; And actu=
ally, it looks like people are converging on option 2 (though I hope it&#39=
;s based on fully understanding option 2). &nbsp;Now is the time for people=
 to speak up, that know of problems this would cause...for instance, needin=
g to have non-upgradable VL guys at the edge for a long time.</div>

<div><br></div>
<div>Radia</div>
<div><br></div>
<div><br></div></div></div></div></div></div></div></div></div></blockquote=
></div><br>

--f46d0434bfea367c2804d4a77181--

From haoweiguo@huawei.com  Sat Feb  2 05:50:43 2013
Return-Path: <haoweiguo@huawei.com>
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 3CAB221F8895 for <trill@ietfa.amsl.com>; Sat,  2 Feb 2013 05:50:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.009
X-Spam-Level: ***
X-Spam-Status: No, score=3.009 tagged_above=-999 required=5 tests=[AWL=-0.040,  BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, J_CHICKENPOX_34=0.6, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
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 pWwn1B8PmANc for <trill@ietfa.amsl.com>; Sat,  2 Feb 2013 05:50:42 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id EA02F21F8799 for <trill@ietf.org>; Sat,  2 Feb 2013 05:50:40 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id APJ24794; Sat, 02 Feb 2013 13:50:39 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Sat, 2 Feb 2013 13:49:55 +0000
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Sat, 2 Feb 2013 13:50:37 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.101]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.01.0323.007; Sat, 2 Feb 2013 21:50:32 +0800
From: Haoweiguo <haoweiguo@huawei.com>
To: Radia Perlman <radiaperlman@gmail.com>
Thread-Topic: =?gb2312?B?tPC4tDogW3RyaWxsXSBFeHBsYWluaW5nIHRocmVlIG9wdGlvbnMgZm9yIHVw?= =?gb2312?Q?grading_to_FGL_(fine-grained-labeling)?=
Thread-Index: AQHOAGlH+f/1qQf5wku+4o3KC8rew5hmlp7g
Date: Sat, 2 Feb 2013 13:50:31 +0000
Message-ID: <DD5FC8DE455C3348B94340C0AB5517334F6519AC@nkgeml501-mbs.china.huawei.com>
References: <CAFOuuo67iBR2JkDtwPFCkrKHs3Fp4U_L1jkmNz5sfht6y05YMw@mail.gmail.com> <CA+-tSzx0E3J4i5Dvfbj4egruCeGi7z1se1Jn5RXtx3RedQLPdg@mail.gmail.com> <CAHD03N89RNX4=XxRZpD+Y2PCktYf-FtVjyYJ5oFS3dui3SsXaA@mail.gmail.com> <CAF4+nEG7YKGzGmObAMaOxackivjJsALymqHX=6PKBd5qU-Z+zQ@mail.gmail.com> <CA+-tSzz0=oh6iB1e-ESyeOx2sCvBFXeVpzuNbKmUVhRNLScDgQ@mail.gmail.com> <CAF4+nEFLrJL=CgX9e6on-cgz89ugmu93P6u5kmODhUia3H7RLg@mail.gmail.com> <1F5A81AE-4B3C-45FD-B431-9BA0011EB085@gmail.com> <DC8898F8-75C0-4535-BA61-C54279901332@gmail.com> <43DF00BE-B5F6-48B9-B313-8D179354C7B7@gmail.com> <A9B8F2D5-C3D7-4688-A76D-ED19EC47E59F@gmail.com> <FBEA3E19AA24F847BA3AE74E2FE19356288F6978@xmb-rcd-x08.cisco.com> <CAFOuuo4jZMdvUU_2EzBj1MLp6k0e+AmW1+k1ai4Q_m4rA0ObMw@mail.gmail.com> <DD5FC8DE455C3348B94340C0AB5517334F65191F@nkgeml501-mbs.china.huawei.com>, <CAFOuuo6=7OtsDW0UjRkhHpEaCaDs2n55Z7Au2Y_bY7nvDzkM5w@mail.gmail.com>
In-Reply-To: <CAFOuuo6=7OtsDW0UjRkhHpEaCaDs2n55Z7Au2Y_bY7nvDzkM5w@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.105.178]
Content-Type: multipart/alternative; boundary="_000_DD5FC8DE455C3348B94340C0AB5517334F6519ACnkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: Anoop Ghanwani <anoop@alumni.duke.edu>, Ayan Banerjee <ayabaner@gmail.com>, Sam Aldrin <aldrin.ietf@gmail.com>, Donald Eastlake <d3e3e3@gmail.com>, "trill@ietf.org" <trill@ietf.org>, "Tissa Senevirathne \(tsenevir\)" <tsenevir@cisco.com>, Jon Hudson <jon.hudson@gmail.com>
Subject: [trill] =?gb2312?b?tPC4tDogtPC4tDogIEV4cGxhaW5pbmcgdGhyZWUgb3B0?= =?gb2312?b?aW9ucyBmb3IgdXBncmFkaW5nIHRvIEZHTCAoZmluZS1ncmFpbmVkLWxhYmVs?= =?gb2312?b?aW5nKQ==?=
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: Sat, 02 Feb 2013 13:50:43 -0000

--_000_DD5FC8DE455C3348B94340C0AB5517334F6519ACnkgeml501mbschi_
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64

T0suIEkgdW5kZXJzdGFuZC4gSSBhZ3JlZSB3aXRoIHlvdXIgZGVmaW5pdGlvbiBvZiAic2FmZSBG
R0wiLg0KDQp0aGFua3MNCg0Kd2VpZ3VvDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fDQq3orz+yMs6IFJhZGlhIFBlcmxtYW4gW3JhZGlhcGVybG1hbkBnbWFpbC5jb21dDQq3osvN
yrG85DogMjAxM8TqMtTCMcjVIDE4OjQ1DQq1vTogSGFvd2VpZ3VvDQpDYzogVGlzc2EgU2VuZXZp
cmF0aG5lICh0c2VuZXZpcik7IEFub29wIEdoYW53YW5pOyBBeWFuIEJhbmVyamVlOyBTYW0gQWxk
cmluOyB0cmlsbEBpZXRmLm9yZzsgRG9uYWxkIEVhc3RsYWtlOyBKb24gSHVkc29uDQrW98ziOiBS
ZTogtPC4tDogW3RyaWxsXSBFeHBsYWluaW5nIHRocmVlIG9wdGlvbnMgZm9yIHVwZ3JhZGluZyB0
byBGR0wgKGZpbmUtZ3JhaW5lZC1sYWJlbGluZykNCg0KSSB0aGluayB5b3Ugd2VyZSBqdXN0IG1p
c2ludGVycHJldGluZyB3aGF0IEkgd3JvdGUuICBJdCBpcyBPSyB0byBsZXQgdGhpbmdzIHRocm91
Z2ggdGhhdCBjb3VsZCBiZSBwcnVuZWQuICBJdCBpcyBub3QgT0sgdG8gZmFsc2VseSBkZWxldGUg
dGhpbmdzLiAgVGhlIGV4YW1wbGUgSSBnYXZlIG9mIGludGVycHJldGluZyB0aGUgZmlyc3QgRkdM
IGxhYmVsIGFzIGEgVkwgbGFiZWwgaXMgc29tZXRoaW5nIHRoYXQgdGhlIFJCcmlkZ2UgTVVTVCBO
T1QgZG8uDQoNClNvIHdlJ3JlIG5vdCBkaXNhZ3JlZWluZy4NCg0KUmFkaWENCg0KT24gRnJpLCBG
ZWIgMSwgMjAxMyBhdCAxOjExIEFNLCBIYW93ZWlndW8gPGhhb3dlaWd1b0BodWF3ZWkuY29tPG1h
aWx0bzpoYW93ZWlndW9AaHVhd2VpLmNvbT4+IHdyb3RlOg0KDQpIaSBSYWRpYSwNCg0KSSBhZ3Jl
ZSB3aXRoIHlvdXIgZGVmaW5pdGlvbiBvZiAiU2FmZSBGR0wiLGJ1dCBJIGhhdmUgYSBwcm9ibGVt
IGFib3V0IHRoZSBmb2xsb3dpbmcgcG9pbnQ6DQoNCg0KDQpiKSBtdWx0aWNhc3QgcHJ1bmluZzog
aXQncyBPSyBub3QgdG8gZG8gcHJ1bmluZyBhdCBhbGwsIG9yIHRvIGFjdHVhbGx5IGxvb2sgYXQg
YWxsIDI0IGJpdHMgb2YgdGhlIEZHTCBhbmQgcHJ1bmUgYXMgYSBwcm9wZXIgRkdMIGd1eSB3b3Vs
ZCBkby4gIEJ1dCBhbiBleGFtcGxlIG9mIHdoYXQgeW91IGNhbk5PVCBkbyBpcyBsb29rIGF0IHRo
ZSBmaXJzdCAxMiBiaXRzIG9mIEZHTCwgcHJldGVuZCBpdCdzIHRoZSBzYW1lIGFzIFZMLCBhbmQg
ZGVsZXRlIHRoZSBtdWx0aWNhc3QgcGFja2V0IGJlY2F1c2Ugbm9ib2R5IGRvd25zdHJlYW0gaXMg
bGlzdGVuaW5nIHRvIHRoYXQgMTIgYml0IFZMIHZhbHVlDQoNClt3ZWlndW9dOklmIGEgc3dpdGNo
IHBlcmZvcm1zIHBydW5pbmcgYnkgZmlyc3QgMTIgYml0cyBvZiBGR0wsIGNhbiB0aGUgc3dpdGNo
IGNhbGxlZCAiU2FmZSBGR0wiIHN3aXRjaD8gSWYgZG93bnN0cmVhbSBoYXZlIG9uZSBWTCBzd2l0
Y2ggd2l0aCBWTEFOIGlzIGVxdWFsIHRvIGZpcnN0IDEyIGJpdHMgb2YgRkdMLHRoZW4gdGhlIHN3
aXRjaCB3aWxsIGZvcndhcmQgbXVsdGljYXN0IGRhdGEgZnJhbWUgdG8gZG93bnN0cmVhbSBWTCBz
d2l0Y2guDQp0aGFua3MNCndlaWd1bw0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N
CreivP7IyzogUmFkaWEgUGVybG1hbiBbcmFkaWFwZXJsbWFuQGdtYWlsLmNvbTxtYWlsdG86cmFk
aWFwZXJsbWFuQGdtYWlsLmNvbT5dDQq3osvNyrG85DogMjAxM8TqMtTCMcjVIDQ6MjQNCg0Ktb06
IFRpc3NhIFNlbmV2aXJhdGhuZSAodHNlbmV2aXIpDQpDYzogQW5vb3AgR2hhbndhbmk7IEF5YW4g
QmFuZXJqZWU7IFNhbSBBbGRyaW47IHRyaWxsQGlldGYub3JnPG1haWx0bzp0cmlsbEBpZXRmLm9y
Zz47IERvbmFsZCBFYXN0bGFrZTsgSm9uIEh1ZHNvbg0K1vfM4jogUmU6IFt0cmlsbF0gRXhwbGFp
bmluZyB0aHJlZSBvcHRpb25zIGZvciB1cGdyYWRpbmcgdG8gRkdMIChmaW5lLWdyYWluZWQtbGFi
ZWxpbmcpDQoNClRpc3NhIHNhaWQ6DQo+PiBob3cgY2FuIHlvdSBtYWtlIHN1cmUgYWxsIG9mIHRo
ZSBzbyBjYWxsZWQgIlNhZmUgRkdMIiBoYXZlIGNvbnNpc3RlbnQgYmVoYXZpb3INCg0KIlNhZmUg
RkdMIiBuZWVkIG5vdCBhbGwgaGF2ZSB0aGUgc2FtZSBiZWhhdmlvciBhcyBlYWNoIG90aGVyLi4u
dGhleSBqdXN0IGhhdmUgdG8gZG8gIm5vdGhpbmcgYmFkIiB3aXRoIGFuIEZHTCBmcmFtZS4gIEl0
J3Mgd29ydGggc3VtbWFyaXppbmcgKGFnYWluKSB3aGF0IGl0IG1lYW5zIHRvIGJlICJGR0wtc2Fm
ZSIsIHdoaWNoIGFsbG93cyB5b3UgdG8gY29leGlzdCBzYWZlbHkgd2l0aCBGR0wgZnJhbWVzLiAg
VG8gYmUgRkdMLXNhZmUgeW91IG11c3QgZG8gdGhlIGZvbGxvd2luZzoNCg0KYSkgdW5pY2FzdDog
eW91IE1VU1QgTk9UIGRyb3AgYSBwYWNrZXQgYmVjYXVzZSBvZiBzZWVpbmcgdGhlIHVucmVjb2du
aXplZCBGR0wgdGFnLiAgWW91IGFsc28gTVVTVCBOT1QgZ2V0IGNvbmZ1c2VkIGFuZCBkbyBmbG93
IGhhc2hpbmcgaW1wcm9wZXJseSAoY2hvb3NpbmcgZGlmZmVyZW50IHBhdGhzIGZvciBwYWNrZXRz
IGZvciB0aGUgc2FtZSBmbG93KS4NCg0KYikgbXVsdGljYXN0IHBydW5pbmc6IGl0J3MgT0sgbm90
IHRvIGRvIHBydW5pbmcgYXQgYWxsLCBvciB0byBhY3R1YWxseSBsb29rIGF0IGFsbCAyNCBiaXRz
IG9mIHRoZSBGR0wgYW5kIHBydW5lIGFzIGEgcHJvcGVyIEZHTCBndXkgd291bGQgZG8uICBCdXQg
YW4gZXhhbXBsZSBvZiB3aGF0IHlvdSBjYW5OT1QgZG8gaXMgbG9vayBhdCB0aGUgZmlyc3QgMTIg
Yml0cyBvZiBGR0wsIHByZXRlbmQgaXQncyB0aGUgc2FtZSBhcyBWTCwgYW5kIGRlbGV0ZSB0aGUg
bXVsdGljYXN0IHBhY2tldCBiZWNhdXNlIG5vYm9keSBkb3duc3RyZWFtIGlzIGxpc3RlbmluZyB0
byB0aGF0IDEyIGJpdCBWTCB2YWx1ZQ0KDQpjKSBlZ3Jlc3Mgb2YgZWl0aGVyIHVuaWNhc3Qgb3Ig
bXVsdGljYXN0OiAgeW91IE1VU1QgTk9UIGVncmVzcyBhbiBGR0wgZnJhbWUgb250byBhIGxpbmsg
dGhhdCBpcyBub3Qgc3VwcG9zZWQgdG8gZ2V0IHRoYXQgRkdMIHZhbHVlDQoNCmQpIHlvdSBoYXZl
IHRvIGFkdmVydGlzZSB0aGF0IHlvdSBhcmUgRkdMLXNhZmUuLi5vdGhlcndpc2Ugb3RoZXIgUkJz
IHdpbGwgYXNzdW1lIHlvdSBhcmUgVkwgKCJGR0wtdW5zYWZlIikNCg0KLS0tLS0tLS0tDQpBbHNv
LCBUSXNzYSBzYWlkOg0KPj5EbyB5b3UgYWdyZWUgaWYgd2Ugc2F5LCBGR0wgd2lsbCBhbHdheXMg
YmUgY29yZSBvZiB0aGUgbmV0d29yaywgYW5kIFZMIHdpbGwgYmUgYXQgdGhlIGVkZ2Ugb2YgdGhl
IG5ldHdvcmsgPw0KDQpXaXRoIG9wdGlvbiAyLCBhIFZMIGd1eSBjYW5ub3QgZXZlbiBiZSBhdCB0
aGUgZWRnZSBvZiBhIG5ldHdvcmsgd2l0aCBGR0wgbGlua3MgdW5sZXNzIGl0IGlzIHVwZ3JhZGVk
IHRvIEZHTC1zYWZlIEFORCBhZHZlcnRpc2VzIHRoYXQgaXQgaXMgRkdMLXNhZmUuICBPcHRpb24g
MiBzYXlzIGEgVkwgZ3V5IGlzIGNvbXBsZXRlbHkgb3N0cmFzaXplZCBvbmNlIEZHTC1sYWJlbGVk
IGxpbmtzIGFyZSBpbnRyb2R1Y2VkLiAgVGhlcmUgaXMgTk8gY29leGlzdGVuY2Ugb2YgVkwgZ3V5
cyBhbmQgRkdMLWxpbmtzLiBUaGUgb25seSBraW5kcyBvZiBjb2V4aXN0ZW5jZSBpbiBvcHRpb24g
MiBhcmU6DQoNCmEpIFZMIGFuZCBGR0wtc2FmZSBSQnJpZGdlLCBidXQgbm8gYWN0dWFsIEZHTCBs
aW5rcyB5ZXQuDQpiKSBGR0wtc2FmZSBndXlzLCBldmVuIGlmIHNvbWUgb2YgdGhlbSBkb24ndCBy
ZWFsbHkgdW5kZXJzdGFuZCBGR0wsIGJ1dCBqdXN0IGRvbid0IGRvICJhbnl0aGluZyBiYWQiIHdp
dGggaXQsIGFuZCBGR0wgZnJhbWVzLg0KDQpTby4uLmFnYWluLi4udGhlIG1pZ3JhdGlvbiBwaGFz
ZXMgaW4gb3B0aW9uIDIgYXJlDQoxKSBWTC1vbmx5ICh0b2RheSdzIGRlcGxveW1lbnQpLCB0aGVu
DQoyKSBBIG1peHR1cmUgb2YgVkwgYW5kIEZHTC1zYWZlLCB1bnRpbA0KMykgRVZFUllvbmUgdXBn
cmFkZWQgdG8gRkdMLXNhZmUsIHRoZW4NCjQpIEZHTC1saW5rcyBjYW4gYmUgaW50cm9kdWNlZC4N
Cg0KDQotLS0tDQpBbHNvLCBUaXNzYSBzYWlkOg0KPj53aGF0IGFib3V0IHNvbWUgZGV2aWNlcyB3
aG8gYXJlIG5vdCAic2FmZSBGR0wiIGFuZCBzbyBvbiwgYXJlIHdlIHNheWluZyBkbyBub3QgYnV5
IG5vIHNhZmUgRkdMIGRldmljZXMsIGlmIHlvdSBkbyB0aGF0IHlvdSBjYW5ub3QgZ2V0IEZHTCBp
bnRlcm9wID8NCg0KSWYgaXQncyBpbXBvcnRhbnQgdG8gaGF2ZSBWTCBndXlzIGFzIHRyYW5zaXQs
IGFuZCB0aGV5IGNhbm5vdCBiZSB1cGdyYWRlZCB0byBGR0wtc2FmZSBiZWNhdXNlIHVwZ3JhZGlu
ZyByZXF1aXJlcyBhIGhhcmR3YXJlIGNoYW5nZSAoaXQgaW52b2x2ZXMgcGFyc2luZyBkYXRhIHBh
Y2tldHMpLCB0aGVuIHdlIGFyZSBzdHVjayB3aXRoIG9wdGlvbiAzLiAgSW4gb3B0aW9uIDMsIHdl
IGNhbiBmb3JldmVyIGhhdmUgVkwgZ3V5cyBhdCB0aGUgZWRnZSBzcGVha2luZyB0aHJvdWdoIGFu
IEZHTC1zYWZlIG9yIGZ1bGwtRkdMIGNvcmUuICBJbiBvcHRpb24gMiwgYXMgSSBzYWlkLCB0aGVy
ZSBpcyBubyBjb2V4aXN0ZW5jZSBvZiBWTCBndXlzLCBldmVuIGF0IHRoZSBlZGdlLCBvbmNlIEZH
TCBsaW5rcyBhcmUgaW50cm9kdWNlZC4gIEluIG9wdGlvbiAyLCBhIFZMIGd1eSwgZXZlbiBhdCB0
aGUgZWRnZSwgd2lsbCBiZSBvc3RyYXNpemVkIGNvbXBsZXRlbHkgb25jZSBhbnlvbmUgYWR2ZXJ0
aXNlcyBjb25uZWN0aXZpdHkgdG8gYW4gRkdMIGxpbmsuDQoNCkkgcGVyc29uYWxseSBsaWtlIG9w
dGlvbiAyLCBiZWNhdXNlIGl0J3Mgc2ltcGxlLCBidXQgYXMgRWluc3RlaW4gc2FpZCAibWFrZSB0
aGluZ3MgYXMgc2ltcGxlIGFzIHBvc3NpYmxlLCBidXQgbm8gc2ltcGxlciIuICBXZSBoYXZlIHRv
IG1ha2Ugc3VyZSB0aGF0IGV2ZXJ5b25lIHVuZGVyc3RhbmRzIHRoZSBpbXBsaWNhdGlvbnMgb2Yg
b3B0aW9uIDIsIGFuZCBjYW4gbGl2ZSB3aXRoIHRoZW0uICBUbyBzdW1tYXJpemUgYWdhaW4gKHNp
bmNlIHRoZXJlIHNlZW1zIHRvIGJlIHNvbWUgY29uZnVzaW9uIGFib3V0IHdoYXQgdGhlIGltcGxp
Y2F0aW9ucyBvZiBvcHRpb24gMiBhcmUpLA0KDQpJZiB3ZSBjYW4gdXBncmFkZSBhbGwgZXhpc3Rp
bmcgVkwgaW1wbGVtZW50YXRpb25zIHRvIEZHTC1zYWZlIHRocm91Z2ggc29mdHdhcmUgdXBncmFk
ZSBvbmx5LCB0aGVuIG9wdGlvbiAyIHByb3ZpZGVzIHNtb290aCBtaWdyYXRpb24gYnkgY2hhbmdp
bmcgQUxMIFJCcmlkZ2VzIChlZGdlIGFzIHdlbGwgYXMgdHJhbnNpdCkgdG8gRkdMLXNhZmUsIGFu
ZCBvbmx5IGFmdGVyIEFMTCBvZiB0aGVtIGFyZSB1cGdyYWRlZCwgdGhlbiBGR0wtbGFiZWxlZCBs
aW5rcyBjYW4gYmUgaW50cm9kdWNlZC4gIElmIHRoZXJlIGFyZSBhbnkgcmVtYWluaW5nIFZMIGd1
eXMgb25jZSBGR0wtbGFiZWxlZCBsaW5rcyBhcmUgaW50cm9kdWNlZCwgdGhlIFZMIGd1eXMgYXJl
IG9zdHJhc2l6ZWQsIGV2ZW4gaWYgdGhleSBhcmUganVzdCBhdCB0aGUgZWRnZS4NCg0KSWYgd2Ug
Y2FuTk9UIHVwZ3JhZGUgYWxsIGV4aXN0aW5nIFZMIHRvIEZHTC1zYWZlLCBBTkQgaWYgaXQncyBp
bXBvcnRhbnQgdG8gYmUgYWJsZSB0byBtaXggVkwgZ3V5cyBpbnRvIGEgbmV0d29yayB3aXRoIEZH
TCBmcmFtZXMgKHNheSwgaGF2aW5nIFZMIGd1eXMgYXQgdGhlIGVkZ2UpLCB0aGVuIG9wdGlvbiAz
IGFsbG93cyB0aGlzLg0KDQpTbyBob3BlZnVsbHkgZXZlcnlvbmUgdW5kZXJzdGFuZHMgdGhlIGlt
cGxpY2F0aW9ucyBvZiBvcHRpb24gMiBmdWxseSBiZWZvcmUgdm90aW5nLiAgQXMgSSBzYWlkLCBJ
IGRvbid0IGtub3cgYWJvdXQgd2hldGhlciB0aGVyZSBhcmUgVkwgY2hpcHMgdGhhdCB3b3VsZCBy
ZXF1aXJlIGEgaGFyZHdhcmUgdXBncmFkZSB0byBiZWNvbWUgRkdMLXNhZmUuICBBc3N1bWluZyB0
aGVyZSBhcmUgbm9uZSwgdGhlbiBJJ20gcXVpdGUgaGFwcHkgd2l0aCBvcHRpb24gMi4gICBBbmQg
YWN0dWFsbHksIGl0IGxvb2tzIGxpa2UgcGVvcGxlIGFyZSBjb252ZXJnaW5nIG9uIG9wdGlvbiAy
ICh0aG91Z2ggSSBob3BlIGl0J3MgYmFzZWQgb24gZnVsbHkgdW5kZXJzdGFuZGluZyBvcHRpb24g
MikuICBOb3cgaXMgdGhlIHRpbWUgZm9yIHBlb3BsZSB0byBzcGVhayB1cCwgdGhhdCBrbm93IG9m
IHByb2JsZW1zIHRoaXMgd291bGQgY2F1c2UuLi5mb3IgaW5zdGFuY2UsIG5lZWRpbmcgdG8gaGF2
ZSBub24tdXBncmFkYWJsZSBWTCBndXlzIGF0IHRoZSBlZGdlIGZvciBhIGxvbmcgdGltZS4NCg0K
UmFkaWENCg0KDQoNCg==

--_000_DD5FC8DE455C3348B94340C0AB5517334F6519ACnkgeml501mbschi_
Content-Type: text/html; charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dgb2312">
<style id=3D"owaParaStyle">P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body fPStyle=3D"1" ocsi=3D"0">
<div style=3D"direction: ltr;font-family: Tahoma;color: #000000;font-size: =
10pt;">
<p>OK. I understand. I agree with your definition of &quot;safe FGL&quot;.<=
/p>
<p>thanks</p>
<p>weiguo</p>
<div style=3D"FONT-FAMILY: Times New Roman; COLOR: #000000; FONT-SIZE: 16px=
">
<hr tabindex=3D"-1">
<div style=3D"DIRECTION: ltr" id=3D"divRpF655710"><font color=3D"#000000" s=
ize=3D"2" face=3D"Tahoma"><b>=B7=A2=BC=FE=C8=CB:</b> Radia Perlman [radiape=
rlman@gmail.com]<br>
<b>=B7=A2=CB=CD=CA=B1=BC=E4:</b> 2013=C4=EA2=D4=C21=C8=D5 18:45<br>
<b>=B5=BD:</b> Haoweiguo<br>
<b>Cc:</b> Tissa Senevirathne (tsenevir); Anoop Ghanwani; Ayan Banerjee; Sa=
m Aldrin; trill@ietf.org; Donald Eastlake; Jon Hudson<br>
<b>=D6=F7=CC=E2:</b> Re: =B4=F0=B8=B4: [trill] Explaining three options for=
 upgrading to FGL (fine-grained-labeling)<br>
</font><br>
</div>
<div></div>
<div>
<div>I think you were just misinterpreting what I wrote.&nbsp; It is OK to =
let things through that could be pruned.&nbsp; It is
<em><u><strong>not</strong></u></em> OK to falsely delete things.&nbsp; The=
 example I gave of interpreting the first FGL label as a VL label is someth=
ing that the RBridge MUST NOT do.</div>
<div>&nbsp;</div>
<div>So we're not disagreeing.</div>
<div>&nbsp;</div>
<div>Radia<br>
<br>
</div>
<div class=3D"gmail_quote">On Fri, Feb 1, 2013 at 1:11 AM, Haoweiguo <span =
dir=3D"ltr">
&lt;<a href=3D"mailto:haoweiguo@huawei.com" target=3D"_blank">haoweiguo@hua=
wei.com</a>&gt;</span> wrote:<br>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">
<div>
<div style=3D"FONT-FAMILY: Tahoma; DIRECTION: ltr; FONT-SIZE: 10pt">
<p>Hi Radia,</p>
<p>I agree with your definition of &quot;Safe FGL&quot;,but I have a proble=
m about the following point:</p>
<div class=3D"im">
<p>&nbsp;</p>
<div>b) multicast pruning: it's OK not to do pruning at all, or to actually=
 look at all 24 bits of the FGL and prune as a proper FGL guy would do. &nb=
sp;But an example of what you canNOT do is look at the first 12 bits of FGL=
, pretend it's the same as VL, and delete
 the multicast packet because nobody downstream is listening to that 12 bit=
 VL value</div>
<div>&nbsp;</div>
</div>
<div>[weiguo]:If a switch performs pruning by first 12 bits of FGL, can the=
 switch called &quot;Safe FGL&quot; switch? If downstream have one VL switc=
h with VLAN is equal to first 12 bits of FGL,then the switch will forward m=
ulticast data frame to downstream VL switch.</div>
<div>thanks</div>
<div>weiguo</div>
<div style=3D"FONT-FAMILY: Times New Roman; FONT-SIZE: 16px">
<hr>
<div style=3D"DIRECTION: ltr"><font color=3D"#000000" face=3D"Tahoma"><b>=
=B7=A2=BC=FE=C8=CB:</b> Radia Perlman [<a href=3D"mailto:radiaperlman@gmail=
.com" target=3D"_blank">radiaperlman@gmail.com</a>]<br>
<b>=B7=A2=CB=CD=CA=B1=BC=E4:</b> 2013=C4=EA2=D4=C21=C8=D5 4:24
<div class=3D"im"><br>
<b>=B5=BD:</b> Tissa Senevirathne (tsenevir)<br>
<b>Cc:</b> Anoop Ghanwani; Ayan Banerjee; Sam Aldrin; <a href=3D"mailto:tri=
ll@ietf.org" target=3D"_blank">
trill@ietf.org</a>; Donald Eastlake; Jon Hudson<br>
</div>
<b>=D6=F7=CC=E2:</b> Re: [trill] Explaining three options for upgrading to =
FGL (fine-grained-labeling)<br>
</font><br>
</div>
<div>
<div class=3D"h5">
<div></div>
<div>Tissa said:
<div>&gt;&gt;&nbsp;how can you make sure all of the so called &quot;Safe FG=
L&quot; have consistent behavior<br>
<div><br>
</div>
<div>&quot;Safe FGL&quot; need not all have the <i><b>same</b></i> behavior=
 as each other...they just have to do &quot;nothing bad&quot; with an FGL f=
rame. &nbsp;It's worth summarizing (again) what it means to be &quot;FGL-sa=
fe&quot;, which allows you to coexist safely with FGL frames. &nbsp;To be
 FGL-safe you must do the following:</div>
<div>
<div><br>
</div>
<div>a) unicast: you MUST NOT drop a packet because of seeing the unrecogni=
zed FGL tag. &nbsp;You also MUST NOT get confused and do flow hashing impro=
perly (choosing different paths for packets for the same flow).</div>
<div><br>
</div>
<div>b) multicast pruning: it's OK not to do pruning at all, or to actually=
 look at all 24 bits of the FGL and prune as a proper FGL guy would do. &nb=
sp;But an example of what you canNOT do is look at the first 12 bits of FGL=
, pretend it's the same as VL, and delete
 the multicast packet because nobody downstream is listening to that 12 bit=
 VL value</div>
<div><br>
</div>
<div>c) egress of either unicast or multicast: &nbsp;you MUST NOT egress an=
 FGL frame onto a link that is not supposed to get that FGL value</div>
<div><br>
</div>
<div>d) you have to advertise that you are FGL-safe...otherwise other RBs w=
ill assume you are VL (&quot;FGL-unsafe&quot;)</div>
<div><br>
</div>
<div>---------</div>
<div>Also, TIssa said:</div>
<div>&gt;&gt;Do you agree if we say, FGL will always be core of the network=
, and VL will be at the edge of the network ?</div>
<div><br>
</div>
<div>With option 2, a VL guy <i><u>cannot even be at the edge of a network =
with FGL links</u></i> unless it is upgraded to FGL-safe AND advertises tha=
t it is FGL-safe. &nbsp;Option 2 says a VL guy is completely ostrasized onc=
e FGL-labeled links are introduced. &nbsp;There
 is NO coexistence of VL guys and FGL-links. The only kinds of coexistence =
in option 2 are:</div>
<div><br>
</div>
<div>a) VL and FGL-safe RBridge, but no actual FGL links yet.</div>
<div>b) FGL-safe guys, even if some of them don't really understand FGL, bu=
t just don't do &quot;anything bad&quot; with it, and FGL frames.</div>
<div><br>
</div>
<div>So...again...the migration phases in option 2 are</div>
<div>1) VL-only (today's deployment), then</div>
<div>2) A mixture of VL and FGL-safe, until</div>
<div>3) EVERYone upgraded to FGL-safe, then</div>
<div>4) FGL-links can be introduced.</div>
<div><br>
</div>
<div><br>
</div>
<div>----</div>
<div>Also, Tissa said:</div>
<div>&gt;&gt;what about some devices who are not &quot;safe FGL&quot; and s=
o on, are we saying do not buy no safe FGL devices, if you do that you cann=
ot get FGL interop ?&nbsp;</div>
<div><br>
</div>
<div><b><i><u>If</u></i></b> it's important to have VL guys as transit, and=
 they cannot be upgraded to FGL-safe because upgrading requires a hardware =
change (it involves parsing data packets), then we are stuck with option 3.=
 &nbsp;In option 3, we can forever have
 VL guys at the edge speaking through an FGL-safe or full-FGL core. &nbsp;I=
n option 2, as I said, there is
<i><u>no coexistence</u></i> of VL guys, <i><u>even at the edg</u></i>e, on=
ce FGL links are introduced. &nbsp;In option 2, a VL guy, even at the edge,=
 will be ostrasized completely once anyone advertises connectivity to an FG=
L link.</div>
<div><br>
</div>
<div>I personally like option 2, because it's simple, but as Einstein said =
&quot;make things as simple as possible, but no simpler&quot;. &nbsp;We hav=
e to make sure that everyone understands the implications of option 2, and =
can live with them. &nbsp;To summarize again (since
 there seems to be some confusion about what the implications of option 2 a=
re),</div>
<div><br>
</div>
<div>If we can upgrade all existing VL implementations to FGL-safe through =
software upgrade only, then option 2 provides smooth migration by changing =
ALL RBridges (edge as well as transit) to FGL-safe, and only after ALL of t=
hem are upgraded, then FGL-labeled
 links can be introduced. &nbsp;If there are any remaining VL guys once FGL=
-labeled links are introduced, the VL guys are ostrasized,
<i><u>even if they are just at the edge.</u></i></div>
<div><br>
</div>
<div>If we canNOT upgrade all existing VL to FGL-safe, AND if it's importan=
t to be able to mix VL guys into a network with FGL frames (say, having VL =
guys at the edge), then option 3 allows this.</div>
<div><br>
</div>
<div>So hopefully everyone understands the implications of option 2 fully b=
efore voting. &nbsp;As I said, I don't know about whether there are VL chip=
s that would require a hardware upgrade to become FGL-safe. &nbsp;Assuming =
there are none, then I'm quite happy with
 option 2. &nbsp; And actually, it looks like people are converging on opti=
on 2 (though I hope it's based on fully understanding option 2). &nbsp;Now =
is the time for people to speak up, that know of problems this would cause.=
..for instance, needing to have non-upgradable
 VL guys at the edge for a long time.</div>
<div><br>
</div>
<div>Radia</div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</body>
</html>

--_000_DD5FC8DE455C3348B94340C0AB5517334F6519ACnkgeml501mbschi_--

From jon.hudson@gmail.com  Sun Feb  3 02:35:42 2013
Return-Path: <jon.hudson@gmail.com>
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 1ACA721F85FC for <trill@ietfa.amsl.com>; Sun,  3 Feb 2013 02:35:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.203
X-Spam-Level: 
X-Spam-Status: No, score=-2.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
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 KNs3fJ-Y0gHJ for <trill@ietfa.amsl.com>; Sun,  3 Feb 2013 02:35:41 -0800 (PST)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2ABB321F8620 for <trill@ietf.org>; Sun,  3 Feb 2013 02:35:41 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id wz12so2776297pbc.17 for <trill@ietf.org>; Sun, 03 Feb 2013 02:35:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=waRWhjrICtZsAOyPholpfuSUHHln676MgIILiOFzQIk=; b=dvyo4wyEgMkbwUfLZclL6CSnD+rjUOEy2nVjfuHaauHZYMDUyLsTKegTi3mjHyOTD4 GhLn+xWmu7tUpAZRl1k801K9gG9MzDIs6b2qOk/7Fxv3FxlR0t/Qyw0vQERq053SXLr5 SfLSiq4t5IGf3iY05+Wipl019uwCvNQgcbPN7z0RDBQKn1U6I8vCnSSmcI0wnA9DbfZI 973SkJnKInu5dOTCF5DN8RTmLEUptB7KhMP0orK6e3Ek+iKTlwcinBu6Tc5w5BXlvqaC 6/9Wkds7jmyhCpXORrbALT1e1Jsq7BqbFvnMAeE2NINKZecLUvNGxvBMrthtW7t4H3hU 1PBQ==
X-Received: by 10.66.76.104 with SMTP id j8mr43197954paw.72.1359887740949; Sun, 03 Feb 2013 02:35:40 -0800 (PST)
Received: from [10.0.1.2] (c-98-234-218-27.hsd1.ca.comcast.net. [98.234.218.27]) by mx.google.com with ESMTPS id sk1sm14414045pbc.0.2013.02.03.02.35.38 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 03 Feb 2013 02:35:39 -0800 (PST)
References: <CAFOuuo67iBR2JkDtwPFCkrKHs3Fp4U_L1jkmNz5sfht6y05YMw@mail.gmail.com> <CA+-tSzx0E3J4i5Dvfbj4egruCeGi7z1se1Jn5RXtx3RedQLPdg@mail.gmail.com> <CAHD03N89RNX4=XxRZpD+Y2PCktYf-FtVjyYJ5oFS3dui3SsXaA@mail.gmail.com> <CAF4+nEG7YKGzGmObAMaOxackivjJsALymqHX=6PKBd5qU-Z+zQ@mail.gmail.com> <CA+-tSzz0=oh6iB1e-ESyeOx2sCvBFXeVpzuNbKmUVhRNLScDgQ@mail.gmail.com> <CAF4+nEFLrJL=CgX9e6on-cgz89ugmu93P6u5kmODhUia3H7RLg@mail.gmail.com> <1F5A81AE-4B3C-45FD-B431-9BA0011EB085@gmail.com> <DC8898F8-75C0-4535-BA61-C54279901332@gmail.com> <43DF00BE-B5F6-48B9-B313-8D179354C7B7@gmail.com> <A9B8F2D5-C3D7-4688-A76D-ED19EC47E59F@gmail.com> <FBEA3E19AA24F847BA3AE74E2FE19356288F6978@xmb-rcd-x08.cisco.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <FBEA3E19AA24F847BA3AE74E2FE19356288F6978@xmb-rcd-x08.cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <9B6B007C-1B7B-4460-8EC6-66D89BD8ADBE@gmail.com>
X-Mailer: iPad Mail (10A523)
From: Jon Hudson <jon.hudson@gmail.com>
Date: Sun, 3 Feb 2013 02:35:37 -0800
To: "Tissa Senevirathne (tsenevir)" <tsenevir@cisco.com>
Cc: Anoop Ghanwani <anoop@alumni.duke.edu>, Radia Perlman <radiaperlman@gmail.com>, Ayan Banerjee <ayabaner@gmail.com>, Sam Aldrin <aldrin.ietf@gmail.com>, "trill@ietf.org" <trill@ietf.org>, Donald Eastlake <d3e3e3@gmail.com>
Subject: Re: [trill] Explaining three options for upgrading to FGL (fine-grained-labeling)
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: Sun, 03 Feb 2013 10:35:42 -0000

Well one can certainly hope that FGLs end up in the core and VLs at the edge=
. However even when included in a design guide or offered as "best practice"=
 this will not always be true. The best rule for users is "If it can be done=
, they will do it"

So in the end what we are really impacting here is volume of support calls f=
or anyone currently shipping non FGL aware switches.=20


On Jan 31, 2013, at 7:18 AM, "Tissa Senevirathne (tsenevir)" <tsenevir@cisco=
.com> wrote:

> Jon
>=20
> You brought up the most import element. Questions Sam asked are extremely v=
alid. What do you mean by "safe FGL", how can you make sure all of the so ca=
lled "Safe FGL" have consistent behavior, what about some devices who are no=
t "safe FGL" and so on, are we saying do not buy no safe FGL devices, if you=
 do that you cannot get FGL interop ? We are not talking about control plane=
 we are talking about Hardware.
>=20
> Based on your point and with the analogy (though not the exact numbers :) )=
, we are looking at a limited install base here. For that Do you agree if we=
 say, FGL will always be core of the network, and VL will be at the edge of t=
he network ?
>=20
> Thanks
> Tissa
>=20
> -----Original Message-----
> From: trill-bounces@ietf.org [mailto:trill-bounces@ietf.org] On Behalf Of J=
on Hudson
> Sent: Wednesday, January 30, 2013 11:16 PM
> To: Sam Aldrin
> Cc: Donald Eastlake; Anoop Ghanwani; Radia Perlman; Ayan Banerjee; trill@i=
etf.org
> Subject: Re: [trill] Explaining three options for upgrading to FGL (fine-g=
rained-labeling)
>=20
> Well most of my customers and bound by 3yr depreciation schedules. So any n=
on-FGL devices they have when Full FGl devices ship will not be available fo=
r swap-pout. If they have been in service for 2hrs then maybe, but 2.5-3yrs i=
deal.
>=20
> So we expect most scenarios to be the addition of net new full FGL rbridge=
s. Then (hopefully) a software update to the existing non FGLs to some quasi=
 FGL mode ( just so you can take some advantage of the new functionality. Th=
en when the older rbridges run out on the books, then they can be replaced w=
ith shiny new full FGL rbridges and now have a full FGL compliant environmen=
t.
>=20
> But that is just for the small number of customers already running non FGL=
 compliant hardware. (~1000 for Brocade, and then probably more, but lets sa=
y 2,000for Cisco)
>=20
> For a large majority it will be green field installs all net new.=20
>=20
> We just don't want to punish those ~3000ish early adopters=20
>=20
> I have had MUCH difficultly getting customers involved in mail list discus=
sions. So getting someone who is today and operator (as apposed to a recover=
ing operator like myself) isn't super easy.  Needless to say the volume of e=
mails and tone of emails scares a lot of folks away. ( not just a TRILL WG t=
hing, an IETF in general thing)
>=20
>=20
> On Jan 31, 2013, at 8:25 AM, Sam Aldrin <aldrin.ietf@gmail.com> wrote:
>=20
>> Here is what I meant.
>>=20
>> Deployment scenarios could be  upgrading to FGL RBridges via 1) new devic=
e insertion OR 2) replacing older devices with FGL supported RBridges OR 3) t=
he so called upgrade to existing hardware to be FGL safe.
>> In each of those cases, the way to do it could differ for the reasons hig=
hlighted in various emails.
>> At the end of the day, by moving towards FGL based network, we cannot aff=
ord to disrupt existing TRILL network or force to forklift upgrade of non-FG=
L aware hardware.
>>=20
>> Lastly, it would be good to hear from the actual user to understand the p=
ain points in doing one way or the other.
>>=20
>> -sam
>>=20
>> On Jan 30, 2013, at 12:40 PM, Jon Hudson <jon.hudson@gmail.com> wrote:
>>=20
>>> Can you clarify on what you mean by deploy?
>>>=20
>>> I ask because I have many customers waiting for this functionality. Ever=
yone of the ~1000 installs we have, that also have multitenancy environments=
 plan to deploy this as soon as possible.=20
>>>=20
>>> But with no one have I gone through and done a Visio of how their Rbridg=
es are wired up today and how FGL rbridges would be integrated gracefully in=
to the environment.
>>>=20
>>> On Jan 31, 2013, at 3:55 AM, Sam Aldrin <aldrin.ietf@gmail.com> wrote:
>>>=20
>>>> [still catching up on email, so the delay]
>>>>=20
>>>> When everyone says, upgrade RBridges, what is the upgrade model they ha=
ve in mind?
>>>> How can one do software upgrade when hardware/silicon cannot support?
>>>> Secondly, any actual users, not vendors, commented on how they plan to d=
eploy FGL?
>>>>=20
>>>> -sam
>>>>=20
>>>> On Jan 29, 2013, at 4:37 PM, Donald Eastlake <d3e3e3@gmail.com> wrote:
>>>>=20
>>>>> Hi Anoop,
>>>>>=20
>>>>> On Tue, Jan 29, 2013 at 7:03 PM, Anoop Ghanwani <anoop@alumni.duke.edu=
> wrote:
>>>>>> On Tue, Jan 29, 2013 at 12:49 PM, Donald Eastlake <d3e3e3@gmail.com> w=
rote:
>>>>>>=20
>>>>>>> The general assumption is that you are migrating from VL to FGL.=20
>>>>>>> First you migrate to FGL-safe. Then you unleash the FGL traffic,=20
>>>>>>> by configuring FGL ports, which isolates any remaining=20
>>>>>>> (FGL-unsafe) VL switches while still being able to handle VL=20
>>>>>>> traffic between VL ports on FGL-safe switches.
>>>>>>=20
>>>>>> Based on what is written so far, it looks like as long as there is=20=

>>>>>> even one VL RBridge in it's database, an RBridge would not be able=20=

>>>>>> to start sourcing FGL traffic.  It may start doing so only when=20
>>>>>> all RBridges in
>>>>>=20
>>>>> Well, it can start sourcing FGL traffic but their are consequences=20
>>>>> as you note below.
>>>>>=20
>>>>>> its database are FGL-safe.  If we ever get into a condition where=20
>>>>>> an RBridge has started advertising FGL information, at that point,=20=

>>>>>> does any other RBridge in the campus simply isolate any VL RBridge=20=

>>>>>> (with the assumption that there was some kind of race condition?
>>>>>=20
>>>>> Yes. (This could just be due to some misconfiguration.)
>>>>>=20
>>>>>> The case I'm concerned about is we have 2 FGL RBridges, RB1 and RB2.
>>>>>> RB1 is connected to a campus of n RBs that are still VL only.  The=20=

>>>>>> VL link Breaks, and RB1 starts advertising FGL information to RB2,=20=

>>>>>> but then the link to the VL campus comes back up.  Does this mean=20
>>>>>> RB1 and RB2 remain isolated from the campus (and operate as they=20
>>>>>> own mini-campus) until all the other RBridges are converted over to FG=
L-safe?
>>>>>=20
>>>>> Yes. But I don't think this as much of a problem given that I=20
>>>>> believe existing TRILL switches can be software upgraded to be=20
>>>>> FGL-safe. I view the configuration of FGL ports on RB1/RB2 and the=20
>>>>> consequent routing of actual FGL traffic to be an active network=20
>>>>> management decision, not something that might just happen because=20
>>>>> there appear to be no more VL TRILL switches in the topology.
>>>>>=20
>>>>> Thanks,
>>>>> Donald
>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>>>>> Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>>>>> 155 Beaver Street, Milford, MA 01757 USA d3e3e3@gmail.com
>>>>>=20
>>>>>> Anoop
>>>>> _______________________________________________
>>>>> trill mailing list
>>>>> trill@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/trill
>>>>=20
>>>> _______________________________________________
>>>> 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

From liyizhou@huawei.com  Tue Feb  5 17:47:01 2013
Return-Path: <liyizhou@huawei.com>
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 23FFE21F894D; Tue,  5 Feb 2013 17:47:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 JCe0Tn5GxxBF; Tue,  5 Feb 2013 17:47:00 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id C965B21F8959; Tue,  5 Feb 2013 17:46:59 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AOE82685; Wed, 06 Feb 2013 01:46:58 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 6 Feb 2013 01:46:05 +0000
Received: from SZXEML414-HUB.china.huawei.com (10.82.67.153) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 6 Feb 2013 01:46:58 +0000
Received: from l63746 (10.138.122.43) by smtpscn.huawei.com (10.82.67.153) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 6 Feb 2013 09:46:48 +0800
From: Yizhou Li <liyizhou@huawei.com>
To: "'Linda Dunbar'" <linda.dunbar@huawei.com>, <internet-drafts@ietf.org>, <i-d-announce@ietf.org>
References: <20130114155111.1010.16060.idtracker@ietfa.amsl.com> <4A95BA014132FF49AE685FAB4B9F17F6450EB7A7@dfweml505-mbb.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F6450EB7A7@dfweml505-mbb.china.huawei.com>
Date: Wed, 6 Feb 2013 09:46:48 +0800
Message-ID: <01f601ce040b$d408a210$7c19e630$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Content-Language: zh-cn
Thread-index: AQHN8m8ckhVnPAyL30CBHCQ1kNw3i5hI/WyQgCM1N0A=
X-Originating-IP: [10.138.122.43]
X-CFilter-Loop: Reflected
Cc: trill@ietf.org
Subject: Re: [trill] I-D Action: draft-ietf-trill-directory-framework-02.txt
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, 06 Feb 2013 01:47:01 -0000

I am ok with current version.

-----Original Message-----
From: trill-bounces@ietf.org [mailto:trill-bounces@ietf.org] On Behalf Of
Linda Dunbar
Sent: Tuesday, January 15, 2013 12:10 AM
To: internet-drafts@ietf.org; i-d-announce@ietf.org
Cc: trill@ietf.org
Subject: Re: [trill] I-D Action: draft-ietf-trill-directory-framework-02.txt

Thanks to everyone who provided the valuable comments to
"draft-ietf-trill-directory-framework" during the last WGLC period. This
updated draft has incorporated all the comments received. Please review
again and let us know if you have more issues or comments. 

Thanks, Linda

> -----Original Message-----
> From: trill-bounces@ietf.org [mailto:trill-bounces@ietf.org] On Behalf
> Of internet-drafts@ietf.org
> Sent: Monday, January 14, 2013 9:51 AM
> To: i-d-announce@ietf.org
> Cc: trill@ietf.org
> Subject: [trill] I-D Action: draft-ietf-trill-directory-framework-
> 02.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 Working Group of the IETF.
> 
> 	Title           : TRILL (Transparent Interconnection of Lots of
> Links) Edge Directory Assistance Framework
> 	Author(s)       : Linda Dunbar
>                           Donald Eastlake
>                           Intel Labs
>                           Igor Gashinsky
> 	Filename        : draft-ietf-trill-directory-framework-02.txt
> 	Pages           : 14
> 	Date            : 2013-01-14
> 
> Abstract:
>    Edge RBridges currently learn the mapping between MAC addresses and
>    their egress RBridges by observing the data packets ingressed or
>    egressed and by the TRILL ESADI protocol. When ingress RBridge
>    receives a data frame whose destination address (MAC&VLAN) that
>    RBridge does not know, the data frame is flooded within the VLAN
>    across the TRILL campus.
> 
>    This draft describes the framework for using directory services to
>    assist edge RBridges by reducing multi-destination frames,
>    particularly unknown unicast frames flooding, and ARP/ND, improving
>    TRILL (Transparent Interconnection of Lots of Links) network
>    scalability in environments such as data centers.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-trill-directory-framework
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-trill-directory-framework-02
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-trill-directory-framework-
> 02
> 
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> 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


From d3e3e3@gmail.com  Fri Feb  8 07:37:03 2013
Return-Path: <d3e3e3@gmail.com>
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 7B19C21F8AAC for <trill@ietfa.amsl.com>; Fri,  8 Feb 2013 07:37:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.367
X-Spam-Level: 
X-Spam-Status: No, score=-103.367 tagged_above=-999 required=5 tests=[AWL=0.232, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 xa7VwCWvWMuf for <trill@ietfa.amsl.com>; Fri,  8 Feb 2013 07:37:02 -0800 (PST)
Received: from mail-oa0-f49.google.com (mail-oa0-f49.google.com [209.85.219.49]) by ietfa.amsl.com (Postfix) with ESMTP id B619121F8AB1 for <trill@ietf.org>; Fri,  8 Feb 2013 07:37:02 -0800 (PST)
Received: by mail-oa0-f49.google.com with SMTP id j6so4085073oag.8 for <trill@ietf.org>; Fri, 08 Feb 2013 07:37:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=LkIopntKysjOJwL1YbQ6zSl611MXXWp4w8kIkFhkr7w=; b=BgZWQf5t3snOD4KlEuMZJS+GM/t5Em69E3R1fmsm2bgoVS8FkR0CGyFq2pFQ+d4+Ka gqer98eWFGFy8w/pGAnQ0iUbNsTyq9XvT52gY4CkjtSA7UnLE5AnpePUp9PMhx7rHI2u B1PigtQ1Xj7RFN4IJE0O/Y/LfyONpcwku8ePOIfqaTSTAJiJij8mETRaCwEKc+UDNpo7 rdt3Ec2YKXGbKFIiKPQTVyiemKOyQNHbrJ1FQo4LfFcTnFQ3EklA/EG4qcc4t7iag+Gv 56cUri0/Wu//7RgGmGRnmfi7q0FNieP26FLFXthiD9vTlzin5x+9Vb0YLQPKgRPZE+ZA ea2g==
X-Received: by 10.60.170.242 with SMTP id ap18mr4336809oec.97.1360337822316; Fri, 08 Feb 2013 07:37:02 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.98.168 with HTTP; Fri, 8 Feb 2013 07:36:42 -0800 (PST)
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 8 Feb 2013 10:36:42 -0500
Message-ID: <CAF4+nEHc9FE7XV4MS2cj-vdW8q_D=gru4Eo-4WFL6ypUvPDM7g@mail.gmail.com>
To: trill@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [trill] TRILL tentative scheduled for Orlando IETF meeting
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: Fri, 08 Feb 2013 15:37:03 -0000

A tentative schedule of meeting slots for the Orlando IETF meeting has
been posted at
https://datatracker.ietf.org/meeting/86/agenda.html
which shows TRILL as late Tuesday.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

From ginsberg@cisco.com  Sat Feb  9 11:07:43 2013
Return-Path: <ginsberg@cisco.com>
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 8950221F861B; Sat,  9 Feb 2013 11:07:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 fv2r1MWHil+D; Sat,  9 Feb 2013 11:07:42 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 7622A21F85EE; Sat,  9 Feb 2013 11:07:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11646; q=dns/txt; s=iport; t=1360436862; x=1361646462; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=XNy3bDAF5Xv+naNwjsAFuVTFZea6yjw91oGQNIWdeOY=; b=ey9Rp4FGvNmUbPEtj3HHW03FyGyyngKDJnosAXQZyHfiADO9d1vEhb99 v1KJZ2ZQlQNEVmqq2NQdUGnmRuORbfSXtDjoRF7qH4xQCNUw3f+iqP0y2 iRkxhgVz/Lt7eN1b+3XzpbFNFp2zVaTrsZkXraGCsAHkTbOdC+KAoI69l k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkIFAPydFlGtJV2d/2dsb2JhbABFgkmEBagSiRmIMH0Wc4IfAQEBBCMKSg4EAgEIEQQBAQsdAwICAjAUBwEBBQMCBAESCAGICAytB5IIjUuDLDJhA5dBjzaDBoFmPg
X-IronPort-AV: E=Sophos;i="4.84,634,1355097600";  d="scan'208,217";a="175328953"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-3.cisco.com with ESMTP; 09 Feb 2013 19:07:27 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r19J7RPk002172 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 9 Feb 2013 19:07:27 GMT
Received: from xmb-rcd-x02.cisco.com ([169.254.4.64]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.02.0318.004; Sat, 9 Feb 2013 13:07:26 -0600
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "isis-wg@ietf.org" <isis-wg@ietf.org>, "trill@ietf.org" <trill@ietf.org>
Thread-Topic: New Version Notification for draft-ginsberg-isis-fs-lsp-00.txt
Thread-Index: AQHOBvT7/sK/fkg5yEW0PflPkjIeNphx4kaw
Date: Sat, 9 Feb 2013 19:07:26 +0000
Message-ID: <F3ADE4747C9E124B89F0ED2180CC814F1324D0B5@xmb-rcd-x02.cisco.com>
References: <20130209184027.21946.697.idtracker@ietfa.amsl.com>
In-Reply-To: <20130209184027.21946.697.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.125.129]
Content-Type: multipart/alternative; boundary="_000_F3ADE4747C9E124B89F0ED2180CC814F1324D0B5xmbrcdx02ciscoc_"
MIME-Version: 1.0
Subject: [trill] FW: New Version Notification for draft-ginsberg-isis-fs-lsp-00.txt
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: Sat, 09 Feb 2013 19:07:43 -0000

--_000_F3ADE4747C9E124B89F0ED2180CC814F1324D0B5xmbrcdx02ciscoc_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

VGhpcyBkcmFmdCBzaG91bGQgYmUgb2YgaW50ZXJlc3QgdG8gYm90aCBXR3MuDQoNCg0KDQogICBM
ZXMNCg0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBpbnRlcm5ldC1kcmFm
dHNAaWV0Zi5vcmcgW21haWx0bzppbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmddDQpTZW50OiBTYXR1
cmRheSwgRmVicnVhcnkgMDksIDIwMTMgMTA6NDAgQU0NClRvOiBMZXMgR2luc2JlcmcgKGdpbnNi
ZXJnKQ0KQ2M6IFlpIFlhbmcgKHlpeWEpOyBTdGVmYW5vIFByZXZpZGkgKHNwcmV2aWRpKQ0KU3Vi
amVjdDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1naW5zYmVyZy1pc2lzLWZz
LWxzcC0wMC50eHQNCg0KDQoNCg0KDQpBIG5ldyB2ZXJzaW9uIG9mIEktRCwgZHJhZnQtZ2luc2Jl
cmctaXNpcy1mcy1sc3AtMDAudHh0DQoNCmhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBzdWJtaXR0ZWQg
YnkgTGVzIEdpbnNiZXJnIGFuZCBwb3N0ZWQgdG8gdGhlDQoNCklFVEYgcmVwb3NpdG9yeS4NCg0K
DQoNCkZpbGVuYW1lOiAgIGRyYWZ0LWdpbnNiZXJnLWlzaXMtZnMtbHNwDQoNClJldmlzaW9uOiAg
IDAwDQoNClRpdGxlOiAgICAgICAgICAgIElTLUlTIEZsb29kaW5nIFNjb3BlIExTUHMNCg0KQ3Jl
YXRpb24gZGF0ZTogICAgMjAxMy0wMi0wOQ0KDQpXRyBJRDogICAgICAgICAgICBJbmRpdmlkdWFs
IFN1Ym1pc3Npb24NCg0KTnVtYmVyIG9mIHBhZ2VzOiAxOQ0KDQpVUkw6ICAgICAgICAgICAgIGh0
dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWdpbnNiZXJnLWlzaXMtZnMt
bHNwLTAwLnR4dA0KDQpTdGF0dXM6ICAgICAgICAgIGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9y
Zy9kb2MvZHJhZnQtZ2luc2JlcmctaXNpcy1mcy1sc3ANCg0KSHRtbGl6ZWQ6ICAgICAgICBodHRw
Oi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1naW5zYmVyZy1pc2lzLWZzLWxzcC0wMA0KDQoN
Cg0KDQoNCkFic3RyYWN0Og0KDQogICBJbnRlcm1lZGlhdGUgU3lzdGVtIFRvIEludGVybWVkaWF0
ZSBTeXN0ZW0gKElTLUlTKSBwcm92aWRlcyBlZmZpY2llbnQNCg0KICAgYW5kIHJlbGlhYmxlIGZs
b29kaW5nIG9mIGluZm9ybWF0aW9uIHRvIGl0cyBwZWVycy4gIEhvd2V2ZXIgdGhlDQoNCiAgIGN1
cnJlbnQgZmxvb2Rpbmcgc2NvcGVzIGFyZSBsaW1pdGVkIHRvIGVpdGhlciBhcmVhIHdpZGUgc2Nv
cGUgb3INCg0KICAgZG9tYWluIHdpZGUgc2NvcGUuICBUaGVyZSBhcmUgZXhpc3RpbmcgdXNlIGNh
c2VzIHdoZXJlIHN1cHBvcnQgb2YNCg0KICAgb3RoZXIgZmxvb2Rpbmcgc2NvcGVzIGFyZSBkZXNp
cmFibGUuICBUaGlzIGRvY3VtZW50IGRlZmluZXMgbmV3DQoNCiAgIFByb3RvY29sIERhdGEgVW5p
dHMgKFBEVXMpIHdoaWNoIHByb3ZpZGUgc3VwcG9ydCBmb3IgbmV3IGZsb29kaW5nDQoNCiAgIHNj
b3BlcyBhcyB3ZWxsIGFzIGFkZGl0aW9uYWwgc3BhY2UgZm9yIGFkdmVydGlzaW5nIGluZm9ybWF0
aW9uDQoNCiAgIHRhcmdldGVkIGZvciB0aGUgY3VycmVudGx5IHN1cHBvcnRlZCBmbG9vZGluZyBz
Y29wZXMuDQoNCg0KDQogICBUaGUgcHJvdG9jb2wgZXh0ZW5zaW9ucyBkZWZpbmVkIGluIHRoaXMg
ZG9jdW1lbnQgYXJlIG5vdCBiYWNrd2FyZHMNCg0KICAgY29tcGF0aWJsZSB3aXRoIGV4aXN0aW5n
IGltcGxlbWVudGF0aW9ucyBhbmQgc28gbXVzdCBiZSBkZXBsb3llZCB3aXRoDQoNCiAgIGNhcmUu
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KVGhlIElFVEYgU2VjcmV0YXJpYXQNCg0KDQo=

--_000_F3ADE4747C9E124B89F0ED2180CC814F1324D0B5xmbrcdx02ciscoc_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZp
bml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXtt
YXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0K
CWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5
cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRl
Y29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dl
ZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3Jh
dGlvbjp1bmRlcmxpbmU7fQ0KcC5Nc29QbGFpblRleHQsIGxpLk1zb1BsYWluVGV4dCwgZGl2Lk1z
b1BsYWluVGV4dA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IlBs
YWluIFRleHQgQ2hhciI7DQoJbWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEwLjVwdDsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCnNwYW4uUGxh
aW5UZXh0Q2hhcg0KCXttc28tc3R5bGUtbmFtZToiUGxhaW4gVGV4dCBDaGFyIjsNCgltc28tc3R5
bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IlBsYWluIFRleHQiOw0KCWZvbnQtZmFt
aWx5OiJDb3VyaWVyIE5ldyI7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhw
b3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjt9DQpAcGFnZSBX
b3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEu
MGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+
PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9
ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBt
c28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0
PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0K
PC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0K
PGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPlRoaXMg
ZHJhZnQgc2hvdWxkIGJlIG9mIGludGVyZXN0IHRvIGJvdGggV0dzLjxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsgTGVzPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRl
eHQiPi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tPGJyPg0KRnJvbTogaW50ZXJuZXQtZHJhZnRz
QGlldGYub3JnIFttYWlsdG86aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnXSA8YnI+DQpTZW50OiBT
YXR1cmRheSwgRmVicnVhcnkgMDksIDIwMTMgMTA6NDAgQU08YnI+DQpUbzogTGVzIEdpbnNiZXJn
IChnaW5zYmVyZyk8YnI+DQpDYzogWWkgWWFuZyAoeWl5YSk7IFN0ZWZhbm8gUHJldmlkaSAoc3By
ZXZpZGkpPGJyPg0KU3ViamVjdDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1n
aW5zYmVyZy1pc2lzLWZzLWxzcC0wMC50eHQ8L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+QSBuZXcgdmVyc2lvbiBvZiBJLUQs
IGRyYWZ0LWdpbnNiZXJnLWlzaXMtZnMtbHNwLTAwLnR4dDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb1BsYWluVGV4dCI+aGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1pdHRlZCBieSBMZXMg
R2luc2JlcmcgYW5kIHBvc3RlZCB0byB0aGU8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPklFVEYgcmVwb3NpdG9yeS48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+
RmlsZW5hbWU6Jm5ic3A7Jm5ic3A7IGRyYWZ0LWdpbnNiZXJnLWlzaXMtZnMtbHNwPG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5SZXZpc2lvbjombmJzcDsmbmJzcDsgMDA8
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPlRpdGxlOiZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBJ
Uy1JUyBGbG9vZGluZyBTY29wZSBMU1BzPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxh
aW5UZXh0Ij5DcmVhdGlvbiBkYXRlOiZuYnNwOyZuYnNwOyZuYnNwOyAyMDEzLTAyLTA5PG86cD48
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5XRyBJRDombmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgSW5kaXZp
ZHVhbCBTdWJtaXNzaW9uPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5O
dW1iZXIgb2YgcGFnZXM6IDE5PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0
Ij5VUkw6Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IDxhIGhyZWY9Imh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJu
ZXQtZHJhZnRzL2RyYWZ0LWdpbnNiZXJnLWlzaXMtZnMtbHNwLTAwLnR4dCI+DQo8c3BhbiBzdHls
ZT0iY29sb3I6d2luZG93dGV4dDt0ZXh0LWRlY29yYXRpb246bm9uZSI+aHR0cDovL3d3dy5pZXRm
Lm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtZ2luc2JlcmctaXNpcy1mcy1sc3AtMDAudHh0PC9z
cGFuPjwvYT48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPlN0YXR1czom
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgPGEg
aHJlZj0iaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1naW5zYmVyZy1pc2lz
LWZzLWxzcCI+DQo8c3BhbiBzdHlsZT0iY29sb3I6d2luZG93dGV4dDt0ZXh0LWRlY29yYXRpb246
bm9uZSI+aHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1naW5zYmVyZy1pc2lz
LWZzLWxzcDwvc3Bhbj48L2E+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0
Ij5IdG1saXplZDombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgPGEg
aHJlZj0iaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtZ2luc2JlcmctaXNpcy1mcy1s
c3AtMDAiPg0KPHNwYW4gc3R5bGU9ImNvbG9yOndpbmRvd3RleHQ7dGV4dC1kZWNvcmF0aW9uOm5v
bmUiPmh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWdpbnNiZXJnLWlzaXMtZnMtbHNw
LTAwPC9zcGFuPjwvYT48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5BYnN0cmFjdDo8bzpwPjwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyBJbnRlcm1lZGlhdGUgU3lz
dGVtIFRvIEludGVybWVkaWF0ZSBTeXN0ZW0gKElTLUlTKSBwcm92aWRlcyBlZmZpY2llbnQ8bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyBhbmQgcmVs
aWFibGUgZmxvb2Rpbmcgb2YgaW5mb3JtYXRpb24gdG8gaXRzIHBlZXJzLiZuYnNwOyBIb3dldmVy
IHRoZTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7
IGN1cnJlbnQgZmxvb2Rpbmcgc2NvcGVzIGFyZSBsaW1pdGVkIHRvIGVpdGhlciBhcmVhIHdpZGUg
c2NvcGUgb3I8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZu
YnNwOyBkb21haW4gd2lkZSBzY29wZS4mbmJzcDsgVGhlcmUgYXJlIGV4aXN0aW5nIHVzZSBjYXNl
cyB3aGVyZSBzdXBwb3J0IG9mPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0
Ij4mbmJzcDsmbmJzcDsgb3RoZXIgZmxvb2Rpbmcgc2NvcGVzIGFyZSBkZXNpcmFibGUuJm5ic3A7
IFRoaXMgZG9jdW1lbnQgZGVmaW5lcyBuZXc8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPiZuYnNwOyZuYnNwOyBQcm90b2NvbCBEYXRhIFVuaXRzIChQRFVzKSB3aGljaCBw
cm92aWRlIHN1cHBvcnQgZm9yIG5ldyBmbG9vZGluZzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7IHNjb3BlcyBhcyB3ZWxsIGFzIGFkZGl0aW9uYWwg
c3BhY2UgZm9yIGFkdmVydGlzaW5nIGluZm9ybWF0aW9uPG86cD48L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsgdGFyZ2V0ZWQgZm9yIHRoZSBjdXJyZW50bHkg
c3VwcG9ydGVkIGZsb29kaW5nIHNjb3Blcy48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+
Jm5ic3A7Jm5ic3A7IFRoZSBwcm90b2NvbCBleHRlbnNpb25zIGRlZmluZWQgaW4gdGhpcyBkb2N1
bWVudCBhcmUgbm90IGJhY2t3YXJkczxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+Jm5ic3A7Jm5ic3A7IGNvbXBhdGlibGUgd2l0aCBleGlzdGluZyBpbXBsZW1lbnRhdGlv
bnMgYW5kIHNvIG11c3QgYmUgZGVwbG95ZWQgd2l0aDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7IGNhcmUuPG86cD48L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPlRoZSBJRVRG
IFNlY3JldGFyaWF0PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_F3ADE4747C9E124B89F0ED2180CC814F1324D0B5xmbrcdx02ciscoc_--

From howardy@cisco.com  Tue Feb 12 11:47:58 2013
Return-Path: <howardy@cisco.com>
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 2CF0821F871C for <trill@ietfa.amsl.com>; Tue, 12 Feb 2013 11:47:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.998
X-Spam-Level: 
X-Spam-Status: No, score=-9.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_54=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9aL1eid9XYgg for <trill@ietfa.amsl.com>; Tue, 12 Feb 2013 11:47:57 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id EB22721F8447 for <trill@ietf.org>; Tue, 12 Feb 2013 11:47:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7616; q=dns/txt; s=iport; t=1360698477; x=1361908077; h=from:to:subject:date:message-id:mime-version; bh=ECssxrjs3MD0CGX/d0Ne3zRSBlcVgNAcnB4fWZZOEaU=; b=cT1YyKYyPaGf0O0IbB3ebNXGN3b6pumId12qhE+i/XGKqDcVgDq8OX2N yebRo4FqGtfAU0aAeCZWNu6XXyaJPgjbm1zSvu+yUtiE1T7MgXY8bmsW4 RwGfvwM7dM5K1EpPWVnMKCwZrddenx3lLgvfBozzGjpG2THHSiUKO8gKB Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAPybGlGtJXG//2dsb2JhbABEgkm+JBZzgiEBBIELASpWJwQBGogKr02QEZEkYQOmd4MGgic
X-IronPort-AV: E=Sophos;i="4.84,652,1355097600";  d="scan'208,217";a="176296782"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-2.cisco.com with ESMTP; 12 Feb 2013 19:47:56 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r1CJluPV003798 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 12 Feb 2013 19:47:56 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.213]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.02.0318.004; Tue, 12 Feb 2013 13:47:56 -0600
From: "Howard Yang (howardy)" <howardy@cisco.com>
To: "draft-ietf-trill-rbridge-bfd@tools.ietf.org" <draft-ietf-trill-rbridge-bfd@tools.ietf.org>, "trill@ietf.org" <trill@ietf.org>, "draft-ietf-isis-rfc6326bis@tools.ietf.org" <draft-ietf-isis-rfc6326bis@tools.ietf.org>
Thread-Topic: Comments on TRILL BFD draft and TRILL use of ISIS draft 
Thread-Index: AQHOCVnZvTs2kU0gw0qmA2l/KI8GPw==
Date: Tue, 12 Feb 2013 19:47:55 +0000
Message-ID: <8F62EB044F07504DB195F82B824F34DD2522B8@xmb-aln-x15.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.1.120420
x-originating-ip: [128.107.157.236]
Content-Type: multipart/alternative; boundary="_000_8F62EB044F07504DB195F82B824F34DD2522B8xmbalnx15ciscocom_"
MIME-Version: 1.0
Subject: [trill] Comments on TRILL BFD draft and TRILL use of ISIS draft
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: Tue, 12 Feb 2013 19:47:58 -0000

--_000_8F62EB044F07504DB195F82B824F34DD2522B8xmbalnx15ciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

I have a couple of comments on TRILL BFD draft <draft-ietf-trill-rbridge-bf=
d-07.txt> and TRILL use of ISIS draft <draft-ietf-isis-rfc6326bis-00.txt>.


(1) To support TRILL BFD, it is required to include nickname TLV or sub-TLV=
 in the ISIS hello packets.

The reason is that when the neighbor receives the BFD packets, if the nickn=
ame of the peer is not known, BFD cannot associate such BFD packets with th=
e BFD session.

By the way, let's look at, in specific, the "One-Hop TRILL BFD Control" her=
e. Looking at Layer 3 (IP or IPv6) BFD, we have IP address TLV included in =
the ISIS hellos, so that when BFD session is created by ISIS, ISIS can pass=
 both local and peer's IP addresses to BFD for BFD to associate a BFD packe=
t to a session. Corresponding to IP address, in TRILL, we have the nickname=
. When a BFD session is created with an unknown nickname for the peer, and =
when a BFD packet from this peer is received, BFD has no way to associate t=
his BFD packet with the BFD session previously created. Notice BFD packets =
are defined to have the TRILL channel encapsulation (draft-ietf-trill-rbrid=
ge-channel-08.txt).

So we need to add the requirement of including the local nickname in ISIS h=
ellos, in addition to the "ISIS BFD enabled TLV" (RFC 6213).

The nickname is currently defined as nickname sub-tlv (<draft-ietf-isis-rfc=
6326bis-00.txt>) and it is defined only in Router or MT Capability TLV. We =
need to extend it and allow the nickname sub-tlv to be in the Multi-Topolog=
y-Aware Port Capability TLV.



(2) In Section 3.1 of the TRILL BFD draft, we have

3.1 One-Hop TRILL BFD Control

   One-hop TRILL BFD Control is typically used to rapidly detect link
   and RBridge failures.  TRILL BFD frames over one hop for such
   purposes SHOULD be sent with high priority; that is, the Inner.VLAN
   tag priority should be 7, they should be queued for transmission as
   maximum priority frames and, if they are being sent on an Ethernet
   link where the output port is configured to include an Outer.VLAN
   tag, that tag should specify priority 7.

   For neighbor RBridges RB1 and RB2, each RBridge sends one-hop TRILL
   BFD Control frames to the other only if TRILL IS-IS has detected bi-
   directional connectivity, that is, the adjacency is in the Two-Way or
   Report state [RFC6327] and both RBridges indicate support of TRILL
   BFD is enabled.  The BFD Enabled TLV is used to indicate this as
   specified in [RFC6213].



The "Two-Way" or "Report" is specific to TRILL LAN interface. It does not a=
pply to the point-to-point interface. So, it should be modified to:

"that is, the adjacency is in the Two-Way or Report state [RFC6327] on the =
LAN or INIT on the point-to-point when neighbor is known and both Rbridges =
indicate support of TRILL BFD is enabled."


Thanks,

-Howard Yang





--_000_8F62EB044F07504DB195F82B824F34DD2522B8xmbalnx15ciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <5EC61EFDDC7EDB4682F9A3D5675D1585@cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif; ">
<div>Hi,</div>
<div><br>
</div>
<div>I have a couple of comments on TRILL BFD draft&nbsp;<span class=3D"App=
le-style-span" style=3D"font-family: monospace; white-space: pre; ">&lt;dra=
ft-ietf-trill-rbridge-bfd-07.txt&gt; and&nbsp;TRILL use of ISIS draft
</span><span class=3D"Apple-style-span" style=3D"font-family: monospace; wh=
ite-space: pre; ">&lt;draft-ietf-isis-rfc6326bis-00.txt&gt;</span>.</div>
<div><br>
</div>
<div><br>
</div>
<div>(1) To support TRILL BFD, it is required to include nickname TLV or su=
b-TLV in the ISIS hello packets.</div>
<div><br>
</div>
<div>The reason is that when the neighbor receives the BFD packets, if the =
nickname of the peer is not known, BFD cannot associate such BFD packets wi=
th the BFD session.&nbsp;</div>
<div><br>
</div>
<div>By the way, let's look at, in specific, the &quot;One-Hop TRILL BFD Co=
ntrol&quot; here.&nbsp;Looking at Layer 3 (IP or IPv6) BFD, we have IP addr=
ess TLV included in the ISIS hellos, so that when BFD session is created by=
 ISIS, ISIS can pass both local and peer's IP addresses
 to BFD for BFD to associate a BFD packet to a session. Corresponding to IP=
 address, in TRILL, we have the nickname. When a BFD session is created wit=
h an unknown nickname for the peer, and when a BFD packet from this peer is=
 received, BFD has no way to associate
 this BFD packet with the BFD session previously created. Notice BFD packet=
s are defined to have the TRILL channel encapsulation (<span class=3D"Apple=
-style-span" style=3D"font-family: monospace; white-space: pre; ">draft-iet=
f-trill-rbridge-channel-08.txt).
</span></div>
<div><br>
</div>
<div>So we need to add the requirement of including the local nickname in I=
SIS hellos, in addition to the &quot;ISIS BFD enabled TLV&quot; (RFC 6213).=
 &nbsp;</div>
<div><br>
</div>
<div>The nickname is currently defined as nickname sub-tlv (<span class=3D"=
Apple-style-span" style=3D"font-family: monospace; white-space: pre; ">&lt;=
draft-ietf-isis-rfc6326bis-00.txt&gt;) and it is defined only in Router or =
MT Capability TLV. We need to extend it and
 allow the nickname sub-tlv to be in the Multi-Topology-Aware Port Capabili=
ty TLV.</span></div>
<div><span class=3D"Apple-style-span" style=3D"font-family: monospace; whit=
e-space: pre; "><br>
</span></div>
<div><br>
</div>
<div><br>
</div>
<div>(2) In Section 3.1 of the TRILL BFD draft, we have</div>
<div>
<pre><span class=3D"m_h">3.1 One-Hop TRILL BFD Control</span>

   One-hop TRILL BFD Control is typically used to rapidly detect link
   and RBridge failures.  TRILL BFD frames over one hop for such
   purposes SHOULD be sent with high priority; that is, the Inner.VLAN
   tag priority should be 7, they should be queued for transmission as
   maximum priority frames and, if they are being sent on an Ethernet
   link where the output port is configured to include an Outer.VLAN
   tag, that tag should specify priority 7.

   For neighbor RBridges RB1 and RB2, each RBridge sends one-hop TRILL
   BFD Control frames to the other only if TRILL IS-IS has detected bi-
   directional connectivity, that is, the adjacency is in the Two-Way or
   Report state [RFC6327] and both RBridges indicate support of TRILL
   BFD is enabled.  The BFD Enabled TLV is used to indicate this as
   specified in [RFC6213].
</pre>
<pre><br></pre>
<pre>The &quot;Two-Way&quot; or &quot;Report&quot; is specific to TRILL LAN=
 interface. It does not apply to the point-to-point interface. So, it shoul=
d be modified to:</pre>
<pre>&quot;that is, the adjacency is in the Two-Way or Report state [RFC632=
7] on the LAN or INIT on the point-to-point when neighbor is known and both=
 Rbridges indicate support of TRILL BFD is enabled.&quot;</pre>
<pre><br></pre>
<pre>Thanks,</pre>
<pre>-Howard Yang</pre>
<pre><br></pre>
<pre><br></pre>
<pre><br></pre>
<pre><br></pre>
</div>
</body>
</html>

--_000_8F62EB044F07504DB195F82B824F34DD2522B8xmbalnx15ciscocom_--

From d3e3e3@gmail.com  Tue Feb 12 19:45:53 2013
Return-Path: <d3e3e3@gmail.com>
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 157ED21F895B for <trill@ietfa.amsl.com>; Tue, 12 Feb 2013 19:45:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.12
X-Spam-Level: 
X-Spam-Status: No, score=-103.12 tagged_above=-999 required=5 tests=[AWL=-0.121, BAYES_00=-2.599, J_CHICKENPOX_54=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oXIxLKYYw7jz for <trill@ietfa.amsl.com>; Tue, 12 Feb 2013 19:45:52 -0800 (PST)
Received: from mail-oa0-f48.google.com (mail-oa0-f48.google.com [209.85.219.48]) by ietfa.amsl.com (Postfix) with ESMTP id 3844A21F8844 for <trill@ietf.org>; Tue, 12 Feb 2013 19:45:49 -0800 (PST)
Received: by mail-oa0-f48.google.com with SMTP id j1so864031oag.21 for <trill@ietf.org>; Tue, 12 Feb 2013 19:45:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=Xk+vDRsyzkNZ2qDhEMCgTICyYlCc6jG6Qz6fSImkpqU=; b=sjM93Jdo1nNxFkOyRMjUaNrfIXx6wpcS3sg7oMC61Qh3Bl8ULgPyqyJhMKJiT/TvKX xkKNzBWdFZYDA1r74ckbBuUMaMCfUQ1fYVdec/k+v+mxhNmAmlAHJIiQ1twN/s3cEamq DuoM8Vhzj3ZN+EUroDe2THsBbi4id0Q3e+IhmpDOUmYbUIcWXpFtz1i/iXy4283qD5yk R1widg5jro8OUmESPxatx5f/5PfVynmvi9KuMA5zdcDytha+0QYXfY7YuQaq5H4nU2pt 6svfjnCl4c11bFioL01uPhfeWSpMWBLl7MtAeoYT4gLRyhF7dDbHjJTlMukcNBJmUwDA CTQQ==
X-Received: by 10.60.3.193 with SMTP id e1mr15810637oee.39.1360727135558; Tue, 12 Feb 2013 19:45:35 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.98.168 with HTTP; Tue, 12 Feb 2013 19:45:14 -0800 (PST)
In-Reply-To: <8F62EB044F07504DB195F82B824F34DD2522B8@xmb-aln-x15.cisco.com>
References: <8F62EB044F07504DB195F82B824F34DD2522B8@xmb-aln-x15.cisco.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 12 Feb 2013 22:45:14 -0500
Message-ID: <CAF4+nEGXb5_s0LOz+Zh8KBNTOGBBvX5ntHVo_02xrM-vaT==Sw@mail.gmail.com>
To: "Howard Yang (howardy)" <howardy@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "draft-ietf-trill-rbridge-bfd@tools.ietf.org" <draft-ietf-trill-rbridge-bfd@tools.ietf.org>, "draft-ietf-isis-rfc6326bis@tools.ietf.org" <draft-ietf-isis-rfc6326bis@tools.ietf.org>, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] Comments on TRILL BFD draft and TRILL use of ISIS draft
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, 13 Feb 2013 03:45:53 -0000

Hi Howard,

On Tue, Feb 12, 2013 at 2:47 PM, Howard Yang (howardy)
<howardy@cisco.com> wrote:
> Hi,
>
> I have a couple of comments on TRILL BFD draft
> <draft-ietf-trill-rbridge-bfd-07.txt> and TRILL use of ISIS draft
> <draft-ietf-isis-rfc6326bis-00.txt>.
>
> (1) To support TRILL BFD, it is required to include nickname TLV or sub-TLV
> in the ISIS hello packets.

Every TRILL IS-IS Hello PDU is required to include a Special VLANs and
Flags Sub-TLV which includes the Sender Nickname. Perhaps the
explanatory text for that the Sub-TLV should be expanded to mention
BFD bootstrap.

> The reason is that when the neighbor receives the BFD packets, if the
> nickname of the peer is not known, BFD cannot associate such BFD packets
> with the BFD session.
>
> By the way, let's look at, in specific, the "One-Hop TRILL BFD Control"
> here. Looking at Layer 3 (IP or IPv6) BFD, we have IP address TLV included
> in the ISIS hellos, so that when BFD session is created by ISIS, ISIS can
> pass both local and peer's IP addresses to BFD for BFD to associate a BFD
> packet to a session. Corresponding to IP address, in TRILL, we have the
> nickname. When a BFD session is created with an unknown nickname for the
> peer, and when a BFD packet from this peer is received, BFD has no way to
> associate this BFD packet with the BFD session previously created. Notice
> BFD packets are defined to have the TRILL channel encapsulation
> (draft-ietf-trill-rbridge-channel-08.txt).
>
> So we need to add the requirement of including the local nickname in ISIS
> hellos, in addition to the "ISIS BFD enabled TLV" (RFC 6213).

As above, Sender Nickname is already included in every TRILL IS-IS Hello.

> The nickname is currently defined as nickname sub-tlv
> (<draft-ietf-isis-rfc6326bis-00.txt>) and it is defined only in Router or MT
> Capability TLV. We need to extend it and allow the nickname sub-tlv to be in
> the Multi-Topology-Aware Port Capability TLV.

As above, I do not believe that is necessary.

> (2) In Section 3.1 of the TRILL BFD draft, we have
>
> 3.1 One-Hop TRILL BFD Control
>
>    One-hop TRILL BFD Control is typically used to rapidly detect link
>    and RBridge failures.  TRILL BFD frames over one hop for such
>    purposes SHOULD be sent with high priority; that is, the Inner.VLAN
>    tag priority should be 7, they should be queued for transmission as
>    maximum priority frames and, if they are being sent on an Ethernet
>    link where the output port is configured to include an Outer.VLAN
>    tag, that tag should specify priority 7.
>
>    For neighbor RBridges RB1 and RB2, each RBridge sends one-hop TRILL
>    BFD Control frames to the other only if TRILL IS-IS has detected bi-
>    directional connectivity, that is, the adjacency is in the Two-Way or
>    Report state [RFC6327] and both RBridges indicate support of TRILL
>    BFD is enabled.  The BFD Enabled TLV is used to indicate this as
>    specified in [RFC6213].
>
> The "Two-Way" or "Report" is specific to TRILL LAN interface. It does not
> apply to the point-to-point interface. So, it should be modified to:
>
> "that is, the adjacency is in the Two-Way or Report state [RFC6327] on the
> LAN or INIT on the point-to-point when neighbor is known and both Rbridges
> indicate support of TRILL BFD is enabled."

Work has started on an rfc6327bis draft to extend the proper TRILL
adjacency state machine to point-to-point links and also include MTU
testing on such links, to make them consistent with broadcast links. I
believe that this is the best course. Would you be interested in
helping with rfc6327bis?

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> Thanks,
> -Howard Yang

From howardy@cisco.com  Tue Feb 12 21:27:29 2013
Return-Path: <howardy@cisco.com>
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 3AA0821F894E for <trill@ietfa.amsl.com>; Tue, 12 Feb 2013 21:27:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.999
X-Spam-Level: 
X-Spam-Status: No, score=-9.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_54=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1JB9sKLwPf4g for <trill@ietfa.amsl.com>; Tue, 12 Feb 2013 21:27:27 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id CB04321F8943 for <trill@ietf.org>; Tue, 12 Feb 2013 21:27:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4282; q=dns/txt; s=iport; t=1360733247; x=1361942847; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=1cWoObHp+79C13A6UvEijtpsty40UvNhEhbiQ+a/INo=; b=UeRykbEOqw5w62KzkMSHPsGDSfNI8bvu2ZylN7Zq+K9Jk3ObmLBHv/wG nn0OGvnCAmkGk+sBhNlS+f8VbgPhWWPh5x5WEeocaHh9PqtT2QP47lVxJ c0k/ExkRO5XLtTVn6q0pt31GnC+tQx6PQ0+hY4wYFxl5lVotIP9oZy/9Y g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAIojG1GtJXG9/2dsb2JhbABBA8BuFnOCHwEBAQQ6PxIBCA4KChQxESUCBA4FCId4Aw+2AQ2JW4w1giGCTmEDlEuNGYUTgwaCJw
X-IronPort-AV: E=Sophos;i="4.84,655,1355097600"; d="scan'208";a="176508796"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-3.cisco.com with ESMTP; 13 Feb 2013 05:27:27 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r1D5RRUR026668 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 13 Feb 2013 05:27:27 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.213]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.02.0318.004; Tue, 12 Feb 2013 23:27:26 -0600
From: "Howard Yang (howardy)" <howardy@cisco.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Thread-Topic: [trill] Comments on TRILL BFD draft and TRILL use of ISIS draft
Thread-Index: AQHOCZybTO2m0M8pekyW1cpAvkGbmZh3INyA
Date: Wed, 13 Feb 2013 05:27:26 +0000
Message-ID: <8F62EB044F07504DB195F82B824F34DD25269F@xmb-aln-x15.cisco.com>
In-Reply-To: <CAF4+nEGXb5_s0LOz+Zh8KBNTOGBBvX5ntHVo_02xrM-vaT==Sw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.1.120420
x-originating-ip: [10.21.70.93]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <BE2358CD4A24364EB43B18E19431B99D@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ietf-trill-rbridge-bfd@tools.ietf.org" <draft-ietf-trill-rbridge-bfd@tools.ietf.org>, "draft-ietf-isis-rfc6326bis@tools.ietf.org" <draft-ietf-isis-rfc6326bis@tools.ietf.org>, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] Comments on TRILL BFD draft and TRILL use of ISIS draft
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, 13 Feb 2013 05:27:29 -0000

Hi Donald,

Thanks very much for the answers and explanation.

Yes, I would be very interested in the rfc6327bis extension work.

Thanks,
-Howard


On 2/12/13 7:45 PM, "Donald Eastlake" <d3e3e3@gmail.com> wrote:

>Hi Howard,
>
>On Tue, Feb 12, 2013 at 2:47 PM, Howard Yang (howardy)
><howardy@cisco.com> wrote:
>> Hi,
>>
>> I have a couple of comments on TRILL BFD draft
>> <draft-ietf-trill-rbridge-bfd-07.txt> and TRILL use of ISIS draft
>> <draft-ietf-isis-rfc6326bis-00.txt>.
>>
>> (1) To support TRILL BFD, it is required to include nickname TLV or
>>sub-TLV
>> in the ISIS hello packets.
>
>Every TRILL IS-IS Hello PDU is required to include a Special VLANs and
>Flags Sub-TLV which includes the Sender Nickname. Perhaps the
>explanatory text for that the Sub-TLV should be expanded to mention
>BFD bootstrap.
>
>> The reason is that when the neighbor receives the BFD packets, if the
>> nickname of the peer is not known, BFD cannot associate such BFD packets
>> with the BFD session.
>>
>> By the way, let's look at, in specific, the "One-Hop TRILL BFD Control"
>> here. Looking at Layer 3 (IP or IPv6) BFD, we have IP address TLV
>>included
>> in the ISIS hellos, so that when BFD session is created by ISIS, ISIS
>>can
>> pass both local and peer's IP addresses to BFD for BFD to associate a
>>BFD
>> packet to a session. Corresponding to IP address, in TRILL, we have the
>> nickname. When a BFD session is created with an unknown nickname for the
>> peer, and when a BFD packet from this peer is received, BFD has no way
>>to
>> associate this BFD packet with the BFD session previously created.
>>Notice
>> BFD packets are defined to have the TRILL channel encapsulation
>> (draft-ietf-trill-rbridge-channel-08.txt).
>>
>> So we need to add the requirement of including the local nickname in
>>ISIS
>> hellos, in addition to the "ISIS BFD enabled TLV" (RFC 6213).
>
>As above, Sender Nickname is already included in every TRILL IS-IS Hello.
>
>> The nickname is currently defined as nickname sub-tlv
>> (<draft-ietf-isis-rfc6326bis-00.txt>) and it is defined only in Router
>>or MT
>> Capability TLV. We need to extend it and allow the nickname sub-tlv to
>>be in
>> the Multi-Topology-Aware Port Capability TLV.
>
>As above, I do not believe that is necessary.
>
>> (2) In Section 3.1 of the TRILL BFD draft, we have
>>
>> 3.1 One-Hop TRILL BFD Control
>>
>>    One-hop TRILL BFD Control is typically used to rapidly detect link
>>    and RBridge failures.  TRILL BFD frames over one hop for such
>>    purposes SHOULD be sent with high priority; that is, the Inner.VLAN
>>    tag priority should be 7, they should be queued for transmission as
>>    maximum priority frames and, if they are being sent on an Ethernet
>>    link where the output port is configured to include an Outer.VLAN
>>    tag, that tag should specify priority 7.
>>
>>    For neighbor RBridges RB1 and RB2, each RBridge sends one-hop TRILL
>>    BFD Control frames to the other only if TRILL IS-IS has detected bi-
>>    directional connectivity, that is, the adjacency is in the Two-Way or
>>    Report state [RFC6327] and both RBridges indicate support of TRILL
>>    BFD is enabled.  The BFD Enabled TLV is used to indicate this as
>>    specified in [RFC6213].
>>
>> The "Two-Way" or "Report" is specific to TRILL LAN interface. It does
>>not
>> apply to the point-to-point interface. So, it should be modified to:
>>
>> "that is, the adjacency is in the Two-Way or Report state [RFC6327] on
>>the
>> LAN or INIT on the point-to-point when neighbor is known and both
>>Rbridges
>> indicate support of TRILL BFD is enabled."
>
>Work has started on an rfc6327bis draft to extend the proper TRILL
>adjacency state machine to point-to-point links and also include MTU
>testing on such links, to make them consistent with broadcast links. I
>believe that this is the best course. Would you be interested in
>helping with rfc6327bis?
>
>Thanks,
>Donald
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
> Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
> 155 Beaver Street, Milford, MA 01757 USA
> d3e3e3@gmail.com
>
>> Thanks,
>> -Howard Yang


From ginsberg@cisco.com  Tue Feb 12 22:42:24 2013
Return-Path: <ginsberg@cisco.com>
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 6CD7821F89AA for <trill@ietfa.amsl.com>; Tue, 12 Feb 2013 22:42:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l6WsBnYoaeBa for <trill@ietfa.amsl.com>; Tue, 12 Feb 2013 22:42:23 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 4B9DD21F891D for <trill@ietf.org>; Tue, 12 Feb 2013 22:42:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2655; q=dns/txt; s=iport; t=1360737743; x=1361947343; h=from:to:cc:subject:date:message-id: content-transfer-encoding:mime-version; bh=AGBcstIbtzaw637q9vNTmtB7CY34My0erReKg3CZNxg=; b=DTRUGcBzoCe+ms6Z/DEOxWklpAr8FNOaYkl70vutLRJBqFbNeTn2RPtI Fo9IrjEr9fIz/Yj1b60AiXHKYq9ZRq1+5S9rlTFKD0ZQqVV8/ybBDRWK4 sMeGtweSZGovRhKcyxDZlRcRp9JhLylw29MtUz+0q5gqVevL/U9yjI4bo Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAGU1G1GtJXHA/2dsb2JhbABEwG4Wc4IhAQQ6PxIBFhQUQiYBBA4NiAq/V5EkYQOmd4MGgWkHNw
X-IronPort-AV: E=Sophos;i="4.84,655,1355097600"; d="scan'208";a="176502921"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-6.cisco.com with ESMTP; 13 Feb 2013 06:42:06 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r1D6g6jL021996 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 13 Feb 2013 06:42:06 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.155]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.02.0318.004; Wed, 13 Feb 2013 00:42:06 -0600
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Thread-Topic: TRILL BFD draft and RFC 6213
Thread-Index: Ac4JsgKkFLEjd0LuTIe537xTBjgKGA==
Date: Wed, 13 Feb 2013 06:42:05 +0000
Message-ID: <F3ADE4747C9E124B89F0ED2180CC814F1326FE03@xmb-aln-x02.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.75.73]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "trill@ietf.org" <trill@ietf.org>
Subject: [trill] TRILL BFD draft and RFC 6213
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, 13 Feb 2013 06:42:24 -0000

draft-ietf-trill-rbridge-bfd-07.txt states in Section 3.1 states:

<snip>
For neighbor RBridges RB1 and RB2, each RBridge sends one-hop TRILL
   BFD Control frames to the other only if TRILL IS-IS has detected bi-
   directional connectivity, that is, the adjacency is in the Two-Way or
   Report state [RFC6327] and both RBridges indicate support of TRILL
   BFD is enabled.  The BFD Enabled TLV is used to indicate this as
   specified in [RFC6213].
<end snip>

The BFD Enabled TLV was introduced to address the lack of fate sharing betw=
een IS-IS PDUs and BFD packets. When this is the case, the preferred use of=
 BFD is as a necessary condition for a topology specific adjacency to be us=
able - rather than as simply a fast failure detection mechanism. RFC 6213 t=
herefore introduces (in a backwards compatible way) changes in the ISO 1058=
9 adjacency state machine such that an adjacency is NOT UP and/or the topol=
ogy specific IS neighbor is NOT advertised in LSPs unless the BFD session i=
s up. The logical equivalent of this in RFC 6327 states would be to make th=
e BFD session UP requirement apply to the Report state.

The wording in the draft seems to be stating something different. It is sta=
ting that an Rbridge should not send BFD control frames until after the fol=
lowing two conditions have been verified:

1)Two-Way or Report state has been achieved
2)Neighbor BFD enabled support has been indicated by receipt of the BFD ena=
bled TLV

Defined in this way you differ from RFC 6213 usage in significant ways.

You allow the adjacency to reach full operational state (including IS neigh=
bor advertisement in LSPs) w/o requiring the BFD session to be UP. This mea=
ns you do not have fate sharing protection. Now, if this is because you bel=
ieve there is no fate sharing issue in TRILL, then frankly you don't really=
 need RFC 6213 functionality. The only value add the BFD enabled TLV provid=
es is a small optimization in that you won't needlessly send BFD packets to=
 a neighbor who does not support BFD. This comes at the cost of not being a=
ble to use BFD w a neighbor which supports BFD but does not send the BFD en=
abled TLV. Perhaps this also is not a concern since TRILL use of BFD is onl=
y now being defined and so it can be expected that the BFD enabled TLV will=
 be sent by any Rbridge which supports TRILL BFD.

I do not object to your revised use of the BFD enabled TLV, but I do think =
the draft would be improved by explicitly stating the ways in which TRILL B=
FD usage of the BFD enabled TLV differs from RFC 6213 and the reasons why.

Thanx.

    Les


From iesg-secretary@ietf.org  Wed Feb 13 08:13:10 2013
Return-Path: <iesg-secretary@ietf.org>
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 C446121F86F8; Wed, 13 Feb 2013 08:13:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.531
X-Spam-Level: 
X-Spam-Status: No, score=-102.531 tagged_above=-999 required=5 tests=[AWL=0.068, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 GbCNzfV97fel; Wed, 13 Feb 2013 08:13:10 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 095AB21F8890; Wed, 13 Feb 2013 08:13:10 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.40
Message-ID: <20130213161310.12223.37044.idtracker@ietfa.amsl.com>
Date: Wed, 13 Feb 2013 08:13:10 -0800
Cc: trill mailing list <trill@ietf.org>, trill chair <trill-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [trill] Document Action: 'Requirements for Operations, Administration and Maintenance (OAM) in TRILL (Transparent	Interconnection of Lots of Links)' to Informational RFC	(draft-ietf-trill-oam-req-05.txt)
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, 13 Feb 2013 16:13:11 -0000

The IESG has approved the following document:
- 'Requirements for Operations, Administration and Maintenance (OAM) in
   TRILL (Transparent Interconnection of Lots of Links)'
  (draft-ietf-trill-oam-req-05.txt) as Informational RFC

This document is the product of the Transparent Interconnection of Lots
of Links Working Group.

The IESG contact persons are Ralph Droms and Brian Haberman.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-trill-oam-req/




Technical Summary: 

  The TRILL protocol current supports SNMP and BFD but those provide
  only limited OAM facilities. This document is the first in a planned
  series of documents to provide more complete OAM facilities. It
  gives requirements for those OAM facilities and is expected to be
  followed by an OAM Framework document (currently a TRILL WG draft)
  which is in turn expected to be followed by two detailed
  specifications: Fault Management (current a personal draft) and
  Performance Management (no draft posted at this time). While the
  current direction of TRILL OAM is to parallel IEEE 802.1ag, this
  requirement document is general independent of OAM technology and
  does not constrain that direction.

Working Group Summary: 

  This document originated in the TRILL OAM design team. It was
  adopted by a strong consensus and reviewed by the WG. Changes were
  made based on review in the working group and there was a good
  consensus to forward it for publication.

Document Quality: 

  There is significant vendor interest in more complete OAM facilities
  for TRILL. This document has been thoroughly reviewed. It was
  originated in the TRILL OAM design team and has also been reviewed
  by a number of IEEE 802.1 voting members who volunteered to do so in
  their individual capacity. In addition, it was closely reviewed
  several times by Thomas Narten, a former Internet Area Director.

Personnel: 

  The Document Shepherd is Donald Eastlake.  The Responsible Area
  Director is Ralph Droms.

From iesg-secretary@ietf.org  Wed Feb 13 08:13:10 2013
Return-Path: <iesg-secretary@ietf.org>
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 ED9DB21F8890 for <trill@ietfa.amsl.com>; Wed, 13 Feb 2013 08:13:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.531
X-Spam-Level: 
X-Spam-Status: No, score=-102.531 tagged_above=-999 required=5 tests=[AWL=0.068, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 K6JnsaIUkaiH; Wed, 13 Feb 2013 08:13:10 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 186A121F889C; Wed, 13 Feb 2013 08:13:10 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IANA <drafts-approval@icann.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.40
X-IETF-Draft-string: draft-ietf-trill-oam-req
X-IETF-Draft-revision: 05
Message-ID: <20130213161310.12223.86328.idtracker@ietfa.amsl.com>
Date: Wed, 13 Feb 2013 08:13:10 -0800
Cc: trill mailing list <trill@ietf.org>, trill chair <trill-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [trill] Document Action: 'Requirements for Operations, Administration and Maintenance (OAM) in TRILL (Transparent	Interconnection of Lots of Links)' to Informational RFC	(draft-ietf-trill-oam-req-05.txt)
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: noreply@ietf.org
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, 13 Feb 2013 16:13:11 -0000

The IESG has approved the following document:
- 'Requirements for Operations, Administration and Maintenance (OAM) in
   TRILL (Transparent Interconnection of Lots of Links)'
  (draft-ietf-trill-oam-req-05.txt) as Informational RFC

This document is the product of the Transparent Interconnection of Lots
of Links Working Group.

The IESG contact persons are Ralph Droms and Brian Haberman.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-trill-oam-req/




Technical Summary: 

  The TRILL protocol current supports SNMP and BFD but those provide
  only limited OAM facilities. This document is the first in a planned
  series of documents to provide more complete OAM facilities. It
  gives requirements for those OAM facilities and is expected to be
  followed by an OAM Framework document (currently a TRILL WG draft)
  which is in turn expected to be followed by two detailed
  specifications: Fault Management (current a personal draft) and
  Performance Management (no draft posted at this time). While the
  current direction of TRILL OAM is to parallel IEEE 802.1ag, this
  requirement document is general independent of OAM technology and
  does not constrain that direction.

Working Group Summary: 

  This document originated in the TRILL OAM design team. It was
  adopted by a strong consensus and reviewed by the WG. Changes were
  made based on review in the working group and there was a good
  consensus to forward it for publication.

Document Quality: 

  There is significant vendor interest in more complete OAM facilities
  for TRILL. This document has been thoroughly reviewed. It was
  originated in the TRILL OAM design team and has also been reviewed
  by a number of IEEE 802.1 voting members who volunteered to do so in
  their individual capacity. In addition, it was closely reviewed
  several times by Thomas Narten, a former Internet Area Director.

Personnel: 

  The Document Shepherd is Donald Eastlake.  The Responsible Area
  Director is Ralph Droms.

From internet-drafts@ietf.org  Wed Feb 13 12:21:29 2013
Return-Path: <internet-drafts@ietf.org>
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 75BE421F86EB; Wed, 13 Feb 2013 12:21:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 WHfntMcDaFMH; Wed, 13 Feb 2013 12:21:29 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E56FA21F84B6; Wed, 13 Feb 2013 12:21:28 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.40
Message-ID: <20130213202128.18172.2727.idtracker@ietfa.amsl.com>
Date: Wed, 13 Feb 2013 12:21:28 -0800
Cc: trill@ietf.org
Subject: [trill] I-D Action: draft-ietf-trill-fine-labeling-05.txt
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, 13 Feb 2013 20:21:29 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Transparent Interconnection of Lots of Li=
nks Working Group of the IETF.

	Title           : TRILL (Transparent Interconnection of Lots of Links): Fi=
ne-Grained Labeling
	Author(s)       : Donald Eastlake
                          Mingui Zhang
                          Puneet Agarwal
                          Radia Perlman
                          Dinesh G. Dutt
	Filename        : draft-ietf-trill-fine-labeling-05.txt
	Pages           : 31
	Date            : 2013-02-13

Abstract:
   The IETF has standardized TRILL (Transparent Interconnection of Lots
   of Links), a protocol for least cost transparent frame routing in
   multi-hop networks with arbitrary topologies and link technologies,
   using link-state routing and a hop count. The TRILL base protocol
   standard supports labeling of TRILL data with up to 4K IDs. However,
   there are applications that require more fine-grained labeling of
   data. This document updates RFC 6325 by specifying optional
   extensions to the TRILL base protocol to safely accomplish this.



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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-trill-fine-labeling-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-trill-fine-labeling-05


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


From d3e3e3@gmail.com  Wed Feb 13 17:08:04 2013
Return-Path: <d3e3e3@gmail.com>
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 6B0A121E80BF for <trill@ietfa.amsl.com>; Wed, 13 Feb 2013 17:08:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.414
X-Spam-Level: 
X-Spam-Status: No, score=-103.414 tagged_above=-999 required=5 tests=[AWL=0.185, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 qOw8EfoW2eCn for <trill@ietfa.amsl.com>; Wed, 13 Feb 2013 17:08:01 -0800 (PST)
Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by ietfa.amsl.com (Postfix) with ESMTP id 3601121E80B7 for <trill@ietf.org>; Wed, 13 Feb 2013 17:07:58 -0800 (PST)
Received: by mail-ob0-f182.google.com with SMTP id va7so1930773obc.13 for <trill@ietf.org>; Wed, 13 Feb 2013 17:07:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=cl5ivGuwNqGV2OyjZ8YgCVSAHgWghIjA62Ay6Cy20NM=; b=askeKMmEXxGmT10gJps0Cd6rI3CiJueMA8fUH8Zacv1GDF97TmbpdIwn2g5bOrJrEE gxA3nVJOO7RuF+NTBSkaf3gifWviKyczo3dRD4aw1IsV+HAVwDSIk8ekRy2Oo9uTTvMT LrJCN8w7tOhSBzKtMYCyBCfgHQ8Ab4xWUEzdSMCPsD+8LQlAaC64JKi526dejjvPOuYl FCvC2bUimo2wuCBzDMVtEk99FU8WdzAcH0RNl9fUru27eeOssiFSQLWKzWy7aVwA0BAx 1sXGUQN247dJTXsvCEDzca0wNWafH+TEYa6+FUAFdjVjUky73lA/mupZlPdR65s6RBqU ETnw==
X-Received: by 10.182.40.71 with SMTP id v7mr17861396obk.85.1360804077753; Wed, 13 Feb 2013 17:07:57 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.98.168 with HTTP; Wed, 13 Feb 2013 17:07:37 -0800 (PST)
In-Reply-To: <20130213202128.18172.2727.idtracker@ietfa.amsl.com>
References: <20130213202128.18172.2727.idtracker@ietfa.amsl.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 13 Feb 2013 20:07:37 -0500
Message-ID: <CAF4+nEHWwz4N0pd7OaBVcp4BiHLByy+SvsCpC1G8w+yGjdsS_w@mail.gmail.com>
To: trill@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [trill] I-D Action: draft-ietf-trill-fine-labeling-05.txt
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: Thu, 14 Feb 2013 01:08:04 -0000

This version is intended to corporate tweaked option 2 as per the
following message
http://www.ietf.org/mail-archive/web/trill/current/msg05633.html

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

On Wed, Feb 13, 2013 at 3:21 PM,  <internet-drafts@ietf.org> wrote:
>
> 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 Working Group of the IETF.
>
>         Title           : TRILL (Transparent Interconnection of Lots of Links): Fine-Grained Labeling
>         Author(s)       : Donald Eastlake
>                           Mingui Zhang
>                           Puneet Agarwal
>                           Radia Perlman
>                           Dinesh G. Dutt
>         Filename        : draft-ietf-trill-fine-labeling-05.txt
>         Pages           : 31
>         Date            : 2013-02-13
>
> Abstract:
>    The IETF has standardized TRILL (Transparent Interconnection of Lots
>    of Links), a protocol for least cost transparent frame routing in
>    multi-hop networks with arbitrary topologies and link technologies,
>    using link-state routing and a hop count. The TRILL base protocol
>    standard supports labeling of TRILL data with up to 4K IDs. However,
>    there are applications that require more fine-grained labeling of
>    data. This document updates RFC 6325 by specifying optional
>    extensions to the TRILL base protocol to safely accomplish this.
>
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-trill-fine-labeling
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-trill-fine-labeling-05
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-trill-fine-labeling-05
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> trill mailing list
> trill@ietf.org
> https://www.ietf.org/mailman/listinfo/trill

From d3e3e3@gmail.com  Thu Feb 14 08:23:04 2013
Return-Path: <d3e3e3@gmail.com>
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 17A9621F86A3 for <trill@ietfa.amsl.com>; Thu, 14 Feb 2013 08:23:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.422
X-Spam-Level: 
X-Spam-Status: No, score=-103.422 tagged_above=-999 required=5 tests=[AWL=0.177, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 Ef51TqZwL6c0 for <trill@ietfa.amsl.com>; Thu, 14 Feb 2013 08:23:00 -0800 (PST)
Received: from mail-ob0-f179.google.com (mail-ob0-f179.google.com [209.85.214.179]) by ietfa.amsl.com (Postfix) with ESMTP id 51B2721F869F for <trill@ietf.org>; Thu, 14 Feb 2013 08:22:59 -0800 (PST)
Received: by mail-ob0-f179.google.com with SMTP id un3so2589138obb.24 for <trill@ietf.org>; Thu, 14 Feb 2013 08:22:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=aXpSl0aGhn63yi9GwpPSoMg6lRly+1AXNRsOOmBEpb4=; b=NWt4M1Lg1ei8mdfjYJ7T5JSbHt4jMCpXoatyT+kSqDfDAkslaP/llK+XRxU/jI+IxK YkRv08FNj9E1DudIy46jn+6pE+kJGWYlROOBBOAIDxqerc3PMLWg9uVSf43MmHGMAVlO MN+ZqhIVYnMKGVcr22VQjp7JsSYLfHwlhm2eFxmlLy6qny3JF1rF+Mbr1TiSArc9QOot 9veHy9EF22TUpUw1y+AxLzoeqr9Et2YTb0YRBlgVyzW8e0R2/Eoj1/lc+qSbhRGwJNLf vO/3NOOuBhRVHb3ZJHd3S9e+F2c0Hg3jKLsMzs8mzaulcPzN0NTr6k36dVWfCmzsE44A 4+hQ==
X-Received: by 10.60.172.71 with SMTP id ba7mr20318952oec.50.1360858978841; Thu, 14 Feb 2013 08:22:58 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.98.168 with HTTP; Thu, 14 Feb 2013 08:22:37 -0800 (PST)
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 14 Feb 2013 11:22:37 -0500
Message-ID: <CAF4+nEEfqLM5cD202gN1zj2wi6BJ3w9VP5NfZ7n_VmfnrZWAhA@mail.gmail.com>
To: trill@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [trill] Figure 2 in draft-ietf-trill-oam-framework-00
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: Thu, 14 Feb 2013 16:23:06 -0000

Note that Figure 2 in draft-ietf-trill-oam-framework-00.txt may be
misleading. There is no "MAC Relay", at least as that term is normally
used, inside a TRILL switch.  A revised draft will be posted.

Of course, you can always implement both a TRILL switch and a bridge
and interconnect them in various ways, including putting them in the
same box, if that is what you want to do.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

From d3e3e3@gmail.com  Thu Feb 14 12:57:54 2013
Return-Path: <d3e3e3@gmail.com>
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 D989521F86DD for <trill@ietfa.amsl.com>; Thu, 14 Feb 2013 12:57:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.429
X-Spam-Level: 
X-Spam-Status: No, score=-103.429 tagged_above=-999 required=5 tests=[AWL=0.170, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 9-mt+bM5aViY for <trill@ietfa.amsl.com>; Thu, 14 Feb 2013 12:57:54 -0800 (PST)
Received: from mail-oa0-f45.google.com (mail-oa0-f45.google.com [209.85.219.45]) by ietfa.amsl.com (Postfix) with ESMTP id 419E921F86D3 for <trill@ietf.org>; Thu, 14 Feb 2013 12:57:54 -0800 (PST)
Received: by mail-oa0-f45.google.com with SMTP id o6so3058730oag.18 for <trill@ietf.org>; Thu, 14 Feb 2013 12:57:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=39PYHqq4Sqf2lydKf1PommBCiQuc7SkPbn/J7IpFJ/0=; b=wf2c8a6fXysTRCIVtgJnesF55xKwo3EBg/y/+enWIe24SSZyIbk9heBjPHfjbBwFDQ AhEnGHEmrGabB9vK0fBESTdkaDZ/OdGeXZ1DZIYGQUtcZzRYvKGzvW27DDwdjW0v4RQr swo0CW/n5g7vWTEhjoZQmg20AJk97im/2QK1xSmp6OwNKJoFz/mjyO8zs0BzLVbd1cd0 Zp2b8IGBpEP+nFoHC8epuTYrb1PjquH8zS/ec24CTmOlYC5mFb4MH/KXXlQuKs5lL5eR WMhfesmXjFVvQR8R1ny93rDIgjAdVxkHVmUY1Vmqgm/3wEqguOfhfTagKWlwAqx2nUbb +4QA==
X-Received: by 10.182.86.196 with SMTP id r4mr36170obz.56.1360875473769; Thu, 14 Feb 2013 12:57:53 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.98.168 with HTTP; Thu, 14 Feb 2013 12:57:33 -0800 (PST)
In-Reply-To: <F3ADE4747C9E124B89F0ED2180CC814F1326FE03@xmb-aln-x02.cisco.com>
References: <F3ADE4747C9E124B89F0ED2180CC814F1326FE03@xmb-aln-x02.cisco.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 14 Feb 2013 15:57:33 -0500
Message-ID: <CAF4+nEFQs2GT+Nz3S9ymFRhpmthA7S=Lqm0D5nLmrE8zA5RiuA@mail.gmail.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] TRILL BFD draft and RFC 6213
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: Thu, 14 Feb 2013 20:57:55 -0000

Hi Les,

Thanks for the comments. See below

On Wed, Feb 13, 2013 at 1:42 AM, Les Ginsberg (ginsberg)
<ginsberg@cisco.com> wrote:
> draft-ietf-trill-rbridge-bfd-07.txt states in Section 3.1 states:
>
> <snip>
> For neighbor RBridges RB1 and RB2, each RBridge sends one-hop TRILL
>    BFD Control frames to the other only if TRILL IS-IS has detected bi-
>    directional connectivity, that is, the adjacency is in the Two-Way or
>    Report state [RFC6327] and both RBridges indicate support of TRILL
>    BFD is enabled.  The BFD Enabled TLV is used to indicate this as
>    specified in [RFC6213].
> <end snip>

I believe the reference to RFC 6213 was primarily because that is
where the BFD Enabled TLV is defined.

> The BFD Enabled TLV was introduced to address the lack of fate sharing be=
tween IS-IS PDUs and BFD packets. When this is the case, the preferred use =
of BFD is as a necessary condition for a topology specific adjacency to be =
usable - rather than as simply a fast failure detection mechanism. RFC 6213=
 therefore introduces (in a backwards compatible way) changes in the ISO 10=
589 adjacency state machine such that an adjacency is NOT UP and/or the top=
ology specific IS neighbor is NOT advertised in LSPs unless the BFD session=
 is up. The logical equivalent of this in RFC 6327 states would be to make =
the BFD session UP requirement apply to the Report state.

I agree that, when BFD is in use, it should be a pre-condition for an
adjacency in TRILL to enter the Report state and that RFC 6327 should
be revised to reflect that.

> The wording in the draft seems to be stating something different. It is s=
tating that an Rbridge should not send BFD control frames until after the f=
ollowing two conditions have been verified:
>
> 1)Two-Way or Report state has been achieved
> 2)Neighbor BFD enabled support has been indicated by receipt of the BFD e=
nabled TLV
>
> Defined in this way you differ from RFC 6213 usage in significant ways.
>
> You allow the adjacency to reach full operational state (including IS nei=
ghbor advertisement in LSPs) w/o requiring the BFD session to be UP. This m=
eans you do not have fate sharing protection. Now, if this is because you b=
elieve there is no fate sharing issue in TRILL, then frankly you don't real=
ly need RFC 6213 functionality. The only value add the BFD enabled TLV prov=
ides is a small optimization in that you won't needlessly send BFD packets =
to a neighbor who does not support BFD. This comes at the cost of not being=
 able to use BFD w a neighbor which supports BFD but does not send the BFD =
enabled TLV. Perhaps this also is not a concern since TRILL use of BFD is o=
nly now being defined and so it can be expected that the BFD enabled TLV wi=
ll be sent by any Rbridge which supports TRILL BFD.

I believe that, as you point out, since TRILL use of BFD is just
starting, it can be assumed that the BFD Enabled TLV will be used.

> I do not object to your revised use of the BFD enabled TLV, but I do thin=
k the draft would be improved by explicitly stating the ways in which TRILL=
 BFD usage of the BFD enabled TLV differs from RFC 6213 and the reasons why=
.

OK. I believe this can be incorporated into an RFC 6327bis.

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> Thanx.
>
>     Les

From tsenevir@cisco.com  Sun Feb 17 10:30:34 2013
Return-Path: <tsenevir@cisco.com>
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 1BD1321F8AED for <trill@ietfa.amsl.com>; Sun, 17 Feb 2013 10:30:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.294
X-Spam-Level: 
X-Spam-Status: No, score=-10.294 tagged_above=-999 required=5 tests=[AWL=0.304, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 aa0IIjgklUfc for <trill@ietfa.amsl.com>; Sun, 17 Feb 2013 10:30:33 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id D3EE421F8A8A for <trill@ietf.org>; Sun, 17 Feb 2013 10:30:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4806; q=dns/txt; s=iport; t=1361125833; x=1362335433; h=from:to:subject:date:message-id:mime-version; bh=OSVDvtYbpH5MDjYfIGUVYjjCMHEwR14p+bALY/pJqMc=; b=BYmphJLfQPkY3TQcGhytkGBVwkesNg0AToX4o1/j48rj419WRxMw9BTW tfpjnH6SmyiDyNY0bBx+I2kDaQMJi51zmQI7HxHxKJ/koOj1LGDVm6KLA Uk4pLcB8BVBgl4bWejodTQWno2ZTxJJ6NnFj1JBm6NZCc9fn4zEga19RX Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAFchIVGtJV2Z/2dsb2JhbABFgkO9Wn8Wc4IhAQQtXgEqViYBBBsBEod3DJ14oBaPBoMXYQOnBIMHgic
X-IronPort-AV: E=Sophos;i="4.84,682,1355097600";  d="scan'208,217";a="178043398"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-2.cisco.com with ESMTP; 17 Feb 2013 18:30:32 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r1HIUWAv029256 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <trill@ietf.org>; Sun, 17 Feb 2013 18:30:32 GMT
Received: from xmb-rcd-x08.cisco.com ([169.254.8.192]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.02.0318.004; Sun, 17 Feb 2013 12:30:32 -0600
From: "Tissa Senevirathne (tsenevir)" <tsenevir@cisco.com>
To: "trill@ietf.org" <trill@ietf.org>
Thread-Topic: draft-tissa-trill-oam-fm <OAM solution draft>
Thread-Index: Ac4NPN0vxChb4ubyS3Ox1Pwfi9sifw==
Date: Sun, 17 Feb 2013 18:30:31 +0000
Message-ID: <FBEA3E19AA24F847BA3AE74E2FE193562890C3E1@xmb-rcd-x08.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.167.54]
Content-Type: multipart/alternative; boundary="_000_FBEA3E19AA24F847BA3AE74E2FE193562890C3E1xmbrcdx08ciscoc_"
MIME-Version: 1.0
Subject: [trill] draft-tissa-trill-oam-fm <OAM solution draft>
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: Sun, 17 Feb 2013 18:30:34 -0000

--_000_FBEA3E19AA24F847BA3AE74E2FE193562890C3E1xmbrcdx08ciscoc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dear All

We have published -01 version. Significant edits have been made to align wi=
th the 802.1 CFM.

Please review and share the comments.


Abstract:

   TRILL OAM Fault Management solution is presented in this document.

   Methods proposed in this document follow the IEEE 802.1 CFM

   framework and reuse OAM tools where possible. Additional messages

   and TLVs are defined for TRILL specific applications or where

   different set of information is required than IEEE 802.1 CFM.


:             http://www.ietf.org/internet-drafts/draft-tissa-trill-oam-fm-=
01.txt

Thanks
Tissa

--_000_FBEA3E19AA24F847BA3AE74E2FE193562890C3E1xmbrcdx08ciscoc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:m=3D"http://schema=
s.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html=
40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Dear All<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We have published -01 version. Significant edits hav=
e been made to align with the 802.1 CFM.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please review and share the comments.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Abstract:<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; TRILL OAM Fault Management solution =
is presented in this document.<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; Methods proposed in this document fo=
llow the IEEE 802.1 CFM<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; framework and reuse OAM tools where =
possible. Additional messages<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; and TLVs are defined for TRILL speci=
fic applications or where<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; different set of information is requ=
ired than IEEE 802.1 CFM.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; <a href=3D"http://www.ietf.org/internet-drafts/dra=
ft-tissa-trill-oam-fm-01.txt">
http://www.ietf.org/internet-drafts/draft-tissa-trill-oam-fm-01.txt</a><o:p=
></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks<o:p></o:p></p>
<p class=3D"MsoNormal">Tissa<o:p></o:p></p>
</div>
</body>
</html>

--_000_FBEA3E19AA24F847BA3AE74E2FE193562890C3E1xmbrcdx08ciscoc_--

From talmi@marvell.com  Mon Feb 18 07:08:15 2013
Return-Path: <talmi@marvell.com>
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 1E6B621F87D4 for <trill@ietfa.amsl.com>; Mon, 18 Feb 2013 07:08:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.598
X-Spam-Level: 
X-Spam-Status: No, score=-5.598 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 Rt7wh+cr8Cnn for <trill@ietfa.amsl.com>; Mon, 18 Feb 2013 07:08:12 -0800 (PST)
Received: from na3sys009aog110.obsmtp.com (na3sys009aog110.obsmtp.com [74.125.149.203]) by ietfa.amsl.com (Postfix) with ESMTP id B795D21F8461 for <trill@ietf.org>; Mon, 18 Feb 2013 07:08:12 -0800 (PST)
Received: from sc-owa02.marvell.com ([199.233.58.137]) (using TLSv1) by na3sys009aob110.postini.com ([74.125.148.12]) with SMTP ID DSNKUSJD1lBb4JH4xFYsimpkZ0H3IawDhAzD@postini.com; Mon, 18 Feb 2013 07:08:12 PST
Received: from YK-HUB02.marvell.com (10.4.102.52) by sc-owa02.marvell.com (10.93.76.22) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 18 Feb 2013 06:47:29 -0800
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB02.marvell.com ([10.4.102.52]) with mapi; Mon, 18 Feb 2013 16:47:25 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: "trill@ietf.org" <trill@ietf.org>
Date: Mon, 18 Feb 2013 16:47:23 +0200
Thread-Topic: New draft: draft-mizrahi-trill-loss-delay-00
Thread-Index: Ac4N5mrEG1XxBAnYSvSlgxyFBe7Mxw==
Message-ID: <74470498B659FA4687F0B0018C19A89C01A0F951B684@IL-MB01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_74470498B659FA4687F0B0018C19A89C01A0F951B684ILMB01marve_"
MIME-Version: 1.0
Cc: "tsenevir@cisco.com" <tsenevir@cisco.com>, "Donald Eastlake \(d3e3e3@gmail.com\)" <d3e3e3@gmail.com>, "Samer Salam \(ssalam\) \(ssalam@cisco.com\)" <ssalam@cisco.com>
Subject: [trill] New draft: draft-mizrahi-trill-loss-delay-00
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: Mon, 18 Feb 2013 15:08:15 -0000

--_000_74470498B659FA4687F0B0018C19A89C01A0F951B684ILMB01marve_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

We have uploaded a new draft titled "Loss and Delay Measurement in TRILL".

http://tools.ietf.org/html/draft-mizrahi-trill-loss-delay

Comments will be welcome.

Thanks,
Tal.


--_000_74470498B659FA4687F0B0018C19A89C01A0F951B684ILMB01marve_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Hi,<o:p></o:p></=
p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>We have up=
loaded a new draft titled &#8220;Loss and Delay Measurement in TRILL&#8221;=
.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNor=
mal><a href=3D"http://tools.ietf.org/html/draft-mizrahi-trill-loss-delay">h=
ttp://tools.ietf.org/html/draft-mizrahi-trill-loss-delay</a><o:p></o:p></p>=
<p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Comments wil=
l be welcome.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p cl=
ass=3DMsoNormal>Thanks,<o:p></o:p></p><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:"Arial","sans-serif"'>Tal.<o:p></o:p></span></p=
><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>=

--_000_74470498B659FA4687F0B0018C19A89C01A0F951B684ILMB01marve_--

From zhangmingui@huawei.com  Mon Feb 18 16:36:40 2013
Return-Path: <zhangmingui@huawei.com>
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 5FBF321E8063 for <trill@ietfa.amsl.com>; Mon, 18 Feb 2013 16:36:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.51
X-Spam-Level: 
X-Spam-Status: No, score=-6.51 tagged_above=-999 required=5 tests=[AWL=0.089,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 3-8YkS4G1wlT for <trill@ietfa.amsl.com>; Mon, 18 Feb 2013 16:36:39 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 567AD21E8051 for <trill@ietf.org>; Mon, 18 Feb 2013 16:36:39 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id APV72479; Tue, 19 Feb 2013 00:36:36 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 19 Feb 2013 00:35:56 +0000
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 19 Feb 2013 00:36:20 +0000
Received: from NKGEML508-MBX.china.huawei.com ([169.254.7.33]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.01.0323.007; Tue, 19 Feb 2013 08:36:14 +0800
From: Mingui Zhang <zhangmingui@huawei.com>
To: "trill@ietf.org" <trill@ietf.org>
Thread-Topic: Problem Statement: TRILL Active/Active Edge
Thread-Index: AQHODjkf163nSSUg6Eys4bt7WEZfPA==
Date: Tue, 19 Feb 2013 00:36:13 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E732AFFF03@nkgeml508-mbx.china.huawei.com>
References: <CAFOuuo4zvX5AtD-oGRRftuZaKmhY7C7-SvDjznMOdzUj+Q3fGQ@mail.gmail.com> <FBEA3E19AA24F847BA3AE74E2FE1935628892DF6@xmb-rcd-x08.cisco.com> <CAFOuuo5LP1EzajpeBri2KhTT-wf+vv=JwmTLma9_mxg7dM5PvQ@mail.gmail.com> <FBEA3E19AA24F847BA3AE74E2FE1935628892EAE@xmb-rcd-x08.cisco.com> <4552F0907735844E9204A62BBDD325E732138B02@SZXEML507-MBS.china.huawei.com> <EE1367B6-5498-492E-A57A-155312162CFC@gmail.com> <201212122025.qBCKPmM7013618@cichlid.raleigh.ibm.com> <0E430FEE-F2AD-4EA0-9E98-50762B563E9B@gmail.com> <201212122257.qBCMvdeW014734@cichlid.raleigh.ibm.com> <4552F0907735844E9204A62BBDD325E732139D5A@SZXEML507-MBS.china.huawei.com> <CAFOuuo4wfJDfbshPa14ruK-SPrxU4W-Pu9uRY2to0KBaKjt5JA@mail.gmail.com> <4552F0907735844E9204A62BBDD325E73213A2AB@SZXEML507-MBS.china.huawei.com>
In-Reply-To: <4552F0907735844E9204A62BBDD325E73213A2AB@SZXEML507-MBS.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.102.175]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: Thomas Narten <narten@us.ibm.com>, "zhai.hongjun@zte.com.cn" <zhai.hongjun@zte.com.cn>, "sunny.rajagopalan@us.ibm.com" <sunny.rajagopalan@us.ibm.com>, Radia Perlman <radiaperlman@gmail.com>, Sam Aldrin <aldrin.ietf@gmail.com>, "Tissa Senevirathne \(tsenevir\)" <tsenevir@cisco.com>
Subject: [trill] Problem Statement: TRILL Active/Active Edge
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: Tue, 19 Feb 2013 00:36:40 -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.=20

Whether we have left anything out, whether the ideas in the document are ac=
curate? 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 repo=
sitory.

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-aggr=
egation-03.txt
Status:          http://datatracker.ietf.org/doc/draft-zhang-trill-aggregat=
ion
Htmlized:        http://tools.ietf.org/html/draft-zhang-trill-aggregation-0=
3
Diff:            http://www.ietf.org/rfcdiff?url2=3Ddraft-zhang-trill-aggre=
gation-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.

                                                                           =
      =20


The IETF Secretariat

From Gagan_Goel@infosys.com  Tue Feb 19 00:24:50 2013
Return-Path: <Gagan_Goel@infosys.com>
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 02CCE21F8BA1 for <trill@ietfa.amsl.com>; Tue, 19 Feb 2013 00:24:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 eoRezSKJx4CD for <trill@ietfa.amsl.com>; Tue, 19 Feb 2013 00:24:47 -0800 (PST)
Received: from KECGATE03.infosys.com (kecgate03.infosys.com [122.98.10.31]) by ietfa.amsl.com (Postfix) with ESMTP id 9870C21F8BC9 for <trill@ietf.org>; Tue, 19 Feb 2013 00:24:46 -0800 (PST)
X-TM-IMSS-Message-ID: <3932d3e70005aa1b@infosys.com>
Received: from blrkechub04.ad.infosys.com ([10.66.236.44]) by infosys.com ([122.98.10.31]) with ESMTP (TREND IMSS SMTP Service 7.1) id 3932d3e70005aa1b ; Tue, 19 Feb 2013 13:47:50 +0530
Received: from BLRKECHUB08.ad.infosys.com (10.66.236.138) by blrkechub04.ad.infosys.com (10.66.236.44) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 19 Feb 2013 13:54:26 +0530
Received: from BLRKECMBX23.ad.infosys.com ([fe80::d9f9:2028:fd8:1e35]) by BLRKECHUB08.ad.infosys.com ([::1]) with mapi id 14.02.0318.004; Tue, 19 Feb 2013 13:54:25 +0530
From: Gagan Mohan Goel <Gagan_Goel@infosys.com>
To: Tal Mizrahi <talmi@marvell.com>
Thread-Topic: New draft: draft-mizrahi-trill-loss-delay-00
Thread-Index: Ac4N5mrEG1XxBAnYSvSlgxyFBe7MxwAkmsFg
Date: Tue, 19 Feb 2013 08:24:25 +0000
Message-ID: <06D3FFFAA621E5459625E5E757AE9A1B0B8D970A@BLRKECMBX23.ad.infosys.com>
References: <74470498B659FA4687F0B0018C19A89C01A0F951B684@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01A0F951B684@IL-MB01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.236.169]
Content-Type: multipart/alternative; boundary="_000_06D3FFFAA621E5459625E5E757AE9A1B0B8D970ABLRKECMBX23adin_"
MIME-Version: 1.0
Cc: "tsenevir@cisco.com" <tsenevir@cisco.com>, "Donald Eastlake \(d3e3e3@gmail.com\)" <d3e3e3@gmail.com>, "Samer Salam \(ssalam\) \(ssalam@cisco.com\)" <ssalam@cisco.com>, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] New draft: draft-mizrahi-trill-loss-delay-00
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: Tue, 19 Feb 2013 08:24:50 -0000

--_000_06D3FFFAA621E5459625E5E757AE9A1B0B8D970ABLRKECMBX23adin_
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Tal,

Following are my views on the draft http://tools.ietf.org/html/draft-mizr=
ahi-trill-loss-delay.

1) Section 4.2.3 SLR Message Reception

<snip>    The receiver computes the one-way packet delay with respect to =
a measurement interval. A measurement interval includes a sequence of
   1SLM message. The one-way packet delay is performed by comparing the c=
ounter values TXp and RXp at the beginning of the measurement
   interval, and the counter values TXc and RXc at the end of the  measur=
ement interval (Figure 2):
<snip>

I understand that receiver can only calculate the one way packet loss (an=
d not packet delay) with incoming SLM message. I think the above can be m=
odified to:



 The receiver computes the one-way packet loss with respect to a measurem=
ent interval. A measurement interval includes a sequence of
   SLM message. The one-way packet loss is performed by comparing the cou=
nter values TXp and RXp at the beginning of the measurement
   interval, and the counter values TXc and RXc at the end of the  measur=
ement interval (Figure 2):

2) 4.1.2<http://tools.ietf.org/html/draft-mizrahi-trill-loss-delay-00#sec=
tion-4.1.2>. 1SLM Message Reception

<snip> The receiver MUST maintain a reception counter for each peer MEP a=
nd test ID. Upon receiving a 1SLM packet, the receiver MUST verify that:



   o The 1SLM packet is destined to the current MEP.

   o The packet's MD level matches the MEP's MD level.

<snip>
May be another criteria that can be added to handle any transient network=
 loop scenario:
=D8  Discard the message if counter received in the incoming 1SLM message=
 is lower than current RX count for same testID.
Regards
Gagan Mohan Goel

From: trill-bounces@ietf.org [mailto:trill-bounces@ietf.org] On Behalf Of=
 Tal Mizrahi
Sent: Monday, February 18, 2013 8:17 PM
To: trill@ietf.org
Cc: tsenevir@cisco.com; Donald Eastlake (d3e3e3@gmail.com); Samer Salam (=
ssalam) (ssalam@cisco.com)
Subject: [trill] New draft: draft-mizrahi-trill-loss-delay-00

Hi,

We have uploaded a new draft titled "Loss and Delay Measurement in TRILL"=
.

http://tools.ietf.org/html/draft-mizrahi-trill-loss-delay

Comments will be welcome.

Thanks,
Tal.


**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended sol=
ely 
for the use of the addressee(s). If you are not the intended recipient, p=
lease 
notify the sender by e-mail and delete the original message. Further, you=
 are not 
to copy, disclose, or distribute this e-mail or its contents to any other=
 person and 
any such actions are unlawful. This e-mail may contain viruses. Infosys h=
as taken 
every reasonable precaution to minimize this risk, but is not liable for =
any damage 
you may sustain as a result of any virus in this e-mail. You should carry=
 out your 
own virus checks before opening the e-mail or attachment. Infosys reserve=
s the 
right to monitor and review the content of all messages sent to or from t=
his e-mail 
address. Messages sent to or from this e-mail address may be stored on th=
e 
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***

--_000_06D3FFFAA621E5459625E5E757AE9A1B0B8D970ABLRKECMBX23adin_
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-mi=
crosoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:wo=
rd" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D=
"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-885=
9-1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
=09{font-family:Wingdings;
=09panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
=09{font-family:Wingdings;
=09panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
=09{font-family:Calibri;
=09panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
=09{font-family:Tahoma;
=09panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
=09{margin:0in;
=09margin-bottom:.0001pt;
=09font-size:11.0pt;
=09font-family:"Calibri","sans-serif";}
h4
=09{mso-style-priority:9;
=09mso-style-link:"Heading 4 Char";
=09mso-margin-top-alt:auto;
=09margin-right:0in;
=09mso-margin-bottom-alt:auto;
=09margin-left:0in;
=09mso-line-height-alt:0pt;
=09font-size:12.0pt;
=09font-family:"Courier New";}
a:link, span.MsoHyperlink
=09{mso-style-priority:99;
=09color:blue;
=09text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
=09{mso-style-priority:99;
=09color:purple;
=09text-decoration:underline;}
pre
=09{mso-style-priority:99;
=09mso-style-link:"HTML Preformatted Char";
=09margin:0in;
=09margin-bottom:.0001pt;
=09font-size:12.0pt;
=09font-family:"Courier New";}
span.EmailStyle17
=09{mso-style-type:personal;
=09font-family:"Calibri","sans-serif";
=09color:windowtext;}
span.EmailStyle18
=09{mso-style-type:personal-reply;
=09font-family:"Calibri","sans-serif";
=09color:#1F497D;}
span.Heading4Char
=09{mso-style-name:"Heading 4 Char";
=09mso-style-priority:9;
=09mso-style-link:"Heading 4";
=09font-family:"Courier New";
=09font-weight:bold;}
span.HTMLPreformattedChar
=09{mso-style-name:"HTML Preformatted Char";
=09mso-style-priority:99;
=09mso-style-link:"HTML Preformatted";
=09font-family:"Courier New";}
.MsoChpDefault
=09{mso-style-type:export-only;
=09font-size:10.0pt;}
@page WordSection1
=09{size:8.5in 11.0in;
=09margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
=09{page:WordSection1;}
/* List Definitions */
@list l0
=09{mso-list-id:1395347903;
=09mso-list-type:hybrid;
=09mso-list-template-ids:-864665048 67698699 67698691 67698693 67698689 6=
7698691 67698693 67698689 67698691 67698693;}
@list l0:level1
=09{mso-level-number-format:bullet;
=09mso-level-text:\F0D8;
=09mso-level-tab-stop:none;
=09mso-level-number-position:left;
=09text-indent:-.25in;
=09font-family:Wingdings;}
@list l0:level2
=09{mso-level-number-format:bullet;
=09mso-level-text:o;
=09mso-level-tab-stop:none;
=09mso-level-number-position:left;
=09text-indent:-.25in;
=09font-family:"Courier New";}
@list l0:level3
=09{mso-level-number-format:bullet;
=09mso-level-text:\F0A7;
=09mso-level-tab-stop:none;
=09mso-level-number-position:left;
=09text-indent:-.25in;
=09font-family:Wingdings;}
@list l0:level4
=09{mso-level-number-format:bullet;
=09mso-level-text:\F0B7;
=09mso-level-tab-stop:none;
=09mso-level-number-position:left;
=09text-indent:-.25in;
=09font-family:Symbol;}
@list l0:level5
=09{mso-level-number-format:bullet;
=09mso-level-text:o;
=09mso-level-tab-stop:none;
=09mso-level-number-position:left;
=09text-indent:-.25in;
=09font-family:"Courier New";}
@list l0:level6
=09{mso-level-number-format:bullet;
=09mso-level-text:\F0A7;
=09mso-level-tab-stop:none;
=09mso-level-number-position:left;
=09text-indent:-.25in;
=09font-family:Wingdings;}
@list l0:level7
=09{mso-level-number-format:bullet;
=09mso-level-text:\F0B7;
=09mso-level-tab-stop:none;
=09mso-level-number-position:left;
=09text-indent:-.25in;
=09font-family:Symbol;}
@list l0:level8
=09{mso-level-number-format:bullet;
=09mso-level-text:o;
=09mso-level-tab-stop:none;
=09mso-level-number-position:left;
=09text-indent:-.25in;
=09font-family:"Courier New";}
@list l0:level9
=09{mso-level-number-format:bullet;
=09mso-level-text:\F0A7;
=09mso-level-tab-stop:none;
=09mso-level-number-position:left;
=09text-indent:-.25in;
=09font-family:Wingdings;}
ol
=09{margin-bottom:0in;}
ul
=09{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi Tal,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;=
Arial&quot;,&quot;sans-serif&quot;">Following are my views on the draft h=
ttp://tools.ietf.org/html/draft-mizrahi-trill-loss-delay.<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;=
Arial&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<h4 style=3D"page-break-before:always"><span style=3D"font-size:10.0pt;fo=
nt-family:&quot;Arial&quot;,&quot;sans-serif&quot;;font-weight:normal">1)=
 Section 4.2.3
</span><span lang=3D"EN" style=3D"font-size:10.0pt;font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;;font-weight:normal">SLR Message Reception<=
o:p></o:p></span></h4>
<pre style=3D"page-break-before:always"><span style=3D"font-size:10.0pt;f=
ont-family:&quot;Arial&quot;,&quot;sans-serif&quot;">&lt;snip&gt; </span>=
<span lang=3D"EN" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;=
,&quot;sans-serif&quot;">&nbsp;&nbsp;&nbsp;The receiver computes the one-=
way packet delay with respect to a measurement interval. A measurement in=
terval includes a sequence of<o:p></o:p></span></pre>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"E=
N" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-ser=
if&quot;">&nbsp;&nbsp; 1SLM message. The one-way packet delay is performe=
d by comparing the counter values TXp and RXp at the beginning of the mea=
surement<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"E=
N" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-ser=
if&quot;">&nbsp;&nbsp; interval, and the counter values TXc and RXc at th=
e end of the &nbsp;measurement interval (Figure 2):
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;=
Arial&quot;,&quot;sans-serif&quot;">&lt;snip&gt;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;=
Arial&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;=
Arial&quot;,&quot;sans-serif&quot;">I understand that receiver can only c=
alculate the one way packet loss (and not packet delay) with incoming SLM=
 message. I think the above can be modified to:<o:p></o:p></span></p>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-s=
ize:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">&nbsp; <=
o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-s=
ize:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">&nbsp;Th=
e receiver computes the one-way packet <b><i>loss</i></b> with respect to=
 a measurement interval. A measurement interval includes a sequence of<o:=
p></o:p></span></pre>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"E=
N" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-ser=
if&quot;">&nbsp;&nbsp;
<b><i>SLM</i></b> message. The one-way packet <b><i>loss</i></b> is perfo=
rmed by comparing the counter values TXp and RXp at the beginning of the =
measurement<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"E=
N" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-ser=
if&quot;">&nbsp;&nbsp; interval, and the counter values TXc and RXc at th=
e end of the &nbsp;measurement interval (Figure 2):
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;=
Arial&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<h4 style=3D"page-break-before:always"><a name=3D"section-4.1.2"><span la=
ng=3D"EN" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;;font-weight:normal">2)
</span></a><a href=3D"http://tools.ietf.org/html/draft-mizrahi-trill-loss=
-delay-00#section-4.1.2"><span lang=3D"EN" style=3D"font-size:10.0pt;font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:windowtext;font-we=
ight:normal;text-decoration:none">4.1.2</span></a><span lang=3D"EN" style=
=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;=
;font-weight:normal">.
 1SLM Message Reception<o:p></o:p></span></h4>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-s=
ize:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">&lt;snip=
&gt; The receiver MUST maintain a reception counter for each peer MEP and=
 test ID. Upon receiving a 1SLM packet, the receiver MUST verify that:<o:=
p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-s=
ize:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;"><o:p>&nb=
sp;</o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-s=
ize:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">&nbsp;&n=
bsp; o The 1SLM packet is destined to the current MEP.<o:p></o:p></span><=
/pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-s=
ize:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">&nbsp;&n=
bsp; o The packet's MD level matches the MEP's MD level.<o:p></o:p></span=
></pre>
<h4 style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;font-weigh=
t:normal">&lt;snip&gt;<o:p></o:p></span></h4>
<h4 style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;font-weigh=
t:normal">May be another criteria that can be added to handle any transie=
nt network loop scenario:<o:p></o:p></span></h4>
<h4 style=3D"margin-left:.5in;text-indent:-.25in;page-break-before:always=
;mso-list:l0 level1 lfo1">
<![if !supportLists]><span lang=3D"EN" style=3D"font-size:10.0pt;font-fam=
ily:Wingdings;font-weight:normal"><span style=3D"mso-list:Ignore">=D8<spa=
n style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;
</span></span></span><![endif]><span lang=3D"EN" style=3D"font-size:10.0p=
t;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;font-weight:normal=
">Discard the message if counter received in the incoming 1SLM message is=
 lower than current RX count for same testID.<o:p></o:p></span></h4>
<h4 style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;font-weigh=
t:normal">Regards<o:p></o:p></span></h4>
<p class=3D"MsoNormal"><span lang=3D"EN" style=3D"font-size:10.0pt;font-f=
amily:&quot;Arial&quot;,&quot;sans-serif&quot;">Gagan Mohan Goel</span><o=
:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></s=
pan></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0i=
n 0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&qu=
ot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"fo=
nt-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> tr=
ill-bounces@ietf.org [mailto:trill-bounces@ietf.org]
<b>On Behalf Of </b>Tal Mizrahi<br>
<b>Sent:</b> Monday, February 18, 2013 8:17 PM<br>
<b>To:</b> trill@ietf.org<br>
<b>Cc:</b> tsenevir@cisco.com; Donald Eastlake (d3e3e3@gmail.com); Samer =
Salam (ssalam) (ssalam@cisco.com)<br>
<b>Subject:</b> [trill] New draft: draft-mizrahi-trill-loss-delay-00<o:p>=
</o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We have uploaded a new draft titled &#8220;Loss an=
d Delay Measurement in TRILL&#8221;.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><a href=3D"http://tools.ietf.org/html/draft-mizrah=
i-trill-loss-delay">http://tools.ietf.org/html/draft-mizrahi-trill-loss-d=
elay</a><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Comments will be welcome.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;=
Arial&quot;,&quot;sans-serif&quot;">Tal.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

<table><tr><td bgcolor=3D#ffffff><font color=3D#000000><pre>*************=
*** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended sol=
ely 
for the use of the addressee(s). If you are not the intended recipient, p=
lease 
notify the sender by e-mail and delete the original message. Further, you=
 are not 
to copy, disclose, or distribute this e-mail or its contents to any other=
 person and 
any such actions are unlawful. This e-mail may contain viruses. Infosys h=
as taken 
every reasonable precaution to minimize this risk, but is not liable for =
any damage 
you may sustain as a result of any virus in this e-mail. You should carry=
 out your 
own virus checks before opening the e-mail or attachment. Infosys reserve=
s the 
right to monitor and review the content of all messages sent to or from t=
his e-mail 
address. Messages sent to or from this e-mail address may be stored on th=
e 
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***</pre></font></td>=
</tr></table>

--_000_06D3FFFAA621E5459625E5E757AE9A1B0B8D970ABLRKECMBX23adin_--

From talmi@marvell.com  Tue Feb 19 01:38:04 2013
Return-Path: <talmi@marvell.com>
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 78D3721F87A4 for <trill@ietfa.amsl.com>; Tue, 19 Feb 2013 01:38:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.798
X-Spam-Level: 
X-Spam-Status: No, score=-5.798 tagged_above=-999 required=5 tests=[AWL=0.800,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 NWiAJqjEs64m for <trill@ietfa.amsl.com>; Tue, 19 Feb 2013 01:38:02 -0800 (PST)
Received: from na3sys009aog120.obsmtp.com (na3sys009aog120.obsmtp.com [74.125.149.140]) by ietfa.amsl.com (Postfix) with ESMTP id 8B96321F8692 for <trill@ietf.org>; Tue, 19 Feb 2013 01:37:57 -0800 (PST)
Received: from SC-OWA01.marvell.com ([199.233.58.136]) (using TLSv1) by na3sys009aob120.postini.com ([74.125.148.12]) with SMTP ID DSNKUSNH9H9oopeVGnA06s6f7xeEyVdbpwa6@postini.com; Tue, 19 Feb 2013 01:38:02 PST
Received: from YK-HUB01.marvell.com (10.4.102.51) by sc-owa01.marvell.com (10.93.76.21) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 19 Feb 2013 01:34:13 -0800
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB01.marvell.com ([10.4.102.51]) with mapi; Tue, 19 Feb 2013 11:34:11 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: Gagan Mohan Goel <Gagan_Goel@infosys.com>
Date: Tue, 19 Feb 2013 11:34:07 +0200
Thread-Topic: New draft: draft-mizrahi-trill-loss-delay-00
Thread-Index: Ac4N5mrEG1XxBAnYSvSlgxyFBe7MxwAkmsFgAAJ5bcA=
Message-ID: <74470498B659FA4687F0B0018C19A89C01A0F951B840@IL-MB01.marvell.com>
References: <74470498B659FA4687F0B0018C19A89C01A0F951B684@IL-MB01.marvell.com> <06D3FFFAA621E5459625E5E757AE9A1B0B8D970A@BLRKECMBX23.ad.infosys.com>
In-Reply-To: <06D3FFFAA621E5459625E5E757AE9A1B0B8D970A@BLRKECMBX23.ad.infosys.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_74470498B659FA4687F0B0018C19A89C01A0F951B840ILMB01marve_"
MIME-Version: 1.0
Cc: "tsenevir@cisco.com" <tsenevir@cisco.com>, "Donald Eastlake \(d3e3e3@gmail.com\)" <d3e3e3@gmail.com>, "Samer Salam \(ssalam\) \(ssalam@cisco.com\)" <ssalam@cisco.com>, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] New draft: draft-mizrahi-trill-loss-delay-00
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: Tue, 19 Feb 2013 09:38:04 -0000

--_000_74470498B659FA4687F0B0018C19A89C01A0F951B840ILMB01marve_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Gagan,

Thanks for your comments.
Please see my responses inline.

Tal.

From: Gagan Mohan Goel [mailto:Gagan_Goel@infosys.com]
Sent: Tuesday, February 19, 2013 10:24 AM
To: Tal Mizrahi
Cc: tsenevir@cisco.com; Donald Eastlake (d3e3e3@gmail.com); Samer Salam (ss=
alam) (ssalam@cisco.com); trill@ietf.org
Subject: RE: New draft: draft-mizrahi-trill-loss-delay-00

Hi Tal,

Following are my views on the draft http://tools.ietf.org/html/draft-mizrah=
i-trill-loss-delay.

1) Section 4.2.3 SLR Message Reception

<snip>    The receiver computes the one-way packet delay with respect to a =
measurement interval. A measurement interval includes a sequence of
   1SLM message. The one-way packet delay is performed by comparing the cou=
nter values TXp and RXp at the beginning of the measurement
   interval, and the counter values TXc and RXc at the end of the  measurem=
ent interval (Figure 2):
<snip>

I understand that receiver can only calculate the one way packet loss (and =
not packet delay) with incoming SLM message. I think the above can be modif=
ied to:



 The receiver computes the one-way packet loss with respect to a measuremen=
t interval. A measurement interval includes a sequence of
   SLM message. The one-way packet loss is performed by comparing the count=
er values TXp and RXp at the beginning of the measurement
   interval, and the counter values TXc and RXc at the end of the  measurem=
ent interval (Figure 2):

[TM] Right. It is indeed a typo.

2) 4.1.2<http://tools.ietf.org/html/draft-mizrahi-trill-loss-delay-00#secti=
on-4.1.2>. 1SLM Message Reception

<snip> The receiver MUST maintain a reception counter for each peer MEP and=
 test ID. Upon receiving a 1SLM packet, the receiver MUST verify that:



   o The 1SLM packet is destined to the current MEP.

   o The packet's MD level matches the MEP's MD level.

<snip>
May be another criteria that can be added to handle any transient network l=
oop scenario:
=D8  Discard the message if counter received in the incoming 1SLM message i=
s lower than current RX count for same testID.
[TM] Since packets can in some cases be received out-of-order, this filter =
may discard 1SLM packets that should be counted.

Regards
Gagan Mohan Goel

From: trill-bounces@ietf.org [mailto:trill-bounces@ietf.org] On Behalf Of T=
al Mizrahi
Sent: Monday, February 18, 2013 8:17 PM
To: trill@ietf.org
Cc: tsenevir@cisco.com; Donald Eastlake (d3e3e3@gmail.com); Samer Salam (ss=
alam) (ssalam@cisco.com)
Subject: [trill] New draft: draft-mizrahi-trill-loss-delay-00

Hi,

We have uploaded a new draft titled "Loss and Delay Measurement in TRILL".

http://tools.ietf.org/html/draft-mizrahi-trill-loss-delay

Comments will be welcome.

Thanks,
Tal.






--_000_74470498B659FA4687F0B0018C19A89C01A0F951B840ILMB01marve_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Diso-8859-1"><meta name=3DGenerator content=3D"Micr=
osoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
h4
	{mso-style-priority:9;
	mso-style-link:"Heading 4 Char";
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-line-height-alt:0pt;
	font-size:12.0pt;
	font-family:"Courier New";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.Heading4Char
	{mso-style-name:"Heading 4 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 4";
	font-family:"Courier New";
	font-weight:bold;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle24
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1395347903;
	mso-list-type:hybrid;
	mso-list-template-ids:-864665048 67698699 67698691 67698693 67698689 67698=
691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0D8;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'c=
olor:#1F497D'>Hi Gagan,<o:p></o:p></span></p><p class=3DMsoNormal><span sty=
le=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span=
 style=3D'color:#1F497D'>Thanks for your comments.<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Please see my responses inl=
ine.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'color:#1F497D=
'><o:p>&nbsp;</o:p></span></p><div><p class=3DMsoNormal><span style=3D'font=
-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Tal.<o:p></o:p=
></span></p></div><p class=3DMsoNormal><span style=3D'color:#1F497D'><o:p>&=
nbsp;</o:p></span></p><div><div style=3D'border:none;border-top:solid #B5C4=
DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span style=3D'=
font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span s=
tyle=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Gagan Mohan Go=
el [mailto:Gagan_Goel@infosys.com] <br><b>Sent:</b> Tuesday, February 19, 2=
013 10:24 AM<br><b>To:</b> Tal Mizrahi<br><b>Cc:</b> tsenevir@cisco.com; Do=
nald Eastlake (d3e3e3@gmail.com); Samer Salam (ssalam) (ssalam@cisco.com); =
trill@ietf.org<br><b>Subject:</b> RE: New draft: draft-mizrahi-trill-loss-d=
elay-00<o:p></o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</=
o:p></p><p class=3DMsoNormal>Hi Tal,<o:p></o:p></p><p class=3DMsoNormal><o:=
p>&nbsp;</o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font=
-family:"Arial","sans-serif"'>Following are my views on the draft <a href=
=3D"http://tools.ietf.org/html/draft-mizrahi-trill-loss-delay">http://tools=
.ietf.org/html/draft-mizrahi-trill-loss-delay</a>.<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","sans=
-serif"'><o:p>&nbsp;</o:p></span></p><h4 style=3D'page-break-before:always'=
><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";font-weig=
ht:normal'>1) Section 4.2.3 </span><span lang=3DEN style=3D'font-size:10.0p=
t;font-family:"Arial","sans-serif";font-weight:normal'>SLR Message Receptio=
n<o:p></o:p></span></h4><pre style=3D'page-break-before:always'><span style=
=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>&lt;snip&gt; </span>=
<span lang=3DEN style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'=
>&nbsp;&nbsp;&nbsp;The receiver computes the one-way packet delay with resp=
ect to a measurement interval. A measurement interval includes a sequence o=
f<o:p></o:p></span></pre><p class=3DMsoNormal style=3D'page-break-before:al=
ways'><span lang=3DEN style=3D'font-size:10.0pt;font-family:"Arial","sans-s=
erif"'>&nbsp;&nbsp; 1SLM message. The one-way packet delay is performed by =
comparing the counter values TXp and RXp at the beginning of the measuremen=
t<o:p></o:p></span></p><p class=3DMsoNormal style=3D'page-break-before:alwa=
ys'><span lang=3DEN style=3D'font-size:10.0pt;font-family:"Arial","sans-ser=
if"'>&nbsp;&nbsp; interval, and the counter values TXc and RXc at the end o=
f the &nbsp;measurement interval (Figure 2): <o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","sans-seri=
f"'>&lt;snip&gt;<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span><=
/p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial"=
,"sans-serif"'>I understand that receiver can only calculate the one way pa=
cket loss (and not packet delay) with incoming SLM message. I think the abo=
ve can be modified to:<o:p></o:p></span></p><pre style=3D'page-break-before=
:always'><span lang=3DEN style=3D'font-size:10.0pt;font-family:"Arial","san=
s-serif"'>&nbsp; <o:p></o:p></span></pre><pre style=3D'page-break-before:al=
ways'><span lang=3DEN style=3D'font-size:10.0pt;font-family:"Arial","sans-s=
erif"'>&nbsp;The receiver computes the one-way packet <b><i>loss</i></b> wi=
th respect to a measurement interval. A measurement interval includes a seq=
uence of<o:p></o:p></span></pre><p class=3DMsoNormal style=3D'page-break-be=
fore:always'><span lang=3DEN style=3D'font-size:10.0pt;font-family:"Arial",=
"sans-serif"'>&nbsp;&nbsp; <b><i>SLM</i></b> message. The one-way packet <b=
><i>loss</i></b> is performed by comparing the counter values TXp and RXp a=
t the beginning of the measurement<o:p></o:p></span></p><p class=3DMsoNorma=
l style=3D'page-break-before:always'><span lang=3DEN style=3D'font-size:10.=
0pt;font-family:"Arial","sans-serif"'>&nbsp;&nbsp; interval, and the counte=
r values TXc and RXc at the end of the &nbsp;measurement interval (Figure 2=
): <o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0=
pt;font-family:"Arial","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span>=
</p><p class=3DMsoNormal><b><i><span style=3D'color:#1F497D'>[TM] Right. It=
 is indeed a typo.<o:p></o:p></span></i></b></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><h4 style=3D'page-break=
-before:always'><a name=3Dsection-4.1.2><span lang=3DEN style=3D'font-size:=
10.0pt;font-family:"Arial","sans-serif";font-weight:normal'>2) </span></a><=
a href=3D"http://tools.ietf.org/html/draft-mizrahi-trill-loss-delay-00#sect=
ion-4.1.2"><span lang=3DEN style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";color:windowtext;font-weight:normal;text-decoration:none'>4.1.2<=
/span></a><span lang=3DEN style=3D'font-size:10.0pt;font-family:"Arial","sa=
ns-serif";font-weight:normal'>. 1SLM Message Reception<o:p></o:p></span></h=
4><pre style=3D'page-break-before:always'><span lang=3DEN style=3D'font-siz=
e:10.0pt;font-family:"Arial","sans-serif"'>&lt;snip&gt; The receiver MUST m=
aintain a reception counter for each peer MEP and test ID. Upon receiving a=
 1SLM packet, the receiver MUST verify that:<o:p></o:p></span></pre><pre st=
yle=3D'page-break-before:always'><span lang=3DEN style=3D'font-size:10.0pt;=
font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></pre><pre style=
=3D'page-break-before:always'><span lang=3DEN style=3D'font-size:10.0pt;fon=
t-family:"Arial","sans-serif"'>&nbsp;&nbsp; o The 1SLM packet is destined t=
o the current MEP.<o:p></o:p></span></pre><pre style=3D'page-break-before:a=
lways'><span lang=3DEN style=3D'font-size:10.0pt;font-family:"Arial","sans-=
serif"'>&nbsp;&nbsp; o The packet's MD level matches the MEP's MD level.<o:=
p></o:p></span></pre><h4 style=3D'page-break-before:always'><span lang=3DEN=
 style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";font-weight:nor=
mal'>&lt;snip&gt;<o:p></o:p></span></h4><h4 style=3D'page-break-before:alwa=
ys'><span lang=3DEN style=3D'font-size:10.0pt;font-family:"Arial","sans-ser=
if";font-weight:normal'>May be another criteria that can be added to handle=
 any transient network loop scenario:<o:p></o:p></span></h4><h4 style=3D'ma=
rgin-left:.5in;text-indent:-.25in;page-break-before:always;mso-list:l0 leve=
l1 lfo2'><![if !supportLists]><span lang=3DEN style=3D'font-size:10.0pt;fon=
t-family:Wingdings;font-weight:normal'><span style=3D'mso-list:Ignore'>=D8<=
span style=3D'font:7.0pt "Times New Roman"'>&nbsp; </span></span></span><![=
endif]><span dir=3DLTR></span><span lang=3DEN style=3D'font-size:10.0pt;fon=
t-family:"Arial","sans-serif";font-weight:normal'>Discard the message if co=
unter received in the incoming 1SLM message is lower than current RX count =
for same testID.<o:p></o:p></span></h4><h4 style=3D'page-break-before:alway=
s'><i><span lang=3DEN style=3D'font-size:11.0pt;font-family:"Calibri","sans=
-serif";color:#1F497D'>[TM] Since packets can in some cases be received out=
-of-order, this filter may discard 1SLM packets that should be counted.</sp=
an></i><span lang=3DEN style=3D'font-size:11.0pt;font-family:"Calibri","san=
s-serif";color:#1F497D;font-weight:normal'><o:p></o:p></span></h4><h4 style=
=3D'page-break-before:always'><span lang=3DEN style=3D'font-size:10.0pt;fon=
t-family:"Arial","sans-serif";color:#1F497D;font-weight:normal'><o:p>&nbsp;=
</o:p></span></h4><h4 style=3D'page-break-before:always'><span lang=3DEN st=
yle=3D'font-size:10.0pt;font-family:"Arial","sans-serif";font-weight:normal=
'>Regards<o:p></o:p></span></h4><p class=3DMsoNormal><span lang=3DEN style=
=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Gagan Mohan Goel</sp=
an><o:p></o:p></p><p class=3DMsoNormal><span style=3D'color:#1F497D'><o:p>&=
nbsp;</o:p></span></p><div><div style=3D'border:none;border-top:solid #B5C4=
DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span style=3D'=
font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span s=
tyle=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> trill-bounces@=
ietf.org [mailto:trill-bounces@ietf.org] <b>On Behalf Of </b>Tal Mizrahi<br=
><b>Sent:</b> Monday, February 18, 2013 8:17 PM<br><b>To:</b> trill@ietf.or=
g<br><b>Cc:</b> tsenevir@cisco.com; Donald Eastlake (d3e3e3@gmail.com); Sam=
er Salam (ssalam) (ssalam@cisco.com)<br><b>Subject:</b> [trill] New draft: =
draft-mizrahi-trill-loss-delay-00<o:p></o:p></span></p></div></div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Hi,<o:p></o:p></p><p=
 class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>We have upload=
ed a new draft titled &#8220;Loss and Delay Measurement in TRILL&#8221;.<o:=
p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>=
<a href=3D"http://tools.ietf.org/html/draft-mizrahi-trill-loss-delay">http:=
//tools.ietf.org/html/draft-mizrahi-trill-loss-delay</a><o:p></o:p></p><p c=
lass=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Comments will be=
 welcome.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=
=3DMsoNormal>Thanks,<o:p></o:p></p><p class=3DMsoNormal><span style=3D'font=
-size:10.0pt;font-family:"Arial","sans-serif"'>Tal.<o:p></o:p></span></p><p=
 class=3DMsoNormal><o:p>&nbsp;</o:p></p><table class=3DMsoNormalTable borde=
r=3D0 cellpadding=3D0><tr><td style=3D'background:white;padding:.75pt .75pt=
 .75pt .75pt'><pre><span style=3D'color:black'><o:p>&nbsp;</o:p></span></pr=
e></td></tr></table><p class=3DMsoNormal><span style=3D'font-size:12.0pt;fo=
nt-family:"Times New Roman","serif"'><o:p>&nbsp;</o:p></span></p></div></bo=
dy></html>=

--_000_74470498B659FA4687F0B0018C19A89C01A0F951B840ILMB01marve_--

From Gagan_Goel@infosys.com  Tue Feb 19 02:15:05 2013
Return-Path: <Gagan_Goel@infosys.com>
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 6D02D21F89A3 for <trill@ietfa.amsl.com>; Tue, 19 Feb 2013 02:15:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 NkHhYcQZd7lF for <trill@ietfa.amsl.com>; Tue, 19 Feb 2013 02:15:02 -0800 (PST)
Received: from kecgate02.infosys.com (kecgate02.infosys.com [122.98.14.32]) by ietfa.amsl.com (Postfix) with ESMTP id 9AD4C21F897F for <trill@ietf.org>; Tue, 19 Feb 2013 02:15:00 -0800 (PST)
X-TM-IMSS-Message-ID: <398b1ede0005d1b4@infosys.com>
Received: from blrkechub03.ad.infosys.com ([10.66.236.43]) by infosys.com ([122.98.14.32]) with ESMTP (TREND IMSS SMTP Service 7.1) id 398b1ede0005d1b4 ; Tue, 19 Feb 2013 15:38:51 +0530
Received: from BLRKECHUB06.ad.infosys.com (10.66.236.116) by blrkechub03.ad.infosys.com (10.66.236.43) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 19 Feb 2013 15:44:37 +0530
Received: from BLRKECMBX23.ad.infosys.com ([fe80::d9f9:2028:fd8:1e35]) by BLRKECHUB06.ad.infosys.com ([::1]) with mapi id 14.02.0318.004; Tue, 19 Feb 2013 15:44:36 +0530
From: Gagan Mohan Goel <Gagan_Goel@infosys.com>
To: "Tal Mizrahi (talmi@marvell.com)" <talmi@marvell.com>
Thread-Topic: New draft: draft-mizrahi-trill-loss-delay-00
Thread-Index: Ac4N5mrEG1XxBAnYSvSlgxyFBe7MxwAkmsFgAAJ5bcAAAKqUgA==
Date: Tue, 19 Feb 2013 10:14:36 +0000
Message-ID: <06D3FFFAA621E5459625E5E757AE9A1B0B8D9748@BLRKECMBX23.ad.infosys.com>
References: <74470498B659FA4687F0B0018C19A89C01A0F951B684@IL-MB01.marvell.com> <06D3FFFAA621E5459625E5E757AE9A1B0B8D970A@BLRKECMBX23.ad.infosys.com> <74470498B659FA4687F0B0018C19A89C01A0F951B840@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01A0F951B840@IL-MB01.marvell.com>
Accept-Language: en-US, en-IN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.236.169]
Content-Type: multipart/alternative; boundary="_000_06D3FFFAA621E5459625E5E757AE9A1B0B8D9748BLRKECMBX23adin_"
MIME-Version: 1.0
Cc: "tsenevir@cisco.com" <tsenevir@cisco.com>, "Donald Eastlake \(d3e3e3@gmail.com\) \(d3e3e3@gmail.com\)" <d3e3e3@gmail.com>, "Samer Salam \(ssalam\) \(ssalam@cisco.com\) \(ssalam@cisco.com\)" <ssalam@cisco.com>, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] New draft: draft-mizrahi-trill-loss-delay-00
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: Tue, 19 Feb 2013 10:15:05 -0000

--_000_06D3FFFAA621E5459625E5E757AE9A1B0B8D9748BLRKECMBX23adin_
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Tal,

Thanks for the reply.

Please find my views inline.

Thanks,
Gagan Mohan Goel

From: Tal Mizrahi [mailto:talmi@marvell.com]
Sent: Tuesday, February 19, 2013 3:04 PM
To: Gagan Mohan Goel
Cc: tsenevir@cisco.com; Donald Eastlake (d3e3e3@gmail.com); Samer Salam (=
ssalam) (ssalam@cisco.com); trill@ietf.org
Subject: RE: New draft: draft-mizrahi-trill-loss-delay-00

Hi Gagan,

Thanks for your comments.
Please see my responses inline.

Tal.

From: Gagan Mohan Goel [mailto:Gagan_Goel@infosys.com]
Sent: Tuesday, February 19, 2013 10:24 AM
To: Tal Mizrahi
Cc: tsenevir@cisco.com<mailto:tsenevir@cisco.com>; Donald Eastlake (d3e3e=
3@gmail.com<mailto:d3e3e3@gmail.com>); Samer Salam (ssalam) (ssalam@cisco=
.com<mailto:ssalam@cisco.com>); trill@ietf.org<mailto:trill@ietf.org>
Subject: RE: New draft: draft-mizrahi-trill-loss-delay-00

Hi Tal,

Following are my views on the draft http://tools.ietf.org/html/draft-mizr=
ahi-trill-loss-delay.

1) Section 4.2.3 SLR Message Reception

<snip>    The receiver computes the one-way packet delay with respect to =
a measurement interval. A measurement interval includes a sequence of
   1SLM message. The one-way packet delay is performed by comparing the c=
ounter values TXp and RXp at the beginning of the measurement
   interval, and the counter values TXc and RXc at the end of the  measur=
ement interval (Figure 2):
<snip>

I understand that receiver can only calculate the one way packet loss (an=
d not packet delay) with incoming SLM message. I think the above can be m=
odified to:



 The receiver computes the one-way packet loss with respect to a measurem=
ent interval. A measurement interval includes a sequence of
   SLM message. The one-way packet loss is performed by comparing the cou=
nter values TXp and RXp at the beginning of the measurement
   interval, and the counter values TXc and RXc at the end of the  measur=
ement interval (Figure 2):

[TM] Right. It is indeed a typo.

2) 4.1.2<http://tools.ietf.org/html/draft-mizrahi-trill-loss-delay-00#sec=
tion-4.1.2>. 1SLM Message Reception

<snip> The receiver MUST maintain a reception counter for each peer MEP a=
nd test ID. Upon receiving a 1SLM packet, the receiver MUST verify that:



   o The 1SLM packet is destined to the current MEP.

   o The packet's MD level matches the MEP's MD level.

<snip>
May be another criteria that can be added to handle any transient network=
 loop scenario:
=D8  Discard the message if counter received in the incoming 1SLM message=
 is lower than current RX count for same testID.
[TM] Since packets can in some cases be received out-of-order, this filte=
r may discard 1SLM packets that should be counted.
[Gagan] I agree. Thanks for clarification. I was considering scenario whe=
re due to transient network loop, 1SLM packet (with same testID) is recei=
ved more than once on the receiver. Receiver may also include the criteri=
a to filter such duplicate packets.
Regards
Gagan Mohan Goel

From: trill-bounces@ietf.org<mailto:trill-bounces@ietf.org> [mailto:trill=
-bounces@ietf.org] On Behalf Of Tal Mizrahi
Sent: Monday, February 18, 2013 8:17 PM
To: trill@ietf.org<mailto:trill@ietf.org>
Cc: tsenevir@cisco.com<mailto:tsenevir@cisco.com>; Donald Eastlake (d3e3e=
3@gmail.com<mailto:d3e3e3@gmail.com>); Samer Salam (ssalam) (ssalam@cisco=
.com<mailto:ssalam@cisco.com>)
Subject: [trill] New draft: draft-mizrahi-trill-loss-delay-00

Hi,

We have uploaded a new draft titled "Loss and Delay Measurement in TRILL"=
.

http://tools.ietf.org/html/draft-mizrahi-trill-loss-delay

Comments will be welcome.

Thanks,
Tal.






**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended sol=
ely 
for the use of the addressee(s). If you are not the intended recipient, p=
lease 
notify the sender by e-mail and delete the original message. Further, you=
 are not 
to copy, disclose, or distribute this e-mail or its contents to any other=
 person and 
any such actions are unlawful. This e-mail may contain viruses. Infosys h=
as taken 
every reasonable precaution to minimize this risk, but is not liable for =
any damage 
you may sustain as a result of any virus in this e-mail. You should carry=
 out your 
own virus checks before opening the e-mail or attachment. Infosys reserve=
s the 
right to monitor and review the content of all messages sent to or from t=
his e-mail 
address. Messages sent to or from this e-mail address may be stored on th=
e 
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***

--_000_06D3FFFAA621E5459625E5E757AE9A1B0B8D9748BLRKECMBX23adin_
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-mi=
crosoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:wo=
rd" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D=
"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-885=
9-1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
=09{font-family:Wingdings;
=09panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
=09{font-family:Wingdings;
=09panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
=09{font-family:Calibri;
=09panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
=09{font-family:Tahoma;
=09panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
=09{margin:0in;
=09margin-bottom:.0001pt;
=09font-size:11.0pt;
=09font-family:"Calibri","sans-serif";}
h4
=09{mso-style-priority:9;
=09mso-style-link:"Heading 4 Char";
=09mso-margin-top-alt:auto;
=09margin-right:0in;
=09mso-margin-bottom-alt:auto;
=09margin-left:0in;
=09mso-line-height-alt:0pt;
=09font-size:12.0pt;
=09font-family:"Courier New";}
a:link, span.MsoHyperlink
=09{mso-style-priority:99;
=09color:blue;
=09text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
=09{mso-style-priority:99;
=09color:purple;
=09text-decoration:underline;}
pre
=09{mso-style-priority:99;
=09mso-style-link:"HTML Preformatted Char";
=09margin:0in;
=09margin-bottom:.0001pt;
=09font-size:12.0pt;
=09font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
=09{mso-style-priority:99;
=09mso-style-link:"Balloon Text Char";
=09margin:0in;
=09margin-bottom:.0001pt;
=09font-size:8.0pt;
=09font-family:"Tahoma","sans-serif";}
span.Heading4Char
=09{mso-style-name:"Heading 4 Char";
=09mso-style-priority:9;
=09mso-style-link:"Heading 4";
=09font-family:"Courier New";
=09font-weight:bold;}
span.HTMLPreformattedChar
=09{mso-style-name:"HTML Preformatted Char";
=09mso-style-priority:99;
=09mso-style-link:"HTML Preformatted";
=09font-family:"Courier New";}
span.BalloonTextChar
=09{mso-style-name:"Balloon Text Char";
=09mso-style-priority:99;
=09mso-style-link:"Balloon Text";
=09font-family:"Tahoma","sans-serif";}
span.EmailStyle22
=09{mso-style-type:personal;
=09font-family:"Calibri","sans-serif";
=09color:windowtext;}
span.EmailStyle23
=09{mso-style-type:personal;
=09font-family:"Calibri","sans-serif";
=09color:#1F497D;}
span.EmailStyle24
=09{mso-style-type:personal;
=09font-family:"Calibri","sans-serif";
=09color:#1F497D;}
span.EmailStyle25
=09{mso-style-type:personal-reply;
=09font-family:"Calibri","sans-serif";
=09color:#1F497D;}
.MsoChpDefault
=09{mso-style-type:export-only;
=09font-size:10.0pt;}
@page WordSection1
=09{size:8.5in 11.0in;
=09margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
=09{page:WordSection1;}
/* List Definitions */
@list l0
=09{mso-list-id:1395347903;
=09mso-list-type:hybrid;
=09mso-list-template-ids:-864665048 67698699 67698691 67698693 67698689 6=
7698691 67698693 67698689 67698691 67698693;}
@list l0:level1
=09{mso-level-number-format:bullet;
=09mso-level-text:\F0D8;
=09mso-level-tab-stop:none;
=09mso-level-number-position:left;
=09text-indent:-.25in;
=09font-family:Wingdings;}
@list l0:level2
=09{mso-level-number-format:bullet;
=09mso-level-text:o;
=09mso-level-tab-stop:none;
=09mso-level-number-position:left;
=09text-indent:-.25in;
=09font-family:"Courier New";}
@list l0:level3
=09{mso-level-number-format:bullet;
=09mso-level-text:\F0A7;
=09mso-level-tab-stop:none;
=09mso-level-number-position:left;
=09text-indent:-.25in;
=09font-family:Wingdings;}
@list l0:level4
=09{mso-level-number-format:bullet;
=09mso-level-text:\F0B7;
=09mso-level-tab-stop:none;
=09mso-level-number-position:left;
=09text-indent:-.25in;
=09font-family:Symbol;}
@list l0:level5
=09{mso-level-number-format:bullet;
=09mso-level-text:o;
=09mso-level-tab-stop:none;
=09mso-level-number-position:left;
=09text-indent:-.25in;
=09font-family:"Courier New";}
@list l0:level6
=09{mso-level-number-format:bullet;
=09mso-level-text:\F0A7;
=09mso-level-tab-stop:none;
=09mso-level-number-position:left;
=09text-indent:-.25in;
=09font-family:Wingdings;}
@list l0:level7
=09{mso-level-number-format:bullet;
=09mso-level-text:\F0B7;
=09mso-level-tab-stop:none;
=09mso-level-number-position:left;
=09text-indent:-.25in;
=09font-family:Symbol;}
@list l0:level8
=09{mso-level-number-format:bullet;
=09mso-level-text:o;
=09mso-level-tab-stop:none;
=09mso-level-number-position:left;
=09text-indent:-.25in;
=09font-family:"Courier New";}
@list l0:level9
=09{mso-level-number-format:bullet;
=09mso-level-text:\F0A7;
=09mso-level-tab-stop:none;
=09mso-level-number-position:left;
=09text-indent:-.25in;
=09font-family:Wingdings;}
ol
=09{margin-bottom:0in;}
ul
=09{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;=
Arial&quot;,&quot;sans-serif&quot;">Hi Tal,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;=
Arial&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;=
Arial&quot;,&quot;sans-serif&quot;">Thanks for the reply.<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;=
Arial&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;=
Arial&quot;,&quot;sans-serif&quot;">Please find my views inline.<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;=
Arial&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;=
Arial&quot;,&quot;sans-serif&quot;">Thanks,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;=
Arial&quot;,&quot;sans-serif&quot;">Gagan Mohan Goel<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></s=
pan></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0i=
n 0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&qu=
ot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"fo=
nt-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Ta=
l Mizrahi [mailto:talmi@marvell.com]
<br>
<b>Sent:</b> Tuesday, February 19, 2013 3:04 PM<br>
<b>To:</b> Gagan Mohan Goel<br>
<b>Cc:</b> tsenevir@cisco.com; Donald Eastlake (d3e3e3@gmail.com); Samer =
Salam (ssalam) (ssalam@cisco.com); trill@ietf.org<br>
<b>Subject:</b> RE: New draft: draft-mizrahi-trill-loss-delay-00<o:p></o:=
p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Gagan,<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks for your comm=
ents.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Please see my respon=
ses inline.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></s=
pan></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;=
Arial&quot;,&quot;sans-serif&quot;;color:#1F497D">Tal.<o:p></o:p></span><=
/p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></s=
pan></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0i=
n 0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&qu=
ot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"fo=
nt-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Ga=
gan Mohan Goel [<a href=3D"mailto:Gagan_Goel@infosys.com">mailto:Gagan_Go=
el@infosys.com</a>]
<br>
<b>Sent:</b> Tuesday, February 19, 2013 10:24 AM<br>
<b>To:</b> Tal Mizrahi<br>
<b>Cc:</b> <a href=3D"mailto:tsenevir@cisco.com">tsenevir@cisco.com</a>; =
Donald Eastlake (<a href=3D"mailto:d3e3e3@gmail.com">d3e3e3@gmail.com</a>=
); Samer Salam (ssalam) (<a href=3D"mailto:ssalam@cisco.com">ssalam@cisco=
.com</a>);
<a href=3D"mailto:trill@ietf.org">trill@ietf.org</a><br>
<b>Subject:</b> RE: New draft: draft-mizrahi-trill-loss-delay-00<o:p></o:=
p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi Tal,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;=
Arial&quot;,&quot;sans-serif&quot;">Following are my views on the draft
<a href=3D"http://tools.ietf.org/html/draft-mizrahi-trill-loss-delay">htt=
p://tools.ietf.org/html/draft-mizrahi-trill-loss-delay</a>.<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;=
Arial&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<h4 style=3D"page-break-before:always"><span style=3D"font-size:10.0pt;fo=
nt-family:&quot;Arial&quot;,&quot;sans-serif&quot;;font-weight:normal">1)=
 Section 4.2.3
</span><span lang=3D"EN" style=3D"font-size:10.0pt;font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;;font-weight:normal">SLR Message Reception<=
o:p></o:p></span></h4>
<pre style=3D"page-break-before:always"><span style=3D"font-size:10.0pt;f=
ont-family:&quot;Arial&quot;,&quot;sans-serif&quot;">&lt;snip&gt; </span>=
<span lang=3D"EN" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;=
,&quot;sans-serif&quot;">&nbsp;&nbsp;&nbsp;The receiver computes the one-=
way packet delay with respect to a measurement interval. A measurement in=
terval includes a sequence of<o:p></o:p></span></pre>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"E=
N" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-ser=
if&quot;">&nbsp;&nbsp; 1SLM message. The one-way packet delay is performe=
d by comparing the counter values TXp and RXp at the beginning of the mea=
surement<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"E=
N" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-ser=
if&quot;">&nbsp;&nbsp; interval, and the counter values TXc and RXc at th=
e end of the &nbsp;measurement interval (Figure 2):
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;=
Arial&quot;,&quot;sans-serif&quot;">&lt;snip&gt;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;=
Arial&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;=
Arial&quot;,&quot;sans-serif&quot;">I understand that receiver can only c=
alculate the one way packet loss (and not packet delay) with incoming SLM=
 message. I think the above can be modified to:<o:p></o:p></span></p>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-s=
ize:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">&nbsp; <=
o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-s=
ize:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">&nbsp;Th=
e receiver computes the one-way packet <b><i>loss</i></b> with respect to=
 a measurement interval. A measurement interval includes a sequence of<o:=
p></o:p></span></pre>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"E=
N" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-ser=
if&quot;">&nbsp;&nbsp;
<b><i>SLM</i></b> message. The one-way packet <b><i>loss</i></b> is perfo=
rmed by comparing the counter values TXp and RXp at the beginning of the =
measurement<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"E=
N" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-ser=
if&quot;">&nbsp;&nbsp; interval, and the counter values TXc and RXc at th=
e end of the &nbsp;measurement interval (Figure 2):
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;=
Arial&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span=
></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">[TM] Right. It=
 is indeed a typo.<o:p></o:p></span></i></b></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></s=
pan></p>
<h4 style=3D"page-break-before:always"><a name=3D"section-4.1.2"><span la=
ng=3D"EN" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;;font-weight:normal">2)
</span></a><a href=3D"http://tools.ietf.org/html/draft-mizrahi-trill-loss=
-delay-00#section-4.1.2"><span lang=3D"EN" style=3D"font-size:10.0pt;font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:windowtext;font-we=
ight:normal;text-decoration:none">4.1.2</span></a><span lang=3D"EN" style=
=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;=
;font-weight:normal">.
 1SLM Message Reception<o:p></o:p></span></h4>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-s=
ize:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">&lt;snip=
&gt; The receiver MUST maintain a reception counter for each peer MEP and=
 test ID. Upon receiving a 1SLM packet, the receiver MUST verify that:<o:=
p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-s=
ize:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;"><o:p>&nb=
sp;</o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-s=
ize:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">&nbsp;&n=
bsp; o The 1SLM packet is destined to the current MEP.<o:p></o:p></span><=
/pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-s=
ize:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">&nbsp;&n=
bsp; o The packet's MD level matches the MEP's MD level.<o:p></o:p></span=
></pre>
<h4 style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;font-weigh=
t:normal">&lt;snip&gt;<o:p></o:p></span></h4>
<h4 style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;font-weigh=
t:normal">May be another criteria that can be added to handle any transie=
nt network loop scenario:<o:p></o:p></span></h4>
<h4 style=3D"margin-left:.5in;text-indent:-.25in;page-break-before:always=
;mso-list:l0 level1 lfo2">
<![if !supportLists]><span lang=3D"EN" style=3D"font-size:10.0pt;font-fam=
ily:Wingdings;font-weight:normal"><span style=3D"mso-list:Ignore">=D8<spa=
n style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;
</span></span></span><![endif]><span lang=3D"EN" style=3D"font-size:10.0p=
t;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;font-weight:normal=
">Discard the message if counter received in the incoming 1SLM message is=
 lower than current RX count for same testID.<o:p></o:p></span></h4>
<h4 style=3D"page-break-before:always"><i><span lang=3D"EN" style=3D"font=
-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color=
:#1F497D">[TM] Since packets can in some cases be received out-of-order, =
this filter may discard 1SLM packets that should be counted.</span></i><s=
pan lang=3D"EN" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:#1F497D;font-weight:normal"><o:p></o:p></sp=
an></h4>
<h4 style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;font-weigh=
t:normal">[Gagan] I agree. Thanks for clarification. I was considering sc=
enario where due to transient network loop, 1SLM packet (with same
 testID) is received more than once on the receiver. Receiver may also in=
clude the criteria to filter such duplicate packets.<o:p></o:p></span></h=
4>
<h4 style=3D"page-break-before:always"><span lang=3D"EN" style=3D"font-si=
ze:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;font-weigh=
t:normal">Regards<o:p></o:p></span></h4>
<p class=3D"MsoNormal"><span lang=3D"EN" style=3D"font-size:10.0pt;font-f=
amily:&quot;Arial&quot;,&quot;sans-serif&quot;">Gagan Mohan Goel</span><o=
:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></s=
pan></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0i=
n 0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&qu=
ot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"fo=
nt-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:trill-bounces@ietf.org">trill-bounces@ietf.org</a> [<a =
href=3D"mailto:trill-bounces@ietf.org">mailto:trill-bounces@ietf.org</a>]
<b>On Behalf Of </b>Tal Mizrahi<br>
<b>Sent:</b> Monday, February 18, 2013 8:17 PM<br>
<b>To:</b> <a href=3D"mailto:trill@ietf.org">trill@ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:tsenevir@cisco.com">tsenevir@cisco.com</a>; =
Donald Eastlake (<a href=3D"mailto:d3e3e3@gmail.com">d3e3e3@gmail.com</a>=
); Samer Salam (ssalam) (<a href=3D"mailto:ssalam@cisco.com">ssalam@cisco=
.com</a>)<br>
<b>Subject:</b> [trill] New draft: draft-mizrahi-trill-loss-delay-00<o:p>=
</o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We have uploaded a new draft titled &#8220;Loss an=
d Delay Measurement in TRILL&#8221;.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><a href=3D"http://tools.ietf.org/html/draft-mizrah=
i-trill-loss-delay">http://tools.ietf.org/html/draft-mizrahi-trill-loss-d=
elay</a><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Comments will be welcome.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;=
Arial&quot;,&quot;sans-serif&quot;">Tal.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<table class=3D"MsoNormalTable" border=3D"0" cellpadding=3D"0">
<tbody>
<tr>
<td style=3D"background:white;padding:.75pt .75pt .75pt .75pt">
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
</td>
</tr>
</tbody>
</table>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;=
Times New Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

<table><tr><td bgcolor=3D#ffffff><font color=3D#000000><pre>*************=
*** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended sol=
ely 
for the use of the addressee(s). If you are not the intended recipient, p=
lease 
notify the sender by e-mail and delete the original message. Further, you=
 are not 
to copy, disclose, or distribute this e-mail or its contents to any other=
 person and 
any such actions are unlawful. This e-mail may contain viruses. Infosys h=
as taken 
every reasonable precaution to minimize this risk, but is not liable for =
any damage 
you may sustain as a result of any virus in this e-mail. You should carry=
 out your 
own virus checks before opening the e-mail or attachment. Infosys reserve=
s the 
right to monitor and review the content of all messages sent to or from t=
his e-mail 
address. Messages sent to or from this e-mail address may be stored on th=
e 
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***</pre></font></td>=
</tr></table>

--_000_06D3FFFAA621E5459625E5E757AE9A1B0B8D9748BLRKECMBX23adin_--

From internet-drafts@ietf.org  Tue Feb 19 11:53:56 2013
Return-Path: <internet-drafts@ietf.org>
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 C5C9521F8E38; Tue, 19 Feb 2013 11:53:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.554
X-Spam-Level: 
X-Spam-Status: No, score=-102.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 SGwOnTPDSWmv; Tue, 19 Feb 2013 11:53:56 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E63021F8E3D; Tue, 19 Feb 2013 11:53:56 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.40
Message-ID: <20130219195356.15497.56084.idtracker@ietfa.amsl.com>
Date: Tue, 19 Feb 2013 11:53:56 -0800
Cc: trill@ietf.org
Subject: [trill] I-D Action: draft-ietf-trill-oam-framework-01.txt
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: Tue, 19 Feb 2013 19:53:56 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Transparent Interconnection of Lots of Li=
nks Working Group of the IETF.

	Title           : TRILL OAM Framework
	Author(s)       : Samer Salam
                          Tissa Senevirathne
                          Sam Aldrin
                          Donald Eastlake
	Filename        : draft-ietf-trill-oam-framework-01.txt
	Pages           : 25
	Date            : 2013-02-19

Abstract:
   This document specifies a reference framework for Operations,
   Administration and Maintenance (OAM) in TRILL networks. The focus of
   the document is on the fault and performance management aspects of
   TRILL OAM.



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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-trill-oam-framework-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-trill-oam-framework-01


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


From howardy@cisco.com  Tue Feb 19 12:24:22 2013
Return-Path: <howardy@cisco.com>
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 A6CB421F8ABA for <trill@ietfa.amsl.com>; Tue, 19 Feb 2013 12:24:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.998
X-Spam-Level: 
X-Spam-Status: No, score=-9.998 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599, J_CHICKENPOX_54=0.6, RCVD_IN_DNSWL_HI=-8]
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 qQvhLnj9KPqK for <trill@ietfa.amsl.com>; Tue, 19 Feb 2013 12:24:21 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 93C5521F868B for <trill@ietf.org>; Tue, 19 Feb 2013 12:24:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5950; q=dns/txt; s=iport; t=1361305461; x=1362515061; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=Bx44c4n/AHoeCiK3cOjxCZbtFwr0ytpv/ubt/Ya1nzE=; b=dplp0Ifp035ZaqvdIoxSTrKHH/F9S55ECgyxZGUIdCQlr8k0Oeqz1+aM WrJPwPKRG+FhmCMI6UnjiPXDOOoUiCAt2PDyFnLhKsvdxqyUdLvc2sPL3 zSp/PkpMQBj2M65S7B82pMequ6S04vk7aEgMTz2lmvU+bJeQ7B65/UnQY A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFANDeI1GtJXHB/2dsb2JhbABCA8A7gQ0Wc4IfAQEBBDo/EgEIDgoKFDERJQIEAQ0FCId4Aw+wQoZCDYlajDeCJAIhEAcRgk5hA5RQjR6FFYMHgic
X-IronPort-AV: E=Sophos;i="4.84,697,1355097600"; d="scan'208";a="178870025"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-8.cisco.com with ESMTP; 19 Feb 2013 20:24:21 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r1JKOKXQ002379 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 19 Feb 2013 20:24:20 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.213]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.02.0318.004; Tue, 19 Feb 2013 14:24:20 -0600
From: "Howard Yang (howardy)" <howardy@cisco.com>
To: Donald Eastlake <d3e3e3@gmail.com>, "draft-ietf-trill-rbridge-bfd@tools.ietf.org" <draft-ietf-trill-rbridge-bfd@tools.ietf.org>
Thread-Topic: [trill] Comments on TRILL BFD draft and TRILL use of ISIS draft
Thread-Index: AQHOCZybTO2m0M8pekyW1cpAvkGbmZiBiXEA
Date: Tue, 19 Feb 2013 20:24:20 +0000
Message-ID: <8F62EB044F07504DB195F82B824F34DD257551@xmb-aln-x15.cisco.com>
In-Reply-To: <CAF4+nEGXb5_s0LOz+Zh8KBNTOGBBvX5ntHVo_02xrM-vaT==Sw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.1.120420
x-originating-ip: [128.107.157.236]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <BBA6B300630DF34185571FB2C85F1A34@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] Comments on TRILL BFD draft and TRILL use of ISIS draft
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: Tue, 19 Feb 2013 20:24:22 -0000

Hi Donald,

I have more questions about the TRILL BFD.

Suppose 3 Rbridges are to be connected on the LAN, and all 3 RBs (A, B and
C) are having the same nickname before they are to be connected (So it's a
3-node nickname collision case, which is not likely to happen in the real
world, but just to demonstrate the points.)

Since TRILL BFD Control frames are TRILL Rbridge Channel frames, we need
both local and peer's nicknames, which happens to be the same in this case.

Therefore, if A receives a TRILL BFD packet, it cannot tell if the packet
is from B or C. This would prevent an RB from establish any TRILL BFD
sessions.

Notice we support RFC6213 (ISIS BFD enabled TLV), which requires to have
BFD session to be in UP state before bringing up ISIS adjacency, and
notice the nickname collision resolution is done after exchange of LSPs.
And notice we need to bring up ISIS adjacency first before LSP can be
exchanged. Therefore, we are stuck.

To solve this problem, I am suggesting to modify the TRILL BFD
encapsulation by adding the source system_ID and destination system_ID.

So the packet could look like the following:

             =20
      +--------------------------------+
      |          Link Header           |
      +--------------------------------+
      |          TRILL Header          |
      +--------------------------------+
      |     Inner Ethernet Header      |
      +--------------------------------+
      |     RBridge Channel Header     |
      +--------------------------------+
      | dest system_id | src system_id |
+--------------------------------+
| Protocol Specific Payload (BFD) |
+--------------------------------+

      | Link Trailer (FCS if Ethernet) |
      +--------------------------------+



Thanks,
-Howard




On 2/12/13 7:45 PM, "Donald Eastlake" <d3e3e3@gmail.com> wrote:

>Hi Howard,
>
>On Tue, Feb 12, 2013 at 2:47 PM, Howard Yang (howardy)
><howardy@cisco.com> wrote:
>> Hi,
>>
>> I have a couple of comments on TRILL BFD draft
>> <draft-ietf-trill-rbridge-bfd-07.txt> and TRILL use of ISIS draft
>> <draft-ietf-isis-rfc6326bis-00.txt>.
>>
>> (1) To support TRILL BFD, it is required to include nickname TLV or
>>sub-TLV
>> in the ISIS hello packets.
>
>Every TRILL IS-IS Hello PDU is required to include a Special VLANs and
>Flags Sub-TLV which includes the Sender Nickname. Perhaps the
>explanatory text for that the Sub-TLV should be expanded to mention
>BFD bootstrap.
>
>> The reason is that when the neighbor receives the BFD packets, if the
>> nickname of the peer is not known, BFD cannot associate such BFD packets
>> with the BFD session.
>>
>> By the way, let's look at, in specific, the "One-Hop TRILL BFD Control"
>> here. Looking at Layer 3 (IP or IPv6) BFD, we have IP address TLV
>>included
>> in the ISIS hellos, so that when BFD session is created by ISIS, ISIS
>>can
>> pass both local and peer's IP addresses to BFD for BFD to associate a
>>BFD
>> packet to a session. Corresponding to IP address, in TRILL, we have the
>> nickname. When a BFD session is created with an unknown nickname for the
>> peer, and when a BFD packet from this peer is received, BFD has no way
>>to
>> associate this BFD packet with the BFD session previously created.
>>Notice
>> BFD packets are defined to have the TRILL channel encapsulation
>> (draft-ietf-trill-rbridge-channel-08.txt).
>>
>> So we need to add the requirement of including the local nickname in
>>ISIS
>> hellos, in addition to the "ISIS BFD enabled TLV" (RFC 6213).
>
>As above, Sender Nickname is already included in every TRILL IS-IS Hello.
>
>> The nickname is currently defined as nickname sub-tlv
>> (<draft-ietf-isis-rfc6326bis-00.txt>) and it is defined only in Router
>>or MT
>> Capability TLV. We need to extend it and allow the nickname sub-tlv to
>>be in
>> the Multi-Topology-Aware Port Capability TLV.
>
>As above, I do not believe that is necessary.
>
>> (2) In Section 3.1 of the TRILL BFD draft, we have
>>
>> 3.1 One-Hop TRILL BFD Control
>>
>>    One-hop TRILL BFD Control is typically used to rapidly detect link
>>    and RBridge failures.  TRILL BFD frames over one hop for such
>>    purposes SHOULD be sent with high priority; that is, the Inner.VLAN
>>    tag priority should be 7, they should be queued for transmission as
>>    maximum priority frames and, if they are being sent on an Ethernet
>>    link where the output port is configured to include an Outer.VLAN
>>    tag, that tag should specify priority 7.
>>
>>    For neighbor RBridges RB1 and RB2, each RBridge sends one-hop TRILL
>>    BFD Control frames to the other only if TRILL IS-IS has detected bi-
>>    directional connectivity, that is, the adjacency is in the Two-Way or
>>    Report state [RFC6327] and both RBridges indicate support of TRILL
>>    BFD is enabled.  The BFD Enabled TLV is used to indicate this as
>>    specified in [RFC6213].
>>
>> The "Two-Way" or "Report" is specific to TRILL LAN interface. It does
>>not
>> apply to the point-to-point interface. So, it should be modified to:
>>
>> "that is, the adjacency is in the Two-Way or Report state [RFC6327] on
>>the
>> LAN or INIT on the point-to-point when neighbor is known and both
>>Rbridges
>> indicate support of TRILL BFD is enabled."
>
>Work has started on an rfc6327bis draft to extend the proper TRILL
>adjacency state machine to point-to-point links and also include MTU
>testing on such links, to make them consistent with broadcast links. I
>believe that this is the best course. Would you be interested in
>helping with rfc6327bis?
>
>Thanks,
>Donald
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
> Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
> 155 Beaver Street, Milford, MA 01757 USA
> d3e3e3@gmail.com
>
>> Thanks,
>> -Howard Yang


From ssalam@cisco.com  Tue Feb 19 12:32:32 2013
Return-Path: <ssalam@cisco.com>
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 B0FC121F8B90 for <trill@ietfa.amsl.com>; Tue, 19 Feb 2013 12:32:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 kypdmGGDmwpK for <trill@ietfa.amsl.com>; Tue, 19 Feb 2013 12:32:32 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 7475621F8BE8 for <trill@ietf.org>; Tue, 19 Feb 2013 12:32:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1748; q=dns/txt; s=iport; t=1361305951; x=1362515551; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=cQLyhhisdXgXWT45YjT8mOOURGGCcVjwhZmMOq4E8kk=; b=Nl/Glinpg5mno/Rl2tW3NaAkNhFQqDqJFiw1W9c+eUJ036emBfobB+Tp gQ9tYgZfJ85GEbY9CEsy+1cJqodqr/tw59jT3FQVrCoPBV3lmLr0j2++D o2WSweArakdOck+Yrr6uva5o8ELOfhZAOlkdHpcA6G41MLha6FeM8wFMJ 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhAFAPfgI1GtJV2a/2dsb2JhbABEgmaBDrxHgQ0Wc4IhAQQBAQE3NAsSAQgiFDcLJQIEDgUIAYgJAQYFsCKQJ409gSAxB4JfYQOXSI87gweBcjU
X-IronPort-AV: E=Sophos;i="4.84,697,1355097600"; d="scan'208";a="178867635"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-5.cisco.com with ESMTP; 19 Feb 2013 20:32:31 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r1JKWUMw006240 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 19 Feb 2013 20:32:31 GMT
Received: from xmb-aln-x13.cisco.com ([fe80::5404:b599:9f57:834b]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.02.0318.004; Tue, 19 Feb 2013 14:32:30 -0600
From: "Samer Salam (ssalam)" <ssalam@cisco.com>
To: "trill@ietf.org" <trill@ietf.org>
Thread-Topic: [trill] I-D Action: draft-ietf-trill-oam-framework-01.txt
Thread-Index: AQHODtrzNOmaSORtXU6yozu6NZbSzZiBgTeA
Date: Tue, 19 Feb 2013 20:32:30 +0000
Message-ID: <8F25FF8EA49D164EBE5F1B5AD33F3BC91235BBF3@xmb-aln-x13.cisco.com>
In-Reply-To: <20130219195356.15497.56084.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [161.44.210.189]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <5F47A5E3EF4D294DA7AA4E9A221B0348@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Tissa Senevirathne \(tsenevir\)" <tsenevir@cisco.com>, Donald Eastlake <d3e3e3@gmail.com>, Sam Aldrin <sam.aldrin@gmail.com>
Subject: Re: [trill] I-D Action: draft-ietf-trill-oam-framework-01.txt
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: Tue, 19 Feb 2013 20:32:32 -0000

Hi,

This updated version of the OAM Framework draft primarily fixes Figure 2
(per an earlier email that Donald had sent to the workgroup) and updates
the supporting text which describes the OAM Layer and Maintenance Point
placement.

Comments are appreciated.

Regards,
Samer

On 13-02-19 11:53 AM, "internet-drafts@ietf.org"
<internet-drafts@ietf.org> wrote:

>
>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 Working Group of the IETF.
>
>	Title           : TRILL OAM Framework
>	Author(s)       : Samer Salam
>                          Tissa Senevirathne
>                          Sam Aldrin
>                          Donald Eastlake
>	Filename        : draft-ietf-trill-oam-framework-01.txt
>	Pages           : 25
>	Date            : 2013-02-19
>
>Abstract:
>   This document specifies a reference framework for Operations,
>   Administration and Maintenance (OAM) in TRILL networks. The focus of
>   the document is on the fault and performance management aspects of
>   TRILL OAM.
>
>
>
>The IETF datatracker status page for this draft is:
>https://datatracker.ietf.org/doc/draft-ietf-trill-oam-framework
>
>There's also a htmlized version available at:
>http://tools.ietf.org/html/draft-ietf-trill-oam-framework-01
>
>A diff from the previous version is available at:
>http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-trill-oam-framework-01
>
>
>Internet-Drafts are also available by anonymous FTP at:
>ftp://ftp.ietf.org/internet-drafts/
>
>_______________________________________________
>trill mailing list
>trill@ietf.org
>https://www.ietf.org/mailman/listinfo/trill


From d3e3e3@gmail.com  Tue Feb 19 13:15:09 2013
Return-Path: <d3e3e3@gmail.com>
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 A046621F87ED for <trill@ietfa.amsl.com>; Tue, 19 Feb 2013 13:15:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.183
X-Spam-Level: 
X-Spam-Status: No, score=-103.183 tagged_above=-999 required=5 tests=[AWL=-0.184, BAYES_00=-2.599, J_CHICKENPOX_54=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 yvGi+MjEowTX for <trill@ietfa.amsl.com>; Tue, 19 Feb 2013 13:15:08 -0800 (PST)
Received: from mail-ob0-f169.google.com (mail-ob0-f169.google.com [209.85.214.169]) by ietfa.amsl.com (Postfix) with ESMTP id 9DA0921F87E0 for <trill@ietf.org>; Tue, 19 Feb 2013 13:15:08 -0800 (PST)
Received: by mail-ob0-f169.google.com with SMTP id ta14so7154633obb.0 for <trill@ietf.org>; Tue, 19 Feb 2013 13:15:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=f4/XpPKLwEEBF9yczXtsRHaUoH9GetljV0tBaUR9pPo=; b=vD73AuBTn7Ym7mx0HaqwI+4NfLm7wW6onEzZ5xqqTuCbovlKR8ePQSdyyAdXQmpNGa WbHa+9U1OshuyEziwT5bOabMn12h+e0gqdRgsGF5aXg0+rDLGcIW8DwUJ9EMcFeKyq7M 14wiCESUTbipTxgN49PHJpzMk0P1b8nkuBWMWkT2BEz685v6nTsvEr9AUYXpQsMmyEom dY6DlIlPkt8gEwmSf6h1w8sA3eQtm3Zy1EMfhqi9ABvO0BRO5uWCG2q4Qpb6DB7kLQ2U 3w9+OHeq929yKMvEgu973jQ8yigdH/dswnA+KUPQTLYfNS3y/G5nhTeZAQGnExAMnr4i X0EA==
X-Received: by 10.182.123.49 with SMTP id lx17mr8218196obb.63.1361308508228; Tue, 19 Feb 2013 13:15:08 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.98.168 with HTTP; Tue, 19 Feb 2013 13:14:48 -0800 (PST)
In-Reply-To: <8F62EB044F07504DB195F82B824F34DD257551@xmb-aln-x15.cisco.com>
References: <CAF4+nEGXb5_s0LOz+Zh8KBNTOGBBvX5ntHVo_02xrM-vaT==Sw@mail.gmail.com> <8F62EB044F07504DB195F82B824F34DD257551@xmb-aln-x15.cisco.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 19 Feb 2013 16:14:48 -0500
Message-ID: <CAF4+nEFt_Bf+QdevfoJ1r69Mu_CNXDkPbpdHsFEjJJydRz=s7A@mail.gmail.com>
To: "Howard Yang (howardy)" <howardy@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "draft-ietf-trill-rbridge-bfd@tools.ietf.org" <draft-ietf-trill-rbridge-bfd@tools.ietf.org>, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] Comments on TRILL BFD draft and TRILL use of ISIS draft
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: Tue, 19 Feb 2013 21:15:09 -0000

Hi Howard,

See below.

On Tue, Feb 19, 2013 at 3:24 PM, Howard Yang (howardy)
<howardy@cisco.com> wrote:
> Hi Donald,
>
> I have more questions about the TRILL BFD.
>
> Suppose 3 Rbridges are to be connected on the LAN, and all 3 RBs (A, B and
> C) are having the same nickname before they are to be connected (So it's a
> 3-node nickname collision case, which is not likely to happen in the real
> world, but just to demonstrate the points.)

Sure. It is good to consider all the corner cases. You are also
assuming that there are no other paths through the topology by which
link state could flood and the nickname collision already have been
resolved, which is OK to assume for this unusual case.

> Since TRILL BFD Control frames are TRILL Rbridge Channel frames, we need
> both local and peer's nicknames, which happens to be the same in this case.

Well, actually you can use "Any-RBridge" as the egress nickname. TRILL
switches supporting the RBridge Channel facility are required to
recognize the "Any-RBridge" nickname.

> Therefore, if A receives a TRILL BFD packet, it cannot tell if the packet
> is from B or C. This would prevent an RB from establish any TRILL BFD
> sessions.

Yes, that is true until the nicknames are resolved, which should
happen quickly (see below).

> Notice we support RFC6213 (ISIS BFD enabled TLV), which requires to have
> BFD session to be in UP state before bringing up ISIS adjacency, and
> notice the nickname collision resolution is done after exchange of LSPs.
> And notice we need to bring up ISIS adjacency first before LSP can be
> exchanged. Therefore, we are stuck.

Actually I don't think so. There are Down, Detect, Two-Way, and Report
states for a TRILL Adjacency on a LAN link [RFC6327]. A question is,
when does LSP synchronization start? This was not addressed in
[RFC6325] but that oversight is fixed in the approved
draft-ietf-trill-clear-correct-06.txt, Section 9. In particular, LSP
synchronization starts when the adjacency reaches the Two-Way state.
So, of A, B, and C, as soon as any pair's adjacency reaches Two-Way,
the nicknames should be quickly resolved.

> To solve this problem, I am suggesting to modify the TRILL BFD
> encapsulation by adding the source system_ID and destination system_ID.
>
> So the packet could look like the following:
>
>
>       +--------------------------------+
>       |          Link Header           |
>       +--------------------------------+
>       |          TRILL Header          |
>       +--------------------------------+
>       |     Inner Ethernet Header      |
>       +--------------------------------+
>       |     RBridge Channel Header     |
>       +--------------------------------+
>       | dest system_id | src system_id |
> +--------------------------------+
> | Protocol Specific Payload (BFD) |
> +--------------------------------+
>
>       | Link Trailer (FCS if Ethernet) |
>       +--------------------------------+

I do not think that is necessary.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> Thanks,
> -Howard
>
>
> On 2/12/13 7:45 PM, "Donald Eastlake" <d3e3e3@gmail.com> wrote:
>
>>Hi Howard,
>>
>>On Tue, Feb 12, 2013 at 2:47 PM, Howard Yang (howardy)
>><howardy@cisco.com> wrote:
>>> Hi,
>>>
>>> I have a couple of comments on TRILL BFD draft
>>> <draft-ietf-trill-rbridge-bfd-07.txt> and TRILL use of ISIS draft
>>> <draft-ietf-isis-rfc6326bis-00.txt>.
>>>
>>> (1) To support TRILL BFD, it is required to include nickname TLV or
>>>sub-TLV
>>> in the ISIS hello packets.
>>
>>Every TRILL IS-IS Hello PDU is required to include a Special VLANs and
>>Flags Sub-TLV which includes the Sender Nickname. Perhaps the
>>explanatory text for that the Sub-TLV should be expanded to mention
>>BFD bootstrap.
>>
>>> The reason is that when the neighbor receives the BFD packets, if the
>>> nickname of the peer is not known, BFD cannot associate such BFD packets
>>> with the BFD session.
>>>
>>> By the way, let's look at, in specific, the "One-Hop TRILL BFD Control"
>>> here. Looking at Layer 3 (IP or IPv6) BFD, we have IP address TLV
>>>included
>>> in the ISIS hellos, so that when BFD session is created by ISIS, ISIS
>>>can
>>> pass both local and peer's IP addresses to BFD for BFD to associate a
>>>BFD
>>> packet to a session. Corresponding to IP address, in TRILL, we have the
>>> nickname. When a BFD session is created with an unknown nickname for the
>>> peer, and when a BFD packet from this peer is received, BFD has no way
>>>to
>>> associate this BFD packet with the BFD session previously created.
>>>Notice
>>> BFD packets are defined to have the TRILL channel encapsulation
>>> (draft-ietf-trill-rbridge-channel-08.txt).
>>>
>>> So we need to add the requirement of including the local nickname in
>>>ISIS
>>> hellos, in addition to the "ISIS BFD enabled TLV" (RFC 6213).
>>
>>As above, Sender Nickname is already included in every TRILL IS-IS Hello.
>>
>>> The nickname is currently defined as nickname sub-tlv
>>> (<draft-ietf-isis-rfc6326bis-00.txt>) and it is defined only in Router
>>>or MT
>>> Capability TLV. We need to extend it and allow the nickname sub-tlv to
>>>be in
>>> the Multi-Topology-Aware Port Capability TLV.
>>
>>As above, I do not believe that is necessary.
>>
>>> (2) In Section 3.1 of the TRILL BFD draft, we have
>>>
>>> 3.1 One-Hop TRILL BFD Control
>>>
>>>    One-hop TRILL BFD Control is typically used to rapidly detect link
>>>    and RBridge failures.  TRILL BFD frames over one hop for such
>>>    purposes SHOULD be sent with high priority; that is, the Inner.VLAN
>>>    tag priority should be 7, they should be queued for transmission as
>>>    maximum priority frames and, if they are being sent on an Ethernet
>>>    link where the output port is configured to include an Outer.VLAN
>>>    tag, that tag should specify priority 7.
>>>
>>>    For neighbor RBridges RB1 and RB2, each RBridge sends one-hop TRILL
>>>    BFD Control frames to the other only if TRILL IS-IS has detected bi-
>>>    directional connectivity, that is, the adjacency is in the Two-Way or
>>>    Report state [RFC6327] and both RBridges indicate support of TRILL
>>>    BFD is enabled.  The BFD Enabled TLV is used to indicate this as
>>>    specified in [RFC6213].
>>>
>>> The "Two-Way" or "Report" is specific to TRILL LAN interface. It does
>>>not
>>> apply to the point-to-point interface. So, it should be modified to:
>>>
>>> "that is, the adjacency is in the Two-Way or Report state [RFC6327] on
>>>the
>>> LAN or INIT on the point-to-point when neighbor is known and both
>>>Rbridges
>>> indicate support of TRILL BFD is enabled."
>>
>>Work has started on an rfc6327bis draft to extend the proper TRILL
>>adjacency state machine to point-to-point links and also include MTU
>>testing on such links, to make them consistent with broadcast links. I
>>believe that this is the best course. Would you be interested in
>>helping with rfc6327bis?
>>
>>Thanks,
>>Donald
>>=============================
>> Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>> 155 Beaver Street, Milford, MA 01757 USA
>> d3e3e3@gmail.com
>>
>>> Thanks,
>>> -Howard Yang
>

From howardy@cisco.com  Tue Feb 19 15:14:39 2013
Return-Path: <howardy@cisco.com>
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 C354221F8890 for <trill@ietfa.amsl.com>; Tue, 19 Feb 2013 15:14:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.999
X-Spam-Level: 
X-Spam-Status: No, score=-9.999 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, J_CHICKENPOX_54=0.6, RCVD_IN_DNSWL_HI=-8]
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 4Gagsq5+Hizt for <trill@ietfa.amsl.com>; Tue, 19 Feb 2013 15:14:38 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 2608D21F8949 for <trill@ietf.org>; Tue, 19 Feb 2013 15:14:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8416; q=dns/txt; s=iport; t=1361315678; x=1362525278; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=aQXdNLVYSufD2/iCklgUsuSwyDF0ocMG4DqRZCSgh7E=; b=cW64pwjfUcZweuvigLtAqCfXzkr9W4EKV1Tm+kXn25chGYC1VbXvVdtY RAj7fj/B3NpDeCZuvGCrN18mt+h835IyMGm7s6603Kx3RmQ2hrtTZU0sv J2R1YcRnckyu+VJWqE1M/v/Sv+RILSvhLPrXL83BVpIKZ0QgFRiNdnxiv M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAC0GJFGtJXHB/2dsb2JhbAA/AwPARIENFnOCHwEBAQQ6PxIBCA4KChQxESUCBA4FCId4Aw+wOYZADYlajDeBIoECAiEQBxGCTmEDlFCNHoUVgweCJw
X-IronPort-AV: E=Sophos;i="4.84,698,1355097600"; d="scan'208";a="178966876"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-4.cisco.com with ESMTP; 19 Feb 2013 23:14:37 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r1JNEb0x006031 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 19 Feb 2013 23:14:37 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.213]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.02.0318.004; Tue, 19 Feb 2013 17:14:37 -0600
From: "Howard Yang (howardy)" <howardy@cisco.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Thread-Topic: [trill] Comments on TRILL BFD draft and TRILL use of ISIS draft
Thread-Index: AQHOCZybTO2m0M8pekyW1cpAvkGbmZiBiXEAgACUNgD//5tbgA==
Date: Tue, 19 Feb 2013 23:14:36 +0000
Message-ID: <8F62EB044F07504DB195F82B824F34DD257740@xmb-aln-x15.cisco.com>
In-Reply-To: <CAF4+nEFt_Bf+QdevfoJ1r69Mu_CNXDkPbpdHsFEjJJydRz=s7A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.1.120420
x-originating-ip: [128.107.157.236]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C44248E88D9B4A40BFDCF0C9B9296F8D@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ietf-trill-rbridge-bfd@tools.ietf.org" <draft-ietf-trill-rbridge-bfd@tools.ietf.org>, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] Comments on TRILL BFD draft and TRILL use of ISIS draft
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: Tue, 19 Feb 2013 23:14:39 -0000

Hi Donald,

Thanks very much for the explanation. That works for LAN.

By the way, on the point-to-point interface, we don't have the mechanism
to resolve the nickname collision (as we don't have TWO-WAY state). So we
use the Any-Rbridge as destination nickname in TRILL BFD packets. And
since there could be only up to one BFD neighbor for one-hope BFD control,
we are fine with the BFD bootstrapping. However, this would be an issue if
we allow multiple-hop BFD, isn't it (as there could be multiple BFD
sessions coming off an interface)?

Thanks,
-Howard



On 2/19/13 1:14 PM, "Donald Eastlake" <d3e3e3@gmail.com> wrote:

>Hi Howard,
>
>See below.
>
>On Tue, Feb 19, 2013 at 3:24 PM, Howard Yang (howardy)
><howardy@cisco.com> wrote:
>> Hi Donald,
>>
>> I have more questions about the TRILL BFD.
>>
>> Suppose 3 Rbridges are to be connected on the LAN, and all 3 RBs (A, B
>>and
>> C) are having the same nickname before they are to be connected (So
>>it's a
>> 3-node nickname collision case, which is not likely to happen in the
>>real
>> world, but just to demonstrate the points.)
>
>Sure. It is good to consider all the corner cases. You are also
>assuming that there are no other paths through the topology by which
>link state could flood and the nickname collision already have been
>resolved, which is OK to assume for this unusual case.
>
>> Since TRILL BFD Control frames are TRILL Rbridge Channel frames, we need
>> both local and peer's nicknames, which happens to be the same in this
>>case.
>
>Well, actually you can use "Any-RBridge" as the egress nickname. TRILL
>switches supporting the RBridge Channel facility are required to
>recognize the "Any-RBridge" nickname.
>
>> Therefore, if A receives a TRILL BFD packet, it cannot tell if the
>>packet
>> is from B or C. This would prevent an RB from establish any TRILL BFD
>> sessions.
>
>Yes, that is true until the nicknames are resolved, which should
>happen quickly (see below).
>
>> Notice we support RFC6213 (ISIS BFD enabled TLV), which requires to have
>> BFD session to be in UP state before bringing up ISIS adjacency, and
>> notice the nickname collision resolution is done after exchange of LSPs.
>> And notice we need to bring up ISIS adjacency first before LSP can be
>> exchanged. Therefore, we are stuck.
>
>Actually I don't think so. There are Down, Detect, Two-Way, and Report
>states for a TRILL Adjacency on a LAN link [RFC6327]. A question is,
>when does LSP synchronization start? This was not addressed in
>[RFC6325] but that oversight is fixed in the approved
>draft-ietf-trill-clear-correct-06.txt, Section 9. In particular, LSP
>synchronization starts when the adjacency reaches the Two-Way state.
>So, of A, B, and C, as soon as any pair's adjacency reaches Two-Way,
>the nicknames should be quickly resolved.
>
>> To solve this problem, I am suggesting to modify the TRILL BFD
>> encapsulation by adding the source system_ID and destination system_ID.
>>
>> So the packet could look like the following:
>>
>>
>>       +--------------------------------+
>>       |          Link Header           |
>>       +--------------------------------+
>>       |          TRILL Header          |
>>       +--------------------------------+
>>       |     Inner Ethernet Header      |
>>       +--------------------------------+
>>       |     RBridge Channel Header     |
>>       +--------------------------------+
>>       | dest system_id | src system_id |
>> +--------------------------------+
>> | Protocol Specific Payload (BFD) |
>> +--------------------------------+
>>
>>       | Link Trailer (FCS if Ethernet) |
>>       +--------------------------------+
>
>I do not think that is necessary.
>
>Thanks,
>Donald
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
> Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
> 155 Beaver Street, Milford, MA 01757 USA
> d3e3e3@gmail.com
>
>> Thanks,
>> -Howard
>>
>>
>> On 2/12/13 7:45 PM, "Donald Eastlake" <d3e3e3@gmail.com> wrote:
>>
>>>Hi Howard,
>>>
>>>On Tue, Feb 12, 2013 at 2:47 PM, Howard Yang (howardy)
>>><howardy@cisco.com> wrote:
>>>> Hi,
>>>>
>>>> I have a couple of comments on TRILL BFD draft
>>>> <draft-ietf-trill-rbridge-bfd-07.txt> and TRILL use of ISIS draft
>>>> <draft-ietf-isis-rfc6326bis-00.txt>.
>>>>
>>>> (1) To support TRILL BFD, it is required to include nickname TLV or
>>>>sub-TLV
>>>> in the ISIS hello packets.
>>>
>>>Every TRILL IS-IS Hello PDU is required to include a Special VLANs and
>>>Flags Sub-TLV which includes the Sender Nickname. Perhaps the
>>>explanatory text for that the Sub-TLV should be expanded to mention
>>>BFD bootstrap.
>>>
>>>> The reason is that when the neighbor receives the BFD packets, if the
>>>> nickname of the peer is not known, BFD cannot associate such BFD
>>>>packets
>>>> with the BFD session.
>>>>
>>>> By the way, let's look at, in specific, the "One-Hop TRILL BFD
>>>>Control"
>>>> here. Looking at Layer 3 (IP or IPv6) BFD, we have IP address TLV
>>>>included
>>>> in the ISIS hellos, so that when BFD session is created by ISIS, ISIS
>>>>can
>>>> pass both local and peer's IP addresses to BFD for BFD to associate a
>>>>BFD
>>>> packet to a session. Corresponding to IP address, in TRILL, we have
>>>>the
>>>> nickname. When a BFD session is created with an unknown nickname for
>>>>the
>>>> peer, and when a BFD packet from this peer is received, BFD has no way
>>>>to
>>>> associate this BFD packet with the BFD session previously created.
>>>>Notice
>>>> BFD packets are defined to have the TRILL channel encapsulation
>>>> (draft-ietf-trill-rbridge-channel-08.txt).
>>>>
>>>> So we need to add the requirement of including the local nickname in
>>>>ISIS
>>>> hellos, in addition to the "ISIS BFD enabled TLV" (RFC 6213).
>>>
>>>As above, Sender Nickname is already included in every TRILL IS-IS
>>>Hello.
>>>
>>>> The nickname is currently defined as nickname sub-tlv
>>>> (<draft-ietf-isis-rfc6326bis-00.txt>) and it is defined only in Router
>>>>or MT
>>>> Capability TLV. We need to extend it and allow the nickname sub-tlv to
>>>>be in
>>>> the Multi-Topology-Aware Port Capability TLV.
>>>
>>>As above, I do not believe that is necessary.
>>>
>>>> (2) In Section 3.1 of the TRILL BFD draft, we have
>>>>
>>>> 3.1 One-Hop TRILL BFD Control
>>>>
>>>>    One-hop TRILL BFD Control is typically used to rapidly detect link
>>>>    and RBridge failures.  TRILL BFD frames over one hop for such
>>>>    purposes SHOULD be sent with high priority; that is, the Inner.VLAN
>>>>    tag priority should be 7, they should be queued for transmission as
>>>>    maximum priority frames and, if they are being sent on an Ethernet
>>>>    link where the output port is configured to include an Outer.VLAN
>>>>    tag, that tag should specify priority 7.
>>>>
>>>>    For neighbor RBridges RB1 and RB2, each RBridge sends one-hop TRILL
>>>>    BFD Control frames to the other only if TRILL IS-IS has detected
>>>>bi-
>>>>    directional connectivity, that is, the adjacency is in the Two-Way
>>>>or
>>>>    Report state [RFC6327] and both RBridges indicate support of TRILL
>>>>    BFD is enabled.  The BFD Enabled TLV is used to indicate this as
>>>>    specified in [RFC6213].
>>>>
>>>> The "Two-Way" or "Report" is specific to TRILL LAN interface. It does
>>>>not
>>>> apply to the point-to-point interface. So, it should be modified to:
>>>>
>>>> "that is, the adjacency is in the Two-Way or Report state [RFC6327] on
>>>>the
>>>> LAN or INIT on the point-to-point when neighbor is known and both
>>>>Rbridges
>>>> indicate support of TRILL BFD is enabled."
>>>
>>>Work has started on an rfc6327bis draft to extend the proper TRILL
>>>adjacency state machine to point-to-point links and also include MTU
>>>testing on such links, to make them consistent with broadcast links. I
>>>believe that this is the best course. Would you be interested in
>>>helping with rfc6327bis?
>>>
>>>Thanks,
>>>Donald
>>>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>>> Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>>> 155 Beaver Street, Milford, MA 01757 USA
>>> d3e3e3@gmail.com
>>>
>>>> Thanks,
>>>> -Howard Yang
>>


From d3e3e3@gmail.com  Tue Feb 19 15:57:39 2013
Return-Path: <d3e3e3@gmail.com>
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 C448221F89A3 for <trill@ietfa.amsl.com>; Tue, 19 Feb 2013 15:57:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.177
X-Spam-Level: 
X-Spam-Status: No, score=-103.177 tagged_above=-999 required=5 tests=[AWL=-0.178, BAYES_00=-2.599, J_CHICKENPOX_54=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 MU-2fImF4LI9 for <trill@ietfa.amsl.com>; Tue, 19 Feb 2013 15:57:38 -0800 (PST)
Received: from mail-oa0-f49.google.com (mail-oa0-f49.google.com [209.85.219.49]) by ietfa.amsl.com (Postfix) with ESMTP id BBE9821F8952 for <trill@ietf.org>; Tue, 19 Feb 2013 15:57:38 -0800 (PST)
Received: by mail-oa0-f49.google.com with SMTP id j6so7625486oag.36 for <trill@ietf.org>; Tue, 19 Feb 2013 15:57:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=Gy/dKmpj6s+XK15y3N5tskDhjsiHbT5Q9lqxxkOgMtk=; b=qpNHs7aatEitrB+Fng3WcZUdVPykZ8ck0Fd+O9pPzhNqnYng3BKyWkrSAfn4kKy2C8 PjUTmqjXtZLKrPB9JhFejk5PlUYHx05yL8ShsF/HPqZLrU9+onUpwt4wsMa8Od+WEQTt cQgSEx0OSPBV3TnuZqwBAiEkbhUVFGbs/p8jxTWEGou6IxScWaIsC6zQ3Xw5kT89WNFW /JNXh4kZJKMXq4htwRv+qCl1zHPfJ0ox9rEE+jMSvHczWLr4zreT89UXM/u2y+EMpv6T 5m9jaW4UFIl3a0010vobHuwMHlgc9rleIIgLhIZUblznCruZTNfloim9UXADkD4DajpR EFKQ==
X-Received: by 10.182.235.49 with SMTP id uj17mr8379598obc.18.1361318258335; Tue, 19 Feb 2013 15:57:38 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.98.168 with HTTP; Tue, 19 Feb 2013 15:57:18 -0800 (PST)
In-Reply-To: <8F62EB044F07504DB195F82B824F34DD257740@xmb-aln-x15.cisco.com>
References: <CAF4+nEFt_Bf+QdevfoJ1r69Mu_CNXDkPbpdHsFEjJJydRz=s7A@mail.gmail.com> <8F62EB044F07504DB195F82B824F34DD257740@xmb-aln-x15.cisco.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 19 Feb 2013 18:57:18 -0500
Message-ID: <CAF4+nEGSOofx9TKx_WGU-+0wpQWff3nkPXuCXH06cU7m_rU+wA@mail.gmail.com>
To: "Howard Yang (howardy)" <howardy@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "draft-ietf-trill-rbridge-bfd@tools.ietf.org" <draft-ietf-trill-rbridge-bfd@tools.ietf.org>, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] Comments on TRILL BFD draft and TRILL use of ISIS draft
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: Tue, 19 Feb 2013 23:57:39 -0000

Hi Howard,

On Tue, Feb 19, 2013 at 6:14 PM, Howard Yang (howardy)
<howardy@cisco.com> wrote:
> Hi Donald,
>
> Thanks very much for the explanation. That works for LAN.
>
> By the way, on the point-to-point interface, we don't have the mechanism
> to resolve the nickname collision (as we don't have TWO-WAY state). So we
> use the Any-Rbridge as destination nickname in TRILL BFD packets. And
> since there could be only up to one BFD neighbor for one-hope BFD control,
> we are fine with the BFD bootstrapping. However, this would be an issue if
> we allow multiple-hop BFD, isn't it (as there could be multiple BFD
> sessions coming off an interface)?

Yes, you can't use Any-RBridge for more than one hop. And, after the
first hop, subsequent hops can only be taken if they are fully up and
part of the topology.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> Thanks,
> -Howard
>
>
>
> On 2/19/13 1:14 PM, "Donald Eastlake" <d3e3e3@gmail.com> wrote:
>
>>Hi Howard,
>>
>>See below.
>>
>>On Tue, Feb 19, 2013 at 3:24 PM, Howard Yang (howardy)
>><howardy@cisco.com> wrote:
>>> Hi Donald,
>>>
>>> I have more questions about the TRILL BFD.
>>>
>>> Suppose 3 Rbridges are to be connected on the LAN, and all 3 RBs (A, B
>>>and
>>> C) are having the same nickname before they are to be connected (So
>>>it's a
>>> 3-node nickname collision case, which is not likely to happen in the
>>>real
>>> world, but just to demonstrate the points.)
>>
>>Sure. It is good to consider all the corner cases. You are also
>>assuming that there are no other paths through the topology by which
>>link state could flood and the nickname collision already have been
>>resolved, which is OK to assume for this unusual case.
>>
>>> Since TRILL BFD Control frames are TRILL Rbridge Channel frames, we need
>>> both local and peer's nicknames, which happens to be the same in this
>>>case.
>>
>>Well, actually you can use "Any-RBridge" as the egress nickname. TRILL
>>switches supporting the RBridge Channel facility are required to
>>recognize the "Any-RBridge" nickname.
>>
>>> Therefore, if A receives a TRILL BFD packet, it cannot tell if the
>>>packet
>>> is from B or C. This would prevent an RB from establish any TRILL BFD
>>> sessions.
>>
>>Yes, that is true until the nicknames are resolved, which should
>>happen quickly (see below).
>>
>>> Notice we support RFC6213 (ISIS BFD enabled TLV), which requires to have
>>> BFD session to be in UP state before bringing up ISIS adjacency, and
>>> notice the nickname collision resolution is done after exchange of LSPs.
>>> And notice we need to bring up ISIS adjacency first before LSP can be
>>> exchanged. Therefore, we are stuck.
>>
>>Actually I don't think so. There are Down, Detect, Two-Way, and Report
>>states for a TRILL Adjacency on a LAN link [RFC6327]. A question is,
>>when does LSP synchronization start? This was not addressed in
>>[RFC6325] but that oversight is fixed in the approved
>>draft-ietf-trill-clear-correct-06.txt, Section 9. In particular, LSP
>>synchronization starts when the adjacency reaches the Two-Way state.
>>So, of A, B, and C, as soon as any pair's adjacency reaches Two-Way,
>>the nicknames should be quickly resolved.
>>
>>> To solve this problem, I am suggesting to modify the TRILL BFD
>>> encapsulation by adding the source system_ID and destination system_ID.
>>>
>>> So the packet could look like the following:
>>>
>>>
>>>       +--------------------------------+
>>>       |          Link Header           |
>>>       +--------------------------------+
>>>       |          TRILL Header          |
>>>       +--------------------------------+
>>>       |     Inner Ethernet Header      |
>>>       +--------------------------------+
>>>       |     RBridge Channel Header     |
>>>       +--------------------------------+
>>>       | dest system_id | src system_id |
>>> +--------------------------------+
>>> | Protocol Specific Payload (BFD) |
>>> +--------------------------------+
>>>
>>>       | Link Trailer (FCS if Ethernet) |
>>>       +--------------------------------+
>>
>>I do not think that is necessary.
>>
>>Thanks,
>>Donald
>>=============================
>> Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>> 155 Beaver Street, Milford, MA 01757 USA
>> d3e3e3@gmail.com
>>
>>> Thanks,
>>> -Howard
>>>
>>>
>>> On 2/12/13 7:45 PM, "Donald Eastlake" <d3e3e3@gmail.com> wrote:
>>>
>>>>Hi Howard,
>>>>
>>>>On Tue, Feb 12, 2013 at 2:47 PM, Howard Yang (howardy)
>>>><howardy@cisco.com> wrote:
>>>>> Hi,
>>>>>
>>>>> I have a couple of comments on TRILL BFD draft
>>>>> <draft-ietf-trill-rbridge-bfd-07.txt> and TRILL use of ISIS draft
>>>>> <draft-ietf-isis-rfc6326bis-00.txt>.
>>>>>
>>>>> (1) To support TRILL BFD, it is required to include nickname TLV or
>>>>>sub-TLV
>>>>> in the ISIS hello packets.
>>>>
>>>>Every TRILL IS-IS Hello PDU is required to include a Special VLANs and
>>>>Flags Sub-TLV which includes the Sender Nickname. Perhaps the
>>>>explanatory text for that the Sub-TLV should be expanded to mention
>>>>BFD bootstrap.
>>>>
>>>>> The reason is that when the neighbor receives the BFD packets, if the
>>>>> nickname of the peer is not known, BFD cannot associate such BFD
>>>>>packets
>>>>> with the BFD session.
>>>>>
>>>>> By the way, let's look at, in specific, the "One-Hop TRILL BFD
>>>>>Control"
>>>>> here. Looking at Layer 3 (IP or IPv6) BFD, we have IP address TLV
>>>>>included
>>>>> in the ISIS hellos, so that when BFD session is created by ISIS, ISIS
>>>>>can
>>>>> pass both local and peer's IP addresses to BFD for BFD to associate a
>>>>>BFD
>>>>> packet to a session. Corresponding to IP address, in TRILL, we have
>>>>>the
>>>>> nickname. When a BFD session is created with an unknown nickname for
>>>>>the
>>>>> peer, and when a BFD packet from this peer is received, BFD has no way
>>>>>to
>>>>> associate this BFD packet with the BFD session previously created.
>>>>>Notice
>>>>> BFD packets are defined to have the TRILL channel encapsulation
>>>>> (draft-ietf-trill-rbridge-channel-08.txt).
>>>>>
>>>>> So we need to add the requirement of including the local nickname in
>>>>>ISIS
>>>>> hellos, in addition to the "ISIS BFD enabled TLV" (RFC 6213).
>>>>
>>>>As above, Sender Nickname is already included in every TRILL IS-IS
>>>>Hello.
>>>>
>>>>> The nickname is currently defined as nickname sub-tlv
>>>>> (<draft-ietf-isis-rfc6326bis-00.txt>) and it is defined only in Router
>>>>>or MT
>>>>> Capability TLV. We need to extend it and allow the nickname sub-tlv to
>>>>>be in
>>>>> the Multi-Topology-Aware Port Capability TLV.
>>>>
>>>>As above, I do not believe that is necessary.
>>>>
>>>>> (2) In Section 3.1 of the TRILL BFD draft, we have
>>>>>
>>>>> 3.1 One-Hop TRILL BFD Control
>>>>>
>>>>>    One-hop TRILL BFD Control is typically used to rapidly detect link
>>>>>    and RBridge failures.  TRILL BFD frames over one hop for such
>>>>>    purposes SHOULD be sent with high priority; that is, the Inner.VLAN
>>>>>    tag priority should be 7, they should be queued for transmission as
>>>>>    maximum priority frames and, if they are being sent on an Ethernet
>>>>>    link where the output port is configured to include an Outer.VLAN
>>>>>    tag, that tag should specify priority 7.
>>>>>
>>>>>    For neighbor RBridges RB1 and RB2, each RBridge sends one-hop TRILL
>>>>>    BFD Control frames to the other only if TRILL IS-IS has detected
>>>>>bi-
>>>>>    directional connectivity, that is, the adjacency is in the Two-Way
>>>>>or
>>>>>    Report state [RFC6327] and both RBridges indicate support of TRILL
>>>>>    BFD is enabled.  The BFD Enabled TLV is used to indicate this as
>>>>>    specified in [RFC6213].
>>>>>
>>>>> The "Two-Way" or "Report" is specific to TRILL LAN interface. It does
>>>>>not
>>>>> apply to the point-to-point interface. So, it should be modified to:
>>>>>
>>>>> "that is, the adjacency is in the Two-Way or Report state [RFC6327] on
>>>>>the
>>>>> LAN or INIT on the point-to-point when neighbor is known and both
>>>>>Rbridges
>>>>> indicate support of TRILL BFD is enabled."
>>>>
>>>>Work has started on an rfc6327bis draft to extend the proper TRILL
>>>>adjacency state machine to point-to-point links and also include MTU
>>>>testing on such links, to make them consistent with broadcast links. I
>>>>believe that this is the best course. Would you be interested in
>>>>helping with rfc6327bis?
>>>>
>>>>Thanks,
>>>>Donald
>>>>=============================
>>>> Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>>>> 155 Beaver Street, Milford, MA 01757 USA
>>>> d3e3e3@gmail.com
>>>>
>>>>> Thanks,
>>>>> -Howard Yang
>>>
>

From internet-drafts@ietf.org  Thu Feb 21 14:04:32 2013
Return-Path: <internet-drafts@ietf.org>
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 1176D21F8E90; Thu, 21 Feb 2013 14:04:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.554
X-Spam-Level: 
X-Spam-Status: No, score=-102.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 qbwrUABA07SR; Thu, 21 Feb 2013 14:04:31 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B83C21F8E96; Thu, 21 Feb 2013 14:04:31 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.40
Message-ID: <20130221220431.1135.93274.idtracker@ietfa.amsl.com>
Date: Thu, 21 Feb 2013 14:04:31 -0800
Cc: trill@ietf.org
Subject: [trill] I-D Action: draft-ietf-trill-directory-framework-03.txt
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: Thu, 21 Feb 2013 22:04:32 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Transparent Interconnection of Lots of Li=
nks Working Group of the IETF.

	Title           : TRILL (Transparent Interconnection of Lots of Links) Edg=
e Directory Assistance Framework
	Author(s)       : Linda Dunbar
                          Donald Eastlake
                          Radia Perlman
                          Igor Gashinsky
	Filename        : draft-ietf-trill-directory-framework-03.txt
	Pages           : 16
	Date            : 2013-02-21

Abstract:
   Edge RBridges currently learn the mapping between MAC addresses
   and their egress RBridges by observing the data packets traversed
   or by the TRILL ESADI protocol. When ingress RBridge receives a
   data frame whose destination address (MAC&VLAN) that RBridge does
   not know, the data frame is flooded within the VLAN across the
   TRILL campus.

   This draft describes the framework for using directory services
   to assist edge RBridges by reducing multi-destination frames,
   particularly unknown unicast frames flooding, and ARP/ND,
   improving TRILL (Transparent Interconnection of Lots of Links)
   network scalability in environments such as data centers.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-trill-directory-framework-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-trill-directory-framework-03


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


From internet-drafts@ietf.org  Thu Feb 21 19:34:49 2013
Return-Path: <internet-drafts@ietf.org>
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 C92FB21F8883; Thu, 21 Feb 2013 19:34:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 8IJsXCjWlW3Z; Thu, 21 Feb 2013 19:34:49 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59F3D21F888B; Thu, 21 Feb 2013 19:34:49 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.40
Message-ID: <20130222033449.23054.99461.idtracker@ietfa.amsl.com>
Date: Thu, 21 Feb 2013 19:34:49 -0800
Cc: trill@ietf.org
Subject: [trill] I-D Action: draft-ietf-trill-esadi-02.txt
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: Fri, 22 Feb 2013 03:34:50 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Transparent Interconnection of Lots of Li=
nks Working Group of the IETF.

	Title           : TRILL (Transparent Interconnection of Lots of Links): ES=
ADI (End Station Address Distribution Information) Protocol
	Author(s)       : Hongjun Zhai
                          Fangwei Hu
                          Radia Perlman
                          Donald Eastlake
                          Olen Stokes
	Filename        : draft-ietf-trill-esadi-02.txt
	Pages           : 31
	Date            : 2013-02-21

Abstract:
   The IETF TRILL (Transparent Interconnection of Lots of Links)
   protocol provides least cost pair-wise data forwarding without
   configuration in multi-hop networks with arbitrary topologies and
   link technologies.  TRILL supports multi-pathing of both unicast and
   multicast traffic.  Devices that implement the TRILL protocol are
   called RBridges (Routing Bridges) or TRILL Switches.

   ESADI (End Station Address Distribution Information) is an optional
   protocol by which a TRILL switch can communicate, in a Data Label
   (VLAN or Fine Grained Label) scoped way, end station addresses and
   other information to TRILL switches pariticipating in ESADI for the
   relevant Data Label.  This document updates RFC 6325, specifically
   the documentation of the ESADI protocol.





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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-trill-esadi-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-trill-esadi-02


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


From d3e3e3@gmail.com  Thu Feb 21 20:06:07 2013
Return-Path: <d3e3e3@gmail.com>
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 4608521E804B for <trill@ietfa.amsl.com>; Thu, 21 Feb 2013 20:06:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.471
X-Spam-Level: 
X-Spam-Status: No, score=-103.471 tagged_above=-999 required=5 tests=[AWL=0.128, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 nhd6c-VGt4Pc for <trill@ietfa.amsl.com>; Thu, 21 Feb 2013 20:06:06 -0800 (PST)
Received: from mail-oa0-f43.google.com (mail-oa0-f43.google.com [209.85.219.43]) by ietfa.amsl.com (Postfix) with ESMTP id 7E6A321E803D for <trill@ietf.org>; Thu, 21 Feb 2013 20:06:06 -0800 (PST)
Received: by mail-oa0-f43.google.com with SMTP id l10so226833oag.30 for <trill@ietf.org>; Thu, 21 Feb 2013 20:06:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=GrBbU8PFlXp0qNG5mqpbEFAbx9OLDIv1wOxAwdneMpI=; b=RU6OJ3dBR5WqB86Zx8lKuw+YQf07S1FV6MYKRfIA6GFfF8tnXRXpXJJGhCF3ZC/8SS qDcF8Cpn7wkjaj1kE179wQ1NPcF1a6220h493B/xw3E8Wou0QoNPlx5dsCTSNxPLRVsH gpzc+4Ir4tS/zikbFqucn4Vp0oxpC3eIXp48Ngr2wTIIcVlRNFmGXPv7h7m/Qg47FKHy W1q6iBvkDI1crlj6ZClIrX+udbBL/9Be0AmMQdbjTtl37+YFTTLOVM+zi/htQhX0xvgk E637vTasXrylkNYYHiwO4QrHSW5/V6Bwjd8+Lnm8Fl6ct49qt0ZOcGHwKfhUOgbD++9v dAGg==
X-Received: by 10.60.26.72 with SMTP id j8mr227803oeg.2.1361505964483; Thu, 21 Feb 2013 20:06:04 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.98.168 with HTTP; Thu, 21 Feb 2013 20:05:44 -0800 (PST)
In-Reply-To: <20130222033449.23054.99461.idtracker@ietfa.amsl.com>
References: <20130222033449.23054.99461.idtracker@ietfa.amsl.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 21 Feb 2013 23:05:44 -0500
Message-ID: <CAF4+nEF0cCUp495-QbTLpzhvstb60_j40nKKxxqqN8wL_ibVvg@mail.gmail.com>
To: trill@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [trill] I-D Action: draft-ietf-trill-esadi-02.txt
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: Fri, 22 Feb 2013 04:06:07 -0000

This version has the changes that were posted to the list (see below)
incorporated. The fourth change listed was generalized a bit to allow
use of ECMP if the sending TRILL switch is OK with return traffic from
a particular MAC and Data Label coming from different TRILL switches.

http://www.ietf.org/mail-archive/web/trill/current/msg05559.html
http://www.ietf.org/mail-archive/web/trill/current/msg05560.html
http://www.ietf.org/mail-archive/web/trill/current/msg05561.html
http://www.ietf.org/mail-archive/web/trill/current/msg05581.html

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

On Thu, Feb 21, 2013 at 10:34 PM,  <internet-drafts@ietf.org> wrote:
>
> 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 Working Group of the IETF.
>
>         Title           : TRILL (Transparent Interconnection of Lots of Links): ESADI (End Station Address Distribution Information) Protocol
>         Author(s)       : Hongjun Zhai
>                           Fangwei Hu
>                           Radia Perlman
>                           Donald Eastlake
>                           Olen Stokes
>         Filename        : draft-ietf-trill-esadi-02.txt
>         Pages           : 31
>         Date            : 2013-02-21
>
> Abstract:
>    The IETF TRILL (Transparent Interconnection of Lots of Links)
>    protocol provides least cost pair-wise data forwarding without
>    configuration in multi-hop networks with arbitrary topologies and
>    link technologies.  TRILL supports multi-pathing of both unicast and
>    multicast traffic.  Devices that implement the TRILL protocol are
>    called RBridges (Routing Bridges) or TRILL Switches.
>
>    ESADI (End Station Address Distribution Information) is an optional
>    protocol by which a TRILL switch can communicate, in a Data Label
>    (VLAN or Fine Grained Label) scoped way, end station addresses and
>    other information to TRILL switches pariticipating in ESADI for the
>    relevant Data Label.  This document updates RFC 6325, specifically
>    the documentation of the ESADI protocol.
>
>
>
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-trill-esadi
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-trill-esadi-02
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-trill-esadi-02
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> trill mailing list
> trill@ietf.org
> https://www.ietf.org/mailman/listinfo/trill

From d3e3e3@gmail.com  Fri Feb 22 11:40:14 2013
Return-Path: <d3e3e3@gmail.com>
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 D773021F88B5 for <trill@ietfa.amsl.com>; Fri, 22 Feb 2013 11:40:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.475
X-Spam-Level: 
X-Spam-Status: No, score=-103.475 tagged_above=-999 required=5 tests=[AWL=0.124, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 sQEKV7WYA00r for <trill@ietfa.amsl.com>; Fri, 22 Feb 2013 11:40:14 -0800 (PST)
Received: from mail-ob0-f180.google.com (mail-ob0-f180.google.com [209.85.214.180]) by ietfa.amsl.com (Postfix) with ESMTP id F405321F8891 for <trill@ietf.org>; Fri, 22 Feb 2013 11:40:13 -0800 (PST)
Received: by mail-ob0-f180.google.com with SMTP id ef5so895000obb.25 for <trill@ietf.org>; Fri, 22 Feb 2013 11:40:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=2lGYY7e3vTzft9yF4x51Lf1tFf6at7n30AP0rRYZ3QY=; b=adLySHKBn6A3wL3jFm8hlGBNrp01Jcs3ZlypT7/NyebVgt3lsJ3EYynMZw5vLUMif8 iUckbsNJflJtYLBBpsHUYnCUdQi+iw7cPe98lZRdfKi9hitd7G4eoX0zwXmgoukBUW+J 9LZ7YfO6Y1ssAuONJaxbhSWNxPYSb+GO9YjPyssesTH/9VkRW8tDChUn0MdgpnK/JkT8 rSnvRVfCo1kCHplw4cEv31IJigvbvX1tSl4hPwv4hRNkMadDua0kTlQ1pfdAzMEKvUh/ V9VyEHGo0RMZUx8yVkdKa6B3A3+6WWHjVSVK++mPEUkt0GgHKWd/KrEPIQC/XY/YAOE3 480w==
X-Received: by 10.60.3.193 with SMTP id e1mr1322024oee.39.1361562013462; Fri, 22 Feb 2013 11:40:13 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.98.168 with HTTP; Fri, 22 Feb 2013 11:39:53 -0800 (PST)
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 22 Feb 2013 14:39:53 -0500
Message-ID: <CAF4+nEFZ9WJF83MQYR7f-moG+PY+jieEDNKP5ZH7swSNFKxDeQ@mail.gmail.com>
To: trill@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [trill] draft-yong-pwe3-trill-o-pw
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: Fri, 22 Feb 2013 19:40:15 -0000

The following draft may be of interest to participants in the TRILL WG
https://datatracker.ietf.org/doc/draft-yong-pwe3-trill-o-pw/

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

From liyizhou@huawei.com  Sun Feb 24 16:57:35 2013
Return-Path: <liyizhou@huawei.com>
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 303A121F9179 for <trill@ietfa.amsl.com>; Sun, 24 Feb 2013 16:57:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 U8GBF3zHoKZp for <trill@ietfa.amsl.com>; Sun, 24 Feb 2013 16:57:34 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 08C6421F9175 for <trill@ietf.org>; Sun, 24 Feb 2013 16:57:33 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AQA29673; Mon, 25 Feb 2013 00:57:33 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 25 Feb 2013 00:56:44 +0000
Received: from SZXEML423-HUB.china.huawei.com (10.82.67.162) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 25 Feb 2013 00:57:32 +0000
Received: from l63746 (10.138.122.43) by smtpscn.huawei.com (10.82.67.162) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 25 Feb 2013 08:57:26 +0800
From: Yizhou Li <liyizhou@huawei.com>
To: "'Donald Eastlake'" <d3e3e3@gmail.com>, <trill@ietf.org>
References: <20130213202128.18172.2727.idtracker@ietfa.amsl.com> <CAF4+nEHWwz4N0pd7OaBVcp4BiHLByy+SvsCpC1G8w+yGjdsS_w@mail.gmail.com>
In-Reply-To: <CAF4+nEHWwz4N0pd7OaBVcp4BiHLByy+SvsCpC1G8w+yGjdsS_w@mail.gmail.com>
Date: Mon, 25 Feb 2013 08:57:27 +0800
Message-ID: <01af01ce12f3$14df8970$3e9e9c50$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac4KT8JefoGZJlZ7SuSOQsD5jsrFHQIo0dlA
Content-Language: zh-cn
X-Originating-IP: [10.138.122.43]
X-CFilter-Loop: Reflected
Subject: Re: [trill] I-D Action: draft-ietf-trill-fine-labeling-05.txt
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: Mon, 25 Feb 2013 00:57:35 -0000

That looks fine to me.

Yizhou

-----Original Message-----
From: trill-bounces@ietf.org [mailto:trill-bounces@ietf.org] On Behalf Of
Donald Eastlake
Sent: Thursday, February 14, 2013 9:08 AM
To: trill@ietf.org
Subject: Re: [trill] I-D Action: draft-ietf-trill-fine-labeling-05.txt

This version is intended to corporate tweaked option 2 as per the
following message
http://www.ietf.org/mail-archive/web/trill/current/msg05633.html

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

On Wed, Feb 13, 2013 at 3:21 PM,  <internet-drafts@ietf.org> wrote:
>
> 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 Working Group of the IETF.
>
>         Title           : TRILL (Transparent Interconnection of Lots of
Links): Fine-Grained Labeling
>         Author(s)       : Donald Eastlake
>                           Mingui Zhang
>                           Puneet Agarwal
>                           Radia Perlman
>                           Dinesh G. Dutt
>         Filename        : draft-ietf-trill-fine-labeling-05.txt
>         Pages           : 31
>         Date            : 2013-02-13
>
> Abstract:
>    The IETF has standardized TRILL (Transparent Interconnection of Lots
>    of Links), a protocol for least cost transparent frame routing in
>    multi-hop networks with arbitrary topologies and link technologies,
>    using link-state routing and a hop count. The TRILL base protocol
>    standard supports labeling of TRILL data with up to 4K IDs. However,
>    there are applications that require more fine-grained labeling of
>    data. This document updates RFC 6325 by specifying optional
>    extensions to the TRILL base protocol to safely accomplish this.
>
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-trill-fine-labeling
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-trill-fine-labeling-05
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-trill-fine-labeling-05
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> 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


From zhai.hongjun@zte.com.cn  Sun Feb 24 22:20:50 2013
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 BBE2221F91C5 for <trill@ietfa.amsl.com>; Sun, 24 Feb 2013 22:20:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.999
X-Spam-Level: 
X-Spam-Status: No, score=-96.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 aUukbIyGwvrj for <trill@ietfa.amsl.com>; Sun, 24 Feb 2013 22:20:49 -0800 (PST)
Received: from zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id 244C621F91AF for <trill@ietf.org>; Sun, 24 Feb 2013 22:20:48 -0800 (PST)
Received: from zte.com.cn (unknown [192.168.168.119]) by Websense Email Security Gateway with ESMTP id 3720DC2503 for <trill@ietf.org>; Mon, 25 Feb 2013 14:20:19 +0800 (CST)
Received: from mse02.zte.com.cn (unknown [10.30.3.21]) by Websense Email Security Gateway with ESMTPS id 27F0B737D7C; Mon, 25 Feb 2013 14:15:21 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id r1P6KH8O051936; Mon, 25 Feb 2013 14:20:17 +0800 (GMT-8) (envelope-from zhai.hongjun@zte.com.cn)
In-Reply-To: <CAF4+nEHWwz4N0pd7OaBVcp4BiHLByy+SvsCpC1G8w+yGjdsS_w@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
MIME-Version: 1.0
X-KeepSent: 72244E02:B708C7CB-48257B1D:00210B67; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF72244E02.B708C7CB-ON48257B1D.00210B67-48257B1D.002339A4@zte.com.cn>
From: zhai.hongjun@zte.com.cn
Date: Mon, 25 Feb 2013 14:20:18 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2013-02-25 14:20:06, Serialize complete at 2013-02-25 14:20:06
Content-Type: multipart/alternative; boundary="=_alternative 0023399C48257B1D_="
X-MAIL: mse02.zte.com.cn r1P6KH8O051936
Cc: trill@ietf.org
Subject: Re: [trill] I-D Action: draft-ietf-trill-fine-labeling-05.txt
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: Mon, 25 Feb 2013 06:20:50 -0000

This is a multipart message in MIME format.
--=_alternative 0023399C48257B1D_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

SGkgRG9uYWxkLA0KDQpBY2NvcmRpbmcgdG8gdGhlIGN1cnJlbnQgRkdMIGRyYWZ0LCB0aGUgcm9v
dCBmb3IgYW4gRkdMIEQtdHJlZSBjYW4gb25seSBiZSANCnRoZSBuaWNrbmFtZSBoZWxkIGJ5IGFu
IEZHTCBSQnJpZGdlIG9yIGEgcHNldWRvbm9kZSByZXByZXNlbnRpbmcgYSBGR0wgDQpsaW5rLg0K
DQpIb3dldmVyLCBzaW5jZSBhbiBGR0wtc2FmZSBjYW4gY2FsY3VsYXRlIEZHTCBELXRyZWVzIGNv
cnJlY3RseSBhbmQgZm9yd2FyZCANCm11bHRpLWRlc3RpYXRpb24gRkdMIHBhY2t0ZXMgc2FmZWx5
LCBJIHRoaW5rIGl0IGlzIGFsc28gc2FmZSB0byB1c2UgdGhlIA0Kbmlja25hbWUgb2YgYW4gRkdM
LXNhZmUgUkJyaWRnZSBhcyB0aGUgcm9vdCBvZiBhbiBGR0wgRC10cmVlLCBpZiB0aGlzIA0KUmJy
aWRnZSBoYXMgYW5ub3VuY2VkIGl0cyBGR0wtc2FmZXR5IGluIFRSSUxMIGNhbXB1cy4gSXMgaXQg
cmlnaHQ/DQoNCklmIEkgYW0gd3JvbmcsIHBsZWFzZSBjb3JyZWN0IG1lLg0KDQpCZXN0IFJlZ2Fy
ZHMsDQpaaGFpIEhvbmdqdW4NCiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIi
IiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiINCiBQcm90b2NvbCBEZXZlbG9wbWVudCBE
ZXB0LlZJLCBDZW50cmFsIFImRCBJbnN0aXR1dGUsIFpURSBDb3Jwb3JhdGlvbg0KIE5vLiA2OCwg
WmlqaW5naHVhIFJvYWQsIFl1aHVhdGFpIERpc3RyaWN0LCBOYW5qaW5nLCBQLlIuQ2hpbmEsIDIx
MDAxMg0KIA0KIFpoYWkgSG9uZ2p1bg0KIA0KIFRlbDogKzg2LTI1LTUyODc3MzQ1DQogRW1haWw6
IHpoYWkuaG9uZ2p1bkB6dGUuY29tLmNuDQoiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIi
IiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIiIg0KDQoNCg0KDQoNCkRvbmFs
ZCBFYXN0bGFrZSA8ZDNlM2UzQGdtYWlsLmNvbT4gDQq3orz+yMs6ICB0cmlsbC1ib3VuY2VzQGll
dGYub3JnDQoyMDEzLTAyLTE0IDA5OjA3DQoNCsrVvP7Iyw0KdHJpbGxAaWV0Zi5vcmcNCrOty80N
Cg0K1vfM4g0KUmU6IFt0cmlsbF0gSS1EIEFjdGlvbjogZHJhZnQtaWV0Zi10cmlsbC1maW5lLWxh
YmVsaW5nLTA1LnR4dA0KDQoNCg0KDQoNCg0KVGhpcyB2ZXJzaW9uIGlzIGludGVuZGVkIHRvIGNv
cnBvcmF0ZSB0d2Vha2VkIG9wdGlvbiAyIGFzIHBlciB0aGUNCmZvbGxvd2luZyBtZXNzYWdlDQpo
dHRwOi8vd3d3LmlldGYub3JnL21haWwtYXJjaGl2ZS93ZWIvdHJpbGwvY3VycmVudC9tc2cwNTYz
My5odG1sDQoNClRoYW5rcywNCkRvbmFsZA0KPT09PT09PT09PT09PT09PT09PT09PT09PT09PT0N
CiBEb25hbGQgRS4gRWFzdGxha2UgM3JkICAgKzEtNTA4LTMzMy0yMjcwIChjZWxsKQ0KIDE1NSBC
ZWF2ZXIgU3RyZWV0LCBNaWxmb3JkLCBNQSAwMTc1NyBVU0ENCiBkM2UzZTNAZ21haWwuY29tDQoN
Ck9uIFdlZCwgRmViIDEzLCAyMDEzIGF0IDM6MjEgUE0sICA8aW50ZXJuZXQtZHJhZnRzQGlldGYu
b3JnPiB3cm90ZToNCj4NCj4gQSBOZXcgSW50ZXJuZXQtRHJhZnQgaXMgYXZhaWxhYmxlIGZyb20g
dGhlIG9uLWxpbmUgSW50ZXJuZXQtRHJhZnRzIA0KZGlyZWN0b3JpZXMuDQo+ICBUaGlzIGRyYWZ0
IGlzIGEgd29yayBpdGVtIG9mIHRoZSBUcmFuc3BhcmVudCBJbnRlcmNvbm5lY3Rpb24gb2YgTG90
cyBvZiANCkxpbmtzIFdvcmtpbmcgR3JvdXAgb2YgdGhlIElFVEYuDQo+DQo+ICAgICAgICAgVGl0
bGUgICAgICAgICAgIDogVFJJTEwgKFRyYW5zcGFyZW50IEludGVyY29ubmVjdGlvbiBvZiBMb3Rz
IG9mIA0KTGlua3MpOiBGaW5lLUdyYWluZWQgTGFiZWxpbmcNCj4gICAgICAgICBBdXRob3Iocykg
ICAgICAgOiBEb25hbGQgRWFzdGxha2UNCj4gICAgICAgICAgICAgICAgICAgICAgICAgICBNaW5n
dWkgWmhhbmcNCj4gICAgICAgICAgICAgICAgICAgICAgICAgICBQdW5lZXQgQWdhcndhbA0KPiAg
ICAgICAgICAgICAgICAgICAgICAgICAgIFJhZGlhIFBlcmxtYW4NCj4gICAgICAgICAgICAgICAg
ICAgICAgICAgICBEaW5lc2ggRy4gRHV0dA0KPiAgICAgICAgIEZpbGVuYW1lICAgICAgICA6IGRy
YWZ0LWlldGYtdHJpbGwtZmluZS1sYWJlbGluZy0wNS50eHQNCj4gICAgICAgICBQYWdlcyAgICAg
ICAgICAgOiAzMQ0KPiAgICAgICAgIERhdGUgICAgICAgICAgICA6IDIwMTMtMDItMTMNCj4NCj4g
QWJzdHJhY3Q6DQo+ICAgIFRoZSBJRVRGIGhhcyBzdGFuZGFyZGl6ZWQgVFJJTEwgKFRyYW5zcGFy
ZW50IEludGVyY29ubmVjdGlvbiBvZiBMb3RzDQo+ICAgIG9mIExpbmtzKSwgYSBwcm90b2NvbCBm
b3IgbGVhc3QgY29zdCB0cmFuc3BhcmVudCBmcmFtZSByb3V0aW5nIGluDQo+ICAgIG11bHRpLWhv
cCBuZXR3b3JrcyB3aXRoIGFyYml0cmFyeSB0b3BvbG9naWVzIGFuZCBsaW5rIHRlY2hub2xvZ2ll
cywNCj4gICAgdXNpbmcgbGluay1zdGF0ZSByb3V0aW5nIGFuZCBhIGhvcCBjb3VudC4gVGhlIFRS
SUxMIGJhc2UgcHJvdG9jb2wNCj4gICAgc3RhbmRhcmQgc3VwcG9ydHMgbGFiZWxpbmcgb2YgVFJJ
TEwgZGF0YSB3aXRoIHVwIHRvIDRLIElEcy4gSG93ZXZlciwNCj4gICAgdGhlcmUgYXJlIGFwcGxp
Y2F0aW9ucyB0aGF0IHJlcXVpcmUgbW9yZSBmaW5lLWdyYWluZWQgbGFiZWxpbmcgb2YNCj4gICAg
ZGF0YS4gVGhpcyBkb2N1bWVudCB1cGRhdGVzIFJGQyA2MzI1IGJ5IHNwZWNpZnlpbmcgb3B0aW9u
YWwNCj4gICAgZXh0ZW5zaW9ucyB0byB0aGUgVFJJTEwgYmFzZSBwcm90b2NvbCB0byBzYWZlbHkg
YWNjb21wbGlzaCB0aGlzLg0KPg0KPg0KPg0KPiBUaGUgSUVURiBkYXRhdHJhY2tlciBzdGF0dXMg
cGFnZSBmb3IgdGhpcyBkcmFmdCBpczoNCj4gaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9k
b2MvZHJhZnQtaWV0Zi10cmlsbC1maW5lLWxhYmVsaW5nDQo+DQo+IFRoZXJlJ3MgYWxzbyBhIGh0
bWxpemVkIHZlcnNpb24gYXZhaWxhYmxlIGF0Og0KPiBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRt
bC9kcmFmdC1pZXRmLXRyaWxsLWZpbmUtbGFiZWxpbmctMDUNCj4NCj4gQSBkaWZmIGZyb20gdGhl
IHByZXZpb3VzIHZlcnNpb24gaXMgYXZhaWxhYmxlIGF0Og0KPiBodHRwOi8vd3d3LmlldGYub3Jn
L3JmY2RpZmY/dXJsMj1kcmFmdC1pZXRmLXRyaWxsLWZpbmUtbGFiZWxpbmctMDUNCj4NCj4NCj4g
SW50ZXJuZXQtRHJhZnRzIGFyZSBhbHNvIGF2YWlsYWJsZSBieSBhbm9ueW1vdXMgRlRQIGF0Og0K
PiBmdHA6Ly9mdHAuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzLw0KPg0KPiBfX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiB0cmlsbCBtYWlsaW5nIGxpc3QN
Cj4gdHJpbGxAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by90cmlsbA0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N
CnRyaWxsIG1haWxpbmcgbGlzdA0KdHJpbGxAaWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYub3Jn
L21haWxtYW4vbGlzdGluZm8vdHJpbGwNCg0KDQo=
--=_alternative 0023399C48257B1D_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkhpIERvbmFsZCw8L2ZvbnQ+DQo8
YnI+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkFjY29yZGluZyB0byB0aGUg
Y3VycmVudCBGR0wgZHJhZnQsDQp0aGUgcm9vdCBmb3IgYW4gRkdMIEQtdHJlZSBjYW4gb25seSBi
ZSB0aGUgbmlja25hbWUgaGVsZCBieSBhbiBGR0wgUkJyaWRnZQ0Kb3IgYSBwc2V1ZG9ub2RlIHJl
cHJlc2VudGluZyBhIEZHTCBsaW5rLjwvZm9udD4NCjxicj4NCjxicj48Zm9udCBzaXplPTIgZmFj
ZT0ic2Fucy1zZXJpZiI+SG93ZXZlciwgc2luY2UgYW4gRkdMLXNhZmUgY2FuIGNhbGN1bGF0ZQ0K
RkdMIEQtdHJlZXMgY29ycmVjdGx5IGFuZCBmb3J3YXJkIG11bHRpLWRlc3RpYXRpb24gRkdMIHBh
Y2t0ZXMgc2FmZWx5LA0KSSB0aGluayBpdCBpcyBhbHNvIHNhZmUgdG8gdXNlIHRoZSBuaWNrbmFt
ZSBvZiBhbiBGR0wtc2FmZSBSQnJpZGdlIGFzIHRoZQ0Kcm9vdCBvZiBhbiBGR0wgRC10cmVlLCBp
ZiB0aGlzIFJicmlkZ2UgaGFzIGFubm91bmNlZCBpdHMgRkdMLXNhZmV0eSBpbg0KVFJJTEwgY2Ft
cHVzLiBJcyBpdCByaWdodD88L2ZvbnQ+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNh
bnMtc2VyaWYiPklmIEkgYW0gd3JvbmcsIHBsZWFzZSBjb3JyZWN0IG1lLjwvZm9udD4NCjxicj48
Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KQmVzdCBSZWdhcmRzLDxicj4NClpo
YWkgSG9uZ2p1bjxicj4NCiZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90
OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZx
dW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90
OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZx
dW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90
OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZx
dW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90
OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90Ozxicj4NCiBQcm90b2NvbCBEZXZl
bG9wbWVudCBEZXB0LlZJLCBDZW50cmFsIFImYW1wO0QgSW5zdGl0dXRlLCBaVEUgQ29ycG9yYXRp
b248YnI+DQogTm8uIDY4LCBaaWppbmdodWEgUm9hZCwgWXVodWF0YWkgRGlzdHJpY3QsIE5hbmpp
bmcsIFAuUi5DaGluYSwgMjEwMDEyPGJyPg0KIDxicj4NCiBaaGFpIEhvbmdqdW48YnI+DQogPGJy
Pg0KIFRlbDogKzg2LTI1LTUyODc3MzQ1PGJyPg0KIEVtYWlsOiB6aGFpLmhvbmdqdW5AenRlLmNv
bS5jbjxicj4NCiZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90
OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZx
dW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90
OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZx
dW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90
OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZx
dW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90
OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90OyZxdW90Ozxicj4NCjxicj4NCjwvZm9udD4N
Cjxicj4NCjxicj4NCjxicj4NCjx0YWJsZSB3aWR0aD0xMDAlPg0KPHRyIHZhbGlnbj10b3A+DQo8
dGQgd2lkdGg9MzYlPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj48Yj5Eb25hbGQgRWFz
dGxha2UgJmx0O2QzZTNlM0BnbWFpbC5jb20mZ3Q7PC9iPg0KPC9mb250Pg0KPGJyPjxmb250IHNp
emU9MSBmYWNlPSJzYW5zLXNlcmlmIj63orz+yMs6ICZuYnNwO3RyaWxsLWJvdW5jZXNAaWV0Zi5v
cmc8L2ZvbnQ+DQo8cD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+MjAxMy0wMi0xNCAw
OTowNzwvZm9udD4NCjx0ZCB3aWR0aD02MyU+DQo8dGFibGUgd2lkdGg9MTAwJT4NCjx0ciB2YWxp
Z249dG9wPg0KPHRkPg0KPGRpdiBhbGlnbj1yaWdodD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1z
ZXJpZiI+ytW8/sjLPC9mb250PjwvZGl2Pg0KPHRkPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNl
cmlmIj50cmlsbEBpZXRmLm9yZzwvZm9udD4NCjx0ciB2YWxpZ249dG9wPg0KPHRkPg0KPGRpdiBh
bGlnbj1yaWdodD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+s63LzTwvZm9udD48L2Rp
dj4NCjx0ZD4NCjx0ciB2YWxpZ249dG9wPg0KPHRkPg0KPGRpdiBhbGlnbj1yaWdodD48Zm9udCBz
aXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+1vfM4jwvZm9udD48L2Rpdj4NCjx0ZD48Zm9udCBzaXpl
PTEgZmFjZT0ic2Fucy1zZXJpZiI+UmU6IFt0cmlsbF0gSS1EIEFjdGlvbjogZHJhZnQtaWV0Zi10
cmlsbC1maW5lLWxhYmVsaW5nLTA1LnR4dDwvZm9udD48L3RhYmxlPg0KPGJyPg0KPHRhYmxlPg0K
PHRyIHZhbGlnbj10b3A+DQo8dGQ+DQo8dGQ+PC90YWJsZT4NCjxicj48L3RhYmxlPg0KPGJyPg0K
PGJyPg0KPGJyPjx0dD48Zm9udCBzaXplPTI+VGhpcyB2ZXJzaW9uIGlzIGludGVuZGVkIHRvIGNv
cnBvcmF0ZSB0d2Vha2VkIG9wdGlvbg0KMiBhcyBwZXIgdGhlPGJyPg0KZm9sbG93aW5nIG1lc3Nh
Z2U8YnI+DQpodHRwOi8vd3d3LmlldGYub3JnL21haWwtYXJjaGl2ZS93ZWIvdHJpbGwvY3VycmVu
dC9tc2cwNTYzMy5odG1sPGJyPg0KPGJyPg0KVGhhbmtzLDxicj4NCkRvbmFsZDxicj4NCj09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PGJyPg0KIERvbmFsZCBFLiBFYXN0bGFrZSAzcmQgJm5i
c3A7ICsxLTUwOC0zMzMtMjI3MCAoY2VsbCk8YnI+DQogMTU1IEJlYXZlciBTdHJlZXQsIE1pbGZv
cmQsIE1BIDAxNzU3IFVTQTxicj4NCiBkM2UzZTNAZ21haWwuY29tPGJyPg0KPGJyPg0KT24gV2Vk
LCBGZWIgMTMsIDIwMTMgYXQgMzoyMSBQTSwgJm5ic3A7Jmx0O2ludGVybmV0LWRyYWZ0c0BpZXRm
Lm9yZyZndDsNCndyb3RlOjxicj4NCiZndDs8YnI+DQomZ3Q7IEEgTmV3IEludGVybmV0LURyYWZ0
IGlzIGF2YWlsYWJsZSBmcm9tIHRoZSBvbi1saW5lIEludGVybmV0LURyYWZ0cw0KZGlyZWN0b3Jp
ZXMuPGJyPg0KJmd0OyAmbmJzcDtUaGlzIGRyYWZ0IGlzIGEgd29yayBpdGVtIG9mIHRoZSBUcmFu
c3BhcmVudCBJbnRlcmNvbm5lY3Rpb24NCm9mIExvdHMgb2YgTGlua3MgV29ya2luZyBHcm91cCBv
ZiB0aGUgSUVURi48YnI+DQomZ3Q7PGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgVGl0bGUgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOw0KOiBUUklMTCAoVHJh
bnNwYXJlbnQgSW50ZXJjb25uZWN0aW9uIG9mIExvdHMgb2YgTGlua3MpOiBGaW5lLUdyYWluZWQg
TGFiZWxpbmc8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBBdXRob3Iocykg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgOiBEb25hbGQNCkVhc3RsYWtlPGJyPg0KJmd0OyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsNCiZuYnNwOyAmbmJzcDsgJm5ic3A7IE1pbmd1aSBaaGFuZzxicj4NCiZndDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7DQombmJzcDsgJm5ic3A7ICZuYnNwOyBQdW5lZXQgQWdhcndhbDxicj4NCiZndDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7DQombmJzcDsgJm5ic3A7ICZuYnNwOyBSYWRpYSBQZXJsbWFuPGJyPg0KJmd0OyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsNCiZuYnNwOyAmbmJzcDsgJm5ic3A7IERpbmVzaCBHLiBEdXR0PGJyPg0KJmd0
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgRmlsZW5hbWUgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7Og0KZHJhZnQtaWV0Zi10cmlsbC1maW5lLWxhYmVsaW5nLTA1LnR4dDxicj4NCiZn
dDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IFBhZ2VzICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsNCjogMzE8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyBEYXRlICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsNCiZuYnNwOzogMjAxMy0w
Mi0xMzxicj4NCiZndDs8YnI+DQomZ3Q7IEFic3RyYWN0Ojxicj4NCiZndDsgJm5ic3A7ICZuYnNw
O1RoZSBJRVRGIGhhcyBzdGFuZGFyZGl6ZWQgVFJJTEwgKFRyYW5zcGFyZW50IEludGVyY29ubmVj
dGlvbg0Kb2YgTG90czxicj4NCiZndDsgJm5ic3A7ICZuYnNwO29mIExpbmtzKSwgYSBwcm90b2Nv
bCBmb3IgbGVhc3QgY29zdCB0cmFuc3BhcmVudCBmcmFtZQ0Kcm91dGluZyBpbjxicj4NCiZndDsg
Jm5ic3A7ICZuYnNwO211bHRpLWhvcCBuZXR3b3JrcyB3aXRoIGFyYml0cmFyeSB0b3BvbG9naWVz
IGFuZCBsaW5rDQp0ZWNobm9sb2dpZXMsPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7dXNpbmcgbGlu
ay1zdGF0ZSByb3V0aW5nIGFuZCBhIGhvcCBjb3VudC4gVGhlIFRSSUxMIGJhc2UNCnByb3RvY29s
PGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7c3RhbmRhcmQgc3VwcG9ydHMgbGFiZWxpbmcgb2YgVFJJ
TEwgZGF0YSB3aXRoIHVwIHRvIDRLDQpJRHMuIEhvd2V2ZXIsPGJyPg0KJmd0OyAmbmJzcDsgJm5i
c3A7dGhlcmUgYXJlIGFwcGxpY2F0aW9ucyB0aGF0IHJlcXVpcmUgbW9yZSBmaW5lLWdyYWluZWQN
CmxhYmVsaW5nIG9mPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7ZGF0YS4gVGhpcyBkb2N1bWVudCB1
cGRhdGVzIFJGQyA2MzI1IGJ5IHNwZWNpZnlpbmcgb3B0aW9uYWw8YnI+DQomZ3Q7ICZuYnNwOyAm
bmJzcDtleHRlbnNpb25zIHRvIHRoZSBUUklMTCBiYXNlIHByb3RvY29sIHRvIHNhZmVseSBhY2Nv
bXBsaXNoDQp0aGlzLjxicj4NCiZndDs8YnI+DQomZ3Q7PGJyPg0KJmd0Ozxicj4NCiZndDsgVGhl
IElFVEYgZGF0YXRyYWNrZXIgc3RhdHVzIHBhZ2UgZm9yIHRoaXMgZHJhZnQgaXM6PGJyPg0KJmd0
OyBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLXRyaWxsLWZpbmUt
bGFiZWxpbmc8YnI+DQomZ3Q7PGJyPg0KJmd0OyBUaGVyZSdzIGFsc28gYSBodG1saXplZCB2ZXJz
aW9uIGF2YWlsYWJsZSBhdDo8YnI+DQomZ3Q7IGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2Ry
YWZ0LWlldGYtdHJpbGwtZmluZS1sYWJlbGluZy0wNTxicj4NCiZndDs8YnI+DQomZ3Q7IEEgZGlm
ZiBmcm9tIHRoZSBwcmV2aW91cyB2ZXJzaW9uIGlzIGF2YWlsYWJsZSBhdDo8YnI+DQomZ3Q7IGh0
dHA6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRyYWZ0LWlldGYtdHJpbGwtZmluZS1sYWJl
bGluZy0wNTxicj4NCiZndDs8YnI+DQomZ3Q7PGJyPg0KJmd0OyBJbnRlcm5ldC1EcmFmdHMgYXJl
IGFsc28gYXZhaWxhYmxlIGJ5IGFub255bW91cyBGVFAgYXQ6PGJyPg0KJmd0OyBmdHA6Ly9mdHAu
aWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzLzxicj4NCiZndDs8YnI+DQomZ3Q7IF9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0KJmd0OyB0cmlsbCBtYWls
aW5nIGxpc3Q8YnI+DQomZ3Q7IHRyaWxsQGlldGYub3JnPGJyPg0KJmd0OyBodHRwczovL3d3dy5p
ZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3RyaWxsPGJyPg0KX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQp0cmlsbCBtYWlsaW5nIGxpc3Q8YnI+DQp0
cmlsbEBpZXRmLm9yZzxicj4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8v
dHJpbGw8YnI+DQo8L2ZvbnQ+PC90dD4NCjxicj4NCg==
--=_alternative 0023399C48257B1D_=--

From d3e3e3@gmail.com  Sun Feb 24 22:24:25 2013
Return-Path: <d3e3e3@gmail.com>
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 4041321F91D3 for <trill@ietfa.amsl.com>; Sun, 24 Feb 2013 22:24:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.566
X-Spam-Level: 
X-Spam-Status: No, score=-101.566 tagged_above=-999 required=5 tests=[AWL=-1.814, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_LOW=-1, 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 6QhTURz1QZ7F for <trill@ietfa.amsl.com>; Sun, 24 Feb 2013 22:24:24 -0800 (PST)
Received: from mail-ob0-f178.google.com (mail-ob0-f178.google.com [209.85.214.178]) by ietfa.amsl.com (Postfix) with ESMTP id 3F19921F91D1 for <trill@ietf.org>; Sun, 24 Feb 2013 22:24:23 -0800 (PST)
Received: by mail-ob0-f178.google.com with SMTP id wd20so2450413obb.23 for <trill@ietf.org>; Sun, 24 Feb 2013 22:24:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=udktM2ZK3nyiOhZ5QlwUvWF6oNEbdcB4fJhC+7L+e7o=; b=FOs4QuDqgyOn3LEGTLu9HwI5kaXky2o3PjhWgM6pQxUWCkdUTwLpephP0aMFh8YCZp LvVH3DgoOOsmGqutIQSZyGzJoN1SVDi4I/UvivgazvxprzcWF5vWQhRLWlG3s3DBzXEG LuTZePXPe8rLsCESCsr4uaix+5MLLDOLzSPlQDvfJ4wXJ/5LEclPoOTmEm7Yaoze2tqP 0Fa9Efz5LmKWimNWdrnh9HQzcbkEDstsGTjyWlC2D0DndXzeSJ3g2XTWSNUEj3wO91Df qT8uXtdQMOf82jkxFA4GZh1FiHNe7ttM6xGhZxv7Cx+wVLL/W6GAaQrhzqTGGykIP+1w KvKQ==
X-Received: by 10.60.22.34 with SMTP id a2mr6451218oef.97.1361773462587; Sun, 24 Feb 2013 22:24:22 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.98.168 with HTTP; Sun, 24 Feb 2013 22:24:01 -0800 (PST)
In-Reply-To: <OF72244E02.B708C7CB-ON48257B1D.00210B67-48257B1D.002339A4@zte.com.cn>
References: <CAF4+nEHWwz4N0pd7OaBVcp4BiHLByy+SvsCpC1G8w+yGjdsS_w@mail.gmail.com> <OF72244E02.B708C7CB-ON48257B1D.00210B67-48257B1D.002339A4@zte.com.cn>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 25 Feb 2013 01:24:01 -0500
Message-ID: <CAF4+nEHwE5w2E+Sf-Qta3t+L9SiQ=vnYJO+aTiZGG89kkjEDig@mail.gmail.com>
To: zhai.hongjun@zte.com.cn
Content-Type: multipart/alternative; boundary=e89a8fb205e48096c304d68697b7
Cc: trill@ietf.org
Subject: Re: [trill] I-D Action: draft-ietf-trill-fine-labeling-05.txt
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: Mon, 25 Feb 2013 06:24:25 -0000

--e89a8fb205e48096c304d68697b7
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

Hi Hongjun,

Yes, you are right. But "FGL" and "FGL-safe" mean exactly the same thing.
All "FGL-safe" TRILL switches are FGL TRILL switches.

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com


On Mon, Feb 25, 2013 at 1:20 AM, <zhai.hongjun@zte.com.cn> wrote:

>
> Hi Donald,
>
> According to the current FGL draft, the root for an FGL D-tree can only b=
e
> the nickname held by an FGL RBridge or a pseudonode representing a FGL li=
nk.
>
> However, since an FGL-safe can calculate FGL D-trees correctly and forwar=
d
> multi-destiation FGL packtes safely, I think it is also safe to use the
> nickname of an FGL-safe RBridge as the root of an FGL D-tree, if this
> Rbridge has announced its FGL-safety in TRILL campus. Is it right?
>
> If I am wrong, please correct me.
>
> 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
> """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
>
>
>
>
>  *Donald Eastlake <d3e3e3@gmail.com>*
> =B7=A2=BC=FE=C8=CB:  trill-bounces@ietf.org
>
> 2013-02-14 09:07
>   =CA=D5=BC=FE=C8=CB
> trill@ietf.org
> =B3=AD=CB=CD
>   =D6=F7=CC=E2
> Re: [trill] I-D Action: draft-ietf-trill-fine-labeling-05.txt
>
>
>
>
> This version is intended to corporate tweaked option 2 as per the
> following message
> http://www.ietf.org/mail-archive/web/trill/current/msg05633.html
>
> Thanks,
> Donald
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
> Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
> 155 Beaver Street, Milford, MA 01757 USA
> d3e3e3@gmail.com
>
> On Wed, Feb 13, 2013 at 3:21 PM,  <internet-drafts@ietf.org> wrote:
> >
> > 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 o=
f
> Links Working Group of the IETF.
> >
> >         Title           : TRILL (Transparent Interconnection of Lots of
> Links): Fine-Grained Labeling
> >         Author(s)       : Donald Eastlake
> >                           Mingui Zhang
> >                           Puneet Agarwal
> >                           Radia Perlman
> >                           Dinesh G. Dutt
> >         Filename        : draft-ietf-trill-fine-labeling-05.txt
> >         Pages           : 31
> >         Date            : 2013-02-13
> >
> > Abstract:
> >    The IETF has standardized TRILL (Transparent Interconnection of Lots
> >    of Links), a protocol for least cost transparent frame routing in
> >    multi-hop networks with arbitrary topologies and link technologies,
> >    using link-state routing and a hop count. The TRILL base protocol
> >    standard supports labeling of TRILL data with up to 4K IDs. However,
> >    there are applications that require more fine-grained labeling of
> >    data. This document updates RFC 6325 by specifying optional
> >    extensions to the TRILL base protocol to safely accomplish this.
> >
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-trill-fine-labeling
> >
> > There's also a htmlized version available at:
> > http://tools.ietf.org/html/draft-ietf-trill-fine-labeling-05
> >
> > A diff from the previous version is available at:
> > http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-trill-fine-labeling-05
> >
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > 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
>
>

--e89a8fb205e48096c304d68697b7
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: quoted-printable

Hi Hongjun,<div><br></div><div>Yes, you are right. But &quot;FGL&quot; and =
&quot;FGL-safe&quot; mean exactly the same thing. All &quot;FGL-safe&quot; =
TRILL switches are FGL TRILL switches.<div><br clear=3D"all"><div>Thanks,<b=
r>

Donald<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D<br>&nbsp;Donald E. Eastlake 3rd&nbsp;&nbsp; +1-508=
-333-2270 (cell)<br>&nbsp;155 Beaver Street,&nbsp;Milford, MA 01757 USA<br>=
&nbsp;<a href=3D"mailto:d3e3e3@gmail.com" target=3D"_blank">d3e3e3@gmail.co=
m</a></div>
<br><br><div class=3D"gmail_quote">On Mon, Feb 25, 2013 at 1:20 AM,  <span =
dir=3D"ltr">&lt;<a href=3D"mailto:zhai.hongjun@zte.com.cn" target=3D"_blank=
">zhai.hongjun@zte.com.cn</a>&gt;</span> wrote:<br><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">


<br><font face=3D"sans-serif">Hi Donald,</font>
<br>
<br><font face=3D"sans-serif">According to the current FGL draft,
the root for an FGL D-tree can only be the nickname held by an FGL RBridge
or a pseudonode representing a FGL link.</font>
<br>
<br><font face=3D"sans-serif">However, since an FGL-safe can calculate
FGL D-trees correctly and forward multi-destiation FGL packtes safely,
I think it is also safe to use the nickname of an FGL-safe RBridge as the
root of an FGL D-tree, if this Rbridge has announced its FGL-safety in
TRILL campus. Is it right?</font>
<br>
<br><font face=3D"sans-serif">If I am wrong, please correct me.</font>
<br><font face=3D"sans-serif"><br>
Best Regards,<br>
Zhai Hongjun<br>
&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&qu=
ot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;=
&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&qu=
ot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;=
&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&qu=
ot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;<br>


 Protocol Development Dept.VI, Central R&amp;D Institute, ZTE Corporation<b=
r>
 No. 68, Zijinghua Road, Yuhuatai District, Nanjing, P.R.China, 210012<br>
 <br>
 Zhai Hongjun<br>
 <br>
 Tel: <a href=3D"tel:%2B86-25-52877345" value=3D"+862552877345" target=3D"_=
blank">+86-25-52877345</a><br>
 Email: <a href=3D"mailto:zhai.hongjun@zte.com.cn" target=3D"_blank">zhai.h=
ongjun@zte.com.cn</a><br>
&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&qu=
ot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;=
&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&qu=
ot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;=
&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&qu=
ot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;&quot;<br>


<br>
</font>
<br>
<br>
<br>
<p></p><table width=3D"100%">
<tbody><tr valign=3D"top">
<td width=3D"36%"><font size=3D"1" face=3D"sans-serif"><b>Donald Eastlake &=
lt;<a href=3D"mailto:d3e3e3@gmail.com" target=3D"_blank">d3e3e3@gmail.com</=
a>&gt;</b>
</font>
<br><font size=3D"1" face=3D"sans-serif">=B7=A2=BC=FE=C8=CB: &nbsp;<a href=
=3D"mailto:trill-bounces@ietf.org" target=3D"_blank">trill-bounces@ietf.org=
</a></font>
<p><font size=3D"1" face=3D"sans-serif">2013-02-14 09:07</font>
</p></td><td width=3D"63%">
<table width=3D"100%">
<tbody><tr valign=3D"top">
<td>
<div align=3D"right"><font size=3D"1" face=3D"sans-serif">=CA=D5=BC=FE=C8=
=CB</font></div>
</td><td><font size=3D"1" face=3D"sans-serif"><a href=3D"mailto:trill@ietf.=
org" target=3D"_blank">trill@ietf.org</a></font>
</td></tr><tr valign=3D"top">
<td>
<div align=3D"right"><font size=3D"1" face=3D"sans-serif">=B3=AD=CB=CD</fon=
t></div>
</td><td>
</td></tr><tr valign=3D"top">
<td>
<div align=3D"right"><font size=3D"1" face=3D"sans-serif">=D6=F7=CC=E2</fon=
t></div>
</td><td><font size=3D"1" face=3D"sans-serif">Re: [trill] I-D Action: draft=
-ietf-trill-fine-labeling-05.txt</font></td></tr></tbody></table>
<br>
<table>
<tbody><tr valign=3D"top">
<td>
</td><td></td></tr></tbody></table>
<br></td></tr></tbody></table>
<br>
<br><div class=3D"HOEnZb"><div class=3D"h5">
<br><tt><font>This version is intended to corporate tweaked option
2 as per the<br>
following message<br>
<a href=3D"http://www.ietf.org/mail-archive/web/trill/current/msg05633.html=
" target=3D"_blank">http://www.ietf.org/mail-archive/web/trill/current/msg0=
5633.html</a><br>
<br>
Thanks,<br>
Donald<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D<br>
 Donald E. Eastlake 3rd &nbsp; <a href=3D"tel:%2B1-508-333-2270" value=3D"+=
15083332270" target=3D"_blank">+1-508-333-2270</a> (cell)<br>
 155 Beaver Street, Milford, MA 01757 USA<br>
 <a href=3D"mailto:d3e3e3@gmail.com" target=3D"_blank">d3e3e3@gmail.com</a>=
<br>
<br>
On Wed, Feb 13, 2013 at 3:21 PM, &nbsp;&lt;<a href=3D"mailto:internet-draft=
s@ietf.org" target=3D"_blank">internet-drafts@ietf.org</a>&gt;
wrote:<br>
&gt;<br>
&gt; A New Internet-Draft is available from the on-line Internet-Drafts
directories.<br>
&gt; &nbsp;This draft is a work item of the Transparent Interconnection
of Lots of Links Working Group of the IETF.<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; Title &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
: TRILL (Transparent Interconnection of Lots of Links): Fine-Grained Labeli=
ng<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; Author(s) &nbsp; &nbsp; &nbsp; : Donald
Eastlake<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; Mingui Zhang<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; Puneet Agarwal<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; Radia Perlman<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; Dinesh G. Dutt<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; Filename &nbsp; &nbsp; &nbsp; &nbsp;:
draft-ietf-trill-fine-labeling-05.txt<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; Pages &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
: 31<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; Date &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp;: 2013-02-13<br>
&gt;<br>
&gt; Abstract:<br>
&gt; &nbsp; &nbsp;The IETF has standardized TRILL (Transparent Interconnect=
ion
of Lots<br>
&gt; &nbsp; &nbsp;of Links), a protocol for least cost transparent frame
routing in<br>
&gt; &nbsp; &nbsp;multi-hop networks with arbitrary topologies and link
technologies,<br>
&gt; &nbsp; &nbsp;using link-state routing and a hop count. The TRILL base
protocol<br>
&gt; &nbsp; &nbsp;standard supports labeling of TRILL data with up to 4K
IDs. However,<br>
&gt; &nbsp; &nbsp;there are applications that require more fine-grained
labeling of<br>
&gt; &nbsp; &nbsp;data. This document updates RFC 6325 by specifying option=
al<br>
&gt; &nbsp; &nbsp;extensions to the TRILL base protocol to safely accomplis=
h
this.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; The IETF datatracker status page for this draft is:<br>
&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-trill-fine-labe=
ling" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-trill-f=
ine-labeling</a><br>
&gt;<br>
&gt; There&#39;s also a htmlized version available at:<br>
&gt; <a href=3D"http://tools.ietf.org/html/draft-ietf-trill-fine-labeling-0=
5" target=3D"_blank">http://tools.ietf.org/html/draft-ietf-trill-fine-label=
ing-05</a><br>
&gt;<br>
&gt; A diff from the previous version is available at:<br>
&gt; <a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-trill-fine-la=
beling-05" target=3D"_blank">http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-=
trill-fine-labeling-05</a><br>
&gt;<br>
&gt;<br>
&gt; Internet-Drafts are also available by anonymous FTP at:<br>
&gt; <a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp:=
//ftp.ietf.org/internet-drafts/</a><br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; trill mailing list<br>
&gt; <a href=3D"mailto:trill@ietf.org" target=3D"_blank">trill@ietf.org</a>=
<br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/trill" target=3D"_bla=
nk">https://www.ietf.org/mailman/listinfo/trill</a><br>
_______________________________________________<br>
trill mailing list<br>
<a href=3D"mailto:trill@ietf.org" target=3D"_blank">trill@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/trill" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/trill</a><br>
</font></tt>
<br>
</div></div></blockquote></div><br></div></div>

--e89a8fb205e48096c304d68697b7--

From d3e3e3@gmail.com  Mon Feb 25 09:01:23 2013
Return-Path: <d3e3e3@gmail.com>
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 CC0D221F9593 for <trill@ietfa.amsl.com>; Mon, 25 Feb 2013 09:01:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.289
X-Spam-Level: 
X-Spam-Status: No, score=-102.289 tagged_above=-999 required=5 tests=[AWL=-0.990, BAYES_00=-2.599, MANGLED_LIST=2.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 OP76HxR5GLjI for <trill@ietfa.amsl.com>; Mon, 25 Feb 2013 09:01:22 -0800 (PST)
Received: from mail-ob0-f174.google.com (mail-ob0-f174.google.com [209.85.214.174]) by ietfa.amsl.com (Postfix) with ESMTP id 2DD6521F9563 for <trill@ietf.org>; Mon, 25 Feb 2013 09:01:08 -0800 (PST)
Received: by mail-ob0-f174.google.com with SMTP id 16so3094733obc.5 for <trill@ietf.org>; Mon, 25 Feb 2013 09:01:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=1LldWr8Mmo8rbZeF3U126Yh4sdR5TQza/A9S4To+UgM=; b=BfoKR5NarB9x2yGFZXz1chtUvsbgFb1QNSb2iTqsc8J2brW8foy3gG6Bq16kx3MmL7 LWDP+qmUSoYzP0Y6eb2jBN6jfAJRMjP70wawtdvLr0wQs/pIAO53WVy6Z6WjQwzdoJnN /lViRKwkU0GAEcGHDXn9CYuOdxyWz0AQx2/IHDC4u2vQo2AuHZfUboRxiSOOE5lG1y0J dRDtgfO2VF/Xa+Cb62o/UuW0rdW09uVVz74uWrgbdPc9bdqPXNyS4MrMa3o7WaLK0SEP sNFqjRJ2tMK9eUgkVFgrdAX3Tk4j8cvYWcrnmvWJMrdW+hYPwMVmqdDlGxUQQCtTFTz+ pVCQ==
X-Received: by 10.60.20.129 with SMTP id n1mr4755143oee.39.1361811667598; Mon, 25 Feb 2013 09:01:07 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.98.168 with HTTP; Mon, 25 Feb 2013 09:00:47 -0800 (PST)
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71284D3FF0C@MX15A.corp.emc.com>
References: <CAF4+nEH9_MkMTDDG7jn_xipXV-feu4Xy0GyH9NyNO_5EaNw3nQ@mail.gmail.com> <50A4095E.80009@acm.org> <8D3D17ACE214DC429325B2B98F3AE71284D3FF0C@MX15A.corp.emc.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 25 Feb 2013 12:00:47 -0500
Message-ID: <CAF4+nEHO2TijzjgCCSP0XMcjaWtsuhMUdY2Lveos6YgO1QhtTA@mail.gmail.com>
To: "Black, David" <david.black@emc.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] WG Last Call: draft-ietf-trill-directory-framework-01.txt
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: Mon, 25 Feb 2013 17:01:24 -0000

Hi David,

Thanks for pointing out your earlier review and comments which were
partially responded to at the time.

I understand that you comments were on the -02 version. When I say
below something was done, I'm referring to the -03 version and when I
just say OK or indicate something will be done, I am referring to the
to be posted -04 version.

On Sat, Nov 24, 2012 at 3:28 PM, Black, David <david.black@emc.com>
wrote:
> Hi Linda,
>
> Here are some (somewhat tardy) comments on this WG Last Call.
>
> (1) As noted by some of the others who commented, more functionality
> details would be good to add, especially on mixing of the push and
> pull models in Section 5.  Cache consistency needs to be covered,
> at least its invalidation portion, as relying solely on aging out
> entries can black-hole traffic that uses a stale entry that hasn't
> aged out yet.

Functional detail is to be covered in
draft-dunbar-trill-scheme-for-directory-assist a new version of which
is about to be posted. The framework document is very high level and
it's primary purpose was to provide a means for the WG to indicate its
approval of pursuing this direction. However, we will put in a bit
more concerning cache consistency.

> (2) I also agree with Erik's earlier comment about not understanding
> why Appointed Forwarders are in this draft.  If use of a directory
> can relax Appointed Forwarder restrictions without causing problems
> (e.g., loops), that needs to be explained somewhere, probably in
> Section 4.  Otherwise, Appointed Forwarders should not be discussed.

References to Appointed Forwarders will be removed.

> (3) On the comment about capitalizing MUST, SHOULD and MAY, the
> applicable RFC is RFC 2119, but those terms are not ordinarily used
> in requirements documents.  An explanation that these keywords
> express requirements on protocol development should be provided in
> order to use the upper case versions of these keywords.

Reference to RFC 2119 and capitalized implementation requirement words
were eliminated.

> Here are some more detailed comments:
>
> Abstract:
>    Edge RBridges currently learn the mapping between MAC addresses and
>    their egress RBridges by observing the data packets traversed
>    through.
>
> Change to: ... by observing traffic that traverses the RBridge.

Actually, I don't particularly like "traverses". It sound like
learning from transit frames, which TRILL switches do not do, although
the fact that it mentiones "Edge RBridges" helps. I think "...by
observing traffic they ingress or egress..." would be better.

> Section 1, 1st paragraph:
>
>                 (This ''blocked'' state
>    has no effect of TRILL Data or IS-IS frames, which can still be sent
>    and received. It only affects native frames.)
>
> "of TRILL data" -> "on TRILL Data" in second line above.

That wording has been removed.

> In item 2 in the list, I'd change "usually" to "often":
>    2. Topology is usually based on racks and rows.

OK.

> In item 3 in the list, explain that server reload can change the MAC
> address and why that change may be needed or desirable, because
> Section 4 appears to assert that the MAC address can change.  If
> that wasn't intended, this text in Section 4 needs attention for
> physical servers (it's ok for VMs):
>
>    When a VM is moved to a new
>    location or a server is loaded with a new application with different
>    IP/MAC addresses, it is more likely that the DA of data packets sent
>    out from those VMs are unknown to their attached edge RBridges.

OK.

> Item 4 should follow up on the mention of subnets in item 3 and
> observe that multiple subnets on the same port at the same time is
> common for server virtualization and the change rate is higher than
> for physical servers.

OK.

> In the definition of "Bridge", change "draft" to "document".

There are a number of occurrences of "draft" which should probably be
changed because it will not be a draft when it is published as an RFC.

> Section 3, p.6, first bullet - change both instances of "RB1" to
> "an RBridge" as there's no RB1 in figure 1.

OK.

> The last bullet in Section 3.1 is a bit sloppy about its use of the
> word "entries".  It needs to explain exactly what is in an "entry" -
> it might be possible to do this in an introduction by stating that
> the presence of an entry (and list what it contains) avoids flooding
> of inbound frames that match the entry.

The wording will be improved.

> Section 3.2, Scenario #1 - The use of the word "uplink" is confusing,
> overly constraining and not necessary.  The important concept is how
> many ToR switches are in each rack.  It's quite feasible for a server
> or switch in a rack to have multiple uplinks to the same ToR (e.g.,
> when the links are 1 Gigabit Ethernet).

OK.

> Section 4, first sentence:
> OLD
>    In data center environment, applications placement to servers,
>    racks, and rows is orchestrated by Server (or VM) Management
>    System(s).
> NEW
>    In a data center environment, the assignment of applications
>    to servers, including rack and row selection, is orchestrated
>    by Server (or VM) Management System(s).
> END

That seems like an improvement in wording.

> I'd suggest deleting Section 6 (Conclusion and Recommendations), as
> it's important for considering what the WG will do, but may not have
> much value in a published RFC.

Since the point of the adoption of this document was the the TRILL WG
wishes to pursue directory assistence, I think that the recommendation
part should stay.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> Thanks,
> --David
>
>> -----Original Message-----
>> From: trill-bounces@ietf.org [mailto:trill-bounces@ietf.org] On Behalf Of Erik
>> Nordmark
>> Sent: Wednesday, November 14, 2012 4:13 PM
>> To: trill@ietf.org
>> Subject: Re: [trill] WG Last Call:
>>    draft-ietf-trill-directory-framework-01.txt
>>
>> We would really like to she some more explicit indications from WG
>> participants that they have read this document and agree with it.
>>
>> Please include any substantial as well as editorial improvements that
>> result from reviewing the document.
>>
>>     Erik
>>
>> On 10/25/12 3:55 PM, Donald Eastlake wrote:
>> > This message begins a TRILL WG two week Last Call on the
>> > draft-ietf-trill-directory-framework draft.
>> >
>> > Thanks,
>> > Donald
>> > =============================
>> >   Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>> >   155 Beaver Street, Milford, MA 01757 USA
>> >   d3e3e3@gmail.com

From internet-drafts@ietf.org  Mon Feb 25 09:02:51 2013
Return-Path: <internet-drafts@ietf.org>
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 CA02321F94E6; Mon, 25 Feb 2013 09:02:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.53
X-Spam-Level: 
X-Spam-Status: No, score=-102.53 tagged_above=-999 required=5 tests=[AWL=0.069, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 3IpXPwN7Zjqm; Mon, 25 Feb 2013 09:02:51 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 308AF21F9344; Mon, 25 Feb 2013 09:02:51 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.40
Message-ID: <20130225170251.27510.14282.idtracker@ietfa.amsl.com>
Date: Mon, 25 Feb 2013 09:02:51 -0800
Cc: trill@ietf.org
Subject: [trill] I-D Action: draft-ietf-trill-directory-framework-04.txt
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: Mon, 25 Feb 2013 17:02:52 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Transparent Interconnection of Lots of Li=
nks Working Group of the IETF.

	Title           : TRILL (Transparent Interconnection of Lots of Links): Ed=
ge Directory Assistance Framework
	Author(s)       : Linda Dunbar
                          Donald Eastlake
                          Radia Perlman
                          Igor Gashinsky
	Filename        : draft-ietf-trill-directory-framework-04.txt
	Pages           : 17
	Date            : 2013-02-25

Abstract:
   Edge RBridges currently learn the mapping between MAC addresses and
   their egress RBridges by observing the data packets they ingress or
   egress or by the TRILL ESADI protocol. When an ingress RBridge
   receives a data frame whose destination address (MAC&VLAN) that
   RBridge does not know, the data frame is flooded within the VLAN
   across the TRILL campus.

   This document describes the framework for using directory services to
   assist edge RBridges in reducing multi-destination frames,
   particularly unknown unicast frames flooding, and ARP/ND, thus
   improving TRILL (Transparent Interconnection of Lots of Links)
   network scalability.




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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-trill-directory-framework-04

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-trill-directory-framework-04


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


From david.black@emc.com  Mon Feb 25 14:31:53 2013
Return-Path: <david.black@emc.com>
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 6AF1421F9347 for <trill@ietfa.amsl.com>; Mon, 25 Feb 2013 14:31:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.374
X-Spam-Level: 
X-Spam-Status: No, score=-101.374 tagged_above=-999 required=5 tests=[AWL=-1.075, BAYES_00=-2.599, MANGLED_LIST=2.3, USER_IN_WHITELIST=-100]
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 pfunoAZtcI-O for <trill@ietfa.amsl.com>; Mon, 25 Feb 2013 14:31:45 -0800 (PST)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id A825721F9344 for <trill@ietf.org>; Mon, 25 Feb 2013 14:31:43 -0800 (PST)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r1PMVfJI022277 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 25 Feb 2013 17:31:41 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd04.lss.emc.com [10.254.222.226]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor); Mon, 25 Feb 2013 17:31:28 -0500
Received: from mxhub32.corp.emc.com (mxhub32.corp.emc.com [128.222.70.172]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r1PMVRKj009381; Mon, 25 Feb 2013 17:31:27 -0500
Received: from mx15a.corp.emc.com ([169.254.1.74]) by mxhub32.corp.emc.com ([128.222.70.172]) with mapi; Mon, 25 Feb 2013 17:31:27 -0500
From: "Black, David" <david.black@emc.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 25 Feb 2013 17:31:26 -0500
Thread-Topic: [trill] WG Last Call: draft-ietf-trill-directory-framework-01.txt
Thread-Index: Ac4TecXBAbsBF/ykSVCoG20xevY8rwAKHzzg
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7128F801FFF@MX15A.corp.emc.com>
References: <CAF4+nEH9_MkMTDDG7jn_xipXV-feu4Xy0GyH9NyNO_5EaNw3nQ@mail.gmail.com> <50A4095E.80009@acm.org> <8D3D17ACE214DC429325B2B98F3AE71284D3FF0C@MX15A.corp.emc.com> <CAF4+nEHO2TijzjgCCSP0XMcjaWtsuhMUdY2Lveos6YgO1QhtTA@mail.gmail.com>
In-Reply-To: <CAF4+nEHO2TijzjgCCSP0XMcjaWtsuhMUdY2Lveos6YgO1QhtTA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] WG Last Call: draft-ietf-trill-directory-framework-01.txt
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: Mon, 25 Feb 2013 22:31:53 -0000

Hi Donald,

This looks reasonable, and in particular the remaining Recommendations
section (section 6) in the just-posted -04 version is fine with me.

Thank you for dealing with these comments.

Thanks,
--David

> -----Original Message-----
> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
> Sent: Monday, February 25, 2013 12:01 PM
> To: Black, David
> Cc: trill@ietf.org
> Subject: Re: [trill] WG Last Call: draft-ietf-trill-directory-framework-0=
1.txt
>=20
> Hi David,
>=20
> Thanks for pointing out your earlier review and comments which were
> partially responded to at the time.
>=20
> I understand that you comments were on the -02 version. When I say
> below something was done, I'm referring to the -03 version and when I
> just say OK or indicate something will be done, I am referring to the
> to be posted -04 version.
>=20
> On Sat, Nov 24, 2012 at 3:28 PM, Black, David <david.black@emc.com>
> wrote:
> > Hi Linda,
> >
> > Here are some (somewhat tardy) comments on this WG Last Call.
> >
> > (1) As noted by some of the others who commented, more functionality
> > details would be good to add, especially on mixing of the push and
> > pull models in Section 5.  Cache consistency needs to be covered,
> > at least its invalidation portion, as relying solely on aging out
> > entries can black-hole traffic that uses a stale entry that hasn't
> > aged out yet.
>=20
> Functional detail is to be covered in
> draft-dunbar-trill-scheme-for-directory-assist a new version of which
> is about to be posted. The framework document is very high level and
> it's primary purpose was to provide a means for the WG to indicate its
> approval of pursuing this direction. However, we will put in a bit
> more concerning cache consistency.
>=20
> > (2) I also agree with Erik's earlier comment about not understanding
> > why Appointed Forwarders are in this draft.  If use of a directory
> > can relax Appointed Forwarder restrictions without causing problems
> > (e.g., loops), that needs to be explained somewhere, probably in
> > Section 4.  Otherwise, Appointed Forwarders should not be discussed.
>=20
> References to Appointed Forwarders will be removed.
>=20
> > (3) On the comment about capitalizing MUST, SHOULD and MAY, the
> > applicable RFC is RFC 2119, but those terms are not ordinarily used
> > in requirements documents.  An explanation that these keywords
> > express requirements on protocol development should be provided in
> > order to use the upper case versions of these keywords.
>=20
> Reference to RFC 2119 and capitalized implementation requirement words
> were eliminated.
>=20
> > Here are some more detailed comments:
> >
> > Abstract:
> >    Edge RBridges currently learn the mapping between MAC addresses and
> >    their egress RBridges by observing the data packets traversed
> >    through.
> >
> > Change to: ... by observing traffic that traverses the RBridge.
>=20
> Actually, I don't particularly like "traverses". It sound like
> learning from transit frames, which TRILL switches do not do, although
> the fact that it mentiones "Edge RBridges" helps. I think "...by
> observing traffic they ingress or egress..." would be better.
>=20
> > Section 1, 1st paragraph:
> >
> >                 (This ''blocked'' state
> >    has no effect of TRILL Data or IS-IS frames, which can still be sent
> >    and received. It only affects native frames.)
> >
> > "of TRILL data" -> "on TRILL Data" in second line above.
>=20
> That wording has been removed.
>=20
> > In item 2 in the list, I'd change "usually" to "often":
> >    2. Topology is usually based on racks and rows.
>=20
> OK.
>=20
> > In item 3 in the list, explain that server reload can change the MAC
> > address and why that change may be needed or desirable, because
> > Section 4 appears to assert that the MAC address can change.  If
> > that wasn't intended, this text in Section 4 needs attention for
> > physical servers (it's ok for VMs):
> >
> >    When a VM is moved to a new
> >    location or a server is loaded with a new application with different
> >    IP/MAC addresses, it is more likely that the DA of data packets sent
> >    out from those VMs are unknown to their attached edge RBridges.
>=20
> OK.
>=20
> > Item 4 should follow up on the mention of subnets in item 3 and
> > observe that multiple subnets on the same port at the same time is
> > common for server virtualization and the change rate is higher than
> > for physical servers.
>=20
> OK.
>=20
> > In the definition of "Bridge", change "draft" to "document".
>=20
> There are a number of occurrences of "draft" which should probably be
> changed because it will not be a draft when it is published as an RFC.
>=20
> > Section 3, p.6, first bullet - change both instances of "RB1" to
> > "an RBridge" as there's no RB1 in figure 1.
>=20
> OK.
>=20
> > The last bullet in Section 3.1 is a bit sloppy about its use of the
> > word "entries".  It needs to explain exactly what is in an "entry" -
> > it might be possible to do this in an introduction by stating that
> > the presence of an entry (and list what it contains) avoids flooding
> > of inbound frames that match the entry.
>=20
> The wording will be improved.
>=20
> > Section 3.2, Scenario #1 - The use of the word "uplink" is confusing,
> > overly constraining and not necessary.  The important concept is how
> > many ToR switches are in each rack.  It's quite feasible for a server
> > or switch in a rack to have multiple uplinks to the same ToR (e.g.,
> > when the links are 1 Gigabit Ethernet).
>=20
> OK.
>=20
> > Section 4, first sentence:
> > OLD
> >    In data center environment, applications placement to servers,
> >    racks, and rows is orchestrated by Server (or VM) Management
> >    System(s).
> > NEW
> >    In a data center environment, the assignment of applications
> >    to servers, including rack and row selection, is orchestrated
> >    by Server (or VM) Management System(s).
> > END
>=20
> That seems like an improvement in wording.
>=20
> > I'd suggest deleting Section 6 (Conclusion and Recommendations), as
> > it's important for considering what the WG will do, but may not have
> > much value in a published RFC.
>=20
> Since the point of the adoption of this document was the the TRILL WG
> wishes to pursue directory assistence, I think that the recommendation
> part should stay.
>=20
> Thanks,
> Donald
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA
>  d3e3e3@gmail.com
>=20
> > Thanks,
> > --David
> >
> >> -----Original Message-----
> >> From: trill-bounces@ietf.org [mailto:trill-bounces@ietf.org] On Behalf=
 Of
> Erik
> >> Nordmark
> >> Sent: Wednesday, November 14, 2012 4:13 PM
> >> To: trill@ietf.org
> >> Subject: Re: [trill] WG Last Call:
> >>    draft-ietf-trill-directory-framework-01.txt
> >>
> >> We would really like to she some more explicit indications from WG
> >> participants that they have read this document and agree with it.
> >>
> >> Please include any substantial as well as editorial improvements that
> >> result from reviewing the document.
> >>
> >>     Erik
> >>
> >> On 10/25/12 3:55 PM, Donald Eastlake wrote:
> >> > This message begins a TRILL WG two week Last Call on the
> >> > draft-ietf-trill-directory-framework draft.
> >> >
> >> > Thanks,
> >> > Donald
> >> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D
> >> >   Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
> >> >   155 Beaver Street, Milford, MA 01757 USA
> >> >   d3e3e3@gmail.com


From linda.dunbar@huawei.com  Mon Feb 25 15:47:39 2013
Return-Path: <linda.dunbar@huawei.com>
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 BD75021E819B for <trill@ietfa.amsl.com>; Mon, 25 Feb 2013 15:47:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.624
X-Spam-Level: 
X-Spam-Status: No, score=-6.624 tagged_above=-999 required=5 tests=[AWL=-0.025, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 JtTkRejAkEab for <trill@ietfa.amsl.com>; Mon, 25 Feb 2013 15:47:39 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9953D21E81AD for <trill@ietf.org>; Mon, 25 Feb 2013 15:47:36 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AQB17720; Mon, 25 Feb 2013 23:47:35 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 25 Feb 2013 23:47:33 +0000
Received: from DFWEML408-HUB.china.huawei.com (10.193.5.134) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 25 Feb 2013 23:47:19 +0000
Received: from DFWEML505-MBX.china.huawei.com ([10.124.31.100]) by dfweml408-hub.china.huawei.com ([10.193.5.134]) with mapi id 14.01.0323.007; Mon, 25 Feb 2013 15:47:17 -0800
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "trill@ietf.org" <trill@ietf.org>
Thread-Topic: Update of the draft-dunbar-trill-directory-assisted-encap-03
Thread-Index: AQHOE7Jxax/h5pAVaECqDTVSn8wuOA==
Date: Mon, 25 Feb 2013 23:47:16 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F64512D32A@dfweml505-mbx>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.137.1]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [trill] Update of the draft-dunbar-trill-directory-assisted-encap-03
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: Mon, 25 Feb 2013 23:47:39 -0000

V2hlbiBkaXJlY3RvcnkgaXMgdXNlZCwgYW55IG5vZGUsIGV2ZW4gbm9uLVJCcmlkZ2Ugbm9kZSwg
Y2FuIHBlcmZvcm0gdGhlIFRSSUxMIGVuY2Fwc3VsYXRpb24uIFRoaXMgZHJhZnQgaXMgdG8gZGVt
b25zdHJhdGUgdGhlIGJlbmVmaXRzIGFuZCBzaW1wbGUgc2NoZW1lIG9mIG5vbi1SQnJpZGdlIG5v
ZGVzIHBlcmZvcm1pbmcgVFJJTEwgZW5jYXBzdWxhdGlvbi4gDQoNCg0KaHR0cHM6Ly9kYXRhdHJh
Y2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtZHVuYmFyLXRyaWxsLWRpcmVjdG9yeS1hc3Npc3RlZC1l
bmNhcC8NCg0KV2UgYXJlIGxvb2tpbmcgZm9yIHlvdXIgY29tbWVudHMgYW5kIGZlZWRiYWNrLiAN
Cg0KVGhhbmtzLCBMaW5kYSANCg0K

From d3e3e3@gmail.com  Mon Feb 25 15:58:06 2013
Return-Path: <d3e3e3@gmail.com>
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 2734A21F841E for <trill@ietfa.amsl.com>; Mon, 25 Feb 2013 15:58:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.412
X-Spam-Level: 
X-Spam-Status: No, score=-103.412 tagged_above=-999 required=5 tests=[AWL=0.187, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 14lYkkDzlgQD for <trill@ietfa.amsl.com>; Mon, 25 Feb 2013 15:57:59 -0800 (PST)
Received: from mail-oa0-f41.google.com (mail-oa0-f41.google.com [209.85.219.41]) by ietfa.amsl.com (Postfix) with ESMTP id 6AD6221E81C1 for <trill@ietf.org>; Mon, 25 Feb 2013 15:57:55 -0800 (PST)
Received: by mail-oa0-f41.google.com with SMTP id i10so4132905oag.28 for <trill@ietf.org>; Mon, 25 Feb 2013 15:57:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=7lTMWddZGJH6bbzo7VfGPPc+zL8Wf6kDyJDHSNbDOrk=; b=oiPFDNB5vzx/uEwZvfVFVWgoDiiU9msc49VPFJRMY7IYoEtV6VqRgYLne9zgOOnnak z0rwFMkSHcOVEwc9c3bWPrvjhzclyjICZRCTk91iL5AeZ9ZcYiJCrs+DsfP3x71HEXI6 yuZf1RMbdwpbB9HCRILb0gFe35xws0Zaw16VfGBLHI+7H+JDWbdK4imEcJf3d3/6xIlb mVpnMdRUr3zDwQ5Or8qkTjKvaUbagWMhb3l7k3TuYy/l7Qp9/lgiqnXFFRjX3aN3zO+G fy1nyJZOZAdbCLvy+oMMlwcseTz4keUptKZtAZ/hfqwrpWyjzhc+rPkY59WpzTdM0QYR eCgQ==
X-Received: by 10.60.26.72 with SMTP id j8mr136993oeg.2.1361836664887; Mon, 25 Feb 2013 15:57:44 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.98.168 with HTTP; Mon, 25 Feb 2013 15:57:24 -0800 (PST)
In-Reply-To: <20130225234158.16210.90930.idtracker@ietfa.amsl.com>
References: <20130225234158.16210.90930.idtracker@ietfa.amsl.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 25 Feb 2013 18:57:24 -0500
Message-ID: <CAF4+nEHy8ZY2MtjFWj0PLij2E1dZqgWasX_wYgC92s62fzQn2w@mail.gmail.com>
To: trill@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [trill] Fwd: New Version Notification for draft-dunbar-trill-scheme-for-directory-assist-04.txt
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: Mon, 25 Feb 2013 23:58:06 -0000

Hi,

This draft has some TBDs in it and is in need of polishing but it has
a more detailed description of possible mechanisms for providing
directory assistance to TRILL edge switches.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

---------- Forwarded message ----------
From:  <internet-drafts@ietf.org>
Date: Mon, Feb 25, 2013 at 6:41 PM
Subject: New Version Notification for
draft-dunbar-trill-scheme-for-directory-assist-04.txt
To: d3e3e3@gmail.com
Cc: ldunbar@huawei.com, radia@alum.mit.edu, liyizhou@huawei.com,
igor@yahoo-inc.com

A new version of I-D, draft-dunbar-trill-scheme-for-directory-assist-04.txt
has been successfully submitted by Donald Eastlake and posted to the
IETF repository.

Filename:        draft-dunbar-trill-scheme-for-directory-assist
Revision:        04
Title:           TRILL: Directory Assistance Mechanisms
Creation date:   2013-02-25
Group:           Individual Submission
Number of pages: 36
URL:
http://www.ietf.org/internet-drafts/draft-dunbar-trill-scheme-for-directory-assist-04.txt
Status:
http://datatracker.ietf.org/doc/draft-dunbar-trill-scheme-for-directory-assist
Htmlized:
http://tools.ietf.org/html/draft-dunbar-trill-scheme-for-directory-assist-04
Diff:
http://www.ietf.org/rfcdiff?url2=draft-dunbar-trill-scheme-for-directory-assist-04

Abstract:
   This document describes optional mechanisms for using directory
   server(s) to assist TRILL (Transparent Interconnection of Lots of
   Links) edge switches in reducing multi-destination traffic,
   particularly ARP/ND and unknown unicast flooding.





The IETF Secretariat

From nordmark@acm.org  Mon Feb 25 16:29:23 2013
Return-Path: <nordmark@acm.org>
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 F06EA21E81A5 for <trill@ietfa.amsl.com>; Mon, 25 Feb 2013 16:29:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 kwPMNO6axycs for <trill@ietfa.amsl.com>; Mon, 25 Feb 2013 16:29:23 -0800 (PST)
Received: from a.mail.sonic.net (a.mail.sonic.net [64.142.16.245]) by ietfa.amsl.com (Postfix) with ESMTP id 7AD4821E81A9 for <trill@ietf.org>; Mon, 25 Feb 2013 16:29:23 -0800 (PST)
Received: from [10.154.212.113] (128-107-239-233.cisco.com [128.107.239.233]) (authenticated bits=0) by a.mail.sonic.net (8.13.8.Beta0-Sonic/8.13.7) with ESMTP id r1Q0TKcH008898 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 25 Feb 2013 16:29:21 -0800
Message-ID: <512C01E2.6030907@acm.org>
Date: Mon, 25 Feb 2013 16:29:22 -0800
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: "trill@ietf.org" <trill@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [trill] Conclusion of WG last call on draft-ietf-trill-fine-labeling
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: Tue, 26 Feb 2013 00:29:24 -0000

We started the WG last call back in November. Then in December the 
authors started discussing some concerns about mixed VL and FGL networks.

That later resulted in a proposal on the mailing list with three options 
described in
http://www.ietf.org/mail-archive/web/trill/current/msg05604.html

The email discussion showed (rough) consensus for option 2 with a tweak 
to it as described in:
http://www.ietf.org/mail-archive/web/trill/current/msg05633.html

Those changes have been applied to the draft and appears in
draft-ietf-trill-fine-labeling-05.txt

Thus -05 concludes the WG last call.

Thanks for all the review and comments to make the draft better.

    Erik

From d3e3e3@gmail.com  Tue Feb 26 06:14:31 2013
Return-Path: <d3e3e3@gmail.com>
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 0EDF621F87D6 for <trill@ietfa.amsl.com>; Tue, 26 Feb 2013 06:14:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.426
X-Spam-Level: 
X-Spam-Status: No, score=-103.426 tagged_above=-999 required=5 tests=[AWL=0.173, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 ty6En0Af7l21 for <trill@ietfa.amsl.com>; Tue, 26 Feb 2013 06:14:30 -0800 (PST)
Received: from mail-oa0-f49.google.com (mail-oa0-f49.google.com [209.85.219.49]) by ietfa.amsl.com (Postfix) with ESMTP id 0D88E21F87D5 for <trill@ietf.org>; Tue, 26 Feb 2013 06:14:29 -0800 (PST)
Received: by mail-oa0-f49.google.com with SMTP id j6so5098828oag.22 for <trill@ietf.org>; Tue, 26 Feb 2013 06:14:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=Q6oxT89mJQo5aCjV7LR/oEbPEj3W85/pd7JA0wtftpg=; b=l5WBKpkchsglFR8wmw+fZJ99mnG9C4eMuoDbl1xgvhzRbjVEXat18nnGaFrdGVr/f0 7mLiaHU+Z2FpKEeU4M2Z0oAK33+SQmbjT7qDd5RicZkbBPTuKpCoMQcmdZwJgl+TDKOR JHvSqVZlOiqZgpGp3ezVBWVO3apnHM38Nkovn9wRMuURBL6MtpN10eAv/z4UHZm8+l/6 TvCq8EGDNcx0rR+5sstyGmxHRxTuhiKFvld4o5uNR3GZcBwWt3G6cLMwU0rtrwRDAMvs L4yvkxdjfbea8HKgesFWRZcNK9KhuoF4Tk5qFEUknLxpT61BHHg6+bdy68EyzihLjq7n 0LCA==
X-Received: by 10.182.132.43 with SMTP id or11mr119983obb.67.1361888069500; Tue, 26 Feb 2013 06:14:29 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.98.168 with HTTP; Tue, 26 Feb 2013 06:14:09 -0800 (PST)
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 26 Feb 2013 09:14:09 -0500
Message-ID: <CAF4+nEEDb6Lp0A0vfMpujsnAQY_E8gOhkBpFYjgsGypj5tH1wQ@mail.gmail.com>
To: trill@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [trill] Planned TRILL Plugfest the week of 25 March
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: Tue, 26 Feb 2013 14:14:31 -0000

Hi,

UNH IOL is planning a TRILL plugfest the week of 25 March. See
https://www.iol.unh.edu/services/testing/bfc/grouptest/March_25_2013/
for further information. Interoperability is good!

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

From d3e3e3@gmail.com  Thu Feb 28 00:34:46 2013
Return-Path: <d3e3e3@gmail.com>
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 4A6E421F8700 for <trill@ietfa.amsl.com>; Thu, 28 Feb 2013 00:34:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 ypNXt3X+QnWP for <trill@ietfa.amsl.com>; Thu, 28 Feb 2013 00:34:45 -0800 (PST)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id BEF1E21F84B8 for <trill@ietf.org>; Thu, 28 Feb 2013 00:34:42 -0800 (PST)
Received: by mail-ob0-f172.google.com with SMTP id tb18so319784obb.31 for <trill@ietf.org>; Thu, 28 Feb 2013 00:34:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=eoV6sWEtgRbluteXtVxMWJc31Gl6PBLlsmRES+mkHow=; b=eEmFnhCr5WMfCkZKLUg/hdUEDNtDmC40Y/TIPgK0QLf//9713K6N9kIhSOYxehvPBH xahetuJYXBKoVqitLZ22lHM4znMb0/BCGvKzs/z+yJ63is2GoLtYo+d5TjOynG+BgUyt r1k/8O+1BuEJpGWfCOqWXGG87f3PNjOHduVUKhDqLl26WkMOkL2bQs0rG9chQkfI3eD5 Tn0ERUOheeUX7wzA1pUB0pnMbyM3Rokt3MVgY1YOydhz6mQIE8YNZD3+hqEvi0hsh4x3 3w7NU6fwFPVTFq6jleB8Bpalfy23ltXFQLYM9xx5bFhwwBDs55A479F9Vfp8NQn4IDbc GK3w==
X-Received: by 10.182.227.106 with SMTP id rz10mr4780991obc.78.1362040482327;  Thu, 28 Feb 2013 00:34:42 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.98.168 with HTTP; Thu, 28 Feb 2013 00:34:22 -0800 (PST)
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 28 Feb 2013 03:34:22 -0500
Message-ID: <CAF4+nEEqWkma8u=onpGeaTajy1Cj7YVxnGZHDsi=Hjs2Ss2FAg@mail.gmail.com>
To: trill@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [trill] Preliminary Orlando Agenda
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: Thu, 28 Feb 2013 08:34:46 -0000

Hi,

A Preliminary agenda for the TRILL Orlando WG meeting has been posted at
https://datatracker.ietf.org/meeting/86/agenda/trill/

(Although we only asked for 2 or 2 1/2 hours, we ended up with a
session spanning two 1 1/2 hour slots.)

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

From ostokes@extremenetworks.com  Thu Feb 28 10:21:57 2013
Return-Path: <ostokes@extremenetworks.com>
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 6679621F8BF1 for <trill@ietfa.amsl.com>; Thu, 28 Feb 2013 10:21:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.001]
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 NniDCqdw1Y9B for <trill@ietfa.amsl.com>; Thu, 28 Feb 2013 10:21:55 -0800 (PST)
Received: from ussc-casht-p1.extremenetworks.com (ussc-casht-p2.extremenetworks.com [207.179.9.62]) by ietfa.amsl.com (Postfix) with ESMTP id B20E421F8BD4 for <trill@ietf.org>; Thu, 28 Feb 2013 10:21:55 -0800 (PST)
Received: from USEXCHANGE.corp.extremenetworks.com ([10.0.4.74]) by ussc-casht-p2.corp.extremenetworks.com ([10.255.181.88]) with mapi; Thu, 28 Feb 2013 10:21:55 -0800
From: Olen Stokes <ostokes@extremenetworks.com>
To: "trill@ietf.org" <trill@ietf.org>
Date: Thu, 28 Feb 2013 10:21:54 -0800
Thread-Topic: Asymmetric link costs and D-Tree calculations
Thread-Index: Ac4V3Y6ATGi9IG/PRKq/U2lfEPXETg==
Message-ID: <A3C4E51A53661B4EBEE7C5F5E6FCDEB5029BB4E8D921@USEXCHANGE.corp.extremenetworks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_A3C4E51A53661B4EBEE7C5F5E6FCDEB5029BB4E8D921USEXCHANGEc_"
MIME-Version: 1.0
Subject: [trill] Asymmetric link costs and D-Tree calculations
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: Thu, 28 Feb 2013 18:21:57 -0000

--_000_A3C4E51A53661B4EBEE7C5F5E6FCDEB5029BB4E8D921USEXCHANGEc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Appendix A.1 of RFC 6325 discusses the fact that "two RBridges may know the=
y are connected but each sees the link as a different speed from how it is =
seen by the other."



We have been looking at this and how it relates to D-Tree calculation as di=
scussed in Section 4.5.1.  In that section, it states, "Each RBridge RBn in=
dependently calculates a tree rooted at RBi by performing the SPF (Shortest=
 Path First) calculation with RBi as the root".  So, it appears that the D-=
Tree is calculated from the root RBridge outward.



The following three paragraphs describe how to determine the potential pare=
nts P for a node N.  There does not appear to be any mention of direction s=
o it would seem that all calculations are done in the direction from the ro=
ot RBi outward.



The last paragraph in Section 4.5.1 states, "In other words, the set of pot=
ential parents for N, for the tree rooted at R, consists of those that give=
 equally minimal cost paths from N to R and that have distinct IS-IS IDs, b=
ased on what is reported in LSPs."  In this case, costs are discussed as in=
ward from node N towards root RBi.



This change in direction of cost calculation could potentially be confusing=
 when there are asymmetric link costs as described in Appendix A.1.  For an=
y parent P found during the SPF calculation, it is possible that the cost f=
rom N to

P is different than the cost from P to N.  It is also possible that none of=
 the parents found during the SPF calculation are found along any of the "e=
qually minimal cost paths from N to R".



Is the potential change of direction when calculating costs in the last par=
agraph unintended?  Would the paragraph have been more clear discussing "eq=
ually minimal cost paths from R to N"?



Is there agreement in the presence of asymmetric link costs that it is poss=
ible that none of the parents found during the SPF calculation are found al=
ong any of the "equally minimal cost paths from N to R" calculated for know=
n unicast traffic?



Cheers,

Olen



--_000_A3C4E51A53661B4EBEE7C5F5E6FCDEB5029BB4E8D921USEXCHANGEc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:m=3D"http://schema=
s.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html=
40"><head><meta http-equiv=3DContent-Type content=3D"text/html; charset=3Du=
s-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 (filtered medi=
um)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1942909303;
	mso-list-type:hybrid;
	mso-list-template-ids:1756167516 -869116086 67698713 67698715 67698703 676=
98713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoPlainText><span style=
=3D'font-size:10.0pt;font-family:"Courier New"'>Appendix A.1 of RFC 6325 di=
scusses the fact that &#8220;two RBridges may know they are connected but e=
ach sees the link as a different speed from how it is seen by the other.&#8=
221;&nbsp; <o:p></o:p></span></p><p class=3DMsoPlainText><span style=3D'fon=
t-size:10.0pt;font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p cla=
ss=3DMsoPlainText><span style=3D'font-size:10.0pt;font-family:"Courier New"=
'>We have been looking at this and how it relates to D-Tree calculation as =
discussed in Section 4.5.1.&nbsp; In that section, it states, &#8220;</span=
><span style=3D'font-family:"Courier New"'>Each RBridge RBn independently c=
alculates a tree rooted at RBi by performing the SPF (Shortest Path First) =
calculation with RBi as the root</span><span style=3D'font-size:10.0pt;font=
-family:"Courier New"'>&#8221;.&nbsp; So, it appears that the D-Tree is cal=
culated from the root RBridge outward.&nbsp; <o:p></o:p></span></p><p class=
=3DMsoPlainText><span style=3D'font-size:10.0pt;font-family:"Courier New"'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span style=3D'font-siz=
e:10.0pt;font-family:"Courier New"'>The following three paragraphs describe=
 how to determine the potential parents P for a node N.&nbsp; There does no=
t appear to be any mention of direction so it would seem that all calculati=
ons are done in the direction from the root RBi outward.<o:p></o:p></span><=
/p><p class=3DMsoPlainText><span style=3D'font-size:10.0pt;font-family:"Cou=
rier New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span style=
=3D'font-size:10.0pt;font-family:"Courier New"'>The last paragraph in Secti=
on 4.5.1 states, &#8220;</span><span style=3D'font-family:"Courier New"'>In=
 other words, the set of potential parents for N, for the tree rooted at R,=
 consists of those that give equally minimal cost paths from N to R and tha=
t have distinct IS-IS IDs, based on what is reported in LSPs.</span><span s=
tyle=3D'font-size:10.0pt;font-family:"Courier New"'>&#8221;&nbsp; In this c=
ase, costs are discussed as inward from node N towards root RBi.&nbsp; <o:p=
></o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:10.0pt;f=
ont-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainTe=
xt><span style=3D'font-size:10.0pt;font-family:"Courier New"'>This change i=
n direction of cost calculation could potentially be confusing when there a=
re asymmetric link costs as described in Appendix A.1.&nbsp; For any parent=
 P found during the SPF calculation, it is possible that the cost from N to=
 <o:p></o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:10.=
0pt;font-family:"Courier New"'>P is different than the cost from P to N.&nb=
sp; It is also possible that none of the parents found during the SPF calcu=
lation are found along any of the &#8220;</span><span style=3D'font-family:=
"Courier New"'>equally minimal cost paths from N to R</span><span style=3D'=
font-size:10.0pt;font-family:"Courier New"'>&#8221;.<o:p></o:p></span></p><=
p class=3DMsoPlainText><span style=3D'font-size:10.0pt;font-family:"Courier=
 New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span style=3D'f=
ont-size:10.0pt;font-family:"Courier New"'>Is the potential change of direc=
tion when calculating costs in the last paragraph unintended? &nbsp;Would t=
he paragraph have been more clear discussing &#8220;</span><span style=3D'f=
ont-family:"Courier New"'>equally minimal cost paths from R to N</span><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New"'>&#8221;? &nbsp;<o:p>=
</o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:10.0pt;fo=
nt-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainTex=
t><span style=3D'font-size:10.0pt;font-family:"Courier New"'>Is there agree=
ment in the presence of asymmetric link costs that it is possible that none=
 of the parents found during the SPF calculation are found along any of the=
 &#8220;</span><span style=3D'font-family:"Courier New"'>equally minimal co=
st paths from N to R</span><span style=3D'font-size:10.0pt;font-family:"Cou=
rier New"'>&#8221; calculated for known unicast traffic?<o:p></o:p></span><=
/p><p class=3DMsoPlainText><span style=3D'font-size:10.0pt;font-family:"Cou=
rier New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span style=
=3D'font-size:10.0pt;font-family:"Courier New"'>Cheers,<o:p></o:p></span></=
p><p class=3DMsoPlainText><span style=3D'font-size:10.0pt;font-family:"Cour=
ier New"'>Olen<o:p></o:p></span></p><p class=3DMsoPlainText><span style=3D'=
font-size:10.0pt;font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p></d=
iv></body></html>=

--_000_A3C4E51A53661B4EBEE7C5F5E6FCDEB5029BB4E8D921USEXCHANGEc_--

From d3e3e3@gmail.com  Thu Feb 28 23:21:36 2013
Return-Path: <d3e3e3@gmail.com>
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 2FF1421F871D for <trill@ietfa.amsl.com>; Thu, 28 Feb 2013 23:21:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.452
X-Spam-Level: 
X-Spam-Status: No, score=-103.452 tagged_above=-999 required=5 tests=[AWL=0.147, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 1vamP0jUgjHY for <trill@ietfa.amsl.com>; Thu, 28 Feb 2013 23:21:35 -0800 (PST)
Received: from mail-oa0-f47.google.com (mail-oa0-f47.google.com [209.85.219.47]) by ietfa.amsl.com (Postfix) with ESMTP id E9F0321F8717 for <trill@ietf.org>; Thu, 28 Feb 2013 23:21:34 -0800 (PST)
Received: by mail-oa0-f47.google.com with SMTP id o17so5242933oag.34 for <trill@ietf.org>; Thu, 28 Feb 2013 23:21:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=UQ3+5+LHk+6nxodNyHPlhf9q6zZCP5mBTfssrPQ/vMg=; b=tjtSocLxaN7YmO4y/faaXjuOEMXbJQhD39+3BlxrTx0Fbu/bzKMOdTet/k5Fde/95y oJqyznoKE8gO3hEikkTbwYKtMkd3DICisxUIrbkO3+3GYT2kDQ0HXYTf+iSEOPHuQ/Gh /WwtSOLnZ4AJkalCL3run+aluaf6thFahlLBJpxuSSVVeg/a9YW+gPuvy9QMcJtmJP61 f1B+WcvKUjP9kW2WYX6CkGt/4tnpD2xnPs35hrDW9QXOQGCGPhugVhKf4SVqqsfkMFwB wmniqFTUU58uPDP3ZRxr+BaQm/O14KGKy/cHfnzAR7Vc8IaY7wSCoLv3DZURXnIENKv7 lfJA==
X-Received: by 10.60.172.18 with SMTP id ay18mr7611757oec.126.1362122494381; Thu, 28 Feb 2013 23:21:34 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.98.168 with HTTP; Thu, 28 Feb 2013 23:21:14 -0800 (PST)
In-Reply-To: <A3C4E51A53661B4EBEE7C5F5E6FCDEB5029BB4E8D921@USEXCHANGE.corp.extremenetworks.com>
References: <A3C4E51A53661B4EBEE7C5F5E6FCDEB5029BB4E8D921@USEXCHANGE.corp.extremenetworks.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 1 Mar 2013 02:21:14 -0500
Message-ID: <CAF4+nEGytby1OmDJ+x-OTTg8CEOFzrt_FRW8gTuTm6Jc4H7-pQ@mail.gmail.com>
To: Olen Stokes <ostokes@extremenetworks.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] Asymmetric link costs and D-Tree calculations
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: Fri, 01 Mar 2013 07:21:36 -0000

Hi Olen,

On Thu, Feb 28, 2013 at 1:21 PM, Olen Stokes
<ostokes@extremenetworks.com> wrote:
> Appendix A.1 of RFC 6325 discusses the fact that =93two RBridges may know=
 they
> are connected but each sees the link as a different speed from how it is
> seen by the other.=94

Yes, and asymmetry can also occur through manual cost configuration of cost=
s.

> We have been looking at this and how it relates to D-Tree calculation as
> discussed in Section 4.5.1.  In that section, it states, =93Each RBridge =
RBn
> independently calculates a tree rooted at RBi by performing the SPF
> (Shortest Path First) calculation with RBi as the root=94.  So, it appear=
s
> that the D-Tree is calculated from the root RBridge outward.
>
> The following three paragraphs describe how to determine the potential
> parents P for a node N.  There does not appear to be any mention of
> direction so it would seem that all calculations are done in the directio=
n
> from the root RBi outward.

That was the intent. The tree is calculated through a Dijkstra SPF
process starting at the Root and working outwards.

> The last paragraph in Section 4.5.1 states, =93In other words, the set of
> potential parents for N, for the tree rooted at R, consists of those that
> give equally minimal cost paths from N to R and that have distinct IS-IS
> IDs, based on what is reported in LSPs.=94  In this case, costs are discu=
ssed
> as inward from node N towards root RBi.

That text in RFC 6325 is wrong, as far as I know.

> This change in direction of cost calculation could potentially be confusi=
ng
> when there are asymmetric link costs as described in Appendix A.1.  For a=
ny
> parent P found during the SPF calculation, it is possible that the cost f=
rom
> N to
> P is different than the cost from P to N.  It is also possible that none =
of
> the parents found during the SPF calculation are found along any of the
> =93equally minimal cost paths from N to R=94.

Yes.

Although I think the asymmetric costs will be rarely encountered, it
is critical that all RBridges calculate the same tree so the method
must be unambiguous.

> Is the potential change of direction when calculating costs in the last
> paragraph unintended?  Would the paragraph have been more clear discussin=
g
> =93equally minimal cost paths from R to N=94?

Yes, thanks for spotting this. It should have said "from R to N" or
something like that. I'll file an Errata against RFC 6325.

> Is there agreement in the presence of asymmetric link costs that it is
> possible that none of the parents found during the SPF calculation are fo=
und
> along any of the =93equally minimal cost paths from N to R=94 calculated =
for
> known unicast traffic?

It seems to me that could happen.

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> Cheers,
> Olen

From haoweiguo@huawei.com  Thu Feb 28 23:39:21 2013
Return-Path: <haoweiguo@huawei.com>
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 A459E21F8833 for <trill@ietfa.amsl.com>; Thu, 28 Feb 2013 23:39:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.731
X-Spam-Level: 
X-Spam-Status: No, score=-0.731 tagged_above=-999 required=5 tests=[AWL=4.114,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4]
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 KXc3rBLRDsH3 for <trill@ietfa.amsl.com>; Thu, 28 Feb 2013 23:39:21 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9FDEF21F87EA for <trill@ietf.org>; Thu, 28 Feb 2013 23:39:20 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AQF11052; Fri, 01 Mar 2013 07:39:19 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 1 Mar 2013 07:39:18 +0000
Received: from NKGEML410-HUB.china.huawei.com (10.98.56.41) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 1 Mar 2013 07:39:18 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.101]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.01.0323.007; Fri, 1 Mar 2013 15:39:14 +0800
From: Haoweiguo <haoweiguo@huawei.com>
To: "trill@ietf.org" <trill@ietf.org>
Thread-Topic: About draft of <The problem statement of RBridge edge group state synchronization> 
Thread-Index: Ac4WT3J8LIq+79DlRimIrnfxQiQrqQ==
Date: Fri, 1 Mar 2013 07:39:13 +0000
Message-ID: <DD5FC8DE455C3348B94340C0AB5517334F653B5D@nkgeml501-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.135.22.248]
Content-Type: multipart/alternative; boundary="_000_DD5FC8DE455C3348B94340C0AB5517334F653B5Dnkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [trill] About draft of <The problem statement of RBridge edge group state synchronization>
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: Fri, 01 Mar 2013 07:39:21 -0000

--_000_DD5FC8DE455C3348B94340C0AB5517334F653B5Dnkgeml501mbschi_
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64

SGkgQWxsLA0KDQpJIGhhdmUgcG9zdGVkIG9uZSBkcmFmdCBvZiA8VGhlIHByb2JsZW0gc3RhdGVt
ZW50IG9mIFJCcmlkZ2UgZWRnZSBncm91cCBzdGF0ZSBzeW5jaHJvbml6YXRpb24+IGluIEphbnVh
cnkgdGhpcyB5ZWFyLg0KDQpDdXJyZW50bHkgdGhlcmUgYXJlIFBzZXVkby1OaWNrbmFtZSBhbmQg
Q01UIGRyYWZ0IHRvIHNvbHZlIG11bHRpLWhvbWluZyBwcm9ibGVtcy4gQnV0IGkgdGhpbmsgaXQn
cyBub3QgZW5vdWdoLiBBbm90aGVyIHJlcXVpcmVtZW50cyBzaG91bGQgYWxzbyBiZSBjb25zaWRl
cmVkIHN1Y2ggYXMgbXVsdGktY2hhc3NpcyBMQUNQLi4uIENvbW11bmljYXRpb24gcHJvdG9jb2wg
YW1vbmcgZWRnZSBSQnMgc2hvdWxkIGJlIGludHJvZHVjZWQgdG8gc3luY3Jvbml6ZSBzdGF0ZSBh
bmQgY29uZmlndXJhdGlvbiBhbW9uZyB0aGVzZSBSQnMuDQoNClRoaXMgZHJhZnQgb25seSBkZXNj
cmliZXMgdGhlIHByb2JsZW1zIGFuZCByZXF1aXJlbWVudHMuIFN1Z2dlc3Rpb25zIGFuZCBjb21t
ZW50cyBhcmUgd2VsY29tZWQuDQoNCnRoYW5rcw0KDQp3ZWlndW8NCg==

--_000_DD5FC8DE455C3348B94340C0AB5517334F653B5Dnkgeml501mbschi_
Content-Type: text/html; charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dgb2312">
<style id=3D"owaParaStyle">P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body fPStyle=3D"1" ocsi=3D"0">
<div style=3D"FONT-FAMILY: Tahoma; DIRECTION: ltr; COLOR: #000000; FONT-SIZ=
E: 10pt">
<p>Hi All,</p>
<p>I have posted one draft of &lt;The problem statement of RBridge edge gro=
up state synchronization&gt; in January this year.</p>
<p>Currently there are Pseudo-Nickname and CMT draft to solve multi-homing =
problems. But i think it's not enough. Another requirements should also be =
considered such as multi-chassis LACP... Communication protocol among edge =
RBs should be introduced to syncronize
 state and configuration among these RBs.</p>
<p>This draft only describes the problems and requirements. Suggestions and=
 comments are welcomed.</p>
<p>thanks</p>
<p>weiguo</p>
</div>
</body>
</html>

--_000_DD5FC8DE455C3348B94340C0AB5517334F653B5Dnkgeml501mbschi_--
