Re: [radext] [Technical Errata Reported] RFC5176 (4280)
Alan DeKok <aland@freeradius.org> Wed, 25 February 2015 14:46 UTC
Return-Path: <aland@freeradius.org>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C08661A6F2E for <radext@ietfa.amsl.com>; Wed, 25 Feb 2015 06:46:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 dTo1Bk2Shhse for <radext@ietfa.amsl.com>; Wed, 25 Feb 2015 06:46:32 -0800 (PST)
Received: from power.freeradius.org (power.freeradius.org [195.154.231.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1DB7C1A1B92 for <radext@ietf.org>; Wed, 25 Feb 2015 06:46:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by power.freeradius.org (Postfix) with ESMTP id 6C05F22403E0; Wed, 25 Feb 2015 15:46:31 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at power.freeradius.org
Received: from power.freeradius.org ([127.0.0.1]) by localhost (power.freeradius.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bDDtTbBGGVDE; Wed, 25 Feb 2015 15:46:29 +0100 (CET)
Received: from [192.168.20.59] (69-196-165-104.dsl.teksavvy.com [69.196.165.104]) by power.freeradius.org (Postfix) with ESMTPSA id 891CD22402ED; Wed, 25 Feb 2015 15:46:26 +0100 (CET)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Alan DeKok <aland@freeradius.org>
In-Reply-To: <BLUPR03MB1497BA8D4B7777E18060FD4EC160@BLUPR03MB149.namprd03.prod.outlook.com>
Date: Wed, 25 Feb 2015 09:46:24 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <9BE727B3-42D6-4C3C-84E5-398B32D2D538@freeradius.org>
References: <20150224204147.6CCC6181B3D@rfc-editor.org> <BLUPR03MB1497BA8D4B7777E18060FD4EC160@BLUPR03MB149.namprd03.prod.outlook.com>
To: Bernard Aboba <Bernard.Aboba@microsoft.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/radext/Whg-7nvB9A88RBmK8TgL5tMybXU>
X-Mailman-Approved-At: Wed, 25 Feb 2015 12:58:59 -0800
Cc: "gdommety@cisco.com" <gdommety@cisco.com>, "radext@ietf.org" <radext@ietf.org>, "lionel.morand@orange.com" <lionel.morand@orange.com>, Winter Stefan <stefan.winter@restena.lu>, "joelja@bogus.com" <joelja@bogus.com>, "david@mitton.com" <david@mitton.com>, "bclaise@cisco.com" <bclaise@cisco.com>, "meklund@cisco.com" <meklund@cisco.com>, "mchiba@cisco.com" <mchiba@cisco.com>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [radext] [Technical Errata Reported] RFC5176 (4280)
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/radext>, <mailto:radext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/radext/>
List-Post: <mailto:radext@ietf.org>
List-Help: <mailto:radext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radext>, <mailto:radext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Feb 2015 14:46:34 -0000
I agree. There should be an additional paragraph after the paragraph below, saying: ... Error-Cause MAY be included in a CoA-ACK and Disconnect-ACK packet to indicate successful actions. If it is included in those packets, the Value MUST be within the range 200-299. ... There is further discussion of CoA-ACK in the text describing the allowed VALUEs. But there should be a short sentence in the Description, too. On Feb 24, 2015, at 6:07 PM, Bernard Aboba <Bernard.Aboba@microsoft.com> wrote: > The Description text should also be addressed in this Errata: > > Description > > It is possible that a Dynamic Authorization Server cannot honor > Disconnect-Request or CoA-Request packets for some reason. The > Error-Cause Attribute provides more detail on the cause of the > problem. It MAY be included within CoA-NAK and Disconnect-NAK > packets. > > > -----Original Message----- > From: RFC Errata System [mailto:rfc-editor@rfc-editor.org] > Sent: Tuesday, February 24, 2015 12:42 PM > To: mchiba@cisco.com; gdommety@cisco.com; meklund@cisco.com; david@mitton.com; Bernard Aboba; bclaise@cisco.com; joelja@bogus.com; stefan.winter@restena.lu; lionel.morand@orange.com > Cc: aland@freeradius.org; radext@ietf.org; rfc-editor@rfc-editor.org > Subject: [Technical Errata Reported] RFC5176 (4280) > > The following errata report has been submitted for RFC5176, "Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS)". > > -------------------------------------- > You may review the report below and at: > http://www.rfc-editor.org/errata_search.php?rfc=5176&eid=4280 > > -------------------------------------- > Type: Technical > Reported by: Alan DeKok <aland@freeradius.org> > > Section: 3.6 > > Original Text > ------------- > 0 0 0+ 101 Error-Cause > > > In both tables, for CoA and Disconnect messages. > > Corrected Text > -------------- > 0 0+ 0+ 101 Error-Cause > > > In both tables, for CoA and Disconnect messages. > > Notes > ----- > Section 3.5 says that Error-Cause may be sent in a CoA-ACK or Disconnect-ACK packet: > > ... > Values 200-299 represent successful completion, so that these > values may only be sent within CoA-ACK or Disconnect-ACK packets > > 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 (IESG) can log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC5176 (draft-ietf-radext-rfc3576bis-13) > -------------------------------------- > Title : Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS) > Publication Date : January 2008 > Author(s) : M. Chiba, G. Dommety, M. Eklund, D. Mitton, B. Aboba > Category : INFORMATIONAL > Source : RADIUS EXTensions > Area : Operations and Management > Stream : IETF > Verifying Party : IESG >
- Re: [radext] [Technical Errata Reported] RFC5176 … Kathleen Moriarty
- Re: [radext] [Technical Errata Reported] RFC5176 … Stefan Winter
- Re: [radext] [Technical Errata Reported] RFC5176 … lionel.morand
- Re: [radext] [Technical Errata Reported] RFC5176 … Bernard Aboba
- [radext] [Technical Errata Reported] RFC5176 (428… RFC Errata System
- Re: [radext] [Technical Errata Reported] RFC5176 … Alan DeKok
- Re: [radext] [Technical Errata Reported] RFC5176 … Kathleen Moriarty
- Re: [radext] [Technical Errata Reported] RFC5176 … lionel.morand
- Re: [radext] [Technical Errata Reported] RFC5176 … Kathleen Moriarty
- [radext] [Errata Verified] RFC5176 (4280) RFC Errata System