PPP Numbers

- Assigned PPP DLL Protocol Numbers

- Network Layer Numbers
- LCP Layer Numbers
- NCP Layer Numbers

- PPP LCP AND IPCP CODES
- PPP LCP Configuration Option Types
- PPP CCP Configuration option Types
- PPP Authentication Algorithms
- PPP IPCP Configuration Option Types

POINT-TO-POINT PROTOCOL FIELD ASSIGNMENTS

PPP DLL PROTOCOL NUMBERS

The Point-to-Point Protocol (PPP) Data Link Layer [146,147,175] contains a 16 bit Protocol field to identify the encapsulated protocol. The Protocol field is consistent with the ISO 3309 (HDLC) extension mechanism for Address fields. All Protocols MUST be assigned such that the least significant bit of the most significant octet equals "0", and the least significant bit of the least significant octet equals "1".

- Network Layer Numbers

`

Value (in hex) Protocol Name

`
`---------------------------------------------------------------------`
`0001 Padding Protocol`
`0003 to 001f reserved (transparency inefficient)`
`0021 Internet Protocol version 4`
`0023 OSI Network Layer`
`0025 Xerox NS IDP`
`0027 DECnet Phase IV`
`0029 AppleTalk`
`002b Novell IPX`
`002d Van Jacobson Compressed TCP/IP`
`002f Van Jacobson Uncompressed TCP/IP`
`0031 Bridging PDU`
`0033 Stream Protocol (ST-II)`
`0035 Banyan Vines`
`0037 reserved (until 1993)`
`0039 AppleTalk EDDP`
`003b AppleTalk SmartBuffered`
`003d Multi-Link [RFC1717]`
`003f NETBIOS Framing`
`0041 Cisco Systems`
`0043 Ascom Timeplex`
`0045 Fujitsu Link Backup and Load Balancing (LBLB)`
`0047 DCA Remote Lan`
`0049 Serial Data Transport Protocol (PPP-SDTP)`
`004b SNA over 802.2`
`004d SNA`
`004f Pv6 Header Compression`
`0051 KNX Bridging Data [ianp]`
`0053 Encryption [Meyer]`
`0055 Individual Link Encryption [Meyer]`
`0057 Internet Protocol version 6 [Hinden]`
`006f Stampede Bridging`
`0071 Reserved [Fox]`
`0073 MP+ Protocol [Smith]`
`007d reserved (Control Escape) [RFC1661]`
`007f reserved (compression inefficient) [RFC1662]`
`0081 Reserved Until 20-Oct-2000 [IANA]`
`0083 Reserved Until 20-Oct-2000 [IANA]`
`00c1 NTCITS IPI [Ungar]`
`00cf reserved (PPP NLPID)`
`00fb single link compression in multilink [RFC1962]`
`00fd compressed datagram [RFC1962]`
`00ff reserved (compression inefficient)`

`02xx-1exx (compression inefficient)`
`0201 802.1d Hello Packets`
`0203 IBM Source Routing BPDU`
`0205 DEC LANBridge100 Spanning Tree`
`0207 Cisco Discovery Protocol [Sastry]`
`0209 Netcs Twin Routing [Korfmacher]`
`0231 Luxcom`
`0233 Sigma Network Systems`
`0235 Apple Client Server Protocol [Ridenour]`
`0281 Tag Switching - Unicast [Davie]`
`0283 Tag Switching - Multicast [Davie]`
`4001 Cray Communications Control Protocol [Stage]`
`4003 CDPD Mobile Network Registration Protocol [Quick]`
`4021 Stacker LZS [Simpson]`
`4023 RefTek Protocol [Banfill]`

- `NCP Layer Number`

