RFC 5713: Security Threats and Security Requirements for the Access Node Control Protocol (ANCP)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC5713
- Published
- January 2010
- Authors
- H. Moustafa; H. Tschofenig; S. De Cnodder
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 18
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5722Handling of Overlapping IPv6 FragmentsUpdated
December 2009
- RFC 5702Use of SHA-2 Algorithms with RSA in DNSKEY and RRSIG Resource Records for DNSSECUpdated
October 2009
- RFC 5692Transmission of IP over Ethernet over IEEE 802.16 NetworksCurrent
October 2009
- RFC 5679Locating IEEE 802.21 Mobility Services Using DNSUpdated
December 2009
- RFC 5678Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Options for IEEE 802.21 Mobility Services (MoS) DiscoveryCurrent
December 2009
- RFC 5677IEEE 802.21 Mobility Services Framework Design (MSFD)Current
December 2009
- RFC 5770Basic Host Identity Protocol (HIP) Extensions for Traversal of Network Address TranslatorsCurrent
April 2010
- RFC 5648Multiple Care-of Addresses RegistrationUpdated
October 2009
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?