Re: [trill] WG LC on draft-ietf-trill-vendor-channel-00.txt (1/19 to 2/2/2018)

Linda Dunbar <linda.dunbar@huawei.com> Tue, 20 February 2018 21:00 UTC

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 5348A126CD6 for <trill@ietfa.amsl.com>; Tue, 20 Feb 2018 13:00:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.229
X-Spam-Level:
X-Spam-Status: No, score=-4.229 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VAae-tqGtWid for <trill@ietfa.amsl.com>; Tue, 20 Feb 2018 13:00:55 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B8EF120725 for <trill@ietf.org>; Tue, 20 Feb 2018 13:00:55 -0800 (PST)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 3C453E89A2EB7 for <trill@ietf.org>; Tue, 20 Feb 2018 21:00:51 +0000 (GMT)
Received: from SJCEML702-CHM.china.huawei.com (10.208.112.38) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.361.1; Tue, 20 Feb 2018 21:00:52 +0000
Received: from SJCEML521-MBB.china.huawei.com ([169.254.6.91]) by SJCEML702-CHM.china.huawei.com ([169.254.4.179]) with mapi id 14.03.0382.000; Tue, 20 Feb 2018 13:00:47 -0800
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "shares@ndzh.com" <shares@ndzh.com>, "trill@ietf.org" <trill@ietf.org>
Thread-Topic: WG LC on draft-ietf-trill-vendor-channel-00.txt (1/19 to 2/2/2018)
Thread-Index: AQHTqmrl+rn98r0OKUawdEnJCjW9+KOtjdVA
Date: Tue, 20 Feb 2018 21:00:47 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F66B00C747@SJCEML521-MBB.china.huawei.com>
References: <02a201d39144$ed4a0090$c7de01b0$@ndzh.com> <CAF4+nEGjFMW7Si3pMg1aRq4EoEUxtU=z76k9Jv_ws7uU4gCHdQ@mail.gmail.com>
In-Reply-To: <CAF4+nEGjFMW7Si3pMg1aRq4EoEUxtU=z76k9Jv_ws7uU4gCHdQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.218.137.155]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F66B00C747SJCEML521MBBchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/GhWUVHwZ1o0xCKaD7Ynr-paNHhE>
Subject: Re: [trill] WG LC on draft-ietf-trill-vendor-channel-00.txt (1/19 to 2/2/2018)
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 20 Feb 2018 21:00:57 -0000

Support the WG LC for draft-ietf-trill-vendor-channel.
I think vendor channel provides flexibility for the vendors’ managements.

I think the draft is ready for publication.

Linda

---------- Forwarded message ---------
From: Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>
Date: Fri, Jan 19, 2018 at 11:45
Subject: WG LC on draft-ietf-trill-vendor-channel-00.txt (1/19 to 2/2/2018)
To: <trill@ietf.org<mailto:trill@ietf.org>>
CC: <draft-ietf-trill-vendor-channel@ietf.org<mailto:draft-ietf-trill-vendor-channel@ietf.org>>

This begins a 2 week WG last call on draft-ietf-trill-vendor-channel-00 from 1/19/2018 to 2/2/2018.

During your WG last call comments, please consider:


1)      Does this vendor channel provide flexibility for the vendors management of TRILL switches?

2)      Will this option help vendors to continue to extend their TRILL campuses?

3)      Is specification ready for publication?

Cheerily, Susan Hares


--
Sent from Gmail Mobile