Re: [netmod] yang-data-ext issues

Joe Clarke <jclarke@cisco.com> Mon, 25 June 2018 19:45 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 DD920130EED; Mon, 25 Jun 2018 12:45:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, 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 npBQE8SJp-sO; Mon, 25 Jun 2018 12:45:44 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CA59130EDC; Mon, 25 Jun 2018 12:45:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=873; q=dns/txt; s=iport; t=1529955944; x=1531165544; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=zXd29iAiXBIFpt1xk7Z8as0k4Fl0heuF2AZ5/fCWXGQ=; b=Jk9EfXKh/+wvXV9ANvRF1UVG/6oLgtEBzoHAcizla4veZvkf/OVoYIBY H5fFIrB0UQYSm2GmlkdAqpu0C+pHG9LZ5qOkRNpQSpfLP6yIVBSDyB39C 10MONxo6Nze6apDJgwP3dRuiASFnt7c5nENhEp7TdJifimL+bsVfKOnRn 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ChAQBlRTFb/4UNJK1cGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYMqAQEBASGBYYQhlEWBWwgilwQLhGwCgw0hOBQBAgEBAQE?= =?us-ascii?q?BAQJtKIUpAQUjVhALDgoCAiYCAlcGAQwIAQEXgwqCAKwFghyIR4EYgQuHYYF?= =?us-ascii?q?WP4E2DIJch3uCVQKZLwmPCwaBQIQGgkaFPYd0iXmBWCGBUk0jFYMlkGwjj3s?= =?us-ascii?q?BAQ?=
X-IronPort-AV: E=Sophos;i="5.51,271,1526342400"; d="scan'208";a="134489513"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Jun 2018 19:45:43 +0000
Received: from [10.118.87.86] (rtp-jclarke-nitro5.cisco.com [10.118.87.86]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id w5PJjhjT001877; Mon, 25 Jun 2018 19:45:43 GMT
To: Kent Watsen <kwatsen@juniper.net>, "netmod@ietf.org" <netmod@ietf.org>
Cc: "netmod-chairs@ietf.org" <netmod-chairs@ietf.org>, "draft-ietf-netconf-restconf@ietf.org" <draft-ietf-netconf-restconf@ietf.org>, "draft-ietf-netconf-zerotouch@ietf.org" <draft-ietf-netconf-zerotouch@ietf.org>, "draft-ietf-netconf-notification-messages@ietf.org" <draft-ietf-netconf-notification-messages@ietf.org>
References: <CABCOCHSupojOLssLebB-mR_PybRLA_4bcbaNF6-8ZUrx1Pu53w@mail.gmail.com> <20180502.092527.2305319833268262996.mbj@tail-f.com> <9fca04b0-fb29-36b3-67aa-2f2c4fb98748@cisco.com> <20180502.112506.845305331945500257.mbj@tail-f.com> <20180502093626.ugsg6nq24a6vjtdn@elstar.local> <64990DFB-CF50-401A-A4EF-B6161C8D227B@juniper.net> <20180529170900.qboedr2rmefsmblc@anna.jacobs.jacobs-university.de> <87muwe4pjt.fsf@nic.cz> <6AF80451-1644-4B1B-A6DD-3A42D4EEFB7A@juniper.net>
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: <e0b3b4bc-97bc-f3e0-1285-1a925f73c14e@cisco.com>
Date: Mon, 25 Jun 2018 15:45:42 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <6AF80451-1644-4B1B-A6DD-3A42D4EEFB7A@juniper.net>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/UNC6hODRoLtdBuO5s0OwBw5pwqg>
Subject: Re: [netmod] yang-data-ext issues
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.26
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, 25 Jun 2018 19:45:48 -0000

On 6/25/18 14:56, Kent Watsen wrote:
> 
> The authors of yang-data-ext met today to discuss how to move this draft forward.  After about an hour, we decided that the best course of action is to:
> 
>   * clarify RFC 8040 rc:yang-data for the zerotouch use case
>       - and update the zerotouch draft to use rc:yang-data
> 
>   * request this WG for the unadoption of this draft
>       - the notification-messages draft solution is TBD
> 
> Can the working group, especially the chairs and the affected document authors (all CC-ed) please review this proposal?

What about the ability to augment yang-data?  The proposed instance data
draft also makes use of yang-data-ext, and I have a use case to augment
some of its MD.  I realize this draft is not a WG item [yet], but I
wonder what the co-authors thought around the fate of the augments work.

Joe