blank.gif (43 bytes)

Church Of The
Swimming Elephant

Search:
PPP Numbers Connected: An Internet Encyclopedia
PPP Numbers

Up: Connected: An Internet Encyclopedia
Up: Requests For Comments

PPP Numbers

PPP Numbers

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 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".

Assigned PPP DLL Protocol Numbers

Value (in hex)  Protocol Name

0001		Padding Protocol
0003 to 001f    reserved (transparency inefficient)
0021            Internet Protocol
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            IP6 Header Compression
0051            KNX Bridging Data                          [ianp]
0053            Encryption                                [Meyer]
0055            Individual Link Encryption                [Meyer]
006f            Stampede Bridging
0071            BAP Bandwidth Allocation Protocol      [Richards]
0073            MP+ Protocol                              [Smith]
007d            reserved (Control Escape)               [RFC1661]
007f            reserved (compression inefficient)      [RFC1662]
00cf            reserved (PPP NLPID)
00fb            compression on single link in multilink group
00fd            1st choice compression
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]

4001            Cray Communications Control Protocol      [Stage]
4003            CDPD Mobile Network Registration Protocol [Quick]
4021            Stacker LZS                             [Simpson]

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]
806f            Stampede Bridging Control Protocol
8073            MP+ Control Protocol                          [Smith]
8071            BACP Bandwidth Allocation Control Protocol [Richards]
807d            Not Used - reserved                     [RFC1661]
80cf            Not Used - reserved                     [RFC1661]
80fb            compression on single link in multilink group control
80fd            Compression Control Protocol
80ff		Not Used - reserved                           [RFC1661]

8207            Cisco Discovery Protocol Control               [Sastry]
8209            Netcs Twin Routing                         [Korfmacher]
8235            Apple Client Server Protocol Control         [Ridenour]

c021            Link Control Protocol
c023            Password Authentication Protocol
c025            Link Quality Report
c027            Shiva Password Authentication Protocol
c029            CallBack Control Protocol (CBCP)
c081            Container Control Protocol                    [KEN]
c223            Challenge Handshake Authentication Protocol
c225            RSA Authentication Protocol                   [Narayana]
c227            Extensible Authentication Protocol            [Blunk]
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), [146]
the Compression Control Protocol (CCP), Internet Protocol Control
Protocol (IPCP), [147] 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
----       -----------
   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
  15     + Reset-Reply

* 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 [146] which are
distinguished by an 8 bit Type field.  These Types are assigned as
follows:

Type       Configuration Option
----       --------------------
   1       Maximum-Receive-Unit
   2       Async-Control-Character-Map
   3       Authentication-Protocol
   4       Quality-Protocol
   5       Magic-Number
   6       RESERVED
   7       Protocol-Field-Compression
   8       Address-and-Control-Field-Compression
   9       FCS-Alternatives
  10       Self-Describing-Pad
  11       Numbered-Mode
  12       Multi-Link-Procedure
  13       Callback
  14       Connect-Time
  15       Compound-Frames
  16       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                [Richards]

PPP AUTHENTICATION ALGORITHMS

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

Number     Name
------     ----------------------------
   0       Reserved                                    [RFC1334]
   1       Reserved                                    [RFC1334]
   2       Reserved                                    [RFC1334]
   3       Reserved                                    [RFC1334]
   4       Reserved                                    [RFC1334]
   5       MD5                                         [RFC1334]

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 [147] which are
distinguished by an 8 bit Type field.  These Types are assigned as
follows:

Type       Configuration Option
----       --------------------
   1       IP-Addresses (deprecated)
   2       IP-Compression-Protocol
   3       IP-Address

 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


REFERENCES

[RFC1334] Lloyd, B., and W. Simpson, "PPP Authentication Protocols",
          RFC 1334, L&A, Datdreamer, October 1992.

[RFC1661] Simpson, W., Editor, "The Point-to-Point Protocol (PPP)",
          STD 51, RFC 1661, Daydreamer, July 1994.

[RFC1662] Simpson, W., Editor, "PPP in HDLC-like Framing", STD 51, RFC
          1662, Daydreamer, July 1994.

[RFC1717] Sklower, K., B. LLoyd, G. McGregor, and D. Carr, "The PPP
          Multilink Protocol", RFC 1717, University of California
          Berkeley, Lloyd Internetworking, Newbridge Networks,
          November 1994.

[RFC1763] Senum, S., "The PPP Banyan Vines Control Protocol", RFC
          1763, DigiBoard, March 1995.

[RFC1877] Cobb, S., "PPP Internet Protocol Control Protocol Extensions
          for Name Server Addresses", RFC 1877, Microsoft, December
          1995.

PEOPLE

[Blunk] Larry Blunk, <ljb@merit.edu>, December 1995.

[ianp] <ianp@knxunix.knx.co.uk> November 1994.

[KEN]  <ken@funk.com>

[Korfmacher] Oliver Korfmacher, <okorf@netcs.com>, April 1995.

[Meyer] Gerry Meyer <gerry@spider.co.uk> December 1994.

[Quick] Frank Quick <fquick@qualcomm.com>

[Richards] Craig Richards, <crichards@shiva.com>, January 1996.

[Ridenour] Howard Ridenour, <RIDENOUR1@applelink.apple.com>, February 1995.

[Sastry] Arun Sastry, <asastry@cisco.com>, April 1995.

[Schneider] Kevin Schneider <kevin@adtran.com>

[Simpson] Willian Allen Simpson, <bsimpson@morningstar.com>, March 1995.

[Smith] Kevin Smith, Kevin@Smith.ascend.com, January 1996.

[Stage] Erling B. Stage <ebs@craycom.dk> October 1994.

[Narayana]  Badari Narayana <badari@ca.SJF.Novell.COM>

[Tackabury] Wayne Tackabury, <wayne@cayman.cayman.com>, January 1995.


[]


Connected: An Internet Encyclopedia
PPP Numbers

Cotse.Net

Protect yourself from cyberstalkers, identity thieves, and those who would snoop on you.
Stop spam from invading your inbox without losing the mail you want. We give you more control over your e-mail than any other service.
Block popups, ads, and malicious scripts while you surf the net through our anonymous proxies.
Participate in Usenet, host your web files, easily send anonymous messages, and more, much more.
All private, all encrypted, all secure, all in an easy to use service, and all for only $5.95 a month!

Service Details

 
.
www.cotse.com
Have you gone to church today?
.
All pages ©1999, 2000, 2001, 2002, 2003 Church of the Swimming Elephant unless otherwise stated
Church of the Swimming Elephant©1999, 2000, 2001, 2002, 2003 Cotse.com.
Cotse.com is a wholly owned subsidiary of Packetderm, LLC.

Packetderm, LLC
210 Park Ave #308
Worcester, MA 01609