Re: [Netconf] [yang-doctors] YANG Doctor question: empty mandatory choice?

"Eric Voit (evoit)" <evoit@cisco.com> Wed, 15 August 2018 20:57 UTC

Return-Path: <evoit@cisco.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CBB4130E1E for <netconf@ietfa.amsl.com>; Wed, 15 Aug 2018 13:57:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 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_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=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 AaioI5kKrAtL for <netconf@ietfa.amsl.com>; Wed, 15 Aug 2018 13:57:45 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6813C130E12 for <netconf@ietf.org>; Wed, 15 Aug 2018 13:57:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2217; q=dns/txt; s=iport; t=1534366665; x=1535576265; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=b7yBTrJNsD69XP0YJ4MfVHbFBs07IIeDfI9STv7M+Kw=; b=JuxOSesSwQRESoLLZPVb+SNwqp4uzQ41injiwejLQwyR+4pbMDWuyFJj LDz/7ledtvDxxiZPJQgjHwjkxx9mAR6yoeHWsvFeITtxwRjA2pBa4C5Fo mKa4LKOC0DQJqImQoDIoOPuKv6c2vAxasdgDfhSgLCbnP18t4+zZP6viv w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DNAQCMknRb/5xdJa1dGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYNPY38oCpghgg2WJ4FmCxgLhANGAoM0ITcVAQIBAQIBAQJ?= =?us-ascii?q?tHAyFNwEBAQMBAQE4NAsFCwIBCA4HAx4QJwslAgQBDQUIgxuBeQgPrH2KWwW?= =?us-ascii?q?JFBeBQT+EJIMbAQGBSYVOIAKJWZESCQKPUR2BOoQuiESSegIRFIEkMyKBUnA?= =?us-ascii?q?VO4JpixWFPm+NDoEbAQE?=
X-IronPort-AV: E=Sophos;i="5.53,244,1531785600"; d="scan'208";a="157545667"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 Aug 2018 20:57:44 +0000
Received: from XCH-RTP-015.cisco.com (xch-rtp-015.cisco.com [64.101.220.155]) by rcdn-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id w7FKviZT023217 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 15 Aug 2018 20:57:44 GMT
Received: from xch-rtp-013.cisco.com (64.101.220.153) by XCH-RTP-015.cisco.com (64.101.220.155) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 15 Aug 2018 16:57:43 -0400
Received: from xch-rtp-013.cisco.com ([64.101.220.153]) by XCH-RTP-013.cisco.com ([64.101.220.153]) with mapi id 15.00.1320.000; Wed, 15 Aug 2018 16:57:43 -0400
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: Martin Bjorklund <mbj@tail-f.com>, "kwatsen@juniper.net" <kwatsen@juniper.net>
CC: "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [Netconf] [yang-doctors] YANG Doctor question: empty mandatory choice?
Thread-Index: AQHUJ1ReOwlfbH+3hkGPLp9Bm3apCaS3Rs0AgAgy14CAAFoT4IAAU4OAgAE69bA=
Date: Wed, 15 Aug 2018 20:57:43 +0000
Message-ID: <2fddae1d98df4fbb8561bae86bd94d17@XCH-RTP-013.cisco.com>
References: <E4A0250D-B2B9-47D5-81EF-275A0144379A@juniper.net> <C266AC08-6C4D-4BF9-AA94-C90B30A9038C@juniper.net> <fd1642302aa1407da1ca22d14d4c6f8f@XCH-RTP-013.cisco.com> <20180814.235447.386903603331582623.mbj@tail-f.com>
In-Reply-To: <20180814.235447.386903603331582623.mbj@tail-f.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.56.234]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Outbound-SMTP-Client: 64.101.220.155, xch-rtp-015.cisco.com
X-Outbound-Node: rcdn-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/9vqFcGmQPc2N9LHxwboCMIHfvYg>
Subject: Re: [Netconf] [yang-doctors] YANG Doctor question: empty mandatory choice?
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Aug 2018 20:57:47 -0000

Hi Kent,
Hi Martin,

I posted -v16.   This version:

(1) Removes the empty mandatory choice "transport"

(2) Updates non-normative Appendix A so the example configured transport is no longer "NETCONF".  Instead it is now of transport "Foo".  Note: to stop automated inclusion in IETF model catalogs, I removed the <CODE BEGINS> and <CODE ENDS> for the augmentation example in Appendix A.  If instead either of you prefer renaming the YANG model to "example-transport-foo", and this renaming would also exclude the model from IETF processes, I am happy to make such a change.

Beyond this, I am not aware of other open issues.

Eric

> From: Martin Bjorklund, August 14, 2018 5:55 PM
> 
> Hi,
> 
> "Eric Voit (evoit)" <evoit@cisco.com> wrote:
> > Hi Kent,
> >
> > Before I post the change, there is the question of whether SN Appendix
> > A should be totally dropped, or whether it should be tweaked and
> > inserted into NETCONF-Notif.
> 
> I think an example of what a transport-specific module looks like should be in
> this document.  Adding an example tranport module to the netconf transport
> draft (that eventually already defines a real transport module) doesn't make
> much sense.
> 
> However, the example in this draft should be made for an example transport,
> rather than for NETCONF.  And the module should be named as such.
> Specifically, it must not be called "ietf-netconf-subscribed-notifications", but
> instead "example-something...".
> 
> 
> 
> /martin
> 
> 
> 
> 
> >
> > Moving it to NETCONF-Notif would allow SN section 2.5.7 to retain a
> > reference to a non-normative example augmentation without SN becoming
> > dependent on a document split of RESTCONF-Notif.
> >
> > Eric
> >
> > > No further comments are coming, so it seems that we've reached in end.
> > > I'm glad we had the discussion.
> > >
> > > Eric, please post an updated SN draft without the mandatory choice.
> > >
> > > Kent
> > >
> > >
> > >
> > > _______________________________________________
> > > Netconf mailing list
> > > Netconf@ietf.org
> > > https://www.ietf.org/mailman/listinfo/netconf
> >