IETF Logo Mail Archive

Re: [Softwires] Issue with ietf-dslite@2017-11-15.yang and yangdump-pro

<mohamed.boucadair@orange.com> Mon, 20 November 2017 13:31 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0C001296B3; Mon, 20 Nov 2017 05:31:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.617
X-Spam-Level:
X-Spam-Status: No, score=-2.617 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 DiAnTf1gxoaN; Mon, 20 Nov 2017 05:31:32 -0800 (PST)
Received: from orange.com (mta241.mail.business.static.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E69D1296B0; Mon, 20 Nov 2017 05:31:32 -0800 (PST)
Received: from opfedar06.francetelecom.fr (unknown [xx.xx.xx.8]) by opfedar25.francetelecom.fr (ESMTP service) with ESMTP id E6D9F120849; Mon, 20 Nov 2017 14:31:30 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.63]) by opfedar06.francetelecom.fr (ESMTP service) with ESMTP id BD3A780084; Mon, 20 Nov 2017 14:31:30 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM6E.corporate.adroot.infra.ftgroup ([fe80::f5a7:eab1:c095:d9ec%18]) with mapi id 14.03.0361.001; Mon, 20 Nov 2017 14:31:30 +0100
From: mohamed.boucadair@orange.com
To: Andy Bierman <andy@yumaworks.com>, Benoit Claise <bclaise@cisco.com>
CC: "draft-ietf-softwire-dslite-yang@ietf.org" <draft-ietf-softwire-dslite-yang@ietf.org>, Mahesh Jethanandani <mjethanandani@gmail.com>, "softwires@ietf.org" <softwires@ietf.org>
Thread-Topic: Issue with ietf-dslite@2017-11-15.yang and yangdump-pro
Thread-Index: AQHTYKB2ZYGrsDx+gk62O9uIGhBYrqMalMsAgAKxIkA=
Date: Mon, 20 Nov 2017 13:31:29 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93300A07D70F@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <10bf60a6-84bb-af3d-1789-09ca02794f46@cisco.com> <CABCOCHQkjNSte2ONpT4zRzbEzNtm7sUtEd9TwPcmoe_nz09fJA@mail.gmail.com>
In-Reply-To: <CABCOCHQkjNSte2ONpT4zRzbEzNtm7sUtEd9TwPcmoe_nz09fJA@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.6]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B93300A07D70FOPEXCLILMA3corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/18di43fQdLOsIeEibvX2lzZd0_U>
Subject: Re: [Softwires] Issue with ietf-dslite@2017-11-15.yang and yangdump-pro
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Nov 2017 13:31:33 -0000

Hi Andy, Benoit,

Thank you for investigating this.

A new version which fixes this issue is available online. A diff is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-softwire-dslite-yang-11

Cheers,
Med

De : Andy Bierman [mailto:andy@yumaworks.com]
Envoyé : samedi 18 novembre 2017 22:23
À : Benoit Claise
Cc : draft-ietf-softwire-dslite-yang@ietf.org; Mahesh Jethanandani
Objet : Re: Issue with ietf-dslite@2017-11-15.yang and yangdump-pro

Hi,

yangdump-pro is correct. Every other compiler missed it...


9.10.2.  The identityref's "base" Statement



   The "base" statement, which is a substatement to the "type"

   statement, MUST be present at least once if the type is

   "identityref".  The argument is the name of an identity, as defined

   by an "identity" statement.  If a prefix is present on the identity

   name, it refers to an identity defined in the module that was

   imported with that prefix.  Otherwise, an identity with the matching

   name MUST be defined in the current module or an included submodule.

Using ietf-dslite@2017-11-15.yang<mailto:ietf-dslite@2017-11-15.yang> and ietf-nat@2017-11-15.yang<mailto:ietf-nat@2017-11-15.yang>

When I change 'natp44' to 'nat:natp44' in both when-stmts:

andy@andy-homedev:~/Desktop/FD1289/IETF$ yangdump-pro ietf-dslite@2017-11-15.yang<mailto:ietf-dslite@2017-11-15.yang> modpath=.

*** /home/andy/Desktop/FD1289/IETF/ietf-dslite@2017-11-15.yang<mailto:/home/andy/Desktop/FD1289/IETF/ietf-dslite@2017-11-15.yang>
*** 0 Errors, 0 Warnings

andy@andy-homedev:~/Desktop/FD1289/IETF$


Andy


On Sat, Nov 18, 2017 at 11:07 AM, Benoit Claise <bclaise@cisco.com<mailto:bclaise@cisco.com>> wrote:
Hi Andy,

Can you please have a look at ietf-dslite@2017-11-15.yang<mailto:ietf-dslite@2017-11-15.yang> at http://www.claise.be/IETFYANGPageCompilation.html .
yangdump-pro reports a new error, while the other validators are fine.

Copying Mahesh, as YANG doctor.

Regards, Benoit

v2.23.0 | Report a Bug | By Email