RFC 3772 (rfc3772) - Page 1 of 10
Point-to-Point Protocol (PPP) Vendor Protocol
Alternative Format: Original Text Document
Network Working Group J. Carlson
Request for Comments: 3772 Sun Microsystems
Category: Standards Track R. Winslow
L-3 Communications
May 2004
Point-to-Point Protocol (PPP) Vendor Protocol
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract
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.
1. Introduction
PPP's [1] Vendor Extensions [3] defines a general-purpose mechanism
for the negotiation of various vendor-proprietary options and
extensions to the kinds of control messages that may be sent via the
Code field.
Some implementors may want to define proprietary network and control
protocols in addition to the already-described features. While it
would be possible for such an implementor to use the existing LCP
Vendor-Specific Option to enable the use of the proprietary protocol,
this staged negotiation (enable via LCP, then negotiate via some
locally-assigned protocol number) suffers from at least three
problems:
Carlson & Winslow Standards Track