QTECH SmartEdge 100 PPP and PPPoE - Manual (Page 5)

Overview
1 Overview
This document describes how to configure, monitor, and troubleshoot
Point-to-Point Protocol (PPP) or PPP over Ethernet (PPPoE) on ports,
channels, and PPP or PPPoE encapsulated circuits.
Note: Unless otherwise noted, the SmartEdge ® 100 router supports all
commands described in this document.
1.1 PPP-Encapsulated Circuits and Binding
PPP and PPPoE features comply with the following RFCs:
• RFC 1332, The PPP Internet Protocol Control Protocol (IPCP)
The current implementation does not support compression.
• RFC 1334, PPP Authentication Protocols
• RFC 1661, The Point-to-Point Protocol (PPP)
• RFC 1877, PPP Internet Protocol Control Protocol Extensions for Name
Server Addresses
• RFC 1990, The Multilink Protocol (MLPPP)
• RFC 1994, PPP Challenge Handshake Authentication Protocol (CHAP)
• RFC 2364, PPP Over AAL5
• RFC 2516, A Method for Transmitting PPP Over Ethernet, including the
Extensions to a Method for Transmitting PPP over Ethernet (PPPoE)
• RFC 2615, PPP over SONET/SDH
The SmartEdge OS supports PPP on the following ports, channels, and circuits:
• POS ports
• ATM PVCs on ATM OC ports
On ATM PVCs, PPP encapsulation types include virtual circuit-multiplexed
(VC-multiplexed), logical link control (LLC), Network Layer Protocol Identifier
(NLPID), and serial (High-Level Data Link Control [HDLC]) encapsulations
as described in RFC 2364.
PPP-encapsulated ATM PVCs, unlike RFC 1483-encapsulated ATM
PVCs, can be dynamically bound to an interface; you can use the bind
authentication
command (in ATM PVC configuration mode) to dynamically
1 64/1543-CRA 119 1170/1 Uen K | 2012-12-04