CNES-CNIT Interoperability Experiment: Italian Side of the IP Tunnel Point of View

Transcription

1 consorzio nazionale interuniversitario per le telecomunicazioni COST Action 272 Packet-Oriented Service Delivery via Satellite CNES-CNIT Interoperability Experiment: Italian Side of the IP Tunnel Point of View Franco Davoli, Erina Ferro, Luca Simone Ronga, Stefano Vignola, Sandro Zappatore

2 Introduction Goal: to perform tests in Ka-Ku band interoperability, IP packet transmission, performance evaluation of multimedia applications, etc., by using a minimum amount of resources, by exploiting existing test-beds and equipment. We verified the possibility to start by interconnecting the CNIT networking infrastructure with the Toulouse site of CNES, which has an earth station transmitting over the Ku band with DVB-S.

3 Introduction (cont d) The CNIT network is a mixed cabled and satellite IP network, with the satellite portion operating in Ka band over 2 Mbps channels, with an operating center located at the CNIT National Multimedia Communications Laboratory in Naples.

4 CNIT Networking Infrastructure CNIT Satellite Network Ka/Ku Band CNIT Terrestrial Network N.O.C. National Multimedia Communications Laboratory

5 Networking Infrastructure (Terrestrial Wide Area Network) Bologna Educational Institutions SMEs High Schools Perugia Engineering Faculty (P.le Tecchio) Access Network Naples Sinform CNIT NETWORK (Albacom) Busseto Parma Genova Milano Torino Savona Departments (Via Claudio) N.O.C. National Multimedia Communications Laboratory CNIT NETWORK (interbusiness) Pisa Ferrara Catania CNR Engines Institute Rende Wind Tunnel Labs. Federico II Univ., Naples Roma

6 Networking Infrastructure (Satellite Wide Area Network) Ku Band Satellite CNES NETWORK Catania Internet IPIP Tunnel Ka Band Satellite Padova Ku band Receivers N.O.C. National Multimedia Communications Laboratory Bologna Genova Prato

7 Networking Infrastructure (Terrestrial/Satellite Wide Area Network) Catania Bologna Padova Genova Sinform Busseto Bologna Perugia Milano Parma Torino Prato Ku Band Satellite Ku band Rx CNES NETWORK Ku band Rx Internet IPIP Tunnel Ku band Rx N.O.C. National Multimedia Communications Laboratory Ka Band Satellite CNIT NETWORK (Albacom) Departments (Via Claudio) CNIT NETWORK (interbusiness) Engineering Fac. (P.le Tecchio) Genova Roma Pisa Ferrara Catania Rende Savona

8 The CNIT Teledottorato Project We decided to take advantage of the existing infrastructure and of the ongoing Teledottorato lectures. The latter are currently regularly broadcast (multicast) over the CNIT network. They consist of specialized teaching modules (10 hours each), with real-time audio, video and slides, with the possibility of two-way interaction.

9 Teledottorato Audio-Visual Tools The Teledottorato project adopts a subset of MBONE Tools, namely: VIC v2.8 (Video, H.261, Hardware Encoded via BT848-based acquisition board) RAT v4.2.4 (Audio) SDR v3.0 (Session Announcement) MPPT v1.3 (Microsoft PowerPoint Multicast Transmission Plug.In) The first 3 applications are available for the major platforms; MPPT is only available for the Microsoft Windows one.

10 Teledottorato Traffic Rates The Lecturer-Originated flows are dimensioned as follows: Audio RTP Flow on IP Multicast: 64 kbps Video RTP Flow on IP Multicast: 256 kbps fps) MPPT ECSRM/FCAST Reliable Multicast with bursts <= 128 kbps The overall lecturer flow requires a sustained rate of 384 kbps with bursts of 512 kbps (more or less) The Students-Originated flows are: For Iron sites: Audio RTP Flow on IP Multicast : 64 kbps (muted during the lecture) For Gold Sites Audio RTP Flow on IP Multicast : 64 kbps Video RTP Flow on IP Multicast : 128 kbps (@15 fps) Only a limited number of Gold sites are allowed for each session, depending on the size of the minimum link of the heterogeneous network.

