Medianet Reference Guide - Cisco
Medianet Reference Guide - Cisco
Medianet Reference Guide - Cisco
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Chapter 4<br />
<strong>Medianet</strong> QoS Design Considerations<br />
Drivers for QoS Design Evolution<br />
The combination of top-down and bottom-up media application proliferation places a heavy burden on<br />
the IT department as it struggles to cope with officially-supported and officially-unsupported, yet highly<br />
proliferated, media applications.<br />
The Convergence Within Media Applications<br />
Much like the integration of rich text and graphics into documentation, audio and video media continue<br />
to be integrated into many forms of communication. Sharing of information with E-mailed slide sets will<br />
gradually be replaced with E-mailed video clips. The audio conference bridge will be supplanted with<br />
the video-enabled conference bridge. Collaboration tools designed to link together distributed<br />
employees will increasingly integrate desktop video to bring teams closer together.<br />
<strong>Cisco</strong> WebEx is a prime example of such integration, providing text, audio, instant messaging,<br />
application sharing, and desktop video conferencing easily to all meeting participates, regardless of their<br />
location. Instead of a cumbersome setup of a video conference call, applications such as CUPC and<br />
WebEx greatly simplify the process and video capability is added to the conference just as easily as any<br />
other type of media, such as audio.<br />
The complexity that application presents to the network administrator relates to application<br />
classification: as media applications include voice, video, and data sub-components, the question of how<br />
to mark and provision a given media application becomes more difficult and blurry, as illustrated in<br />
Figure 4-3.<br />
Figure 4-3<br />
Media Application Convergence—Voice, Video, and Data Within an Application<br />
Data Convergence Media Explosion Collaborative Media<br />
Video<br />
Voice<br />
• Interactive Video<br />
• Streaming Video<br />
• IP Telephony<br />
Unmanaged<br />
Applications<br />
Video<br />
Voice<br />
• Internet Streaming<br />
• Internet VoIP<br />
• YouTube<br />
• MySpace<br />
• Other<br />
• Desktop Streaming Video<br />
• Desktop Broadcast Video<br />
• Digital Signage<br />
• IP Video Surveillance<br />
• Desktop Video Conferencing<br />
• HD Video<br />
• IP Telephony<br />
• HD Audio<br />
• SoftPhone<br />
• Other VoIP<br />
Ad-Hoc App<br />
TelePresence<br />
Data<br />
Apps<br />
• App Sharing<br />
• Web/Internet<br />
• Messaging<br />
• Email<br />
Data<br />
Apps<br />
• App Sharing<br />
• Web/Internet<br />
• Messaging<br />
• Email<br />
Data<br />
Apps<br />
• App Sharing<br />
• Web/Internet<br />
• Messaging<br />
• Email<br />
WebEx<br />
224515<br />
For example, since <strong>Cisco</strong> WebEx has voice, video, and data sub-components, how should it be classified?<br />
As a voice application? As a video application? As a data application? Or is an altogether new<br />
application-class model needed to accommodate multimedia applications?<br />
OL-22201-01<br />
<strong>Medianet</strong> <strong>Reference</strong> <strong>Guide</strong><br />
4-7