RFC 6934: Applicability of the Access Node Control Mechanism to Broadband Networks Based on Passive Optical Networks (PONs)
In plain English — editorial summary, not part of the RFC
The purpose of this document is to provide applicability of the Access Node Control Mechanism to broadband access based on Passive Optical Networks (PONs). The need for an Access Node Control Mechanism between a Network Access Server (NAS) and an Access Node Complex, composed of a combination of Optical Line Termination (OLT) and Optical Network Termination (ONT) elements, is described in a multi-service reference architecture in order to perform QoS-related, service-related, and subscriber-related operations. The Access Node Control Mechanism is also extended for interaction between components of the Access Node Complex (OLT and ONT). The Access Node Control Mechanism will ensure that the transmission of information between the NAS and Access Node Complex (ANX) and between the OLT and ONT within an ANX does not need to go through distinct element managers but rather uses direct device-to-device communication and stays on net. This allows for performing access-link-related operations within those network elements to meet performance objectives.
Document record
- Document ID
- RFC6934
- Published
- June 2013
- Authors
- N. Bitar; S. Wadhwa; T. Haag; H. Li
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 39
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6935IPv6 and UDP Checksums for Tunneled PacketsCurrent
April 2013
- RFC 6936Applicability Statement for the Use of IPv6 UDP Datagrams with Zero ChecksumsCurrent
April 2013
- RFC 6930RADIUS Attribute for IPv6 Rapid Deployment on IPv4 Infrastructures (6rd)Current
April 2013
- RFC 6939Client Link-Layer Address Option in DHCPv6Current
May 2013
- RFC 6926DHCPv4 Bulk LeasequeryUpdated
April 2013
- RFC 6925The DHCPv4 Relay Agent Identifier Sub-OptionCurrent
April 2013
- RFC 6944Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm Implementation StatusObsoleted
April 2013
- RFC 6946Processing of IPv6 "Atomic" FragmentsCurrent
May 2013
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?