[i2rs] I2RS and duplicate YANG module definitions
Benoit Claise <bclaise@cisco.com> Tue, 29 August 2017 06:46 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 C571B132386; Mon, 28 Aug 2017 23:46:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.6
X-Spam-Level:
X-Spam-Status: No, score=-12.6 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, 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, 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 Q1cJEtCm3yrg; Mon, 28 Aug 2017 23:46:52 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 497EB1320BB; Mon, 28 Aug 2017 23:46:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2741; q=dns/txt; s=iport; t=1503989212; x=1505198812; h=to:cc:from:subject:message-id:date:mime-version; bh=5WlFfI3Sc9wWRoGDIsNwdlE/2YjqiJAkqiwIFcX4MIw=; b=CJoI5WVckzPJGih7VXGME3mWTP7a+iTUeRRxpnOnwkHBmegq4bmqMS2X YuSIcxGuhcAbNDLju3GL5mpPkxfS43vrqT7f0WRRuNYrxnt6Nzf4QI+qw /qv7W3IjcENxRbu7qt47KLXL/zSWn+u+yv3BGJYvXcafmlGbha+7ofdES c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DEAwB1DKVZ/xbLJq1eGwEBAQMBAQEJAQEBhD6BFQGDdosRkHWRC4VMggQuhRmERhUBAgEBAQEBAQFrHQuFQlYfAT0CXw0GAgEBii0QsSyCJyeLPgEBAQEGAQEBAQEBIoMqg1CCDguHL4NLgmEFoGeHWYxygmyIZYcZjU2EMYRBNSKBDTIhCBwVh2Y+NosbAQEB
X-IronPort-AV: E=Sophos;i="5.41,444,1498521600"; d="scan'208,217";a="655271982"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Aug 2017 06:46:50 +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 v7T6knZ2031112; Tue, 29 Aug 2017 06:46:50 GMT
To: "i2rs-chairs@ietf.org" <i2rs-chairs@ietf.org>
Cc: "i2rs@ietf.org" <i2rs@ietf.org>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <f1e3a13b-3077-794d-0586-223f92d071e3@cisco.com>
Date: Tue, 29 Aug 2017 08:46:51 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------7FB3BE6E4CCBA023579D8A30"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/Li8_ekjQ86hqDS0ZvfyQ64wFfQw>
Subject: [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 06:46:55 -0000
Dear all, I see that 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 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" and "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