Re: [netmod] New Version Notification for draft-lengyel-netmod-yang-instance-data-00.txt

Kent Watsen <kwatsen@juniper.net> Mon, 12 February 2018 17:20 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 DF43D12D866; Mon, 12 Feb 2018 09:20:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.711
X-Spam-Level:
X-Spam-Status: No, score=-0.711 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, 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 wX7hLq8zhnZp; Mon, 12 Feb 2018 09:20:54 -0800 (PST)
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 51B9812D864; Mon, 12 Feb 2018 09:20:54 -0800 (PST)
Received: from pps.filterd (m0108163.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w1CHIwKQ009796; Mon, 12 Feb 2018 09:20:51 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=PPS1017; bh=gR059zqFokpB55F4F9ym6fw4//TBwQO+aydE+i8FSEM=; b=qFBrA6of7Dle6E9LgFVGaDXb6lfL+c6bUsEiRaut0nqnS9HNDoSDFPW9qnQWkMSTOMeQ /ViUa8QF/3D9oD+QMHW5olE3n6iETegeOkYq7TbmU/voDBfWw0KklCiVXCkL0rJwCglc A3zB6tAgYod4B6A0silXLBsPgz7vfADv1c7ylK650vWAJ1MD35ikT81WNbXlVn0iu75A rjShIivJGxFZJxlXRVsLty/PDGRtv5ORDmkv5PBqaPut8h8hfoRPDAxypsBQTh+tO9tk GUBDYjC/azDYdE4kii50/C8jS1qMd3G1dDGOFXRd0eQVN26vS06M0fUlsdctuMp7ZGK0 gQ==
Received: from nam03-by2-obe.outbound.protection.outlook.com (mail-by2nam03lp0055.outbound.protection.outlook.com [216.32.180.55]) by mx0b-00273201.pphosted.com with ESMTP id 2g3eey82pf-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 12 Feb 2018 09:20:50 -0800
Received: from DM5PR05MB3484.namprd05.prod.outlook.com (10.174.240.147) by DM5PR05MB3196.namprd05.prod.outlook.com (10.173.219.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.506.7; Mon, 12 Feb 2018 17:20:48 +0000
Received: from DM5PR05MB3484.namprd05.prod.outlook.com ([fe80::7433:3915:f20d:6747]) by DM5PR05MB3484.namprd05.prod.outlook.com ([fe80::7433:3915:f20d:6747%13]) with mapi id 15.20.0506.013; Mon, 12 Feb 2018 17:20:48 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: Balazs Lengyel <balazs.lengyel@ericsson.com>, "netmod@ietf.org" <netmod@ietf.org>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [netmod] New Version Notification for draft-lengyel-netmod-yang-instance-data-00.txt
Thread-Index: AQHToL2thWcJ1c3u0k60yCgwjzlx8KOgtlSA
Date: Mon, 12 Feb 2018 17:20:48 +0000
Message-ID: <CDAB1B4E-4A4F-4B84-B03F-EC3EC4049CAA@juniper.net>
References: <151802453050.4811.17681759233520578672.idtracker@ietfa.amsl.com> <fbf20002-e114-c55a-d595-bb5710e7de7e@ericsson.com>
In-Reply-To: <fbf20002-e114-c55a-d595-bb5710e7de7e@ericsson.com>
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.12]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM5PR05MB3196; 7:9XcUmMJfEytU7xfJGtjMU0QuE495IIo4DiQvTjSUO0FWSuNFEOU8xWSCOLQ+d9FLXD4nzzzjDm9OO4okqxxofZz6+/i6/yCD4CWbikdZh9ZrPjzDEKUXIsNPA05ztQt8c+1NOwOtPj3hXlhRwKpRL+8c2m+5PVcVNnEtu4aKGj1C9/1DLRzXNTmJB5cleD7nAI5xCQJnqseOHb2uxWxkLhIxE7h+qUE4HoN7ckNFZmS6lPH5wXAOcg4R0Sj4tZGo
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: b5bdf117-7b9a-4f0f-76f0-08d5723cf55b
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(48565401081)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603307)(7153060)(7193020); SRVR:DM5PR05MB3196;
x-ms-traffictypediagnostic: DM5PR05MB3196:
x-microsoft-antispam-prvs: <DM5PR05MB3196DCA39DF461CB8122F17FA5F70@DM5PR05MB3196.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(37575265505322)(28532068793085)(158342451672863)(10436049006162)(120809045254105)(95692535739014)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(5005006)(8121501046)(3231101)(2400082)(944501161)(10201501046)(93006095)(93001095)(3002001)(6055026)(6041288)(20161123562045)(20161123560045)(20161123558120)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:DM5PR05MB3196; BCL:0; PCL:0; RULEID:; SRVR:DM5PR05MB3196;
x-forefront-prvs: 0581B5AB35
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(39380400002)(376002)(366004)(396003)(39860400002)(189003)(199004)(377424004)(252514010)(5250100002)(110136005)(6246003)(33656002)(2501003)(2900100001)(6436002)(36756003)(966005)(7736002)(316002)(478600001)(83716003)(6486002)(58126008)(186003)(82746002)(236005)(606006)(3280700002)(83506002)(53936002)(106356001)(6512007)(54896002)(2906002)(97736004)(6306002)(99286004)(8936002)(229853002)(81166006)(66066001)(102836004)(68736007)(8676002)(105586002)(7110500001)(2950100002)(2201001)(81156014)(14454004)(3660700001)(6506007)(76176011)(9326002)(26005)(3846002)(6116002)(25786009)(5660300001)(86362001)(15650500001)(59450400001)(2420400007); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR05MB3196; H:DM5PR05MB3484.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: YgbI9AxqecyBpWWdgdgWlnQ+4OloNJcbdbvAmCVNaLCk1//liqPdz/6Emd8MnaTIxYEWp3aRHE5U+cIvDXQzvA==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_CDAB1B4E4A4F4B84B03FEC3EC4049CAAjunipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: b5bdf117-7b9a-4f0f-76f0-08d5723cf55b
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Feb 2018 17:20:48.2340 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR05MB3196
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-02-12_07:, , 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-1802120222
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/ruQsvzkzcH71jligpbyHQ7FZG1Q>
Subject: Re: [netmod] New Version Notification for draft-lengyel-netmod-yang-instance-data-00.txt
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: Mon, 12 Feb 2018 17:20:58 -0000

