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

Mai-Huong Nguyen

dblp:70/6119 · DBLP profile ↗
← Back
3ranked-venue papers
2as first author
0since 2021 · last 1996
—ORCID · none

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

Computer networks · 3 · 2 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
3 papers
Transport protocols and congestion control · 45% Internet architecture and protocols · 29% Physical-layer communications · 26%
Computer architecture, parallel and distributed computing, and storage systems
2 papers
Distributed systems · 91% Interconnection networks and networks-on-chip · 9%

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

TopicWeightPapersLastEvidence papers
Internet architecture and protocols › upper layer protocols
session management
0.011996
MCMP: A Transport/Session Level Distributed Protocol for Desktop Conference Setup · IEEE J. Sel. Areas Commun. 1996
Transport protocols and congestion control
transport protocols
0.011996
MCMP: A Transport/Session Level Distributed Protocol for Desktop Conference Setup · IEEE J. Sel. Areas Commun. 1996
Distributed systems
distributed coordination
0.011996
MCMP: A Transport/Session Level Distributed Protocol for Desktop Conference Setup · IEEE J. Sel. Areas Commun. 1996
Distributed systems › group communication
group communication protocol
0.011996
MCMP: A Transport/Session Level Distributed Protocol for Desktop Conference Setup · IEEE J. Sel. Areas Commun. 1996
Physical-layer communications
modulation
0.011995
51.84 Mb/s 16 CAP ATM LAN Standard · IEEE J. Sel. Areas Commun. 1995
Transport protocols and congestion control
TCP
0.011993
Reducing the Complexities of TCP for a High Speed Networking Environment · INFOCOM 1993
Transport protocols and congestion control › real-time communication
multimedia conferencing
0.011996
MCMP: A Transport/Session Level Distributed Protocol for Desktop Conference Setup · IEEE J. Sel. Areas Commun. 1996
Internet architecture and protocols › ATM networks
ATM LAN
0.011995
51.84 Mb/s 16 CAP ATM LAN Standard · IEEE J. Sel. Areas Commun. 1995
Physical-layer communications › digital transmission systems › wireline communication
unshielded twisted-pair transmission
0.011995
51.84 Mb/s 16 CAP ATM LAN Standard · IEEE J. Sel. Areas Commun. 1995
Interconnection networks and networks-on-chip
high-speed networks
0.011993
Reducing the Complexities of TCP for a High Speed Networking Environment · INFOCOM 1993

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

distributed algorithm · 0.0correctness proof · 0.0rate-based congestion control · 0.0protocol partitioning · 0.0
YearPublicationVenuePosition
1996 MCMP: A Transport/Session Level Distributed Protocol for Desktop Conference Setup
abstract
The multiparty conference management protocol (MCMP) is an end-to-end distributed session/transport level protocol intended for group management of desktop conferencing applications. This paper describes the MCMP conference setup algorithms and proves that they meet specified correctness properties. MCMP sets up control channels for use in exchanging control information while the conference is in progress. The logical topology used is a completely interconnected mesh, MCMP always provides best effort services in cases of failures. Correctness properties guaranteed upon termination of the protocol include connectivity, validity, uniqueness, and consistency of local views. Application control information that can be exchanged using the control channels include resource negotiation and subconferencing.
Mai-Huong Nguyen, Mischa Schwartz
IEEE J. Sel. Areas Commun.1
1995 51.84 Mb/s 16 CAP ATM LAN Standard
abstract
The paper describes the characteristics and performance of the 16-CAP transmission scheme that has been chosen by the Technical Committee of the ATM Forum as the ATM LAN physical layer interface standard at 51.84 Mb/s for category 3 unshielded-twisted-pair (UTP) wiring. The two most attractive features of the 16-CAP transceiver are its capability of operating in the presence of multiple users in a voice-grade UTP cable and the straightforward way in which it can provide scalability to lower speeds. It is also shown in the paper how the carrierless AM/PM (CAP) modulation scheme used for the ATM LAN standard can be utilized to provide substantially higher data rates than 51 Mb/s when there is only one user in a cable. Under this condition, data rates up to 155 Mb/s can be achieved over category 3 wiring and significantly higher rates can be achieved over high-performance category 5 wiring.>
Gi-Hong Im, Dale D. Harman, A. V. Mandzik, Mai-Huong Nguyen, Jean-Jacques Werner
IEEE J. Sel. Areas Commun.5
1993 Reducing the Complexities of TCP for a High Speed Networking Environment
abstract
The authors examine the data transfer phase of TCP (Transmission Control Protocol) to identify complex processing elements, where complexity is measured in terms of instruction counts. The objective is to reduce the complexity and improve the performance of TCP in a high speed networking environment, especially for bulk data transfer. It is found that most of the complexity is due to incomplete state information exchange with the peer, and to adapting to network dynamics using the current congestion control scheme. By partitioning of the protocol functionality into data and control information processing, along with the use of a rate based congestion control scheme, the complexity can be reduced by up to 67%. Performance can be further enhanced by running the new properly partitioned TCP in parallel as well as by simplifying the logic associated with some TCP timers.>
Mai-Huong Nguyen, Mischa Schwartz
INFOCOM1