RFC 3817: Layer 2 Tunneling Protocol (L2TP) Active Discovery Relay for PPP over Ethernet (PPPoE)
In plain English — editorial summary, not part of the RFC
The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. Layer Two Tunneling Protocol (L2TP), facilitates the tunneling of PPP packets across an intervening packet-switched network. And yet a third protocol, PPP over Ethernet (PPPoE) describes how to build PPP sessions and to encapsulate PPP packets over Ethernet. L2TP Active Discovery Relay for PPPoE describes a method to relay Active Discovery and Service Selection functionality from PPPoE over the reliable control channel within L2TP. Two new L2TP control message types and associated PPPoE-specific Attribute Value Pairs (AVPs) for L2TP are defined. This relay mechanism provides enhanced integration of a specific feature in the PPPoE tunneling protocol with L2TP. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3817
- Published
- June 2004
- Authors
- W. Townsley; R. da Silva
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3931Layer Two Tunneling Protocol - Version 3 (L2TPv3)Updated
March 2005
- RFC 3573Signalling of Modem-On-Hold status in Layer 2 Tunneling Protocol (L2TP)Current
July 2003
- RFC 3438Layer Two Tunneling Protocol (L2TP) Internet Assigned Numbers Authority (IANA) Considerations UpdateCurrent
December 2002
- RFC 3145L2TP Disconnect Cause InformationCurrent
July 2001
- RFC 3070Layer Two Tunneling Protocol (L2TP) over Frame RelayCurrent
February 2001
- RFC 7177Transparent Interconnection of Lots of Links (TRILL): AdjacencyUpdated
May 2014
- RFC 3772Point-to-Point Protocol (PPP) Vendor ProtocolCurrent
May 2004
- RFC 3748Extensible Authentication Protocol (EAP)Updated
June 2004
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?