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 BE57C12D6B1;
 Sat, 16 Jul 2016 11:09:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.807
X-Spam-Level: 
X-Spam-Status: No, score=-15.807 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,
 RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01,
 RP_MATCHES_RCVD=-1.287, SPF_PASS=-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 MSFNT5eTfv6Q; Sat, 16 Jul 2016 11:09:48 -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 8941412B04D;
 Sat, 16 Jul 2016 11:09:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;
 d=cisco.com; i=@cisco.com; l=2050; q=dns/txt; s=iport;
 t=1468692587; x=1469902187;
 h=to:cc:from:subject:message-id:date:mime-version;
 bh=f+8oajnf+FRYDlN+GTp2wp4EgaAt2onzh5/+iEZMAb4=;
 b=MxvUEJqnIsu2UdXXPVqporiH/FjsOwIEpM547RdmdImyA766suRfqdCy
 jNUWZqh/9WYuhObv1Wyv359DXFZYgF0k1RDHxGB+L3xI8/6GzH78aSuVW
 NRupr7HuKeRsoadhnt6P3CW5ipXr4AhGL8AxRCKOb8VvBrxjupWyZMfz0 o=;
X-IronPort-AV: E=Sophos;i="5.28,374,1464652800"; 
 d="scan'208,217";a="636766638"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com)
 ([173.38.203.22])
 by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384;
 16 Jul 2016 18:09:46 +0000
Received: from [10.61.161.254] ([10.61.161.254])
 by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u6GI9jK5030179;
 Sat, 16 Jul 2016 18:09:45 GMT
To: draft-zhuang-i2rs-yang-dc-fabric-network-topology@ietf.org
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <4cd1dcb1-7043-64e4-48f8-29f5c526ba71@cisco.com>
Date: Sat, 16 Jul 2016 20:09:46 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.2.0
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="------------350315261BA044BCCDEB25A8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/d2ezj4rsL_cdnHownE4o0edF7d4>
Cc: "i2rs@ietf.org" <i2rs@ietf.org>,
 "Carl Moberg \(camoberg\)" <camoberg@cisco.com>
Subject: [i2rs] draft-zhuang-i2rs-yang-dc-fabric-network-topology-00.txt:
 YANG compilation error
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.17
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: Sat, 16 Jul 2016 18:09:50 -0000

This is a multi-part message in MIME format.
--------------350315261BA044BCCDEB25A8
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Dear authors,

Part of the IETF hackathon today, I integrated confdc , as a second YANG 
module compiler, in http://www.claise.be/IETFYANGPageCompilation.html. 
Reason? For example, confdc validates xpath while pyang doesn't.
And confdc found an issue with your draft, which is now flagged as 
failing the YANG compilation.
Please correct this issue.
Note: you're not alone, look at the green dip today on green graph 
<http://claise.be/IETFYANGPageCompilation.png>!

During the hackathon today, Carl Moberg also integrated the confdc 
output in his www.yangalidtor.com.
This might help you.

Regards, Benoit

--------------350315261BA044BCCDEB25A8
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Dear authors, <br>
    <br>
    Part of the IETF hackathon today, I integrated confdc , as a second
    YANG module compiler, in
    <a class="moz-txt-link-freetext" href="http://www.claise.be/IETFYANGPageCompilation.html">http://www.claise.be/IETFYANGPageCompilation.html</a>. Reason? For
    example, confdc validates xpath while pyang doesn't.<br>
    And confdc found an issue with your draft, which is now flagged as
    failing the YANG compilation.<br>
    Please correct this issue. <br>
    Note: you're not alone, look at <a
      href="http://claise.be/IETFYANGPageCompilation.png">the green dip
      today on green graph</a>!<br>
    <br>
    During the hackathon today, Carl Moberg also integrated the confdc
    output in his <a class="moz-txt-link-abbreviated" href="http://www.yangalidtor.com">www.yangalidtor.com</a>.<br>
    This might help you.<br>
    <br>
    Regards, Benoit
  </body>
</html>

--------------350315261BA044BCCDEB25A8--

