IETF Logo Mail Archive

Re: [netconf] Question about RFC8040 data root node and depth example

Henning Rogge <hrogge@gmail.com> Thu, 07 May 2020 12:41 UTC

Return-Path: <hrogge@gmail.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C1F83A0404 for <netconf@ietfa.amsl.com>; Thu, 7 May 2020 05:41:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 DAncGu7GXye4 for <netconf@ietfa.amsl.com>; Thu, 7 May 2020 05:41:29 -0700 (PDT)
Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF1F13A0400 for <netconf@ietf.org>; Thu, 7 May 2020 05:41:28 -0700 (PDT)
Received: by mail-lf1-x136.google.com with SMTP id a4so4334751lfh.12 for <netconf@ietf.org>; Thu, 07 May 2020 05:41:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7aDjqBrdE34WOHMREuKOriWY+bS6Ai40pHawETjfb0A=; b=plowirqGy+77y+0Kg4BKh3IptXgxiySwYF7BMrRasEBoaLXBhMtGGp8GXG2ePdYH0t vwYPajrZOEsQpccCqz8budEwTG90ebI7alfdL3pBVhIYVwLmsW/Dhp31ARXGBr5CNSuT ajcbsjhS4BD1lui6IT1c9VsLX1Ejf4BUoVQc44WSIWt0BmNmlkWjaiNt7FKN1gVxqiSR n07Ue1e3f5ZmUBuus8AGofP45KHZobkzqVAtSnSxr+/Iw3PIzkmNEdvML3qimk+osPyI BYNC+aAwIW3vjqOBJ55waqd4xvNNDDtw5ja9wo4DRSaACaueifLvaeeb3vCvmcXVtnmH +uTw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=7aDjqBrdE34WOHMREuKOriWY+bS6Ai40pHawETjfb0A=; b=FYZws8L9jmzTN4zUo8YGQVg2iJjW9LP/xPH29fyAK/9p7G5zDZty4w+DDLj4hKi2cm YwfHwZ1Xkn3d9A/J/P5ObQn4HRU9LY4MnTeOZwgzgFNh0AtuxK1tZg4H7USLad6CPguK CtsCzJUjLzFTfJq21LE8h/xl9oBTIR4AgYrjGm/+m1zPigqJxXD71mFx93BgTPHb49wb 4Tcc6LFelUvWW6TRshsO8MdJEyOOptO5r6UZpkrWt/gF4XXFpxDhfH3R1twHl9eSeO7K tJDJUWG+1eRyomPqV7EY/NKPOtx010W6cORnzFvoOxgbSGiVVRgMHz/Gg+TnZoeR1diL KenA==
X-Gm-Message-State: AGi0Puau33/OEaCQXgGXJ3++hhYKoB8Ze9QqUqOkct1J9YpILL2AyF58 Jj3vEc73lBmznmcSH9VNcNT7R31AXX2PN/6G3I0=
X-Google-Smtp-Source: APiQypL504YjA7oBIQjNlzZoozEXzlrtUAJgGQnueQN5sGsc4YoTJkfJneRM8wyrBemj9DCEbHUDS7A+AJ8Gtgqlrd4=
X-Received: by 2002:a19:cc92:: with SMTP id c140mr8702300lfg.34.1588855286893; Thu, 07 May 2020 05:41:26 -0700 (PDT)
MIME-Version: 1.0
References: <CAGnRvuqk6UnbZSr0GzHRfS4E5ORGTmPO=cY_KA9gAg=Nout50A@mail.gmail.com> <DM6PR11MB38183AC997EA6C633F2A0864DBA50@DM6PR11MB3818.namprd11.prod.outlook.com> <CAGnRvuox=3F0eH89a0FBHy3Bz9eSH=gKwh0zH6sFhcyM0kRVPw@mail.gmail.com> <DM6PR11MB38186C2A41E4D9AFE9240A3BDBA50@DM6PR11MB3818.namprd11.prod.outlook.com>
In-Reply-To: <DM6PR11MB38186C2A41E4D9AFE9240A3BDBA50@DM6PR11MB3818.namprd11.prod.outlook.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Thu, 07 May 2020 14:41:00 +0200
Message-ID: <CAGnRvup7e3Hbf71LCmiutJwcPFxnOfYV2MciT9WLNNWcXhmCbg@mail.gmail.com>
To: "Per Andersson (perander)" <perander@cisco.com>
Cc: "netconf@ietf.org" <netconf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/prikNLTAjTNYhrCzUO0rskAxeZo>
Subject: Re: [netconf] Question about RFC8040 data root node and depth example
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 May 2020 12:41:31 -0000

On Thu, May 7, 2020 at 2:30 PM Per Andersson (perander)
<perander@cisco.com> wrote:
> > In theory It should be possible to define the "data" YANG model and
> > then import/augment everything from there, right?
>
> The datastore resource "data" is not a model per say but a container
> which should be populated with loaded models' top nodes.

Yes, but because of query modifiers like depth/fields it is necessary
to have a common filtering system that starts at the base datastore
resource. A GET query easily can contain data from multiple models.

It is more of an implementation problem, nothing wrong with the
specification. At the moment my code just use different hooks in the
REST server to deal with each Yang model (modules-state,
restconf-state, userdata, ect.).

Henning

v2.23.0 | Report a Bug | By Email