ys for execu- tion. See Table 3-1 for a list of requirements for multimedia applications. Table 3-1 Application Required Sensitivity Multimedia Bandwidth to Delay Application Requirements Voice Video Medium to high Medical Imaging Medium to high Web Surfing Medium Medium LAN Interconnection Low to high Electronic Mail Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website. Telephony Chapter 3 Meanwhile, Lucent created a new protocol called the Media Device Control Protocol (MDCP). The best features of the original three were combined to create a full-featured protocol called the MeGaCo, also defined as H.248. In March 1999, the IETF and ITU met collaboratively and created a formal technical agreement between the two organiza- tions, which resulted in a single protocol with two names. The IETF calls it MeGaCo, the ITU calls it H.GCP. MeGaCo/H.GCP operates under the assumption that network intelli- gence is housed in the central office, and therefore replaces the gate- keeper concept proposed by H.323. By managing multiple gateways within a single IP-equipped central office, MeGaCo minimizes the com- plexity of the telephone network. In other words, a corporation might be connected to an IP-capable central office, but because of the IP-capable switches in the CO which have the ability to convert between circuit- switched and packet-switched voice, full telephony features are possible. Thus the next generation switch converts between circuit and packet, while MeGaCo performs the signaling necessary to establish a call across an IP wide area network. It effectively bridges the gap between legacy SS7 signaling and the new requirements of IP, and supports both connection-oriented and connectionless services. A Final Thought: Network Management for QoS Because of the diverse audiences that require network performance information and the importance of servi