Slide 1

Doc.: IEEE 11-04/0319r0

Submission

March 2004

W. Steven Conner, Intel Corporation

Architectural Considerations and Requirements for 802.11

ESS Mesh

March 16, 2004

Steven Conner

Intel Corporation

(w.steven.conner@intel.com)

Slide 2

Doc.: IEEE 11-04/0319r0

Submission

March 2004

W. Steven Conner, Intel Corporation

Outline Review of 802.11 ESS Mesh Scope

Architectural Considerations and Requirements

Proposed Next Steps

Slide 3

Doc.: IEEE 11-04/0319r0

Submission

March 2004

W. Steven Conner, Intel Corporation

Overview: 802.11 Mesh Mesh is not limited to highly mobile networks with Mesh is not limited to highly mobile networks with

no infrastructureno infrastructure

Also has application in many fixed-infrastructure Also has application in many fixed-infrastructure environmentsenvironments

Extended range and coverage, without requiring Extended range and coverage, without requiring additional wires (convenient deployment, cost)additional wires (convenient deployment, cost)

Enhanced redundancy, reliabilityEnhanced redundancy, reliability

Potential throughput improvementPotential throughput improvement

Example networks where 802.11 Mesh is useful:Example networks where 802.11 Mesh is useful:

Home networks, hotspot networks, etc.Home networks, hotspot networks, etc.

Slide 4

Doc.: IEEE 11-04/0319r0

Submission

March 2004

W. Steven Conner, Intel Corporation

Summary of 802.11s PAR Scope Approved by WG in January

Scope: Develop an Infrastructure-Mode 802.11 Scope: Develop an Infrastructure-Mode 802.11 ESS Mesh ESS Mesh with 802.11 MAC/PHY (WDS links)with 802.11 MAC/PHY (WDS links) Scale: Target ~32 active mesh APsScale: Target ~32 active mesh APs Security: Include support for trusted set of mesh APs Security: Include support for trusted set of mesh APs

controlled by single logical administrative domaincontrolled by single logical administrative domain Mesh Topology/Paths: Include support for both Mesh Topology/Paths: Include support for both

broadcast/multicast and radio-channel-aware unicast broadcast/multicast and radio-channel-aware unicast path selection/data deliverypath selection/data delivery

Multiple-radios: Include support for optional multiple-Multiple-radios: Include support for optional multiple-radios per routerradios per router

Ensure support for interfacing with higher layersEnsure support for interfacing with higher layers Enable interoperability, extensibilityEnable interoperability, extensibility

Slide 5

Doc.: IEEE 11-04/0319r0

Submission

March 2004

W. Steven Conner, Intel Corporation

Distribution SystemDistribution System(DS)(DS)

802.11 ESS Mesh802.11 ESS Mesh

Mesh AP LinksMesh AP Links802.11 MAC/PHY802.11 MAC/PHY

(4-addr data frames)(4-addr data frames)

Client-to-AP LinksClient-to-AP Links802.11 MAC/PHY802.11 MAC/PHY

(3-addr data frames)(3-addr data frames)

802.11 BSS802.11 BSS

How does IEEE 802.11 ESS Mesh fit in to the big picture?

802.11 ESS802.11 ESS

Slide 6

Doc.: IEEE 11-04/0319r0

Submission

March 2004

W. Steven Conner, Intel Corporation

High-Level Requirements for 802.11s ESS Mesh Interoperability: 802.11 is required to appear to higher Interoperability: 802.11 is required to appear to higher

layers as a current style 802 LAN (5.1.1.4)layers as a current style 802 LAN (5.1.1.4) LAN broadcast and unicast deliveryLAN broadcast and unicast delivery Interfacing to other networks, e.g. bridging and gatewayingInterfacing to other networks, e.g. bridging and gatewaying

Self-configuring multi-hop topologies and pathsSelf-configuring multi-hop topologies and paths 802.11 MAC/PHY radio-awareness for efficient path selection 802.11 MAC/PHY radio-awareness for efficient path selection

and data deliveryand data delivery

Maintain WLAN securityMaintain WLAN security New 802.11 security requirements: New 802.11 security requirements:

AP-to-AP authentication, key distribution, topology/statistics AP-to-AP authentication, key distribution, topology/statistics exchange, data forwardingexchange, data forwarding

Don’t break 802.11i for legacy client STA securityDon’t break 802.11i for legacy client STA security

Slide 7

Doc.: IEEE 11-04/0319r0

Submission

March 2004

W. Steven Conner, Intel Corporation

ESS Mesh Functional Components 802.11 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.)

802.11 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

Slide 8

Doc.: IEEE 11-04/0319r0

Submission

March 2004

W. Steven Conner, Intel Corporation

802.11s Strawman Architecture

UnicastPath

Selection

LANBcast

Protocol

Radio-AwareMesh

Metrics

MAC Enhancements for Mesh

UnicastFwding

BcastFwding

ESS Mesh Security

PHY

MAC

802.11k

802.11i

802.11e/n

Interfacing to 802.11 Services

802.11a/b/g/n/…

Interfacing to Higher-Layers 802.11

Neighbor/TopologyDiscovery

Higher-Layers

802.1,IP, etc.

Slide 9

Doc.: IEEE 11-04/0319r0

Submission

March 2004

W. Steven Conner, Intel Corporation

Proposed Next Steps Set up telecons to continue architecture Set up telecons to continue architecture

discussionsdiscussions Generate draft high-level architecture doc.Generate draft high-level architecture doc.

Major functional components and definitions, based on Major functional components and definitions, based on IEEE 802.11 architecture requirements and the PARIEEE 802.11 architecture requirements and the PAR

How ESS Mesh fits in with 802.11/802 architectureHow ESS Mesh fits in with 802.11/802 architecture Identify potential standard and TG draft sections that Identify potential standard and TG draft sections that

