July 2003 doc 00 03 0026 00 0000

July. 2003 doc. : 00 -03 -0026 -00 -0000 Handoff_Par_Discussion PAR Discussion David Johnston david. johnston@ieee. org dj. johnston@intel. com Submission 1 David Johnston, Intel

July. 2003 doc. : 00 -03 -0026 -00 -0000 Handoff_Par_Discussion Scope Intent • “The scope of this project is to develop a standard that shall define mechanisms that may be adopted into 802 implementations. . . ” – This is an 802 thing – We are not a layer 3 thing Submission 2 David Johnston, Intel

July. 2003 doc. : 00 -03 -0026 -00 -0000 Handoff_Par_Discussion Scope Intent • “so that handoff of handoff-capable upper layer entities e. g. Mobile. IP sessions, can be optimized. . . ” – We are not trying to hand of MAC or PHY layer entities. It is the upper layer entity that is handing off – We are trying to enable higher layer entities to be handed off – We are not Mobile. IP but Mobile. IP is and example of something that is applicable Submission 3 David Johnston, Intel

July. 2003 doc. : 00 -03 -0026 -00 -0000 Handoff_Par_Discussion Scope Intent • “between homogeneous and heterogeneous 802 media types both wired and wireless. . . ” – We apply for handoff between • 802. x 802. y when x==y or x!=y – We include 802. 3 and other wired technologies • Addresses the case of a docked laptop/PDA handing off to a wireless connection when undocked – When x==y we must not conflict with handoff mechanisms specified for that case – Also we must avoid cases where specific optimized handoff mechanisms have been defined between a pair of dissimilar network types (x!=y) • So, we need an exception… Submission 4 David Johnston, Intel

July. 2003 doc. : 00 -03 -0026 -00 -0000 Handoff_Par_Discussion Scope Intent • “, where handoff is not otherwise defined. . . ” – Avoids E. G. intra ESS 802. 11 handoff – But applies to inter ESS 802. 11 handoff – Addresses handoff between heterogeneous network types since no 802. x to 802. y handoff mechanism is currently specified Submission 5 David Johnston, Intel

July. 2003 doc. : 00 -03 -0026 -00 -0000 Handoff_Par_Discussion Scope Intent • “Consideration will be made to ensure compatibility with the 802 architectural model. …” – This is a 5 C requirement – Make it clear in the PAR • In our case it speaks in particular to 802. 1 x that influences the pre and post authentication flow of data through a MAC Submission 6 David Johnston, Intel

July. 2003 doc. : 00 -03 -0026 -00 -0000 Handoff_Par_Discussion Scope Intent • “Consideration will be made to ensure that compatibility is maintained with 802 security mechanisms including 802. 1 x. Neither security algorithms nor security protocols shall be defined in the specification. ” – Here we address security issues – Specifically call out consideration 802. 1 x. We are cognizant of intersections with 802. 1 x as a result of our study work. – We are not defining new security protocols – We are not defining new security algorithms • To do combined secure-handoff across heterogeneous media would be a huge task that is unlikely to complete and is likely to overlap with work ongoing elsewhere (linksec, 802. 1 aa, IETF etc) Submission 7 David Johnston, Intel

July. 2003 doc. : 00 -03 -0026 -00 -0000 Handoff_Par_Discussion Proposed PAR - Scope 12. Scope of Proposed Project: The scope of this project is to develop a standard that shall define mechanisms that may be adopted into 802 implementations so that handoff of handoff-capable upper layer entities, e. g. Mobile. IP sessions, can be optimized between homogeneous or heterogeneous 802 media types both wired and wireless, where handoff is not otherwise defined. Consideration will be made to ensure compatibility with the 802 architectural model. Consideration will be made to ensure that compatibility is maintained with 802 security mechanisms including 802. 1 x. Neither security algorithms nor security protocols shall be defined in the specification. Submission 8 David Johnston, Intel

July. 2003 doc. : 00 -03 -0026 -00 -0000 Handoff_Par_Discussion Purpose Intent • “The purpose of the project is to • a) facilitate the optimization of handoff between 802 networks that may be of different media types both wired and wireless, where 802 level handoff is not otherwise defined. . . ” – We are an optimization spec. Not a handoff spec – The handoff must be there already Submission 9 David Johnston, Intel

July. 2003 doc. : 00 -03 -0026 -00 -0000 Handoff_Par_Discussion Purpose Intent • “b) to make it possible for mobile devices to perform seamless handoff where the network environment supports it. . . ” – Seamless handoff (as in smooth and fast) is the end goal. But it is not universally available since the network interfaces may have features that inhibit seamless handoff. – So do not promise the impossible Submission 10 David Johnston, Intel

July. 2003 doc. : 00 -03 -0026 -00 -0000 Handoff_Par_Discussion Purpose Intent • “This will improve the user experience of mobile devices by improving the available continuous network coverage through the support of multiple media types and preventing the interruption of upper layer sessions during handoff. ” – The end goal is improvement of user experience through greater continuity of not only connectivity, but the sessions operating over that connectivity Submission 11 David Johnston, Intel

July. 2003 doc. : 00 -03 -0026 -00 -0000 Handoff_Par_Discussion Proposed PAR - purpose 13. Purpose of Proposed Project: The purpose of the project is to a) facilitate the optimization of handoff between 802 networks that may be of different media types both wired and wireless, where 802 level handoff is not otherwise defined b) to make it possible for mobile devices to perform seamless handoff where the network environment supports it. This will improve the user experience of mobile devices by improving the available network coverage through the support of multiple media types and preventing the interruption of upper layer sessions during handoff. Submission 12 David Johnston, Intel