VC versus VP Merging in ATM Networks

        For the implementation of multipoint-to-point connections in ATM, various approaches exist, each with its own advantages and disadvantages. VP-based methods require unique sender identification but they do not require reassembly in merging points. In contrast, VC-based methods do not require unique sender identification but they
        do require reassembly in merging points. It is likely that VC merging will be the method of choice as it is scalable and yet relatively simple to implement. One of its drawbacks is the increased output buffer space required at the switches because of packet pseudo-reassembly at the merging points. This paper investigates the impact of the switch
        architecture and characteristics on the output buffer space by means of simulation. The results obtained demonstrate that for typical switch architectures, VC merging does not require significant additional buffering compared to VP merging.

By: A. L. Schmid, I. Iliadis and P. Droz

Published in: RZ3055 in 1998

LIMITED DISTRIBUTION NOTICE:

This Research Report is available. This report has been submitted for publication outside of IBM and will probably be copyrighted if accepted for publication. It has been issued as a Research Report for early dissemination of its contents. In view of the transfer of copyright to the outside publisher, its distribution outside of IBM prior to publication should be limited to peer communications and specific requests. After outside publication, requests should be filled only by reprints or legally obtained copies of the article (e.g., payment of royalties). I have read and understand this notice and am a member of the scientific community outside or inside of IBM seeking a single copy only.

rz3055.ps.Z

Questions about this service can be mailed to reports@us.ibm.com .