Skip to main content

Security Threats and Security Requirements for the Access Node Control Protocol (ANCP)
RFC 5713

Revision differences

Document history

Date By Action
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'The Access Node Control Protocol (ANCP) aims to communicate Quality of Service (QoS)-related, service-related, and subscriber-related …
Received changes through RFC Editor sync (changed abstract to 'The Access Node Control Protocol (ANCP) aims to communicate Quality of Service (QoS)-related, service-related, and subscriber-related configurations and operations between a Network Access Server (NAS) and an Access Node (e.g., a Digital Subscriber Line Access Multiplexer (DSLAM)). The main goal of this protocol is to allow the NAS to configure, manage, and control access equipment, including the ability for the Access Nodes to report information to the NAS.

This present document investigates security threats that all ANCP nodes could encounter. This document develops a threat model for ANCP security, with the aim of deciding which security functions are required. Based on this, security requirements regarding the Access Node Control Protocol are defined. This document is not an Internet Standards Track specification; it is published for informational purposes.')
2015-10-14
(System) Notify list changed from ancp-chairs@ietf.org, draft-ietf-ancp-security-threats@ietf.org to (None)
2010-01-19
Cindy Morgan State Changes to RFC Published from RFC Ed Queue by Cindy Morgan
2010-01-19
Cindy Morgan [Note]: 'RFC 5713' added by Cindy Morgan
2010-01-14
(System) RFC published