Hi Balazs,

I'm unclear about the scope of the problem.  Is it limited to server capabilities?    It seems that the idea is to move from having a stateful connection to a live server to having a way to pass the equivalent state even when not connected to the server.

Related, but probably not what you're angling for, I've been having issues with validating RESTCONF examples.  The issue is that the RESTCONF documents are context specific.  For instance, GET /widgets/ returns a document that might have an outermost element called "widgets", whereas GET /widgets/widget=foo returns a document that might have an outermost element called "widget".   In order to validate the second document, my code first wraps the "widget" element with a "widgets" element, and then the validation tools work.

Perhaps a more generalized instance data mechanism could include where in the tree the data is situated?   For example, it would be helpful if an action's instance data could provide more context (e.g., the input/output documents could indicate the name of the action, the object that the action was invoked on, etc.).

Generally, there is some state being held by the protocols that complicates examining instance data outside of the protocol, as extra bits of state need to be passed around separately.  It would be nice if the documents were (or at least could be) more self-contained.

Kent // contributor


On 2/8/18, 4:17 AM, "netmod on behalf of Balazs Lengyel" <netmod-bounces@ietf.org<mailto:netmod-bounces@ietf.org> on behalf of balazs.lengyel@ericsson.com<mailto:balazs.lengyel@ericsson.com>> wrote:


Hello,

With Benoit I prepared a draft about how to document and use YANG defined instance data. It could be useful for documenting  server capabilities or preloading data defined in implementation time and probably for other purposes as well.

