Provided by Colasoft Co., Ltd.

PPP ( Point-to-Point Protocol )

Home > Protocols > PPP Update: 2005-11-10 16:13:09    I have words to say about this protocol
On this page
SUMMARY
Protocol : Point-to-Point Protocol
Protocol suite : TCP/IP
Layer : Data Link Layer
Related protocols : PPPoE,
PPPoA,
SLIP,
CHAP,
PAP,
HDLC,
LCP,
NCP,
IPCP,
L2TP,
IP,
IPX,
DECnet
Working groups : PPPEXT, Point-to-Point Protocol Extensions
DESCRIPTION
PPP (Point-to-Point Protocol) is designed for simple links which transport packets between two peers. These links provide full-duplex simultaneous bi-directional operation, and are assumed to deliver packets in order. It is intended that PPP provide a common solution for easy connection of a wide variety of hosts, bridges and routers.
  • Encapsulation

  • The PPP encapsulation provides for multiplexing of different network-layer protocols simultaneously over the same link. Only 8 additional octets are necessary to form the encapsulation when used within the default HDLC-like framing. To support high speed implementations, the default encapsulation uses only simple fields, only one of which needs to be examined for demultiplexing.

  • Link Control Protocol

  • In order to be sufficiently versatile to be portable to a wide variety of environments, PPP provides a Link Control Protocol (LCP). The LCP is used to automatically agree upon the encapsulation format options, handle varying limits on sizes of packets, detect a looped-back link and other common misconfiguration errors, and terminate the link.

  • Network Control Protocols

  • Point-to-Point links tend to exacerbate many problems with the current family of network protocols. For instance, assignment and management of IP addresses, which is a problem even in LAN environments, is especially difficult over circuit-switched point-to-point links (such as dial-up modem servers).

  • Configuration

  • It is intended that PPP links be easy to configure. By design, the standard defaults handle all common configurations. The implementor can specify improvements to the default configuration, which are automatically communicated to the peer without operator intervention.


PPP provides a method for transmitting datagrams over serial point-to-point links. PPP contains three main components:
  • A method for encapsulating datagrams over serial links. PPP uses the High-Level Data Link Control (HDLC) protocol as a basis for encapsulating datagrams over point-to-point links.


  • An extensible LCP to establish, configure, and test the data link connection.


  • A family of NCPs for establishing and configuring different network layer protocols. PPP is designed to allow the simultaneous use of multiple network layer protocols.


To establish communications over a point-to-point link, the originating PPP first sends LCP frames to configure and (optionally) test the data link. After the link has been established and optional facilities have been negotiated as needed by the LCP, the originating PPP sends NCP frames to choose and configure one or more network layer protocols. When each of the chosen network layer protocols has been configured, packets from each network layer protocol can be sent over the link. The link will remain configured for communications until explicit LCP or NCP frames close the link, or until some external event occurs

Here are some key PPP features, all of which are lacking in SLIP:
  • Address Notification

  • Address Notification allows a server to inform a dial-up client of its IP address for that link, but the mechanism is powerful enough for clients to request IP addresses and supports fallback configurations. SLIP required the user to configure this information manually.

  • Authentication

  • Authentication is available as an option, either with the Password Authentication Protocol (PAP), or the Challenge-Handshake Authentication Protocol (CHAP).

  • Authentication

  • Authentication can interoperate on the same link, simply by running additional NCPs. For example, both IP and IPX traffic can share a PPP link.

  • Link Monitoring

  • Link Monitoring facilities include a link-level echo facility which can periodically check link operation.


PPP uses the principles, terminology, and frame structure of the International Organization for Standardization (ISO) HDLC procedures, as modified by ISO 3309:1984/PDAD1 "Addendum 1: Start/Stop Transmission." ISO 3309-1979 specifies the HDLC frame structure for use in synchronous environments. ISO 3309:1984/PDAD1 specifies proposed modifications to ISO 3309-1979 to allow its use in asynchronous environments. The PPP control procedures use the definitions and control field encodings standardized in ISO 4335-1979 and ISO 4335-1979/Addendum 1-1979.


