Re: [netconf] [Technical Errata Reported] RFC8040 (5761)

Qin Wu <bill.wu@huawei.com> Mon, 24 June 2019 13:27 UTC

Return-Path: <bill.wu@huawei.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 BD8E112028B for <netconf@ietfa.amsl.com>; Mon, 24 Jun 2019 06:27:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 ojcdS3clYjOu for <netconf@ietfa.amsl.com>; Mon, 24 Jun 2019 06:27:53 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3306A12010C for <netconf@ietf.org>; Mon, 24 Jun 2019 06:27:53 -0700 (PDT)
Received: from lhreml708-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 8909BB6677558CE9F0D8; Mon, 24 Jun 2019 14:27:50 +0100 (IST)
Received: from lhreml711-chm.china.huawei.com (10.201.108.62) by lhreml708-cah.china.huawei.com (10.201.108.49) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 24 Jun 2019 14:27:44 +0100
Received: from lhreml711-chm.china.huawei.com (10.201.108.62) by lhreml711-chm.china.huawei.com (10.201.108.62) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Mon, 24 Jun 2019 14:27:44 +0100
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by lhreml711-chm.china.huawei.com (10.201.108.62) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Mon, 24 Jun 2019 14:27:44 +0100
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.66]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0415.000; Mon, 24 Jun 2019 21:27:38 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Andy Bierman <andy@yumaworks.com>, RFC Errata System <rfc-editor@rfc-editor.org>
CC: Martin Bjorklund <mbj@tail-f.com>, Kent Watsen <kwatsen@juniper.net>, Ignas Bagdonas <ibagdona@gmail.com>, Warren Kumari <warren@kumari.net>, "Kent Watsen" <kent+ietf@watsen.net>, Mahesh Jethanandani <mjethanandani@gmail.com>, Netconf <netconf@ietf.org>
Thread-Topic: [Technical Errata Reported] RFC8040 (5761)
Thread-Index: AdUqkH9l9wzBT2yeTqKInHAuw/R2NQ==
Date: Mon, 24 Jun 2019 13:27:38 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABAA49AB6EE@nkgeml513-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.134.31.203]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABAA49AB6EEnkgeml513mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/MNLlKdCiq4ZV5JhMOyZz67xKWCw>
Subject: Re: [netconf] [Technical Errata Reported] RFC8040 (5761)
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: Mon, 24 Jun 2019 13:27:56 -0000

Thanks for the quick reply, can you clarify the reason behind? Thanks!

-Qin
发件人: Andy Bierman [mailto:andy@yumaworks.com]
发送时间: 2019年6月24日 20:59
收件人: RFC Errata System <rfc-editor@rfc-editor.org>
抄送: Martin Bjorklund <mbj@tail-f.com>om>; Kent Watsen <kwatsen@juniper.net>et>; Ignas Bagdonas <ibagdona@gmail.com>om>; Warren Kumari <warren@kumari.net>et>; Kent Watsen <kent+ietf@watsen.net>et>; Mahesh Jethanandani <mjethanandani@gmail.com>om>; Qin Wu <bill.wu@huawei.com>om>; Netconf <netconf@ietf.org>
主题: Re: [Technical Errata Reported] RFC8040 (5761)

Hi,

The cited text is in 4.4.1 (there is no 4.1.1).

I do not see any evidence that the WG intended to write the word "data-exists" but
wrote "resource-denied" instead. Therefore this cannot be changed with an errata.


Andy


On Sun, Jun 23, 2019 at 6:08 PM RFC Errata System <rfc-editor@rfc-editor.org<mailto:rfc-editor@rfc-editor.org>> wrote:
The following errata report has been submitted for RFC8040,
"RESTCONF Protocol".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid5761

--------------------------------------
Type: Technical
Reported by: Qin WU <bill.wu@huawei.com<mailto:bill.wu@huawei.com>>

Section: 4.1.1

Original Text
-------------
If the data resource already exists, then the POST request MUST fail
and a "409 Conflict" status-line MUST be returned.  The error-tag
value "resource-denied" is used in this case

Corrected Text
--------------
If the data resource already exists, then the POST request MUST fail
and a "409 Conflict" status-line MUST be returned.  The error-tag
value "data-exists" is used in this case

Notes
-----
The error-tag value should be corrected as "data-exists" in this case
based on the context. According to error-tag definition in RFC6241:

   error-tag:      resource-denied
   error-type:     transport, rpc, protocol, application
   error-severity: error
   error-info:     none
   Description:    Request could not be completed because of
                   insufficient resources.

It is apparent error-tag value "data-exists" should be corresponding
to the data resource already exists condition.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party
can log in to change the status and edit the report, if necessary.

--------------------------------------
RFC8040 (draft-ietf-netconf-restconf-18)
--------------------------------------
Title               : RESTCONF Protocol
Publication Date    : January 2017
Author(s)           : A. Bierman, M. Bjorklund, K. Watsen
Category            : PROPOSED STANDARD
Source              : Network Configuration
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG