Understanding Multicast Routing in Networking

Lecture 15 and 16Ch 12: Multicast RoutingSection 12.3 IGMPChapter 9: ICMPv4 Lecture

Lecture 15Ch 12: Multicast Routing Lecture

Put Your Unicast RoutingHAT on Lecture

Recall Unicasting Vs Multicasting Vs Broadcasting Unicasting Case: • In unicast routing, the router forwards the received packet through only one of its interfaces. • Both the source and destination addresses are unicast addresses • One-to-One Relationship Lecture

Multicasting Case Packet starts from source, S1, and goes to all destinations belonging to group, G1 • In multicast routing, the router may forward the received packet through several of its interfaces. • The source address is unicast and the destination address is a group address (Class D) • Group address define a set of Rx’s • One-to-Many Relationship • Actually, the packet is DUPLICATED at each router – only one copy travels in between any two routers Lecture

Broadcasting Case • One-to-all case would cause traffic problems Lecture

Multicasting versus multiple unicasting • Recall Multicasting • One packet start from source and is duplicated at each router • Only one copy of the packet travels in between any two routers • Packet has a single group address • Multiple Unicast Case • More than one copy of the packet starts from the source • Each copy of the packet has a different destination address • In this case, there could be multiple copies traveling between any two routers Multicast is more efficient than multiple unicast because in the unicast cast, some links will use more bandwidth in handling more packet copies. Also for the unicast case, there is more delay at the source due to packet duplication Lecture

MULTICAST ROUTING • Now we understand what multicasting is • Now let’s understand how packets are routed in the multicast case • Some Objectives of multicast routing (very complex) • Each Rx of the group must get only one copy of the packet • Rx’s not belonging to the group DO NOT get a copy of the packet • The packet can not visit the same router more than once (no loops) • The route from Tx to various Rx’s must be optimal (shortest path) Lecture

MULTICAST TREES • Recall in the RIP/OSPF unicast World, we converted networks to graphs in finding the optimal routes • For graphs, nodes can have both successors and predecessors • In the multicast World, networks are converted totrees • Tree has a hierarchical structure • Each node on a tree has (1) a single parent and (2) zero to multiple off-springs (children) • The root (source or Tx) of the tree is the initial node (has no parent) • A leaf (group members) of a tree has no child • Called Spanning Tree provided all nodes are connected • NOTE: show students difference between graph & tree Lecture

Two Types of Trees are used for multicasting by protocols: • Source-Based Trees – a single tree is created for each Source-to-Group combination. For example, given M sources and N groups, there would be a maximum of MxN trees • Group-Shared Trees – each group has it’s own tree. Given N groups, there would be a maximum of N trees. Lecture

Source-Based Tree • Given a source needs to send a packet to group-1, a certain tree is used • Given the same source needs to send a packet to group-5, a different tree is used • Challenge: (1) determining all source-to-group combinations, (2) each tree needs to be optimal • Two approaches used to create optimal source-based trees: • (1st) An extension to the unicast distance vector routing we covered in regards to RIP – used by DVMRP(Distance Vector Multicasting Routing Protocol) • (2nd) An extension to the unicast link state routing we covered in regards to OSPF – used by MOSPF(Multicast Open Shortest Path First) • Another protocol called PIM-DM(Protocol Independent Multicast – Dense Mode) uses either RIP or OSPF depending on need Lecture

Group-Shared Tree • Given a source (source x) needs to send a packet to group-1, a certain tree is used • Given a different source (source y) needs to send a packet to the same group, group-1, the same tree is used • If either source-x or source-y need to send to a different group, the tree would change • Note: the tree changes when the group changes – the tree remains the same for a group regardless if the source changes – the group determines the tree • Two approaches used to create optimal group-shared trees: • (1st) Steiner Tree – the optimal tree has the minimum cost routes like Dijkstra’ algorithm however, instead of it being based around a source node, it is not based around any particular source (very complex and has to re-run every time the topology changes) – not really used by the Internet • (2nd) Rendezvous-Point Tree – a tree is created for each group and a single router is selected as the core or rendezvous point or root of the tree. The CBT (Core-Based Tree Protocol) and PIM-SM (Protocol Independent Multicast – Sparse Mode) use the rendezvous-point tree approach. Lecture

