Re: [netmod] ?==?utf-8?q? mandatory choice with non-presence container case

Michal Vaško <mvasko@cesnet.cz> Mon, 24 June 2019 17:01 UTC

Return-Path: <mvasko@cesnet.cz>
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 AB9E012065B for <netmod@ietfa.amsl.com>; Mon, 24 Jun 2019 10:01:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cesnet.cz
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 hFcjdxPIv5Xh for <netmod@ietfa.amsl.com>; Mon, 24 Jun 2019 10:01:32 -0700 (PDT)
Received: from kalendar.cesnet.cz (kalendar.cesnet.cz [78.128.211.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5A4C12065D for <netmod@ietf.org>; Mon, 24 Jun 2019 10:01:31 -0700 (PDT)
Received: by kalendar.cesnet.cz (Postfix, from userid 999) id 863B4601AE; Mon, 24 Jun 2019 19:01:29 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cesnet.cz; s=kalendar; t=1561395689; bh=agw5wBkKkKwEGV/AozMTrXm9GFSy2BbN76gggdPhPRA=; h=In-Reply-To:From:Date:Cc:To:Subject; b=iEcoaFm8kfefk/GtfeuGVwgsi5vm4IS4X9ZBRjKvFwAEccr4pvuVGiQKU+612OOo8 a4Ag+ElfkP2vkgZ9KVT8JszHgzH/SiiyCAO/K4etAaClXkCx4Y56MpRrnEhCJgMZcy vC/LSwoWfNk83Tp1EkhKYn6lTLyVEMIko/BEwCRA=
Content-Type: text/plain; charset="utf-8"
In-Reply-To: <BYAPR11MB263111549D604096368CC2ABB5E00@BYAPR11MB2631.namprd11.prod.outlook.com>
From: Michal Vaško <mvasko@cesnet.cz>
X-Forward: 88.101.100.176
Date: Mon, 24 Jun 2019 19:01:29 +0200
Cc: netmod <netmod@ietf.org>
To: "Rob Wilton (rwilton)" <rwilton@cisco.com>
MIME-Version: 1.0
Message-ID: <7797-5d110200-71-35dfff00@18550405>
User-Agent: SOGoMail 2.3.23
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/53F4LCZX8o-MDGArgEJnEqD-7to>
Subject: Re: [netmod] ?==?utf-8?q? mandatory choice with non-presence container case
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 24 Jun 2019 17:01:35 -0000

Hi Rob,
I think there is a problem in the RFC because using only allowed steps I got invalid data from initially valid data. That cannot be correct.

Regards,
Michal

On Monday, June 24, 2019 18:52 CEST, "Rob Wilton (rwilton)" <rwilton@cisco.com> wrote: 
 
> Hi Michal,
> 
> My thoughts:
> 
> According to 7.5.1:
> 
>    In the first style, the container has no meaning of its own, existing
>    only to contain child nodes.  In particular, the presence of the
>    container node with no child nodes is semantically equivalent to the
>    absence of the container node.  YANG calls this style a "non-presence
>    container".  This is the default style.
> 
> Hence your request (because the NP container does not have any children) is equivalent to:
> 
>  <TOP>
>    <L/>
>  </TOP>
> 
> which fails the "mandatory" check.
> 
> Thanks,
> Rob
> 
> 
> > -----Original Message-----
> > From: netmod <netmod-bounces@ietf.org> On Behalf Of Michal Vaško
> > Sent: 24 June 2019 17:39
> > To: netmod <netmod@ietf.org>
> > Subject: [netmod] mandatory choice with non-presence container case
> > 
> > Hi,
> > I have encountered a situation that I think is not covered by RFC 7950. My
> > specific use-case was as follows.
> > 
> > model:
> > 
> > container TOP {
> >   leaf L {
> >     type empty;
> >   }
> >   choice A {
> >     mandatory true;
> >     container C;
> >   }
> > }
> > 
> > data:
> > 
> > <TOP>
> >   <L/>
> >   <C/>
> > </TOP>
> > 
> > Parsing was successful, but printing these data back to XML produced:
> > 
> > <TOP>
> >   <L/>
> > </TOP>
> > 
> > and parsing this correctly failed with missing mandatory choice. According
> > to section 7.5.7 [1], I think the C container could be omitted but the
> > whole situation does not seem correct. Thank you for any input.
> > 
> > Regards,
> > Michal
> > 
> > [1] https://tools.ietf.org/html/rfc7950#section-7.5.7
> > 
> > _______________________________________________
> > netmod mailing list
> > netmod@ietf.org
> > https://www.ietf.org/mailman/listinfo/netmod