RFC 2867 (rfc2867) - Page 1 of 11
RADIUS Accounting Modifications for Tunnel Protocol Support
Alternative Format: Original Text Document
Network Working Group G. Zorn
Request for Comments: 2867 Cisco Systems, Inc.
Category: Informational B. Aboba
Updates: 2866 Microsoft Corporation
D. Mitton
Nortel Networks
June 2000
RADIUS Accounting Modifications for Tunnel Protocol Support
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 defines new RADIUS accounting Attributes and new values
for the existing Acct-Status-Type Attribute [1] designed to support
the provision of compulsory tunneling in dial-up networks.
Specification of Requirements
In this document, the key words "MAY", "MUST, "MUST NOT", "optional",
"recommended", "SHOULD", and "SHOULD NOT", are to be interpreted as
described in [2].
1. Introduction
Many applications of tunneling protocols such as PPTP [5] and L2TP
[4] involve dial-up network access. Some, such as the provision of
secure access to corporate intranets via the Internet, are
characterized by voluntary tunneling: the tunnel is created at the
request of the user for a specific purpose. Other applications
involve compulsory tunneling: the tunnel is created without any
action from the user and without allowing the user any choice in the
matter, as a service of the Internet service provider (ISP).
Typically, ISPs providing a service want to collect data regarding
that service for billing, network planning, etc. One way to collect
usage data in dial-up networks is by means of RADIUS Accounting [1].
The use of RADIUS Accounting allows dial-up usage data to be
collected at a central location, rather than stored on each NAS.
Zorn, et al. Informational