Internet Engineering Task Force (IETF) G. Zorn, Ed.
Request for Comments: 7155 Network Zen
Obsoletes: 4005 April 2014
Category: Standards Track
ISSN: 2070-1721
Internet Engineering Task Force (IETF) G. Zorn, Ed.
Request for Comments: 7155 Network Zen
Obsoletes: 4005 April 2014
Category: Standards Track
ISSN: 2070-1721
Diameter Network Access Server Application
Diameter网络访问服务器应用程序
Abstract
摘要
This document describes the Diameter protocol application used for Authentication, Authorization, and Accounting services in the Network Access Server (NAS) environment; it obsoletes RFC 4005. When combined with the Diameter Base protocol, Transport Profile, and Extensible Authentication Protocol specifications, this application specification satisfies typical network access services requirements.
本文档描述了网络访问服务器（NAS）环境中用于身份验证、授权和记帐服务的Diameter协议应用程序；它淘汰了RFC 4005。当与Diameter基本协议、传输配置文件和可扩展身份验证协议规范结合使用时，此应用程序规范满足典型的网络访问服务需求。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7155.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7155.
Copyright Notice
版权公告
Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2014 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction ....................................................4
1.1. Changes from RFC 4005 ......................................5
1.2. Terminology ................................................6
1.3. Requirements Language ......................................7
1.4. Advertising Application Support ............................8
1.5. Application Identification .................................8
1.6. Accounting Model ...........................................8
2. NAS Calls, Ports, and Sessions ..................................8
2.1. Diameter Session Establishment .............................9
2.2. Diameter Session Reauthentication or Reauthorization .......9
2.3. Diameter Session Termination ..............................10
3. Diameter NAS Application Messages ..............................11
3.1. AA-Request (AAR) Command ..................................11
3.2. AA-Answer (AAA) Command ...................................13
3.3. Re-Auth-Request (RAR) Command .............................15
3.4. Re-Auth-Answer (RAA) Command ..............................16
3.5. Session-Termination-Request (STR) Command .................17
3.6. Session-Termination-Answer (STA) Command ..................17
3.7. Abort-Session-Request (ASR) Command .......................18
3.8. Abort-Session-Answer (ASA) Command ........................19
3.9. Accounting-Request (ACR) Command ..........................20
3.10. Accounting-Answer (ACA) Command ..........................22
4. Diameter NAS Application AVPs ..................................23
4.1. Derived AVP Data Formats ..................................23
4.1.1. QoSFilterRule ......................................23
4.2. NAS Session AVPs ..........................................24
4.2.1. Call and Session Information .......................24
4.2.2. NAS-Port AVP .......................................25
4.2.3. NAS-Port-Id AVP ....................................25
4.2.4. NAS-Port-Type AVP ..................................26
4.2.5. Called-Station-Id AVP ..............................26
4.2.6. Calling-Station-Id AVP .............................26
4.2.7. Connect-Info AVP ...................................27
4.2.8. Originating-Line-Info AVP ..........................27
4.2.9. Reply-Message AVP ..................................28
4.3. NAS Authentication AVPs ...................................28
4.3.1. User-Password AVP ..................................29
4.3.2. Password-Retry AVP .................................29
4.3.3. Prompt AVP .........................................29
4.3.4. CHAP-Auth AVP ......................................29
4.3.5. CHAP-Algorithm AVP .................................30
4.3.6. CHAP-Ident AVP .....................................30
4.3.7. CHAP-Response AVP ..................................30
4.3.8. CHAP-Challenge AVP .................................30
4.3.9. ARAP-Password AVP ..................................30
4.3.10. ARAP-Challenge-Response AVP .......................31
1. Introduction ....................................................4
1.1. Changes from RFC 4005 ......................................5
1.2. Terminology ................................................6
1.3. Requirements Language ......................................7
1.4. Advertising Application Support ............................8
1.5. Application Identification .................................8
1.6. Accounting Model ...........................................8
2. NAS Calls, Ports, and Sessions ..................................8
2.1. Diameter Session Establishment .............................9
2.2. Diameter Session Reauthentication or Reauthorization .......9
2.3. Diameter Session Termination ..............................10
3. Diameter NAS Application Messages ..............................11
3.1. AA-Request (AAR) Command ..................................11
3.2. AA-Answer (AAA) Command ...................................13
3.3. Re-Auth-Request (RAR) Command .............................15
3.4. Re-Auth-Answer (RAA) Command ..............................16
3.5. Session-Termination-Request (STR) Command .................17
3.6. Session-Termination-Answer (STA) Command ..................17
3.7. Abort-Session-Request (ASR) Command .......................18
3.8. Abort-Session-Answer (ASA) Command ........................19
3.9. Accounting-Request (ACR) Command ..........................20
3.10. Accounting-Answer (ACA) Command ..........................22
4. Diameter NAS Application AVPs ..................................23
4.1. Derived AVP Data Formats ..................................23
4.1.1. QoSFilterRule ......................................23
4.2. NAS Session AVPs ..........................................24
4.2.1. Call and Session Information .......................24
4.2.2. NAS-Port AVP .......................................25
4.2.3. NAS-Port-Id AVP ....................................25
4.2.4. NAS-Port-Type AVP ..................................26
4.2.5. Called-Station-Id AVP ..............................26
4.2.6. Calling-Station-Id AVP .............................26
4.2.7. Connect-Info AVP ...................................27
4.2.8. Originating-Line-Info AVP ..........................27
4.2.9. Reply-Message AVP ..................................28
4.3. NAS Authentication AVPs ...................................28
4.3.1. User-Password AVP ..................................29
4.3.2. Password-Retry AVP .................................29
4.3.3. Prompt AVP .........................................29
4.3.4. CHAP-Auth AVP ......................................29
4.3.5. CHAP-Algorithm AVP .................................30
4.3.6. CHAP-Ident AVP .....................................30
4.3.7. CHAP-Response AVP ..................................30
4.3.8. CHAP-Challenge AVP .................................30
4.3.9. ARAP-Password AVP ..................................30
4.3.10. ARAP-Challenge-Response AVP .......................31
4.3.11. ARAP-Security AVP .................................31
4.3.12. ARAP-Security-Data AVP ............................31
4.4. NAS Authorization AVPs ....................................31
4.4.1. Service-Type AVP ...................................33
4.4.2. Callback-Number AVP ................................34
4.4.3. Callback-Id AVP ....................................34
4.4.4. Idle-Timeout AVP ...................................34
4.4.5. Port-Limit AVP .....................................34
4.4.6. NAS-Filter-Rule AVP ................................35
4.4.7. Filter-Id AVP ......................................35
4.4.8. Configuration-Token AVP ............................35
4.4.9. QoS-Filter-Rule AVP ................................35
4.4.10. Framed Access Authorization AVPs ..................36
4.4.10.1. Framed-Protocol AVP ......................36
4.4.10.2. Framed-Routing AVP .......................36
4.4.10.3. Framed-MTU AVP ...........................37
4.4.10.4. Framed-Compression AVP ...................37
4.4.10.5. IP Access Authorization AVPs .............37
4.4.10.5.1. Framed-IP-Address AVP .........37
4.4.10.5.2. Framed-IP-Netmask AVP .........37
4.4.10.5.3. Framed-Route AVP ..............38
4.4.10.5.4. Framed-Pool AVP ...............38
4.4.10.5.5. Framed-Interface-Id AVP .......38
4.4.10.5.6. Framed-IPv6-Prefix AVP ........39
4.4.10.5.7. Framed-IPv6-Route AVP .........39
4.4.10.5.8. Framed-IPv6-Pool AVP ..........39
4.4.10.6. IPX Access AVPs ..........................39
4.4.10.6.1. Framed-IPX-Network AVP ........40
4.4.10.7. AppleTalk Network Access AVPs ............40
4.4.10.7.1. Framed-Appletalk-Link AVP .....40
4.4.10.7.2. Framed-Appletalk-Network AVP ..40
4.4.10.7.3. Framed-Appletalk-Zone AVP .....41
4.4.10.8. AppleTalk Remote Access AVPs .............41
4.4.10.8.1. ARAP-Features AVP .............41
4.4.10.8.2. ARAP-Zone-Access AVP ..........41
4.4.11. Non-Framed Access Authorization AVPs ..............41
4.4.11.1. Login-IP-Host AVP ........................41
4.4.11.2. Login-IPv6-Host AVP ......................42
4.4.11.3. Login-Service AVP ........................42
4.4.11.4. TCP Services .............................42
4.4.11.4.1. Login-TCP-Port AVP ............42
4.4.11.5. LAT Services .............................43
4.4.11.5.1. Login-LAT-Service AVP .........43
4.4.11.5.2. Login-LAT-Node AVP ............43
4.4.11.5.3. Login-LAT-Group AVP ...........44
4.4.11.5.4. Login-LAT-Port AVP ............44
4.5. NAS Tunneling AVPs ........................................45
4.5.1. Tunneling AVP ......................................45
4.3.11. ARAP-Security AVP .................................31
4.3.12. ARAP-Security-Data AVP ............................31
4.4. NAS Authorization AVPs ....................................31
4.4.1. Service-Type AVP ...................................33
4.4.2. Callback-Number AVP ................................34
4.4.3. Callback-Id AVP ....................................34
4.4.4. Idle-Timeout AVP ...................................34
4.4.5. Port-Limit AVP .....................................34
4.4.6. NAS-Filter-Rule AVP ................................35
4.4.7. Filter-Id AVP ......................................35
4.4.8. Configuration-Token AVP ............................35
4.4.9. QoS-Filter-Rule AVP ................................35
4.4.10. Framed Access Authorization AVPs ..................36
4.4.10.1. Framed-Protocol AVP ......................36
4.4.10.2. Framed-Routing AVP .......................36
4.4.10.3. Framed-MTU AVP ...........................37
4.4.10.4. Framed-Compression AVP ...................37
4.4.10.5. IP Access Authorization AVPs .............37
4.4.10.5.1. Framed-IP-Address AVP .........37
4.4.10.5.2. Framed-IP-Netmask AVP .........37
4.4.10.5.3. Framed-Route AVP ..............38
4.4.10.5.4. Framed-Pool AVP ...............38
4.4.10.5.5. Framed-Interface-Id AVP .......38
4.4.10.5.6. Framed-IPv6-Prefix AVP ........39
4.4.10.5.7. Framed-IPv6-Route AVP .........39
4.4.10.5.8. Framed-IPv6-Pool AVP ..........39
4.4.10.6. IPX Access AVPs ..........................39
4.4.10.6.1. Framed-IPX-Network AVP ........40
4.4.10.7. AppleTalk Network Access AVPs ............40
4.4.10.7.1. Framed-Appletalk-Link AVP .....40
4.4.10.7.2. Framed-Appletalk-Network AVP ..40
4.4.10.7.3. Framed-Appletalk-Zone AVP .....41
4.4.10.8. AppleTalk Remote Access AVPs .............41
4.4.10.8.1. ARAP-Features AVP .............41
4.4.10.8.2. ARAP-Zone-Access AVP ..........41
4.4.11. Non-Framed Access Authorization AVPs ..............41
4.4.11.1. Login-IP-Host AVP ........................41
4.4.11.2. Login-IPv6-Host AVP ......................42
4.4.11.3. Login-Service AVP ........................42
4.4.11.4. TCP Services .............................42
4.4.11.4.1. Login-TCP-Port AVP ............42
4.4.11.5. LAT Services .............................43
4.4.11.5.1. Login-LAT-Service AVP .........43
4.4.11.5.2. Login-LAT-Node AVP ............43
4.4.11.5.3. Login-LAT-Group AVP ...........44
4.4.11.5.4. Login-LAT-Port AVP ............44
4.5. NAS Tunneling AVPs ........................................45
4.5.1. Tunneling AVP ......................................45
4.5.2. Tunnel-Type AVP ....................................46
4.5.3. Tunnel-Medium-Type AVP .............................46
4.5.4. Tunnel-Client-Endpoint AVP .........................46
4.5.5. Tunnel-Server-Endpoint AVP .........................47
4.5.6. Tunnel-Password AVP ................................48
4.5.7. Tunnel-Private-Group-Id AVP ........................48
4.5.8. Tunnel-Assignment-Id AVP ...........................48
4.5.9. Tunnel-Preference AVP ..............................50
4.5.10. Tunnel-Client-Auth-Id AVP .........................50
4.5.11. Tunnel-Server-Auth-Id AVP .........................50
4.6. NAS Accounting AVPs .......................................51
4.6.1. Accounting-Input-Octets AVP ........................52
4.6.2. Accounting-Output-Octets AVP .......................52
4.6.3. Accounting-Input-Packets AVP .......................52
4.6.4. Accounting-Output-Packets AVP ......................53
4.6.5. Acct-Session-Time AVP ..............................53
4.6.6. Acct-Authentic AVP .................................53
4.6.7. Accounting-Auth-Method AVP .........................53
4.6.8. Acct-Delay-Time AVP ................................53
4.6.9. Acct-Link-Count AVP ................................54
4.6.10. Acct-Tunnel-Connection AVP ........................55
4.6.11. Acct-Tunnel-Packets-Lost AVP ......................55
5. AVP Occurrence Tables ..........................................55
5.1. AA-Request / AA-Answer AVP Table ..........................56
5.2. Accounting AVP Tables .....................................58
5.2.1. Framed Access Accounting AVP Table .................59
5.2.2. Non-Framed Access Accounting AVP Table .............61
6. Unicode Considerations .........................................62
7. IANA Considerations ............................................63
8. Security Considerations ........................................63
8.1. Authentication Considerations .............................63
8.2. AVP Considerations ........................................64
9. References .....................................................65
9.1. Normative References ......................................65
9.2. Informative References ....................................65
Appendix A. Acknowledgements ......................................69
A.1. This Document ..............................................69
A.2. RFC 4005 ...................................................69
4.5.2. Tunnel-Type AVP ....................................46
4.5.3. Tunnel-Medium-Type AVP .............................46
4.5.4. Tunnel-Client-Endpoint AVP .........................46
4.5.5. Tunnel-Server-Endpoint AVP .........................47
4.5.6. Tunnel-Password AVP ................................48
4.5.7. Tunnel-Private-Group-Id AVP ........................48
4.5.8. Tunnel-Assignment-Id AVP ...........................48
4.5.9. Tunnel-Preference AVP ..............................50
4.5.10. Tunnel-Client-Auth-Id AVP .........................50
4.5.11. Tunnel-Server-Auth-Id AVP .........................50
4.6. NAS Accounting AVPs .......................................51
4.6.1. Accounting-Input-Octets AVP ........................52
4.6.2. Accounting-Output-Octets AVP .......................52
4.6.3. Accounting-Input-Packets AVP .......................52
4.6.4. Accounting-Output-Packets AVP ......................53
4.6.5. Acct-Session-Time AVP ..............................53
4.6.6. Acct-Authentic AVP .................................53
4.6.7. Accounting-Auth-Method AVP .........................53
4.6.8. Acct-Delay-Time AVP ................................53
4.6.9. Acct-Link-Count AVP ................................54
4.6.10. Acct-Tunnel-Connection AVP ........................55
4.6.11. Acct-Tunnel-Packets-Lost AVP ......................55
5. AVP Occurrence Tables ..........................................55
5.1. AA-Request / AA-Answer AVP Table ..........................56
5.2. Accounting AVP Tables .....................................58
5.2.1. Framed Access Accounting AVP Table .................59
5.2.2. Non-Framed Access Accounting AVP Table .............61
6. Unicode Considerations .........................................62
7. IANA Considerations ............................................63
8. Security Considerations ........................................63
8.1. Authentication Considerations .............................63
8.2. AVP Considerations ........................................64
9. References .....................................................65
9.1. Normative References ......................................65
9.2. Informative References ....................................65
Appendix A. Acknowledgements ......................................69
A.1. This Document ..............................................69
A.2. RFC 4005 ...................................................69
This document describes the Diameter protocol application used for Authentication, Authorization, and Accounting in the Network Access Server (NAS) environment. When combined with the Diameter Base protocol [RFC6733], Transport Profile [RFC3539], and Extensible Authentication Protocol (EAP) [RFC4072] specifications, this specification satisfies the NAS-related requirements defined in [RFC2989] and [RFC3169].
本文档描述了在网络访问服务器（NAS）环境中用于身份验证、授权和记帐的Diameter协议应用程序。当与Diameter基本协议[RFC6733]、传输配置文件[RFC3539]和可扩展身份验证协议（EAP）[RFC4072]规范结合使用时，本规范满足[RFC2989]和[RFC3169]中定义的NAS相关要求。
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.
首先，本文档介绍Diameter NAS应用程序的操作。然后，它定义Diameter消息命令代码。以下各节列出了这些消息中使用的AVP，按常见用法分组。它们是会话标识、身份验证、授权、隧道和记帐。授权AVP按服务类型进一步细分。
This document obsoletes [RFC4005] and is not backward compatible with that document. An overview of some of the major changes is given below.
本文件已过时[RFC4005]，且与该文件不向后兼容。下文概述了一些主要变化。
o All of the material regarding RADIUS/Diameter protocol interactions has been removed; however, where AVPs are derived from RADIUS Attributes, the range and format of those Attribute values have been retained for ease of transition.
o 关于半径/直径协议交互的所有材料均已移除；但是，如果AVP是从RADIUS属性派生的，则保留了这些属性值的范围和格式，以便于转换。
o The Command Code Format (CCF) [RFC6733] for the Accounting-Request and Accounting-Answer messages has been changed to explicitly require the inclusion of the Acct-Application-Id AVP and exclude the Vendor-Specific-Application-Id AVP. Normally, this type of change would require the allocation of a new command code (see Section 1.3.3 of [RFC6733]) and consequently, a new application-id. However, the presence of an instance of the Acct-Application-Id AVP was required in [RFC4005], as well:
o 会计请求和会计应答消息的命令代码格式（CCF）[RFC6733]已更改为明确要求包含会计应用程序Id AVP，并排除特定于供应商的应用程序Id AVP。通常，这种类型的更改需要分配新的命令代码（见[RFC6733]第1.3.3节），因此需要分配新的应用程序id。然而，[RFC4005]中也要求存在Acct应用程序id AVP的实例：
The Accounting-Request (ACR) message [BASE] is sent by the NAS to report its session information to a target server downstream.
NAS发送记帐请求（ACR）消息[BASE]，以向下游目标服务器报告其会话信息。
Either the Acct-Application-Id or the Vendor-Specific-Application-Id AVP 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。
Thus, though the syntax of the commands has changed, the semantics have not (with the caveat that the Acct-Application-Id AVP can no longer be contained in the Vendor-Specific-Application-Id AVP).
因此，尽管命令的语法已经改变，但语义没有改变（需要注意的是，Acct应用程序Id AVP不能再包含在特定于供应商的应用程序Id AVP中）。
o The lists of RADIUS attribute values have been deleted in favor of references to the appropriate IANA registries.
o RADIUS属性值列表已被删除，以便引用适当的IANA注册表。
o The accounting model to be used is now specified (see Section 1.6).
o 现在指定了要使用的会计模型（见第1.6节）。
There are many other miscellaneous fixes that have been introduced in this document that may not be considered significant, but they are useful nonetheless. Examples are fixes to example IP addresses, addition of clarifying references, etc. Errata reports filed against [RFC4005] at the time of writing have been reviewed and incorporated as necessary. A comprehensive list of changes is not shown here for practical reasons.
本文档中引入的许多其他杂项修复可能并不重要，但它们仍然很有用。示例包括对示例IP地址的修复、添加澄清参考等。在撰写本文时针对[RFC4005]提交的勘误表报告已经过审查，并在必要时纳入其中。出于实际原因，此处未显示全面的变更列表。
Section 1.2 of the Diameter Base protocol specification [RFC6733] defines most of the terminology used in this document. Additionally, the following terms and acronyms are used in this application:
Diameter基本协议规范[RFC6733]第1.2节定义了本文件中使用的大部分术语。此外，本应用程序中使用了以下术语和首字母缩略词：
NAS (Network Access Server)
NAS（网络访问服务器）
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 [RFC2881].
为用户提供网络访问服务的设备。该服务可以是网络连接或增值服务，例如终端仿真[RFC2881]。
PPP (Point-to-Point Protocol)
PPP（点对点协议）
A multiprotocol serial datalink. PPP is the primary IP datalink used for dial-in NAS connection service [RFC1661].
多协议串行数据链路。PPP是用于拨入NAS连接服务[RFC1661]的主要IP数据链路。
CHAP (Challenge Handshake Authentication Protocol)
CHAP（质询握手认证协议）
An authentication process used in PPP [RFC1994].
PPP[RFC1994]中使用的身份验证过程。
PAP (Password Authentication Protocol)
PAP（密码认证协议）
A deprecated PPP authentication process, but often used for backward compatibility [RFC1334].
不推荐使用的PPP身份验证过程，但通常用于向后兼容[RFC1334]。
SLIP (Serial Line Internet Protocol)
SLIP（串行线路互联网协议）
A serial datalink that only supports IP. A design prior to PPP.
仅支持IP的串行数据链路。PPP之前的设计。
ARAP (AppleTalk Remote Access Protocol)
ARAP（AppleTalk远程访问协议）
A serial datalink for accessing AppleTalk networks [ARAP].
用于访问AppleTalk网络[ARAP]的串行数据链路。
IPX (Internetwork Packet Exchange)
IPX（网络间数据包交换）
The network protocol used by NetWare networks [IPX].
NetWare网络[IPX]使用的网络协议。
L2TP (Layer Two Tunneling Protocol)
L2TP（第二层隧道协议）
L2TP [RFC3931] provides a dynamic mechanism for tunneling Layer 2 "circuits" across a packet-oriented data network.
L2TP[RFC3931]为穿越面向分组的数据网络的隧道层2“电路”提供了一种动态机制。
LAC (L2TP Access Concentrator)
LAC（L2TP接入集中器）
An L2TP Control Connection Endpoint being used to cross-connect an L2TP session directly to a datalink [RFC3931].
L2TP控制连接端点，用于将L2TP会话直接交叉连接到数据链路[RFC3931]。
LAT (Local Area Transport)
LAT（本地区交通）
A Digital Equipment Corp. LAN protocol for terminal services [LAT].
一种用于终端服务的数字设备公司局域网协议[LAT]。
LCP (Link Control Protocol)
链路控制协议
One of the three major components of PPP [RFC1661]. LCP is used to automatically agree upon encapsulation format options, handle varying limits on sizes of packets, detect a looped-back link and other common misconfiguration errors, and terminate the link. Other optional facilities provided are authentication of the identity of its peer on the link, and determination when a link is functioning properly and when it is failing.
PPP的三个主要组成部分之一[RFC1661]。LCP用于自动商定封装格式选项，处理数据包大小的不同限制，检测环回链路和其他常见错误配置，并终止链路。提供的其他可选功能包括验证链路上对等方的身份，以及确定链路何时正常运行以及何时出现故障。
PPTP (Point-to-Point Tunneling Protocol)
PPTP（点对点隧道协议）
A protocol that allows PPP to be tunneled through an IP network [RFC2637].
允许PPP通过IP网络隧道传输的协议[RFC2637]。
VPN (Virtual Private Network)
VPN（虚拟专用网络）
In this document, this term is used to describe access services that use tunneling methods.
在本文档中，该术语用于描述使用隧道方法的访问服务。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“建议”、“不建议”、“可”和“可选”应按照[RFC2119]中的说明进行解释。
The use of "MUST" and "MUST NOT" in the AVP Flag Rules columns of AVP Tables in this document refers to AVP flags ([RFC6733], Section 4.1) that:
本文件中AVP表格的AVP标志规则列中使用的“必须”和“不得”指的是AVP标志（[RFC6733]，第4.1节）：
o MUST be set to 1 in the AVP Header ("MUST" column) and
o 必须在AVP标题（“必须”列）中设置为1，并且
o MUST NOT be set to 1 ("MUST NOT" column)
o 不得设置为1（“不得”列）
Diameter nodes conforming to this specification MUST advertise support by including the value of one (1) in the Auth-Application-Id of the Capabilities-Exchange-Request (CER) message [RFC6733].
符合本规范的Diameter节点必须通过在功能交换请求（CER）消息[RFC6733]的身份验证应用程序Id中包含一（1）个值来公布支持。
When used in this application, the Auth-Application-Id AVP MUST be set to the value one (1) in the following messages
在此应用程序中使用时，必须在以下消息中将身份验证应用程序Id AVP设置为值1
o AA-Request (Section 3.1)
o AA请求（第3.1节）
o Re-Auth-Request(Section 3.3)
o 重新授权请求（第3.3节）
o Session-Termination-Request (Section 3.5)
o 会话终止请求（第3.5节）
o Abort-Session-Request (Section 3.7)
o 中止会话请求（第3.7节）
It is RECOMMENDED that the coupled accounting model (RFC 6733, Section 9.3) be used with this application; therefore, the value of the Acct-Application-Id AVP in the Accounting-Request (Section 3.9) and Accounting-Answer (Section 3.10) messages SHOULD be set to one (1).
建议将耦合会计模型（RFC 6733，第9.3节）用于该应用；因此，会计请求（第3.9节）和会计应答（第3.10节）消息中的Acct应用程序Id AVP的值应设置为一（1）。
The arrival of a new call or service connection at a port of a Network Access Server (NAS) starts a Diameter NAS Application 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
服务器处理该信息，并以包含NAS授权信息或故障代码（结果代码AVP）的Diameter AA应答（AAA）消息进行响应。价值
DIAMETER_MULTI_ROUND_AUTH indicates an additional authentication exchange, and several AAR and AAA messages may be exchanged until the transaction completes.
DIAMETER\u MULTI\u ROUND\u AUTH表示额外的身份验证交换，在事务完成之前可以交换多个AAR和AAA消息。
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 [RFC6733]. 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.
如果记帐处于活动状态，则应用程序还必须发送记帐消息[RFC6733]。为新会话发送记帐记录类型的开始记录。如果会话无法启动，则会发送带有所述故障原因的事件记录消息。
Note that the return of an unsupportable Accounting-Realtime-Required value [RFC6733] would result in a failure to establish the session.
请注意，返回不支持的Accounting Realtime Required值[RFC6733]将导致建立会话失败。
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 [RFC6733]. 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[RFC6733]通知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 [RFC6733]) to the NAS. Upon receipt of such a message, the NAS MUST respond to the request with a Re-Auth-Answer (RAA) message [RFC6733].
此外，Diameter服务器可以向NAS发出未经请求的重新身份验证和/或重新身份验证请求（例如，重新身份验证请求（RAR）消息[RFC6733]）。收到此类消息后，NAS必须使用重新验证应答（RAA）消息[RFC6733]响应请求。
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 subsessions. A service may also use a different Session-Id value for accounting (see Section 9.6 of [RFC6733]).
如果记帐处于活动状态，则每次身份验证或授权更改都应生成记帐消息。如果NAS服务是先前用户上下文的延续，则表示新会话属性和累积状态的临时_记录的记帐记录类型将是合适的。如果NAS检测到新用户或授权的重大更改，则服务可能会发送两条类型为STOP_RECORD和START_RECORD的消息。记帐可以更改子会话标识符（Acct Session Id或Acct Sub Session Id）以指示此类子会话。服务也可以使用不同的会话Id值进行记帐（参见[RFC6733]第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., an LCP Terminate-Request message [RFC1661] is received) or an administrative command, the NAS MUST issue a Session-Termination-Request (STR) [RFC6733] to its Diameter server. This will ensure that any resources maintained on the servers are freed appropriately.
当NAS接收到客户端正在断开用户会话的指示（例如，接收到LCP终止请求消息[RFC1661]或管理命令时，NAS必须向其Diameter服务器发出会话终止请求（STR）[RFC6733]。这将确保适当释放服务器上维护的任何资源。
Furthermore, a NAS that receives an Abort-Session-Request (ASR) [RFC6733] MUST issue an Abort-Session-Answer (ASA) if the session identified is active and disconnect the PPP (or tunneling) session.
此外，如果识别的会话处于活动状态，则接收中止会话请求（ASR）[RFC6733]的NAS必须发出中止会话应答（ASA），并断开PPP（或隧道）会话。
If accounting is active, an Accounting STOP_RECORD message [RFC6733] MUST be sent upon termination of the session context.
如果记帐处于活动状态，则会话上下文终止时必须发送记帐停止记录消息[RFC6733]。
More information on Diameter Session Termination can be found in Sections 8.4 and 8.5 of [RFC6733].
有关Diameter会话终止的更多信息，请参见[RFC6733]第8.4节和第8.5节。
This section defines the Diameter message Command Code [RFC6733] values that MUST be supported by all Diameter implementations conforming to this specification. The Command Codes are as follows:
本节定义了符合本规范的所有Diameter实现必须支持的Diameter消息命令代码[RFC6733]值。命令代码如下：
+-----------------------------------+---------+------+--------------+
| Command Name | Abbrev. | Code | Reference |
+-----------------------------------+---------+------+--------------+
| AA-Request | AAR | 265 | Section 3.1 |
| AA-Answer | AAA | 265 | Section 3.2 |
| Re-Auth-Request | RAR | 258 | Section 3.3 |
| Re-Auth-Answer | RAA | 258 | Section 3.4 |
| Session-Termination-Request | STR | 275 | Section 3.5 |
| Session-Termination-Answer | STA | 275 | Section 3.6 |
| Abort-Session-Request | ASR | 274 | Section 3.7 |
| Abort-Session-Answer | ASA | 274 | Section 3.8 |
| Accounting-Request | ACR | 271 | Section 3.9 |
| Accounting-Answer | ACA | 271 | Section 3.10 |
+-----------------------------------+---------+------+--------------+
+-----------------------------------+---------+------+--------------+
| Command Name | Abbrev. | Code | Reference |
+-----------------------------------+---------+------+--------------+
| AA-Request | AAR | 265 | Section 3.1 |
| AA-Answer | AAA | 265 | Section 3.2 |
| Re-Auth-Request | RAR | 258 | Section 3.3 |
| Re-Auth-Answer | RAA | 258 | Section 3.4 |
| Session-Termination-Request | STR | 275 | Section 3.5 |
| Session-Termination-Answer | STA | 275 | Section 3.6 |
| Abort-Session-Request | ASR | 274 | Section 3.7 |
| Abort-Session-Answer | ASA | 274 | Section 3.8 |
| Accounting-Request | ACR | 271 | Section 3.9 |
| Accounting-Answer | ACA | 271 | Section 3.10 |
+-----------------------------------+---------+------+--------------+
Note that the message formats in the following subsections use the standard Diameter Command Code Format ([RFC6733], Section 3.2).
请注意，以下小节中的消息格式使用标准Diameter命令代码格式（[RFC6733]，第3.2节）。
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 [RFC6733]. The recommended value for most situations is AUTHORIZE_AUTHENTICATE.
AA请求（AAR）通过将命令代码字段设置为265和命令标志字段中的“R”位来指示，用于为给定NAS用户请求身份验证和/或授权。请求类型通过身份验证请求类型AVP[RFC6733]标识。大多数情况下的建议值为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 4.4.
如果请求身份验证，则应显示用户名属性，以及携带密码信息的任何附加身份验证AVP。授权请求应仅包括执行授权的信息，如用户名、被叫站Id或主叫站Id AVPs。所有请求都应包含唯一标识呼叫源的AVP，如原始主机和NAS端口。某些网络可能使用不同的AVP进行授权。授权请求将包括第4.4节中定义的一些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 ]
<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 ]
* [ 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 4.4.
AA应答（AAA）消息通过将命令代码字段设置为265并清除命令标志字段中的“R”位来指示。它是响应AA请求（AAR）消息而发送的。如果请求授权，成功响应将包括适用于所提供服务的授权AVP，如第4.4节所定义。
For authentication exchanges requiring more than a single round trip, the server MUST set the Result-Code AVP to DIAMETER_MULTI_ROUND_AUTH.
对于需要多次往返的身份验证交换，服务器必须将结果代码AVP设置为DIAMETER\u MULTI\u round\u AUTH。
An AAA message with this result code MAY include one Reply-Message or more and MAY include zero or one State AVPs.
具有该结果代码的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 can be achieved in PPP via PAP. If it is impossible to deliver the text prompt to the user, the Diameter NAS Application client MUST treat the AA-Answer (AAA) with the Reply-Message AVP as an error and deny access.
如果存在回复消息AVP，则网络访问服务器应将文本发送到用户的客户端以向用户显示，指示客户端提示用户进行响应。例如，这可以通过PAP在PPP中实现。如果无法向用户发送文本提示，Diameter NAS应用程序客户端必须将带有回复消息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 ]
<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 ]
* [ 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 ]
[ Login-TCP-Port ]
* [ NAS-Filter-Rule ]
* [ QoS-Filter-Rule ]
* [ Tunneling ]
* [ Redirect-Host ]
[ Redirect-Host-Usage ]
[ Redirect-Max-Cache-Time ]
* [ Proxy-Info ]
* [ AVP ]
[ 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 ]
A Diameter server can initiate reauthentication and/or reauthorization for a particular session by issuing a Re-Auth-Request (RAR) message [RFC6733].
Diameter服务器可以通过发出重新身份验证请求（RAR）消息[RFC6733]来启动特定会话的重新身份验证和/或重新身份验证。
For example, for prepaid 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 reauthentication 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 ]
<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 ]
[ 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 Re-Auth-Answer (RAA) message [RFC6733] is sent in response to the RAR. The Result-Code AVP MUST be present and indicates the disposition of the request.
发送重新验证应答（RAA）消息[RFC6733]以响应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 ]
<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 ]
* [代理信息]*[AVP]
The Session-Termination-Request (STR) message [RFC6733] is sent by the NAS to inform the Diameter server that an authenticated and/or authorized session is being terminated.
NAS发送会话终止请求（STR）消息[RFC6733]，通知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 [RFC6733] 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）消息[RFC6733]以确认会话已终止的通知。结果代码AVP必须存在，并且可能包含在维修STR时发生错误的指示。
Upon sending 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 ]
* [ Failed-AVP ]
[ Origin-AAA-Protocol ]
[ Origin-State-Id ]
* [ Redirect-Host ]
[ Redirect-Host-Usage ]
[ Redirect-Max-Cache-Time ]
* [ Proxy-Info ]
* [ AVP ]
<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-Usage ]
[ Redirect-Max-Cache-Time ]
* [ Proxy-Info ]
* [ AVP ]
The Abort-Session-Request (ASR) message [RFC6733] can be sent by any Diameter server to the NAS providing session service to request that the session identified by the Session-Id be stopped.
任何Diameter服务器都可以向提供会话服务的NAS发送中止会话请求（ASR）消息[RFC6733]，请求停止会话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 ]
<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 ]
[ 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 [RFC6733] is sent in response to the ASR. The Result-Code AVP MUST be present and indicates the disposition of the request.
发送ASA消息[RFC6733]以响应ASR。结果代码AVP必须存在，并指示请求的处理。
If the session identified by Session-Id in the ASR was successfully terminated, the Result-Code is set to DIAMETER_SUCCESS. If the session is not currently active, the Result-Code AVP is set to DIAMETER_UNKNOWN_SESSION_ID. If the access device does not stop the session for any other reason, the Result-Code AVP is set to DIAMETER_UNABLE_TO_COMPLY.
如果ASR中由会话Id标识的会话已成功终止，则结果代码将设置为DIAMETER\u SUCCESS。如果会话当前未处于活动状态，则结果代码AVP设置为DIAMETER_UNKNOWN_session_ID。如果访问设备未因任何其他原因停止会话，则结果代码AVP设置为DIAMETER_UNABLE_to_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 [RFC6733] is sent by the NAS to report its session information to a target server downstream.
NAS发送ACR消息[RFC6733]以向下游目标服务器报告其会话信息。
The Acct-Application-Id AVP MUST be present.
帐户应用程序Id AVP必须存在。
The AVPs listed in the Diameter Base protocol specification [RFC6733] MUST be assumed to be present, as appropriate. NAS service-specific accounting AVPs SHOULD be present as described in Section 4.6 and the rest of this specification.
必须假设Diameter基本协议规范[RFC6733]中列出的AVP存在（视情况而定）。NAS服务特定的会计AVP应按照第4.6节和本规范其余部分的说明提供。
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 }
[ 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 ]
<AC-Request> ::= < Diameter Header: 271, REQ, PXY >
< Session-Id >
{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
{ Accounting-Record-Type }
{ Accounting-Record-Number }
{ Acct-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 ]
[ 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 ]
The ACA message [RFC6733] is used to acknowledge an Accounting-Request command. The Accounting-Answer command contains the same Session-Id as the Request.
ACA消息[RFC6733]用于确认记帐请求命令。记帐应答命令包含与请求相同的会话Id。
Only the target Diameter server or home Diameter server SHOULD respond with the Accounting-Answer command.
只有目标Diameter服务器或home Diameter服务器应使用记帐应答命令进行响应。
The Acct-Application-Id AVP MUST be present.
帐户应用程序Id AVP必须存在。
The AVPs listed in the Diameter Base protocol specification [RFC6733] MUST be assumed to be present, as appropriate. NAS service-specific accounting AVPs SHOULD be present as described in Section 4.6 and the rest of this specification.
必须假设Diameter基本协议规范[RFC6733]中列出的AVP存在（视情况而定）。NAS服务特定的会计AVP应按照第4.6节和本规范其余部分的说明提供。
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 }
[ 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 ]
<AC-Answer> ::= < Diameter Header: 271, PXY >
< Session-Id >
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
{ Accounting-Record-Type }
{ Accounting-Record-Number }
{ Acct-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 ]
* [ AVP ]
[ Acct-Interim-Interval ]
* [ Class ]
* [ Proxy-Info ]
* [ AVP ]
The following sections define a new derived AVP data format, define a set of application-specific AVPs, and describe the use of AVPs defined in other documents by the Diameter NAS Application.
以下各节定义了新的衍生AVP数据格式，定义了一组特定于应用程序的AVP，并描述了Diameter NAS应用程序在其他文档中定义的AVP的使用。
The QosFilterRule format is derived from the OctetString AVP Base Format. It uses the US-ASCII charset. Packets may be marked or metered based on the following information:
QosFilterRule格式源自八进制字符串AVP基本格式。它使用US-ASCII字符集。可根据以下信息对数据包进行标记或计量：
o Direction (in or out)
o 方向（向内或向外）
o Source and destination IP address (possibly masked)
o 源和目标IP地址（可能被屏蔽）
o Protocol
o 协议
o Source and destination port (lists or ranges)
o 源端口和目标端口（列表或范围）
o Differentiated Services Code Point (DSCP) values (no mask or range)
o 区分服务代码点（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的操作目录协议[选项]
where
哪里
action
行动
tag Mark packet with a specific DSCP [RFC2474]
使用特定DSCP标记数据包[RFC2474]
meter Meter traffic
表流量
dir The format is as described under IPFilterRule [RFC6733]
dir格式如IPFilterRule[RFC6733]中所述
proto The format is as described under IPFilterRule [RFC6733]
proto格式如IPFilterRule[RFC6733]中所述
src and dst The format is as described under IPFilterRule [RFC6733]
src和dst格式如IPFilterRule[RFC6733]所述
The options are described in Section 4.4.9.
第4.4.9节描述了这些选项。
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代码可以为实现提供有用的基础。
Diameter reserves the AVP Codes 0 - 255 for RADIUS Attributes that are implemented in Diameter.
Diameter为在Diameter中实现的半径属性保留AVP代码0-255。
This section describes the AVPs specific to 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.
本节介绍特定于Diameter应用程序的AVP，这些应用程序用于识别呼叫和会话上下文及状态信息。根据请求，此信息允许服务器限定会话。
These AVPs are used in addition to the following AVPs from the Diameter Base protocol specification [RFC6733]:
除了Diameter基本协议规范[RFC6733]中的以下AVP之外，还使用了这些AVP：
Session-Id Auth-Application-Id Origin-Host Origin-Realm Auth-Request-Type Termination-Cause
会话Id身份验证应用程序Id源主机源域身份验证请求类型终止原因
The following table gives the possible flag values for the session level AVPs.
下表给出了会话级AVP的可能标志值。
+-----------+
| AVP Flag |
| Rules |
|-----+-----+
|MUST | MUST|
Attribute Name Section Defined | | NOT|
-----------------------------------------|-----+-----|
NAS-Port 4.2.2 | M | V |
NAS-Port-Id 4.2.3 | M | V |
NAS-Port-Type 4.2.4 | M | V |
Called-Station-Id 4.2.5 | M | V |
Calling-Station-Id 4.2.6 | M | V |
Connect-Info 4.2.7 | M | V |
Originating-Line-Info 4.2.8 | M | V |
Reply-Message 4.2.9 | M | V |
-----------------------------------------|-----+-----|
+-----------+
| AVP Flag |
| Rules |
|-----+-----+
|MUST | MUST|
Attribute Name Section Defined | | NOT|
-----------------------------------------|-----+-----|
NAS-Port 4.2.2 | M | V |
NAS-Port-Id 4.2.3 | M | V |
NAS-Port-Type 4.2.4 | M | V |
Called-Station-Id 4.2.5 | M | V |
Calling-Station-Id 4.2.6 | M | V |
Connect-Info 4.2.7 | M | V |
Originating-Line-Info 4.2.8 | M | V |
Reply-Message 4.2.9 | M | V |
-----------------------------------------|-----+-----|
The NAS-Port AVP (AVP Code 5) is of type Unsigned32 and contains the physical or virtual port number of the NAS, which authenticates the user. Note that "port" is meant in its sense as a service connection on the NAS, not as an IP protocol identifier; hence, the format and contents of the string that identifies the port are specific to the NAS implementation.
NAS端口AVP（AVP代码5）的类型为Unsigned32，包含NAS的物理或虚拟端口号，用于验证用户。注意，“端口”是指NAS上的服务连接，而不是IP协议标识符；因此，标识端口的字符串的格式和内容特定于NAS实现。
Either the NAS-Port AVP or the NAS-Port-Id AVP (Section 4.2.3) SHOULD be present in the AA-Request (AAR, Section 3.1) command if the NAS differentiates among its ports.
如果NAS在其端口之间存在差异，则NAS端口AVP或NAS端口Id AVP（第4.2.3节）应出现在AA请求（AAR，第3.1节）命令中。
The NAS-Port-Id AVP (AVP Code 87) is of type UTF8String and consists of 7-bit US-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类型，由7位US-ASCII文本组成，用于标识NAS端口，以验证用户身份。请注意，“端口”是指NAS上的服务连接，而不是IP协议标识符。
Either the NAS-Port-Id AVP or the NAS-Port AVP (Section 4.2.2) SHOULD be present in the AA-Request (AAR, Section 3.1) command if the NAS differentiates among its ports. NAS-Port-Id is intended for use by NASes that cannot conveniently number their ports.
如果NAS在其端口之间存在差异，则NAS端口Id AVP或NAS端口AVP（第4.2.2节）应出现在AA请求（AAR，第3.1节）命令中。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 currently supported values of the NAS-Port-Type AVP are listed in [RADIUSAttrVals].
[RADIUSAttrVals]中列出了当前支持的NAS端口类型AVP值。
The Called-Station-Id AVP (AVP Code 30) is of type UTF8String and contains a 7-bit US-ASCII string sent by the NAS to describe the Layer 2 address the user contacted in the request. For dialup access, this can be a phone number obtained by using the Dialed Number Identification Service (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 Media Access Control (MAC) address formatted as described in [RFC3580].
被叫站Id AVP（AVP代码30）为UTF8String类型，包含NAS发送的7位US-ASCII字符串，用于描述用户在请求中联系的第2层地址。对于拨号接入，这可以是通过使用拨号号码识别服务（DNIS）或类似技术获得的电话号码。请注意，这可能与电话号码不同。为了与IEEE 802访问一起使用，被叫站Id可以包含如[RFC3580]中所述格式化的媒体访问控制（MAC）地址。
If the Called-Station-Id AVP is present in an AAR message, the Auth-Request-Type AVP is set to AUTHORIZE_ONLY, and the User-Name AVP is absent, the Diameter server MAY perform authorization based on this AVP. This can be used by a NAS to request whether a call should be answered based on the DNIS result.
如果AAR消息中存在被叫站Id AVP，则Auth请求类型AVP被设置为仅授权，并且用户名AVP不存在，Diameter服务器可以基于该AVP执行授权。NAS可使用此命令请求是否应根据DNIS结果应答呼叫。
Further codification of this field's allowed content and usage is outside the scope of this specification.
此字段允许内容和用法的进一步编码不在本规范的范围内。
The Calling-Station-Id AVP (AVP Code 31) is of type UTF8String and contains a 7-bit US-ASCII string sent by the NAS to describe 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, formatted as described in RFC 3580.
呼叫站Id AVP（AVP代码31）为UTF8String类型，包含NAS发送的7位US-ASCII字符串，用于描述用户在请求中连接的第2层地址。对于拨号接入，这是使用自动号码识别（ANI）或类似技术拨打的电话号码。为了与IEEE 802接入一起使用，呼叫站Id AVP可以包含MAC地址，其格式如RFC 3580中所述。
If the Calling-Station-Id AVP is present in an AAR message, the Auth-Request-Type AVP is set to AUTHORIZE_ONLY, and the User-Name AVP is absent, the Diameter server MAY perform authorization based on the value of this AVP. 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.)
如果呼叫站Id AVP存在于AAR消息中，则Auth请求类型AVP被设置为仅授权，并且用户名AVP不存在，Diameter服务器可以基于该AVP的值执行授权。NAS可使用此功能请求是否应根据第2层地址（ANI、MAC地址等）应答呼叫
Further codification of this field's allowed content and usage 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 an ACR message with the value of the Accounting-Record-Type AVP set to STOP. When sent in the AA-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 at which the NAS modem transmits), then a slash (/), then the receive speed, and then other optional information.
Connect Info AVP（AVP代码77）为UTF8String类型，在AA请求消息或ACR消息中发送，会计记录类型AVP的值设置为STOP。在AA请求中发送时，它指示用户连接的性质。连接速度应包含在消息中第一个连接信息AVP的开头。如果发送和接收连接速度不同，则两种连接速度都可以包含在第一个AVP中，首先列出发送速度（NAS调制解调器发送的速度），然后是斜杠（/），然后是接收速度，然后是其他可选信息。
For example: "28800 V42BIS/LAPM" or "52000/31200 V90"
For example: "28800 V42BIS/LAPM" or "52000/31200 V90"
If sent in an ACR message with the value of the Accounting-Record-Type AVP set to STOP, this attribute may summarize statistics relating to session quality. For example, in IEEE 802.11, the Connect-Info AVP may contain information on the number of link layer retransmissions. The exact format of this attribute is implementation specific.
如果在ACR消息中发送，且会计记录类型AVP的值设置为STOP，则此属性可能汇总与会话质量相关的统计信息。例如，在IEEE 802.11中，Connect Info AVP可以包含关于链路层重传次数的信息。此属性的确切格式是特定于实现的。
The Originating-Line-Info AVP (AVP Code 94) is of type OctetString and is sent by the NAS system to convey information about the origin of the call from a Signaling System 7 (SS7).
始发线路信息AVP（AVP代码94）是OctetString类型，由NAS系统发送以传送关于来自信令系统7（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 phone, cellular phone). 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 information on the currently assigned values, see [ANITypes].
值字段包含两个八位字节（00-99）。ANSI T1.113和BELLCORE 394可用于获取有关这些值及其使用的附加信息。有关当前指定值的信息，请参见[ANITypes]。
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 contain text to prompt the user before another AA-Request attempt. When used in an AA-Answer message containing a Result-Code AVP with the value DIAMETER_MULTI_ROUND_AUTH or in a Re-Auth-Request message, it MAY contain text to prompt the user for a response.
回复消息AVP可能包含在另一个AA请求尝试之前提示用户的文本。在包含结果代码AVP且值为DIAMETER\u MULTI\u ROUND\u AUTH的AA应答消息中或在重新认证请求消息中使用时，它可能包含提示用户响应的文本。
This section defines the AVPs necessary to carry the authentication information in the Diameter protocol. The functionality defined here provides a RADIUS-like Authentication, Authorization, and Accounting service [RFC2865] over a more reliable and secure transport, as defined in the Diameter Base protocol [RFC6733].
本节定义了在Diameter协议中承载身份验证信息所需的AVP。此处定义的功能通过Diameter基本协议[RFC6733]中定义的更可靠、更安全的传输提供类似RADIUS的身份验证、授权和记帐服务[RFC2865]。
The following table gives the possible flag values for the session level AVPs.
下表给出了会话级AVP的可能标志值。
+----------+
| AVP Flag |
| Rules |
|----+-----|
|MUST| MUST|
Attribute Name Section Defined | | NOT|
-----------------------------------------|----+-----|
User-Password 4.3.1 | M | V |
Password-Retry 4.3.2 | M | V |
Prompt 4.3.3 | M | V |
CHAP-Auth 4.3.4 | M | V |
CHAP-Algorithm 4.3.5 | M | V |
CHAP-Ident 4.3.6 | M | V |
CHAP-Response 4.3.7 | M | V |
CHAP-Challenge 4.3.8 | M | V |
ARAP-Password 4.3.9 | M | V |
ARAP-Challenge-Response 4.3.10 | M | V |
ARAP-Security 4.3.11 | M | V |
ARAP-Security-Data 4.3.12 | M | V |
-----------------------------------------|----+-----|
+----------+
| AVP Flag |
| Rules |
|----+-----|
|MUST| MUST|
Attribute Name Section Defined | | NOT|
-----------------------------------------|----+-----|
User-Password 4.3.1 | M | V |
Password-Retry 4.3.2 | M | V |
Prompt 4.3.3 | M | V |
CHAP-Auth 4.3.4 | M | V |
CHAP-Algorithm 4.3.5 | M | V |
CHAP-Ident 4.3.6 | M | V |
CHAP-Response 4.3.7 | M | V |
CHAP-Challenge 4.3.8 | M | V |
ARAP-Password 4.3.9 | M | V |
ARAP-Challenge-Response 4.3.10 | M | V |
ARAP-Security 4.3.11 | M | V |
ARAP-Security-Data 4.3.12 | M | V |
-----------------------------------------|----+-----|
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 by the Diameter Base protocol [RFC6733], Diameter messages are encrypted by using IPsec [RFC4301] or Transport Layer Security (TLS) [RFC5246]. Unless this AVP is used for one-time passwords, the User-Password AVP SHOULD NOT be used in untrusted proxy environments without encrypting it by using end-to-end security techniques.
用户密码AVP包含用户密码或一次性密码，因此表示敏感信息。根据Diameter基本协议[RFC6733]的要求，Diameter消息使用IPsec[RFC4301]或传输层安全性（TLS）[RFC5246]进行加密。除非此AVP用于一次性密码，否则在未使用端到端安全技术加密的情况下，不应在不受信任的代理环境中使用用户密码AVP。
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 (Section 4.4.10.1) is set to ARAP.
密码重试AVP（AVP代码75）的类型为Unsigned32，如果结果代码指示身份验证失败，则可能包含在AA应答中。此AVP的值表示在断开连接之前允许用户进行多少次身份验证尝试。本AVP主要用于帧协议AVP（第4.4.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 [RADIUSAttrVals].
支持的值列在[RADIUSAttrVals]中。
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) [RFC1994]. If the CHAP-Auth AVP is found in a message, the CHAP-Challenge AVP (Section 4.3.8) MUST be present as well. The optional AVPs containing the CHAP response depend upon the value of the CHAP-Algorithm AVP (Section 4.3.8). The grouped AVP has the following ABNF [RFC5234] grammar:
CHAP认证AVP（AVP代码402）属于分组类型，并且包含使用PPP质询握手认证协议（CHAP）认证用户所需的信息[RFC1994]。如果在消息中找到CHAP验证AVP，则CHAP质询AVP（第4.3.8节）也必须存在。包含CHAP响应的可选AVP取决于CHAP算法AVP的值（第4.3.8节）。分组的AVP具有以下ABNF[RFC5234]语法：
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 [RFC1994]. The following values are currently supported:
CHAP算法AVP（AVP代码403）属于枚举类型，包含CHAP响应计算中使用的算法标识符[RFC1994]。当前支持以下值：
CHAP with MD5 5
具有MD5的CHAP
The CHAP response is computed by using the procedure described in [RFC1994]. This algorithm requires that the CHAP-Response AVP (Section 4.3.7) MUST be present in the CHAP-Auth AVP (Section 4.3.4).
CHAP响应是使用[RFC1994]中描述的程序计算的。该算法要求CHAP响应AVP（第4.3.7节）必须出现在CHAP身份验证AVP（第4.3.4节）中。
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 [RFC1994].
CHAP标识AVP（AVP代码404）为八进制字符串类型，包含用于计算CHAP响应的1个八进制CHAP标识[RFC1994]。
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 [RFC1994].
CHAP响应AVP（AVP代码405）是OctetString类型，包含用户响应CHAP质询提供的16个八位字节的身份验证数据[RFC1994]。
The CHAP-Challenge AVP (AVP Code 60) is of type OctetString and contains the CHAP Challenge sent by the NAS to the CHAP peer [RFC1994].
CHAP质询AVP（AVP代码60）的类型为OctetString，包含NAS发送给CHAP对等方的CHAP质询[RFC1994]。
The ARAP-Password AVP (AVP Code 70) is of type OctetString and is only present when the Framed-Protocol AVP (Section 4.4.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 [RFC2869] for more information on the contents of this AVP.
ARAP密码AVP（AVP代码70）为OctetString类型，仅当消息中包含帧协议AVP（第4.4.10.1节）并设置为ARAP时才存在。如果存在用户密码或CHAP Auth AVP，则此AVP不得存在。有关本AVP内容的更多信息，请参见[RFC2869]。
The ARAP-Challenge-Response AVP (AVP Code 84) is of type OctetString and is only present when the Framed-Protocol AVP (Section 4.4.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 Diameter 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 as the key. If the user's password is fewer than 8 octets in length, the password is padded at the end with NULL octets to a length of 8 before it is used as a key.
ARAP质询响应AVP（AVP代码84）为OctetString类型，仅当消息中包含帧协议AVP（第4.4.10.1节）并设置为ARAP时才存在。此AVP包含对拨入客户端质询的8位字节响应。Diameter服务器通过从ARAP密码AVP的高阶8个八位字节中获取拨入客户端的质询，并使用身份验证用户的密码作为密钥对该值执行DES加密来计算该值。如果用户的密码长度小于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 (Section 4.4.10.1) is set to the value of ARAP, and the Result-Code AVP ([RFC6733], Section 7.1) is set to DIAMETER_MULTI_ROUND_AUTH. See RFC 2869 for more information on the contents of this AVP.
如果帧协议AVP（第4.4.10.1节）设置为ARAP值，并且结果代码AVP（[RFC6733]，第7.1节）设置为DIAMETER\u MULTI\u ROUND\u AUTH，则ARAP安全AVP（AVP代码73）的类型为Unsigned32，并且可能出现在AA应答消息中。有关本AVP内容的更多信息，请参见RFC 2869。
The ARAP-Security-Data 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 (Section 4.4.10.1) is set to the value of ARAP and the Result-Code AVP ([RFC6733], Section 7.1) is set to DIAMETER_MULTI_ROUND_AUTH. This AVP contains the security module challenge or response associated with the ARAP Security Module specified in the ARAP-Security AVP (Section 4.3.11).
ARAP安全数据AVP（AVP代码74）为OctetString类型，如果帧协议AVP（第4.4.10.1节）设置为ARAP值，且结果代码AVP（[RFC6733]，第7.1节）设置为DIAMETER_MULTI_ROUND_AUTH，则可能出现在AA请求或AA应答消息中。本AVP包含与ARAP安全AVP（第4.3.11节）中规定的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 Section 4.5 MAY be present.
本节包含NAS应用程序中支持的授权AVP。服务类型AVP应出现在所有消息中，根据其值，本节和第4.5节中定义的其他AVP可能会出现。
The following table gives the possible flag values for the session-level AVPs.
下表给出了会话级AVP的可能标志值。
+----------+
| AVP Flag |
| Rules |
|----+-----|
|MUST| MUST|
Attribute Name Section Defined | | NOT|
-----------------------------------------|----+-----|
Service-Type 4.4.1 | M | V |
Callback-Number 4.4.2 | M | V |
Callback-Id 4.4.3 | M | V |
Idle-Timeout 4.4.4 | M | V |
Port-Limit 4.4.5 | M | V |
NAS-Filter-Rule 4.4.6 | M | V |
Filter-Id 4.4.7 | M | V |
Configuration-Token 4.4.8 | M | V |
QoS-Filter-Rule 4.4.9 | | |
Framed-Protocol 4.4.10.1 | M | V |
Framed-Routing 4.4.10.2 | M | V |
Framed-MTU 4.4.10.3 | M | V |
Framed-Compression 4.4.10.4 | M | V |
Framed-IP-Address 4.4.10.5.1 | M | V |
Framed-IP-Netmask 4.4.10.5.2 | M | V |
Framed-Route 4.4.10.5.3 | M | V |
Framed-Pool 4.4.10.5.4 | M | V |
Framed-Interface-Id 4.4.10.5.5 | M | V |
Framed-IPv6-Prefix 4.4.10.5.6 | M | V |
Framed-IPv6-Route 4.4.10.5.7 | M | V |
Framed-IPv6-Pool 4.4.10.5.8 | M | V |
Framed-IPX-Network 4.4.10.6.1 | M | V |
Framed-Appletalk-Link 4.4.10.7.1 | M | V |
Framed-Appletalk-Network 4.4.10.7.2 | M | V |
Framed-Appletalk-Zone 4.4.10.7.3 | M | V |
ARAP-Features 4.4.10.8.1 | M | V |
ARAP-Zone-Access 4.4.10.8.2 | M | V |
Login-IP-Host 4.4.11.1 | M | V |
Login-IPv6-Host 4.4.11.2 | M | V |
Login-Service 4.4.11.3 | M | V |
Login-TCP-Port 4.4.11.4.1 | M | V |
Login-LAT-Service 4.4.11.5.1 | M | V |
Login-LAT-Node 4.4.11.5.2 | M | V |
Login-LAT-Group 4.4.11.5.3 | M | V |
Login-LAT-Port 4.4.11.5.4 | M | V |
-----------------------------------------|----+-----|
+----------+
| AVP Flag |
| Rules |
|----+-----|
|MUST| MUST|
Attribute Name Section Defined | | NOT|
-----------------------------------------|----+-----|
Service-Type 4.4.1 | M | V |
Callback-Number 4.4.2 | M | V |
Callback-Id 4.4.3 | M | V |
Idle-Timeout 4.4.4 | M | V |
Port-Limit 4.4.5 | M | V |
NAS-Filter-Rule 4.4.6 | M | V |
Filter-Id 4.4.7 | M | V |
Configuration-Token 4.4.8 | M | V |
QoS-Filter-Rule 4.4.9 | | |
Framed-Protocol 4.4.10.1 | M | V |
Framed-Routing 4.4.10.2 | M | V |
Framed-MTU 4.4.10.3 | M | V |
Framed-Compression 4.4.10.4 | M | V |
Framed-IP-Address 4.4.10.5.1 | M | V |
Framed-IP-Netmask 4.4.10.5.2 | M | V |
Framed-Route 4.4.10.5.3 | M | V |
Framed-Pool 4.4.10.5.4 | M | V |
Framed-Interface-Id 4.4.10.5.5 | M | V |
Framed-IPv6-Prefix 4.4.10.5.6 | M | V |
Framed-IPv6-Route 4.4.10.5.7 | M | V |
Framed-IPv6-Pool 4.4.10.5.8 | M | V |
Framed-IPX-Network 4.4.10.6.1 | M | V |
Framed-Appletalk-Link 4.4.10.7.1 | M | V |
Framed-Appletalk-Network 4.4.10.7.2 | M | V |
Framed-Appletalk-Zone 4.4.10.7.3 | M | V |
ARAP-Features 4.4.10.8.1 | M | V |
ARAP-Zone-Access 4.4.10.8.2 | M | V |
Login-IP-Host 4.4.11.1 | M | V |
Login-IPv6-Host 4.4.11.2 | M | V |
Login-Service 4.4.11.3 | M | V |
Login-TCP-Port 4.4.11.4.1 | M | V |
Login-LAT-Service 4.4.11.5.1 | M | V |
Login-LAT-Node 4.4.11.5.2 | M | V |
Login-LAT-Group 4.4.11.5.3 | M | V |
Login-LAT-Port 4.4.11.5.4 | M | V |
-----------------------------------------|----+-----|
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-Type AVPs received in a response as a failure and end the session with a DIAMETER_INVALID_AVP_VALUE Result-Code.
服务类型AVP（AVP代码6）是枚举类型，包含用户请求的服务类型或要提供的服务类型。一个这样的AVP可以存在于认证和/或授权请求或响应中。NAS不需要实现所有这些服务类型。它必须将响应中接收到的未知或不受支持的服务类型AVP视为失败，并使用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 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).
在请求中使用时，服务类型AVP应被视为向服务器发出的提示，即NAS认为用户更喜欢指定的服务类型。服务器不需要遵守提示。此外，如果服务器指定的服务受支持，但与当前访问模式不兼容，则NAS必须无法启动会话。NAS还必须生成相应的错误消息。
The complete list of defined values that the Service-Type AVP can take can be found in [RFC2865] and the relevant IANA registry [RADIUSAttrVals], but the following values require further qualification here:
服务类型AVP可采用的定义值的完整列表可在[RFC2865]和相关IANA注册表[RADIUSAttrVals]中找到，但以下值需要进一步限定：
Login (1)
登录（1）
The user should be connected to a host. The message MAY include additional AVPs as defined in Sections 4.4.11.4 or 4.4.11.5.
用户应连接到主机。该信息可能包括第4.4.11.4节或第4.4.11.5节中定义的附加AVP。
Framed (2)
框架（2）
A Framed Protocol, such as PPP or SLIP, should be started for the user. The message MAY include additional AVPs defined in Sections 4.4.10 or 4.5 for tunneling services.
应为用户启动框架协议，如PPP或SLIP。该信息可能包括第4.4.10节或第4.5节中定义的隧道服务附加AVP。
Callback Login (3)
回调登录（3）
The user should be disconnected and called back, then connected to a host. The message MAY include additional AVPs defined in this section.
用户应断开连接并回拨，然后连接到主机。该消息可能包括本节中定义的附加AVP。
Callback Framed (4)
电话号码（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 Sections 4.4.10 or 4.5 for tunneling services.
用户应断开连接并回拨，然后为用户启动一个框架协议，如PPP或SLIP。该信息可能包括第4.4.10节或第4.5节中定义的隧道服务附加AVP。
The Callback-Number AVP (AVP Code 19) is of type UTF8String and contains a dialing string to be used for callback, the format of which is deployment specific. The Callback-Number AVP 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类型，包含用于回拨的拨号字符串，其格式特定于部署。回拨号码AVP可在认证和/或授权请求中用作向服务器提示需要回拨服务的提示，但服务器不需要在相应响应中遵守该提示。
Any further 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 (Section 4.4.2) is therefore RECOMMENDED.
此AVP不支持漫游，因为它假定在NAS上配置了回调Id。因此，建议使用回拨号码AVP（第4.4.2节）。
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 [RFC1990] service is desired, but the server is not required to honor the hint in the corresponding response.
端口限制AVP（AVP代码62）的类型为Unsigned32，并设置NAS向用户提供的最大端口数。它可以在身份验证和/或授权请求中用作对服务器的提示，提示需要多链路PPP[RFC1990]服务，但服务器不需要在相应的响应中遵守该提示。
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. It is intended to be human readable. Zero or more Filter-Id AVPs MAY be sent in an authorization answer message.
过滤器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 environments where backward compatibility with RADIUS is not required, it is RECOMMENDED that the NAS-Filter-Rule AVP (Section 4.4.6) be used instead.
在不要求与RADIUS向后兼容的环境中，建议改用NAS筛选规则AVP（第4.4.6节）。
The Configuration-Token AVP (AVP Code 78) is of type OctetString and is sent by a Diameter server to a Diameter Proxy 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 (Section 4.1.1) 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类型（第4.1.1节），并提供需要在NAS上为用户配置的QoS过滤规则。一个或多个这样的avp可以存在于授权响应中。
The use of this AVP is NOT RECOMMENDED; the AVPs defined by [RFC5777] SHOULD be used instead.
不建议使用此AVP；应改用[RFC5777]定义的AVP。
The following options are defined for the QoSFilterRule filters:
为QoSFilterRule过滤器定义了以下选项：
DSCP <color>
DSCP<color>
If action is set to tag (Section 4.1.1), this option MUST be included in the rule.
如果操作设置为标记（第4.1.1节），则该选项必须包含在规则中。
Color values are defined in [RFC2474]. Exact matching of DSCP values is required (no masks or ranges).
颜色值在[RFC2474]中定义。需要精确匹配DSCP值（无掩码或范围）。
metering <rate> <color_under> <color_over>
metering <rate> <color_under> <color_over>
The metering option provides Assured Forwarding, as defined in [RFC2597]. and MUST be present if the action is set to meter (Section 4.1.1) 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 [RFC2597] (e.g., AF13).
计量选项提供有保证的转发，如[RFC2597]中所定义。如果操作设置为“计量”（第4.1.1节），则必须存在。速率选项是接入设备用于标记数据包的吞吐量，单位为比特/秒。速率上的流量在码点上用颜色_标记，速率下的流量在码点下用颜色_标记。color_under和color_over选项包含drop首选项，并且必须符合[RFC2597]中描述的推荐代码点关键字（例如，AF13）。
The metering option also supports the strict limit on traffic required by Expedited Forwarding, as defined in [RFC3246]. The color_over option may contain the keyword "drop" to prevent forwarding of traffic that exceeds the rate parameter.
计量选项还支持[RFC3246]中定义的对快速转发所需流量的严格限制。color_over选项可能包含关键字“drop”，以防止转发超过rate参数的流量。
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 [RADIUSAttrVals].
帧协议AVP（AVP代码7）属于枚举类型，包含用于帧访问的帧。此AVP可能存在于请求和响应中。支持的值列在[RADIUSAttrVals]中。
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 [RADIUSAttrVals].
帧路由AVP（AVP代码10）是枚举的类型，并且包含当用户是网络的路由器时用户的路由方法。此AVP应仅出现在授权响应中。支持的值列在[RADIUSAttrVals]中。
The Framed-MTU AVP (AVP Code 12) is of type Unsigned32 and contains the Maximum Transmission Unit (MTU) 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，并且包含要为用户配置的最大传输单元（MTU），当它不是通过某些其他方式（例如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 [RADIUSAttrVals].
支持的值列在[RADIUSAttrVals]中。
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) [RFC2865] 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）[RFC2865]的类型为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 7-bit US-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上为用户配置的7位US-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.0.2.0/24 192.0.2.1 1"
"192.0.2.0/24 192.0.2.1 1"
The length specifier may be omitted, in which case it should default to 8 bits for class A prefixes, 16 bits for class B prefixes, and 24 bits for class C prefixes; for example,
长度说明符可以省略，在这种情况下，A类前缀默认为8位，B类前缀默认为16位，C类前缀默认为24位；例如
"192.0.2.0 192.0.2.1 1"
"192.0.2.0 192.0.2.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 [RFC2869], the encoding of the Data field SHOULD also conform to the rules for the UTF8String Data Format.
尽管为了与RADIUS[RFC2869]兼容而指定为类型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 identifier is desired, but the server is not required to honor the hint in the corresponding response.
帧接口Id AVP（AVP代码96）的类型为Unsigned64，包含要为用户配置的IPv6接口标识符。它可以在授权请求中用作提示服务器需要特定的接口标识符，但服务器不需要在相应的响应中遵守该提示。
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 US-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上的用户配置的US-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地址前缀，后跟一个斜杠和一个十进制长度说明符，说明应使用前缀的高位。后跟一个空格、十六进制表示法的网关地址、一个空格和一个或多个由空格分隔的度量；例如
"2001:db8::/32 2001:db8:106:a00:20ff:fe99:a998 1"
"2001:db8::/32 2001:db8: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地址用作网关地址，例如：
"2001:db8::/32 :: 1"
"2001:db8::/32 :: 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 [RFC3162], the encoding of the Data field SHOULD also conform to the rules for the UTF8String Data Format.
尽管为了与RADIUS[RFC3162]兼容而指定为类型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].
当用户请求或被授予访问IPX网络服务[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 (Section 4.4.10.1) is set to ARAP. Section 2.2 of RFC 2869 describes the operational use of these attributes.
当用户通过AppleTalk远程访问协议[ARAP]请求或被授权访问AppleTalk网络时，使用本节中定义的AVP。仅当帧协议AVP（第4.4.10.1节）设置为ARAP时，它们才存在。RFC 2869第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 RFC 2869 for more information about the format of this AVP.
ARAP功能AVP（AVP代码71）为OctetString类型，如果帧协议AVP设置为ARAP值，则可能出现在AA接受消息中。有关此AVP格式的更多信息，请参阅RFC 2869。
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 [RADIUSAttrVals] and defined in [RFC2869].
支持的值在[RADIUSAttrVals]中列出，并在[RFC2869]中定义。
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) [RFC2865] 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
登录IP主机AVP（AVP代码14）[RFC2865]为OctetString类型，包含登录服务AVP时连接用户的主机的IPv4地址。它可以在一个特定的环境中使用
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.
AA Request命令向Diameter服务器提示需要特定主机，但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) [RFC3162] 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）[RFC3162]的类型为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.
两个地址具有特殊意义，0xFFFFFFFFFFFFFFFFFFFFFFFFFFFF和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. The supported values are listed in RFC 2869.
登录服务AVP（AVP代码15）属于枚举类型，包含应用于将用户连接到登录主机的服务。此AVP应仅出现在授权响应中。RFC 2869中列出了支持的值。
The AVP described in the following 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. 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.
管理员在处理群集系统时使用此服务属性。在这些环境中，几个不同的分时主机共享相同的资源（磁盘、打印机等），管理员通常配置每个主机以提供对每个共享资源的访问（服务）。在这种情况下，集群中的每个主机都通过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 lower-case alphabetics, and the ISO Latin-1 character set extension [ISO.8859-1.1987]. All LAT string comparisons are case insensitive.
字符串字段包含要使用的LAT服务的标识。LAT体系结构允许此字符串包含$（美元），-（连字符）。（句号）、u9（下划线）、数字、大写和小写字母以及ISO拉丁-1字符集扩展[ISO.8859-1.1987]。所有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 lower-case alphabetics, and the ISO Latin-1 character set extension [ISO.8859-1.1987]. All LAT string comparisons are case insensitive.
字符串字段包含要使用的LAT服务的标识。LAT体系结构允许此字符串包含$（美元），-（连字符）。（句号）、u9（下划线）、数字、大写和小写字母以及ISO拉丁-1字符集扩展[ISO.8859-1.1987]。所有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 [ISO.8859-1.1987].
字符串字段包含要使用的LAT服务的标识。LAT体系结构允许此字符串包含$（美元），-（连字符）。（句号）、u9（下划线）、数字、大写和小写字母以及ISO拉丁-1字符集扩展[ISO.8859-1.1987]。
All LAT string comparisons are case insensitive.
所有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 Authentication, Authorization, and Accounting server, based on the user's authorization information. Several tunnel characteristics may be returned, and the NAS implementation may choose one. See [RFC2868] and [RFC2867] for further information.
一些NASE支持强制隧道服务，其中传入的连接数据通过封装方法传输到网络中其他地方的网关。这通常对服务用户是透明的，并且隧道特征可以由远程认证、授权和记帐服务器基于用户的授权信息来描述。可以返回多个隧道特征，NAS实现可以选择一个。有关更多信息，请参阅[RFC2868]和[RFC2867]。
The following table gives the possible flag values for the session-level AVPs and specifies whether the AVP MAY be encrypted.
下表给出了会话级AVP的可能标志值，并指定是否可以加密AVP。
+----------+
| AVP Flag |
| Rules |
|----+-----|
|MUST| MUST|
Attribute Name Section Defined | | NOT |
-----------------------------------------|----+-----|
Tunneling 4.5.1 | M | V |
Tunnel-Type 4.5.2 | M | V |
Tunnel-Medium-Type 4.5.3 | M | V |
Tunnel-Client-Endpoint 4.5.4 | M | V |
Tunnel-Server-Endpoint 4.5.5 | M | V |
Tunnel-Password 4.5.6 | M | V |
Tunnel-Private-Group-Id 4.5.7 | M | V |
Tunnel-Assignment-Id 4.5.8 | M | V |
Tunnel-Preference 4.5.9 | M | V |
Tunnel-Client-Auth-Id 4.5.10 | M | V |
Tunnel-Server-Auth-Id 4.5.11 | M | V |
-----------------------------------------|----+-----|
+----------+
| AVP Flag |
| Rules |
|----+-----|
|MUST| MUST|
Attribute Name Section Defined | | NOT |
-----------------------------------------|----+-----|
Tunneling 4.5.1 | M | V |
Tunnel-Type 4.5.2 | M | V |
Tunnel-Medium-Type 4.5.3 | M | V |
Tunnel-Client-Endpoint 4.5.4 | M | V |
Tunnel-Server-Endpoint 4.5.5 | M | V |
Tunnel-Password 4.5.6 | M | V |
Tunnel-Private-Group-Id 4.5.7 | M | V |
Tunnel-Assignment-Id 4.5.8 | M | V |
Tunnel-Preference 4.5.9 | M | V |
Tunnel-Client-Auth-Id 4.5.10 | M | V |
Tunnel-Server-Auth-Id 4.5.11 | M | V |
-----------------------------------------|----+-----|
The Tunneling AVP (AVP Code 401) is of type Grouped and contains the following AVPs, used to describe a compulsory tunnel service [RFC2868] [RFC2867]. Its data field has the following ABNF grammar:
隧道AVP（AVP代码401）属于分组类型，包含以下AVP，用于描述强制隧道服务[RFC2868][RFC2867]。其数据字段具有以下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 ACR messages.
ACR消息中还应包括隧道型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 [RADIUSAttrVals].
支持的值列在[RADIUSAttrVals]中。
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 [RFC3931]) 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[RFC3931]）创建隧道时使用的传输介质。它可以在授权请求中用作向服务器提示需要特定介质的提示，但服务器不需要在相应的响应中遵守该提示。
The supported values are listed in [RADIUSAttrVals].
支持的值列在[RADIUSAttrVals]中。
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
隧道客户端端点AVP（AVP代码66）的类型为UTF8String，包含隧道启动器端的地址。它可以在授权请求中用作提示服务器需要特定端点，但不要求服务器遵守
the hint in the corresponding response. This AVP SHOULD be included in the corresponding ACR messages, in which case it indicates the address from which the tunnel was initiated. This AVP, along with the Tunnel-Server-Endpoint (Section 4.5.5) and Session-Id AVPs ([RFC6733], Section 8.8), can be used to provide a globally unique means to identify a tunnel for accounting and auditing purposes.
相应响应中的提示。该AVP应包含在相应的ACR消息中，在这种情况下，它指示启动隧道的地址。该AVP，连同隧道服务器端点（第4.5.5节）和会话Id AVP（[RFC6733]，第8.8节），可用于提供一种全局唯一的方法来识别隧道，以便进行会计和审计。
If the value of the Tunnel-Medium-Type AVP (Section 4.5.3) is IPv4 (1), then this string is either the fully qualified domain name (FQDN) of the tunnel client machine or a "dotted-decimal" IP address. Implementations MUST support the dotted-decimal format and SHOULD support the FQDN format for IP addresses.
如果隧道介质类型AVP（第4.5.3节）的值为IPv4（1），则此字符串是隧道客户端计算机的完全限定域名（FQDN）或“点十进制”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 [RFC3516]. 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或首选或备用形式的地址文本表示形式[RFC3516]。一致性实现必须支持首选格式，并且应支持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客户端本地的配置数据，描述要使用的接口或特定于介质的客户端地址。
Note that this application handles Internationalized Domain Names (IDNs) in the same way as the Diameter Base protocol (see Appendix D of RFC 6733 for details).
请注意，此应用程序处理国际化域名（IDN）的方式与Diameter基本协议相同（有关详细信息，请参阅RFC 6733的附录D）。
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 ACR messages, in which case it indicates the address from which the tunnel was initiated. This AVP, along with the Tunnel-Client-Endpoint (Section 4.5.4) and Session-Id AVP ([RFC6733], Section 8.8), can be used to provide a globally unique means to identify a tunnel for accounting and auditing purposes.
该AVP应包含在相应的ACR消息中，在这种情况下，它指示启动隧道的地址。该AVP，连同隧道客户端端点（第4.5.4节）和会话Id AVP（[RFC6733]，第8.8节），可用于提供一种全局唯一的方法来识别隧道，以进行会计和审计。
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 [RFC3516]. Implementations MUST support the preferred form and SHOULD support both the alternate text form and the FQDN format for IPv6 addresses.
如果隧道介质类型为IPv6（2），则此字符串要么是隧道服务器计算机的FQDN，要么是首选或备用形式的地址文本表示形式[RFC3516]。实现必须支持首选格式，并且应支持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客户端本地的配置数据，描述要使用的接口或特定于介质的服务器地址。
Note that this application handles IDNs in the same way as the Diameter base protocol (see Appendix D of RFC 6733 for details).
请注意，此应用程序处理IDN的方式与Diameter base协议相同（有关详细信息，请参阅RFC 6733的附录D）。
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.
隧道密码AVP（AVP代码69）是OctetString类型，可以包含用于对远程服务器进行身份验证的密码。
The Tunnel-Password AVP SHOULD NOT be used in untrusted proxy environments without encrypting it by using end-to-end security techniques.
如果不使用端到端安全技术对隧道密码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 ACR messages that pertain to the tunneled session.
隧道专用组Id AVP（AVP代码81）为OctetString类型，包含特定隧道会话的组Id。如果隧道发起方可以预先确定由特定连接产生的组，则隧道专用组Id AVP可以包括在授权请求中。如果要将此隧道会话视为属于特定私有组，则应将其包括在授权响应中。私有组可用于将隧道会话与特定用户组相关联。例如，它可用于促进通过特定接口路由未注册的IP地址。此AVP应包含在与隧道会话相关的ACR消息中。
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 [RFC2637] and L2TP [RFC3931], 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 (for example, a LAC) whether to assign the session to a
隧道分配Id AVP（AVP代码82）是OctetString类型，用于向隧道发起方指示会话将被分配到的特定隧道。一些隧道协议，如PPTP[RFC2637]和L2TP[RFC3931]，允许在同一隧道上复用相同两个隧道端点之间的会话，并且允许给定会话使用其自己的专用隧道。此属性为Diameter提供了一种机制，用于通知隧道启动器（例如，LAC）是否将会话分配给
multiplexed tunnel or to a separate tunnel. Furthermore, it allows for sessions sharing multiplexed tunnels to be assigned to different multiplexed tunnels.
多路复用隧道或到单独的隧道。此外，它允许将共享多路复用隧道的会话分配给不同的多路复用隧道。
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 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.
特定隧道实现可将不同的特性分配给特定隧道。例如，可以为不同的隧道分配不同的QoS参数。此类隧道可用于承载单个或多个会话。因此，隧道分配Id属性允许Diameter服务器指示将特定会话分配给提供适当服务级别的隧道。预期将来随此一起定义的任何与QoS相关的Diameter隧道属性都将由隧道启动器与此属性给定的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，则应按以下方式将会话分配给隧道：
o 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.
o 如果存在此AVP，并且在具有指定Id的指定端点之间存在隧道，则应将会话分配给该隧道。
o 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.
o 如果存在此AVP，且指定端点之间不存在具有指定Id的隧道，则应为会话建立新隧道，并且指定Id应与新隧道关联。
o 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
o 如果此AVP不存在，则将会话分配给未命名的隧道。如果指定端点之间尚不存在未命名的隧道，则将建立该隧道，并将其用于此会话以及在不使用隧道分配Id属性的情况下建立的后续会话。隧道启动器不得分配
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).
未将隧道分配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 AVPs. 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.
隧道首选项AVP（AVP代码83）的类型为Unsigned32，用于在单独分组的AVP中返回多组隧道AVP时识别分配给每个隧道的相对首选项。它可以在授权请求中用作向服务器提示需要特定首选项的提示，但服务器不需要在相应的响应中遵守该提示。
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 7-bit US-ASCII 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 ACR messages pertaining to the tunneled session.
隧道客户端身份验证Id AVP（AVP代码90）为UTF8String类型，并指定隧道启动器在隧道建立的身份验证阶段使用的7位US-ASCII名称。它可以在授权请求中用作向服务器提示需要特定首选项的提示，但服务器不需要在相应的响应中遵守该提示。如果需要默认名称以外的身份验证名称，则授权响应中必须存在此AVP。此AVP应包含在与隧道会话相关的ACR消息中。
The Tunnel-Server-Auth-Id AVP (AVP Code 91) is of type UTF8String and specifies the 7-bit US-ASCII 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
隧道服务器身份验证Id AVP（AVP代码91）为UTF8String类型，并指定隧道终止程序在隧道建立的身份验证阶段使用的7位US-ASCII名称。它可以在授权请求中用作向服务器提示需要特定首选项的提示，但服务器不需要这样做
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 ACR messages pertaining to the tunneled session.
尊重相应回复中的提示。如果需要默认名称以外的身份验证名称，则授权响应中必须存在此AVP。此AVP应包含在与隧道会话相关的ACR消息中。
Applications implementing this specification use Diameter Accounting (as defined in [RFC6733]) and the AVPs in the following section. Service-specific AVP usage is defined in the tables in Section 5.
实现本规范的应用程序使用直径计算（定义见[RFC6733]）和下一节中的AVP。第5节的表格中定义了特定于服务的AVP使用。
If accounting is active, Accounting Request (ACR) messages SHOULD be sent after the completion of any Authentication or Authorization transaction and at the end of a session. The value of the Accounting-Record-Type AVP [RFC6733] indicates the type of event. All other AVPs identify the session and provide additional information relevant to the event.
如果记帐处于活动状态，则应在任何身份验证或授权事务完成后以及会话结束时发送记帐请求（ACR）消息。会计记录类型AVP[RFC6733]的值表示事件的类型。所有其他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 latter 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_记录。如果在以后的事务中发生额外的身份验证或授权，则第一次交换应生成一个START_记录，而后一次交换应生成一个临时_记录。对于给定会话，必须只有一组匹配的开始和停止记录，中间必须有任意数量的临时记录，或者一个事件记录指示会话未启动的原因。
The following table gives the possible flag values for the session-level AVPs and specifies whether the AVP MAY be encrypted.
下表给出了会话级AVP的可能标志值，并指定是否可以加密AVP。
+----------+
| AVP Flag |
| Rules |
|----+-----|
Section |MUST| MUST|
Attribute Name Defined | | NOT|
-----------------------------------------|----+-----|
Accounting-Input-Octets 4.6.1 | M | V |
Accounting-Output-Octets 4.6.2 | M | V |
Accounting-Input-Packets 4.6.3 | M | V |
Accounting-Output-Packets 4.6.4 | M | V |
Acct-Session-Time 4.6.5 | M | V |
Acct-Authentic 4.6.6 | M | V |
Accounting-Auth-Method 4.6.7 | M | V |
Acct-Delay-Time 4.6.8 | M | V |
Acct-Link-Count 4.6.9 | M | V |
Acct-Tunnel-Connection 4.6.10 | M | V |
Acct-Tunnel-Packets-Lost 4.6.11 | M | V |
-----------------------------------------|----+-----|
+----------+
| AVP Flag |
| Rules |
|----+-----|
Section |MUST| MUST|
Attribute Name Defined | | NOT|
-----------------------------------------|----+-----|
Accounting-Input-Octets 4.6.1 | M | V |
Accounting-Output-Octets 4.6.2 | M | V |
Accounting-Input-Packets 4.6.3 | M | V |
Accounting-Output-Packets 4.6.4 | M | V |
Acct-Session-Time 4.6.5 | M | V |
Acct-Authentic 4.6.6 | M | V |
Accounting-Auth-Method 4.6.7 | M | V |
Acct-Delay-Time 4.6.8 | M | V |
Acct-Link-Count 4.6.9 | M | V |
Acct-Tunnel-Connection 4.6.10 | M | V |
Acct-Tunnel-Packets-Lost 4.6.11 | M | V |
-----------------------------------------|----+-----|
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 [RFC6733] of INTERIM_RECORD or STOP_RECORD.
对于NAS使用，此AVP表示在此会话过程中从端口接收到的八位字节数。它只能出现在会计记录类型为[RFC6733]的临时记录或停止记录的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 [RADIUSAttrVals].
Acct Authentic AVP（AVP代码45）属于枚举类型，并指定用户的身份验证方式。支持的值列在[RADIUSAttrVals]中。
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 AVP is semantically equivalent, and the supported values are identical, to the Microsoft MS-Acct-Auth-Type vendor-specific RADIUS attribute [RFC2548]).
会计验证方法AVP（AVP代码406）属于枚举类型。NAS可以在记帐请求消息中包括该AVP，以指示用于认证用户的方法。（请注意，此AVP在语义上与Microsoft MS Acct Auth Type特定于供应商的RADIUS属性[RFC2548]等效，且支持的值相同）。
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 it 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 re-sent 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-Request AVPs for any session that may be part of a multilink service.
Acct Link Count AVP（AVP代码51）的类型为Unsigned32，表示生成记帐记录时给定多链路会话中处于活动状态（当前或关闭）的链路总数。该AVP可以包含在多链路服务的任何会话的记帐请求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-Request AVPs received with Accounting-Record-Type = STOP_RECORD and with the same Acct-Multi-Session-Id and unique Session-Id AVPs equals the largest value of Acct-Link-Count seen in those Accounting-Request AVPs, all STOP_RECORD Accounting-Request AVPs for that multilink service have been received.
Acct Link Count AVP可用于使记帐服务器更容易了解其何时拥有给定多链路服务的所有记录。当接收到的记帐记录类型为STOP_记录且具有相同帐户多会话Id和唯一会话Id AVP的记帐请求AVP数等于这些记帐请求AVP中看到的最大帐户链接计数值时，该多链路服务的所有STOP_记录记帐请求AVP均已接收。
The following example, showing eight Accounting-Request AVPs, 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 AVPs.
下面的示例显示了八个记帐请求AVP，说明了如何使用Acct Link Count AVP。在下表中，仅显示了相关的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 (Section 4.5.4) and Tunnel-Server-Endpoint (Section 4.5.5) AVPs, may be used to provide a means to uniquely identify a tunnel session for auditing purposes.
Acct隧道连接AVP（AVP代码68）的类型为OctetString，包含分配给隧道会话的标识符。该AVP，连同隧道客户端端点（第4.5.4节）和隧道服务器端点（第4.5.5节）AVP，可用于提供唯一标识隧道会话的方法，用于审计目的。
The format of the identifier in this AVP depends upon the value of the Tunnel-Type AVP (Section 4.5.2). 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的值（第4.5.2节）。例如，为了完全识别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 tunnel.
Acct Tunnel Packets Lost AVP（AVP代码86）的类型为Unsigned32，包含给定隧道上丢失的数据包数。
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. Messages and AVPs defined in the Diameter Base protocol [RFC6733] 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消息中。本文档中未描述Diameter基本协议[RFC6733]中定义的消息和AVP。请注意，此表中未显示只能出现在分组AVP中的AVP。
The tables use the following symbols:
这些表使用以下符号：
0 The AVP MUST NOT be present in the message.
0消息中不得出现AVP。
0+ Zero or more instances of the AVP MAY be present in the message.
消息中可能存在0+零个或多个AVP实例。
0-1 Zero or one instance of the AVP MAY be present in the message.
0-1消息中可能存在零个或一个AVP实例。
1 Exactly one instance of the AVP MUST be present in the message.
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 [RFC6733] and [RFC2866].
本节中的表格用于显示本文档中定义的哪些AVP将出现并用于NAS应用程序记帐消息。这些AVP在本文件以及[RFC6733]和[RFC2866]中均有定义。
The table in this section is used when the Service-Type AVP (Section 4.4.1) specifies Framed Access.
当服务类型AVP（第4.4.1节）指定框架访问时，使用本节中的表格。
+-----------+
| 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 |
---------------------------------------|-----+-----+
+-----------+
| 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 |
---------------------------------------|-----+-----+
The table in this section is used when the Service-Type AVP (Section 4.4.1) specifies Non-Framed Access.
当服务类型AVP（第4.4.1节）指定非帧访问时，使用本节中的表格。
+-----------+
| 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 |
---------------------------------------|-----+-----+
+-----------+
| 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 |
---------------------------------------|-----+-----+
A number of the AVPs in this RFC use the UTF8String type specified in the Diameter Base protocol [RFC6733]. Implementation differences in Unicode input processing may result in the same Unicode input characters generating different UTF-8 strings that fail to match when compared for equality. This may result in interoperability problems between a network access server and a Diameter server when a UTF-8 string entered locally is compared with one received via Diameter. Many of the uses of UTF8String in this RFC are limited to the 7-bit US-ASCII-compatible subset of UTF-8, where this class of Unicode string comparison problems does not arise.
此RFC中的许多AVP使用Diameter Base协议[RFC6733]中指定的UTF8String类型。Unicode输入处理中的实现差异可能会导致相同的Unicode输入字符生成不同的UTF-8字符串，这些字符串在进行相等性比较时无法匹配。当本地输入的UTF-8字符串与通过Diameter接收的UTF-8字符串进行比较时，这可能会导致网络访问服务器和Diameter服务器之间的互操作性问题。此RFC中UTF8String的许多使用仅限于UTF-8的7位US ASCII兼容子集，其中不会出现此类Unicode字符串比较问题。
Careful preparation of Unicode strings can increase the likelihood that string comparison will work in ways that make sense for typical users throughout the world; [RFC3454] is an example a framework for such Unicode string preparation. The Diameter application specified in this RFC has been deployed with use of Unicode in accordance with [RFC4005], which does not require any Unicode string preparation. As a result, additional requirements for Unicode string preparation in this RFC would not be backwards compatible with existing usage.
仔细准备Unicode字符串可以增加字符串比较工作的可能性，使其对全世界的典型用户都有意义；[RFC3454]是这种Unicode字符串准备框架的一个示例。本RFC中指定的Diameter应用程序已根据[RFC4005]使用Unicode进行部署，不需要任何Unicode字符串准备。因此，此RFC中Unicode字符串准备的附加要求将与现有用法不向后兼容。
The Diameter server and the network access servers that it serves can be assumed to be under common administrative control, and all of the UTF-8 strings involved are part of the configuration of these servers. Therefore, administrative interfaces for implementations of this RFC:
可以假设Diameter服务器及其服务的网络访问服务器处于公共管理控制之下，所有涉及的UTF-8字符串都是这些服务器配置的一部分。因此，本RFC实施的管理接口：
a. SHOULD accept direct UTF-8 input of all configuration strings for AVPs that allow Unicode characters beyond the 7-bit US-ASCII-compatible subset of Unicode (in addition to any provisions for accepting Unicode characters for processing into UTF-8), and
a. 应接受AVP所有配置字符串的直接UTF-8输入，这些AVP允许Unicode字符超出Unicode的7位US ASCII兼容子集（除了接受Unicode字符以处理为UTF-8的任何规定），以及
b. SHOULD make all such configuration strings available as UTF-8 strings.
b. 应将所有此类配置字符串作为UTF-8字符串提供。
This functionality enables an administrator who encounters Unicode string comparison problems to copy one instance of aproblematic UTF-8 string from one server to the other, after which the two (now identical) copies should compare as expected.
此功能使遇到Unicode字符串比较问题的管理员能够将有问题的UTF-8字符串的一个实例从一台服务器复制到另一台服务器，然后两个（现在相同）副本应按预期进行比较。
Several of the namespaces used in this document are managed by the
Internet Assigned Numbers Authority [IANA], including the AVP Codes
[AVP-Codes], AVP Specific Values [AVP-Vals], Application IDs
[App-Ids], Command Codes [Command-Codes], and RADIUS Attribute Values
[RADIUSAttrVals].
Several of the namespaces used in this document are managed by the
Internet Assigned Numbers Authority [IANA], including the AVP Codes
[AVP-Codes], AVP Specific Values [AVP-Vals], Application IDs
[App-Ids], Command Codes [Command-Codes], and RADIUS Attribute Values
[RADIUSAttrVals].
For the current values allocated, and the policies governing allocation in those namespaces, please see the above-referenced registries.
有关分配的当前值以及管理这些名称空间中的分配的策略，请参阅上面引用的注册表。
This document describes the extension of Diameter for the NAS application. Security considerations regarding the Diameter protocol itself are discussed in [RFC6733]. Use of this application of Diameter MUST take into consideration the security issues and requirements of the Base protocol.
本文档介绍NAS应用程序的直径扩展。[RFC6733]中讨论了有关Diameter协议本身的安全注意事项。使用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.
本文档还描述了如何在Diameter协议中承载CHAP，这是RADIUS向后兼容性所必需的。在RADIUS环境中使用的CHAP协议有助于身份验证重放攻击。
The use of the EAP authentication protocols [RFC4072] can offer better security, given a method suitable for the circumstances.
使用EAP身份验证协议[RFC4072]可以提供更好的安全性，因为它提供了一种适合这种情况的方法。
Depending on the value of 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 provided by RADIUS (Section 5.6 of [RFC2865]) in that no access decision is requested. As a result, a new session cannot be started as a result of a response to an authorization-only request without introducing a significant security vulnerability.
根据身份验证请求类型AVP的值，Diameter协议只允许不包含来自客户端的身份验证信息的授权请求。此功能超出RADIUS（RFC2865）第5.6节提供的呼叫检查功能，因为不需要访问决策。因此，如果响应仅授权请求，则无法启动新会话，而不会引入严重的安全漏洞。
Diameter AVPs often contain security-sensitive data; for example, user passwords and location data, network addresses and cryptographic keys. With the exception of the Configuration-Token (Section 4.4.8), QoS-Filter-Rule (Section 4.4.9), and Tunneling (Section 4.5.1) AVPs, all of the AVPs defined in this document are considered to be security-sensitive.
Diameter AVP通常包含安全敏感数据；例如，用户密码和位置数据、网络地址和加密密钥。除配置令牌（第4.4.8节）、QoS过滤规则（第4.4.9节）和隧道（第4.5.1节）AVP外，本文件中定义的所有AVP均视为安全敏感型。
Diameter messages containing any AVPs considered to be security-sensitive MUST only be sent protected via mutually authenticated TLS or IPsec. In addition, those messages MUST NOT be sent via intermediate nodes unless there is end-to-end security between the originator and recipient or the originator has locally trusted configuration that indicates that end-to-end security is not needed. For example, end-to-end security may not be required in the case where an intermediary node is known to be operated as part of the same administrative domain as the endpoints so that an ability to successfully compromise the intermediary would imply a high probability of being able to compromise the endpoints as well. Note that no end-to-end security mechanism is specified in this document.
包含任何视为安全敏感的AVP的Diameter消息只能通过相互验证的TLS或IPsec进行发送保护。此外，这些消息不得通过中间节点发送，除非发端人和收件人之间存在端到端安全性，或者发端人具有本地受信任的配置，表明不需要端到端安全性。例如，在已知中间节点作为与端点相同的管理域的一部分操作的情况下，可能不需要端到端安全性，因此成功地危害中间节点的能力将意味着也能够危害端点的高概率。请注意，本文档中未指定端到端安全机制。
[ANITypes] NANPA Number Resource Info, "ANI Assignments", <http://www.nanpa.com/number_resource_info/ ani_ii_assignments.html>.
[ANITypes]NANPA编号资源信息，“ANI分配”<http://www.nanpa.com/number_resource_info/ ani_ii_assignments.html>。
[RFC1994] Simpson, W., "PPP Challenge Handshake Authentication Protocol (CHAP)", RFC 1994, August 1996.
[RFC1994]辛普森，W.，“PPP挑战握手认证协议（CHAP）”，RFC 1994，1996年8月。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, "Remote Authentication Dial In User Service (RADIUS)", RFC 2865, June 2000.
[RFC2865]Rigney，C.，Willens，S.，Rubens，A.，和W.Simpson，“远程认证拨入用户服务（RADIUS）”，RFC 28652000年6月。
[RFC3162] Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6", RFC 3162, August 2001.
[RFC3162]Aboba，B.，Zorn，G.和D.Mitton，“RADIUS和IPv6”，RFC 3162，2001年8月。
[RFC3516] Nerenberg, L., "IMAP4 Binary Content Extension", RFC 3516, April 2003.
[RFC3516]Nerenberg，L.，“IMAP4二进制内容扩展”，RFC3516，2003年4月。
[RFC3539] Aboba, B. and J. Wood, "Authentication, Authorization and Accounting (AAA) Transport Profile", RFC 3539, June 2003.
[RFC3539]Aboba，B.和J.Wood，“认证、授权和会计（AAA）传输概要”，RFC 3539，2003年6月。
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC5234]Crocker，D.和P.Overell，“语法规范的扩充BNF:ABNF”，STD 68，RFC 5234，2008年1月。
[RFC5777] Korhonen, J., Tschofenig, H., Arumaithurai, M., Jones, M., and A. Lior, "Traffic Classification and Quality of Service (QoS) Attributes for Diameter", RFC 5777, February 2010.
[RFC5777]Korhonen，J.，Tschofenig，H.，Arumaithurai，M.，Jones，M.，和A.Lior，“直径的流量分类和服务质量（QoS）属性”，RFC 57772010年2月。
[RFC6733] Fajardo, V., Arkko, J., Loughney, J., and G. Zorn, "Diameter Base Protocol", RFC 6733, October 2012.
[RFC6733]Fajardo，V.，Arkko，J.，Loughney，J.，和G.Zorn，“直径基准协议”，RFC 67332012年10月。
[ARAP] Apple Computer, "Apple Remote Access Protocol (ARAP) Version 2.0 External Reference Specification", R0612LL/B , September 1994.
[ARAP]苹果计算机，“苹果远程访问协议（ARAP）2.0版外部参考规范”，R0612LL/B，1994年9月。
[AVP-Codes] IANA, "AVP Codes", <http://www.iana.org/assignments/aaa-parameters/>.
[AVP代码]IANA，“AVP代码”<http://www.iana.org/assignments/aaa-parameters/>.
[AVP-Vals] IANA, "AVP Specific Values", <http://www.iana.org/assignments/aaa-parameters/>.
[AVP VAL]IANA，“AVP特定值”<http://www.iana.org/assignments/aaa-parameters/>.
[App-Ids] IANA, "Application IDs", <http://www.iana.org/assignments/aaa-parameters/>.
[应用程序ID]IANA，“应用程序ID”<http://www.iana.org/assignments/aaa-parameters/>.
[AppleTalk] Sidhu, G., Andrews, R., and A. Oppenheimer, "Inside AppleTalk", Second Edition Apple Computer, 1990.
[AppleTalk]Sidhu，G.，Andrews，R.，和A.Oppenheimer，“AppleTalk内部”，第二版苹果电脑，1990年。
[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月。
[Command-Codes] IANA, "Command Codes", <http://www.iana.org/assignments/aaa-parameters/>.
[命令代码]IANA，“命令代码”<http://www.iana.org/assignments/aaa-parameters/>.
[IANA] IANA, "Internet Assigned Numbers Authority", <http://www.iana.org/>.
[IANA]IANA，“互联网分配号码管理局”<http://www.iana.org/>.
[IPX] Novell, Inc., "NetWare System Technical Interface Overview", #883-000780-001, June 1989.
[IPX]Novell，Inc.，“NetWare系统技术接口概述”，#883-000780-001，1989年6月。
[ISO.8859-1.1987] International Organization for Standardization, "Information technology - 8-bit single byte coded graphic - character sets - Part 1: Latin alphabet No. 1, JTC1/ SC2", ISO Standard 8859-1, 1987.
[ISO.8859-1.1987]国际标准化组织，“信息技术-8位单字节编码图形-字符集-第1部分：第1号拉丁字母JTC1/SC2”，ISO标准8859-11987。
[LAT] Digital Equipment Corp., "Local Area Transport (LAT) Specification V5.0", AA-NL26A-TE, June 1989.
[LAT]数字设备公司，“局域网传输（LAT）规范V5.0”，AA-NL26A-TE，1989年6月。
[RADIUSAttrVals] IANA, "Radius Attribute Values", <http://www.iana.org/assignments/radius-types/>.
[RADIUSATRVALS]IANA，“半径属性值”<http://www.iana.org/assignments/radius-types/>.
[RFC1334] Lloyd, B. and W. Simpson, "PPP Authentication Protocols", RFC 1334, October 1992.
[RFC1334]Lloyd，B.和W.Simpson，“PPP认证协议”，RFC 13341992年10月。
[RFC1661] Simpson, W., "The Point-to-Point Protocol (PPP)", STD 51, RFC 1661, July 1994.
[RFC1661]辛普森，W.“点对点协议（PPP）”，标准51，RFC1661，1994年7月。
[RFC1990] Sklower, K., Lloyd, B., McGregor, G., Carr, D., and T. Coradetti, "The PPP Multilink Protocol (MP)", RFC 1990, August 1996.
[RFC1990]K.Sklower、Lloyd、B.McGregor、G.Carr、D.和T.Coradetti，“PPP多链路协议（MP）”，RFC 1990，1996年8月。
[RFC2474] 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.
[RFC2474]Nichols，K.，Blake，S.，Baker，F.，和D.Black，“IPv4和IPv6头中区分服务字段（DS字段）的定义”，RFC 2474，1998年12月。
[RFC2548] Zorn, G., "Microsoft Vendor-specific RADIUS Attributes", RFC 2548, March 1999.
[RFC2548]Zorn，G.，“微软特定于供应商的半径属性”，RFC 2548，1999年3月。
[RFC2597] Heinanen, J., Baker, F., Weiss, W., and J. Wroclawski, "Assured Forwarding PHB Group", RFC 2597, June 1999.
[RFC2597]Heinanen，J.，Baker，F.，Weiss，W.，和J.Wroclawski，“保付PHB集团”，RFC 25971999年6月。
[RFC2637] Hamzeh, K., Pall, G., Verthein, W., Taarud, J., Little, W., and G. Zorn, "Point-to-Point Tunneling Protocol", RFC 2637, July 1999.
[RFC2637]Hamzeh，K.，Pall，G.，Verthein，W.，Taarud，J.，Little，W.，和G.Zorn，“点对点隧道协议”，RFC 2637，1999年7月。
[RFC2866] Rigney, C., "RADIUS Accounting", RFC 2866, June 2000.
[RFC2866]Rigney，C.，“半径会计”，RFC 28662000年6月。
[RFC2867] Zorn, G., Aboba, B., and D. Mitton, "RADIUS Accounting Modifications for Tunnel Protocol Support", RFC 2867, June 2000.
[RFC2867]Zorn，G.，Aboba，B.和D.Mitton，“隧道协议支持的半径计算修改”，RFC 28672000年6月。
[RFC2868] Zorn, G., Leifer, D., Rubens, A., Shriver, J., Holdrege, M., and I. Goyret, "RADIUS Attributes for Tunnel Protocol Support", RFC 2868, June 2000.
[RFC2868]Zorn，G.，Leifer，D.，Rubens，A.，Shriver，J.，Holdrege，M.，和I.Goyret，“隧道协议支持的半径属性”，RFC 28682000年6月。
[RFC2869] Rigney, C., Willats, W., and P. Calhoun, "RADIUS Extensions", RFC 2869, June 2000.
[RFC2869]Rigney，C.，Willats，W.，和P.Calhoun，“半径延伸”，RFC 2869，2000年6月。
[RFC2881] Mitton, D. and M. Beadles, "Network Access Server Requirements Next Generation (NASREQNG) NAS Model", RFC 2881, July 2000.
[RFC2881]Mitton，D.和M.Beadles，“网络访问服务器要求下一代（NASREQNG）NAS模型”，RFC 28812000年7月。
[RFC2989] Aboba, B., Calhoun, P., Glass, S., Hiller, T., McCann, P., Shiino, H., Walsh, P., Zorn, G., Dommety, G., Perkins, C., Patil, B., Mitton, D., Manning, S., Beadles, M., Chen, X., Sivalingham, S., Hameed, A., Munson, M., Jacobs, S., Lim, B., Hirschman, B., Hsu, R., Koo, H., Lipford, M., Campbell, E., Xu, Y., Baba, S., and E. Jaques, "Criteria for Evaluating AAA Protocols for Network Access", RFC 2989, November 2000.
[RFC2989]Aboba，B.，Calhoun，P.，Glass，S.，Hiller，T.，McCann，P.，Shiino，H.，Walsh，P.，Zorn，G.，Dommety，G.，Perkins，C.，Patil，B.，Mitton，D.，Manning，S.，Beadles，M.，Chen，X.，Sivalingham，S.，Hameed，A.，Munson，M.，Jacobs，S.，Lim，B.，Hirschman，B.，Hsu，R.，Koo，H.，Lipford，M.，Campbell，E.，Xu，Y.，Y.，Baba，S.，E.Jaques，“评估网络接入AAA协议的标准”，RFC 2989，2000年11月。
[RFC3169] Beadles, M. and D. Mitton, "Criteria for Evaluating Network Access Server Protocols", RFC 3169, September 2001.
[RFC3169]Beadles，M.和D.Mitton，“评估网络访问服务器协议的标准”，RFC 3169，2001年9月。
[RFC3246] Davie, B., Charny, A., Bennet, J., 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.
[RFC3246]Davie，B.，Charny，A.，Bennet，J.，Benson，K.，Le Boudec，J.，Courtney，W.，Davari，S.，Firoiu，V.，和D.Stiliadis，“快速转发PHB（每跳行为）”，RFC 32462002年3月。
[RFC3454] Hoffman, P. and M. Blanchet, "Preparation of Internationalized Strings ("stringprep")", RFC 3454, December 2002.
[RFC3454]Hoffman，P.和M.Blanchet，“国际化弦的准备（“stringprep”）”，RFC 3454，2002年12月。
[RFC3580] 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.
[RFC3580]Congdon，P.，Aboba，B.，Smith，A.，Zorn，G.，和J.Roese，“IEEE 802.1X远程认证拨入用户服务（RADIUS）使用指南”，RFC 35802003年9月。
[RFC3931] Lau, J., Townsley, M., and I. Goyret, "Layer Two Tunneling Protocol - Version 3 (L2TPv3)", RFC 3931, March 2005.
[RFC3931]Lau，J.，Townsley，M.，和I.Goyret，“第二层隧道协议-版本3（L2TPv3）”，RFC 39312005年3月。
[RFC4005] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, "Diameter Network Access Server Application", RFC 4005, August 2005.
[RFC4005]Calhoun，P.，Zorn，G.，Spence，D.，和D.Mitton，“Diameter网络访问服务器应用”，RFC 4005，2005年8月。
[RFC4072] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible Authentication Protocol (EAP) Application", RFC 4072, August 2005.
[RFC4072]Eronen，P.，Hiller，T.，和G.Zorn，“直径可扩展认证协议（EAP）应用”，RFC 4072，2005年8月。
[RFC4301] Kent, S. and K. Seo, "Security Architecture for the Internet Protocol", RFC 4301, December 2005.
[RFC4301]Kent，S.和K.Seo，“互联网协议的安全架构”，RFC 43012005年12月。
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security (TLS) Protocol Version 1.2", RFC 5246, August 2008.
[RFC5246]Dierks，T.和E.Rescorla，“传输层安全（TLS）协议版本1.2”，RFC 5246，2008年8月。
The vast majority of the text in this document was taken directly from RFC 4005; the editor owes a debt of gratitude to the authors thereof (especially Dave Mitton, who somehow managed to make nroff paginate the AVP Occurance Tables correctly!).
本文件中的绝大多数文本直接取自RFC 4005；编辑应该感谢这本书的作者（尤其是戴夫·米顿，他设法让nroff正确地对AVP发生率表进行分页！）。
Thanks (in no particular order) to Jai-Jin Lim, Liu Hans, Sebastien Decugis, Jouni Korhonen, Mark Jones, Hannes Tschofenig, Dave Crocker, David Black, Barry Leiba, Peter Saint-Andre, Stefan Winter, and Lionel Morand for their useful reviews and helpful comments.
感谢（无特殊顺序）Jai Jin Lim、Liu Hans、Sebastien Decugis、Jouni Korhonen、Mark Jones、Hannes Tschofenig、Dave Crocker、David Black、Barry Leiba、Peter Saint Andre、Stefan Winter和Lionel Morand的评论和评论。
The authors would like to thank Carl Rigney, Allan C. Rubens, William Allen Simpson, and Steve Willens for their work on the original RADIUS protocol, from which many of the concepts in this specification were derived. Thanks, also, to Carl Rigney for [RFC2866] and [RFC2869]; Ward Willats for [RFC2869]; Glen Zorn, Bernard Aboba, and Dave Mitton for [RFC2867] and [RFC3162]; and Dory Leifer, John Shriver, Matt Holdrege, Allan Rubens, Glen Zorn, and Ignacio Goyret for their work on [RFC2868]. This document stole text and concepts from both [RFC2868] and [RFC2869]. Thanks go to Carl Williams for providing IPv6-specific text.
作者要感谢Carl Rigney、Allan C.Rubens、William Allen Simpson和Steve Willens为原始RADIUS协议所做的工作，本规范中的许多概念都是从原始RADIUS协议中衍生出来的。同时感谢Carl Rigney的[RFC2866]和[RFC2869]；[RFC2869]的Ward Willats；[RFC2867]和[RFC3162]的Glen Zorn、Bernard Aboba和Dave Mitton；多莉·莱弗、约翰·施莱弗、马特·霍尔德雷格、艾伦·鲁本斯、格伦·佐恩和伊格纳西奥·戈雷特在[RFC2868]上的工作。本文档从[RFC2868]和[RFC2869]中窃取了文本和概念。感谢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，因为在本文档中投入的大部分精力都是在他任职期间完成的。
Author's Address
作者地址
Glen Zorn (editor) Network Zen 227/358 Thanon Sanphawut Bang Na, Bangkok 10260 Thailand
格伦·佐恩（编辑）网络禅227/358泰国曼谷Thnon Sanphawut Bang Na 10260
Phone: +66 (0)8-1000-4155
EMail: glenzorn@gmail.com
Phone: +66 (0)8-1000-4155
EMail: glenzorn@gmail.com