Contents

• Abstract
• Samenvatting
• Acknowledgements
• 1 Introduction
  • 1.1 Motivation to research IP multicasting over ATM
  • 1.2 Problem statement
    • 1.2.1 Original Problem Statement
    • 1.2.2 Rephrased Problem Statement
  • 1.3 Structure of This Thesis
• 2 The Internet Protocol Suite
  • 2.1 Basic Network Description
    • 2.1.1 Protocol Stack View
    • 2.1.2 Network View
    • 2.1.3 IETF Protocol Stack
    • 2.1.4 IETF Layer Functions
      • Physical Layer
      • Network Interface Layer
      • Internet Layer
      • Transport Layer
      • Application Layer
    • 2.1.5 Network View in the IETF World
  • 2.2 TCP/IP Protocol Suite Implementation Model
    • 2.2.1 Network Interface Layer
    • 2.2.2 Internet Layer
    • 2.2.3 Transport Protocols
    • 2.2.4 Application Protocols
  • 2.3 IP addressing
  • 2.4 ARP
    • 2.4.1 ARP on a LAN
      • ARP on a Broadcast LAN
      • ARP on a non-broadcast LAN
    • 2.4.2 Resolution for non-local IP addresses
  • 2.5 Implementation Architecture of Physical Components
    • 2.5.1 Nodes, Hosts and Routers
    • 2.5.2 Protocol Entities in the Nodes
      • IP host
      • IP router
    • 2.5.3 Interconnection of Nodes in the Internet
  • 2.6 Conclusions
• 3 IP multicasting
  • 3.1 Multicasting
    • 3.1.1 Discussion
  • 3.2 Multicasting in the Internet Protocol
    • Multiple Unicasting
    • Multicasting
  • 3.3 Adding multicast support to the IP Layer
  • 3.4 IP Multicast Addressing
    • 3.4.1 Multicast Address Resolution
  • 3.5 Internet Group Management Protocol (IGMP)
    • 3.5.1 Basic IGMP operations
      • Periodic Host Membership Queries
      • Joining a Host Group
      • Leaving a Host Group
  • 3.6 Data Forwarding between IP Entities
  • 3.7 IP Multicast Usage
    • 3.7.1 The Multicast Backbone (MBone)
  • 3.8 Conclusions
• 4 ATM, LANE and CLIP
  • 4.1 Asynchronous Transfer Mode (ATM)
    • 4.1.1 Basic Concepts
      • Physical Layer
      • ATM Transport Layer
      • ATM Adaptation Layers
      • ATM Signalling Entities
      • ATM Bearer Service
    • 4.1.2 Network Structure
      • Virtual Connections
      • Native ATM addresses
    • 4.1.3 User Network Interface
      • Signalling UNI
  • 4.2 LAN Emulation (LANE)
    • 4.2.1 LANE Architecture
  • 4.3 Classical IP and ARP over ATM (CLIP)
    • ATMARP and InATMARP
    • 4.3.1 Next Hop Resolution Protocol
  • 4.4 Carrying Connectionless Data over ATM
    • 4.4.1 Packet Encapsulation
  • 4.5 Conclusions
• 5 IP Multicasting over ATM
  • 5.1 RFC 2022 Concepts
  • 5.2 Intra-Cluster IP Multicast Transmissions over ATM
    • 5.2.1 VC Mesh
    • 5.2.2 Multicast Server
      • Association with an IP host group
      • Pros and Cons of the MCS
      • Comparison between the VC-mesh and MCS Approach
  • 5.3 Multicast Address Resolution
    • 5.3.1 A Host Group with MCS
  • 5.4 MARS Group Management
    • 5.4.1 IGMP in combination with MARS
  • 5.5 IP Multicast Transmission Example
    • Discussion of the multicast transmission example
  • 5.6 Integration of the MARS with CLIP
  • 5.7 IP Multicast over ATM, Alternatives
    • 5.7.1 EARTH
    • 5.7.2 VENUS
    • 5.7.3 Comments on EARTH and VENUS
  • 5.8 Conclusions
• 6 Linux ATM System
  • 6.1 The Linux Operating System
    • 6.1.1 BSD Socket API
    • 6.1.2 Kernel-space vs. User-space
  • 6.2 The Linux-ATM driver
    • 6.2.1 Currently Supported Features
      • The following Physical Interface Cards (PICs) are supported:
      • The following connection types are supported:
      • Other supported features:
    • 6.2.2 Supposed Point-to-Multipoint SVC Support
    • 6.2.3 ATM Hardware for Linux
    • 6.2.4 Connecting the Hardware
    • 6.2.5 Internal Structure of the Linux-ATM modules
  • 6.3 Getting Linux-ATM Operational
    • 6.3.1 Getting ATM operational
    • 6.3.2 Configuration of Classical IP over ATM
  • 6.4 Conclusions
• 7 IP multicasting on the Linux-ATM system
  • 7.1 Implementation of the RFC 2022 Entities in Linux-ATM
    • 7.1.1 MARS Cluster Member
      • IGMP to MARS interface
    • 7.1.2 MARS Server
    • 7.1.3 Multicast Server
    • 7.1.4 Generic Parts
      • LLC/SNAP encapsulation
      • Copy Service
      • ATM Bearer Services
  • 7.2 Point-to-Multipoint Solutions
    • 7.2.1 Copy Service
      • Copying after LLC/SNAP Encapsulation
      • Copying before LLC/SNAP Encapsulation
      • Copy service inside MARS or MCS Entities
      • Copy Service Implementation Choices
    • UNI 3.1 or 4.0 Multicast Signalling
  • 7.3 Available Source Code
    • 7.3.1 Time scale of an implementation of RFC 2022
  • 7.4 Future Developments of the ATM driver
    • 7.4.1 Integration into the Next Linux Kernel
    • 7.4.2 Extension of Supported Services
  • 7.5 Conclusions
• 8 Conclusions and Recommendations
  • 8.1 Conclusions
  • 8.2 Recommendations
  • 8.3 Conjectures
• References
• List of Figures
• Index
• List of Acronyms
• About this document ...