VSP, Vendor-Specific Protocol |
Description | Glossary | RFCs | Publications | Obsolete RFCs |
Protocol suite: | PPP. |
PPP protocol: | 0x405B. |
Links: |
VSP is intended for use in situations where the implementation of a complete Network Layer Protocol is unnecessary, or where per-link signaling is required.
VSP header:
00 | 01 | 02 | 03 | 04 | 05 | 06 | 07 | 08 | 09 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Magic Number | |||||||||||||||||||||||||||||||
OUI | reserved | ||||||||||||||||||||||||||||||
Data ::: |
Magic Number. 32 bits.
Used to detect looped-back links. If the Magic-Number Option was not negotiated
by LCP, then this field MUST be cleared to 0.
Implementation of the LCP Magic-Number Option is RECOMMENDED.
OUI, Organizationally Unique Identifier.
24 bits.
Contains the OUI of the vendor.
The bits within the bytes are in canonical order with the most significant byte transmitted first.
reserved. 8 bits.
Must be cleared to zero on transmit and ignored on reception.
RFCs:
[RFC 3772] Point-to-Point Protocol (PPP) Vendor Protocol.
Description | Glossary | RFCs | Publications | Obsolete RFCs |