-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Eddy, Wesley M. (GRC-MS00)[Verizon] wrote: ... > To me, if a piece of code is controlling transmission in terms of > things like timing, segmentation/reassembly, error checking, ACK, > retransmission, on behalf of some set of applications, then it > smells a lot like a "transport". Muxing in HTTP ended up reinventing a lot of transport solutions exactly because HTTP tried too hard to run many exchanges over a single connection. That doesn't make it a transport protocol, though - it may just have issues similar to the transport layer. > John Day has noticed that the > same thing can be said about part of the link layer, and realized > that these are all just different flavors of the same flow and > error-control parent class in his PNA. FYI, our Recursive Network Architecture had come to the same conclusion and has been implemented: Touch, J., and Pingali, V. K., "The RNA Metaprotocol" in Proc. IEEE ICCCN (Future Internet Architectures and Protocols track), St. Thomas, Virgin Islands, August 2008. Touch, J., Wang. Y., and Pingali, V., "A Recursive Network Architecture," ISI Technical Report ISI-TR-2006-626, October 2006. Joe -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkon+RIACgkQE5f5cImnZrtmdACfYmM/7R9aSWBr1tjV8YEhD67S BEAAoLn+0PO1lMMhrYHzFeZEHc+DhykT =dVZT -----END PGP SIGNATURE-----