regards Balazs

-------- Forwarded Message --------
Subject:

New Version Notification for draft-lengyel-netmod-yang-instance-data-00.txt

Date:

Wed, 7 Feb 2018 09:28:50 -0800

From:

internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>

To:

Benoit Claise <bclaise@cisco.com><mailto:bclaise@cisco.com>, Balazs Lengyel <balazs.lengyel@ericsson.com><mailto:balazs.lengyel@ericsson.com>



A new version of I-D, draft-lengyel-netmod-yang-instance-data-00.txt

has been successfully submitted by Balazs Lengyel and posted to the

IETF repository.



Name:          draft-lengyel-netmod-yang-instance-data

Revision:      00

Title:         YANG Instance Data Files and their use for Documenting Server Capabilities

Document date: 2018-02-06

Group:         Individual Submission

Pages:         10

URL:            https://www.ietf.org/internet-drafts/draft-lengyel-netmod-yang-instance-data-00.txt<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_internet-2Ddrafts_draft-2Dlengyel-2Dnetmod-2Dyang-2Dinstance-2Ddata-2D00.txt&d=DwMDaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=9zkP0xnJUvZGJ9EPoOH7Yhqn2gsBYaGTvjISlaJdcZo&m=hnU9-LLpaIzWowZefBxYfrcvaEILD8Bz2n6gSTHI5WQ&s=-cx3SgYxfmIlRWYz3RLb81BDCoJZy2ViqIAI8Cq0dlk&e=>

Status:         https://datatracker.ietf.org/doc/draft-lengyel-netmod-yang-instance-data/<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dlengyel-2Dnetmod-2Dyang-2Dinstance-2Ddata_&d=DwMDaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=9zkP0xnJUvZGJ9EPoOH7Yhqn2gsBYaGTvjISlaJdcZo&m=hnU9-LLpaIzWowZefBxYfrcvaEILD8Bz2n6gSTHI5WQ&s=veCJKfYZs8V9krZOIZlMR1HS6jmmO0nk5FCXwYengSQ&e=>

Htmlized:       https://tools.ietf.org/html/draft-lengyel-netmod-yang-instance-data-00<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dlengyel-2Dnetmod-2Dyang-2Dinstance-2Ddata-2D00&d=DwMDaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=9zkP0xnJUvZGJ9EPoOH7Yhqn2gsBYaGTvjISlaJdcZo&m=hnU9-LLpaIzWowZefBxYfrcvaEILD8Bz2n6gSTHI5WQ&s=Ro0Lzr3-CMLj03kjq2WVcZCUbBBUqrWPls1ZES0GbnY&e=>

Htmlized:       https://datatracker.ietf.org/doc/html/draft-lengyel-netmod-yang-instance-data-00<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_html_draft-2Dlengyel-2Dnetmod-2Dyang-2Dinstance-2Ddata-2D00&d=DwMDaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=9zkP0xnJUvZGJ9EPoOH7Yhqn2gsBYaGTvjISlaJdcZo&m=hnU9-LLpaIzWowZefBxYfrcvaEILD8Bz2n6gSTHI5WQ&s=PTQT_O1Yp9WGYa2aodkOfVe5l0DFPkKfeodj4y5ptH0&e=>





Abstract:

   This document specifies a standard file format for YANG instance

   data, that is data that could be stored in a datastore and whose

   syntax and semantics is defined by YANG models.  Instance data files

   can be used to provide information that is defined in design time.

   There is a need to document Server capabilities (which are often

   specified in design time), which should be done using instance data

   files.









Please note that it may take a couple of minutes from the time of submission

until the htmlized version and diff are available at tools.ietf.org.



The IETF Secretariat



--

Balazs Lengyel                       Ericsson Hungary Ltd.

Senior Specialist

Mobile: +36-70-330-7909              email: Balazs.Lengyel@ericsson.com<mailto:Balazs.Lengyel@ericsson.com>