IETF Logo Mail Archive

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

Mahesh Jethanandani <mjethanandani@gmail.com> Thu, 28 March 2024 20:53 UTC

Return-Path: <mjethanandani@gmail.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 72391C169410 for <netconf@ietfa.amsl.com>; Thu, 28 Mar 2024 13:53:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.094
X-Spam-Level:
X-Spam-Status: No, score=-7.094 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 pPt_lgjI_jKx for <netconf@ietfa.amsl.com>; Thu, 28 Mar 2024 13:53:40 -0700 (PDT)
Received: from mail-ot1-x330.google.com (mail-ot1-x330.google.com [IPv6:2607:f8b0:4864:20::330]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 93DADC15198D for <netconf@ietf.org>; Thu, 28 Mar 2024 13:53:40 -0700 (PDT)
Received: by mail-ot1-x330.google.com with SMTP id 46e09a7af769-6e68d358974so664094a34.3 for <netconf@ietf.org>; Thu, 28 Mar 2024 13:53:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1711659220; x=1712264020; darn=ietf.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=fi5+7RNL/urr2NtqudBfMzi4Nicgw9upuFlCcIL6IjA=; b=BYSPucf5sSQxA9sR6PidGr9LWVgAE9xeJlRfArIev3BOuF7Pj76/SiW1WUpCJ5cCEy B1Kl7sR2Ag7Qv3yZUrM3jySIVVAcrhtTjejNhnZmhgUJKCSGnk7POSYKuZUfKyEEw4Ev 1vK29s2fXHc72RL91RFJfUsQAAR8ufEziFmjlbAVX3yL7vkDKNoRbMPi1v8oa5o1Kdk3 Eshozz1z/xMkKlg3I+ZRWFE3DR35n/92s1rwZFxAFHR55Tk5rsUgmVQb83ff7qPIWcf2 ztbQ8B50fbDGvw1r1pczlpVk4RF9zeIxYgFXt2Nr8HqZdzh7GQ+8ScoMkGD5fgjZBSNv FMWg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711659220; x=1712264020; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=fi5+7RNL/urr2NtqudBfMzi4Nicgw9upuFlCcIL6IjA=; b=cmekRp/1GErTz3++sJSHEh6h0BX5q966TAfM7raEYx9NhT1wOzowRtVtYpFrSiqBr5 GW2W70ABEEKI/8teFR/2STQgrVvJe8AwexacPSj2NfqFToXcX3ComBtwJu1LytcU8SsF MDVL+W3KNPBz0K70EK9NIX8BadzmLZhVi9x4Z99wGBLvAKQCcMW+2Di2RnUPhERaBvqY 4kO5DD0Zj7+K4jygJ1h4FS/Wto9P+nSBywa6q2F2ZQk8iZC5oS1KO1Vg6v7UsmA7LkXX TjHSJTiSwvc/vwoIKVpX64evnTyoc2sdQ8xd9xhIZtc5ESKMEoB0h/saR+gq6S58ZTJV Rh2Q==
X-Forwarded-Encrypted: i=1; AJvYcCVTy4ZZ5LpXYCaKq22ZKK3s2viz2voJ2bH5NId/FOxjAW6uyZaZMu61muGjgCpVHDMVBXLzf29FoiVhXGPnAIdj
X-Gm-Message-State: AOJu0Yz72p9VjjJ5M0SVJSd8FxKw1TQx/6Y0cMaLpiQFDRae9/hnfJrZ KADRBxxPZ7lLXPWrJAgcC+2nz5mbpNMIfk4ijey69CJBdae157Dq5PyeIhjZUgI=
X-Google-Smtp-Source: AGHT+IEN34/vj80AYKPcDrfWzW2FmgF8mvN74I4opqyZSRg+UNvqePCgnBReyM9+/mD/SlvjSGh4yg==
X-Received: by 2002:a05:6870:cc85:b0:221:cdf9:2453 with SMTP id ot5-20020a056870cc8500b00221cdf92453mr418711oab.27.1711659219672; Thu, 28 Mar 2024 13:53:39 -0700 (PDT)
Received: from smtpclient.apple ([70.234.233.187]) by smtp.gmail.com with ESMTPSA id g15-20020aa79f0f000000b006e6c60aeb21sm1804729pfr.70.2024.03.28.13.53.38 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 28 Mar 2024 13:53:39 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <6E1A4F42-8579-48E0-949C-F52414C1C8CE@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_02C9BCD8-0A40-4F46-8116-5A80B693F690"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.15\))
Date: Thu, 28 Mar 2024 13:53:38 -0700
In-Reply-To: <CABCOCHR3FxYdh3atxpSmGuxAa4KP+oXRgaK2AZe9ANvJ=zs=TQ@mail.gmail.com>
Cc: Kent Watsen <kent+ietf@watsen.net>, RFC Editor <rfc-editor@rfc-editor.org>, mbj@tail-f.com, Warren Kumari <warren@kumari.net>, NETCONF WG <netconf@ietf.org>
To: Andy Bierman <andy@yumaworks.com>
References: <20240323173810.33A49E6634@rfcpa.amsl.com> <0100018e809ecc8b-b17354dc-f70c-437a-b915-b8ed4086bffb-000000@email.amazonses.com> <DBDBA573-AEB6-4231-9684-E1C0E23660C6@gmail.com> <CABCOCHT-hY8+pd=05bgAmZdnVmN_HuARzX6WrOXp2imD0RpuAg@mail.gmail.com> <A5FFCFE0-57AC-44F1-B6A4-2FCD352A8CA7@gmail.com> <CABCOCHR3FxYdh3atxpSmGuxAa4KP+oXRgaK2AZe9ANvJ=zs=TQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3654.120.0.1.15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/pBhy_RtSndaWlg4M0RW8PG7bzEI>
Subject: Re: [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: Thu, 28 Mar 2024 20:53:44 -0000

Ok. How about this?

Original Text:
------------------

Text occurs in five 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]. 

3)    

      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].