PPP Packet Format

1 byte

1 byte

1 byte

2 bytes

variable

2 or 4 bytes

Flag

Address

Control

Protocol

Information

FCS


  • Flag

  • A single byte that indicates the beginning or end of a frame. The flag field consists of the binary sequence 01111110.

  • Address

  • HDLC broadcast address. PPP does not assign individual station addresses. The value of this field is always set to FF Hex.

  • Control

  • HDLC command for Unnumbered Information (UI) with the Poll/Final bit set to zero. The value of this field is always set to 03 Hex. Frames containing any other value in this field are discarded.

  • Protocol

  • 8 or 16 bits. The structure of this field is consistent with the ISO 3309 extension mechanism for address fields. All valid protocols have the least significant bit of the least significant byte set to 1 and the least significant bit of the most significant byte is cleared to 0. Frames that do not comply are treated as having an unrecognized protocol.
    ValueProtocolReferences
    0x0XXX - 0x3XXX, Network layer protocols.
    0x0001Padding Protocol.
    0x0003ROHC small-CID.A small CID with the value 0 is represented using zero bits.
    0x0005ROHC large-CID.
    0x0007
    -
    0x001F
    Reserved (transparency inefficient).
    0x0021IP, Internet Protocol.
    0x0023OSI Network Layer.
    0x0025Xerox NS IDP.
    0x0027DECnet Phase IV.
    0x0029Appletalk.
    0x002BIPX.
    0x002DVan Jacobson Compressed TCP/IP.
    0x002FVan Jacobson Uncompressed TCP/IP.
    0x0031Bridging PDU.
    0x0033ST-II, Stream Protocol.
    0x0035Banyan Vines.
    0x0037Reserved (until 1993).
    0x0039AppleTalk EDDP.
    0x003BAppleTalk SmartBuffered.
    0x003DMP, PPP Multilink Protocol.
    0x003FNETBIOS Framing.
    0x0041Cisco Systems.
    0x0043Ascom Timeplex.
    0x0045LBLB, Fujitsu Link Backup and Load Balancing.
    0x0047DCA Remote Lan.
    0x0049SDTP, PPP Serial Data Transport Protocol.
    0x004BSNA over 802.2.
    0x004DSNA.
    0x004FIP6 Header Compression.
    0x0051KNX Bridging Data.
    0x0053Encryption.
    0x0055Individual Link Encryption.
    0x0057IPv6, Internet Protocol version 6.
    0x0059PPP Multiplexing.The method sends multiple PPP encapsulated packets in a single PPP frame.
    0x005BVSNP, Vendor-Specific Network Protocol.
    0x0061RTP IPHC Full Header.RTP IPHC communicates the uncompressed IP header plus any following headers and data to establish the uncompressed header state in the decompressor for a particular context.
    0x0063RTP IPHC Compressed TCP.It indicates a packet with a compressed TCP header, containing a CID, a flag octet identifying what fields have changed, and the changed fields encoded as the difference from the previous value.
    0x0065RTP IPHC Compressed Non TCP.Indicates a non-TCP packet with a compressed header.
    0x0067RTP IPHC Compressed UDP 8.It communicates the IP and UDP headers compressed to 8 bytes, followed by any subsequent headers (possibly RTP) in uncompressed form, plus data.
    0x0069RTP IPHC Compressed RTP 8.Indicates that the RTP header is compressed along with the IP and UDP headers.
    0x006FStampede Bridging.
    0x0071Reserved.
    0x0073MP+, PPP Ascend's Multilink Protocol Plus.
    0x007DReserved (Control Escape).
    0x007FReserved (compression inefficient).
    0x0081Reserved (until 20-Oct-2000).
    0x0083Reserved (until 20-Oct-2000).
    0x00C1NTCITS IPI.
    0x00CFReserved (PPP NLPID).
    0x00FBSingle link compression in multilink.
    0x00FDCompressed datagram.
    0x00FFReserved (compression inefficient).
    0x02XX - 0x1EXX, Compression inefficient protocols.
    0x0201802.1d Hello Packets.
    0x0203IBM Source Routing BPDU.
    0x0205DEC LANBridge100 Spanning Tree.
    0x0207Cisco Discovery Protocol.
    0x0209Netcs Twin Routing.
    0x020BSTP, Scheduled Transfer Protocol.
    0x020DEDP, Extreme Discovery Protocol.
    0x0211OSCP, Optical Supervisory Channel Protocol.
    0x0213OSCP, Optical Supervisory Channel Protocol.
    0x0231Luxcom.
    0x0233Sigma Network Systems.
    0x0235Apple Client Server Protocol.
    0x0281Multi-Protocol Label Switching, unicast.
    0x0283Multi-Protocol Label Switching, multicast.
    0x0285IEEE p1284.4 standard - data packets.
    0x0287ETSI TETRA Network Protocol Type 1.
    0x0289Multichannel Flow Treatment Protocol.
    0x2063RTP IPHC Compressed TCP No Delta.Indicates a packet with a compressed TCP header where all fields that are normally sent as the difference to the previous value are instead sent as-is.
    0x2065RTP IPHC Context State.Indicates a special packet sent from the decompressor to the compressor to communicate a list of context IDs for which synchronization has or may have been lost.
    0x2067RTP IPHC Compressed UDP 16.Communicates the IP and UDP headers compressed to 16 bytes, followed by any subsequent headers (possibly RTP) in uncompressed form, plus data.
    0x2069RTP IPHC Compressed RTP 16.Indicates that the RTP header is compressed along with the IP and UDP headers.
    0x4XXX - 0x7XXX, Low volume traffic without an associated NCP.
    0x4001Cray Communications Control Protocol.
    0x4003CDPD Mobile Network Registration Protocol.
    0x4005Expand accelerator protocol.
    0x4007ODSICP NCP.
    0x4021LZS, PPP Stac LZS Compression Protocol.
    0x4023RefTek Protocol.
    0x4025Fibre Channel.
    0x4027EMIT Protocols.
    0x405BVSP, Vendor-Specific Protocol.
    0x8XXX - 0xBXXX, Network Control Protocols.
    0x8001
    -
    0x801F
    Reserved.
    0x8021IPCP, PPP Internet Protocol Control Protocol.
    0x8023OSINLCP, PPP OSI Network Layer Control Protocol.
    0x8025XNSCP, PPP XNS IDP Control Protocol.
    0x8027DNCP, DECnet Phase IV Control Protocol.
    0x8029ATCP, PPP AppleTalk Control Protocol.
    0x802BIPXCP, PPP IPX Control Protocol.
    0x802DReserved.
    0x802FReserved.
    0x8031BCP, PPP Bridging Control Protocol.
    0x8033Stream Protocol Control Protocol.
    0x8035BVCP, Banyan Vines Control Protocol.
    0x8037Reserved (until 1993).
    0x8039Reserved.
    0x803BReserved.
    0x803DMulti-Link Control Protocol.
    0x803FNBFCP, PPP NetBIOS Frames Control Protocol.
    0x8041PPP-LEX, PPP LAN extension protocol.
    0x8043Ascom Timeplex.
    0x8045Fujitsu LBLB Control Protocol.
    0x8047RLNCP, DCA Remote Lan Network Control Protocol.
    0x8049SDCP, PPP Serial Data Control Protocol.
    0x804BSNACP, SNA over 802.2 Control Protocol.
    0x804DSNACP, SNA Control Protocol.
    0x804FIP6 Header Compression Control Protocol.
    0x8051KNX Bridging Control Protocol.
    0x8053ECP, PPP Encryption Control Protocol.
    0x8055Individual Link Encryption Control Protocol.
    0x8057IPV6CP, PPP IPv6 Control Protocol.
    0x8059PPP Multiplexing Control Protocol.
    0x805BVSNCP, Vendor-Specific Network Control Protocol.
    0x806FStampede Bridging Control Protocol.
    0x8071Reserved.
    0x8073MP+ Control Protocol.
    0x807DReserved.
    0x8081Reserved (until 20-Oct-2000).
    0x8083Reserved (until 20-Oct-2000).
    0x80C1NTCITS IPI Control Protocol.
    0x80CFReserved.
    0x80FBCompression on single link in multilink group control.
    0x80FDCCP, PPP Compression Control Protocol.
    0x80FFReserved (not used).
    0x8207Cisco Discovery Protocol Control.
    0x8209Netcs Twin Routing.
    0x820BSTP, Control Protocol.
    0x820DEDPCP, Extreme Discovery Protocol Control Protocol.
    0x8235Apple Client Server Protocol Control.
    0x8281MPLSCP, MPLS Control Protocol.
    0x8283Tag Switching - Multicast.
    0x8285IEEE p1284.4 standard - Protocol Control.
    0x8287ETSI TETRA NSP1 Control Protocol.
    0x8289Multichannel Flow Treatment Protocol.
    0xCXXX - 0xFXXX, Link Control Protocols.
    0xC021LCP, Link Control Protocol.
    0xC023PAP, Password Authentication Protocol.
    0xC025Link Quality Report.
    0xC027SPAP, Shiva Password Authentication Protocol.
    0xC029CBCP, CallBack Control Protocol.
    0xC02BBACP, PPP Bandwidth Allocation Control Protocol.
    0xC02DBAP, PPP Bandwidth Allocation Protocol.
    0xC05BVSAP, Vendor-Specific Authentication Protocol.
    0xC081Container Control Protocol.
    0xC223CHAP, Challenge Handshake Authentication Protocol.
    0xC225RSA Authentication Protocol.
    0xC227EAP, Extensible Authentication Protocol.
    0xC229SIEP, Mitsubishi Security Info Exch Protocol.
    0xC26FStampede Bridging Authorization Protocol.
    0xC281Proprietary Authentication Protocol.
    0xC283Proprietary Authentication Protocol.
    0xC481Proprietary Node ID Authentication Protocol.

  • Information

  • Higher-level protocol data. Zero or more bytes that contain the datagram for the protocol specified in the protocol field. The end of the information field is found by locating the closing flag sequence and allowing 2 bytes for the FCS field. The default maximum length
    of the information field is 1,500 bytes. By prior agreement, consenting PPP implementations can use other values for the maximum information field length.

  • FCS

  • Value of the frame checksum calculation. PPP verifies the contents of the FCS field upon receipt of the packet.



