1. Extensible Security and Routing Proposal
doc.: IEEE /0165r0
March 2005
May 2005
Extensible Security and Routing Proposal
Date:
Authors:
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 < ieee802.org/guides/bylaws/sb-bylaws.pdf>, 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
Hideyuki Suzuki, Sony Corp.
Steven Conner, Intel Corp.

2. doc.: IEEE /0165r0
March 2005
May 2005
Overview/Agenda
This presentation will outline the basic principle to support Extensible Mesh Security and Routing.
Keys to extensibility
Extensible Mesh Security
Extensible Mesh Routing
Hideyuki Suzuki, Sony Corp.
Steven Conner, Intel Corp.

3. Focus of this presentation
doc.: IEEE /0165r0
March 2005
May 2005
Focus of this presentation
Mesh Topology Learning, Routing, and Forwarding
Mesh Security
Mesh Measurement
Mesh Discovery and Association
Mesh Medium Access Coordination
Compatibility to Services
Interworking
Mesh Configuration and Management
Hideyuki Suzuki, Sony Corp.
Steven Conner, Intel Corp.

4. PAR Extensible-conscious framework requires
doc.: IEEE /0165r0
March 2005
May 2005
PAR
“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.”
“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.”
Extensible-conscious framework requires
an abstraction and discovery functionality
Hideyuki Suzuki, Sony Corp.
Steven Conner, Intel Corp.

5. Keys to Extensibility Layering and Abstraction Advertise and Scanning
doc.: IEEE /0165r0
March 2005
May 2005
Keys to Extensibility
Layering and Abstraction
Layering
fundamental technique in network protocol design
Abstraction
EAP (Extensible Authentication Protocol)
ERP (Extensible Routing Protocol)
Advertise and Scanning
Advertise
advertise its existence and capabilities
Scanning
discover Mesh Points with active/passive scanning
Hideyuki Suzuki, Sony Corp.
Steven Conner, Intel Corp.

6. Layering and Abstraction
doc.: IEEE /0165r0
March 2005
May 2005
Layering and Abstraction
EAP-TLS
PEAP
EAP-TTLS
Proactive
Routing
Protocol
Reactive
Routing
Protocol
Hybrid
Routing
Protocol
...
...
EAP
(Extensible Authentication Protocol)
ERP
(Extensible Routing Protocol)
802.1X
802.11s
(Mesh Discovery for Mesh Security)
Mesh Discovery for Mesh Routing
802.11i
PHY
PHY
Mesh Security Layering
Mesh Routing Layering
Hideyuki Suzuki, Sony Corp.
Steven Conner, Intel Corp.

7. Advertise and Scanning
doc.: IEEE /0165r0
March 2005
May 2005
Advertise and Scanning
Advertise its capability
Active scanning with Mesh Beacon
Passive scanning with Mesh Probe Request and Probe Response
Discover and Negotiate capabilities
Security Capability
Discovery with mesh scanning, negotiation by RSN IE
Routing Capability
Announce a routing information element
But, current IEEE draft does not mention about
any details of scanning in WDS mode.
Hideyuki Suzuki, Sony Corp.
Steven Conner, Intel Corp.

8. Extensible Mesh Security
doc.: IEEE /0165r0
March 2005
May 2005
Extensible Mesh Security
Hideyuki Suzuki, Sony Corp.
Steven Conner, Intel Corp.

9. Basic Idea Utilize IEEE 802.11i security mechanisms basically.
doc.: IEEE /0165r0
March 2005
May 2005
Basic Idea
Utilize IEEE i security mechanisms basically.
But, current i draft does not mention about any details in WDS mode.
Need some extensions to i
Advertise/Scanning
Advertise security capability with RSN IE in WDS mode
Negotiation
“ RSNA policy selection in an IBSS” as a model
The role of Supplicant, Authenticator, AS
Each Mesh Point implements both an Authenticator PAE and a Supplicant PAE, and both the EAP Authenticator and Peer roles.
Centralized or Distributed Security support
In certain applications, the AS may be integrated into the same physical device as the Mesh Point in a WDS.
Hideyuki Suzuki, Sony Corp.
Steven Conner, Intel Corp.

10. Example Sequence doc.: IEEE 802.11-05/0165r0 May 2005 March 2005
Mesh Probe Request
Mesh
Discovery
Mesh Beacon or Mesh Probe Response
with RSN IE
Mesh Association Request
with RSN IE
Mesh
Negotiation
Mesh Association Response
Hideyuki Suzuki, Sony Corp.
Steven Conner, Intel Corp.

11. Extensible Mesh Routing
doc.: IEEE /0165r0
March 2005
May 2005
Extensible Mesh Routing
Hideyuki Suzuki, Sony Corp.
Steven Conner, Intel Corp.

12. Mesh Routing Architecture
doc.: IEEE /0165r0
March 2005
May 2005
Mesh Routing Architecture
Finding one suitable routing protocol for all scenarios is almost impossible
→ Introducing new architecture to achieve selective routing protocol
Each mesh node need to have Routing Capability of its own
Routing capability contains:
Available Routing Protocol
Available Routing Metrics
Current Usage/Deployment Scenario
Node Attribute
Optional area for future extension
Advertise Routing Capability for neighbors in Mesh Beacon
Each node can recognize the active routing protocol
Hideyuki Suzuki, Sony Corp.
Steven Conner, Intel Corp.

13. Mesh Unicast/Broadcast Data Delivery
doc.: IEEE /0165r0
March 2005
May 2005
Mesh Unicast/Broadcast Data Delivery
Mesh Unicast Data Delivery
WDS header has 4 address fields (RA, TA, DA, SA)
Table Driven Routing is appropriate for s
Lookup routing table by DA, set next-hop address in RA
Decrement TTL value by forwarding
Mesh Broadcast Data Delivery
Flooding to all nodes is a key feature to enable IP-Layer broadcast
Choosing good MPRs leads to efficient flooding mechanism
Proposed beacon has Neighbor Type like an OLSR HELLO message
Unicast Data Delivery -> WDS 4つのフィールドの話　そこからTable Driven Routingの話に持っていく
Broadcast Data Delivery -> Flooding MPRsの話
Flooding is the one of key feature for mesh network
Hideyuki Suzuki, Sony Corp.
Steven Conner, Intel Corp.

14. doc.: IEEE /0165r0
March 2005
May 2005
Mesh Routing Protocol
Selective Routing Protocol based on application demands
At least one mandatory routing protocol on each scenario
(e.g.) Reactive is well-suited to residential network
(e.g.) Proactive can be best for public network
Every routing protocol may be able to access routing table
Routing table should have multiple next-hop to achieve multi-path routing
Proposed routing entry must have all of fields as below:
Destination MAC address
Next-hop MAC address(es)
Link quality related to the next-hop
Hop count to the destination
Routing flags and status
Optional fields S D A B C E F G
Next-hop 1
Next-hop 2
Source
Destination
Hideyuki Suzuki, Sony Corp.
Steven Conner, Intel Corp.

15. doc.: IEEE /0165r0
March 2005
May 2005
Conclusion
One of the goals of this presentation is to provide an extensible framework.
This proposal enables to change the security and routing protocol flexibly.
Hideyuki Suzuki, Sony Corp.
Steven Conner, Intel Corp.

16. End of the slide doc.: IEEE 802.11-05/0165r0 May 2005 March 2005
Hideyuki Suzuki, Sony Corp.
Steven Conner, Intel Corp.