ASCII Gave Printers Separate Commands to Go Left and Down. Your Text Files Kept Them.
Vint Cerf's memo recorded incompatible host conventions before Telnet settled on a shared wire format. The mismatch was present at the network's beginning.

A carriage return could get you back to the beginning without getting you out of the line you were already on. The printer had obeyed. Your next sentence was still heading for the previous one.
RFC 20 defines CR as moving the printing position to the first position on the “same printing line.” LF advances to the next printing line. Both definitions explicitly cover display devices, too. The commands describe positions, so removing the paper does not remove their separate meanings.
There is an escape clause. LF can mean a complete new line, including the return to the first position, but that interpretation “requires agreement between sender and recipient of data.” Even the newline needed both sides to have the same conversation.
Vint Cerf’s October 16, 1969 memo proposed standard seven-bit ASCII inside an eight-bit byte, with the high bit zero. Then, right in the opening, he documented how quickly a shared character set could run into local habits: SRI used a period as its end-of-line character; UCLA used carriage return. Agreeing on the alphabet had not settled what finished a line.
That makes the little control-character table more interesting than a museum label. ASCII included movement instructions alongside the characters you wanted printed. Backspace moved one printing space backward. Horizontal tab advanced to a predetermined position. Form feed moved to the next form or page. A receiver needed to understand the instructions around the words as well as the words themselves.
MDN’s CRLF reference gives the modern byte names: CR is \r, hexadecimal 0D; LF is \n, hexadecimal 0A. CRLF puts them together as 0D 0A. The Enter key hides an argument your file can still have with the next application.
Telnet’s May 1983 specification shows how much work that agreement could require. Its Network Virtual Terminal was an imaginary common terminal: each end mapped its own device’s conventions to that shared representation. The protocol did the translation so every host did not need intimate knowledge of every other terminal.
The authors, Jon Postel and Joyce Reynolds, required CR LF when the combined newline action was intended. For carriage return alone, the sequence was CR NUL. Some terminals could not do a separate return at all; the specification suggested simulating one by backspacing. Imagine explaining to your printer that moving left is now a compatibility feature.
The extra NUL gave the receiver enough information to choose the correct action. Telnet required the convention even when both parties knew no actual printer was involved. Getting rid of the mechanical device had left the communication problem intact.
Invisible formatting can keep causing visible trouble wherever software exchanges text. A helpful editor can conceal the difference during everyday work; a helpful diagnostic should reveal it when something breaks. The next time a file opens perfectly but another tool rejects it, which bytes did your editor politely leave out of the conversation?