Multicast routing protocols Lecture

DVMRP • Distance Vector Multicast Routing Protocol –similar to the distance vector routing protocol we covered for the unicast case – next hop scenario. • For DVMRP, the optimal tree is not pre-defined – only the next hop • How do we build a tree using the DVMRP approach ? • Use a modified “flooding” approach • Recall what flooding is: a router sends a copy of a packet out of all of it’s interfaces – all interfaces except the interface the packet came in on • Flooding will cause looping problems (ie. the same packet copy that left the router will re-visit the router) • The flooding is modified to stop the looping problem • How is the flooding modified ?????? Lecture

DVMRP - How is the flooding modified ?????? • Instead of forwarding copies of the packet through all interfaces (except the receiving interface), ONLY FORWARD THE PACKET IF IT CAME IN ON THE SHORTEST PATH If it comes in on the non-shortest path – drop it • This approach of only forwarding the packet if it comes in on the shortest path is called Reverse Path Forwarding (RPF) – RPF prevents looping • How does the router determines if the packet came in on the shortest path ??? • Recall that the unicast routing tables contain the next hop based around the shortest path – the table has destinations, interfaces and next hops en route to destinations • If the router used the packet’s source address (instead of destination address), the router could determine the NEXT HOP and desired INTERFACE to exit en route to the packet’s source address • Punch Line: if the INTERFACE the packet arrived at, is the same INTERFACE the packet needs to take in achieving the shortest path en route to the source address – then the PACKET ARRIVED USING THE SHORTEST PATH – make sense ?? Lecture

DVMRP Continuing EXAMPLE A multicast router receives a packet with source address 195.34.23.7 and destination address 227.45.9.5 from interface 2. Should the router discard or forward the packet based on the following unicast table ? SOLUTION: In interpreting the source address of 195.34.23.7 using the default mask, the router would send the packet to network 195.34.0.0 via interface 3 (not interface 2). Recall the packet came in on interface 2 – therefore, the router would DROP the packet (and not forward it) Lecture

DVMRP Continuing • What RPF guarantees is: each network will receive a copy of the multicast packet WITHOUT the loop problem • What RPF doesn’t guarantee is: each network will receive ONLY ONE COPY • With the Reverse Path Forwarding approach, networks could received multiple copies (see example below) • In fixing this problem, a policy called Reverse Path Broadcasting (RPB) can be implemented. Lecture

Reverse Path Broadcasting (RPB) • To eliminate networks (nodes) receiving more than one copy, ONLY THE PARENT HAS THE RIGHT TO FORWARD (this is the RPB policy) • Recall: with a tree, each node has only ONE PARENT • Therefore, if the parent is the only node that can forward, no node should receive duplicates • Policy: the router sends the packet only out of those interfaces for which it is the designated parent. • See the example  • The next question: “How is the parent determined ????” • The router with the shortest path to the source is designated as the PARENT • Recall: because routers share info with their neighbors, they can easily determine which router has the shortest path to the source Lecture

RPB creates a shortest path broadcast tree (not multicast tree) from the source to each destination. It guarantees that each destination receives one and only one copy of the packet. Lecture

Based on pruning Using the IGMP (Internet Group Management Protocol), each PARENT ROUTER holds a membership and knows which groups it is not responsible for. The PARENT ROUTER sends a “prune message” to it’s upstream router letting the upstream router know NOT to send any packets belonging to certain no-interest groups through that corresponding interface. That upstream router will do the same to it’s upstream router This creates a “pruning” effect in that only the packets belonging to a group are forwarded through a particular interface Based on grafting Suppose a “leaf” router (a router with NO children) had previously sent a prune message and suddenly realize it NOW INTERESTED in receiving the multicast packet The leaf router will issue a grafting message upstream and as a result, multicasting will resume Reverse Path Multicasting (RPM) • Recall RPB broadcast a packet versus multicast • How is multicasting achieved ? (1) the first packet is broadcasted no matter what, (2) the remaining packets are multicasted based on pruning and grafting • Another name for pruning and grafting is Reverse Path Multicasting (RPM) Lecture

RPM adds pruning and grafting to RPB to create a multicast shortest path tree that supports dynamic membership changes. Lecture

