Re: [netmod] yang-data issues

Joe Clarke <jclarke@cisco.com> Mon, 22 October 2018 20:01 UTC

Return-Path: <jclarke@cisco.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 208DD130E61 for <netmod@ietfa.amsl.com>; Mon, 22 Oct 2018 13:01:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level:
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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 E1dsNNZvs150 for <netmod@ietfa.amsl.com>; Mon, 22 Oct 2018 13:01:23 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF7EF130E64 for <netmod@ietf.org>; Mon, 22 Oct 2018 13:01:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5275; q=dns/txt; s=iport; t=1540238482; x=1541448082; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=NCYmzF2iSM3gwMT590yRy5DDF5DGD5IjwmWaAKuj8WY=; b=CyTJj5L+D29zAyTfdDHGRlFqajMsXqpZRFfFheVT0PacopKaXJXhsK7u gtPsPrZT5F7Z5GgTlarI6/N+LCXwh1sgpYeZOQP9sF5saHJkpGxoYtbXJ szulGSK0llmGFyVSakTpnXaQyEN/l0ZAyQvbKj72vwJehD/Kfe0JoCnON Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BMAAD0K85b/51dJa1jGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBZYFbKmZ/KIN1lDOBYC2XKYFmDRgLhANGAoUVITgWAQM?= =?us-ascii?q?BAQIBAQJtHAyFOgEBAQMBAQEhDwE7CwwECQIRAwECAQICCRoDAgInHwkIBgE?= =?us-ascii?q?MBgIBAReDBgGBeQgPizCbTYEuih6BC4pHF4FBP4ERJ4JrgxsBAYEtAQESAQk?= =?us-ascii?q?WgwOCVwKIZIcojWlTCYZiigoGF4IehxWGe5ZdgVohZHFNIxU7gmwJgh0XfQE?= =?us-ascii?q?IAYJBhRSFWiMwihiCPgEB?=
X-IronPort-AV: E=Sophos;i="5.54,413,1534809600"; d="scan'208";a="468138728"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Oct 2018 20:01:21 +0000
Received: from [10.118.87.91] (rtp-jclarke-nitro10.cisco.com [10.118.87.91]) by rcdn-core-6.cisco.com (8.15.2/8.15.2) with ESMTP id w9MK1DjP011429; Mon, 22 Oct 2018 20:01:13 GMT
To: Andy Bierman <andy@yumaworks.com>, Kent Watsen <kwatsen@juniper.net>
Cc: "netmod@ietf.org" <netmod@ietf.org>
References: <20180911.104447.2165943059473950359.mbj@tail-f.com> <DAEC916E-564D-436E-8B34-6235BDC466AC@juniper.net> <CABCOCHT5NYseHZoqFR4FDV+0upePvQe=iUTwiuFAspcD-ejuWw@mail.gmail.com>
From: Joe Clarke <jclarke@cisco.com>
Openpgp: preference=signencrypt
Autocrypt: addr=jclarke@cisco.com; prefer-encrypt=mutual; keydata= xsDiBDo1cJ0RBADSZSmbmzdRr1CoRWWKmAyu0eaQimaLV1TsZEML/ksLyg6faXrKIA/MWc7M w4FmKkDjaZdFzobzabnKp2QwVadLqi1gYY2WsApKC0rSoqsPx5E847AmwNWXgjXiXORXmnZL mf5PZ2ECOEJC27sji5Nrh9GSw7OPp6c+EE20gMNVrwCgu3iK5vyGQfy0/wX/jcIvP0nHznUD /RvijiKomyaf6F5pibmouFNeuCDHc8lwx2giA/MCZl/nSkI2/UX27sULGNgvKNkVPu/AukXu zW3fIthsJgjQZUoi/BTe9kUP+RL3+RALXXuLv7b3xGRHJ8A1Rpy9H43fkjHZ945YNPrUvJlG LP5PNGBD1xC21X3EGAyywVynDskcA/4qgbJFkVzmPjFJUjq+RW1zw3UIb3bbkskl/wk5qd+M w2EhiSPTbEhJQAQUvqSGFWEGp2ANic7iYLdPXV/O6I1/guRRaY0eK77YkkCjz1snaKYnGSeI GHGwmHb6D+ZHzTqZqr6IssgEIUHjXfgOUTARQbL15nJTVRzDGUiT/65R3c0eSm9lIENsYXJr ZSA8amNsYXJrZUBjaXNjby5jb20+wl8EExECABcFAjyDqGQFCwcKAwQDFQMCAxYCAQIXgAAS CRDN7TXCWm4C3wdlR1BHAAEB5KkAn0kBda/9+uF6RfnDSFS7RExUU9DqAJ4knRckYiSASteC K03QVtEiXblL287ATQQ6NXCeEAQAhIURlK17jmIMdMIuScFU6xK+jkKgVVFrjlRH5vLV2spp jH/uQ57MMGuOcs7PckXCnPjBV8Tm32Tuw+fCyrbc2gt0ouiT/5WWj0EMeAfWew1zBXX2okGf LqS6gucVDS6tcEFN6PmJEmX+tWDcmiqx/xXiSfMVYiLMdlK+YDkMDDsAAwUD/3BWOyfdnBGH Kv28zx+5wq/2vhYnUYCAdVD2ZWCJizQTMbkcxEIKAwtAj6yqKq9ah82nt4VHl5ZejVe47jvR 2nXwJ5VQ9eITuTjTLDw+3qr9lN077VZ32hyb5ULJcW756j9Z3YB2FTANw6KHgChaSVVx9kYJ FlAggraU7mi39/wvwk4EGBECAAYFAjo1cJ4AEgkQze01wlpuAt8HZUdQRwABAQbdAJ9R8SzU Mluu9r93BMv6fAW9j6qTZgCfYcEAqOMJv+3Z+YxLiDtWcCY4Sfo=
Organization: Cisco
Message-ID: <a5bfb45e-e0ac-d3c2-af8a-1ab6f51b2818@cisco.com>
Date: Mon, 22 Oct 2018 16:01:13 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.2.1
MIME-Version: 1.0
In-Reply-To: <CABCOCHT5NYseHZoqFR4FDV+0upePvQe=iUTwiuFAspcD-ejuWw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Outbound-SMTP-Client: 10.118.87.91, rtp-jclarke-nitro10.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/Daedbof9LyqArxE-c-Z4Ji7Dbjk>
Subject: Re: [netmod] yang-data issues
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2018 20:01:36 -0000

