MulticastSummary.ppt

3,391 views

Published on

0 Comments
6 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,391
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
255
Comments
0
Likes
6
Embeds 0
No embeds

No notes for slide
  • Video conference Distance learning
  • Broadcast and unicast can be seen as two special types of Multicast
  • MulticastSummary.ppt

    1. 1. Summary of IP Multicast CPSC 601.43 Course Director: Dr. Anirban Mahanti Student : Liqi Shi
    2. 2. Outline <ul><li>Introduction to Multicast </li></ul><ul><li>Multicast Group and Service Model </li></ul><ul><li>Multicast Routing </li></ul><ul><li>Deployment Issues of Multicast </li></ul><ul><li>EXPRESS </li></ul><ul><li>References </li></ul>
    3. 3. 1 Introduction to Multicast <ul><li>1.1 Why Multicast /Multicast Applications </li></ul><ul><li>1.2 Broadcast/Unicast/Multicast </li></ul>
    4. 4. 1.1 Why Multicast /Multicast Applications <ul><li>Same data sent to multiple receivers </li></ul><ul><li>To use the bandwidth efficiently </li></ul><ul><li>Reduce routing processing </li></ul><ul><li>Sender doesn’t get receiver’s address </li></ul>
    5. 5. 1.1 Why Multicast /Multicast Applications <ul><li>Video/audio conference </li></ul><ul><li>IP TV, Video on Demand </li></ul><ul><li>Advertisement, Stock, Distance learning </li></ul><ul><li>Synchronizing of distributed database, websites </li></ul>
    6. 6. 1.1 Why Multicast /Multicast Applications <ul><li>ConferenceXP: An Example of Multicast application </li></ul>Video Conference Distance Learning
    7. 7. 1.2 Broadcast/Unicast/Multicast <ul><li>Broadcast: One sender, all the others as receivers </li></ul><ul><li>Unicast: One sender and one receiver </li></ul><ul><li>Multicast: One sender (potentially many senders), many receivers </li></ul><ul><li>You can take broadcast and unicast as two special types of multicast </li></ul>
    8. 8. 1.2 Broadcast/Unicast/Multicast UNICAST With 4 receivers, sender must replicate the stream 4 times
    9. 9. 1.2 Broadcast/Unicast/Multicast <ul><li>MULTICAST </li></ul><ul><li>Source transmits one stream of data for n receivers </li></ul><ul><li>Replication happens inside routers and switches </li></ul><ul><li>WAN links only need one copy of the data, not n copies. </li></ul>
    10. 10. 2 Multicast Group and Service Model <ul><li>Each multicast group is identified by a class D IP address </li></ul><ul><li>Members of the group could be anywhere in the Internet </li></ul><ul><li>Members can join and leave the group and indicate this to the routers </li></ul><ul><li>Senders and receivers are distinct: i.e., a sender need not be a member, but receivers should be </li></ul><ul><li>Routers listen to all multicast addresses and use multicast routing protocols to manage groups (IGMP) </li></ul>
    11. 11. 2 Multicast Group and Service Model <ul><li>Multicast Address </li></ul><ul><ul><li>IP reserved class D addresses for multicast 224.0.0.0~239.255.255.255 </li></ul></ul><ul><ul><li>Base address: 224.0.0.0 is reserved </li></ul></ul><ul><ul><li>224.0.0.1~224.0.0.255 are devoted to multicast routing and group maintenance protocols </li></ul></ul><ul><ul><li>Multicast addresses can only be used as destination </li></ul></ul><ul><ul><li>No ICMP error messages can be generated for multicast datagram </li></ul></ul>
    12. 12. 2 Multicast Group and Service Model <ul><ul><li>Mapping IP Multicast to Ethernet Multicast: Place the lower 23 bits of the IP multicast address into the lower 23 bits of special Ethernet multicast address 01.00.5E.00.00.00. 32 multicast groups may be mapped into the same address. Probability is small, but receivers should check the datagram </li></ul></ul>
    13. 13. 3 Multicast Routing <ul><li>3.1 Transmission and Delivery of Multicast Datagram </li></ul><ul><li>3.2 Internet Group Management Protocol (IGMP) </li></ul><ul><li>3.3 Multicast Forwarding Algorithms </li></ul><ul><ul><li>Flooding </li></ul></ul><ul><ul><li>Spanning Trees </li></ul></ul><ul><ul><li>Reverse Path Broadcasting (RPB) </li></ul></ul><ul><ul><li>Truncated Reverse Path Broadcasting (TRPB) </li></ul></ul><ul><ul><li>Reverse Path Multicasting (RPM) </li></ul></ul><ul><ul><li>Core Based Trees (CBT) </li></ul></ul><ul><li>3.4 Multicast Protocols </li></ul><ul><ul><li>Distance Vector Multicast Routing Protocol (DVMRP) </li></ul></ul><ul><ul><li>Multicast OSPF (MOSPF) </li></ul></ul><ul><ul><li>Protocol-Independent Multicast (PIM) </li></ul></ul><ul><ul><li>BGMP and MASC </li></ul></ul>
    14. 14. 3.1 Transmission and Delivery of Multicast Datagram <ul><li>Local subnetwork transmission </li></ul><ul><li>The source station simply addresses the IP packet to the multicast group, the network interface card maps the Class D address to the corresponding Ethernet multicast address, and the frame is sent. Receivers that wish to capture the frame notify their IP layer that they want to receive datagrams addressed to the group </li></ul><ul><li>Transmission throughout the Internet </li></ul><ul><li>Routers are required to implement a multicast routing protocol that permits the construction of multicast delivery trees and supports multicast data packet forwarding. In addition, each router needs to implement a group membership protocol (IGMP) that allows it to learn about the existence of group members on its directly attached subnetwork </li></ul>
    15. 15. 3.2 Internet Group Management Protocol (IGMP) <ul><li>Introduction </li></ul><ul><li>IGMP runs between hosts and the nearest multicast routers. A local host can use it to inform the router which multicast group it wants to be added in, while the multicast routers can use it to poll the LAN periodically, thus determine if known group members are still active </li></ul><ul><li>IGMP message format </li></ul>0 8 16 32 Membership report (V1) Leave group Membership report Specific membership query General membership query Meaning used used used used unused Group Address 0x12 0x17 0x16 0x11 0x11 Type
    16. 16. 3.2 Internet Group Management Protocol (IGMP) <ul><li>IGMP versions </li></ul><ul><ul><li>RFC1112, IGMP version 1 </li></ul></ul><ul><ul><li><draft-ietf-idmr-igmp-v2-01.txt>, IGMP version2 </li></ul></ul><ul><ul><ul><li>defines a procedure for the election of the multicast querier for each LAN </li></ul></ul></ul><ul><ul><ul><li>defines a new type of Query message-the Group-Specific Query message </li></ul></ul></ul><ul><ul><ul><li>defines a Leave Group message </li></ul></ul></ul><ul><ul><li><draft-cain-igmp-00. txt>, IGMP version 3 </li></ul></ul><ul><ul><ul><li>introduces support for Group-Source Report messages so that a host can elect to receive traffic from specific sources of a multicast group </li></ul></ul></ul><ul><ul><ul><li>support for Leave Group messages first introduced in IGMP Version 2 has been enhanced to support Group-Source Leave messages. This feature allows a host to leave an entire group or to specify the specific IP address(es) of the (source, group) pair(s) that it wishes to leave </li></ul></ul></ul>
    17. 17. 3.2 Internet Group Management Protocol (IGMP) <ul><li>How it works </li></ul><ul><ul><li>One host joins a group </li></ul></ul><ul><ul><ul><li>Newly joined host in a group sends IGMP message to group multicast address declaring membership. </li></ul></ul></ul><ul><ul><ul><li>Local multicast router receives the message and establishes necessary routing path </li></ul></ul></ul><ul><ul><li>Group membership report </li></ul></ul><ul><ul><ul><li>Router sends Host Membership Query to 224.0.0.1 (all multicast hosts on a subnet) </li></ul></ul></ul><ul><ul><ul><li>Host responds with Host Membership report for each group to which it belongs ( sent to group address) </li></ul></ul></ul><ul><ul><ul><li>other hosts in the same group “suppress” reports </li></ul></ul></ul><ul><ul><ul><li>Router periodically broadcasts query to detect if groups have gone away </li></ul></ul></ul>
    18. 18. 3.2 Internet Group Management Protocol (IGMP) <ul><li>Each host responds to the query with a random delay. If one report is received at the router, the other reports will be suppressed </li></ul>
    19. 19. 3.3 Multicast Forwarding Algorithms <ul><li>Introduction: IGMP is responsible for delivering packets from a local router to directly attached subnetwork. To forwarding multicast packets across internet, we should use multicast protocols. Several algorithms may be used by the protocols. </li></ul><ul><li>3.3.1 Flooding </li></ul><ul><li>3.3.2 Spanning Trees </li></ul><ul><li>3.3.3 Reverse Path Broadcasting (RPB) </li></ul><ul><li>3.3.4 Truncated Reverse Path Broadcasting (TRPB) </li></ul><ul><li>3.3.5 Reverse Path Multicasting (RPM) </li></ul><ul><li>3.3.6 Core Based Trees (CBT) </li></ul>
    20. 20. 3.3.1 Flooding <ul><li>When a router receives a packet, the router will determine whether it’s the first time it receives the packet. If so, the packet will be delivered to all interfaces except the one on which it arrived, otherwise the packet will be discarded. </li></ul><ul><li>No routing tables needed </li></ul><ul><li>Inefficient use of bandwidth </li></ul>SRC Non-red streams will be discarded according to flooding algorithm
    21. 21. 3.3.2 Spanning Tree <ul><li>Only one active path connects any two of routers </li></ul><ul><li>The multicast packets will not loop and reach all routers </li></ul><ul><li>May not provide the most efficient path between the source subnetwork and group members </li></ul>
    22. 22. 3.3.3 Reverse Path Broadcasting (RPB) <ul><li>A local router only accepts packets from the ‘nearest’ source (parent), otherwise the packets are discarded </li></ul><ul><li>Accepted packets will be forwarded to all interfaces except the source </li></ul><ul><li>it does not take into account multicast group membership when building the distribution tree, so packets may be forwarded to non-membership subnetwork </li></ul>
    23. 23. 3.3.4 Truncated Reverse Path Broadcasting (TRPB) <ul><li>It’s an enhancement of RPB </li></ul><ul><li>With the help of IGMP, multicast routers determine the group membership on each leaf subnetwork, thus avoiding forwarding packets to non-members </li></ul><ul><li>Eliminates unnecessary traffic on leaf subnetworks , but does not consider group memberships when building the branches of the distribution tree </li></ul>Source,G1 G1 G2 G3 Truncated
    24. 24. 3.3.5 Reverse Path Multicasting (RPM) <ul><li>RPM creates a delivery tree that spans only </li></ul><ul><ul><li>Subnetworks with group members, and </li></ul></ul><ul><ul><li>Routers along the shortest path to subnetworks with group members </li></ul></ul><ul><li>First packet will be sent to all interfaces except the source. If none of the subnetworks connected to the leaf router have group members, the leaf router may transmit a &quot;prune&quot; message on its parent link informing the upstream router not to forward packets in this group to the leaf </li></ul><ul><li>In RPM, ‘first packet’ still needs to be forwarded throughout the network. </li></ul><ul><li>Each router has to maintain state information for all groups. It will be impossible as the number of groups and sources increases. </li></ul>
    25. 25. 3.3.5 Reverse Path Multicasting (RPM) Source, G G G First packet of G G Member subnetwork Non-member subnetwork Prune message
    26. 26. 3.3.6 Core Based Trees (CBT) <ul><li>There is a backbone for CBT. It includes both core and non-core routers. </li></ul>
    27. 27. 3.3.6 Core Based Trees (CBT) <ul><li>If a host wants to join one group, it has to send a unicast “join request” message to the core. The nearest router in the backbone will respond with ACK and the intermediate routers will record the routing information, thus a delivery tree for a group is established </li></ul><ul><li>Compared to previous algorithms, CBT can use bandwidth and router resources more efficiently </li></ul><ul><li>CBT may result in traffic concentration and bottlenecks near core routers since traffic from all sources traverses the same set of links as it approaches the core </li></ul><ul><li>A single shared tree may create trees not as optimal as source-trees </li></ul>
    28. 28. 3.4 Multicast Protocols <ul><li>3.4.1 Distance Vector Multicast Routing Protocol (DVMRP) </li></ul><ul><li>3.4.2 Multicast OSPF (MOSPF) </li></ul><ul><li>3.4.3 Protocol-Independent Multicast (PIM) </li></ul><ul><li>3.4.4 BGMP and MASC </li></ul>
    29. 29. 3.4.1 Distance Vector Multicast Routing Protocol (DVMRP) <ul><li>Source-based trees, data-driven (broadcast-and-prune), implicit join, dense mode protocol </li></ul><ul><li>RPM algorithm </li></ul><ul><li>Derived from Routing Information Protocol (RIP) </li></ul><ul><ul><li>RIP forwards the unicast packets based on the next-hop towards a destination </li></ul></ul><ul><ul><li>DVMRP constructs delivery trees based on shortest previous-hop back to the source </li></ul></ul><ul><li>DVMRP forwarding table: built from DVMRP’s own routing table, received prune messages </li></ul><ul><li>TTL and admin scoping available; physical or tunnel interfaces possible </li></ul>
    30. 30. 3.4.1 Distance Vector Multicast Routing Protocol (DVMRP) <ul><li>If router C can receive datagrams from both A and B, then it will receive from A if A’s metric to the source is smaller than B’s or if they are equal, A has the smaller IP address on its downstream interface </li></ul>
    31. 31. 3.4.1 Distance Vector Multicast Routing Protocol (DVMRP) <ul><li>Separate processes (and updates) for unicast and multicast routing </li></ul><ul><li>Limitations: </li></ul><ul><ul><li>distance-vector => slow to adapt to topology changes; </li></ul></ul><ul><ul><li>Must store source-specific sate even when not on tree => scaling problems </li></ul></ul>B A Source
    32. 32. 3.4.2 Multicast OSPF (MOSPF) <ul><li>OSPF provides each router with the topology of the Internet or its OSPF area </li></ul><ul><li>MOSPF uses OSPF’s topology database to calculate forwarding tree. </li></ul><ul><li>Broadcasting data for a group is demand-driven, that means it happens only when a host joins or leaves a group. Compared to data-driven protocols, the cost is that routing information should be propagated, because all routers in an area must maintain membership about every group </li></ul>
    33. 33. 3.4.3 Protocol-Independent Multicast (PIM) <ul><li>PIM has two variants: Dense mode (DM) and sparse mode (SM) </li></ul><ul><ul><li>DM builds source-based trees in a data-driven (broadcast-and-prune), implicit join manner </li></ul></ul><ul><ul><li>SM allows shared tree and uses explicit join. </li></ul></ul><ul><li>PIM-DM </li></ul><ul><ul><li>it employs the Reverse Path Multicasting (RPM) algorithm </li></ul></ul><ul><ul><li>PIM-DM relies on the presence of an existing unicast routing protocol to adapt to topology changes, but it is independent of the mechanisms of the specific unicast routing protocol, while DVMRP has its own routing table </li></ul></ul><ul><ul><li>PIM-DM simply forwards multicast traffic on all downstream interfaces until explicit prune messages are received </li></ul></ul>
    34. 34. 3.4.3 Protocol-Independent Multicast (PIM) <ul><li>PIM-SM </li></ul><ul><ul><li>Routers with directly attached or downstream members are required to join a sparse-mode distribution tree by transmitting explicit join messages </li></ul></ul><ul><ul><li>PIM-SM is similar to the Core-Based Tree (CBT) approach in that it employs the concept of a rendezvous point (RP) where receivers &quot;meet&quot; sources </li></ul></ul>Join a PIM-SM distribution tree
    35. 35. 3.4.3 Protocol-Independent Multicast (PIM) <ul><li>PIM-SM (cont.) </li></ul><ul><ul><li>When a host first transmits a multicast packet to a group, its DR encapsulates the multicast packet in a PIM-SM-Register packet and unicasts it to the primary RP. The RP responds PIM-Join message. All routers between source and RP maintain the route so that subsequent unencapsulated multicast packets could be forwarded to the RP </li></ul></ul>
    36. 36. 3.4.3 Protocol-Independent Multicast (PIM) <ul><li>PIM-SM (cont.) </li></ul><ul><ul><li>PIM-SM allows receivers to either continue to receive multicast traffic over the RP-shared tree or over a source-rooted shortest-path tree that a receiver subsequently creates. The shortest-path tree allows a group member to reduce the delay between itself and a particular source </li></ul></ul>
    37. 37. 3.4.4 BGMP and MASC <ul><li>BGMP (Border Gateway Multicast Protocol ) </li></ul><ul><ul><li>BGMP builds shared tree of domains for a group </li></ul></ul><ul><ul><ul><ul><li>So we can use a rendezvous mechanism at the domain level Shared tree is bidirectional Root of shared tree of domains is at root domain </li></ul></ul></ul></ul><ul><ul><li>Runs in routers that border a multicast routing domain </li></ul></ul><ul><ul><li>Runs over TCP </li></ul></ul><ul><ul><li>Joins and prunes travel across domains </li></ul></ul><ul><ul><li>Can build unidirectional source trees </li></ul></ul>
    38. 38. 3.4.4 BGMP and MASC unidirectional source tree
    39. 39. 3.4.4 BGMP and MASC <ul><li>MASC (Multicast Address Set Claim ) </li></ul><ul><ul><li>Group prefixes are temporarily leased to domains </li></ul></ul><ul><ul><li>Allocated by ISP who in turn received them from its upstream provider </li></ul></ul><ul><ul><li>Claims for group allocation resolve collisions </li></ul></ul><ul><ul><li>Group allocations are advertised across domains </li></ul></ul><ul><ul><li>Group prefix allocations are not assigned to domains—they are leased </li></ul></ul><ul><ul><ul><li>Applications must know that group addresses may go away </li></ul></ul></ul><ul><ul><li>RFC 2909 </li></ul></ul>
    40. 40. 3.4.4 BGMP and MASC
    41. 41. 4 Deployment Issues of Multicast <ul><li>Current architecture deters the commercial deployment of multicast. </li></ul><ul><ul><li>Router mitigation: Older hardware doesn’t support multicast. If software upgrade is not applicable, the routers are forced into early retirement </li></ul></ul><ul><ul><li>Domain independent: For sparse mode multicast, it’s better to use CBT or PIM-SM. However, many problems are present when RPs/core and sources are in different domains </li></ul></ul><ul><ul><ul><li>Traffic sources in other domains may require traffic controls, such as rate or congestion control </li></ul></ul></ul><ul><ul><ul><li>ISP has little control over receivers who receive messages from an RP in another domain </li></ul></ul></ul><ul><ul><ul><li>ISP refuses to be a core if it has no receives or sources </li></ul></ul></ul><ul><ul><ul><li>Advertisement of the addresses of the RP/core is not very easy </li></ul></ul></ul>
    42. 42. 4 Deployment Issues of Multicast <ul><li>Current architecture deters the commercial deployment of multicast (cont.) </li></ul><ul><ul><li>Group management: Current service model does not consider group management, including receiver/transmitter authorization, group creation, billing, etc. Dangers: </li></ul></ul><ul><ul><ul><li>Flooding attack </li></ul></ul></ul><ul><ul><ul><li>Collision of sessions </li></ul></ul></ul><ul><ul><ul><li>Unauthorized reception </li></ul></ul></ul><ul><ul><ul><li>Changing the content of a session </li></ul></ul></ul>
    43. 43. 4 Deployment Issues of Multicast <ul><li>Current architecture deters the commercial deployment of multicast (cont.) </li></ul><ul><ul><li>Multicast security: </li></ul></ul><ul><ul><li>Authentication, authorization, encryption and data integrity </li></ul></ul><ul><ul><li>Current IP multicast service and architecture do not mandate any authentication </li></ul></ul><ul><ul><li>Encryption is appropriate mechanism to preserve data privacy at application level </li></ul></ul><ul><ul><li>Secure Multicast services are network level solutions to ensure that multicast tree construction and delivery services are restricted to authenticated and authorized hosts (i.e. KHIP) </li></ul></ul><ul><ul><li>MSEC - Multicast Security ( [email_address] ) </li></ul></ul><ul><ul><ul><li>Drafts: </li></ul></ul></ul><ul><ul><ul><ul><li>The Group Domain of Interpretation ( draft-ietf-msec-gdoi-06.txt ) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Group Key Management Architecture ( draft-ietf-msec-gkmarch-03.txt ) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>GSAKMP Light ( draft-ietf-msec-gsakmp-light-sec-01.txt ) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>MIKEY: Multimedia Internet KEYing ( draft-ietf-msec-mikey-04.txt ) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>HMAC-authenticated Diffie-Hellman for MIKEY ( draft-ietf-msec-mikey-dhhmac-00.txt ) </li></ul></ul></ul></ul><ul><ul><ul><li>RFCs: </li></ul></ul></ul><ul><ul><ul><ul><li><none> </li></ul></ul></ul></ul>
    44. 44. 4 Deployment Issues of Multicast <ul><li>Current architecture deters the commercial deployment of multicast (cont.) </li></ul><ul><ul><li>Address allocation: When multicast service is popular, address allocation will be a big problem. Currently there are four alternatives for address allocation. </li></ul></ul><ul><ul><ul><li>MAAA: It is very complicated, consisting of three protocols which connect hosts, domains, address allocation servers. The allocation of addresses between domains is handled by Multicast Address Set Claim (MASC). Multicast Address Dynamic Client Allocation Protocol (MADCAP) is used by host to request address from server. The servers inform each other of claimed address blocks by Address Allocation Protocol (AAP). However, MAAA never considers whether address resource is enough </li></ul></ul></ul><ul><ul><ul><li>Static allocation and assignment (GLOP): Restrict addresses available to domains by AS numbers </li></ul></ul></ul><ul><ul><ul><li>EXPRESS model: Uses per source and channel (S,E) structure, so each source can have 16 million channels </li></ul></ul></ul><ul><ul><ul><li>IPv6 addressing: IPv6 provides sufficient addresses </li></ul></ul></ul>
    45. 45. 4 Deployment Issues of Multicast <ul><li>Some alternate service models </li></ul><ul><ul><li>EXPRESS </li></ul></ul><ul><ul><li>Application level multicast: Application level multicast has the potential to address most problems associated with IP multicast, since it’s based on unicast. However, Application level multicast can not perform as well as IP multicast. The reason is that some redundant traffic on physical links is unavoidable </li></ul></ul>
    46. 46. 5 EXPRESS (Explicitly Requested Single Source Multicast) <ul><li>5.1 EXPRESS channel model and advantages </li></ul><ul><li>5.2 EXPRESS count management protocol (ECMP) </li></ul><ul><li>5.3 Multi-source applications </li></ul><ul><li>5.4 Cost of EXPRESS and conclusion </li></ul>
    47. 47. 5.1 EXPRESS channel model and advantages <ul><li>1. Channel Model </li></ul><ul><ul><li>The channel model is identified by (S,E), where S is the single source and E is a channel destination address </li></ul></ul><ul><ul><li>Only source S can send datagrams to (S,E) </li></ul></ul><ul><ul><li>If a subscriber host wants to receive data from S, it should explicitly specify both S and E in its request </li></ul></ul><ul><ul><li>Compared to group model, (S,E) and (S’,E) are unrelated. That means a subscriber to (S,E) won’t receive data from (S’,E) </li></ul></ul><ul><ul><li>Class D address (232.*.*.*) are assigned for experimental use by EXPRESS </li></ul></ul>
    48. 48. 5.1 EXPRESS channel model and advantages Channel Model Group Model
    49. 49. 5.1 EXPRESS channel model and advantages <ul><li>2. EXPRESS Service Interface Extensions </li></ul><ul><ul><li>Source Host </li></ul></ul><ul><ul><ul><li>count = CountQuery (channel, countId, timeout) is used to collect count information for the channel </li></ul></ul></ul><ul><ul><ul><li>channelKey (channel, K(S,E)) is used to inform the network that the channel is authenticated </li></ul></ul></ul><ul><ul><li>Subscriber Host </li></ul></ul><ul><ul><ul><li>result = newSubscription (channel, [K(S,E)]) is used to participate in a channel </li></ul></ul></ul><ul><ul><ul><li>result = deleteSubscription (channel) is used to unsubscribe form a channel </li></ul></ul></ul><ul><ul><ul><li>count (channel, countId, count) is used to reply to CountQuery </li></ul></ul></ul>
    50. 50. 5.1 EXPRESS channel model and advantages <ul><li>3 Advantages </li></ul><ul><ul><li>EXPRESS provides 2 channels per source. Channels needn’t be treated as scarce resource </li></ul></ul><ul><ul><li>The source has exclusive access to a channel </li></ul></ul><ul><ul><li>A subscriber can only get data from the designated source </li></ul></ul><ul><ul><li>Single source and knowledge of subscriber numbers enables ISP easy in charging </li></ul></ul>24
    51. 51. 5.2 EXPRESS count management protocol (ECMP) <ul><li>ECMP maintains the distribution tree and supports source-directed counting and voting </li></ul><ul><li>Routing aspect of ECMP is simple because explicit source specification allows reverse path forwarding (RPF) </li></ul><ul><li>ECMP consists of three messages: </li></ul><ul><ul><li>CountQuery(channel, countId, timeout) </li></ul></ul><ul><ul><li>Count(channel, CountId, K(S,E)) </li></ul></ul><ul><ul><li>CountResponse(channel, CountId, status) </li></ul></ul>
    52. 52. 5.2 EXPRESS count management protocol (ECMP) <ul><li>Generic Counting Operation </li></ul><ul><ul><li>CountQuery can start at source or any router on the channel distribution tree. A sub-range of CountIds are defined for local use. </li></ul></ul><ul><ul><li>The query is sent from source to the first hop router, specifying a channel, countId and timeout </li></ul></ul><ul><ul><li>Receiving router minus timeout value by the measured round-trip time to its upstream router, and send the query to each downstream router </li></ul></ul><ul><ul><li>An end-station host responds to CountQuery with Count message </li></ul></ul><ul><ul><li>The value in the Count response is recorded locally. Once Counts are received from all neighbors or timeout, the counts are summed and the total is sent upstream in a Count reply </li></ul></ul>
    53. 53. 5.2 EXPRESS count management protocol (ECMP) <ul><li>Distribution Tree Maintenance </li></ul><ul><ul><li>subscriberId is a reserved countId used to report number of subscribers in a subtree </li></ul></ul><ul><ul><li>A newSubscription causes an unsolicited subscriberId Count message to be propagated to the channel source, just as a host joins to the core in CBT </li></ul></ul><ul><ul><li>A host unsubscribes by sending zero Count message </li></ul></ul><ul><ul><li>For authenticated subscription, the upstream router uses CoutResponse to deny or validate the user. A valid key is cached in the local router </li></ul></ul><ul><ul><li>Core routers are connected by TCP, using Count message to maintain the connection </li></ul></ul><ul><ul><li>Edge routers are connected by UDP. Upstream routers have to send CountQuery periodically to maintain the tree, like IGMP </li></ul></ul>
    54. 54. 5.2 EXPRESS count management protocol (ECMP)
    55. 55. 5.2 EXPRESS count management protocol (ECMP) <ul><li>Neighbor discovery uses ‘neighbors’ countId, and for a local LAN, ‘all channels’ countId is used by CountQuery, as IGMP general query </li></ul><ul><li>Packet forwarding is like conventional multicast. A router looks up (S,E) after receiving an EXPRESS packet </li></ul><ul><li>Authentication is used based on trust of routers. To get more security, end-to-end encryption can be used </li></ul><ul><li>Due to single source, ECMP is easy to manage and implement </li></ul>
    56. 56. 5.3 Multi-source applications <ul><li>Multi-source applications can be built on EXPRESS channels either by using multiple channels, one per source, or by allowing multiple sources to share a channel using higher-level relaying. The later one is specially used for ‘almost single source’ </li></ul><ul><li>Almost single source can have several sources, but one of them is the main source </li></ul><ul><li>Session relay approach uses an SR host to relay packets. The main resource can reside on it. Packets are transferred from source station to SR host by unicast </li></ul>
    57. 57. 5.3 Multi-source applications
    58. 58. 5.3 Multi-source applications <ul><li>Advantages of session relay </li></ul><ul><ul><li>The application can select the SR placement, thus reduce communication </li></ul></ul><ul><ul><li>Backup SRs can be used for fault-tolerance </li></ul></ul><ul><ul><li>The SR can provide extra application-specific functionality beyond simply relaying data, as it can add sequence numbers to relayed packets </li></ul></ul><ul><ul><li>Can be used by ISP to provide session relay service. Standard relaying and accessing protocol is needed </li></ul></ul><ul><li>Session relay is like CBT but the later one has no application level control </li></ul><ul><li>Relaying time is not significant in wide area applications </li></ul>
    59. 59. 5.4 Cost of EXPRESS <ul><li>The key cost of EXPRESS </li></ul><ul><ul><li>Cost of router FIB memory for channels (12 bytes for each entry) </li></ul></ul><ul><ul><li>Cost of management-level router state (16 bytes for each count activity) </li></ul></ul><ul><ul><li>Cost of maintaining this state (the cost growing linearly with the number of channels) </li></ul></ul><ul><li>The incremental costs of EXPRESS can be neglected compared to economic effects </li></ul>
    60. 60. 5.4 Cost of EXPRESS <ul><li>Counting: to get an average number of customers in a long period by polling doesn’t affect system’s performance </li></ul><ul><li>Proactive Counting: Receivers and routers proactively send Count upstream without requiring a CountQuery solicitation. </li></ul><ul><ul><li>Get more accurate estimation of user number, consume more bandwidth </li></ul></ul><ul><ul><li>The convergence time of the algorithm grows approximately linearly with the depth of the tree, while the depth of a tree grows logarithmically with the group size </li></ul></ul>
    61. 61. 6 References <ul><li>Douglas E. Comer, Internetworking with TCP/IP vol1, Principles, Protocols, and Architectures, 4 th edition Pages:319-350 </li></ul><ul><li>Chuck Semeria and Tom Maufer, Introduction to IP Multicast Routing </li></ul><ul><li>L. Sahasrabuddhe and B. Mukherjee, Multicast Routing Algorithms and Protocols: A Tutorial, IEEE Network, Vol. 14, No. 1, January/February 2000 </li></ul><ul><li>H. Holbrook and D. Cheriton, IP Multicast Channels: Express Support for Large-scale Single-source Applications, Proc. of ACM SIGCOMM Conference 1999 </li></ul><ul><li>C. Diot, D. Levine, B. Lyles, H. Kassem, and D. Balensiefen, Deployment Issues for the IP Multicast Service and Architecture, IEEE Network, Vol. 14, No. 1, January/February 2000 </li></ul><ul><li>http://www.nleymann.de/ip-multicast/mcLinksMain.htm </li></ul>

    ×