[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Strawman RADIUSEXT WG charter
Here is a proposed strawman charter for a RADIUSEXT WG. Comments welcome.
RADIUS Extensions Working Group (RADIUSEXT)
Last Modified: 2003-08-19
Bernard Aboba <email@example.com>
David Nelson <firstname.lastname@example.org>
Operations and Management Area Director(s):
Randy Bush <email@example.com>
Bert Wijnen <firstname.lastname@example.org>
Operations and Management Area Advisor:
Randy Bush <email@example.com>
General Discussion: firstname.lastname@example.org
To Subscribe: email@example.com, In Body: subscribe
Description of Working Group:
The RADIUS Extensions Working Group will focus on extensions
to the RADIUS protocol required to enable its use in applications
such as IP Telephony and Local Area Network authentication,
authorization and accounting. All extensions produced by this
working group are required to demonstrate backward compatibility with
the existing RADIUS protocol as well as compatibility with the
equivalent capabilities in the Diameter protocol. No new RADIUS commands
will be defined.
The immediate goals of the RADIUSEXT working group are to address the
- Attribute space extension. The RADIUS protocol, defined in
RFC 2865, has an eight (8) bit attribute space, a good portion
of which has already been allocated or is in use. In order to
address attribute exhaustion, an extended attribute space will be
- RADIUS UDP transport profile. The transport behavior of the RADIUS
protocol is unspecified in RFC 2865 and 2866. This has resulted in
implementations lacking support for congestion control. This task
involves specification of the RADIUS UDP transport mapping,
providing support for congestion control and jittering. Failover
behavior is not part of this work item, although it may be
considered in the future. An explicit non-goal of this work item
is to bring RADIUS up to the level of reliability achievable in
- Pre-paid support. Pre-paid services are contemplated in a number
of potential applications, including wireless LAN access and IP
telephony. In order to enable support of pre-paid services in an
interoperable way, a specification is required. The implementation of
RADIUS prepaid needs to be compatible with RFC 2865 and 2866,
as well as with Diameter prepaid capabilities.
- LAN attributes. A number of additional attributes have been
proposed to enable use of RADIUS authentication, authorization and
accounting in wired and wireless LANs. Standardization of these
attributes will enable improved interoperability.
Goals and Milestones:
Apr 04 RADIUS attribute space extension submitted as a Proposed Standard RFC.
Apr 04 RADIUS UDP transport profile submitted as a Proposed Standard RFC.
Sep 04 RADIUS pre-paid suport submitted as an Informational RFC.
Dec 04 RADIUS attributes for LANs submitted as an Informational RFC.
to unsubscribe send a message to firstname.lastname@example.org with
the word 'unsubscribe' in a single line as the message text body.