Network Working Group F. Xia Internet-Draft B. Sarikaya Expires: April 22, 2010 Huawei USA October 19, 2009 Home Agent Initiated Flow Binding for Mobile IPv6 draft-xia-mext-ha-init-flow-binding-01 Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on April 22, 2010. Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Xia & Sarikaya Expires April 22, 2010 [Page 1] Internet-Draft HA Initiated Flow Binding for Mobile IPv6 October 2009 Abstract There are scenarios in which home agent initiated flow binding operations towards the mobile node is needed such as revoking a flow binding or moving a flow from one interface to another because of network resource availability. This document defines two new Mobility Headers and three new options to perform home agent initiated interactions for flow bindings in a mobile node. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.1. Default Flow Binding Provisioning . . . . . . . . . . . . 3 3.2. Flow Binding Revocation . . . . . . . . . . . . . . . . . 4 3.3. Inter-Interface Flow Binding Movement . . . . . . . . . . 4 4. Protocol Operation . . . . . . . . . . . . . . . . . . . . . . 4 4.1. Adding flow bindings . . . . . . . . . . . . . . . . . . . 4 4.2. Deleting flow bindings . . . . . . . . . . . . . . . . . . 5 4.3. Modifying flow bindings . . . . . . . . . . . . . . . . . 5 4.4. Refreshing flow bindings . . . . . . . . . . . . . . . . . 5 4.5. Moving flow bindings . . . . . . . . . . . . . . . . . . . 5 4.6. Switching flow bindings . . . . . . . . . . . . . . . . . 5 4.7. Acknowledging flow bindings . . . . . . . . . . . . . . . 6 4.8. Handling of the Flow Bindings List . . . . . . . . . . . . 6 5. Flow Binding Messages and Options . . . . . . . . . . . . . . 7 5.1. Mobility Header . . . . . . . . . . . . . . . . . . . . . 7 5.1.1. Flow Binding Indication . . . . . . . . . . . . . . . 7 5.1.2. Flow Binding Acknowledgement . . . . . . . . . . . . . 9 5.2. New Options . . . . . . . . . . . . . . . . . . . . . . . 10 5.2.1. Flow Attribute Option . . . . . . . . . . . . . . . . 10 5.2.2. Alternate Home Agent sub-option . . . . . . . . . . . 11 5.2.3. Target Care-of-Address sub-option . . . . . . . . . . 12 6. Security Considerations . . . . . . . . . . . . . . . . . . . 13 7. IANA considerations . . . . . . . . . . . . . . . . . . . . . 13 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 9.1. Normative References . . . . . . . . . . . . . . . . . . . 13 9.2. Informative references . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15 Xia & Sarikaya Expires April 22, 2010 [Page 2] Internet-Draft HA Initiated Flow Binding for Mobile IPv6 October 2009 1. Introduction [I-D.ietf-mext-flow-binding] allows a mobile node to bind a particular flow to a care-of address without affecting other flows using the same home address. Binding Update (BU)/Binding Acknowledgement(BA) messages are extended for the mobile node to add, modify, remove and refresh flow binding in a home agent. The operations are always initiated by the mobile node. In some cases, the home agent would like to initiate flow binding operations. e.g, the home agent revokes a flow binding for reasons such as accounting insufficiency of the mobile node; for the mobile node equipped with multiple interfaces, the home agent moves a flow binding from one interface to another based on network resource availability; the home agent provisions default flow binding rules to the mobile node based on the mobile node's default profile. This document defines two new Mobility Headers for the home agent to control flow binding in the mobile node. 2. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. The terminology in this document is based on the definitions in [RFC3775] and [I-D.ietf-mext-flow-binding]. 3. Use Cases 3.1. Default Flow Binding Provisioning Michael purchases a dual mode phone equipped with both 3GPP and WiFi interfaces. He also signs a Service Level Agreement(SLA) with an operator including the following information: o 3GPP access takes priority over WiFi access when providing Voice- over-IP (VoIP) service. That is, the 3GPP network is always used when Michael makes a call if the network is accessible. o WiFi access is primarily selected to serve IPTV service. o Peer-to-peer (p2p) download is only allowed through WiFi access. Michael's default profile can be downloaded from AAA server through the home agent to its mobile node when registering. Xia & Sarikaya Expires April 22, 2010 [Page 3] Internet-Draft HA Initiated Flow Binding for Mobile IPv6 October 2009 3.2. Flow Binding Revocation The operator also provides a package to Michael, for example, unlimited call and 8 hours of free Video on Demand (VoD). Michael is a movie fan, and every month he uses up all the 8 hours. The operator has no choice but cutting his ongoing VoD while still providing unlimited call service. 3.3. Inter-Interface Flow Binding Movement Michael stays home using WLAN access for call and downloading. However, the operator does its routine maintenance of its WiFi devices. The operator then moves all the calls and downloading to its 3GPP interface. Once the maintenance is over, the operator then moves back the service. 4. Protocol Operation [I-D.ietf-mext-flow-binding] makes use of Binding Update (BU) /Binding Acknowledgement(BA) signalling to add, modify, remove and refresh flow binding in a home agent. That is, flow binding operations are always initiated from the mobile node. The mechanism specified in this document is complementary to the method described in [I-D.ietf-mext-flow-binding]. It is assumed that the home agent has already created Binding Cache entries for the mobile node before launching flow binding operations. In this document, two new Mobility Headers are defined, that is, Flow Binding Indication(FBI) Section 5.1.1 and Flow Binding Acknowledgement(FBA)Section 5.1.2. FBI is used by the home agent to initiate flow binding operations, while FBA is used for acknowledging FBI. 4.1. Adding flow bindings Adding the flow binding implies associating a flow with a particular care-of address for the mobile node. The care-of address concerned with the flow binding is present in the destination address of the packet or the alternate care-of address option. Alternatively, the care-of address may be indicated by the Binding Identification number (BID) described in [RFC5648] which is pointing to an existing care-of address, and the BID is included in the Binding Reference sub-option of the Flow Attribute option defined in Section 5.2.1. When adding a new flow binding, the home agent sends a FBI with a Flow Attribute option to the mobile node. The Flow Attribute option includes a unique Flow Identifier (FID). The PRO field of the option Xia & Sarikaya Expires April 22, 2010 [Page 4] Internet-Draft HA Initiated Flow Binding for Mobile IPv6 October 2009 MUST indicate an Add operation. The FID needs only be unique for the receiver of the message that adds a flow, i.e. the same FID can be used across different receivers of the message. A lifetime value is included to indicate the remaining lifetime of the flow binding. 4.2. Deleting flow bindings When removing a flow binding, the home agent node sends a FBI with a Flow Attribute option which PRO field indicates Delete operation. The Flow Attribute option includes a unique FID for the mobile node to locate the flow binding and remove it. 4.3. Modifying flow bindings When modifying a flow binding (either the care-of address or other attributes of the flow), the home agent sends the mobile node a FBI message with Flow Attribute option. The option includes the FID for the binding being modified. A Flow Description Option may come with the Flow Attribute Option and contain the new attributes needed to classify the flow such as in [I-D.ietf-mext-binary-ts]. Hence, flow modification is essentially a process where an existing flow definition is removed and a new flow (included in the option) is added and given the same FID as the flow that was removed. 4.4. Refreshing flow bindings A flow binding is refreshed by simply including the Flow Attribute option with Refresh PRO field in the FBI message. The message should be sent before the expiration of the flow binding. The message updates existing bindings with new information. Hence, all information previously sent in the last refreshing message need to be resent, otherwise such information will be lost. 4.5. Moving flow bindings The home agent can move a flow associated to one interface of the multi-interfaced mobile node to another by sending a FBI message to the mobile node. A Flow Attribute option whose PRO field is set to Move is included. The address of the target interface is also included in the Flow Attribute option. 4.6. Switching flow bindings Here are some example scenarios where a home agent signal to the mobile node that it should acquire a new home agent for some specific flows: Xia & Sarikaya Expires April 22, 2010 [Page 5] Internet-Draft HA Initiated Flow Binding for Mobile IPv6 October 2009 o The home agent is overloaded. o An operator may wish to balance the load among home agents. o Operators do periodic maintenance in order to maintain reliability. o Some other scenarios. The home agent sends the mobile node a FBI with Flow Attribute Option to indicate that the mobile node should bind a flow to a new home agent. The alternative home agent addresses are included for the mobile node to initiate the flow binding to a new home agent. 4.7. Acknowledging flow bindings The mobile node sends FBA message to acknowledge the reception of FBI to Add, Delete, Modify, Refresh, Move, or Switch a flow binding. On receiving messages with Flow Attribute Option(s), the mobile node should copy each Flow Attribute Option to the Acknowledgement messages. 4.8. Handling of the Flow Bindings List Flow bindings list defined in [I-D.ietf-mext-flow-binding] needs to be modified after each protocol operation defined above as follows: If FBI contains a flow binding add operation and if the corresponding FBA has a status code equal to zero, home agent MUST add a new entry to the flow bindings list. FID, Flow Descriptor, FID-PRI and Action fields are taken from the Flow Attribute Option. BID is copied from the Binding Reference sub-option. Active/Inactive Flag is set to Active. Note that if BID is not available it may be replaced by Care-of-Address. If FBI contains a flow binding delete operation and if the corresponding FBA has a status code equal to zero, home agent MUST locate the list entry corresponding to this flow and then delete the entry. If FBI contains a flow binding modify operation and if the corresponding FBA has a status code equal to zero, home agent MUST delete the list entry corresponding to this flow and then add a new entry setting the values as defined in the Flow Attribute Option. If FBI contains a flow binding refresh operation and if the corresponding FBA has a status code equal to zero, home agent MUST locate the list entry corresponding to this flow and then set Active/ Inactive Flag to Active. If FBI contains a flow binding move operation and if the Xia & Sarikaya Expires April 22, 2010 [Page 6] Internet-Draft HA Initiated Flow Binding for Mobile IPv6 October 2009 corresponding FBA has a status code equal to zero, home agent MUST locate the list entry corresponding to this flow and then change the BID value to the Care-of-Address in Flow Attribute Option. If FBI contains a flow binding switch operation and if the corresponding FBA has a status code equal to zero, home agent MUST locate the list entry corresponding to this flow and then delete the entry. 5. Flow Binding Messages and Options 5.1. Mobility Header The messages described below follow the Mobility Header format specified in Section 6.1 of [RFC3775]: +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Payload Proto | Header Len | MH Type | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Checksum | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | | . . . Message Data . . . | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 1: Mobility Header 5.1.1. Flow Binding Indication The Flow Binding Indication messages are used by the home agent to initiate flow binding operations to the mobile node. The Flow Binding Indication messages use the MH Type value (IANA-TBD1), and the format of the Message Data field in the Mobility Header is as follows: Xia & Sarikaya Expires April 22, 2010 [Page 7] Internet-Draft HA Initiated Flow Binding for Mobile IPv6 October 2009 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Sequence # | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Trigger |A| Reserved | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | | . . . Mobility options . | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 2: Flow Binding Indication Message Type Sequence # A 16-bit unsigned integer used by the home agent to match a returned Flow Binding Acknowledgement with this Flow Binding Indication. It could be a random number. Trigger 8-bit unsigned integer indicating the event which triggered the home agent to send the Flow Binding Indication message. The following Revocation Trigger values are currently defined: 0 Reserved 1 Unspecified 2 Administrative Reason 3 Possible Out-of Sync BCE State 250-255 Reserved For Testing Purposes only All other values are Reserved Acknowledge (A) The Acknowledge (A) bit is set by the home agent to request a Flow Binding Acknowledgement be returned upon receipt of the Flow Binding Indication. Reserved These fields are unused. They MUST be initialized to zero by the sender and MUST be ignored by the receiver. Mobility Options Variable-length field of such length that the complete Mobility Header is an integer multiple of 8 octets long. Flow Attribute Options defined in this document are included in this field. Xia & Sarikaya Expires April 22, 2010 [Page 8] Internet-Draft HA Initiated Flow Binding for Mobile IPv6 October 2009 5.1.2. Flow Binding Acknowledgement The Flow Binding Acknowledgement is used to acknowledge receipt of a Flow Binding Indication. The Flow Binding Acknowledgement has the MH Type value (IANA-TBD2). When this value is indicated in the MH Type field, the format of the Message Data field in the Mobility Header is as follows: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Sequence # | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Status | Reserved | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | | . . . Mobility options . | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 3: Flow Binding Acknowledgement Message Type Sequence # The sequence number in the Flow Binding Acknowledgement is copied from the Sequence Number field in the Flow Binding Indication. Status 8-bit unsigned integer indicating the result of processing the Flow Binding Indication message by the receiving mobile node. Values of the Status field less than 128 indicate that the Flow Binding Indication was processed successfully by the receiving node. Values greater than or equal to 128 indicate that the Flow Binding Indication was rejected by the receiving node. The following status values are currently defined: 0 success 1 partial success 128 Binding Does NOT Exist All other values are Reserved Mobility Options Variable-length field of such length that the complete Mobility Header is an integer multiple of 8 octets long. This field contains zero or more TLV-encoded mobility options. Flow Attribute Options defined in this document are included in this Xia & Sarikaya Expires April 22, 2010 [Page 9] Internet-Draft HA Initiated Flow Binding for Mobile IPv6 October 2009 field. 5.2. New Options 5.2.1. Flow Attribute Option This is a Mobility Option 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Option Type | Option Len | PRO | PRI | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | FID | Status | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Lifetime | Sub-options | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Flow Description ... ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 4: Flow Attribute Mobility Option Option Type TBD Option Len Length of the option in 8-octet units PRO This is a 4-bit field that describes the required processing for the option. It can be assigned one of the following values: 0 Reserved 1 Add a flow binding 2 Delete a flow binding 3 Modify a flow binding 4 Refresh a flow binding 5 Move a flow binding 6 Switch a flow binding to alternative home agents All other values are reserved PRI This is a 8-bit priority field to indicate the priority of a particular option. This field is needed in cases where two different flow descriptions in two different options overlap. The priority field decides which policy should be in those cases. A Xia & Sarikaya Expires April 22, 2010 [Page 10] Internet-Draft HA Initiated Flow Binding for Mobile IPv6 October 2009 lower number in this field indicates a higher priority. FID The Flow Identifier field is an 16-bit unsigned integer that includes the identifier for the flow binding. This field is used to refer to an existing binding or to create a new binding. Status This field indicates the success or failure of the flow binding operation for the particular flow in the option. Values from 0 to 127 indicate success; Values of 128 and higher indicate failure. This field is only relevant when included in the Flow Binding Acknowledgement message and must be ignored in the Flow Binding Indication message. Reserved This field is unused. It MUST be initialized to zero by the sender and MUST be ignored by the receiver. Lifetime 16-bit unsigned integer. One time unit is 4 seconds. Except for Delete and Switch processing in which the lifetime field is ignored, the lifetime in other PROs has the following meaning: Add, the time remaining before the flow binding expired Modify, the lifetime of the modified flow binding Refresh, the lifetime of the refreshed flow binding Move, the lifetime of the moved flow binding Sub-options One or more sub-options may be included. These variable length options are defined in later sections. Flow Description Variable length field including attributes defining a flow. 5.2.2. Alternate Home Agent sub-option This section introduces the Alternate Home Agent sub-option, which may be included in the Flow Attribute option. This sub-option is used to indicate the mobile node to switch a flow binding from one home agent to another. Xia & Sarikaya Expires April 22, 2010 [Page 11] Internet-Draft HA Initiated Flow Binding for Mobile IPv6 October 2009 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Option Type | Option Len | # of Addresses| Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Home Agent Addresses | . . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 5: Alternate Home Agent Sub-option Option Type TBD Option Len Length of option in 8-octet units # of Addresses The number of home agent addresses in this option. Reserved This field is unused. It MUST be initialized to zero by the sender and MUST be ignored by the receiver. Home Agent Addresses Alternative home agent addresses to which the mobile node is going to switch its flow bindings. 5.2.3. Target Care-of-Address sub-option This section introduces the Target Care-of-Address, which may be included in the Flow Attribute Option. This sub-option is used to indicate the mobile node to move a flow binding from one interface to another. 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Option Type | Option Len | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Target Care-of-Address | . . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Xia & Sarikaya Expires April 22, 2010 [Page 12] Internet-Draft HA Initiated Flow Binding for Mobile IPv6 October 2009 Figure 6: Target Care-of-Address Sub-option Option Type TBD Option Len Length of option in 8-octet units Reserved This field is unused. It MUST be initialized to zero by the sender and MUST be ignored by the receiver. Target Care-of-Address The address of an interface that the flow is moved to. 6. Security Considerations TBD. 7. IANA considerations TBD. 8. Acknowledgements TBD. 9. References 9.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008. [RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in IPv6", RFC 3775, June 2004. [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless Address Autoconfiguration", RFC 4862, September 2007. Xia & Sarikaya Expires April 22, 2010 [Page 13] Internet-Draft HA Initiated Flow Binding for Mobile IPv6 October 2009 [RFC0792] Postel, J., "Internet Control Message Protocol", STD 5, RFC 792, September 1981. [RFC4443] Conta, A., Deering, S., and M. Gupta, "Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification", RFC 4443, March 2006. 9.2. Informative references [I-D.ietf-mext-flow-binding] Soliman, H., Montavont, N., and K. Kuladinithi, "Flow Bindings in Mobile IPv6 and NEMO Basic Support", draft-ietf-mext-flow-binding-03 (work in progress), July 2009. [I-D.ietf-mext-generic-signaling-message] Haley, B. and S. Gundavelli, "Mobile IPv6 Generic Signaling Message", draft-ietf-mext-generic-signaling-message-00 (work in progress), August 2008. [I-D.ietf-mext-binding-revocation] Muhanna, A., Khalil, M., Gundavelli, S., Chowdhury, K., and P. Yegani, "Binding Revocation for IPv6 Mobility", draft-ietf-mext-binding-revocation-13 (work in progress), September 2009. [I-D.ietf-mext-nemo-v4traversal] Soliman, H., "Mobile IPv6 Support for Dual Stack Hosts and Routers", draft-ietf-mext-nemo-v4traversal-10 (work in progress), April 2009. [RFC5648] Wakikawa, R., Devarapalli, V., Tsirtsis, G., Ernst, T., and K. Nagami, "Multiple Care-of Addresses Registration", RFC 5648, October 2009. [I-D.ietf-mext-binary-ts] Tsirtsis, G., Giaretta, G., Soliman, H., and N. Montavont, "Binary Traffic Selectors for FB", draft-ietf-mext-binary-ts-00 (work in progress), July 2009. Xia & Sarikaya Expires April 22, 2010 [Page 14] Internet-Draft HA Initiated Flow Binding for Mobile IPv6 October 2009 Authors' Addresses Frank Xia Huawei USA 1700 Alma Dr. Suite 500 Plano, TX 75075 Phone: +1 972-509-5599 Email: xiayangsong@huawei.com Behcet Sarikaya Huawei USA 1700 Alma Dr. Suite 500 Plano, TX 75075 Phone: +1 972-509-5599 Email: sarikaya@ieee.org Xia & Sarikaya Expires April 22, 2010 [Page 15]