IETF Logo Mail Archive

Re: [trill] WG Adoption call for draft-eastlake-trill-vendor-channel (11/15 to 11/29)

"Zhuangyan (Yan)" <zhuangyan.zhuang@huawei.com> Tue, 26 December 2017 06:20 UTC

Return-Path: <zhuangyan.zhuang@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 CADA6124B17 for <trill@ietfa.amsl.com>; Mon, 25 Dec 2017 22:20:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.23
X-Spam-Level:
X-Spam-Status: No, score=-4.23 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] 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 e5gFsBaDJIVu for <trill@ietfa.amsl.com>; Mon, 25 Dec 2017 22:20:57 -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 1A89A120727 for <trill@ietf.org>; Mon, 25 Dec 2017 22:20:57 -0800 (PST)
Received: from LHREML711-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 3FBD1150799E for <trill@ietf.org>; Tue, 26 Dec 2017 06:20:53 +0000 (GMT)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by LHREML711-CAH.china.huawei.com (10.201.108.34) with Microsoft SMTP Server (TLS) id 14.3.361.1; Tue, 26 Dec 2017 06:20:54 +0000
Received: from NKGEML513-MBS.china.huawei.com ([169.254.2.231]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0361.001; Tue, 26 Dec 2017 14:20:48 +0800
From: "Zhuangyan (Yan)" <zhuangyan.zhuang@huawei.com>
To: Susan Hares <shares@ndzh.com>, "trill@ietf.org" <trill@ietf.org>
Thread-Topic: Re: [trill] WG Adoption call for draft-eastlake-trill-vendor-channel (11/15 to 11/29)
Thread-Index: AdN+ENchB3zpJJyoRuezr3NrONuIMg==
Date: Tue, 26 Dec 2017 06:20:47 +0000
Message-ID: <9B4BC45FDEDDD84F813E9E4A5BAF8785A9681193@nkgeml513-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.170.230]
Content-Type: multipart/alternative; boundary="_000_9B4BC45FDEDDD84F813E9E4A5BAF8785A9681193nkgeml513mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/SaptZR--uVHYrMRx6OGnkTOUXn0>
Subject: Re: [trill] WG Adoption call for draft-eastlake-trill-vendor-channel (11/15 to 11/29)
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, 26 Dec 2017 06:20:59 -0000

I am not aware of IPR related to this draft and I think it is useful to have and ready for standardization.

Best Regards,

Yan

-----Original Message-----
From: trill [mailto:trill-bounces at ietf.org] On Behalf Of Susan Hares
Sent: Thursday, November 16, 2017 11:45 AM
To: trill at ietf.org
Subject: [trill] WG Adoption call for draft-eastlake-trill-vendor-channel (11/15 to 11/29)

TRILL WG:

This is a WG adoption call for draft-eastlake-trill-vendor-channel-03.txt (11/15 to 11/29).

In this WG Adoption call please consider,

1)      Is this vendor specific message channel useful to deployments?
2)      Is this mechanism ready for standardization?  The TRILL WG group must move rapidly from adoption of this draft to WG LC in December?
3)      Do you know of any IPR related to this draft?

Susan Hares

v2.23.0 | Report a Bug | By Email