Service Flow Identifier in Proxy Mobile IPv6 draft-hui-netext-service-flow- identifier-03

Abstract This document proposes extensions to PMIP6 that – Allows flow identification and binding during the flow mobility – Enable PMIP tunnels set up based on the service flow granularity between a pair of LMA/MAG Therefore, multiple service flows of the MN can be separately controlled, e.g. Qos, charging, traffic control.

Problem Status What’s the requirement? – For different services, we want to have different charging rate, service quality, and latency. E.g. User can bear some latency of the streaming TV, but require a high quality of voice service. What’s the status? – Currently, there is single PMIP tunnel between a pair of LMA/MAG It’s no difference in the tunnel for multiple services Service-differ control can not be achieved based on the tunnel

Protocol Operation When a new service flow of the mobile node is started, it will trigger the service flow proxy binding update MAG sends the PBU message to LMA including the service flow identifier option and the assigned downlink GRE Key for this SF. LMA will generate the uplink GRE key and return a PBA message. The new bi-directional tunnel for this specific service is set up

Message Formats Service Flow Identifier option – included in the PBU/PBA – Service Flow Identifier A 16-bit unsigned integer, including the unique identifier within the LMA for the service flow of the mobile node. However, its length can also be implementation dependent. – Service Flow Description option The detailed binary encoding of the service flow description field could follow the defined binary traffic selector in draft- ietf-mext-binary-ts Or the new traffic selector can be defined

Scenario SFID is used to identify the service flow SFID can enable the flow binding Refer to a SFID, there is a unique PMIP tunnle SFID is unique in one LMA

New Work Item