From nobody Mon Sep 5 14:14:06 2016 Return-Path: X-Original-To: yang-multicast@ietfa.amsl.com Delivered-To: yang-multicast@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 235AD12B464 for ; Mon, 5 Sep 2016 14:14:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.029 X-Spam-Level: X-Spam-Status: No, score=-16.029 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_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_HELO_PASS=-0.001, 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 rx3hqb9iHnmk for ; Mon, 5 Sep 2016 14:14:03 -0700 (PDT) Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF4FB12B0D7 for ; Mon, 5 Sep 2016 14:14:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5814; q=dns/txt; s=iport; t=1473110042; x=1474319642; h=subject:references:to:from:message-id:date:mime-version: in-reply-to; bh=CaKAQlt8lc3WVXU+WL4MhM8IuKXT+92tmLgVcg0Fq7w=; b=J5Yb8HwIfi+XrJ0jExdgttvGPxfUDFi1cYWmxYDuhui7FXunL2bhLV6R QYPSNW+4/XJNAjuDt1rgYLg5eXFz0NqHjAllVu0kTtfBOn6/0pYyksTBh jXenLvNANUz31kUkDH2l3lGdQ2OBux874p47/Mlo5MiXv75rK7itMnsEf E=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BvBwA2381X/xbLJq1dHAEBBAEBgy0BA?= =?us-ascii?q?QEBAXUqUo0upXmFDYICGQEKhXgCggMUAQIBAQEBAQEBXidBEoQOAQEBBAEBAWs?= =?us-ascii?q?bHAMBAi8nJgIIEwYCAQEXiC8OvDkBAQEBAQUBAQEBASKGL4F4glaEEhEBPIUfH?= =?us-ascii?q?QWUCoVJhiGJFYI8hyGFfIkAg0yDeh42gxKBNzo0AYMjgUSCHwEBAQ?= X-IronPort-AV: E=Sophos;i="5.30,288,1470700800"; d="scan'208,217";a="687782218" Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Sep 2016 21:14:00 +0000 Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id u85LE0aS019190 for ; Mon, 5 Sep 2016 21:14:00 GMT References: <296084b3-791f-d33f-e46e-b1dd6adc66bd@cisco.com> To: yang-multicast@ietf.org From: Benoit Claise X-Forwarded-Message-Id: <296084b3-791f-d33f-e46e-b1dd6adc66bd@cisco.com> Message-ID: Date: Mon, 5 Sep 2016 23:14:00 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <296084b3-791f-d33f-e46e-b1dd6adc66bd@cisco.com> Content-Type: multipart/alternative; boundary="------------CCB4E5BD868549685F4A00FF" Archived-At: Subject: [Yang-multicast] Fwd: [yang-doctors] claise.be/xym/line number/YANG module download => easier troubleshooting X-BeenThere: yang-multicast@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: YANG Multicast List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Sep 2016 21:14:05 -0000 This is a multi-part message in MIME format. --------------CCB4E5BD868549685F4A00FF Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit FYI. Regards, B. -------- Forwarded Message -------- Subject: [yang-doctors] claise.be/xym/line number/YANG module download => easier troubleshooting Date: Mon, 5 Sep 2016 23:10:51 +0200 From: Benoit Claise To: YANG Doctors CC: Einar Nilsen-Nygaard (einarnn) , Per Hedeland , Jan Medved (jmedved) , 'Lou Berger' Dear all, I've been adding a new column to the report at http://www.claise.be/IETFYANGPageCompilation.html, where from you can download the extracted YANG module. Lately, I received some concerns about the line number from the pyang output that could not easily match to the YANG module line number. Indeed the pyang error line number is the one from the YANG module and not the IETF draft. This is specifically a concern with xpath issues. On top of that, some people use rfcstrip as opposed to xym.py to extract the YANG modules from IETF dratf. Along with the latest xym developments by Jan Medved (still working on it, so not yet in github), this should really ease the troubleshooting. Typically, you check a YANG module(s) from a specific draft at http://www.claise.be/IETFYANGPageCompilation.html. If you see a compilation error, you note the line number, download the extracted YANG module and you know directly where the error corresponds to. From there, you click on "Email Authors" and warn the authors of the mistake and related solution. All this from a single page. Regards, Benoit _______________________________________________ yang-doctors mailing list yang-doctors@ietf.org https://www.ietf.org/mailman/listinfo/yang-doctors . --------------CCB4E5BD868549685F4A00FF Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 7bit FYI.

Regards, B.


-------- Forwarded Message --------
Subject: [yang-doctors] claise.be/xym/line number/YANG module download => easier troubleshooting
Date: Mon, 5 Sep 2016 23:10:51 +0200
From: Benoit Claise <bclaise@cisco.com>
To: YANG Doctors <yang-doctors@ietf.org>
CC: Einar Nilsen-Nygaard (einarnn) <einarnn@cisco.com>, Per Hedeland <per@tail-f.com>, Jan Medved (jmedved) <jmedved@cisco.com>, 'Lou Berger' <lberger@labn.net> 


Dear all,

I've been adding a new column to the report at 
http://www.claise.be/IETFYANGPageCompilation.html, where from you can 
download the extracted YANG module.
Lately, I received some concerns about the line number from the pyang 
output that could not easily match to the YANG module line number.
Indeed the pyang error line number is the one from the YANG module and 
not the IETF draft. This is specifically a concern with xpath issues.
On top of that, some people use rfcstrip as opposed to xym.py to extract 
the YANG modules from IETF dratf.

Along with the latest xym developments by Jan Medved (still working on 
it, so not yet in github), this should really ease the troubleshooting.
Typically, you check a YANG module(s) from a specific draft at 
http://www.claise.be/IETFYANGPageCompilation.html.
If you see a compilation error, you note the line number, download the 
extracted YANG module and you know directly where the error corresponds to.
 From there, you click on "Email Authors" and warn the authors of the 
mistake and related solution.
All this from a single page.

Regards, Benoit

_______________________________________________
yang-doctors mailing list
yang-doctors@ietf.org
https://www.ietf.org/mailman/listinfo/yang-doctors
.
--------------CCB4E5BD868549685F4A00FF--