`

8001-801f Not Used - reserved [RFC1661]

`
`8021 Internet Protocol Control Protocol`
`8023 OSI Network Layer Control Protocol`
`8025 Xerox NS IDP Control Protocol`
`8027 DECnet Phase IV Control Protocol`
`8029 Appletalk Control Protocol`
`802b Novell IPX Control Protocol`
`802d reserved`
`802f reserved`
`8031 Bridging NCP`
`8033 Stream Protocol Control Protocol`
`8035 Banyan Vines Control Protocol`
`8037 reserved till 1993`
`8039 reserved`
`803b reserved`
`803d Multi-Link Control Protocol`
`803f NETBIOS Framing Control Protocol`
`8041 Cisco Systems Control Protocol`
`8043 Ascom Timeplex`
`8045 Fujitsu LBLB Control Protocol`
`8047 DCA Remote Lan Network Control Protocol (RLNCP)`
`8049 Serial Data Control Protocol (PPP-SDCP)`
`804b SNA over 802.2 Control Protocol`
`804d SNA Control Protocol`
`804f IP6 Header Compression Control Protocol`
`8051 KNX Bridging Control Protocol [ianp]`
`8053 Encryption Control Protocol [Meyer]`
`8055 Individual Link Encryption Control Protocol [Meyer]`
`8057 IPv6 Control Protovol [Hinden]`
`806f Stampede Bridging Control Protocol`
`8073 MP+ Control Protocol [Smith]`
`8071 Reserved [Fox]`
`807d Not Used - reserved [RFC1661]`
`8081 Reserved Until 20-Oct-2000 [IANA]`
`8083 Reserved Until 20-Oct-2000 [IANA]`
`80c1 NTCITS IPI Control Protocol [Ungar]`
`80cf Not Used - reserved [RFC1661]`
`80fb single link compression in multilink control [RFC1962]`
`80fd Compression Control Protocol [RFC1962]`
`80ff Not Used - reserved [RFC1661]`
`8207 Cisco Discovery Protocol Control [Sastry]`
`8209 Netcs Twin Routing [Korfmacher]`
`8235 Apple Client Server Protocol Control [Ridenour]`
`8281 Tag Switching - Unicast [Davie]`
`8283 Tag Switching - Multicast [Davie]`

- LCP Layer Numbers

`

c021 Link Control Protocol

`
`c023 Password Authentication Protocol`
`c025 Link Quality Report`
`c027 Shiva Password Authentication Protocol`
`c029 CallBack Control Protocol (CBCP)`
`c02b BACP Bandwidth Allocation Control Protocol [RFC2125]`
`c02d BAP [RFC2125]`
`c081 Container Control Protocol [KEN]`
`c223 Challenge Handshake Authentication Protocol`
`c225 RSA Authentication Protocol [Narayana]`
`c227 Extensible Authentication Protocol [RFC2284]`
`c229 Mitsubishi Security Info Exch Ptcl (SIEP) [Seno]`
`c26f Stampede Bridging Authorization Protocol`
`c281 Proprietary Authentication Protocol [KEN]`
`c283 Proprietary Authentication Protocol [Tackabury]`
`c481 Proprietary Node ID Authentication Protocol [KEN]`

It is recommended that values in the "02xx" to "1exx" and "xx01" to "xx1f" ranges not be assigned, as they are compression inefficient. Protocol field values in the "0xxx" to "3xxx" range identify the network-layer protocol of specific datagrams, and values in the "8xxx" to "bxxx" range identify datagrams belonging to the associated Network Control Protocol (NCP), if any. Protocol field values in the "4xxx" to "7xxx" range are used for protocols with low volume traffic which have no associated NCP. Protocol field values in the "cxxx" to "exxx" range identify datagrams as Control Protocols (such as LCP).

- PPP LCP AND IPCP CODES

The Point-to-Point Protocol (PPP) Link Control Protocol (LCP), the Compression Control Protocol (CCP), Internet Protocol Control Protocol (IPCP), and other control protocols, contain an 8 bit Code field which identifies the type of packet. These Codes are assigned as follows:

`Code Packet Type`
`---------------------------------------------------------`
`0 Vendor Specific [RFC2153]`
`1 Configure-Request`
`2 Configure-Ack`
`3 Configure-Nak`
`4 Configure-Reject`
`5 Terminate-Request`
`6 Terminate-Ack`
`7 Code-Reject`
`8 * Protocol-Reject`
`9 * Echo-Request`
`10 * Echo-Reply`
`11 * Discard-Request`
`12 * Identification`
`13 * Time-Remaining`
`14 + Reset-Request [RFC1962]`
`15 + Reset-Reply [RFC1962]`

* LCP Only
+ CCP Only

- PPP LCP CONFIGURATION OPTION TYPES

The Point-to-Point Protocol (PPP) Link Control Protocol (LCP) specifies a number of Configuration Options which are distinguished by an 8 bit Type field. These Types are assigned as follows:

