Deploying Next Generation Multicast-enabled Applications: Label Switched Multicast for MPLS VPNs, VPLS, and Wholesale Ethernet
560
Deploying Next Generation Multicast-enabled Applications: Label Switched Multicast for MPLS VPNs, VPLS, and Wholesale Ethernet
560eBook
Available on Compatible NOOK devices, the free NOOK App and in My Digital Library.
Related collections and offers
Overview
The book is written for engineers, technical managers, and visionaries engaged in the development of next-generation IP Multicast infrastructures.
- Offers contextualized case studies for illustrating deployment of the Next Generation Multicast technology
- Provides the background necessary to understand current generation multi-play applications and their service requirements
- Includes practical tips on various migration options available for moving to the Next Generation framework from the legacy
Product Details
| ISBN-13: | 9780123849243 |
|---|---|
| Publisher: | Elsevier Science |
| Publication date: | 08/20/2011 |
| Sold by: | Barnes & Noble |
| Format: | eBook |
| Pages: | 560 |
| File size: | 24 MB |
| Note: | This product may take a few minutes to download. |
About the Author
Srinivasarao Mulugu heads the Packet division of Nokia Siemens Networks in India. He has over 17 years of experience in the telecommunication industry spanning across North America, APAC, Middle East and India. During the course of his career, Srinivasarao has worked in various capacities at Cisco Systems, Juniper Networks, 3Com and Sprint Communications. He is also active in the industry forums and has chaired several technology sessions in forums such as SANOG, APRICOT, etc. He has an MS in Electrical Engineering and an MBA, both from University of Maryland, College Park, USA.
In his personal life Srinivasarao holds the position of Director Auromira Foundation and is involved in social welfare activities.
Read an Excerpt
Deploying Next Generation Multicast-Enabled Applications
Label Switched Multicast for MPLS VPNs, VPLS, and Wholesale EthernetBy Vinod Joseph Srinivas Mulugu
MORGAN KAUFMANN
Copyright © 2011 Elsevier Inc.All right reserved.
ISBN: 978-0-12-384924-3
Chapter One
Overview of IP Multicast
1.1 INTRODUCTION
Welcome to the world of IP Multicast and more important Multicast-based Virtual Private Networks (MVPNs). The objective of this book is to provide detailed information about existing Multicast and MVPN standards—the most recent are referred to as next-generation Multicast-based standards, Multicast Applications, and case studies with detailed configurations. Whenever a given topic of an advanced nature is discussed, the best way to relate to it is by looking at a relevant piece of configuration or a case study. That is exactly what we have done in this book with the three vendors: Juniper, Cisco, and Alcatel-Lucent. Therefore, a given illustration might contain a configuration of JUNOS, TiMOS (Alcatel's OS), or Cisco IOS, and each of the configurations will be explained in great detail. The reason we chose various vendor configurations instead of just one is to provide diversity. Also, the intent of this book is to tell you where the industry at large is moving to, not to be vendor centric. As engineers, technical managers, and visionaries in building next-generation IP Multicast infrastructures, we are more interested in standards and areas where there is consensus rather than looking at proprietary implementations. The illustrations provided in this book do not represent a given vendor's hardware or software unless explicitly mentioned. Therefore, do not assume that a particular illustration is relevant to any one vendor. Similarly, a configuration template provided regarding a solution/technology does not necessarily indicate that the implementation is only supported by that vendor. Specific details on a vendor's unique implementation of a standard or Internet Engineering Task Force (IETF) draft will be explicitly mentioned. With this short introduction, We will continue on with this interesting journey.
1.1.1 Overview of IP Multicast
Some of the information provided in this chapter will be repeated in other chapters to refresh our memories and provide the relevance needed for that specific chapter. Traditional IP communications allow a host to send packets to another host (unicast transmissions) or to all hosts (broadcast transmissions). IP Multicast provides a third communication alternative—allowing a host to send packets to a group made up of a subset of the hosts on the network. IP Multicast is a bandwidth-conserving technology specifically designed to reduce traffic by simultaneously delivering a single stream of information to potentially thousands of corporate recipients or homes. There are three modes of communication: Unicast, Broadcast, and Multicast (see Figure 1.1).
By replacing copies for all recipients with the delivery of a single stream of information, IP Multicast is able to minimize the burden on both sending and receiving hosts and reduce overall network traffic. Within a multicast network, routers are responsible for replicating and distributing multicast content to all hosts listening to a particular multicast group. Routers employ Protocol Independent Multicast (PIM) to build distribution trees for transmitting multicast content, resulting in the most efficient delivery of data to multiple receivers. Alternatives to IP Multicast require the source to send more than one copy of the data. Traditional application-level unicast, for example, requires the source to transmit one copy for each individual receiver in the group. There are two scenarios: without Multicast in the network and traffic delivery with Multicast (see Figure 1.2).
The same scenario changes when there is Multicast in the network. This is illustrated in Figure 1.3. IP Multicast solutions offer benefits relating to the conservation of network bandwidth. In a high-bandwidth application, such as MPEG video, IP Multicast can benefit situations with only a few receivers, because video streams would otherwise consume a large portion of the available network bandwidth. Even for low-bandwidth applications, IP Multicast conserves resources when transmissions involve thousands of receivers. Additionally, IP Multicast is the only non-broadcasting alternative for situations that require simultaneously sending information to more than one receiver. For low-bandwidth applications, an alternative to IP Multicast could involve replicating data at the source. This solution, however, can deteriorate application performance, introduce latencies and variable delays that impact users and applications, and require expensive servers to manage the replications and data distribution. Such solutions also result in multiple transmissions of the same content, consuming an enormous amount of network bandwidth. For most high-bandwidth applications, these same issues make IP Multicast the only viable option. Today, many applications take advantage of multicast, as shown in Figure 1.4. Other applications that take advantage of IP Multicast include:
• Corporate communications
• Consumer television and music channel delivery
• Distance learning (e.g., e-learning) and white-boarding solutions
• IP surveillance systems
• Interactive gaming
IP Multicast is also supported in
• IPv4 networks
• IPv6 networks
• Multiprotocol Label Switching (MPLS) VPNs
• Mobile and wireless networks
IP Multicast capabilities can be deployed using a variety of different protocols, conventions, and considerations suited to the different network environments just mentioned. Multicast services can also be deployed across multiple protocol platforms and domains within the same network. By implementing native IP Multicast functionality inside MPLS VPN networks, service providers can more efficiently deliver bandwidth-intensive streaming services such as telecommuting, videoconferencing, e-learning, and a host of other business applications. Multicast VPN technology eliminates the packet replication and performance issues associated with the traffic relating to these applications. Multicast MPLS VPNs further benefit service providers by
• Minimizing configuration time and complexity; configuration is required only at edge routers
• Ensuring transparency of the service provider network
• Providing the ability to easily build advanced enterprise-friendly services such as Virtual Multicast Networks
• Increasing network scalability
IP Multicast can work with Mobile Networks. An IP Mobility platform extends the network with traditional fixed-line access to an environment that supports mobile wireless access. Multicast, from the point of IP Mobility, is a network service or application. Within an IP Mobility environment, IP Multicast can be employed to deliver content to users with wireless devices.
Over the past decade, enterprise and public sector adoption of IP Multicast-enabled applications has skyrocketed, and service providers have responded by increasingly adding multicast VPNs to service portfolios. Today, any service provider with enterprise customers must support IP Multicast to remain competitive. The deployment of video services provides further incentives for the strengthening of a service provider's multicast platform, because it offers the most efficient, cost-effective means of supporting triple-play traffic (data, voice, and video).
1.1.2 Multicast Addressing
1.1.2.1 Layer 3 Multicast Addressing
IP multicast uses the Class D range of IP addresses (224.0.0.0 through 239.255.255.255; see Figure 1.5). Within the IP multicast Class D address range, there are a number of addresses reserved by the Internet Assigned Numbers Authority (IANA). These addresses are reserved for well-known multicast protocols and applications, such as routing protocol Hellos. Examples of special and reserved Class D addresses are given in Figure 1.6. Table 1.1 summarizes the IANA allocations for the Class D range and the recommendations as per RFC 2365.
The usage of these address ranges are as follows:
• The Local Link Scope (224.0.0.0) addresses have been reserved by IANA for use by network protocol. Packets using this range are local in scope and are not forwarded by Multicast routers regardless of the TTL.
• The Global Scope (224.0.1.0–238.255.255.255) is reserved for network-wide protocols and commercial Internet multicast applications. These addresses can transit Administrative boundaries and are globally (Internet wide) unique.
• (RFC 2365) The ranges 239.0.0.0/10, 239.64.0.0/10, and 239.128.0.0/10 are unassigned and available for expansion of the Organizational Local Scope. However, these ranges should be left unassigned until the 239.192.0.0/14 space is no longer sufficient. This is to allow for the possibility that future revisions of RFC 2365 may define additional scopes on a scale larger than organizations (hence the name Greater than Organizational Scope)
• (RFC 2365) The Organizational Local Scope (239.192.0.0/14) is the space from which the Service Provider should allocate groups for the Default and Data MDTs to support multicast VPN. However, they should not be used outside the Service Provider, unless by agreement with interconnected service providers. The multicast groups from these ranges will be used by all PE routers to identify associated MDTs for particular VPNs. The addresses in the Organizational Local Scope can be used across the Service Provider as defined by that service provider.
• (RFC 2365) The Site Local Scope (239.255.0.0/16) addresses represent applications that are confined to within local boundaries. For example, the same 239.255.0.0/16 range could be reused across all precincts in a Service Provider as long as the address was contained within that precinct. RFC 2365 states that the range must not be subdivided for use across sites; therefore all sources in that precinct will be uniquely identified within the range. The groups from this scope must not be advertised across the network into other precincts, as each precinct could use the same Site Local Scope to define local multicast services.
The following are some of the options available for the Multicast Address design within a Service Provider Network. More details on Source Specific Multicast (SSM) can be found in the following sections:
• SSM group range of 232.x.x.x
• Administratively scoped Multicast range of 239.x.x.x
• Private SSM range (part of admin scoped range) of 239.232.x.x
1.1.2.1.1 Ad Hoc Multicast Block
The multicast group range of 224.0.2.0 through 224.0.255.255 is the ad hoc multicast block. Historically, addresses in this range have been assigned to applications that do not clearly fall into the Local Network Control and Inter-Network Control categories. In general, the guidelines provided in RFC 3171bis for the assignment of addresses in this range state that the IANA should not assign addresses in this range except under very special circumstances. Even then, the assignment must undergo a strict Expert Review, IESG Approval, or Standards Action process before addresses are assigned.
1.1.2.1.2 SDP/SAP Multicast Block
The multicast group range of 224.2.0.0 through 224.2.255.255 (224.2/16) is the SDP/SAP Multicast Block, which is reserved for applications that send and receive multimedia session announcements via the Session Announcement Protocol (SAP) described in RFC 2974. An example of an application that uses SAP is the Session Directory tool (SDR), which transmits global scope SAP announcements on groups 224.2.127.254 and 224.2.127.255.
1.1.2.2 GLOP Multicast Block
This block of addresses has been assigned by the IANA as an experimental, statically assigned range of multicast addresses intended for use by Content Providers, ISPs, or anyone wishing to source content into the global Internet. This allocation methodology, called GLOP addressing, which is defined in RFC 2770, uses the multicast group range of 233.0.0.0 through 233.255.255.255 (233/8) and provides each Autonomous System (AS) with a block of 255 statically assigned multicast addresses. Content Providers who wish to transmit multicast traffic to their customers in the Internet and that have an assigned Autonomous System Number (ASN) can use multicast addresses from their block of 255 static GLOP addresses to transmit content. If the content provider does not have its own assigned ASN, it can usually lease static GLOP addresses from their ISP.
(Continues...)
Excerpted from Deploying Next Generation Multicast-Enabled Applications by Vinod Joseph Srinivas Mulugu Copyright © 2011 by Elsevier Inc.. Excerpted by permission of MORGAN KAUFMANN. All rights reserved. No part of this excerpt may be reproduced or reprinted without permission in writing from the publisher.
Excerpts are provided by Dial-A-Book Inc. solely for the personal use of visitors to this web site.
Table of Contents
1. Overview of IP2. Draft Rosen-based Multicast VPNs3. Next Generation Multicast VPNs4. Internet Multicast and Multicast VPN based on MLDP In-Band Signalling5. Understanding Multicast Applications and Service Requirements6. Applications: IPTV7. Virtual Private LAN Services aka VPLS8. Mobile Video Multicast9. SummaryWhat People are Saying About This
The definitive guide for implementing the Next Gen Multicast Network model of deploying streaming media, IPTV, VPN, and other content distribution applications.