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

Martin Bjorklund <mbj@tail-f.com> Mon, 30 July 2018 18:43 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 799C4130EAE; Mon, 30 Jul 2018 11:43:40 -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 e6Q4CZqe2lc5; Mon, 30 Jul 2018 11:43:39 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 03812129619; Mon, 30 Jul 2018 11:43:39 -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 469D51AE0290; Mon, 30 Jul 2018 20:43:38 +0200 (CEST)
Date: Mon, 30 Jul 2018 20:43:38 +0200
Message-Id: <20180730.204338.1880656734367112577.mbj@tail-f.com>
To: kwatsen@juniper.net
Cc: evoit=40cisco.com@dmarc.ietf.org, yang-doctors@ietf.org, netconf@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <277A3AB6-40E9-466C-9FF6-316EC38737E7@juniper.net>
References: <727ae35abd394a85812168615acce2d3@XCH-RTP-013.cisco.com> <20180729.175356.1841285666617255654.mbj@tail-f.com> <277A3AB6-40E9-466C-9FF6-316EC38737E7@juniper.net>
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/rNIVvSvVaxNe_NBBnqyUUPP6oNA>
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: Mon, 30 Jul 2018 18:43:41 -0000

Kent Watsen <kwatsen@juniper.net> wrote:
> 
> 
> 
> > I assume that an augmentation would be done like this:
> >
> >   module ietf-netconf-subscribed-notifications {
> >     ...
> >     prefix nsn;
> >    
> >     identity netconf { ... }
> >
> >     augment /subscriptions/subscription/receivers/receiver/transport {
> >       when 'derived-from-or-self(../../../transport, "nsn:netconf"');
> >    
> >        case netconf {
> >          // leafref to call-home config
> >        }
> >      }
> >    }
> >
> > ... so that *if* the client configures the mandatory "transport" leaf
> > to "nsn:netconf", then it also MUST configure the corresponding
> > netconf-specific params.
> 
> 
> But this depends greatly on the "notif" model having the right
> "when" statement.  Will non-IETF notif models always do this?

It is not really crucial.  And if a vendor-specific model is badly
written, well, then it is badly written...


/martin


> 
> 
> > /martin
> 
> Kent // contributor
> 
> 
>