Re: [netconf] restconf collections

Martin Björklund <mbj+ietf@4668.se> Thu, 29 October 2020 16:22 UTC

Return-Path: <mbj+ietf@4668.se>
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 546323A09EF for <netconf@ietfa.amsl.com>; Thu, 29 Oct 2020 09:22:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.102
X-Spam-Level:
X-Spam-Status: No, score=-0.102 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, PDS_NAKED_TO_NUMERO=1.999, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=4668.se header.b=FCtNUxhb; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Tu3z2Iel
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 r_-Tq6KVbpOe for <netconf@ietfa.amsl.com>; Thu, 29 Oct 2020 09:22:24 -0700 (PDT)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AE223A09E7 for <netconf@ietf.org>; Thu, 29 Oct 2020 09:22:24 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 498897BC; Thu, 29 Oct 2020 12:22:23 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Thu, 29 Oct 2020 12:22:23 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=4668.se; h=date :message-id:to:cc:subject:from:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=fm3; bh= fPDCqfq4eUXn3KhsW8NRdD6KPeKkZAihDKWmRAkxfps=; b=FCtNUxhbQo/g497J WmzF14s5hQSXYHdMBSQhjPo5uIrnmTlC2cZrzvoayGyKtcHMZcndXu069l2usr84 wWV0rX83yHql63LvLt6P/W4kzR5e/rHUkXWwgBfrjfznSlaxxHXrF3gIuOenyFoc MUvLiBCKFYqc48TwiJlBA2TXYe6e5qgTTmih7zrADB3MpNg6D/dHnyintAby20Xe AFciZN3pRb6+cz3844B2F7h+oIwnrzhytAvQDu30IQpaCGF/WwHslwVVyGxMr0ff ZgGg1dO+8e4pKhe01/NUdL47ci9ZaAf1eJFISK3A8J0atdrieezrB0b+kMtGiyEf OFch0g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=fPDCqfq4eUXn3KhsW8NRdD6KPeKkZAihDKWmRAkxf ps=; b=Tu3z2IeliF5UnN+VnLlB22JSgevkcFBr6S6nPlOxa0gOHm4GlEpE4q12T kCBRt8G2/RPN4/dRWVHEgBJSbYwNGybsDH1+8AqLaEaO73bnBCsOWn4ndUCLll9G 6bnqJSZEXaWutcAu3aTqIXgCLxFs4WW9WR56diKYhIytrF1qRu/vIj+pAYILi9l1 yZMqW/E8R8KAO3jx2bgmgy+1yMlLVnrpDO+1VQGxzcTPxI9Pqaj7GrrRuoUwBNmL UnIJ+H72FjfAiAhVrA+SCPzBptL7fZmv0RnZeiMxWE5csfjgC/vWg8n2jCzlMGe2 ctZR7y880Zzg1fI46te0ESPaTz7mA==
X-ME-Sender: <xms:PuyaX2IyyRkFgLTYY_LBKRcXyN9mQZJMiTh5NgdYn_5yaliembgNdA> <xme:PuyaX-KbPHR1RsbquT2G4diF58IK1cuAZ-TqbWQtjkrVxqx-IPt_NvziysmiNKk1T wzTTGvfBv7xYQa9Zaw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrleefgdekjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepfffkvffuhfgjfhfogggtgfesthgsre dtredtjeenucfhrhhomhepofgrrhhtihhnuceujhpnrhhklhhunhguuceomhgsjhdoihgv thhfseegieeikedrshgvqeenucggtffrrghtthgvrhhnpeehteegtdffgfegffekvdejke evleetuedutddtfffhlefgtedvveehvdeguedtudenucfkphepvdduvddrvddugedruddu rdeitdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe hmsghjodhivghtfhesgeeiieekrdhsvg
X-ME-Proxy: <xmx:PuyaX2vDk5k49Lo6HiLSWkgiZzwgCGYR_NQ6DlkOJx-4bExQpVX9VQ> <xmx:PuyaX7bCA1tZ3vJ_vZb6-_PYFg-v5boagZqUgRdOfxdo718rmU0kNw> <xmx:PuyaX9YvlbHkR7Fk3KZiEvMN29z72wvYS2sgq_VWCN1PMzEvZfSrpA> <xmx:PuyaX_2oD_YV0Xl8IwiY7-o0GZrCa9VBnu2iw24dcNcLIqGk800K0A>
Received: from localhost (212-214-11-60-static.se.customer.tele2.net [212.214.11.60]) by mail.messagingengine.com (Postfix) with ESMTPA id 240453280064; Thu, 29 Oct 2020 12:22:22 -0400 (EDT)
Date: Thu, 29 Oct 2020 17:22:20 +0100 (CET)
Message-Id: <20201029.172220.1401832604665061345.id@4668.se>
To: kent+ietf@watsen.net
Cc: netconf@ietf.org
From: Martin =?iso-8859-1?Q?Bj=F6rklund?= <mbj+ietf@4668.se>
In-Reply-To: <01000175751b1e3f-d4a84796-9f90-49eb-bbea-d3be5966f233-000000@email.amazonses.com>
References: <20201029.085108.142889809049265936.id@4668.se> <01000175751b1e3f-d4a84796-9f90-49eb-bbea-d3be5966f233-000000@email.amazonses.com>
X-Mailer: Mew version 6.8 on Emacs 26.3
Mime-Version: 1.0
Content-Type: Text/Plain; charset=utf-8
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/yF0bP9euvyBhyxyf5bdFDpawXfI>
Subject: Re: [netconf] restconf collections
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, 29 Oct 2020 16:22:25 -0000

Kent Watsen <kent+ietf@watsen.net> wrote:
> Hi Martin,
> 
> > This is not a good proposal, since the result is not a valid XML
> > document.  
> 
> How is this important?

I will be difficult to parse, since you can't just parse it with a
standard XML parser.


> It’s not an HTTP-constraint, right?

No.

> and I
> don’t think it is needed for message-framing either.
> 
> I guess, as you mention below, the media-type is inappropriate (though
> 11.3.1 isn’t as clear as one might hope), so maybe the response is
> okay if only changing the media type?

Sure, from a pure media type pow; but I still think it would be a
mistake to send a concatenation of valid XML documents w/o any
separators (and adding custom separators may work, but note how the
original NETCONF XML encoding tried to do that, but failed...).

> > An XML document has exactly one root element.
> > 
> > Also, the media types used in the examples are misleading.  The
> > example reply doesn't match the media type
> > "application/yang-data+json" (same for xml).
> 
> How isn’t the media-type okay for JSON, for the response in the
> previous message?  It seems valid to me...

You're right, it is valid.  My bad.  I forgot how clever the JSON
encoding of a single list entry was ;-)

> No dispute regarding the XML media-type.  
> 
> 
> > I suggest you define new media types and a "collection" root
> > element; or keep the media types and define "collection" in a YANG
> > module as:
> > 
> >  anydata collection;
> 
> Noted, but first would like to understand why simply changing the
> media-type alone (while keeping the responses in the previous message)
> isn’t sufficient, for both xml and json.
> 
> Each media-type can define its own format so, e.g.,
> “application/yang-data+xml-list" could be used to define a list of XML
> documents, right?
> 
> That said, I acknowledge that having a root-element may aid
> xml-parsers, and thus perhaps worthwhile for that reason...just want
> to ensure we understand the motivations accurately.

Yes this is my concern.


/martin