RFC 2153 (rfc2153) - Page 3 of 6

PPP Vendor Extensions

Alternative Format: Original Text Document
< Previous
Next >
RFC 2153                 PPP vendor extensions                  May 1997


   Value(s)

      Zero or more octets.  The details are implementation specific.


2.  Configuration Options

   The Configuration Option format and basic options are already defined
   for LCP [1].

   Up-to-date values of the LCP Option Type field are specified in the
   most recent "Assigned Numbers" [2].  This document concerns the
   following values:

       0      Vendor-Specific



2.1.  Vendor-Specific Option

   Description

      Some implementors might not need nor want to publish their
      proprietary algorithms and attributes.  This mechanism is
      available to specify these without encumbering the IANA with
      proprietary number requests.

      Before accepting this option, the implementation must verify that
      the Organizationally Unique Identifier and Kind specify a known
      mechanism, and that any vendor specific negotiation values are
      fully understood.

   Rationale:

      This is defined as general feature of all PPP Control Protocols,
      to avoid future conflicts in vendor secretly self-assigned Type
      numbers.

   A summary of the Vendor-Specific Configuration Option format is shown
   below.  The fields are transmitted from left to right.

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |    Length     |              OUI
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
          ...      |     Kind      |  Value(s) ...
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-





Simpson                      Informational
< Previous
Next >