1 / 8

802 Handoff ECSG SEC Report

802 Handoff ECSG SEC Report. David Johnston david.johnston@ieee.org dj.johnston@intel.com. First Session of 802 Handoff ECSG Launched, May 2003. Attendance Monday – 30 Tuesday – 19 Thursday – 22 Total Attendance – 45 29 Separate organizations represented. Officers. Chair

tedith
Download Presentation

802 Handoff ECSG SEC Report

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. 802 Handoff ECSGSEC Report David Johnston david.johnston@ieee.org dj.johnston@intel.com David Johnston, Intel

  2. First Session of 802 Handoff ECSG Launched, May 2003 • Attendance • Monday – 30 • Tuesday – 19 • Thursday – 22 • Total Attendance – 45 • 29 Separate organizations represented David Johnston, Intel

  3. Officers • Chair • David Johnston, Intel • Reluctant Recording Secretary • Paul Lin, Intel • Vice Chair • None, volunteers welcome David Johnston, Intel

  4. Activities • Technical presentations received • DoCoMo, Intel (4), Lucent, Boeing • Addressed • Mobile IP interdependencies with L2 methods (E.G. L2 Triggers • Feasibility of handoff timing • Technical aspects of solutions • PAR text • Worked on definitions of problem, scope and PAR • To be completed David Johnston, Intel

  5. Solution Space • Proposed Elements of Solution Include: • Layer 2 Triggers, semantics and interface • Meets needs of mobile IP handoffs but are generally applicable • Handoff decision data • Data accessible to mobile stations to enable good and timely handoff decisions • May include authentication services required, QoS capabilities, upper layer services present, neighbor AP information, vendor proprietary etc. • Needs structure and interface • Potential for backbone signalling (no consensus) • Does not include handoff signalling primitives • Handoff-Req/Handoff-Resp etc. David Johnston, Intel

  6. Targets • Fill out technical issues this session • Consensus on text for PAR & 5C text by end of September Interim • Consensus on Placement Issue by end of September Interim • Submit PAR & Coverletters, Recommendations etc. shortly after September interim David Johnston, Intel

  7. Placement • Correct placement is non obvious • Feedback from SEC sought • 802.1[xy] • For: • May not look out of place in 802.1 • Against: • Predominantly wireless issues not the main focus of 802.1 constituency • Makes Co-location with wireless groups difficult • 802.1 busy with linksec? • 802 WG • For • Suitable co-location can be arranged (11/15/16/20) • Access to higher concentration of relevant expertise • Against • Covers wired and wireless, but wireless is the main problem space. Solving for wireless solves for the general case David Johnston, Intel

  8. Continuation • Request that the SEC re-approve the 802 Handoff ECSG. David Johnston, Intel

More Related