IETF Logo Mail Archive

Re: [netconf] Added restconf-next for restructuring error messages

Kent Watsen <kent+ietf@watsen.net> Wed, 01 July 2020 18:12 UTC

Return-Path: <010001730b94bddd-e070a169-e418-46ec-b639-294fa7c5fbd2-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 64E323A0937 for <netconf@ietfa.amsl.com>; Wed, 1 Jul 2020 11:12:47 -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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, 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 33xYkTP4iGPB for <netconf@ietfa.amsl.com>; Wed, 1 Jul 2020 11:12:45 -0700 (PDT)
Received: from a48-92.smtp-out.amazonses.com (a48-92.smtp-out.amazonses.com [54.240.48.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FEF23A0929 for <netconf@ietf.org>; Wed, 1 Jul 2020 11:12:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1593627164; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=EMP7A3m0gOqsZaE/w+zBUIChvyWVpXFI9rYJ+PIqzv0=; b=HB1QtGJ05MvDNYQfqigmyv77D7qe9iVNNczf9Mwk1JVY8NzVTAJgUjP8YCVi1v8l YWEUEaU++7PM7JqKC31XjC03Dr7hOFvd9qguXsmQi898XLa3Hb7HFHFytwBNcTy/3Am UXJ3cQiZo34znO4htWD98i473i1REUnOjoUbZh6Y=
From: Kent Watsen <kent+ietf@watsen.net>
Message-ID: <010001730b94bddd-e070a169-e418-46ec-b639-294fa7c5fbd2-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A3C69E4B-2EC9-45A6-8D24-6B4FC499DA61"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Wed, 01 Jul 2020 18:12:44 +0000
In-Reply-To: <CABCOCHQqWADVDou+tXDOah_wTHR9RBMpwn1QKwbRAQ-EH0BRQg@mail.gmail.com>
Cc: "netconf@ietf.org" <netconf@ietf.org>
To: Andy Bierman <andy@yumaworks.com>
References: <010001730ac58f90-0ce0fc67-2c25-403e-98c4-983d7007ea68-000000@email.amazonses.com> <CABCOCHQqWADVDou+tXDOah_wTHR9RBMpwn1QKwbRAQ-EH0BRQg@mail.gmail.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-SES-Outgoing: 2020.07.01-54.240.48.92
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/GRtB83sD8IRSPhwl5nj6esHHFYI>
Subject: Re: [netconf] Added restconf-next for restructuring error messages
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: Wed, 01 Jul 2020 18:12:48 -0000

I was expecting this response  ;)

We could grandfather the current “errors” structure by, e.g., using a “choice”...

We don’t even have to wait for RC-next, as someone could submit a short I-D for just this issue.  We just need to define a way for the client to signal to the server its preferences…likely the existing "Accept-Type” header could be used.

K.


> On Jul 1, 2020, at 12:41 PM, Andy Bierman <andy@yumaworks.com> wrote:
> 
> Hi,
> 
> I don't agree that any NBC changes are needed to RESTCONF, including this one.
> I agree servers usually send 1 error, but not always. E.g., the <validate> operation
> returns as many errors as it can find and does not stop on the first error.
> It is not a burden to have an "errors" container so the protocol allows for multiple errors
> and is the same data model for XML and JSON.
> 
> Andy
> 
> 
> 
> On Wed, Jul 1, 2020 at 7:26 AM Kent Watsen <kent+ietf@watsen.net <mailto:kent%2Bietf@watsen.net>> wrote:
> Folks,
> 
> I just added this “restconf-next” issue for restructuring error messages:
> 
> 	https://github.com/netconf-wg/restconf-next/issues/3 <https://github.com/netconf-wg/restconf-next/issues/3>
> 
> K.
> 
> _______________________________________________
> netconf mailing list
> netconf@ietf.org <mailto:netconf@ietf.org>
> https://www.ietf.org/mailman/listinfo/netconf <https://www.ietf.org/mailman/listinfo/netconf>

v2.23.0 | Report a Bug | By Email