Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Network Access Servers Requirements: Extended RADIUS Practices (RFC2882)

IP.com Disclosure Number: IPCOM000003482D
Original Publication Date: 2000-Jul-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 13 page(s) / 29K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

D. Mitton: AUTHOR

Abstract

This document describes current practices implemented in NAS products that go beyond the scope of the RADIUS RFCs 2138, 2139 [1,2]. The purpose of this effort is to give examples that show the need for addressing and standardizing these types of ad-hoc functions. Since many of these features require a matching server support component, the ability to deploy and manage interoperable NAS and AAA server products is severely hindered.

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 9% of the total text.

Network Working Group D. Mitton

Request for Comments: 2882 Nortel Networks

Category: Informational July 2000

Network Access Servers Requirements:

Extended RADIUS Practices

Status of this Memo

This memo provides information for the Internet community. It does

not specify an Internet standard of any kind. Distribution of this

memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2000). All Rights Reserved.

Abstract

This document describes current practices implemented in NAS products

that go beyond the scope of the RADIUS RFCs 2138, 2139 [1,2]. The

purpose of this effort is to give examples that show the need for

addressing and standardizing these types of ad-hoc functions. Since

many of these features require a matching server support component,

the ability to deploy and manage interoperable NAS and AAA server

products is severely hindered.

These practices are documented here to show functions that are

obviously desired in developing future AAA protocols for NAS

deployment.

Table of Contents

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 2

1.1. Disclaimers . . . . . . . . . . . . . . . . . . . . . . . 3

1.2. Presentation . . . . . . . . . . . . . . . . . . . . . . 3

2. Attribute Usage . . . . . . . . . . . . . . . . . . . . . . 3

2.1. Attribute Conflicts . . . . . . . . . . . . . . . . . . . 4

2.2. Attribute Value Conflicts . . . . . . . . . . . . . . . . 4

2.2.1 Vendor Specific Enumerations Proposal . . . . . . . . . . 4

2.3 Vendor Specific Attribute Usage . . . . . . . . . . . . . 5

2.3.1 VSAs in use by clients: . . . . . . . . . . . . . . . . . 5

2.3.2 Clients that support multiple Vendors: . . . . . . . . . 5

3. Attribute Data Types . . . . . . . . . . . . . . . . . . . 6

4. New Messages . . . . . . . . . . . . . . . . . . . . . . . 7

5. Additional Functions . . . . . . . . . . . . . . . . . . . 7

5.1 Password Change . . . . . . . . . . . . . . . . . . . . . 8

5.2 Authentication Modes . . . . . . . . . . . . . . . . . . . 8

5.3 Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

5.4 Pseudo Users . . . . . . . . . . . . . . . . . . . . . . . 9

6. Resource Management . . . . . . . . . . . . . . . . . . . . 9

6.1 Managed Resources . . . . . . . . . . . . . . . . . . . . . 9

6.2 Resource Management Messages . . . . . . . . . . . . . . . 10

6.3 Concurrent Logins . . . . . . . . . . . . . . . . . . . . . 10

...