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

Brian Rosen <br@brianrosen.net> Fri, 19 August 2022 13:58 UTC

Return-Path: <br@brianrosen.net>
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 2C98BC1526FC for <p2psip@ietfa.amsl.com>; Fri, 19 Aug 2022 06:58:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_PERMERROR=0.01, 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=brianrosen-net.20210112.gappssmtp.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 SIHMclIGbwEK for <p2psip@ietfa.amsl.com>; Fri, 19 Aug 2022 06:58:21 -0700 (PDT)
Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) (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 7C7B4C1526F8 for <p2psip@ietf.org>; Fri, 19 Aug 2022 06:58:21 -0700 (PDT)
Received: by mail-io1-xd2a.google.com with SMTP id o2so3340271iof.8 for <p2psip@ietf.org>; Fri, 19 Aug 2022 06:58:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20210112.gappssmtp.com; s=20210112; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc; bh=BWfTulw5hW16Ee8s5E/3feWg09ZWI2wca/xkGMGbF1M=; b=YRfpVrx1gip26yvefKjTqd2XZ3RjX0K+sl+BpS4mCZS620p8Vgic73L4SzdK8CZS/7 sUnldrLXpT73zcgtq9uy2u0s7ogaYGlPB6KQ3sDjTC9q9ewMedxlBZKirWzVWLBELJuc Oz3cHmy1LrFYz6VkR6CH7k4TGnsmcUILwAMny+PVS/fGwPXgEDwJCzX1Er+WZMI3vVng Bb8HMWiBCS/JDU06Un/qYwGqAqRiSpPYPvyMNsWdeQmkH7RfQdMDtvDNUoSPCLIqUOls LmKAXMmuzZQ4P0VM4BIvDefgLYWlCxou4UFxAnrpE42dgQk6GRVbn4wgREWYnVOWbe6+ DEkA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc; bh=BWfTulw5hW16Ee8s5E/3feWg09ZWI2wca/xkGMGbF1M=; b=oh75NQOHE9uTv1XUTSBcNHqtUqKsCtfWVN3Az0rt/5g9+nki2f0luR2me+q3H+waLC D7qbLFVLDEtn/+aKdtV7Xp+vbiLPNtyiNzS8sCLeD6Ict7DZ3A3Ob1wP8ksM5p3uXQ0y COjW/E3HC1IXpiF8nIBPekqckMIrYphTDM5WUE1QwjvoMh0vIBi4MXpj6a5DtpY9D5bU 7HBGnDyFcGS58RTA0yf7E2HpTqSbSHHS6iSVMFSMIAvf0xd4uZFqMO+E8AsGA7oKe7x3 4lElnklHCAnZQRB8qynf2/cLk9wla94PCELu7iefNGjaMH0BVexKZ/zNBve6bpCwlzct Anjg==
X-Gm-Message-State: ACgBeo1WoNkBNdAtSOP/sfjNtgY5fecubuJ0eMY5bziKsghdD7Uf+4QW +OvL1orCvjG+VeZXaOL1qlFCaA==
X-Google-Smtp-Source: AA6agR5vtexh9c2czQw4yzuhGvI3QAkHPoAATkyeZC8DoHJMU2iuXkS9P2I6is4WBXtH0C/m/ouZjA==
X-Received: by 2002:a05:6638:1652:b0:343:6e45:176c with SMTP id a18-20020a056638165200b003436e45176cmr3540349jat.251.1660917500435; Fri, 19 Aug 2022 06:58:20 -0700 (PDT)
Received: from smtpclient.apple (dynamic-acs-24-154-121-237.zoominternet.net. [24.154.121.237]) by smtp.gmail.com with ESMTPSA id x6-20020a0566022c4600b006886c4bc1a0sm2119589iov.16.2022.08.19.06.58.19 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 19 Aug 2022 06:58:20 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\))
From: Brian Rosen <br@brianrosen.net>
In-Reply-To: <acb8ff49-93f7-7f1e-55c9-114ca0b3d6ec@softarmor.com>
Date: Fri, 19 Aug 2022 09:58:18 -0400
Cc: RFC Errata System <rfc-editor@rfc-editor.org>, 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>, keepn58@gmail.com, p2psip@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <798A2A5D-C249-41B8-A203-2DF3691207C4@brianrosen.net>
References: <20220815074425.ECED34C09D@rfcpa.amsl.com> <acb8ff49-93f7-7f1e-55c9-114ca0b3d6ec@softarmor.com>
To: Dean Willis <dean.willis@softarmor.com>
X-Mailer: Apple Mail (2.3696.100.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/p2psip/-md-WCdcZgpBgt4rjbGaYu1Mx7s>
Subject: Re: [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: Fri, 19 Aug 2022 13:58:25 -0000

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
>