Telecommunications Industry Association TR41.4-07-08-010-L

Status LLDP (IEEE 802.1AB) approved May 2005 LLDP-MED (ANSI/TIA-1057) approved April 2006 IEEE initiatives: IEEE 802.1AB revision (“ABrev”), work in progress Includes roll-in of some LLDP-MED concepts (e.g. Fast Start) IEEE 802.3at “PoE Plus”, work in progress LLDP-MED Extended PoE TLV adopted as basis for management: dynamic fine-grain power negotiation, priority, conservation modes WLAN-related extensions proposed Restrict TLV visibility to particular endpoints, using unicast MAC address (today, 802.11 broadcasts LLDP to all endpoints in same SSID on AP) Proposed to be part of ABrev (not yet accepted, status unclear) IETF Emergency Call Service standardization IETF will define next generation ECS (E911) architecture LLDP-MED a MUST requirement for IP Phone support (one of 3 methods) and part of overall framework, work in progress (draft-ecrit-phonebcp-xx, draft-ecrit-framework-xx) Consensus agreement: all location discovery methods must be able to support location by reference as well as PIDF-LO format  LLDP-MED does not support this today Blatherwick 10.08.07 2

Potential LLDP-MED updates (TR-41.4 work items) Further refinement of Advanced PoE Align with IEEE PoE Plus needs Alternative, TR-41.4 assist IEEE to define it Extend Location Identification to enable further IETF requirements PIDF-LO data type Location by reference (pass location URI) NOTE: Likely LbyR required for PIDF-LO, due to size constraints Indicate location determination method used (manual, GPS, triangulated, etc) Add ECS call in progress flag Give high network priority, unauthenticated access IEEE perceived requirement (may not be valid!) Update LAN Policy application types Add voice management, voice application etc Add further device identification Phone number / extension, sip: & tel: URI, user name, etc Remove Annex B “Content of Civic Address LCI data format“ No longer needed, refer directly to RFC4776 – cleanup only Blatherwick 10.08.07 3