PPP Link Operation
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.

  • Phase Diagram

  • In the process of configuring, maintaining and terminating the point-to-point link, the PPP link goes through several distinct phases which are specified in the following simplified state diagram:



+------+ +-----------+ +--------------+
| | UP | | OPENED | | SUCCESS/NONE
| Dead |------->| Establish |---------->| Authenticate |--+
| | | | | | |
+------+ +-----------+ +--------------+ |
^ | | |
| FAIL | FAIL | |
+<--------------+ +----------+ |
| | |
| +-----------+ | +---------+ |
| DOWN | | | CLOSING | | |
+------------| Terminate |<---+<----------| Network |<-+
| | | |
+-----------+ +---------+

Top of Page

EXAMPLES

Top of Page


PROTOCOL RELATIONS
Parent layer
Child layer
PPPoE Session
GRE
PPP
Padding
1st Choice Compression
IP
IP Control Protocol
Link Control Protocol
Password Authentication Protocol
Link Quality Report
Challenge Handshake
Top of Page

GLOSSARY
CHAP
CHAP (Challenge-Handshake Authentication Protocol) is an authentication protocol used for remote logon, usually between a client and server or Web browser and Web server. Both the sender and peer share a predefined secret. The peer concatenates the random value (or nonce), the ID and the secret and calculates a one-way hash using MD5. The hash value is sent to the authenticator, which in turn builds that same string on its side, calculates the MD5 sum itself and compares the result with the value received from the peer. If the values match, the peer is authenticated.

