This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| SLIP | |
|---|---|
| Name | SLIP |
| Released | 1980s |
| Author | Computer Networking Community |
| Status | Obsolete / Legacy |
SLIP is a simple encapsulation protocol used to transmit Internet Protocol packets over serial links such as RS-232 connections and early modem links. Originating in the early 1980s, it provided a minimal overhead method adopted by implementations on systems like the Berkeley Software Distribution and embedded devices used by UNIX sites, academic networks, and hobbyist operators. SLIP’s simplicity made it widely implementable on platforms ranging from DEC VAX systems to microcontroller-based routers, though it was largely superseded by more feature-rich protocols.
SLIP is a serial line encapsulation mechanism enabling the framing and transmission of Internet Protocol datagrams over point-to-point RS-232 and dial-up links used by systems such as Sun Microsystems workstations, Digital Equipment Corporation machines, and early IBM PC compatibles. It defines a minimal byte-oriented framing with an END sentinel and escape sequences to delimit packet boundaries, allowing interoperability among implementations on Berkeley Software Distribution, 4.3BSD, NetBSD, FreeBSD, and other UNIX derivatives. SLIP does not define address negotiation, compression, or authentication mechanisms and therefore often operates alongside protocols like TCP/IP stacks and PPP-based control protocols in environments managed by organizations such as DARPA research projects and campus networks.
SLIP emerged in the context of early Internet and packet-switched networking efforts at academic and research institutions in the late 1970s and early 1980s, contemporaneous with developments like TCP/IP standardization and the growth of the ARPANET. Implementations appeared in BSD Unix releases distributed at universities and labs where researchers used equipment from DEC, Bell Labs, and manufacturers like Xerox and Intel to connect workstations via serial lines and low-speed modems. As adoption grew among communities surrounding University of California, Berkeley, MIT, and Stanford, SLIP filled a niche until the introduction and standardization of the Point-to-Point Protocol and enhancements from groups behind IETF working groups and RFC publications. Vendors including Cisco Systems and embedded-platform designers provided SLIP support in early routers and network stacks, but rising needs for configuration, compression, and authentication drove migration to alternatives.
SLIP’s framing is defined by a single END byte value to mark packet termination and an escape mechanism to encode END and ESC within payloads; the protocol prescribes no additional header fields, checksums, or multilink support. Packet boundaries are delineated by the END sentinel, with byte stuffing implemented via ESC sequences to preserve payload transparency; these mechanisms are comparable in simplicity to early framing choices used in serial protocols deployed by DEC terminals and modem controllers. SLIP does not specify link control protocols comparable to those in PPP nor does it include negotiation states found in protocols documented by IETF working groups; as such, IP packet integrity depends on the encapsulated IP headers and higher-layer checksums provided by TCP and UDP.
SLIP was implemented in many UNIX distributions including 4.3BSD, NetBSD, FreeBSD, and appeared in TCP/IP stacks for platforms such as SunOS, VMS on DEC VAX, and early MS-DOS TCP/IP packages. Embedded vendors integrated SLIP into firmware for early router products from companies like Cisco Systems and hobbyist boards based on Intel 8051 and Motorola 68000 microcontrollers. Administrators of campus networks and regional research networks used SLIP for dial-up remote access and point-to-point serial links in environments managed by institutions such as Stanford Linear Accelerator Center and national research labs. Toolchains and utilities within UNIX System V and BSD distributions provided SLIP configuration scripts and device drivers for serial interfaces.
SLIP’s minimal framing yields low header overhead, making it efficient on low-bandwidth serial links typical of early modem connections and leased lines produced by carriers like X.25 service providers. However, the lack of link-layer error detection, in-band control negotiation, or compression (contrasting with mechanisms in PPP and MPPP) results in limitations for noisy links and dynamic address assignment scenarios encountered in networks managed by ISPs and enterprise providers such as AT&T and MCI. SLIP cannot natively multiplex multiple network-layer protocols on a single link nor provide dynamic IP address assignment or authentication features present in later standards implemented by vendors such as Cisco Systems.
Because of its simplicity, SLIP interoperates with many legacy IP stacks but is incompatible with protocols that require link-level negotiation like PPP, which was standardized by IETF to provide link control, authentication (PAP/CHAP), and compression (e.g., Deflate) options. Other alternatives that emerged include proprietary dial-up encapsulations used by Novell and vendor-specific implementations in routing platforms from Juniper Networks and Cisco Systems. Modern VPN and tunneling technologies deployed by projects like OpenVPN, IPsec, and WireGuard provide features and security far beyond SLIP’s capabilities, while lightweight serial-over-IP solutions in embedded systems often prefer protocols tailored by vendors such as NXP Semiconductors and STMicroelectronics.
SLIP lacks built-in authentication, encryption, and integrity protection; consequently, deployments over public or adversarial links are vulnerable to eavesdropping and tampering in ways documented during evaluations by organizations such as CERT and security researchers affiliated with SANS Institute and academic security groups. Mitigation typically involves layering cryptographic protection using IPsec or tunneling over secure transports like SSH and OpenVPN, or operating SLIP only on physically secured serial circuits in controlled facilities such as campus labs and research centers. Operators using legacy SLIP deployments in environments managed by agencies like NASA or national research networks should apply modern cryptographic safeguards and consider migration to supported alternatives.
Category:Network protocols