[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RADEXT BOF Agenda, Take Eight
RADEXT BOF Agenda
IETF 58
Friday, November 14, 2003
0900 - 1130 AM
Chairs:
Bernard Aboba <aboba@internaut.com>
David Nelson <dnelson@enterasys.com>
Operations and Management Area Director(s):
Randy Bush <randy@psg.com>
Bert Wijnen <bwijnen@lucent.com>
Operations and Management Area Advisor:
Randy Bush <randy@psg.com>
Mailing Lists:
General Discussion: radiusext@ops.ietf.org
To Subscribe: radiusext-request@ops.ietf.org, In Body: subscribe
Archive: http://ops.ietf.org/lists/radiusext/
Agenda
Preliminaries - 5 minutes
Bluesheets
Meeting Minutes
Agenda Bashing
Basic RADIUS work
RADIUS UDP Transport Mapping - Avi Lior, 5 minutes
http://www.ietf.org/internet-drafts/draft-lior-radius-udp-transport-mapping-00.txt
IPv6 support in the RADIUS MIBs - Bert Wijnen, 5 minutes
http://www.ietf.org/rfc/rfc2618.txt
http://www.ietf.org/rfc/rfc2619.txt
http://www.ietf.org/rfc/rfc2620.txt
http://www.ietf.org/rfc/rfc2621.txt
RADIUS client kickstart - Alan DeKok, 10 minutes
http://www.ietf.org/internet-drafts/draft-moskowitz-radius-client-kickstart-01.txt
http://www.ietf.org/internet-drafts/draft-moskowitz-sspp-snmp-01.txt
RADIUS Prepaid - Avi Lior, 10 minutes
http://www.ietf.org/internet-drafts/draft-lior-radius-prepaid-extensions-02.txt
SIP-RADIUS
RADIUS Accounting & Authentication for SIP - Wolfgang Beck, 15 minutes
http://www.watersprings.org/pub/id/draft-schulzrinne-sipping-radius-accounting-00.txt
http://www.watersprings.org/pub/id/draft-sterman-aaa-sip-00.txt
LAN applications
LAN Edge Device RADIUS Attributes - Paul Congdon, 10 minutes
http://www.drizzle.com/~aboba/IEEE/draft-black-radius-lanedge-00.txt
RADIUS context relocation issues - Bernard Aboba, 10 minutes
http://www.ietf.org/internet-drafts/draft-aboba-context-802-00.txt
http://www.ietf.org/internet-drafts/draft-ietf-eap-keying-01.txt
WLAN Roaming - Farid Adrangi, 15 minutes
http://www.ietf.org/internet-drafts/draft-adrangi-radius-issues-in-pwlan-roaming-01.txt
http://www.ietf.org/internet-drafts/draft-adrangi-radius-attributes-extension-for-pwlan-00.txt
http://www.weca.net/OpenSection/downloads/WISPr_V1.0.pdf
RADIUS & PPVPNs
RADIUS & L2TP Extended NAS-Port AVPs - G. Weber, 5 minutes
http://www.ietf.org/internet-drafts/draft-nmcgill-l2tp-radius-ext-nas-port-01.txt
RADIUS in PPVPN - Greg Weber, 10 minutes
http://www.ietf.org/internet-drafts/draft-heinanen-radius-pe-discovery-04.txt
Wrapup - 20 minutes
Proposed RADIUSEXT WG Charter
Interest in forming a WG
-------------------------------------------------------------------------------
Proposed RADIUS Extensions Working Group (RADEXT) Charter
Last Modified: 2003-10-20
Chair(s):
Bernard Aboba <aboba@internaut.com>
David Nelson <dnelson@enterasys.com>
Operations and Management Area Director(s):
Randy Bush <randy@psg.com>
Bert Wijnen <bwijnen@lucent.com>
Operations and Management Area Advisor:
Randy Bush <randy@psg.com>
Mailing Lists:
General Discussion: radiusext@ops.ietf.org
To Subscribe: radiusext-request@ops.ietf.org, In Body: subscribe
Archive: http://ops.ietf.org/lists/radiusext
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.
In order to ensure backward compatibility with RADIUS, the following
restrictions are imposed on extensions considered by the RADEXT WG:
- All work MUST be backward compatible with existing RADIUS RFCs.
- No new RADIUS transports (e.g. TCP, SCTP) will be defined.
- No changes will be considered to the RADIUS attribute format.
- No new RADIUS data types will be defined.
- The RADIUS maximum packet size (4K) will not be increased.
- No RADIUS attribute "sub-types" will be defined.
- No new RADIUS security mechanisms will be defined.
Work Items
The immediate goals of the RADEXT working group are to address the
following issues:
- RADIUS UDP transport profile. The transport behavior of the RADIUS
protocol is unspecified in existing RFCs. This has resulted in
implementations lacking support for congestion control. This task
involves specification of the RADIUS UDP transport mapping. Failover
is not part of this work item. An explicit non-goal is to bring
RADIUS up to the level of reliability of Diameter.
- 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 existing RADIUS RFCs
as well as with Diameter prepaid capabilities.
- LAN attributes. New attributes have been proposed to enable use of
RADIUS authentication, authorization and accounting in wired and
wireless LANs, including Layer 2 Virtual Private LANs (VPLS).
Standardization of these attributes will enable improved
interoperability.
Goals and Milestones:
Sep 04 RADIUS UDP transport profile submitted as a Proposed Standard RFC.
Dec 04 RADIUS pre-paid suport submitted as an Informational RFC.
Apr 05 RADIUS attributes for LANs submitted as an Informational RFC.
Quality Control Plan
In order to ensure quality of work:
* This WG will not be chartered until sufficient resources can be
demonstrated to be available to guarantee a high probability of
success. This includes recruitment of a core of editors and
reviewers with significant IETF experience and demonstrated time
commitment.
* All drafts will need to undergo review prior to acceptance as WG work
items, which includes demonstration that the drafts are backward
compatible with RADIUS RFCs and are compatible with equivalent
facilities in Diameter.
* The WG will utilize an issue tracking system.
* XML to RFC will be used in production of documents. This enables
production of HTML and text files from a single source file as
well as automated production of difference files.
--
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/>