1 / 10

Interconnectivity Considerations for ESS Mesh Networking

This article discusses the need for standardized interconnectivity in ESS mesh networking and the feasibility of standardizing a routing protocol. It also explores different interconnectivity scenarios and suggests changes to the scope of the project. The article concludes with suggestions for the implementation and development of ESS mesh networks.

ssander
Download Presentation

Interconnectivity Considerations for ESS Mesh Networking

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Scope and Interconnectivity Considerations for ESS Mesh Narasimha Chari (chari@tropos.com) Malik Audeh (malik.audeh@tropos.com) Tropos Networks San Mateo, CA Narasimha Chari, Malik Audeh - Tropos Networks

  2. Overview • Tropos Networks is supportive of the ESS Mesh Standards effort • We highlight the need for standardized interconnectivity • We present some observations about the state of mesh networking and on the feasibility of standardizing a routing protocol • Lastly, we present comments on the draft PAR/5C and our suggestions for changes to the scope Narasimha Chari, Malik Audeh - Tropos Networks

  3. Interconnectivity • Multiple vendors of mesh networking products already exist in the marketplace, serving different customer needs and providing solutions for different deployment environments • Specification of a standard way for mesh products from different vendors to interconnect is likely to fuel large-scale adoption of such systems • Interconnectivity across domain boundaries is likely to emerge as an important market requirement Narasimha Chari, Malik Audeh - Tropos Networks

  4. Interconnectivity Scenarios - I Node-level interconnectivity Narasimha Chari, Malik Audeh - Tropos Networks

  5. Interconnectivity Scenarios - II Over-the-wire interconnectivity Narasimha Chari, Malik Audeh - Tropos Networks

  6. Interconnectivity Scenarios - III Interconnectivity across domain boundaries Narasimha Chari, Malik Audeh - Tropos Networks

  7. Mesh Networking- A rapidly evolving area • Active area of research and development • Academic research – MIT RoofNet, CMU Monarch • Commercial innovation • Startups – Tropos, Mesh Networks, BelAir, Strix, Firetide, PacketHop, others • Established companies – Nortel, Intel, Motorola, others • Standards bodies (IETF MANET: AODV, DSR, DSDV, etc.) • Multiple approaches exist and more are being actively developed • Standardization of a protocol may be premature and may stifle innovation in a rapidly evolving space Narasimha Chari, Malik Audeh - Tropos Networks

  8. Multiple Deployment Scenarios • Multiple deployment scenarios with differing functional requirements • Directional vs omni-directional meshes • Indoor vs outdoor • Fixed vs mobile • Public safety vs ISP vs wireless carriers • Domestic vs international markets • No one-size-fits-all approach is likely to work Narasimha Chari, Malik Audeh - Tropos Networks

  9. Routing • Routing is traditionally a Layer 3 function • There are good arguments for wireless routing protocols to be radio-aware • However, this does not necessarily imply that the protocol needs to be implemented at Layer 2, merely that radio-level information needs to be gathered and leveraged in making the routing decisions • 802.11k Task Group activities (Radio Resource Measurement) are a step in the right direction Narasimha Chari, Malik Audeh - Tropos Networks

  10. Our Suggestions • Scope should include definitions and mechanisms to allow internetworking of mesh domains • Clarification of the 4-address format within 802.11 • Mechanism to identify neighbor nodes in a mesh • Mechanism to identify wired gateway nodes • Mechanism to share routing information across domain boundaries • Scope should explicitly exclude specification of the routing protocol between individual APs in a domain to be used for the reasons cited earlier • This will enable faster completion of TG activities Narasimha Chari, Malik Audeh - Tropos Networks

More Related