1. CONFIDENTIAL © Copyright 2009. Aruba Networks, Inc. All rights reserved Proposed indoor extensions to RFC 5139 Peter Thornycroft December 2009

2. CONFIDENTIAL © Copyright 2009. Aruba Networks, Inc. All rights reserved WLAN location opportunities Floorplan showing WLAN access pointsFloorplan showing access points and clients WLANs providing pervasive Wi-Fi access can triangulate to 1-5m Isolated Wi-Fi hotspots can also locate clients Current WLAN managers use a local datum and coordinate structure Uses for location information include: Emergency caller location (can be used to feed E9-1-1 or NG9-1-1) Internal or campus first-responders for emergency calls Asset tracking (healthcare, retail, manufacturing) Location of network devices, clients, rogue APs and intruders (future) Building automation, energy management…

3. CONFIDENTIAL © Copyright 2009. Aruba Networks, Inc. All rights reserved Location in IEEE 802.11 standards Where am I? You’re here, buddy. 802.11k (2008) introduced ‘Location Configuration Information (LCI)’ Can be initiated from AP or client Can be for ‘my location’ or ‘your location’ Format is geospatial, based on RFC 3825 (latitude, longitude, altitude) 802.11v (draft) adds 2 new formats for location ‘Civic address’ (RFC 4776/5139) ‘Identifier’ (URI) But Civic address format to date does not extend within buildings with sufficient granularity. Hence Liaison request from IEEE to IETF https://datatracker.ietf.org/documents/LIAISON/file704.doc … develop extensions to existing Civic binary encodings … to support WLAN location applications… A binary representation that supports the Point, Polygon, Arc Band, Rectangle, Circle, Ellipse, Cube, Cuboid, Sphere, and Ellipsoid shapes is required. The binary representation should extend or be combinable with civic information already defined in RFC 4776 so that a single payload message can convey the location of a WLAN entity that combines Building Address, Floor and a determined/known reference point and reference location as represented by a shape. Note alternate draft submitted: http://tools.ietf.org/html/draft-thomson-geopriv- indoor-location-00 authors are in active discussions on a joint proposal http://tools.ietf.org/html/draft-thomson-geopriv- indoor-location-00

4. CONFIDENTIAL © Copyright 2009. Aruba Networks, Inc. All rights reserved Draft proposal in IETF draft-stanley-geopriv-int-ext & draft-polk-geopriv-int-relative-in-tlv

5. CONFIDENTIAL © Copyright 2009. Aruba Networks, Inc. All rights reserved Proposal Summary Define and register new xml elements for use in PIDF-LO http://www.ietf.org/id/draft-stanley-geopriv-int-ext-00.txt Register the corresponding TLV binary mappings http://tools.ietf.org/id/draft-polk-geopriv-int-relative-in-tlv- 00.txt http://tools.ietf.org/id/draft-polk-geopriv-int-relative-in-tlv- 00.txt Extend the ‘INT’ mechanism defined in draft-rosen-geopriv- pidf-interior http://www.ietf.org/id/draft-rosen-geopriv-pidf-interior-00.txt Support private ‘INT’ element provided in baseline INT Add an extension to support a set of ‘registered INT’ elements Define 4 shapes – point, circle, arcband, polygon Maintain a registry of these elements and TLV fields to enable vendor interoperability Multi-vendor proposal Datum X-axis (East- West) offset Y-axis (North- South) offset ‘shape’ containing location with 95% confidence PointCircleArcbandPolygon Four shapes defined

6. CONFIDENTIAL © Copyright 2009. Aruba Networks, Inc. All rights reserved Example US California Sunnyvale 1344 Crossman Avenue 94089 1 100 Front Door +24 +5 +2 3 Datum (front door) X-axis offset 24m East Y-axis offset 5m North Circle radius 3 m to 95% Z-axis offset 2m ‘up’ North

7. CONFIDENTIAL © Copyright 2009. Aruba Networks, Inc. All rights reserved Questions?