1. doc.: IEEE 802.11-06/1860r0 Submission November 2006 Manfred Arndt (ProCurve Networking by HP)Slide 1 LLDP and LLDP-MED Location Overview Notice: This document has been prepared to assist IEEE 802.11. 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 802.11. 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 802.11 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at.http:// ieee802.org/guides/bylaws/sb-bylaws.pdfstuart.kerry@philips.compatcom@ieee.org Date: 2006-11-16 Authors:

2. doc.: IEEE 802.11-06/1860r0 Submission November 2006 Manfred Arndt (ProCurve Networking by HP)Slide 2 Abstract This location proposal provides a mechanism for a STA to acquire physical location information from the network infrastructure, suitable for Emergency Call Services. No specific location determination mechanism is defined or required.

3. doc.: IEEE 802.11-06/1860r0 Submission November 2006 Manfred Arndt (ProCurve Networking by HP)Slide 3 Emergency Location Overview Location Acquisition ─ Method of providing location information to a network entity Location Conveyance ─ Transporting location information with an emergency call (e.g., as a PIDF-LO SIP header) Location Determination ─ Using measurements to calculate or otherwise discover the physical location Emergency Call Routing ─ Approximate location MUST be known to route call to appropriate PSAP Internet Draft - Best Current Practice for Communications Services in support of Emergency Calling (ECRIT) ─ Minimize the number of protocols to discover physical location, but more than one required to support legacy networks and operator flexibility ─ Devices capable of supporting an emergency call MUST support location by DHCP, [Placeholder for L7, possibly HELD] and LLDP-MED ─ Access network MUST support at least one of DHCP, L7, LLDP-MED, unless operator controls every device (which almost never really happens) PIDF-LO: Presences Information Data Format – Location Object

4. doc.: IEEE 802.11-06/1860r0 Submission November 2006 Manfred Arndt (ProCurve Networking by HP)Slide 4 LLDP Scope IEEE 802.1AB – Link Layer Discovery Protocol (LLDP) A standard and extensible multi-vendor protocol and management elements to support network topology discovery and exchange device configuration and capabilities Developed and maintained by IEEE 802.1, planned for revision PAR submitted Nov 2006, with no comments received

5. doc.: IEEE 802.11-06/1860r0 Submission November 2006 Manfred Arndt (ProCurve Networking by HP)Slide 5 LLDP Objectives Widespread industry adoption –Simple and leveraged design increases chances of vendor adoption –Simple design leads to low development cost Interoperability with many endpoint device types –Low complexity  higher interoperability potential –Must be practical for both cost-restrained and feature rich endpoints High reliability, critical to Emergency Call Service (ECS) scenarios –Low complexity with fewest possible “moving parts” –Location always provided immediately on connection or move Easily extensible for future needs

6. doc.: IEEE 802.11-06/1860r0 Submission November 2006 Manfred Arndt (ProCurve Networking by HP)Slide 6 Basic Functions of IEEE 802.1AB-2005 Simple one-way neighbor discovery protocol with periodic transmissions LLDP frames are not forwarded, but constrained to a point to point link LLDP frames contain formatted TLVs (type, length, value) –Globally unique system and port identification –Time-to-Live information for ageing purposes –Optional system capabilities (e.g. router, IP phone, wireless AP) –Optional system name, description, and management address –Organizational extensions Receiver stores information in a neighbor database, accessible via SNMP Receiver ages MIB to insure only valid network data is available Management applications can harness the power via SNMP

7. doc.: IEEE 802.11-06/1860r0 Submission November 2006 Manfred Arndt (ProCurve Networking by HP)Slide 7 All LLDP Entities contain 1 or more LLDP Agents LLDP operates above the MAC Service Layer LSAP = Link service access point MSAP = MAC service access point A peak under the hood * Local MIBs: Holds locally configured data Data may be supplied/modified by management applications Remote MIBs: Holds and ages received data from far end Available for management applications use Entity Management MIBs: Common data, of use to LLDP and others Not directly part of LLDP LLDP State machine Controls Tx and Rx of frames Contains state machine control variables * Animated Slide

8. doc.: IEEE 802.11-06/1860r0 Submission November 2006 Manfred Arndt (ProCurve Networking by HP)Slide 8 IEEE 802.3 LLDP frame format LLDP Multicast = 01-80-C2-00-00-0E (same as Spanning Tree except for last octet) LLDPDU format Each TLV (Type, Length, Value) contains a set of useful attributes

9. doc.: IEEE 802.11-06/1860r0 Submission November 2006 Manfred Arndt (ProCurve Networking by HP)Slide 9 Easy to define organizational extensions There are currently three organizational extensions: 1. IEEE 802.1 Port VLAN, Port & Protocol VLANs, VLAN Name, Protocol Entity 2. IEEE 802.3 MAC/PHY configuration, PoE Power, Link Aggregation, Maximum Frame Size 3. TIA - IP Telephony Infrastructure (LLDP-MED) VLAN & QoS auto-config, Physical Location Discovery, Detailed Inventory, Fine Grain PoE Power LLDP TLV Extensibility

