1. draft-kellil-sam-mtocp-01.txt – CEA, LIST - 78th IETF Meeting, 29July 2010 1 Multiparty Transport Overlay Control Protocol (MTOCP) draft-kellil-sam-mtocp-01.txt Authors: Mounir Kellil, mounir.kellil@cea.fr Christophe Janneteau Pierre Roux CEA, LIST Speaker: Alexandru Petrescu 78th IETF Meeting Maastricht, Netherlands

2. draft-kellil-sam-mtocp-01.txt – CEA, LIST - 78th IETF Meeting, 29 July 2010 2 Objective Efficient support of group communications –Cope with the moderate deployment of IP multicasting in today's Internet. –Hide network heterogeneity to the application layer IPv4 and IPv6. Multicast and non-multicast networks. –Provide an application-agnostic group data delivery service. –Provide a multicast routing-agnostic delivery service. –Maximize the use of IP multicast available in the network. Solution: Multiparty Transport Overlay Control Protocol (MTOCP) –Idea: Place the multiparty overlay paradigm at the transport layer: Multiparty Transport Overlay (MTO). Dynamic addition and removal of MTO’s transport connections.

3. draft-kellil-sam-mtocp-01.txt – CEA, LIST - 78th IETF Meeting, 29 July 2010 3 MTO Architecture Components (1/2) MTO Tree: a set of overlay nodes (ONs) interconnected through unicast or multicast transport connections. –Overlay Node (ON): Forward data based on local forwarding table (packets received on a given ''input'' transport connection will be forwarded to one or more ''output'' transport connections). No IP-in-IP tunneling. 3 types but a common functionality: source overlay node (S-ON), on tree overlay node (O-ON), and leaf overlay node (L-ON). –Transport Connections of MTO tree UDP. Unicast or Multicast destination address IPv4 or IPv6 addresses. Transport Connection ID:. S-ON L-ON2L-ON1L-ON3 R1 R2 R3R4 R5 ucast1 mcast2 mcast1 mcast3mcast4 ucast2 ucast3 R6 Example of an MTO Tree Source MTO = Multiparty Transport Overlay

4. draft-kellil-sam-mtocp-01.txt – CEA, LIST - 78th IETF Meeting, 29 July 2010 4 MTO Architecture Components (2/2) MTO controller (MTO-Ctrl): control the creation, update, and removal of the MTO tree in the network. –Define an MTO tree through: an MTO tree ID, a list of ONs and associated transport connections. –Assign a couple of unique ports (source and destination ports) per MTO tree. Ports SHOULD be used for all transport connections belonging to the same MTO tree. MTO-Ctrl MAY choose to use a different destination port for a given connection of an MTO tree. –e.g., the destination port is the listening port of a unicast terminal (MTO-Ctrl MAY learn the destination port through an out-of-band mechanism). –Push to (and further update for) each ON its MTO Tree-specific forwarding table in the form of a list of input and output transport connections. –Remove/flush transport connections from ONs.

5. draft-kellil-sam-mtocp-01.txt – CEA, LIST - 78th IETF Meeting, 29 July 2010 5 MTOCP Protocol - Operations MTOCP: operates between the MTO-Ctrl and ON to manage the MTO tree. Message exchange is initiated by MTO-Ctrl. Use of TCP for MTOCP message transport. Three types of exchanges –Connection Addition Add one or multiple connections of a given MTO tree –Connection Removal Remove one or multiple connections of a given MTO tree –Connection Flush Remove all the connections of a given MTO tree MTO-Ctrl (1) CONNECTION_START ON (2) ACK_CONNECTION_START MTO-Ctrl (1) CONNECTION_STOP ON (2) ACK_CONNECTION_STOP MTO-Ctrl (1) CONNECTION_FLUSH ON (2) ACK_CONNECTION_FLUSH

