|
BACP
RFC2125 http://www.cis.ohio-state.edu/htbin/rfc/rfc2125.html
The Bandwidth Allocation Control Protocol
(BACP) is the associated control protocol for BAP. BAP can be
used to manage the number of links in a multi-link bundle. BAP
defines datagrams to coordinate adding and removing individual
links in a multi-link bundle, as well as specifying which peer
is responsible for which decisions regarding managing bandwidth
during a multi-link connection. BACP defines control parameters
for the BAP protocol to use.
The format of the BACP packet is shown in
the following illustration:
|
Code |
Identifier |
Length |
Data |
|
1 byte |
1 byte |
2 bytes |
variable |
| BACP
packet structure |
Code
Decimal value which indicates the type of BACP packet.
| 1 |
Configure-Request |
| 2 |
Configure-Ack |
| 3 |
Configure-Nak |
| 4 |
Configure-Reject |
| 5 |
Terminate-Request |
| 6 |
Terminate-Ack |
| 7 |
Code-Reject |
Identifier
Decimal value which aids in matching requests and replies.
Length
Length of the BACP packet, including the Code, Identifier, Length
and Data fields.
Data
Variable length field which may contain one or more configuration
options. The format of the BACP configuration options is as
follows:
|
Type |
Length |
Data |
Format
of BACP configuration options |
Type
One-byte indication of the type of the configuration option.
Length
Length of the configuration option
including the Type, Length and Data fields.
Data
Value of the Data field.
Interested in more
details about testing this protocol?
BCP
RFC1638 http://www.cis.ohio-state.edu/htbin/rfc/rfc1638.html
The Bridging Control Protocol (BCP) is responsible
for configuring the bridge protocol parameters on both ends
of the point-to-point link. BCP uses the same packet exchange
mechanism as the Link Control Protocol. BCP packets can not
be exchanged until PPP has reached the Network-Layer Protocol
phase. BCP packets received before this phase is reached are
discarded.
The format of the BCP packet is shown in
the following illustration:
|
Code |
Identifier |
Length |
Data |
|
1 byte |
1 byte |
2 bytes |
variable |
BCP
packet structure |
Code
Decimal value which indicates the type of BCP packet.
| 1 |
Configure-Request |
| 2 |
Configure-Ack |
| 3 |
Configure-Nak |
| 4 |
Configure-Reject |
| 5 |
Terminate-Request |
| 6 |
Terminate-Ack |
| 7 |
Code-Reject |
Identifier
Decimal value which aids in matching
requests and replies.
Length
Length of the BCP packet, including the Code, Identifier, Length
and Data fields.
Data
Variable length field which may contain one or more configuration
options. The format of the BCP configuration options is as follows:
|
Type |
Length |
Data |
|
Format of BCP configuration options |
Type
One-byte indication of the type of the configuration option.
| 1 |
Bridge-Identification |
| 2 |
Line-Identification |
| 3 |
MAC-Support |
| 4 |
Tinygram-Compression |
| 5 |
LAN-Identification |
| 6 |
MAC-Address |
| 7 |
Spanning-Tree-Protocol |
Length
Length of the configuration option including the Type, Length
and Data fields.
Data
Value of the Data field.
Interested in more
details about testing this protocol?
IPCP
RFC1332 http://www.cis.ohio-state.edu/htbin/rfc/rfc1332.html
The IP Control Protocol (IPCP) is responsible
for configuring the IP protocol parameters on both ends of the
point-to-point link. IPCP uses the same packet exchange mechanism
as the Link Control Protocol (LCP). IPCP packets may not be
exchanged until PPP has reached the Network-Layer Protocol phase.
Any IPCP packets received before this phase is reached are discarded.
The format of the IPCP packet is shown in
the following illustration:
|
Code |
Identifier |
Length |
Data |
|
1 byte |
1 byte |
2 bytes |
variable |
IPCP
packet structure |
Code
Decimal value which indicates the type of IPCP packet.
| 1 |
Configure-Request |
| 2 |
Configure-Ack |
| 3 |
Configure-Nak |
| 4 |
Configure-Reject |
| 5 |
Terminate-Request |
| 6 |
Terminate-Ack |
| 7 |
Code-Reject |
Identifier
Decimal value which aids in matching requests and replies.
Length
Length of the IPCP packet, including the Code, Identifier, Length
and Data fields.
Data
Variable length field which may contain one or more configuration
options. The format of the IPCP configuration options is as
follows:
|
Type |
Length |
Data |
Format
of IPCP configuration options |
Type
One-byte indication of the type of the configuration option.
| 1 |
IP Addresses - use of which is deprecated.
Use of 3 is preferred. |
| 2 |
IP Compression Protocol. |
| 3 |
IP Address - way to negotiate the IP address
to be used on the local end of the link. |
Length
Length of the configuration option including the Type, Length
and Data fields.
Data
Value of the Data field.
Interested in more
details about testing this protocol?
IPXCP
RFC1552
http://www.cis.ohio-state.edu/htbin/rfc/rfc1552.html
In order to establish communication over
a point-to-point link, each end of the PPP link must first send
LCP packets to configure and test the data link. After the link
has been established and optional facilities have been negotiated
as needed by the LCP, PPP may send IPXCP packets to choose and
configure the IPX network-layer protocol. Once IPXCP has reached
the Opened state, IPX datagrams can be sent over the link.
The format of the IPXCP packet is shown in
the following illustration:
|
Code |
Identifier |
Length |
Data |
|
1 byte |
1 byte |
2 bytes |
variable |
| IPXCP
packet structure |
Code
Decimal value which indicates
the type of IPXCP packet.
| 1 |
Configure-Request |
| 2 |
Configure-Ack |
| 3 |
Configure-Nak |
| 4 |
Configure-Reject |
| 5 |
Terminate-Request |
| 6 |
Terminate-Ack |
| 7 |
Code-Reject |
Identifier
Decimal value which aids in matching requests and replies.
Length
Length of the IPXCP packet, including the Code, Identifier,
Length and Data fields.
Data
Variable length field which may contain one or more configuration
options. The format of the IPXCP configuration options is as
follows:
|
Type |
Length |
Data |
Format
of IPXCP configuration options |
Type
One-byte indication of the type of the configuration option.
| 1 |
IPX Network number |
| 2 |
IPX Node number |
| 3 |
IPX Compression protocol |
| 4 |
IPX Routing protocol |
| 5 |
IPX Router name |
| 6 |
IPX Configuration complete |
Length
Length of the configuration option including the Type, Length
and Data fields.
Data
Value of the Data field.
Interested in more
details about testing this protocol?
CCP
RFC1962
http://www.cis.ohio-state.edu/htbin/rfc/rfc1962.html
The Compression Control Protocol (CCP) is
responsible for configuring the data compression algorithms
on both ends of the point-to-point link. It is also used to
signal a failure of the compression/decompression mechanism
in a reliable manner. CCP uses the same packet exchange mechanism
as the Link Control Protocol. CCP packets cannot be exchanged
until PPP has reached the Network-Layer Protocol phase. CCP
packets received before this phase is reached are discarded.
The format of the CCP packet is shown in
the following illustration:
| Code |
Identifier
|
Length |
Data |
| 1
byte |
1
byte |
2
bytes |
variable
|
|
CCP packet structure |
Code
Decimal value which indicates the
type of CCP packet.
| 1 |
Configure-Request |
| 2 |
Configure-Ack |
| 3 |
Configure-Nak |
| 4 |
Configure-Reject |
| 5 |
Terminate-Request |
| 6 |
Terminate-Ack |
| 7 |
Code-Reject |
| 14 |
Reset Request |
| 15 |
Reset-Ack |
Identifier
Decimal value which aids in matching requests and replies.
Length
Length of the CCP packet, including
the Code, Identifier, Length and Data fields.
Data
Variable length field which may
contain one or more configuration options. The format of the
CCP configuration options is as follows:
| Type |
Length |
Data |
| Format
of CCP configuration options |
Type
One-byte indication of the type
of the configuration option.
| 0 |
OUI |
| 1 |
Predictor Type 1 |
| 2 |
Predictor Type 2 |
| 3 |
Puddle Jumper |
| 16 |
Hewlett-Packard-PPC |
| 17 |
Stac Electronics LZS |
| 18 |
MicroSoft PPC |
| 19 |
Gandalf FZA |
| 20 |
V.42 bis Compression |
| 21 |
BSD LZW Compress |
| 23 |
LZS-DCP |
Length
Length of the configuration option
including the Type, Length and Data fields.
Data
Value of the Data field.
Interested in more details about testing
this protocol?
IPv6CP
RFC2023
http://www.cis.ohio-state.edu/htbin/rfc/rfc2023.html
The IPv6 PPP Control Protocol is responsible
for configuring, enabling and disabling the IPv6 protocol modules
on both ends of the point-to-point link.
(Compliant with IETF RFC2023 1996-10.)
The format of the IPv6CP packet is shown
in the following illustration:
| Code |
Identifier
|
Length |
Data |
| 1
byte |
1
byte |
2
bytes |
variable
|
|
IPv6CP packet structure |
Code
Decimal value which indicates the
type of IPv6CP packet.
| 1 |
Configure-Request |
| 2 |
Configure-Ack |
| 3 |
Configure-Nak |
| 4 |
Configure-Reject |
| 5 |
Terminate-Request |
| 6 |
Terminate-Ack |
| 7 |
Code-Reject |
Identifier
Decimal value which aids in matching
requests and replies.
Length
Length of the IPv6CP packet, including the Code, Identifier,
Length and Data fields.
Data
Variable length field which may contain one or more configuration
options. The format of the IPv6CP configuration options is as
follows:
| Type |
Length |
Data |
Format
of IPv6CP configuration options |
Type
One-byte indication of the type
of the configuration option.
| 1 |
Interface-Token |
| 2 |
IPv6-Compression-Protocol |
Length
Length of the configuration option
including the type, length and data fields.
Data
Value of the Data field.
 |
