POINT-TO-POINT PROTOCOL FIELD ASSIGNMENTS (last updated 28 June 2004) For information on registration procedures for PPP Numbers please see [RFC3818]. The following registries appear below: PPP DLL PROTOCOL NUMBERS PPP LCP AND IPCP CODES PPP LCP CONFIGURATION OPTION TYPES PPP ECP CONFIGURATION OPTION TYPES PPP CCP CONFIGURATION OPTION TYPES PPP SDCP CONFIGURATION OPTIONS PPP AUTHENTICATION ALGORITHMS PPP LCP FCS-ALTERNATIVES PPP MULTILINK ENDPOINT DISCRIMINATOR CLASS PPP LCP CALLBACK OPERATION FIELDS PPP ATCP CONFIGURATION OPTION TYPES PPP OSINLCP CONFIGURATION OPTION TYPES PPP BANYAN VINES CONFIGURATION OPTION TYPES PPP BRIDGING CONFIGURATION OPTION TYPES PPP BRIDGING MAC TYPES PPP BRIDGING SPANNING TREE PPP INTERNETWORK PACKET EXCHANGE CONTROL PROTOCOL (IPXCP) IPXCP CONFIGURATION OPTIONS IPX COMPRESSION PROTOCOL VALUES IPX-ROUTING-PROTOCOL OPTIONS NBFCP Configuration Options PPP EAP REQUEST/RESPONSE TYPES PPP VENDOR SPECIFIC OUI OPTIONS PPP IPCP CONFIGURATION OPTION TYPES PPP IPV6CP CONFIGURATION OPTIONS IP-Compression-Protocol Types IPv6-Compression-Protocol Types IP Header Compression Configuration Option Suboption Types ROHC Configuration Option Suboption Identifier Values 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 Reference -------------- ---------------------------------- --------- 0001 Padding Protocol 0003 ROHC small-CID [RFC3095] 0005 ROHC large-CID [RFC3095] 0007 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) [Typo in RFC1172] 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 IPv6 Header Compression 0051 KNX Bridging Data [ianp] 0053 Encryption [Meyer] 0055 Individual Link Encryption [Meyer] 0057 Internet Protocol version 6 [Hinden] 0059 PPP Muxing [RFC3153] 005b Vendor-Specific Network Protocol (VSNP) [RFC3772] 0061 RTP IPHC Full Header [RFC3544] 0063 RTP IPHC Compressed TCP [RFC3544] 0065 RTP IPHC Compressed Non TCP [RFC3544] 0067 RTP IPHC Compressed UDP 8 [RFC3544] 0069 RTP IPHC Compressed RTP 8 [RFC3544] 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] 020b STP - Scheduled Transfer Protocol [Segal] 020d EDP - Extreme Discovery Protocol [Grosser] 0211 Optical Supervisory Channel Protocol (OSCP)[Prasad] 0213 Optical Supervisory Channel Protocol (OSCP)[Prasad] 0231 Luxcom 0233 Sigma Network Systems 0235 Apple Client Server Protocol [Ridenour] 0281 MPLS Unicast [RFC3032] 0283 MPLS Multicast [RFC3032] 0285 IEEE p1284.4 standard - data packets [Batchelder] 0287 ETSI TETRA Network Protocol Type 1 [Nieminen] 0289 Multichannel Flow Treatment Protocol [McCann] 2063 RTP IPHC Compressed TCP No Delta [RFC3544] 2065 RTP IPHC Context State [RFC3544] 2067 RTP IPHC Compressed UDP 16 [RFC3544] 2069 RTP IPHC Compressed RTP 16 [RFC3544] 4001 Cray Communications Control Protocol [Stage] 4003 CDPD Mobile Network Registration Protocol [Quick] 4005 Expand accelerator protocol [Rachmani] 4007 ODSICP NCP [Arvind] 4009 DOCSIS DLL [Gaedtke] 400B Cetacean Network Detection Protocol [Siller] 4021 Stacker LZS [Simpson] 4023 RefTek Protocol [Banfill] 4025 Fibre Channel [Rajagopal] 4027 EMIT Protocols [Eastham] 405b Vendor-Specific Protocol (VSP) [RFC3772] 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 (until 1993) [See note for 0037] 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] 8059 PPP Muxing Control Protocol [RFC3153] 805b Vendor-Specific Network Control Protocol (VSNCP) [RFC3772] 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] 820b STP - Control Protocol [Segal] 820d EDPCP - Extreme Discovery Protocol Ctrl Prtcl [Grosser] 8235 Apple Client Server Protocol Control [Ridenour] 8281 MPLSCP [RFC3032] 8285 IEEE p1284.4 standard - Protocol Control [Batchelder] 8287 ETSI TETRA TNP1 Control Protocol [Nieminen] 8289 Multichannel Flow Treatment Protocol [McCann] 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] c05b Vendor-Specific Authentication Protocol (VSAP) [RFC3772] 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:n 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], [Warning: The above Collides with RFC1976] 26 Prefix elision [Bormann] 27 Multilink header format [Bormann] 28 Internationalization [RFC2484] 29 Simple Data Link on SONET/SDH [Carlson] 30 Reserved until 14-Oct-2002 [CFox] 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 3DESE [RFC2420] 3 DESE-bis [RFC2419] 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 Predictor 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 Unassigned 26 Deflate [RFC1979] 27 V.44/LZJH Compression Protocol [Heath] 28-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] 6 SHA-1 [Black] 128 MS-CHAP [Crocker] 129 MS-CHAP-2 [Zorn] 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] 6 Internet Protocol (Ipv6) Address [Nesser] 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 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 Reference ---- -------------------- --------- 1 Bridge-Identification 2 Line-Identification 3 MAC-Support 4 Tinygram-Compression 5 LAN-Identification 6 MAC-Address 7 Spanning-Tree-Protocol 8 IEEE-802-Tagged-Frame 9 Management-Inline 10 Bridge-Control-Packet-Indicator [RFC3518] 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 canonical addresses 2 IEEE 802.4 with canonical addresses 3 IEEE 802.5 with non-canonical addresses 4 FDDI with non-canonical addresses 5-10 reserved 11 IEEE 802.5 with canonical addresses 12 FDDI with canonical 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 [RFC1552] 235 Shiva Compressed NCP/IPX [RFC1552] 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]. This registry has been replaced. See: http://www.iana.org/assignments/eap-numbers for a current list of the assigned EAP Request/Response types. PPP VENDOR SPECIFIC OUI OPTIONS PPP Vendor Extensions (RFC 2153) uses IEEE standard OUIs (Organizationally Unique Identifiers) to indicate vendor-specific features. See RFC 1700 for details on contacting the IEEE. Vendors that desire to use their IEEE 802 OUI for PPP Vendor Extensions should register their OUI with IANA. Vendors that do not otherwise need an IEEE assigned OUI can request a PPP specific OUI from IANA out of the 'CF0000' range, which has both the "locally-assigned" and "broadcast/multicast" bits set to one. See RFC 2153 for details. OUI (in hex) Organization Reference ------------ ------------ --------- CF0001 NTT Mobile Communications Network CF0002 3GPP2 Vendor specific packet ID [Plestid] 008037 Ericsson [Johnson] CF0003-CFFFFF Reserved for assignment by the IANA 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 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] IP-Compression-Protocol Types per [RFC1332] Value (hex) Description Reference ----------- ---------------------------------- --------- 002d Van Jacobson Compressed TCP/IP [RFC1144, RFC2023] 0061 IP Header Compression [RFC2507, 3544] 0003 Robust Header Compression (ROHC) [RFC3241] IPv6-Compression-Protocol Types per [RFC2023] Value (hex) Description Reference ----------- ---------------------------------- --------- 004f IPv6 Header Compression [RFC2023] 0061 IP Header Compression [RFC2507, RFC3544] 0003 Robust Header Compression (ROHC) [RFC3241] IP Header Compression Configuration Option Suboption Types per [RFC3544] Value Description Reference ------ ---------------------------------- --------- 1 RTP Header Compression [RFC2508, RFC3544] 2 Enhanced RTP-Compression [RFC3544] 3 TCP or non-TCP Compression Disable [RFC3544] ROHC Configuration Option Suboption Identifier Values - Per [RFC3241] Suboption ID Usage Reference ------------ ----------------------------------- --------- 1 Profiles [RFC3241] 2-127 Unassigned 128-254 Unassigned 255 Reserved [RFC3241] REFERENCES ---------- [RFC1144] V. Jacobson, "Compressing TCP/IP Headers for Low-Speed Serial Links", RFC 1144, February 1990. [RFC1332] McGregor, G., "The PPP Internet Protocol Control Protocol (IPCP)", RFC 1332, Merit, May 1992. [RFC1552] Simpson, W., "The PPP Internetwork Packet Exchange Control Protocol (IPXCP)", RFC 1552, Daydreamer, December 1993. [RFC1570] Simpson, W., "PPP LCP Extensions", RFC 1570, Daydreamer, January 1994. [RFC1582] Meyer, G., "Extensions to RIP to Support Demand Circuits", RFC 1582, Spider Systems, February 1994. [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. [RFC1663] Rand, D. "PPP Reliable Transmission", RFC 1663, Novell, 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. [RFC1962] Rand, D., "The PPP Compression Control Protocol (CCP)", RFC 1962, Novell, June 1996. [RFC1963] Schneider, K., and S. Venters, "PPP Serial Data Transport Protocol (SDTP)", RFC 1963, ADTRAN, Inc., June 1996. [RFC1967] Schneider, K., and R. Friend, "PPP LZS-DCP Compression Protocol (LZS-DCP)", RFC 1967, ADTRAN, Inc., Stac Technology, June 1996. [RFC1968] Meyer, G., "The PPP Encryption Control Protocol (ECP)", RFC 1968, Spider Systems, June 1996. [RFC1974] Friend, R., W. Simpson, "PPP Stac LZS Compression Protocol", RFC 1974, Stac Electronics, Daydreamer, August 1996. [RFC1975] Schremp, D., J. Black, J. Weiss. "PPP Magnalink Variable Resource Conpression", RFC 1975, Magnalink, August 1996. [RFC1976] Schnieder, k, S. Venters, " PPP for Data Compression in Data Circuit-Terminating Equipment (DCE)", RFC 1976, Adtran, August 1996. [RFC1977] Schryver, V., "PPP BSD Compression Protocol", RFC 1977, August 1996. [RFC1979] Woods, J., "PPP Deflate Protocol", Proteon, August 1996. [RFC1994] Simpson, W., "PPP Challenge Handshake Authentication Protocol (CHAP)", RFC 1994, Datdreamer, August 1994. [RFC2023] Haskin, D., and E. Allen, "IP Version 6 over PPP", RFC 2023, Bay Networks, October 1996. [RFC2097] Pall, G., "The PPP NetBIOS Frames Control Protocol (NBFCP)", RFC 2097, Microsoft Corp., January 1997. [RFC2118] Pall, G., "Microsoft Point-to-Point Compression (MPPC) Protocol", RFC 2118, Microsoft, March 1997. [RFC2125] Richards, C., and K. Smith, "The PPP Bandwidth Allocation Protocol (BAP) - The PPP Bandwidth Allocation Control Protocol (BACP)", RFC 2125, March 1997. [RFC2153] Simpson, W., "PPP Vendor Extensions", RFC 2153, DayDreamer, May 1997. [RFC2290] Solomon, J., and S. Glass, "Mobile-IPv4 Configuration Option for PPP IPCP", RFC 2290, Motorola, FTP Software, February 1998. [RFC2419] Sklower, K., and G. Meyer, "The PPP DES Encryption Protocol, Version 2 (DESE-bis)", RFC 2419, University of California, Berkeley, Shiva, September 1998. [RFC2420] Kummert, H., "The PPP Triple-DES Encryption Protocol (3DESE)", RFC 2420, Nentec GmbH., September 1998. [RFC2484] Zorn, G., "PPP LCP Internationalization Configuration Option", RFC 2484, January 1999. [RFC2507] M. Degermark, B. Nordgren, and S. Pink, "IP Header Compression", RFC 2507, February 1999. [RFC2508] S. Casner and V. Jacobson, "Compressing IP/UDP/RTP Headers for Low-Speed Serial Links", RFC 2508, February 1999. [RFC3032] E. Rosen, D. Tappan, G. Fedorkow, Y. Rekhter, D. Farinacci, T. Li and A. Conta, "MPLS Label Stack Encoding", RFC 3032, January 2001. [RFC3095] C. Bormann, C. Burmeister, M. Degermark, H. Fukushima, H. Hannu, L-E. Jonsson, R. Hakenberg, T. Koren, K. Le, Z. Liu, A. Martensson, A. Miyazaki, K. Svanbro, T. Wiebke, T. Yoshimura, H. Zheng, "RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed", RFC 3095, July 2001. [RFC3153] R. Pazhyannur, I. Ali, and C. Fox, "PPP Multiplexing", RFC 3153, August 2001. [RFC3241] C. Bormann, "ROHC over PPP", RFC 3241, April 2002. [RFC3518] M. Higashiyama, F. Baker, and T. Liao, "PPP Bridging Control Protocol (BCP)", RFC 3518, April 2003. [RFC3544] M. Egan, S. Casner, C. Bormann, and T. Koren, "IP Header Compression over PPP", RFC 3544, July 2003. [RFC3772] J. Carlson and R. Winslow, "Point-to-Point Protocol (PPP) Vendor Protocol", RFC 3772, May 2004. [RFC3818] V. Schryver, "IANA Considerations for the Point-to-Point Protocol (PPP)", RFC 3818, June 2004. PEOPLE ------ [Aboba] Bernard Aboba , December 1997. [Arvind] K. Arvind, , November 2000. [Asnes] Kenneth Asnes , June 1999. [Banfill] Robert Banfill , July 1997. [Batchelder] Brian Batchelder , January 1999. [Berrendonner] Romain Berrendonner, , December 2001. [Black] David L. Black, , December 2002. [Blunk] Larry Blunk, , December 1995, 1997. [Bogue] Darrin Bogue, , February 2004. [Bormann] Cartsen Bormann , March 1998. [Cam-Winget] Nancy Cam-Winget, , December 2003. [Carlson] James Carlson, , January 1998, June 1999, February 2001. [CFox] Craig Fox , October 1999. [Chang] Victor Chang, , June 2002. [Clements] Matt Clements, , February 2003. [Crocker] Ken Crocker, , March 1996. [Culbert] Ken Culbert, , October 1996. [Edmonstone] Richard Edmonstone, , July 1996. [Eastham] Bryant Eastham, , June 2001. [Fields] Steven Fields, , November 2001. [Fox] Karl Fox, , January 1997. [Funk] Paul Funk, , October 2001. [Gaedtke] Jason Gaedtke, , April 2002. [Grosser] Don Grosser, , October 2000. [Haverinen] Henry Haverinen, , November 2000, December 2001. [Heath] Jeff Heath, , April 2002. [Hibbard] Richard Hibbard, , February 2003. [Hinden] Bob Hinden, , March 1996. [ianp] , November 1994. [Jerdonek] Rob Jerdonek, , May 2000. [Johnson] Sten Johnson, , October 2000. [Josefsson] Simon Josefsson, , March 2002. [Kelleher] Joe Kelleher, , April 2002. [KEN] [Korfmacher] Oliver Korfmacher, , April 1995. [Kummert] Holger Kummert, , August 1997. [Liberman] David Liberman, mccap@research.bell-labs.com>, March 2001. [Merlin] Pascal Merlin, , January 2002. [Meyer] Gerry Meyer, December 1994. [Nace] William Nace, , December 1997 [Nesser] Philip J. Nesser II, , April 2002. [Nieminen] Seppo Nieminen, , July 1999. [Norman] Stuart Norman, , November 2000. [Palekar] Ashwin Palekar, , December 2001, April 2002. [Pitard] David Pitard, , February 2003. [Plestid] Trevor Plestid, , June 2003. [Potter] Darran Potter, , January 2002. [Prasad] Sharat C. Prasad, , October 2001. [Quick] Frank Quick, [Rachmani] Ilan Rachmani, , October 1999. [Rajagopal] Murali Rajagopal, , May 2000. [Ridenour] Howard Ridenour, , February 1995. [Rixom] Tom Rixom, , May 2003. [Rosselli] Michael Rosselli, , January 1998. [Sastry] Arun Sastry, , April 1995. [Schneider] Kevin Schneider [Segal] Ben Segal, , August 2000. [Seno] Shoichiro Seno, , April 1995. [Siller] Curtis A. Siller, Jr., , January 2003. [Simpson] Willian Allen Simpson, , March 1995. [Smith] Kevin Smith, Kevin@Smith.ascend.com, January 1996. [Stage] Erling B. Stage October 1994. [Solomon] Jim Solomon, , Feburary 1997. [Narayana] Badari Narayana [Tackabury] Wayne Tackabury, , January 1995. [Tavakoli] Oliver K. Tavakoli, , February 2003. [Ullah] Sana Ullah, , February 2002. [Ungar] Alan Ungar, , April 1995. [Webb] Stephen M. Webb, , January 2002. [Whelan] William Whelan, , December 1997. [Xiong] John Xiong, , June 2002. [Young] Albert Young, , December 2001. [Zick] Don Zick, , February 2003, April 2004. [Zorn] Glen Zorn, , June 1998, September 1998. []