10. doc.: IEEE 802.11-06/1860r0 Submission November 2006 Manfred Arndt (ProCurve Networking by HP)Slide 10 LLDP-MED Scope ANSI/TIA-1057 - LLDP Media Endpoint Discovery (LLDP-MED) Extension to base IEEE 802.1AB (LLDP) standard to support multi- vendor interoperability between VoIP endpoint devices and IEEE 802 networking infrastructure elements, including physical location discovery (among other things) Developed by TIA TR-41.4 (VoIP Standards) ANSI - American National Standards Institute TIA - Telecommunications Industry Association

11. doc.: IEEE 802.11-06/1860r0 Submission November 2006 Manfred Arndt (ProCurve Networking by HP)Slide 11 What is LLDP-MED? ANSI/TIA-1057, LLDP Media Endpoint Discovery: Developed by TIA TR-41.4 (VoIP Standards) Provides VoIP-specific extensions to base LLDP protocol – New TLVs (Type, Length, Value) for: Location identification, including to support Emergency Call Service LAN policy discovery (VLAN, Layer 2 priority, Layer 3 QoS) Fine grained power management for Power over Ethernet devices Inventory management – Endpoint move detection and reporting – “Fast Start” protocol behaviour, to improve timeliness – SNMP MIBs definition to support management of above

12. doc.: IEEE 802.11-06/1860r0 Submission November 2006 Manfred Arndt (ProCurve Networking by HP)Slide 12 Enables Physical Location Services, including Emergency Call Service (ECS) –Supports NENA E911 and other location services (for example NENA TID 07-501) Multiple Location Formats Supported, and easily extensible –Coordinate-based LCI (Location Configuration Information) subtype as defined by IETF RFC 3825 –Civic Address LCI subtype defined by draft-ietf-geopriv-dhcp-civil-09 (approved, in RFC Editor queue) –ELIN (Emergency Location Identification Number) subtype, to support traditional PSAP-based ECS –One or more formats may be used simultaneously for different endpoint requirements Two ECS methods supported (End-device & Notification based) –Switch advertises periodic location info for endpoint to use –Switch sends notification whenever a new endpoint is detected or an endpoint moves Location TLV NENA - National Emergency Number Association PSAP - Public Service Access Point

13. doc.: IEEE 802.11-06/1860r0 Submission November 2006 Manfred Arndt (ProCurve Networking by HP)Slide 13 End-device based location Method 1 - Ideal for smart clients (e.g., SIP phones) 1.A management application or an LIS (Location Information Server) programs the location identification into network infrastructure using SNMP and the LLDP-MED MIB –Every port may advertise a unique coordinate, civic, and/or ELIN location value 2.Network infrastructure advertise periodic LLDP-MED frames containing location TLV –Endpoint has location information to use immediately in the call setup

14. doc.: IEEE 802.11-06/1860r0 Submission November 2006 Manfred Arndt (ProCurve Networking by HP)Slide 14 Applicability to VoWLAN LLDP applicability –LLDP operates above the MAC service layer, and as such can be easily implemented, without requiring any driver modifications –LLDP is a multicast protocol, and as such is limited to advertise attributes common to all stations in the same SSID broadcast domain –Multicasts to DS are sent using unicast for AP to relay, but BPDU frames must never be forwarded (01-80-C2-00-00-xx) Physical Location Identification –As currently defined, LLDP-MED can provide physical location of AP, which is suitable for many ECS requirements –For APs capable of client specific location, consider using reliable 802.11 multicasting with the 4 address format

15. doc.: IEEE 802.11-06/1860r0 Submission November 2006 Manfred Arndt (ProCurve Networking by HP)Slide 15 VoWLAN Location Considerations Emergency Services, Some Thoughts... Wireless client would quickly discover new physical location on roaming Ethernet switches need physical location configuration anyway, to support wired IP phones AP could auto-discover it’s physical location via LLDP from wired network For WLAN devices capable of higher accuracy –Smart clients could compute relative position, using TOA or triangulation, from nearby APs –AP could advertise client specific location using reliable multicasts or via the Presence Parameters information element (11v), in addition to LLDP-MED location

16. doc.: IEEE 802.11-06/1860r0 Submission November 2006 Manfred Arndt (ProCurve Networking by HP)Slide 16 Summary: LLDP-MED Location LLDP-MED provides several technical advantages for ECS location ─ Existing, well defined standard that is easily understood ─ Reduced complexity with high interoperability potential ─ Easily extensible for future needs ─ Applicable to all IEEE 802 networks and would provide common interface across many networking technologies for ECS capable software applications LLDP-MED is a MUST in ecrit-phonebcp (for Emergency Services) Believed that all interfaces required for ECS location delivery are defined by LLDP-MED today Industry accepted solution, already deployed in wired IP phones

17. doc.: IEEE 802.11-06/1860r0 Submission November 2006 Manfred Arndt (ProCurve Networking by HP)Slide 17 References The formal IEEE 802.1AB-2005 LLDP specification is available for download at: http://standards.ieee.org/getieee802/download/802.1AB-2005.pdf The formal ANSI/TIA-1057 specification is available for download at: http://www.tiaonline.org/standards/technology/voip/documents/ANSI-TIA-1057_final_for_publication.pdf Best Current Practice for Communications Services in support of Emergency Calling http://www.ietf.org/internet-drafts/draft-ietf-ecrit-phonebcp-00.txt