IETF Logo Mail Archive

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

Kent Watsen <kent+ietf@watsen.net> Tue, 14 April 2020 14:28 UTC

Return-Path: <010001717917c312-741f8486-519f-4e87-bc12-4fb98174ebd5-000000@amazonses.watsen.net>
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 A7F333A0865 for <netconf@ietfa.amsl.com>; Tue, 14 Apr 2020 07:28:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] 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 nd3EocZEpgIH for <netconf@ietfa.amsl.com>; Tue, 14 Apr 2020 07:28:58 -0700 (PDT)
Received: from a8-88.smtp-out.amazonses.com (a8-88.smtp-out.amazonses.com [54.240.8.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2776A3A0840 for <netconf@ietf.org>; Tue, 14 Apr 2020 07:28:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1586874532; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:Feedback-ID; bh=2+ljaO8sUxl9F18cEy2tL5LnGJcMLGnpt5v93TLQylM=; b=L1zl/sREU+dB36UR5QGRCDG6loBFyZmt/65xeQF5Mm0UK/E0tNHgfCVCAyk/IG6t O+uSJhKLQFDfGJ3Wzyi80AfZqzmy0XypctmvuPxpem8grPuVpdYrro9sU7WDaEzW2xB 6QrZr2tcXrr3E5ksNRNPiSJhw6AwiolJr5GZC7LE=
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Kent Watsen <kent+ietf@watsen.net>
In-Reply-To: <CAGnRvuq=ESLkeyWsgiqE9sXqFwHGUef3A4QRuW=H8ompVO3C4Q@mail.gmail.com>
Date: Tue, 14 Apr 2020 14:28:52 +0000
Cc: "netconf@ietf.org" <netconf@ietf.org>
Content-Transfer-Encoding: 7bit
Message-ID: <010001717917c312-741f8486-519f-4e87-bc12-4fb98174ebd5-000000@email.amazonses.com>
References: <CAGnRvup-pLVYgxAx7PnbJJ1gS-GTkD6t5jGD_Ayhh7ctpPothw@mail.gmail.com> <CAGnRvuq=ESLkeyWsgiqE9sXqFwHGUef3A4QRuW=H8ompVO3C4Q@mail.gmail.com>
To: Henning Rogge <hrogge@gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-SES-Outgoing: 2020.04.14-54.240.8.88
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/IYW5bqmUWTLdd8zneXNrD9WUaTQ>
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 14:29:00 -0000

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

v2.23.0 | Report a Bug | By Email