1. unrestricted Connection manager MIF WG IETF 78, Maastricht 2010-07-29 Gaëtan Feige, Cisco (presenter) gfeige@cisco.com Pierrick Seïté, France Telecom - Orange pierrick.seite@orange-ftgroup.com gfeige@cisco.com pierrick.seite@orange-ftgroup.com

2. unrestricted Context  Connection manager is a key feature for MIF host –The CM deals with some of the MIF issues (e.g. "smart" domain selection, source address selection) => optimize ressource usage and Quality of Eperience for end-user –Make a decision on various criteria (application requirement, user preferences, operator policies, available QoS,….)  draft-ietf-mif-problem-statement stressed that Lack of standardization leads to specific issues –Connections manager exists but behave in different ways –Implementation of different connection managers on a same host –We may need more criteria for an appropriate selection  The I-D list requirements and gives functional description for a generic connection manager

3. unrestricted Possible scope for the work item  draft-seite-mif-connection-manager lists functions, interfaces and proposes a functional architecture for the connection manager draft-seite-mif-connection-manager –Can apply to control of virtual interface ( e.g the one defined in NETEXT)

4. unrestricted Functions of the connection manager Initiation monitors for events (access link measurement, application hints, user triggers, etc… ) and trigger the decision function Decision makes path selection depending on trigger/measurement and selection criteria (user preferences, operator policies, access link Qos,…) Execution attachment to a new interface IP connectivity check steer the mobility protocol if needed …

5. unrestricted Interfaces of the connection manager  Network: relates to features directly integrated with the link layer access technologies and network interface –Access monitoring,  Interface with terminal Operating system –Notification/information of IP address network assignment. Information are needed for the control of virtual interfaces and source address selection mechanisms. –Energy status triggers …  Interface between the client and network/cloud operator –Policy provisioning  Interface with applications –Allows the CM to fetch application triggers and interact with applications  Interface with "Execution" mechanisms – command actions on connectivity layers (e.g., IP configuration, IP connectivity check, Virtual interface control, trigger IP session continuity management protocols,….)  Interface with authentication framework –access to all supported authentication protocols in a shared fashion for all interfaces

6. unrestricted Conclusion  The WG could give a framework for generic connection manager –Requirements, functional description, API –The purpose is not to define the « Decision Algorythms » but just to specify which required / minimum IE ( Information Elements ), function calls are needed for each interface  The purpose is not to duplicate work existing in other SDO but to state the dependencies to them  Include requirements/specifications for connection manager as a work item ?