RFC 3772: Point-to-Point Protocol (PPP) Vendor Protocol
In plain English — editorial summary, not part of the RFC
The Point-to-Point Protocol (PPP) defines a Link Control Protocol (LCP) and a method for negotiating the use of multi-protocol traffic over point-to-point links. The PPP Vendor Extensions document adds vendor-specific general-purpose Configuration Option and Code numbers. This document extends these features to cover vendor-specific Network, Authentication, and Control Protocols. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3772
- Published
- May 2004
- Authors
- J. Carlson; R. Winslow
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2716PPP EAP TLS Authentication ProtocolObsoleted
October 1999
- RFC 2484PPP LCP Internationalization Configuration OptionCurrent
January 1999
- RFC 3336PPP Over Asynchronous Transfer Mode Adaptation Layer 2 (AAL2)Current
December 2002
- RFC 2661Layer Two Tunneling Protocol "L2TP"Updated
August 1999
- RFC 2118Microsoft Point-To-Point Compression (MPPC) ProtocolCurrent
March 1997
- RFC 1976PPP for Data Compression in Data Circuit-Terminating Equipment (DCE)Current
August 1996
- 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
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?