will need to be amendedwill need to be amended

In parallel, begin documenting and prioritizing In parallel, begin documenting and prioritizing usage models usage models Will be used to drive specific requirements for Will be used to drive specific requirements for

functional component solutionsfunctional component solutions

Slide 10

Doc.: IEEE 11-04/0319r0

Submission

March 2004

W. Steven Conner, Intel Corporation

802.11s (ESS Mesh) WG Draft Timeline

Jan 04: Approval of PAR/5C by 802.11 WG Jan 04: Approval of PAR/5C by 802.11 WG

Mar 04: Approval by 802 executive committee Mar 04: Approval by 802 executive committee to start TG to start TG

May 04: First ESS Mesh TGs MeetingMay 04: First ESS Mesh TGs Meeting

May-Sept 04: May-Sept 04: Adopt high-level architectureAdopt high-level architecture

Prioritize usage modelsPrioritize usage models

Adopt detailed requirements for functional Adopt detailed requirements for functional component solutionscomponent solutions

Slide 11

Doc.: IEEE 11-04/0319r0

Submission

March 2004

W. Steven Conner, Intel Corporation

Questions

or

Comments?

Slide 12

Doc.: IEEE 11-04/0319r0

Submission

March 2004

W. Steven Conner, Intel Corporation

Backup

Slide 13

Doc.: IEEE 11-04/0319r0

Submission

March 2004

W. Steven Conner, Intel Corporation

Key benefits of building on 802.11 infrastructure mode:

Immediately applicable to many existing usage Immediately applicable to many existing usage modelsmodels

Existing security models assume infrastructure Existing security models assume infrastructure modemode

Infrastructure mode design/implementations Infrastructure mode design/implementations tend to be more mature than ad-hoc modetend to be more mature than ad-hoc mode Ad-hoc mode is broken for multi-hop, power Ad-hoc mode is broken for multi-hop, power

saving, multi-channel, coalescing, etc.saving, multi-channel, coalescing, etc.

Eliminate requirement to bridge between ad-hoc Eliminate requirement to bridge between ad-hoc and infrastructure modeand infrastructure mode

Slide 14

Doc.: IEEE 11-04/0319r0

Submission

March 2004

W. Steven Conner, Intel Corporation

IEEE 802.11 ESS Mesh PAR Scope:Scope:

To develop an IEEE 802.11 Extended Service Set (ESS) Mesh* with To develop an IEEE 802.11 Extended Service Set (ESS) Mesh* with an IEEE 802.11 Wireless Distribution System (WDS) using the IEEE an IEEE 802.11 Wireless Distribution System (WDS) using the IEEE 802.11 MAC/PHY layers that supports both broadcast/multicast and 802.11 MAC/PHY layers that supports both broadcast/multicast and unicast delivery over self-configuring multi-hop topologies.unicast delivery over self-configuring multi-hop topologies.

Purpose:Purpose: The IEEE 802.11-1999 (2003 edition) standard provides a four-The IEEE 802.11-1999 (2003 edition) standard provides a four-

address frame format for exchanging data packets between APs for address frame format for exchanging data packets between APs for the purpose of creating a Wireless Distribution System (WDS), but the purpose of creating a Wireless Distribution System (WDS), but does not define how to configure or use a WDS. The purpose of the 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 project is to provide a protocol for auto-configuring paths between APs over self-configuring multi-hop topologies in a WDS to support APs over self-configuring multi-hop topologies in a WDS to support both broadcast/multicast and unicast traffic in an ESS Mesh using both broadcast/multicast and unicast traffic in an ESS Mesh using the four-address frame format or an extension.the four-address frame format or an extension.

Slide 15

Doc.: IEEE 11-04/0319r0

Submission

March 2004

W. Steven Conner, Intel Corporation

IEEE 802.11 ESS Mesh PAR Additional Explanatory Notes:Additional Explanatory Notes:

Scope of the Project. An IEEE 802.11 Extended Service Set (ESS) Mesh* is a Scope of the Project. An IEEE 802.11 Extended Service Set (ESS) Mesh* is a collection of APs interconnected with wireless links that enable automatic topology collection of APs interconnected with wireless links that enable automatic topology learning and dynamic path configuration. learning and dynamic path configuration.

The proposed amendment shall be an extension to the IEEE 802.11 MAC. The The proposed amendment shall be an extension to the IEEE 802.11 MAC. The amendment will define an architecture and protocol for providing an IEEE 802.11 ESS amendment will define an architecture and protocol for providing an IEEE 802.11 ESS Mesh using the IEEE 802.11 MAC to create an IEEE 802.11 Wireless Distribution Mesh using the IEEE 802.11 MAC to create an IEEE 802.11 Wireless Distribution System that supports both broadcast/multicast and unicast delivery at the MAC layer 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 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 is functionally equivalent to a wired ESS, with respect to the STAs relationship with the BSS and ESS. the BSS and ESS.

The amendment shall enable interoperable formation and operation of an ESS Mesh, 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 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 based on application requirements. A target configuration is up to 32 devices participating as AP forwarders in the ESS Mesh. However, larger configurations may 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 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 the amendment shall allow an ESS Mesh to interface with higher layers and to connect with other networks using higher layer protocols.connect with other networks using higher layer protocols.

The amendment shall utilize IEEE 802.11i security mechanisms, or an extension The amendment shall utilize IEEE 802.11i security mechanisms, or an extension thereof, for the purpose of securing an ESS Mesh in which all of the APs are 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 controlled by a single logical administrative entity for security. The amendment shall allow the use of one or more IEEE 802.11 radios on each AP in the ESS Mesh.allow the use of one or more IEEE 802.11 radios on each AP in the ESS Mesh.