[P2PSIP] [Technical Errata Reported] RFC7363 (7086)
RFC Errata System <rfc-editor@rfc-editor.org> Mon, 15 August 2022 07:36 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 9AA7EC14F73D for <p2psip@ietfa.amsl.com>; Mon, 15 Aug 2022 00:36:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.659
X-Spam-Level:
X-Spam-Status: No, score=-6.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, 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 Xa6NXtiAgTqv for <p2psip@ietfa.amsl.com>; Mon, 15 Aug 2022 00:36:02 -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 C68C8C14CE3D for <p2psip@ietf.org>; Mon, 15 Aug 2022 00:36:02 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 8EF994C09D; Mon, 15 Aug 2022 00:36:02 -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: <20220815073602.8EF994C09D@rfcpa.amsl.com>
Date: Mon, 15 Aug 2022 00:36:02 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/p2psip/6K2YnRuQudbB3iY3myEbL0R2grI>
Subject: [P2PSIP] [Technical Errata Reported] RFC7363 (7086)
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:36:06 -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/eid7086 -------------------------------------- Type: Technical Reported by: Keepn <keepn58@gmail.com> Section: Global Original Text ------------- Server implementations of this specification MAY accept OAuth2.0 clients that do not implement this extension. If the "code_verifier" is not received from the client in the Authorization Request, servers supporting backwards compatibility revert to the OAuth 2.0 [RFC6749] protocol without this extension. As the OAuth 2.0 [RFC6749] server responses are unchanged by this specification, client implementations of this specification do not need to know if the server has implemented this specification or not and SHOULD send the additional parameters as defined in Section 4 to all servers. Corrected Text -------------- Server implementations of this specification MAY accept OAuth2.0 clients that do not implement this extension. If the "code_challenge" is not received from the client in the Authorization Request, servers supporting backwards compatibility revert to the OAuth 2.0 [RFC6749] protocol without this extension. As the OAuth 2.0 [RFC6749] server responses are unchanged by this specification, client implementations of this specification do not need to know if the server has implemented this specification or not and SHOULD send the additional parameters as defined in Section 4 to all servers. Notes ----- The code_verifier is not sent in the authorization request. 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] [Technical Errata Reported] RFC7363 (708… RFC Errata System