Context and Micro-mobility Routing WG (seamoby) Wednesday, December 13 at 1530-1730 =================================== CHAIRS: Pat Calhoun Phil Neumiller DESCRIPTION: There are a large number of IP access networks that support mobility of hosts. For example, wireless Personal Area Netwoks (PANs) and LANs, satellite and cellular WANs. The nature of this roaming is such that the communication path to the host changes frequently, and rapidly. In many situations, the change of communications path includes a change in communications media between the host and access networking, incuding changes from a wireless to a wired connection. To support these changes, there is a need for support in the access network to actively re-direct the IP packet flows, while preserving the context of all active IP flows. The IP flow context includes, but is not limited to security, policy, QOS, congestion indication/management, header compression and accounting. The SeaMoby Working Group will develop a protocol to provide fast mobility within an access network, and thereby reduce the latency of the data/traffic flow to/from the mobile node during intra- and inter-domain handoffs, across heterogeneous network access infrastructure. This work is typically known as Micro-Mobility, where specialized signalling is used in an Administrative Domain to support the movement of IP nodes across IP subnets. The SeaMoby Working Group will also develop a protocol that is used to transfer the context information for a session from a mobile's old access point to the new access point. The context information to be transfered includes QOS, header compression state, policy, etc. Transferring the context state is expected to provide a seamless handoff to the user, and applications. Lastly, the Working Group will investigate the use of paging at the IP layer in networks, and if it is deemed necessary, a protocol will be developed to tackle this problem. IP paging is typically used in Micro-Mobility protocols to quickly track a mobile that has moved from its previously know point of attachment, while in dormant mode. This is in no way the same as Instant Messaging, since its purpose is to setup the routing path necessary to forward packets to the mobile. All work produced by the Working Group will support both IPv4 and IPv6, will be congestion friendly, and will undergo a security review prior to WG last call. The Working Group will coordinate closely with the aaa, cnrp, impp, mobileip, pilc, and rohc WGs. AGENDA: 1. Agenda Bashing (charis) - 3 minutes 2. Ground Rules (chairs) - 5 minutes 3. Milestone Review (chairs) - 5 minutes 4. Strategy on achieving our agressive milestones (chairs) - 40 minutes (e.g. interim meeting, design teams) 5. SeaMoby Concerns (ietf-loughney-seamoby-concerns-00.txt) - 10 minutes (john.loughney@nokia.com) 6. Header Compression State Relocation Design Considerations - 10 minutes (charliep@iprg.nokia.com) 7. Cellular IP - Some Micro-Mobility requirements for v4 - 10 Minutes (campbell@comet.columbia.edu) 8. Cellular IPv6 - Some Micro-Mobility Requirements for v6 - 10 minutes (zach.shelby@vtt.fi) 9. State transfer between Access Routes during Handoff - 10 minutes (alan.w.oneill@bt.com) 10. Buffer Management for Smooth Handovers - Requirements - 10 minutes (charliep@iprg.nokia.com)