[Pppext] [Technical Errata Reported] RFC2759 (6429)

RFC Errata System <rfc-editor@rfc-editor.org> Sun, 14 February 2021 07:12 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 C14AF3A15AA for <pppext@ietfa.amsl.com>; Sat, 13 Feb 2021 23:12:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level:
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AjYSx6bY3Yer for <pppext@ietfa.amsl.com>; Sat, 13 Feb 2021 23:12:23 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1A543A15A9 for <pppext@ietf.org>; Sat, 13 Feb 2021 23:12:23 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id DF345F40755; Sat, 13 Feb 2021 23:12:22 -0800 (PST)
To: gwz@acm.org, ek.ietf@gmail.com, evyncke@cisco.com, d3e3e3@gmail.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: valopaint@yahoo.com, pppext@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20210214071222.DF345F40755@rfc-editor.org>
Date: Sat, 13 Feb 2021 23:12:22 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pppext/Un8gsg0swk1Gq4v3FZBjLDxjUOs>
Subject: [Pppext] [Technical Errata Reported] RFC2759 (6429)
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 14 Feb 2021 07:12:25 -0000

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

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

--------------------------------------
Type: Technical
Reported by: Valentin Atanasov <valopaint@yahoo.com>

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.

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. 

--------------------------------------
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