Doc.: IEEE 11-04/0319r0 Submission March 2004 W. Steven Conner, Intel Corporation Slide 1 Architectural Considerations and Requirements for ESS Mesh March 16, 2004 Steven Conner Intel Corporation

Doc.: IEEE 11-04/0319r0 Submission March 2004 W. Steven Conner, Intel Corporation Slide 2 Outline   Review of ESS Mesh Scope   Architectural Considerations and Requirements   Proposed Next Steps

Doc.: IEEE 11-04/0319r0 Submission March 2004 W. Steven Conner, Intel Corporation Slide 3 Overview: Mesh  Mesh is not limited to highly mobile networks with no infrastructure  Also has application in many fixed-infrastructure environments  Extended range and coverage, without requiring additional wires (convenient deployment, cost)  Enhanced redundancy, reliability  Potential throughput improvement  Example networks where Mesh is useful:  Home networks, hotspot networks, etc.

Doc.: IEEE 11-04/0319r0 Submission March 2004 W. Steven Conner, Intel Corporation Slide 4 Summary of s PAR Scope Approved by WG in January  Scope: Develop an Infrastructure-Mode ESS Mesh with MAC/PHY (WDS links)  Scale: Target ~32 active mesh APs  Security: Include support for trusted set of mesh APs controlled by single logical administrative domain  Mesh Topology/Paths: Include support for both broadcast/multicast and radio-channel-aware unicast path selection/data delivery  Multiple-radios: Include support for optional multiple- radios per router  Ensure support for interfacing with higher layers  Enable interoperability, extensibility

Doc.: IEEE 11-04/0319r0 Submission March 2004 W. Steven Conner, Intel Corporation Slide 5 Distribution System (DS) ESS Mesh Mesh AP Links MAC/PHY (4-addr data frames) Client-to-AP Links MAC/PHY (3-addr data frames) BSS How does IEEE ESS Mesh fit in to the big picture? ESS

Doc.: IEEE 11-04/0319r0 Submission March 2004 W. Steven Conner, Intel Corporation Slide 6 High-Level Requirements for s ESS Mesh  Interoperability: is required to appear to higher layers as a current style 802 LAN ( )  LAN broadcast and unicast delivery  Interfacing to other networks, e.g. bridging and gatewaying  Self-configuring multi-hop topologies and paths  MAC/PHY radio-awareness for efficient path selection and data delivery  Maintain WLAN security  New security requirements:  AP-to-AP authentication, key distribution, topology/statistics exchange, data forwarding  Don’t break i for legacy client STA security

Doc.: IEEE 11-04/0319r0 Submission March 2004 W. Steven Conner, Intel Corporation Slide 7 ESS Mesh Functional Components  ESS Mesh Topology Formation – Mesh APs establish peer-to-peer links between neighbors, resulting in a secure “mesh of connectivity”  Key Components:  AP neighbor discovery  AP-to-AP security (authentication, key distribution, etc.)  ESS Mesh Path Formation/Forwarding – Establishment of end-to-end data comm. paths in a mesh network, potentially across multiple radio hops  Key Components:  Multi-hop topology discovery  Radio-aware path selection/data delivery  LAN broadcast  Goals:  Interoperability through standard protocol tuned for core usage model requirements  Extensibility for future applications and technology enhancements

Doc.: IEEE 11-04/0319r0 Submission March 2004 W. Steven Conner, Intel Corporation Slide s Strawman Architecture Unicast Path Selection LAN Bcast Protocol Radio- Aware Mesh Metrics MAC Enhancements for Mesh Unicast Fwding Bcast Fwding ESS Mesh Security PHY MAC k i e/n Interfacing to Services a/b/g/n/… Interfacing to Higher-Layers Neighbor/ Topology Discovery Higher- Layers 802.1, IP, etc.

