< draft-deng-gmmp-00.txt		draft-deng-gmmp-01.txt >
	Network Working Group H. Deng		Network Working Group H. Deng
	Internet-Draft China Mobile		Internet-Draft China Mobile
	Intended status: Standards Track July 1, 2008		Intended status: Standards Track October 30, 2008
	Expires: January 2, 2009		Expires: May 3, 2009
	Generic Mobility Management Protocol		Generic Mobility Management Protocol
	draft-deng-gmmp-00		draft-deng-gmmp-01
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, each author represents that any		By submitting this Internet-Draft, each author represents that any
	applicable patent or other IPR claims of which he or she is aware		applicable patent or other IPR claims of which he or she is aware
	have been or will be disclosed, and any of which he or she becomes		have been or will be disclosed, and any of which he or she becomes
	aware will be disclosed, in accordance with Section 6 of BCP 79.		aware will be disclosed, in accordance with Section 6 of 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
	skipping to change at page 1, line 34 ¶		skipping to change at page 1, line 34 ¶
	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 January 2, 2009.		This Internet-Draft will expire on May 3, 2009.
	Abstract		Abstract
	This document discusses the communication protocol between mobile		This document discusses the communication protocol between mobile
	access point and terminal. With the evolution of mobile		access point and terminal. With the evolution of mobile
	communication, there are various kind of wireless communication		communication, there are various kind of wireless communication
	technologies such as WCDMA, LTE, WLAN, WiMAX, and TDS-CDMA et al.		technologies such as WCDMA, LTE, WLAN, WiMAX, and TDS-CDMA et al.
	Each of these wireless communication technology has independent		Each of these wireless communication technology has independent
	connection, mobility and configuration management. This document		connection, mobility and configuration management. This document
	would like to cover all these functions into a common ground		would like to cover all these functions into a common ground
	skipping to change at page 5, line 4 ¶		skipping to change at page 4, line 45 ¶
	WiMAX, radio y is WLAN and radio z is TDS-CDMA. when terminal make a		WiMAX, radio y is WLAN and radio z is TDS-CDMA. when terminal make a
	movement, wireless connections will also changes, the routing and		movement, wireless connections will also changes, the routing and
	mobility management would better change accordingly.		mobility management would better change accordingly.
	Different service may act independently when terminal has multiple		Different service may act independently when terminal has multiple
	connections. From the service provider point of view, they don't		connections. From the service provider point of view, they don't
	mandate that the application must handover to the second interface		mandate that the application must handover to the second interface
	when it just start up. Some services may keep original connection,		when it just start up. Some services may keep original connection,
	and others may handover to the second interface. This kind of		and others may handover to the second interface. This kind of
	handover could happen both initiated by network or terminal itself.		handover could happen both initiated by network or terminal itself.
			On this purpose, operator normally specify some policy accordingly,
			GMMP could be used for transmiting this policy between AP and
			terminal.
	3. Reference Model		3. Reference Model
	Assuming the name of protocol between terminal and access point is		Assuming the name of protocol between terminal and access point is
	GMMP which would work in the various kind of wireless connections		GMMP which would work in the various kind of wireless connections
	such as GSM, GPRS, WCDMA, LTE, WiFi, and TDS-CDMA et al. After the		such as WCDMA, LTE, WiFi, and TD-SCDMA et al. After the coding of
	coding of each command for connections, mobility, and configuration,		each command for connections, mobility, and configuration, network or
	network or terminal could control each connection and mobility		terminal could control each connection and mobility management based
	management based on a common language like the figure below.		on a common language like the figure below.
	+------+------+------+------+------+-------+		+------+------+------+------+------+-------+
	| GMMP Protocol |		| GMMP Protocol |
	+------+------+------+------+------+-------+		+------+------+------+------+------+-------+
	| GMMP Interface and Payload |		| GMMP Interface and Payload |
	+------+------+------+------+------+-------+		+------+------+------+------+------+-------+
	| Various Kinds of MAC layer and Protocol |		| Various Kinds of MAC layer and Protocol |
	+------+------+------+------+------+-------+		+------+------+------+------+------+-------+
	| WCDMA | LTE | WiFi |TDSCDMA|		| WCDMA | LTE | WiFi | TDSCDMA |
	+------+------+------+------+------+-------+		+------+------+------+------+------+-------+
	Each wireless technology essentially has independent control command		Each wireless technology essentially has independent control command
	and protocol, but when network would like to control all wireless		and protocol, but when network would like to control all wireless
	connection based on a generic command, it has to some changes in		connection based on a generic command, it has to some changes in
	driver level.		driver level.
	+-----------------+ | +-----------------+		+-----------------+ | +-----------------+
	| | | | |		| | | | |
	| +-------------+ | | | +-------------+ |		| +-------------+ | | | +-------------+ |
	skipping to change at page 6, line 7 ¶		skipping to change at page 6, line 7 ¶
	| | Driver | | | | | Driver | |		| | Driver | | | | | Driver | |
	| | MAC | | Radio/MAC | | MAC | |		| | MAC | | Radio/MAC | | MAC | |
	| | Phy |(------|------)| Phy | |		| | Phy |(------|------)| Phy | |
	| +-------------+ | | | +-------------+ |		| +-------------+ | | | +-------------+ |
	| | | | |		| | | | |
	| MN | | | AP |		| MN | | | AP |
	+-----------------+ | +-----------------+		+-----------------+ | +-----------------+
	4. Protocol Overview		4. Protocol Overview
	GMMP uses UDP/TCP/SCTP as its transport protocol. GMMP messages from		GMMP could use UDP/TCP/SCTP as its transport protocol. GMMP messages
	a client to a server are sent to the 'GMMP server' port (TBD), and		from a client to a server are sent to the 'GMMP server' port (TBD),
	GMMP messages from a server to a client are sent to the 'GMMP client'		and GMMP messages from a server to a client are sent to the 'GMMP
	port (TBD).		client' port (TBD).
	0 1 2 3		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		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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|GMMP v.| Type | Length | Flags |		|GMMP v.| Type | Length | Flags |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Identification |		| Identification |
	| |		| |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| options |		| options |
	skipping to change at page 14, line 5 ¶		skipping to change at page 13, line 17 ¶
	Proxy Mobile IPv6 protocol [NETLMM-MM-MAG] has specify an interface		Proxy Mobile IPv6 protocol [NETLMM-MM-MAG] has specify an interface
	between mobile node and MAG, but it doesn't specify any protocol for		between mobile node and MAG, but it doesn't specify any protocol for
	usage. Normally, it will depends on layer 2 specific message.		usage. Normally, it will depends on layer 2 specific message.
	Another issue for Proxy Mobile IPv6, regarding to mobile initiate		Another issue for Proxy Mobile IPv6, regarding to mobile initiate
	mobility management, the trigger for sending proxy binding update		mobility management, the trigger for sending proxy binding update
	message could be various kind of message such as DHCP, Router		message could be various kind of message such as DHCP, Router
	solicitaion or acknowledgement message. When the mobile node has		solicitaion or acknowledgement message. When the mobile node has
	multiple heterogenerous wireless connections, such various kind of		multiple heterogenerous wireless connections, such various kind of
	message will be not suitable.		message will be not suitable.
			GMMP could be used between MAG and MN in Proxy Mobile IPv6 protocol
			which will be used for mobility trigger, IP address configuration,
			policy configuration et al.
	7. Security Considerations		7. Security Considerations
	The protocol between terminal and wireless access point could be		The protocol between terminal and wireless access point could be
	protected by wirless protection mechanism since most of wireless		protected by wirless protection mechanism since most of wireless
	communication is based on point to point connections, in the case of		communication is based on point to point connections, in the case of
	shared link wireless connection, layer 2 or layer 3 based security		shared link wireless connection, layer 2 or layer 3 based security
	mechanism should be adopted.		mechanism should be adopted.
	8. IANA Considerations		8. IANA Considerations
	skipping to change at page 17, line 5 ¶		skipping to change at page 16, line 22 ¶
	9.2. Informative References		9.2. Informative References
	[NETLMM-MM-MAG]		[NETLMM-MM-MAG]
	Laganier, J., "Interface between a Proxy MIPv6 Mobility		Laganier, J., "Interface between a Proxy MIPv6 Mobility
	Access Gateway and a Mobile Node", Februray 2008,		Access Gateway and a Mobile Node", Februray 2008,
	<draft-ietf-netlmm-mn-ar-if-03(work in progress)>.		<draft-ietf-netlmm-mn-ar-if-03(work in progress)>.
	[RFC2131] Droms, R., "Dynamic Host Configuration Protocol",		[RFC2131] Droms, R., "Dynamic Host Configuration Protocol",
	RFC 2131, March 1997.		RFC 2131, March 1997.
			[RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K.,
			and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008.
	Author's Address		Author's Address
	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
End of changes. 9 change blocks.
	13 lines changed or deleted		23 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/