Re: [P2PSIP] correction: RFC 7636 (EID 6471) - Re: [Technical Errata Reported] RFC7363 (7088)
Dean Willis <dean.willis@softarmor.com> Fri, 02 September 2022 06:48 UTC
Return-Path: <dean.willis@softarmor.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 D312AC14CE21 for <p2psip@ietfa.amsl.com>; Thu, 1 Sep 2022 23:48:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=softarmor.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 kedYdScjgGan for <p2psip@ietfa.amsl.com>; Thu, 1 Sep 2022 23:48:00 -0700 (PDT)
Received: from mail-4323.proton.ch (mail-4323.proton.ch [185.70.43.23]) (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 C3913C1522A6 for <p2psip@ietf.org>; Thu, 1 Sep 2022 23:48:00 -0700 (PDT)
Date: Fri, 02 Sep 2022 06:47:53 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=softarmor.com; s=protonmail; t=1662101277; x=1662360477; bh=XzfX5Vh7ie0F873ODqAdk9nkJv3Z9PXqxVkapTMxgm4=; h=Date:To:From:Cc:Reply-To:Subject:Message-ID:In-Reply-To: References:Feedback-ID:From:To:Cc:Date:Subject:Reply-To: Feedback-ID:Message-ID; b=5PRxRhuSApob3Ds3wS8rRboREVliXH+E+iNfAhbZlOl8Ij4yht3czbspnbHGbh+Co ep/NJHPCgxqAaUIcM9nwN02W9QRH9Sfcp5vVfYbdrpYVqUY/JDlLYSrX5y8Tg5QvBK 82fIT5sWZdPfe34A+jVzIusVeyOoqdjoDeeK3v9UM/beSGEFHbkbIaU1LnlRgcKsso RtBTZa0KTy7/N6p45qVWohNr9SZR1Mh4OvXez75tcmsi1tXfe8AP3eeIInm9vghmi5 TMXVgQlmOjwmvaayl5xD+0hYkxvvKH47B0YKYYKAZZWg6NRnbHexvdeKAYhWeg8B5U qh09I1cwDZuKw==
To: Alice Russo <arusso@amsl.com>
From: Dean Willis <dean.willis@softarmor.com>
Cc: Brian Rosen <br@brianrosen.net>, Jouni.Maenpaa@ericsson.com, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, "Murray S. Kucherawy" <superuser@gmail.com>, "Francesca Palombini francesca.palombini@ericsson.com" <francesca.palombini@ericsson.com>, CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es>, p2psip@ietf.org, RFC Editor <rfc-editor@rfc-editor.org>
Reply-To: Dean Willis <dean.willis@softarmor.com>
Message-ID: <BEC134E9-2EAE-416E-A107-A7F8B9548815@softarmor.com>
In-Reply-To: <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> <DF2FFE9F-A2CB-4564-953B-36E55DF254CE@amsl.com>
Feedback-ID: 30044069:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/p2psip/DGplqhcOZjZOVV3QKJE7F6qB-ko>
Subject: Re: [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: Fri, 02 Sep 2022 06:48:05 -0000
Thanks I guess I’m overdue for new glasses. Or bigger fonts. > On Aug 31, 2022, at 2:36 PM, Alice Russo <arusso@amsl.com> wrote: > > 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 >>> >> >
- [P2PSIP] [Technical Errata Reported] RFC7363 (708… RFC Errata System
- Re: [P2PSIP] [Technical Errata Reported] RFC7363 … Dean Willis
- Re: [P2PSIP] [Technical Errata Reported] RFC7363 … Brian Rosen
- Re: [P2PSIP] [Technical Errata Reported] RFC7363 … Dean Willis
- [P2PSIP] correction: RFC 7636 (EID 6471) - Re: [T… Alice Russo
- Re: [P2PSIP] correction: RFC 7636 (EID 6471) - Re… Dean Willis