Re: [i2rs] I2RS and duplicate YANG module definitions
Benoit Claise <bclaise@cisco.com> Tue, 29 August 2017 10:34 UTC
Return-Path: <bclaise@cisco.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 741E3132339; Tue, 29 Aug 2017 03:34:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.489
X-Spam-Level:
X-Spam-Status: No, score=-14.489 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 2QIwGClbiCCv; Tue, 29 Aug 2017 03:34:16 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1406B1321B7; Tue, 29 Aug 2017 03:34:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8851; q=dns/txt; s=iport; t=1504002856; x=1505212456; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=mJBt12PuW87vbkxeSJct9LbP5warFTh3GEH6thhd0Yg=; b=OCTkL73xLCbINflX8NuduwfJryNcf4lo5P5vAYYTw17ZXj/2QcglShfc TEzpHECABsQOdaYjVO9lztOImLapIUyI92g3f5GwA1Yv7N/xJe9PAspfe MGVmqF7bbpv2dwAhOkxpyKUegcoL23h1X1iGjdxhCXLE3s3dpL01ISU3i g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AoBgBjQqVZ/xbLJq1eHAEBBAEBCgEBgm+BT4EVg3eLEaIBhUyCBC6FGQKETRUBAgEBAQEBAQFrKIUZBiMKTBAJAj8DAgJGEQYBDAYCAQGKLRCSNp1mgicnizsBAQEBAQEBAQEBAQEBAQEBAQEBAQEdgyqDUIIOgn2EPW6CXYJhBaBoh1mMc4ISWohmhxmJd4NZhDGEQTUigQ0yIQgcFYdmPjaLIQEBAQ
X-IronPort-AV: E=Sophos;i="5.41,444,1498521600"; d="scan'208,217";a="657096797"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Aug 2017 10:34:14 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v7TAYDKe013824; Tue, 29 Aug 2017 10:34:13 GMT
To: "Zhuangyan (Yan)" <zhuangyan.zhuang@huawei.com>, "i2rs-chairs@ietf.org" <i2rs-chairs@ietf.org>
Cc: "i2rs@ietf.org" <i2rs@ietf.org>
References: <9B4BC45FDEDDD84F813E9E4A5BAF8785A95CD67E@nkgeml513-mbx.china.huawei.com>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <7b55bd77-a747-2bc3-1f31-8b0d0b06c3f6@cisco.com>
Date: Tue, 29 Aug 2017 12:34:13 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <9B4BC45FDEDDD84F813E9E4A5BAF8785A95CD67E@nkgeml513-mbx.china.huawei.com>
Content-Type: multipart/alternative; boundary="------------B7B55277F881A604C24538DC"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/yYJTFVrl46RMxGi0nXbEIGojBqo>
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 10:34:18 -0000
Yan, The "update" has been introduced in https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-dc-fabric-network-topology/ That will simplify the YANG modules extraction. Regards, B. > > 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 >
- [i2rs] I2RS and duplicate YANG module definitions Benoit Claise
- Re: [i2rs] I2RS and duplicate YANG module definit… Zhuangyan (Yan)
- Re: [i2rs] I2RS and duplicate YANG module definit… Benoit Claise