Doc.: IEEE 11-04/0319r0 Submission March 2004 W. Steven Conner, Intel Corporation Slide 9 Proposed Next Steps  Set up telecons to continue architecture discussions  Generate draft high-level architecture doc.  Major functional components and definitions, based on IEEE architecture requirements and the PAR  How ESS Mesh fits in with /802 architecture  Identify potential standard and TG draft sections that will need to be amended  In parallel, begin documenting and prioritizing usage models  Will be used to drive specific requirements for functional component solutions

Doc.: IEEE 11-04/0319r0 Submission March 2004 W. Steven Conner, Intel Corporation Slide s (ESS Mesh) WG Draft Timeline  Jan 04: Approval of PAR/5C by WG  Mar 04: Approval by 802 executive committee to start TG  May 04: First ESS Mesh TGs Meeting  May-Sept 04:  Adopt high-level architecture  Prioritize usage models  Adopt detailed requirements for functional component solutions

Doc.: IEEE 11-04/0319r0 Submission March 2004 W. Steven Conner, Intel Corporation Slide 11 Questions or Comments?

Doc.: IEEE 11-04/0319r0 Submission March 2004 W. Steven Conner, Intel Corporation Slide 12 Backup

Doc.: IEEE 11-04/0319r0 Submission March 2004 W. Steven Conner, Intel Corporation Slide 13 Key benefits of building on infrastructure mode:  Immediately applicable to many existing usage models  Existing security models assume infrastructure mode  Infrastructure mode design/implementations tend to be more mature than ad-hoc mode  Ad-hoc mode is broken for multi-hop, power saving, multi-channel, coalescing, etc.  Eliminate requirement to bridge between ad- hoc and infrastructure mode

Doc.: IEEE 11-04/0319r0 Submission March 2004 W. Steven Conner, Intel Corporation Slide 14 IEEE ESS Mesh PAR  Scope:  To develop an IEEE Extended Service Set (ESS) Mesh* with an IEEE Wireless Distribution System (WDS) using the IEEE MAC/PHY layers that supports both broadcast/multicast and unicast delivery over self-configuring multi-hop topologies.  Purpose:  The IEEE (2003 edition) standard provides a four- address frame format for exchanging data packets between APs for the purpose of creating a Wireless Distribution System (WDS), but does not define how to configure or use a WDS. The purpose of the project is to provide a protocol for auto-configuring paths between APs over self-configuring multi-hop topologies in a WDS to support both broadcast/multicast and unicast traffic in an ESS Mesh using the four-address frame format or an extension.

Doc.: IEEE 11-04/0319r0 Submission March 2004 W. Steven Conner, Intel Corporation Slide 15 IEEE ESS Mesh PAR  Additional Explanatory Notes:  Scope of the Project. An IEEE Extended Service Set (ESS) Mesh* is a collection of APs interconnected with wireless links that enable automatic topology learning and dynamic path configuration.  The proposed amendment shall be an extension to the IEEE MAC. The amendment will define an architecture and protocol for providing an IEEE ESS Mesh using the IEEE MAC to create an IEEE Wireless Distribution System that supports both broadcast/multicast and unicast delivery at the MAC layer using radio-aware metrics over self-configuring multi-hop topologies. An ESS Mesh is functionally equivalent to a wired ESS, with respect to the STAs relationship with the BSS and ESS.  The amendment shall enable interoperable formation and operation of an ESS Mesh, but shall be extensible to allow for alternative path selection metrics and/or protocols based on application requirements. A target configuration is up to 32 devices participating as AP forwarders in the ESS Mesh. However, larger configurations may also be contemplated by the standard. It is intended that the architecture defined by the amendment shall allow an ESS Mesh to interface with higher layers and to connect with other networks using higher layer protocols.  The amendment shall utilize IEEE i security mechanisms, or an extension thereof, for the purpose of securing an ESS Mesh in which all of the APs are controlled by a single logical administrative entity for security. The amendment shall allow the use of one or more IEEE radios on each AP in the ESS Mesh.