IETF Logo Mail Archive

Re: [i2rs] draft-ietf-i2rs-yang-dc-fabric-network-topology - WG LC from 11/28 to 12/12/2017

"Zhuangyan (Yan)" <zhuangyan.zhuang@huawei.com> Wed, 29 November 2017 13:03 UTC

Return-Path: <zhuangyan.zhuang@huawei.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 488E8126C2F for <i2rs@ietfa.amsl.com>; Wed, 29 Nov 2017 05:03:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 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] 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 DKjYIvyY1_8x for <i2rs@ietfa.amsl.com>; Wed, 29 Nov 2017 05:03:44 -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 1E370120725 for <i2rs@ietf.org>; Wed, 29 Nov 2017 05:03:44 -0800 (PST)
Received: from LHREML711-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id F383A43AB0F6A for <i2rs@ietf.org>; Wed, 29 Nov 2017 13:03:38 +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; Wed, 29 Nov 2017 13:02:34 +0000
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.219]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0361.001; Wed, 29 Nov 2017 21:02:29 +0800
From: "Zhuangyan (Yan)" <zhuangyan.zhuang@huawei.com>
To: Susan Hares <shares@ndzh.com>, "i2rs@ietf.org" <i2rs@ietf.org>
Thread-Topic: [i2rs] draft-ietf-i2rs-yang-dc-fabric-network-topology - WG LC from 11/28 to 12/12/2017
Thread-Index: AdNpEUQAMLKuGd0MQ2yO0GwP+44ktg==
Date: Wed, 29 Nov 2017 13:02:28 +0000
Message-ID: <9B4BC45FDEDDD84F813E9E4A5BAF8785A9665C62@nkgeml513-mbx.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.45.109.161]
Content-Type: multipart/alternative; boundary="_000_9B4BC45FDEDDD84F813E9E4A5BAF8785A9665C62nkgeml513mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/OuCDkvaJD9eT9Y0Ji7aGiZtZU6A>
Subject: Re: [i2rs] draft-ietf-i2rs-yang-dc-fabric-network-topology - WG LC from 11/28 to 12/12/2017
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Nov 2017 13:03:46 -0000

I am not aware of any IPR relating to this draft.

We have implementation of this model in ODL which is used to help network management in data center.
The model now is in NMDA style.

As a co-author, I support the publication of this model.

Best Regards,

Yan

发件人: i2rs [mailto:i2rs-bounces@ietf.org] 代表 Susan Hares
发送时间: 2017年11月28日 21:56
收件人: i2rs@ietf.org
主题: [i2rs] draft-ietf-i2rs-yang-dc-fabric-network-topology - WG LC from 11/28 to 12/12/2017

This begins a 2 week WG LC on the I2RS draft draft-ietf-i2rs-yang-dc-fabric-network-topology from 11/28 to 12/12/2017.

https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-dc-fabric-network-topology/

The authors should indicate if they know of any IPR relating to this draft.

Please consider during your WG LC review, the following questions:


1)      Do you know of any implementations of this draft?

2)      Does this draft adhere to the Network Management Datastore architecture (NMDA)?

3)      Do you know of any technical issues with this yang module?

4)      Will the deployment of this yang module aid the management of Data Center Fabrics?

5)      Do you support publication of this yang module?

Sue Hares

v2.23.0 | Report a Bug | By Email