`Type Configuration Option`
`--------------------------------------------------------------`
`0 Vendor Specific [RFC2153]`
`1 Maximum-Receive-Unit`
`2 Async-Control-Character-Map`
`3 Authentication-Protocol`
`4 Quality-Protocol`
`5 Magic-Number`
`6 DEPRECATED (Quality-Protocol)`
`7 Protocol-Field-Compression`
`8 Address-and-Control-Field-Compression`
`9 FCS-Alternatives [RFC1570]`
`10 Self-Describing-Pad [RFC1570]`
`11 Numbered-Mode [RFC1663]`
`12 DEPRECATED (Multi-Link-Procedure)`
`13 Callback [RFC1570]`
`14 DEPRECATED (Connect-Time)`
`15 DEPRECATED (Compound-Frames)`
`16 DEPRECATED (Nominal-Data-Encapsulation)`
`17 Multilink-MRRU [RFC1717]`
`18 Multilink-Short-Sequence-Number-Header [RFC1717]`
`19 Multilink-Endpoint-Discriminator [RFC1717]`
`20 Proprietary [KEN]`
`21 DCE-Identifier [SCHNEIDER]`
`22 Multi-Link-Plus-Procedure [Smith]`
`23 Link Discriminator for BACP [RFC2125]`
`24 LCP-Authentication-Option [ Culbert]`
`25 Consistent Overhead Byte Stuffing (COBS) [Carlson]`
`26 Prefix elision [Bormann]`
`27 Multilink header format [Bormann]`

- IPV6CP CONFIGURATION OPTIONS

IPV6CP Configuration Options allow negotiation of desirable IPv6 parameters. IPV6CP uses the same Configuration Option format defined for LCP, with a separate set of Options. If a Configuration Option is not included in a Configure-Request packet, the default value for that Configuration Option is assumed.

1 Interface-Token [RFC2023]
2 IPv6-Compression-Protocol [RFC2023]

- PPP ECP CONFIGURATION OPTION TYPES

A one octet field is used in the Encryption Control Protocol (ECP) to indicate the configuration option type [RFC1968].

`ECP Option Configuration Type`
`-----------------------------------------------------------`
`0 OUI [RFC1968]`
`1 Deprecated (DESE) [Fox]`
`2 DESE [Kummert]`
`3 DESE-bis [Fox]`
`4-255 Unassigned`

PPP CCP CONFIGURATION OPTION TYPES

A one octet field is used in the Compression Control Protocol (CCP) to indicate the configuration option type [RFC1962].

`CCP Option Configuration Type`
`------------------------------------------------------------`
`0 OUI [RFC1962]`
`1 Predictor type 1 [RFC1962]`
`2 Rredictor type 2 [RFC1962]`
`3 Puddle Jumper [RFC1962]`
`4-15 unassigned`
`16 Hewlett-Packard PPC [RFC1962]`
`17 Stac Electronics LZS [RFC1974]`
`18 Microsoft PPC [RFC2118]`
`19 Gandalf FZA [RFC1962]`
`20 V.42bis compression [RFC1962]`
`21 BSD Compress [RFC1977]`
`22 unassigned`
`23 LZS-DCP [RFC1967]`
`24 MVRCA (Magnalink) [RFC1975]`
`25 DCE [RFC1976]`
`26 Deflate [RFC1979]`
`27-254 unassigned`
`255 Reserved [RFC1962]`

The unassigned values 4-15 are intended to be assigned to other freely available compression algorithms that have no license fees.

- PPP SDCP CONFIGURATION OPTIONS

A one octet field is used in the Compression Control Protocol (CCP) PPP Serial Data Transport Protocol (SDTP) to indicate the option type [RFC1963].

`SDCP Option Configuration Element`
`----------------------------------------------------------------------------------`
`1 Packet-Format [RFC1963]`
`2 Header-Type [RFC1963]`
`3 Length-Field-Present [RFC1963]`
`4 Multi-Port [RFC1963]`
`5 Transport-Mode [RFC1963]`
`6 Maximum-Frame-Size [RFC1963]`
`7 Allow-Odd-Frames [RFC1963]`
`8 FCS-Type [RFC1963]`
`9 Flow-Expiration-Time [RFC1963]`

Note that Option Types 5-8 are specific to a single port and require port numbers in their format. Option Types 6-8 are specific to the HDLC-Synchronous Transport-Mode.

- PPP AUTHENTICATION ALGORITHMS

A one octet field is used in the Challenge-Handshake Authentication Protocol (CHAP) to indicate which algorithm is in use [RFC1994].

`Number Name`
`------------------------------------------------------------------`
`0 Reserved [RFC1994]`
`1 Reserved [RFC1994]`
`2 Reserved [RFC1994]`
`3 Reserved [RFC1994]`
`4 Reserved [RFC1994]`
`5 CHAP with MD5 [RFC1994]`
`128 MS-CHAP [Crocker]`
`PPP LCP FCS-ALTERNATIVES`

