draft-ietf-mext-flow-binding-10.txt   draft-ietf-mext-flow-binding-11.txt 
IETF MEXT Working Group G. Tsirtsis IETF MEXT Working Group G. Tsirtsis
Internet-Draft Qualcomm Internet-Draft Qualcomm
Updates: 5648 (if approved) H. Soliman Updates: 5648 (if approved) H. Soliman
Intended status: Standards Track Elevate Technologies Intended status: Standards Track Elevate Technologies
Expires: March 18, 2011 N. Montavont Expires: April 8, 2011 N. Montavont
IT/TB IT/TB
G. Giaretta G. Giaretta
Qualcomm Qualcomm
K. Kuladinithi K. Kuladinithi
University of Bremen University of Bremen
September 14, 2010 October 5, 2010
Flow Bindings in Mobile IPv6 and NEMO Basic Support Flow Bindings in Mobile IPv6 and NEMO Basic Support
draft-ietf-mext-flow-binding-10.txt draft-ietf-mext-flow-binding-11.txt
Abstract Abstract
This document introduces extensions to Mobile IPv6 that allow nodes This document introduces extensions to Mobile IPv6 that allow nodes
to bind one or more flows to a care-of address. These extensions to bind one or more flows to a care-of address. These extensions
allow multihomed nodes to instruct home agents and other Mobile IPv6 allow multihomed nodes to instruct home agents and other Mobile IPv6
entities to direct inbound flows to specific addresses. entities to direct inbound flows to specific addresses.
Status of this Memo Status of this Memo
skipping to change at page 1, line 40 skipping to change at page 1, line 40
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 18, 2011. This Internet-Draft will expire on April 8, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 5, line 34 skipping to change at page 5, line 34
bind a particular flow to a care-of address without affecting other bind a particular flow to a care-of address without affecting other
flows using the same home address. In addition, this specification flows using the same home address. In addition, this specification
allows to bind a particular flow to a particular care-of address allows to bind a particular flow to a particular care-of address
directly with correspondent node and mobility agents (i.e., home directly with correspondent node and mobility agents (i.e., home
agents [RFC3775] and mobility anchor points [RFC5380]). agents [RFC3775] and mobility anchor points [RFC5380]).
In this document, a flow is defined as a set of IP packets matching a In this document, a flow is defined as a set of IP packets matching a
traffic selector. A traffic selector can identify the source and traffic selector. A traffic selector can identify the source and
destination IP addresses, transport protocol number, the source and destination IP addresses, transport protocol number, the source and
destination port numbers and other fields in IP and higher layer destination port numbers and other fields in IP and higher layer
headers. This specification, however, does not define traffic di headers. This specification, does not define traffic selectors,
going to be defined in other specifications. This specification, which are going to be defined in other specifications. This
however, does define the traffic selector sub-option format to be specification, however, does define the traffic selector sub-option
used for any specific traffic selectors. format to be used for any specific traffic selector.
Using the flow identifier option introduced in this specification a Using the flow identifier option introduced in this specification a
mobile node / mobile router can bind one or more flows to a care-of mobile node / mobile router can bind one or more flows to a care-of
address while maintaining the reception of other flows on another address while maintaining the reception of other flows on another
care-of address. The mobile node / mobile router assembles the flow care-of address. The mobile node / mobile router assembles the flow
binding requests based on local policies, link characteristics and binding requests based on local policies, link characteristics and
the types of applications running at the time. Such policies are the types of applications running at the time. Such policies are
outside the scope of this document. outside the scope of this document.
It should be noted that the flow identification mobility option can It should be noted that the flow identification mobility option can
 End of changes. 5 change blocks. 
8 lines changed or deleted 8 lines changed or added

This html diff was produced by rfcdiff 1.39. The latest version is available from http://tools.ietf.org/tools/rfcdiff/