Internet Engineering Task Force (IETF) S. Ooghe
Request for Comments: 5851 Alcatel-Lucent
Category: Informational N. Voigt
ISSN: 2070-1721 Nokia Siemens Networks
M. Platnic
ECI Telecom
T. Haag
Deutsche Telekom
S. Wadhwa
Juniper Networks
May 2010
Internet Engineering Task Force (IETF) S. Ooghe
Request for Comments: 5851 Alcatel-Lucent
Category: Informational N. Voigt
ISSN: 2070-1721 Nokia Siemens Networks
M. Platnic
ECI Telecom
T. Haag
Deutsche Telekom
S. Wadhwa
Juniper Networks
May 2010
Framework and Requirements for an Access Node Control Mechanism in Broadband Multi-Service Networks
宽带多业务网络中接入节点控制机制的框架和要求
Abstract
摘要
The purpose of this document is to define a framework for an Access Node Control Mechanism between a Network Access Server (NAS) and an Access Node (e.g., a Digital Subscriber Line Access Multiplexer (DSLAM)) in a multi-service reference architecture in order to perform operations related to service, quality of service, and subscribers. The Access Node Control Mechanism will ensure that the transmission of the information does not need to go through distinct element managers but rather uses a direct device-device communication. This allows for performing access-link-related operations within those network elements, while avoiding impact on the existing Operational Support Systems.
本文档的目的是定义多业务参考体系结构中网络接入服务器（NAS）和接入节点（例如，数字用户线接入多路复用器（DSLAM））之间的接入节点控制机制的框架，以便执行与服务、服务质量和用户相关的操作。接入节点控制机制将确保信息的传输不需要通过不同的元素管理器，而是使用直接的设备通信。这允许在这些网元内执行接入链路相关操作，同时避免对现有操作支持系统造成影响。
This document first identifies a number of use cases for which the Access Node Control Mechanism may be appropriate. It then presents the requirements for the Access Node Control Protocol (ANCP) that must be taken into account during protocol design. Finally, it describes requirements for the network elements that need to support ANCP and the described use cases. These requirements should be seen as guidelines rather than as absolute requirements. RFC 2119 therefore does not apply to the nodal requirements.
本文档首先确定了访问节点控制机制可能适用的一些用例。然后介绍了在协议设计过程中必须考虑的访问节点控制协议（ANCP）的要求。最后，它描述了需要支持ANCP的网络元素的需求和所描述的用例。这些要求应被视为指导原则，而不是绝对要求。因此，RFC 2119不适用于节点要求。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
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). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非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/rfc5851.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc5851.
Copyright Notice
版权公告
Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2010 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许可证中所述的无担保。
This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.
本文件可能包含2008年11月10日之前发布或公开的IETF文件或IETF贡献中的材料。控制某些材料版权的人员可能未授予IETF信托允许在IETF标准流程之外修改此类材料的权利。在未从控制此类材料版权的人员处获得充分许可的情况下，不得在IETF标准流程之外修改本文件，也不得在IETF标准流程之外创建其衍生作品，除了将其格式化以RFC形式发布或将其翻译成英语以外的其他语言。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Requirements Notation . . . . . . . . . . . . . . . . . . 5
1.2. Definitions . . . . . . . . . . . . . . . . . . . . . . . 5
2. General Architecture Aspects . . . . . . . . . . . . . . . . . 7
2.1. Concept of an Access Node Control Mechanism . . . . . . . 7
2.2. Reference Architecture . . . . . . . . . . . . . . . . . . 8
2.2.1. Home Gateway . . . . . . . . . . . . . . . . . . . . . 9
2.2.2. Access Loop . . . . . . . . . . . . . . . . . . . . . 9
2.2.3. Access Node . . . . . . . . . . . . . . . . . . . . . 9
2.2.4. Access Node Uplink . . . . . . . . . . . . . . . . . . 10
2.2.5. Aggregation Network . . . . . . . . . . . . . . . . . 10
2.2.6. Network Access Server . . . . . . . . . . . . . . . . 10
2.2.7. Regional Network . . . . . . . . . . . . . . . . . . . 10
2.3. Prioritizing Access Node Control Traffic . . . . . . . . . 11
2.4. Interaction with Management Systems . . . . . . . . . . . 12
2.5. Circuit Addressing Scheme . . . . . . . . . . . . . . . . 12
3. Use Cases for Access Node Control Mechanism . . . . . . . . . 13
3.1. Access Topology Discovery . . . . . . . . . . . . . . . . 13
3.2. Access-Loop Configuration . . . . . . . . . . . . . . . . 15
3.3. Remote Connectivity Test . . . . . . . . . . . . . . . . . 16
3.4. Multicast . . . . . . . . . . . . . . . . . . . . . . . . 17
3.4.1. Multicast Conditional Access . . . . . . . . . . . . . 18
3.4.2. Multicast Admission Control . . . . . . . . . . . . . 21
3.4.3. Multicast Accounting and Reporting . . . . . . . . . . 26
3.4.4. Spontaneous Admission Response . . . . . . . . . . . . 27
4. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.1. ANCP Functional Requirements . . . . . . . . . . . . . . . 28
4.2. ANCP Multicast Requirements . . . . . . . . . . . . . . . 29
4.3. Protocol Design Requirements . . . . . . . . . . . . . . . 30
4.4. Access Node Control Adjacency Requirements . . . . . . . . 31
4.5. ANCP Transport Requirements . . . . . . . . . . . . . . . 31
4.6. Access Node Requirements . . . . . . . . . . . . . . . . . 32
4.6.1. General Architecture . . . . . . . . . . . . . . . . . 32
4.6.2. Control Channel Attributes . . . . . . . . . . . . . . 33
4.6.3. Capability Negotiation Failure . . . . . . . . . . . . 33
4.6.4. Adjacency Status Reporting . . . . . . . . . . . . . . 33
4.6.5. Identification . . . . . . . . . . . . . . . . . . . . 34
4.6.6. Multicast . . . . . . . . . . . . . . . . . . . . . . 34
4.6.7. Message Handling . . . . . . . . . . . . . . . . . . . 36
4.6.8. Parameter Control . . . . . . . . . . . . . . . . . . 37
4.7. Network Access Server Requirements . . . . . . . . . . . . 37
4.7.1. General Architecture . . . . . . . . . . . . . . . . . 37
4.7.2. Control Channel Attributes . . . . . . . . . . . . . . 39
4.7.3. Capability Negotiation Failure . . . . . . . . . . . . 39
4.7.4. Adjacency Status Reporting . . . . . . . . . . . . . . 40
4.7.5. Identification . . . . . . . . . . . . . . . . . . . . 40
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Requirements Notation . . . . . . . . . . . . . . . . . . 5
1.2. Definitions . . . . . . . . . . . . . . . . . . . . . . . 5
2. General Architecture Aspects . . . . . . . . . . . . . . . . . 7
2.1. Concept of an Access Node Control Mechanism . . . . . . . 7
2.2. Reference Architecture . . . . . . . . . . . . . . . . . . 8
2.2.1. Home Gateway . . . . . . . . . . . . . . . . . . . . . 9
2.2.2. Access Loop . . . . . . . . . . . . . . . . . . . . . 9
2.2.3. Access Node . . . . . . . . . . . . . . . . . . . . . 9
2.2.4. Access Node Uplink . . . . . . . . . . . . . . . . . . 10
2.2.5. Aggregation Network . . . . . . . . . . . . . . . . . 10
2.2.6. Network Access Server . . . . . . . . . . . . . . . . 10
2.2.7. Regional Network . . . . . . . . . . . . . . . . . . . 10
2.3. Prioritizing Access Node Control Traffic . . . . . . . . . 11
2.4. Interaction with Management Systems . . . . . . . . . . . 12
2.5. Circuit Addressing Scheme . . . . . . . . . . . . . . . . 12
3. Use Cases for Access Node Control Mechanism . . . . . . . . . 13
3.1. Access Topology Discovery . . . . . . . . . . . . . . . . 13
3.2. Access-Loop Configuration . . . . . . . . . . . . . . . . 15
3.3. Remote Connectivity Test . . . . . . . . . . . . . . . . . 16
3.4. Multicast . . . . . . . . . . . . . . . . . . . . . . . . 17
3.4.1. Multicast Conditional Access . . . . . . . . . . . . . 18
3.4.2. Multicast Admission Control . . . . . . . . . . . . . 21
3.4.3. Multicast Accounting and Reporting . . . . . . . . . . 26
3.4.4. Spontaneous Admission Response . . . . . . . . . . . . 27
4. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.1. ANCP Functional Requirements . . . . . . . . . . . . . . . 28
4.2. ANCP Multicast Requirements . . . . . . . . . . . . . . . 29
4.3. Protocol Design Requirements . . . . . . . . . . . . . . . 30
4.4. Access Node Control Adjacency Requirements . . . . . . . . 31
4.5. ANCP Transport Requirements . . . . . . . . . . . . . . . 31
4.6. Access Node Requirements . . . . . . . . . . . . . . . . . 32
4.6.1. General Architecture . . . . . . . . . . . . . . . . . 32
4.6.2. Control Channel Attributes . . . . . . . . . . . . . . 33
4.6.3. Capability Negotiation Failure . . . . . . . . . . . . 33
4.6.4. Adjacency Status Reporting . . . . . . . . . . . . . . 33
4.6.5. Identification . . . . . . . . . . . . . . . . . . . . 34
4.6.6. Multicast . . . . . . . . . . . . . . . . . . . . . . 34
4.6.7. Message Handling . . . . . . . . . . . . . . . . . . . 36
4.6.8. Parameter Control . . . . . . . . . . . . . . . . . . 37
4.7. Network Access Server Requirements . . . . . . . . . . . . 37
4.7.1. General Architecture . . . . . . . . . . . . . . . . . 37
4.7.2. Control Channel Attributes . . . . . . . . . . . . . . 39
4.7.3. Capability Negotiation Failure . . . . . . . . . . . . 39
4.7.4. Adjacency Status Reporting . . . . . . . . . . . . . . 40
4.7.5. Identification . . . . . . . . . . . . . . . . . . . . 40
4.7.6. Multicast . . . . . . . . . . . . . . . . . . . . . . 40
4.7.7. Message Handling . . . . . . . . . . . . . . . . . . . 42
4.7.8. Wholesale Model . . . . . . . . . . . . . . . . . . . 42
5. Management-Related Requirements . . . . . . . . . . . . . . . 43
6. Security Considerations . . . . . . . . . . . . . . . . . . . 44
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 44
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 45
8.1. Normative References . . . . . . . . . . . . . . . . . . . 45
8.2. Informative References . . . . . . . . . . . . . . . . . . 45
4.7.6. Multicast . . . . . . . . . . . . . . . . . . . . . . 40
4.7.7. Message Handling . . . . . . . . . . . . . . . . . . . 42
4.7.8. Wholesale Model . . . . . . . . . . . . . . . . . . . 42
5. Management-Related Requirements . . . . . . . . . . . . . . . 43
6. Security Considerations . . . . . . . . . . . . . . . . . . . 44
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 44
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 45
8.1. Normative References . . . . . . . . . . . . . . . . . . . 45
8.2. Informative References . . . . . . . . . . . . . . . . . . 45
Digital Subscriber Line (DSL) technology is widely deployed for Broadband Access for Next Generation Networks. Several documents like Broadband Forum TR-058 [TR-058], Broadband Forum TR-059 [TR-059], and Broadband Forum TR-101 [TR-101] describe possible architectures for these access networks. The scope of these specifications consists of the delivery of voice, video, and data services. The framework defined by this document is targeted at DSL-based access (either by means of ATM/DSL or as Ethernet/DSL). The framework shall be open to other access technologies, such as Passive Optical Networks using DSL technology at the Optical Network Unit (ONU), or wireless technologies like IEEE 802.16. Several use cases such as Access Topology Discovery, Remote Connectivity Test, and Multicast may be applied to these access technologies, but the details of this are outside the scope of this document.
数字用户线（DSL）技术广泛应用于下一代网络的宽带接入。宽带论坛TR-058[TR-058]、宽带论坛TR-059[TR-059]和宽带论坛TR-101[TR-101]等文件描述了这些接入网络的可能架构。这些规范的范围包括语音、视频和数据服务的交付。本文档定义的框架针对基于DSL的访问（通过ATM/DSL或以太网/DSL）。该框架应向其他接入技术开放，如在光网络单元（ONU）使用DSL技术的无源光网络，或IEEE 802.16等无线技术。访问拓扑发现、远程连接测试和多播等几个用例可应用于这些访问技术，但其细节不在本文档的范围内。
Traditional architectures require Permanent Virtual Circuit(s) per subscriber. Such a virtual circuit is configured on layer 2 and terminated at the first layer 3 device (e.g., Broadband Remote Access Server (BRAS)). Beside the data plane, the models define the architectures for element, network, and service management. Interworking at the management plane is not always possible because of the organizational boundaries between departments operating the local loop, departments operating the ATM network, and departments operating the IP network. Besides, management networks are usually not designed to transmit management data between the different entities in real time.
传统体系结构要求每个用户具有永久虚拟电路。这种虚拟电路配置在第2层上，并在第一层3设备（例如，宽带远程接入服务器（BRAS））处终止。除了数据平面之外，这些模型还定义了元素、网络和服务管理的体系结构。由于运营本地环路的部门、运营ATM网络的部门和运营IP网络的部门之间的组织边界，在管理平面上的互通并不总是可能的。此外，管理网络通常不设计为在不同实体之间实时传输管理数据。
When deploying value-added services across DSL access networks, special attention regarding quality of service and service control is required, which implies a tighter coordination between Network Nodes (e.g., Access Nodes and Network Access Server (NAS)), without burdening the Operational Support System (OSS) with unpractical expectations.
在跨DSL接入网络部署增值服务时，需要特别注意服务质量和服务控制，这意味着网络节点（例如，接入节点和网络接入服务器（NAS））之间的协调更加紧密，而不会给运营支持系统（OSS）带来不现实的期望。
Therefore, there is a need for an Access Node Control Mechanism between a NAS and an Access Node (e.g., a Digital Subscriber Line Access Multiplexer (DSLAM)) in a multi-service reference architecture in order to perform operations related to service, quality of service, and subscribers. The Access Node Control Mechanism will ensure that the transmission of the information does not need to go through distinct element managers but rather using a direct device-device communication. This allows for performing access-link-related operations within those network elements, while avoiding impact on the existing OSSes.
因此，在多业务参考体系结构中，需要NAS和接入节点（例如，数字用户线接入多路复用器（DSLAM））之间的接入节点控制机制，以便执行与服务、服务质量和用户相关的操作。接入节点控制机制将确保信息的传输不需要通过不同的元素管理器，而是使用直接的设备通信。这允许在这些网络元件内执行与接入链路相关的操作，同时避免对现有OSS的影响。
This document provides a framework for such an Access Node Control Mechanism and identifies a number of use cases for which this mechanism can be justified. Next, it presents a number of requirements for the Access Node Control Protocol (ANCP) and the network elements that need to support it.
本文档为这种访问节点控制机制提供了一个框架，并确定了可以证明这种机制的许多用例。接下来，它介绍了访问节点控制协议（ANCP）的一些要求以及需要支持它的网络元素。
The requirements spelled out in this document are based on the work that is performed by the Broadband Forum [TR-147].
本文件中规定的要求基于宽带论坛[TR-147]开展的工作。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
o Access Node (AN): network device, usually located at a service provider central office or street cabinet, that terminates access-loop connections from subscribers. In case the access loop is a Digital Subscriber Line (DSL), this is often referred to as a DSL Access Multiplexer (DSLAM).
o 接入节点（Access Node）：网络设备，通常位于服务提供商的中央办公室或街道机柜，用于终止来自订阅者的接入环路连接。在接入环路是数字用户线（DSL）的情况下，这通常被称为DSL接入多路复用器（DSLAM）。
o Network Access Server (NAS): network device that aggregates multiplexed subscriber traffic from a number of Access Nodes. The NAS plays a central role in per-subscriber policy enforcement and quality of service (QoS). Often referred to as a Broadband Network Gateway (BNG) or Broadband Remote Access Server (BRAS). A detailed definition of the NAS is given in [RFC2881].
o 网络访问服务器（NAS）：聚合来自多个访问节点的多路复用用户流量的网络设备。NAS在按订户策略实施和服务质量（QoS）方面起着核心作用。通常称为宽带网络网关（BNG）或宽带远程访问服务器（BRAS）。[RFC2881]中给出了NAS的详细定义。
o "Net Data Rate": defined by ITU-T G.993.2 [G.993.2], section 3.39, i.e., the portion of the total data rate that can be used to transmit user information (e.g., ATM cells or Ethernet frames). It excludes overhead that pertains to the physical transmission mechanism (e.g., trellis coding in the case of DSL). It includes
o “净数据速率”：由ITU-T G.993.2[G.993.2]第3.39节定义，即可用于传输用户信息（如ATM信元或以太网帧）的总数据速率部分。它排除了与物理传输机制相关的开销（例如，DSL情况下的网格编码）。它包括
TPS-TC (Transport Protocol Specific - Transmission Convergence) encapsulation; this is zero for ATM encapsulation, and non-zero for 64/65 encapsulation.
TPS-TC（传输协议专用-传输汇聚）封装；这对于ATM封装是零，对于64/65封装是非零。
o "Line Rate": defined by ITU-T G.993.2. It contains the complete overhead including Reed-Solomon and Trellis coding.
o “线路费率”：由ITU-T G.993.2定义。它包含完整的开销，包括Reed-Solomon和网格编码。
o Access Node Control Mechanism: a method for multiple network scenarios with an extensible communication scheme that conveys status and control information between one or more ANs and one or more NASes without using intermediate element managers.
o 接入节点控制机制：一种用于多个网络场景的方法，具有可扩展的通信方案，在一个或多个an和一个或多个NASE之间传输状态和控制信息，而无需使用中间元素管理器。
o Control Channel: a bidirectional IP communication interface between the controller function (in the NAS) and the reporting/ enforcement function (in the AN). It is assumed that this interface is configured (rather than discovered) on the AN and the NAS.
o 控制通道：控制器功能（在NAS中）和报告/实施功能（在AN中）之间的双向IP通信接口。假定此接口是在AN和NAS上配置的（而不是发现的）。
o Access Node Control Adjacency: the relationship between an Access Node and a NAS for the purpose of exchanging Access Node Control Protocol messages. The adjacency may either be up or down, depending on the result of the Access Node Control Adjacency protocol operation.
o 访问节点控制邻接：访问节点与NAS之间的关系，用于交换访问节点控制协议消息。根据接入节点控制邻接协议操作的结果，邻接可以是向上或向下。
o Multicast Flow: designates datagrams sent to a group from a set of sources for which multicast reception is desired. A distinction can be made between Any Source Multicast (ASM) and Source-Specific Multicast (SSM).
o 多播流：指定从一组需要多播接收的源发送到组的数据报。可以区分任何源多播（ASM）和源特定多播（SSM）。
o Join: signaling from the user equipment that it wishes to start receiving a new multicast flow. In ASM, it is referred to as a "Join". In SSM [RFC4607], it is referred to as a "subscribe". In IGMPv2, "joins" are indicated through an "IGMPv2 membership report". In IGMPv3 [RFC3376], "join" is indicated through "membership report" using different Filter-Mode-Change (ASM) and Source-List-Change Records.
o 加入：来自用户设备的信号，表示它希望开始接收新的多播流。在ASM中，它被称为“连接”。在SSM[RFC4607]中，它被称为“订阅”。在IGMPv2中，“加入”通过“IGMPv2成员报告”表示。在IGMPv3[RFC3376]中，“加入”通过使用不同过滤模式更改（ASM）和源列表更改记录的“成员报告”表示。
o Leave: signaling from the user equipment that it wishes to stop receiving a multicast flow. With IGMPv2, this is conveyed inside the "Leave Group" message, while in IGMPv3, "leave" is indicated through the "IGMPv3 membership report" message using different Filter-Mode-Change (ASM) and Source-List-Change Records.
o 离开：来自用户设备的信号，表示它希望停止接收多播流。对于IGMPv2，这在“离开组”消息中传递，而在IGMPv3中，“离开”通过“IGMPv3成员报告”消息使用不同的过滤模式更改（ASM）和源列表更改记录来指示。
This section introduces the basic concept of the Access Node Control Mechanism and describes the reference architecture where it is being applied. Based on the reference architecture, the section then describes how Access Node Control messages are to be prioritized over other data traffic, and the interaction between ANCP and the network management system. Finally, the addressing schemes are described that allow identifying an Access Port in Access Node Control messages.
本节介绍访问节点控制机制的基本概念，并描述应用该机制的参考体系结构。基于参考体系结构，本节接着描述了访问节点控制消息如何优先于其他数据流量，以及ANCP和网络管理系统之间的交互。最后，描述了允许在接入节点控制消息中识别接入端口的寻址方案。
The high-level communication framework for an Access Node Control Mechanism is defined in Figure 1. The Access Node Control Mechanism defines a quasi-real-time, general-purpose method for multiple network scenarios with an extensible communication scheme, addressing the different use cases that are described throughout this document.
访问节点控制机制的高级通信框架如图1所示。接入节点控制机制通过可扩展的通信方案为多个网络场景定义了一种准实时、通用的方法，解决了本文档中描述的不同用例。
+--------+
| Policy |
| Server |
+--------+
|
|
+-----+ +-----+ +--------+ +-----+ +----------+
| CPE |--| HGW |--| | | | | |
+-----+ +-----+ | Access | +-------------+ | | | Regional |
| Node |---| Aggregation |---| NAS |--| Network |
+-----+ +-----+ | | | Network | | | | |
| CPE |--| HGW |--| | +-------------+ | | | |
+-----+ +-----+ +--------+ +-----+ +----------+
Information Report / Admission Request
------------------------------>
Admission Response / Control Request
<------------------------------
Control Response
------------------------------>
+--------+
| Policy |
| Server |
+--------+
|
|
+-----+ +-----+ +--------+ +-----+ +----------+
| CPE |--| HGW |--| | | | | |
+-----+ +-----+ | Access | +-------------+ | | | Regional |
| Node |---| Aggregation |---| NAS |--| Network |
+-----+ +-----+ | | | Network | | | | |
| CPE |--| HGW |--| | +-------------+ | | | |
+-----+ +-----+ +--------+ +-----+ +----------+
Information Report / Admission Request
------------------------------>
Admission Response / Control Request
<------------------------------
Control Response
------------------------------>
Access Node Control Mechanism
<----------------------------->
PPP, DHCP, IP
<---------><----------------------------------------->
Access Node Control Mechanism
<----------------------------->
PPP, DHCP, IP
<---------><----------------------------------------->
CPE: Customer Premises Equipment HGW: Home Gateway
CPE：客户场所设备HGW：家庭网关
Figure 1: Access Network Architecture
图1：接入网络架构
A number of functions can be identified:
可以确定许多功能：
o A controller function: this function is used either to send out requests for information to be used by the network element where the controller function resides, or to trigger a certain behavior in the network element where the reporting and/or enforcement function resides.
o 控制器功能：此功能用于发送信息请求，以供控制器功能所在的网元使用，或触发报告和/或强制功能所在的网元中的特定行为。
o A reporting function: this function is used to convey status information to the controller function. An example of this is the transmission of the access-loop data rate from an Access Node to a Network Access Server (NAS) tasked with shaping traffic to that rate.
o 报告功能：该功能用于向控制器功能传递状态信息。这方面的一个例子是从接入节点向网络接入服务器（NAS）传输接入环路数据速率，该网络接入服务器（NAS）负责将流量调整为该速率。
o An enforcement function: this function is contacted by the controller function to trigger a remote action on the Access Node. An example is the initiation of a port-testing mechanism on an Access Node. Another example is enforcing whether a multicast join is to be honored or denied.
o 强制功能：控制器功能联系此功能以触发访问节点上的远程操作。例如，在接入节点上启动端口测试机制。另一个例子是强制执行多播连接是被接受还是被拒绝。
The messages shown in Figure 1 show the conceptual message flow. The actual use of these flows, and the times or frequencies when these messages are generated depends on the actual use cases, which are described in Section 3.
图1所示的消息显示了概念性的消息流。这些流的实际使用以及生成这些消息的时间或频率取决于第3节中描述的实际用例。
The use cases in this document are described in an abstract way, independent from any actual protocol mapping. The actual protocol specification is out of scope of this document, but there are certain characteristics of the protocol that are required to simplify specification, implementation, debugging and troubleshooting, and to extend support for additional use cases.
本文中的用例是以抽象的方式描述的，独立于任何实际的协议映射。实际的协议规范不在本文档的范围内，但是需要协议的某些特性来简化规范、实现、调试和故障排除，并扩展对其他用例的支持。
The reference architecture used in this document can be based on ATM or Ethernet access/aggregation. Specifically:
本文档中使用的参考体系结构可以基于ATM或以太网访问/聚合。明确地：
o In case of a legacy ATM aggregation network that is to be used for the introduction of new QoS-enabled IP services, the architecture builds on the reference architecture specified in the Broadband Forum [TR-059];
o 对于用于引入新的QoS支持IP服务的传统ATM聚合网络，该体系结构建立在宽带论坛[TR-059]中规定的参考体系结构基础上；
o In case of an Ethernet aggregation network that supports new QoS-enabled IP services (including Ethernet multicast replication), the architecture builds on the reference architecture specified in the Broadband Forum [TR-101].
o 对于支持新的支持QoS的IP服务（包括以太网多播复制）的以太网聚合网络，该体系结构基于宽带论坛[TR-101]中指定的参考体系结构。
Given the industry's move towards Ethernet as the new access and aggregation technology for triple-play services, the primary focus throughout this document is on a TR-101 architecture. However the concepts are equally applicable to an ATM architecture based on TR-059.
鉴于业界正朝着以太网的方向发展，将其作为三网融合服务的新接入和聚合技术，本文档主要关注TR-101体系结构。然而，这些概念同样适用于基于TR-059的ATM体系结构。
The Home Gateway (HGW) connects the different Customer Premises Equipment (CPE) to the Access Node and the access network. In case of DSL, the HGW is a DSL Network Termination (NT) that could either operate as a layer 2 bridge or as a layer 3 router. In the latter case, such a device is also referred to as a Routing Gateway (RG).
家庭网关（HGW）将不同的客户场所设备（CPE）连接到接入节点和接入网络。在DSL的情况下，HGW是DSL网络终端（NT），可以作为第2层网桥或第3层路由器运行。在后一种情况下，这种设备也称为路由网关（RG）。
The access loop ensures physical connectivity between the HGW at the customer premises and the Access Node. In case of DSL, the access-loop physical layer could be, e.g., ADSL, ADSL2+, VDSL, VDSL2, or SHDSL. In order to increase bandwidth, it is also possible that multiple DSL links are grouped together to form a single virtual link; this process is called "DSL bonding". The protocol encapsulation on the access loop could be based on multi-protocol encapsulation over ATM Adaption Layer 5 (AAL5) defined in [RFC2684]. This covers PPP over Ethernet (PPPoE, defined in [RFC2516]), bridged IP (IP over Ethernet (IPoE), defined in [RFC894]) and routed IP (IP over ATM (IPoA), defined in [RFC2225]). Next to this, PPP over AAL5 (PPPoA) as defined in [RFC2364] can be used. Future scenarios include cases where the access loop supports direct Ethernet encapsulation (e.g., when using VDSL or VDSL2).
接入环路确保客户场所的HGW与接入节点之间的物理连接。在DSL的情况下，接入环路物理层可以是，例如，ADSL、ADSL2+、VDSL、VDSL2或SHDSL。为了增加带宽，还可以将多个DSL链路分组在一起以形成单个虚拟链路；这个过程称为“DSL键合”。接入环路上的协议封装可以基于[RFC2684]中定义的ATM适配层5（AAL5）上的多协议封装。这包括以太网PPP（PPPoE，定义见[RFC2516]）、桥接IP（IP over Ethernet（IPoE），定义见[RFC894]）和路由IP（IP over ATM（IPoA），定义见[RFC2225]）。除此之外，还可以使用[RFC2364]中定义的AAL5上的购买力平价（PPPoA）。未来的场景包括接入环路支持直接以太网封装的情况（例如，当使用VDSL或VDSL2时）。
The Access Node (AN) may support one or more access-loop technologies and allow them to interwork with a common aggregation network technology. Besides the access-loop termination, the AN can also aggregate traffic from other Access Nodes using ATM or Ethernet.
接入节点（AN）可以支持一个或多个接入环路技术，并允许它们与公共聚合网络技术互通。除了接入环路终端，AN还可以使用ATM或以太网聚合来自其他接入节点的流量。
The framework defined by this document is targeted at DSL-based access (either by means of ATM/DSL or as Ethernet/DSL). The framework shall be open to non-DSL technologies, like Passive Optical Networks (PONs) and IEEE 802.16 (WiMAX), but the details of this are outside the scope of this document.
本文档定义的框架针对基于DSL的访问（通过ATM/DSL或以太网/DSL）。该框架应向非DSL技术开放，如无源光网络（PON）和IEEE 802.16（WiMAX），但其细节不在本文件范围内。
The reporting and/or enforcement function defined in Section 2.1 typically resides in an Access Node.
第2.1节中定义的报告和/或实施功能通常位于访问节点中。
The fundamental requirements for the Access Node uplink are to provide traffic aggregation, Class of Service (CoS) distinction, and customer separation and traceability. This can be achieved using an ATM- or Ethernet-based technology.
接入节点上行链路的基本要求是提供业务聚合、服务类别（CoS）区分以及客户分离和可追溯性。这可以通过使用基于ATM或以太网的技术来实现。
The aggregation network provides traffic aggregation towards the NAS. The aggregation technology can be based on ATM (in case of a TR-059 architecture) or Ethernet (in case of a TR-101 architecture).
聚合网络向NAS提供流量聚合。聚合技术可以基于ATM（在TR-059体系结构的情况下）或以太网（在TR-101体系结构的情况下）。
The Network Access Server (NAS) interfaces to the aggregation network by means of standard ATM or Ethernet interfaces, and towards the Regional Network by means of transport interfaces for Ethernet frames (e.g., Gigabit Ethernet (GigE), Ethernet over Synchronous Optical Network (SONET)). The NAS functionality corresponds to the BNG functionality described in Broadband Forum TR-101. In addition to this, the NAS supports the Access Node Control functionality defined for the respective use cases throughout this document.
网络接入服务器（NAS）通过标准ATM或以太网接口与聚合网络连接，并通过以太网帧传输接口（如千兆以太网（GigE）、同步光网络以太网（SONET））与区域网络连接。NAS功能与宽带论坛TR-101中描述的BNG功能相对应。除此之外，NAS还支持本文档中针对各个用例定义的访问节点控制功能。
The controller function defined in Section 2.1 typically resides in a NAS.
第2.1节中定义的控制器功能通常位于NAS中。
The Regional Network connects one or more NAS and associated Access Networks to Network Service Providers (NSPs) and Application Service Providers (ASPs). The NSP authenticates access and provides and manages the IP address to subscribers. It is responsible for overall service assurance and includes Internet Service Providers (ISPs). The ASP provides application services to the application subscriber (gaming, video, content on demand, IP telephony, etc.).
区域网络将一个或多个NAS和关联的接入网络连接到网络服务提供商（NSP）和应用程序服务提供商（ASP）。NSP对访问进行身份验证，并向订阅者提供和管理IP地址。它负责总体服务保证，包括互联网服务提供商（ISP）。ASP向应用程序订户提供应用程序服务（游戏、视频、内容点播、IP电话等）。
The Regional Network supports aggregation of traffic from multiple Access Networks and hands off larger geographic locations to NSPs and ASPs -- relieving a potential requirement for them to build infrastructure to attach more directly to the various Access Networks.
区域网络支持来自多个接入网络的流量聚合，并将更大的地理位置移交给NSP和ASP，从而减轻了他们建设基础设施以更直接连接到各种接入网络的潜在需求。
When sending Access Node Control messages across the aggregation network, care is needed that messages won't get lost. The connectivity between the Access Node and the NAS may differ depending on the actual layer 2 technology used (ATM or Ethernet). This section briefly outlines how network connectivity can be established.
在通过聚合网络发送访问节点控制消息时，需要注意消息不会丢失。根据实际使用的第2层技术（ATM或以太网），接入节点和NAS之间的连接可能有所不同。本节简要介绍如何建立网络连接。
In case of an ATM access/aggregation network, a typical practice is to send the Access Node Control Protocol messages over a dedicated Permanent Virtual Circuit (PVC) configured between the AN and the NAS. These ATM PVCs would then be given a high priority so that at times of network congestion, loss of the ATM cells carrying the Access Node Control Protocol is avoided or minimized. It is discouraged to route the Access Node Control Protocol messages within the Virtual Path (VP) that also carries the customer connections, if that VP is configured with a best-effort QoS class (e.g., Unspecified Bitrate (UBR)). The PVCs of multiple Access Node Control Adjacencies can be aggregated into a VP that is given a high priority and runs across the aggregation network. This requires the presence of a VC cross-connect in the aggregation node that terminates the VP.
在ATM接入/聚合网络的情况下，典型实践是通过在an和NAS之间配置的专用永久虚拟电路（PVC）发送接入节点控制协议消息。这些ATM pvc随后将被赋予高优先级，以便在网络拥塞时，避免或最小化携带接入节点控制协议的ATM信元的丢失。如果虚拟路径（VP）配置了尽力而为的QoS等级（例如，未指定比特率（UBR）），则不鼓励在也承载客户连接的虚拟路径（VP）内路由接入节点控制协议消息。多址节点控制邻接的PVC可以聚合成一个VP，该VP具有高优先级，并在聚合网络中运行。这需要在终止VP的聚合节点中存在VC交叉连接。
In case of an Ethernet access/aggregation network, a typical practice is to send the Access Node Control Protocol messages over a dedicated Ethernet Virtual LAN (VLAN) using a separate VLAN identifier (VLAN ID). This can be achieved using a different VLAN ID for each Access Node, or, in networks with many Access Nodes and a high degree of aggregation, one Customer VLAN (C-VLAN) per Access Node and one Service VLAN (S-VLAN) for the Access Node Control Adjacencies of all Access Nodes. The traffic should be given a high priority (e.g., by using a high CoS value) so that the frame loss of Ethernet frames carrying the Access Node Control Protocol messages is minimized in the event of network congestion.
对于以太网访问/聚合网络，典型的做法是使用单独的VLAN标识符（VLAN ID）通过专用以太网虚拟LAN（VLAN）发送访问节点控制协议消息。这可以通过为每个接入节点使用不同的VLAN ID来实现，或者，在具有多个接入节点和高度聚合的网络中，每个接入节点一个客户VLAN（C-VLAN）和一个服务VLAN（S-VLAN）用于所有接入节点的接入节点控制邻接来实现。应给予通信量高优先级（例如，通过使用高CoS值），以便在网络拥塞的情况下，将承载接入节点控制协议消息的以太网帧的帧丢失降至最低。
In both cases, the Control Channel between NAS and Access Node could use the same physical network and routing resources as the subscriber traffic. This means that the connection is an inband connection between the involved network elements. Therefore, there is no need for an additional physical interface to establish the Control Channel.
在这两种情况下，NAS和接入节点之间的控制通道可以使用与订户通信相同的物理网络和路由资源。这意味着该连接是相关网络元件之间的带内连接。因此，不需要额外的物理接口来建立控制通道。
Note that these methods for transporting Access Node Control Protocol messages are typical examples; they do not rule out other methods that achieve the same behavior.
注意，这些用于传输接入节点控制协议消息的方法是典型示例；他们不排除实现相同行为的其他方法。
The Access Node Control Adjacency interactions must be reliable. In addition to this, some of the use cases described in Section 3 require the interactions to be performed in a transactional fashion,
访问节点控制邻接交互必须是可靠的。除此之外，第3节中描述的一些用例要求以事务方式执行交互，
i.e., using a "request/response" mechanism. This is required so that the network elements always remain in a known state, irrespective of whether or not the transaction is successful.
i、 例如，使用“请求/响应”机制。这是必需的，以便无论交易是否成功，网络元件始终保持在已知状态。
When introducing an Access Node Control Mechanism, care is needed to ensure that the existing management mechanisms remain operational as before.
在引入访问节点控制机制时，需要注意确保现有的管理机制仍能像以前一样运行。
Specifically, when using the Access Node Control Mechanism for performing a configuration action on a network element, one gets confronted with the challenge of supporting multiple managers for the same network element: both the Element Manager as well as the Access Node Control Mechanism may now perform configuration actions on the same network element. Therefore, conflicts need to be avoided.
具体地，当使用接入节点控制机制来对网元执行配置动作时，人们面临着为同一网元支持多个管理器的挑战：网元管理器和访问节点控制机制现在都可以在同一网元上执行配置操作。因此，需要避免冲突。
Using the Access Node Control Mechanism, the NAS retrieves and controls a number of subscriber-related parameters. The NAS may decide to communicate this information to a central Policy or AAA Server so that it can keep track of the parameters and apply policies on them. The Server can then enforce those policies on the NAS. For instance, in case a subscriber is connected to more than one NAS, the policy server could be used to coordinate the bandwidth available on a given Access Port for use amongst the different NAS devices.
NAS使用访问节点控制机制检索和控制许多与订户相关的参数。NAS可能会决定将此信息传递给中央策略或AAA服务器，以便跟踪参数并对其应用策略。然后，服务器可以在NAS上实施这些策略。例如，如果订户连接到多个NAS，则可以使用策略服务器来协调给定访问端口上的可用带宽，以便在不同NAS设备之间使用。
Guidelines related to management will be addressed in Section 5.
第5节将介绍与管理相关的指南。
In order to associate subscriber parameters to a particular Access Port, the NAS needs to be able to uniquely identify the Access Port (or a specific circuit on an Access Port) using an addressing scheme.
为了将订户参数与特定访问端口相关联，NAS需要能够使用寻址方案唯一地标识访问端口（或访问端口上的特定电路）。
In deployments using an ATM aggregation network, the ATM PVC on an access loop connects the subscriber to a NAS. Based on this property, the NAS typically includes a NAS-Port-Id, NAS-Port, or Calling-Station-Id attribute in RADIUS authentication and accounting packets sent to the RADIUS server(s). Such attribute includes the identification of the ATM VC for this subscriber, which allows in turn identifying the access loop.
在使用ATM聚合网络的部署中，接入环路上的ATM PVC将用户连接到NAS。基于此属性，NAS通常在发送到RADIUS服务器的RADIUS身份验证和记帐数据包中包含NAS端口Id、NAS端口或呼叫站Id属性。该属性包括该用户的ATM VC标识，从而允许标识接入环路。
In an Ethernet-based aggregation network, a new addressing scheme is defined in [TR-101]. Two mechanisms can be used:
在基于以太网的聚合网络中，[TR-101]中定义了一种新的寻址方案。可以使用两种机制：
o A first approach is to use a one-to-one VLAN assignment model for all Access Ports (e.g., a DSL port) and circuits on an Access Port (e.g., an ATM PVC on an ADSL port). This enables directly deriving the port and circuit identification from the VLAN tagging information, i.e., S-VLAN ID or <S-VLAN ID, C-VLAN ID> pair.
o 第一种方法是对所有接入端口（例如DSL端口）和接入端口上的电路（例如ADSL端口上的ATM PVC）使用一对一VLAN分配模型。这使得能够从VLAN标记信息（即S-VLAN ID或<S-VLAN ID，C-VLAN ID>对）直接导出端口和电路标识。
o A second approach is to use a many-to-one VLAN assignment model and to encode the Access Port and circuit identification in the "Agent Circuit ID" sub-option to be added to a DHCP or PPPoE message. The details of this approach are specified in [TR-101].
o 第二种方法是使用多对一VLAN分配模型，并在要添加到DHCP或PPPoE消息的“代理电路ID”子选项中对接入端口和电路标识进行编码。[TR-101]中详细说明了该方法。
This document reuses the addressing scheme specified in TR-101. It should be noted however that the use of such a scheme does not imply the actual existence of a PPPoE or DHCP session, nor the presence of the specific interworking function in the Access Node. In some cases, no PPPoE or DHCP session may be present, while port and circuit addressing would still be desirable.
本文件重复使用TR-101中规定的寻址方案。然而，应当注意，这种方案的使用并不意味着实际存在PPPoE或DHCP会话，也不意味着接入节点中存在特定的互通功能。在某些情况下，可能不存在PPPoE或DHCP会话，但仍需要端口和电路寻址。
[TR-059] and [TR-101] discuss various queuing/scheduling mechanisms to avoid congestion in the access network while dealing with multiple flows with distinct QoS requirements. One technique that can be used on a NAS is known as "Hierarchical Scheduling" (HS). This option is applicable in a single NAS scenario (in which case the NAS manages all the bandwidth available on the access loop) or in a dual NAS scenario (in which case the NAS manages some fraction of the access loop's bandwidth). The HS must, at a minimum, support 3 levels modeling the NAS port, Access Node uplink, and access-loop sync rate. The rationale for the support of HS is as follows:
[TR-059]和[TR-101]讨论了各种排队/调度机制，以避免接入网络中的拥塞，同时处理具有不同QoS要求的多个流。可以在NAS上使用的一种技术称为“分层调度”（HS）。此选项适用于单个NAS方案（在这种情况下，NAS管理接入环路上的所有可用带宽）或双NAS方案（在这种情况下，NAS管理接入环路的部分带宽）。HS必须至少支持3个级别的NAS端口、接入节点上行链路和接入环路同步速率建模。支持房协的理由如下：
o Provide fairness of network resources within a class.
o 提供类内网络资源的公平性。
o Allow for a better utilization of network resources. Drop traffic early at the NAS rather than letting it traverse the aggregation network just to be dropped at the Access Node.
o 允许更好地利用网络资源。尽早在NAS上丢弃通信量，而不是让它穿过聚合网络，在访问节点上丢弃。
o Enable more flexible CoS behaviors than only strict priority.
o 启用比严格优先级更灵活的CoS行为。
o The HS system could be augmented to provide per-application admission control.
o HS系统可以进行扩充，以提供每个应用程序的准入控制。
o Allow fully dynamic bandwidth partitioning between the various applications (as opposed to static bandwidth partitioning).
o 允许在各种应用程序之间进行完全动态的带宽分区（与静态带宽分区相反）。
o Support "per-user weighted scheduling" to allow differentiated Service Level Agreements (e.g., business services) within a given traffic class.
o 支持“每用户加权调度”，以允许在给定流量类别内达成不同的服务级别协议（如业务服务）。
Such mechanisms require that the NAS gains knowledge about the topology of the access network, the various links being used, and their respective rates. Some of the information required is somewhat dynamic in nature (e.g., DSL line rate -- thus also the net data rate); hence, it cannot come from a provisioning and/or inventory management OSS system. Some of the information varies less frequently (e.g., capacity of a DSLAM uplink), but nevertheless needs to be kept strictly in sync between the actual capacity of the uplink and the image the BRAS has of it.
这种机制要求NAS获得有关接入网络拓扑、所使用的各种链路及其各自速率的知识。所需的一些信息本质上是动态的（例如，DSL线路速率——因此也是净数据速率）；因此，它不能来自供应和/或库存管理OSS系统。一些信息的变化频率较低（例如，DSLAM上行链路的容量），但仍需要在上行链路的实际容量和BRAS的图像之间保持严格的同步。
OSS systems are typically not designed to enforce the consistency of such data in a reliable and scalable manner across organizational boundaries. The Access Topology Discovery function is intended to allow the NAS to perform these functions without having to rely on an integration with an OSS system.
OSS系统的设计通常不是为了跨组织边界以可靠和可扩展的方式强制实现此类数据的一致性。访问拓扑发现功能旨在允许NAS执行这些功能，而无需依赖与OSS系统的集成。
Communicating access-loop attributes is specifically important in case the rate of the access loop changes overtime. The DSL actual data rate may be different every time the DSL NT is turned on. In this case, the Access Node sends an Information Report message to the NAS after the DSL line has resynchronized.
如果访问环路的速率随时间变化，则通信访问环路属性尤其重要。每次打开DSL NT时，DSL实际数据速率可能不同。在这种情况下，接入节点在DSL线路重新同步后向NAS发送信息报告消息。
Additionally, during the time the DSL NT is active, data rate changes can occur due to environmental conditions (the DSL access loop can get "out of sync" and can retrain to a lower value, or the DSL access loop could use Seamless Rate Adaptation making the actual data rate fluctuate while the line is active). In this case, the Access Node sends an additional Information Report to the NAS each time the access-loop attributes change above a threshold value.
此外，在DSL NT处于活动状态期间，由于环境条件，数据速率可能发生变化（DSL接入环路可能会“不同步”，并且可以重新训练到较低的值，或者DSL接入环路可以使用无缝速率适配，使得实际数据速率在线路处于活动状态时波动）。在这种情况下，每次访问环路属性更改超过阈值时，访问节点都会向NAS发送附加信息报告。
The hierarchy and the rates of the various links to enable the NAS hierarchical scheduling and policing mechanisms are the following:
用于启用NAS分层调度和策略机制的各种链路的层次结构和速率如下所示：
o The identification and speed (data rate) of the DSL access loop (i.e., the net data rate)
o DSL接入环路的标识和速度（数据速率）（即净数据速率）
o The identification and speed (data rate) of the Remote Terminal (RT) / Access Node uplink (when relevant)
o 远程终端（RT）/接入节点上行链路的标识和速度（数据速率）（相关时）
The NAS can adjust downstream shaping to the Access Loop's current actual data rate, and more generally reconfigure the appropriate nodes of its hierarchical scheduler (support of advanced capabilities according to TR-101).
NAS可以根据接入环路的当前实际数据速率调整下游成形，并更一般地重新配置其分层调度器的适当节点（根据TR-101支持高级功能）。
This use case may actually include more information than link identification and corresponding data rates. In case of DSL access loops, the following access-loop characteristics can be sent to the NAS (cf. ITU-T Recommendation G.997.1 [G.997.1]):
该用例实际上可能包含比链路标识和相应数据速率更多的信息。对于DSL接入环路，可以向NAS发送以下接入环路特性（参见ITU-T建议G.997.1[G.997.1]）：
o DSL Type (e.g., ADSL1, ADSL2, SDSL, ADSL2+, VDSL, VDSL2)
o DSL类型（例如，ADSL1、ADSL2、SDSL、ADSL2+、VDSL、VDSL2）
o Framing mode (e.g., ATM, ITU-T Packet Transfer Mode (PTM), IEEE 802.3 Ethernet in the First Mile (EFM))
o 帧模式（例如，ATM、ITU-T数据包传输模式（PTM）、IEEE 802.3第一英里以太网（EFM））
o DSL port state (e.g., synchronized/showtime, low power, no power/ idle)
o DSL端口状态（例如，同步/显示时间、低功率、无功率/空闲）
o Actual net data rate (upstream/downstream)
o 实际净数据速率（上游/下游）
o Maximum achievable/attainable net data rate (upstream/downstream)
o 最大可实现/可实现净数据速率（上游/下游）
o Minimum net data rate configured for the access loop (upstream/ downstream)
o 为接入环路配置的最小净数据速率（上游/下游）
o Maximum net data rate configured for the access loop (upstream/ downstream)
o 为接入环路配置的最大净数据速率（上游/下游）
o Minimum net data rate in low power state configured for the access loop (upstream/downstream)
o 为接入环路（上游/下游）配置的低功率状态下的最小净数据速率
o Maximum achievable interleaving delay (upstream/downstream)
o 最大可实现交织延迟（上游/下游）
o Actual interleaving delay (upstream/downstream)
o 实际交织延迟（上游/下游）
The NAS MUST be able to receive access-loop characteristics information, and share such information with AAA/policy servers.
NAS必须能够接收访问环路特征信息，并与AAA/策略服务器共享这些信息。
access-loop rates are typically configured in a static way. When a subscriber wants to change its access-loop rate, the network operator needs to reconfigure the Access Port configuration, possibly implying a business-to-business transaction between an Internet Service Provider (ISP) and an Access Provider. From an Operating Expenditures (OPEX) perspective this is a costly operation.
访问环路速率通常以静态方式配置。当用户想要更改其接入环路速率时，网络运营商需要重新配置接入端口配置，这可能意味着互联网服务提供商（ISP）和接入提供商之间的企业对企业交易。从运营支出（OPEX）的角度来看，这是一项成本高昂的操作。
Using the Access Node Control Mechanism to change the access-loop rate from the NAS avoids those cross-organization business-to-business interactions and allows to centralize subscriber-related service data in e.g., a policy server. More generally, several access-loop parameters (e.g., minimum data rate, interleaving delay) could be changed by means of the Access Node Control Mechanism.
使用访问节点控制机制更改NAS的访问环路速率可避免跨组织的业务对业务交互，并允许将与订户相关的服务数据集中到策略服务器中。更一般地，可以通过接入节点控制机制来改变若干接入环路参数（例如，最小数据速率、交织延迟）。
Triggered by the communication of the access-loop attributes described in Section 3.1, the NAS could query a Policy or AAA Server to retrieve access-loop configuration data. The best way to change access-loop parameters is by using profiles. These profiles (e.g., DSL profiles for different services) are pre-configured by the Element Manager managing the Access Nodes. The NAS may then use the Configure Request message to send a reference to the right profile to the Access Node. The NAS may also update the access-loop configuration due to a subscriber service change (e.g., triggered by the policy server).
由第3.1节中描述的访问环路属性的通信触发，NAS可以查询策略或AAA服务器以检索访问环路配置数据。更改访问循环参数的最佳方法是使用配置文件。这些配置文件（例如，不同服务的DSL配置文件）由管理接入节点的元素管理器预先配置。然后，NAS可以使用配置请求消息向接入节点发送对正确配置文件的引用。NAS还可能由于订户服务更改（例如，由策略服务器触发）而更新访问环路配置。
The access-loop configuration mechanism may also be useful for configuration of parameters that are not specific to the access-loop technology. Examples include the QoS profile to be used for an access loop, or the per-subscriber multicast channel entitlement information, used for IPTV applications where the Access Node is performing IGMP snooping or IGMP proxy function. The latter is also discussed in Section 3.4.
接入环路配置机制还可用于配置非特定于接入环路技术的参数。示例包括用于接入环路的QoS简档，或用于接入节点正在执行IGMP窥探或IGMP代理功能的IPTV应用的每订户多播信道授权信息。第3.4节也讨论了后者。
It may be possible that a subscriber wants to change its access-loop rate, and that the operator wants to enforce this updated access-loop rate on the Access Node using ANCP, but that the Access Node Control Adjacency is down. In such a case, the NAS will not be able to request the configuration change on the Access Node. The NAS should then report this failure to the external management system, which could use application-specific signaling to notify the subscriber of the fact that the change could not be performed at this time.
可能订户想要改变其接入环路速率，并且运营商想要使用ANCP在接入节点上强制实施该更新的接入环路速率，但是接入节点控制邻接度降低。在这种情况下，NAS将无法请求访问节点上的配置更改。然后，NAS应将此故障报告给外部管理系统，外部管理系统可使用特定于应用程序的信令通知订户此时无法执行更改。
Traditionally, ATM circuits are point-to-point connections between the BRAS and the DSLAM or DSL NT. In order to test the connectivity on layer 2, appropriate Operations, Administration, and Maintenance (OAM) functionality is used for operation and troubleshooting. An end-to-end OAM loopback is performed between the edge devices (NAS and HGW) of the broadband access network.
传统上，ATM电路是BRA和DSLAM或DSL NT之间的点对点连接。为了测试第2层上的连接，使用适当的操作、管理和维护（OAM）功能进行操作和故障排除。在宽带接入网络的边缘设备（NAS和HGW）之间执行端到端OAM环回。
When migrating to an Ethernet-based aggregation network (as defined by TR-101), end-to-end ATM OAM functionality is no longer applicable. Ideally in an Ethernet aggregation network, end-to-end Ethernet OAM (as specified in IEEE 802.1ag and ITU-T Recommendation Y.1730/1731) can provide access-loop connectivity testing and fault isolation. However, most HGWs do not yet support these standard Ethernet OAM procedures. Also, various access technologies exist such as ATM/DSL, Ethernet in the First Mile (EFM), etc. Each of these access technologies have their own link-based OAM mechanisms that have been or are being standardized in different standard bodies.
当迁移到基于以太网的聚合网络（如TR-101所定义）时，端到端ATM OAM功能不再适用。理想情况下，在以太网聚合网络中，端到端以太网OAM（如IEEE 802.1ag和ITU-T建议Y.1730/1731所规定）可以提供接入环路连接测试和故障隔离。然而，大多数HGW还不支持这些标准以太网OAM过程。此外，还存在各种接入技术，如ATM/DSL、第一英里以太网（EFM）等。这些接入技术中的每一种都有自己的基于链路的OAM机制，这些机制已经或正在不同的标准机构中标准化。
In a mixed Ethernet and ATM access network (including the local loop), it is desirable to keep the same ways to test and troubleshoot connectivity as those used in an ATM-based architecture. To reach consistency with the ATM-based approach, an Access Node Control Mechanism between NAS and Access Node can be used until end-to-end Ethernet OAM mechanisms are more widely available.
在混合以太网和ATM接入网络（包括本地环路）中，最好保持与基于ATM的体系结构中使用的相同的连接测试和故障排除方法。为了与基于ATM的方法保持一致，可以在NAS和接入节点之间使用接入节点控制机制，直到端到端以太网OAM机制更广泛地可用为止。
Triggered by a local management interface, the NAS can use the Access Node Control Mechanism to initiate an access-loop test between Access Node and HGW. In case of an ATM-based access loop, the Access Node Control Mechanism can trigger the Access Node to generate ATM (F4/F5) loopback cells on the access loop. In case of Ethernet, the Access Node can perform a port synchronization and administrative test for the access loop. The Access Node can send the result of the test to the NAS via a Control Response message. The NAS may then send the result via a local management interface. Thus, the connectivity between the NAS and the HGW can be monitored by a single trigger event.
由本地管理接口触发，NAS可以使用接入节点控制机制启动接入节点和HGW之间的接入环路测试。在基于ATM的接入环路的情况下，接入节点控制机制可以触发接入节点在接入环路上生成ATM（F4/F5）环回信元。对于以太网，接入节点可以对接入环路执行端口同步和管理测试。接入节点可以通过控制响应消息将测试结果发送到NAS。NAS随后可通过本地管理接口发送结果。因此，NAS和HGW之间的连接可以通过单个触发事件进行监控。
With the rise of supporting IPTV services in a resource efficient way, multicast services are getting increasingly important.
随着以资源高效的方式支持IPTV服务的兴起，组播服务变得越来越重要。
In case of an ATM access/aggregation network, such as the reference architecture specified in Broadband Forum [TR-059], multicast traffic replication is performed in the NAS. In this model, typically IGMP is used to control the multicast replication process towards the subscribers. The NAS terminates and processes IGMP signaling messages sent by the subscribers; towards the Regional Network, the NAS typically uses a multicast routing protocol such as Protocol Independent Multicast (PIM). The ATM Access Nodes and aggregation switches don't perform IGMP processing, nor do they perform multicast traffic replication. As a result, network resources are wasted within the access/aggregation network.
对于ATM接入/聚合网络，如宽带论坛[TR-059]中规定的参考体系结构，在NAS中执行多播通信量复制。在该模型中，通常使用IGMP来控制面向订阅者的多播复制过程。NAS终止并处理用户发送的IGMP信令消息；对于区域网络，NAS通常使用多播路由协议，例如协议独立多播（PIM）。ATM接入节点和聚合交换机不执行IGMP处理，也不执行多播通信量复制。因此，在访问/聚合网络中浪费了网络资源。
To overcome this resource inefficiency, the Access Node, aggregation node(s), and the NAS must all be involved in the multicast replication process. This prevents several copies of the same stream from being sent within the access/aggregation network. In case of an Ethernet-based access/aggregation network, this may, for example, be achieved by means of IGMP snooping or IGMP proxy in the Access Node and aggregation node(s).
为了克服这种资源效率低下的问题，访问节点、聚合节点和NAS都必须参与多播复制过程。这将防止在访问/聚合网络中发送同一流的多个副本。在基于以太网的接入/聚合网络的情况下，这可以例如通过接入节点和聚合节点中的IGMP窥探或IGMP代理来实现。
By introducing IGMP processing in the access/aggregation nodes, the multicast replication process is now divided between the NAS, the aggregation node(s), and Access Nodes. In order to ensure backward compatibility with the ATM-based model, the NAS, aggregation node,
通过在访问/聚合节点中引入IGMP处理，现在可以在NAS、聚合节点和访问节点之间划分多播复制过程。为了确保与基于ATM的模型的向后兼容性，NAS、聚合节点、，
and Access Node need to behave as a single logical device. This logical device must have exactly the same functionality as the NAS in the ATM access/aggregation network. The Access Node Control Mechanism can be used to make sure that this logical/functional equivalence is achieved by exchanging the necessary information between the Access Node and the NAS.
和访问节点需要作为一个单一的逻辑设备。此逻辑设备必须与ATM访问/聚合网络中的NAS具有完全相同的功能。访问节点控制机制可用于确保通过在访问节点和NAS之间交换必要的信息来实现这种逻辑/功能等效。
Another option is for the subscriber to communicate the "join/leave" information with the NAS. This can for instance be done by terminating all subscriber IGMP signaling on the NAS. Another example could be a subscriber using some form of application-level signaling, which is redirected to the NAS. In any case, this option is transparent to the access and aggregation network. In this scenario, the NAS can use ANCP to create replication state in the AN for efficient multicast replication. The NAS sends a single copy of the multicast stream towards the AN. The NAS can perform conditional access and multicast admission control on multicast joins, and create replication state in the AN if the flow is admitted by the NAS.
另一个选项是订户与NAS通信“加入/离开”信息。例如，这可以通过终止NAS上的所有订户IGMP信令来实现。另一个示例是使用某种形式的应用程序级信令的订户，该信令被重定向到NAS。在任何情况下，此选项对访问和聚合网络都是透明的。在这种情况下，NAS可以使用ANCP在AN中创建复制状态，以实现高效的多播复制。NAS向AN发送多播流的单个副本。NAS可以对多播连接执行条件访问和多播允许控制，如果NAS允许流，则可以在AN中创建复制状态。
The following subsections describe the different use cases related to multicast.
以下小节描述了与多播相关的不同用例。
In a DSL broadband access scenario, service providers may want to dynamically control, at the network level, access to some multicast flows on a per-user basis. This may be used in order to differentiate among multiple Service Offers or to realize/reinforce conditional access for sensitive content. Note that, in some environments, application-layer conditional access by means of Digital Rights Management (DRM) may provide sufficient control, so that Multicast Conditional Access may not be needed.
在DSL宽带接入场景中，服务提供商可能希望在网络级别以每个用户为基础动态控制对一些多播流的接入。这可用于区分多个服务提供，或实现/加强对敏感内容的有条件访问。注意，在某些环境中，通过数字版权管理（DRM）的应用层条件接收可以提供足够的控制，因此可能不需要多播条件接收。
Where Multicast Conditional Access is required, it is possible, in some cases, to provision the necessary conditional access information into the AN so the AN can then perform the conditional access decisions autonomously. For these cases, the NAS can use ANCP to provision the necessary information in the AN so that the AN can decide locally to honor a join or to not honor a join. This can be done with the Control Request and Control Response messages.
在需要多播条件接收的情况下，在某些情况下，可以将必要的条件接收信息提供给AN，以便AN可以自主地执行条件接收决策。对于这些情况，NAS可以使用ANCP在AN中提供必要的信息，以便AN可以在本地决定是否接受加入。这可以通过控制请求和控制响应消息来完成。
Provisioning the conditional access information on the AN can be done using a "white list", "grey list", and/or a "black list". A white list associated with an Access Port identifies the multicast flows that are allowed to be replicated to that port. A black list associated with an Access Port identifies the multicast flows that are not allowed to be replicated to that port. A grey list associated with an Access Port identifies the multicast flows for
可以使用“白名单”、“灰名单”和/或“黑名单”在AN上设置条件接收信息。与访问端口关联的白名单标识允许复制到该端口的多播流。与访问端口关联的黑名单标识不允许复制到该端口的多播流。与访问端口相关联的灰色列表用于标识多播流
which the AN on receiving a join message, before starting traffic replication queries the NAS for further authorization. Each list contains zero, one, or multiple entries, and each entry may specify a single flow or contain ranges (i.e., mask on Group address and/or mask on Source address).
在开始流量复制之前，当接收到加入消息时，会向NAS查询进一步的授权。每个列表包含零个、一个或多个条目，每个条目可以指定单个流或包含范围（即组地址上的掩码和/或源地址上的掩码）。
Upon receiving a join message on an Access Port, the Access Node will first check if the requested multicast flow is part of a white, grey, or a black list associated with that Access Port. If it is part of a white list, the AN autonomously starts replicating multicast traffic. If it is part of a black list, the AN autonomously discards the message because the request is not authorized, and may thus inform the NAS and log the request accordingly. If it is part of a grey list the AN uses ANCP to query the NAS, that in turn will respond to the AN indicating whether the join is to be honored (and hence replication performed by the AN) or denied (and hence replication not performed by the AN).
在接入端口上接收到加入消息后，接入节点将首先检查请求的多播流是否是与该接入端口相关联的白名单、灰名单或黑名单的一部分。如果它是白名单的一部分，则AN将自动开始复制多播流量。如果它是黑名单的一部分，则AN会自动丢弃该消息，因为该请求未经授权，因此可能会通知NAS并相应地记录该请求。如果它是灰色列表的一部分，则AN使用ANCP查询NAS，这反过来将响应AN，指示加入是被遵守（因此由AN执行复制）还是被拒绝（因此不由AN执行复制）。
If the requested multicast flow is part of multiple lists associated with the Access Port, then the most specific match will be used. If the most specific match occurs in multiple lists, the black list entry takes precedence over the grey list, which takes precedence over the white list.
如果请求的多播流是与访问端口关联的多个列表的一部分，则将使用最特定的匹配。如果最具体的匹配出现在多个列表中，则黑名单条目优先于灰名单，灰名单优先于白名单。
If the requested multicast flow is not part of any list, the message should be discarded. This default behavior can easily be changed by means of a "catch-all" statement in either the white list or the grey list. For instance, adding (<S=*,G=*>) in the white list would make the default behavior to accept join messages for a multicast flow that has no other match on any list. Similarly, if the default behavior should be to send a request to the NAS, then adding (<S=*,G=*>) in the grey list accomplishes that.
如果请求的多播流不是任何列表的一部分，则应丢弃该消息。此默认行为可以通过白名单或灰名单中的“catch all”语句轻松更改。例如，在白名单中添加（<S=*，G=*>）将使默认行为接受任何列表上没有其他匹配项的多播流的加入消息。类似地，如果默认行为应该是向NAS发送请求，则在灰色列表中添加（<S=*，G=*>）即可完成此操作。
The white list, black list, and grey list can contain entries allowing:
白名单、黑名单和灰名单可以包含允许以下内容的条目：
o an exact match for a (*,G) ASM group (e.g., <G=g.h.i.l>);
o 精确匹配（*，G）ASM组（例如，<G=G.h.i.l>）；
o an exact match for a (S,G) SSM channel (e.g., <S=s.t.u.v,G=g.h.i.l>);
o （S，G）SSM信道的精确匹配（例如，<S=S.t.u.v，G=G.h.i.l>）；
o a mask-based range match for a (*,G) ASM group (e.g., <G=g.h.i.l/ Mask>);
o （*，G）ASM组的基于掩码的范围匹配（例如，<G=G.h.i.l/mask>）；
o a mask-based range match for a (S,G) SSM channel (e.g., <S=s.t.u.v/Mask,G=g.h.i.l/Mask>);
o （S，G）SSM信道的基于掩码的范围匹配（例如，<S=S.t.u.v/掩码，G=G.h.i.l/掩码>）；
The following are some example configurations:
以下是一些示例配置：
o Scenario 1: reject all messages
o 场景1：拒绝所有消息
* black list = {<S=*,G=*>}
* 黑名单={<S=*，G=*>}
o Scenario 2: reject all messages, except Join (S=*,G=Gi) (1<=i<=n)
o 场景2：拒绝所有消息，除了Join（S=*，G=Gi）（1<=i<=n）
* white list = { <S=*,G=G1> , <S=*,G=G2>, ... <S=*,G=Gn>}
* 白名单={S=*，G=G1>，<S=*，G=G2>，…<S=*，G=Gn>}
* black list = {<S=*,G=*>}
* 黑名单={<S=*，G=*>}
o Scenario 3: AN performs autonomous decisions for some channels, and asks the NAS for other channels
o 场景3：AN对某些通道执行自主决策，并向NAS请求其他通道
* white list = { <S=*,G=G1> , <S=*,G=G2>, ... <S=*,G=Gn>}
* 白名单={S=*，G=G1>，<S=*，G=G2>，…<S=*，G=Gn>}
* grey list = { <S=s,G=Gm>} for m>n
* 灰色列表={<S=S，G=Gm>}表示m>n
* black list = {<S=*,G=*>}
* 黑名单={<S=*，G=*>}
* ==> Join (S=*,G=Gi) gets honored by AN (1<=i<=n)
* ==> Join (S=*,G=Gi) gets honored by AN (1<=i<=n)
* ==> Join (S=s,G=Gm) triggers ANCP Admission Request to NAS
* ==> Join (S=s,G=Gm) triggers ANCP Admission Request to NAS
* ==> everything else gets rejected by AN
* ==> everything else gets rejected by AN
The use of a white list and black list may be applicable, for instance, to regular IPTV services (i.e., broadcast TV) offered by an Access Provider to broadband (e.g., DSL) subscribers. For this application, the IPTV subscription is typically bound to a specific DSL line, and the multicast flows that are part of the subscription are well-known beforehand. Furthermore, changes to the conditional access information are infrequent, since they are bound to the subscription. Hence, the Access Node can be provisioned with the conditional access information related to the IPTV service.
例如，白名单和黑名单的使用可适用于接入提供商向宽带（例如DSL）用户提供的常规IPTV服务（即，广播电视）。对于该应用，IPTV订阅通常绑定到特定DSL线路，并且作为订阅的一部分的多播流是预先已知的。此外，对条件接收信息的更改很少，因为它们绑定到订阅。因此，可以向接入节点提供与IPTV服务相关的条件接入信息。
In some other cases, it may be desirable to have the conditional access decision being taken by the NAS or a Policy Server. This may be the case when conditional access information changes frequently, or when the multicast groups are not known to a client application in advance. The conditional access control could be tied to a more complex policy/authorization mechanism, e.g., time-of-day access, location-based access, or to invoke a remote authorization server. For these cases, the AN can use ANCP to query the NAS that in turn will respond to the AN indicating whether the join is to be denied or honored (and hence replication performed by the AN). This can be done with the Admission Request and Admission Response messages.
在一些其他情况下，可能希望由NAS或策略服务器作出条件接收决定。当条件接收信息频繁更改时，或者当客户端应用程序事先不知道多播组时，可能会出现这种情况。条件访问控制可以与更复杂的策略/授权机制相关联，例如，时间访问、基于位置的访问或调用远程授权服务器。对于这些情况，AN可以使用ANCP查询NAS，而NAS反过来将响应AN，指示加入是被拒绝还是被接受（从而由AN执行复制）。这可以通过许可请求和许可响应消息来完成。
Some examples of using NAS querying are the following:
使用NAS查询的一些示例如下：
o Roaming users: a subscriber that logs in on different wireless hotspots and would like to receive multicast content he is entitled to receive;
o 漫游用户：登录不同无线热点并希望接收其有权接收的多播内容的用户；
o Mobility or seamless handover (a related example): in both cases, the burden of (re)configuring access nodes with white lists or black lists may be too high;
o 移动性或无缝切换（一个相关示例）：在这两种情况下，使用白名单或黑名单（重新）配置接入节点的负担可能过高；
o "Over-the-top video partnerships": service providers may choose to partner with Internet video providers to provide video content. In this case, the multicast group mappings may not be known in advance, or may be reused for different content in succession.
o “顶级视频合作伙伴关系”：服务提供商可以选择与互联网视频提供商合作提供视频内容。在这种情况下，多播组映射可能事先未知，或者可以连续地对不同内容重用。
o "Pay Per View": a subscriber chooses a specific IPTV channel which is made available for a given amount of time.
o “按次付费”：订户选择特定的IPTV频道，该频道在给定的时间内可用。
The successful delivery of triple-play broadband services is quickly becoming a big capacity planning challenge for most of the Service Providers nowadays. Solely increasing available bandwidth is not always practical, cost-economical, and/or sufficient to satisfy end-user experience given not only the strict requirements of unicast delay sensitive applications like VoIP and video, but also the fast growth of multicast interactive applications such as videoconferencing, digital TV, digital audio, online movies, and networked gaming. These applications are typically characterized by a delay-sensitive nature, an extremely loss-sensitive nature, and intensive bandwidth requirements. They are also typically "non-elastic", which means that they operate at a fixed bandwidth that cannot be dynamically adjusted to the currently available bandwidth.
三网融合宽带服务的成功交付正迅速成为当今大多数服务提供商面临的一大容量规划挑战。考虑到VoIP和视频等单播延迟敏感应用的严格要求，以及视频会议、数字电视、数字音频等多播交互应用的快速增长，仅增加可用带宽并不总是切实可行、经济划算和/或足以满足最终用户体验，在线电影和网络游戏。这些应用程序通常具有延迟敏感特性、极易丢失特性和密集的带宽需求。它们通常也是“非弹性”的，这意味着它们在固定带宽上运行，无法动态调整到当前可用带宽。
Therefore, a Connection Admission Control (CAC) mechanism covering admission of video traffic over the DSL broadband access is required, in order to avoid oversubscribing the available bandwidth and negatively impacting the end-user experience.
因此，需要一种连接许可控制（CAC）机制，该机制涵盖通过DSL宽带接入的视频业务的许可，以避免过度订阅可用带宽并对最终用户体验产生负面影响。
Considering specifically admission control over the access line, before honoring a user request to join a new multicast flow, the combination of AN and NAS must ensure admission control is performed to validate that there is sufficient bandwidth remaining on the access line to carry the new video stream (in addition to all other multicast and unicast video streams sent over the access line). The solution needs to cope with multiple flows per access line and needs
具体考虑接入线上的许可控制，在接受用户加入新多播流的请求之前，AN和NAS的组合必须确保执行许可控制，以验证接入线上是否有足够的剩余带宽来承载新视频流（除了通过接入线发送的所有其他多播和单播视频流之外）。该解决方案需要处理每条接入线的多个流，并且需要
to allow access-line bandwidth to be dynamically shared across multicast and unicast traffic (the unicast CAC is performed either by the NAS or by some off-path policy server).
允许在多播和单播通信量之间动态共享接入线带宽（单播CAC由NAS或某些非路径策略服务器执行）。
Thus, supporting CAC for the access line requires some form of synchronization between the entity performing multicast CAC (e.g., the NAS or the AN), the entity performing unicast CAC (e.g., the policy server), and the entity actually enforcing the multicast replication (i.e., the AN). This synchronization can be achieved in a number of ways:
因此，支持接入线的CAC需要在执行多播CAC的实体（例如，NAS或AN）、执行单播CAC的实体（例如，策略服务器）和实际实施多播复制的实体（例如，AN）之间进行某种形式的同步。这种同步可以通过多种方式实现：
o One approach is for the AN to query the NAS so that Admission Control for the access line is performed by the NAS, or by the policy server which interacts with the AN via NAS. The AN can use ANCP to query the NAS that in turn performs a multicast Admission Control check for the new multicast flow and responds to the AN indicating whether the join is to be denied or honored (and hence replication performed by the AN). The NAS may locally keep track of the portion of the access-loop net data rate that is available for (unicast or multicast) video flows and perform video bandwidth accounting for the access loop. Upon receiving an Admission Request from the AN, the NAS can check available access-loop bandwidth before admitting or denying the multicast flow. In the process, the NAS may communicate with the policy server. For unicast video services such as Video on Demand (VoD), the NAS may also be queried (by a policy server or via on-path CAC signaling), so that it can perform admission control for the unicast flow and update the remaining available access-loop bandwidth. The ANCP requirements to support this approach are specified in this document.
o 一种方法是由AN查询NAS，以便由NAS或通过NAS和AN交互的策略服务器执行接入线路的准入控制。AN可以使用ANCP查询NAS，NAS反过来对新的多播流执行多播许可控制检查，并响应AN，指示加入是被拒绝还是被接受（从而由AN执行复制）。NAS可以本地跟踪可用于（单播或多播）视频流的接入环路净数据速率的部分，并对接入环路执行视频带宽计费。当从an接收到接纳请求时，NAS可以在接纳或拒绝多播流之前检查可用的访问环路带宽。在此过程中，NAS可以与策略服务器通信。对于诸如视频点播（VoD）之类的单播视频服务，还可以（通过策略服务器或经由路径CAC信令）查询NAS，以便它可以对单播流执行接纳控制并更新剩余的可用接入环路带宽。本文件规定了支持该方法的ANCP要求。
o The above model could be enhanced with the notion of "Delegation of Authorization". In such a model, the NAS or the policy server delegates authority to the Access Node to perform multicast Admission Control on the access loop. This is sometimes referred to as "Bandwidth Delegation", referring to the portion of the total access-loop bandwidth that can be used by the Access Node for multicast Admission Control. In this model, the NAS or the policy server manages the total access-line bandwidth, performs unicast admission control, and uses ANCP to authorize the Access Node to perform multicast Admission Control within the bounds of the "delegated bandwidth". Upon receiving a request for a multicast flow replication that matches an entry in the white or grey list, the AN performs the necessary bandwidth admission control check for the new multicast flow, before starting the multicast flow replication. At this point, there is typically no
o 可以通过“授权授权”的概念来加强上述模式。在这样的模型中，NAS或策略服务器将权限委托给接入节点，以便在接入环路上执行多播接纳控制。这有时被称为“带宽委派”，指的是接入节点可用于多播接入控制的总接入环路带宽的部分。在该模型中，NAS或策略服务器管理总接入线带宽，执行单播准入控制，并使用ANCP授权接入节点在“委托带宽”的范围内执行多播准入控制。在接收到与白名单或灰名单中的条目匹配的多播流复制请求后，an在开始多播流复制之前，对新的多播流执行必要的带宽许可控制检查。在这一点上，通常没有
need for the Access Node to communicate with the NAS or the policy server via the NAS. The ANCP requirements to support this approach are also specified in this document.
访问节点需要通过NAS与NAS或策略服务器通信。本文件还规定了支持该方法的ANCP要求。
o In case the subscriber communicates the "join/leave" information with the NAS (e.g., by terminating all subscriber IGMP signaling on the NAS or by using some form of application-level signaling), the approach is very similar. In this case, the NAS may locally keep track of the portion of the access-loop bandwidth that is available for video flows, perform CAC for unicast and multicast flows, and perform video bandwidth management. The NAS can set the replication state on the AN using ANCP if the flow is admitted. For unicast video services, the NAS may be queried (by a policy server or via on-path CAC signaling) to perform admission control for the unicast flow, and update the remaining available access-loop bandwidth. The ANCP requirements to support this approach are specified in this document.
o 在订户与NAS通信“加入/离开”信息的情况下（例如，通过终止NAS上的所有订户IGMP信令或通过使用某种形式的应用级信令），该方法非常相似。在这种情况下，NAS可以本地跟踪可用于视频流的接入环路带宽的部分，对单播和多播流执行CAC，并执行视频带宽管理。如果允许流，NAS可以使用ANCP在AN上设置复制状态。对于单播视频服务，可以（通过策略服务器或经由路径上CAC信令）查询NAS以对单播流执行接纳控制，并更新剩余的可用接入环路带宽。本文件规定了支持该方法的ANCP要求。
o In the last approach, the policy server queries the AN directly or indirectly via the NAS, so that both unicast and multicast CAC for the access line are performed by the AN. In this case, a subscriber request for a unicast flow (e.g., a Video on Demand session) will trigger a resource request message towards a policy server; the latter will then query the AN (possibly via the NAS), that in turn will perform unicast CAC for the access line and respond, indicating whether the unicast request is to be honored or denied. The above model could also be enhanced with the notion of "Delegation of Authorization". In such a model, the policy server delegates authority to the Access Node to perform multicast Admission Control on the access loop. In the case when the policy server queries the AN directly, the approach doesn't require the use of ANCP. It is therefore beyond the scope of this document. In the case when the policy server queries the AN indirectly via the NAS, the approach requires the use of ANCP and is therefore in the scope of this document.
o 在最后一种方法中，策略服务器通过NAS直接或间接地查询AN，以便由AN执行接入线路的单播和多播CAC。在这种情况下，对于单播流（例如，视频点播会话）的订户请求将触发朝向策略服务器的资源请求消息；然后，后者将查询AN（可能通过NAS），AN将依次对接入线路执行单播CAC并作出响应，指示单播请求是被接受还是被拒绝。上述模式还可以通过“授权授权”的概念加以加强。在这样的模型中，策略服务器将权限委托给接入节点，以便在接入环路上执行多播接纳控制。在策略服务器直接查询AN的情况下，该方法不需要使用ANCP。因此，这超出了本文件的范围。在策略服务器通过NAS间接查询AN的情况下，该方法需要使用ANCP，因此属于本文档的范围。
The NAS uses ANCP to indicate to the AN whether or not Admission Control is required for a particular multicast flow on a given Access Port. In case Admission Control is required, the Access Node needs to know whether or not it is authorized to perform Admission Control itself and, if so, within which bounds it is authorized to do so (i.e., how much bandwidth is "delegated" by the NAS or the policy server). Depending on the type of multicast flow, Admission Control may or may not by done by the AN:
NAS使用ANCP向AN指示给定访问端口上的特定多播流是否需要许可控制。在需要许可控制的情况下，接入节点需要知道它是否被授权自己执行许可控制，如果是，它被授权在什么范围内执行许可控制（即，NAS或策略服务器“委派”了多少带宽）。根据多播流的类型，接入控制可能由AN完成，也可能不由AN完成：
o Multicast flows that require a Conditional Access operation to be performed by the Access Node are put in the black or white list. In addition, the Access Node performs Admission Control for those flows in the white list for which it is authorized to do so.
o 需要由接入节点执行条件接入操作的多播流被置于黑名单或白名单中。此外，接入节点对其被授权进行接纳控制的白名单中的那些流执行接纳控制。
o Multicast flows that require a Conditional Access operation to be performed by the NAS or the policy server, are put in the grey list. In addition, for those flows in the grey list for which the Access Node should perform Admission Control, the NAS or the policy server will delegate authority to the AN.
o 需要NAS或策略服务器执行条件访问操作的多播流被放入灰色列表中。此外，对于灰色列表中接入节点应执行准入控制的那些流，NAS或策略服务器将把权限委托给AN。
In some cases, the bandwidth that the NAS or the policy server initially delegated to the AN may not be enough to satisfy a multicast request for a new flow. In this scenario, the AN can use ANCP to query the NAS in order to request additional delegated multicast bandwidth. This is a form of extending the AN authorization to perform Admission Control. The NAS or the policy server decides if the request for more bandwidth can be satisfied and uses ANCP to send a response to the AN indicating the updated delegated multicast bandwidth. It is worth noting that in this case, the time taken to complete the procedure is an increment to the zapping delay. In order to minimize the zapping delay for future join requests, the AN can insert in the request message two values: the minimum amount of additional multicast bandwidth requested and the preferred additional amount. The first value is the amount that allows the present join request to be satisfied, the second value an amount that anticipates further join requests.
在某些情况下，NAS或策略服务器最初委派给AN的带宽可能不足以满足新流的多播请求。在这种情况下，AN可以使用ANCP查询NAS，以请求额外的委托多播带宽。这是扩展授权以执行准入控制的一种形式。NAS或策略服务器决定是否可以满足更多带宽的请求，并使用ANCP向AN发送响应，指示更新的委托多播带宽。值得注意的是，在这种情况下，完成程序所需的时间是切换延迟的增量。为了最小化未来加入请求的切换延迟，AN可以在请求消息中插入两个值：请求的附加多播带宽的最小量和首选附加量。第一个值是允许满足当前加入请求的量，第二个值是预期进一步加入请求的量。
In some cases, the NAS or the policy server may not have enough unicast bandwidth to satisfy a new incoming video request: in these scenarios, the NAS can use ANCP to query (or instruct) the AN in order to decrease the amount of multicast bandwidth previously delegated on a given Access Port. This is a form of limiting/ withdrawing AN authorization to perform Admission Control. The NAS can use ANCP to send a response to AN indicating the updated delegated multicast bandwidth. Based on considerations similar to those of the previous paragraph, it indicates the minimum amount of multicast bandwidth that it needs released and a preferred amount, which may be larger.
在某些情况下，NAS或策略服务器可能没有足够的单播带宽来满足新的传入视频请求：在这些情况下，NAS可以使用ANCP查询（或指示）AN，以减少先前在给定访问端口上委派的多播带宽量。这是限制/撤销执行准入控制的授权的一种形式。NAS可以使用ANCP向指示更新的委托多播带宽的发送响应。基于与上一段类似的考虑，它指出了需要释放的最小多播带宽量和首选带宽量，可能更大。
Note: in order to avoid impacting existing multicast traffic, the NAS must not decrease the amount of delegated multicast bandwidth to a value lower than the bandwidth that is currently in use. This requires the NAS to be aware of this information (e.g., by means of a separate query action).
注意：为了避免影响现有的多播流量，NAS不得将委派的多播带宽减少到低于当前使用的带宽的值。这要求NAS了解此信息（例如，通过单独的查询操作）。
In addition, in some cases, upon receiving a leave for a specific multicast flow, the AN may decide that it has an excess of delegated but uncommitted bandwidth. In such case, the AN can use ANCP to send a message to the NAS to release all of part of the unused multicast bandwidth that was previously delegated. In this process, the Access Node may decide to retain a minimum amount of bandwidth for multicast services.
此外，在某些情况下，在接收到针对特定多播流的许可时，AN可能会决定其具有超过委托但未提交的带宽。在这种情况下，AN可以使用ANCP向NAS发送消息，以释放先前委派的所有未使用的多播带宽。在此过程中，接入节点可决定为多播服务保留最小带宽量。
In general, the Access Node and NAS may not be aware of all possible multicast groups that will be streamed in the access network. For instance, it is likely that there will be multicast streams offered across the Internet. For these unknown streams, performing bandwidth Admission Control may be challenging.
通常，接入节点和NAS可能不知道将在接入网络中流式传输的所有可能的多播组。例如，很可能会有跨Internet提供的多播流。对于这些未知流，执行带宽许可控制可能是一项挑战。
To solve this, these requests could be accepted without performing Admission Control. This solution works, provided that the network handles the streams as best effort, so that other streams (that are subject to Admission Control) are not impacted at times of congestion.
为了解决这个问题，这些请求可以在不执行许可控制的情况下被接受。此解决方案有效，前提是网络尽最大努力处理流，以便其他流（受准入控制）在拥塞时不受影响。
Disabling Admission Control for an unknown stream can be achieved by adding a "catch-all statement" in the Access Node white list or grey list. In case the Access Node queries the NAS, the NAS on his turn will have to accept the request. That way, the unknown streams are not blocked by default.
通过在访问节点白名单或灰名单中添加“catch all statement”，可以实现对未知流禁用准入控制。如果访问节点查询NAS，则轮到他的NAS必须接受该请求。这样，默认情况下不会阻止未知流。
Next, in order to ensure that the streams are handled as best effort, the flow must be marked as such when entering the service provider network. This way, whenever congestion occurs somewhere in the access/aggregation network, this stream will be kicked out before the access provider's own premium content.
接下来，为了确保流被尽最大努力处理，在进入服务提供商网络时必须将流标记为尽最大努力处理流。这样，每当访问/聚合网络中的某个地方发生拥塞时，该流将在访问提供商自己的高级内容之前被踢出。
The above concept is applicable beyond the notion of "Internet streams" or other unknown streams; it can be applied to known multicast streams as well. In this case, the Access Node or NAS will accept the stream even when bandwidth may not be sufficient to support the stream. This again requires that the stream be marked as best-effort traffic before entering the access/aggregation network.
上述概念适用于“互联网流”或其他未知流的概念之外；它也可以应用于已知的多播流。在这种情况下，即使带宽可能不足以支持该流，接入节点或NAS也将接受该流。这再次要求在进入访问/聚合网络之前将流标记为尽力而为的流量。
As mentioned in Section 3.4.1, conditional access to popular IPTV channels can be achieved by means of a white and black list configured on the Access Node. This method allows the Access Node to autonomously decide whether or not access can be granted to a multicast flow.
如第3.4.1节所述，通过接入节点上配置的白名单和黑名单，可以实现对流行IPTV频道的有条件接入。此方法允许访问节点自主决定是否可以向多播流授予访问权限。
IPTV is an example of a service that will not be offered as best effort, but requires some level of guaranteed quality of service. This requires the use of Multicast Admission Control. Hence, if the Access Node wants to autonomously perform the admission process, it must be aware of the bandwidth characteristics of multicast flows. Otherwise, the Access Node would have to query the NAS for Multicast Admission Control (per the grey list behavior); this would defeat the purpose of using a white and black list.
IPTV是一种服务的示例，这种服务不会尽最大努力提供，但需要一定程度的服务质量保证。这需要使用多播接纳控制。因此，如果接入节点想要自主地执行接纳过程，那么它必须知道多播流的带宽特性。否则，接入节点将不得不查询NAS以进行多播接纳控制（根据灰名单行为）；这将破坏使用白名单和黑名单的目的。
Some network deployments may combine the use of white list, black list, and grey list. The implications of such a model to the overall Multicast Admission Control model are not fully explored in this document.
某些网络部署可能会结合使用白名单、黑名单和灰名单。本文没有充分探讨这种模型对整个多播接纳控制模型的影响。
It may be desirable to perform time- and/or volume-based accounting for certain multicast flows sent on particular Access Ports. In case the AN is performing the traffic replication process, it knows when replication of a multicast flow to a particular Access Port or user start and stops. Multicast accounting can be addressed in two ways:
可能需要对在特定接入端口上发送的特定多播流执行基于时间和/或基于卷的记帐。在AN正在执行流量复制过程的情况下，它知道多播流到特定访问端口或用户的复制何时开始和停止。可以通过两种方式解决多播记帐问题：
o The AN keeps track of when replication for a given multicast flow starts or ends on a specified Access Port, and generates time-and/or volume-based accounting information per Access Port and per multicast flow, before sending it to a central accounting system for logging. Given that the AN communicates with the accounting system directly, the approach doesn't require the use of ANCP. It is therefore beyond the scope of this document;
o AN跟踪给定多播流的复制何时在指定的访问端口上开始或结束，并在将其发送到中央记帐系统进行记录之前，为每个访问端口和每个多播流生成基于时间和/或卷的记帐信息。鉴于AN直接与会计系统通信，该方法不需要使用ANCP。因此，它超出了本文件的范围；
o The AN keeps track of when replication for a given multicast flow starts or ends on a specified Access Port, and reports this information to the NAS for further processing. In this case, ANCP can be used to send the information from the AN to the NAS. This will be discussed in the remainder of this document.
o AN跟踪给定多播流的复制何时在指定的访问端口上开始或结束，并将此信息报告给NAS以供进一步处理。在这种情况下，可以使用ANCP将信息从AN发送到NAS。这将在本文件的其余部分讨论。
The Access Node can send multicast accounting information to the NAS using the Information Report message. A distinction can be made between two cases:
接入节点可以使用信息报告消息向NAS发送多播计费信息。可以区分两种情况：
o Basic accounting information: the Access Node informs the NAS whenever replication starts or ends for a given multicast flow on a particular Access Port;
o 基本记帐信息：当特定访问端口上给定多播流的复制开始或结束时，访问节点通知NAS；
o Detailed accounting information: the Access Node not only informs the NAS when replication starts or ends, but also informs the NAS about the multicast traffic volume replicated on the Access Port
o 详细记帐信息：访问节点不仅在复制开始或结束时通知NAS，而且还通知NAS在访问端口上复制的多播通信量
for that multicast flow. This is done by adding a byte count in the Information Report message that is sent to the NAS when replication ends.
对于该多播流。这是通过在复制结束时发送到NAS的信息报告消息中添加字节计数来完成的。
Upon receiving the Information Report messages, the NAS generates the appropriate time- and/or volume-based accounting records per access loop and per multicast flow to be sent to the accounting system.
在接收到信息报告消息后，NAS会为每个访问环路和每个多播流生成适当的基于时间和/或卷的记帐记录，以发送到记帐系统。
The NAS should inform the Access Node about the type of accounting needed for a given multicast flow on a particular Access Port:
NAS应通知接入节点特定接入端口上给定多播流所需的计费类型：
o No reporting messages need to be sent to the NAS.
o 无需向NAS发送报告消息。
o Basic accounting is required.
o 基本会计是必需的。
o Detailed accounting is required.
o 需要详细核算。
Note that in case of very fast channel changes, the amount of Information Report messages to be sent to the NAS could become high.
请注意，在通道变化非常快的情况下，发送到NAS的信息报告消息量可能会很高。
The ANCP requirements to support this use case are specified below in this document.
支持该用例的ANCP要求在本文件中规定如下。
It may also be desirable for the NAS to have the capability to asynchronously query the AN to obtain an instantaneous status report related to multicast flows currently replicated by the AN. Such a reporting functionality could be useful for troubleshooting and monitoring purposes. The NAS can query the AN to know the following:
NAS可能还希望能够异步查询AN，以获得与当前由AN复制的多播流相关的即时状态报告。这种报告功能可用于故障排除和监控目的。NAS可以查询AN以了解以下信息：
o Which flows are currently being sent on a specific Access Port (i.e., a report for one Access Port)
o 当前在特定访问端口上发送哪些流（即，一个访问端口的报告）
o On which Access Ports a specified multicast flow is currently being sent (i.e., a report for one multicast flow)
o 当前正在哪个访问端口上发送指定的多播流（即，一个多播流的报告）
o Which multicast flows are currently being sent on each of the Access Ports (i.e., a global report for one Access Node)
o 当前在每个访问端口上发送哪些多播流（即，一个访问节点的全局报告）
The capability to dynamically stop the replication of a multicast flow can be useful in different scenarios: for example in case of prepaid service, when available credit expires, the Service Provider may want to be able to stop multicast replication on a specified Access Port for a particular user. Another example of applicability for this functionality is a scenario where a Service Provider would like to show a "Content Preview": in this case, a multicast content will be delivered just for a fixed amount of time.
动态停止多播流复制的功能在不同的场景中非常有用：例如，在预付费服务的情况下，当可用信用到期时，服务提供商可能希望能够在特定用户的指定访问端口上停止多播复制。此功能适用性的另一个示例是服务提供商希望显示“内容预览”的场景：在这种情况下，多播内容将仅在固定时间内交付。
In both cases, an external entity (for example, a policy server or an external application entity) can instruct the NAS to interrupt the multicast replication of a specified multicast flow to a specified Access Port or user. The NAS can then use ANCP to communicate this decision to the Access Node. This can be done with the Admission Response message.
在这两种情况下，外部实体（例如，策略服务器或外部应用程序实体）可以指示NAS中断指定多播流到指定访问端口或用户的多播复制。然后，NAS可以使用ANCP将该决策传达给接入节点。这可以通过准入响应消息来完成。
In some deployment scenarios, the NAS may be made aware of end-users' requests to join/leave a multicast flow by other means than ANCP Admission Requests sent by the AN. One possible deployment scenario where this model applies is the case where the Access Node doesn't process the IGMP join/leave messages from the end-user (e.g., because they are tunneled), but forwards them to the NAS. In such environments, the NAS can control multicast replication on the AN via ANCP through the use of Spontaneous Admission Responses (i.e., sent by the NAS without prior receipt of a corresponding Admission Request).
在一些部署场景中，除了由AN发送的ANCP接纳请求之外，还可以通过其他方式使NAS知道最终用户加入/离开多播流的请求。此模型适用的一种可能的部署场景是，访问节点不处理来自最终用户的IGMP加入/离开消息（例如，因为它们是隧道式的），而是将它们转发到NAS。在这样的环境中，NAS可以通过使用自发的接纳响应（即，由NAS发送而无需事先接收到相应的接纳请求），通过ANCP控制AN上的多播复制。
R-1 The ANCP MUST be easily extensible through the definition of new message types or TLVs to support use cases beyond those currently addressed in this document (this includes the use of Access Nodes different from a DSLAM, e.g., a PON Access Node).
R-1 ANCP必须通过定义新的消息类型或TLV易于扩展，以支持超出本文档当前所述范围的用例（这包括使用不同于DSLAM的接入节点，例如PON接入节点）。
R-2 The ANCP MUST be flexible enough to accommodate the various technologies that can be used in an access network and in the Access Node; this includes both ATM and Ethernet.
R-2 ANCP必须足够灵活，以适应可在接入网络和接入节点中使用的各种技术；这包括ATM和以太网。
R-3 The Access Node Control interactions MUST be reliable (using either a reliable transport protocol (e.g., TCP) for the Access Node Control Protocol messages, or by designing ANCP to be reliable).
R-3接入节点控制交互必须是可靠的（使用接入节点控制协议消息的可靠传输协议（如TCP），或通过将ANCP设计为可靠的）。
R-4 The ANCP MUST support "request/response" transaction-based interactions for the NAS to communicate control decisions to the Access Node, or for the NAS to request information from the Access Node. Transactions MUST be atomic, i.e., they are either fully completed, or rolled back to the previous state. This is required so that the network elements always remain in a known state, irrespective of whether or not the transaction is successful.
R-4 ANCP必须支持“请求/响应”基于事务的交互，以便NAS将控制决策传达给接入节点，或者NAS从接入节点请求信息。事务必须是原子的，即它们要么完全完成，要么回滚到以前的状态。这是必需的，以便无论交易是否成功，网络元件始终保持在已知状态。
In case the NAS wants to communicate a bulk of independent control decisions to the Access Node, the transaction (and notion of atomicity) applies to the individual control decisions. This avoids
如果NAS希望将大量独立的控制决策传达给访问节点，则事务（以及原子性的概念）适用于各个控制决策。这避免了
having to roll back all control decisions. Similarly, if the NAS wants to request a bulk of independent information elements from the Access Node, the notion of transaction applies to the individual information elements.
必须回滚所有控制决策。类似地，如果NAS希望从访问节点请求大量独立的信息元素，则事务的概念适用于各个信息元素。
R-5 The ANCP MUST be scalable enough to allow a given NAS to control at least 5000 Access Nodes.
R-5 ANCP必须具有足够的可扩展性，以允许给定NAS控制至少5000个访问节点。
R-6 The operation of the ANCP in the NAS and Access Nodes MUST be controllable via a management station (e.g., via SNMP). This MUST allow a management station to retrieve statistics and alarms related to the operation of the ANCP, as well as to allow it to initiate OAM operations and retrieve corresponding results.
R-6 NAS和访问节点中ANCP的操作必须通过管理站（例如，通过SNMP）进行控制。这必须允许管理站检索与ANCP操作相关的统计数据和警报，并允许其启动OAM操作并检索相应的结果。
R-7 The ANCP MUST support providing multicast conditional access information to Access Ports on an Access Node, using black, grey, and white lists.
R-7 ANCP必须支持使用黑名单、灰名单和白名单向接入节点上的接入端口提供多播条件接入信息。
R-8 The ANCP MUST support binding a particular black, grey, and white List to a given Access Port.
R-8 ANCP必须支持将特定的黑、灰、白列表绑定到给定的访问端口。
R-9 Upon receiving a join to a multicast flow that matches the grey list, the ANCP MUST allow the AN to query the NAS to request an admission decision for replicating that multicast flow to a particular Access Port.
R-9在接收到与灰色列表匹配的多播流的加入时，ANCP必须允许AN查询NAS以请求许可决定，以便将该多播流复制到特定的接入端口。
R-10 The ANCP MUST allow the NAS to send an admission decision to the AN indicating whether or not a multicast flow may be replicated to a particular Access Port.
R-10 ANCP必须允许NAS向an发送接纳决定，指示是否可以将多播流复制到特定接入端口。
R-11 The ANCP MUST allow the NAS to indicate to the AN whether or not Admission Control is needed for some multicast flows on a given Access Port, and (where needed) whether or not the Access Node is authorized to perform Admission Control itself (i.e., whether or not AN Bandwidth Delegation applies).
R-11 ANCP必须允许NAS向AN指示给定接入端口上的一些多播流是否需要许可控制，以及（在需要时）接入节点是否被授权自行执行许可控制（即，是否应用带宽委派）。
R-12 In case of Admission Control without AN Bandwidth Delegation, the ANCP MUST allow the NAS to reply to a query from the AN indicating whether or not a multicast flow is allowed to be replicated to a particular Access Port.
R-12在没有带宽委派的许可控制情况下，ANCP必须允许NAS回复来自AN的查询，该查询指示是否允许将多播流复制到特定接入端口。
R-13 In case of Admission Control with AN Bandwidth Delegation, the ANCP MUST allow the NAS to delegate a certain amount of bandwidth to the AN for a given Access Port for multicast services only.
R-13在通过带宽委派进行准入控制的情况下，ANCP必须允许NAS仅为多播服务的给定接入端口将一定数量的带宽委派给AN。
R-14 In case of Admission Control with AN Bandwidth Delegation, the ANCP MUST allow the AN to query the NAS to request additional multicast bandwidth on a given Access Port.
R-14在通过带宽委派进行准入控制的情况下，ANCP必须允许AN查询NAS以请求给定接入端口上的额外多播带宽。
R-15 In case of Admission Control with AN Bandwidth Delegation, the ANCP MUST allow the NAS to query (or to instruct) the AN to reduce the amount of bandwidth previously delegated on a given Access Port.
R-15在通过带宽委派进行准入控制的情况下，ANCP必须允许NAS查询（或指示）AN以减少先前在给定接入端口上委派的带宽量。
R-16 In case of Admission Control with AN Bandwidth Delegation, the ANCP MUST allow the AN to inform the NAS if it autonomously releases redundant multicast bandwidth on a given Access Port.
R-16在通过带宽授权进行准入控制的情况下，ANCP必须允许AN通知NAS它是否自主释放给定接入端口上的冗余多播带宽。
R-17 The ANCP MUST allow the AN to send an Information Report message to the NAS whenever replication of a multicast flow on a particular Access Port starts or ends.
R-17 ANCP必须允许AN在特定访问端口上的多播流复制开始或结束时向NAS发送信息报告消息。
R-18 The ANCP MUST allow the AN to send an Information Report message to the NAS indicating the multicast traffic volume that has been replicated on that port.
R-18 ANCP必须允许AN向NAS发送信息报告消息，指示已在该端口上复制的多播通信量。
R-19 The ANCP MUST allow the NAS to indicate to the AN whether or not multicast accounting is needed for a multicast flow on a particular Access Port.
R-19 ANCP必须允许NAS向AN指示特定接入端口上的多播流是否需要多播计费。
R-20 In case multicast accounting is needed for a multicast flow on a particular Access Port, the ANCP MUST allow the NAS to indicate to the AN whether or not additional volume accounting information is required.
R-20如果特定接入端口上的多播流需要多播计费，ANCP必须允许NAS向AN指示是否需要额外的卷计费信息。
R-21 The ANCP MUST allow the NAS to revoke a decision to replicate a multicast flow to a particular Access Port, which had been conveyed earlier to an AN.
R-21 ANCP必须允许NAS撤销将多播流复制到特定接入端口的决定，该多播流先前已传送到an。
R-22 The ANCP MUST support partial updates of the white, grey, and black lists.
R-22 ANCP必须支持白名单、灰名单和黑名单的部分更新。
R-23 The ANCP MUST allow the NAS to query the AN to obtain information on what multicast flows are currently being replicated on a given Access Port, what Access Ports are currently receiving a given multicast flow, or what multicast flows are currently replicated on each Access Port.
R-23 ANCP必须允许NAS查询AN，以获取关于给定访问端口上当前复制的多播流、当前接收给定多播流的访问端口或每个访问端口上当前复制的多播流的信息。
R-24 The ANCP SHOULD provide a "shutdown" sequence allowing the protocol to inform the peer that the system is gracefully shutting down.
R-24 ANCP应提供“关机”序列，允许协议通知对等方系统正在正常关机。
R-25 The ANCP SHOULD include a "report" model for the Access Node to spontaneously communicate to the NAS changes of states.
R-25 ANCP应包括一个“报告”模型，用于接入节点自发地与NAS通信状态的变化。
R-26 The ANCP SHOULD support a graceful restart mechanism to enable it to be resilient to network failures between the AN and NAS.
R-26 ANCP应支持优雅的重启机制，使其能够适应AN和NAS之间的网络故障。
R-27 The ANCP MUST provide a means for the AN and the NAS to inform each peer about the supported use cases (either use cases defined in this document or future use cases yet to be defined), and to negotiate a common subset.
R-27 ANCP必须为AN和NAS提供一种方法，以告知每个对等方支持的用例（本文档中定义的用例或未来尚未定义的用例），并协商一个公共子集。
The notion of an Access Node Control Adjacency is defined in Section 1.2.
第1.2节定义了访问节点控制邻接的概念。
R-28 The ANCP MUST support an adjacency protocol in order to automatically synchronize its operational state between its peers, to agree on which version of the protocol to use, to discover the identity of its peers, and to detect when they change.
R-28 ANCP必须支持邻接协议，以便在其对等方之间自动同步其运行状态，商定使用哪个版本的协议，发现其对等方的身份，并检测它们何时更改。
R-29 The ANCP MUST include a mechanism to automatically detect adjacency loss.
R-29 ANCP必须包括自动检测邻接丢失的机制。
R-30 A loss of the Access Node Control Adjacency MUST NOT affect subscriber connectivity.
R-30接入节点控制邻接的丢失不得影响用户连接。
R-31 If the Access Node Control Adjacency is lost, it MUST leave the network elements in a known state, irrespective of whether or not the ongoing transaction was successful.
R-31如果访问节点控制邻接丢失，则无论正在进行的事务是否成功，它都必须使网元保持已知状态。
R-32 The ANCP MUST support a mechanism to synchronize access port configuration and status information between ANCP peers as part of establishing or recovering the Access Node Control Adjacency.
R-32作为建立或恢复接入节点控制邻接的一部分，ANCP必须支持在ANCP对等方之间同步接入端口配置和状态信息的机制。
R-33 The Access Node Control Mechanism MUST be defined in a way that is independent of the underlying layer 2 transport technology. Specifically, the Access Node Control Mechanism MUST support transmission over an ATM as well as over an Ethernet aggregation network.
R-33必须以独立于底层第2层传输技术的方式定义接入节点控制机制。具体而言，接入节点控制机制必须支持通过ATM以及以太网聚合网络进行传输。
R-34 The ANCP MUST use the IP protocol stack.
R-34 ANCP必须使用IP协议栈。
R-35 If the layer 2 transport technology is based on ATM, then the ANCP peers must use the encapsulation according to [RFC2684] (IPoA).
R-35如果第2层传输技术基于ATM，则ANCP对等方必须根据[RFC2684]（IPoA）使用封装。
R-36 If the layer 2 transport technology is based on Ethernet, then the ANCP peers must use the encapsulation according to [RFC894] (IPoE).
R-36如果第2层传输技术基于以太网，则ANCP对等方必须根据[RFC894]（IPoE）使用封装。
This section lists the requirements for an AN that supports the use cases defined in this document. Note that this document does not intend to impose absolute requirements on network elements. Therefore, the words "must" and "should" used in this section are not capitalized.
本节列出了支持本文档中定义的用例的an的需求。请注意，本文件无意对网络元件施加绝对要求。因此，本节中使用的“必须”和“应该”不大写。
The Access Node Control Mechanism is defined to operate between an Access Node (AN) and a NAS. In some cases, one AN can be connected to more than one physical NAS device (e.g., in case different wholesale service providers have different NAS devices). In such a model, the physical AN needs to be split in virtual ANs, each having its own Access Node Control reporting and/or enforcement function.
接入节点控制机制定义为在接入节点（an）和NAS之间操作。在某些情况下，一个AN可以连接到多个物理NAS设备（例如，在不同批发服务提供商拥有不同NAS设备的情况下）。在这种模型中，需要将物理AN拆分为虚拟AN，每个AN都有自己的访问节点控制报告和/或实施功能。
R-37 An Access Node as physical device can be split in logical partitions. Each partition may have its independent NAS. Therefore, the Access Node must support at least 2 partitions. The Access Node should support 8 partitions.
R-37作为物理设备的访问节点可以在逻辑分区中拆分。每个分区可能有其独立的NAS。因此，访问节点必须支持至少2个分区。访问节点应该支持8个分区。
R-38 One partition is grouped of several Access Ports. Each Access Port on an Access Node must be assigned uniquely to one partition.
R-38一个分区由多个访问端口组成。访问节点上的每个访问端口必须唯一地分配给一个分区。
It is assumed that all circuits (i.e., ATM PVCs or Ethernet VLANs) on top of the same physical Access Port are associated with the same partition. In other words, partitioning is performed at the level of the physical Access Port only.
假设同一物理访问端口上的所有电路（即ATM PVC或以太网VLAN）都与同一分区相关联。换句话说，分区仅在物理访问端口级别执行。
R-39 Each AN partition must have a separate Access Node Control Adjacency to a NAS.
R-39每个分区必须与NAS有单独的访问节点控制邻接。
R-40 Each AN partition must be able to enforce access of the controllers to their designated partitions.
R-40每个分区必须能够强制控制器访问其指定分区。
R-41 The Access Node should be able to establish and maintain ANCP Adjacencies to redundant controllers.
R-41接入节点应能够建立和维护与冗余控制器的ANCP邻接。
The Control Channel is a bidirectional IP communication interface between the controller function (in the NAS) and the reporting/ enforcement function (in the AN). It is assumed that this interface is configured (rather than discovered) on the AN and the NAS.
控制通道是控制器功能（在NAS中）和报告/实施功能（在AN中）之间的双向IP通信接口。假定此接口是在AN和NAS上配置的（而不是发现的）。
Depending on the network topology, the Access Node can be located in a street cabinet or in a central office. If an Access Node in a street cabinet is connected to a NAS, all user traffic and Access Node Control data can use the same physical link.
根据网络拓扑，访问节点可以位于街道机柜或中央办公室中。如果街道机柜中的访问节点连接到NAS，则所有用户流量和访问节点控制数据都可以使用相同的物理链路。
R-42 The Control Channel should use the same facilities as the ones used for the data traffic. Note that this is actually a deployment consideration, which has no impact on the actual protocol design.
R-42控制信道应使用与数据通信相同的设施。请注意，这实际上是一个部署考虑事项，对实际协议设计没有影响。
R-43 The Access Node must process control transactions in real-time (i.e., with a specific response latency).
R-43接入节点必须实时处理控制事务（即，具有特定的响应延迟）。
R-44 The Access Node should mark Access Node Control Protocol messages with a high priority (e.g., Variable Bit Rate - Real Time (VBR-RT) for ATM cells, p-bit 6 or 7 for Ethernet packets) in order to avoid or reduce the likelihood of dropping packets in case of network congestion.
R-44接入节点应标记具有高优先级的接入节点控制协议消息（例如，ATM信元的可变比特率-实时（VBR-RT），以太网数据包的p位6或7），以避免或降低在网络拥塞情况下丢弃数据包的可能性。
R-45 If ATM interfaces are used, then any Virtual Path Identifier (VPI) and Virtual Circuit Identifier (VCI) value must be able to be used for the purpose of supporting the Access Node Control Channel.
R-45如果使用ATM接口，则必须能够使用任何虚拟路径标识符（VPI）和虚拟电路标识符（VCI）值来支持接入节点控制信道。
R-46 If Ethernet interfaces are used then any C-VID and S-VID must be able to be used for the purpose of supporting the Access Node Control Channel.
R-46如果使用以太网接口，则任何C-VID和S-VID必须能够用于支持接入节点控制信道。
R-47 In case the Access Node and NAS cannot agree on a common set of capabilities, as part of the ANCP capability negotiation procedure, the Access Node must report this to network management.
R-47如果接入节点和NAS不能就一组共同的能力达成一致，作为ANCP能力协商过程的一部分，接入节点必须向网络管理部门报告。
R-48 The Access Node should support generating an alarm to a management station upon loss or malfunctioning of the Access Node Control Adjacency with the NAS.
R-48接入节点应支持在与NAS相邻的接入节点控制丢失或出现故障时向管理站发出警报。
R-49 To identify the Access Node and Access Port within a control domain, a unique identifier is required. This identifier must be in line with the addressing scheme principles specified in Section 3.9.3 of TR-101.
R-49为了识别控制域内的接入节点和接入端口，需要一个唯一标识符。该标识符必须符合TR-101第3.9.3节规定的寻址方案原则。
R-50 In a Broadband Forum TR-101 network architecture, an Access Circuit Identifier (ACI) identifying an AN and Access Port is added to DHCP and PPPoE messages. The NAS must use the same ACI format in ANCP messages in order to allow the NAS to correlate this information with the information present in DHCP and PPPoE messages.
R-50在宽带论坛TR-101网络体系结构中，识别an和接入端口的接入电路标识符（ACI）被添加到DHCP和PPPoE消息中。NAS必须在ANCP消息中使用相同的ACI格式，以便允许NAS将此信息与DHCP和PPPoE消息中的信息相关联。
R-51 The AN must deny any join to a multicast flow matching the black list for the relevant Access Port.
R-51 AN必须拒绝任何与相关接入端口黑名单匹配的多播流的加入。
R-52 The AN must accept any join to a multicast flow matching the white list and for which no Bandwidth Delegation is used.
R-52 AN必须接受与白名单匹配且未使用带宽委派的多播流的任何加入。
R-53 Upon receiving a join to a multicast flow that matches the white list and for which Bandwidth Delegation is used, the AN must perform the necessary bandwidth admission control check for the new flow before starting the multicast flow replication. This may involve a decision made locally, or querying the NAS or external system such as a policy server, to request additional delegated multicast bandwidth on a given Access Port.
R-53在接收到与白名单匹配且使用带宽委派的多播流的加入时，AN必须在开始多播流复制之前对新流执行必要的带宽许可控制检查。这可能涉及在本地做出的决定，或查询NAS或外部系统（如策略服务器），以请求给定访问端口上的额外委派多播带宽。
R-54 Upon receiving a join to a multicast flow which matches the grey list and for which no Bandwidth Delegation is used, the AN must support using ANCP to query the NAS to receive a response indicating whether that join is to be honored or denied. In this case, the NAS will perform both the necessary conditional access and the admission control checks for the new flow.
R-54当接收到与灰色列表匹配且未使用带宽委派的多播流的加入时，AN必须支持使用ANCP查询NAS以接收指示该加入是被接受还是被拒绝的响应。在这种情况下，NAS将对新流执行必要的条件接收和准入控制检查。
R-55 Upon receiving a join to a multicast flow that matches the grey list and for which Bandwidth Delegation is used, the AN must first perform the necessary bandwidth admission control check for the new flow. If successful, the AN must support using ANCP to query the NAS to receive a response indicating whether that join is to be honored or denied.
R-55在接收到与灰色列表匹配的多播流的加入且使用了带宽委派时，AN必须首先对新流执行必要的带宽允许控制检查。如果成功，AN必须支持使用ANCP查询NAS，以接收指示加入是被接受还是被拒绝的响应。
R-56 In case of Admission Control with AN Bandwidth Delegation, the AN must support using ANCP to notify the NAS when the user leaves the multicast flow.
R-56在通过带宽委派进行准入控制的情况下，AN必须支持在用户离开多播流时使用ANCP通知NAS。
R-57 In case of Admission Control with AN Bandwidth Delegation, the AN must support using ANCP to query the NAS to request additional delegated multicast bandwidth on a given Access Port; the AN should be able to specify both the minimum and the preferred amount of additional multicast bandwidth requested.
R-57在通过带宽委托进行准入控制的情况下，AN必须支持使用ANCP查询NAS以请求给定接入端口上额外的委托多播带宽；AN应该能够指定请求的额外多播带宽的最小量和首选量。
R-58 In case of Admission Control with AN Bandwidth Delegation, upon receiving a Bandwidth Delegation Request from the NAS querying the AN for the delegated multicast bandwidth on a given Access Port, the AN must support using ANCP to send a Bandwidth Delegation Response, indicating the currently delegated multicast bandwidth.
R-58在通过带宽委派进行准入控制的情况下，在接收到来自NAS的带宽委派请求后，在给定接入端口上查询AN的委派多播带宽，AN必须支持使用ANCP发送带宽委派响应，指示当前委派多播带宽。
R-59 In case of Admission Control with AN Bandwidth Delegation, it may happen that the NAS wants to "revoke" all or part of the delegated bandwidth. Part of the previously delegated bandwidth may however be in use by multicast services. Therefore, upon receiving a Bandwidth Delegation Request from the NAS instructing to decrease the delegated multicast bandwidth on a given Access Port, the AN must support using ANCP to send a Bandwidth Delegation Response, indicating the delegated multicast bandwidth after the decrease (indicating how much of the delegated bandwidth can be returned to the NAS without impacting multicast services that are currently running).
R-59在通过带宽委派进行准入控制的情况下，NAS可能希望“撤销”全部或部分委派的带宽。然而，先前委派的带宽的一部分可能正由多播服务使用。因此，当从NAS接收到指示减少给定接入端口上的委托多播带宽的带宽委托请求时，AN必须支持使用ANCP发送带宽委托响应，指示减少后的委托多播带宽（指示在不影响当前运行的多播服务的情况下，可以将多少委派带宽返回到NAS）。
R-60 In case of Admission Control with AN Bandwidth Delegation, the AN must support using ANCP to send a Bandwidth Release message to the NAS in order to release unused delegated multicast bandwidth on a given Access Port.
R-60在通过带宽委派进行准入控制的情况下，AN必须支持使用ANCP向NAS发送带宽释放消息，以便释放给定接入端口上未使用的委派多播带宽。
R-61 If the requested multicast flow is not part of any list associated with the Access Port, the AN must discard the message.
R-61如果请求的多播流不是与访问端口相关联的任何列表的一部分，则AN必须丢弃该消息。
R-62 If the requested multicast flow is part of multiple lists associated with the Access Port, the AN must use the most specific match.
R-62如果请求的多播流是与接入端口相关联的多个列表的一部分，则AN必须使用最特定的匹配。
R-63 If the requested multicast flow has the same most specific match in multiple lists, the AN must give precedence to the black list, followed by the grey list, and then the white list.
R-63如果请求的多播流在多个列表中具有相同的最特定匹配，则AN必须优先于黑名单，然后是灰名单，然后是白名单。
R-64 The AN must support configuring a "catch-all" statement in the black, white, or grey list in order to enforce a default behavior for a join to a multicast flow which doesn't match any other entry in a list for the relevant Access Port.
R-64 AN必须支持在黑、白或灰列表中配置“catch all”语句，以便强制多播流的连接的默认行为，该行为与相关访问端口列表中的任何其他条目都不匹配。
R-65 Upon querying the NAS, the AN must not propagate the join message before the successful authorization from the NAS is received.
R-65查询NAS时，在收到来自NAS的成功授权之前，AN不得传播加入消息。
R-66 Upon receiving a leave for a multicast flow that matches the grey list, the AN should be able to autonomously stop replication and advertise this event to the NAS.
R-66收到符合灰色列表的多播流许可后，AN应能够自动停止复制并向NAS播发此事件。
R-67 The AN must support using ANCP to send an Information Report message to the NAS whenever replication starts or ends.
R-67 AN必须支持在复制开始或结束时使用ANCP向NAS发送信息报告消息。
R-68 The AN should support using ANCP to send an Information Report message to the NAS indicating the multicast traffic volume that has been replicated on that port.
R-68 AN应支持使用ANCP向NAS发送信息报告消息，指示已在该端口上复制的多播通信量。
R-69 Upon request by the NAS, the AN must support using ANCP to send an Information Report message to the NAS, indicating what multicast flows are currently being replicated on a given Access Port.
R-69根据NAS的请求，AN必须支持使用ANCP向NAS发送信息报告消息，指示当前在给定访问端口上复制的多播流。
R-70 Upon request by the NAS, the AN must support using ANCP to send an Information Report message to the NAS, indicating what Access Ports are currently receiving a given multicast flow.
R-70根据NAS的请求，AN必须支持使用ANCP向NAS发送信息报告消息，指示哪些接入端口当前正在接收给定的多播流。
R-71 Upon request by the NAS, the AN must support using ANCP to send an Information Report message to the NAS, indicating what multicast flows are currently being replicated on each Access Port.
R-71根据NAS的请求，AN必须支持使用ANCP向NAS发送信息报告消息，指示当前在每个访问端口上复制的多播流。
R-72 Upon receiving an Admission Response from the NAS, indicating that replication of a multicast flow is to start or stop on a given access port of the AN, the AN must enforce this decision. This decision must be taken irrespective of whether or not a corresponding Admission Request was issued by the AN earlier.
R-72当从NAS接收到许可响应，指示多播流的复制将在an的给定访问端口上启动或停止时，an必须强制执行此决定。无论AN是否已发出相应的准入请求，都必须做出该决定。
R-73 The Access Node must be designed to allow fast completion of ANCP operations, in the order of magnitude of tens of milliseconds.
R-73接入节点的设计必须允许ANCP操作以几十毫秒的数量级快速完成。
R-74 The Access Node should avoid sending bursts of ANCP messages related to notification of line attributes or line state, by spreading message transmission over time.
R-74接入节点应避免发送与线路属性或线路状态通知相关的突发ANCP消息，方法是随时间扩展消息传输。
Naturally, the Access Node Control Mechanism is not designed to replace an Element Manager managing the Access Node. There are parameters in the Access Node, such as the DSL noise margin and DSL Power Spectral Density (PSD), which are not allowed to be changed via ANCP or any other control session, but only via the Element Manager. This has to be ensured and protected by the Access Node.
当然，访问节点控制机制并不是为了取代管理访问节点的元素管理器而设计的。接入节点中存在一些参数，例如DSL噪声容限和DSL功率谱密度（PSD），这些参数不允许通过ANCP或任何其他控制会话进行更改，而只能通过元素管理器进行更改。这必须由接入节点确保和保护。
When using ANCP for access-loop configuration, the EMS needs to configure on the Access Node which parameters may or may not be modified using the Access Node Control Mechanism. Furthermore, for those parameters that may be modified using ANCP, the EMS needs to specify the default values to be used when an Access Node comes up after recovery.
当使用ANCP进行接入环路配置时，EMS需要在接入节点上配置哪些参数可以使用接入节点控制机制修改，哪些参数可以不修改。此外，对于那些可以使用ANCP修改的参数，EMS需要指定恢复后接入节点出现时使用的默认值。
R-75 When access-loop configuration via ANCP is required, the EMS must configure on the Access Node which parameter set(s) may be changed/controlled using ANCP.
R-75当需要通过ANCP配置接入环路时，EMS必须在接入节点上配置可使用ANCP更改/控制的参数集。
R-76 Upon receiving an Access Node Control Request message, the Access Node must not apply changes to the parameter set(s) that have not been enabled by the EMS.
R-76在收到接入节点控制请求消息后，接入节点不得对EMS未启用的参数集应用更改。
This section lists the requirements for a NAS that supports the use cases defined in this document. Note that this document does not intend to impose absolute requirements on network elements. Therefore, the words "must" and "should" used in this section are not capitalized.
本节列出了支持本文档中定义的用例的NAS的要求。请注意，本文件无意对网络元件施加绝对要求。因此，本节中使用的“必须”和“应该”不大写。
R-77 The NAS must establish ANCP Adjacencies only with authorized ANCP peers.
R-77 NAS必须仅与授权的ANCP对等方建立ANCP邻接。
R-78 The NAS must support the capability to simultaneously run ANCP with multiple ANs in a network.
R-78 NAS必须支持与网络中的多个AN同时运行ANCP的能力。
R-79 The NAS must be able to establish an Access Node Control Adjacency to a particular partition on an AN and control the access loops belonging to such a partition.
R-79 NAS必须能够建立与an上特定分区的访问节点控制邻接，并控制属于此类分区的访问环路。
R-80 The NAS must support obtaining access-loop information (e.g., net data rate), from its peer Access Node partitions via the Access Node Control Mechanism.
R-80 NAS必须支持通过访问节点控制机制从其对等访问节点分区获取访问环路信息（例如，净数据速率）。
R-81 The NAS must support shaping traffic directed towards a particular access loop to not exceed the net data rate learned from the AN via the Access Node Control Mechanism.
R-81 NAS必须支持对定向到特定接入环路的流量进行整形，使其不超过通过接入节点控制机制从AN获取的净数据速率。
R-82 The NAS should support reducing or disabling the shaping limit used in the Hierarchical Scheduling process, according to per-subscriber authorization data retrieved from a AAA or policy server.
R-82 NAS应支持根据从AAA或策略服务器检索到的每个订户授权数据，减少或禁用分层调度过程中使用的成形限制。
R-83 The NAS must support reporting of access-loop attributes learned via the Access Node Control Mechanism to a Policy or AAA Server using RADIUS Vendor-Specific Attributes (VSAs).
R-83 NAS必须支持使用RADIUS供应商特定属性（VSA）将通过访问节点控制机制学到的访问环路属性报告给策略或AAA服务器。
R-84 In a TR-059/TR-101 network architecture, the NAS shapes traffic sent to a particular Access Port according to the bitrate available on that port. The NAS should take into account the layer 1 and layer 2 encapsulation overhead on the Access Port, retrieved from the AN via the Access Node Control Mechanism.
R-84在TR-059/TR-101网络体系结构中，NAS根据特定接入端口上可用的比特率对发送到该端口的流量进行整形。NAS应考虑接入端口上的第1层和第2层封装开销（通过接入节点控制机制从AN检索）。
R-85 The NAS should support dynamically configuring and reconfiguring discrete service parameters for access loops that are controlled by the NAS. The configurable service parameters for access loops could be driven by local configuration on the NAS or by a policy server.
R-85 NAS应支持为NAS控制的接入环路动态配置和重新配置离散服务参数。访问环路的可配置服务参数可以由NAS上的本地配置或策略服务器驱动。
R-86 The NAS should support triggering an AN via the Access Node Control Mechanism to execute local OAM procedures on an access loop that is controlled by the NAS. If the NAS supports this capability, then the following applies:
R-86 NAS应支持通过接入节点控制机制触发an，以在NAS控制的接入环路上执行本地OAM过程。如果NAS支持此功能，则以下情况适用：
* The NAS must identify the access loop on which OAM procedures need to be executed by specifying an Access Circuit Identifier (ACI) in the request message to the AN.
* NAS必须通过在向an发送的请求消息中指定接入电路标识符（ACI）来识别需要在其上执行OAM过程的接入环路。
* The NAS should support processing and reporting of the remote OAM results learned via the Access Node Control Mechanism.
* NAS应支持处理和报告通过访问节点控制机制获知的远程OAM结果。
* As part of the parameters conveyed within the OAM message to the AN, the NAS should send the list of test parameters pertinent to the OAM procedure. The AN will then execute the OAM procedure on the specified access loop according to the specified parameters. In case no test parameters are conveyed, the AN and NAS must use default and/or appropriately computed values.
* 作为OAM消息中传送到AN的参数的一部分，NAS应发送与OAM过程相关的测试参数列表。然后，AN将根据指定的参数在指定的访问环路上执行OAM过程。如果未传送任何测试参数，AN和NAS必须使用默认值和/或适当的计算值。
* After issuing an OAM request, the NAS will consider the request to have failed if no response is received after a certain period of time. The timeout value should be either the one sent within the OAM message to the AN, or the computed timeout value when no parameter was sent.
* 在发出OAM请求之后，NAS将考虑在某段时间后没有接收到响应时失败的请求。超时值应该是OAM消息中发送给AN的值，或者是未发送参数时计算的超时值。
The exact set of test parameters mentioned above depends on the particular OAM procedure executed on the access loop. An example of a set of test parameters is the number of loopbacks to be performed on the access loop and the timeout value for the overall test. In this case, and assuming an ATM-based access loop, the default value for the timeout parameter would be equal to the number of F5 loopbacks to be performed, multiplied by the F5 loopback timeout (i.e., 5 seconds per the ITU-T I.610 standard).
上述测试参数的精确设置取决于在访问环路上执行的特定OAM过程。测试参数集的一个示例是要在访问环路上执行的环回数量和整个测试的超时值。在这种情况下，并假设基于ATM的访问环路，超时参数的默认值将等于要执行的F5环回数量乘以F5环回超时（即，按照ITU-T i.610标准为5秒）。
R-87 The NAS must treat PPP or DHCP session state independently from any Access Node Control Adjacency state. The NAS must not bring down the PPP or DHCP sessions just because the Access Node Control Adjacency goes down.
R-87 NAS必须独立于任何访问节点控制邻接状态来处理PPP或DHCP会话状态。NAS不能仅仅因为访问节点控制邻接性下降就关闭PPP或DHCP会话。
R-88 The NAS should internally treat Access Node Control traffic in a timely and scalable fashion.
R-88 NAS应以及时且可扩展的方式在内部处理访问节点控制流量。
R-89 The NAS should support protection of Access Node Control communication to an Access Node in case of line card failure.
R-89 NAS应支持在线路卡发生故障时保护与接入节点的接入节点控制通信。
R-90 The NAS must mark Access Node Control Protocol messages as high priority (e.g., appropriately set Diffserv Code Point (DSCP), Ethernet priority bits, or ATM Cell Loss Priority (CLP) bit) such that the aggregation network between the NAS and the AN can prioritize the Access Node Control Protocol messages over user traffic in case of congestion.
R-90 NAS必须将接入节点控制协议消息标记为高优先级（例如，适当设置区分服务码点（DSCP）、以太网优先级位或ATM信元丢失优先级（CLP）位）这样，在发生拥塞的情况下，NAS和AN之间的聚合网络可以将访问节点控制协议消息优先于用户流量。
R-91 In case the NAS and Access Node cannot agree on a common set of capabilities, as part of the ANCP capability negotiation procedure, the NAS must report this to network management.
R-91如果NAS和接入节点不能就一组通用能力达成一致，作为ANCP能力协商过程的一部分，NAS必须将此情况报告给网络管理部门。
R-92 The NAS must only commence Access Node Control information exchange and state synchronization with the AN when there is a non-empty common set of capabilities with that AN.
R-92 NAS必须仅在存在与AN的非空公共功能集时才开始与AN进行访问节点控制信息交换和状态同步。
R-93 The NAS must support generating an alarm to a management station upon loss or malfunctioning of the Access Node Control Adjacency with the Access Node.
R-93 NAS必须支持在与接入节点相邻的接入节点控制丢失或出现故障时向管理站发出警报。
R-94 The NAS must support correlating Access Node Control Protocol messages pertaining to a given access loop with subscriber session(s) over that access loop. This correlation must be achieved by either:
R-94 NAS必须支持将与给定接入环路相关的接入节点控制协议消息与该接入环路上的用户会话相关联。这种相关性必须通过以下方式实现：
* Matching an Access Circuit Identifier (ACI) inserted by the AN in Access Node Control Protocol messages with the corresponding ACI value received in subscriber signaling (e.g., PPPoE and DHCP) messages as inserted by the AN. The format of ACI is defined in [TR-101]; or
* 将由接入节点控制协议消息插入的接入电路标识符（ACI）与由接入节点插入的订户信令（例如PPPoE和DHCP）消息中接收的相应ACI值相匹配。[TR-101]中定义了ACI的格式；或
* Matching an ACI inserted by the AN in Access Node Control Protocol messages with an ACI value locally configured for a static subscriber on the NAS.
* 将接入节点控制协议消息插入的ACI与本地为NAS上的静态订阅服务器配置的ACI值相匹配。
R-95 The NAS must support using ANCP to configure multicast conditional access information to Access Ports on an Access Node, using black lists, grey lists, and white lists.
R-95 NAS必须支持使用ANCP配置多播条件接收信息，以使用黑名单、灰名单和白名单访问访问节点上的端口。
R-96 The NAS must support using ANCP to indicate to the AN whether or not Admission Control is needed for some multicast flows on a given Access Port and where needed whether or not the Access Node is authorized to perform Admission Control itself (i.e., whether or not AN Bandwidth Delegation applies).
R-96 NAS必须支持使用ANCP向AN指示给定接入端口上的某些多播流是否需要许可控制，以及在需要时，接入节点是否被授权自行执行许可控制（即，是否应用带宽委派）。
R-97 Upon receiving a query from the AN for a request to replicate a multicast flow to a particular Access Port, and no AN Bandwidth Delegation is used for that flow, the NAS must be able to perform the necessary checks (conditional access and/or admission control) for the new flow. The NAS must support using ANCP to reply to the AN indicating whether the request is to be honored or denied. This may involve a decision made locally or querying an external system such as a policy server.
R-97当从AN接收到将多播流复制到特定接入端口的请求的查询，并且该流没有使用带宽委派时，NAS必须能够对新流执行必要的检查（条件接入和/或许可控制）。NAS必须支持使用ANCP回复AN，以指示请求是被接受还是被拒绝。这可能涉及本地决策或查询外部系统（如策略服务器）。
R-98 Upon receiving a query from the AN for a request to replicate a multicast flow to a particular Access Port, and Admission Control with AN Bandwidth Delegation is used for that flow, the NAS must be able to perform the conditional access checks (if needed), and must support using ANCP to delegate a certain amount of bandwidth to the AN for a given Access Port.
R-98当从AN接收到将多播流复制到特定接入端口的请求的查询，并且对该流使用带带宽委派的许可控制时，NAS必须能够执行条件接入检查（如果需要），并且必须支持使用ANCP为给定的访问端口将一定数量的带宽委托给AN。
R-99 In case of Admission Control with AN Bandwidth Delegation, upon receiving a Bandwidth Delegation Request from the AN requesting to increase the delegated multicast bandwidth on a given Access Port, the NAS must support using ANCP to send a Bandwidth Delegation Response indicating the new delegating multicast bandwidth.
R-99在通过带宽委派进行准入控制的情况下，在接收到来自AN的带宽委派请求以请求增加给定接入端口上的委派多播带宽时，NAS必须支持使用ANCP发送指示新委派多播带宽的带宽委派响应。
R-100 In case of Admission Control with AN Bandwidth Delegation, the NAS must support using ANCP to send a request to the AN to decrease the amount of multicast bandwidth previously delegated on a given Access Port; the NAS should be able to specify both the minimum and the preferred amount of decrement of multicast bandwidth requested.
R-100在通过带宽委派进行准入控制的情况下，NAS必须支持使用ANCP向AN发送请求，以减少先前在给定接入端口上委派的多播带宽量；NAS应该能够指定请求的多播带宽的最小减量和首选减量。
R-101 In case of Admission Control with AN Bandwidth Delegation, upon receiving an ANCP Bandwidth Release message, the NAS must be able to update accordingly its view of the multicast bandwidth delegated to the AN.
R-101在通过带宽委派进行许可控制的情况下，在接收到ANCP带宽释放消息时，NAS必须能够相应地更新其对委派给AN的多播带宽的视图。
R-102 The NAS must support using ANCP to configure the Access Node with the "maximum number of multicast streams" allowed to be received concurrently per Access Port.
R-102 NAS必须支持使用ANCP将接入节点配置为允许每个接入端口同时接收的“最大多播流数”。
R-103 The NAS must support using ANCP to incrementally add, remove, and modify individual entries in white, black, and grey lists.
R-103 NAS必须支持使用ANCP以增量方式添加、删除和修改白名单、黑名单和灰名单中的单个条目。
R-104 The NAS must support using ANCP to indicate to the AN whether or not multicast accounting is needed for a multicast flow on a particular Access Port.
R-104 NAS必须支持使用ANCP向AN指示特定接入端口上的多播流是否需要多播计费。
R-105 In case multicast accounting is needed for a multicast flow on a particular Access Port, the NAS should support using ANCP to indicate to the AN whether or not additional volume accounting information is required.
R-105如果特定接入端口上的多播流需要多播计费，NAS应支持使用ANCP向AN指示是否需要额外的卷计费信息。
R-106 The NAS must support using ANCP to query the AN to obtain information on what multicast flows are currently replicated on a given Access Port.
R-106 NAS必须支持使用ANCP查询AN，以获取关于给定访问端口上当前复制的多播流的信息。
R-107 The NAS must support using ANCP to query the AN to obtain information on what Access Ports are currently receiving a given multicast flow.
R-107 NAS必须支持使用ANCP查询AN，以获取关于哪些接入端口当前正在接收给定多播流的信息。
R-108 The NAS must support using ANCP to query the AN to obtain information on what multicast flows are currently replicated on each Access Port.
R-108 NAS必须支持使用ANCP查询AN，以获取关于当前在每个接入端口上复制的多播流的信息。
R-109 When Multicast replication occurs on the AN, the NAS must support using ANCP to revoke the authorization to replicate a multicast flow to a particular Access Port.
R-109当在AN上进行多播复制时，NAS必须支持使用ANCP撤销将多播流复制到特定访问端口的授权。
R-110 The NAS should support using ANCP to indicate to the AN that replication of a multicast flow is to start or stop on a given access port of the AN, without having received a corresponding Admission Request from the AN earlier on.
R-110 NAS应支持使用ANCP向AN指示多播流的复制将在AN的给定接入端口上启动或停止，而无需从较早的AN接收到相应的许可请求。
R-111 The NAS must be designed to allow fast completion of ANCP operations, in the order of magnitude of tens of milliseconds.
R-111 NAS的设计必须允许快速完成ANCP操作，数量级为几十毫秒。
R-112 The NAS should protect its resources from misbehaving Access Node Control peers by providing a mechanism to dampen information related to an Access Node partition.
R-112 NAS应通过提供抑制与接入节点分区相关的信息的机制来保护其资源免受行为不端的接入节点控制对等方的影响。
Broadband Forum TR-058 [TR-058], Broadband Forum TR-059 [TR-059], and Broadband Forum TR-101 [TR-101] describe a DSL broadband access architecture and how it enables wholesaling. In such a model, the broadband access provider has a wholesale agreement with one or more service providers. The access provider owns the broadband access network and manages connectivity to the service providers. This allows service providers to provide broadband services to retail customers without having to own the access network infrastructure itself.
宽带论坛TR-058[TR-058]、宽带论坛TR-059[TR-059]和宽带论坛TR-101[TR-101]描述了DSL宽带接入体系结构及其实现批发的方式。在这种模式中，宽带接入提供商与一个或多个服务提供商签订了批发协议。接入提供商拥有宽带接入网络，并管理与服务提供商的连接。这允许服务提供商向零售客户提供宽带服务，而不必拥有接入网络基础设施本身。
When applying the Access Node Control Mechanism to a wholesale network architecture, a number of additional requirements apply.
当将接入节点控制机制应用于批发网络体系结构时，应用了许多附加要求。
R-113 In case of wholesale access, the network provider's NAS should support reporting of access-loop attributes learned from the AN via the Access Node Control Mechanism (or values derived from such attributes), to a retail provider's network gateway owning the corresponding subscriber(s).
R-113在大规模接入的情况下，网络提供商的NAS应支持通过接入节点控制机制（或从此类属性派生的值）向拥有相应订户的零售提供商的网络网关报告从AN学到的接入环路属性。
R-114 In case of Layer 2 Tunneling Protocol (L2TP) wholesale, the NAS must support a proxy architecture that gives different providers conditional access to dedicated Access Node Control resources on an Access Node.
R-114在第2层隧道协议（L2TP）的情况下，NAS必须支持代理体系结构，该体系结构为不同的提供商提供对接入节点上专用接入节点控制资源的有条件访问。
R-115 The NAS when acting as an L2TP Access Concentrator (LAC) must communicate generic access-line-related information to the L2TP Network Server (LNS) in a timely fashion.
R-115 NAS作为L2TP接入集中器（LAC）时，必须及时将通用接入线路相关信息传送给L2TP网络服务器（LNS）。
R-116 The NAS when acting as a LAC may asynchronously notify the LNS of updates to generic access-line-related information.
R-116当NAS充当LAC时，NAS可以异步通知LNS通用接入线相关信息的更新。
This section lists the management-related requirements for the AN and NAS. Note that this document does not intend to impose absolute requirements on network elements. Therefore, the words "must" and "should" used in this section are not capitalized.
本节列出了AN和NAS的管理相关要求。请注意，本文件无意对网络元件施加绝对要求。因此，本节中使用的“必须”和“应该”不大写。
R-117 It must be possible to configure the following parameters on the Access Node and the NAS:
R-117必须能够在接入节点和NAS上配置以下参数：
* Parameters related to the Control Channel transport method: these include the VPI/VCI and transport characteristics (e.g., VBR-RT or Constant Bitrate (CBR)) for ATM networks, or the C-VLAN ID, S-VLAN ID, and p-bit marking for Ethernet networks;
* 与控制信道传输方法相关的参数：包括ATM网络的VPI/VCI和传输特性（例如，VBR-RT或恒定比特率（CBR）），或以太网的C-VLAN ID、S-VLAN ID和p位标记；
* Parameters related to the Control Channel itself: these include the IP address of the IP interface on the Access Node and the NAS.
* 与控制通道本身相关的参数：这些参数包括访问节点和NAS上IP接口的IP地址。
R-118 When the operational status of the Control Channel is changed (up>down, down>up) a linkdown/linkup trap should be sent towards the EMS. This requirement applies to both the AN and the NAS.
R-118当控制信道的运行状态发生变化（向上>向下，向下>向上）时，应向EMS发送一个向下链路/向上链路陷阱。此要求适用于AN和NAS。
R-119 The Access Node must provide the possibility using SNMP to associate individual DSL lines with specific Access Node Control Adjacencies.
R-119接入节点必须提供使用SNMP将单个DSL线路与特定接入节点控制邻接相关联的可能性。
R-120 The Access Node must notify the EMS of configuration changes made by the NAS on the AN using ANCP, in a timely manner.
R-120接入节点必须使用ANCP及时通知EMS NAS在AN上进行的配置更改。
R-121 The Access Node must provide a mechanism that allows the concurrent access on the same resource from several managers (EMS via SNMP, NAS via ANCP). Only one manager may perform a change at a certain time.
R-121访问节点必须提供一种机制，允许多个管理器（通过SNMP的EMS、通过ANCP的NAS）对同一资源进行并发访问。在特定时间，只有一名经理可以执行变更。
R-122 The ANCP may provide a notification mechanism to inform the NAS about configuration changes done by an EMS, in a timely manner. This applies only to changes of parameters that are part of the use case "Access-Loop Configuration" (Section 3.2).
R-122 ANCP可以提供通知机制，以便及时地将EMS所做的配置更改通知NAS。这仅适用于属于用例“访问环路配置”（第3.2节）一部分的参数更改。
[RFC5713] lists the ANCP-related security threats that could be encountered on the Access Node and the NAS. It develops a threat model and identifies requirements for ANCP security, aiming to decide which security functions are required at the ANCP level.
[RFC5713]列出了访问节点和NAS上可能遇到的与ANCP相关的安全威胁。它开发了一个威胁模型，并确定了ANCP安全需求，旨在确定在ANCP级别需要哪些安全功能。
With multicast handling as described in this document, ANCP protocol activity between the AN and the NAS is triggered by join/leave requests coming from the end-user equipment. This could potentially be used for denial-of-service attacks against the AN and/or the NAS.
通过本文档中所述的多播处理，AN和NAS之间的ANCP协议活动由来自最终用户设备的加入/离开请求触发。这可能用于针对AN和/或NAS的拒绝服务攻击。
This is not a new class of risk over already possible IGMP messages sent from subscribers to the NAS when the AN uses no IGMP snooping, and thus is transparent as long as processing of ANCP messages on the NAS/AN is comparably efficient and protected against congestion.
当AN不使用IGMP窥探时，这并不是一种新的风险，因为从订阅者发送到NAS的已经可能的IGMP消息，因此，只要NAS/AN上的ANCP消息处理具有相当的效率，并且能够防止拥塞，这一风险是透明的。
To mitigate this risk, the AN MAY implement control-plane protection mechanisms such as limiting the number of multicast flows a given user can simultaneously join, or limiting the maximum rate of join/ leave from a given user.
为了减轻该风险，AN可以实现控制平面保护机制，例如限制给定用户可以同时加入的多播流的数量，或者限制来自给定用户的最大加入/离开速率。
We also observe that an operator can easily deploy some protection against attacks using invalid multicast flows by taking advantage of the mask-based match in the black list. This way, joins for invalid multicast flows can be denied at the AN level without any ANCP protocol interactions and without NAS involvement.
我们还观察到，通过利用黑名单中基于掩码的匹配，运营商可以轻松部署一些针对使用无效多播流的攻击的保护。这样，在没有任何ANCP协议交互和NAS参与的情况下，可以在AN级别拒绝无效多播流的连接。
R-123 The ANCP MUST comply with the security requirements spelled out in RFC 5713.
R-123 ANCP必须符合RFC 5713中规定的安全要求。
R-124 The Access Node MUST NOT allow the sending of Access Node Control Messages towards the customer premises.
R-124接入节点不得允许向客户场所发送接入节点控制消息。
The authors would like to thank everyone that has provided comments or input to this document. In particular, the authors acknowledge the work done by the contributors to the activities related to the Broadband Forum: Jerome Moisand, Wojciech Dec, Peter Arberg, and Ole Helleberg Andersen. The authors also acknowledge the inputs provided by Roberta Maglione, Angelo Garofalo, Francois Le Faucheur, and
作者要感谢为本文件提供评论或意见的所有人。特别是，作者感谢与宽带论坛相关活动的贡献者所做的工作：Jerome Moissand、Wojciech Dec、Peter Arberg和Ole Helleberg Andersen。作者还感谢Roberta Maglione、Angelo Garofalo、Francois Le Faucheur和
Toerless Eckert regarding multicast. Finally, the authors thank Bharat Joshi, Stefaan De Cnodder, Kirubaharan Dorairaj, Markus Freudenberger, Fortune Huang, and Lothar Reith for providing comments.
关于多播的Toerless Eckert。最后，作者感谢Bharat Joshi、Stefaan De Cnodder、Kirubaharan Doraraj、Markus Freudenberger、Fortune Huang和Lothar Reith提供的评论。
[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月。
[RFC2684] Grossman, D. and J. Heinanen, "Multiprotocol Encapsulation over ATM Adaptation Layer 5", RFC 2684, September 1999.
[RFC2684]Grossman，D.和J.Heinanen，“ATM适配层5上的多协议封装”，RFC 2684，1999年9月。
[RFC5713] Moustafa, H., Tschofenig, H., and S. De Cnodder, "Security Threats and Security Requirements for the Access Node Control Protocol (ANCP)", RFC 5713, January 2010.
[RFC5713]Moustafa，H.，Tschofenig，H.，和S.De Cnodder，“接入节点控制协议（ANCP）的安全威胁和安全要求”，RFC 5713，2010年1月。
[RFC894] Hornig, C., "A Standard for the Transmission of IP Datagrams over Ethernet Networks", STD 41, RFC 894, April 1984.
[RFC894]Hornig，C.，“通过以太网传输IP数据报的标准”，STD 41，RFC894，1984年4月。
[TR-101] Cohen, A. and E. Shrum, "Migration to Ethernet-Based DSL Aggregation", Broadband Forum TR-101, May 2006.
[TR-101]Cohen，A.和E.Shrum，“迁移到基于以太网的DSL聚合”，宽带论坛TR-101，2006年5月。
[G.993.2] ITU-T, "Very high speed digital subscriber line transceivers 2 (VDSL2)", ITU-T Rec. G.993.2, Feb 2006.
[G.993.2]ITU-T，“甚高速数字用户线收发器2（VDSL2）”，ITU-T Rec.G.993.2，2006年2月。
[G.997.1] ITU-T, "Physical layer management for digital subscriber line (DSL) transceivers", ITU-T Rec. G.997.1, Sep 2005.
[G.997.1]ITU-T，“数字用户线（DSL）收发器的物理层管理”，ITU-T Rec.G.997.12005年9月。
[RFC2225] Laubach, M. and J. Halpern, "Classical IP and ARP over ATM", RFC 2225, April 1998.
[RFC2225]Laubach，M.和J.Halpern，“ATM上的经典IP和ARP”，RFC 2225，1998年4月。
[RFC2364] Gross, G., Kaycee, M., Lin, A., Malis, A., and J. Stephens, "PPP Over AAL5", RFC 2364, July 1998.
[RFC2364]Gross，G.，Kaycee，M.，Lin，A.，Malis，A.，和J.Stephens，“AAL5上的购买力平价”，RFC 2364，1998年7月。
[RFC2516] Mamakos, L., Lidl, K., Evarts, J., Carrel, D., Simone, D., and R. Wheeler, "A Method for Transmitting PPP Over Ethernet (PPPoE)", RFC 2516, February 1999.
[RFC2516]Mamakos，L.，Lidl，K.，Evarts，J.，Carrel，D.，Simone，D.，和R.Wheeler，“通过以太网传输PPP（PPPoE）的方法”，RFC 2516，1999年2月。
[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月。
[RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. Thyagarajan, "Internet Group Management Protocol, Version 3", RFC 3376, October 2002.
[RFC3376]Cain，B.，Deering，S.，Kouvelas，I.，Fenner，B.，和A.Thyagarajan，“互联网组管理协议，第3版”，RFC 3376，2002年10月。
[RFC4607] Holbrook, H. and B. Cain, "Source-Specific Multicast for IP", RFC 4607, August 2006.
[RFC4607]Holbrook，H.和B.Cain，“IP的源特定多播”，RFC4607，2006年8月。
[TR-058] Elias, M. and S. Ooghe, "Multi-Service Architecture & Framework Requirements", Broadband Forum TR-058, September 2003.
[TR-058]Elias，M.和S.Ooghe，“多业务架构和框架要求”，宽带论坛TR-058，2003年9月。
[TR-059] Anschutz, T., "DSL Evolution - Architecture Requirements for the Support of QoS-Enabled IP Services", Broadband Forum TR-059, September 2003.
[TR-059]Anschutz，T.，“DSL演进-支持QoS支持IP服务的架构要求”，宽带论坛TR-059，2003年9月。
[TR-147] Voigt, N., Ooghe, S., and M. Platnic, "Layer 2 Control Mechanism For Broadband Multi-Service Architectures", Broadband Forum TR-147, November 2008.
[TR-147]Voigt，N.，Ooghe，S.和M.Platnic，“宽带多业务架构的第2层控制机制”，宽带论坛TR-147，2008年11月。
Authors' Addresses
作者地址
Sven Ooghe Alcatel-Lucent Copernicuslaan 50 B-2018 Antwerpen Belgium
Sven Ooghe Alcatel-Lucent Copernicuslaan 50 B-2018比利时安特卫普
Phone: +32 3 240 42 26
EMail: sven.ooghe@alcatel-lucent.com
Phone: +32 3 240 42 26
EMail: sven.ooghe@alcatel-lucent.com
Norbert Voigt Nokia Siemens Networks Siemensallee 1 17489 Greifswald Germany
诺伯特·沃伊特诺基亚西门子网络西门萨尔1 17489德国格雷夫斯瓦尔德
Phone: +49 3834 555 771
EMail: norbert.voigt@nsn.com
Phone: +49 3834 555 771
EMail: norbert.voigt@nsn.com
Michel Platnic ECI Telecom 30 Hasivim Street 49517 Petakh Tikva Israel
Michel Platnic ECI Telecom 30号Hasivim街49517 Petakh Tikva以色列
Phone: + 972 54 33 81 567
EMail: mplatnic@gmail.com
Phone: + 972 54 33 81 567
EMail: mplatnic@gmail.com
Thomas Haag Deutsche Telekom Heinrich-Hertz-Strasse 3-7 64295 Darmstadt Germany
托马斯·哈格德国电信海因里希·赫兹大街3-7 64295德国达姆施塔特
Phone: +49 6151 628 2088
EMail: haagt@telekom.de
Phone: +49 6151 628 2088
EMail: haagt@telekom.de
Sanjay Wadhwa Juniper Networks 10 Technology Park Drive Westford, MA 01886 US
美国马萨诸塞州韦斯特福德科技园大道10号Sanjay Wadhwa Juniper Networks美国01886
Phone: EMail: swadhwa@juniper.net
电话：电邮：swadhwa@juniper.net