IETF Logo Mail Archive

Re: [netmod] adoption poll for yang-versioning-reqs-02

Kent Watsen <kent+ietf@watsen.net> Wed, 20 March 2019 23:25 UTC

Return-Path: <010001699d6c0b6a-3ff01ba1-35e2-4bf0-aecf-8e276e2ac8c8-000000@amazonses.watsen.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 9EB0E12AF7B for <netmod@ietfa.amsl.com>; Wed, 20 Mar 2019 16:25:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.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 zBzXCAvoUOo1 for <netmod@ietfa.amsl.com>; Wed, 20 Mar 2019 16:24:59 -0700 (PDT)
Received: from a8-83.smtp-out.amazonses.com (a8-83.smtp-out.amazonses.com [54.240.8.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EAA101277E5 for <netmod@ietf.org>; Wed, 20 Mar 2019 16:24:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1553124297; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=Zw7xezusJuN9dKCBXrildzJqarKx484E55AO91KfUBA=; b=KK3O4Gw+Rn3ucPqlaaGDoCAZTk6nh3Vchcxj0PUuBWg9sjUMjzuLPqGC6h7V25ao kjoGo83ZdZ+4fq8cEsdKLX3yT7wts9amttu5Ia8+HvvMasaXeG0Vdu1+0twHs9PxcLN 2bbDJog3C4Gz5scdd0XNlvU72kZ5InKxFimW5Nn0=
From: Kent Watsen <kent+ietf@watsen.net>
Message-ID: <010001699d6c0b6a-3ff01ba1-35e2-4bf0-aecf-8e276e2ac8c8-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4FD86B2C-BCA8-4240-8AF0-9BBB8D054019"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Wed, 20 Mar 2019 23:24:57 +0000
In-Reply-To: <CABCOCHRbbUjsODMEaD0rYSrwCOB5u_iGAoi8O5cfNuyHySd49A@mail.gmail.com>
Cc: "Rob Wilton (rwilton)" <rwilton@cisco.com>, Martin Bjorklund <mbj@tail-f.com>, "netmod@ietf.org" <netmod@ietf.org>
To: Andy Bierman <andy@yumaworks.com>
References: <0100016978b80dcd-31f317a5-443b-400a-98b3-2bfc91841bdc-000000@email.amazonses.com> <20190319.161229.1910835285804688041.mbj@tail-f.com> <aee7d9770a2c4570a3185a1ebeef4c36@XCH-RCD-007.cisco.com> <CABCOCHTsH_wk+MGQwSPA-JZCUiTT38ua-dsnoFgjO=r0U07veA@mail.gmail.com> <8871415dce7343a28afa25faf6080d8c@XCH-RCD-007.cisco.com> <CABCOCHQX5i1a6zqOSc2ec3YJ=8Ugc6WeN4_uh6YqRq6jKrR1ig@mail.gmail.com> <010001699c901a90-fd39b577-918d-4082-b139-b4843f6540cc-000000@email.amazonses.com> <CABCOCHRbbUjsODMEaD0rYSrwCOB5u_iGAoi8O5cfNuyHySd49A@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.102.3)
X-SES-Outgoing: 2019.03.20-54.240.8.83
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/MBkOCwYl4i4uXAbM-7wujJrD878>
Subject: Re: [netmod] adoption poll for yang-versioning-reqs-02
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: Wed, 20 Mar 2019 23:25:01 -0000

> This is much simpler because the REST APIs are like RPC operations in YANG -- they do not interact with each other.
> In fact, it is impossible in YANG to have the XPath/leafref cross-references in 1 RPC access another RPC.
> 
> It is easy to support many revisions of an RPC operation.
> Not so easy for the contents of a YANG datastore.


The REST API was modeled using YANG, but each "object" was effectively yang-data.   This was for an NMS, so the objects were large.  For example, each NE device was an object, as was each application-level abstraction built on top of the device native models.

K.

v2.23.0 | Report a Bug | By Email