By transmitting only the hash, the secret can't be reverse-engineered. The ID value is increased with each CHAP dialogue to protect against replay attacks.

HDLC
HDLC (High-Level Data Link Control) protocol which operates at the data link layer uses the services of a physical layer, and provides either a best effort or reliable communications path between the transmitter and receiver. The HDLC protocol embeds information in a data frame that allows devices to control data flow and correct errors. HDLC is an ISO standard developed from the Synchronous Data Link Control (SDLC) standard proposed by IBM in the 1970's.

For any HDLC communications session, one station is designated primary and the other secondary. A session can use one of the following connection modes, which determine how the primary and secondary stations interact.
Normal unbalanced: The secondary station responds only to the primary station.

Asynchronous: The secondary station can initiate a message.
Asynchronous balanced: Both stations send and receive over its part of a duplex line. This mode is used for X.25 packet-switching networks.

The Link Access Procedure-Balanced (LAP-B) and Link Access Procedure D-channel (LAP-D) protocols are subsets of HDLC.

IPX
IPX(Internetwork Packet Exchange), a networking protocol used by the Novell NetWare operating systems. Like UDP/IP, IPX is a datagram protocol used for connectionless communications. Higher-level protocols, such as SPX and NCP, are used for additional error recovery services.

ISO
ISO (International Organization for Standardization) is a network of the national standards institutes of 146 countries, on the basis of one member per country, with a Central Secretariat in Geneva, Switzerland, that coordinates the system. ISO has defined a number of important computer standards, the most significant of which is perhaps OSI (Open Systems Interconnection), a standardized architecture for designing networks.

