RE: Authorization for AAA and RADIUS work items
"Roy, Radhika R, ALABS" <rrroy@att.com> Sun, 04 January 2004 18:28 UTC
Envelope-to: radiusext-data@psg.com
Delivery-date: Sun, 04 Jan 2004 18:29:21 +0000
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Authorization for AAA and RADIUS work items
Date: Sun, 04 Jan 2004 13:28:47 -0500
Message-ID: <34DA635B184A644DA4588E260EC0A25A05D9E34F@ACCLUST02EVS1.ugd.att.com>
Thread-Topic: Authorization for AAA and RADIUS work items
Thread-Index: AcPS6E8mhzFaanC4S06cBF4K2719LQAByXLQ
From: "Roy, Radhika R, ALABS" <rrroy@att.com>
To: Bernard Aboba <aboba@internaut.com>, radiusext@ops.ietf.org
Hi, Bernard: I agree that AAA/RADIUS/DIAMETER server MUST not signal QoS. It is also clear that authentication is also NOT directly related to QoS. However, you have agreed that "accounting" has implications on QoS. I also believe that "authorization" may/will also have implications QoS as John also mentioned. So, we have bounded the problems how far we should go for standardization of QoS attributes for the AAA/RADIUS/DIAMETER server. So, is it possible to provide clear guidance what we should do in addressing the QoS attributes? Radhika -----Original Message----- From: Bernard Aboba [mailto:aboba@internaut.com] Sent: Sunday, January 04, 2004 12:44 PM To: radiusext@ops.ietf.org Subject: Authorization for AAA and RADIUS work items In order to make sure that AAA-related WGs stay in sync with other WGs and SDOs, there is a requirement that AAA-related work items be authorized by a requirements document. Here are some of the AAA requirements documents that have been approved for publication as RFCs: draft-ietf-sipping-aaa-req-04.txt RFC 3141 RFC 2989 RFC 2977 RFC 2881 RFC 2477 Nowhere in these documents is there any mention of AAA requirements for signaled QoS. In the NSIS requirements document (draft-ietf-nsis-req-09.txt) there is a requirement 5.9.4 that mentions AAA: "The NSIS SHOULD be developed with respect to be able to collect usage records from one or more network elements. " However this seems to only relate to accounting, not authentication and authorized of signaled QoS. It would therefore appear to me that use of AAA for signaled QoS has not been authorized by a requirements document, and therefore cannot become a RADEXT (or even AAA) WG work item. -- 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/> -- 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/>
- RE: Authorization for AAA and RADIUS work items john.loughney
- RE: Authorization for AAA and RADIUS work items Roy, Radhika R, ALABS
- Authorization for AAA and RADIUS work items Bernard Aboba