The Experts below are selected from a list of 39 Experts worldwide ranked by ideXlab platform

L. Iftode - One of the best experts on this subject based on the ideXlab platform.

  • Migratory TCP: connection migration for service continuity in the Internet
    Proceedings 22nd International Conference on Distributed Computing Systems, 2002
    Co-Authors: F. Sultan, K. Srinivasan, D. Iyer, L. Iftode
    Abstract:

    Today's Internet services are commonly built over TCP, the standard Internet connection-oriented reliable transport protocol. The Endpoint naming scheme of TCP, based on network layer (IP) addresses, creates an implicit binding between a service and the IP address of a server providing it, throughout the lifetime of a client connection. This makes a TCP client prone to all adverse conditions that may affect the server Endpoint or the internetwork in between, after the connection is established: congestion or failure in the network, server overloaded, failed or under DoS attack. Studies that quantify the effects of network stability and route availability demonstrate that connectivity failures can significantly impact Internet services. As a result, although highly available servers can be deployed, sustaining continuous service remains a problem. We propose cooperative service model, in which a pool of similar servers, possibly geographically distributed across the Internet, cooperate in sustaining a service by migration of client connections within the pool. The control traffic between servers, needed to support migrated connections, can be carried either over the Internet or over a private network. From client's viewpoint, at any point during the lifetime of its service session, the Remote Endpoint of its connection may transparently migrate between servers.

  • ICDCS - Migratory TCP: connection migration for service continuity in the Internet
    Proceedings 22nd International Conference on Distributed Computing Systems, 2002
    Co-Authors: F. Sultan, K. Srinivasan, D. Iyer, L. Iftode
    Abstract:

    Today's Internet services are commonly built over TCP, the standard Internet connection-oriented reliable transport protocol. The Endpoint naming scheme of TCP, based on network layer (IP) addresses, creates an implicit binding between a service and the IP address of a server providing it, throughout the lifetime of a client connection. This makes a TCP client prone to all adverse conditions that may affect the server Endpoint or the internetwork in between, after the connection is established: congestion or failure in the network, server overloaded, failed or under DoS attack. Studies that quantify the effects of network stability and route availability demonstrate that connectivity failures can significantly impact Internet services. As a result, although highly available servers can be deployed, sustaining continuous service remains a problem. We propose cooperative service model, in which a pool of similar servers, possibly geographically distributed across the Internet, cooperate in sustaining a service by migration of client connections within the pool. The control traffic between servers, needed to support migrated connections, can be carried either over the Internet or over a private network. From client's viewpoint, at any point during the lifetime of its service session, the Remote Endpoint of its connection may transparently migrate between servers.

Christian Jacquenet - One of the best experts on this subject based on the ideXlab platform.

  • Negotiating the Maximum Number of Multipath TCP (MPTCP) Subflows
    2016
    Co-Authors: Mohamed Boucadair, Christian Jacquenet
    Abstract:

    This document specifies an experimental Multipath TCP (MPTCP) option that is meant to negotiate the maximum number of subflows that can be established and maintained for a given MPTCP connection. The purpose is to minimize any possible performance degradation that can be induced by a possibly large number of establishment requests for additional subflows if the Remote Endpoint is not appropriately dimensioned to handle such requests.

  • Negotiating the Maximum Number of MPTCP Subflows
    2015
    Co-Authors: Mohamed Boucadair, Christian Jacquenet
    Abstract:

    This document specifies an experimental MPTCP option that is meant to negotiate the maximum number of subflows that can be established and maintained for a given MPTCP connection. The purpose is to minimize any possible performance degradation that can be induced by a possibly large number of establishment requests for additional subflows if the Remote Endpoint is not appropriateley dimensioned to handle such requests.

