< draft-hui-netext-service-flow-identifier-02.txt		draft-hui-netext-service-flow-identifier-03.txt >
	Internet Area M.Hui		Internet Area M.Hui
	Internet Draft G.Chen		Internet Draft G.Chen
	Intended status: Informational H.Deng		Intended status: Informational H.Deng
	China Mobile		China Mobile
	Expires: September 08, 2010 March 08, 2010		Expires: Jan 01, 2011 July 01, 2010
	Service Flow Identifier in Proxy Mobile IPv6		Service Flow Identifier in Proxy Mobile IPv6
	draft-hui-netext-service-flow-identifier-02.txt		draft-hui-netext-service-flow-identifier-03.txt
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with the		This Internet-Draft is submitted to IETF in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as Internet-Drafts.		other groups may also distribute working documents as Internet-Drafts.
	skipping to change at page 1, line 31 ¶		skipping to change at page 1, line 31 ¶
	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."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt		http://www.ietf.org/ietf/1id-abstracts.txt
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html		http://www.ietf.org/shadow.html
	This Internet-Draft will expire on September 2010.		This Internet-Draft will expire on Jan 2011.
	Copyright Notice		Copyright Notice
	Copyright (c) 2009 IETF Trust and the persons identified as the		Copyright (c) 2009 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 Provisions		This document is subject to BCP 78 and the IETF Trust's Legal Provisions
	Relating to IETF Documents (http://trustee.ietf.org/license-info)		Relating to IETF Documents (http://trustee.ietf.org/license-info)
	in effect on the date of publication of this document. Please		in effect on the date of publication of this document. Please
	review these documents carefully, as they describe your rights and		review these documents carefully, as they describe your rights and
	skipping to change at page 3, line 13 ¶		skipping to change at page 3, line 13 ¶
	mobility among multiple interfaces of the mobile node.		mobility among multiple interfaces of the mobile node.
	Table of Contents		Table of Contents
	1. Introduction ................................................ 4		1. Introduction ................................................ 4
	2. Protocol Operation .......................................... 5		2. Protocol Operation .......................................... 5
	3. Message Formats ............................................. 7		3. Message Formats ............................................. 7
	3.1. Service Flow Identifier option .......................... 7		3.1. Service Flow Identifier option .......................... 7
	3.2. Service Flow Description option ......................... 8		3.2. Service Flow Description option ......................... 8
	4. Scenario ................................................... 10		4. Scenario ................................................... 10
	5. Mobility Access Gateway Operation ........................... 12		5. Mobility Access Gateway Operation .......... 12
	5.1. Binding Update List extensions ......................... 12		5.1. Binding Update List extensions ......................... 12
	5.2. Service Flow Proxy Binding Update Operation ............ 12		5.2. Service Flow Proxy Binding Update Operation ............ 12
	5.3. Data Forwarding Rules .................................. 12		5.3. Data Forwarding Rules.................................. 12
	6. Local Mobility Anchor Operation ............................. 14		6. Local Mobility Anchor Operation ............................. 14
	6.1. Binding Cache extensions ............................... 14		6.1. Binding Cache extensions ............................... 14
	6.2. Service Flow Proxy Binding Acknowledge Operation ........ 14		6.2. Service Flow Proxy Binding Acknowledge Operation........ 14
	6.3. Data Forwarding Considerations ......................... 14		6.3. Data Forwarding Considerations ......................... 14
	7. Security Considerations ..................................... 16		7. Security Considerations..................................... 16
	8. IANA Considerations ........................................ 17		8. IANA Considerations ........................................ 17
	9. References ................................................. 18		9. References ................................................. 18
	9.1. Normative References ................................... 18		9.1. Normative References................................... 18
	9.2. Informative References ................................. 18		9.2. Informative References................................. 18
	Author's Addresses ............................................ 19		Author's Addresses ............................................ 19
	1. Introduction		1. Introduction
	Proxy Mobile IPv6 is a network based local mobility management		Proxy Mobile IPv6 is a network based local mobility management
	protocol which binds the home network prefix(es) assigned to a given		protocol which binds the home network prefix(es) assigned to a given
	interface of a mobile node to its current care-of address (Proxy-CoA).		interface of a mobile node to its current care-of address (Proxy-CoA).
	The mobile access gateway performs the proxy binding update with the		The mobile access gateway performs the proxy binding update with the
	local mobility anchor and does the mobility management on behalf of		local mobility anchor and does the mobility management on behalf of
	the mobile node attached to the network. Details of protocol		the mobile node attached to the network. Details of protocol
	skipping to change at line 330 ¶		skipping to change at page 11, line 4 ¶
	the local mobility anchor with the service flow identifier option and		the local mobility anchor with the service flow identifier option and
	assigned downlink GRE key for this service flow.		assigned downlink GRE key for this service flow.
	O The service flow identifier option for SF1 included in the Proxy		O The service flow identifier option for SF1 included in the Proxy
	Binding Update message is set as follows:		Binding Update message is set as follows:
	Service Flow Identifier field is SFID1=1 and PRO field is 0;		Service Flow Identifier field is SFID1=1 and PRO field is 0;
	The service flow description option included in the service flow		The service flow description option included in the service flow
	identifier option is set as follows: Type field is set to 0,		identifier option is set as follows: Type field is set to 0,
	Hui&Chen&Deng Expire September, 2010 [Page
	10]
	Source Port Range field is set to 49724, and Destination Port		Source Port Range field is set to 49724, and Destination Port
	Range field is set to 56512.		Range field is set to 56512.
	O The service flow identifier option for SF2 included in the Proxy		O The service flow identifier option for SF2 included in the Proxy
	Binding Update message is set as follows:		Binding Update message is set as follows:
	Service Flow Identifier field is SFID2=2 and PRO field is 0;		Service Flow Identifier field is SFID2=2 and PRO field is 0;
	The service flow description option included in the service flow		The service flow description option included in the service flow
	identifier option is set as follows: Type field is set to 0, and		identifier option is set as follows: Type field is set to 0, and
	skipping to change at line 360 ¶		skipping to change at page 12, line 5 ¶
	If the mobile access gateway doesn't receive the data packet of the		If the mobile access gateway doesn't receive the data packet of the
	peer-to-peer voice over IP traffic from the mobile node for a long		peer-to-peer voice over IP traffic from the mobile node for a long
	time, it will send the Proxy Binding Update message to the local		time, it will send the Proxy Binding Update message to the local
	mobility anchor again to delete this service flow binding.		mobility anchor again to delete this service flow binding.
	O The service flow identifier option included in the Proxy Binding		O The service flow identifier option included in the Proxy Binding
	Update message is set as follows: Service Flow Identifier field is		Update message is set as follows: Service Flow Identifier field is
	set to 1, and PRO field is set to 2.		set to 1, and PRO field is set to 2.
	Hui&Chen&Deng Expire September, 2010 [Page
	11]
	5. Mobility Access Gateway Operation		5. Mobility Access Gateway Operation
	5.1. Binding Update List extensions		5.1. Binding Update List extensions
	Service flow binding is conceptually stored in the binding update		Service flow binding is conceptually stored in the binding update
	list entry of the mobile access gateway. To better implement the		list entry of the mobile access gateway. To better implement the
	service flow based control, the original BULE should be extended to		service flow based control, the original BULE should be extended to
	include the following parameters:		include the following parameters:
	O SFID (service flow identifier): A service flow identifier for the		O SFID (service flow identifier): A service flow identifier for the
	skipping to change at line 408 ¶		skipping to change at page 13, line 4 ¶
	5.3. Data Forwarding Rules		5.3. Data Forwarding Rules
	As the service flow binding operation is succeed, the mobile access		As the service flow binding operation is succeed, the mobile access
	gateway and local mobility anchor sets up the bi-directional tunnel,		gateway and local mobility anchor sets up the bi-directional tunnel,
	and assigns downlink and uplink GRE Key for this service flow binding.		and assigns downlink and uplink GRE Key for this service flow binding.
	When the mobile access gateway receives a data packet from the mobile		When the mobile access gateway receives a data packet from the mobile
	node, it MUST check that a service flow binding for the service flow		node, it MUST check that a service flow binding for the service flow
	that the data packet belongs to is created or not. If the bi-		that the data packet belongs to is created or not. If the bi-
	directional tunnel is set up, the mobile access gateway will		directional tunnel is set up, the mobile access gateway will
	Hui&Chen&Deng Expire September, 2010 [Page
	12]
	encapsulate the data packet with the uplink GRE key, and then forward		encapsulate the data packet with the uplink GRE key, and then forward
	it to the mobile node's local mobility anchor.		it to the mobile node's local mobility anchor.
	When the mobile access gateway receives a data packet from the bi-		When the mobile access gateway receives a data packet from the bi-
	direction tunnel established with the local mobility anchor, it will		direction tunnel established with the local mobility anchor, it will
	decapsulate the data packet by removing the outer header, and attains		decapsulate the data packet by removing the outer header, and attains
	the destination address of the inner packet. Then the mobile access		the destination address of the inner packet. Then the mobile access
	gateway will forward it to the mobile node on the interface where the		gateway will forward it to the mobile node on the interface where the
	destination network prefix is hosted.		destination network prefix is hosted.
	Hui&Chen&Deng Expire September, 2010 [Page
	13]
	6. Local Mobility Anchor Operation		6. Local Mobility Anchor Operation
	6.1. Binding Cache extensions		6.1. Binding Cache extensions
	Service flow binding is conceptually stored in the binding cache		Service flow binding is conceptually stored in the binding cache
	entry of the local mobility anchor. To better implement the service		entry of the local mobility anchor. To better implement the service
	flow based control, the original BCE should be extended to include		flow based control, the original BCE should be extended to include
	the following parameters:		the following parameters:
	O SFID (service flow identifier): A service flow identifier for the		O SFID (service flow identifier): A service flow identifier for the
	skipping to change at line 470 ¶		skipping to change at page 15, line 4 ¶
	anchor first checks the service flow identifier field that it needs		anchor first checks the service flow identifier field that it needs
	to contain a value that already exists. Then the local mobility		to contain a value that already exists. Then the local mobility
	anchor will return a Proxy Binding Acknowledge message with the		anchor will return a Proxy Binding Acknowledge message with the
	uplink GRE key and modify or delete the corresponding service flow		uplink GRE key and modify or delete the corresponding service flow
	binding in its binding cache.		binding in its binding cache.
	6.3. Data Forwarding Considerations		6.3. Data Forwarding Considerations
	When the local mobility anchor receives a data packet from a		When the local mobility anchor receives a data packet from a
	correspondent node with the destination address matching a mobile		correspondent node with the destination address matching a mobile
	Hui&Chen&Deng Expire September, 2010 [Page
	14]
	node's home network prefix field, with the source address matching		node's home network prefix field, with the source address matching
	the destination address field, and other attributes matching of the		the destination address field, and other attributes matching of the
	corresponding fields in the binding cache entry, it MUST encapsulate		corresponding fields in the binding cache entry, it MUST encapsulate
	it with the downlink GRE key of this service flow binding, and		it with the downlink GRE key of this service flow binding, and
	forward it to the mobile access gateway through the bi-directional		forward it to the mobile access gateway through the bi-directional
	tunnel.		tunnel.
	When the local mobility anchor receives a data packet from the bi-		When the local mobility anchor receives a data packet from the bi-
	directional tunnel with the mobile access gateway, it MUST		directional tunnel with the mobile access gateway, it MUST
	decapsulate the data packet by removing the outer header. Then it		decapsulate the data packet by removing the outer header. Then it
	will forward the data packet to the destination address of the		will forward the data packet to the destination address of the
	correspondent node in the inner header.		correspondent node in the inner header.
	Hui&Chen&Deng Expire September, 2010 [Page
	15]
	7. Security Considerations		7. Security Considerations
	Since the service flow identifier option is part of the mobility		Since the service flow identifier option is part of the mobility
	option in the proxy binding update and acknowledge message, it uses		option in the proxy binding update and acknowledge message, it uses
	the same security as the proxy binding update operation in RFC 5213.		the same security as the proxy binding update operation in RFC 5213.
	Hui&Chen&Deng Expire September, 2010 [Page
	16]
	8. IANA Considerations		8. IANA Considerations
	This specification defines two new mobility options as in section 2,		This specification defines two new mobility options as in section 2,
	the Service Flow Identifier Option and the Service Flow Description		the Service Flow Identifier Option and the Service Flow Description
	Option.		Option.
	Hui&Chen&Deng Expire September, 2010 [Page
	17]
	9. References		9. References
	9.1. Normative References		9.1. Normative References
	[1] S. Gundavelli, Ed., "Proxy Mobile IPv6", RFC 5213, August 2008.		[1] S. Gundavelli, Ed., "Proxy Mobile IPv6", RFC 5213, August 2008.
	[2] D. Johnson, C. Perkins, and J. Arkko, "Mobility Support in IPv6",		[2] D. Johnson, C. Perkins, and J. Arkko, "Mobility Support in IPv6",
	RFC 3775, June 2004.		RFC 3775, June 2004.
	[3] H. Soliman, Ed., "Flow Bindings in Mobile IPv6 and Nemo Basic		[3] H. Soliman, Ed., "Flow Bindings in Mobile IPv6 and Nemo Basic
	Support", draft-ietf-mext-flow-binding-03, July 2009.		Support", draft-ietf-mext-flow-binding-03, July 2009.
	9.2. Informative References		9.2. Informative References
	[4] G. Wolfner, J. Korhonen, Ed., "Connection Identifier for Proxy		[4] G. Wolfner, J. Korhonen, Ed., "Connection Identifier for Proxy
	Mobile IPv6", draft-wolfner-netext-pmip6-connid-01, October 2009.		Mobile IPv6", draft-wolfner-netext-pmip6-connid-01, October 2009.
	[5] "General Packet Radio Service (GPRS); Service description; Stage 2		[5] "General Packet Radio Service (GPRS); Service description; Stage 2
	Release 9 ", 3GPP TS 23.060, March 2009.		Release 9 ", 3GPP TS 23.060, July 2009.
	[6] "Policy and charging control architecture (Release 9)", 3GPP TS		[6] "Policy and charging control architecture (Release 9)", 3GPP TS
	23.203, March 2009.		23.203, July 2009.
	[7] G. Tsirtsis, Ed., "Binary Traffic Selectors for FB", draft-ietf-		[7] G. Tsirtsis, Ed., "Binary Traffic Selectors for FB", draft-ietf-
	mext-binary-ts-00, July 2009.		mext-binary-ts-00, July 2009.
	Hui&Chen&Deng Expire September, 2010 [Page
	18]
	Author's Addresses		Author's Addresses
	Min Hui		Min Hui
	China Mobile		China Mobile
	53A,Xibianmennei Ave.,		53A,Xibianmennei Ave.,
	Xuanwu District,		Xuanwu District,
	Beijing 100053		Beijing 100053
	China		China
	Email: huimin.cmcc@gmail.com		Email: huimin.cmcc@gmail.com
	skipping to change at line 562 ¶		skipping to change at line 532 ¶
	China		China
	Email: chengang@chinamobile.com		Email: chengang@chinamobile.com
	Hui Deng		Hui Deng
	China Mobile		China Mobile
	53A,Xibianmennei Ave.,		53A,Xibianmennei Ave.,
	Xuanwu District,		Xuanwu District,
	Beijing 100053		Beijing 100053
	China		China
	Email: denghui02@gmail.com		Email: denghui02@gmail.com
	Hui&Chen&Deng Expire September, 2010 [Page
	19]
End of changes. 19 change blocks.
	43 lines changed or deleted		13 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/