Authentication, Authorization and Accounting (aaa)

Authentication, Authorization and Accounting (aaa)
--------------------------------------------------

Charter
Last Modified: 2006-03-24

Current Status: Active Working Group

Chair(s):
Bernard Aboba <[email protected]>
David Mitton <[email protected]>
John Loughney <[email protected]>

Operations and Management Area Director(s):
Dan Romascanu <[email protected]>
David Kessens <[email protected]>

Operations and Management Area Advisor:
Dan Romascanu <[email protected]>

Mailing Lists:
General Discussion:[email protected]
To Subscribe: [email protected]
In Body: subscribe aaa-wg
Archive: http://www.merit.edu/mail.archives/aaa-wg/

Description of Working Group:

The Authentication, Authorization and Accounting Working Group
focused on the development of requirements for Authentication,
Authorization and Accounting as applied to network access.
Requirements were gathered from NASREQ, MOBILE IP, and ROAMOPS
Working Groups as well as TIA 45.6. The AAA WG then solicited
submission of protocols meeting the requirements, and evaluated
the submissions.

This incarnation of the AAA Working Group will focus on development
of an IETF Standards track protocol, based on the DIAMETER submission.

In this process, it is to be understood that the IETF does not function
as a rubber stamp. It is likely that the protocol will be changed
significantly during the process of development.

The immediate goals of the AAA working group are to address the
following issues:

- Clarity. The protocol documents should clearly describe the contents
of typical messages and the requirements for interoperability.

- Error messages. The protocol should define categories of error
messages, enabling implementations to respond correctly based on the
category. The set of error messages should cover the full range of
operational problems.

- Accounting. The accounting operational model should be described for
each type of network access.

- IPv6. The protocol must include attributes in support for IPv6
network access and must be transportable over IPv6.

- Transport. The protocol should be transport independent and must
define at least one mandatory-to-implement transport mapping. Other
transport mappings may also be defined. All transport mappings must
effectively support congestion control.

- Explicit proxy support. The protocol should offer explicit support
for proxies, including support for automated message routing, route
recording, and (where necessary) path hiding.

- RADIUS compatibility. The protocol should provide improved RADIUS
backward compatibility in the case where only RADIUS attributes are
used or where RADIUS proxies or servers exist in the path.

- Security. The protocol should define a lightweight data object
security model that is implementable on NASes.

- Data model. The proposal should offer logical separation between the
protocol and the data model and should support rich data types.

- MIBs. A MIB must be defined, supporting both IPv4 and IPv6 operation.

Goals and Milestones:

Done Submission of requirements document as an Informational RFC.

Done Submission of evaluation document as an Informational RFC.

Done Submission of design team recommendations on protocol
improvements.

Done Incorporation of design team recommendations into protocol
submission.

Done Submission of AAA Transport as a Proposed Standard RFC

Done Submission of Diameter Base as a Proposed Standard RFC

Done Submission of Diameter NASREQ as a Proposed Standard RFC

Done Submission of Diameter EAP as a Proposed Standard RFC

Done Submission of Diameter Credit Control as a Proposed Standard
RFC

Done Submission of Diameter SIP application as a Proposed Standard
RFC

Internet-Drafts:

No Current Internet-Drafts.

Request For Comments:

RFC Stat Published Title
------- -- ----------- ------------------------------------
RFC2924 I Sep 2000 Accounting Attributes and Record Formats

RFC2975 I Nov 2000 Introduction to Accounting Management

RFC2989 I Dec 2000 Criteria for Evaluating AAA Protocols for Network Access

RFC3127 I Jul 2001 Authentication, Authorization, and Accounting:Protocol
Evaluation

RFC3539 PS Jun 2003 Authentication, Authorization and Accounting (AAA)
Transport Profile

RFC3588 PS Sep 2003 Diameter Base Protocol

RFC4004Standard Aug 2005 Diameter Mobile IPv4 Application

RFC4005Standard Aug 2005 Diameter Network Access Server Application

RFC4006Standard Aug 2005 Diameter Credit-Control Application

RFC4072Standard Aug 2005 Diameter Extensible Authentication Protocol (EAP)
Application

RFC4740 PS Nov 2006 Diameter Session Initiation Protocol (SIP) Application