< draft-song-mobileip-mipv6-user-mobility-00.txt		draft-song-mobileip-mipv6-user-mobility-01.txt >
	JUNHYUK SONG		JUNHYUK SONG
	INTERNET DRAFT CHAEYOUNG CHONG		INTERNET DRAFT CHAEYOUNG CHONG
	October 2001 SAMSUNG ELECTRONICS.		October 2001 SAMSUNG ELECTRONICS.
	DONGKIE LEE		DONGKIE LEE
	SK TELECOM		SK TELECOM
	MIPv6 IP User mobility support through DNS		MIPv6 IP User mobility support through DNS
	draft-song-mobileip-mipv6-user-mobility-00.txt		draft-song-mobileip-mipv6-user-mobility-01.txt
	Status of This Memo		Status of This Memo
	Distribution of this memo is unlimited.		Distribution of this memo is unlimited.
	This document is an Internet-Draft and is in full conformance with		This document is an Internet-Draft and is in full conformance with
	all provisions of Section 10 of RFC2026. Internet-Drafts are working		all provisions of Section 10 of RFC2026. Internet-Drafts are working
	documents of the Internet Engineering Task Force (IETF), its areas,		documents of the Internet Engineering Task Force (IETF), its areas,
	and its working groups. Note that other groups may also distribute		and its working groups. Note that other groups may also distribute
	working documents as Internet-Drafts.		working documents as Internet-Drafts.
	skipping to change at page 5, line 36 ¶		skipping to change at page 5, line 36 ¶
	| |Advertisement | | | |		| |Advertisement | | | |
	| | | MIPv6 | Binding Update | MIPv6 |		| | | MIPv6 | Binding Update | MIPv6 |
	| MN |<------------ | Router |---------------->| HA/UMA |		| MN |<------------ | Router |---------------->| HA/UMA |
	| |------------> | |<----------------| |		| |------------> | |<----------------| |
	| |Binding Update| | Binding Ack | |		| |Binding Update| | Binding Ack | |
	| | | | | |		| | | | | |
	| |<-------------| | | |		| |<-------------| | | |
	+------+ Binding Ack +--------------+ +--------------+		+------+ Binding Ack +--------------+ +--------------+
	|		|
	DNS |		DNS |
	Update |		Update |
	v		v
	+--------------+		+--------------+
	| DNS server |		| DNS server |
	+--------------+		+--------------+
	Figure 1: User Mobility		Figure 1: User Mobility
	2.3 User connectivity by DNS server		2.3 User connectivity by DNS server
	MIPv6 capable correspondent node shall query of the user location		MIPv6 capable correspondent node shall query the user location
	through DNS server to locate the most recent location of the		through DNS server to locate the most recent location of the
	user. The MIPv6 host shall retrieve two records from DNS server		user. The MIPv6 host shall retrieve two records from DNS server
	indexed by the user identifier (FQDN), one for home address of		indexed by the user identifier (FQDN), one for home address of
	mobile node and the other is current mobile node address (Mobile IPv6		mobile node and the other is current mobile node address (Mobile IPv6
	CoA). If there is no previous cache for the location of the user,		CoA). If there is no previous cache for the location of the user,
	MIPv6 host shall begin to transmit IP packets to home address of MN.		MIPv6 host shall begin to transmit IP packets to home address of MN.
	The IP data will deliver to MN by through HA as tunneled data.		The IP data will deliver to MN by through HA as tunneled data.
	Upon receiving of encapsulated IP data from HA, MN would know either		Upon receiving of encapsulated IP data from HA, MN would know either
	MIPv6 host currently didn't have the cached binding table for the		MIPv6 host currently didn't have the cached binding table for the
	skipping to change at page 6, line 35 ¶		skipping to change at page 6, line 35 ¶
	| |<----------------| MIPv6 |Binding Update(3)| MIPv6 |		| |<----------------| MIPv6 |Binding Update(3)| MIPv6 |
	| MN |Binding Update(2)| Router |---------------->| HA/UMA |		| MN |Binding Update(2)| Router |---------------->| HA/UMA |
	| |---------------->| |<----------------| |		| |---------------->| |<----------------| |
	| |<----------------| |Binding Ack (5) | |		| |<----------------| |Binding Ack (5) | |
	| |Binding Ack(6) | | | |		| |Binding Ack(6) | | | |
	| | | |<----------------| |		| | | |<----------------| |
	| |<----------------| |Encapsulated IP | |		| |<----------------| |Encapsulated IP | |
	+------+ Encapsulated IP +------------+Packet (9) +--------------+		+------+ Encapsulated IP +------------+Packet (9) +--------------+
	| ^ Packet (10) ^ ^		| ^ Packet (10) ^ ^
	| | | |		| | | |
	| | | |		| | | |
	| | | |		| | | |
	| | IP traffic (12) +------------+ IP traffic (8) | |		| | IP traffic (12) +------------+ IP traffic (8) | |
	| +----------------------| MIPv6 Host |---------------------+ |		| +----------------------| MIPv6 Host |---------------------+ |
	+----------------------->| CN | |		+----------------------->| CN | |
	Binding Update (11)+------------+ |		Binding Update (11)+------------+ |
	^ DNS |		^ DNS |
	| Update |		| Update |
	DNS | (4) |		DNS | (4) |
	Query | |		Query | |
	(7) | v		(7) | v
	| +--------------+		| +--------------+
	+-------------------->| DNS server |		+-------------------->| DNS server |
	+--------------+		+--------------+
	Figure 2: Binding update case		Figure 2: Binding update case
	Upon receiving binding update message, the MIPv6 correspondent host		Upon receiving binding update message, the MIPv6 correspondent host
	shall compares IP source address of binding update message with		shall compares IP source address of binding update message with
	previously retrieved the user records from the DNS server.		previously retrieved the user records from the DNS server.
	If the second record (CoA) matches with the source IP address of the		If the second record (CoA) matches with the source IP address of the
	binding update message, correspondent node shall begin to sending IP		binding update message, correspondent node shall begin to sending IP
	packets to MN directly. (see figure 2)		packets to MN directly. (see figure 2)
	The retrieved record shall not match with the source IP address of		The retrieved record shall not match with the source IP address of
End of changes. 6 change blocks.
	13 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/