RFC 7256: Multicast Control Extensions for the Access Node Control Protocol (ANCP)
In plain English — editorial summary, not part of the RFC
This document specifies the extensions to the Access Node Control Protocol (ANCP) (RFC 6320) required for support of the multicast use cases defined in the Access Node Control Protocol framework document (RFC 5851) and one additional use case described in this document. These use cases are organized into the following ANCP capabilities: o multicast replication initiated by the Network Access Server (NAS); o conditional access and admission control with white and black lists; o conditional access and admission control with grey lists; o bandwidth delegation; and o committed bandwidth reporting. These capabilities may be combined according to the rules given in this specification. This document updates RFC 6320 by assigning capability type 3 to a capability specified in this document and by changing the starting point for IANA allocation of result codes determined by IETF Consensus from 0x100 to 0x64.
Document record
- Document ID
- RFC7256
- Published
- July 2014
- Authors
- F. Le Faucheur; R. Maglione; T. Taylor
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 99
- Also known as
- —
- Updates:
- RFC 6320
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7283Handling Unknown DHCPv6 MessagesObsoleted
July 2014
- RFC 7228Terminology for Constrained-Node NetworksCurrent
May 2014
- RFC 7227Guidelines for Creating New DHCPv6 OptionsCurrent
May 2014
- RFC 7287Mobile Multicast Sender Support in Proxy Mobile IPv6 (PMIPv6) DomainsCurrent
June 2014
- RFC 7225Discovering NAT64 IPv6 Prefixes Using the Port Control Protocol (PCP)Current
May 2014
- RFC 7222Quality-of-Service Option for Proxy Mobile IPv6Current
May 2014
- RFC 7291DHCP Options for the Port Control Protocol (PCP)Current
July 2014
- RFC 7220Description Option for the Port Control Protocol (PCP)Current
May 2014
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?