4)    

      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].  The comma (",") character MUST be percent-encoded if
      it is present in the key value.


5)    

      The contents of any query parameter value MUST be encoded according
      to Section 3.4 of [RFC3986].  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]. 

3)    

      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].

4)    

      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].  The comma (",") character MUST be percent-encoded if
      it is present in the key value.

5)    
      
      The contents of any query parameter value MUST be encoded according
      to Section 3.4 of [RFC3986].  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

> On Mar 28, 2024, at 12:39 PM, Andy Bierman <andy@yumaworks.com> wrote:
> 
> 
> 
> On Thu, Mar 28, 2024 at 12:25 PM Mahesh Jethanandani <mjethanandani@gmail.com <mailto:mjethanandani@gmail.com>> wrote:
> Apparently, I can edit the Errata. Please confirm that this is all the corrections we are making:
> 
> Original Text:
> -----------------
> 
> Text occurs in three places
> 
> 
> Now there are 2 sections to identify:
> 
> 1) sec. 3.5.3 (para 4)
> 2) sec. 3.5.3 (para 5)
> 3) sec. 5.1 (para 3)
> 
> Andy
> 
> 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]. 
> 
> 3)    
> 
>        The contents of any query parameter value MUST be encoded according
>         to Section 3.4 of [RFC3986].  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]. 
> 
> 3)  
> 
>      The contents of any query parameter value MUST be encoded according
>       to Section 3.4 of [RFC3986].  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
> 
>> On Mar 28, 2024, at 11:05 AM, Andy Bierman <andy@yumaworks.com <mailto:andy@yumaworks.com>> wrote:
>> 
>> 
>> 
>> On Thu, Mar 28, 2024 at 9:25 AM Mahesh Jethanandani <mjethanandani@gmail.com <mailto:mjethanandani@gmail.com>> wrote:
>> Hi Kent/Andy,
>> 
>> Should I reject the Errata so it can be filed again?
>> 
>> 
>> I guess so -- I don't think there is any way to edit this one
>> 
>> Andy
>>  
>>> On Mar 27, 2024, at 8:54 AM, Kent Watsen <kent+ietf@watsen.net <mailto:kent+ietf@watsen.net>> wrote:
>>> 
>>> This errata is incomplete.
>>> The issue occurs three times.  
>>> The occurrence in Section 5.1 is missing.
>>> 
>>> K.
>>> 
>>> 
>>>> On Mar 23, 2024, at 1:38 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/eid7866 <https://www.rfc-editor.org/errata/eid7866>
>>>> 
>>>> --------------------------------------
>>>> Type: Technical
>>>> Reported by: Andy Bierman <andy@yumaworks.com <mailto: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
>>> 
>> 
>> 
>> Mahesh Jethanandani
>> mjethanandani@gmail.com <mailto:mjethanandani@gmail.com>
>> 
>> 
>> 
>> 
>> 
>> 
> 
> 
> Mahesh Jethanandani
> mjethanandani@gmail.com <mailto:mjethanandani@gmail.com>
> 
> 
> 
> 
> 
> 


Mahesh Jethanandani
mjethanandani@gmail.com

v2.23.0 | Report a Bug | By Email