[Netconf] NETCONF warnings
Andy Bierman <andy@yumaworks.com> Fri, 02 October 2015 20:28 UTC
Return-Path: <andy@yumaworks.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2258E1B2D46 for <netconf@ietfa.amsl.com>; Fri, 2 Oct 2015 13:28:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 sxdKXwPChy89 for <netconf@ietfa.amsl.com>; Fri, 2 Oct 2015 13:28:37 -0700 (PDT)
Received: from mail-la0-f50.google.com (mail-la0-f50.google.com [209.85.215.50]) (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 263111B2D30 for <netconf@ietf.org>; Fri, 2 Oct 2015 13:28:37 -0700 (PDT)
Received: by lafb9 with SMTP id b9so10576211laf.0 for <netconf@ietf.org>; Fri, 02 Oct 2015 13:28:35 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=fRQ+siGQvaLvT3LnD1rw32WG2p1q1Y+GDrM/9Nemtcg=; b=Jjr25XkDFqFT0lRWvk/RqBpzjQtcKyeLcGvem7ZaVi9OK3mgk0tYvttkkdO4M6Awyd +9NTJ/y+SiyPjhskmiVEdPmfnHRGMFywTWxp98xfiP6QXMKhVwdItCLeonO3DcBVUNcA ypnd7Le7YA2J6TINiXXkuSpwYtbsef1tgwmN9cETgpuia5DDOrIlRpWhbEr67Kw+G6cg MqglKUY/R1p7q9kOi+r1bsbCWjtPUVLJXAiobsjixQFVgc0FB/aeXGHesBUgyCzcD63S GcLnM88jo4FoYHFgkzsZY9BLLe+Dyj0c18mXqQmSmLvwStlS/1HzwrvWx9fJWJBzKhlD 28iQ==
X-Gm-Message-State: ALoCoQmEPjuXC15Rf1liLpK4C5LFK6iYpE2/SKKNhbfUDLHws9d4OrPhLizzyiznfKy/FbBfhpU5
MIME-Version: 1.0
X-Received: by 10.112.200.229 with SMTP id jv5mr6498670lbc.123.1443817715424; Fri, 02 Oct 2015 13:28:35 -0700 (PDT)
Received: by 10.112.138.72 with HTTP; Fri, 2 Oct 2015 13:28:35 -0700 (PDT)
Date: Fri, 02 Oct 2015 13:28:35 -0700
Message-ID: <CABCOCHS9Dkj4JmDq_27qz3PuO9CLRLm=VH2iDip3VaUb0WBqfA@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: Netconf <netconf@ietf.org>
Content-Type: multipart/alternative; boundary="001a11c266500c79fe0521250230"
Archived-At: <http://mailarchive.ietf.org/arch/msg/netconf/9xiPU_p1jqyB282OQrMBgkENwcU>
Subject: [Netconf] NETCONF warnings
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Network Configuration WG mailing 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: Fri, 02 Oct 2015 20:28:39 -0000
Hi, The issue of warnings keeps coming up with customers. Technically, there are no error-tags that have an assigned error-severity of 'warning'. The <rpc-error> message is supposed to use 1 of the standard error-tags. So how should the server send warnings in NETCONF? A) new message like <rpc-warning> B) new error-tag with assigned severity 'warning' C) pick an existing error-tag to allow as a warning D) allow any error-tag to be severity warning E) something else? Andy
- [Netconf] NETCONF warnings Andy Bierman
- Re: [Netconf] NETCONF warnings t.petch
- Re: [Netconf] NETCONF warnings Andy Bierman
- Re: [Netconf] NETCONF warnings Andy Bierman
- Re: [Netconf] NETCONF warnings Kent Watsen
- Re: [Netconf] NETCONF warnings Mahesh Jethanandani
- Re: [Netconf] NETCONF warnings Andy Bierman
- Re: [Netconf] NETCONF warnings Juergen Schoenwaelder
- Re: [Netconf] NETCONF warnings Andy Bierman