11 Ping/mtr measurements After a number of trials, by pinging two routers and tracing the route between Naples and Toulouse, it was decided to set up an IP tunnel. It is perhaps worth noting that ping may be not always reliable in such measurements, as the routers of some providers treat ICMP packets used by ping at lower priority, and may discard them in heavy traffic conditions. This is probably the reason of some deep fluctuations that were observed, which, given the subsequent satisfactory behaviour of the tunnel, would have been misleading.

12 Ping/mtr measurements Set of measurements from Naples Report produced by "mtr 0.41" -Source IP: (CNIT - NOC in Naples) - Destination IP: HOST LOSS RCVD SENT BEST AVG WORST gw-cnit-na.cnit.it 0% % r-na71-fa11.interbusiness.it 0% r-rm99-na71.interbusiness.it 0% r-rm83-fa3.interbusiness.it 0% pa5-ibs-12-it.seabone.net 0% ge3-0-0-mil1-milb.mil.seabone.net 0% geneva5.ch.eqip.net 0% frankfurt50.de.eqip.net 0% infonet.de1.de.geant.net 0% de.fr1.fr.geant.net 0% renater-gw.fr1.fr.geant.net 0% nio-n1.cssi.renater.fr 0% toulouse.cssi.renater.fr 0% % ??? 100% % % % % %

13 Ping/mtr measurements Report produced by "ping" - Source IP: (CNIT - NOC in Naples) Destination IP: Packet size: 72 bytes - Count: bytes from : icmp_seq=0 ttl=229 time=87.6 ms 72 bytes from : icmp_seq=1 ttl=229 time=89.6 ms 72 bytes from : icmp_seq=2 ttl=229 time=87.6 ms 72 bytes from : icmp_seq=3 ttl=229 time=86.9 ms 72 bytes from : icmp_seq=4 ttl=229 time=96.6 ms 72 bytes from : icmp_seq=5 ttl=229 time=85.7 ms 72 bytes from : icmp_seq=6 ttl=229 time=90.5 ms 72 bytes from : icmp_seq=7 ttl=229 time=84.0 ms 72 bytes from : icmp_seq=8 ttl=229 time=86.4 ms 72 bytes from : icmp_seq=9 ttl=229 time=84.6 ms 72 bytes from : icmp_seq=10 ttl=229 time=94.5 ms 72 bytes from : icmp_seq=11 ttl=229 time=87.1 ms 72 bytes from : icmp_seq=12 ttl=229 time=95.2 ms 72 bytes from : icmp_seq=13 ttl=229 time=87.8 ms 72 bytes from : icmp_seq=14 ttl=229 time=89.3 ms 72 bytes from : icmp_seq=15 ttl=229 time=88.2 ms 72 bytes from : icmp_seq=16 ttl=229 time=92.3 ms 72 bytes from : icmp_seq=17 ttl=229 time=93.6 ms 72 bytes from : icmp_seq=18 ttl=229 time=90.8 ms 72 bytes from : icmp_seq=19 ttl=229 time=88.3 ms (cont d) ping statistics packets transmitted, 20 packets received, 0% packet loss round-trip min/avg/max = 84.0/89.3/96.6 ms

