On Implementing IPTV Platform with IPv4 and IPv6 Devices

• Autorzy: Batalla J. M. , Krawiec P.
• Języki publikacji: EN

Abstrakty

EN

The end of IPv4 addresses is now a reality. Providers not updated to IPv6 will have to hurry up the IPv6 start in its own network. Introduction of IPv6 means not only change of main routers but also change of mentality in operators, applications' programmers besides end users. Even when for the last years the core network is prepared for transferring IPv6 traffic, other built-in parts of the Internet limit the IPv6 start. Examples of these limitations we find in not IPv6-awareness of many applications and services. For instance, voice over IP service, which uses session initiation protocol (SIP) needs to implement IPv6 aware SIP proxies and IPv6 aware AAA (authentication, authorization and accounting) servers as well as adapting application programming interfaces to IPv6. Internet protocol television (IPTV) system includes many different hardware devices, which not always are IPv6 compatible. In this paper, we propose a global solution for integrating all the devices, these one working on IPv4 and these one working on IPv6, under the same IPTV platform. This solution allows end users to receive IPTV stream irrespective of IP protocol used. The proposed solution is particularly relevant for small IPTV systems, which, step by step, are adapting into IPv6.

Słowa kluczowe

EN

good practices; IPTV; IPv4/IPv6 interoperability; IPv6; set top box

• Wydawca: Instytut Łączności - Państwowy Instytut Badawczy
• Czasopismo: Journal of Telecommunications and Information Technology
• Rocznik: 2011
• Tom: nr 2
• Strony: 31--36
• Opis fizyczny: Bibliogr. 13 poz., rys.

Twórcy

autor

Batalla J. M.

autor

Krawiec P.

• National Institute of Telecommunications, Szachowa st 1, 04-894 Warsaw, Poland,

Bibliografia

• [1] “Mu Dynamics introduces Mu Test Suite for IPv6 to significantly accelerate and ensure successful IPv6 migration”, Mu Dynamics Inc. 2010 [Online]. Available: http://www.tmcnet.com/usubmit/2010/04/26/4749761.htm
• [2] C. D. Marsan, “YouTube turns on IPv6 Support, net traffic spikes”, PCWorld Mag., Feb. 2010.
• [3] D. H. Ramirez, IPTV Security: Protecting High-Value Digital Contents. Wiley, 2008.
• [4] “Information Technology – Generic Coding of Moving Pictures and Associated Audio Information: Systems”, ITU-T Recommendation H.222.0, Inst. Telecommun. Union, Geneva, Switzerland, 2000.
• [5] MySQL 5.1 Reference Manual, paragraph 17.7.2.22. Oracle USA, January 2009.
• [6] “VLC media player: The cross-platform open-source multimedia framework, player and server“ [Online]. Available: http://www.videolan.org/vlc/
• [7] B. Cain, S. Deering, I. Kouvelas, B. Fenner and A. Thyagarajan, “Internet Group Management Protocol, Version 3”, RFC 3376, IETF, October 2002.
• [8] B. Fenner , M. Handley, H. Holbrook, I. Kouvelas, “Protocol Independent Multicast – Sparse Mode (PIM-SM): Protocol Specification (Revised)”, RFC 4601, IETF, August 2006.
• [9] E.-M. Lee, Y.-T. Han, H.-S. Park, “Rendezvous point relocation for IPTV services with PIM-SM”, in Proc. 14th Asia-Pacific Conf. Commun. APCC 2008, Tokyo, Japan, 2008.
• [10] P. Savola and B. Haberman, “Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address”, RFC 3956, IETF, November 2004.
• [11] B. Haberman and D. Thaler, “Unicast-Prefix-based IPv6 Multicast Addresses”, RFC 4601, IETF, August 2002.
• [12] M. Crawford, “Transmission of IPv6 Packets over Ethernet Networks”, RFC 2464, IETF, December 1998.
• [13] R. Vida and L. Costa, “Multicast Listener Discovery Version 2 (MLDv2) for IPv6”, RFC 3810, IETF, June 2004.