Re: [netmod] YANG tree diagram uses

Benoit Claise <bclaise@cisco.com> Sun, 04 February 2018 09:24 UTC

Return-Path: <bclaise@cisco.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F597124C27 for <netmod@ietfa.amsl.com>; Sun, 4 Feb 2018 01:24:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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, 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 XEuo1xseWn0g for <netmod@ietfa.amsl.com>; Sun, 4 Feb 2018 01:24:15 -0800 (PST)
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 DA9FE1241FC for <netmod@ietf.org>; Sun, 4 Feb 2018 01:24:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1961; q=dns/txt; s=iport; t=1517736255; x=1518945855; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=wIVPHEmsZoSPv4eXrBo54V3knYSRMLquc40FZtyb2B8=; b=EIttYRGmZIhunKQHdsM4fTca8CXMQZSZXuMv7bFV7bi75EEpjeS/5jZP I0Pn59vRd737kzPsleKHWTrQu5pKjamQ60+q7ODOyLMKna7A1Tfd7UKhT aBfhW1eUPHiFhwiLrQwDHGbLboul7sjDf8gnw5MUYh/+ezDbW6OMC0uYD s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ByAQDH0HZa/xbLJq1aGQEBAQEBAQEBAQEBAQcBAQEBAYQ3cCiOfY87mWAKGAuESU8CgxAUAQEBAQEBAQECayiFJAEBBAEBMAEFNgsQCw4KLicwBgEMBgIBAYoxEMIThQCDcoIGAQEBAQEBAQEBAQEBAQEBAQEBAQEZBYRqg2yBaCmDBYMvAQECh2sFkkWRYIwbiVaMN4gAj1+IF4E8NiKBUDMaCBsVPYJGhHhAN4wlAQEB
X-IronPort-AV: E=Sophos;i="5.46,458,1511827200"; d="scan'208";a="1844971"
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; 04 Feb 2018 09:24:03 +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 w149O3d3010076; Sun, 4 Feb 2018 09:24:03 GMT
To: Martin Bjorklund <mbj@tail-f.com>, mvasko@cesnet.cz
Cc: netmod@ietf.org
References: <4f1c-5a703c80-79-5fc7eb00@206654228> <20180130.160056.1269600856222747465.mbj@tail-f.com>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <b83b8e9b-f371-04f6-b47a-563d28e64d02@cisco.com>
Date: Sun, 04 Feb 2018 10:24:03 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <20180130.160056.1269600856222747465.mbj@tail-f.com>
Content-Type: text/plain; charset="iso-8859-15"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/FvknIjpoWUlPokdWOL0oPA6lLTo>
Subject: Re: [netmod] YANG tree diagram uses
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Feb 2018 09:24:17 -0000

Martin, Michal,

Do we need any clarification in the draft?

Regards, B.
> Michal Vaško <mvasko@cesnet.cz> wrote:
>> Hi,
>>
>> we have encountered some problem while implementing a feature from
>> draft-ietf-netmod-yang-tree-diagrams-05, specifically not resolving
>> groupings and printing uses names instead (Section 2.2).
>>
>> We have 2 example models, A and B. A defines a container and a
>> grouping. B defines an augment that adds uses into the container from
>> A and resolves to the grouping from model A.
>>
>> grouping A:g;
>> A:c {
>>    B:uses A:g;
>> }
>>
>> Now, if printing model A with the augment not resolving uses we
>> currently print
>>
>> +--rw c
>>     +---u B:A:g;
> pyang prints this as well, but it is more "by accident".   It looks
> quite odd.
>
> It wouldn't be correct to write
>
>      +---u B:g;
>
> since 'g' isn't defined in B.
>     
> OTOH,
>
>      +---u A:g;
>
> is correct in the sense that "A:g" is the "name of the grouping", and
> that is what the current document says should be printed.  Granted,
> this doesn't show the whole picture, but maybe this is good enough.
>
> It might be wise to not print a grouping like this in order to avoid
> confusion.
>
>
> /martin
>
>
>> since the uses is foreign. We could not decide what the "correct"
>> output should be and it is likely left to various interpretations but
>> we were wondering what some of you think. Should it perhaps be only
>> "B:g" since the grouping becomes local? But what if the grouping would
>> be from a third model, are 2 prefixes okay? Thanks for your opinions.
>>
>> Regards,
>> Michal
>>
>> _______________________________________________
>> netmod mailing list
>> netmod@ietf.org
>> https://www.ietf.org/mailman/listinfo/netmod
>>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
> .
>