IETF Logo Mail Archive

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

Henning Rogge <hrogge@gmail.com> Thu, 02 April 2020 12:19 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 334BE3A10FD for <netconf@ietfa.amsl.com>; Thu, 2 Apr 2020 05:19:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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] 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 aB0hdHOxhjsw for <netconf@ietfa.amsl.com>; Thu, 2 Apr 2020 05:19:02 -0700 (PDT)
Received: from mail-lj1-x242.google.com (mail-lj1-x242.google.com [IPv6:2a00:1450:4864:20::242]) (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 7A0B53A10FE for <netconf@ietf.org>; Thu, 2 Apr 2020 05:19:02 -0700 (PDT)
Received: by mail-lj1-x242.google.com with SMTP id t17so2945876ljc.12 for <netconf@ietf.org>; Thu, 02 Apr 2020 05:19:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=vXrAnQqt5PI3s47s5nLg5T6Tz+JMgkmfa6pVoS9IqM0=; b=pJ/mWzGWX2mmiHDJBEGQ/mCta9sZsBGnrT4h+ECdjssdxQ0QFW35DOzwnMptpxUFh4 Qu41GI/q5EEF7AyCN6xB6e6+QAFAKjdLDSemZCU9Wn/L5rYk87VMfvKd7om0XtlkIVUu ONPYgYUQCMIbaoj5FYw+OfYsfe4gDtbEBZVaN3Lbixjpe0FURKggmRVTduuckg6C+N30 bqrAfl4vYM9u8jP/VPOzWiyt6rwgMgHZ/iNwtxEljVRxPSfylvIr+6gN72TLjRwBDQMV E8AgrmweEdpKm6U/zf0qSDCGgye5sexs8rA2ygj/eXjuViJJGfQzqFERpsJ1XCMLC78e 1j4g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=vXrAnQqt5PI3s47s5nLg5T6Tz+JMgkmfa6pVoS9IqM0=; b=Zd10OPgz4SOOyHtujdsQZBR//ZYocIzryw1WU60xHnV4JSg65gUBt8RKnB6/HQFAw+ HkX2E7QbvkOwZqaFfpnULtC9KJioTPXqY8EdvP7pgKg15wUDzE/IPgbTJnkRxnHnPbE8 og8nDE56uXFUPaOLPd8neoDQYA0GeIfv7YuPoiFfxyCKB9v0WPQ5SbwPfYuiBPmAqbmC Yz8gcd4WmUfNs7IGUjup5ZLF94dx3wrkunqYoztq4VmZLJF40G/KKHriqPKYaZ9LkPRR /6812deJCroAxteD9MQfwWgf6DC59uhP4Z9sL1gbFnIgQKJFtZ+bGpoV8/lFOmqzCw3x HinQ==
X-Gm-Message-State: AGi0Pubs9k4W0jFlnXyXAxBd81iSADnLLOYKp9riIVNo/bDv3WcTHpwY b8osTKQulPzn96qelauW7ZDnJyUxrOSyFXmj6syuYCW7
X-Google-Smtp-Source: APiQypJtlT3CCgYfHohlHb5VCAWIOMGcVV+2AurxpvntRWSUVjF3kJQduIG0mAinLbJGwQwsn1mq/ifPF6DapbGDAg8=
X-Received: by 2002:a2e:87da:: with SMTP id v26mr1794609ljj.63.1585829939904; Thu, 02 Apr 2020 05:18:59 -0700 (PDT)
MIME-Version: 1.0
From: Henning Rogge <hrogge@gmail.com>
Date: Thu, 02 Apr 2020 14:18:33 +0200
Message-ID: <CAGnRvup-pLVYgxAx7PnbJJ1gS-GTkD6t5jGD_Ayhh7ctpPothw@mail.gmail.com>
To: netconf@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/SVcB7w42ASFiUZPbY0U6C-GHHFs>
Subject: [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: Thu, 02 Apr 2020 12:19:09 -0000

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

v2.23.0 | Report a Bug | By Email