Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Guy Almes

dblp:10/1737 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 2006
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Systems, architecture and hardware · 1 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Computer networks
1 paper
Transport protocols and congestion control · 61% Internet architecture and protocols · 39%

Topics — the 3 heaviest of 4, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Internet architecture and protocols
high bandwidth network
0.112006
Bandwidth challenge - Phoebus · SC 2006
Transport protocols and congestion control
TCP performance
0.112006
Bandwidth challenge - Phoebus · SC 2006
Transport protocols and congestion control
transport protocols
0.112006
Bandwidth challenge - Phoebus · SC 2006

Methods — techniques the papers use, named apart from their topics

transport protocol splitting · 0.1
YearPublicationVenuePosition
2006 Bandwidth challenge - Phoebus
abstract
Phoebus is a project whose goal is to allow legacy applications to utilize high bandwidth connections over Internet2's Hybrid Packet Optical Infrastructure (HOPI) backbone. Phoebus works by breaking a single end-to-end TCP connection into a series of transport layer connections. The end connections (from Internet2 edge nodes to the end hosts) still use TCP. However, the connection over the Internet2 backbone is handled by server software running on the edge nodes. These servers can then choose the best transport protocol and protocol settings for sending the data across Internet2. Using this service, end users are no longer required to modify a variety of TCP settings in order to achieve good performance over long distances. The end users only need to be concerned about ensuring adequate speed across the path between themselves and the Internet2 edge nodes. In many cases, the default TCP settings will prove adequate for achieving acceptable speeds.
Guy Almes, D. Martin Swany, Aaron Brown
SC1