[Technical Errata Reported] RFC5997 (2507)
RFC Errata System <rfc-editor@rfc-editor.org> Wed, 01 September 2010 19:28 UTC
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4872F3A696A for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 1 Sep 2010 12:28:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.335
X-Spam-Level:
X-Spam-Status: No, score=-102.335 tagged_above=-999 required=5 tests=[AWL=0.265, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ETn4YluVySUi for <ietfarch-radext-archive-IeZ9sae2@core3.amsl.com>; Wed, 1 Sep 2010 12:28:26 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id D0BC03A6910 for <radext-archive-IeZ9sae2@lists.ietf.org>; Wed, 1 Sep 2010 12:28:25 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1Oqsuq-000JbR-QK for radiusext-data0@psg.com; Wed, 01 Sep 2010 19:24:12 +0000
Received: from rfc-editor.org ([2001:1890:1112:1::2f]) by psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <wwwrun@rfc-editor.org>) id 1Oqsuj-000JaK-Uz for radiusext@ops.ietf.org; Wed, 01 Sep 2010 19:24:06 +0000
Received: by rfc-editor.org (Postfix, from userid 30) id D1E41E06C6; Wed, 1 Sep 2010 12:24:04 -0700 (PDT)
To: aland@freeradius.org, dromasca@avaya.com, rbonica@juniper.net, Bernard_Aboba@hotmail.com, mauricio.sanchez@hp.com
Subject: [Technical Errata Reported] RFC5997 (2507)
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: ah@TR-Sys.de, radiusext@ops.ietf.org, rfc-editor@rfc-editor.org
Message-Id: <20100901192404.D1E41E06C6@rfc-editor.org>
Date: Wed, 01 Sep 2010 12:24:04 -0700
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>
The following errata report has been submitted for RFC5997, "Use of Status-Server Packets in the Remote Authentication Dial In User Service (RADIUS) Protocol". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5997&eid=2507 -------------------------------------- Type: Technical Reported by: Alfred Hoenes <ah@TR-Sys.de> Section: 3, pg.9 Original Text ------------- [[ last paragraph on page 9 (extending to page 10): ]] | The Access-Accept MAY contain a Reply-Message or Message- Authenticator attribute. It SHOULD NOT contain other attributes. The Accounting-Response packets sent in response to a Status-Server query SHOULD NOT contain any attributes. [...] Corrected Text -------------- | The Access-Accept sent in response to a Status-Server query MAY contain a Reply-Message or Message-Authenticator attribute. It SHOULD NOT contain other attributes. The Accounting-Response packets sent in response to a Status-Server query SHOULD NOT contain any attributes. [...] Notes ----- Rationale: Bare "Access-Accept" is potentially misleading. The clause needed to properly restrict the scope of the sentence has been added in most similar instances of specification text in the RFC, but that has been missed here. So for consistency and clarity, the New text once more provides this additional clause -- as it already appears in the 3rd sentence of this paragraph. Instructions: ------------- This errata 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 (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC5997 (draft-ietf-radext-status-server-09) -------------------------------------- Title : Use of Status-Server Packets in the Remote Authentication Dial In User Service (RADIUS) Protocol Publication Date : August 2010 Author(s) : A. DeKok Category : INFORMATIONAL Source : RADIUS EXTensions Area : Operations and Management Stream : IETF Verifying Party : IESG -- to unsubscribe send a message to radiusext-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: <http://psg.com/lists/radiusext/>
- [Technical Errata Reported] RFC5997 (2507) RFC Errata System