[ih] TCP

[vinton cerf]

I hope no one disagrees with that observation, Karl. I sure don't.

v

On Sun, May 5, 2024 at 3:12 PM Karl Auerbach via Internet-history <
internet-history at elists.isoc.org> wrote:

> By-the-way, there is an event on May 19:
>
> https://engage.ieee.org/celebrate-i50
>
> I would add, however, that the Internet is more than just TCP/IP.
>
> I tend to think of TCP/IP as the super-glue that allowed several diverse
> energies to come together.
>
> We had the need of research and academic communities to share
> information and resources, we had growing communities of USENET and BBS
> people who had become familiar with network based communications, we had
> government $$ from agencies desirous of making networks happen, we had
> passed through a legal evolution in which the telco monopolies had been
> eroded and their utility services pried open (i.e. via HushAPhone,
> Carterphone, MCI cases), and computers that could be nodes on networks
> became smaller and more ubiquitous (first with mini-computers then with
> personal computers.)
>
> In other words, we had a supersaturated solution of need and desire -
> TCP was the invention that triggered the precipitation of the Internet.
>
>         --karl--
>
> On 5/5/24 2:59 AM, Patrik Fältström via Internet-history wrote:
> > 50 years ago today Vint Cerf and Bob Kahn published their paper on
> packet switching which is the basis for the Internet we use today.
> >
> > They did come up with TCP: "Within a HOST we assume that existence of a
> transmission control program (TCP) which handles the transmission and
> acceptance of messages on behalf of the processes it serves."
> >
> > It was published in IEEE Transactions on Communications ( Volume: 22,
> Issue: 5, May 1974): https://ieeexplore.ieee.org/document/1092259
> >
> >> A protocol that supports the sharing of resources that exist in
> different packet switching networks is presented. The protocol provides for
> variation in individual network packet sizes, transmission failures,
> sequencing, flow control, end-to-end error checking, and the creation and
> destruction of logical process-to-process connections. Some implementation
> issues are considered, and problems such as internetwork routing,
> accounting, and timeouts are exposed.
> >
> >
> https://www.cs.princeton.edu/courses/archive/fall06/cos561/papers/cerf74.pdf
> >
> > I think this is the right moment to just say “and the rest is history”.
> >
> > Thanks Vint and Bob!
> >
> > Patrik
> >
> --
> Internet-history mailing list
> Internet-history at elists.isoc.org
> https://elists.isoc.org/mailman/listinfo/internet-history
>