Graham J <
nob...@nowhere.co.uk> wrote:
> I think the same dial-up mechanism worked the same for all ISPs. Also
> if your connection was via ISDN in the form of BT Home Highway.
As in it was V.whatever - a 19K2, 33K6, 56K modem.
> I think AOL forced you to connect via some sort of VPN (built into their
> own dial-upmodem) so that your were in a slightly more secure
> environment, and could only get to the bits of the internet that they
> allowed. Their early selling point was "internet safety" ...
Not built into their modem hardware - they used whatever hardware your
machine had - but built into their dialler app. That connected to their
walled garden. I presume originally internet wasn't part of that picture,
but it was later grafted on, in a sort of VPN as you say - presumably
the software presented an IP connection to Windows that went through their
filters (or maybe just an HTTP proxy?).
Before PPP the common connection type was SLIP, but I suspect AOL did their
own thing.
According to:
http://justinakapaste.com/aol-ppp-information-doc/
there were several other components. However it doesn't explain what all
the abbreviations mean - "AOL TFEPs and Super Tunnels", "T2TP", "P3" - so
we're left guessing as to what they did.
Ah, this has a lot more info:
http://koin.org/files/aol.aim/aol/fdo/manuals/WAOL.doc
- gives the architecture of the Windows software stack in some details. In
particular it appears they have their own networking stack below the VxD
level:
" • P3: procides reliable, in-order packet delivery. P3 was originally
created to optimized slow-speed connections over packet-switched networks
(e.g. Sprint X.25)."
"The AOLMODEM tool acts as the primary interface between the WAOL program
and the modem. It receives the packet data from the comm. port associated
with the modem and passes it on to the P3 tool."
"AOLMODEM and TCPIP talk through the AOLCOMM module to the P3 module. The
AOLCOMM module acts as the interface between AOLMODEM and TCPIP and P3."
"Non-PPP data flow
• Client’s basic connection to the host complex : TTY (raw byte)
connection to the network Point of Presence (POP).
• POP converts raw byte stream into a TCP/IP connection to a TFEP in the
AOL host complex. (Non-AOLnet POP’s use X.25 to a FEP instead.)
• Data flow diagram for service traffic might look like this ...
"
"The P3 Tool is a communications protocol used to ensure error-free
transmission between the host and the
client computer. The data is formed into packets with an 8-byte header and a
terminating carriage return. The minimum length of a packet is the header
plus carriage return, the nominal length is 128 bytes, and the current
maximum length is 1024 bytes.
The P3 protocol was designed with the following constraints:
(1) The protocol must detect any errors in transmission, and make sure
that all messages are delivered without error in correct order.
(2) The number of packets sent should be kept to a minimum.
(3) The maximum size of a packet, including all headers and trailers
must be less than or equal to 128 characters, because of its intended use
over packet networks.
There are two classes of packets - numbered and unnumbered. Data packets are
numbered; all other packets are not. The data packets are numbered
consecutively and must be delivered in order."
So it seems like what goes over the modem link in that implementation is P3,
not PPP.
> Once ADSL modems came along they could not enforce that any longer.
They could have done roughly the same with the original USB ADSL modems, but
as soon as people started having dedicated routers this wasn't something
they could maintain. Presumably the opportunity was taken to throw out the
legacy P3 stack and start again.
Theo