Скачать презентацию Deployment of IP Multicast in Campus Infrastructures Kevin Скачать презентацию Deployment of IP Multicast in Campus Infrastructures Kevin

367c7a0bb94b55f45d78adbc99f1f9aa.ppt

  • Количество слайдов: 25

Deployment of IP Multicast in Campus Infrastructures Kevin Almeroth (almeroth@cs. ucsb. edu) UC--Santa Barbara Deployment of IP Multicast in Campus Infrastructures Kevin Almeroth ([email protected] ucsb. edu) UC--Santa Barbara http: //www. internet 2. edu/multicast/ http: //www. cs. ucsb. edu/~almeroth/talks/I 2 -ATL-01. ppt 1

Outline • multicast protocols overview—see the WWW site – super-brief overview • • state Outline • multicast protocols overview—see the WWW site – super-brief overview • • state of deployment getting started with deployment working group activities addendum: router configs—see the WWW site 2

Unicast source performs routing and forwarding at the same time, and in the source-to-receiver Unicast source performs routing and forwarding at the same time, and in the source-to-receiver direction 3

Multicast Routing (and Functions) source routing (path determination) [but in the reverse direction] packet Multicast Routing (and Functions) source routing (path determination) [but in the reverse direction] packet forwarding and replication handling dynamic membership---path pruning/grafting 4

Building the Reverse Path source 5 Building the Reverse Path source 5

Building an RP Tree source 6 Building an RP Tree source 6

Forwarding Data source routing (path determination) [but in the reverse direction] packet forwarding and Forwarding Data source routing (path determination) [but in the reverse direction] packet forwarding and replication handling dynamic membership---path pruning/grafting 7

Question for the Ages source How to find the source(s)? 8 Question for the Ages source How to find the source(s)? 8

How to Find the Sources? • broadcast everywhere – receivers decide when they do How to Find the Sources? • broadcast everywhere – receivers decide when they do not want the traffic • any source multicast (ASM) [PIM-SM/MBGP/MSDP/IGMPv 2] – use a rendezvous point (RP) – receivers send joins along reverse path to RP – sources send traffic to RP • source specific multicast (SSM) [PIM/MBGP/IGMPv 3] – require receivers to already know source(s) – use some out-of-band mechanism 9

How MSDP works with PIM-SM A SA RP Source C D SA Join B How MSDP works with PIM-SM A SA RP Source C D SA Join B Join RP RP Join Receiver RP SA MSDP peer PIM message Physical link MSDP message 10

How SSM Works A Source C D Join B Join Join Receiver PIM message How SSM Works A Source C D Join B Join Join Receiver PIM message Physical link 11

State of Deployment 12 State of Deployment 12

Status of the Multicast Pieces (Support for IGMPv 2 & PIM-SM/MBGP/MSDP) • network: lots Status of the Multicast Pieces (Support for IGMPv 2 & PIM-SM/MBGP/MSDP) • network: lots of vendors support multicast routing: Cisco & Juniper then Nortel, Foundry, Lucent, others, etc. • OSs/kernel: most kernels support functions (IGMPv 2) • applications: – MBone tools (http: //www-mice. cs. ucl. ac. uk/multimedia/software/) – IPTV, Real, Media. Player, and now LOTS others… 13

Status of the Multicast Pieces (Support for IGMPv 2 & PIM-SM/MBGP/MSDP) • content: – Status of the Multicast Pieces (Support for IGMPv 2 & PIM-SM/MBGP/MSDP) • content: – Uof. O (http: //videolab. uoregon. edu/) – GRID (http: //www-fp. mcs. anl. gov/fl/accessgrid/) – ICAIR CSPAN (http: //cspan. icair. org/) – On-the-I (http: //www. on-the-i. com/) – Yahoo (http: //www. broadcast. com/broadband/) – NASA (http: //www. nasa. gov/ntvweb. html) – UCSB (http: //imj. gatech. edu/) – All the commodity traffic (sdr) 14

Status of the Multicast Pieces (Support for IGMPv 3 & SSM) • network: most Status of the Multicast Pieces (Support for IGMPv 3 & SSM) • network: most vendors already support it since functionality in the core has been simplified • OSs/kernel: test kernels available – http: //videolab. uoregon. edu/projects. html • applications: lots of talk, but not much action – http: //videolab. uoregon. edu/projects. html • content: without supporting software/hardware, content is not there 15

Status of Deployment • nice and stable in Abilene (since early 1999) • some Status of Deployment • nice and stable in Abilene (since early 1999) • some commercial ISPs… – but typically service is not announced and is not supported – issues are beginning to be only political/financial (layers 8&9) • to track multicast deployment and stats… – see http: //imj. ucsb. edu/mantra/ – see http: //dast. nlanr. net/projects/beacon/ 16

Latest Multicast Topology 17 Latest Multicast Topology 17

The Internet 2 (Abilene) Topology 18 The Internet 2 (Abilene) Topology 18

19 19

Site Deployment: Getting Started and Using Multicast 20 Site Deployment: Getting Started and Using Multicast 20

Deploying Multicast Locally • experiment with multicast on a local network • try one- Deploying Multicast Locally • experiment with multicast on a local network • try one- or few-hop multicast topology • connect to I 2 • experiment with advanced applications • transition to production service 21

Resources • I 2 multicast WWW page – http: //www. internet 2. edu/multicast/ • Resources • I 2 multicast WWW page – http: //www. internet 2. edu/multicast/ • I 2 multicast mailing list – send email to [email protected] 2. edu with: subscribe wg-multicast Your-Name – in the body of the message • I 2 multicast working group meetings – at Joint Techs meetings (http: //www. ncne. nlanr. net/training/techs/) 22

Working Group Activities • Continue robust backbone service – track deployment and use – Working Group Activities • Continue robust backbone service – track deployment and use – support Source Specific Multicast (SSM) – provide support for gigapop and campus deployment • Increase deployment – campuses, international and commodity peering – provide assistance beyond the NOC 23

Working Group Activities • Increase use of multicast – encourage campuses to offer events Working Group Activities • Increase use of multicast – encourage campuses to offer events – advertise availability of events to non-geeks – new service to track events • Increase variety of applications – create opportunities to use multicast in novel ways – new service to track tools/applications 24

Conclusions • Stable backbone – Key first step • Deployment in some campuses (low Conclusions • Stable backbone – Key first step • Deployment in some campuses (low hanging fruit) • Working on building a robust service – More than just one-to-many packet delivery • applications, support, service, etc. – Lots of issues with legacy infrastructure 25