The Point-to-Point Protocol (PPP) Link Control Protocol (LCP) FCS-Alternatives Configuration Option contains an 8-bit Options field which identifies the FCS used. These are assigned as follows:

`Bit FCS`
`-----------------------------------------------------------------`
`1 Null FCS`
`2 CCITT 16-Bit FCS`
`4 CCITT 32-bit FCS`

- PPP MULTILINK ENDPOINT DISCRIMINATOR CLASS

The Point-to-Point Protocol (PPP) Link Control Protocol (LCP) Multilink Endpoint Discriminator Option includes a Class field which identifies the address class, These are assigned as follows:

`Class Description`
`------------------------------------------------------------------------------`
`0 Null Class [RFC1717]`
`1 Locally Assigned [RFC1717]`
`2 Internet Protocol (IPv4) [RFC1717]`
`3 IEEE 802.1 global MAC address [RFC1717]`
`4 PPP Magic Number Block [RFC1717]`
`5 Public Switched Network Director Number [RFC1717]`

- PPP LCP CALLBACK OPERATION FIELDS

The Point-to-Point Protocol (PPP) Link Control Protocol (LCP) Callback Configuration Option contains an 8-bit Operations field which identifies the format of the Message. These are assigned as follows:

`Operation Description`
`----------------------------------------------------------------------------------`
`0 Location determined by user authentication.`
`1 Dialing string.`
`2 Location identifier.`
`3 E.164 number.`
`4 X.500 distinguished name.`
`5 unassigned`
`6 Location is determined during CBCP negotiation.`

- PPP IPCP CONFIGURATION OPTION TYPES

The Point-to-Point Protocol (PPP) Internet Protocol Control Protocol (IPCP) specifies a number of Configuration Options which are distinguished by an 8 bit Type field. These Types are assigned as follows:

`Type Configuration Option`
`---------------------------------------------------------------------------------`
`1 IP-Addresses (deprecated) [RFC1332]`
`2 IP-Compression-Protocol [RFC1332]`
`3 IP-Address [RFC1332]`
`4 Mobile-IPv4 [RFC2290]`
`129 Primary DNS Server Address [RFC1877]`
`130 Primary NBNS Server Address [RFC1877]`
`131 Secondary DNS Server Address [RFC1877]`
`132 Secondary NBNS Server Address [RFC1877]`

- PPP ATCP CONFIGURATION OPTION TYPES

The Point-to-Point Protocol (PPP) Apple Talk Control Protocol (ATCP) specifies a number of Configuration Options [RFC-1378] which are distinguished by an 8 bit Type field. These Types are assigned as follows:

`Type Configuration Option`
`---------------------------------------------------------------------`
`1 AppleTalk-Address`
`2 Routing-Protocol`
`3 Suppress-Broadcasts`
`4 AT-Compression-Protocol`
`5 Reserved`
`6 Server-information`
`7 Zone-information`
`8 Default-Router-Address`

- PPP OSINLCP CONFIGURATION OPTION TYPES

The Point-to-Point Protocol (PPP) OSI Network Layer Control Protocol (OSINLCP) specifies a number of Configuration Options [RFC1377] which are distinguished by an 8 bit Type field. These Types are assigned as follows:

`Type Configuration Option`
`--------------------------------------------------------`
`1 Align-NPDU`

- PPP BANYAN VINES CONFIGURATION OPTION TYPES

The Point-to-Point Protocol (PPP) Banyan Vines Control Protocol (BVCP) specifies a number of Configuration Options [RFC1763] which are distinguished by an 8 bit Type field. These Types are assigned as follows:

`Type Configuration Option`
`------------------------------------------------------------`
`1 BV-NS-RTP-Link-Type`
`2 BV-FRP`
`3 BV-RTP`
`4 BV-Suppress-Broadcast`

- PPP BRIDGING CONFIGURATION OPTION TYPES

The Point-to-Point Protocol (PPP) Bridging Control Protocol (BCP) specifies a number of Configuration Options which are distinguished by an 8 bit Type field. These Types are assigned as follows:

`Type Configuration Option`
`-------------------------------------------------------------`
`1 Bridge-Identification`
`2 Line-Identification`
`3 MAC-Support`
`4 Tinygram-Compression`
`5 LAN-Identification`
`6 MAC-Address`
`7 Spanning-Tree-Protocol`

