doc.: IEEE /xxxx-r0 Submission July 2005 Jan Kruys, Shah Rahman.e.a, CiscoSlide 1 Tree Based Routing Protocol (I20) Five Minute Summary Notice: This document has been prepared to assist IEEE It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE Working Group. If you have questions, contact the IEEE Patent Committee Administrator at.

doc.: IEEE /xxxx-r0 Submission July 2005 Jan Kruys, Shah Rahman.e.a, CiscoSlide 2 The focus of our proposal Routing/forwarding is a key part any mesh solution The ability to handle any scale of network is a key to major market segments like home, municipal and enterprise networks Simplicity of design and operation is critical for success and for rapid progress with this standard mobility simplicity functionality network size

doc.: IEEE /xxxx-r0 Submission July 2005 Jan Kruys, Shah Rahman.e.a, CiscoSlide 3 Tree Based Routing Aimed at the typical access network: “fixed” installations but that also works well for small, flat meshes Organises mesh points into tree structures rooted in major information sources/sinks: –Portals to other (sub)networks - in any scenario –Local Servers - in the office –Screens, DVDs, PCs at home Applications with more demanding requirements are better served by routing schemes that focus on mobility and frequent configuration change

doc.: IEEE /xxxx-r0 Submission July 2005 Jan Kruys, Shah Rahman.e.a, CiscoSlide 4 Tree Construction Trees are easy to construct and maintain: - N sends out a request and gets responses - N learns the path to the root (distance vector, link metrics) - N picks the best and links up Pre-conditions: - Roots announce themselves - Mesh points recognize roots (like STA’s recognize IBSS’ses Root N 4 7 5

doc.: IEEE /xxxx-r0 Submission July 2005 Jan Kruys, Shah Rahman.e.a, CiscoSlide 5 Link Metrics The question is: “will my packet make it quickly to the root” Factors that play a role: net link rate, current load uplink and hop count to root Further (radio metric) detail data is overkill SNR is a good predictor of net link rate Going down link is easier: traffic fans out Routing metric data reported by neighbours: upstream SNR and load, hops Supports simple distributed congestion control Processing and decision making is a local matter and outside scope

doc.: IEEE /xxxx-r0 Submission July 2005 Jan Kruys, Shah Rahman.e.a, CiscoSlide 6 MP and STA Mobility Mesh points: Mesh point mobility is handled by hooking up to another node STAs: Mesh (access) points, and portals learn addresses and keep routing tables Root A A7 A5 STA A2

doc.: IEEE /xxxx-r0 Submission July 2005 Jan Kruys, Shah Rahman.e.a, CiscoSlide 7 Scalability Replication allows scaling to almost any size network Root/Bridge Mesh 1 Root/Bridge Mesh 2 Root/Bridge Mesh 4 Root/Bridge Mesh 3 RSTP /MST

doc.: IEEE /xxxx-r0 Submission July 2005 Jan Kruys, Shah Rahman.e.a, CiscoSlide 8 Summary A simple discovery and binding scheme is all we need to build “mesh connectivity” A tree-based routing scheme should be the baseline of the TGs standard Meets the requirements of many, major applications Complementary schemes that meet specific needs have been identified in other proposals Re-using features and (encapsulated) frame formats facilitates specification as well as implementation

doc.: IEEE /xxxx-r0 Submission July 2005 Jan Kruys, Shah Rahman.e.a, CiscoSlide 9 Thank you for your attention