From: pierre@shell.portal.com (Pierre Uszynski)
To: cypherpunks@toad.com
Message Hash: e603acf65dcc2c4a05cabbbb124ac3dff217e83967b927591de7d98331e6d48d
Message ID: <9310262252.AA06685@jobe.shell.portal.com>
Reply To: N/A
UTC Datetime: 1993-10-26 22:52:45 UTC
Raw Date: Tue, 26 Oct 93 15:52:45 PDT
From: pierre@shell.portal.com (Pierre Uszynski)
Date: Tue, 26 Oct 93 15:52:45 PDT
To: cypherpunks@toad.com
Subject: Re: DC-nets, up from the basic concept
Message-ID: <9310262252.AA06685@jobe.shell.portal.com>
MIME-Version: 1.0
Content-Type: text/plain
> You could (maaaybe :-( establish the layering:
>
> Coaxial - Ethernet - IP - TCP / Telnet - RFC822 email -
> PEM - DC-net - IP - TCP / Telnet - RFC822 email - PEM
Before somebody takes the above tooooo seriously, I'll add
that it would take major work to modify TCP/IP to function
as the second "TCP/IP" layer in the example above. This is
because TCP/IP relies on dialogs between machines/nets
instead of broadcasts (at least at the internetwork level),
so messages should be traceable back to an inter-DC-net
"table", but could not be traced back to a specific host.
Pierre
pierre@shell.portal.com
Return to October 1993
Return to “pierre@shell.portal.com (Pierre Uszynski)”
1993-10-26 (Tue, 26 Oct 93 15:52:45 PDT) - Re: DC-nets, up from the basic concept - pierre@shell.portal.com (Pierre Uszynski)