80 likes | 95 Views
Dive into Work Packages 1-4 to address L2-L3 handoff challenges. Explore APIs, triggers, information conduit, and network detection solutions. Drive towards optimized handoff mechanisms.
E N D
IEEE 802 Handoff ECSGWork Package Discussion David Johnston david.johnston@ieee.org dj.johnston@intel.com David Johnston, Intel
How to Structure the Work Work Package 1 Work Package 2 Work Package 3 Work Package 4 Editor Assembles Structured Document Ballots/Recircs Work on draft text until we like it David Johnston, Intel
Which Work Packages • Need to address the problem statements • Insuffiencient L2-L3 information to support L3 handoff • Network detection sucks • No media independent conduit to carry any of this information • And attack them with technical solutions • Technical solutions ≈ Work Packages David Johnston, Intel
WP1. Information Conduit • How to get information across the link in a handoff independent way • E.G. • Controlled/uncontrolled Port Entity David Johnston, Intel
WP2. Information • What information will we pass? • Support Handoff • Network Detection and Selection • Advertisments • Align with non 802 information • Support interworking with non 802 systems • How is it structured and encoded? David Johnston, Intel
WP3. Triggers • What triggers should we define • Address mobile IP as a primary case • Do we care about end to end triggers? • Mobile IP fast handoff use cases • Work with IETF to get it right David Johnston, Intel
WP4. APIs & Interfaces • Define APIs and/or other interfaces at the top of the MAC service at the top of any entity above the LLC we define David Johnston, Intel
Output • Output is • Recommendations or Text • Initial draft text is assembled from the WP output • WPs can happen in parallel or serial David Johnston, Intel