LCP
LCP (Link Control Protocol) is used to automatically agree upon the encapsulation format options, handle varying limits on sizes of packets, detect a looped-back link and other common misconfiguration errors, and terminate the link. The LCP checks the identity of the linked device and either accepts or rejects the peer device, determines the acceptable packet size for transmission, searches for errors in configuration and can terminate the link if the parameters are not satisfied. Data cannot be transmitted over the network until the LCP packet determines that the link is acceptable.

NCP
NCP (Novell NetWare Core Protocol) manages access to the primary NetWare server resources. Used to establish and configure one or more network layer protocols that will be used by the link. Protocol field values in the range of 0x8XXX to 0xBXXX identify packets belonging to the associated Network Control Protocol.

PAP
PAP (Password Authentication Protocol) is the most basic form of authentication, in which a user's name and password are transmitted over a network and compared to a table of name-password pairs. Typically, the passwords stored in the table are encrypted. The Basic Authentication feature built into the HTTP protocol uses PAP. The main weakness of PAP is that both the username and password are transmitted "in the clear" -- that is, in an unencrypted form. Contrast with CHAP.

Peer
The other end of a point-to-point link.

Peer-to-peer
Peer-to-peer(peer-to-peer architecture), or abbreviated P2P, a type of network in which each workstation has equivalent capabilities and responsibilities. This differs from client/server architectures, in which some computers are dedicated to serving the others. Peer-to-peer networks are generally simpler, but they usually do not offer the same performance under heavy loads.

Top of Page

REFERENCES
Related links:
                PPP Assigned numbers
RFCs:
[RFC 1332] The PPP Internet Protocol Control Protocol (IPCP).
                Obsoletes: RFC 1172.
[RFC 1377] The PPP OSI Network Layer Control Protocol (OSINLCP).
[RFC 1378] The PPP AppleTalk Control Protocol (ATCP).
[RFC 1471] The Definitions of Managed Objects for the Link Control Protocol of the Point-to-Point Protocol.
[RFC 1472] The Definitions of Managed Objects for the Security Protocols of the Point-to-Point Protocol.
[RFC 1473] The Definitions of Managed Objects for the IP Network Control Protocol of the Point-to-Point Protocol.
[RFC 1474] The Definitions of Managed Objects for the Bridge Network Control Protocol of the Point-to-Point Protocol.
[RFC 1547] Requirements for an Internet Standard Point-to-Point Protocol.
[RFC 1549] PPP in HDLC Framing.
[RFC 1552] The PPP Internetwork Packet Exchange Control Protocol (IPXCP).
[RFC 1570] PPP LCP Extensions.
                Updates: RFC 1548.