- PPP BRIDGING MAC TYPES

The Point-to-Point Protocol (PPP) Bridging Control Protocol (BCP) contains an 8 bit MAC Type field which identifies the MAC encapsulated. These Types are assigned as follows:

`Type MAC`
`--------------------------------------------------------------------------------`
`0 Reserved`
`1 IEEE 802.3/Ethernet with cannonical addresses`
`2 IEEE 802.4 with cannonical addresses`
`3 IEEE 802.5 with non-cannonical addresses`
`4 FDDI with non-cannonical addresses`
`5-10 reserved`
`11 IEEE 802.5 with cannonical addresses`
`12 FDDI with cannonical addresses`

- PPP BRIDGING SPANNING TREE

The Point-to-Point Protocol (PPP) Bridging Control Protocol (BCP) Spanning Tree Configuration Option contains an 8-bit Protocol field which identifies the spanning tree used. These are assigned as follows:

`Protocol Spanning Tree`
`------------------------------------------------------------------------------------`
`0 Null - no spanning tree protocol supported`
`1 IEEE 802.1D spanning tree protocol`
`2 IEEE 802.1G extended spanning tree protocol`
`3 IBM source route spanning tree protocol`
`4 DEC LANbridge 100 spanning tree protocol`

- PPP INTERNETWORK PACKET EXCHANGE CONTROL PROTOCOL (IPXCP)

IPXCP CONFIGURATION OPTIONS

`Option Description Reference`
`----------------------------------------------------------------------------------`
`1 IPX-Network-Number [RFC1552]`
`2 IPX-Node-Number [RFC1552]`
`3 IPX-Compression-Protocol [RFC1552]`
`4 IPX-Routing-Protocol [RFC1552]`
`5 IPX-Router-Name [RFC1552]`
`6 IPX-Configuration-Complete [RFC1552]`

- IPX COMPRESSION PROTOCOL VALUES

`

Value Protocol Reference

`
`-----------------------------------------------------------------------`
`2 Telebit Compressed IPX [Fox]`
`235 Shiva Compressed NCP/IPX [Fox]`

- IPX-ROUTING-PROTOCOL OPTIONS

`

Value Protocol Reference

`
`-----------------------------------------------------------`
`0 No routing protocol required [RFC1552]`
`1 RESERVED [RFC1552]`
`2 Novell RIP/SAP required [RFC1552]`
`4 Novell NLSP required [RFC1552]`
`5 Novell Demand RIP required [RFC1582]`
`6 Novell Demand SAP required [RFC1582]`
`7 Novell Triggered RIP required [Edmonstone]`
`8 Novell Triggered SAP required [Edmonstone]`

- NBFCP Configuration Options

NBFCP Configuration Options [RFC 2097] allow modifications to the standard characteristics of the network-layer protocol to be negotiated. If a Configuration Option is not included in a Configure-Request packet, the default value for that Configuration Option is assumed.

NBFCP uses the same Configuration Option format defined for LCP, with a separate set of Options.
Current values are assigned as follows:

1 Name-Projection
2 Peer-Information
3 Multicast-Filtering
4 IEEE-MAC-Address-Required

- PPP EAP REQUEST/RESPONSE TYPES

A one octet field is used in the Extensible Authentication Protocol (EAP) to indicate the function and structure of EAP Request and Response packets [RFC2284].

`Type Description`
`-----------------------------------------------------------------`
`1 Identity [RFC2284]`
`2 Notification [RFC2284]`
`3 Nak (Response only) [RFC2284]`
`4 MD5-Challenge [RFC2284]`
`5 One Time Password (OTP) [RFC2289]`
`6 Generic Token Card [RFC2284]`
`7`
`8`
`9 RSA Public Key Authentication [Whelan]`
`10 DSS Unilateral [Nace]`
`11 KEA [Nace]`
`12 KEA-VALIDATE [Nace]`
`13 EAP-TLS [Adoba]`
`14 Defender Token (AXENT) [Rosselli]`

- PPP VENDOR SPECIFIC OUI OPTIONS

There are some provisions in some PPP message formats for vendor specific options to be identified by the Organisationally Unique Identifier (OUI), namely the first three octets of a Vendor's Ethernet address assigned by IEEE 802 [RFC1968. RFC2153]. These are listed in the "ethernet-numbers" file (see http://www.iana.org/in-notes/iana/assignments/ethernet-numbers).

All contents copyright © 1999 ZyXEL Communications Corporation.