13.07.2015 Views

Page 2 Lecture Notes in Computer Science 2865 Edited by G. Goos ...

Page 2 Lecture Notes in Computer Science 2865 Edited by G. Goos ...

Page 2 Lecture Notes in Computer Science 2865 Edited by G. Goos ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

86 P.M. Ruiz et al.Section 4 presents some empirical results. F<strong>in</strong>ally, section 5 gives some conclusions.2 Proposed Multicast ArchitectureOne of the most important design issues <strong>in</strong> the multicast architecture for seamlessIP multicast provision <strong>in</strong> ad hoc network extensions is the separation of thefunctions between the different network boundaries. We followed a top-downapproach which allowed us to derive the best design options from the particularrequirements and related issues of a seamless and <strong>in</strong>tegrated multicast solution.2.1 RequirementsThe first step towards an <strong>in</strong>tegrated IP multicast solution is the identificationof the requirements. As an objective for ad hoc network extensions we seek atrade-off <strong>in</strong> which at least the follow<strong>in</strong>g requirements are met:– Interoperability with IP Multicast mechanisms <strong>in</strong> fixed networks– Efficiency, scalability and low signall<strong>in</strong>g overhead– Resilience and robustness (e.g. several po<strong>in</strong>ts of attachment to the fixednetwork)– Compatibility with <strong>in</strong>ter-doma<strong>in</strong> multicast rout<strong>in</strong>g– Support of seamless mov<strong>in</strong>g of term<strong>in</strong>als among network types2.2 Problems to SolveTry<strong>in</strong>g to map the traditional IP multicast model <strong>in</strong>to the concrete scenario of adhoc network extensions, allows us to identify specific problems which need to besolved. Accord<strong>in</strong>g to the IP multicast model for IP multicast hosts, the processof tak<strong>in</strong>g part <strong>in</strong> multicast communications is quite straightforward. When theywish to send multicast traffic they simply use a class-D address as a dest<strong>in</strong>ationand send the datagrams. When they are <strong>in</strong>terested <strong>in</strong> receiv<strong>in</strong>g multicast traffic,they use the Internet Group Management Protocol (IGMP[6]) to <strong>in</strong>form theirFirst Hop Multicast Router (FHMR) about the group they wish to jo<strong>in</strong>. Thissimple operation is not automatically supported <strong>in</strong> ad hoc networks due to someof the problems presented below.TTL Issues. IGMP uses IP datagrams with a time-to-live (TTL) of one hop forthe communication between hosts and routers. Thus, <strong>by</strong> default, only directlyconnected hosts are able to jo<strong>in</strong> multicast groups s<strong>in</strong>ce IGMP messages areunable to transit a multi-hop ad hoc network fr<strong>in</strong>ge.Multihop Nature of MANETs. Packets sent <strong>by</strong> sources which are morethan one hop away will not automatically be received <strong>by</strong> the FHMR. However,<strong>in</strong>termediate ad hoc nodes must ensure that these packets reach the FHMR as it

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!