2.4.8 Network Access Server Requirements (nasreq)

NOTE: This charter is a snapshot of the 46th IETF Meeting in Washington, DC. It may now be out-of-date. Last Modified: 18-Oct-99


David Mitton <dmitton@baynetworks.com>
Mark Beadles <mbeadles@wcom.net>

Operations and Management Area Director(s):

Randy Bush <randy@psg.com>
Bert Wijnen <wijnen@vnet.ibm.com>

Operations and Management Area Advisor:

Randy Bush <randy@psg.com>


Bernard Aboba <aboba@internaut.com>

Mailing Lists:

General Discussion:nasreq@tdmx.rutgers.edu
To Subscribe: majordomo@tdmx.rutgers.edu
Archive: http://nasreq.rutgers.edu/nasreq/

Description of Working Group:

The purpose of this group is to gather and process the requirements of modern Network Access Servers (NAS) with respect to user-based service Authentication, Authorization, and usage Accounting. Services being considered go beyond simple dial-in access, and include Virtual Private Network support, smart authentication methods, and roaming concerns. The common thread is demand-based dynamic services requested within a user authentication model, viewing the NAS as a tool for implementing network policy and security.

The RADIUS protocol was developed in response to the previous incar- nation of the Network Access Servers Requirements (NASREQ) BOFs. The protocol was a simple but flexible solution to many of the require- ments in terminal and network access servers at the time. The RADIUS Working Group is about to conclude its work on the basic protocol, but NAS development continues at a rapid pace, and implementations are trying to use more standards now than when RADIUS began. As we add more services to NAS boxes, the RADIUS protocol is often stretched and bent well beyond the original design goals, and often fails to deliver the desired reliability, functionality, or security.

As NAS installations become larger and more complex, and as NAS services are virtualized in other servers, the services being authorized require more sophisticated mechanisms for coordinating policy and resource state across multiple systems and servers.

The group will work closely with other Working Groups (including roamops, pppext, policy, et al.), to serve as input for the group's requirements and to identify candidate protocols which may meet those requirements.

This group will document all of the current requirements for services which fully meet the needs of modern and next generation NAS systems.

Goals and Work items:

The first goal of the group will be to collect and organize functional requirements. The focus of the requirements will center on NAS user authorization. Functions provided adequately by other standardized protocols will be documented as such. Requirements will be generated by the members of the BOF/WG, with input from the RADIUS WG, the RoamOps WG, the AAA BOF/WG, and other groups as required. The output of this effort will be an informational requirements document.

In parallel, another document will be a survey of the current practices that NAS vendors and deployers are engaging in to provide similar services, using extensions to RADIUS or pro- prietary protocols. The output will become an informational survey document.

The group will review current draft work on RADIUS extension or successor protocols and determine their suitability to meeting the WG's requirements. The output of this effort will be an informational document detailing the evaluation and recommendations.

The charter of the group will be reviewed at that time, and adjusted according to any new work items and directions.

Goals and Milestones:

Jun 99


Submit first draft of requirements as an Internet-Draft

Jun 99


Submit first draft of practices as an Internet-Draft

Aug 99


Interim Meeting to finalize practices & requirements

Sep 99


WG Last Call on I-Ds

Oct 99


Submit practices document to IESG requesting publication as an RFC

Oct 99


Submit requirements document to IESG requesting publication as an RFC

Nov 99


Meet at DC IETF (Decide on recommendations for final document)

Dec 99


Submit review and recommendations document as an Internet-Draft

Jan 00


Review/update WG charter


No Request For Comments

Current Meeting Report

The Nasreq WG met as scheduled on Tuesday.

The group plans to advance the draft-ietf-nasreq-model-01.txt to IETF last call.
Draft-ietf-nasreq-ext-radpract-01.txt will be revised and reposted for WG last call. The draft-ietf-nasreq-criteria has undergone much discussion on the list and in the AAA WG. It will be reissued soon for WG last call in the next month. Presentations were made on the suitability of RADIUS, COPS, and Diameter against the criteria. This material will be rolled up into the group's final recommentation document by the next meeting.


None received.