On 10/22/18 13:41, Andy Bierman wrote:
> 
> 
> On Sat, Oct 20, 2018 at 5:48 AM, Kent Watsen <kwatsen@juniper.net
> <mailto:kwatsen@juniper.net>> wrote:
> 
>     Folks,
> 
>     Can we get some quick replies to this email?
> 
> 
> 
> At the last IETF there were people that said both yang-data and
> augment-yang-data extensions
> were needed and they wanted this work to be completed quickly.  Is that
> still the case?

Yes.  We're now seeing people that want to augment the ANIMA voucher
artifact (draft just proposed by Eliot Lear).  I have some non-IETF work
that would also benefit.

Joe

> 
> 
> IMO, NMDA and yang-library-bis offer a better solution path (which has
> been brought up before).
> If there is a need for specialized datastores like "factory-default"
> then why not have
> an abstract datastore or abstract module-set?  I do not think current
> YANG supports this
> approach very well (because modules used outside a server do not have
> yang-library)
> but that could probably be fixed with yang-instance-data
> 
> 
>     Kent // all hats
> 
> 
> 
> 
> Andy
>  
> 
> 
> 
>     -----Original Message-----
>     From: netmod <netmod-bounces@ietf.org
>     <mailto:netmod-bounces@ietf.org>> on behalf of Martin Bjorklund
>     <mbj@tail-f.com <mailto:mbj@tail-f.com>>
>     Date: Tuesday, September 11, 2018 at 4:45 AM
>     To: "netmod@ietf.org <mailto:netmod@ietf.org>" <netmod@ietf.org
>     <mailto:netmod@ietf.org>>
>     Subject: [netmod] yang-data issues
> 
>     Hi,
> 
>     The authors of draft-ietf-netmod-yang-data-ext have been discussing
>     the two remaining issues on this draft; the issue of whether a
>     yang-data structure must have unique top-level node names or not, and
>     the issue of the syntax for augment-yang-data.  We haven't been able
>     to find agreement with the current proposal, so I have a suggestion
>     for a slightly modified yang-data statement (which may have been
>     discussed before):
> 
>     The idea is to encode a yang-data extension the same way as anydata,
>     i.e., as a container.  For example:
> 
>       yd:yang-data modify-subscription-datastore-error-info {
>           description
>             "This yang-data MAY be provided as part of a subscription's RPC
>             error response when there is a failure of a
>             'modify-subscription' RPC which has been made against a
>             datastore.  This yang-data MUST be used if hints are to be
>             provides back to the subscriber.";
>           leaf reason {
>             type identityref {
>               base sn:modify-subscription-error;
>             }
>             description
>               "Indicates the reason why the subscription has failed to
>               be modified.";
>           }
>           uses hints;
>         }
> 
>     This would be encoded as:
> 
>       <modify-subscription-datastore-error-info>
>         <reason>foo</reason>
>         <period-hint>42</period-hint>
>         ...
>       </modify-subscription-datastore-error-info>
> 
> 
>     Since the structure is always encoded as a container, it follows that
>     it can have any data definition statement as substatement, with no
>     restriction on naming and type of statement.  An instance of this can
>     trivially be a complete instance document in XML w/o additional
>     context, works well with JSON, and can appear in an error-info
>     structure.
> 
>     Such a structure can be augemented as:
> 
>       yd:augment-yang-data /sn:modify-subscription-datastore-error-info {
>         leaf foo { ... }
>       }
> 
>     The drawback is that it forces the use of an extra container in the
>     encoding.  OTOH, most usages of current rc:yang-data follows this
>     pattern:
> 
>       rc:yang-data modify-subscription-datastore-error-info {
>         container modify-subscription-datastore-error-info {
>           ...
>         }
>       }
> 
> 
> 
> 
>     /martin
> 
>     _______________________________________________
>     netmod mailing list
>     netmod@ietf.org <mailto:netmod@ietf.org>
>     https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_netmod&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=9zkP0xnJUvZGJ9EPoOH7Yhqn2gsBYaGTvjISlaJdcZo&m=7nlVu5dJaa8XsD0LRd0VTH301caVRUXGsa6L-UgXVRE&s=1o7vXH-j8Ha6xbJFTG1jjNzy9JQw7k-UWIqpeCr8qrk&e=
>     <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_netmod&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=9zkP0xnJUvZGJ9EPoOH7Yhqn2gsBYaGTvjISlaJdcZo&m=7nlVu5dJaa8XsD0LRd0VTH301caVRUXGsa6L-UgXVRE&s=1o7vXH-j8Ha6xbJFTG1jjNzy9JQw7k-UWIqpeCr8qrk&e=>
> 
>     _______________________________________________
>     netmod mailing list
>     netmod@ietf.org <mailto:netmod@ietf.org>
>     https://www.ietf.org/mailman/listinfo/netmod
>     <https://www.ietf.org/mailman/listinfo/netmod>
> 
> 
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
>