[RFC 1598] PPP in X.25.
[RFC 1618] PPP over ISDN.
[RFC 1619] PPP over SONET/SDH.
[RFC 1661] The Point-to-Point Protocol (PPP).
                STD: 51.
                Obsoletes: RFC 1548.
[RFC 1662] PPP in HDLC-like Framing.
                Obsoletes: RFC 1549.
[RFC 1663] PPP Reliable Transmission.
[RFC 1716] Towards Requirements for IP Routers.
[RFC 1762] The PPP DECnet Phase IV Control Protocol (DNCP).
                Obsoletes: RFC 1376.
[RFC 1763] The PPP Banyan Vines Control Protocol (BVCP).
[RFC 1764] The PPP XNS IDP Control Protocol (XNSCP).
[RFC 1812] Requirements for IP Version 4 Routers.
[RFC 1841] PPP Network Control Protocol for LAN Extension.
[RFC 1877] PPP Internet Protocol Control Protocol Extensions for Name Server Addresses.
[RFC 1915] Variance for The PPP Connection Control Protocol and The PPP Encryption Control Protocol.
[RFC 1934] Ascend's Multilink Protocol Plus (MP+).
[RFC 1962] The PPP Compression Control Protocol (CCP).
[RFC 1963] PPP Serial Data Transport Protocol (SDTP).
[RFC 1967] PPP LZS-DCP Compression Protocol (LZS-DCP).
[RFC 1968] The PPP Encryption Control Protocol (ECP).
[RFC 1973] PPP in Frame Relay.
[RFC 1974] PPP Stac LZS, Compression Protocol.
[RFC 1975] PPP Magnalink Variable Resource Compression.
[RFC 1976] PPP for Data Compression in Data Circuit-Terminating Equipment (DCE).
[RFC 1977] PPP BSD Compression Protocol.
[RFC 1978] PPP Predictor Compression Protocol.
[RFC 1979] PPP Deflate Protocol.
[RFC 1989] PPP Link Quality Monitoring.
                Obsoletes: RFC 1333.
[RFC 1990] The PPP Multilink Protocol (MP).
                Obsoletes: RFC 1717.
[RFC 1993] PPP Gandalf FZA Compression Protocol.
[RFC 1994] PPP Challenge Handshake Authentication Protocol (CHAP).
                Obsoletes: RFC 1334.
[RFC 2043] The PPP SNA Control Protocol (SNACP).
[RFC 2097] The PPP NetBIOS Frames Control Protocol (NBFCP).
[RFC 2118] Microsoft Point-To-Point Compression (MPPC) Protocol.
[RFC 2125] The PPP Bandwidth Allocation Protocol (BAP) The PPP Bandwidth Allocation Control Protocol (BACP).
[RFC 2153] PPP Vendor Extensions.
[RFC 2290] Mobile-IPv4 Configuration Option for PPP IPCP.
[RFC 2363] PPP Over FUNI.
[RFC 2364] PPP Over AAL5.
[RFC 2419] The PPP DES Encryption Protocol, Version 2 (DESE-bis).
                Obsoletes: RFC 1969.
[RFC 2420] The PPP Triple-DES Encryption Protocol (3DESE).
[RFC 2433] Microsoft PPP CHAP Extensions.
[RFC 2472] IP Version 6 over PPP.
                Obsoletes: RFC 2023.
[RFC 2484] PPP LCP Internationalization Configuration Option.
[RFC 2516] A Method for Transmitting PPP Over Ethernet (PPPoE).
[RFC 2615] PPP over SONET/SDH.
                Obsoletes: RFC 1619.
