Browse Prior Art Database

Remote Authentication Dial In User Service (RADIUS) (RFC2138)

IP.com Disclosure Number: IPCOM000002693D
Original Publication Date: 1997-Apr-01
Included in the Prior Art Database: 2019-Feb-15
Document File: 65 page(s) / 72K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

C. Rigney: AUTHOR [+3]

Related Documents

10.17487/RFC2138: DOI

Abstract

This document describes a protocol for carrying authentication, authorization, and configuration information between a Network Access Server which desires to authenticate its links and a shared Authentication Server. [STANDARDS-TRACK]

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 4% of the total text.

Network Working Group C. Rigney Request for Comments: 2138 Livingston Obsoletes: 2058 A. Rubens Category: Standards Track Merit W. Simpson Daydreamer S. Willens Livingston April 1997

Remote Authentication Dial In User Service (RADIUS)

Status of this Memo

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Abstract

This document describes a protocol for carrying authentication, authorization, and configuration information between a Network Access Server which desires to authenticate its links and a shared Authentication Server.

Implementation Note

This memo documents the RADIUS protocol. There has been some confusion in the assignment of port numbers for this protocol. The early deployment of RADIUS was done using the erroneously chosen port number 1645, which conflicts with the "datametrics" service. The officially assigned port number for RADIUS is 1812.

Table of Contents

1. Introduction .......................................... 3 1.1 Specification of Requirements ................... 4 1.2 Terminology ..................................... 5 2. Operation ............................................. 5 2.1 Challenge/Response .............................. 7 2.2 Interoperation with PAP and CHAP ................ 7 2.3 Why UDP? ........................................ 8 3. Packet Format ......................................... 10 4. Packet Types .......................................... 13 4.1 Access-Request .................................. 13

Rigney, et. al. Standards Track [Page 1]

RFC 2138 RADIUS April 1997

4.2 Access-Accept ................................... 14 4.3 Access-Reject ................................... 15 4.4 Access-Challenge ................................ 17 5. Attributes ............................................ 18 5.1 User-Name ....................................... 21 5.2 User-Password ................................... 22 5.3 CHAP-Password ................................... 23 5.4 NAS-IP-Address .................................. 24 5.5 NAS-Port ........................................ 25 5.6 Service-Type .................................... 26 5.7 Framed-Protocol ................................. 28 5.8 Framed-IP-Address ............................... 29 5.9 Framed-IP-Netmask ............................... 29 5.10 Framed-Routing .................................. 30 5.11 Filter-Id ....................................... 31 5.12 Framed-MTU ...................................... 32 5.13 Framed-Compression .............................. 33 5.14 Login-IP-Host ................................... 33 5.15 Login-Service ................................... 34 5.16 Login-TCP-Port .................................. 35 5.17 (unassigned) ........

Processing...
Loading...