Framework and Requirements for an Access Node Control Mechanism in Broadband Multi-Service Networks
RFC 5851, “Framework and Requirements for an Access Node Control Mechanism in Broadband Multi-Service Networks”, is an Informational document published in May 2010 by S. Ooghe, N. Voigt, M. Platnic, T. Haag, S. Wadhwa. The canonical text is published by the RFC Editor.
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.
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. This document is not an Internet Standards Track specification; it is published for informational purposes.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 5851 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5850 A Call Control and Multi-Party Usage Framework for the Session Initiation Protocol
- RFC 5852 RSVP-TE Signaling Extension for LSP Handover from the Management Plane to the Control Plane in a GMPLS-Enabled Transport Network
- RFC 5849 The OAuth 1.0 Protocol
- RFC 5853 Requirements from Session Initiation Protocol Session Border Control Deployments
- RFC 5848 Signed Syslog Messages
- RFC 5854 The Metalink Download Description Format
- RFC 5847 Heartbeat Mechanism for Proxy Mobile IPv6
- RFC 5855 Nameservers for IPv4 and IPv6 Reverse Zones