[netconf] [Technical Errata Reported] RFC8040 (7866)
RFC Errata System <rfc-editor@rfc-editor.org> Sat, 23 March 2024 17:38 UTC
Return-Path: <wwwrun@rfcpa.amsl.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 03295C14F5FB for <netconf@ietfa.amsl.com>; Sat, 23 Mar 2024 10:38:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.658
X-Spam-Level:
X-Spam-Status: No, score=-6.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 rjKoluTtwqdl for <netconf@ietfa.amsl.com>; Sat, 23 Mar 2024 10:38:10 -0700 (PDT)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 7354CC151073 for <netconf@ietf.org>; Sat, 23 Mar 2024 10:38:10 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 33A49E6634; Sat, 23 Mar 2024 10:38:10 -0700 (PDT)
To: andy@yumaworks.com, mbj@tail-f.com, kwatsen@juniper.net, warren@kumari.net, mjethanandani@gmail.com, mjethanandani@gmail.com, kent+ietf@watsen.net
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: andy@yumaworks.com, netconf@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240323173810.33A49E6634@rfcpa.amsl.com>
Date: Sat, 23 Mar 2024 10:38:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/HTi5G7a8SwyRO3QyyaA8KGO4978>
Subject: [netconf] [Technical Errata Reported] RFC8040 (7866)
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: Sat, 23 Mar 2024 17:38:15 -0000
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/eid7866 -------------------------------------- Type: Technical Reported by: Andy Bierman <andy@yumaworks.com> Section: 3.5.3 Original Text ------------- Text occurs in two places 1) The leaf-list value is specified as a string, using the canonical representation for the YANG data type. Any reserved characters MUST be percent-encoded, according to Sections 2.1 and 2.5 of [RFC3986]. 2) The key value is specified as a string, using the canonical representation for the YANG data type. Any reserved characters MUST be percent-encoded, according to Sections 2.1 and 2.5 of [RFC3986]. Corrected Text -------------- 1) The leaf-list value is specified as a string, using the canonical representation for the YANG data type. Any reserved characters MUST be percent-encoded, according to Sections 2.1, 2.2, and 2.5 of [RFC3986]. 2) The key value is specified as a string, using the canonical representation for the YANG data type. Any reserved characters MUST be percent-encoded, according to Sections 2.1, 2.2, and 2.5 of [RFC3986]. Notes ----- The reserved character list is defined in section 2.2 of RFC 3986 Instructions: ------------- This erratum is currently posted as "Reported". (If it is spam, it will be removed shortly by the RFC Production Center.) Please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party will 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 Stream : IETF Verifying Party : IESG
- [netconf] [Technical Errata Reported] RFC8040 (78… RFC Errata System
- Re: [netconf] [Technical Errata Reported] RFC8040… Jernej Tuljak
- Re: [netconf] [Technical Errata Reported] RFC8040… Kent Watsen
- Re: [netconf] [Technical Errata Reported] RFC8040… Andy Bierman
- Re: [netconf] [Technical Errata Reported] RFC8040… Andy Bierman
- Re: [netconf] [Technical Errata Reported] RFC8040… Jernej Tuljak
- Re: [netconf] [Technical Errata Reported] RFC8040… Andy Bierman
- Re: [netconf] [Technical Errata Reported] RFC8040… Mahesh Jethanandani
- Re: [netconf] [Technical Errata Reported] RFC8040… Kent Watsen
- Re: [netconf] [Technical Errata Reported] RFC8040… Mahesh Jethanandani
- Re: [netconf] [Technical Errata Reported] RFC8040… Andy Bierman
- Re: [netconf] [Technical Errata Reported] RFC8040… Mahesh Jethanandani
- Re: [netconf] [Technical Errata Reported] RFC8040… Jernej Tuljak
- Re: [netconf] [Technical Errata Reported] RFC8040… Mahesh Jethanandani
- Re: [netconf] [Technical Errata Reported] RFC8040… Andy Bierman
- Re: [netconf] [Technical Errata Reported] RFC8040… Jernej Tuljak
- Re: [netconf] [Technical Errata Reported] RFC8040… Andy Bierman