[RFC 2637] Point-to-Point Tunneling Protocol (PPTP).
[RFC 2686] The Multi-Class Extension to Multi-Link PPP.
                Describes LCP options 26 (Prefix elision) and 27 (Multilink header format).
[RFC 2687] PPP in a Real-time Oriented HDLC-like Framing.
[RFC 2688] Integrated Services Mappings for Low Speed Networks.
[RFC 2759] Microsoft PPP CHAP Extensions, Version 2.
[RFC 2794] Mobile IP Network Access Identifier Extension for IPv4.
                Updates: RFC 2290.
[RFC 2823] PPP over Simple Data Link (SDL) using SONET/SDH with ATM-like framing.
[RFC 2878] PPP Bridging Control Protocol (BCP).
                Obsoletes: RFC 1638.
[RFC 3032] MPLS Label Stack Encoding.
[RFC 3078] Microsoft Point-To-Point Encryption (MPPE) Protocol.
                Updates: RFC 2118.
[RFC 3153] PPP Multiplexing.
[RFC 3255] Extending Point-to-Point Protocol (PPP) over Synchronous Optical NETwork/Synchronous Digital Hierarchy (SONET/SDH) with virtual concatenation, high order and low order payloads.
[RFC 3241] Robust Header Compression (ROHC) over PPP.
                Updates: RFC 1332.
[RFC 3336] PPP Over Asynchronous Transfer Mode Adaptation Layer 2 (AAL2).
[RFC 3337] Class Extensions for PPP over Asynchronous Transfer Mode Adaptation Layer 2 (AAL2).
[RFC 3544] IP Header Compression over PPP.
                Obsoletes: RFC 2509.
[RFC 3748] Extensible Authentication Protocol (EAP).
                Obsoletes: RFC 2284.
[RFC 3772] Point-to-Point Protocol (PPP) Vendor Protocol.
[RFC 3818] IANA Considerations for the Point-to-Point Protocol (PPP).
                BCP: 88.
Obsolete RFCs:
[RFC 1134] The Point-to-Point Protocol: A Proposal for Multi-Protocol Transmission of Datagrams Over Point-to-Point Links.
                Obsoleted by: RFC 1171.
[RFC 1171] The Point-to-Point Protocol for the Transmission of Multi-Protocol Datagrams Over Point-to-Point Links.
                Obsoleted by: RFC 1331.
                Obsoletes: RFC 1134.
[RFC 1172] The Point-to-Point Protocol (PPP) Initial Configuration Options.
                Obsoleted by: RFC 1331, RFC 1332.
[RFC 1220] Point-to-Point Protocol Extensions for Bridging.
                Obsoleted by: RFC 1638.
[RFC 1331] The Point-to-Point Protocol (PPP) for the Transmission of Multi-protocol Datagrams over Point-to-Point Links.
                Obsoleted by: RFC 1548.
                Obsoletes: RFC 1171, RFC 1172.
[RFC 1333] PPP Link Quality Monitoring.
                Obsoleted by: RFC 1989.
[RFC 1334] PPP Authentication Protocols.
                Obsoleted by: RFC 1994.
[RFC 1376] The PPP DECnet Phase IV Control Protocol (DNCP).
                Obsoleted by: RFC 1762.
[RFC 1548] The Point-to-Point Protocol (PPP).
                Obsoleted by: RFC 1661.
                Obsoletes: RFC 1331.
[RFC 1549] PPP in HDLC Framing.
                Obsoleted by: RFC 1662.
[RFC 1619] PPP over SONET/SDH.
                Obsoleted by: RFC 2615.
[RFC 1638] PPP Bridging Control Protocol (BCP).
                Obsoleted by: RFC 2878.
                Obsoletes: RFC 1220.
[RFC 1717] The PPP Multilink Protocol (MP).
                Obsoleted by: RFC 1990.
[RFC 1969] The PPP DES Encryption Protocol (DESE).
                Obsoleted by: RFC 2419.
