From nobody Thu Jul 6 09:23:39 2017 Return-Path: X-Original-To: rtg-yang-coord@ietfa.amsl.com Delivered-To: rtg-yang-coord@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86A2A1317D2 for ; Thu, 6 Jul 2017 09:23:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 YQnyL_7jQWkj for ; Thu, 6 Jul 2017 09:23:36 -0700 (PDT) Received: from mail-wr0-x231.google.com (mail-wr0-x231.google.com [IPv6:2a00:1450:400c:c0c::231]) (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 7BC2B13163D for ; Thu, 6 Jul 2017 09:23:33 -0700 (PDT) Received: by mail-wr0-x231.google.com with SMTP id 77so9651152wrb.1 for ; Thu, 06 Jul 2017 09:23:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=lyQ2UtGxUA8u1KP6xEUOdzFyqI88zH0ay/BMpRbfq68=; b=IJCAa8nMcAji23SuZ1gf75qvUZk/d/vh6rDOxHjRQsgu4QwAGxaG5Iezz/u3FH5ueu u+7jHwEU4JcW0luhy8U056D6qzxlQDpMd3yEVFg8MhHd3L4VxclYH7bz4RZRrc3xvQDJ fP8LOabYrPK4hx57spEq73lryRZOnVdkwAInzYHngS5JxsuPw030zt3pim1LL+nzMzAQ kiCrfKdNaiuzKbFUSVOTFBj1W5x1Z7wChGb0uOgmNmYOxDdpPP965S8AJ+Tq78JMm5ON p8F9bIw0p9FoHbRi38PlrThOjWyD7ikSoE9OgvNic7/qoD3DEjI1DO0rOhEsneWrM1VY SIFA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=lyQ2UtGxUA8u1KP6xEUOdzFyqI88zH0ay/BMpRbfq68=; b=A/P+wej2ll992oVr+UgMlzA25gt037xT2cQnOrQPq31bClwhpf26VZ8SbybLpABWfZ XnywEtxl/deuVdgj3YYSrRkcKthRJXrHL5dAZhqOBhRbBnSTV837I2BjK2ooCMfrehbC C1xC6FxjhApSotUvsOSMZmg8vBt6iTUqTHwpTHqOr3zRWQxONNzfWdxKjBVQdfr9DiCg YtkdUcqLLkJMfJRPQXFaFtYYHb8cpfEYopfZmdmhHvaR4wTYTw5JTPcd6nMTrFgt2yQ0 L1YBEuZCnUtGlBFqHALKGy31XN9XS1ZNiecxGoixUb/y0HOIk8c7stmurWkiOMYGhMkG gzMg== X-Gm-Message-State: AKS2vOweI6azMxuM4aFGkeDLczPmwkW4KVHE3a+SDiuj1C+KmtDTt6v0 B74opaufrdoRoMwJ/0ur0I7oWUHwpClA X-Received: by 10.223.179.193 with SMTP id x1mr34223845wrd.86.1499358211856; Thu, 06 Jul 2017 09:23:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.130.179 with HTTP; Thu, 6 Jul 2017 09:23:31 -0700 (PDT) In-Reply-To: <149929190188.12960.15178727221967201992.idtracker@ietfa.amsl.com> References: <149929190188.12960.15178727221967201992.idtracker@ietfa.amsl.com> From: Alia Atlas Date: Thu, 6 Jul 2017 12:23:31 -0400 Message-ID: To: "Rtg-yang-coord@ietf.org" Content-Type: multipart/alternative; boundary="f403043897189be1540553a8891c" Archived-At: Subject: [Rtg-yang-coord] Fwd: New Non-WG Mailing List: Yot- Yang of Things X-BeenThere: rtg-yang-coord@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "\"List to discuss coordination between the Routing related YANG models\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2017 16:23:38 -0000 --f403043897189be1540553a8891c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable ---------- Forwarded message ---------- From: IETF Secretariat Date: Wed, Jul 5, 2017 at 5:58 PM Subject: New Non-WG Mailing List: Yot- Yang of Things To: IETF Announcement List Cc: bclaise@cisco.com, yot@ietf.org A new IETF non-working group email list has been created. List address: yot@ietf.org Archive: https://mailarchive.ietf.org/arch/search/?email_list=3Dyot To subscribe: https://www.ietf.org/mailman/listinfo/yot Purpose: YANG is the method of choice in the IETF for describing data models exposed by manageable items. It is currently being used in the context of the NETCONF (and, increasingly, RESTCONF) protocols, which generally target high-function devices. The Coman initiative (RFC 7547, 7548) investigated requirements and use cases for management of networks with constrained devices. Building blocks for protocols that make this a reality (COMI) are emerging in the CoRE working group; however, CoRE as a WG is not currently focused on network or device management. The "Yang of Things=E2=80=9D (YOT) non-WG mailing list will discuss best pr= actices for using YANG-based data modeling for the management of networks with constrained devices and constrained networks. It will also address how to best make use of properties of the combination of technologies involved (YANG, CBOR, SID, CoAP, RESTCONF, =E2=80=A6). Of interest are the ways thes= e same technologies could be applied outside the COMI focus of interest. The YOT mailing list will also be the proper forum to discuss new YANG modules targeting constrained devices and networks. For additional information, please contact the list administrators. --f403043897189be1540553a8891c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

---------- Forwarded messag= e ----------
From: IETF Secretariat <ietf-secre= tariat@ietf.org>
Date: Wed, Jul 5, 2017 at 5:58 PM
Subj= ect: New Non-WG Mailing List: Yot- Yang of Things
To: IETF Announcement = List <ietf-announce@ietf.org>
Cc: bclaise@cisco.com, <= a href=3D"mailto:yot@ietf.org">yot@ietf.org


A new IETF non-w= orking group email list has been created.

List address: yot@ietf.org
Archive: https://mailarchive.ietf.org/arch/search/?email_list=3Dyot
To subscribe: https://www.ietf.org/mailman/listinfo/yo= t

Purpose:
YANG is the method of choice in the IETF for describing data models exposed= by manageable items. It is currently being used in the context of the NETC= ONF (and, increasingly, RESTCONF) protocols, which generally target high-fu= nction devices. The Coman initiative (RFC 7547, 7548) investigated requirem= ents and use cases for management of networks with constrained devices. Bui= lding blocks for protocols that make this a reality (COMI) are emerging in = the CoRE working group; however, CoRE as a WG is not currently focused on n= etwork or device management.

The "Yang of Things=E2=80=9D (YOT) non-WG mailing list will discuss be= st practices for using YANG-based data modeling for the management of netwo= rks with constrained devices and constrained networks. It will also address= how to best make use of properties of the combination of technologies invo= lved (YANG, CBOR, SID, CoAP, RESTCONF, =E2=80=A6). Of interest are the ways= these same technologies could be applied outside the COMI focus of interes= t. The YOT mailing list will also be the proper forum to discuss new YANG m= odules targeting constrained devices and networks.

For additional information, please contact the list administrators.


--f403043897189be1540553a8891c-- From nobody Tue Jul 18 21:31:14 2017 Return-Path: X-Original-To: rtg-yang-coord@ietfa.amsl.com Delivered-To: rtg-yang-coord@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEDE412700F; Tue, 18 Jul 2017 21:31:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 XiivswicdgLj; Tue, 18 Jul 2017 21:31:11 -0700 (PDT) Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d:c09::22c]) (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 93609126B6E; Tue, 18 Jul 2017 21:31:11 -0700 (PDT) Received: by mail-qk0-x22c.google.com with SMTP id p126so27550091qkf.0; Tue, 18 Jul 2017 21:31:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=mU3wlIzmI6BbDH7xMfcegD1lF/rphKPSE4hhIFlC0/M=; b=iu5fgZhoHHGBSaIhtqUTUdqo0XepG3E3KZLpOKGc+UaQ5MmrS7rBoTU6hXpGX7FO9Z R4sw0xGBoYaCuIip4sGSWgIAPrXfpsvtNB95qlplp+HeuIKinlgutjsPtI9iesODSTVx kzKj+bw4tML+jw4y/3qNEfe5q2WzeNULfUNZeyzIjGfMfa34MzXBZE6q3kHi/EBv0/0v k9bL345AqEeEAT+uFMv+HOK+qrj2TVYYnIJr1dK0Xl+oaoNR2k4cKcELs1dQLjAfxt/C /nBkApi0GrVxqBvZG73UhkzwZn16lX7/Mbk1W795w3nkN6mDMtmipkfbNtIzAAFNc/D9 ZvMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=mU3wlIzmI6BbDH7xMfcegD1lF/rphKPSE4hhIFlC0/M=; b=L2lcjO7/6bKqiBCerL4Sh91l9j1LmuldHah8mGdhVHsdz/gVyjMmZ2WlFC/XZakdye 8H+/wDzbO7M+LijT+9LFIuRfANbB9a2ecbUS9u1jzqJzXlSLJJkLMmgjtmR2VNSBTqGM Ei4cw5kJdtenz745c/ktAUbPk9c2C2mgHqvuKNEospsDXMPN/sD2OPd2YhByYwhWyhf3 A6tRDwbkbMZ6aKaQrL2K69fKTmR51Ku/cU5VcOAwtFNtDBU6tVJqXNO1M371z8fBB6ww lUQ3ei/5WMTZTprrjF9yMx3wY3iFrBEcfNiGcZucv0Bp3nKSh4xbQKNDYvQnIeJ1yjok zB6A== X-Gm-Message-State: AIVw112tQo23yS3V3n+gjPJSJrylWPy7nAmyCvq80+V3R3WT7TVz2qc4 uNJDJ07vhxJnh/Npzr1kyR7KBKz2lg== X-Received: by 10.55.10.11 with SMTP id 11mr915381qkk.251.1500438670441; Tue, 18 Jul 2017 21:31:10 -0700 (PDT) MIME-Version: 1.0 Received: by 10.237.51.164 with HTTP; Tue, 18 Jul 2017 21:31:09 -0700 (PDT) In-Reply-To: References: From: Dhruv Dhody Date: Wed, 19 Jul 2017 10:01:09 +0530 Message-ID: To: yang-doctors@ietf.org, Benoit Claise Cc: "dhruv.dhody@huawei.com" , draft-ietf-pce-pcep-yang@ietf.org, pce-chairs@ietf.org, Rtg-yang-coord@ietf.org Content-Type: multipart/alternative; boundary="001a114c92bef583fa0554a41988" Archived-At: Subject: Re: [Rtg-yang-coord] Notification in Yang X-BeenThere: rtg-yang-coord@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "\"List to discuss coordination between the Routing related YANG models\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jul 2017 04:31:13 -0000 --001a114c92bef583fa0554a41988 Content-Type: text/plain; charset="UTF-8" Hi, A reminder.... This question remained un-answered, regarding the notifications in Yang model. Any guidance would be appreciated, thanks! Regards, Dhruv On Wed, May 17, 2017 at 5:50 PM, Dhruv Dhody wrote: > Hi Yang-Doctors, > > What is the guideline for including Notification in the Yang model, now > that [I-D.ietf-netconf-yang-push] and [I-D.ietf-netconf-subscribed-notifications] > is the preferred approach? > > Should we keep only "mandatory to implement notifications" in the Yang > model? Or just remove the notifications completely? > > A guideline to model writers would be helpful here, IMHO. > > Regards, > > Dhruv > > > > --001a114c92bef583fa0554a41988 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,=C2=A0

A reminder....=C2=A0
This question remained un-= answered, regarding the notifications in Yang model. Any guidance would be = appreciated, thanks!=C2=A0

Regar= ds,
Dhruv

On Wed, May 17, 2017 at 5:50 PM, Dhruv Dhody <dh= ruv.ietf@gmail.com> wrote:
= Hi Yang-Doctors,

What is the guideline for including Notification in the Yang model, now tha= t [I-D.ietf-netconf-yang-push] and [I-D.ietf-netconf-subscribed-notifi= cations] is the preferred approach?

Should we keep only "mandatory to implement notifications" in the= Yang model? Or just remove the notifications completely?

A guideline to model writers would be helpful here, IMHO.

Regards,

Dhruv




--001a114c92bef583fa0554a41988-- From nobody Tue Jul 18 23:03:41 2017 Return-Path: X-Original-To: rtg-yang-coord@ietfa.amsl.com Delivered-To: rtg-yang-coord@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D267612EB13 for ; Tue, 18 Jul 2017 23:03:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.199 X-Spam-Level: X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net 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 1gYR7TPIviXF for ; Tue, 18 Jul 2017 23:03:38 -0700 (PDT) Received: from gproxy5.mail.unifiedlayer.com (gproxy5-pub.mail.unifiedlayer.com [67.222.38.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CAF7129A97 for ; Tue, 18 Jul 2017 23:03:38 -0700 (PDT) Received: from cmgw4 (unknown [10.0.90.85]) by gproxy5.mail.unifiedlayer.com (Postfix) with ESMTP id E20A01404E2 for ; Tue, 18 Jul 2017 23:38:00 -0600 (MDT) Received: from box313.bluehost.com ([69.89.31.113]) by cmgw4 with id mVdx1v0032SSUrH01Ve0gz; Tue, 18 Jul 2017 23:38:00 -0600 X-Authority-Analysis: v=2.2 cv=eYdNR/MH c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=xqWC_Br6kY4A:10 a=G3gG6ho9WtcA:10 a=r77TgQKjGQsHNAKrUKIA:9 a=pGLkceISAAAA:8 a=48vgC7mUAAAA:8 a=Wh1fFEszq-NghL4PYtgA:9 a=QEXdDO2ut3YA:10 a=zDa0setxYYww4pvdCvcA:9 a=pHvTY0i16fvs11Vg:21 a=_W_S_7VecoQA:10 a=6kGIvZw6iX1k4Y-7sg4_:22 a=w1C3t2QeGrPiZgrLijVG:22 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Type:In-Reply-To:MIME-Version:Date:Message-ID: References:Cc:To:Subject:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=5Fxu8YLtmxzf6NxQCeRwWprjCYKZsDK8rF4nqN/jnoU=; b=HZBmg5qpuFhma/8XRYSJbJSJeX hCcq7Mi3DtLS9EFUY24CaL3Wgc3/P0owHJnZAJGr6R/93BtbHKbzw2GFIR6Jj7IKYyt3iFdq6+n84 gSWV/LKmtQNM73i5IhezMWXpC; Received: from pool-100-15-84-20.washdc.fios.verizon.net ([100.15.84.20]:48652 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from ) id 1dXhgK-001qyg-SA; Tue, 18 Jul 2017 23:37:57 -0600 From: Lou Berger To: Dhruv Dhody , yang-doctors@ietf.org, Benoit Claise Cc: "Rtg-yang-coord@ietf.org" , draft-ietf-pce-pcep-yang@ietf.org, dhruv.dhody@huawei.com, pce-chairs@ietf.org References: Message-ID: <484936b4-9493-4449-d3bf-4ff25a2c26c4@labn.net> Date: Wed, 19 Jul 2017 07:37:53 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------F588B40B945CE9DD2468A342" Content-Language: en-US X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - box313.bluehost.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - labn.net X-BWhitelist: no X-Source-IP: 100.15.84.20 X-Exim-ID: 1dXhgK-001qyg-SA X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: pool-100-15-84-20.washdc.fios.verizon.net ([IPv6:::1]) [100.15.84.20]:48652 X-Source-Auth: lberger@labn.net X-Email-Count: 7 X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ== Archived-At: Subject: Re: [Rtg-yang-coord] Notification in Yang X-BeenThere: rtg-yang-coord@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "\"List to discuss coordination between the Routing related YANG models\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jul 2017 06:03:40 -0000 This is a multi-part message in MIME format. --------------F588B40B945CE9DD2468A342 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Dhruv, Perhaps send a message on this to netmod. This topic has come up a couple of times this week and your suggestion of guidelines make sense and perhaps should be addressed in 6087bis. Thanks, Lou On July 19, 2017 6:31:46 AM Dhruv Dhody wrote: > Hi, > > A reminder.... > This question remained un-answered, regarding the notifications in > Yang model. Any guidance would be appreciated, thanks! > > Regards, > Dhruv > > On Wed, May 17, 2017 at 5:50 PM, Dhruv Dhody > wrote: > > Hi Yang-Doctors, > > What is the guideline for including Notification in the Yang > model, now that [I-D.ietf-netconf-yang-push] and > [I-D.ietf-netconf-subscribed-notifications] is the preferred approach? > > Should we keep only "mandatory to implement notifications" in the > Yang model? Or just remove the notifications completely? > > A guideline to model writers would be helpful here, IMHO. > > Regards, > > Dhruv > > > > > _______________________________________________ > Rtg-yang-coord mailing list > Rtg-yang-coord@ietf.org > https://www.ietf.org/mailman/listinfo/rtg-yang-coord > --------------F588B40B945CE9DD2468A342 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

Dhruv,

    Perhaps send a message on this to netmod.  This topic has come up a couple of times this week and your suggestion of guidelines make sense and perhaps should be addressed in 6087bis.

Thanks,

Lou


On July 19, 2017 6:31:46 AM Dhruv Dhody <dhruv.ietf@gmail.com> wrote:

Hi, 

A reminder.... 
This question remained un-answered, regarding the notifications in Yang model. Any guidance would be appreciated, thanks! 

Regards,
Dhruv

On Wed, May 17, 2017 at 5:50 PM, Dhruv Dhody <dhruv.ietf@gmail.com> wrote:
Hi Yang-Doctors,

What is the guideline for including Notification in the Yang model, now that [I-D.ietf-netconf-yang-push] and [I-D.ietf-netconf-subscribed-notifications] is the preferred approach?

Should we keep only "mandatory to implement notifications" in the Yang model? Or just remove the notifications completely?

A guideline to model writers would be helpful here, IMHO.

Regards,

Dhruv




_______________________________________________
Rtg-yang-coord mailing list
Rtg-yang-coord@ietf.org
https://www.ietf.org/mailman/listinfo/rtg-yang-coord

--------------F588B40B945CE9DD2468A342--