IETF Logo Mail Archive

[P2PSIP] [Technical Errata Reported] RFC7363 (7088)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 15 August 2022 07:44 UTC

Return-Path: <wwwrun@rfcpa.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 947DBC14F741 for <p2psip@ietfa.amsl.com>; Mon, 15 Aug 2022 00:44:30 -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 1GqyTwBDxCCg for <p2psip@ietfa.amsl.com>; Mon, 15 Aug 2022 00:44:26 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [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 0D7BCC14CE41 for <p2psip@ietf.org>; Mon, 15 Aug 2022 00:44:26 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id ECED34C09D; Mon, 15 Aug 2022 00:44:25 -0700 (PDT)
To: Jouni.Maenpaa@ericsson.com, Gonzalo.Camarillo@ericsson.com, superuser@gmail.com, francesca.palombini@ericsson.com, br@brianrosen.net, cjbc@it.uc3m.es
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: keepn58@gmail.com, p2psip@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20220815074425.ECED34C09D@rfcpa.amsl.com>
Date: Mon, 15 Aug 2022 00:44:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/p2psip/GyFhxJu-Zrjws0mrt_LK37K9Yp0>
Subject: [P2PSIP] [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: Mon, 15 Aug 2022 07:44:30 -0000

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

v2.23.0 | Report a Bug | By Email