Re: [radext] Ready to go? New Version Notification - draft-ietf-softwire-6rd-radius-attrib-10.txt
Alan DeKok <aland@deployingradius.com> Tue, 30 April 2013 13:27 UTC
Return-Path: <aland@deployingradius.com>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E27421F9ABE; Tue, 30 Apr 2013 06:27:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e93rnX2v4mDT; Tue, 30 Apr 2013 06:27:17 -0700 (PDT)
Received: from power.freeradius.org (power.freeradius.org [88.190.25.44]) by ietfa.amsl.com (Postfix) with ESMTP id 49A6721F9B07; Tue, 30 Apr 2013 06:27:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by power.freeradius.org (Postfix) with ESMTP id D4BC52240EBD; Tue, 30 Apr 2013 15:26:22 +0200 (CEST)
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 nzaE4kiLaDEv; Tue, 30 Apr 2013 15:26:22 +0200 (CEST)
Received: from Thor-2.local (bas1-ottawa11-1176121151.dsl.bell.ca [70.26.47.63]) by power.freeradius.org (Postfix) with ESMTPSA id 40D172240842; Tue, 30 Apr 2013 15:26:21 +0200 (CEST)
Message-ID: <517FC67C.1070502@deployingradius.com>
Date: Tue, 30 Apr 2013 09:26:20 -0400
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
References: <50F5316E.905@cisco.com>, <50F53205.2020209@cisco.com> <BLU002-W4919D9CC68A161060FD4B9932D0@phx.gbl>
In-Reply-To: <BLU002-W4919D9CC68A161060FD4B9932D0@phx.gbl>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "radext@ietf.org" <radext@ietf.org>, "aaa-doctors@ietf.org" <aaa-doctors@ietf.org>, Ralph Droms <rdroms@cisco.com>, draft-ietf-softwire-6rd-radius-attrib@ietf.org, Benoit Claise <bclaise@cisco.com>, 'RFC Editor' <rfc-editor@rfc-editor.org>
Subject: Re: [radext] Ready to go? New Version Notification - draft-ietf-softwire-6rd-radius-attrib-10.txt
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 30 Apr 2013 13:27:22 -0000
Bernard Aboba wrote: > While Section 3 now does describe how authentication/authorization > functions in a way that is compliant with RFC 2865 and 5080, there is no > normative language and the requirements (e.g. for User-Name and > User-Password attributes, Message-Authenticator attribute) are not > included in Section 4.2. Also, it would be helpful to be explicit about > the value of the Service-Type attribute in Access-Requests (I am > assuming that this is no longer "Call-Check", since the User-Password > attribute is included in the Access-Request). http://datatracker.ietf.org/doc/draft-ietf-softwire-6rd-radius-attrib/?include_text=1 The Table of Attributes in Section 4.2 lists User-Password as 0-1 for Accounting-Request. It should be just "0". RFC 2866 does not allow User-Password to be in Accounting-Request packets. Alan DeKok.
- Re: [radext] Ready to go? New Version Notificatio… Bernard Aboba
- Re: [radext] Ready to go? New Version Notificatio… Alan DeKok