Re: [netmod] yang-data-ext issues

Kent Watsen <kwatsen@juniper.net> Tue, 01 May 2018 20:34 UTC

Return-Path: <kwatsen@juniper.net>
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 1206712E8EC for <netmod@ietfa.amsl.com>; Tue, 1 May 2018 13:34:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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_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=juniper.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 khDj8HJbbTB7 for <netmod@ietfa.amsl.com>; Tue, 1 May 2018 13:34:01 -0700 (PDT)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (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 7520A12420B for <netmod@ietf.org>; Tue, 1 May 2018 13:34:01 -0700 (PDT)
Received: from pps.filterd (m0108162.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w41KK0It001568; Tue, 1 May 2018 13:34:00 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=PPS1017; bh=4KzvvdYJ8hGWxjW7B10zHQizgmoK47JVaJmDdHjG3ro=; b=LfO5VrOfth2m+3GFNCp0Wh5XDqh6E9f7/wUO18r4w40NDfc0krq4u2bn6U2mChxCGGzS Psre+cKDOPpGxtR/illb8q4gSGJcstqWL+/3kFg8xjtBcGriako+xYjcBXlw/sQuG4Wd K6Xo+ZzsvkZ+hU8EcIu+Le3VwDAH/nWn+CFc08jElm8Q6K+iflw/eC5EJVzsD5BfYShd Y6h5HFC6EH4ArOP6NsXYc1J3o256weSW4x5+yQteykTceOmFfUZWVywJKqW/CLZUyywV +4InZSiGBGtx/ii1B8DPjsC8aFLSBw8BHZzNvUtKNl2lVjLMr/TxM/re1F+61iXgWzH+ WA==
Received: from nam01-sn1-obe.outbound.protection.outlook.com (mail-sn1nam01lp0111.outbound.protection.outlook.com [207.46.163.111]) by mx0b-00273201.pphosted.com with ESMTP id 2hpxcwg3m9-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 01 May 2018 13:34:00 -0700
Received: from BYAPR05MB4230.namprd05.prod.outlook.com (52.135.200.153) by BYAPR05MB4182.namprd05.prod.outlook.com (52.135.200.141) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.735.6; Tue, 1 May 2018 20:33:58 +0000
Received: from BYAPR05MB4230.namprd05.prod.outlook.com ([fe80::44ac:d4a9:49d0:101e]) by BYAPR05MB4230.namprd05.prod.outlook.com ([fe80::44ac:d4a9:49d0:101e%13]) with mapi id 15.20.0735.006; Tue, 1 May 2018 20:33:58 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
CC: NetMod WG <netmod@ietf.org>
Thread-Topic: [netmod] yang-data-ext issues
Thread-Index: AQHT1YJYRSnZmZlnhU6JIK4LoPfNTqQEcM6AgAYAzwCAAlYhgIAB08UAgAAyUgCAATikgIAAAaSAgAGHGgCAAAK9AIAAEH6AgAACpYCAAPWtAIABPh0AgACT0YCAAAY/gIAABasAgAALQACAAARkgIAANngAgAADfgCAAAdSAIAADKEAgASYmID///yYAIABJ2YAgACWo4A=
Date: Tue, 1 May 2018 20:33:58 +0000
Message-ID: <508FA1DE-87BF-425E-BC52-2C4626ACAB12@juniper.net>
References: <20180427.120325.419501937185262392.mbj@tail-f.com> <11da9315-40d9-60cd-d32f-b0ac4a5640c4@cisco.com> <45f5a97d205a9251b382687f54865c62250787cb.camel@nic.cz> <99aac5c0-aa2f-1a35-8a5c-ad97635e5a40@cisco.com> <b9211ebacd24ffdd558ecf4da5bfa1ad71cfdabb.camel@nic.cz> <20180427144708.6ekknrajexvz5yvf@elstar.local> <4305e62a9d301da22f89a0dd9a34c9c4882735af.camel@nic.cz> <CABCOCHSKfDCOpQJ4bX2ueHSj-e90ZyHVC1z3h9WMfPkn2OMMvw@mail.gmail.com> <87d0yglra0.fsf@nic.cz> <C9640A34-AC7F-4890-A3FA-C1CC0D056626@juniper.net> <20180501073448.vs642cc2mpuzrvv3@elstar.local>
In-Reply-To: <20180501073448.vs642cc2mpuzrvv3@elstar.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.20.0.170309
x-originating-ip: [66.129.241.14]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BYAPR05MB4182; 7:xBulur+zsB6K1wqAmP9YntmAIUrmwvOrgEz9n6xkQtHc2le28PqJohjsUEPR2dO6LJRFZ2khWIWt0o50zKdDKrego7o2aKQ+7IApfpullDOqDp32iV0ZGc3sZLKYUjYmWL+O70C8RLF0ecIZaHPCctmAW5kL5H/KqPnD7FsnsXDt9xPKYFVhoQFHVygbTV2RtB7pCFHFaGiTqf/Vn1r89pjegCYmZgoIzswYi9mzCAZZVp4Nsl5hMyiIqcenN+8l
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(48565401081)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:BYAPR05MB4182;
x-ms-traffictypediagnostic: BYAPR05MB4182:
x-microsoft-antispam-prvs: <BYAPR05MB418242AFCF2971136B549EA7A5810@BYAPR05MB4182.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3002001)(3231254)(944501410)(52105095)(10201501046)(93006095)(93001095)(6055026)(6041310)(20161123564045)(20161123558120)(20161123560045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:BYAPR05MB4182; BCL:0; PCL:0; RULEID:; SRVR:BYAPR05MB4182;
x-forefront-prvs: 06592CCE58
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39380400002)(39860400002)(376002)(396003)(366004)(346002)(189003)(199004)(86362001)(3660700001)(102836004)(26005)(3280700002)(305945005)(6486002)(68736007)(5660300001)(6916009)(6246003)(6512007)(36756003)(53936002)(4326008)(93886005)(229853002)(76176011)(6506007)(25786009)(97736004)(186003)(59450400001)(33656002)(99286004)(486006)(476003)(2900100001)(2616005)(446003)(81166006)(81156014)(5250100002)(8676002)(8936002)(6116002)(66066001)(105586002)(11346002)(6436002)(83716003)(14454004)(2906002)(3846002)(58126008)(316002)(106356001)(478600001)(82746002)(7736002); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB4182; H:BYAPR05MB4230.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: DClmh03UynLm+D9OLJ/1rHLEdVbB5/e2yfy7uWQAQ8vTM3Xz/PMsG+XMjQjvVwOTOduNlAL5+HKnn5TdItMPZ+Pbtj+5K8AqGo+o+v12d/qOXlRLnFKFbWQeql+RGNIQiXZE9rEPNcBMbB1tiaGz/0FSoWFl77aVXy4b5ySPAcqeq/RzYHRboLQ2fFJTXNs0
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <BAEB3856A791CF4298E01E58DB63ABDA@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 04e6c323-7c6f-4861-a9bf-08d5afa2de09
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 04e6c323-7c6f-4861-a9bf-08d5afa2de09
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 May 2018 20:33:58.6906 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB4182
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-01_10:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1805010196
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/QrLtMDG9bGk0a_JyepM53MkRoY4>
Subject: Re: [netmod] yang-data-ext issues
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 01 May 2018 20:34:04 -0000

Juergen writes:
> Kent writes:
>> I don't understand talk about abandoning this draft.  There is no question
>> that it is needed (e.g., anima vouch, zerotouch, tail-f's "structure"),
>> and RFC 8040 is unsatisfactory because 1) it doesn't allow a top-level
>> 'choice' between two containers and 2) it requires drafts to reference 
>> RFC 8040, even though the drafts may have nothing to do with RESTCONF.
>>
>
> Re 1: RFC 8040 says: "It MUST contain data definition statements that
> result in exactly one container data node definition." So a choice may
> actually work as long as the result is exactly one container data
> node. OK, the wording in the RFC 8040 statement is not clear since
> 'result' and 'definition' do not line up (does 'result' mean the
> toplevel data node instances that are possible? In this case,
> 'definition' would be misleading).

I agree, but Martin did not and he even modified `pyang` to throw an 
error on the zerotouch draft, thus forcing the current situation.  If
a new understanding regarding rc:yang-data can be reached, the zerotouch
draft can go back to using it.


> Re 2: It does not really matter whether you import the extension from
> RFC 8040 or some other module. Why is depending on A better than
> depending on B? The definition in RFC 8040 is already know by tools.
>
> I view the yang-data definition of RFC 8040 as a temporary solution, a
> proper solution should in my view be part of YANG 1.x.

What is the "proper solution", and why does it need to wait for YANG 1.x?
In the discussion regarding moving faster, it's been suggested that YANG 
1.x could be a cherry-picking of some number of extension statements 
produced in other I-Ds.  I was hoping that this was the case here.  True,
some tools know about A, but if B is the LTS, then I'd hope to move to B
ASAP.

> Since NMDA essentially binds all data tree definitions to datastores,
> the yang-data construct allows us to define data structures that are
> specifically not bound to any datastore, i.e., data structures that by
> design can't be operated on directly with NMDA NETCONF/RESTCONF.

Yes.


Kent // contributor