January 2004 doc L 2Triggersdjr 1 IEEE 802

January. 2004 doc. : L 2_Triggers_dj_r 1 IEEE 802 Handoff ECSG L 2 Triggers David Johnston david. johnston@ieee. org dj. johnston@intel. com Submission 1 David Johnston, Intel

January. 2004 doc. : L 2_Triggers_dj_r 1 Background. . • ‘Fast Handoff for Mobile IP and Link Layer Triggers’. Gang Wu & Alper Yegin. – Recommends • • • ‘Architectural Elements of an 802 Handoff Solution’, David Johnston – Recommends • • • Formal definition of 802 L 2 triggers and associated APIs Align definitions between IETF and IEEE L 2 Triggers Flexibility/Extensibility in trigger definition ‘draft-satish-l 2 -mobilereq-01. txt’, Satish Jamadagni – Submission Ties L 2 triggers to handover decision stages 2 David Johnston, Intel

January. 2004 doc. : L 2_Triggers_dj_r 1 Potential Trigger Types • • • Link_up(which link) Link_down(which_link, why) Link_going_up(which link, when) Link_going_down(which link, when) Domain_crossing(old subnet, new subnet) Etc. Submission 3 David Johnston, Intel

January. 2004 doc. : L 2_Triggers_dj_r 1 Trigger Trajectories - Local • Upper Layer attaches to LSAP of LLC IP Other LLC • May register interest in particular triggers from a trigger source • Triggers may therefore have multiple destinations • Triggers may originate from PHY, or MAC PHY Submission 4 David Johnston, Intel

January. 2004 doc. : L 2_Triggers_dj_r 1 Trigger Trajectories – Link Traversing IP Other LLC MAC PHY • Trigger sent down the stack to appear at remote end of link Other • Requires a transport • Security Implicationsb • Applies to AP-STA, SS-BS situations • Upper layer needs a reason to use these triggers • Could originate from upper layer Submission IP 5 LLC MAC PHY David Johnston, Intel

January. 2004 doc. : L 2_Triggers_dj_r 1 Trigger Semantics • • • Triggers should have well defined semantics Implementations or standards defined behavior (e. g. in dot 11 or dot 16) map semantics of trigger to internal events E. G. – “Link_up” = Full MSDU transport established Submission 6 David Johnston, Intel

January. 2004 doc. : L 2_Triggers_dj_r 1 Upper layer trigger interface • MIBs – • Programmatic API? – • Wrong application, not station management, SNMP access not required, doesn’t fit with link traversing triggers Goes beyond the 802 spec <-> implementation domain boundary Triggers look similar in type to incoming asynchronous data arrival – – – Submission Causes indication upwards through MAC SAP Are annotated events, not states Recommend adding MAC SAP trigger primitives 7 David Johnston, Intel

January. 2004 doc. : L 2_Triggers_dj_r 1 Upper layer trigger interface • Must support trigger registration – Register interest in a trigger – Declare supported trigger capabilities • Still do through MAC SAP? Or use MIBs? – Link traversing triggers suggest MAC SAP approach Submission 8 David Johnston, Intel

January. 2004 doc. : L 2_Triggers_dj_r 1 Trigger Parameters • Generic: – – • Type Remote, Local? Source (UL, MAC, PHY) Registered Recipients (LSAP id list) Specific – Reason Codes – Time Estimates – Other? Submission 9 David Johnston, Intel

January. 2004 doc. : L 2_Triggers_dj_r 1 IETF/3 GPP/other • Triggers are pointless unless upper layer handover algorithms are deployed that understand them We should kickstart the process by drawing up strawman trigger specification • – – • • • Trigger Semantics MAC SAP Primitives Iterate and refine with trigger consuming bodies such as IETF Arrive at base trigger suite that will be used/useable Standardize them! Submission 10 David Johnston, Intel