Message-ID:

BOFH excuse #199: the curls in your keyboard cord are losing electricity.

comp / comp.os.linux.misc / Re: I never thought of this scenario

Subject: Re: I never thought of this scenario
From: Nuno Silva
Newsgroups: comp.os.linux.misc
Organization: A noiseless patient Spider
Date: Sat, 27 Apr 2024 16:45 UTC
References: 1 2 3 4 5 6 7 8 9 10 11 12 13

Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nunojsilva@invalid.invalid (Nuno Silva)
Newsgroups: comp.os.linux.misc
Subject: Re: I never thought of this scenario
Date: Sat, 27 Apr 2024 17:45:49 +0100
Organization: A noiseless patient Spider
Lines: 32
Message-ID: <v0ja3v$fdp4$1@dont-email.me>
References: <uutq04$2n9pt$1@dont-email.me>
<07WdnchvLrr2GI_7nZ2dnZfqn_qdnZ2d@giganews.com>
<uuu39t$2pd0s$1@dont-email.me> <uuvblp$32mbm$1@dont-email.me>
<uv06o4$3c5fm$2@dont-email.me> <uv09ad$3cnth$1@dont-email.me>
<uv2e60$jin$1@dont-email.me> <uv3e7p$7nqq$3@dont-email.me>
<uvcu20$2qdb0$3@dont-email.me> <uvdeb7$2t82j$4@dont-email.me>
<uvht4i$3th0n$2@dont-email.me> <uviifd$53ll$1@dont-email.me>
<uvjbc5$l1b$1@tncsrv09.home.tnetconsulting.net>
MIME-Version: 1.0
Content-Type: text/plain
Injection-Date: Sat, 27 Apr 2024 18:45:51 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="31fd31a4bcdf4693faf7a380600d6aa6";
logging-data="505636"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+rXEUL8eaydIaX/gOSivNU"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
Cancel-Lock: sha1:9TtSMAVjl3q2ZQlbnPyUFIicOyo=

View all headers

On 2024-04-15, Grant Taylor wrote:

> On 4/15/24 01:50, Nuno Silva wrote:
>> Why does it get called "TCP/IP" so often? What is the origin of that
>> name?
>
> That's at lease partially becuase IPv1-3 was a single protocol. There
> was lots of debating going on during the development of IPv1-3 for the
> raw point to point that IP provides and in order delivery circuit that
> TCP provides. It was part way through the development that the
> realized that they could split IP into two layers TCP for end-to-end /
> in-order delivery and IP for point to point connectivity that other
> protocols could use.
>
>> These are two different protocols for different layers and that name
>> does not include, say, UDP.
>
> IPv1-3 was split into TCP/IPv4. TCP was the first protocol that ran
> on top of IPv4. I think part of the reason for the split name was to
> emphasize the split protocol design.
>
> I think UDP was officially documented within a year of TCP/IPv4 being
> documented. But the progenitor of UDP existed before TCP/IPv4 was
> documented. Experiments were ongoing with the parts of IPv3 that
> became UDP/IP. Some of the experiments were for voice transmission.

Thanks for this explanation! I can't believe I either never came across
this information or I forgot it. Which probably means I have a lot of
interesting reading to do regarding this area of computing history :-)

--
Nuno Silva

Subject: Re: I never thought of this scenario
From: Grant Taylor
Newsgroups: comp.os.linux.misc
Organization: TNet Consulting
Date: Sat, 27 Apr 2024 22:26 UTC
References: 1 2 3 4 5 6 7 8 9 10 11 12 13 14

Path: eternal-september.org!news.eternal-september.org!feeder3.eternal-september.org!tncsrv06.tnetconsulting.net!tncsrv09.home.tnetconsulting.net!.POSTED.omega.home.tnetconsulting.net!not-for-mail
From: gtaylor@tnetconsulting.net (Grant Taylor)
Newsgroups: comp.os.linux.misc
Subject: Re: I never thought of this scenario
Date: Sat, 27 Apr 2024 17:26:41 -0500
Organization: TNet Consulting
Message-ID: <v0ju31$ntp$1@tncsrv09.home.tnetconsulting.net>
References: <uutq04$2n9pt$1@dont-email.me>
<07WdnchvLrr2GI_7nZ2dnZfqn_qdnZ2d@giganews.com>
<uuu39t$2pd0s$1@dont-email.me> <uuvblp$32mbm$1@dont-email.me>
<uv06o4$3c5fm$2@dont-email.me> <uv09ad$3cnth$1@dont-email.me>
<uv2e60$jin$1@dont-email.me> <uv3e7p$7nqq$3@dont-email.me>
<uvcu20$2qdb0$3@dont-email.me> <uvdeb7$2t82j$4@dont-email.me>
<uvht4i$3th0n$2@dont-email.me> <uviifd$53ll$1@dont-email.me>
<uvjbc5$l1b$1@tncsrv09.home.tnetconsulting.net> <v0ja3v$fdp4$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sat, 27 Apr 2024 22:26:41 -0000 (UTC)
Injection-Info: tncsrv09.home.tnetconsulting.net; posting-host="omega.home.tnetconsulting.net:198.18.1.140";
logging-data="24505"; mail-complaints-to="newsmaster@tnetconsulting.net"
User-Agent: Mozilla Thunderbird
Content-Language: en-US
In-Reply-To: <v0ja3v$fdp4$1@dont-email.me>

View all headers

On 4/27/24 11:45, Nuno Silva wrote:
> Thanks for this explanation!

You're welcome.

> I can't believe I either never came across this information or I
> forgot it.

Eh. I'm not too surprised. Most people got their introduction to
TCP/IPv4 and never looked at what came before that.

> Which probably means I have a lot of interesting reading to do
> regarding this area of computing history :-)

There's a lot of history. Some of it is interesting. Less of it is
actually useful save for knowing where we have been / come from as
influence to where we are going.

But day to day, knowing about history doesn't help as much as one might
hope.

--
Grant. . . .

Subject	Author
Re: I never thought of this scenario	Nuno Silva
Re: I never thought of this scenario	Grant Taylor