Re: [Rtg-yang-coord] container with presence
Mahesh Jethanandani <mjethanandani@gmail.com> Thu, 28 May 2015 20:38 UTC
Return-Path: <mjethanandani@gmail.com>
X-Original-To: rtg-yang-coord@ietfa.amsl.com
Delivered-To: rtg-yang-coord@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id E965C1A88F5
for <rtg-yang-coord@ietfa.amsl.com>; Thu, 28 May 2015 13:38:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,
DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 3mCNPqaPpBcx for <rtg-yang-coord@ietfa.amsl.com>;
Thu, 28 May 2015 13:38:02 -0700 (PDT)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com
[IPv6:2607:f8b0:400e:c02::22a])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id CE6261A8880
for <Rtg-yang-coord@ietf.org>; Thu, 28 May 2015 13:38:01 -0700 (PDT)
Received: by pdea3 with SMTP id a3so49528928pde.2
for <Rtg-yang-coord@ietf.org>; Thu, 28 May 2015 13:38:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=content-type:mime-version:subject:from:in-reply-to:date:cc
:content-transfer-encoding:message-id:references:to;
bh=l1YKQlQz3ndN+lBRrKMk+nGeG69N4FUjNjni041OFoE=;
b=Jgy3KCogEZeanlC/Mv4Xh+CbC1WGqVCBsbesLGOjCSgE9VAFOwjGLaboWtZkihLGP7
B3Y4sSz48ez6HK1fNiDjmHpAHboQ+G/YAN1iWM9BCArw91jKKaLsj1VasRmqCr3quQV8
+bvz1Mokn/zdtvILvHcuU4c1/cQMNErT3H8PO1/Xo4Yk3yUBpp5LSCIfBop0IGZvOEgD
+Pud1zRTMq6T8vAIL9qzS5g/mNnQsJR4WGDYVUQMoXVvqkhBdzpYXuZh8NDoyxpMB5xj
Iee0difpl42CM8fqjnR/5QlaxjPlLv69R7OYqkEau5BeaRAbjqTuHlBrkcAYrhZM1VZ6
nnUA==
X-Received: by 10.68.68.142 with SMTP id w14mr8764688pbt.95.1432845481363;
Thu, 28 May 2015 13:38:01 -0700 (PDT)
Received: from ?IPv6:2001:420:302:1330:7197:4184:582e:ba8f?
([2001:420:302:1330:7197:4184:582e:ba8f])
by mx.google.com with ESMTPSA id nb10sm3276303pdb.76.2015.05.28.13.38.00
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Thu, 28 May 2015 13:38:00 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: Mahesh Jethanandani <mjethanandani@gmail.com>
In-Reply-To: <331A2562-6D35-4D49-911E-9881CCE5D6A1@nic.cz>
Date: Thu, 28 May 2015 13:38:24 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C4730376-085F-4660-B4F7-9BA4FC9B234A@gmail.com>
References: <331A2562-6D35-4D49-911E-9881CCE5D6A1@nic.cz>
To: Ladislav Lhotka <lhotka@nic.cz>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/-Sp6vQGK-HUGB4vJHHH0haivPn4>
Cc: Rtg-yang-coord@ietf.org
Subject: Re: [Rtg-yang-coord] container with presence
X-BeenThere: rtg-yang-coord@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "\"List to discuss coordination between the Routing related YANG
models\"" <rtg-yang-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-yang-coord>,
<mailto:rtg-yang-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-yang-coord/>
List-Post: <mailto:rtg-yang-coord@ietf.org>
List-Help: <mailto:rtg-yang-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-yang-coord>,
<mailto:rtg-yang-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 May 2015 20:38:04 -0000
And the error that will pop up as result will be something like this: Warning: top-level NP container ‘twamp-client' is mandatory ietf-twamp.yang:59.9: warning(1048): top-level object is mandatory > On May 28, 2015, at 2:28 AM, Ladislav Lhotka <lhotka@nic.cz> wrote: > > Hi, > > I have a suggestion for the authors of all routing protocol modules: the container that encapsulates all configuration data for a given protocol should be a container with presence (see sec. 7.5.1 in RFC 6020) because then the configuration data may include mandatory items that are otherwise forbidden at the top level of an augment. > > See also YANG 1.1 issue Y26: > > https://svn.tools.ietf.org/svn/wg/netmod/yang-1.1/issues.html#sec-27 > > For example, in the the ietf-isis it should look like this: > > augment "/rt:routing/rt:routing-instance/rt:routing-protocols/" > +"rt:routing-protocol" { > when "rt:type = 'isis:isis'" { > description > "This augment is only valid when routing protocol > instance type is isis."; > } > presence "IS-IS routing protocol”; > ... > } > > I am also including this recommendation in the routing-cfg draft. > > Lada > -- > Ladislav Lhotka, CZ.NIC Labs > PGP Key ID: E74E8C0C > > > > > _______________________________________________ > Rtg-yang-coord mailing list > Rtg-yang-coord@ietf.org > https://www.ietf.org/mailman/listinfo/rtg-yang-coord Mahesh Jethanandani mjethanandani@gmail.com
- [Rtg-yang-coord] container with presence Ladislav Lhotka
- Re: [Rtg-yang-coord] container with presence Ladislav Lhotka
- Re: [Rtg-yang-coord] container with presence Susan Hares
- Re: [Rtg-yang-coord] container with presence Ladislav Lhotka
- Re: [Rtg-yang-coord] container with presence Mahesh Jethanandani
- Re: [Rtg-yang-coord] container with presence Ladislav Lhotka
- Re: [Rtg-yang-coord] container with presence Andy Bierman
- Re: [Rtg-yang-coord] container with presence Ladislav Lhotka
- Re: [Rtg-yang-coord] container with presence Susan Hares
- Re: [Rtg-yang-coord] container with presence Ladislav Lhotka