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

Martin Bjorklund <mbj@tail-f.com> Wed, 15 August 2018 21:03 UTC

Return-Path: <mbj@tail-f.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 1A889130E12 for <netconf@ietfa.amsl.com>; Wed, 15 Aug 2018 14:03:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 GkmvQlmV-zZA for <netconf@ietfa.amsl.com>; Wed, 15 Aug 2018 14:03:19 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 11B19130E02 for <netconf@ietf.org>; Wed, 15 Aug 2018 14:03:19 -0700 (PDT)
Received: from localhost (h-80-27.A165.priv.bahnhof.se [212.85.80.27]) by mail.tail-f.com (Postfix) with ESMTPSA id 7D2991AE0118; Wed, 15 Aug 2018 23:03:17 +0200 (CEST)
Date: Wed, 15 Aug 2018 23:03:16 +0200 (CEST)
Message-Id: <20180815.230316.1097239410478486890.mbj@tail-f.com>
To: evoit@cisco.com
Cc: kwatsen@juniper.net, netconf@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <2fddae1d98df4fbb8561bae86bd94d17@XCH-RTP-013.cisco.com>
References: <fd1642302aa1407da1ca22d14d4c6f8f@XCH-RTP-013.cisco.com> <20180814.235447.386903603331582623.mbj@tail-f.com> <2fddae1d98df4fbb8561bae86bd94d17@XCH-RTP-013.cisco.com>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/-AlUbLj3W5Mlp5aAlEBt8H62qnI>
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 21:03:21 -0000

"Eric Voit (evoit)" <evoit@cisco.com> wrote:
> 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.

Yes, all example modules that we put into rfcs should be called
example-...  See section 4.1 in 6087bis.

I think Kent had some suggestion for how to name the transport
modules, so we should follow that also for this example module.


/martin


> 
> 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
> > >
>