[P2PSIP] correction: RFC 7636 (EID 6471) - Re: [Technical Errata Reported] RFC7363 (7088)

Alice Russo <arusso@amsl.com> Wed, 31 August 2022 19:36 UTC

Return-Path: <arusso@amsl.com>
X-Original-To: p2psip@ietfa.amsl.com
Delivered-To: p2psip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F4087C15AE2F for <p2psip@ietfa.amsl.com>; Wed, 31 Aug 2022 12:36:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.207
X-Spam-Level:
X-Spam-Status: No, score=-4.207 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 stdj7D9axXWe for <p2psip@ietfa.amsl.com>; Wed, 31 Aug 2022 12:36:07 -0700 (PDT)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (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 CC5B2C14CE44 for <p2psip@ietf.org>; Wed, 31 Aug 2022 12:36:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id BC1F54243EF8; Wed, 31 Aug 2022 12:36:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YTfvbQjvNIga; Wed, 31 Aug 2022 12:36:07 -0700 (PDT)
Received: from [192.168.4.33] (unknown [76.146.133.44]) by c8a.amsl.com (Postfix) with ESMTPSA id 6515D424B440; Wed, 31 Aug 2022 12:36:07 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Alice Russo <arusso@amsl.com>
In-Reply-To: <798A2A5D-C249-41B8-A203-2DF3691207C4@brianrosen.net>
Date: Wed, 31 Aug 2022 12:36:05 -0700
Cc: Jouni.Maenpaa@ericsson.com, Gonzalo.Camarillo@ericsson.com, "Murray S. Kucherawy" <superuser@gmail.com>, Francesca Palombini <francesca.palombini@ericsson.com>, CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es>, p2psip@ietf.org, RFC Editor <rfc-editor@rfc-editor.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <DF2FFE9F-A2CB-4564-953B-36E55DF254CE@amsl.com>
References: <20220815074425.ECED34C09D@rfcpa.amsl.com> <acb8ff49-93f7-7f1e-55c9-114ca0b3d6ec@softarmor.com> <798A2A5D-C249-41B8-A203-2DF3691207C4@brianrosen.net>
To: Brian Rosen <br@brianrosen.net>, Dean Willis <dean.willis@softarmor.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/p2psip/g9fE1nNU4wP3hR-npnu3tUZlEkE>
Subject: [P2PSIP] correction: RFC 7636 (EID 6471) - Re: [Technical Errata Reported] RFC7363 (7088)
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/p2psip>, <mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/p2psip/>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2022 19:36:12 -0000

Brian, Dean,

FYI, the content of this errata report was actually about RFC 7636, not RFC 7363. (The submitted report used the wrong RFC number.)

And the content of this report already exists as
https://www.rfc-editor.org/errata/eid6471  (so EID 7088 has been deleted).

Separately, I'll forward the notification re: RFC 7636 (EID 6471) in case you'd like to pass along your recommendation to the relevant ADs that the report be marked "Held for Document Update".

Thank you.
RFC Editor/ar

> On Aug 19, 2022, at 6:58 AM, Brian Rosen <br@brianrosen.net> wrote:
> 
> Yeah but do we want to do anything with it?
> “Hold for revision?”
> 
> Brian
> 
>> On Aug 17, 2022, at 2:52 PM, Dean Willis <dean.willis@softarmor.com> wrote:
>> 
>> 
>> Seems legit.
>> 
>> On 8/15/22 02:44, RFC Errata System wrote:
>>> The following errata report has been submitted for RFC7363,
>>> "Self-Tuning Distributed Hash Table (DHT) for REsource LOcation And Discovery (RELOAD)".
>>> 
>>> --------------------------------------
>>> You may review the report below and at:
>>> https://www.rfc-editor.org/errata/eid7088
>>> 
>>> --------------------------------------
>>> Type: Technical
>>> Reported by: Keepn <keepn58@gmail.com>
>>> 
>>> Section: 7.1
>>> 
>>> Original Text
>>> -------------
>>> The client SHOULD create a "code_verifier" with a minimum of 256 bits
>>> of entropy.  This can be done by having a suitable random number
>>> generator create a 32-octet sequence.  The octet sequence can then be
>>> base64url-encoded to produce a 43-octet URL safe string to use as a
>>> "code_challenge" that has the required entropy.
>>> 
>>> Corrected Text
>>> --------------
>>> The client SHOULD create a "code_verifier" with a minimum of 256 bits
>>> of entropy.  This can be done by having a suitable random number
>>> generator create a 32-octet sequence.  The octet sequence can then be
>>> base64url-encoded to produce a 43-octet URL safe string to use as a
>>> "code_verifier" that has the required entropy.
>>> 
>>> Notes
>>> -----
>>> The "32-octet sequence" referenced in the original text seems to be inconsistent with Section 4.1, which states that the minimum length of the code_verifier is 43 characters. It would be consistent by changing "code_challenge" to "code_verifier".
>>> 
>>> 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.
>>> 
>>> --------------------------------------
>>> RFC7363 (draft-ietf-p2psip-self-tuning-15)
>>> --------------------------------------
>>> Title               : Self-Tuning Distributed Hash Table (DHT) for REsource LOcation And Discovery (RELOAD)
>>> Publication Date    : September 2014
>>> Author(s)           : J. Maenpaa, G. Camarillo
>>> Category            : PROPOSED STANDARD
>>> Source              : Peer-to-Peer Session Initiation Protocol RAI
>>> Area                : Real-time Applications and Infrastructure
>>> Stream              : IETF
>>> Verifying Party     : IESG
>>> 
>>> _______________________________________________
>>> P2PSIP mailing list
>>> P2PSIP@ietf.org
>>> https://www.ietf.org/mailman/listinfo/p2psip
>> 
>