[RFC 2023] IP Version 6 over PPP.
                Obsoleted by: RFC 2472.
[RFC 2284] PPP Extensible Authentication Protocol (EAP).
                Obsoleted by: RFC 3748.
[RFC 2509] IP Header Compression over PPP.
                Obsoleted by: RFC 3544.
                


Top of Page

OTHER PROTOCOLS OF TCP/IP SUITE
AARP   RRP   RTP Video   RTP Audio   RTP   COPS   Gopher   HSRP   ICP   MPLS   IEEE 802.2   CIP   FTP - Data   FTP - Ctrl   IMAPS   IP Fragment   LDAPS   PUP   MSSQL   RSH   SQL   POP3s   RTELNET   RSVP   STP   VLAN   MSN   H.323   MSRDP   HTTPS   WINS   LPD   GTP   ICMPv6   POP   TELNET   H.225   VRRP   PIM   RARP   SAP   OSPF   RLOGIN   SCTP   SIP   RTCP   PPPoE   Mobile IP   IMAP3   WhoIs   SLP   NCP   PPTP   MGCP   LDAP   L2TP   Kerberos   IPv6   GRE   Ethernet SNAP   AFP   CIFS   IEEE 802.3   Finger   NBDGM   NetBEUI   NBSSN   ESP   EIGRP   EGP   DHCP   CGMP   CDP   BOOTP   AH   NBNS   EthernetII   ICQ   PPP   ARP   RIP   IPX   IGRP   IGMP   SSH   RPC   NetBIOS   TFTP   SNMP   SNA   SMB   RADIUS   NTP   NNTP   UDP   TCP   BGP   DNS   SOCKS   IMAP   RTSP   NFS   ICMP   IP   FTP   Telnet   POP3   SMTP   HTTP  
Search RFCs:

Advanced Search
Search Glossary:
Exact search
Fuzzy search


All Protocols
Submit a Request

Recommend an Article

 Layer 7 Application Layer
  AFP
  BOOTP
  CIFS
  CIP
  COPS
  DHCP
  DNS
  Finger
  FTP
  FTP - Ctrl
  FTP - Data
  Gopher
  HSRP
  HTTP
  HTTPS
  ICP
  ICQ
  IMAP
  IMAP3
  IMAPS
  Kerberos
  LPD
  MGCP
  MSN
  MSRDP
  MSSQL
  NCP
  NFS
  NNTP
  NTP
  POP
  POP3
  POP3s
  RADIUS
  RLOGIN
  RRP
  RSH
  RTCP
  RTELNET
  RTP
  RTP Audio
  RTP Video
  RTSP
  SAP
  SIP
  SLP
  SMB
  SMTP
  SNA
  SNMP
  SOCKS
  SSH
  Telnet
  TELNET
  TFTP
  WhoIs
  WINS
 Layer 6 Presentation Layer
  NBNS
  NBSSN
  NCP
  NetBIOS
 Layer 5 Session Layer
  LDAP
  LDAPS
  NCP
  NetBEUI
  RPC
 Layer 4 Transport Layer
  H.225
  H.323
  NBDGM
  NetBEUI
  PUP
  SCTP
  TCP
  UDP
 Layer 3 Network Layer
  AARP
  AH
  BGP
  EGP
  EIGRP
  ESP
  GRE
  GTP
  ICMP
  ICMPv6
  IGMP
  IGRP
  IP
  IP Fragment
  IPv6
  IPX
  Mobile IP
  MPLS
  OSPF
  PIM
  PPPoE
  RIP
  RSVP
  STP
  VRRP
 Layer 2 Data Link Layer
  ARP
  CDP
  CGMP
  Ethernet SNAP
  EthernetII
  IEEE 802.2
  IEEE 802.3
  L2TP
  PPP
  PPTP
  RARP
  SQL
  VLAN
 Layer 1 Physical Layer
© 2006 - 2007 Colasoft Co., Ltd. All rights reserved.