MOSPF • MOSPF stands for Multicast Open Shortest Path First • Extension of the OSPF protocol • Instead of the tree being generated gradually – it’s generated all at once – by using the link state database (recall) • With the link state database, the router can see the entire topology • Each router could then use Dijikstra’s algorithm and obtain a least cost tree for each router (or node) • For multicasting routing, we need a tree for each source/group pair • For the source/group trees, the only hosts with the particular group address are included • We do the previous by associating the unicast address with the group address – with this approach, we do the calculation the same way using the unicast address however, the associated group address dictates if the host is added to the tree or not • MOSPF is a data-driven protocol – the first time a MOSPF router sees a datagram with a given source and group address, the router calculates Dijkstra Lecture

Core-Based Tree (CBT) Protocol • Is a group-shared protocol • Autonomous systems are divided into regions and a core router or rendezvous point is used for each region • In forming a tree: • 1st: the core router or rendezvous router is selected (very complex - will not cover this process – not covered in your book as well) • 2nd: all other routers are informed of the unicast address of rendezvous router • 3rd: all routers wanting to join group sends a “join message” to the rendezvous router • 4th: the intermediate routers between the rendezvous router and Tx router record the address of the source and the interface in which the packet came into the router on • 5th: after the rendezvous has received all joined messages – the tree is formed Lecture

CBT - Sending a multicast packet • Now that the tree is formed, how are multicast packets sent ? • Any particular source can send a multicast packet to the group by: • 1st: source (inside or outside of the shared tree) sends packet to rendezvous router (via the rendezvous router’s unicast address) • 2nd: rendezvous router then sends the packet to the group members Lecture

DVMRP & MOSPF Versus CBT • For DVMRP and MOSPF, the tree is created from the root • For CBT, the tree is created starting from the leaves • For DVMRP, the tree is first made via broadcast and then pruned into a multicast tree • For CBT, initially there is no tree and then a tree is created gradually via grafting (ie. announcing to the core you want to be apart of the group) Lecture

Protocol Independent Multicast – Dense Mode (PIM-DM) • PIM-DM is used in a dense multicast environment, such as a LAN environment. • PIM-DM is justifiably used when each router is involved in multicasting – therefore broadcasting is justified • PIM-DM uses reverse path forwarding, pruning and grafting techniques for multicasting Lecture

Protocol Independent Multicast – Sparse Mode (PIM-SM) • PIM-SM is used in a sparse multicast environment, such as a WAN environment. • PIM-SM is used when there is a slight possibility each router is involved in multicasting – therefore NOT justifying broadcasting • PIM-SM operates more like CBT • PIM-SM allows the ability to switch between source-based tree and group-shared tree strategies Lecture

Multicast Backbone (MBONE) • There are many more unicast oriented routers in the Internet than multicast routers (ie. routers able to multicast) • In creating more links between multicast routers, the concept of “tunneling” is used • Tunneling - via unicast routers, multicast routers are logically connected – in essence we create a multicast backbone in logically linking the multicast routers Lecture

MBONE – How are tunnels created ? • How to create a tunnel • 1st: encapsulate multicast packet inside a unicast packet (in the data field) • 2nd: the unicast intermediate routers route the packet to the next multicast router Lecture

Chapter 9 Internet Control Message Protocol Lecture

Recall - (1) Explain Creating a Table Recall – (2) Explain How the Router Uses the Table MaskDestinationNext HopI. 255.255.0.0 134.18.0.0 -- m0 255.255.0.0 129.8.0.0 222.13.16.40 m1 255.255.255.0 220.3.6.0 222.13.16.40 m1 0.0.0.0 0.0.0.0 134.18.5.2 m0 U UG Lecture

ICMP IP, as an unreliable protocol, is not concerned with error checking and error control. ICMP was designed, in part, to compensate for this shortcoming. ICMP does not correct errors, it simply reports them. ICMP messages are divided into error-reporting messages and query messages. The error-reporting messages report problems that a router or a host (destination) may encounter. The query messages get specific information from a router or another host. Lecture

ICMP encapsulation Lecture

ICMP messages Lecture

