[Pppext] [Errata Rejected] RFC2759 (6429)

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 03 August 2023 13:13 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: pppext@ietfa.amsl.com
Delivered-To: pppext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A234C16952F; Thu, 3 Aug 2023 06:13:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.865
X-Spam-Level:
X-Spam-Status: No, score=-0.865 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, 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=no 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 esMgBvyAkNMU; Thu, 3 Aug 2023 06:13:03 -0700 (PDT)
Received: from rfcpa.amsl.com (unknown [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 67C63C16952D; Thu, 3 Aug 2023 06:13:03 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 3649ECD7E7; Thu, 3 Aug 2023 06:13:03 -0700 (PDT)
To: valopaint@yahoo.com, gwz@acm.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: evyncke@cisco.com, iesg@ietf.org, pppext@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20230803131303.3649ECD7E7@rfcpa.amsl.com>
Date: Thu, 03 Aug 2023 06:13:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pppext/LN7EvuDZBYf30N3L-5UjwjVXZAE>
Subject: [Pppext] [Errata Rejected] RFC2759 (6429)
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pppext/>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Aug 2023 13:13:07 -0000

The following errata report has been rejected for RFC2759,
"Microsoft PPP CHAP Extensions, Version 2".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6429

--------------------------------------
Status: Rejected
Type: Technical

Reported by: Valentin Atanasov <valopaint@yahoo.com>
Date Reported: 2021-02-14
Rejected by: Eric Vyncke (IESG)

Section: 9.1.2.

Original Text
-------------
Authenticator authentication failure

                         <- Authenticator Challenge
       Peer Response/Challenge ->
                         <- Success/Authenticator Response

   (Authenticator Response verification fails, peer disconnects)

Corrected Text
--------------
Authenticator authentication failure

                         <- Authenticator Challenge
       Peer Response/Challenge ->
                         <- Failure/Authenticator Response

   (Authenticator Response verification fails, peer disconnects)

Notes
-----
According to section 6. Failure Packet is identical in format to the standard CHAP Failure packet, but there are different codes for success and for failure so in case of failure the returned code must be 4 thus in section 9.1.2. the line "<- Success/Authenticator Response"  the response logic should be Failure, not Succsess.
 --VERIFIER NOTES-- 
   The example is when the authenticator fails authenticate itself to the peer (i.e., it is a rogue authenticator). MS-CHAPv2 is doing piggy-backed mutual authentication.

--------------------------------------
RFC2759 (draft-ietf-pppext-mschap-v2-04)
--------------------------------------
Title               : Microsoft PPP CHAP Extensions, Version 2
Publication Date    : January 2000
Author(s)           : G. Zorn
Category            : INFORMATIONAL
Source              : Point-to-Point Protocol Extensions
Area                : Internet
Stream              : IETF
Verifying Party     : IESG