Network Working Group P. Calhoun
Request for Comments: 4005 G. Zorn
Category: Standards Track Cisco Systems Inc.
D. Spence
Consultant
D. Mitton
Circular Networks
August 2005
Network Working Group P. Calhoun
Request for Comments: 4005 G. Zorn
Category: Standards Track Cisco Systems Inc.
D. Spence
Consultant
D. Mitton
Circular Networks
August 2005
Diameter Network Access Server Application
Diameter网络访问服务器应用程序
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.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
Abstract
摘要
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.
本文档描述了网络访问服务器（NAS）环境中用于身份验证、授权和记帐（AAA）服务的Diameter协议应用程序。当与Diameter基本协议、传输配置文件和可扩展身份验证协议规范结合使用时，此应用程序规范满足典型的网络访问服务需求。
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 Diameter. This is achieved by including the RADIUS attribute space to eliminate the need to perform many attribute translations.
Diameter协议的初始部署预计将包括遗留系统。因此，该应用程序经过精心设计，可以减轻RADIUS和Diameter之间协议转换的负担。这是通过包括半径属性空间来实现的，以消除执行许多属性转换的需要。
The interactions between Diameter applications and RADIUS specified in this document are to be applied to all Diameter applications. In this sense, this document extends the Base Diameter protocol.
本文件中规定的直径应用和半径之间的相互作用适用于所有直径应用。从这个意义上讲，本文档扩展了基本直径协议。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . 5
1.2. Requirements Language . . . . . . . . . . . . . . . . . 6
1.3. Advertising Application Support . . . . . . . . . . . . 6
2. NAS Calls, Ports, and Sessions . . . . . . . . . . . . . . . . 6
2.1. Diameter Session Establishment . . . . . . . . . . . . . 7
2.2. Diameter Session Reauthentication or Reauthorization . . 7
2.3. Diameter Session Termination . . . . . . . . . . . . . . 8
3. NAS Messages . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1. AA-Request (AAR) Command . . . . . . . . . . . . . . . . 9
3.2. AA-Answer (AAA) Command . . . . . . . . . . . . . . . . 11
3.3. Re-Auth-Request (RAR) Command . . . . . . . . . . . . . 13
3.4. Re-Auth-Answer (RAA) Command . . . . . . . . . . . . . . 14
3.5. Session-Termination-Request (STR) Command . . . . . . . 15
3.6. Session-Termination-Answer (STA) Command . . . . . . . . 15
3.7. Abort-Session-Request (ASR) Command . . . . . . . . . . 16
3.8. Abort-Session-Answer (ASA) Command . . . . . . . . . . . 17
3.9. Accounting-Request (ACR) Command . . . . . . . . . . . . 17
3.10. Accounting-Answer (ACA) Command. . . . . . . . . . . . . 19
4. NAS Session AVPs . . . . . . . . . . . . . . . . . . . . . . . 20
4.1. Call and Session Information . . . . . . . . . . . . . . 21
4.2. NAS-Port AVP . . . . . . . . . . . . . . . . . . . . . . 22
4.3. NAS-Port-Id AVP . . . . . . . . . . . . . . . . . . . . 22
4.4. NAS-Port-Type AVP . . . . . . . . . . . . . . . . . . . 22
4.5. Called-Station-Id AVP . . . . . . . . . . . . . . . . . 23
4.6. Calling-Station-Id AVP . . . . . . . . . . . . . . . . . 23
4.7. Connect-Info AVP . . . . . . . . . . . . . . . . . . . . 24
4.8. Originating-Line-Info AVP . . . . . . . . . . . . . . . 24
4.9. Reply-Message AVP . . . . . . . . . . . . . . . . . . . 25
5. NAS Authentication AVPs . . . . . . . . . . . . . . . . . . . 26
5.1. User-Password AVP . . . . . . . . . . . . . . . . . . . 26
5.2. Password-Retry AVP . . . . . . . . . . . . . . . . . . . 27
5.3. Prompt AVP . . . . . . . . . . . . . . . . . . . . . . . 27
5.4. CHAP-Auth AVP . . . . . . . . . . . . . . . . . . . . . 27
5.5. CHAP-Algorithm AVP . . . . . . . . . . . . . . . . . . . 28
5.6. CHAP-Ident AVP . . . . . . . . . . . . . . . . . . . . . 28
5.7. CHAP-Response AVP . . . . . . . . . . . . . . . . . . . 28
5.8. CHAP-Challenge AVP . . . . . . . . . . . . . . . . . . . 28
5.9. ARAP-Password AVP . . . . . . . . . . . . . . . . . . . 28
5.10. ARAP-Challenge-Response AVP. . . . . . . . . . . . . . . 28
5.11. ARAP-Security AVP. . . . . . . . . . . . . . . . . . . . 29
5.12. ARAP-Security-Data AVP . . . . . . . . . . . . . . . . . 29
6. NAS Authorization AVPs . . . . . . . . . . . . . . . . . . . . 29
6.1. Service-Type AVP . . . . . . . . . . . . . . . . . . . . 30
6.2. Callback-Number AVP . . . . . . . . . . . . . . . . . . 32
6.3. Callback-Id AVP . . . . . . . . . . . . . . . . . . . . 32
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . 5
1.2. Requirements Language . . . . . . . . . . . . . . . . . 6
1.3. Advertising Application Support . . . . . . . . . . . . 6
2. NAS Calls, Ports, and Sessions . . . . . . . . . . . . . . . . 6
2.1. Diameter Session Establishment . . . . . . . . . . . . . 7
2.2. Diameter Session Reauthentication or Reauthorization . . 7
2.3. Diameter Session Termination . . . . . . . . . . . . . . 8
3. NAS Messages . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1. AA-Request (AAR) Command . . . . . . . . . . . . . . . . 9
3.2. AA-Answer (AAA) Command . . . . . . . . . . . . . . . . 11
3.3. Re-Auth-Request (RAR) Command . . . . . . . . . . . . . 13
3.4. Re-Auth-Answer (RAA) Command . . . . . . . . . . . . . . 14
3.5. Session-Termination-Request (STR) Command . . . . . . . 15
3.6. Session-Termination-Answer (STA) Command . . . . . . . . 15
3.7. Abort-Session-Request (ASR) Command . . . . . . . . . . 16
3.8. Abort-Session-Answer (ASA) Command . . . . . . . . . . . 17
3.9. Accounting-Request (ACR) Command . . . . . . . . . . . . 17
3.10. Accounting-Answer (ACA) Command. . . . . . . . . . . . . 19
4. NAS Session AVPs . . . . . . . . . . . . . . . . . . . . . . . 20
4.1. Call and Session Information . . . . . . . . . . . . . . 21
4.2. NAS-Port AVP . . . . . . . . . . . . . . . . . . . . . . 22
4.3. NAS-Port-Id AVP . . . . . . . . . . . . . . . . . . . . 22
4.4. NAS-Port-Type AVP . . . . . . . . . . . . . . . . . . . 22
4.5. Called-Station-Id AVP . . . . . . . . . . . . . . . . . 23
4.6. Calling-Station-Id AVP . . . . . . . . . . . . . . . . . 23
4.7. Connect-Info AVP . . . . . . . . . . . . . . . . . . . . 24
4.8. Originating-Line-Info AVP . . . . . . . . . . . . . . . 24
4.9. Reply-Message AVP . . . . . . . . . . . . . . . . . . . 25
5. NAS Authentication AVPs . . . . . . . . . . . . . . . . . . . 26
5.1. User-Password AVP . . . . . . . . . . . . . . . . . . . 26
5.2. Password-Retry AVP . . . . . . . . . . . . . . . . . . . 27
5.3. Prompt AVP . . . . . . . . . . . . . . . . . . . . . . . 27
5.4. CHAP-Auth AVP . . . . . . . . . . . . . . . . . . . . . 27
5.5. CHAP-Algorithm AVP . . . . . . . . . . . . . . . . . . . 28
5.6. CHAP-Ident AVP . . . . . . . . . . . . . . . . . . . . . 28
5.7. CHAP-Response AVP . . . . . . . . . . . . . . . . . . . 28
5.8. CHAP-Challenge AVP . . . . . . . . . . . . . . . . . . . 28
5.9. ARAP-Password AVP . . . . . . . . . . . . . . . . . . . 28
5.10. ARAP-Challenge-Response AVP. . . . . . . . . . . . . . . 28
5.11. ARAP-Security AVP. . . . . . . . . . . . . . . . . . . . 29
5.12. ARAP-Security-Data AVP . . . . . . . . . . . . . . . . . 29
6. NAS Authorization AVPs . . . . . . . . . . . . . . . . . . . . 29
6.1. Service-Type AVP . . . . . . . . . . . . . . . . . . . . 30
6.2. Callback-Number AVP . . . . . . . . . . . . . . . . . . 32
6.3. Callback-Id AVP . . . . . . . . . . . . . . . . . . . . 32
6.4. Idle-Timeout AVP . . . . . . . . . . . . . . . . . . . . 32
6.5. Port-Limit AVP . . . . . . . . . . . . . . . . . . . . . 32
6.6. NAS-Filter-Rule AVP . . . . . . . . . . . . . . . . . . 32
6.7. Filter-Id AVP . . . . . . . . . . . . . . . . . . . . . 33
6.8. Configuration-Token AVP . . . . . . . . . . . . . . . . 33
6.9. QoS-Filter-Rule AVP . . . . . . . . . . . . . . . . . . 33
6.10. Framed Access Authorization AVPs . . . . . . . . . . . . 35
6.10.1. Framed-Protocol AVP . . . . . . . . . . . . . . 35
6.10.2. Framed-Routing AVP. . . . . . . . . . . . . . . 35
6.10.3. Framed-MTU AVP. . . . . . . . . . . . . . . . . 35
6.10.4. Framed-Compression AVP. . . . . . . . . . . . . 36
6.11. IP Access Authorization AVPs.. . . . . . . . . . . . . . 36
6.11.1. Framed-IP-Address AVP . . . . . . . . . . . . . 36
6.11.2. Framed-IP-Netmask AVP . . . . . . . . . . . . . 36
6.11.3. Framed-Route AVP. . . . . . . . . . . . . . . . 37
6.11.4. Framed-Pool AVP . . . . . . . . . . . . . . . . 37
6.11.5. Framed-Interface-Id AVP . . . . . . . . . . . . 37
6.11.6. Framed-IPv6-Prefix AVP. . . . . . . . . . . . . 38
6.11.7. Framed-IPv6-Route AVP . . . . . . . . . . . . . 38
6.11.8. Framed-IPv6-Pool AVP. . . . . . . . . . . . . . 38
6.12. IPX Access . . . . . . . . . . . . . . . . . . . . . . . 38
6.12.1. Framed-IPX-Network AVP. . . . . . . . . . . . . 39
6.13. AppleTalk Network Access . . . . . . . . . . . . . . . . 39
6.13.1. Framed-AppleTalk-Link AVP . . . . . . . . . . . 39
6.13.2. Framed-AppleTalk-Network AVP . . . . . . . . . 39
6.13.3. Framed-AppleTalk-Zone AVP . . . . . . . . . . . 40
6.14. AppleTalk Remote Access. . . . . . . . . . . . . . . . . 40
6.14.1. ARAP-Features AVP . . . . . . . . . . . . . . . 40
6.14.2. ARAP-Zone-Access AVP. . . . . . . . . . . . . . 40
6.15. Non-Framed Access Authorization AVPs . . . . . . . . . . 40
6.15.1. Login-IP-Host AVP . . . . . . . . . . . . . . . 40
6.15.2. Login-IPv6-Host AVP . . . . . . . . . . . . . . 41
6.15.3. Login-Service AVP . . . . . . . . . . . . . . . 41
6.16. TCP Services . . . . . . . . . . . . . . . . . . . . . . 42
6.16.1. Login-TCP-Port AVP . . . . . . . . . . . . . . 42
6.17. LAT Services . . . . . . . . . . . . . . . . . . . . . . 42
6.17.1. Login-LAT-Service AVP . . . . . . . . . . . . . 42
6.17.2. Login-LAT-Node AVP. . . . . . . . . . . . . . . 43
6.17.3. Login-LAT-Group AVP . . . . . . . . . . . . . . 43
6.17.4. Login-LAT-Port AVP. . . . . . . . . . . . . . . 43
7. NAS Tunneling . . . . . . . . . . . . . . . . . . . . . . . . 44
7.1. Tunneling AVP . . . . . . . . . . . . . . . . . . . . . 44
7.2. Tunnel-Type AVP . . . . . . . . . . . . . . . . . . . . 45
7.3. Tunnel-Medium-Type AVP . . . . . . . . . . . . . . . . . 46
7.4. Tunnel-Client-Endpoint AVP . . . . . . . . . . . . . . . 46
7.5. Tunnel-Server-Endpoint AVP . . . . . . . . . . . . . . . 47
7.6. Tunnel-Password AVP . . . . . . . . . . . . . . . . . . 48
7.7. Tunnel-Private-Group-Id AVP . . . . . . . . . . . . . . 48
6.4. Idle-Timeout AVP . . . . . . . . . . . . . . . . . . . . 32
6.5. Port-Limit AVP . . . . . . . . . . . . . . . . . . . . . 32
6.6. NAS-Filter-Rule AVP . . . . . . . . . . . . . . . . . . 32
6.7. Filter-Id AVP . . . . . . . . . . . . . . . . . . . . . 33
6.8. Configuration-Token AVP . . . . . . . . . . . . . . . . 33
6.9. QoS-Filter-Rule AVP . . . . . . . . . . . . . . . . . . 33
6.10. Framed Access Authorization AVPs . . . . . . . . . . . . 35
6.10.1. Framed-Protocol AVP . . . . . . . . . . . . . . 35
6.10.2. Framed-Routing AVP. . . . . . . . . . . . . . . 35
6.10.3. Framed-MTU AVP. . . . . . . . . . . . . . . . . 35
6.10.4. Framed-Compression AVP. . . . . . . . . . . . . 36
6.11. IP Access Authorization AVPs.. . . . . . . . . . . . . . 36
6.11.1. Framed-IP-Address AVP . . . . . . . . . . . . . 36
6.11.2. Framed-IP-Netmask AVP . . . . . . . . . . . . . 36
6.11.3. Framed-Route AVP. . . . . . . . . . . . . . . . 37
6.11.4. Framed-Pool AVP . . . . . . . . . . . . . . . . 37
6.11.5. Framed-Interface-Id AVP . . . . . . . . . . . . 37
6.11.6. Framed-IPv6-Prefix AVP. . . . . . . . . . . . . 38
6.11.7. Framed-IPv6-Route AVP . . . . . . . . . . . . . 38
6.11.8. Framed-IPv6-Pool AVP. . . . . . . . . . . . . . 38
6.12. IPX Access . . . . . . . . . . . . . . . . . . . . . . . 38
6.12.1. Framed-IPX-Network AVP. . . . . . . . . . . . . 39
6.13. AppleTalk Network Access . . . . . . . . . . . . . . . . 39
6.13.1. Framed-AppleTalk-Link AVP . . . . . . . . . . . 39
6.13.2. Framed-AppleTalk-Network AVP . . . . . . . . . 39
6.13.3. Framed-AppleTalk-Zone AVP . . . . . . . . . . . 40
6.14. AppleTalk Remote Access. . . . . . . . . . . . . . . . . 40
6.14.1. ARAP-Features AVP . . . . . . . . . . . . . . . 40
6.14.2. ARAP-Zone-Access AVP. . . . . . . . . . . . . . 40
6.15. Non-Framed Access Authorization AVPs . . . . . . . . . . 40
6.15.1. Login-IP-Host AVP . . . . . . . . . . . . . . . 40
6.15.2. Login-IPv6-Host AVP . . . . . . . . . . . . . . 41
6.15.3. Login-Service AVP . . . . . . . . . . . . . . . 41
6.16. TCP Services . . . . . . . . . . . . . . . . . . . . . . 42
6.16.1. Login-TCP-Port AVP . . . . . . . . . . . . . . 42
6.17. LAT Services . . . . . . . . . . . . . . . . . . . . . . 42
6.17.1. Login-LAT-Service AVP . . . . . . . . . . . . . 42
6.17.2. Login-LAT-Node AVP. . . . . . . . . . . . . . . 43
6.17.3. Login-LAT-Group AVP . . . . . . . . . . . . . . 43
6.17.4. Login-LAT-Port AVP. . . . . . . . . . . . . . . 43
7. NAS Tunneling . . . . . . . . . . . . . . . . . . . . . . . . 44
7.1. Tunneling AVP . . . . . . . . . . . . . . . . . . . . . 44
7.2. Tunnel-Type AVP . . . . . . . . . . . . . . . . . . . . 45
7.3. Tunnel-Medium-Type AVP . . . . . . . . . . . . . . . . . 46
7.4. Tunnel-Client-Endpoint AVP . . . . . . . . . . . . . . . 46
7.5. Tunnel-Server-Endpoint AVP . . . . . . . . . . . . . . . 47
7.6. Tunnel-Password AVP . . . . . . . . . . . . . . . . . . 48
7.7. Tunnel-Private-Group-Id AVP . . . . . . . . . . . . . . 48
7.8. Tunnel-Assignment-Id AVP . . . . . . . . . . . . . . . . 48
7.9. Tunnel-Preference AVP . . . . . . . . . . . . . . . . . 49
7.10. Tunnel-Client-Auth-Id AVP. . . . . . . . . . . . . . . . 50
7.11. Tunnel-Server-Auth-Id AVP. . . . . . . . . . . . . . . . 50
8. NAS Accounting . . . . . . . . . . . . . . . . . . . . . . . . 50
8.1. Accounting-Input-Octets AVP . . . . . . . . . . . . . . 51
8.2. Accounting-Output-Octets AVP . . . . . . . . . . . . . . 52
8.3. Accounting-Input-Packets AVP . . . . . . . . . . . . . . 52
8.4. Accounting-Output-Packets AVP . . . . . . . . . . . . . 52
8.5. Acct-Session-Time AVP . . . . . . . . . . . . . . . . . 52
8.6. Acct-Authentic AVP . . . . . . . . . . . . . . . . . . . 52
8.7. Accounting-Auth-Method AVP . . . . . . . . . . . . . . . 53
8.8. Acct-Delay-Time . . . . . . . . . . . . . . . . . . . . 53
8.9. Acct-Link-Count . . . . . . . . . . . . . . . . . . . . 54
8.10. Acct-Tunnel-Connection AVP . . . . . . . . . . . . . . . 54
8.11. Acct-Tunnel-Packets-Lost AVP . . . . . . . . . . . . . . 55
9. RADIUS/Diameter Protocol Interactions . . . . . . . . . . . . 55
9.1. RADIUS Request Forwarded as Diameter Request . . . . . . 55
9.1.1. RADIUS Dynamic Authorization Considerations . . 59
9.2. Diameter Request Forwarded as RADIUS Request . . . . . . 60
9.2.1. RADIUS Dynamic Authorization Considerations . . 62
9.3. AVPs Used Only for Compatibility . . . . . . . . . . . . 63
9.3.1. NAS-Identifier AVP. . . . . . . . . . . . . . . 63
9.3.2. NAS-IP-Address AVP. . . . . . . . . . . . . . . 64
9.3.3. NAS-IPv6-Address AVP. . . . . . . . . . . . . . 65
9.3.4. State AVP . . . . . . . . . . . . . . . . . . . 65
9.3.5. Termination-Cause AVP Code Values . . . . . . . 66
9.3.6. Origin-AAA-Protocol . . . . . . . . . . . . . . 68
9.4. Prohibited RADIUS Attributes . . . . . . . . . . . . . . 69
9.5. Translatable Diameter AVPs . . . . . . . . . . . . . . . 69
9.6. RADIUS Vendor-Specific Attributes . . . . . . . . . . . 69
9.6.1. Forwarding a Diameter Vendor Specific AVP as a
RADIUS VSA . . . . . . . . . . . . . . . . . . . 70
9.6.2. 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
10.2.1. Accounting Framed Access AVP Table. . . . . . . 74
10.2.2. 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
7.8. Tunnel-Assignment-Id AVP . . . . . . . . . . . . . . . . 48
7.9. Tunnel-Preference AVP . . . . . . . . . . . . . . . . . 49
7.10. Tunnel-Client-Auth-Id AVP. . . . . . . . . . . . . . . . 50
7.11. Tunnel-Server-Auth-Id AVP. . . . . . . . . . . . . . . . 50
8. NAS Accounting . . . . . . . . . . . . . . . . . . . . . . . . 50
8.1. Accounting-Input-Octets AVP . . . . . . . . . . . . . . 51
8.2. Accounting-Output-Octets AVP . . . . . . . . . . . . . . 52
8.3. Accounting-Input-Packets AVP . . . . . . . . . . . . . . 52
8.4. Accounting-Output-Packets AVP . . . . . . . . . . . . . 52
8.5. Acct-Session-Time AVP . . . . . . . . . . . . . . . . . 52
8.6. Acct-Authentic AVP . . . . . . . . . . . . . . . . . . . 52
8.7. Accounting-Auth-Method AVP . . . . . . . . . . . . . . . 53
8.8. Acct-Delay-Time . . . . . . . . . . . . . . . . . . . . 53
8.9. Acct-Link-Count . . . . . . . . . . . . . . . . . . . . 54
8.10. Acct-Tunnel-Connection AVP . . . . . . . . . . . . . . . 54
8.11. Acct-Tunnel-Packets-Lost AVP . . . . . . . . . . . . . . 55
9. RADIUS/Diameter Protocol Interactions . . . . . . . . . . . . 55
9.1. RADIUS Request Forwarded as Diameter Request . . . . . . 55
9.1.1. RADIUS Dynamic Authorization Considerations . . 59
9.2. Diameter Request Forwarded as RADIUS Request . . . . . . 60
9.2.1. RADIUS Dynamic Authorization Considerations . . 62
9.3. AVPs Used Only for Compatibility . . . . . . . . . . . . 63
9.3.1. NAS-Identifier AVP. . . . . . . . . . . . . . . 63
9.3.2. NAS-IP-Address AVP. . . . . . . . . . . . . . . 64
9.3.3. NAS-IPv6-Address AVP. . . . . . . . . . . . . . 65
9.3.4. State AVP . . . . . . . . . . . . . . . . . . . 65
9.3.5. Termination-Cause AVP Code Values . . . . . . . 66
9.3.6. Origin-AAA-Protocol . . . . . . . . . . . . . . 68
9.4. Prohibited RADIUS Attributes . . . . . . . . . . . . . . 69
9.5. Translatable Diameter AVPs . . . . . . . . . . . . . . . 69
9.6. RADIUS Vendor-Specific Attributes . . . . . . . . . . . 69
9.6.1. Forwarding a Diameter Vendor Specific AVP as a
RADIUS VSA . . . . . . . . . . . . . . . . . . . 70
9.6.2. 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
10.2.1. Accounting Framed Access AVP Table. . . . . . . 74
10.2.2. 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
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 79
13.1. Normative References . . . . . . . . . . . . . . . . . . 79
13.2. Informative References . . . . . . . . . . . . . . . . . 80
14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 83
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 84
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 85
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 79
13.1. Normative References . . . . . . . . . . . . . . . . . . 79
13.2. Informative References . . . . . . . . . . . . . . . . . 80
14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 83
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 84
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 85
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].
本文档介绍网络访问服务器（NAS）环境中用于AAA的Diameter协议应用程序。当与Diameter基本协议[Base]、传输配置文件[DiamTrans]和EAP[DiamEAP]规范结合使用时，此Diameter NAS应用规范满足RFC 2989[AAC协议]和RFC 3169[NASChriteria]中定义的NAS相关要求。
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 Diameter. This is achieved by including the RADIUS attribute space to eliminate the need to perform many attribute translations.
Diameter协议的初始部署预计将包括遗留系统。因此，该应用程序经过精心设计，可以减轻RADIUS和Diameter之间协议转换的负担。这是通过包括半径属性空间来实现的，以消除执行许多属性转换的需要。
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].
本文件中规定的直径应用和半径之间的相互作用适用于所有直径应用。从这个意义上讲，本文档扩展了Base Diameter协议[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.
首先，本文档介绍Diameter NAS应用程序的操作。然后定义Diameter消息命令代码。以下各节列出了这些消息中使用的AVP，按常见用法分组。它们是会话标识、身份验证、授权、隧道和记帐。授权AVP按服务类型进一步细分。与RADIUS的交互和向后兼容性问题将在后面的章节中讨论。
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:
底座直径【底座】规范第1.4节定义了本文件中使用的大部分术语。此外，本应用程序中使用了以下术语和首字母缩略词：
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].
NAS（网络访问服务器）-为用户提供网络访问服务的设备。该服务可以是网络连接或增值服务，例如终端仿真[NASModel]。
PPP (Point-to-Point Protocol) - A multiprotocol serial datalink. PPP is the primary IP datalink used for dial-in NAS connection service [PPP].
PPP（点对点协议）-一种多协议串行数据链路。PPP是用于拨入NAS连接服务[PPP]的主要IP数据链路。
CHAP (Challenge Handshake Authentication Protocol) - An authentication process used in PPP [PPPCHAP].
CHAP（质询握手认证协议）-PPP[PPPCHAP]中使用的认证过程。
PAP (Password Authentication Protocol) - A deprecated PPP authentication process, but often used for backward compatibility [PAP].
PAP（密码认证协议）-一种不推荐使用的PPP认证过程，但通常用于向后兼容[PAP]。
SLIP (Serial Line Interface Protocol) - A serial datalink that only supports IP. A design prior to PPP.
SLIP（串行线路接口协议）-仅支持IP的串行数据链路。PPP之前的设计。
ARAP (Appletalk Remote Access Protocol) - A serial datalink for accessing Appletalk networks [ARAP].
ARAP（Appletalk远程访问协议）-用于访问Appletalk网络的串行数据链路[ARAP]。
IPX (Internet Packet Exchange) - The network protocol used by NetWare networks [IPX].
IPX（Internet数据包交换）-NetWare网络使用的网络协议[IPX]。
LAT (Local Area Transport) - A Digital Equipment Corp. LAN protocol for terminal services [LAT].
LAT（局域网传输）-一种用于终端服务的数字设备公司局域网协议[LAT]。
VPN (Virtual Private Network) - In this document, this term is used to describe access services that use tunneling methods.
VPN（虚拟专用网络）-在本文档中，该术语用于描述使用隧道方法的访问服务。
In this document, the key words "MAY", "MUST", "MUST NOT", "OPTIONAL", "RECOMMENDED", "SHOULD", and "SHOULD NOT" are to be interpreted as described in [Keywords].
在本文件中，关键词“可能”、“必须”、“不得”、“可选”、“建议”、“应该”和“不应该”应按照[关键词]中所述进行解释。
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.
符合本规范的Diameter应用程序必须通过在功能交换请求（CER）、AA请求（AAR）和AA应答（AAA）消息的身份验证应用程序Id中包含一（1）个值来公布支持。所有其他消息由[BASE]定义，并使用基本应用程序id值。
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.
新呼叫或服务连接到达网络访问服务器（NAS）的端口时，将启动Diameter NAS消息交换。有关呼叫、用户身份和用户身份验证信息的信息被打包成Diameter AA Request（AAR）消息并发送到服务器。
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.
服务器处理该信息并以包含NAS授权信息的Diameter AA应答（AAA）消息或故障代码（结果代码AVP）响应。DIAMETER\u MULTI\u ROUND\u AUTH的值表示额外的身份验证交换，在事务完成之前可以交换多个AAR和AAA消息。
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.
根据身份验证请求类型AVP，Diameter协议只允许包含来自客户端的身份验证信息的授权请求。该功能超出了[RADIUS]第5.6节所述的呼叫检查功能，因为不需要访问决策。因此，响应仅授权请求时无法启动服务，而不会引入严重的安全漏洞。
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 gateway. 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.
由于RADIUS中不存在等效功能，因此来自实施Diameter的NAS的仅授权请求可能无法通过Diameter/RADIUS网关轻松转换为等效RADIUS消息。例如，当Diameter仅授权请求无法转换为RADIUS呼叫检查时，Diameter/RADIUS网关需要向RADIUS访问请求添加身份验证信息。收到访问回复后，Diameter/RADIUS网关需要放弃访问决定（接受/拒绝）。目前尚不清楚这些翻译是否可以在不增加重大安全漏洞的情况下完成。
When the authentication or authorization exchange completes successfully, the NAS application SHOULD start a session context. If the Result-Code of DIAMETER_MULTI_ROUND_AUTH is returned, the exchange continues until a success or error is returned.
当身份验证或授权交换成功完成时，NAS应用程序应启动会话上下文。如果返回DIAMETER\u MULTI\u ROUND\u AUTH的结果代码，则交换将继续，直到返回成功或错误。
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.
如果记帐处于活动状态，应用程序还必须发送记帐消息[BASE]。为新会话发送记帐记录类型的开始记录。如果会话无法启动，则会发送带有所述故障原因的事件记录消息。
Note that the return of an unsupportable Accounting-Realtime-Required value [BASE] would result in a failure to establish the session.
请注意，返回不支持的Accounting Realtime Required值[BASE]将导致建立会话失败。
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.
Diameter基本协议允许定期重新验证和/或重新验证用户。在这种情况下，AAR消息中的会话Id AVP必须与原始身份验证/授权消息中的会话Id AVP相同。
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.
Diameter服务器通过授权生存期AVP[BASE]通知NAS重新验证或重新验证之前允许的最长时间。NAS可以在结束前重新验证和/或重新验证，但NAS必须在授权生存期AVP提供的期限结束时重新验证和/或重新验证。重新验证交换失败将终止服务。
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].
此外，Diameter服务器可以向NAS发出未经请求的重新身份验证和/或重新身份验证请求（例如，重新身份验证请求（RAR）消息[BASE]）。收到此类消息后，NAS必须使用重新验证应答（RAA）消息[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.
如果RAR正确识别活动会话，NAS将启动新的本地重新身份验证或授权序列，如重新身份验证请求类型值所示。这将导致NAS使用现有会话Id发送新的AAR消息。服务器将使用AAA消息进行响应，以指定新的服务参数。
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-sessions. A service may also use a different Session-Id value for accounting (see [BASE] section 9.6).
如果记帐处于活动状态，则每次身份验证或授权更改都应生成记帐消息。如果NAS服务是先前用户上下文的延续，则表示新会话属性和累积状态的临时_记录的记帐记录类型将是合适的。如果NAS检测到新用户或授权的重大更改，则服务可能会发送两条类型为STOP_RECORD和START_RECORD的消息。记帐可以更改子会话标识符（Acct会话ID或Acct子会话ID）以指示这些子会话。服务也可以使用不同的会话Id值进行记帐（请参见[BASE]第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会话ID AVP值必须用于生成STR消息。
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.
当NAS接收到客户端正在断开用户会话的指示（例如，接收到LCP Terminate）或管理命令时，NAS必须向其Diameter服务器发出会话终止请求（STR）[BASE]。这将确保适当释放服务器上维护的任何资源。
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.
此外，如果识别的会话处于活动状态，则接收中止会话请求（ASR）[BASE]的NAS必须发出ASA，并断开PPP（或隧道）会话。
If accounting is active, an Accounting STOP_RECORD message [BASE] MUST be sent upon termination of the session context.
如果记帐处于活动状态，则会话上下文终止时必须发送记帐停止记录消息[BASE]。
More information on Diameter Session Termination is included in [BASE] sections 8.4 and 8.5.
有关Diameter会话终止的更多信息，请参见[BASE]第8.4节和第8.5节。
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:
本节定义了符合本规范的所有Diameter实现必须支持的Diameter消息命令代码[BASE]值。命令代码如下：
Command-Name Abbrev. Code Reference
-------------------------------------------------------
AA-Request AAR 265 3.1
AA-Answer AAA 265 3.2
Re-Auth-Request RAR 258 3.3
Re-Auth-Answer RAA 258 3.4
Session-Termination-Request STR 275 3.5
Session-Termination-Answer STA 275 3.6
Abort-Session-Request ASR 274 3.7
Abort-Session-Answer ASA 274 3.8
Accounting-Request ACR 271 3.9
Accounting-Answer ACA 271 3.10
Command-Name Abbrev. Code Reference
-------------------------------------------------------
AA-Request AAR 265 3.1
AA-Answer AAA 265 3.2
Re-Auth-Request RAR 258 3.3
Re-Auth-Answer RAA 258 3.4
Session-Termination-Request STR 275 3.5
Session-Termination-Answer STA 275 3.6
Abort-Session-Request ASR 274 3.7
Abort-Session-Answer ASA 274 3.8
Accounting-Request ACR 271 3.9
Accounting-Answer ACA 271 3.10
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 [BASE]. The recommended value for most RADIUS interoperabily situations is AUTHORIZE_AUTHENTICATE.
AA请求（AAR）通过将命令代码字段设置为265和命令标志字段中的“R”位来指示，用于为给定NAS用户请求身份验证和/或授权。请求类型通过身份验证请求类型AVP[BASE]标识。大多数RADIUS互操作情况的建议值为AUTHORIZE\u 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 6.
如果请求身份验证，则应显示用户名属性，以及携带密码信息的任何附加身份验证AVP。授权请求应仅包括执行授权的信息，如用户名、被叫站Id或主叫站Id AVPs。所有请求都应包含唯一标识呼叫源的AVP，如原始主机和NAS端口。某些网络可能使用不同的AVP进行授权。授权请求将包括第6节中定义的一些AVP。
It is possible for a single session to be authorized first and then for an authentication request to follow.
可以先对单个会话进行授权，然后再进行身份验证请求。
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.
此AA请求消息可能是多轮身份验证交换的结果，当收到AA应答消息且结果代码AVP设置为DIAMETER_multi_round_AUTH时，会发生多轮身份验证交换。应发送后续AAR消息，其中包含用户对提示的响应的用户密码AVP，并且必须包含AAA消息中存在的任何状态AVP。
Message Format
<AA-Request> ::= < Diameter Header: 265, REQ, PXY >
< Session-Id >
{ 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 ]
[ State ]
[ 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 ]
Message Format
<AA-Request> ::= < Diameter Header: 265, REQ, PXY >
< Session-Id >
{ 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 ]
[ State ]
[ 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 ]
* [ 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 ]
* [ AVP ]
* [ 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 ]
* [ AVP ]
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. It is sent in response to the AA-Request (AAR) message. If authorization was requested, a successful response will include the authorization AVPs appropriate for the service being provided, as defined in section 6.
AA应答（AAA）消息通过将命令代码字段设置为265并清除命令标志字段中的“R”位来指示。它是响应AA请求（AAR）消息而发送的。如果请求授权，成功响应将包括适用于所提供服务的授权AVP，如第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.
对于需要多次往返的身份验证交换，服务器必须将结果代码AVP设置为DIAMETER\u MULTI\u round\u AUTH。具有该结果代码的AAA消息可以包括一个或多个回复消息，并且可以包括零个或一个状态AVP。
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. For example, this capability can be achieved in PPP via PAP. If the 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.
如果存在回复消息AVP，则网络访问服务器应将文本发送到用户的客户端以向用户显示，指示客户端提示用户进行响应。例如，这种能力可以通过PAP在PPP中实现。如果访问客户端无法提示用户进行新的响应，则必须将带有回复消息AVP的AA应答（AAA）视为错误，并拒绝访问。
Message Format
消息格式
<AA-Answer> ::= < Diameter Header: 265, PXY >
< Session-Id >
{ Auth-Application-Id }
{ Auth-Request-Type }
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ User-Name ]
[ Service-Type ]
* [ Class ]
* [ Configuration-Token ]
[ Acct-Interim-Interval ]
<AA-Answer> ::= < Diameter Header: 265, PXY >
< Session-Id >
{ Auth-Application-Id }
{ Auth-Request-Type }
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ User-Name ]
[ Service-Type ]
* [ Class ]
* [ Configuration-Token ]
[ Acct-Interim-Interval ]
[ 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 ]
[ State ]
* [ 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 ]
[ 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 ]
[ State ]
* [ 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 ]
[ Login-TCP-Port ]
* [ NAS-Filter-Rule ]
* [ QoS-Filter-Rule ]
* [ Tunneling ]
* [ Redirect-Host ]
[ Redirect-Host-Usage ]
[ Redirect-Max-Cache-Time ]
* [ Proxy-Info ]
* [ AVP ]
[ Login-TCP-Port ]
* [ NAS-Filter-Rule ]
* [ QoS-Filter-Rule ]
* [ Tunneling ]
* [ Redirect-Host ]
[ Redirect-Host-Usage ]
[ Redirect-Max-Cache-Time ]
* [ Proxy-Info ]
* [ AVP ]
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].
Diameter服务器可以通过发出重新身份验证请求（RAR）消息[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.
例如，对于预付费服务，最初授权会话的Diameter服务器可能需要确认用户仍在使用服务。
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.
如果NAS接收到会话Id等于当前活动会话的RAR消息以及包含身份验证的重新身份验证类型，则如果服务支持此特定功能，则必须向用户发起重新身份验证。
Message Format
消息格式
<RA-Request> ::= < Diameter Header: 258, REQ, PXY >
< Session-Id >
{ 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 ]
<RA-Request> ::= < Diameter Header: 258, REQ, PXY >
< Session-Id >
{ 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 ]
[ Called-Station-Id ]
[ Calling-Station-Id ]
[ Originating-Line-Info ]
[ Acct-Session-Id ]
[ Acct-Multi-Session-Id ]
[ State ]
* [ Class ]
[ Reply-Message ]
* [ Proxy-Info ]
* [ Route-Record ]
* [ AVP ]
[ Called-Station-Id ]
[ Calling-Station-Id ]
[ Originating-Line-Info ]
[ Acct-Session-Id ]
[ Acct-Multi-Session-Id ]
[ State ]
* [ Class ]
[ Reply-Message ]
* [ Proxy-Info ]
* [ Route-Record ]
* [ AVP ]
The Re-Auth-Answer (RAA) message [BASE] is sent in response to the RAR. The Result-Code AVP MUST be present and indicates the disposition of the request.
发送重新验证应答（RAA）消息[BASE]以响应RAR。结果代码AVP必须存在，并指示请求的处理。
A successful RAA transaction MUST be followed by an AAR message.
成功的RAA事务之后必须有AAR消息。
Message Format
消息格式
<RA-Answer> ::= < Diameter Header: 258, PXY >
< Session-Id >
{ 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 ]
[ State ]
* [ Class ]
* [ Reply-Message ]
[ Prompt ]
* [ Proxy-Info ]
* [ AVP ]
<RA-Answer> ::= < Diameter Header: 258, PXY >
< Session-Id >
{ 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 ]
[ State ]
* [ Class ]
* [ Reply-Message ]
[ Prompt ]
* [ Proxy-Info ]
* [ AVP ]
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.
NAS发送会话终止请求（STR）消息[BASE]，通知Diameter服务器正在终止经过身份验证和/或授权的会话。
Message Format
消息格式
<ST-Request> ::= < Diameter Header: 275, REQ, PXY >
< Session-Id >
{ 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 ]
* [ AVP ]
<ST-Request> ::= < Diameter Header: 275, REQ, PXY >
< Session-Id >
{ 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 ]
* [ AVP ]
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 serviced.
Diameter服务器发送会话终止应答（STA）消息[BASE]，以确认会话已终止的通知。结果代码AVP必须存在，并且可能包含在维修STR时发生错误的指示。
Upon sending or receiving the STA, the Diameter Server MUST release all resources for the session indicated by the Session-Id AVP. Any intermediate server in the Proxy-Chain MAY also release any resources, if necessary.
发送或接收STA后，Diameter服务器必须释放会话Id AVP指示的会话的所有资源。如有必要，代理链中的任何中间服务器也可以释放任何资源。
Message Format
消息格式
<ST-Answer> ::= < Diameter Header: 275, PXY >
< Session-Id >
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ User-Name ]
* [ Class ]
[ Error-Message ]
[ Error-Reporting-Host ]
<ST-Answer> ::= < Diameter Header: 275, PXY >
< Session-Id >
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ User-Name ]
* [ Class ]
[ Error-Message ]
[ Error-Reporting-Host ]
* [ Failed-AVP ]
[ Origin-AAA-Protocol ]
[ Origin-State-Id ]
* [ Redirect-Host ]
[ Redirect-Host-Usase ]
[ Redirect-Max-Cache-Time ]
* [ Proxy-Info ]
* [ AVP ]
* [ Failed-AVP ]
[ Origin-AAA-Protocol ]
[ Origin-State-Id ]
* [ Redirect-Host ]
[ Redirect-Host-Usase ]
[ Redirect-Max-Cache-Time ]
* [ Proxy-Info ]
* [ AVP ]
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.
任何服务器都可以向提供会话服务的NAS发送中止会话请求（ASR）消息[BASE]，请求停止会话Id标识的会话。
Message Format
消息格式
<AS-Request> ::= < Diameter Header: 274, REQ, PXY >
< Session-Id >
{ 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 ]
[ State ]
* [ Class ]
* [ Reply-Message ]
* [ Proxy-Info ]
* [ Route-Record ]
* [ AVP ]
<AS-Request> ::= < Diameter Header: 274, REQ, PXY >
< Session-Id >
{ 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 ]
[ State ]
* [ Class ]
* [ Reply-Message ]
* [ Proxy-Info ]
* [ Route-Record ]
* [ AVP ]
The ASA message [BASE] is sent in response to the ASR. The Result-Code AVP MUST be present and indicates the disposition of the request.
ASA消息[BASE]被发送以响应ASR。结果代码AVP必须存在，并指示请求的处理。
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.
如果ASR中由会话Id标识的会话已成功终止，则结果代码将设置为DIAMETER\u SUCCESS。如果会话当前未处于活动状态，则结果代码将设置为DIAMETER\u UNKNOWN\u session\u ID。如果访问设备未因任何其他原因停止会话，则结果代码将设置为DIAMETER\u UNABLE\u to\u Compliance。
Message Format
消息格式
<AS-Answer> ::= < Diameter Header: 274, PXY >
< Session-Id >
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ User-Name ]
[ Origin-AAA-Protocol ]
[ Origin-State-Id ]
[ State]
[ Error-Message ]
[ Error-Reporting-Host ]
* [ Failed-AVP ]
* [ Redirected-Host ]
[ Redirected-Host-Usage ]
[ Redirected-Max-Cache-Time ]
* [ Proxy-Info ]
* [ AVP ]
<AS-Answer> ::= < Diameter Header: 274, PXY >
< Session-Id >
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ User-Name ]
[ Origin-AAA-Protocol ]
[ Origin-State-Id ]
[ State]
[ Error-Message ]
[ Error-Reporting-Host ]
* [ Failed-AVP ]
* [ Redirected-Host ]
[ Redirected-Host-Usage ]
[ Redirected-Max-Cache-Time ]
* [ Proxy-Info ]
* [ AVP ]
The ACR message [BASE] is sent by the NAS to report its session information to a target server downstream.
NAS发送ACR消息[BASE]以向下游目标服务器报告其会话信息。
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.
必须存在账户应用程序Id或供应商特定应用程序Id AVP。如果存在供应商特定的应用程序Id分组AVP，则其中必须包含一个Acct应用程序Id。
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.
必要时，必须假设基础中列出的AVP存在。NAS特定于服务的计费AVP应如第8节和本规范其余部分所述提供。
Message Format
消息格式
<AC-Request> ::= < Diameter Header: 271, REQ, PXY >
< Session-Id >
{ 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 ]
<AC-Request> ::= < Diameter Header: 271, REQ, PXY >
< Session-Id >
{ 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 ]
[ 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 ]
* [ AVP ]
[ 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 ]
* [ AVP ]
The ACA message [BASE] is used to acknowledge an Accounting-Request command. 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 well.
ACA消息[BASE]用于确认记帐请求命令。记帐应答命令包含与请求相同的会话Id。如果记帐请求受端到端安全保护，则相应的ACA消息也必须受到保护。
Only the target Diameter Server or home Diameter Server SHOULD respond with the Accounting-Answer command.
只有目标Diameter服务器或home Diameter服务器应使用记帐应答命令进行响应。
Either Acct-Application-Id or Vendor-Specific-Application-Id AVPs MUST be present, as it was in the request.
账户应用程序Id或特定于供应商的应用程序Id AVPs必须与请求中一样存在。
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.
必要时，必须假设基础中列出的AVP存在。NAS特定于服务的计费AVP应如第8节和本规范其余部分所述提供。
Message Format
消息格式
<AC-Answer> ::= < Diameter Header: 271, PXY >
< Session-Id >
{ 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 ]
* [ AVP ]
<AC-Answer> ::= < Diameter Header: 271, PXY >
< Session-Id >
{ 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 ]
* [ AVP ]
Diameter reserves the AVP Codes 0 - 255 for RADIUS functions that are implemented in Diameter.
Diameter为在Diameter中实现的RADIUS函数保留AVP代码0-255。
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
新加入Diameter的AVP的代码值为256或更大。包含这些AVP之一的Diameter消息可能表示RADIUS环境中不存在的功能，并可能导致互操作性
issues, should the request traverse an AAA system that only supports the RADIUS protocol.
问题，如果请求通过仅支持RADIUS协议的AAA系统。
Some RADIUS attributes are not allowed or supported directly in Diameter. See section 9 for more information.
直径中不允许或不直接支持某些半径属性。更多信息请参见第9节。
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.
本节包含特定于NAS Diameter应用程序的AVP，这些应用程序用于识别呼叫和会话上下文及状态信息。根据请求，此信息允许服务器限定会话。
These AVPs are used in addition to the Base AVPs of:
这些AVP是对以下基本AVP的补充：
Session-Id Auth-Application-Id Origin-Host Origin-Realm Auth-Request-Type Termination-Cause
会话Id身份验证应用程序Id源主机源域身份验证请求类型终止原因
The following table describes the session level AVPs; their AVP Code values, types, and possible flag values; and whether the AVP MAY be encrypted.
下表描述了会话级AVP；其AVP代码值、类型和可能的标志值；以及AVP是否可以被加密。
+---------------------+
| AVP Flag rules |
|----+-----+----+-----|----+
AVP Section | | |SHLD| MUST| |
Attribute Name Code Defined Value Type |MUST| MAY | NOT| NOT|Encr|
-----------------------------------------|----+-----+----+-----|----|
NAS-Port 5 4.2 Unsigned32 | M | P | | V | Y |
NAS-Port-Id 87 4.3 UTF8String | M | P | | V | Y |
NAS-Port-Type 61 4.4 Enumerated | M | P | | V | Y |
Called-Station-Id 30 4.5 UTF8String | M | P | | V | Y |
Calling-Station- 31 4.6 UTF8String | M | P | | V | Y |
Id | | | | | |
Connect-Info 77 4.7 UTF8String | M | P | | V | Y |
Originating-Line- 94 4.8 OctetString| | M,P | | V | Y |
Info | | | | | |
Reply-Message 18 4.9 UTF8String | M | P | | V | Y |
-----------------------------------------|----+-----+----+-----|----|
+---------------------+
| AVP Flag rules |
|----+-----+----+-----|----+
AVP Section | | |SHLD| MUST| |
Attribute Name Code Defined Value Type |MUST| MAY | NOT| NOT|Encr|
-----------------------------------------|----+-----+----+-----|----|
NAS-Port 5 4.2 Unsigned32 | M | P | | V | Y |
NAS-Port-Id 87 4.3 UTF8String | M | P | | V | Y |
NAS-Port-Type 61 4.4 Enumerated | M | P | | V | Y |
Called-Station-Id 30 4.5 UTF8String | M | P | | V | Y |
Calling-Station- 31 4.6 UTF8String | M | P | | V | Y |
Id | | | | | |
Connect-Info 77 4.7 UTF8String | M | P | | V | Y |
Originating-Line- 94 4.8 OctetString| | M,P | | V | Y |
Info | | | | | |
Reply-Message 18 4.9 UTF8String | M | P | | V | Y |
-----------------------------------------|----+-----+----+-----|----|
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 the user. Note that "port" is meant in its sense as a service connection on the NAS, not as an IP protocol identifier.
NAS端口AVP（AVP代码5）的类型为Unsigned32，包含验证用户身份的NAS的物理或虚拟端口号。请注意，“端口”是指NAS上的服务连接，而不是IP协议标识符。
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在其端口之间存在差异，则NAS端口或NAS端口Id（AVP代码87）应出现在AA请求（AAR）命令中。
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 user. Note that "port" is meant in its sense as a service connection on the NAS, not as an IP protocol identifier.
NAS端口Id AVP（AVP代码87）为UTF8String类型，由标识NAS端口的ASCII文本组成，用于验证用户身份。请注意，“端口”是指NAS上的服务连接，而不是IP协议标识符。
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 ports.
如果NAS在其端口之间存在差异，则在AA请求（AAR）命令中应显示NAS端口或NAS端口Id。NAS端口Id供无法方便地对其端口进行编号的NASE使用。
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 user. This AVP SHOULD be present if the NAS uses the same NAS-Port number ranges for different service types concurrently.
NAS端口类型AVP（AVP代码61）属于枚举类型，并且包含NAS对用户进行身份验证的端口类型。如果NAS同时为不同的服务类型使用相同的NAS端口号范围，则应存在此AVP。
The supported values are defined in [RADIUSTypes]. The following list is informational and subject to change by the IANA.
支持的值在[RADIUSTypes]中定义。以下列表仅供参考，IANA可能会对其进行更改。
0 Async 1 Sync 2 ISDN Sync 3 ISDN Async V.120 4 ISDN Async V.110 5 Virtual 6 PIAFS 7 HDLC Clear Channel 8 X.25 9 X.75 10 G.3 Fax 11 SDSL - Symmetric DSL 12 ADSL-CAP - Asymmetric DSL, Carrierless Amplitude Phase Modulation 13 ADSL-DMT - Asymmetric DSL, Discrete Multi-Tone 14 IDSL - ISDN Digital Subscriber Line
0异步1同步2 ISDN同步3 ISDN异步V.120 4 ISDN异步V.110 5虚拟6 PIAFS 7 HDLC清晰通道8 X.25 9 X.75 10 G.3传真11 SDSL-对称DSL 12 ADSL-CAP-非对称DSL，无载波幅相调制13 ADSL-DMT-非对称DSL，离散多音14 IDSL-ISDN数字用户线
15 Ethernet
16 xDSL - Digital Subscriber Line of unknown type
17 Cable
18 Wireless - Other
19 Wireless - IEEE 802.11
20 Token-Ring [RAD802.1X]
21 FDDI [RAD802.1X]
22 Wireless - CDMA2000
23 Wireless - UMTS
24 Wireless - 1X-EV
25 IAPP [IEEE 802.11f]
15 Ethernet
16 xDSL - Digital Subscriber Line of unknown type
17 Cable
18 Wireless - Other
19 Wireless - IEEE 802.11
20 Token-Ring [RAD802.1X]
21 FDDI [RAD802.1X]
22 Wireless - CDMA2000
23 Wireless - UMTS
24 Wireless - 1X-EV
25 IAPP [IEEE 802.11f]
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.
被叫站Id AVP（AVP代码30）为UTF8String类型，允许NAS发送描述用户在请求中联系的第2层地址的ASCII字符串。对于拨号接入，这可以是通过使用拨号号码识别（DNIS）或类似技术获得的电话号码。请注意，这可能与电话号码不同。为了与IEEE 802访问一起使用，被叫站Id可能包含一个MAC地址，其格式如[RAD802.1X]所述。它只应出现在身份验证和/或授权请求中。
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.
如果身份验证请求类型AVP设置为仅授权，并且用户名AVP不存在，Diameter服务器可以基于此字段执行授权。NAS可使用此命令请求是否应基于DNI应答呼叫。
The codification of this field's allowed usage range is outside the scope of this specification.
此字段允许使用范围的编码不在本规范的范围内。
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.
呼叫站Id AVP（AVP代码31）为UTF8String类型，允许NAS发送描述用户在请求中连接的第2层地址的ASCII字符串。对于拨号接入，这是使用自动号码识别（ANI）或类似技术拨打的电话号码。为了与IEEE 802接入一起使用，呼叫站Id AVP可以包含MAC地址，其格式如[RAD802.1X]中所述。它只应出现在身份验证和/或授权请求中。
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.)
如果身份验证请求类型AVP设置为仅授权，并且用户名AVP不存在，Diameter服务器可以基于此字段执行授权。NAS可使用此功能请求是否应根据第2层地址（ANI、MAC地址等）应答呼叫
The codification of this field's allowed usage range is outside the scope of this specification.
此字段允许使用范围的编码不在本规范的范围内。
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.
连接信息AVP（AVP代码77）为UTF8String类型，在AA请求消息或ACR停止消息中发送。当在访问请求中发送时，它指示用户连接的性质。连接速度应包含在消息中第一个连接信息AVP的开头。如果发送和接收连接速度不同，则两种连接速度都可以包含在第一个AVP中，首先列出传输速度（NAS调制解调器的传输速度），然后是斜杠（/），然后是接收速度，然后是其他可选信息。
For example: "28800 V42BIS/LAPM" or "52000/31200 V90"
For example: "28800 V42BIS/LAPM" or "52000/31200 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.
计费请求数据包中可能存在多个连接信息属性，以适应ITU的预期努力，使调制解调器以可能超过252个八位字节的标准格式报告更多的连接信息。
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.
如果在ACR STOP中发送，此属性可能会汇总与会话质量相关的统计信息。例如，在IEEE 802.11中，Connect Info属性可以包含关于链路层重传次数的信息。此属性的确切格式是特定于实现的。
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.
始发线路信息AVP（AVP代码94）为OctetString类型，由NAS系统发送，以传达关于来自SS7系统的呼叫来源的信息。
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.
发起线路信息（OLI）元素表示发起呼叫的线路的性质和/或特征（例如，付费电话、酒店、蜂窝电话）。电话公司开始向其客户提供OLI，作为主要费率接口（PRI）的一种选择。除了主叫站Id和主叫站Id属性外，Internet服务提供商（ISP）还可以使用OLI来区分客户呼叫和定义不同的服务。
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].
值字段包含两个八位字节（00-99）。ANSI T1.113和BELLCORE 394可用于获取有关这些值及其使用的附加信息。有关当前指定值的详细信息，请参见[ANITypes]。
Value Description
------------------------------------------------------------
00 Plain Old Telephone Service (POTS)
01 Multiparty Line (more than 2)
02 ANI Failure
03 ANI Observed
04 ONI Observed
05 ANI Failure Observed
06 Station Level Rating
07 Special Operator Handling Required
08 InterLATA Restricted
10 Test Call
20 Automatic Identified Outward Dialing (AIOD)
23 Coin or Non-Coin
24 Toll Free Service (Non-Pay Origination)
25 Toll Free Service (Pay Origination)
27 Toll Free Service (Coin Control Origination)
29 Prison/Inmate Service
30-32 Intercept
30 Intercept (Blank)
31 Intercept (Trouble)
32 Intercept (Regular)
34 Telco Operator Handled Call
40-49 Unrestricted Use
52 Outward Wide Area Telecommunications Service (OUTWATS)
60 Telecommunications Relay Service (TRS)(Unrestricted)
61 Cellular/Wireless PCS (Type 1)
62 Cellular/Wireless PCS (Type 2)
63 Cellular/Wireless PCS (Roaming)
66 TRS (Hotel)
67 TRS (Restricted)
70 Pay Station, No Coin Control
93 Access for Private Virtual Network Service
Value Description
------------------------------------------------------------
00 Plain Old Telephone Service (POTS)
01 Multiparty Line (more than 2)
02 ANI Failure
03 ANI Observed
04 ONI Observed
05 ANI Failure Observed
06 Station Level Rating
07 Special Operator Handling Required
08 InterLATA Restricted
10 Test Call
20 Automatic Identified Outward Dialing (AIOD)
23 Coin or Non-Coin
24 Toll Free Service (Non-Pay Origination)
25 Toll Free Service (Pay Origination)
27 Toll Free Service (Coin Control Origination)
29 Prison/Inmate Service
30-32 Intercept
30 Intercept (Blank)
31 Intercept (Trouble)
32 Intercept (Regular)
34 Telco Operator Handled Call
40-49 Unrestricted Use
52 Outward Wide Area Telecommunications Service (OUTWATS)
60 Telecommunications Relay Service (TRS)(Unrestricted)
61 Cellular/Wireless PCS (Type 1)
62 Cellular/Wireless PCS (Type 2)
63 Cellular/Wireless PCS (Roaming)
66 TRS (Hotel)
67 TRS (Restricted)
70 Pay Station, No Coin Control
93 Access for Private Virtual Network Service
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 success. When found in an AAA message with a Result-Code other than DIAMETER_SUCCESS, the AVP contains a failure message.
回复消息AVP（AVP代码18）为UTF8String类型，包含可向用户显示的文本。当在AA应答消息中使用成功结果代码AVP时，表示成功。当在AAA消息中发现结果代码不是DIAMETER_SUCCESS时，AVP包含失败消息。
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 response.
回复消息AVP可以指示在另一个AA请求尝试之前提示用户的对话框文本。当在结果代码为DIAMETER\u MULTI\u ROUND\u AUTH的AA应答或在重新认证请求消息中使用时，它可能包含提示用户响应的对话框文本。
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.
可能会包含多条回复消息，如果显示了任何回复消息，则必须按照在Diameter消息中显示的顺序显示回复消息。
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].
本节定义了在Diameter协议中承载身份验证信息所需的AVP。此处定义的功能通过更可靠、更安全的传输提供类似RADIUS的AAA服务，如基本协议[base]中所定义。
The following table describes the AVPs; their AVP Code values, types, and possible flag values, and whether the AVP MAY be encrypted.
下表描述了AVP；他们的AVP代码值、类型和可能的标志值，以及AVP是否可以加密。
+---------------------+
| AVP Flag rules |
|----+-----+----+-----|----+
AVP Section | | |SHLD| MUST| |
Attribute Name Code Defined Value Type |MUST| MAY | NOT| NOT|Encr|
-----------------------------------------|----+-----+----+-----|----|
User-Password 2 5.1 OctetString| M | P | | V | Y |
Password-Retry 75 5.2 Unsigned32 | M | P | | V | Y |
Prompt 76 5.3 Enumerated | M | P | | V | Y |
CHAP-Auth 402 5.4 Grouped | M | P | | V | Y |
CHAP-Algorithm 403 5.5 Enumerated | M | P | | V | Y |
CHAP-Ident 404 5.6 OctetString| M | P | | V | Y |
CHAP-Response 405 5.7 OctetString| M | P | | V | Y |
CHAP-Challenge 60 5.8 OctetString| M | P | | V | Y |
ARAP-Password 70 5.9 OctetString| M | P | | V | Y |
ARAP-Challenge- 84 5.10 OctetString| M | P | | V | Y |
Response | | | | | |
ARAP-Security 73 5.11 Unsigned32 | M | P | | V | Y |
ARAP-Security- 74 5.12 OctetString| M | P | | V | Y |
Data | | | | | |
-----------------------------------------|----+-----+----+-----|----|
+---------------------+
| AVP Flag rules |
|----+-----+----+-----|----+
AVP Section | | |SHLD| MUST| |
Attribute Name Code Defined Value Type |MUST| MAY | NOT| NOT|Encr|
-----------------------------------------|----+-----+----+-----|----|
User-Password 2 5.1 OctetString| M | P | | V | Y |
Password-Retry 75 5.2 Unsigned32 | M | P | | V | Y |
Prompt 76 5.3 Enumerated | M | P | | V | Y |
CHAP-Auth 402 5.4 Grouped | M | P | | V | Y |
CHAP-Algorithm 403 5.5 Enumerated | M | P | | V | Y |
CHAP-Ident 404 5.6 OctetString| M | P | | V | Y |
CHAP-Response 405 5.7 OctetString| M | P | | V | Y |
CHAP-Challenge 60 5.8 OctetString| M | P | | V | Y |
ARAP-Password 70 5.9 OctetString| M | P | | V | Y |
ARAP-Challenge- 84 5.10 OctetString| M | P | | V | Y |
Response | | | | | |
ARAP-Security 73 5.11 Unsigned32 | M | P | | V | Y |
ARAP-Security- 74 5.12 OctetString| M | P | | V | Y |
Data | | | | | |
-----------------------------------------|----+-----+----+-----|----|
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.
用户密码AVP（AVP代码2）为OctetString类型，包含待验证用户的密码或用户在多轮验证交换中的输入。
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
用户密码AVP包含用户密码或一次性密码，因此表示敏感信息。根据[BASE]中的要求，Diameter消息使用IPsec或TLS进行加密。除非此AVP用于一次性密码，否则用户密码AVP
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].
不应在不受信任的代理环境中使用，而应使用端到端安全技术对其进行加密，如建议的CMS安全[DiamCMS]。
The clear-text password (prior to encryption) MUST NOT be longer than 128 bytes in length.
明文密码（加密前）的长度不得超过128字节。
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.
密码重试AVP（AVP代码75）的类型为Unsigned32，如果结果代码指示身份验证失败，则可能包含在AA应答中。此AVP的值表示在断开连接之前允许用户进行多少次身份验证尝试。该AVP主要用于帧协议AVP（见第6.10.1节）设置为ARAP时使用。
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 echoed.
提示AVP（AVP代码76）属于枚举类型，可能出现在AA应答消息中。如果存在，NAS将使用它来确定输入时是否应回显用户的响应。
The supported values are listed in [RADIUSTypes]. The following list is informational:
支持的值列在[RADIUSTypes]中。以下列表仅供参考：
0 No Echo 1 Echo
0无回音1回音
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]. If the 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认证AVP（AVP代码402）属于分组类型，并且包含使用PPP质询握手认证协议（CHAP）[PPPCHAP]认证用户所需的信息。如果在消息中找到CHAP验证AVP，则CHAP质询AVP也必须存在。包含CHAP响应的可选AVP取决于CHAP算法AVP的值。分组AVP具有以下ABNF语法：
CHAP-Auth ::= < AVP Header: 402 >
{ CHAP-Algorithm }
{ CHAP-Ident }
[ CHAP-Response ]
* [ AVP ]
CHAP-Auth ::= < AVP Header: 402 >
{ CHAP-Algorithm }
{ CHAP-Ident }
[ CHAP-Response ]
* [ 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算法AVP（AVP代码403）属于枚举类型，并且包含用于计算CHAP响应[PPPCHAP]的算法标识符。当前支持以下值：
CHAP with MD5 5 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 with MD5 5使用[PPPCHAP]中描述的程序计算CHAP响应。此算法要求CHAP响应AVP必须存在于CHAP Auth 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标识AVP（AVP代码404）为八进制字符串类型，包含用于计算CHAP响应[PPPCHAP]的1个八进制CHAP标识。
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响应AVP（AVP代码405）是OctetString类型，并且包含用户响应CHAP质询[PPPCHAP]而提供的16个八位字节的认证数据。
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].
CHAP质询AVP（AVP代码60）为OctetString类型，包含NAS发送给CHAP对等方[PPPCHAP]的CHAP质询。
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密码AVP（AVP代码70）为OctetString类型，仅当消息中包含帧协议AVP（见第6.10.1节）并设置为ARAP时才存在。如果存在用户密码或CHAP Auth AVP，则此AVP不得存在。有关此AVP内容的更多信息，请参阅[RadiusText]。
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
ARAP质询响应AVP（AVP代码84）为OctetString类型，仅当消息中包含帧协议AVP（见第6.10.1节）并设置为ARAP时才出现。此AVP包含对拨入客户端质询的8个八位字节响应。RADIUS服务器通过从ARAP密码AVP的高阶8个八位字节获取拨入客户端的质询，并使用身份验证用户的密码对该值执行DES加密来计算该值
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.
作为关键。如果用户的密码长度小于8个八位字节，则在将密码用作密钥之前，将在密码末尾用空八位字节填充到8个八位字节。
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安全AVP（AVP代码73）类型为Unsigned32，如果帧协议AVP（见第6.10.1节）设置为ARAP值，且结果代码AVP设置为DIAMETER\u MULTI\u ROUND\u AUTH，则可能出现在AA应答消息中。有关此AVP格式的更多信息，请参见[RadiusText]。
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.
ARAP安全AVP（AVP代码74）为OctetString类型，如果帧协议AVP设置为ARAP值，且结果代码AVP设置为DIAMETER\u MULTI\u ROUND\u AUTH，则可能出现在AA请求或AA应答消息中。此AVP包含与ARAP security中指定的ARAP安全模块相关联的安全模块质询或响应。
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.
本节包含NAS应用程序中支持的授权AVP。服务类型AVP应出现在所有消息中，根据其值，本节和第7节中定义的附加AVP可能出现。
Due to space constraints, the short-form IPFltrRule is used to represent IPFilterRule, and QoSFltrRule is used for QoSFilterRule.
由于空间限制，缩写形式IPFltrRule用于表示IPFilterRule，QoSFltrRule用于表示QoSFilterRule。
+---------------------+
| AVP Flag rules |
|----+-----+----+-----|----+
AVP Section | | |SHLD| MUST| |
Attribute Name Code Defined Value Type |MUST| MAY | NOT| NOT|Encr|
-----------------------------------------|----+-----+----+-----|----|
Service-Type 6 6.1 Enumerated | M | P | | V | Y |
Callback-Number 19 6.2 UTF8String | M | P | | V | Y |
Callback-Id 20 6.3 UTF8String | M | P | | V | Y |
Idle-Timeout 28 6.4 Unsigned32 | M | P | | V | Y |
Port-Limit 62 6.5 Unsigned32 | M | P | | V | Y |
NAS-Filter-Rule 400 6.6 IPFltrRule | M | P | | V | Y |
Filter-Id 11 6.7 UTF8String | M | P | | V | Y |
Configuration- 78 6.8 OctetString| M | | | P,V | |
Token | | | | | |
QoS-Filter-Rule 407 6.9 QoSFltrRule| | | | | |
Framed-Protocol 7 6.10.1 Enumerated | M | P | | V | Y |
+---------------------+
| AVP Flag rules |
|----+-----+----+-----|----+
AVP Section | | |SHLD| MUST| |
Attribute Name Code Defined Value Type |MUST| MAY | NOT| NOT|Encr|
-----------------------------------------|----+-----+----+-----|----|
Service-Type 6 6.1 Enumerated | M | P | | V | Y |
Callback-Number 19 6.2 UTF8String | M | P | | V | Y |
Callback-Id 20 6.3 UTF8String | M | P | | V | Y |
Idle-Timeout 28 6.4 Unsigned32 | M | P | | V | Y |
Port-Limit 62 6.5 Unsigned32 | M | P | | V | Y |
NAS-Filter-Rule 400 6.6 IPFltrRule | M | P | | V | Y |
Filter-Id 11 6.7 UTF8String | M | P | | V | Y |
Configuration- 78 6.8 OctetString| M | | | P,V | |
Token | | | | | |
QoS-Filter-Rule 407 6.9 QoSFltrRule| | | | | |
Framed-Protocol 7 6.10.1 Enumerated | M | P | | V | Y |
Framed-Routing 10 6.10.2 Enumerated | M | P | | V | Y |
Framed-MTU 12 6.10.3 Unsigned32 | M | P | | V | Y |
Framed- 13 6.10.4 Enumerated | M | P | | V | Y |
Compression | | | | | |
Framed-IP-Address 8 6.11.1 OctetString| M | P | | V | Y |
Framed-IP-Netmask 9 6.11.2 OctetString| M | P | | V | Y |
Framed-Route 22 6.11.3 UTF8String | M | P | | V | Y |
Framed-Pool 88 6.11.4 OctetString| M | P | | V | Y |
Framed- 96 6.11.5 Unsigned64 | M | P | | V | Y |
Interface-Id | | | | | |
Framed-IPv6- 97 6.11.6 OctetString| M | P | | V | Y |
Prefix | | | | | |
Framed-IPv6- 99 6.11.7 UTF8String | M | P | | V | Y |
Route | | | | | |
Framed-IPv6-Pool 100 6.11.8 OctetString| M | P | | V | Y |
Framed-IPX- 23 6.12.1 UTF8String | M | P | | V | Y |
Network | | | | | |
Framed-Appletalk- 37 6.13.1 Unsigned32 | M | P | | V | Y |
Link | | | | | |
Framed-Appletalk- 38 6.13.2 Unsigned32 | M | P | | V | Y |
Network | | | | | |
Framed-Appletalk- 39 6.13.3 OctetString| M | P | | V | Y |
Zone | | | | | |
ARAP-Features 71 6.14.1 OctetString| M | P | | V | Y |
ARAP-Zone-Access 72 6.14.2 Enumerated | M | P | | V | Y |
Login-IP-Host 14 6.15.1 OctetString| M | P | | V | Y |
Login-IPv6-Host 98 6.15.2 OctetString| M | P | | V | Y |
Login-Service 15 6.15.3 Enumerated | M | P | | V | Y |
Login-TCP-Port 16 6.16.1 Unsigned32 | M | P | | V | Y |
Login-LAT-Service 34 6.17.1 OctetString| M | P | | V | Y |
Login-LAT-Node 35 6.17.2 OctetString| M | P | | V | Y |
Login-LAT-Group 36 6.17.3 OctetString| M | P | | V | Y |
Login-LAT-Port 63 6.17.4 OctetString| M | P | | V | Y |
-----------------------------------------|----+-----+----+-----|----|
Framed-Routing 10 6.10.2 Enumerated | M | P | | V | Y |
Framed-MTU 12 6.10.3 Unsigned32 | M | P | | V | Y |
Framed- 13 6.10.4 Enumerated | M | P | | V | Y |
Compression | | | | | |
Framed-IP-Address 8 6.11.1 OctetString| M | P | | V | Y |
Framed-IP-Netmask 9 6.11.2 OctetString| M | P | | V | Y |
Framed-Route 22 6.11.3 UTF8String | M | P | | V | Y |
Framed-Pool 88 6.11.4 OctetString| M | P | | V | Y |
Framed- 96 6.11.5 Unsigned64 | M | P | | V | Y |
Interface-Id | | | | | |
Framed-IPv6- 97 6.11.6 OctetString| M | P | | V | Y |
Prefix | | | | | |
Framed-IPv6- 99 6.11.7 UTF8String | M | P | | V | Y |
Route | | | | | |
Framed-IPv6-Pool 100 6.11.8 OctetString| M | P | | V | Y |
Framed-IPX- 23 6.12.1 UTF8String | M | P | | V | Y |
Network | | | | | |
Framed-Appletalk- 37 6.13.1 Unsigned32 | M | P | | V | Y |
Link | | | | | |
Framed-Appletalk- 38 6.13.2 Unsigned32 | M | P | | V | Y |
Network | | | | | |
Framed-Appletalk- 39 6.13.3 OctetString| M | P | | V | Y |
Zone | | | | | |
ARAP-Features 71 6.14.1 OctetString| M | P | | V | Y |
ARAP-Zone-Access 72 6.14.2 Enumerated | M | P | | V | Y |
Login-IP-Host 14 6.15.1 OctetString| M | P | | V | Y |
Login-IPv6-Host 98 6.15.2 OctetString| M | P | | V | Y |
Login-Service 15 6.15.3 Enumerated | M | P | | V | Y |
Login-TCP-Port 16 6.16.1 Unsigned32 | M | P | | V | Y |
Login-LAT-Service 34 6.17.1 OctetString| M | P | | V | Y |
Login-LAT-Node 35 6.17.2 OctetString| M | P | | V | Y |
Login-LAT-Group 36 6.17.3 OctetString| M | P | | V | Y |
Login-LAT-Port 63 6.17.4 OctetString| M | P | | V | Y |
-----------------------------------------|----+-----+----+-----|----|
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.
服务类型AVP（AVP代码6）是枚举类型，包含用户请求的服务类型或要提供的服务类型。一个这样的AVP可以存在于认证和/或授权请求或响应中。NAS不需要实现所有这些服务类型。它必须将响应中接收到的未知或不受支持的服务类型视为失败，并使用DIAMETER_INVALID_AVP_VALUE结果代码结束会话。
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
在请求中使用时，服务类型AVP应被视为向服务器发出的提示，即NAS认为用户更喜欢指定的服务类型。服务器不需要遵守
hint. 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).
暗示此外，如果服务器指定的服务受支持，但与当前访问模式不兼容，则NAS必须无法启动会话。NAS还必须生成相应的错误消息。
The following values have been defined for the Service-Type AVP. The complete list of defined values can be found in [RADIUS] and [RADIUSTypes]. The following list is informational:
已为服务类型AVP定义了以下值。定义值的完整列表可在[RADIUS]和[RADIUSTypes]中找到。以下列表仅供参考：
1 Login
2 Framed
3 Callback Login
4 Callback Framed
5 Outbound
6 Administrative
7 NAS Prompt
8 Authenticate Only
9 Callback NAS Prompt
10 Call Check
11 Callback Administrative
12 Voice
13 Fax
14 Modem Relay
15 IAPP-Register [IEEE 802.11f]
16 IAPP-AP-Check [IEEE 802.11f]
17 Authorize Only [RADDynAuth]
1 Login
2 Framed
3 Callback Login
4 Callback Framed
5 Outbound
6 Administrative
7 NAS Prompt
8 Authenticate Only
9 Callback NAS Prompt
10 Call Check
11 Callback Administrative
12 Voice
13 Fax
14 Modem Relay
15 IAPP-Register [IEEE 802.11f]
16 IAPP-AP-Check [IEEE 802.11f]
17 Authorize Only [RADDynAuth]
The following values are further qualified:
进一步限定以下值：
Login 1 The user should be connected to a host. The message MAY include additional AVPs defined in sections 6.16 or 6.17.
登录1用户应连接到主机。该信息可能包括第6.16节或第6.17节中定义的附加AVP。
Framed 2 A Framed Protocol, such as PPP or SLIP, should be started for the User. The message MAY include additional AVPs defined in section 6.10, or section 7 for tunneling services.
框架2应为用户启动框架协议，如PPP或SLIP。该消息可能包括第6.10节或第7节中定义的隧道服务的附加AVP。
Callback Login 3 The user should be disconnected and called back, then connected to a host. The message MAY include additional AVPs defined in this section.
回调登录3用户应断开连接并回调，然后连接到主机。该消息可能包括本节中定义的附加AVP。
Callback Framed 4 The user should be disconnected and called back, and then a Framed Protocol, such as PPP or SLIP, should be started for the User. The message MAY include additional AVPs defined in section 6.10, or in section 7 for tunneling services.
Callback Framed 4用户应断开连接并回调，然后应为用户启动框架协议，如PPP或SLIP。该消息可能包括第6.10节或第7节中定义的隧道服务的附加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.
回拨号码AVP（AVP代码19）为UTF8String类型，包含用于回拨的拨号字符串。它可以在身份验证和/或授权请求中用作提示服务器需要回调服务，但服务器不需要在相应的响应中遵守该提示。
The codification of this field's allowed usage range is outside the scope of this specification.
此字段允许使用范围的编码不在本规范的范围内。
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. This AVP MAY be present in an authentication and/or authorization response.
回调Id AVP（AVP代码20）为UTF8String类型，包含要调用的位置的名称，由NAS进行解释。该AVP可以存在于认证和/或授权响应中。
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.
此AVP不支持漫游，因为它假定在NAS上配置了回调Id。因此，最好使用回拨号码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 issued. The default is none, or system specific.
空闲超时AVP（AVP代码28）的类型为Unsigned32，并设置在会话终止或发出提示之前用户允许的最大连续空闲连接秒数。默认值为“无”，或特定于系统。
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.
端口限制AVP（AVP代码62）的类型为Unsigned32，并设置NAS向用户提供的最大端口数。它可以在身份验证和/或授权请求中用作对服务器的提示，提示需要多链路PPP[PPPMP]服务，但服务器不需要在相应的响应中遵守该提示。
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 user. One or more of these AVPs MAY be present in an authorization response.
NAS筛选规则AVP（AVP代码400）属于IPFilterRule类型，并提供需要在NAS上为用户配置的筛选规则。授权响应中可能存在一个或多个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.
过滤器Id AVP（AVP代码11）为UTF8String类型，包含该用户的过滤器列表名称。授权应答中可能会发送零个或多个筛选器Id AVP。
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.
通过名称识别过滤器列表，可以在不同的NASE上使用过滤器，而不考虑过滤器列表的实现细节。但是，此AVP不适合漫游，因为不同服务提供商的筛选器命名不同。
In non-RADIUS environments, it is RECOMMENDED that the NAS-Filter-Rule AVP be used instead.
在非RADIUS环境中，建议改用NAS筛选规则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 be used. It should not be sent to a Diameter Client (NAS).
配置令牌AVP（AVP代码78）为OctetString类型，由Diameter服务器在AA应答命令中发送给Diameter代理或翻译代理，以指示要使用的用户配置文件的类型。不应将其发送到Diameter客户端（NAS）。
The format of the Data field of this AVP is site specific.
此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 the user. One or more such AVPs MAY be present in an authorization response.
QoS过滤规则AVP（AVP代码407）属于QoSFilterRule类型，并提供需要在NAS上为用户配置的QoS过滤规则。一个或多个这样的avp可以存在于授权响应中。
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.
注：由于[BASE]中的编辑错误，仅讨论AVP格式。未包含完整的QoSFilterRule定义。为了澄清，这里重印了它。
QoSFilterRule
QoSFilterRule
The QosFilterRule format is derived from the OctetString AVP Base Format. It uses the ASCII charset. Packets may be marked or metered based on the following information:
QosFilterRule格式源自八进制字符串AVP基本格式。它使用ASCII字符集。可根据以下信息对数据包进行标记或计量：
Direction (in or out) Source and destination IP address (possibly masked) Protocol Source and destination port (lists or ranges) DSCP values (no mask or range)
方向（输入或输出）源和目标IP地址（可能被屏蔽）协议源和目标端口（列表或范围）DSCP值（无屏蔽或范围）
Rules for the appropriate direction are evaluated in order; the first matched rule terminates the evaluation. Each packet is
按顺序评估适当方向的规则；第一个匹配的规则终止计算。每包都是
evaluated once. If no rule matches, the packet is treated as best effort. An access device unable to interpret or apply a QoS rule SHOULD NOT terminate the session.
评估一次。如果没有匹配的规则，则将数据包视为最大努力。无法解释或应用QoS规则的访问设备不应终止会话。
QoSFilterRule filters MUST follow the following format:
QoSFilterRule筛选器必须遵循以下格式：
action dir proto from src to dst [options]
从src到dst的操作目录协议[选项]
tag - Mark packet with a specific DSCP [DIFFSERV]. The DSCP option MUST be included. meter - Meter traffic. The metering options MUST be included.
使用特定的DSCP[DIFFSERV]标记数据包。必须包括DSCP选项。米-米交通。必须包括计量选项。
dir The format is as described under IPFilterRule.
dir格式如IPFilterRule中所述。
proto The format is as described under IPFilterRule.
proto格式如IPFilterRule中所述。
src and dst The format is as described under IPFilterRule.
src和dst格式如IPFilterRule中所述。
options:
选项：
DSCP <color> Color values as defined in [DIFFSERV]. Exact matching of DSCP values is required (no masks or ranges).
[DIFFSERV]中定义的DSCP<color>颜色值。需要精确匹配DSCP值（无掩码或范围）。
metering <rate> <color_under> <color_over> 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. Traffic 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).
计量<rate><color\u under><color\u over>计量选项提供了[DIFFSERVAF]中定义的可靠转发，如果操作设置为计量，则必须存在计量选项。速率选项是接入设备用于标记数据包的吞吐量，单位为比特/秒。速率上的流量在码点上用颜色_标记，速率下的流量在码点下用颜色_标记。color_under和color_over选项包含drop首选项，并且必须符合[DIFFSERVAF]（例如，AF13）中描述的推荐代码点关键字。
The metering option also supports the strict limit on traffic required by Expedited Forwarding, as defined in [DIFFSERVEF]. The color_over option may contain the keyword "drop" to prevent forwarding of traffic that exceeds the rate parameter.
计量选项还支持[DIFFSERVEF]中定义的对快速转发所需流量的严格限制。color_over选项可能包含关键字“drop”，以防止转发超过rate参数的流量。
The rule syntax is a modified subset of ipfw(8) from FreeBSD, and the ipfw.c code may provide a useful base for implementations.
规则语法是FreeBSD中ipfw（8）的一个修改子集，ipfw.c代码可以为实现提供有用的基础。
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".
本节列出了支持框架访问所需的授权AVP，如PPP和SLIP。如果服务类型AVP设置为“框架”或“回调框架”，则本节中定义的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:
帧协议AVP（AVP代码7）属于枚举类型，包含用于帧访问的帧。此AVP可能存在于请求和响应中。支持的值列在[RADIUSTypes]中。以下列表仅供参考：
1 PPP 2 SLIP 3 AppleTalk Remote Access Protocol (ARAP) 4 Gandalf proprietary SingleLink/MultiLink protocol 5 Xylogics proprietary IPX/SLIP 6 X.75 Synchronous
1 PPP 2 SLIP 3 AppleTalk远程访问协议（ARAP）4 Gandalf专有单链路/多链路协议5 Xylogics专有IPX/SLIP 6 X.75同步
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]. The following list is informational:
帧路由AVP（AVP代码10）是枚举的类型，并且包含当用户是网络的路由器时用户的路由方法。此AVP应仅出现在授权响应中。支持的值列在[RADIUSTypes]中。以下列表仅供参考：
0 None 1 Send routing packets 2 Listen for routing packets 3 Send and Listen
0无1发送路由数据包2侦听路由数据包3发送并侦听
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.
帧MTU AVP（AVP代码12）的类型为Unsigned32，并且包含在未通过某些其他方式（例如PPP）协商时为用户配置的最大传输单元。此AVP应仅出现在授权响应中。MTU值必须在64到65535之间。
The Framed-Compression AVP (AVP Code 13) is of type Enumerated and contains the compression protocol to be used for the link. It MAY be 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.
帧压缩AVP（AVP代码13）是枚举类型，并且包含用于链路的压缩协议。它可以在授权请求中用作提示服务器需要特定的压缩类型，但服务器不需要在相应的响应中遵守该提示。
More than one compression protocol AVP MAY be sent. The NAS is responsible for applying the proper compression protocol to the appropriate link traffic.
可以发送多个压缩协议AVP。NAS负责将适当的压缩协议应用于适当的链路流量。
The supported values are listed in [RADIUSTypes]. The following list is informational:
支持的值列在[RADIUSTypes]中。以下列表仅供参考：
0 None 1 VJ TCP/IP header compression 2 IPX header compression 3 Stac-LZS compression
0无1 VJ TCP/IP头压缩2 IPX头压缩3 Stac LZS压缩
The AVPs defined in this section are used when the user requests, or is being granted, access service to IP.
当用户请求或被授权访问IP服务时，使用本节中定义的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.
带帧IP地址AVP（AVP代码8）[RADIUS]的类型为OctetString，并包含为用户配置的属性值中指定类型的IPv4地址。它可以在授权请求中用作向服务器提示需要特定地址的提示，但服务器不需要在相应的响应中遵守该提示。
Two values have special significance: 0xFFFFFFFF and 0xFFFFFFFE. The 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).
两个值具有特殊意义：0xFFFFFF和0xFFFFFE。值0xFFFFFF表示NAS应允许用户选择地址（即协商地址）。值0xFFFFFE表示NAS应为用户选择一个地址（例如，从NAS保留的地址池中分配）。
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
帧式IP网络掩码AVP（AVP代码9）为OctetString类型，包含IPv4网络掩码的四个八位字节，当用户是网络路由器时，将为用户进行配置。它可以在授权请求中用作向服务器提示特定的网络掩码
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.
需要，但服务器不需要遵守相应响应中的提示。如果请求包含值为0xFFFFFF的此AVP，则此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 NAS. Zero or more of these AVPs MAY be present in an authorization response.
帧路由AVP（AVP代码22）为UTF8String类型，包含要为NAS上的用户配置的ASCII路由信息。授权响应中可能存在零个或多个AVP。
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. This is followed by a space, a gateway address in dotted quad form, a space, and one or more metrics separated by spaces; for example,
字符串必须包含一个虚线四元形式的目标前缀（可选），后跟一个斜杠和一个十进制长度说明符，说明应使用前缀的高阶位数。后跟一个空格、一个虚线四元形式的网关地址、一个空格和一个或多个由空格分隔的度量；例如
"192.168.1.0/24 192.168.1.1 1".
"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 prefixes; for example,
长度说明符可以省略，在这种情况下，A类前缀默认为8位，B类前缀默认为16位，C类前缀默认为24位；例如
"192.168.1.0 192.168.1.1 1".
"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.
当网关地址被指定为“0.0.0.0”时，应将用户的IP地址用作网关地址。
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.
框架池AVP（AVP代码88）为OctetString类型，包含分配的地址池的名称，该地址池应用于为用户分配地址。如果NAS不支持多个地址池，则NAS应忽略此AVP。地址池通常用于IP地址，但如果NAS支持用于其他协议的池，则可以用于这些协议。
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.
尽管为了与RADIUS[RADIUSExt]兼容而指定为类型OctetString，但数据字段的编码也应符合UTF8String数据格式的规则。
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.
帧接口Id AVP（AVP代码96）的类型为Unsigned64，包含要为用户配置的IPv6接口标识符。它可以在授权请求中用作提示服务器需要特定的接口id，但服务器不需要在相应的响应中遵守该提示。
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-Prefix AVP（AVP代码97）为OctetString类型，包含要为用户配置的IPv6前缀。一个或多个AVP可用于授权请求中，作为向服务器提示需要特定IPv6前缀的提示，但服务器无需在相应响应中遵守该提示。
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.
Framed-IPv6-Route AVP（AVP代码99）为UTF8String类型，包含要为NAS上的用户配置的ASCII路由信息。授权响应中可能存在零个或多个AVP。
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 separated by spaces; for example,
字符串必须包含一个IPv6地址前缀，后跟一个斜杠和一个十进制长度说明符，说明应使用前缀的高位。后跟一个空格、十六进制表示法的网关地址、一个空格和一个或多个由空格分隔的度量；例如
"2000:0:0:106::/64 2000::106:a00:20ff:fe99:a998 1".
“2000:0:0:106:：/64 2000:：106: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 in:
当网关地址为IPv6未指定地址时，应将用户的IP地址用作网关地址，例如：
"2000:0:0:106::/64 :: 1".
"2000:0:0:106::/64 :: 1".
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.
Framed-IPv6-Pool AVP（AVP代码100）为OctetString类型，包含分配的池的名称，该池应用于为用户分配IPv6前缀。如果访问设备不支持多个前缀池，则必须忽略此AVP。
Although specified as type OctetString for compatibility with RADIUS [RADIUSIPv6], the encoding of the Data field SHOULD also conform to the rules for the UTF8String Data Format.
尽管为与RADIUS[RadiusPv6]兼容而指定为类型OctetString，但数据字段的编码也应符合UTF8String数据格式的规则。
The AVPs defined in this section are used when the user requests, or is being granted, access to an IPX network service.
当用户请求或被授权访问IPX网络服务时，使用本节中定义的AVP。
The Framed-IPX-Network AVP (AVP Code 23) is of type Unsigned32 and contains the IPX Network number 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.
帧IPX网络AVP（AVP代码23）的类型为Unsigned32，包含要为用户配置的IPX网络号。它可以在授权请求中用作向服务器提示需要特定地址的提示，但服务器不需要在相应的响应中遵守该提示。
Two addresses have special significance: 0xFFFFFFFF and 0xFFFFFFFE. The 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., assign it from a pool of one or more IPX networks kept by the NAS).
两个地址具有特殊意义：0xFFFFFF和0xFFFFFE。值0xFFFFFF表示NAS应允许用户选择地址（即协商地址）。值0xFFFFFE表示NAS应为用户选择一个地址（例如，从NAS保留的一个或多个IPX网络池中分配）。
The AVPs defined in this section are used when the user requests, or is being granted, access to an AppleTalk network [AppleTalk].
当用户请求或被授权访问AppleTalk网络[AppleTalk]时，使用本节中定义的AVP。
The Framed-AppleTalk-Link AVP (AVP Code 37) is of type Unsigned32 and contains the AppleTalk network number that should be used for the serial link to the user, which is another AppleTalk router. This AVP MUST only be present in an authorization response and is never used when the user is not another router.
带帧AppleTalk链路AVP（AVP代码37）的类型为Unsigned32，包含应用于与用户（另一个AppleTalk路由器）的串行链路的AppleTalk网络号。此AVP必须仅出现在授权响应中，并且当用户不是其他路由器时，不得使用。
Despite the size of the field, values range from 0 to 65,535. The special value of 0 indicates an unnumbered serial link. A value of 1 to 65,535 means that the serial line between the NAS and the user should be assigned that value as an AppleTalk network number.
尽管字段大小不同，但值的范围从0到65535。特殊值0表示未编号的串行链路。值为1到65535表示NAS和用户之间的串行线应分配该值作为AppleTalk网络号。
The Framed-AppleTalk-Network AVP (AVP Code 38) is of type Unsigned32 and contains the AppleTalk Network number that the NAS should probe to allocate an AppleTalk node for the user. This AVP MUST only be present in an authorization response and is never used when the user is not another router. Multiple instances of this AVP indicate that the NAS may probe, using any of the network numbers specified.
带帧AppleTalk网络AVP（AVP代码38）的类型为Unsigned32，包含NAS应探测以为用户分配AppleTalk节点的AppleTalk网络号。此AVP必须仅出现在授权响应中，并且当用户不是其他路由器时，不得使用。此AVP的多个实例表明NAS可以使用指定的任何网络号进行探测。
Despite the size of the field, values range from 0 to 65,535. The special value 0 indicates that the NAS should assign a network for the user, using its default cable range. A value between 1 and 65,535 (inclusive) indicates to the AppleTalk Network that the NAS should probe to find an address for the user.
尽管字段大小不同，但值的范围从0到65535。特殊值0表示NAS应使用其默认电缆范围为用户分配网络。介于1和65535（包括1和65535）之间的值向AppleTalk网络指示NAS应探测以查找用户的地址。
The Framed-AppleTalk-Zone AVP (AVP Code 39) is of type OctetString and contains the AppleTalk Default Zone to be used for this user. This AVP MUST only be present in an authorization response. Multiple instances of this AVP in the same message are not allowed.
带边框的AppleTalk区域AVP（AVP代码39）为OctetString类型，包含要用于此用户的AppleTalk默认区域。此AVP必须仅出现在授权响应中。不允许在同一消息中使用此AVP的多个实例。
The codification of this field's allowed range is outside the scope of this specification.
该字段允许范围的编码不在本规范的范围内。
The AVPs defined in this section are used when the user requests, or is being granted, access to the AppleTalk network via the AppleTalk Remote Access Protocol [ARAP]. They are only present if the Framed-Protocol AVP (see section 6.10.1) is set to ARAP. Section 2.2 of RFC 2869 [RADIUSExt] describes the operational use of these attributes.
当用户通过AppleTalk远程访问协议[ARAP]请求或被授权访问AppleTalk网络时，使用本节中定义的AVP。仅当帧协议AVP（见第6.10.1节）设置为ARAP时，它们才存在。RFC 2869[RADIUSExt]第2.2节描述了这些属性的操作使用。
The ARAP-Features AVP (AVP Code 71) is of type OctetString and MAY be present in the AA-Accept message if the Framed-Protocol AVP is set to the value of ARAP. See [RADIUSExt] for more information about the format of this AVP.
ARAP功能AVP（AVP代码71）为OctetString类型，如果帧协议AVP设置为ARAP值，则可能出现在AA接受消息中。有关此AVP格式的更多信息，请参阅[RadiusText]。
The ARAP-Zone-Access AVP (AVP Code 72) is of type Enumerated and MAY be present in the AA-Accept message if the Framed-Protocol AVP is set to the value of ARAP.
ARAP区域访问AVP（AVP代码72）是枚举的类型，并且如果帧协议AVP被设置为ARAP的值，则可以存在于AA Accept消息中。
The supported values are listed in [RADIUSTypes] and defined in [RADIUSExt].
支持的值在[RADIUSTypes]中列出，并在[RadiusText]中定义。
This section contains the authorization AVPs that are needed to support terminal server functionality. AVPs defined in this section MAY be present in a message if the Service-Type AVP was set to "Login" or "Callback Login".
本节包含支持终端服务器功能所需的授权AVP。如果服务类型AVP设置为“登录”或“回调登录”，则本节中定义的AVP可能出现在消息中。
The Login-IP-Host AVP (AVP Code 14) [RADIUS] is of type OctetString and contains the IPv4 address of a host with which to connect the user when the Login-Service AVP is included. It MAY be used in an AA-Request command as a hint to the Diameter Server that a specific
登录IP主机AVP（AVP代码14）[RADIUS]的类型为OctetString，包含登录服务AVP时连接用户的主机的IPv4地址。它可以在AA请求命令中用作向Diameter服务器提示特定
host is desired, but the Diameter Server is not required to honor the hint in the AA-Answer.
需要主机，但Diameter服务器不需要遵守AA答案中的提示。
Two addresses have special significance: all ones and 0. The value of all ones indicates that the NAS SHOULD allow the user to select an address. The value 0 indicates that the NAS SHOULD select a host to connect the user to.
两个地址具有特殊意义：所有1和0。all One的值表示NAS应允许用户选择地址。值0表示NAS应选择要将用户连接到的主机。
The Login-IPv6-Host AVP (AVP Code 98) [RADIUSIPv6] is of type OctetString and contains the IPv6 address of a host with which to connect the user when the Login-Service AVP is included. It MAY be used in an AA-Request command as a hint to the Diameter Server that a specific host is desired, but the Diameter Server is not required to honor the hint in the AA-Answer.
Login-IPv6-Host AVP（AVP代码98）[RadiusPv6]的类型为OctetString，包含登录服务AVP时用于连接用户的主机的IPv6地址。它可以在AA请求命令中用作向Diameter服务器提示需要特定主机的提示，但Diameter服务器不需要遵守AA应答中的提示。
Two addresses have special significance:
两个地址具有特殊意义：
0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF and 0. The value 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF indicates that the NAS SHOULD allow the user to select an address. The value 0 indicates that the NAS SHOULD select a host to connect the user to.
0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF和0。值0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF表示NAS应允许用户选择地址。值0表示NAS应选择要将用户连接到的主机。
The Login-Service AVP (AVP Code 15) is of type Enumerated and contains the service that should be used to connect the user to the login host. This AVP SHOULD only be present in authorization responses.
登录服务AVP（AVP代码15）属于枚举类型，包含应用于将用户连接到登录主机的服务。此AVP应仅出现在授权响应中。
The supported values are listed in [RADIUSTypes]. The following list is informational:
支持的值列在[RADIUSTypes]中。以下列表仅供参考：
0 Telnet 1 Rlogin 2 TCP Clear 3 PortMaster (proprietary) 4 LAT 5 X25-PAD 6 X25-T3POS 8 TCP Clear Quiet (suppresses any NAS-generated connect string)
0 Telnet 1 Rlogin 2 TCP清除3端口主机（专有）4 LAT 5 X25-PAD 6 X25-T3POS 8 TCP清除静默（抑制任何NAS生成的连接字符串）
The AVPs described in this section MAY be present if the Login-Service AVP is set to Telnet, Rlogin, TCP Clear, or TCP Clear Quiet.
如果登录服务AVP设置为Telnet、Rlogin、TCP Clear或TCP Clear Quiet，则可能存在本节中描述的AVP。
The Login-TCP-Port AVP (AVP Code 16) is of type Unsigned32 and contains the TCP port with which the user is to be connected when the Login-Service AVP is also present. This AVP SHOULD only be present in authorization responses. The value MUST NOT be greater than 65,535.
登录TCP端口AVP（AVP代码16）的类型为Unsigned32，并且包含当登录服务AVP也存在时用户要连接的TCP端口。此AVP应仅出现在授权响应中。该值不得大于65535。
The AVPs described in this section MAY be present if the Login-Service AVP is set to LAT [LAT].
如果登录服务AVP设置为LAT[LAT]，则可能存在本节中描述的AVP。
The Login-LAT-Service AVP (AVP Code 34) is of type OctetString and contains the system with which the user is to be connected by LAT. It MAY be used in an authorization request as a hint to the server that a specific service is desired, but the server is not required to honor the hint in the corresponding response. This AVP MUST only be present in the response if the Login-Service AVP states that LAT is desired.
登录LAT服务AVP（AVP代码34）为OctetString类型，包含用户将通过LAT连接的系统。它可以在授权请求中用作向服务器提示需要特定服务的提示，但服务器不需要在相应响应中遵守该提示。只有当登录服务AVP声明需要LAT时，此AVP才能出现在响应中。
Administrators use this service attribute when dealing with clustered systems, such as a VAX or Alpha cluster. In these environments, several different time-sharing hosts share the same resources (disks, printers, etc.), and administrators often configure each host to offer access (service) to each of the shared resources. In this case, each host in the cluster advertises its services through LAT broadcasts.
管理员在处理集群系统（如VAX或Alpha集群）时使用此服务属性。在这些环境中，几个不同的分时主机共享相同的资源（磁盘、打印机等），管理员通常配置每个主机以提供对每个共享资源的访问（服务）。在这种情况下，集群中的每个主机都通过LAT广播宣传其服务。
Sophisticated users often know which service providers (machines) are faster and tend to use a node name when initiating a LAT connection. Some administrators want particular users to use certain machines as a primitive form of load balancing (although LAT knows how to do load balancing itself).
成熟的用户通常知道哪些服务提供商（机器）更快，并且在启动LAT连接时倾向于使用节点名称。一些管理员希望特定用户使用某些机器作为负载平衡的基本形式（尽管LAT知道如何自己进行负载平衡）。
The String field contains the identity of the LAT service to use. The LAT Architecture allows this string to contain $ (dollar), - (hyphen), . (period), _ (underscore), numerics, upper- and lowercase alphabetics, and the ISO Latin-1 character set extension [ISOLatin]. All LAT string comparisons are case insensitive.
字符串字段包含要使用的LAT服务的标识。LAT体系结构允许此字符串包含$（美元），-（连字符）。（句号）、u9（下划线）、数字、大小写字母以及ISO拉丁-1字符集扩展名[ISOLatin]。所有LAT字符串比较都不区分大小写。
The Login-LAT-Node AVP (AVP Code 35) is of type OctetString and contains the Node with which the user is to be automatically connected by LAT. It MAY be used in an authorization request as a hint to the server that a specific LAT node is desired, but the server is not required to honor the hint in the corresponding response. This AVP MUST only be present in a response if the Login-Service-Type AVP is set to LAT.
登录LAT节点AVP（AVP代码35）为OctetString类型，包含用户将通过LAT自动连接到的节点。它可以在授权请求中用作向服务器提示需要特定LAT节点，但服务器不需要在相应响应中遵守提示。只有当登录服务类型AVP设置为LAT时，此AVP才能出现在响应中。
The String field contains the identity of the LAT service to use. The LAT Architecture allows this string to contain $ (dollar), - (hyphen), . (period), _ (underscore), numerics, upper- and lowercase alphabetics, and the ISO Latin-1 character set extension [ISOLatin]. All LAT string comparisons are case insensitive.
字符串字段包含要使用的LAT服务的标识。LAT体系结构允许此字符串包含$（美元），-（连字符）。（句号）、u9（下划线）、数字、大小写字母以及ISO拉丁-1字符集扩展名[ISOLatin]。所有LAT字符串比较都不区分大小写。
The Login-LAT-Group AVP (AVP Code 36) is of type OctetString and contains a string identifying the LAT group codes this user is authorized to use. It MAY be used in an authorization request as a hint to the server that a specific group is desired, but the server is not required to honor the hint in the corresponding response. This AVP MUST only be present in a response if the Login-Service-Type AVP is set to LAT.
登录LAT组AVP（AVP代码36）的类型为OctetString，并包含一个字符串，用于标识该用户有权使用的LAT组代码。它可以在授权请求中用作向服务器提示需要特定组的提示，但服务器不需要在相应的响应中遵守该提示。只有当登录服务类型AVP设置为LAT时，此AVP才能出现在响应中。
LAT supports 256 different group codes, which LAT uses as a form of access rights. LAT encodes the group codes as a 256-bit bitmap.
LAT支持256种不同的组码，LAT将其用作访问权限的一种形式。LAT将组码编码为256位位图。
Administrators can assign one or more of the group code bits at the LAT service provider; it will only accept LAT connections that have these group codes set in the bitmap. The administrators assign a bitmap of authorized group codes to each user. LAT gets these from the operating system and uses them in its requests to the service providers.
管理员可以在LAT服务提供商处分配一个或多个组码位；它只接受位图中设置了这些组码的LAT连接。管理员将授权组码位图分配给每个用户。LAT从操作系统获取这些信息，并在向服务提供商发出的请求中使用它们。
The codification of the range of allowed usage of this field is outside the scope of this specification.
该字段允许使用范围的编码不在本规范范围内。
The Login-LAT-Port AVP (AVP Code 63) is of type OctetString and contains the Port with which the user is to be connected by LAT. It MAY be used in an authorization request as a hint to the server that a specific port is desired, but the server is not required to honor the hint in the corresponding response. This AVP MUST only be present in a response if the Login-Service-Type AVP is set to LAT.
登录LAT端口AVP（AVP代码63）为OctetString类型，包含用户将通过LAT连接的端口。它可以在授权请求中用作向服务器提示需要特定端口，但服务器不需要在相应响应中遵守提示。只有当登录服务类型AVP设置为LAT时，此AVP才能出现在响应中。
The String field contains the identity of the LAT service to use. The LAT Architecture allows this string to contain $ (dollar), - (hyphen), . (period), _ (underscore), numerics, upper- and lower-case alphabetics, and the ISO Latin-1 character set extension [ISOLatin]. All LAT string comparisons are case insensitive.
字符串字段包含要使用的LAT服务的标识。LAT体系结构允许此字符串包含$（美元），-（连字符）。（句号），u9（下划线）、数字、大写和小写字母以及ISO拉丁-1字符集扩展名[ISOLatin]。所有LAT字符串比较都不区分大小写。
Some NASes support compulsory tunnel services in which the incoming connection data is conveyed by an encapsulation method to a gateway elsewhere in the network. This is typically transparent to the service user, and the tunnel characteristics may be described by the remote AAA server, based on the user's authorization information. Several tunnel characteristics may be returned, and the NAS implementation may choose one [RADTunnels], [RADTunlAcct].
一些NASE支持强制隧道服务，其中传入的连接数据通过封装方法传输到网络中其他地方的网关。这通常对服务用户是透明的，并且隧道特性可以由远程AAA服务器基于用户的授权信息来描述。可以返回多个隧道特征，NAS实现可以选择一个[RADTunnels]、[radtunlact]。
+---------------------+
| AVP Flag rules |
|----+-----+----+-----|----+
AVP Section | | |SHLD| MUST| |
Attribute Name Code Defined Value Type |MUST| MAY | NOT| NOT |Encr|
-----------------------------------------|----+-----+----+-----|----|
Tunneling 401 7.1 Grouped | M | P | | V | N |
Tunnel-Type 64 7.2 Enumerated | M | P | | V | Y |
Tunnel-Medium- 65 7.3 Enumerated | M | P | | V | Y |
Type | | | | | |
Tunnel-Client- 66 7.4 UTF8String | M | P | | V | Y |
Endpoint | | | | | |
Tunnel-Server- 67 7.5 UTF8String | M | P | | V | Y |
Endpoint | | | | | |
Tunnel-Password 69 7.6 OctetString| M | P | | V | Y |
Tunnel-Private- 81 7.7 OctetString| M | P | | V | Y |
Group-Id | | | | | |
Tunnel- 82 7.8 OctetString| M | P | | V | Y |
Assignment-Id | | | | | |
Tunnel-Preference 83 7.9 Unsigned32 | M | P | | V | Y |
Tunnel-Client- 90 7.10 UTF8String | M | P | | V | Y |
Auth-Id | | | | | |
Tunnel-Server- 91 7.11 UTF8String | M | P | | V | Y |
Auth-Id | | | | | |
-----------------------------------------|----+-----+----+-----|----|
+---------------------+
| AVP Flag rules |
|----+-----+----+-----|----+
AVP Section | | |SHLD| MUST| |
Attribute Name Code Defined Value Type |MUST| MAY | NOT| NOT |Encr|
-----------------------------------------|----+-----+----+-----|----|
Tunneling 401 7.1 Grouped | M | P | | V | N |
Tunnel-Type 64 7.2 Enumerated | M | P | | V | Y |
Tunnel-Medium- 65 7.3 Enumerated | M | P | | V | Y |
Type | | | | | |
Tunnel-Client- 66 7.4 UTF8String | M | P | | V | Y |
Endpoint | | | | | |
Tunnel-Server- 67 7.5 UTF8String | M | P | | V | Y |
Endpoint | | | | | |
Tunnel-Password 69 7.6 OctetString| M | P | | V | Y |
Tunnel-Private- 81 7.7 OctetString| M | P | | V | Y |
Group-Id | | | | | |
Tunnel- 82 7.8 OctetString| M | P | | V | Y |
Assignment-Id | | | | | |
Tunnel-Preference 83 7.9 Unsigned32 | M | P | | V | Y |
Tunnel-Client- 90 7.10 UTF8String | M | P | | V | Y |
Auth-Id | | | | | |
Tunnel-Server- 91 7.11 UTF8String | M | P | | V | Y |
Auth-Id | | | | | |
-----------------------------------------|----+-----+----+-----|----|
The Tunneling AVP (AVP Code 401) is of type Grouped and contains the following AVPs, used to describe a compulsory tunnel service: [RADTunnels], [RADTunlAcct]. Its data field has the following ABNF grammar:
隧道AVP（AVP代码401）属于分组类型，包含以下AVP，用于描述强制隧道服务：[RADTunnels]，[radtunlact]。其数据字段具有以下ABNF语法：
Tunneling ::= < AVP Header: 401 >
{ Tunnel-Type }
{ Tunnel-Medium-Type }
{ Tunnel-Client-Endpoint }
{ Tunnel-Server-Endpoint }
[ Tunnel-Preference ]
[ Tunnel-Client-Auth-Id ]
[ Tunnel-Server-Auth-Id ]
[ Tunnel-Assignment-Id ]
[ Tunnel-Password ]
[ Tunnel-Private-Group-Id ]
Tunneling ::= < AVP Header: 401 >
{ Tunnel-Type }
{ Tunnel-Medium-Type }
{ Tunnel-Client-Endpoint }
{ Tunnel-Server-Endpoint }
[ Tunnel-Preference ]
[ Tunnel-Client-Auth-Id ]
[ Tunnel-Server-Auth-Id ]
[ Tunnel-Assignment-Id ]
[ Tunnel-Password ]
[ Tunnel-Private-Group-Id ]
The Tunnel-Type AVP (AVP Code 64) is of type Enumerated and contains the tunneling protocol(s) to be used (in the case of a tunnel initiator) or in use (in the case of a tunnel terminator). It MAY be used in an authorization request as a hint to the server that a specific tunnel type is desired, but the server is not required to honor the hint in the corresponding response.
隧道类型AVP（AVP代码64）是枚举的类型，并且包含要使用（在隧道启动器的情况下）或正在使用（在隧道终止器的情况下）的隧道协议。它可以在授权请求中用作提示服务器需要特定的隧道类型，但服务器不需要在相应的响应中遵守该提示。
The Tunnel-Type AVP SHOULD also be included in Accounting-Request messages.
隧道类型AVP也应包含在记帐请求消息中。
A tunnel initiator is not required to implement any of these tunnel types. If a tunnel initiator receives a response that contains only unknown or unsupported Tunnel-Types, the tunnel initiator MUST behave as though a response were received with the Result-Code indicating a failure.
实现这些隧道类型中的任何一种都不需要隧道启动器。如果隧道启动器接收到的响应仅包含未知或不受支持的隧道类型，则隧道启动器的行为必须与接收到的响应一样，结果代码指示失败。
The supported values are listed in [RADIUSTypes]. The following list is informational:
支持的值列在[RADIUSTypes]中。以下列表仅供参考：
1 Point-to-Point Tunneling Protocol (PPTP) 2 Layer Two Forwarding (L2F) 3 Layer Two Tunneling Protocol (L2TP) 4 Ascend Tunnel Management Protocol (ATMP) 5 Virtual Tunneling Protocol (VTP) 6 IP Authentication Header in the Tunnel-mode (AH) 7 IP-in-IP Encapsulation (IP-IP) 8 Minimal IP-in-IP Encapsulation (MIN-IP-IP) 9 IP Encapsulating Security Payload in the Tunnel-mode (ESP) 10 Generic Route Encapsulation (GRE) 11 Bay Dial Virtual Services (DVS) 12 IP-in-IP Tunneling 13 Virtual LANs (VLAN)
1点对点隧道协议（PPTP）2层二转发（L2F）3层二隧道协议（L2TP）4上升隧道管理协议（ATMP）5虚拟隧道协议（VTP）6隧道模式下的IP认证头（AH）7 IP-in-IP封装（IP-IP）8最小IP-in-IP封装（MIN-IP-IP）9隧道模式下的IP封装安全有效负载（ESP）10通用路由封装（GRE）11机架拨号虚拟服务（DVS）12 IP隧道模式下的IP 13虚拟LAN（VLAN）
The Tunnel-Medium-Type AVP (AVP Code 65) is of type Enumerated and contains the transport medium to use when creating a tunnel for protocols (such as L2TP) that can operate over multiple transports. It MAY be used in an authorization request as a hint to the server that a specific medium is desired, but the server is not required to honor the hint in the corresponding response.
隧道介质类型AVP（AVP代码65）属于枚举类型，包含为可在多个传输上运行的协议（如L2TP）创建隧道时要使用的传输介质。它可以在授权请求中用作向服务器提示需要特定介质的提示，但服务器不需要在相应的响应中遵守该提示。
The supported values are listed in [RADIUSTypes]. The following list is informational:
支持的值列在[RADIUSTypes]中。以下列表仅供参考：
1 IPv4 (IP version 4) 2 IPv6 (IP version 6) 3 NSAP 4 HDLC (8-bit multidrop) 5 BBN 1822 6 802 (includes all 802 media plus Ethernet "canonical format") 7 E.163 (POTS) 8 E.164 (SMDS, Frame Relay, ATM) 9 F.69 (Telex) 10 X.121 (X.25, Frame Relay) 11 IPX 12 Appletalk 13 Decnet IV 14 Banyan Vines 15 E.164 with NSAP format subaddress
1 IPv4（IP版本4）2 IPv6（IP版本6）3 NSAP 4 HDLC（8位多点）5 BBN 1822 6 802（包括所有802媒体加以太网“标准格式”）7 E.163（POTS）8 E.164（SMDS，帧中继，ATM）9 F.69（电传）10 X.121（X.25，帧中继）11 IPX 12 Appletalk 13 Decnet IV 14 Banyan Vines 15 E.164，带有NSAP格式子地址
The Tunnel-Client-Endpoint AVP (AVP Code 66) is of type UTF8String and contains the address of the initiator end of the tunnel. It MAY be used in an authorization request as a hint to the server that a specific endpoint is desired, but the server is not required to honor the hint in the corresponding response.
隧道客户端端点AVP（AVP代码66）的类型为UTF8String，包含隧道启动器端的地址。它可以在授权请求中用作向服务器提示需要特定端点的提示，但服务器不需要在相应的响应中遵守该提示。
This AVP SHOULD be included in the corresponding Accounting-Request messages, in which case it indicates the address from which the tunnel was initiated. This AVP, along with the Tunnel-Server-Endpoint and Session-Id AVP [BASE], MAY be used to provide a globally unique means to identify a tunnel for accounting and auditing purposes.
该AVP应包含在相应的记帐请求消息中，在这种情况下，它指示启动隧道的地址。此AVP以及隧道服务器端点和会话Id AVP[BASE]可用于提供全局唯一的方法来识别隧道，以用于记帐和审计目的。
If Tunnel-Medium-Type is IPv4 (1), then this string is either the fully qualified domain name (FQDN) of the tunnel client machine, or a
如果隧道介质类型为IPv4（1），则此字符串要么是隧道客户端计算机的完全限定域名（FQDN），要么是
"dotted-decimal" IP address. Implementations MUST support the dotted-decimal format and SHOULD support the FQDN format for IP addresses.
“点十进制”IP地址。实现必须支持点十进制格式，并且应该支持IP地址的FQDN格式。
If Tunnel-Medium-Type is IPv6 (2), then this string is either the FQDN of the tunnel client machine, or a text representation of the address in either the preferred or alternate form [IPv6Addr]. Conforming implementations MUST support the preferred form and SHOULD support both the alternate text form and the FQDN format for IPv6 addresses.
如果隧道介质类型为IPv6（2），则此字符串要么是隧道客户端计算机的FQDN，要么是首选或备用形式[IPv6Addr]的地址文本表示形式。一致性实现必须支持首选格式，并且应支持IPv6地址的备用文本格式和FQDN格式。
If Tunnel-Medium-Type is neither IPv4 nor IPv6, then this string is a tag referring to configuration data local to the Diameter client that describes the interface or medium-specific client address to use.
如果隧道介质类型既不是IPv4也不是IPv6，则此字符串是一个标记，它引用Diameter客户端本地的配置数据，描述要使用的接口或特定于介质的客户端地址。
The Tunnel-Server-Endpoint AVP (AVP Code 67) is of type UTF8String and contains the address of the server end of the tunnel. It MAY be used in an authorization request as a hint to the server that a specific endpoint is desired, but the server is not required to honor the hint in the corresponding response.
隧道服务器端点AVP（AVP代码67）为UTF8String类型，包含隧道服务器端的地址。它可以在授权请求中用作向服务器提示需要特定端点的提示，但服务器不需要在相应的响应中遵守该提示。
This AVP SHOULD be included in the corresponding Accounting-Request messages, in which case it indicates the address from which the tunnel was initiated. This AVP, along with the Tunnel-Client-Endpoint and Session-Id AVP [BASE], MAY be used to provide a globally unique means to identify a tunnel for accounting and auditing purposes.
该AVP应包含在相应的记帐请求消息中，在这种情况下，它指示启动隧道的地址。此AVP以及隧道客户端端点和会话Id AVP[BASE]可用于提供全局唯一的方法来识别隧道，以便进行会计和审计。
If Tunnel-Medium-Type is IPv4 (1), then this string is either the fully qualified domain name (FQDN) of the tunnel server machine, or a "dotted-decimal" IP address. Implementations MUST support the dotted-decimal format and SHOULD support the FQDN format for IP addresses.
如果隧道介质类型为IPv4（1），则此字符串是隧道服务器计算机的完全限定域名（FQDN）或“点十进制”IP地址。实现必须支持点十进制格式，并且应该支持IP地址的FQDN格式。
If Tunnel-Medium-Type is IPv6 (2), then this string is either the FQDN of the tunnel server machine, or a text representation of the address in either the preferred or alternate form [IPv6Addr]. Implementations MUST support the preferred form and SHOULD support both the alternate text form and the FQDN format for IPv6 addresses.
如果隧道介质类型为IPv6（2），则此字符串要么是隧道服务器计算机的FQDN，要么是首选或备用形式[IPv6Addr]的地址文本表示形式。实现必须支持首选格式，并且应支持IPv6地址的备用文本格式和FQDN格式。
If Tunnel-Medium-Type is not IPv4 or IPv6, this string is a tag referring to configuration data local to the Diameter client that describes the interface or medium-specific server address to use.
如果隧道介质类型不是IPv4或IPv6，则此字符串是一个标记，它引用Diameter客户端本地的配置数据，描述要使用的接口或特定于介质的服务器地址。
The Tunnel-Password AVP (AVP Code 69) is of type OctetString and may contain a password to be used to authenticate to a remote server. The Tunnel-Password AVP contains sensitive information. This value is not protected in the same manner as RADIUS [RADTunnels].
隧道密码AVP（AVP代码69）是OctetString类型，可以包含用于对远程服务器进行身份验证的密码。隧道密码AVP包含敏感信息。此值的保护方式与RADIUS[RADTunnels]不同。
As required in [BASE], Diameter messages are encrypted by using IPsec or TLS. The Tunnel-Password AVP SHOULD NOT be used in untrusted proxy environments without encrypting it by using end-to-end security techniques, such as CMS Security [DiamCMS].
根据[BASE]中的要求，Diameter消息使用IPsec或TLS进行加密。如果不使用端到端安全技术（如CMS security[DiamCMS]）对隧道密码AVP进行加密，则不应在不受信任的代理环境中使用隧道密码AVP。
The Tunnel-Private-Group-Id AVP (AVP Code 81) is of type OctetString and contains the group Id for a particular tunneled session. The Tunnel-Private-Group-Id AVP MAY be included in an authorization request if the tunnel initiator can predetermine the group resulting from a particular connection. It SHOULD be included in the authorization response if this tunnel session is to be treated as belonging to a particular private group. Private groups may be used to associate a tunneled session with a particular group of users. For example, it MAY be used to facilitate routing of unregistered IP addresses through a particular interface. This AVP SHOULD be included in the Accounting-Request messages that pertain to the tunneled session.
隧道专用组Id AVP（AVP代码81）为OctetString类型，包含特定隧道会话的组Id。如果隧道发起方可以预先确定由特定连接产生的组，则隧道专用组Id AVP可以包括在授权请求中。如果要将此隧道会话视为属于特定私有组，则应将其包括在授权响应中。私有组可用于将隧道会话与特定用户组相关联。例如，它可用于促进通过特定接口路由未注册的IP地址。此AVP应包含在与隧道会话相关的记帐请求消息中。
The Tunnel-Assignment-Id AVP (AVP Code 82) is of type OctetString and is used to indicate to the tunnel initiator the particular tunnel to which a session is to be assigned. Some tunneling protocols, such as [PPTP] and [L2TP], allow for sessions between the same two tunnel endpoints to be multiplexed over the same tunnel and also for a given session to use its own dedicated tunnel. This attribute provides a mechanism for Diameter to inform the tunnel initiator (e.g., PAC, LAC) whether to assign the session to a multiplexed tunnel or to a separate tunnel. Furthermore, it allows for sessions sharing multiplexed tunnels to be assigned to different multiplexed tunnels.
隧道分配Id AVP（AVP代码82）是OctetString类型，用于向隧道发起方指示会话将被分配到的特定隧道。一些隧道协议，例如[PPTP]和[L2TP]，允许相同的两个隧道端点之间的会话在相同的隧道上多路复用，并且允许给定的会话使用其自己的专用隧道。此属性为Diameter提供了一种机制，用于通知隧道启动器（例如PAC、LAC）是将会话分配给多路复用隧道还是单独的隧道。此外，它允许将共享多路复用隧道的会话分配给不同的多路复用隧道。
A particular tunneling implementation may assign differing characteristics to particular tunnels. For example, different tunnels may be assigned different QoS parameters. Such tunnels may be used to carry either individual or multiple sessions. The Tunnel-Assignment-Id attribute thus allows the Diameter server to indicate that a particular session is to be assigned to a tunnel providing an appropriate level of service. It is expected that any QoS-related Diameter tunneling attributes defined in the future
特定隧道实现可将不同的特性分配给特定隧道。例如，可以为不同的隧道分配不同的QoS参数。此类隧道可用于承载单个或多个会话。因此，隧道分配Id属性允许Diameter服务器指示将特定会话分配给提供适当服务级别的隧道。预计将来会定义任何与QoS相关的直径隧道属性
accompanying this one will be associated by the tunnel initiator with the Id given by this attribute. In the meantime, any semantic given to a particular Id string is a matter left to local configuration in the tunnel initiator.
伴随此属性的将由隧道启动器与此属性给定的Id相关联。同时，给定给特定Id字符串的任何语义都由隧道启动器中的本地配置决定。
The Tunnel-Assignment-Id AVP is of significance only to Diameter and the tunnel initiator. The Id it specifies is only intended to be of local use to Diameter and the tunnel initiator. The Id assigned by the tunnel initiator is not conveyed to the tunnel peer.
隧道分配Id AVP仅对直径和隧道启动器具有重要意义。它指定的Id仅用于Diameter和隧道启动器的本地使用。隧道启动器分配的Id不会传送到隧道对等方。
This attribute MAY be included in authorization responses. The tunnel initiator receiving this attribute MAY choose to ignore it and to assign the session to an arbitrary multiplexed or non-multiplexed tunnel between the desired endpoints. This AVP SHOULD also be included in the Accounting-Request messages pertaining to the tunneled session.
此属性可能包含在授权响应中。接收该属性的隧道启动器可以选择忽略该属性，并将会话分配给所需端点之间的任意多路复用或非多路复用隧道。此AVP还应包含在与隧道会话相关的记帐请求消息中。
If a tunnel initiator supports the Tunnel-Assignment-Id AVP, then it should assign a session to a tunnel in the following manner:
如果隧道启动器支持隧道分配Id AVP，则应按以下方式将会话分配给隧道：
- If this AVP is present and a tunnel exists between the specified endpoints with the specified Id, then the session should be assigned to that tunnel.
- 如果存在此AVP，并且在具有指定Id的指定端点之间存在隧道，则应将会话分配给该隧道。
- If this AVP is present and no tunnel exists between the specified endpoints with the specified Id, then a new tunnel should be established for the session and the specified Id should be associated with the new tunnel.
- 如果存在此AVP，且指定端点之间不存在具有指定Id的隧道，则应为会话建立新隧道，并且指定Id应与新隧道关联。
- If this AVP is not present, then the session is assigned to an unnamed tunnel. If an unnamed tunnel does not yet exist between the specified endpoints, then it is established and used for this session and for subsequent ones established without the Tunnel-Assignment-Id attribute. A tunnel initiator MUST NOT assign a session for which a Tunnel-Assignment-Id AVP was not specified to a named tunnel (i.e., one that was initiated by a session specifying this AVP).
- 如果此AVP不存在，则将会话分配给未命名的隧道。如果指定端点之间尚不存在未命名的隧道，则将建立该隧道，并将其用于此会话以及在不使用隧道分配Id属性的情况下建立的后续会话。隧道启动器不得将未指定隧道分配Id AVP的会话分配给命名隧道（即，由指定此AVP的会话启动的会话）。
Note that the same Id may be used to name different tunnels if these tunnels are between different endpoints.
请注意，如果不同的隧道位于不同的端点之间，则可以使用相同的Id来命名这些隧道。
The Tunnel-Preference AVP (AVP Code 83) is of type Unsigned32 and is used to identify the relative preference assigned to each tunnel when more than one set of tunneling AVPs is returned within separate Grouped-AVP AVPs. It MAY be used in an authorization request as a hint to the server that a specific preference is desired, but the
隧道首选项AVP（AVP代码83）的类型为Unsigned32，用于在单独分组的AVP AVP中返回多组隧道AVP时识别分配给每个隧道的相对首选项。它可以在授权请求中用作向服务器提示需要特定首选项的提示，但是
server is not required to honor the hint in the corresponding response.
服务器不需要接受相应响应中的提示。
For example, suppose that AVPs describing two tunnels are returned by the server, one with a Tunnel-Type of PPTP and the other with a Tunnel-Type of L2TP. If the tunnel initiator supports only one of the Tunnel-Types returned, it will initiate a tunnel of that type. If, however, it supports both tunnel protocols, it SHOULD use the value of the Tunnel-Preference AVP to decide which tunnel should be started. The tunnel with the lowest numerical value in the Value field of this AVP SHOULD be given the highest preference. The values assigned to two or more instances of the Tunnel-Preference AVP within a given authorization response MAY be identical. In this case, the tunnel initiator SHOULD use locally configured metrics to decide which set of AVPs to use.
例如，假设服务器返回描述两个隧道的AVP，一个隧道类型为PPTP，另一个隧道类型为L2TP。如果隧道启动器仅支持返回的一种隧道类型，它将启动该类型的隧道。但是，如果它支持两种隧道协议，则应使用隧道首选项AVP的值来决定应启动哪个隧道。本AVP值字段中数值最低的隧道应优先考虑。在给定授权响应内分配给隧道偏好AVP的两个或多个实例的值可以相同。在这种情况下，隧道启动器应该使用本地配置的度量来决定使用哪一组AVP。
The Tunnel-Client-Auth-Id AVP (AVP Code 90) is of type UTF8String and specifies the name used by the tunnel initiator during the authentication phase of tunnel establishment. It MAY be used in an authorization request as a hint to the server that a specific preference is desired, but the server is not required to honor the hint in the corresponding response. This AVP MUST be present in the authorization response if an authentication name other than the default is desired. This AVP SHOULD be included in the Accounting-Request messages pertaining to the tunneled session.
隧道客户端身份验证Id AVP（AVP代码90）的类型为UTF8String，并指定隧道启动器在隧道建立的身份验证阶段使用的名称。它可以在授权请求中用作向服务器提示需要特定首选项的提示，但服务器不需要在相应的响应中遵守该提示。如果需要默认名称以外的身份验证名称，则授权响应中必须存在此AVP。此AVP应包含在与隧道会话相关的记帐请求消息中。
The Tunnel-Server-Auth-Id AVP (AVP Code 91) is of type UTF8String and specifies the name used by the tunnel terminator during the authentication phase of tunnel establishment. It MAY be used in an authorization request as a hint to the server that a specific preference is desired, but the server is not required to honor the hint in the corresponding response. This AVP MUST be present in the authorization response if an authentication name other than the default is desired. This AVP SHOULD be included in the Accounting-Request messages pertaining to the tunneled session.
隧道服务器身份验证Id AVP（AVP代码91）的类型为UTF8String，并指定隧道终止程序在隧道建立的身份验证阶段使用的名称。它可以在授权请求中用作向服务器提示需要特定首选项的提示，但服务器不需要在相应的响应中遵守该提示。如果需要默认名称以外的身份验证名称，则授权响应中必须存在此AVP。此AVP应包含在与隧道会话相关的记帐请求消息中。
Applications implementing this specification use Diameter Accounting, as defined in [BASE], and the AVPs in the following section. Service-specific AVP usage is defined in the tables in section 10.
实现本规范的应用程序使用[BASE]中定义的直径计算和下一节中的AVP。特定于服务的AVP使用在第10节的表格中定义。
If accounting is active, Accounting Request (ACR) messages SHOULD be sent after the completion of any Authentication or Authorization
如果记帐处于活动状态，则应在完成任何身份验证或授权后发送记帐请求（ACR）消息
transaction and at the end of a Session. The Accounting-Record-Type value indicates the type of event. All other AVPs identify the session and provide additional information relevant to the event.
事务和在会话结束时。会计记录类型值指示事件的类型。所有其他AVP识别会话并提供与事件相关的附加信息。
The successful completion of the first Authentication or Authorization transaction SHOULD cause a START_RECORD to be sent. If additional Authentications or Authorizations occur in later transactions, the first exchange should generate a START_RECORD, and the later an INTERIM_RECORD. For a given session, there MUST only be one set of matching START and STOP records, with any number of INTERIM_RECORDS in between, or one EVENT_RECORD indicating the reason a session wasn't started.
第一次身份验证或授权事务的成功完成应导致发送START_记录。如果在以后的事务中发生额外的身份验证或授权，则第一次交换应生成一个开始\u记录，然后生成一个临时\u记录。对于给定会话，必须只有一组匹配的开始和停止记录，中间必须有任意数量的临时记录，或者一个事件记录指示会话未启动的原因。
The following table describes the AVPs; their AVP Code values, types, and possible flag values; and whether the AVP MAY be encrypted.
下表描述了AVP；其AVP代码值、类型和可能的标志值；以及AVP是否可以被加密。
+---------------------+
| AVP Flag rules |
|----+-----+----+-----|----+
AVP Section | | |SHLD| MUST| |
Attribute Name Code Defined Value Type |MUST| MAY | NOT| NOT|Encr|
-----------------------------------------|----+-----+----+-----|----|
Accounting- 363 8.1 Unsigned64 | M | P | | V | Y |
Input-Octets | | | | | |
Accounting- 364 8.2 Unsigned64 | M | P | | V | Y |
Output-Octets | | | | | |
Accounting- 365 8.3 Unsigned64 | M | P | | V | Y |
Input-Packets | | | | | |
Accounting- 366 8.4 Unsigned64 | M | P | | V | Y |
Output-Packets | | | | | |
Acct-Session-Time 46 8.5 Unsigned32 | M | P | | V | Y |
Acct-Authentic 45 8.6 Enumerated | M | P | | V | Y |
Acounting-Auth- 406 8.7 Enumerated | M | P | | V | Y |
Method | | | | | |
Acct-Delay-Time 41 8.8 Unsigned32 | M | P | | V | Y |
Acct-Link-Count 51 8.9 Unsigned32 | M | P | | V | Y |
Acct-Tunnel- 68 8.10 OctetString| M | P | | V | Y |
Connection | | | | | |
Acct-Tunnel- 86 8.11 Unsigned32 | M | P | | V | Y |
Packets-Lost | | | | | |
-----------------------------------------|----+-----+----+-----|----|
+---------------------+
| AVP Flag rules |
|----+-----+----+-----|----+
AVP Section | | |SHLD| MUST| |
Attribute Name Code Defined Value Type |MUST| MAY | NOT| NOT|Encr|
-----------------------------------------|----+-----+----+-----|----|
Accounting- 363 8.1 Unsigned64 | M | P | | V | Y |
Input-Octets | | | | | |
Accounting- 364 8.2 Unsigned64 | M | P | | V | Y |
Output-Octets | | | | | |
Accounting- 365 8.3 Unsigned64 | M | P | | V | Y |
Input-Packets | | | | | |
Accounting- 366 8.4 Unsigned64 | M | P | | V | Y |
Output-Packets | | | | | |
Acct-Session-Time 46 8.5 Unsigned32 | M | P | | V | Y |
Acct-Authentic 45 8.6 Enumerated | M | P | | V | Y |
Acounting-Auth- 406 8.7 Enumerated | M | P | | V | Y |
Method | | | | | |
Acct-Delay-Time 41 8.8 Unsigned32 | M | P | | V | Y |
Acct-Link-Count 51 8.9 Unsigned32 | M | P | | V | Y |
Acct-Tunnel- 68 8.10 OctetString| M | P | | V | Y |
Connection | | | | | |
Acct-Tunnel- 86 8.11 Unsigned32 | M | P | | V | Y |
Packets-Lost | | | | | |
-----------------------------------------|----+-----+----+-----|----|
The Accounting-Input-Octets AVP (AVP Code 363) is of type Unsigned64 and contains the number of octets received from the user.
记帐输入八位字节AVP（AVP代码363）的类型为Unsigned64，包含从用户接收的八位字节数。
For NAS usage, this AVP indicates how many octets have been received from the port in the course of this session. It can only be present in ACR messages with an Accounting-Record-Type of INTERIM_RECORD or STOP_RECORD.
对于NAS使用，此AVP表示在此会话过程中从端口接收到的八位字节数。它只能出现在会计记录类型为临时记录或停止记录的ACR消息中。
The Accounting-Output-Octets AVP (AVP Code 364) is of type Unsigned64 and contains the number of octets sent to the user.
记帐输出八位字节AVP（AVP代码364）的类型为Unsigned64，包含发送给用户的八位字节数。
For NAS usage, this AVP indicates how many octets have been sent to the port in the course of this session. It can only be present in ACR messages with an Accounting-Record-Type of INTERIM_RECORD or STOP_RECORD.
对于NAS使用，此AVP表示在此会话过程中已向端口发送了多少个八位字节。它只能出现在会计记录类型为临时记录或停止记录的ACR消息中。
The Accounting-Input-Packets (AVP Code 365) is of type Unsigned64 and contains the number of packets received from the user.
记帐输入数据包（AVP代码365）的类型为Unsigned64，包含从用户接收的数据包数。
For NAS usage, this AVP indicates how many packets have been received from the port over the course of a session being provided to a Framed User. It can only be present in ACR messages with an Accounting-Record-Type of INTERIM_RECORD or STOP_RECORD.
对于NAS使用，此AVP指示在向帧用户提供会话的过程中从端口接收到多少数据包。它只能出现在会计记录类型为临时记录或停止记录的ACR消息中。
The Accounting-Output-Packets (AVP Code 366) is of type Unsigned64 and contains the number of IP packets sent to the user.
记帐输出数据包（AVP代码366）的类型为Unsigned64，包含发送给用户的IP数据包的数量。
For NAS usage, this AVP indicates how many packets have been sent to the port over the course of a session being provided to a Framed User. It can only be present in ACR messages with an Accounting-Record-Type of INTERIM_RECORD or STOP_RECORD.
对于NAS使用，此AVP表示在向帧用户提供会话的过程中有多少数据包被发送到端口。它只能出现在会计记录类型为临时记录或停止记录的ACR消息中。
The Acct-Session-Time AVP (AVP Code 46) is of type Unsigned32 and indicates the length of the current session in seconds. It can only be present in ACR messages with an Accounting-Record-Type of INTERIM_RECORD or STOP_RECORD.
Acct会话时间AVP（AVP代码46）的类型为Unsigned32，以秒为单位指示当前会话的长度。它只能出现在会计记录类型为临时记录或停止记录的ACR消息中。
The Acct-Authentic AVP (AVP Code 45) is of type Enumerated and specifies how the user was authenticated. The supported values are listed in [RADIUSTypes]. The following list is informational:
Acct Authentic AVP（AVP代码45）属于枚举类型，并指定用户的身份验证方式。支持的值列在[RADIUSTypes]中。以下列表仅供参考：
1 RADIUS 2 Local 3 Remote 4 Diameter
1半径2本地3远程4直径
The Accounting-Auth-Method AVP (AVP Code 406) is of type Enumerated. A NAS MAY include this AVP in an Accounting-Request message to indicate the method used to authenticate the user. (Note that this is equivalent to the RADIUS MS-Acct-Auth-Type VSA attribute).
会计验证方法AVP（AVP代码406）属于枚举类型。NAS可以在记帐请求消息中包括该AVP，以指示用于认证用户的方法。（请注意，这相当于RADIUS MS Acct Auth Type VSA属性）。
The following values are defined:
定义了以下值：
1 PAP 2 CHAP 3 MS-CHAP-1 4 MS-CHAP-2 5 EAP 7 None
1 PAP 2第3章MS-CHAP-1 4 MS-CHAP-2 5 EAP 7无
The Acct-Delay-Time AVP (AVP Code 41) is of type Unsigned32 and indicates the number of seconds the Diameter client has been trying to send the Accounting-Request (ACR). The accounting server may subtract this value from the time when the ACR arrives at the server to calculate the approximate time of the event that caused the ACR to be generated.
Acct Delay Time AVP（AVP代码41）的类型为Unsigned32，表示Diameter客户端尝试发送记帐请求（ACR）的秒数。记帐服务器可以从ACR到达服务器的时间中减去该值，以计算导致生成ACR的事件的大致时间。
This AVP is not used for retransmissions at the transport level (TCP or SCTP). Rather, it may be used when an ACR command cannot be transmitted because there is no appropriate peer to transmit it to or was rejected because it could not be delivered. In these cases, the command MAY be buffered and transmitted later, when an appropriate peer-connection is available or after sufficient time has passed that the destination-host may be reachable and operational. If the ACR is resent in this way, the Acct-Delay-Time AVP SHOULD be included. The value of this AVP indicates the number of seconds that elapsed between the time of the first attempt at transmission and the current attempt.
此AVP不用于传输级别（TCP或SCTP）的重传。相反，当ACR命令无法传输时，可以使用该命令，因为没有合适的对等方将其传输到，或者因为无法传输而被拒绝。在这些情况下，当适当的对等连接可用时，或者在经过足够的时间使目标主机可以访问和操作之后，可以缓冲和传输命令。如果以这种方式重新发送ACR，则应包括账户延迟时间AVP。此AVP的值表示首次尝试传输与当前尝试传输之间经过的秒数。
The Acct-Link-Count AVP (AVP Code 51) is of type Unsigned32 and indicates the total number of links that have been active (current or closed) in a given multilink session at the time the accounting record is generated. This AVP MAY be included in Accounting-Requests for any session that may be part of a multilink service.
Acct Link Count AVP（AVP代码51）的类型为Unsigned32，表示生成记帐记录时给定多链路会话中处于活动状态（当前或关闭）的链路总数。该AVP可包含在任何会话的记帐请求中，该会话可能是多链路服务的一部分。
The Acct-Link-Count AVP may be used to make it easier for an accounting server to know when it has all the records for a given multilink service. When the number of Accounting-Requests received with Accounting-Record-Type = STOP_RECORD and with the same Acct-Multi-Session-Id and unique Session-Ids equals the largest value of Acct-Link-Count seen in those Accounting-Requests, all STOP_RECORD Accounting-Requests for that multilink service have been received.
Acct Link Count AVP可用于使记帐服务器更容易了解其何时拥有给定多链路服务的所有记录。当接收到的记帐记录类型为STOP_Record且具有相同Acct Multi Session Id和唯一会话Id的记帐请求数等于这些记帐请求中看到的Acct Link Count的最大值时，已接收到该多链路服务的所有STOP_Record记帐请求。
The following example, showing eight Accounting-Requests, illustrates how the Acct-Link-Count AVP is used. In the table below, only the relevant AVPs are shown, although additional AVPs containing accounting information will be present in the Accounting-Requests.
下面的示例显示了八个记帐请求，说明了如何使用Acct Link Count AVP。下表中仅显示了相关的AVP，但包含会计信息的其他AVP将出现在会计请求中。
Acct-Multi- Accounting- Acct-
Session-Id Session-Id Record-Type Link-Count
--------------------------------------------------------
"...10" "...10" START_RECORD 1
"...10" "...11" START_RECORD 2
"...10" "...11" STOP_RECORD 2
"...10" "...12" START_RECORD 3
"...10" "...13" START_RECORD 4
"...10" "...12" STOP_RECORD 4
"...10" "...13" STOP_RECORD 4
"...10" "...10" STOP_RECORD 4
Acct-Multi- Accounting- Acct-
Session-Id Session-Id Record-Type Link-Count
--------------------------------------------------------
"...10" "...10" START_RECORD 1
"...10" "...11" START_RECORD 2
"...10" "...11" STOP_RECORD 2
"...10" "...12" START_RECORD 3
"...10" "...13" START_RECORD 4
"...10" "...12" STOP_RECORD 4
"...10" "...13" STOP_RECORD 4
"...10" "...10" STOP_RECORD 4
The Acct-Tunnel-Connection AVP (AVP Code 68) is of type OctetString and contains the identifier assigned to the tunnel session. This AVP, along with the Tunnel-Client-Endpoint and Tunnel-Server-Endpoint AVPs, may be used to provide a means to uniquely identify a tunnel session for auditing purposes.
Acct隧道连接AVP（AVP代码68）的类型为OctetString，包含分配给隧道会话的标识符。该AVP以及隧道客户端端点和隧道服务器端点AVP可用于提供唯一标识隧道会话以用于审计目的的方法。
The format of the identifier in this AVP depends upon the value of the Tunnel-Type AVP. For example, to identify an L2TP tunnel connection fully, the L2TP Tunnel Id and Call Id might be encoded in this field. The exact encoding of this field is implementation dependent.
此AVP中标识符的格式取决于隧道类型AVP的值。例如，为了完全识别L2TP隧道连接，L2TP隧道Id和呼叫Id可以在该字段中进行编码。此字段的确切编码取决于实现。
The Acct-Tunnel-Packets-Lost AVP (AVP Code 86) is of type Unsigned32 and contains the number of packets lost on a given link.
Acct Tunnel Packets Lost AVP（AVP代码86）的类型为Unsigned32，包含给定链路上丢失的数据包数。
This section describes some basic guidelines that servers acting as AAA Translation Agents may use. A complete description of all the differences between RADIUS and Diameter is beyond the scope of this section and document. Note that this document does not restrict implementations from creating additional translation methods, as long as the translation function doesn't violate the RADIUS or the Diameter protocols.
本节介绍充当AAA翻译代理的服务器可能使用的一些基本准则。半径和直径之间所有差异的完整描述超出本节和本文件的范围。请注意，只要转换函数不违反RADIUS或Diameter协议，本文档不会限制实现创建其他转换方法。
Although the Diameter protocol is in many ways a superset of RADIUS functions, a number of RADIUS representations are not allowed, so that new capabilities can be used without the old problems.
虽然Diameter协议在许多方面是RADIUS函数的超集，但不允许使用大量RADIUS表示，因此可以使用新的功能而不出现旧的问题。
There are primarily two different situations that must be handled: one in which a RADIUS request is received that must be forwarded as a Diameter request, and another in which the inverse is true. RADIUS does not support a peer-to-peer architecture, and server-initiated operations are generally not supported. See [RADDynAuth] for an alternative.
主要有两种不同的情况必须处理：一种是接收到的RADIUS请求必须作为Diameter请求转发，另一种是相反的情况。RADIUS不支持对等体系结构，通常不支持服务器启动的操作。请参见[RADDynAuth]了解替代方案。
Some RADIUS attributes are encrypted. RADIUS security and encryption techniques are applied on a hop-per-hop basis. A Diameter agent will have to decrypt RADIUS attribute data entering the Diameter system, and if that information is forwarded, the agent MUST secure it by using Diameter specific techniques.
某些半径属性是加密的。RADIUS安全和加密技术以每跳为基础应用。Diameter代理必须解密进入Diameter系统的RADIUS属性数据，如果该信息被转发，代理必须使用Diameter特定的技术来保护该信息。
Note that this section uses the two terms, "AVP" and "attribute", in a concise and specific manner. The former is used to signify a Diameter AVP, and the latter to signify a RADIUS attribute.
请注意，本节以简洁和具体的方式使用了“AVP”和“属性”这两个术语。前者表示直径AVP，后者表示半径属性。
This section describes the actions that should be taken when a Translation Agent receives a RADIUS message to be translated to a Diameter message.
本节介绍翻译代理收到要翻译为Diameter消息的RADIUS消息时应采取的操作。
Note that RADIUS servers are assumed to be stateless. It is also quite possible for the RADIUS messages that comprise the session (i.e., authentication and accounting messages) to be handled by different Translation Agents in the proxy network. Therefore, a RADIUS/Diameter Translation Agent SHOULD NOT be assumed to have an accurate track on session-state information.
请注意，假定RADIUS服务器是无状态的。组成会话的RADIUS消息（即认证和记帐消息）也很可能由代理网络中的不同翻译代理处理。因此，不应假定RADIUS/Diameter转换代理对会话状态信息有准确的跟踪。
When a Translation Agent receives a RADIUS message, the following steps should be taken:
当翻译代理收到RADIUS消息时，应采取以下步骤：
- If a Message-Authenticator attribute is present, the value MUST be checked but not included in the Diameter message. If it is incorrect, the RADIUS message should be silently discarded. The gateway system SHOULD generate and include a Message-Authenticator in returned RADIUS responses.
- 如果存在消息验证器属性，则必须检查该值，但不包括在Diameter消息中。如果不正确，RADIUS消息应该被悄悄地丢弃。网关系统应在返回的RADIUS响应中生成并包含消息验证器。
- The transport address of the sender MUST be checked against the NAS identifying attributes. See the description of NAS-Identifier and NAS-IP-Address below.
- 必须根据NAS标识属性检查发送方的传输地址。请参阅下面的NAS标识符和NAS IP地址说明。
- The Translation Agent must maintain transaction state information relevant to the RADIUS request, such as the Identifier field in the RADIUS header, any existing RADIUS Proxy-State attribute, and the source IP address and port number of the UDP packet. These may be maintained locally in a state table or saved in a Proxy-Info AVP group. A Diameter Session-Id AVP value must be created using a session state mapping mechanism.
- 翻译代理必须维护与RADIUS请求相关的事务状态信息，例如RADIUS标头中的标识符字段、任何现有RADIUS代理状态属性以及UDP数据包的源IP地址和端口号。这些可以在状态表中本地维护，也可以保存在代理信息AVP组中。必须使用会话状态映射机制创建Diameter会话Id AVP值。
- If the RADIUS request contained a State attribute and the prefix of the data is "Diameter/", the data following the prefix contains the Diameter Origin-Host/Origin-Realm/Session-Id. If no such attributes are present and the RADIUS command is an Access-Request, a new Session-Id is created. The Session-Id is included in the Session-Id AVP.
- 如果RADIUS请求包含状态属性且数据前缀为“Diameter/”，则前缀后面的数据包含Diameter原始主机/原始域/会话Id。如果不存在此类属性且RADIUS命令为访问请求，则会创建新会话Id。会话Id包含在会话Id AVP中。
- The Diameter Origin-Host and Origin-Realm AVPs MUST be created and added by using the information from an FQDN corresponding to the NAS-IP-Address attribute (preferred if available), and/or to the NAS-Identifier attribute. (Note that the RADIUS NAS-Identifier is not required to be an FQDN.)
- 必须使用对应于NAS IP地址属性（如果可用，首选）和/或NAS标识符属性的FQDN中的信息来创建和添加Diameter源主机和源领域AVP。（请注意，RADIUS NAS标识符不要求是FQDN。）
- The response MUST have an Origin-AAA-Protocol AVP added, indicating the protocol of origin of the message.
- 响应必须添加源AAA协议AVP，指示消息的源协议。
- The Proxy-Info group SHOULD be added, with the local server's identity specified in the Proxy-Host AVP. This should ensure that the response is returned to this system.
- 应添加代理信息组，并在代理主机AVP中指定本地服务器的标识。这将确保响应返回到此系统。
- The Destination-Realm AVP is created from the information found in the RADIUS User-Name attribute.
- 目标领域AVP是根据RADIUS用户名属性中的信息创建的。
- If the RADIUS User-Password attribute is present, the password must be unencrypted by using the link's RADIUS shared secret. The unencrypted value must be forwarded in a User-Password AVP using Diameter security.
- 如果存在RADIUS User Password属性，则必须使用链接的RADIUS共享机密对密码进行解密。必须使用Diameter security在用户密码AVP中转发未加密的值。
- If the RADIUS CHAP-Password attribute is present, the Ident and Data portion of the attribute are used to create the CHAP-Auth grouped AVP.
- 如果存在RADIUS CHAP Password属性，则该属性的标识和数据部分用于创建CHAP Auth分组AVP。
- If the RADIUS message contains an address attribute, it MUST be converted to the appropriate Diameter AVP and type.
- 如果RADIUS消息包含地址属性，则必须将其转换为适当的直径AVP和类型。
- If the RADIUS message contains Tunnel information [RADTunnels], the attributes or tagged groups should each be converted to a Diameter Tunneling Grouped AVP set. If the tunnel information contains a Tunnel-Password attribute, the RADIUS encryption must be resolved, and the password forwarded, by using Diameter security methods.
- 如果RADIUS消息包含隧道信息[RADTunnels]，则属性或标记组应分别转换为直径隧道分组AVP集。如果隧道信息包含隧道密码属性，则必须使用Diameter安全方法解析RADIUS加密并转发密码。
- If the RADIUS message received is an Accounting-Request, the Acct-Status-Type attribute value must be converted to a Accounting-Record-Type AVP value. If the Acct-Status-Type attribute value is STOP, the local server MUST issue a Session-Termination-Request message once the Diameter Accounting-Answer message has been received.
- 如果收到的RADIUS消息是记帐请求，则必须将“帐户状态类型”属性值转换为记帐记录类型AVP值。如果Acct Status Type属性值为STOP，则在收到Diameter Accounting应答消息后，本地服务器必须发出会话终止请求消息。
- If the Accounting message contains an Acct-Termination-Cause attribute, it should be translated to the equivalent Termination-Cause AVP value. (see below)
- 如果记帐消息包含帐户终止原因属性，则应将其转换为等效的终止原因AVP值。（见下文）
- If the RADIUS message contains the Accounting-Input-Octets, Accounting-Input-Packets, Accounting-Output-Octets, or Accounting-Output-Packets, these attributes must be converted to the Diameter equivalents. Further, if the Acct-Input-Gigawords or Acct-Output-Gigawords attributes are present, these must be used to properly compute the Diameter accounting AVPs.
- 如果RADIUS消息包含记帐输入八位字节、记帐输入数据包、记帐输出八位字节或记帐输出数据包，则必须将这些属性转换为等效的直径。此外，如果存在Acct Input GIGAWORD或Acct Output GIGAWORD属性，则必须使用这些属性正确计算直径核算AVP。
The corresponding Diameter response is always guaranteed to be received by the same Translation Agent that translated the original request, due to the contents of the Proxy-Info AVP group in the Diameter request. The following steps are applied to the response message during the Diameter-to-RADIUS translation:
由于Diameter请求中的Proxy Info AVP组的内容，相应的Diameter响应始终保证由翻译原始请求的同一翻译代理接收。在从直径到半径的转换过程中，以下步骤应用于响应消息：
- If the Diameter Command-Code is set to AA-Answer and the Result-Code AVP is set to DIAMETER_MULTI_ROUND_AUTH, the gateway must send a RADIUS Access-Challenge. This must have the Origin-Host, Origin-Realm, and Diameter Session-Id AVPs
- 如果Diameter命令代码设置为AA Answer，结果代码AVP设置为Diameter\u MULTI\u ROUND\u AUTH，则网关必须发送RADIUS访问质询。这必须具有原始主机、原始域和Diameter会话Id AVPs
encapsulated in the RADIUS State attribute, with the prefix "Diameter/", concatenated in the above order separated with "/" characters, in UTF-8 [UTF-8]. This is necessary to ensure that the Translation Agent receiving the subsequent RADIUS Access-Request will have access to the Session Identifier and be able to set the Destination-Host to the correct value. If the Multi-Round-Time-Out AVP is present, the value of the AVP MUST be inserted in the RADIUS Session-Timeout AVP.
封装在RADIUS State属性中，前缀为“Diameter/”，按上述顺序连接，以“/”字符分隔，UTF-8[UTF-8]格式。这对于确保接收后续RADIUS访问请求的翻译代理能够访问会话标识符并能够将目标主机设置为正确的值是必要的。如果存在多轮超时AVP，则必须将AVP的值插入RADIUS会话超时AVP。
- If the Command-Code is set to AA-Answer, the Diameter Session-Id AVP is saved in a new RADIUS Class attribute whose format consists of the string "Diameter/" followed by the Diameter Session Identifier. This will ensure that the subsequent Accounting messages, which could be received by any Translation Agent, would have access to the original Diameter Session Identifier. - If a Proxy-State attribute was present in the RADIUS request, the same attribute is added in the response. This information may be found in the Proxy-Info AVP group, or in a local state table.
- 如果命令代码设置为AA Answer，则Diameter会话Id AVP将保存在一个新的RADIUS类属性中，该属性的格式由字符串“Diameter/”和Diameter会话标识符组成。这将确保任何翻译代理都可以接收到的后续记帐消息能够访问原始Diameter会话标识符。-如果RADIUS请求中存在代理状态属性，则会在响应中添加相同的属性。此信息可以在Proxy Info AVP组或本地状态表中找到。
- If state information regarding the RADIUS request was saved in a Proxy-Info AVP or local state table, the RADIUS Identifier and UDP IP Address and port number are extracted and used in issuing the RADIUS reply.
- 如果有关RADIUS请求的状态信息保存在代理信息AVP或本地状态表中，则提取RADIUS标识符、UDP IP地址和端口号，并在发出RADIUS应答时使用。
When translating a Diameter AA-Answer (with successful result code) to RADIUS Access-Accept that contains a Session-Timeout or Authorization-Lifetime AVP, take the following steps:
将Diameter AA应答（带有成功结果代码）转换为包含会话超时或授权生存期AVP的RADIUS Access Accept时，请执行以下步骤：
- If the Diameter message contains a Session-Timeout AVP but no Authorization-Lifetime AVP, translate it to a Session-Timeout attribute (not a Termination-Action).
- 如果Diameter消息包含会话超时AVP，但没有授权生存期AVP，请将其转换为会话超时属性（而不是终止操作）。
- If the Diameter message contains an Authorization-Lifetime AVP but no Session-Timeout AVP, translate it to a Session-Timeout attribute and a Termination-Action set to AA-REQUEST. (Remove Authorization-Lifetime and Re-Auth-Request-Type.)
- 如果Diameter消息包含授权生存期AVP，但没有会话超时AVP，请将其转换为会话超时属性，并将终止操作设置为AA-REQUEST。（删除授权生存期和重新验证请求类型。）
- If the Diameter message has both, the Session-Timeout must be greater than or equal to the Authorization-Lifetime (required by [BASE]). Translate it to a Session-Timeout value (with value from Authorization-Lifetime AVP, the smaller one) and with the Termination-Action set to AA-REQUEST. (Remove the Authorization-Lifetime and Re-Auth-Request-Type.)
- 如果Diameter消息同时具有这两个属性，则会话超时必须大于或等于授权生存期（由[BASE]要求）。将其转换为会话超时值（使用授权生存期AVP中较小的值），并将终止操作设置为AA-REQUEST。（删除授权生存期和重新验证请求类型。）
A Diameter/RADIUS gateway may communicate with a server that implements RADIUS Dynamic Authorization [RADDynAuth]. If the server supports these functions, it MUST be listening on the assigned port and would receive RADIUS CoA-Request and Disconnect-Request messages. These can be mapped into the Diameter Re-Auth-Request (RAR) and Abort-Session-Request (ASR) message exchanges, respectively [BASE].
Diameter/RADIUS网关可以与实现RADIUS动态授权[RADDynAuth]的服务器通信。如果服务器支持这些功能，它必须在分配的端口上侦听，并将接收RADIUS CoA请求和断开连接请求消息。这些可以分别映射到Diameter重新验证请求（RAR）和中止会话请求（ASR）消息交换[BASE]。
If the [RADDynAuth] is not supported, the port would not be active and the RADIUS server would receive an ICMP Port Unreachable indication. Alternatively, if the messages are received but with an inappropriate Service-Type, the gateway can respond with the appropriate NAK message and an Error-Cause attribute with the value of 405, "Unsupported Service".
如果不支持[RADDynAuth]，则端口将不处于活动状态，RADIUS服务器将收到ICMP端口不可访问指示。或者，如果接收到消息但具有不适当的服务类型，则网关可以使用适当的NAK消息和值为405“不支持的服务”的错误原因属性进行响应。
The RADIUS CoA-Request and Disconnect-Request messages will not contain a Diameter Session-Id. Diameter requires that this value match an active session context. The gateway MUST have a session Id cache (or other means) to identify the sessions these functions pertain to. If unable to identify the session, the gateway (or NAS) should return an Error-Cause value 503, "Session Context Not Found".
RADIUS CoA请求和断开连接请求消息将不包含Diameter会话Id。Diameter要求此值与活动会话上下文匹配。网关必须具有会话Id缓存（或其他方式），以识别这些功能所涉及的会话。如果无法识别会话，网关（或NAS）应返回错误原因值503，“未找到会话上下文”。
The RADIUS CoA-Request message only supports a change of authorization attributes, and the received CoA-Request SHOULD include a Service-Type of "Authorize-Only". This indicates an extended exchange request by the rules given in [RADDynAuth] section 3.2, note 6. This is the only type of exchange supported by Diameter [BASE].
RADIUS CoA请求消息仅支持更改授权属性，收到的CoA请求应包括“仅授权”的服务类型。这表示根据[RADDynAuth]第3.2节注释6中给出的规则提出的扩展交换请求。这是Diameter[BASE]支持的唯一交换类型。
For the CoA-Request, the translated RAR message will have a Re-Auth-Type of AUTHORIZE_ONLY. The returned RAA will be translated into a CoA-NAK with Error-Cause "Request Initiated". The gateway's Diameter client SHOULD also start a reauthorization sequence by sending an AAR message, which will be translated into an Access-Request message. The RADIUS server will use the Access-Accept (or Access-Reject) message to convey the new authorization attributes, which the gateway will pass back in an AAA message.
对于CoA请求，翻译后的RAR消息将具有“仅授权”的重新授权类型。返回的RAA将被转换为错误原因为“请求已启动”的CoA NAK。网关的Diameter客户端还应通过发送AAR消息启动重新授权序列，该消息将被转换为访问请求消息。RADIUS服务器将使用Access Accept（或Access Reject）消息传递新的授权属性，网关将在AAA消息中传回这些属性。
Any attributes included in the COA-Request or Access-Accept message are to be considered mandatory in Diameter. If they cannot be supported, they MUST result in an error message return to the RADIUS server, with an Error-Cause of "Unsupported Attribute". The Diameter NAS will attempt to apply all the attributes supplied in the AA message to the session.
COA请求或访问接受消息中包含的任何属性在直径上都是强制性的。如果它们不受支持，则必须返回到RADIUS服务器的错误消息，错误原因为“Unsupported Attribute”。Diameter NAS将尝试将AA消息中提供的所有属性应用于会话。
A RADIUS Disconnect-Request message received by the gateway would be translated to a Diameter Abort-Session-Request (ASR) message [BASE]. The results will be returned by the Diameter client in an Abort-
网关接收到的RADIUS断开连接请求消息将转换为Diameter中止会话请求（ASR）消息[BASE]。Diameter客户端将在中止中返回结果-
Session-Answer (ASA) message. A success indication would translate to a RADIUS Disconnect-ACK, and a failure would generate a Disconnect-NAK.
会话应答（ASA）消息。成功指示将转换为半径断开确认，失败将生成断开NAK。
When a server receives a Diameter request to be forwarded to a RADIUS entity, the following are examples of the steps that may be taken:
当服务器收到要转发给RADIUS实体的Diameter请求时，以下是可能采取的步骤示例：
- The Origin-Host AVP's value is inserted into the NAS-Identifier attribute.
- 原始主机AVP的值插入到NAS标识符属性中。
- The following information MUST be present in the corresponding Diameter response and therefore MUST be saved, either in a local state table or encoded in a RADIUS Proxy-State attribute:
- 以下信息必须出现在相应的Diameter响应中，因此必须保存在本地状态表中或在RADIUS代理状态属性中进行编码：
1. Origin-Host AVP 2. Session-Id AVP 3. Proxy-Info AVP 4. Any other AVP that MUST be present in the response and has no corresponding RADIUS attribute.
1. 原始主机AVP2。会话Id AVP 3。代理信息AVP4。响应中必须存在且没有相应RADIUS属性的任何其他AVP。
- If the CHAP-Auth AVP is present, the grouped AVPs are used to create the RADIUS CHAP-Password attribute data.
- 如果存在CHAP Auth AVP，则分组的AVP用于创建RADIUS CHAP密码属性数据。
- If the User-Password AVP is present, the data should be encrypted and forwarded by using RADIUS rules. The same is true for any other RADIUS-encrypted attribute values.
- 如果存在用户密码AVP，则应使用RADIUS规则对数据进行加密和转发。对于任何其他RADIUS加密属性值也是如此。
- AVPs of the type Address must be translated to the corresponding RADIUS attribute.
- 类型地址的AVP必须转换为相应的RADIUS属性。
- If the Accounting-Input-Octets, Accounting-Input-Packets, Accounting-Output-Octets, or Accounting-Output-Packets AVPs are present, they must be translated to the corresponding RADIUS attributes. If the value of the Diameter AVPs do not fit within a 32-bit RADIUS attribute, the RADIUS Acct-Input-Gigawords and Acct-Output-Gigawords must be used.
- If the Accounting-Input-Octets, Accounting-Input-Packets, Accounting-Output-Octets, or Accounting-Output-Packets AVPs are present, they must be translated to the corresponding RADIUS attributes. If the value of the Diameter AVPs do not fit within a 32-bit RADIUS attribute, the RADIUS Acct-Input-Gigawords and Acct-Output-Gigawords must be used.translate error, please retry
- If the RADIUS link supports the Message-Authenticator attribute [RADIUSExt], it SHOULD be generated and added to the request.
- 如果RADIUS链接支持消息验证器属性[RADIUSExt]，则应生成该属性并将其添加到请求中。
When the corresponding response is received by the Translation Agent, which is guaranteed in the RADIUS protocol, the following steps may be taken:
当翻译代理收到RADIUS协议保证的相应响应时，可采取以下步骤：
- If the RADIUS code is set to Access-Challenge, a Diameter AA-Answer message is created with the Result-Code set to DIAMETER_MULTI_ROUND_AUTH. If the Session-Timeout AVP is present in the RADIUS message, its value is inserted into the Multi-Round-Time-Out AVP.
- 如果RADIUS代码设置为访问质询，则会创建一条Diameter AA应答消息，结果代码设置为Diameter\u MULTI\u ROUND\u AUTH。如果RADIUS消息中存在会话超时AVP，则其值将插入到多轮超时AVP中。
- If a Proxy-State attribute is present, extract the encoded information; otherwise, retrieve the original Proxy-Info AVP group information from the local state table.
- 如果存在代理状态属性，则提取编码信息；否则，从本地状态表中检索原始代理信息AVP组信息。
- The response's Origin-Host information is created from the FQDN of the RADIUS message's source IP address. The same FQDN is also stored to a Route-Record AVP.
- 响应的源主机信息是从RADIUS消息的源IP地址的FQDN创建的。同样的FQDN也存储到路由记录AVP中。
- The response's Destination-Host AVP is copied from the saved request's Origin-Host information.
- 响应的目标主机AVP是从保存的请求的源主机信息复制的。
- The Session-Id information can be recovered from local state, or from the constructed State or Proxy-State attribute, as above.
- 会话Id信息可以从本地状态恢复，也可以从构造的状态或代理状态属性恢复，如上所述。
- If a Proxy-Info AVP was present in the request, the same AVP MUST be added to the response.
- 如果请求中存在代理信息AVP，则必须将相同的AVP添加到响应中。
- If the RADIUS State attributes are present, they must be present in the Diameter response, minus those added by the gateway.
- 如果存在RADIUS状态属性，则它们必须存在于Diameter响应中，减去网关添加的属性。
- Any other AVPs that were saved at request time, and that MUST be present in the response, are added to the message.
- 在请求时保存的以及响应中必须存在的任何其他AVP将添加到消息中。
When translating a RADIUS Access-Accept to Diameter AA-Answer that contains a Session-Timeout attribute, do the following:
将RADIUS Access Accept转换为包含会话超时属性的Diameter AA应答时，请执行以下操作：
- If the RADIUS message contains a Session-Timeout attribute and a Termination-Action attribute set to DEFAULT (or no Termination-Action attribute at all), translate it to AA-Answer with a Session-Timeout AVP and remove the Termination-Action attribute.
- 如果RADIUS消息包含会话超时属性和设置为默认值的终止操作属性（或根本没有终止操作属性），请将其转换为会话超时AVP的AA应答，并删除终止操作属性。
- If the RADIUS message contains a Session-Timeout attribute and a Termination-Action attribute set to AA-REQUEST, translate it to AA-Answer with Authorization-Lifetime AVP and with Re-Auth-Request-Type set to AUTHORIZE_AUTHENTICATE and remove the Session-Timeout attribute.
- 如果RADIUS消息包含会话超时属性和设置为AA-REQUEST的终止操作属性，请将其转换为AA应答，并将授权生存期AVP和重新验证请求类型设置为AUTHORITY\U AUTHERATICATE，然后删除会话超时属性。
A RADIUS/Diameter gateway communicating with a RADIUS client that implements RADIUS Dynamic Authorization [RADDynAuth] may translate Diameter Re-Auth-Request (RAR) messages and Abort-Session-Request (ASR) messages [BASE] into RADIUS CoA-Request and Disconnect-Request messages respectively.
与实现RADIUS动态授权[RADDynAuth]的RADIUS客户端通信的RADIUS/Diameter网关可将Diameter重新授权请求（RAR）消息和中止会话请求（ASR）消息[BASE]分别转换为RADIUS CoA请求和断开连接请求消息。
If the RADIUS client does not support the capability, the gateway will receive an ICMP Port Unreachable indication when it transmits the RADIUS message. Even if the NAS supports [RADDynAuth], it may not support the Service-Type in the request message. In this case it will respond with a NAK message and (optionally) an Error-Cause attribute with value 405, "Unsupported Service". If the gateway encounters these error conditions, or if it does not support [RADDynAuth], it sends a Diameter Answer message with an Result-Code AVP of "DIAMETER_COMMAND_UNSUPPORTED" to the AAA server.
如果RADIUS客户端不支持该功能，网关将在传输RADIUS消息时收到ICMP端口不可访问指示。即使NAS支持[RADDynAuth]，也可能不支持请求消息中的服务类型。在这种情况下，它将使用NAK消息和（可选）值为405“不支持的服务”的错误原因属性进行响应。如果网关遇到这些错误情况，或者不支持[RADDynAuth]，它会向AAA服务器发送一条Diameter应答消息，结果代码为“Diameter_COMMAND_UNSUPPORTED”。
When encoding the RADIUS messages, the gateway MUST include the Diameter Session-ID in the RADIUS State attribute value, as mentioned above. The RADIUS client should return it in the response.
编码RADIUS消息时，网关必须在RADIUS状态属性值中包含Diameter会话ID，如上所述。RADIUS客户端应在响应中返回它。
A Diameter Re-Auth-Request (RAR) message [BASE] received by the gateway will be translated into a RADIUS CoA-Request and sent to the RADIUS client. The RADIUS client should respond with a CoA-ACK or CoA-NAK message, which the gateway should translate into a Re-Auth-Answer (RAA) message.
网关接收到的Diameter重新验证请求（RAR）消息[BASE]将转换为RADIUS CoA请求并发送到RADIUS客户端。RADIUS客户端应使用CoA ACK或CoA NAK消息进行响应，网关应将其转换为重新验证应答（RAA）消息。
If the gateway receives a RADIUS CoA-NAK response containing a Service-Type Attribute with value "Authorize Only" and an Error-Cause Attribute with value "Request Initiated", this indicates an extended exchange request per [RADDynAuth] section 3.2, note 6.
如果网关接收到RADIUS CoA NAK响应，该响应包含值为“仅授权”的服务类型属性和值为“请求已启动”的错误原因属性，这表示根据[RADDynAuth]第3.2节注释6的规定，扩展交换请求。
The response is translated to a Diameter Re-Auth-Answer (RAA) with a Result-Code AVP of "DIAMETER_LIMITED_SUCCESS" sent to the AAA server.
响应被转换为Diameter重新验证应答（RAA），结果代码AVP为“Diameter_LIMITED_SUCCESS”，发送到AAA服务器。
Subsequently, the gateway should receive a RADIUS Access-Request from the NAS, with a Service-Type of "Authorize Only". This is translated into a Diameter AA-Request with an Auth-Request-Type AVP of AUTHORIZE_ONLY and sent to the AAA server. The AAA server will then reply with a Diameter AA-Answer, which is translated into a RADIUS Access-Accept or Access-Reject, depending on the value of the Result-Code AVP.
随后，网关应接收来自NAS的RADIUS访问请求，服务类型为“仅授权”。这将转换为一个Diameter AA请求，其身份验证请求类型为AVP，仅为AUTHORIZE_，并发送到AAA服务器。AAA服务器随后将使用Diameter AA应答进行应答，该应答被转换为RADIUS访问接受或访问拒绝，具体取决于结果代码AVP的值。
A Diameter Abort-Session-Request (ASR) message [BASE] received by the gateway will be translated into a RADIUS Disconnect-Request and sent to the RADIUS client. The RADIUS client should respond with a
网关接收到的Diameter中止会话请求（ASR）消息[BASE]将转换为RADIUS断开连接请求并发送到RADIUS客户端。RADIUS客户端应使用
Disconnect-ACK or Disconnect-NAK message, which the gateway should translate into an Abort-Session-Answer (ASA) message.
断开ACK或断开NAK消息，网关应将其转换为中止会话应答（ASA）消息。
If the gateway receives a RADIUS Disconnect-NAK response containing a Service-Type Attribute with value "Authorize Only" and an Error-Cause Attribute with value "Request Initiated", the Disconnect-NAK response is translated into a Diameter Abort-Session-Answer (ASA) with a Result-Code AVP of "DIAMETER_LIMITED_SUCCESS" sent to the AAA server.
如果网关接收到RADIUS断开NAK响应，该响应包含值为“仅授权”的服务类型属性和值为“已启动请求”的错误原因属性，则断开NAK响应将转换为Diameter中止会话应答（ASA），并将结果代码AVP“Diameter\u LIMITED\u SUCCESS”发送到AAA服务器。
Subsequently, the gateway should receive a RADIUS Access-Request from the NAS, with a Service-Type of "Authorize Only". This is translated into a Diameter AA-Request with an Auth-Request-Type AVP of AUTHORIZE_ONLY and sent to the AAA server. The AAA server will then reply with a Diameter AA-Answer, which is translated into a RADIUS Access-Accept or Access-Reject, depending on the value of the Result-Code AVP.
随后，网关应接收来自NAS的RADIUS访问请求，服务类型为“仅授权”。这将转换为一个Diameter AA请求，其身份验证请求类型为AVP，仅为AUTHORIZE_，并发送到AAA服务器。AAA服务器随后将使用Diameter AA应答进行应答，该应答被转换为RADIUS访问接受或访问拒绝，具体取决于结果代码AVP的值。
The AVPs defined in this section SHOULD only be used for backwards compatibility when a Diameter/RADIUS translation function is invoked and are not typically originated by Diameter systems during normal operations.
当调用直径/半径转换函数时，本节中定义的AVP仅用于向后兼容，并且在正常操作期间通常不是由直径系统发起的。
+---------------------+
| AVP Flag rules |
|----+-----+----+-----|----+
AVP Section | | |SHLD| MUST| |
Attribute Name Code Defined Value Type |MUST| MAY | NOT| NOT|Encr|
-----------------------------------------|----+-----+----+-----|----|
NAS-Identifier 32 9.3.1 UTF8String | M | P | | V | Y |
NAS-IP-Address 4 9.3.2 OctetString| M | P | | V | Y |
NAS-IPv6-Address 95 9.3.3 OctetString| M | P | | V | Y |
State 24 9.3.4 OctetString| M | P | | V | Y |
Termination- 295 9.3.5 Enumerated | M | P | | V | Y |
Cause | | | | | |
Origin-AAA- 408 9.3.6 Enumerated | M | P | | V | Y |
Protocol | | | | | |
-----------------------------------------|----+-----+----+-----|----|
+---------------------+
| AVP Flag rules |
|----+-----+----+-----|----+
AVP Section | | |SHLD| MUST| |
Attribute Name Code Defined Value Type |MUST| MAY | NOT| NOT|Encr|
-----------------------------------------|----+-----+----+-----|----|
NAS-Identifier 32 9.3.1 UTF8String | M | P | | V | Y |
NAS-IP-Address 4 9.3.2 OctetString| M | P | | V | Y |
NAS-IPv6-Address 95 9.3.3 OctetString| M | P | | V | Y |
State 24 9.3.4 OctetString| M | P | | V | Y |
Termination- 295 9.3.5 Enumerated | M | P | | V | Y |
Cause | | | | | |
Origin-AAA- 408 9.3.6 Enumerated | M | P | | V | Y |
Protocol | | | | | |
-----------------------------------------|----+-----+----+-----|----|
The NAS-Identifier AVP (AVP Code 32) [RADIUS] is of type UTF8String and contains the identity of the NAS providing service to the user. This AVP SHOULD only be added by a RADIUS/Diameter Translation Agent. When this AVP is present, the Origin-Host AVP identifies the NAS providing service to the user.
NAS标识符AVP（AVP代码32）[RADIUS]为UTF8String类型，包含向用户提供服务的NAS的标识。此AVP只能由半径/直径转换代理添加。当存在此AVP时，源主机AVP识别向用户提供服务的NAS。
In RADIUS it would be possible for a rogue NAS to forge the NAS-Identifier attribute. Diameter/RADIUS translation agents SHOULD attempt to check a received NAS-Identifier attribute against the source address of the RADIUS packet, by doing an A/AAAA RR query. If the NAS-Identifier attribute contains an FQDN, then such a query would resolve to an IP address matching the source address. However, the NAS-Identifier attribute is not required to contain an FQDN, so such a query could fail. If it fails, an error should be logged, but no action should be taken, other than a reverse lookup on the source address and insert the resulting FQDN into the Route-Record AVP.
在RADIUS中，流氓NAS可能伪造NAS标识符属性。Diameter/RADIUS翻译代理应通过执行a/AAAA RR查询，尝试根据RADIUS数据包的源地址检查接收到的NAS标识符属性。如果NAS标识符属性包含FQDN，则此类查询将解析为与源地址匹配的IP地址。但是，NAS标识符属性不需要包含FQDN，因此这样的查询可能会失败。如果失败，则应记录一个错误，但除了对源地址进行反向查找并将结果FQDN插入路由记录AVP之外，不应采取任何操作。
Diameter agents and servers SHOULD check whether a NAS-Identifier AVP corresponds to an entry in the Route-Record AVP. If no match is found, then an error is logged, but no other action is taken.
Diameter代理和服务器应检查NAS标识符AVP是否对应于路由记录AVP中的条目。如果未找到匹配项，则会记录错误，但不会采取其他操作。
The NAS-IP-Address AVP (AVP Code 4) [RADIUS] is of type OctetString and contains the IP Address of the NAS providing service to the user. This AVP SHOULD only be added by a RADIUS/Diameter Translation Agent. When this AVP is present, the Origin-Host AVP identifies the NAS providing service to the user.
NAS IP地址AVP（AVP代码4）[RADIUS]为OctetString类型，包含向用户提供服务的NAS的IP地址。此AVP只能由半径/直径转换代理添加。当存在此AVP时，源主机AVP识别向用户提供服务的NAS。
In RADIUS it would be possible for a rogue NAS to forge the NAS-IP-Address attribute value. Diameter/RADIUS translation agents MUST check a received NAS-IP-Address or NAS-IPv6-Address attribute against the source address of the RADIUS packet. If they do not match and the Diameter/RADIUS translation agent does not know whether the packet was sent by a RADIUS proxy or NAS (e.g., no Proxy-State attribute), then by default it is assumed that the source address corresponds to a RADIUS proxy, and that the NAS Address is behind that proxy, potentially with some additional RADIUS proxies in between. The Diameter/RADIUS translation agent MUST insert entries in the Route-Record AVP corresponding to the apparent route. This implies doing a reverse lookup on the source address and NAS-IP-Address or NAS-IPv6-Address attributes to determine the corresponding FQDNs.
在RADIUS中，流氓NAS可能伪造NAS IP地址属性值。Diameter/RADIUS转换代理必须对照RADIUS数据包的源地址检查接收到的NAS IP地址或NAS-IPv6-Address属性。如果它们不匹配，且Diameter/RADIUS转换代理不知道数据包是由RADIUS代理还是NAS发送的（例如，无代理状态属性），则默认情况下，假定源地址对应于RADIUS代理，且NAS地址位于该代理之后，可能有一些额外的半径代理介于两者之间。直径/半径转换代理必须在路由记录AVP中插入与视在路由对应的条目。这意味着对源地址和NAS IP地址或NAS-IPv6-address属性进行反向查找，以确定相应的FQDN。
If the source address and the NAS-IP-Address or NAS-IPv6-Address do not match, and the Diameter/RADIUS translation agent knows that it is talking directly to the NAS (e.g., there are no RADIUS proxies between it and the NAS), then the error should be logged, and the packet MUST be discarded.
如果源地址与NAS IP地址或NAS-IPv6-address不匹配，并且Diameter/RADIUS转换代理知道它正在直接与NAS通信（例如，它与NAS之间没有RADIUS代理），则应记录错误，并且必须丢弃数据包。
Diameter agents and servers MUST check whether the NAS-IP-Address AVP corresponds to an entry in the Route-Record AVP. This is done by doing a reverse lookup (PTR RR) for the NAS-IP-Address to retrieve the corresponding FQDN, and by checking for a match with the Route-
Diameter代理和服务器必须检查NAS IP地址AVP是否对应于路由记录AVP中的条目。这是通过对NAS IP地址执行反向查找（PTR RR）来检索相应的FQDN，并通过检查与路由的匹配来完成的-
Record AVP. If no match is found, then an error is logged, but no other action is taken.
记录AVP。如果未找到匹配项，则会记录错误，但不会采取其他操作。
The NAS-IPv6-Address AVP (AVP Code 95) [RADIUSIPv6] is of type OctetString and contains the IPv6 Address of the NAS providing service to the user. This AVP SHOULD only be added by a RADIUS/Diameter Translation Agent. When this AVP is present, the Origin-Host AVP identifies the NAS providing service to the user.
NAS-IPv6-Address AVP（AVP代码95）[RadiusPv6]为OctetString类型，包含向用户提供服务的NAS的IPv6地址。此AVP只能由半径/直径转换代理添加。当存在此AVP时，源主机AVP识别向用户提供服务的NAS。
In RADIUS it would be possible for a rogue NAS to forge the NAS-IPv6-Address attribute. Diameter/RADIUS translation agents MUST check a received NAS-IPv6-Address attribute against the source address of the RADIUS packet. If they do not match and the Diameter/RADIUS translation agent does not know whether the packet was sent by a RADIUS proxy or NAS (e.g., no Proxy-State attribute), then by default it is assumed that the source address corresponds to a RADIUS proxy, and that the NAS-IPv6-Address is behind that proxy, potentially with some additional RADIUS proxies in between. The Diameter/RADIUS translation agent MUST insert entries in the Route-Record AVP corresponding to the apparent route. This implies doing a reverse lookup on the source address and NAS-IPv6-Address attributes to determine the corresponding FQDNs.
在RADIUS中，流氓NAS可能伪造NAS-IPv6-Address属性。Diameter/RADIUS转换代理必须根据RADIUS数据包的源地址检查接收到的NAS-IPv6-Address属性。如果它们不匹配，且Diameter/RADIUS转换代理不知道数据包是由RADIUS代理还是NAS发送的（例如，无代理状态属性），则默认情况下，假定源地址对应于RADIUS代理，且NAS-IPv6-address位于该代理之后，可能有一些额外的半径代理介于两者之间。直径/半径转换代理必须在路由记录AVP中插入与视在路由对应的条目。这意味着对源地址和NAS-IPv6-address属性进行反向查找，以确定相应的FQDN。
If the source address and the NAS-IPv6-Address do not match, and the Diameter/RADIUS translation agent knows that it is talking directly to the NAS (e.g., there are no RADIUS proxies between it and the NAS), then the error should be logged, and the packet MUST be discarded.
如果源地址和NAS-IPv6-address不匹配，并且Diameter/RADIUS转换代理知道它正在直接与NAS通信（例如，它与NAS之间没有RADIUS代理），则应记录错误，并且必须丢弃数据包。
Diameter agents and servers MUST check whether the NAS-IPv6-Address AVP corresponds to an entry in the Route-Record AVP. This is done by doing a reverse lookup (PTR RR) for the NAS-IPv6-Address to retrieve the corresponding FQDN, and by checking for a match with the Record-Route AVP. If no match is found, then an error is logged, but no other action is taken.
Diameter代理和服务器必须检查NAS-IPv6-Address AVP是否对应于路由记录AVP中的条目。这是通过对NAS-IPv6-Address执行反向查找（PTR RR）以检索相应的FQDN，并通过检查与记录路由AVP的匹配来完成的。如果未找到匹配项，则会记录错误，但不会采取其他操作。
The State AVP (AVP Code 24) [RADIUS] is of type OctetString and has two uses in the Diameter NAS application.
状态AVP（AVP代码24）[RADIUS]为OctetString类型，在Diameter NAS应用程序中有两种用途。
The State AVP MAY be sent by a Diameter Server to a NAS in an AA-Response command that contains a Result-Code of DIAMETER_MULTI_ROUND_AUTH. If so, the NAS MUST return it unmodified in the subsequent AA-Request command.
状态AVP可由Diameter服务器在AA响应命令中发送给NAS，该命令包含Diameter\u MULTI\u ROUND\u AUTH的结果代码。如果是这样，NAS必须在随后的AA请求命令中未经修改地返回它。
The State AVP MAY also be sent by a Diameter Server to a NAS in an AA-Response command that also includes a Termination-Action AVP with the value of AA-REQUEST. If the NAS performs the Termination-Action by sending a new AA-Request command upon termination of the current service, it MUST return the State AVP unmodified in the new request command.
状态AVP也可以由Diameter服务器在AA响应命令中发送到NAS，该AA响应命令还包括具有AA-REQUEST值的终止动作AVP。如果NAS通过在当前服务终止时发送新的AA请求命令来执行终止操作，则必须在新请求命令中返回未修改的状态AVP。
In either usage, the NAS MUST NOT interpret the AVP locally. Usage of the State AVP is implementation dependent.
在这两种情况下，NAS都不得在本地解释AVP。状态AVP的使用取决于实现。
This section defines a mapping between Termination-Cause AVP code values and RADIUS Acct-Terminate-Cause attribute code values from RFC 2866 [RADIUSAcct] and [RADIUSTypes], thereby allowing a RADIUS/Diameter Translation Agent to convert between the attribute and AVP values. This section thus extends the definitions in the "Termination-Cause AVP" section of the Base Diameter specification.
本节定义了RFC 2866[RADIUSAcct]和[RADIUSTypes]中终止原因AVP代码值和RADIUS Acct终止原因属性代码值之间的映射，从而允许RADIUS/Diameter转换代理在属性和AVP值之间进行转换。因此，本节扩展了基础直径规范“终止原因AVP”一节中的定义。
The table in this section defines the mapping between Termination-Cause AVP and RADIUS Acct-Terminate-Cause causes.
本节中的表格定义了终止原因AVP和RADIUS Acct终止原因原因之间的映射。
+-----------------------+
| Value |
+-----------+-----------+
Cause Value Name | RADIUS | Diameter |
------------------------------|-----------+-----------+
User Request | 1 | 11 |
Lost Carrier | 2 | 12 |
Lost Service | 3 | 13 |
Idle Timeout | 4 | 14 |
Session Timeout | 5 | 15 |
Admin Reset | 6 | 16 |
Admin Reboot | 7 | 17 |
Port Error | 8 | 18 |
NAS Error | 9 | 19 |
NAS Request | 10 | 20 |
NAS Reboot | 11 | 21 |
Port Unneeded | 12 | 22 |
Port Preempted | 13 | 23 |
Port Suspended | 14 | 24 |
Service Unavailable | 15 | 25 |
Callback | 16 | 26 |
User Error | 17 | 27 |
Host Request | 18 | 28 |
Supplicant Restart | 19 | 29 | [RAD802.1X]
Reauthentication Failure | 20 | 30 | [RAD802.1X]
Port Reinit | 21 | 31 | [RAD802.1X]
Port Disabled | 22 | 32 | [RAD802.1X]
------------------------------|-----------+-----------+
+-----------------------+
| Value |
+-----------+-----------+
Cause Value Name | RADIUS | Diameter |
------------------------------|-----------+-----------+
User Request | 1 | 11 |
Lost Carrier | 2 | 12 |
Lost Service | 3 | 13 |
Idle Timeout | 4 | 14 |
Session Timeout | 5 | 15 |
Admin Reset | 6 | 16 |
Admin Reboot | 7 | 17 |
Port Error | 8 | 18 |
NAS Error | 9 | 19 |
NAS Request | 10 | 20 |
NAS Reboot | 11 | 21 |
Port Unneeded | 12 | 22 |
Port Preempted | 13 | 23 |
Port Suspended | 14 | 24 |
Service Unavailable | 15 | 25 |
Callback | 16 | 26 |
User Error | 17 | 27 |
Host Request | 18 | 28 |
Supplicant Restart | 19 | 29 | [RAD802.1X]
Reauthentication Failure | 20 | 30 | [RAD802.1X]
Port Reinit | 21 | 31 | [RAD802.1X]
Port Disabled | 22 | 32 | [RAD802.1X]
------------------------------|-----------+-----------+
From RFC 2866, the termination causes are as follows:
根据RFC 2866，终止原因如下：
User Request User requested termination of service, for example with LCP Terminate or by logging out.
用户请求用户请求终止服务，例如通过LCP终止或注销。
Lost Carrier DCD was dropped on the port.
丢失的载波DCD被丢弃在端口上。
Lost Service Service can no longer be provided; for example, user's connection to a host was interrupted.
无法再提供丢失服务；例如，用户与主机的连接被中断。
Idle Timeout Idle timer expired.
空闲超时空闲计时器已过期。
Session Timeout Maximum session length timer expired.
会话超时最大会话长度计时器已过期。
Admin Reset Administrator reset the port or session.
管理员重置管理员重置端口或会话。
Admin Reboot Administrator is ending service on the NAS, for example, prior to rebooting the NAS.
管理员重新启动管理员正在终止NAS上的服务，例如，在重新启动NAS之前。
Port Error NAS detected an error on the port that required ending the session.
端口错误NAS在需要结束会话的端口上检测到错误。
NAS Error NAS detected an error (other than on the port) that required ending the session.
NAS错误NAS检测到需要结束会话的错误（端口上的错误除外）。
NAS Request NAS ended the session for a non-error reason not otherwise listed here.
NAS请求NAS由于此处未列出的非错误原因结束了会话。
NAS Reboot NAS ended the session to reboot non-administratively ("crash").
NAS重新启动NAS结束了以非管理方式重新启动的会话（“崩溃”）。
Port Unneeded NAS ended the session because resource usage fell below a low-water mark (for example, if a bandwidth-on-demand algorithm decided that the port was no longer needed).
不需要端口的NAS结束会话，因为资源使用率低于低水位线（例如，如果按需带宽算法决定不再需要该端口）。
Port Preempted NAS ended the session to allocate the port to a higher priority use.
端口抢占NAS结束会话以将端口分配给更高优先级的使用。
Port Suspended NAS ended the session to suspend a virtual session.
端口挂起NAS结束会话以挂起虚拟会话。
Service Unavailable NAS was unable to provide requested service.
服务不可用NAS无法提供请求的服务。
Callback NAS is terminating the current session to perform callback for a new session.
回调NAS正在终止当前会话以对新会话执行回调。
User Error Input from user is in error, causing session termination.
来自用户的用户错误输入出错，导致会话终止。
Host Request Login Host terminated session normally.
主机请求登录主机正常终止会话。
The Origin-AAA-Protocol AVP (AVP Code 408) is of the type Enumerated and should be inserted in a Diameter message translated by a gateway system from another AAA protocol, such as RADIUS. It identifies the source protocol of the message to the Diameter system receiving the message.
源AAA协议AVP（AVP代码408）是枚举的类型，并且应当插入到由网关系统从另一AAA协议（例如RADIUS）翻译的Diameter消息中。它向接收消息的Diameter系统标识消息的源协议。
The supported values are:
支持的值包括：
1 RADIUS
1半径
The following RADIUS attributes MUST NOT appear in a Diameter message. Instead, they are translated to other Diameter AVPs or handled in some special manner. The rules for the treatment of the attributes are discussed in sections 9.1, 9.2, and 9.6.
以下半径属性不得出现在直径消息中。相反，它们被转换为其他直径AVP或以某种特殊方式处理。第9.1、9.2和9.6节讨论了属性处理规则。
Attribute Description Defined Nearest Diameter AVP
-----------------------------------------------------------------
3 CHAP-Password RFC 2865 CHAP-Auth Group
26 Vendor-Specific RFC 2865 Vendor Specific AVP
29 Termination-Action RFC 2865 Authorization-Lifetime
40 Acct-Status-Type RFC 2866 Accounting-Record-Type
42 Acct-Input-Octets RFC 2866 Accounting-Input-Octets
43 Acct-Output-Octets RFC 2866 Accounting-Output-Octets
47 Acct-Input-Packets RFC 2866 Accounting-Input-Packets
48 Acct-Output-Packets RFC 2866 Accounting-Output-Packets
49 Acct-Terminate-Cause RFC 2866 Termination-Cause
52 Acct-Input-Gigawords RFC 2869 Accounting-Input-Octets
53 Acct-Output-Gigawords RFC 2869 Accounting-Output-Octets
80 Message-Authenticator RFC 2869 none - check and discard
Attribute Description Defined Nearest Diameter AVP
-----------------------------------------------------------------
3 CHAP-Password RFC 2865 CHAP-Auth Group
26 Vendor-Specific RFC 2865 Vendor Specific AVP
29 Termination-Action RFC 2865 Authorization-Lifetime
40 Acct-Status-Type RFC 2866 Accounting-Record-Type
42 Acct-Input-Octets RFC 2866 Accounting-Input-Octets
43 Acct-Output-Octets RFC 2866 Accounting-Output-Octets
47 Acct-Input-Packets RFC 2866 Accounting-Input-Packets
48 Acct-Output-Packets RFC 2866 Accounting-Output-Packets
49 Acct-Terminate-Cause RFC 2866 Termination-Cause
52 Acct-Input-Gigawords RFC 2869 Accounting-Input-Octets
53 Acct-Output-Gigawords RFC 2869 Accounting-Output-Octets
80 Message-Authenticator RFC 2869 none - check and discard
In general, Diameter AVPs that are not RADIUS compatible have code values greater than 255. The table in the section above shows the AVPs that can be converted into RADIUS attributes.
通常，半径不兼容的直径AVP的代码值大于255。上节中的表格显示了可转换为半径属性的AVP。
Another problem may occur with Diameter AVP values that may be more than 253 octets in length. Some RADIUS attributes (including but not limited to (8)Reply-Message, (79)EAP-Message, and (77)Connect-Info) allow concatenation of multiple instances to overcome this limitation. If this is not possible, a Result-Code of DIAMETER_INVALID_AVP_LENGTH should be returned.
直径AVP值可能会出现另一个问题，其长度可能超过253个八位字节。一些RADIUS属性（包括但不限于（8）回复消息、（79）EAP消息和（77）连接信息）允许连接多个实例以克服此限制。如果这不可能，则应返回DIAMETER_INVALID_AVP_LENGTH的结果代码。
RADIUS supports the inclusion of Vendor Specific Attributes (VSAs) through the use of attribute 26. The recommended format [RADIUS] of the attribute data field includes a 4 octet vendor code followed by a one octet vendor type field and a one octet length field. The last two fields MAY be repeated.
RADIUS支持通过使用属性26包含特定于供应商的属性（VSA）。属性数据字段的推荐格式[RADIUS]包括4个八位字节的供应商代码，后跟一个八位字节的供应商类型字段和一个八位字节的长度字段。最后两个字段可以重复。
A system communicating between Diameter and RADIUS MAY have specific knowledge of vendor formats, and MAY be able to translate between the two formats. However, given the deployment of many RADIUS vendor formats that do not follow the example format in RFC 2865 [RADIUS], (e.g., those that use a longer vendor type code) the translations in
直径和半径之间通信的系统可能具有供应商格式的特定知识，并且可能能够在两种格式之间进行转换。但是，由于部署了许多RADIUS供应商格式，这些格式不遵循RFC 2865[RADIUS]中的示例格式（例如，使用较长供应商类型代码的格式），因此
the next two sections will not work in general for those VSAs. RFC 2865 states that a robust implementation SHOULD support the field as undistinguished octets.
接下来的两个部分通常不适用于这些VSA。RFC2865指出，一个健壮的实现应该支持字段作为无差别的八位字节。
Systems that don't have vendor format knowledge MAY discard such attributes without knowing a suitable translation. An alternative format is under consideration [VSA], which proposes encodings that would preserve the native information and not require vendor knowledge in the gateway system.
没有供应商格式知识的系统可能会在不知道适当翻译的情况下丢弃这些属性。另一种替代格式[VSA]正在考虑中，它提出的编码将保留本机信息，并且不需要网关系统中的供应商知识。
The following sections are an example for translating RADIUS VSAs that use the example RADIUS format, and Diameter VSAs that have type codes less than 255, and value field lengths less than 252.
以下部分是转换使用示例RADIUS格式的RADIUS VSA和类型代码小于255、值字段长度小于252的Diameter VSA的示例。
For Type codes less than 255, the value field length MUST be less than 252 or the AVP will be discarded. The RADIUS VSA attribute should consist of the following fields;
对于小于255的类型代码，值字段长度必须小于252，否则将丢弃AVP。半径VSA属性应包括以下字段：；
RADIUS Type = 26, Vendor Specific Attribute RADIUS Length = total length of attribute (header + data) RADIUS Vendor code = Diameter Vendor code RADIUS Vendor type code = low order byte of Diameter AVP code RADIUS Vendor data length = length of Diameter data
半径类型=26，供应商特定属性半径长度=属性总长度（标题+数据）半径供应商代码=直径供应商代码半径供应商类型代码=直径的低位字节AVP代码半径供应商数据长度=直径数据的长度
If the Diameter AVP code is greater than 255, then the RADIUS speaking code may use a Vendor specific field coding, if it knows one for that vendor. Otherwise, the AVP will be ignored. If it is flagged as Mandatory, a "DIAMETER_AVP_UNSUPPORTED" Result-Code will be returned, and the RADIUS message will not be sent.
如果Diameter AVP代码大于255，则RADIUS语音代码可以使用供应商特定的字段编码（如果知道该供应商的字段编码）。否则，AVP将被忽略。如果标记为强制，将返回“DIAMETER_AVP_UNSUPPORTED”结果代码，并且不会发送RADIUS消息。
The Diameter AVP will consist of the following fields:
直径AVP将由以下字段组成：
Diameter Flags: V=1, M=0, P=0
Diameter Vendor code = RADIUS VSA Vendor code
Diameter AVP code = RADIUS VSA Vendor type code
Diameter AVP length = length of AVP (header + data)
Diameter Data = RADIUS VSA vendor data
Diameter Flags: V=1, M=0, P=0
Diameter Vendor code = RADIUS VSA Vendor code
Diameter AVP code = RADIUS VSA Vendor type code
Diameter AVP length = length of AVP (header + data)
Diameter Data = RADIUS VSA vendor data
Note that the VSAs are considered optional by RADIUS rules, and this specification does not set the Mandatory flag. If an implementor desires a VSA be made mandatory because it represents a required service policy, the RADIUS gateway should have a process to set the bit on the Diameter side.
注意，根据RADIUS规则，VSA被认为是可选的，并且本规范没有设置强制标志。如果实施者希望强制执行VSA，因为它表示所需的服务策略，那么RADIUS网关应该有一个在Diameter侧设置位的过程。
If the RADIUS receiving code knows of vendor specific field interpretations for the specific vendor, it may employ them to parse an extended AVP code or data length. Otherwise the recommended standard fields will be used.
如果RADIUS接收代码知道特定供应商的特定字段解释，则可以使用它们解析扩展AVP代码或数据长度。否则，将使用推荐的标准字段。
Nested Multiple vendor data fields MUST be expanded into multiple Diameter AVPs.
嵌套的多供应商数据字段必须扩展为多个直径AVP。
The following tables present the AVPs used by NAS applications in NAS messages and specify in which Diameter messages they MAY or MAY NOT be present. [BASE] messages and AVPs are not described in this document. Note that AVPs that can only be present within a Grouped AVP are not represented in this table.
下表显示了NAS应用程序在NAS消息中使用的AVP，并指定它们可能存在或不存在于哪些Diameter消息中。[BASE]本文档中未描述消息和AVP。请注意，此表中未显示只能出现在分组AVP中的AVP。
The table uses the following symbols:
该表使用以下符号：
0 The AVP MUST NOT be present in the message. 0+ Zero or more instances of the AVP MAY be present in the message. 0-1 Zero or one instance of the AVP MAY be present in the message. 1 One instance of the AVP MUST be present in the message.
0消息中不得出现AVP。消息中可能存在0+零个或多个AVP实例。0-1消息中可能存在零个或一个AVP实例。1消息中必须有一个AVP实例。
The table in this section is limited to the Command Codes defined in this specification.
本节中的表格仅限于本规范中定义的命令代码。
+-----------+
| Command |
|-----+-----+
Attribute Name | AAR | AAA |
------------------------------|-----+-----+
Acct-Interim-Interval | 0 | 0-1 |
ARAP-Challenge-Response | 0 | 0-1 |
ARAP-Features | 0 | 0-1 |
ARAP-Password | 0-1 | 0 |
ARAP-Security | 0-1 | 0-1 |
ARAP-Security-Data | 0+ | 0+ |
ARAP-Zone-Access | 0 | 0-1 |
Auth-Application-Id | 1 | 1 |
Auth-Grace-Period | 0-1 | 0-1 |
Auth-Request-Type | 1 | 1 |
Auth-Session-State | 0-1 | 0-1 |
Authorization-Lifetime | 0-1 | 0-1 |
------------------------------|-----+-----+
+-----------+
| Command |
|-----+-----+
Attribute Name | AAR | AAA |
------------------------------|-----+-----+
Acct-Interim-Interval | 0 | 0-1 |
ARAP-Challenge-Response | 0 | 0-1 |
ARAP-Features | 0 | 0-1 |
ARAP-Password | 0-1 | 0 |
ARAP-Security | 0-1 | 0-1 |
ARAP-Security-Data | 0+ | 0+ |
ARAP-Zone-Access | 0 | 0-1 |
Auth-Application-Id | 1 | 1 |
Auth-Grace-Period | 0-1 | 0-1 |
Auth-Request-Type | 1 | 1 |
Auth-Session-State | 0-1 | 0-1 |
Authorization-Lifetime | 0-1 | 0-1 |
------------------------------|-----+-----+
+-----------+
| Command |
|-----+-----+
Attribute Name | AAR | AAA |
------------------------------|-----+-----+
Callback-Id | 0 | 0-1 |
Callback-Number | 0-1 | 0-1 |
Called-Station-Id | 0-1 | 0 |
Calling-Station-Id | 0-1 | 0 |
CHAP-Auth | 0-1 | 0 |
CHAP-Challenge | 0-1 | 0 |
Class | 0 | 0+ |
Configuration-Token | 0 | 0+ |
Connect-Info | 0+ | 0 |
Destination-Host | 0-1 | 0 |
Destination-Realm | 1 | 0 |
Error-Message | 0 | 0-1 |
Error-Reporting-Host | 0 | 0-1 |
Failed-AVP | 0+ | 0+ |
Filter-Id | 0 | 0+ |
Framed-Appletalk-Link | 0 | 0-1 |
Framed-Appletalk-Network | 0 | 0+ |
Framed-Appletalk-Zone | 0 | 0-1 |
Framed-Compression | 0+ | 0+ |
Framed-Interface-Id | 0-1 | 0-1 |
Framed-IP-Address | 0-1 | 0-1 |
Framed-IP-Netmask | 0-1 | 0-1 |
Framed-IPv6-Prefix | 0+ | 0+ |
Framed-IPv6-Pool | 0 | 0-1 |
Framed-IPv6-Route | 0 | 0+ |
Framed-IPX-Network | 0 | 0-1 |
Framed-MTU | 0-1 | 0-1 |
Framed-Pool | 0 | 0-1 |
Framed-Protocol | 0-1 | 0-1 |
Framed-Route | 0 | 0+ |
Framed-Routing | 0 | 0-1 |
Idle-Timeout | 0 | 0-1 |
Login-IP-Host | 0+ | 0+ |
Login-IPv6-Host | 0+ | 0+ |
Login-LAT-Group | 0-1 | 0-1 |
Login-LAT-Node | 0-1 | 0-1 |
Login-LAT-Port | 0-1 | 0-1 |
Login-LAT-Service | 0-1 | 0-1 |
Login-Service | 0 | 0-1 |
Login-TCP-Port | 0 | 0-1 |
Multi-Round-Time-Out | 0 | 0-1 |
------------------------------|-----+-----+
+-----------+
| Command |
|-----+-----+
Attribute Name | AAR | AAA |
------------------------------|-----+-----+
Callback-Id | 0 | 0-1 |
Callback-Number | 0-1 | 0-1 |
Called-Station-Id | 0-1 | 0 |
Calling-Station-Id | 0-1 | 0 |
CHAP-Auth | 0-1 | 0 |
CHAP-Challenge | 0-1 | 0 |
Class | 0 | 0+ |
Configuration-Token | 0 | 0+ |
Connect-Info | 0+ | 0 |
Destination-Host | 0-1 | 0 |
Destination-Realm | 1 | 0 |
Error-Message | 0 | 0-1 |
Error-Reporting-Host | 0 | 0-1 |
Failed-AVP | 0+ | 0+ |
Filter-Id | 0 | 0+ |
Framed-Appletalk-Link | 0 | 0-1 |
Framed-Appletalk-Network | 0 | 0+ |
Framed-Appletalk-Zone | 0 | 0-1 |
Framed-Compression | 0+ | 0+ |
Framed-Interface-Id | 0-1 | 0-1 |
Framed-IP-Address | 0-1 | 0-1 |
Framed-IP-Netmask | 0-1 | 0-1 |
Framed-IPv6-Prefix | 0+ | 0+ |
Framed-IPv6-Pool | 0 | 0-1 |
Framed-IPv6-Route | 0 | 0+ |
Framed-IPX-Network | 0 | 0-1 |
Framed-MTU | 0-1 | 0-1 |
Framed-Pool | 0 | 0-1 |
Framed-Protocol | 0-1 | 0-1 |
Framed-Route | 0 | 0+ |
Framed-Routing | 0 | 0-1 |
Idle-Timeout | 0 | 0-1 |
Login-IP-Host | 0+ | 0+ |
Login-IPv6-Host | 0+ | 0+ |
Login-LAT-Group | 0-1 | 0-1 |
Login-LAT-Node | 0-1 | 0-1 |
Login-LAT-Port | 0-1 | 0-1 |
Login-LAT-Service | 0-1 | 0-1 |
Login-Service | 0 | 0-1 |
Login-TCP-Port | 0 | 0-1 |
Multi-Round-Time-Out | 0 | 0-1 |
------------------------------|-----+-----+
+-----------+
| Command |
|-----+-----+
Attribute Name | AAR | AAA |
------------------------------|-----+-----+
NAS-Filter-Rule | 0 | 0+ |
NAS-Identifier | 0-1 | 0 |
NAS-IP-Address | 0-1 | 0 |
NAS-IPv6-Address | 0-1 | 0 |
NAS-Port | 0-1 | 0 |
NAS-Port-Id | 0-1 | 0 |
NAS-Port-Type | 0-1 | 0 |
Origin-AAA-Protocol | 0-1 | 0-1 |
Origin-Host | 1 | 1 |
Origin-Realm | 1 | 1 |
Origin-State-Id | 0-1 | 0-1 |
Originating-Line-Info | 0-1 | 0 |
Password-Retry | 0 | 0-1 |
Port-Limit | 0-1 | 0-1 |
Prompt | 0 | 0-1 |
Proxy-Info | 0+ | 0+ |
QoS-Filter-Rule | 0 | 0+ |
Re-Auth-Request-Type | 0 | 0-1 |
Redirect-Host | 0 | 0+ |
Redirect-Host-Usage | 0 | 0-1 |
Redirect-Max-Cache-Time | 0 | 0-1 |
Reply-Message | 0 | 0+ |
Result-Code | 0 | 1 |
Route-Record | 0+ | 0+ |
Service-Type | 0-1 | 0-1 |
Session-Id | 1 | 1 |
Session-Timeout | 0 | 0-1 |
State | 0-1 | 0-1 |
Tunneling | 0+ | 0+ |
User-Name | 0-1 | 0-1 |
User-Password | 0-1 | 0 |
------------------------------|-----+-----+
+-----------+
| Command |
|-----+-----+
Attribute Name | AAR | AAA |
------------------------------|-----+-----+
NAS-Filter-Rule | 0 | 0+ |
NAS-Identifier | 0-1 | 0 |
NAS-IP-Address | 0-1 | 0 |
NAS-IPv6-Address | 0-1 | 0 |
NAS-Port | 0-1 | 0 |
NAS-Port-Id | 0-1 | 0 |
NAS-Port-Type | 0-1 | 0 |
Origin-AAA-Protocol | 0-1 | 0-1 |
Origin-Host | 1 | 1 |
Origin-Realm | 1 | 1 |
Origin-State-Id | 0-1 | 0-1 |
Originating-Line-Info | 0-1 | 0 |
Password-Retry | 0 | 0-1 |
Port-Limit | 0-1 | 0-1 |
Prompt | 0 | 0-1 |
Proxy-Info | 0+ | 0+ |
QoS-Filter-Rule | 0 | 0+ |
Re-Auth-Request-Type | 0 | 0-1 |
Redirect-Host | 0 | 0+ |
Redirect-Host-Usage | 0 | 0-1 |
Redirect-Max-Cache-Time | 0 | 0-1 |
Reply-Message | 0 | 0+ |
Result-Code | 0 | 1 |
Route-Record | 0+ | 0+ |
Service-Type | 0-1 | 0-1 |
Session-Id | 1 | 1 |
Session-Timeout | 0 | 0-1 |
State | 0-1 | 0-1 |
Tunneling | 0+ | 0+ |
User-Name | 0-1 | 0-1 |
User-Password | 0-1 | 0 |
------------------------------|-----+-----+
The tables in this section are used to show which AVPs defined in this document are to be present and used in NAS application Accounting messages. These AVPs are defined in this document, as well as in [BASE] and [RADIUSAcct].
本节中的表格用于显示本文档中定义的哪些AVP将出现并用于NAS应用程序记帐消息。本文件以及[BASE]和[RADIUSACT]中定义了这些AVP。
The table in this section is used when the Service-Type specifies Framed Access.
当服务类型指定框架访问时，将使用本节中的表。
+-----------+
| Command |
|-----+-----+
Attribute Name | ACR | ACA |
---------------------------------------|-----+-----+
Accounting-Auth-Method | 0-1 | 0 |
Accounting-Input-Octets | 1 | 0 |
Accounting-Input-Packets | 1 | 0 |
Accounting-Output-Octets | 1 | 0 |
Accounting-Output-Packets | 1 | 0 |
Accounting-Record-Number | 0-1 | 0-1 |
Accounting-Record-Type | 1 | 1 |
Accounting-Realtime-Required | 0-1 | 0-1 |
Accounting-Sub-Session-Id | 0-1 | 0-1 |
Acct-Application-Id | 0-1 | 0-1 |
Acct-Session-Id | 1 | 0-1 |
Acct-Multi-Session-Id | 0-1 | 0-1 |
Acct-Authentic | 1 | 0 |
Acct-Delay-Time | 0-1 | 0 |
Acct-Interim-Interval | 0-1 | 0-1 |
Acct-Link-Count | 0-1 | 0 |
Acct-Session-Time | 1 | 0 |
Acct-Tunnel-Connection | 0-1 | 0 |
Acct-Tunnel-Packets-Lost | 0-1 | 0 |
Authorization-Lifetime | 0-1 | 0 |
Callback-Id | 0-1 | 0 |
Callback-Number | 0-1 | 0 |
Called-Station-Id | 0-1 | 0 |
Calling-Station-Id | 0-1 | 0 |
Class | 0+ | 0+ |
Connection-Info | 0+ | 0 |
Destination-Host | 0-1 | 0 |
Destination-Realm | 1 | 0 |
Event-Timestamp | 0-1 | 0-1 |
Error-Message | 0 | 0-1 |
Error-Reporting-Host | 0 | 0-1 |
Failed-AVP | 0 | 0+ |
---------------------------------------|-----+-----+
+-----------+
| Command |
|-----+-----+
Attribute Name | ACR | ACA |
---------------------------------------|-----+-----+
Accounting-Auth-Method | 0-1 | 0 |
Accounting-Input-Octets | 1 | 0 |
Accounting-Input-Packets | 1 | 0 |
Accounting-Output-Octets | 1 | 0 |
Accounting-Output-Packets | 1 | 0 |
Accounting-Record-Number | 0-1 | 0-1 |
Accounting-Record-Type | 1 | 1 |
Accounting-Realtime-Required | 0-1 | 0-1 |
Accounting-Sub-Session-Id | 0-1 | 0-1 |
Acct-Application-Id | 0-1 | 0-1 |
Acct-Session-Id | 1 | 0-1 |
Acct-Multi-Session-Id | 0-1 | 0-1 |
Acct-Authentic | 1 | 0 |
Acct-Delay-Time | 0-1 | 0 |
Acct-Interim-Interval | 0-1 | 0-1 |
Acct-Link-Count | 0-1 | 0 |
Acct-Session-Time | 1 | 0 |
Acct-Tunnel-Connection | 0-1 | 0 |
Acct-Tunnel-Packets-Lost | 0-1 | 0 |
Authorization-Lifetime | 0-1 | 0 |
Callback-Id | 0-1 | 0 |
Callback-Number | 0-1 | 0 |
Called-Station-Id | 0-1 | 0 |
Calling-Station-Id | 0-1 | 0 |
Class | 0+ | 0+ |
Connection-Info | 0+ | 0 |
Destination-Host | 0-1 | 0 |
Destination-Realm | 1 | 0 |
Event-Timestamp | 0-1 | 0-1 |
Error-Message | 0 | 0-1 |
Error-Reporting-Host | 0 | 0-1 |
Failed-AVP | 0 | 0+ |
---------------------------------------|-----+-----+
+-----------+
| Command |
|-----+-----+
Attribute Name | ACR | ACA |
---------------------------------------|-----+-----+
Framed-AppleTalk-Link | 0-1 | 0 |
Framed-AppleTalk-Network | 0-1 | 0 |
Framed-AppleTalk-Zone | 0-1 | 0 |
Framed-Compression | 0-1 | 0 |
Framed-IP-Address | 0-1 | 0 |
Framed-IP-Netmask | 0-1 | 0 |
Framed-IPv6-Prefix | 0+ | 0 |
Framed-IPv6-Pool | 0-1 | 0 |
Framed-IPX-Network | 0-1 | 0 |
Framed-MTU | 0-1 | 0 |
Framed-Pool | 0-1 | 0 |
Framed-Protocol | 0-1 | 0 |
Framed-Route | 0-1 | 0 |
Framed-Routing | 0-1 | 0 |
NAS-Filter-Rule | 0+ | 0 |
NAS-Identifier | 0-1 | 0-1 |
NAS-IP-Address | 0-1 | 0-1 |
NAS-IPv6-Address | 0-1 | 0-1 |
NAS-Port | 0-1 | 0-1 |
NAS-Port-Id | 0-1 | 0-1 |
NAS-Port-Type | 0-1 | 0-1 |
Origin-AAA-Protocol | 0-1 | 0-1 |
Origin-Host | 1 | 1 |
Origin-Realm | 1 | 1 |
Origin-State-Id | 0-1 | 0-1 |
Originating-Line-Info | 0-1 | 0 |
Proxy-Info | 0+ | 0+ |
QoS-Filter-Rule | 0+ | 0 |
Route-Record | 0+ | 0+ |
Result-Code | 0 | 1 |
Service-Type | 0-1 | 0-1 |
Session-Id | 1 | 1 |
Termination-Cause | 0-1 | 0-1 |
Tunnel-Assignment-Id | 0-1 | 0 |
Tunnel-Client-Endpoint | 0-1 | 0 |
Tunnel-Medium-Type | 0-1 | 0 |
Tunnel-Private-Group-Id | 0-1 | 0 |
Tunnel-Server-Endpoint | 0-1 | 0 |
Tunnel-Type | 0-1 | 0 |
User-Name | 0-1 | 0-1 |
Vendor-Specific-Application-Id | 0-1 | 0-1 |
---------------------------------------|-----+-----+
+-----------+
| Command |
|-----+-----+
Attribute Name | ACR | ACA |
---------------------------------------|-----+-----+
Framed-AppleTalk-Link | 0-1 | 0 |
Framed-AppleTalk-Network | 0-1 | 0 |
Framed-AppleTalk-Zone | 0-1 | 0 |
Framed-Compression | 0-1 | 0 |
Framed-IP-Address | 0-1 | 0 |
Framed-IP-Netmask | 0-1 | 0 |
Framed-IPv6-Prefix | 0+ | 0 |
Framed-IPv6-Pool | 0-1 | 0 |
Framed-IPX-Network | 0-1 | 0 |
Framed-MTU | 0-1 | 0 |
Framed-Pool | 0-1 | 0 |
Framed-Protocol | 0-1 | 0 |
Framed-Route | 0-1 | 0 |
Framed-Routing | 0-1 | 0 |
NAS-Filter-Rule | 0+ | 0 |
NAS-Identifier | 0-1 | 0-1 |
NAS-IP-Address | 0-1 | 0-1 |
NAS-IPv6-Address | 0-1 | 0-1 |
NAS-Port | 0-1 | 0-1 |
NAS-Port-Id | 0-1 | 0-1 |
NAS-Port-Type | 0-1 | 0-1 |
Origin-AAA-Protocol | 0-1 | 0-1 |
Origin-Host | 1 | 1 |
Origin-Realm | 1 | 1 |
Origin-State-Id | 0-1 | 0-1 |
Originating-Line-Info | 0-1 | 0 |
Proxy-Info | 0+ | 0+ |
QoS-Filter-Rule | 0+ | 0 |
Route-Record | 0+ | 0+ |
Result-Code | 0 | 1 |
Service-Type | 0-1 | 0-1 |
Session-Id | 1 | 1 |
Termination-Cause | 0-1 | 0-1 |
Tunnel-Assignment-Id | 0-1 | 0 |
Tunnel-Client-Endpoint | 0-1 | 0 |
Tunnel-Medium-Type | 0-1 | 0 |
Tunnel-Private-Group-Id | 0-1 | 0 |
Tunnel-Server-Endpoint | 0-1 | 0 |
Tunnel-Type | 0-1 | 0 |
User-Name | 0-1 | 0-1 |
Vendor-Specific-Application-Id | 0-1 | 0-1 |
---------------------------------------|-----+-----+
The table in this section is used when the Service-Type specifies Non-Framed Access.
当服务类型指定非框架访问时，将使用本节中的表。
+-----------+
| Command |
|-----+-----+
Attribute Name | ACR | ACA |
---------------------------------------|-----+-----+
Accounting-Auth-Method | 0-1 | 0 |
Accounting-Input-Octets | 1 | 0 |
Accounting-Output-Octets | 1 | 0 |
Accounting-Record-Type | 1 | 1 |
Accounting-Record-Number | 0-1 | 0-1 |
Accounting-Realtime-Required | 0-1 | 0-1 |
Accounting-Sub-Session-Id | 0-1 | 0-1 |
Acct-Application-Id | 0-1 | 0-1 |
Acct-Session-Id | 1 | 0-1 |
Acct-Multi-Session-Id | 0-1 | 0-1 |
Acct-Authentic | 1 | 0 |
Acct-Delay-Time | 0-1 | 0 |
Acct-Interim-Interval | 0-1 | 0-1 |
Acct-Link-Count | 0-1 | 0 |
Acct-Session-Time | 1 | 0 |
Authorization-Lifetime | 0-1 | 0 |
Callback-Id | 0-1 | 0 |
Callback-Number | 0-1 | 0 |
Called-Station-Id | 0-1 | 0 |
Calling-Station-Id | 0-1 | 0 |
Class | 0+ | 0+ |
Connection-Info | 0+ | 0 |
Destination-Host | 0-1 | 0 |
Destination-Realm | 1 | 0 |
Event-Timestamp | 0-1 | 0-1 |
Error-Message | 0 | 0-1 |
Error-Reporting-Host | 0 | 0-1 |
Failed-AVP | 0 | 0+ |
Login-IP-Host | 0+ | 0 |
Login-IPv6-Host | 0+ | 0 |
Login-LAT-Service | 0-1 | 0 |
Login-LAT-Node | 0-1 | 0 |
Login-LAT-Group | 0-1 | 0 |
Login-LAT-Port | 0-1 | 0 |
Login-Service | 0-1 | 0 |
Login-TCP-Port | 0-1 | 0 |
---------------------------------------|-----+-----+
+-----------+
| Command |
|-----+-----+
Attribute Name | ACR | ACA |
---------------------------------------|-----+-----+
Accounting-Auth-Method | 0-1 | 0 |
Accounting-Input-Octets | 1 | 0 |
Accounting-Output-Octets | 1 | 0 |
Accounting-Record-Type | 1 | 1 |
Accounting-Record-Number | 0-1 | 0-1 |
Accounting-Realtime-Required | 0-1 | 0-1 |
Accounting-Sub-Session-Id | 0-1 | 0-1 |
Acct-Application-Id | 0-1 | 0-1 |
Acct-Session-Id | 1 | 0-1 |
Acct-Multi-Session-Id | 0-1 | 0-1 |
Acct-Authentic | 1 | 0 |
Acct-Delay-Time | 0-1 | 0 |
Acct-Interim-Interval | 0-1 | 0-1 |
Acct-Link-Count | 0-1 | 0 |
Acct-Session-Time | 1 | 0 |
Authorization-Lifetime | 0-1 | 0 |
Callback-Id | 0-1 | 0 |
Callback-Number | 0-1 | 0 |
Called-Station-Id | 0-1 | 0 |
Calling-Station-Id | 0-1 | 0 |
Class | 0+ | 0+ |
Connection-Info | 0+ | 0 |
Destination-Host | 0-1 | 0 |
Destination-Realm | 1 | 0 |
Event-Timestamp | 0-1 | 0-1 |
Error-Message | 0 | 0-1 |
Error-Reporting-Host | 0 | 0-1 |
Failed-AVP | 0 | 0+ |
Login-IP-Host | 0+ | 0 |
Login-IPv6-Host | 0+ | 0 |
Login-LAT-Service | 0-1 | 0 |
Login-LAT-Node | 0-1 | 0 |
Login-LAT-Group | 0-1 | 0 |
Login-LAT-Port | 0-1 | 0 |
Login-Service | 0-1 | 0 |
Login-TCP-Port | 0-1 | 0 |
---------------------------------------|-----+-----+
+-----------+
| Command |
|-----+-----+
Attribute Name | ACR | ACA |
---------------------------------------|-----+-----+
NAS-Identifier | 0-1 | 0-1 |
NAS-IP-Address | 0-1 | 0-1 |
NAS-IPv6-Address | 0-1 | 0-1 |
NAS-Port | 0-1 | 0-1 |
NAS-Port-Id | 0-1 | 0-1 |
NAS-Port-Type | 0-1 | 0-1 |
Origin-AAA-Protocol | 0-1 | 0-1 |
Origin-Host | 1 | 1 |
Origin-Realm | 1 | 1 |
Origin-State-Id | 0-1 | 0-1 |
Originating-Line-Info | 0-1 | 0 |
Proxy-Info | 0+ | 0+ |
QoS-Filter-Rule | 0+ | 0 |
Route-Record | 0+ | 0+ |
Result-Code | 0 | 1 |
Session-Id | 1 | 1 |
Service-Type | 0-1 | 0-1 |
Termination-Cause | 0-1 | 0-1 |
User-Name | 0-1 | 0-1 |
Vendor-Specific-Application-Id | 0-1 | 0-1 |
---------------------------------------|-----+-----+
+-----------+
| Command |
|-----+-----+
Attribute Name | ACR | ACA |
---------------------------------------|-----+-----+
NAS-Identifier | 0-1 | 0-1 |
NAS-IP-Address | 0-1 | 0-1 |
NAS-IPv6-Address | 0-1 | 0-1 |
NAS-Port | 0-1 | 0-1 |
NAS-Port-Id | 0-1 | 0-1 |
NAS-Port-Type | 0-1 | 0-1 |
Origin-AAA-Protocol | 0-1 | 0-1 |
Origin-Host | 1 | 1 |
Origin-Realm | 1 | 1 |
Origin-State-Id | 0-1 | 0-1 |
Originating-Line-Info | 0-1 | 0 |
Proxy-Info | 0+ | 0+ |
QoS-Filter-Rule | 0+ | 0 |
Route-Record | 0+ | 0+ |
Result-Code | 0 | 1 |
Session-Id | 1 | 1 |
Service-Type | 0-1 | 0-1 |
Termination-Cause | 0-1 | 0-1 |
User-Name | 0-1 | 0-1 |
Vendor-Specific-Application-Id | 0-1 | 0-1 |
---------------------------------------|-----+-----+
This section provides guidance to the Internet Assigned Numbers Authority (IANA) regarding registration of values related to the Diameter protocol, in accordance with BCP 26 [IANAConsid].
本节根据BCP 26[IANANCOSID]，为互联网分配号码管理局（IANA）提供有关Diameter协议相关值注册的指南。
This document defines values in the namespaces that have been created and defined in the Diameter Base [BASE]. The IANA Considerations section of that document details the assignment criteria. Values assigned in this document, or by future IANA action, must be coordinated within this shared namespace.
本文档定义了在Diameter Base[Base]中创建和定义的名称空间中的值。该文件的IANA注意事项部分详细说明了分配标准。本文档中分配的值或未来IANA操作分配的值必须在此共享命名空间中进行协调。
This specification assigns the value 265 from the Command Code namespace defined in [BASE]. See sections 3.1 and 3.2 for the assignment of the namespace in this specification.
本规范从[BASE]中定义的命令代码命名空间中指定值265。有关本规范中名称空间的分配，请参见第3.1节和第3.2节。
This specification assigns the values 363 - 366 and 400 - 408 from the AVP Code namespace defined in [BASE]. See sections 4 and 5 for the assignment of the namespace in this specification. Note that the values 363 - 366 are jointly, but consistently, assigned in [DiamMIP]. This document also creates one new namespace to be managed by IANA, as described in section 11.5.
本规范从[BASE]中定义的AVP代码命名空间中分配值363-366和400-408。有关本规范中名称空间的分配，请参见第4节和第5节。注意，值363-366在[DiamMIP]中共同但一致地分配。本文档还创建了一个由IANA管理的新名称空间，如第11.5节所述。
This specification also specifies the use of AVPs in the 0 - 255 range, which are defined in [RADIUSTypes]. These values are assigned by the policy in RFC 2865 section 6 [RADIUS] and are amended by RFC 3575 [RADIUSIANA].
本规范还规定了0-255范围内AVP的使用，这些范围在[RADIUSTypes]中定义。这些值由RFC 2865第6节[RADIUS]中的政策分配，并由RFC 3575[RADIUSIANA]修订。
This specification uses the value one (1) in the Application Identifier namespace as assigned in [BASE]. See section 1.2 above for more information.
本规范使用[BASE]中分配的应用程序标识符命名空间中的值1。更多信息见上文第1.2节。
As defined in section 5.5, the CHAP-Algorithm AVP (AVP Code 403) uses the values of the "PPP AUTHENTICATION ALGORITHMS" namespace defined in [PPPCHAP].
如第5.5节所定义，CHAP算法AVP（AVP代码403）使用[PPPCHAP]中定义的“PPP认证算法”命名空间的值。
As defined in section 8.6, the Accounting-Auth-Method AVP (AVP Code 406) defines the values 1 - 5. All remaining values are available for assignment via IETF Consensus [IANA].
如第8.6节所述，会计认证方法AVP（AVP代码406）定义了值1-5。所有剩余值可通过IETF共识[IANA]分配。
As defined in section 9.3.6, the Origin-AAA-Protocol AVP (AVP Code 408) defines the value 1. All remaining values are available for assignment with a "Specification Required" policy [IANAConsid].
如第9.3.6节所定义，源AAA协议AVP（AVP代码408）定义值1。所有剩余值都可通过“所需规范”策略[IANACSID]进行分配。
This document describes the extension of Diameter for the NAS application. The security considerations of the Diameter protocol itself have been discussed in [BASE]. Use of this application of Diameter MUST take into consideration the security issues and requirements of the Base protocol.
本文档介绍NAS应用程序的直径扩展。Diameter协议本身的安全考虑已在[BASE]中讨论。使用Diameter应用程序必须考虑基本协议的安全问题和要求。
This document does not contain a security protocol but does discuss how PPP authentication protocols can be carried within the Diameter protocol. The PPP authentication protocols described are PAP and CHAP.
本文档不包含安全协议，但讨论了如何在Diameter协议中承载PPP身份验证协议。描述的PPP认证协议是PAP和CHAP。
The use of PAP SHOULD be discouraged, as it exposes users' passwords to possibly non-trusted entities. However, PAP is also frequently used for use with One-Time Passwords, which do not expose a security risk.
不鼓励使用PAP，因为它会将用户密码暴露给可能不受信任的实体。然而，PAP也经常用于一次性密码，不会暴露安全风险。
This document also describes how CHAP can be carried within the Diameter protocol, which is required for RADIUS backward compatibility. The CHAP protocol, as used in a RADIUS environment, facilitates authentication replay attacks.
This document also describes how CHAP can be carried within the Diameter protocol, which is required for RADIUS backward compatibility. The CHAP protocol, as used in a RADIUS environment, facilitates authentication replay attacks.translate error, please retry
The use of the EAP authentication protocols described in [DiamEAP] can offer better security, given a method suitable for the circumstances.
[DiamEAP]中所述的EAP认证协议的使用可以提供更好的安全性，只要方法适合这种情况。
[BASE] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. Arkko, "Diameter Base Protocol", RFC 3588, September 2003.
[基础]Calhoun，P.，Loughney，J.，Guttman，E.，Zorn，G.，和J.Arkko，“直径基础协议”，RFC 3588，2003年9月。
[DiamTrans] Aboba, B. and J. Wood, "Authentication, Authorization and Accounting (AAA) Transport Profile", RFC 3539, June 2003.
[DiamTrans]Aboba，B.和J.Wood，“认证、授权和会计（AAA）运输概况”，RFC 3539，2003年6月。
[RADIUS] Rigney, C., Willens, S., Rubens, A., and W. Simpson, "Remote Authentication Dial In User Service (RADIUS)", RFC 2865, June 2000.
[RADIUS]Rigney，C.，Willens，S.，Rubens，A.，和W.Simpson，“远程认证拨入用户服务（RADIUS）”，RFC 28652000年6月。
[RADIUSTypes] IANA, "RADIUS Types", URL:
<http://www.iana.org/assignments/radius-types>
[RADIUSTypes] IANA, "RADIUS Types", URL:
<http://www.iana.org/assignments/radius-types>
[RADIUSIPv6] Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6", RFC 3162, August 2001.
[RADIUSIPv6]Aboba，B.，Zorn，G.和D.Mitton，“RADIUS和IPv6”，RFC 3162，2001年8月。
[IPv6Addr] Nerenberg, L., "IMAP4 Binary Content Extension", RFC 3516, April 2003.
[IPv6Addr]Nerenberg，L.，“IMAP4二进制内容扩展”，RFC3516，2003年4月。
[PPPCHAP] Simpson, W., "PPP Challenge Handshake Authentication Protocol (CHAP)", RFC 1994, August 1996.
[PPPCHAP]辛普森，W.，“PPP挑战握手认证协议（CHAP）”，RFC 1994，1996年8月。
[IANAConsid] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
[IANANCOSID]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 2434，1998年10月。
[IANA] IANA Assigned Numbers Database, URL:
<http://www.iana.org/numbers.html>
[IANA] IANA Assigned Numbers Database, URL:
<http://www.iana.org/numbers.html>
[Keywords] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[关键词]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[ANITypes] NANPA Number Resource Info, ANI Assignments, URL:
<http://www.nanpa.com/number_resource_info/
ani_ii_assignments.html>
[ANITypes] NANPA Number Resource Info, ANI Assignments, URL:
<http://www.nanpa.com/number_resource_info/
ani_ii_assignments.html>
[RADIUSAcct] Rigney, C., "RADIUS Accounting", RFC 2866, June 2000.
[RADIUSAcct] Rigney, C., "RADIUS Accounting", RFC 2866, June 2000.translate error, please retry
[RADIUSExt] Rigney, C., Willats, W., and P. Calhoun, "RADIUS Extensions", RFC 2869, June 2000.
[RADIUSExt]Rigney，C.，Willats，W.，和P.Calhoun，“半径延伸”，RFC 2869，2000年6月。
[RADTunnels] Zorn, G., Leifer, D., Rubens, A., Shriver, J., Holdrege, M., and I. Goyret, "RADIUS Attributes for Tunnel Protocol Support", RFC 2868, June 2000.
[RADTunnels]Zorn，G.，Leifer，D.，Rubens，A.，Shriver，J.，Holdrege，M.，和I.Goyret，“隧道协议支持的半径属性”，RFC 28682000年6月。
[RADTunlAcct] Zorn, G., Aboba, B., and D. Mitton, "RADIUS Accounting Modifications for Tunnel Protocol Support", RFC 2867, June 2000.
[Radtunlact]Zorn，G.，Aboba，B.，和D.Mitton，“隧道协议支持的半径计算修改”，RFC 28672000年6月。
[RADDynAuth] Chiba, M., Dommety, G., Eklund, M., Mitton, D., and B. Aboba, "Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS)", RFC 3576, July 2003.
[RADDynAuth]Chiba，M.，Dommety，G.，Eklund，M.，Mitton，D.，和B.Aboba，“远程认证拨号用户服务（RADIUS）的动态授权扩展”，RFC 35762003年7月。
[RADIUSIANA] Aboba, B., "IANA Considerations for RADIUS (Remote Authentication Dial In User Service)", RFC 3575, July 2003.
[RADIUSIANA]Aboba，B.，“RADIUS（远程认证拨入用户服务）的IANA注意事项”，RFC 35752003年7月。
[NASModel] Mitton, D. and M. Beadles, "Network Access Server Requirements Next Generation (NASREQNG) NAS Model", RFC 2881, July 2000.
[NASModel]Mitton，D.和M.Beadles，“网络访问服务器需求下一代（NASREQNG）NAS模型”，RFC 28812000年7月。
[NASCriteria] Beadles, M. and D. Mitton, "Criteria for Evaluating Network Access Server Protocols", RFC 3169, September 2001.
[NASCriteria]Beadles，M.和D.Mitton，“评估网络访问服务器协议的标准”，RFC 3169，2001年9月。
[AAACriteria] Aboba, B., Calhoun, P., Glass, S., Hiller, T., McCann, P., Shiino, H., Zorn, G., Dommety, G., Perkins, C., Patil, B., Mitton, D., Manning, S., Beadles, M., Walsh, P., Chen, X., Sivalingham, S., Hameed, A., Munson, M., Jacobs, S., Lim, B., Hirschman, B., Hsu, R., Xu, Y., Campbell, E., Baba, S., and E. Jaques, "Criteria for Evaluating AAA Protocols for Network Access", RFC 2989, November 2000.
[AAACriteria] Aboba, B., Calhoun, P., Glass, S., Hiller, T., McCann, P., Shiino, H., Zorn, G., Dommety, G., Perkins, C., Patil, B., Mitton, D., Manning, S., Beadles, M., Walsh, P., Chen, X., Sivalingham, S., Hameed, A., Munson, M., Jacobs, S., Lim, B., Hirschman, B., Hsu, R., Xu, Y., Campbell, E., Baba, S., and E. Jaques, "Criteria for Evaluating AAA Protocols for Network Access", RFC 2989, November 2000.translate error, please retry
[DiamEAP] Eronen, P., "Diameter EAP Application", Work in Progress, May 2004.
[DiamEAP]Eronen，P.，“Diameter EAP应用”，正在进行的工作，2004年5月。
[DiamCMS] Calhoun, P., Bulley, W., and S. Farrell, "Diameter CMS Security Application", Work in Progress, March 2002.
[DiamCMS]Calhoun，P.，Bulley，W.，和S.Farrell，“Diameter CMS安全应用”，正在进行的工作，2002年3月。
[DiamMIP] Calhoun, P., Johansson, T., Perkins, C., Hiller, T., and P. McCann "Diameter Mobile IPv4 Application", RFC 4004, August 2005.
[DiamMIP]Calhoun，P.，Johansson，T.，Perkins，C.，Hiller，T.，和P.McCann“Diameter移动IPv4应用”，RFC 40042005年8月。
[VSA] Mitton, D., "Diameter/RADIUS Vendor Specific AVP Translation", Work in Progress, April 2005.
[VSA]Mitton，D.，“直径/半径供应商特定AVP翻译”，正在进行的工作，2005年4月。
[RAD802.1X] Congdon, P., Aboba, B., Smith, A., Zorn, G., and J. Roese, "IEEE 802.1X Remote Authentication Dial In User Service (RADIUS) Usage Guidelines", RFC 3580, September 2003.
[RAD802.1X]Congdon，P.，Aboba，B.，Smith，A.，Zorn，G.，和J.Roese，“IEEE 802.1X远程认证拨入用户服务（RADIUS）使用指南”，RFC 35802003年9月。
[CDMA2000] 3GPP2 "P.S0001-B", Wireless IP Network Standard,
October 2002.
http://www.3gpp2.com/Public_html/specs/P.S0001-
B_v1.0.pdf
[CDMA2000] 3GPP2 "P.S0001-B", Wireless IP Network Standard,
October 2002.
http://www.3gpp2.com/Public_html/specs/P.S0001-
B_v1.0.pdf
[AppleTalk] Sidhu, Gursharan; Andrews, Richard F. & Oppenheimer, Alan B. "Inside AppleTalk", Second Edition, Apple Computer., 1990
[AppleTalk] Sidhu, Gursharan; Andrews, Richard F. & Oppenheimer, Alan B. "Inside AppleTalk", Second Edition, Apple Computer., 1990translate error, please retry
[ARAP] Apple Remote Access Protocol (ARAP) Version 2.0 External Reference Specification", Apple Computer, September 1994, R0612LL/B
[ARAP]苹果远程访问协议（ARAP）2.0版外部参考规范”，苹果计算机，1994年9月，R0612LL/B
[IPX] Novell, Inc., "NetWare System Technical Interface Overview", June 1989, # 883-000780-001
[IPX]Novell，Inc.，“NetWare系统技术接口概述”，1989年6月，#883-000780-001
[LAT] Local Area Transport (LAT) Specification V5.0, Digital Equipment Corp., AA-NL26A-TE, June 1989
[LAT]局域网传输（LAT）规范V5.0，数字设备公司，AA-NL26A-TE，1989年6月
[DIFFSERV] Nichols, K., Blake, S., Baker, F., and D. Black, "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers", RFC 2474, December 1998.
[DIFFSERV]Nichols，K.，Blake，S.，Baker，F.，和D.Black，“IPv4和IPv6报头中区分服务字段（DS字段）的定义”，RFC 24741998年12月。
[DIFFSERVAF] Heinanen, J., Baker, F., Weiss, W., and J. Wroclawski, "Assured Forwarding PHB Group", RFC 2597, June 1999.
[DIFFSERVAF]Heinanen，J.，Baker，F.，Weiss，W.，和J.Wroclawski，“保证转发PHB集团”，RFC 25971999年6月。
[DIFFSERVEF] Davie, B., Charny, A., Bennet, J.C., Benson, K., Le Boudec, J., Courtney, W., Davari, S., Firoiu, V., and D. Stiliadis, "An Expedited Forwarding PHB (Per-Hop Behavior)", RFC 3246, March 2002.
[DIFFSERVEF]Davie，B.，Charny，A.，Bennet，J.C.，Benson，K.，Le Boudec，J.，Courtney，W.，Davari，S.，Firoiu，V.，和D.Stiliadis，“快速转发PHB（每跳行为）”，RFC 32462002年3月。
[UTF-8] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, November 2003.
[UTF-8]Yergeau，F.，“UTF-8，ISO 10646的转换格式”，STD 63，RFC 3629，2003年11月。
[ISOLatin] ISO 8859. International Standard -- Information
Processing -- 8-bit Single-Byte Coded Graphic
Character Sets -- Part 1: Latin Alphabet No. 1, ISO
8859-1:1987. URL:
<http://www.iso.ch/cate/d16338.html>
[ISOLatin] ISO 8859. International Standard -- Information
Processing -- 8-bit Single-Byte Coded Graphic
Character Sets -- Part 1: Latin Alphabet No. 1, ISO
8859-1:1987. URL:
<http://www.iso.ch/cate/d16338.html>
[PPP] Simpson, W., "The Point-to-Point Protocol (PPP)", STD 51, RFC 1661, July 1994.
[PPP]辛普森，W.“点对点协议（PPP）”，STD 51，RFC 1661994年7月。
[PAP] Lloyd, B. and W. Simpson, "PPP Authentication Protocols", RFC 1334, October 1992.
[PAP]Lloyd，B.和W.Simpson，“PPP认证协议”，RFC 13341992年10月。
[L2TP] Townsley, W., Valencia, A., Rubens, A., Pall, G., Zorn, G., and B. Palter, "Layer Two Tunneling Protocol "L2TP"", RFC 2661, August 1999.
[L2TP]汤斯利，W.，瓦伦西亚，A.，鲁本斯，A.，帕尔，G.，佐恩，G.，和B.帕尔特，“第二层隧道协议”L2TP“，RFC 26611999年8月。
[PPPMP] Sklower, K., Lloyd, B., McGregor, G., Carr, D., and T. Coradetti, "The PPP Multilink Protocol (MP)", RFC 1990, August 1996.
[PPPMP]Sklower，K.，Lloyd，B.，McGregor，G.，Carr，D.，和T.Coradetti，“PPP多链路协议（MP）”，RFC 1990，1996年8月。
[PPTP] Hamzeh, K., Pall, G., Verthein, W., Taarud, J., Little, W., and G. Zorn, "Point-to-Point Tunneling Protocol", RFC 2637, July 1999.
[PPTP]Hamzeh，K.，Pall，G.，Verthein，W.，Taarud，J.，Little，W.，和G.Zorn，“点对点隧道协议”，RFC 2637，1999年7月。
[IEEE 802.11F] IEEE, "Trial-Use Recommended Practice for Multi-Vendor Access Point Interoperability via an Inter-Access Point Protocol Across Distribution Systems Supporting IEEE 802.11 Operation", IEEE 802.11F-2003, June 2003.
[IEEE 802.11F]IEEE，“通过支持IEEE 802.11操作的配电系统间接入点协议实现多供应商接入点互操作性的试用推荐规程”，IEEE 802.11F-2003，2003年6月。
The authors would like to thank Carl Rigney, Allan C. Rubens, William Allen Simpson, and Steve Willens for their work on the original RADIUS [RADIUS], from which many of the concepts in this specification were derived. Thanks, also, to Carl Rigney for [RADIUSAcct] and [RADIUSExt]; Ward Willats for [RADIUSExt]; Glen Zorn, Bernard Aboba, and Dave Mitton for [RADTunlAcct] and [RADIUSIPv6]; and Dory Leifer, John Shriver, Matt Holdrege, and Ignacio Goyret for their work on [RADTunnels]. This document stole text and concepts from both [RADTunnels] and [RADIUSExt]. Thanks go to Carl Williams for providing IPv6-specific text.
作者要感谢Carl Rigney、Allan C.Rubens、William Allen Simpson和Steve Willens在原始半径[RADIUS]方面的工作，本规范中的许多概念都是从原始半径[RADIUS]衍生而来的。还感谢卡尔·里格尼的[Radiusact]和[RadiusText]；[RADIUSExt]的Ward Willats；格伦·佐恩（Glen Zorn）、伯纳德·阿博巴（Bernard Aboba）和戴夫·米顿（Dave Mitton）担任[Radtunlact]和[RADIUSIPv6]；多莉·莱弗、约翰·施莱弗、马特·霍德雷格和伊格纳西奥·戈雷特，感谢他们在[放射性隧道]方面的工作。此文档从[RADTunnels]和[RadiusText]中窃取了文本和概念。感谢Carl Williams提供IPv6特定文本。
The authors would also like to acknowledge the following people for their contributions in the development of the Diameter protocol: Bernard Aboba, Jari Arkko, William Bulley, Kuntal Chowdhury, Daniel C. Fox, Lol Grant, Nancy Greene, Jeff Hagg, Peter Heitman, Paul Krumviede, Fergal Ladley, Ryan Moats, Victor Muslin, Kenneth Peirce, Sumit Vakil, John R. Vollbrecht, and Jeff Weisberg.
作者还想感谢以下人士在DIAMER协议制定过程中所做的贡献：伯纳德·阿博巴、贾里·阿尔科、威廉·布里、昆塔·乔杜里、丹尼尔·C·福克斯、洛尔·格兰特、南希·格林、杰夫·哈格、彼得·海特曼、保罗·克鲁姆维德、费尔格尔·拉德利、瑞安·莫茨、维克托·穆斯林、肯尼斯·皮尔斯、苏米特·瓦基尔、，约翰·R·沃尔布雷希特和杰夫·韦斯伯格。
Finally, Pat Calhoun would like to thank Sun Microsystems, as most of the effort put into this document was done while he was in their employ.
最后，Pat Calhoun要感谢Sun Microsystems，因为在本文档中投入的大部分精力都是在他任职期间完成的。
Authors' Addresses
作者地址
Pat Calhoun Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134 USA
Pat Calhoun Cisco Systems，Inc.美国加利福尼亚州圣何塞市西塔斯曼大道170号，邮编95134
Phone: +1 408-853-5269
EMail: pcalhoun@cisco.com
Phone: +1 408-853-5269
EMail: pcalhoun@cisco.com
Glen Zorn Cisco Systems, Inc. 500 108th Avenue N.E., Suite 500 Bellevue, WA 98004 USA
格伦佐恩思科系统有限公司，地址：美国华盛顿州贝尔维尤第108大道500号，邮编：98004
Phone: 1 425-471-4861 EMail: gwz@cisco.com
电话：1425-471-4861电子邮件：gwz@cisco.com
David Spence 3259 Bluett Rd. Ann Arbor, MI 48105 USA
David Spence 3259 Bluett Rd. Ann Arbor, MI 48105 USAtranslate error, please retry
Phone: +1 734 834 6481
EMail: dspence@computer.org
Phone: +1 734 834 6481
EMail: dspence@computer.org
David Mitton Circular Networks 733 Turnpike St #154 North Andover, MA 01845
David Mitton环形网络马萨诸塞州北安多佛市收费公路街733号，154号，邮编01845
EMail: dmitton@circularnetworks.com
EMail: dmitton@circularnetworks.com
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。