IETF Logo Mail Archive

Re: [i2rs] I2RS and duplicate YANG module definitions

"Zhuangyan (Yan)" <zhuangyan.zhuang@huawei.com> Tue, 29 August 2017 09:20 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 8B7A813214D; Tue, 29 Aug 2017 02:20:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level:
X-Spam-Status: No, score=-4.209 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_KAM_HTML_FONT_INVALID=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 R-3I-gZO3aVP; Tue, 29 Aug 2017 02:20:18 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C3CD132025; Tue, 29 Aug 2017 02:20:16 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml708-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DNN27125; Tue, 29 Aug 2017 09:20:14 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml708-cah.china.huawei.com (10.201.108.49) with Microsoft SMTP Server (TLS) id 14.3.301.0; Tue, 29 Aug 2017 10:20:10 +0100
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.219]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0235.001; Tue, 29 Aug 2017 17:20:04 +0800
From: "Zhuangyan (Yan)" <zhuangyan.zhuang@huawei.com>
To: Benoit Claise <bclaise@cisco.com>, "i2rs-chairs@ietf.org" <i2rs-chairs@ietf.org>
CC: "i2rs@ietf.org" <i2rs@ietf.org>
Thread-Topic: [i2rs] I2RS and duplicate YANG module definitions
Thread-Index: AdMgp/9aGmJcJMxnQZmfNdVJUaw5MA==
Date: Tue, 29 Aug 2017 09:20:04 +0000
Message-ID: <9B4BC45FDEDDD84F813E9E4A5BAF8785A95CD67E@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.135.170.230]
Content-Type: multipart/alternative; boundary="_000_9B4BC45FDEDDD84F813E9E4A5BAF8785A95CD67Enkgeml513mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020206.59A531CF.0066, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.1.219, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 61e71f23c7eb60f847931700a4c972c5
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/gcJZ5t1e06NUaWP6kSDJFjD9W0Y>
Subject: Re: [i2rs] I2RS and duplicate YANG module definitions
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: Tue, 29 Aug 2017 09:20:20 -0000

Hi Benoit,

Sure, we will update the service module draft accordingly.

Best Regards,

Yan

发件人: i2rs [mailto:i2rs-bounces@ietf.org] 代表 Benoit Claise
发送时间: 2017年8月29日 14:47
收件人: i2rs-chairs@ietf.org
抄送: i2rs@ietf.org
主题: [i2rs] I2RS and duplicate YANG module definitions

Dear all,

I see that ietf-fabric-types@2016-09-29.yang<mailto:ietf-fabric-types@2016-09-29.yang> is extracted from draft-ietf-i2rs-yang-dc-fabric-network-topology-00.txt<http://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-dc-fabric-network-topology>
And that ietf-fabric-types@2016-10-13.yang<mailto:ietf-fabric-types@2016-10-13.yang> is extracted from draft-zhuang-i2rs-dc-fabric-service-model-03.txt<http://datatracker.ietf.org/doc/draft-zhuang-i2rs-dc-fabric-service-model>
Should draft-zhuang-i2rs-dc-fabric-service-model-03.txt<http://datatracker.ietf.org/doc/draft-zhuang-i2rs-dc-fabric-service-model> be updated by draft-ietf-i2rs-yang-dc-fabric-network-topology-00.txt<http://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-dc-fabric-network-topology>, in the tracker?

Similar issues with "ietf-fabric-topology@2017-03-10.yang"<mailto:ietf-fabric-topology@2017-03-10.yang> and "ietf-fabric-topology-state@2017-06-29.yang"<mailto:ietf-fabric-topology-state@2017-06-29.yang> between these two drafts.

Regards, Benoit

v2.23.0 | Report a Bug | By Email