IETF Logo Mail Archive

Re: [netconf] What is the response structure when querying a specific instance object in a list?

Per Andersson <per.ietf@ionio.se> Wed, 17 April 2024 16:15 UTC

Return-Path: <perkietf@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 5B959C14F5FF for <netconf@ietfa.amsl.com>; Wed, 17 Apr 2024 09:15:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.644
X-Spam-Level:
X-Spam-Status: No, score=-1.644 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GIkHEfs09Q6j for <netconf@ietfa.amsl.com>; Wed, 17 Apr 2024 09:15:30 -0700 (PDT)
Received: from mail-pl1-f177.google.com (mail-pl1-f177.google.com [209.85.214.177]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 494FDC14F5E3 for <netconf@ietf.org>; Wed, 17 Apr 2024 09:15:30 -0700 (PDT)
Received: by mail-pl1-f177.google.com with SMTP id d9443c01a7336-1e4bf0b3e06so56497895ad.1 for <netconf@ietf.org>; Wed, 17 Apr 2024 09:15:30 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713370530; x=1713975330; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=iCsr44uBG8YquMjve3jwMIm90HufeUWePywIRjxNcFI=; b=Wlne2uTfJDSZEcJpC3GdtJJxGwuWiBK/ouwmeOaYPP2caQQ0b/vEHBwqRezQKb+KW+ 01tgegr5jeErjryZcr7GoY4OAuuzE1fLspwLekcXqxDz6Sb5a9zB6A2jj2TEQZDOLwZ+ cEw2a6YhibYld3AodgpEZ3ZgoU9ywxD6ZBrj2Q9+IUMjs+irsHbgm3+efJhg8WxAFHnX ZLWy76vxDz38KIco3Osa5QwPIVIo2bTSqy6AFShl99HAO0JVmsvg0flx8nhj4N/o/UXs hsiFuZvjGpRzow4hLxhB3X3onDRYzZyRaP8B5ailF+nqSRbaAoPS4+vFP+1OX0/Bi1Ih PDfQ==
X-Forwarded-Encrypted: i=1; AJvYcCWZPlJGpwXWKpipDECY9A0f1GMrphPaJokdOCQkun44GY39XesVPWQdcG+H4/oa+4SGw0q3cD7ZsUF/31W7nlX5
X-Gm-Message-State: AOJu0YxbVdJTiOtY9oVS6D75hP8E99BFo0Yv9klxcmUeVwK72Zv4bwJR nCJAQVu3T/jYqB4CQJ0lpG11f8t5XQGavIDajOyubUTOQTogsm/e08ZQ760tedY=
X-Google-Smtp-Source: AGHT+IE3IvJFx4UF4vXvHj165CSGTISFta1TFCA/+FLptx7uzC4F0EklflL3gODmCTH5PotLOYUzaA==
X-Received: by 2002:a17:902:f78c:b0:1e5:93fc:efb4 with SMTP id q12-20020a170902f78c00b001e593fcefb4mr21243226pln.35.1713370529562; Wed, 17 Apr 2024 09:15:29 -0700 (PDT)
Received: from mail-pl1-f169.google.com (mail-pl1-f169.google.com. [209.85.214.169]) by smtp.gmail.com with ESMTPSA id x6-20020a170902a38600b001e469386fddsm11975011pla.40.2024.04.17.09.15.29 for <netconf@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 17 Apr 2024 09:15:29 -0700 (PDT)
Received: by mail-pl1-f169.google.com with SMTP id d9443c01a7336-1e2b1cd446fso45543985ad.3 for <netconf@ietf.org>; Wed, 17 Apr 2024 09:15:29 -0700 (PDT)
X-Forwarded-Encrypted: i=1; AJvYcCWyJyOWXRL5iZng8pj4qCx2pDNSMq5fCPCW5ghBrX7Y4lyF/uEnrBGTNfguLdnPVVzH6evpXD0kXOk7+4OqQkbb
X-Received: by 2002:a17:902:c94d:b0:1e3:d4a2:3882 with SMTP id i13-20020a170902c94d00b001e3d4a23882mr21598380pla.2.1713370528968; Wed, 17 Apr 2024 09:15:28 -0700 (PDT)
MIME-Version: 1.0
References: <dec8b1969a8f4511bb99b550407f23d7@huawei.com> <CACvbXWEjB=i6T6JoaCKH3a=eFQ00n2tw2nXfUJkJ_LMgaBQCYg@mail.gmail.com> <0100018eecd3312d-adb42068-b6bf-4608-8797-1e77599b8817-000000@email.amazonses.com>
In-Reply-To: <0100018eecd3312d-adb42068-b6bf-4608-8797-1e77599b8817-000000@email.amazonses.com>
From: Per Andersson <per.ietf@ionio.se>
Date: Wed, 17 Apr 2024 16:15:17 +0000
X-Gmail-Original-Message-ID: <CACvbXWGdp_sh4xncUVbDBBYO2JxKT4RxpuHb5GiANSrtn5FxiQ@mail.gmail.com>
Message-ID: <CACvbXWGdp_sh4xncUVbDBBYO2JxKT4RxpuHb5GiANSrtn5FxiQ@mail.gmail.com>
To: Kent Watsen <kent@watsen.net>
Cc: Olof Hagsand <olof@hagsand.se>, Andy Bierman <andy@yumaworks.com>, yuchaode <yuchaode=40huawei.com@dmarc.ietf.org>, "netconf@ietf.org" <netconf@ietf.org>, "yanglin (N)" <yanglin60@huawei.com>, liuzhoulong <liuzhoulong@huawei.com>, "Wangxi(Cordelia)" <wangxi114@huawei.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/XdM1xqeF1vh4gcGx3NzNTVUt6js>
Subject: Re: [netconf] What is the response structure when querying a specific instance object in a list?
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 17 Apr 2024 16:15:32 -0000

Hi!

ConfD and NSO work exactly the same FWIW. :)

A list element explicitly addressed is returned with
wrapping list square brackets.


--
Per


On Wed, Apr 17, 2024 at 4:10 PM Kent Watsen <kent@watsen.net> wrote:
>
>
> Per is right, it is not well-defined in RFC 8040 and the examples are counter-intuitive.
> - Please see https://github.com/netconf-wg/restconf-next/issues/5
>
> Personally, I’d like file an errata to document that the example is wrong.  But, first, it would be good to know what leading RESTCONF implementations do.
>
> Can we hear back from, e.g., Clixon, Confd, YumaPro devs?
>
> Kent
>
>
> On Apr 16, 2024, at 8:22 AM, Per Andersson <per.ietf@ionio.se> wrote:
>
> Hi!
>
> I tried looking for support on how to return the JSON result
> in RFC 8040 and RFC 7951 but found no text defining it.
>
> However, the examples in Appendix B.3.9 shows that when
> adressing a specific list element, it should be enclosed in
> square brackets.
>
> FWIW this is also how our system behaves.
>
>
> --
> Per
>
> _______________________________________________
> netconf mailing list
> netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
>
>

v2.23.0 | Report a Bug | By Email