RFC 2881: Network Access Server Requirements Next Generation (NASREQNG) NAS Model
In plain English — editorial summary, not part of the RFC
This document describes the terminology and gives a model of typical Network Access Server (NAS). This memo provides information for the Internet community.
Document record
- Document ID
- RFC2881
- Published
- July 2000
- Authors
- D. Mitton; M. Beadles
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2882Network Access Servers Requirements: Extended RADIUS PracticesCurrent
July 2000
- RFC 2866RADIUS AccountingUpdated
June 2000
- RFC 2809Implementation of L2TP Compulsory Tunneling via RADIUSCurrent
April 2000
- RFC 2059RADIUS AccountingObsoleted
January 1997
- RFC 2869RADIUS ExtensionsUpdated
June 2000
- RFC 2868RADIUS Attributes for Tunnel Protocol SupportUpdated
June 2000
- RFC 2867RADIUS Accounting Modifications for Tunnel Protocol SupportCurrent
June 2000
- RFC 2865Remote Authentication Dial In User Service (RADIUS)Updated
June 2000
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?