R.h. Wang - One of the best experts on this subject based on the ideXlab platform.

  • Channel delay impact on TCP and SCPS-TP over LEO/GEO-stationary space links
    Proceedings. 13th International Conference on Computer Communications and Networks (IEEE Cat. No.04EX969), 2004
    Co-Authors: R.h. Wang
    Abstract:

    A substantially long round trip time (RTT) in space channel hurts TCP interactions between the sending and receiving sides, and limits the usefulness and effectiveness of TCP feedback from the Remote Endpoint for space communications. Space communication protocol standards-transport protocol (SCPS-TP) is a set of extensions to transmission control protocol (TCP) aimed at improving TCP performance in space communications. Some work has been done on performance comparison between SCPS-TP and the widely used TCP. It is expected to have an evaluation of SCPS-TP in coping with long channel delay which is one of the primary features in space communications. This paper describes an experimental evaluation of channel delay impact on throughput performance of SCPS-TP over LEO/GEO-stationary space links using a test-bed, by comparing it with the widely used TCP

Ruhai Wang - One of the best experts on this subject based on the ideXlab platform.

  • ICCCN - Channel delay impact on TCP and SCPS-TP over LEO/GEO-stationary space links
    Proceedings. 13th International Conference on Computer Communications and Networks (IEEE Cat. No.04EX969), 2004
    Co-Authors: Ruhai Wang
    Abstract:

    A substantially long round trip time (RTT) in space channel hurts TCP interactions between the sending and receiving sides, and limits the usefulness and effectiveness of TCP feedback from the Remote Endpoint for space communications. Space communication protocol standards-transport protocol (SCPS-TP) is a set of extensions to transmission control protocol (TCP) aimed at improving TCP performance in space communications. Some work has been done on performance comparison between SCPS-TP and the widely used TCP. It is expected to have an evaluation of SCPS-TP in coping with long channel delay which is one of the primary features in space communications. This paper describes an experimental evaluation of channel delay impact on throughput performance of SCPS-TP over LEO/GEO-stationary space links using a test-bed, by comparing it with the widely used TCP

F. Sultan - One of the best experts on this subject based on the ideXlab platform.

  • Migratory TCP: connection migration for service continuity in the Internet
    Proceedings 22nd International Conference on Distributed Computing Systems, 2002
    Co-Authors: F. Sultan, K. Srinivasan, D. Iyer, L. Iftode
    Abstract:

    Today's Internet services are commonly built over TCP, the standard Internet connection-oriented reliable transport protocol. The Endpoint naming scheme of TCP, based on network layer (IP) addresses, creates an implicit binding between a service and the IP address of a server providing it, throughout the lifetime of a client connection. This makes a TCP client prone to all adverse conditions that may affect the server Endpoint or the internetwork in between, after the connection is established: congestion or failure in the network, server overloaded, failed or under DoS attack. Studies that quantify the effects of network stability and route availability demonstrate that connectivity failures can significantly impact Internet services. As a result, although highly available servers can be deployed, sustaining continuous service remains a problem. We propose cooperative service model, in which a pool of similar servers, possibly geographically distributed across the Internet, cooperate in sustaining a service by migration of client connections within the pool. The control traffic between servers, needed to support migrated connections, can be carried either over the Internet or over a private network. From client's viewpoint, at any point during the lifetime of its service session, the Remote Endpoint of its connection may transparently migrate between servers.

  • ICDCS - Migratory TCP: connection migration for service continuity in the Internet
    Proceedings 22nd International Conference on Distributed Computing Systems, 2002
    Co-Authors: F. Sultan, K. Srinivasan, D. Iyer, L. Iftode
    Abstract:

    Today's Internet services are commonly built over TCP, the standard Internet connection-oriented reliable transport protocol. The Endpoint naming scheme of TCP, based on network layer (IP) addresses, creates an implicit binding between a service and the IP address of a server providing it, throughout the lifetime of a client connection. This makes a TCP client prone to all adverse conditions that may affect the server Endpoint or the internetwork in between, after the connection is established: congestion or failure in the network, server overloaded, failed or under DoS attack. Studies that quantify the effects of network stability and route availability demonstrate that connectivity failures can significantly impact Internet services. As a result, although highly available servers can be deployed, sustaining continuous service remains a problem. We propose cooperative service model, in which a pool of similar servers, possibly geographically distributed across the Internet, cooperate in sustaining a service by migration of client connections within the pool. The control traffic between servers, needed to support migrated connections, can be carried either over the Internet or over a private network. From client's viewpoint, at any point during the lifetime of its service session, the Remote Endpoint of its connection may transparently migrate between servers.