Flow bindings in MIPv 6 and NEMO draftietfmextflowbinding00

Flow bindings in MIPv 6 and NEMO draft-ietf-mext-flow-binding-00 Hesham Soliman Nicolas Montavont Nicolaus Fikouras Koojana Kuladinithi 1

History of the document • • • Work started in Mobile IP (2000) Moved to MIP 6 Moved to monami 6 (merged three drafts into the current draft) Monami 6 WG doc (2007) MEXT WG doc (2008) 2

Why is Flow binding needed? • Applications may run more efficiently on one access technology than others (e. g. Vo. IP needs Qo. S capabilities in the radio access, FTP doesn’t). • Different access technologies may be available through different IP subnets => different interfaces on a host. • MIPv 6 does not allow a MN to allocate different Co. As to different flows. • Flow bindings allow the MN to associate flows to different Co. As for optimal utilisation of available interfaces. • Flow bindings as MIPv 6 extensions allow the MN to split flows from HA/CN/MAP, for flows initiated or terminated by MN. • Flow bindings in MIPv 6 are independent of application capability (i. e. whether session control is present or not). 3

How it works • Policy => Rule => Transport • MN needs to be configured with a Policy that allows it to choose the best interface for a flow, e. g. : – port 80 eth 0 – Voiceapp en 1 – Default eth 0 • When a new connection is established, the MN matches the flow information against the policy. • Based on the match, the MN creates a Rule and informs the HA/CN/MAP of the right Co. A for the particular flow. • Informing the HA/MAP/CN is done using the BU including the flow option, which describes the flow • This draft only describes the transport part of the problem 4

Scenarios Correspondent Node (CN) Home Network Correspondent Node (CN) Home Agent Correspondent Node (CN) MAP AR AR Access technology A Access Technology B Mobile Node (MN) 5

Scenarios Correspondent Node (CN) Home Network Home Agent AR AR Access technology A Access Technology B Mobile Node (MN) 6

Issues addressed in this revision • Separated out the flow description from the draft to be done separately in draft-larsson as agreed in monami 6 and MEXT • Incorporated MCo. A for more efficient bulk registration • Several editorials • Draft supports hosts and routers 7