9.2 MESSAGE FORMAT An ICMP message has an 8-byte header and a variable-size data section. Although the general format of the header is different for each message type, the first 4 bytes are common to all. Lecture

Error-reporting messages ICMP always reports error messages to the original source. Lecture

Note: • The following are important points about ICMP error messages: • No ICMP error message will be generated in response to a datagram carrying an ICMP error message. • No ICMP error message will be generated for a fragmented datagram that is not the first fragment. • No ICMP error message will be generated for a datagram having a multicast address. • No ICMP error message will be generated for a datagram having a special address such as 127.0.0.0 or 0.0.0.0. Lecture

Destination-unreachable format Destination-unreachable messages with codes 2 or 3 can be created only by the destination host. Other destination-unreachable messages can be created only by routers. Lecture

Source-quench format NOTE: IP doesn’t have Flow Control. A source-quench message informs the source that a datagram has been discarded due to congestion in a router or the destination host. The source must slow down the sending of datagrams until the congestion is relieved. Lecture

Time-exceeded message format Whenever a router decrements a datagram with a time-to-live value to zero, it discards the datagram and sends a time-exceeded message to the original source. When the final destination does not receive all of the fragments in a set time, it discards the received fragments and sends a time-exceeded message to the original source. In a time-exceeded message, code 0 is used only by routers to show that the value of the time-to-live field is zero. Code 1 is used only by the destination host to show that not all of the fragments have arrived within a set time. Lecture

Parameter-problem message format A parameter-problem message can be created by a router or the destination host. Lecture

Redirection concept A host usually starts with a small routing table that is gradually augmented and updated. One of the tools to accomplish this is the redirection message. A redirection message is sent from a router to a host on the same local network. Router forwards packet to correct router and sends “redirection” message to host so host can correct table Lecture

9.4 QUERY ICMP can also diagnose some network problems through the query messages, a group of four different pairs of messages. In this type of ICMP message, a node sends a message that is answered in a specific format by the destination node. The topics discussed in this section include: Echo Request and Reply Timestamp Request and Reply Address-Mask Request and Reply Router Solicitation and Advertisement Lecture

Echo-request and echo-reply messages An echo-request message can be sent by a host or router. An echo-reply message is sent by the host or router which receives an echo-request message. Echo-request and echo-reply messages can be used by network managers to check the operation of the IP protocol. Echo-request and echo-reply messages can test the reachability of a host. This is usually done by invoking the ping command. Lecture

Timestamp-request and Timestamp-reply message format Timestamp-request and timestamp-reply messages can be used to calculate the round-trip time between a source and a destination machine even if their clocks are not synchronized. The timestamp-request and timestamp-reply messages can be used to synchronize two clocks in two machines if the exact one-way time duration is known. Lecture

Mask-request and mask-reply message format Mask-request and Mask-reply messages can be used to get a mask for a particular IP address Lecture

Router-solicitation/advertisement message format Router-Solicitation Message – router uses this message in determining if adjacent routers are alive or not Router-Advertisement Message – router uses this message in gathering info on the other routers connected to the same network Lecture

ICMP CHECKSUM In ICMP the checksum is calculated over the entire message (header and data). Lecture

9.6 DEBUGGING TOOLS We introduce two tools that use ICMP for debugging: ping and traceroute. The topics discussed in this section include: Ping Traceroute Lecture

The ping program operation We use the ping program to test the server fhda.edu. The result is shown below: $ ping fhda.eduPING fhda.edu (153.18.8.1) 56 (84) bytes of data.64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=0 ttl=62 time=1.91 ms64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=1 ttl=62 time=2.04 ms64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=2 ttl=62 time=1.90 ms64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=3 ttl=62 time=1.97 ms64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=4 ttl=62 time=1.93 ms 64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=5 ttl=62 time=2.00 ms64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=6 ttl=62 time=1.94 ms64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=7 ttl=62 time=1.94 ms64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=8 ttl=62 time=1.97 ms64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=9 ttl=62 time=1.89 ms64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=10 ttl=62 time=1.98 ms--- fhda.edu ping statistics ---11 packets transmitted, 11 received, 0% packet loss, time 10103ms rtt min/avg/max = 1.899/1.955/2.041 ms Lecture

Understanding Multicast Routing in Networking