14 Ping/mtr measurements Report produced by "ping" - Source IP: (CNIT - NOC in Naples) Destination IP: Packet size: 1008 bytes - Count: bytes from : icmp_seq=0 ttl=229 time=110.5 ms 1008 bytes from : icmp_seq=1 ttl=229 time=117.6 ms 1008 bytes from : icmp_seq=2 ttl=229 time=103.7 ms 1008 bytes from : icmp_seq=3 ttl=229 time=109.8 ms 1008 bytes from : icmp_seq=4 ttl=229 time=118.6 ms 1008 bytes from : icmp_seq=5 ttl=229 time=108.9 ms 1008 bytes from : icmp_seq=6 ttl=229 time=118.7 ms 1008 bytes from : icmp_seq=7 ttl=229 time=109.0 ms 1008 bytes from : icmp_seq=8 ttl=229 time=110.8 ms 1008 bytes from : icmp_seq=9 ttl=229 time=109.3 ms 1008 bytes from : icmp_seq=10 ttl=229 time=109.6 ms 1008 bytes from : icmp_seq=11 ttl=229 time=110.3 ms 1008 bytes from : icmp_seq=12 ttl=229 time=115.5 ms 1008 bytes from : icmp_seq=13 ttl=229 time=110.7 ms 1008 bytes from : icmp_seq=14 ttl=229 time=110.4 ms 1008 bytes from : icmp_seq=15 ttl=229 time=112.5 ms 1008 bytes from : icmp_seq=16 ttl=229 time=105.5 ms 1008 bytes from : icmp_seq=17 ttl=229 time=111.3 ms 1008 bytes from : icmp_seq=18 ttl=229 time=103.8 ms 1008 bytes from : icmp_seq=19 ttl=229 time=112.1 ms (cont d) ping statistics packets transmitted, 20 packets received, 0% packet loss round-trip min/avg/max = 103.7/110.9/118.7 ms

15 The IP Tunnel The technical characteristics of the Naples-Toulouse tunnel are described in the following. Tunnel connection with IP-IP data encapsulation mode on a HDSL physical link, operating at 2 Mbps (1 Mbps CIR) on the Naples side. CISCO routers connected Napoli: CISCO 7513 Toulouse: CISCO 7200 Autonomous Systems traversed AS20745 (CNIT) AS3269 (Interbusiness) AS6762 (Interbusiness) AS3300 (AUCS Communications Services) AS20965 (GEANT) AS2200 (INRIA- Rocquencourt) AS3215 (France Telecom) Measured average flight times 90/100ms Multicast traffic propagation mode PIMv.2 (Protocol Independent Multicast) sparse mode Rendezvous Point: Naples router

16 The IP Tunnel (cont d) The generic configuration commands to set up the tunnel are as follows:! ip multicast-routing ip sap cache-timeout 30! interface Tunnel "n" description Tunnel Connection NA<->"" ip address "ip address" "netmask" ip pim sparse-mode ip sap listen load-interval 30 tunnel source tunnel destination "ip address of remote router" tunnel mode ipip! ip pim rp-address "ip address CNIT Naples router"

17 Some Qualitative Evaluations The Teledottorato lectures are currently being multicast over the CNIT network with a certain regularity, according to the calendar and the table of contents that can be found at the URL After Toulouse has become a member of the multicast group, it has operated in real time on the flows received (audio, video and MPPT (Multicast PowerPoint) slides), in two ways: a) By decoding the flows up to the application level, re-encoding in MPEG and sending over DVB in Ku band; b) By directly encapsulating the IP packets (after extraction from the tunnel) in the DVB frame and sending them over the Ku band. This allowed us in Naples to receive back the flows also in two ways: a) In TV mode, either through a normal decoder or the DVB-IP board operating in TV mode; b) In IP mode, by joining in the multicast group with the machine hosting the DVB-IP board, operating in IP mode..

18 Some Qualitative Evaluations (cont d) Frame captured from a lecture (DVB-IP board, TV mode)

19 Some Qualitative Evaluations (cont d) Frame captured from a lecture (DVB-IP board, TV mode)

20 Some Qualitative Evaluations (cont d) Frame captured from a lecture (DVB-IP board, IP mode)

21 Some Qualitative Evaluations (cont d) Frame captured from a lecture (as seen on the LAN of origin)