Re: RE: AD request / L2 Triggers Chapter Statement

I have to respond to this:
>
> My claim, is that IP IS NOT DONE FOR WIRELESS.  Its only
> just begun.  If you shoot me down here in this BOF, other more powerful
> wireless Jedi will follow me!!! :-)
>
>
Sorry - WRONG.
I would suggest you people study what the "packet radio community" has
implemented many years ago. And this has significantly influenced the design
of the IP and TCP protocols when the Old Arpanet NCP had to be redesigned
for a more heterogeneous and wireless environment!
Maybe instead of relying on a connection-oriented subnetwork and dealing
with "handover" problems it might be better tu use a basic datagram
subnetwork (remember - IP does not necessarily require a "link" layer but
assumes what used to be called a "local network") and put the complexity of
signaling and end-to-end aspects on a higher layer.

IP delegated these tasks to TCP - but TCP suffers from the fact that it does
not get any information what happened inside the network, so it has to
implement artefacts such as slow start and a separate congestion window in
order to do a good job. In my opinion this is the real problem we are facing
and the question remaisn whether this is a "protocol" issue or an OS issue;
in this respect I like the ISDN Refernce model which has separate "planes"
for these aspects.

TCP has never been designed as a real-time end-end protocol; maybe the
wireless people ought to define such a beast on top of IP and use the packet
radio techniques for the wireless network instead.

Just my 2 cents.....

--Horst Clausen
(New Mexico Tech/Univ. Salzburg)


_______________________________________________
pilc mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/pilc
http://www.ietf.org/html.charters/pilc-charter.html
http://pilc.grc.nasa.gov/