The Rx Hex
dc.contributor.author | Bachmann, D. | en_US |
dc.contributor.author | Honeyman, P. | en_US |
dc.contributor.author | Huston, L. B. | en_US |
dc.date.accessioned | 2014-07-18T18:12:05Z | |
dc.date.available | 2014-07-18T18:12:05Z | |
dc.date.issued | 1993-11-02 | en_US |
dc.identifier.citation | D. W. Bachmann, P. Honeyman, and L. B. Huston, "The Rx Hex," November 1993. [Proc. of IEEE Workshop on Services in Distributed and Networked Environments, Prague (June 1994).] <http://hdl.handle.net/2027.42/107951> | en_US |
dc.identifier.uri | https://hdl.handle.net/2027.42/107951 | |
dc.description.abstract | At CITI, we run dataless AFS clients over dialup IP networks. Improving Rx performance is critical to that task. In this paper, we report on our progress in adapting Rx to networks characterized by low bandwidth, high delay, or variable round-trip time. Our focus is on adding facilities for congestion avoidance and control, and on compressing Rx headers. Although our work is ongoing, we have overcome several hurdles, and are now getting impressive data transfer rates over ordinary dialup lines. | en_US |
dc.publisher | Center for Information Technology Integration | en_US |
dc.title | The Rx Hex | en_US |
dc.type | Technical Report | en_US |
dc.subject.hlbsecondlevel | Computer Science | en_US |
dc.subject.hlbtoplevel | Engineering | en_US |
dc.contributor.affiliationum | Center for Information Technology Integration | en_US |
dc.contributor.affiliationother | IBM [1st listed author] | en_US |
dc.description.bitstreamurl | http://deepblue.lib.umich.edu/bitstream/2027.42/107951/1/citi-tr-93-8.pdf | |
dc.owningcollname | Electrical Engineering and Computer Science, Department of (EECS) |
Files in this item
Remediation of Harmful Language
The University of Michigan Library aims to describe library materials in a way that respects the people and communities who create, use, and are represented in our collections. Report harmful or offensive language in catalog records, finding aids, or elsewhere in our collections anonymously through our metadata feedback form. More information at Remediation of Harmful Language.
Accessibility
If you are unable to use this file in its current format, please select the Contact Us link and we can modify it to make it more accessible to you.