6. draft-kellil-sam-mtocp-01.txt – CEA, LIST - 78th IETF Meeting, 29 July 2010 6 MTOCP Protocol – Message Structure Command Message CONNECTION_START, CONNECTION_STOP, or CONNECTION_FLUSH Response Message Command_Number command_typecommand_length MTO_TreeID Connection option #1...... Connection option #n Type src_ipAddrdst_ipAddr src_portdst_port Type src_ipAddrdst_ipAddr src_portdst_port Reponse_Number response_typeresponse_length MTO_TreeIDstatus Connection option #1...... Connection option #m Type src_ipAddrdst_ipAddr src_portdst_port Type src_ipAddrdst_ipAddr src_portdst_port Case of operation failure related to CONNECTION_START or CONNECTION_STOP Case of CONNECTION_START or CONNECTION_STOP ACK_CONNECTION_START, ACK_CONNECTION_STOP, or ACK_CONNECTION_FLUSH

7. draft-kellil-sam-mtocp-01.txt – CEA, LIST - 78th IETF Meeting, 29 July 2010 7 MTOCP Implementation Status IPv4 support: done. IPv6 support: in progress. MTOCP implementation integrated in a full context- aware multiparty transport platform (EU FP7 Project C- CAST): –MTOCP (test and validation done), and –Network context-aware service Network capability detection (multicast, IPv4, IPv6, etc). Dynamic creation and push of ONs and unicast terminal lists to MTO-Ctrl. –Leverage of standard protocols SIP protocol for multiparty session initiation (session invitation to terminals). IGMP/MLD for multicast terminals to subscribe to multicast groups. PIM-SM for multicast routing.

8. draft-kellil-sam-mtocp-01.txt – CEA, LIST - 78th IETF Meeting, 29 July 2010 8 Backup (1/2) Changes since version 00.txt 4. ON Operations 4.2. Data Plane –To receive or send multicast traffic, the ON uses the source address of the multicast input (respectively, output) connection to select the downstream (respectively upstream) interface. Of course, the source address of the multicast input/output connection is mentioned by MTO-Ctrl. ON is also an IGMP/MLD listener. So, as such, it sends an IGMP/MLD report whenever it should receive multicast packets from other ONs or from the source. Perspectives –Full support of IPv6 –Support of a decentralized architecture (multiple MTO-Ctrls)

9. draft-kellil-sam-mtocp-01.txt – CEA, LIST - 78th IETF Meeting, 29 July 2010 9 Backup (2/2) multicast IPv6 (e.g., WiFi) Internet (unicast IPv4) L-ON2 L-ON3 L-ON1 S-ON IPv6 (e.g., IPv6 over WiMAX) multicast IPv4 (e.g., Ethernet wired LAN) unicast IPv4 ( e.g., 3G) source R1 R2 R3 R4 R5 Example of MTO Tree Deployment in Today’s Internet

10. draft-kellil-sam-mtocp-01.txt – CEA, LIST - 78th IETF Meeting, 29July 2010 10 Demo of Audio/Video streaming over the MTO Tree

11. draft-kellil-sam-mtocp-01.txt – CEA, LIST - 78th IETF Meeting, 29July 2010 11 Audio/Video streaming over MTO trees (example) Laptop “S-ON” Multimedia source Group session manager MTO controller Source Overlay Node (S-ON) Android Terminals IP networ k (multi cast) Laptop “L-ON” Leaf Overlay Node (L-ON) WiFi AP 3G (uni cast) WiFi multicast 3G unicast

12. draft-kellil-sam-mtocp-01.txt – CEA, LIST - 78th IETF Meeting, 29 July 2010 12 Tree ID =1 Tree ID =1 Audio source Video source MTO S-ONMTO L-ON 193.48.19.215193.48.19.214 Tree ID =2 Tree ID =2 FEC encode FEC encode FEC decode 6002 6003 6002 6003 90.95.68.99 6006 6007 6006 6007 6006 6002 6003 6006 6007 6003 6002 224.1.2.3 224.1.2.4 224.1.2.5 224.1.2.6 Audio/video streaming over MTO trees (example) multicast stream unicast stream FEC