Graph of traffic
distribution by IPv6CP code field |
Interested in more details about testing
this protocol?
SNACP
RFC2043
http://www.cis.ohio-state.edu/htbin/rfc/rfc2043.html
The SNA PPP Control Protocol (SNACP) is responsible
for configuring, enabling, and disabling SNA on both ends of
the point-to-point link. Note that there are actually two SNA
Network Control Protocols; one for SNA over LLC 802.2 and another
for SNA without LLC 802.2. These SNA NCPs are negotiated separately
and independently of each other. In order to establish communications
over a point-to-point link, each end of the PPP link must first
send LCP packets to configure and test the data link. After
the link has been established and optional facilities have been
negotiated as needed by the LCP, PPP must send SNACP packets
to choose and configure the SNA network-layer protocol. Once
SNACP has reached the opened state, SNA datagrams can be sent
over the link.
(Compliant with IETF RFC2043, Oct 1996.)
The format of the SNACP packet is shown in
the following illustration:
| Code |
Identifier
|
Length |
Data |
| 1
byte |
1
byte |
2
bytes |
variable
|
|
SNACP packet structure |
Code
Decimal value which indicates the
type of SNACP packet.
| 1 |
Configure-Request |
| 2 |
Configure-Ack |
| 3 |
Configure-Nak |
| 4 |
Configure-Reject |
| 5 |
Terminate-Request |
| 6 |
Terminate-Ack |
| 7 |
Code-Reject |
Identifier
Decimal value which aids in matching
requests and replies.
Length
Length of the SNACP packet, including the Code, Identifier,
Length and Data fields.
Data
Variable length field.
Interested in more details about testing
this protocol?
BVCP
RFC1763
http://www.cis.ohio-state.edu/htbin/rfc/rfc1763.html
The PPP Banyan VINES Control Protocol (BVCP)
is responsible for configuring, enabling, and disabling the
VINES protocol modules on both ends of the point-to-point link.
BVCP uses the same packet exchange mechanism as the Link Control
Protocol (LCP).
(Compliant with IETF RFC1763, Mar 1995.)
The format of the BVCP packet is shown in
the following illustration:
| Code |
Identifier
|
Length |
Data |
| 1
byte |
1
byte |
2
byte |
variable
|
|
BVCP packet structure |
Code
Decimal value which indicates the
type of BVCP packet.
| 1 |
Configure-Request |
| 2 |
Configure-Ack |
| 3 |
Configure-Nak |
| 4 |
Configure-Reject |
| 5 |
Terminate-Request |
| 6 |
Terminate-Ack |
| 7 |
Code-Reject |
Identifier
Decimal value which aids in matching requests and replies.
Length
Length of the BVCP packet, including the Code, Identifier,
Length and Data fields.
Data
Variable length field which may contain one or more configuration
options. The format of the BVCP configuration options is as
follows:
| Type |
Length |
Data |
| Format
of BVCP configuration options |
Type
One-byte indication of the type of the configuration option.
| 1 |
BV-NS-RTP-Link-Type |
| 2 |
BV-FRP (fragmentation protocol) |
| 3 |
BV-RTP |
| 4 |
BV-Suppress-Broadcast |
Length
Length of the configuration option including the type, length
and data fields.
Data
Value of the data field.
Interested in more details about testing
this protocol?
NBFCP
RFC2097 http://www.cis.ohio-state.edu/htbin/rfc/rfc2097.html
The PPP NetBIOS Frames Control Protocol (NBFCP)
is a network control protocol responsible for establishing and
configuring the NBF protocol over PPP. The NBFCP protocol is
only applicable to an end system connecting to a peer system,
or the LAN to which the peer system is connected.
(Compliant with IETF RFC2097, Jan 1997.)
The format of the NBFCP packet is shown in
the following illustration:
| Code |
Identifier
|
Length |
Data |
| 1
byte |
1
byte |
2
bytes |
variable
|
|
NBFCP packet structure |
Code
Decimal value which indicates the type of NBFCP packet.
| 1 |
Configure-Request |
| 2 |
Configure-Ack |
| 3 |
Configure-Nak |
| 4 |
Configure-Reject |
| 5 |
Terminate-Request |
| 6 |
Terminate-Ack |
| 7 |
Code-Reject |
Identifier
Decimal value which aids in matching requests and replies.
Length
Length of the NBFCP packet, including the Code, Identifier,
Length and Data fields.
Data
Variable length field which may contain one or more configuration
options. The format of the NBFCP configuration options is as
follows:
| Type
|
Length |
Data |
|
Format of NBFCP configuration options |
Type
One-byte indication of the type of the configuration option.
| 1 |
Name-Projection |
| 2 |
Peer-Information |
| 3 |
Multicast-Filtering |
| 4 |
IEEE-MAC-Address-Required |
Length
Length of the configuration option including the Type, Length
and Data fields.
Data
Value of the data field.
 |
Graph of traffic
distribution by NBFCP code field |
Interested in more details about testing
this protocol?
1 2 3 4
5 
PPP Family Protocol Information
ATCP | BACP
| BAP | BCP
| BSD | BVCP
| CCP | CHAP
| DESE | DNCP
| ECP | IPCP
| IPHC | IPv6CP
| IPXCP | L2F
| L2TP | LCP
| LQR | LZS
| MPPC | MultiPPP
| NBFCP | OSINLCP
| PAP | PPP
| PPP-BPDU
| PPTP | SDCP
| SNACP
|
