Re: [netconf] Trouble with RFC 8040 (Restconf) fields Query Parameter

Henning Rogge <hrogge@gmail.com> Tue, 14 April 2020 16:03 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 07ED93A0A8C for <netconf@ietfa.amsl.com>; Tue, 14 Apr 2020 09:03:08 -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 H0X5YQ9v_w4p for <netconf@ietfa.amsl.com>; Tue, 14 Apr 2020 09:03:01 -0700 (PDT)
Received: from mail-lf1-x142.google.com (mail-lf1-x142.google.com [IPv6:2a00:1450:4864:20::142]) (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 C32D93A0A2F for <netconf@ietf.org>; Tue, 14 Apr 2020 09:03:00 -0700 (PDT)
Received: by mail-lf1-x142.google.com with SMTP id 131so135987lfh.11 for <netconf@ietf.org>; Tue, 14 Apr 2020 09:03:00 -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=Cpj56vNJVe0wwJ5//JyK8Hv8wdjXLFiF/Cxetcv82VQ=; b=kXxRhIWGIZxKPxKUyEMUdx75369zKTW7UflkAFncYDFalOkVfTtRZuWq9iXljE3Caw wP+bDEmhn5oGaszqeO7W/RNG4KaBvjeNhURmItwA3fwbZCXrV7eq3hfxS18qTMK3HoHL Y0F3eLms18QO04fIMO32EI76lFHEdHVBa1mS6NoIAks/QhrQ7t6NbZI0MR+/EZIs6dWE 8j8rpcXllg6bO0UBdh2UpsIhVdeEUx5TMkVDjvbEpr2RTDlhgwgei7J7hhxqcB+WTFR9 SQ+vZMGD+LbClsRedA2YUPyu+GzH0xzQa84Aac8Kt3+cOIFYtkT1CR/SVZLUBD+cdIJ8 jNhQ==
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=Cpj56vNJVe0wwJ5//JyK8Hv8wdjXLFiF/Cxetcv82VQ=; b=fSd9F2IulovgrosPz5q9It1s9SdfdK3SnyTud+5r7op4wqWh/NmXk8W0jnDYIsLTn7 Xp1h9v9NksBfGzBNFqNx+gsEcGlQC2ZCQA6KL/3Ml8mLKQDroj/tPnoz/4/v1kVOciym eFrEcbWB4wsFGEph3dldk6WkbBY92b3/3JWXeqcX7OCZ21QYAAc7KEbB42s5LcCY1z3f vDvZSaBbeQJrMAb7P75bpSA+4EsTVhMbnp0YlOMka+4jhF0w7b8LdeUb/b0vNuV4zxEg fvgirruEtoc/5B6kFgycdAVvYM4el3oyRTIeZWqXEXyw8W0QyAnDOrb3Cg7HQyriM/aY hepw==
X-Gm-Message-State: AGi0Puav6U4M3w3IC9jaHEd3FE1q9Ri72yrOMY1CXGjptLyG/8B5y9Xo dE5GGcm7hmk+JRs5QJFDAqBtMp7zxmPMlEx/hrPmVDa+
X-Google-Smtp-Source: APiQypIFM2ZUNLF/gOTlpcu/t03lRAIYyG+bZ3CjV7Jege+DuecUNWW+lmyenQ9MJpKcpamsSMH1KyoIwKgd7k2OsU0=
X-Received: by 2002:a19:f806:: with SMTP id a6mr295056lff.201.1586880178880; Tue, 14 Apr 2020 09:02:58 -0700 (PDT)
MIME-Version: 1.0
References: <CAGnRvup-pLVYgxAx7PnbJJ1gS-GTkD6t5jGD_Ayhh7ctpPothw@mail.gmail.com> <CAGnRvuq=ESLkeyWsgiqE9sXqFwHGUef3A4QRuW=H8ompVO3C4Q@mail.gmail.com> <010001717917c312-741f8486-519f-4e87-bc12-4fb98174ebd5-000000@email.amazonses.com>
In-Reply-To: <010001717917c312-741f8486-519f-4e87-bc12-4fb98174ebd5-000000@email.amazonses.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Tue, 14 Apr 2020 18:02:32 +0200
Message-ID: <CAGnRvuqaTzRA95c63bgDP0ZGzM-bRv09bddQ8Om5Z=U8QcgkLg@mail.gmail.com>
To: Kent Watsen <kent+ietf@watsen.net>
Cc: "netconf@ietf.org" <netconf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/jzw-PTT5CM8ibjeqHZsIeD6etfE>
Subject: Re: [netconf] Trouble with RFC 8040 (Restconf) fields Query Parameter
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: Tue, 14 Apr 2020 16:03:09 -0000

Hi,

my problem is how these "multi-parenthesis" expressions are meant to
be processed. Single parenthesis is easy to understand.

Does anyone has at least one example of such a (valid?) fields
expression and what it should do?

Henning Rogge

On Tue, Apr 14, 2020 at 4:28 PM Kent Watsen <kent+ietf@watsen.net> wrote:
>
> It seems like it would.  Have you tried an ABNF validator?
>
> Kent // contributor
>
>
> > On Apr 11, 2020, at 5:02 PM, Henning Rogge <hrogge@gmail.com> wrote:
> >
> > Anyone (Maybe the timing of the question just before the IETF was not
> > that good ^^) ?
> >
> > Henning Rogge?
> >
> > On Thu, Apr 2, 2020 at 2:18 PM Henning Rogge <hrogge@gmail.com> wrote:
> >>
> >> Hi,
> >>
> >> I am trying to implement a Restconf (RFC8040) compliant server in
> >> Python and having trouble interpreting the definition of the "fields"
> >> query parameter (Section 4.8.3).
> >>
> >> Does the "fields-expr" ABNF allow multiple nested bracket parts?
> >> e.g.:
> >>
> >> fields-expr = path ( path ; ( path ; path; ( path ; path ) ) )
> >>
> >> My guess is it allows to nest the "sub-selector" operator, but only
> >> the rightmost of a series of multiple selected nodes ( split by ";" )
> >> can be another sub-selector.
> >>
> >> Is this interpretation correct? What is the supposed semantic for this
> >> kind of query parameter?
> >>
> >> Henning Rogge
> >
> > _______________________________________________
> > netconf mailing list
> > netconf@ietf.org
> > https://www.ietf.org/mailman/listinfo/netconf
>