460 research outputs found

    Why Hackers Love eHealth Applications

    Get PDF

    Source Behavior for ATM ABR Traffic Management: An Explanation

    Full text link
    The Available Bit Rate (ABR) service has been developed to support data applications over Asynchronous Transfer Mode (ATM) networks. The network continuously monitors its traffic and provides feedback to the source end systems. This paper explains the rules that the sources have to follow to achieve a fair and efficient allocation of network resources.Comment: IEEE Communications Magazine, November 1, 1996, vol 34, no11, pp50-5

    Performance of Bursty World Wide Web (WWW) Sources over ABR

    Full text link
    We model World Wide Web (WWW) servers and clients running over an ATM network using the ABR (available bit rate) service. The WWW servers are modeled using a variant of the SPECweb96 benchmark, while the WWW clients are based on a model by Mah. The traffic generated by this application is typically bursty, i.e., it has active and idle periods in transmission. A timeout occurs after given amount of idle period. During idle period the underlying TCP congestion windows remain open until a timeout expires. These open windows may be used to send data in a burst when the application becomes active again. This raises the possibility of large switch queues if the source rates are not controlled by ABR. We study this problem and show that ABR scales well with a large number of bursty TCP sources in the system.Comment: Submitted to WebNet `97, Toronto, November 9

    Performance and Buffering Requirements of Internet Protocols over ATM ABR and UBR Services

    Full text link
    The Asynchronous Transfer Mode (ATM) networks are quickly being adopted as backbones over various parts of the Internet. This paper analyzes the performance of TCP/IP protocols over ATM network's Available Bit Rate (ABR) and Unspecified Bit Rate (UBR) services. It is shown that ABR pushes congestion to the edges of the ATM network while UBR leaves it inside the ATM portion.Comment: IEEE Communications Magazine, Vol 36, no 6, pp152-15
    corecore