[Teas] Mail regarding YANG in draft-ietf-pce-pcep-yang (impacted by draft-ietf-teas-yang-te)

Benoit Claise <bclaise@cisco.com> Wed, 21 February 2018 18:15 UTC

Return-Path: <bclaise@cisco.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0E3C12D951; Wed, 21 Feb 2018 10:15:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.531
X-Spam-Level:
X-Spam-Status: No, score=-14.531 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 VSroPY2Iyx8b; Wed, 21 Feb 2018 10:15:16 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5F65126B6E; Wed, 21 Feb 2018 10:15:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1841; q=dns/txt; s=iport; t=1519236915; x=1520446515; h=to:subject:cc:from:message-id:date:mime-version: content-transfer-encoding; bh=yM6SeoQ3TNb15SLZildzSKQQTLxxXvPL+6s36eWOwv8=; b=d4V8Kk7UGCf1DEvsi5qXna2ZUfrcofpj2OEHGLm/TzqoVdkgZPPGHyYi bMlm7IWdCH83Iz0Zlpw20uYIKvraKkUnwMZlBfiVnAZXLb+16/PxVAkRd MWHw2+WIpIZWvu6G9RnTGjsGa6ymkgfj+6yuHRKKd4qHJbtzzlZhsMtbV Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0C0CABTto1a/5hdJa1DGhsBAQEBAwEBA?= =?us-ascii?q?QkBAQGDT2ZwKINomB2BW4E+ll6CAgojhRGCelcVAQIBAQEBAQECayhCDAGEfg8?= =?us-ascii?q?BBUEZHAImAmwGAgEBih8QNIwTnXSCJ4UAg3mCEwEBCAEBAQEkgQ+EAoIngVeCE?= =?us-ascii?q?AyGKQIBAQEBgToBEQIBaoJLgmUFk2qQUQmCCoYdjWaCIIYpg3GIC44JggGIHIE?= =?us-ascii?q?8NSMlO3EzGggbFTqCQwmDAIILIzcBiBCCOCyCHwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.47,375,1515456000"; d="scan'208";a="358861403"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Feb 2018 18:15:14 +0000
Received: from [10.82.217.145] (rtp-vpn3-399.cisco.com [10.82.217.145]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id w1LIFClm006001; Wed, 21 Feb 2018 18:15:13 GMT
To: draft-ietf-pce-pcep-yang@ietf.org
Cc: draft-ietf-teas-yang-te@ietf.org, "teas@ietf.org" <teas@ietf.org>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <9c90a4a3-4a04-aa94-1119-fe712e572c90@cisco.com>
Date: Wed, 21 Feb 2018 13:15:11 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/xk_rLCQw0ie5lzMv23GF3x4dy2s>
Subject: [Teas] Mail regarding YANG in draft-ietf-pce-pcep-yang (impacted by draft-ietf-teas-yang-te)
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Feb 2018 18:15:18 -0000

Hi,

I started to see some errors for the draft-ietf-pce-pcep-yang YANG 
module today.
See https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-yang/#
Or http://www.claise.be/IETFYANGPageCompilation.html

This comes from the latest draft-ietf-teas-yang-te draft version.
draft-ietf-teas-yang-te authors, please make sure that dependent YANG 
modules are warned of the changes in your draft.

For example, ietf-actn-te-kpi-telemetry@2017-07-03.yang, 
ietf-actn-vn@2017-10-23.yang, ietf-pcep-stats@2018-01-05.yang, etc. 
don't validate any longer.

See 
https://www.yangcatalog.org/yang-search/impact_analysis.php?modules[]=ietf-te-types@2018-02-19.yang&modules[]=ietf-te@2018-02-19.yang&modules[]=ietf-te-device@2018-02-15.yang&modules[]=ietf-te-sr-mpls@2018-02-15.yang&modules[]=ietf-te-mpls@2018-02-15.yang&modules[]=ietf-te-mpls-types@2018-02-15.yang&recurse=0&rfcs=1&show_subm=1&show_dir=dependents

Querying the yangcatalog.org, here is the list of email of draft authors 
of ietf-te-types dependent YANG modules:
{
     "output": {
         "author-email": [
             "draft-zheng-ccamp-otn-client-signal-yang@ietf.org";,
             "draft-ietf-teas-yang-rsvp-te@ietf.org";,
             "draft-lee-teas-actn-vn-yang@ietf.org";,
             "draft-ietf-teas-yang-te@ietf.org";,
             "draft-ietf-pce-pcep-yang@ietf.org";,
             "draft-ietf-teas-yang-te-topo@ietf.org";,
             "draft-liu-teas-yang-l3-te-topo@ietf.org";,
             "draft-ietf-ccamp-otn-tunnel-model@ietf.org";,
             "draft-lee-teas-actn-pm-telemetry-autonomics@ietf.org";,
             "draft-ietf-teas-yang-path-computation@ietf.org";
         ]
     }
}

Regards, Benoit