This article is rated C-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects:

Computing Low‑importance This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing Low This article has been rated as Low-importance on the project's importance scale. Internet Mid‑importance This article is within the scope of WikiProject Internet, a collaborative effort to improve the coverage of the Internet on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.InternetWikipedia:WikiProject InternetTemplate:WikiProject InternetInternet Mid This article has been rated as Mid-importance on the project's importance scale. Technology This article is within the scope of WikiProject Technology, a collaborative effort to improve the coverage of technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.TechnologyWikipedia:WikiProject TechnologyTemplate:WikiProject TechnologyTechnology

SLIP is a data link layer protocol, please correct if i am wrong.

This article claims

"The compression algorithm used in CSLIP is known as Van Jacobson TCP/IP Header Compression. CSLIP has no effect on the data payload of a packet and is independent of any compression by the serial line modem used for transmission. It reduces the Transmission Control Protocol (TCP) header from 20 bytes to seven bytes."

Van Jacobson TCP/IP Header Compression claims "Van Jacobson compression reduces the normal 40 byte TCP/IP packet headers down to 3-4 bytes for the average case."

Can anyone explain this discrepancy? Plugwash (talk) 02:29, 10 October 2011 (UTC)Reply

I'm not an expert on this stuff, so I welcome clarifications, but it seems to me that the IP header and the TCP header are each 20 bytes, so together we have 40 bytes to be compressed. If so, the article could be better written. Ksn (talk) 17:57, 7 June 2012 (UTC)Reply

Is there a STD/RFC or a well known implementation for SLIP + IPv6? Otherwise the "Internet layer" should be cleaned.

--Tschäfer (talk) 11:46, 8 March 2015 (UTC)Reply

The original SLIP document seems to not care about the actual structure of IP packets, at all. It does not even seem to check it's actually transmitting IP. Which is great, because that's not its business. Artoria2e5 🌉 13:52, 13 May 2023 (UTC)Reply

The article fails to mention that some early consumer dial-up internet access (early to mid 90's) allowed for the use of SLIP (as an option with PPP being the default) to connect to the internet over dial-up modems until basically it was either phased out or never on option with late 90's dial-up ISP's. Probably should include why a home internet user would have preferred to use SLIP (was is better supported on older computers, for example?). I don't remember myself exactly what the rationale was continuing to make it an option with some ISP at the time just that PPP was the recommended choice back then if your computer supported it. --Notcharliechaplin (talk) 01:43, 3 December 2018 (UTC)Reply

SLIP and PPP were absolutely critical to the rapid success of the Mosaic web browser and thus the World Wide Web. This is often overlooked, and this article fails to have any history section. It's easy to forget most people used dialup modems, and most dialed into the Internet over TTY. Thus gopher was widely used. The graphic revolution of the Mosaic browser was made possible only with SLIp and PPP. -- GreenC 17:49, 11 September 2022 (UTC)Reply