Flow bindings in MIPv6 and NEMO draft-soliman-monami-flow-binding-00

1
Flow bindings in MIPv6 and NEMOdraft-soliman-mona
mi-flow-binding-00
2
Why is Flow binding needed?

• Different access technologies have different
  capabilities, capacities, cost, use cases, QoS,
  and security.
• Applications may run more efficiently on one
  access technology than others (e.g. VoIP needs
  QoS capabilities in the radio access, FTP
  doesnt).
• Different access technologies may be available
  through different IP subnets.
• MNs should be able to maximise the utilization
  of the available access technologies.
• MIPv6 does not allow a MN to allocate different
  CoAs to different flows.

3
What is a Flow?

• A flow is a sequence of packets sent from a
  particular source to a particular (unicast or
  multicast) destination.
• An IPv6 Flow can be uniquely identified using
• Src, dst addresses, port numbers, and proto.
• Src, dst addresses and Flow Label
• Src, dst addresses and SPI (for IPsec protected
  packets)
• Traffic Class field with any of the above

4
Flow Identification Option

• Included in BU and BA messages
• Modular format

5
Flow identification option

• Add/modify/remove flows
• Must identify a default address
• Must use the right keygen token to authenticate
  the BU when sending to CNs

6
Scenarios
Home Network
MAP
AR
AR
Access technology A
Access Technology B
MobileNode (MN)
7
Scenarios
CorrespondentNode (CN)
HomeAgent
Home Network
AR
AR
Access technology A
Access Technology B
MobileNode (MN)
8
Issues to be addressed

• Need comments from the WG
• Support for MRs
• Issues with MIPv6 transition work?
• Security issues ?