xflag账号的密码怎么改_百度知道
xflag账号的密码怎么改
我有更好的答案
看你的是发文件的还是收文件的。如果是发文件的就点击发文件，相反则是一样的。选择你手机QQ的版本1.手机传电脑。手机上登录手机QQ同时电脑上也要登录同一个QQ -然后点击我的设备-电脑 把你要传的传过去2面对面（只能手机对手机）进入我的文件以后就可以看到面对面快传（0流量）点击进入。这里非常重要。正在传你想传输的文件，传输到对方的手机上的提示和这个也差不多。只是提示的是接收到的文件，视频，音乐等等这样的文件，选中它再点击发送就可以了。开启了以后就会自动描得到。描扫到了点击它的头像就可以开始传文件了。选择你要传过去的文件或是图片。（安卓还是其他的）手机正在等待附近好友的手机QQ开启面对面接收功能
为您推荐：
其他类似问题
换一换
回答问题，赢新手礼包
个人、企业类
违法有害信息,请在下方选择后提交
色情、暴力
我们会通过消息、邮箱等方式尽快将举报结果通知您。Network Working Group
P. Calhoun
Request for Comments: 4005
Category: Standards Track
Cisco Systems Inc.
Consultant
Circular Networks
August 2005
Diameter Network Access Server Application
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.
Copyright Notice
Copyright (C) The Internet Society (2005).
This document describes the Diameter protocol application used for
Authentication, Authorization, and Accounting (AAA) services in the
Network Access Server (NAS) environment.
When combined with the
Diameter Base protocol, Transport Profile, and Extensible
Authentication Protocol specifications, this application
specification satisfies typical network access services requirements.
Initial deployments of the Diameter protocol are expected to include
legacy systems.
Therefore, this application has been carefully
designed to ease the burden of protocol conversion between RADIUS and
This is achieved by including the RADIUS attribute space
to eliminate the need to perform many attribute translations.
The interactions between Diameter applications and RADIUS specified
in this document are to be applied to all Diameter applications.
this sense, this document extends the Base Diameter protocol.
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
Table of Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . .
Terminology
. . . . . . . . . . . . . . . . . . . . . .
Requirements Language
. . . . . . . . . . . . . . . . .
Advertising Application Support
. . . . . . . . . . . .
NAS Calls, Ports, and Sessions . . . . . . . . . . . . . . . .
Diameter Session Establishment . . . . . . . . . . . . .
Diameter Session Reauthentication or Reauthorization . .
Diameter Session Termination . . . . . . . . . . . . . .
NAS Messages . . . . . . . . . . . . . . . . . . . . . . . . .
AA-Request (AAR) Command . . . . . . . . . . . . . . . .
AA-Answer (AAA) Command
. . . . . . . . . . . . . . . . 11
Re-Auth-Request (RAR) Command
. . . . . . . . . . . . . 13
Re-Auth-Answer (RAA) Command . . . . . . . . . . . . . . 14
Session-Termination-Request (STR) Command
. . . . . . . 15
Session-Termination-Answer (STA) Command . . . . . . . . 15
Abort-Session-Request (ASR) Command
. . . . . . . . . . 16
Abort-Session-Answer (ASA) Command . . . . . . . . . . . 17
Accounting-Request (ACR) Command . . . . . . . . . . . . 17
3.10. Accounting-Answer (ACA) Command. . . . . . . . . . . . . 19
NAS Session AVPs . . . . . . . . . . . . . . . . . . . . . . . 20
Call and Session Information . . . . . . . . . . . . . . 21
NAS-Port AVP . . . . . . . . . . . . . . . . . . . . . . 22
NAS-Port-Id AVP
. . . . . . . . . . . . . . . . . . . . 22
NAS-Port-Type AVP
. . . . . . . . . . . . . . . . . . . 22
Called-Station-Id AVP
. . . . . . . . . . . . . . . . . 23
Calling-Station-Id AVP . . . . . . . . . . . . . . . . . 23
Connect-Info AVP . . . . . . . . . . . . . . . . . . . . 24
Originating-Line-Info AVP
. . . . . . . . . . . . . . . 24
Reply-Message AVP
. . . . . . . . . . . . . . . . . . . 25
NAS Authentication AVPs
. . . . . . . . . . . . . . . . . . . 26
User-Password AVP
. . . . . . . . . . . . . . . . . . . 26
Password-Retry AVP . . . . . . . . . . . . . . . . . . . 27
Prompt AVP . . . . . . . . . . . . . . . . . . . . . . . 27
CHAP-Auth AVP
. . . . . . . . . . . . . . . . . . . . . 27
CHAP-Algorithm AVP . . . . . . . . . . . . . . . . . . . 28
CHAP-Ident AVP . . . . . . . . . . . . . . . . . . . . . 28
CHAP-Response AVP
. . . . . . . . . . . . . . . . . . . 28
CHAP-Challenge AVP . . . . . . . . . . . . . . . . . . . 28
ARAP-Password AVP
. . . . . . . . . . . . . . . . . . . 28
5.10. ARAP-Challenge-Response AVP. . . . . . . . . . . . . . . 28
5.11. ARAP-Security AVP. . . . . . . . . . . . . . . . . . . . 29
5.12. ARAP-Security-Data AVP . . . . . . . . . . . . . . . . . 29
NAS Authorization AVPs . . . . . . . . . . . . . . . . . . . . 29
Service-Type AVP . . . . . . . . . . . . . . . . . . . . 30
Callback-Number AVP
. . . . . . . . . . . . . . . . . . 32
Callback-Id AVP
. . . . . . . . . . . . . . . . . . . . 32
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
Idle-Timeout AVP . . . . . . . . . . . . . . . . . . . . 32
Port-Limit AVP . . . . . . . . . . . . . . . . . . . . . 32
NAS-Filter-Rule AVP
. . . . . . . . . . . . . . . . . . 32
Filter-Id AVP
. . . . . . . . . . . . . . . . . . . . . 33
Configuration-Token AVP
. . . . . . . . . . . . . . . . 33
QoS-Filter-Rule AVP
. . . . . . . . . . . . . . . . . . 33
6.10. Framed Access Authorization AVPs . . . . . . . . . . . . 35
Framed-Protocol AVP . . . . . . . . . . . . . . 35
Framed-Routing AVP. . . . . . . . . . . . . . . 35
Framed-MTU AVP. . . . . . . . . . . . . . . . . 35
Framed-Compression AVP. . . . . . . . . . . . . 36
6.11. IP Access Authorization AVPs.. . . . . . . . . . . . . . 36
Framed-IP-Address AVP . . . . . . . . . . . . . 36
Framed-IP-Netmask AVP . . . . . . . . . . . . . 36
Framed-Route AVP. . . . . . . . . . . . . . . . 37
Framed-Pool AVP . . . . . . . . . . . . . . . . 37
Framed-Interface-Id AVP . . . . . . . . . . . . 37
Framed-IPv6-Prefix AVP. . . . . . . . . . . . . 38
Framed-IPv6-Route AVP . . . . . . . . . . . . . 38
Framed-IPv6-Pool AVP. . . . . . . . . . . . . . 38
6.12. IPX Access . . . . . . . . . . . . . . . . . . . . . . . 38
Framed-IPX-Network AVP. . . . . . . . . . . . . 39
6.13. AppleTalk Network Access . . . . . . . . . . . . . . . . 39
Framed-AppleTalk-Link AVP . . . . . . . . . . . 39
Framed-AppleTalk-Network AVP . . . . . . . . .
Framed-AppleTalk-Zone AVP . . . . . . . . . . . 40
6.14. AppleTalk Remote Access. . . . . . . . . . . . . . . . . 40
ARAP-Features AVP . . . . . . . . . . . . . . . 40
ARAP-Zone-Access AVP. . . . . . . . . . . . . . 40
6.15. Non-Framed Access Authorization AVPs . . . . . . . . . . 40
Login-IP-Host AVP . . . . . . . . . . . . . . . 40
Login-IPv6-Host AVP . . . . . . . . . . . . . . 41
Login-Service AVP . . . . . . . . . . . . . . . 41
6.16. TCP Services . . . . . . . . . . . . . . . . . . . . . . 42
Login-TCP-Port AVP . . . . . . . . . . . . . .
6.17. LAT Services . . . . . . . . . . . . . . . . . . . . . . 42
Login-LAT-Service AVP . . . . . . . . . . . . . 42
Login-LAT-Node AVP. . . . . . . . . . . . . . . 43
Login-LAT-Group AVP . . . . . . . . . . . . . . 43
Login-LAT-Port AVP. . . . . . . . . . . . . . . 43
NAS Tunneling
. . . . . . . . . . . . . . . . . . . . . . . . 44
Tunneling AVP
. . . . . . . . . . . . . . . . . . . . . 44
Tunnel-Type AVP
. . . . . . . . . . . . . . . . . . . . 45
Tunnel-Medium-Type AVP . . . . . . . . . . . . . . . . . 46
Tunnel-Client-Endpoint AVP . . . . . . . . . . . . . . . 46
Tunnel-Server-Endpoint AVP . . . . . . . . . . . . . . . 47
Tunnel-Password AVP
. . . . . . . . . . . . . . . . . . 48
Tunnel-Private-Group-Id AVP
. . . . . . . . . . . . . . 48
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
Tunnel-Assignment-Id AVP . . . . . . . . . . . . . . . . 48
Tunnel-Preference AVP
. . . . . . . . . . . . . . . . . 49
7.10. Tunnel-Client-Auth-Id AVP. . . . . . . . . . . . . . . . 50
7.11. Tunnel-Server-Auth-Id AVP. . . . . . . . . . . . . . . . 50
NAS Accounting . . . . . . . . . . . . . . . . . . . . . . . . 50
Accounting-Input-Octets AVP
. . . . . . . . . . . . . . 51
Accounting-Output-Octets AVP . . . . . . . . . . . . . . 52
Accounting-Input-Packets AVP . . . . . . . . . . . . . . 52
Accounting-Output-Packets AVP
. . . . . . . . . . . . . 52
Acct-Session-Time AVP
. . . . . . . . . . . . . . . . . 52
Acct-Authentic AVP . . . . . . . . . . . . . . . . . . . 52
Accounting-Auth-Method AVP . . . . . . . . . . . . . . . 53
Acct-Delay-Time
. . . . . . . . . . . . . . . . . . . . 53
Acct-Link-Count
. . . . . . . . . . . . . . . . . . . . 54
8.10. Acct-Tunnel-Connection AVP . . . . . . . . . . . . . . . 54
8.11. Acct-Tunnel-Packets-Lost AVP . . . . . . . . . . . . . . 55
RADIUS/Diameter Protocol Interactions
. . . . . . . . . . . . 55
RADIUS Request Forwarded as Diameter Request . . . . . . 55
RADIUS Dynamic Authorization Considerations . . 59
Diameter Request Forwarded as RADIUS Request . . . . . . 60
RADIUS Dynamic Authorization Considerations . . 62
AVPs Used Only for Compatibility . . . . . . . . . . . . 63
NAS-Identifier AVP. . . . . . . . . . . . . . . 63
NAS-IP-Address AVP. . . . . . . . . . . . . . . 64
NAS-IPv6-Address AVP. . . . . . . . . . . . . . 65
State AVP . . . . . . . . . . . . . . . . . . . 65
Termination-Cause AVP Code Values . . . . . . . 66
Origin-AAA-Protocol . . . . . . . . . . . . . . 68
Prohibited RADIUS Attributes . . . . . . . . . . . . . . 69
Translatable Diameter AVPs . . . . . . . . . . . . . . . 69
RADIUS Vendor-Specific Attributes
. . . . . . . . . . . 69
Forwarding a Diameter Vendor Specific AVP as a
RADIUS VSA . . . . . . . . . . . . . . . . . . . 70
Forwarding a RADIUS VSA as a Diameter Vendor
Specific AVP . . . . . . . . . . . . . . . . . . 70
10. AVP Occurrence Tables. . . . . . . . . . . . . . . . . . . . . 71
10.1. AA-Request/Answer AVP Table. . . . . . . . . . . . . . . 71
10.2. Accounting AVP Tables. . . . . . . . . . . . . . . . . . 73
Accounting Framed Access AVP Table. . . . . . . 74
Accounting Non-Framed Access AVP Table. . . . . 76
11. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 77
11.1. Command Codes. . . . . . . . . . . . . . . . . . . . . . 77
11.2. AVP Codes. . . . . . . . . . . . . . . . . . . . . . . . 78
11.3. Application Identifier . . . . . . . . . . . . . . . . . 78
11.4. CHAP-Algorithm AVP Values. . . . . . . . . . . . . . . . 78
11.5. Accounting-Auth-Method AVP Values. . . . . . . . . . . . 78
11.6. Origin-AAA-Protocol AVP Values . . . . . . . . . . . . . 78
12. Security Considerations. . . . . . . . . . . . . . . . . . . . 78
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 79
13.1. Normative References . . . . . . . . . . . . . . . . . . 79
13.2. Informative References . . . . . . . . . . . . . . . . . 80
14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 83
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 84
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 85
Introduction
This document describes the Diameter protocol application used for
AAA in the Network Access Server (NAS) environment.
When combined
with the Diameter Base protocol [BASE], Transport Profile
[DiamTrans], and EAP [DiamEAP] specifications, this Diameter NAS
application specification satisfies NAS-related requirements defined
in RFC 2989 [AAACriteria] and RFC 3169 [NASCriteria].
Initial deployments of the Diameter protocol are expected to include
legacy systems.
Therefore, this application has been carefully
designed to ease the burden of protocol conversion between RADIUS and
This is achieved by including the RADIUS attribute space
to eliminate the need to perform many attribute translations.
The interactions specified in this document between Diameter
applications and RADIUS are to be applied to all Diameter
applications.
In this sense, this document extends the Base Diameter
protocol [BASE].
First, this document describes the operation of a Diameter NAS
application.
Then it defines the Diameter message Command-Codes.
The following sections list the AVPs used in these messages, grouped
by common usage.
These are session identification, authentication,
authorization, tunneling, and accounting.
The authorization AVPs are
further broken down by service type.
Interaction and backward
compatibility issues with RADIUS are discussed in later sections.
Terminology
The base Diameter [BASE] specification section 1.4 defines most of
the terminology used in this document.
Additionally, the following
terms and acronyms are used in this application:
NAS (Network Access Server) - A device that provides an access
service for a user to a network.
The service may be a network
connection or a value-added service such as terminal emulation
[NASModel].
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
PPP (Point-to-Point Protocol) - A multiprotocol serial datalink.
is the primary IP datalink used for dial-in NAS connection service
CHAP (Challenge Handshake Authentication Protocol) - An
authentication process used in PPP [PPPCHAP].
PAP (Password Authentication Protocol) - A deprecated PPP
authentication process, but often used for backward compatibility
SLIP (Serial Line Interface Protocol) - A serial datalink that only
supports IP.
A design prior to PPP.
ARAP (Appletalk Remote Access Protocol) - A serial datalink for
accessing Appletalk networks [ARAP].
IPX (Internet Packet Exchange) - The network protocol used by NetWare
networks [IPX].
LAT (Local Area Transport) - A Digital Equipment Corp. LAN protocol
for terminal services [LAT].
VPN (Virtual Private Network) - In this document, this term is used
to describe access services that use tunneling methods.
Requirements Language
In this document, the key words "MAY", "MUST", "MUST NOT",
"OPTIONAL", "RECOMMENDED", "SHOULD", and "SHOULD NOT" are to be
interpreted as described in [Keywords].
Advertising Application Support
Diameter applications conforming to this specification MUST advertise
support by including the value of one (1) in the Auth-Application-Id
of Capabilities-Exchange-Request (CER), AA-Request (AAR), and AA-
Answer (AAA) messages.
All other messages are defined by [BASE] and
use the Base application id value.
NAS Calls, Ports, and Sessions
The arrival of a new call or service connection at a port of a
Network Access Server (NAS) starts a Diameter NAS message exchange.
Information about the call, the identity of the user, and the user's
authentication information are packaged into a Diameter AA-Request
(AAR) message and sent to a server.
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
The server processes the information and responds with a Diameter
AA-Answer (AAA) message that contains authorization information for
the NAS, or a failure code (Result-Code AVP).
A value of
DIAMETER_MULTI_ROUND_AUTH indicates an additional authentication
exchange, and several AAR and AAA messages may be exchanged until the
transaction completes.
Depending on the Auth-Request-Type AVP, the Diameter protocol allows
authorization-only requests that contain no authentication
information from the client.
This capability goes beyond the Call
Check capabilities described in section 5.6 of [RADIUS] in that no
access decision is requested.
As a result, service cannot be started
as a result of a response to an authorization-only request without
introducing a significant security vulnerability.
Since no equivalent capability exists in RADIUS, authorization-only
requests from a NAS implementing Diameter may not be easily
translated to an equivalent RADIUS message by a Diameter/RADIUS
For example, when a Diameter authorization-only request
cannot be translated to a RADIUS Call Check, it would be necessary
for the Diameter/RADIUS gateway to add authentication information to
the RADIUS Access Request.
On receiving the Access-Reply, the
Diameter/RADIUS gateway would need to discard the access decision
(Accept/Reject).
It is not clear whether these translations can be
accomplished without adding significant security vulnerabilities.
Diameter Session Establishment
When the authentication or authorization exchange completes
successfully, the NAS application SHOULD start a session context.
the Result-Code of DIAMETER_MULTI_ROUND_AUTH is returned, the
exchange continues until a success or error is returned.
If accounting is active, the application MUST also send an Accounting
message [BASE].
An Accounting-Record-Type of START_RECORD is sent
for a new session.
If a session fails to start, the EVENT_RECORD
message is sent with the reason for the failure described.
Note that the return of an unsupportable Accounting-Realtime-Required
value [BASE] would result in a failure to establish the session.
Diameter Session Reauthentication or Reauthorization
The Diameter Base protocol allows users to be periodically
reauthenticated and/or reauthorized.
In such instances, the
Session-Id AVP in the AAR message MUST be the same as the one present
in the original authentication/authorization message.
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
A Diameter server informs the NAS of the maximum time allowed before
reauthentication or reauthorization via the Authorization-Lifetime
AVP [BASE].
A NAS MAY reauthenticate and/or reauthorize before the
end, but A NAS MUST reauthenticate and/or reauthorize at the end of
the period provided by the Authorization-Lifetime AVP.
The failure
of a reauthentication exchange will terminate the service.
Furthermore, it is possible for Diameter servers to issue an
unsolicited reauthentication and/or reauthorization request (e.g.,
Re-Auth-Request (RAR) message [BASE]) to the NAS.
Upon receipt of
such a message, the NAS MUST respond to the request with a Re-Auth-
Answer (RAA) message [BASE].
If the RAR properly identifies an active session, the NAS will
initiate a new local reauthentication or authorization sequence as
indicated by the Re-Auth-Request-Type value.
This will cause the NAS
to send a new AAR message using the existing Session-Id.
The server
will respond with an AAA message to specify the new service
parameters.
If accounting is active, every change of authentication or
authorization SHOULD generate an accounting message.
If the NAS
service is a continuation of the prior user context, then an
Accounting-Record-Type of INTERIM_RECORD indicating the new session
attributes and cumulative status would be appropriate.
If a new user
or a significant change in authorization is detected by the NAS, then
the service may send two messages of the types STOP_RECORD and
START_RECORD.
Accounting may change the subsession identifiers
(Acct-Session-ID, or Acct-Sub-Session-Id) to indicate such sub-
A service may also use a different Session-Id value for
accounting (see [BASE] section 9.6).
However, the Diameter Session-ID AVP value used for the initial
authorization exchange MUST be used to generate an STR message when
the session context is terminated.
Diameter Session Termination
When a NAS receives an indication that a user's session is being
disconnected by the client (e.g., LCP Terminate is received) or an
administrative command, the NAS MUST issue a Session-Termination-
Request (STR) [BASE] to its Diameter Server.
This will ensure that
any resources maintained on the servers are freed appropriately.
Furthermore, a NAS that receives an Abort-Session-Request (ASR)
[BASE] MUST issue an ASA if the session identified is active and
disconnect the PPP (or tunneling) session.
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
If accounting is active, an Accounting STOP_RECORD message [BASE]
MUST be sent upon termination of the session context.
More information on Diameter Session Termination is included in
[BASE] sections 8.4 and 8.5.
NAS Messages
This section defines the Diameter message Command-Code [BASE] values
that MUST be supported by all Diameter implementations conforming to
this specification.
The Command Codes are as follows:
Command-Name
-------------------------------------------------------
AA-Request
Re-Auth-Request
Re-Auth-Answer
Session-Termination-Request
Session-Termination-Answer
Abort-Session-Request
Abort-Session-Answer
Accounting-Request
Accounting-Answer
AA-Request (AAR) Command
The AA-Request (AAR), which is indicated by setting the Command-Code
field to 265 and the 'R' bit in the Command Flags field, is used to
request authentication and/or authorization for a given NAS user.
The type of request is identified through the Auth-Request-Type AVP
The recommended value for most RADIUS interoperabily
situations is AUTHORIZE_AUTHENTICATE.
If Authentication is requested, the User-Name attribute SHOULD be
present, as well as any additional authentication AVPs that would
carry the password information.
A request for authorization SHOULD
only include the information from which the authorization will be
performed, such as the User-Name, Called-Station-Id, or Calling-
Station-Id AVPs.
All requests SHOULD contain AVPs uniquely
identifying the source of the call, such as Origin-Host and NAS-Port.
Certain networks MAY use different AVPs for authorization purposes.
A request for authorization will include some AVPs defined in section
It is possible for a single session to be authorized first and then
for an authentication request to follow.
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
This AA-Request message MAY be the result of a multi-round
authentication exchange, which occurs when the AA-Answer message is
received with the Result-Code AVP set to DIAMETER_MULTI_ROUND_AUTH.
A subsequent AAR message SHOULD be sent, with the User-Password AVP
that includes the user's response to the prompt, and MUST include any
State AVPs that were present in the AAA message.
Message Format
{ Auth-Application-Id }
{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
{ Auth-Request-Type }
[ Destination-Host ]
[ NAS-Identifier ]
[ NAS-IP-Address ]
[ NAS-IPv6-Address ]
[ NAS-Port ]
[ NAS-Port-Id ]
[ NAS-Port-Type ]
[ Origin-AAA-Protocol ]
[ Origin-State-Id ]
[ Port-Limit ]
[ User-Name ]
[ User-Password ]
[ Service-Type ]
[ Authorization-Lifetime ]
[ Auth-Grace-Period ]
[ Auth-Session-State ]
[ Callback-Number ]
[ Called-Station-Id ]
[ Calling-Station-Id ]
[ Originating-Line-Info ]
[ Connect-Info ]
[ CHAP-Auth ]
[ CHAP-Challenge ]
* [ Framed-Compression ]
[ Framed-Interface-Id ]
[ Framed-IP-Address ]
* [ Framed-IPv6-Prefix ]
[ Framed-IP-Netmask ]
[ Framed-MTU ]
[ Framed-Protocol ]
[ ARAP-Password ]
[ ARAP-Security ]
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
* [ ARAP-Security-Data ]
* [ Login-IP-Host ]
* [ Login-IPv6-Host ]
[ Login-LAT-Group ]
[ Login-LAT-Node ]
[ Login-LAT-Port ]
[ Login-LAT-Service ]
* [ Tunneling ]
* [ Proxy-Info ]
* [ Route-Record ]
AA-Answer (AAA) Command
The AA-Answer (AAA) message is indicated by setting the Command-Code
field to 265 and clearing the 'R' bit in the Command Flags field.
is sent in response to the AA-Request (AAR) message.
authorization was requested, a successful response will include the
authorization AVPs appropriate for the service being provided, as
defined in section 6.
For authentication exchanges requiring more than a single round trip,
the server MUST set the Result-Code AVP to DIAMETER_MULTI_ROUND_AUTH.
An AAA message with this result code MAY include one Reply-Message or
more and MAY include zero or one State AVPs.
If the Reply-Message AVP was present, the network access server
SHOULD send the text to the user's client to display to the user,
instructing the client to prompt the user for a response.
example, this capability can be achieved in PPP via PAP.
access client is unable to prompt the user for a new response, it
MUST treat the AA-Answer (AAA) with the Reply-Message AVP as an error
and deny access.
Message Format
{ Auth-Application-Id }
{ Auth-Request-Type }
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ User-Name ]
[ Service-Type ]
* [ Class ]
* [ Configuration-Token ]
[ Acct-Interim-Interval ]
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
[ Error-Message ]
[ Error-Reporting-Host ]
* [ Failed-AVP ]
[ Idle-Timeout ]
[ Authorization-Lifetime ]
[ Auth-Grace-Period ]
[ Auth-Session-State ]
[ Re-Auth-Request-Type ]
[ Multi-Round-Time-Out ]
[ Session-Timeout ]
* [ Reply-Message ]
[ Origin-AAA-Protocol ]
[ Origin-State-Id ]
* [ Filter-Id ]
[ Password-Retry ]
[ Port-Limit ]
[ Prompt ]
[ ARAP-Challenge-Response ]
[ ARAP-Features ]
[ ARAP-Security ]
* [ ARAP-Security-Data ]
[ ARAP-Zone-Access ]
[ Callback-Id ]
[ Callback-Number ]
[ Framed-Appletalk-Link ]
* [ Framed-Appletalk-Network ]
[ Framed-Appletalk-Zone ]
* [ Framed-Compression ]
[ Framed-Interface-Id ]
[ Framed-IP-Address ]
* [ Framed-IPv6-Prefix ]
[ Framed-IPv6-Pool ]
* [ Framed-IPv6-Route ]
[ Framed-IP-Netmask ]
* [ Framed-Route ]
[ Framed-Pool ]
[ Framed-IPX-Network ]
[ Framed-MTU ]
[ Framed-Protocol ]
[ Framed-Routing ]
* [ Login-IP-Host ]
* [ Login-IPv6-Host ]
[ Login-LAT-Group ]
[ Login-LAT-Node ]
[ Login-LAT-Port ]
[ Login-LAT-Service ]
[ Login-Service ]
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
[ Login-TCP-Port ]
* [ NAS-Filter-Rule ]
* [ QoS-Filter-Rule ]
* [ Tunneling ]
* [ Redirect-Host ]
[ Redirect-Host-Usage ]
[ Redirect-Max-Cache-Time ]
* [ Proxy-Info ]
Re-Auth-Request (RAR) Command
A Diameter server may initiate a re-authentication and/or re-
authorization service for a particular session by issuing a Re-Auth-
Request (RAR) message [BASE].
For example, for pre-paid services, the Diameter server that
originally authorized a session may need some confirmation that the
user is still using the services.
If a NAS receives an RAR message with Session-Id equal to a currently
active session and a Re-Auth-Type that includes authentication, it
MUST initiate a re-authentication toward the user, if the service
supports this particular feature.
Message Format
{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
{ Destination-Host }
{ Auth-Application-Id }
{ Re-Auth-Request-Type }
[ User-Name ]
[ Origin-AAA-Protocol ]
[ Origin-State-Id ]
[ NAS-Identifier ]
[ NAS-IP-Address ]
[ NAS-IPv6-Address ]
[ NAS-Port ]
[ NAS-Port-Id ]
[ NAS-Port-Type ]
[ Service-Type ]
[ Framed-IP-Address ]
[ Framed-IPv6-Prefix ]
[ Framed-Interface-Id ]
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
[ Called-Station-Id ]
[ Calling-Station-Id ]
[ Originating-Line-Info ]
[ Acct-Session-Id ]
[ Acct-Multi-Session-Id ]
* [ Class ]
[ Reply-Message ]
* [ Proxy-Info ]
* [ Route-Record ]
Re-Auth-Answer (RAA) Command
The Re-Auth-Answer (RAA) message [BASE] is sent in response to the
The Result-Code AVP MUST be present and indicates the
disposition of the request.
A successful RAA transaction MUST be followed by an AAR message.
Message Format
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ User-Name ]
[ Origin-AAA-Protocol ]
[ Origin-State-Id ]
[ Error-Message ]
[ Error-Reporting-Host ]
* [ Failed-AVP ]
* [ Redirected-Host ]
[ Redirected-Host-Usage ]
[ Redirected-Host-Cache-Time ]
[ Service-Type ]
* [ Configuration-Token ]
[ Idle-Timeout ]
[ Authorization-Lifetime ]
[ Auth-Grace-Period ]
[ Re-Auth-Request-Type ]
* [ Class ]
* [ Reply-Message ]
[ Prompt ]
* [ Proxy-Info ]
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
Session-Termination-Request (STR) Command
The Session-Termination-Request (STR) message [BASE] is sent by the
NAS to inform the Diameter Server that an authenticated and/or
authorized session is being terminated.
Message Format
{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
{ Auth-Application-Id }
{ Termination-Cause }
[ User-Name ]
[ Destination-Host ]
* [ Class ]
[ Origin-AAA-Protocol ]
[ Origin-State-Id ]
* [ Proxy-Info ]
* [ Route-Record ]
Session-Termination-Answer (STA) Command
The Session-Termination-Answer (STA) message [BASE] is sent by the
Diameter Server to acknowledge the notification that the session has
been terminated.
The Result-Code AVP MUST be present and MAY contain
an indication that an error occurred while the STR was being
Upon sending or receiving the STA, the Diameter Server MUST release
all resources for the session indicated by the Session-Id AVP.
intermediate server in the Proxy-Chain MAY also release any
resources, if necessary.
Message Format
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ User-Name ]
* [ Class ]
[ Error-Message ]
[ Error-Reporting-Host ]
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
* [ Failed-AVP ]
[ Origin-AAA-Protocol ]
[ Origin-State-Id ]
* [ Redirect-Host ]
[ Redirect-Host-Usase ]
[ Redirect-Max-Cache-Time ]
* [ Proxy-Info ]
Abort-Session-Request (ASR) Command
The Abort-Session-Request (ASR) message [BASE] may be sent by any
server to the NAS providing session service, to request that the
session identified by the Session-Id be stopped.
Message Format
{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
{ Destination-Host }
{ Auth-Application-Id }
[ User-Name ]
[ Origin-AAA-Protocol ]
[ Origin-State-Id ]
[ NAS-Identifier ]
[ NAS-IP-Address ]
[ NAS-IPv6-Address ]
[ NAS-Port ]
[ NAS-Port-Id ]
[ NAS-Port-Type ]
[ Service-Type ]
[ Framed-IP-Address ]
[ Framed-IPv6-Prefix ]
[ Framed-Interface-Id ]
[ Called-Station-Id ]
[ Calling-Station-Id ]
[ Originating-Line-Info ]
[ Acct-Session-Id ]
[ Acct-Multi-Session-Id ]
* [ Class ]
* [ Reply-Message ]
* [ Proxy-Info ]
* [ Route-Record ]
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
Abort-Session-Answer (ASA) Command
The ASA message [BASE] is sent in response to the ASR.
The Result-
Code AVP MUST be present and indicates the disposition of the
If the session identified by Session-Id in the ASR was successfully
terminated, Result-Code is set to DIAMETER_SUCCESS.
If the session
is not currently active, Result-Code is set to
DIAMETER_UNKNOWN_SESSION_ID.
If the access device does not stop the
session for any other reason, Result-Code is set to
DIAMETER_UNABLE_TO_COMPLY.
Message Format
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ User-Name ]
[ Origin-AAA-Protocol ]
[ Origin-State-Id ]
[ Error-Message ]
[ Error-Reporting-Host ]
* [ Failed-AVP ]
* [ Redirected-Host ]
[ Redirected-Host-Usage ]
[ Redirected-Max-Cache-Time ]
* [ Proxy-Info ]
Accounting-Request (ACR) Command
The ACR message [BASE] is sent by the NAS to report its session
information to a target server downstream.
Either of Acct-Application-Id or Vendor-Specific-Application-Id AVPs
MUST be present.
If the Vendor-Specific-Application-Id grouped AVP
is present, it must have an Acct-Application-Id inside.
The AVPs listed in the Base MUST be assumed to be present, as
appropriate.
NAS service-specific accounting AVPs SHOULD be present
as described in section 8 and the rest of this specification.
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
Message Format
{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
{ Accounting-Record-Type }
{ Accounting-Record-Number }
[ Acct-Application-Id ]
[ Vendor-Specific-Application-Id ]
[ User-Name ]
[ Accounting-Sub-Session-Id ]
[ Acct-Session-Id ]
[ Acct-Multi-Session-Id ]
[ Origin-AAA-Protocol ]
[ Origin-State-Id ]
[ Destination-Host ]
[ Event-Timestamp ]
[ Acct-Delay-Time ]
[ NAS-Identifier ]
[ NAS-IP-Address ]
[ NAS-IPv6-Address ]
[ NAS-Port ]
[ NAS-Port-Id ]
[ NAS-Port-Type ]
* [ Class ]
[ Service-Type ]
[ Termination-Cause ]
[ Accounting-Input-Octets ]
[ Accounting-Input-Packets ]
[ Accounting-Output-Octets ]
[ Accounting-Output-Packets ]
[ Acct-Authentic ]
[ Accounting-Auth-Method ]
[ Acct-Link-Count ]
[ Acct-Session-Time ]
[ Acct-Tunnel-Connection ]
[ Acct-Tunnel-Packets-Lost ]
[ Callback-Id ]
[ Callback-Number ]
[ Called-Station-Id ]
[ Calling-Station-Id ]
* [ Connection-Info ]
[ Originating-Line-Info ]
[ Authorization-Lifetime ]
[ Session-Timeout ]
[ Idle-Timeout ]
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
[ Port-Limit ]
[ Accounting-Realtime-Required ]
[ Acct-Interim-Interval ]
* [ Filter-Id ]
* [ NAS-Filter-Rule ]
* [ Qos-Filter-Rule ]
[ Framed-AppleTalk-Link ]
[ Framed-AppleTalk-Network ]
[ Framed-AppleTalk-Zone ]
[ Framed-Compression ]
[ Framed-Interface-Id ]
[ Framed-IP-Address ]
[ Framed-IP-Netmask ]
* [ Framed-IPv6-Prefix ]
[ Framed-IPv6-Pool ]
* [ Framed-IPv6-Route ]
[ Framed-IPX-Network ]
[ Framed-MTU ]
[ Framed-Pool ]
[ Framed-Protocol ]
* [ Framed-Route ]
[ Framed-Routing ]
* [ Login-IP-Host ]
* [ Login-IPv6-Host ]
[ Login-LAT-Group ]
[ Login-LAT-Node ]
[ Login-LAT-Port ]
[ Login-LAT-Service ]
[ Login-Service ]
[ Login-TCP-Port ]
* [ Tunneling ]
* [ Proxy-Info ]
* [ Route-Record ]
Accounting-Answer (ACA) Command
The ACA message [BASE] is used to acknowledge an Accounting-Request
The Accounting-Answer command contains the same Session-Id
as the Request.
If the Accounting-Request was protected by end-to-
end security, then the corresponding ACA message MUST be protected as
Only the target Diameter Server or home Diameter Server SHOULD
respond with the Accounting-Answer command.
Either Acct-Application-Id or Vendor-Specific-Application-Id AVPs
MUST be present, as it was in the request.
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
The AVPs listed in the Base MUST be assumed to be present, as
appropriate.
NAS service-specific accounting AVPs SHOULD be present
as described in section 8 and the rest of this specification.
Message Format
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
{ Accounting-Record-Type }
{ Accounting-Record-Number }
[ Acct-Application-Id ]
[ Vendor-Specific-Application-Id ]
[ User-Name ]
[ Accounting-Sub-Session-Id ]
[ Acct-Session-Id ]
[ Acct-Multi-Session-Id ]
[ Event-Timestamp ]
[ Error-Message ]
[ Error-Reporting-Host ]
* [ Failed-AVP ]
[ Origin-AAA-Protocol ]
[ Origin-State-Id ]
[ NAS-Identifier ]
[ NAS-IP-Address ]
[ NAS-IPv6-Address ]
[ NAS-Port ]
[ NAS-Port-Id ]
[ NAS-Port-Type ]
[ Service-Type ]
[ Termination-Cause ]
[ Accounting-Realtime-Required ]
[ Acct-Interim-Interval ]
* [ Class ]
* [ Proxy-Info ]
* [ Route-Record ]
NAS Session AVPs
Diameter reserves the AVP Codes 0 - 255 for RADIUS functions that are
implemented in Diameter.
AVPs new to Diameter have code values of 256 and greater.
A Diameter
message that includes one of these AVPs may represent functions not
present in the RADIUS environment and may cause interoperability
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
issues, should the request traverse an AAA system that only supports
the RADIUS protocol.
Some RADIUS attributes are not allowed or supported directly in
See section 9 for more information.
Call and Session Information
This section contains the AVPs specific to NAS Diameter applications
that are needed to identify the call and session context and status
information.
On a request, this information allows the server to
qualify the session.
These AVPs are used in addition to the Base AVPs of:
Session-Id
Auth-Application-Id
Origin-Host
Origin-Realm
Auth-Request-Type
Termination-Cause
The following table describes the session level AVPs; their AVP Code
values, types, and
and whether the AVP MAY be
encrypted.
+---------------------+
AVP Flag rules
|----+-----+----+-----|----+
|SHLD| MUST|
Attribute Name
Code Defined
Value Type |MUST| MAY | NOT|
-----------------------------------------|----+-----+----+-----|----|
Unsigned32 | M
NAS-Port-Id
UTF8String | M
NAS-Port-Type
Enumerated | M
Called-Station-Id 30
UTF8String | M
Calling-Station-
UTF8String | M
Connect-Info
UTF8String | M
Originating-Line- 94
OctetString|
Reply-Message
UTF8String | M
-----------------------------------------|----+-----+----+-----|----|
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
NAS-Port AVP
The NAS-Port AVP (AVP Code 5) is of type Unsigned32 and contains the
physical or virtual port number of the NAS which is authenticating
Note that "port" is meant in its sense as a service
connection on the NAS, not as an IP protocol identifier.
Either NAS-Port or NAS-Port-Id (AVP Code 87) SHOULD be present in
AA-Request (AAR) commands if the NAS differentiates among its ports.
NAS-Port-Id AVP
The NAS-Port-Id AVP (AVP Code 87) is of type UTF8String and consists
of ASCII text identifying the port of the NAS authenticating the
Note that "port" is meant in its sense as a service connection
on the NAS, not as an IP protocol identifier.
Either NAS-Port or NAS-Port-Id SHOULD be present in AA-Request (AAR)
commands if the NAS differentiates among its ports.
NAS-Port-Id is
intended for use by NASes that cannot conveniently number their
NAS-Port-Type AVP
The NAS-Port-Type AVP (AVP Code 61) is of type Enumerated and
contains the type of the port on which the NAS is authenticating the
This AVP SHOULD be present if the NAS uses the same NAS-Port
number ranges for different service types concurrently.
The supported values are defined in [RADIUSTypes].
The following
list is informational and subject to change by the IANA.
ISDN Async V.120
ISDN Async V.110
HDLC Clear Channel
SDSL - Symmetric DSL
ADSL-CAP - Asymmetric DSL, Carrierless Amplitude Phase
Modulation
ADSL-DMT - Asymmetric DSL, Discrete Multi-Tone
IDSL - ISDN Digital Subscriber Line
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
xDSL - Digital Subscriber Line of unknown type
Wireless - Other
Wireless - IEEE 802.11
Token-Ring
[RAD802.1X]
[RAD802.1X]
Wireless - CDMA2000
Wireless - UMTS
Wireless - 1X-EV
[IEEE 802.11f]
Called-Station-Id AVP
The Called-Station-Id AVP (AVP Code 30) is of type UTF8String and
allows the NAS to send the ASCII string describing the layer 2
address the user contacted in the request.
For dialup access, this
can be a phone number obtained by using Dialed Number Identification
(DNIS) or a similar technology.
Note that this may be different from
the phone number the call comes in on.
For use with IEEE 802 access,
the Called-Station-Id MAY contain a MAC address formatted as
described in [RAD802.1X].
It SHOULD only be present in
authentication and/or authorization requests.
If the Auth-Request-Type AVP is set to authorization-only and the
User-Name AVP is absent, the Diameter Server MAY perform
authorization based on this field.
This can be used by a NAS to
request whether a call should be answered based on the DNIS.
The codification of this field's allowed usage range is outside the
scope of this specification.
Calling-Station-Id AVP
The Calling-Station-Id AVP (AVP Code 31) is of type UTF8String and
allows the NAS to send the ASCII string describing the layer 2
address from which the user connected in the request.
For dialup
access, this is the phone number the call came from, using Automatic
Number Identification (ANI) or a similar technology.
For use with
IEEE 802 access, the Calling-Station-Id AVP MAY contain a MAC
address, formated as described in [RAD802.1X].
It SHOULD only be
present in authentication and/or authorization requests.
If the Auth-Request-Type AVP is set to authorization-only and the
User-Name AVP is absent, the Diameter Server MAY perform
authorization based on this field.
This can be used by a NAS to
request whether a call should be answered based on the layer 2
address (ANI, MAC Address, etc.)
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
The codification of this field's allowed usage range is outside the
scope of this specification.
Connect-Info AVP
The Connect-Info AVP (AVP Code 77) is of type UTF8String and is sent
in the AA-Request message or ACR STOP message.
When sent in the
Access-Request, it indicates the nature of the user's connection.
The connection speed SHOULD be included at the beginning of the first
Connect-Info AVP in the message.
If the transmit and receive
connection speeds differ, both may be included in the first AVP with
the transmit speed listed first (the speed the NAS modem transmits
at), then a slash (/), then the receive speed, and then other
optional information.
For example: "28800 V42BIS/LAPM" or " V90"
More than one Connect-Info attribute may be present in an
Accounting-Request packet to accommodate expected efforts by the ITU
to have modems report more connection information in a standard
format that might exceed 252 octets.
If sent in the ACR STOP, this attribute may summarize statistics
relating to session quality.
For example, in IEEE 802.11, the
Connect-Info attribute may contain information on the number of link
layer retransmissions.
The exact format of this attribute is
implementation specific.
Originating-Line-Info AVP
The Originating-Line-Info AVP (AVP Code 94) is of type OctetString
and is sent by the NAS system to convey information about the origin
of the call from an SS7 system.
The originating line information (OLI) element indicates the nature
and/or characteristics of the line from which a call originated
(e.g., pay phone, hotel, cellular).
Telephone companies are starting
to offer OLI to their customers as an option over Primary Rate
Interface (PRI).
Internet Service Providers (ISPs) can use OLI in
addition to Called-Station-Id and Calling-Station-Id attributes to
differentiate customer calls and to define different services.
The Value field contains two octets (00 - 99).
ANSI T1.113 and
BELLCORE 394 can be used for additional information about these
values and their use.
For more information on current assignment
values, see [ANITypes].
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
Description
------------------------------------------------------------
Plain Old Telephone Service (POTS)
Multiparty Line (more than 2)
ANI Failure
ANI Observed
ONI Observed
ANI Failure Observed
Station Level Rating
Special Operator Handling Required
InterLATA Restricted
Automatic Identified Outward Dialing (AIOD)
Coin or Non-Coin
Toll Free Service (Non-Pay Origination)
Toll Free Service (Pay Origination)
Toll Free Service (Coin Control Origination)
Prison/Inmate Service
30-32 Intercept
Intercept (Blank)
Intercept (Trouble)
Intercept (Regular)
Telco Operator Handled Call
40-49 Unrestricted Use
Outward Wide Area Telecommunications Service (OUTWATS)
Telecommunications Relay Service (TRS)(Unrestricted)
Cellular/Wireless PCS (Type 1)
Cellular/Wireless PCS (Type 2)
Cellular/Wireless PCS (Roaming)
TRS (Hotel)
TRS (Restricted)
Pay Station, No Coin Control
Access for Private Virtual Network Service
Reply-Message AVP
The Reply-Message AVP (AVP Code 18) is of type UTF8String and
contains text that MAY be displayed to the user.
When used in an
AA-Answer message with a successful Result-Code AVP, it indicates
When found in an AAA message with a Result-Code other than
DIAMETER_SUCCESS, the AVP contains a failure message.
The Reply-Message AVP MAY indicate dialog text to prompt the user
before another AA-Request attempt.
When used in an AA-Answer with a
Result-Code of DIAMETER_MULTI_ROUND_AUTH or in an Re-Auth-Request
message, it MAY contain a dialog text to prompt the user for a
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
Multiple Reply-Messages MAY be included, and if any are displayed,
they MUST be displayed in the same order as they appear in the
Diameter message.
NAS Authentication AVPs
This section defines the AVPs necessary to carry the authentication
information in the Diameter protocol.
The functionality defined here
provides a RADIUS-like AAA service over a more reliable and secure
transport, as defined in the base protocol [BASE].
The following table describes the AVPs; their AVP Code values, types,
and possible flag values, and whether the AVP MAY be encrypted.
+---------------------+
AVP Flag rules
|----+-----+----+-----|----+
|SHLD| MUST|
Attribute Name
Code Defined
Value Type |MUST| MAY | NOT|
-----------------------------------------|----+-----+----+-----|----|
User-Password
OctetString| M
Password-Retry
Unsigned32 | M
Enumerated | M
CHAP-Algorithm
Enumerated | M
CHAP-Ident
OctetString| M
CHAP-Response
OctetString| M
CHAP-Challenge
OctetString| M
ARAP-Password
OctetString| M
ARAP-Challenge-
OctetString| M
ARAP-Security
Unsigned32 | M
ARAP-Security-
OctetString| M
-----------------------------------------|----+-----+----+-----|----|
User-Password AVP
The User-Password AVP (AVP Code 2) is of type OctetString and
contains the password of the user to be authenticated, or the user's
input in a multi-round authentication exchange.
The User-Password AVP contains a user password or one-time password
and therefore represents sensitive information.
As required in
[BASE], Diameter messages are encrypted by using IPsec or TLS.
Unless this AVP is used for one-time passwords, the User-Password AVP
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
SHOULD NOT be used in untrusted proxy environments without encrypting
it by using end-to-end security techniques, such as the proposed CMS
Security [DiamCMS].
The clear-text password (prior to encryption) MUST NOT be longer than
128 bytes in length.
Password-Retry AVP
The Password-Retry AVP (AVP Code 75) is of type Unsigned32 and MAY be
included in the AA-Answer if the Result-Code indicates an
authentication failure.
The value of this AVP indicates how many
authentication attempts a user is permitted before being
disconnected.
This AVP is primarily intended for use when the
Framed-Protocol AVP (see section 6.10.1) is set to ARAP.
Prompt AVP
The Prompt AVP (AVP Code 76) is of type Enumerated and MAY be present
in the AA-Answer message.
When present, it is used by the NAS to
determine whether the user's response, when entered, should be
The supported values are listed in [RADIUSTypes].
The following list
is informational:
CHAP-Auth AVP
The CHAP-Auth AVP (AVP Code 402) is of type Grouped and contains the
information necessary to authenticate a user using the PPP
Challenge-Handshake Authentication Protocol (CHAP) [PPPCHAP].
CHAP-Auth AVP is found in a message, the CHAP-Challenge AVP MUST be
present as well.
The optional AVPs containing the CHAP response
depend upon the value of the CHAP-Algorithm AVP.
The grouped AVP has
the following ABNF grammar:
{ CHAP-Algorithm }
{ CHAP-Ident }
[ CHAP-Response ]
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
CHAP-Algorithm AVP
The CHAP-Algorithm AVP (AVP Code 403) is of type Enumerated and
contains the algorithm identifier used in the computation of the CHAP
response [PPPCHAP].
The following values are currently supported:
CHAP with MD5
The CHAP response is computed by using the procedure described
in [PPPCHAP].
This algorithm requires that the CHAP-Response
AVP MUST be present in the CHAP-Auth AVP.
CHAP-Ident AVP
The CHAP-Ident AVP (AVP Code 404) is of type OctetString and contains
the 1 octet CHAP Identifier used in the computation of the CHAP
response [PPPCHAP].
CHAP-Response AVP
The CHAP-Response AVP (AVP Code 405) is of type OctetString and
contains the 16 octet authentication data provided by the user in
response to the CHAP challenge [PPPCHAP].
CHAP-Challenge AVP
The CHAP-Challenge AVP (AVP Code 60) is of type OctetString and
contains the CHAP Challenge sent by the NAS to the CHAP peer
[PPPCHAP].
ARAP-Password AVP
The ARAP-Password AVP (AVP Code 70) is of type OctetString and is
only present when the Framed-Protocol AVP (see section 6.10.1) is
included in the message and is set to ARAP.
This AVP MUST NOT be
present if either the User-Password or the CHAP-Auth AVP is present.
See [RADIUSExt] for more information on the contents of this AVP.
ARAP-Challenge-Response AVP
The ARAP-Challenge-Response AVP (AVP Code 84) is of type OctetString
and is only present when the Framed-Protocol AVP (see section 6.10.1)
is included in the message and is set to ARAP.
This AVP contains an
8 octet response to the dial-in client's challenge.
The RADIUS
server calculates this value by taking the dial-in client's challenge
from the high-order 8 octets of the ARAP-Password AVP and performing
DES encryption on this value with the authenticating user's password
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
as the key.
If the user's password is fewer than 8 octets in length,
the password is padded at the end with NULL octets to a length of 8
before it is used as a key.
ARAP-Security AVP
The ARAP-Security AVP (AVP Code 73) is of type Unsigned32 and MAY be
present in the AA-Answer message if the Framed-Protocol AVP (see
section 6.10.1) is set to the value of ARAP, and the Result-Code AVP
is set to DIAMETER_MULTI_ROUND_AUTH.
See [RADIUSExt] for more
information on the format of this AVP.
ARAP-Security-Data AVP
The ARAP-Security AVP (AVP Code 74) is of type OctetString and MAY be
present in the AA-Request or AA-Answer message if the Framed-Protocol
AVP is set to the value of ARAP, and the Result-Code AVP is set to
DIAMETER_MULTI_ROUND_AUTH.
This AVP contains the security module
challenge or response associated with the ARAP Security Module
specified in ARAP-Security.
NAS Authorization AVPs
This section contains the authorization AVPs supported in the NAS
Application.
The Service-Type AVP SHOULD be present in all messages,
and, based on its value, additional AVPs defined in this section and
in section 7 MAY be present.
Due to space constraints, the short-form IPFltrRule is used to
represent IPFilterRule, and QoSFltrRule is used for QoSFilterRule.
+---------------------+
AVP Flag rules
|----+-----+----+-----|----+
|SHLD| MUST|
Attribute Name
Code Defined
Value Type |MUST| MAY | NOT|
-----------------------------------------|----+-----+----+-----|----|
Service-Type
Enumerated | M
Callback-Number
UTF8String | M
Callback-Id
UTF8String | M
Idle-Timeout
Unsigned32 | M
Port-Limit
Unsigned32 | M
NAS-Filter-Rule
IPFltrRule | M
UTF8String | M
Configuration-
OctetString| M
QoS-Filter-Rule
QoSFltrRule|
Framed-Protocol
Enumerated | M
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
Framed-Routing
Enumerated | M
Framed-MTU
Unsigned32 | M
Enumerated | M
Compression
Framed-IP-Address
OctetString| M
Framed-IP-Netmask
OctetString| M
Framed-Route
UTF8String | M
Framed-Pool
OctetString| M
Unsigned64 | M
Interface-Id
Framed-IPv6-
OctetString| M
Framed-IPv6-
UTF8String | M
Framed-IPv6-Pool 100
OctetString| M
Framed-IPX-
UTF8String | M
Framed-Appletalk- 37
Unsigned32 | M
Framed-Appletalk- 38
Unsigned32 | M
Framed-Appletalk- 39
OctetString| M
ARAP-Features
OctetString| M
ARAP-Zone-Access
Enumerated | M
Login-IP-Host
OctetString| M
Login-IPv6-Host
OctetString| M
Login-Service
Enumerated | M
Login-TCP-Port
Unsigned32 | M
Login-LAT-Service 34
OctetString| M
Login-LAT-Node
OctetString| M
Login-LAT-Group
OctetString| M
Login-LAT-Port
OctetString| M
-----------------------------------------|----+-----+----+-----|----|
Service-Type AVP
The Service-Type AVP (AVP Code 6) is of type Enumerated and contains
the type of service the user has requested or the type of service to
be provided.
One such AVP MAY be present in an authentication and/or
authorization request or response.
A NAS is not required to
implement all of these service types.
It MUST treat unknown or
unsupported Service-Types received in a response as a failure and end
the session with a DIAMETER_INVALID_AVP_VALUE Result-Code.
When used in a request, the Service-Type AVP SHOULD be considered a
hint to the server that the NAS believes the user would prefer the
kind of service indicated.
The server is not required to honor the
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
Furthermore, if the service specified by the server is
supported, but not compatible with the current mode of access, the
NAS MUST fail to start the session.
The NAS MUST also generate the
appropriate error message(s).
The following values have been defined for the Service-Type AVP.
complete list of defined values can be found in [RADIUS] and
[RADIUSTypes].
The following list is informational:
Callback Login
Callback Framed
Administrative
NAS Prompt
Authenticate Only
Callback NAS Prompt
Call Check
Callback Administrative
Modem Relay
IAPP-Register
[IEEE 802.11f]
IAPP-AP-Check
[IEEE 802.11f]
Authorize Only
[RADDynAuth]
The following values are further qualified:
The user should be connected to a host.
The message MAY
include additional AVPs defined in sections 6.16 or 6.17.
A Framed Protocol, such as PPP or SLIP, should be started for
The message MAY include additional AVPs defined in
section 6.10, or section 7 for tunneling services.
Callback Login
The user should be disconnected and called back, then connected
to a host.
The message MAY include additional AVPs defined in
this section.
Callback Framed
The user should be disconnected and called back, and then a
Framed Protocol, such as PPP or SLIP, should be started for the
The message MAY include additional AVPs defined in
section 6.10, or in section 7 for tunneling services.
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
Callback-Number AVP
The Callback-Number AVP (AVP Code 19) is of type UTF8String and
contains a dialing string to be used for callback.
It MAY be used in
an authentication and/or authorization request as a hint to the
server that a Callback service is desired, but the server is not
required to honor the hint in the corresponding response.
The codification of this field's allowed usage range is outside the
scope of this specification.
Callback-Id AVP
The Callback-Id AVP (AVP Code 20) is of type UTF8String and contains
the name of a place to be called, to be interpreted by the NAS.
AVP MAY be present in an authentication and/or authorization
This AVP is not roaming-friendly as it assumes that the Callback-Id
is configured on the NAS.
Using the Callback-Number AVP therefore
preferable.
Idle-Timeout AVP
The Idle-Timeout AVP (AVP Code 28) is of type Unsigned32 and sets the
maximum number of consecutive seconds of idle connection allowable to
the user before termination of the session or before a prompt is
The default is none, or system specific.
Port-Limit AVP
The Port-Limit AVP (AVP Code 62) is of type Unsigned32 and sets the
maximum number of ports the NAS provides to the user.
It MAY be used
in an authentication and/or authorization request as a hint to the
server that multilink PPP [PPPMP] service is desired, but the server
is not required to honor the hint in the corresponding response.
NAS-Filter-Rule AVP
The NAS-Filter-Rule AVP (AVP Code 400) is of type IPFilterRule and
provides filter rules that need to be configured on the NAS for the
One or more of these AVPs MAY be present in an authorization
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
Filter-Id AVP
The Filter-Id AVP (AVP Code 11) is of type UTF8String and contains
the name of the filter list for this user.
Zero or more Filter-Id
AVPs MAY be sent in an authorization answer.
Identifying a filter list by name allows the filter to be used on
different NASes without regard to filter-list implementation details.
However, this AVP is not roaming friendly, as filter naming differs
from one service provider to another.
In non-RADIUS environments, it is RECOMMENDED that the NAS-Filter-
Rule AVP be used instead.
Configuration-Token AVP
The Configuration-Token AVP (AVP Code 78) is of type OctetString and
is sent by a Diameter Server to a Diameter Proxy Agent or Translation
Agent in an AA-Answer command to indicate a type of user profile to
It should not be sent to a Diameter Client (NAS).
The format of the Data field of this AVP is site specific.
QoS-Filter-Rule AVP
The QoS-Filter-Rule AVP (AVP Code 407) is of type QoSFilterRule and
provides QoS filter rules that need to be configured on the NAS for
One or more such AVPs MAY be present in an authorization
Note: Due to an editorial mistake in [BASE], only the AVP format is
discussed.
The complete QoSFilterRule definition was not included.
It is reprinted here for clarification.
QoSFilterRule
The QosFilterRule format is derived from the OctetString AVP Base
It uses the ASCII charset.
Packets may be marked or
metered based on the following information:
(in or out)
Source and destination IP address
(possibly masked)
Source and destination port
(lists or ranges)
DSCP values
(no mask or range)
Rules for the appropriate direction ar the
first matched rule terminates the evaluation.
Each packet is
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
evaluated once.
If no rule matches, the packet is treated as best
An access device unable to interpret or apply a QoS rule
SHOULD NOT terminate the session.
QoSFilterRule filters MUST follow the following format:
action dir proto from src to dst [options]
- Mark packet with a specific DSCP
[DIFFSERV].
The DSCP option MUST be
- Meter traffic.
The metering options
MUST be included.
The format is as described under IPFilterRule.
The format is as described under IPFilterRule.
src and dst
The format is as described under IPFilterRule.
Color values as defined in [DIFFSERV].
matching of DSCP values is required (no masks or
The metering option provides Assured Forwarding,
as defined in [DIFFSERVAF], and MUST be present
if the action is set to meter.
The rate option is
the throughput, in bits per second, used
by the access device to mark packets.
over the rate is marked with the color_over
codepoint, and traffic under the rate is marked
with the color_under codepoint.
The color_under
and color_over options contain the drop
preferences and MUST conform to the recommended
codepoint keywords described in [DIFFSERVAF]
(e.g., AF13).
The metering option also supports the strict
limit on traffic required by Expedited
Forwarding, as defined in [DIFFSERVEF].
color_over option may contain the keyword "drop"
to prevent forwarding of traffic that exceeds the
rate parameter.
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
The rule syntax is a modified subset of ipfw(8) from FreeBSD,
and the ipfw.c code may provide a useful base for
implementations.
Framed Access Authorization AVPs
This section lists the authorization AVPs necessary to
support framed access, such as PPP and SLIP.
AVPs defined in this
section MAY be present in a message if the Service-Type AVP was set
to "Framed" or "Callback Framed".
Framed-Protocol AVP
The Framed-Protocol AVP (AVP Code 7) is of type Enumerated and
contains the framing to be used for framed access.
This AVP MAY be
present in both requests and responses.
The supported values are
listed in [RADIUSTypes].
The following list is informational:
AppleTalk Remote Access Protocol (ARAP)
Gandalf proprietary SingleLink/MultiLink protocol
Xylogics proprietary IPX/SLIP
X.75 Synchronous
Framed-Routing AVP
The Framed-Routing AVP (AVP Code 10) is of type Enumerated and
contains the routing method for the user when the user is a router to
a network.
This AVP SHOULD only be present in authorization
responses.
The supported values are listed in [RADIUSTypes].
following list is informational:
Send routing packets
Listen for routing packets
Send and Listen
Framed-MTU AVP
The Framed-MTU AVP (AVP Code 12) is of type Unsigned32 and contains
the Maximum Transmission Unit to be configured for the user, when it
is not negotiated by some other means (such as PPP).
This AVP SHOULD
only be present in authorization responses.
The MTU value MUST be in
the range from 64 to 65535.
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
Framed-Compression AVP
The Framed-Compression AVP (AVP Code 13) is of type Enumerated and
contains the compression protocol to be used for the link.
used in an authorization request as a hint to the server that a
specific compression type is desired, but the server is not required
to honor the hint in the corresponding response.
More than one compression protocol AVP MAY be sent.
The NAS is
responsible for applying the proper compression protocol to the
appropriate link traffic.
The supported values are listed in [RADIUSTypes].
The following list
is informational:
VJ TCP/IP header compression
IPX header compression
Stac-LZS compression
IP Access Authorization AVPs
The AVPs defined in this section are used when the user requests, or
is being granted, access service to IP.
Framed-IP-Address AVP
The Framed-IP-Address AVP (AVP Code 8) [RADIUS] is of type
OctetString and contains an IPv4 address of the type specified in the
attribute value to be configured for the user.
It MAY be used in an
authorization request as a hint to the server that a specific address
is desired, but the server is not required to honor the hint in the
corresponding response.
Two values have special significance: 0xFFFFFFFF and 0xFFFFFFFE.
value 0xFFFFFFFF indicates that the NAS should allow the user to
select an address (i.e., negotiated).
The value 0xFFFFFFFE indicates
that the NAS should select an address for the user (e.g., assigned
from a pool of addresses kept by the NAS).
Framed-IP-Netmask AVP
The Framed-IP-Netmask AVP (AVP Code 9) is of type OctetString and
contains the four octets of the IPv4 netmask to be configured for the
user when the user is a router to a network.
It MAY be used in an
authorization request as a hint to the server that a specific netmask
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
is desired, but the server is not required to honor the hint in the
corresponding response.
This AVP MUST be present in a response if
the request included this AVP with a value of 0xFFFFFFFF.
Framed-Route AVP
The Framed-Route AVP (AVP Code 22) is of type UTF8String and contains
the ASCII routing information to be configured for the user on the
Zero or more of these AVPs MAY be present in an authorization
The string MUST contain a destination prefix in dotted quad form
optionally followed by a slash and a decimal length specifier stating
how many high-order bits of the prefix should be used.
followed by a space, a gateway address in dotted quad form, a space,
and one or more metrics for example,
"192.168.1.0/24 192.168.1.1 1".
The length specifier may be omitted, in which case it should default
to 8 bits for class A prefixes, to 16 bits for class B prefixes, and
to 24 bits for class C for example,
"192.168.1.0 192.168.1.1 1".
Whenever the gateway address is specified as "0.0.0.0" the IP address
of the user SHOULD be used as the gateway address.
Framed-Pool AVP
The Framed-Pool AVP (AVP Code 88) is of type OctetString and contains
the name of an assigned address pool that SHOULD be used to assign an
address for the user.
If a NAS does not support multiple address
pools, the NAS SHOULD ignore this AVP.
Address pools are usually
used for IP addresses but can be used for other protocols if the NAS
supports pools for those protocols.
Although specified as type OctetString for compatibility with RADIUS
[RADIUSExt], the encoding of the Data field SHOULD also conform to
the rules for the UTF8String Data Format.
Framed-Interface-Id AVP
The Framed-Interface-Id AVP (AVP Code 96) is of type Unsigned64 and
contains the IPv6 interface identifier to be configured for the user.
It MAY be used in authorization requests as a hint to the server that
a specific interface id is desired, but the server is not required to
honor the hint in the corresponding response.
Calhoun, et al.
Standards Track
Diameter Network Access Server Application
August 2005
Framed-IPv6-Prefix AVP
The Framed-IPv6-Prefix AVP (AVP Code 97) is of type OctetString and
contains the IPv6 prefix to be configured for the user.
One or more
AVPs MAY be used in authorization requests as a hint to the server
that specific IPv6 prefixes are desired, but the server is not
required to honor the hint in the corresponding response.
Framed-IPv6-Route AVP
The Framed-IPv6-Route AVP (AVP Code 99) is of type UTF8String and
contains the ASCII routing information to be configured for the user
on the NAS.
Zero or more of these AVPs MAY be present in an
authorization response.
The string MUST contain an IPv6 address prefix followed by a slash
and a decimal length specifier stating how many high order bits of
the prefix should be used.
This is followed by a space, a gateway
address in hexadecimal notation, a space, and one or more metrics
for example,
":106::/64 :a00:20ff:fe99:a998 1".
Whenever the gateway address is the IPv6 unspecified address, the IP
address of the user SHOULD be used as the gateway address, such as
":106::/64 :: 1".
Framed-IPv6-Pool AVP
The Framed-IPv6-Pool AVP (AVP Code 100) is of type OctetString and
contains the name of an assigned pool that SHOULD be used to assign
an IPv6 prefix for the user.
If the access device does not support
multiple prefix pools, it MUST ignore this AVP.
Although specified as type OctetString for compatibility with RADIUS
[RADIUSIPv6], the encodi