< draft-song-dnsext-nai-support-00.txt		draft-song-dnsext-nai-support-01.txt >
	INTERNET DRAFT JUNHYUK SONG		INTERNET DRAFT JUNHYUK SONG
	January 2002 CHAE YOUNG CHONG		March 2002 SAMSUNG ELECTRONICS
	SAMSUNG ELECTRONICS.
	DONGKIE LEE		DONGKIE LEE
	SK TELECOM		SK TELECOM
	DNS RR type for NAI		DNS RR type for NAI
	draft-song-dnsext-nai-support-00.txt		draft-song-dnsext-nai-support-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 1, line 34 ¶		skipping to change at page 1, line 33 ¶
	any time. It is inappropriate to use Internet-Drafts as reference		any 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.
	Abstract		Abstract
	This document proposes the use of the new DNS RR type "NAI" to		This document proposes the use of the new DNS RR type "NAI"
	specify the most current location of the user(Host IP address).		(Network Access Identifier) [RFC2486] to specify dynamically assigned
			IP address.
	1. Introduction		1. Introduction
	The demand for wireless mobile networking has been dramatically		The use of the wireless mobile networking has been dramatically
	increased thanks to rapid development of wireless technology and		increased thanks to rapid development of wireless technology and
	de facto Mobile IP technology [1]. Therefore, the need for		commercial deployment of Mobile IP technology [RFC3220].
	standardized method of specifying the user over different Internet		The most recent release of Mobile IPv4 supports the dynamic Home
	Service Providers (ISPs) was identified. NAI is as defined in		Address assignment mechanism that allow MN (Mobile Node) being
	RFC-2486 provides the standardized method for identifying users		identified by NAI (Network Access Identifier) [RFC2486] rather than
	in order to accomplish the interoperability for roaming and		static Home IP address. NAI has a prominent role on the mobile
	tunneling over multiple Internet Service Providers (ISPs).		network environment. This is not only because NAI significantly
	The NAI (Network Access Identifier) is of the form user@realm [3].		reduces the IPv4 address shortage problem and but also it provides
			the standardized method for identifying users in order to accomplish
			the interoperability for roaming over multiple ISPs (Internet Service
			Providers).
			The most of the Mobile IPv4 deployment including 3GPP2 CDMA2000
			wireless packet data system architecture [P.S0001-B] identify
			the Mobile Node by NAI. Therefore the need for standardized method
			of binding the ever changing home address of the MN over various ISPs
			to NAI is necessary.
	The DNS basically provides a mechanism to map between hostnames and		The DNS basically provides a mechanism to map between hostnames and
	IP address with support of many other RRs thorough hierarchically		IP address with support of many other RRs thorough hierarchically
	built domain names.		built domain names. The NAI is of the form user@realm [RFC2486].
			Adding NAI as a DNS RR shall enable tracking of the dynamically
	Combining above two, NAI and DNS shall enable IP user mobility [2].		changed home IP address. This document specifies a new RR type for
	The IP user mobility is the ability of end user to send and		NAI, mapping host IP address and user identifier (NAI) [RFC2486].
	receive IP datagrams regardless of the location of the mobile
	terminal and user location.
	This document specifies a new RR type for NAI, mapping host IP
	address and user identifier (NAI) [3].
	2. Applicability Statement		2. Applicability Statement
			Mobile IPv4 is designed to provide the IP mobility that provides
			reasonably seamless IP connectivity. Since the MN (Mobile Node) is
			no longer necessarily identified by the unique home IP address,
			the mechanism for the locating and updating newly assigned home IP
			address is required [UM].
	The NAI RR defines user identifier, NAI widely used for PPP dialup		The NAI RR defines user identifier, NAI widely used for PPP dialup
	connection and Mobile IPv4. The basic idea is to let mobile Internet		connection and Mobile IPv4. The basic idea is to let mobile Internet
	user to constantly update its location(IP address), while moving		user to constantly update its IP address, while moving around
	around multiple access provider network. It can enables		multiple access provider network. It can enables correspondent user
	correspondent user to always reach the specific user by querying NAI		to always reach the specific user by querying NAI to name server,
	to name server, regardless of the location.		regardless of the connecting location.
	It is expected that NAI RR will be used in IRS(Internet Reachability		It is expected that NAI RR will be used in IRS(Internet Reachability
	Service) of 3GPP2 wireless IP network standard [4] (see Appendix A)		Service) of 3GPP2 wireless IP network standard [P.S0001-B]
	and IP user mobility application [5]. Those application depends on		(see Appendix A).
	one to one mapping of NAI and mobile host IP address in name server.
			The applications that running on the Dynamic Home Address Allocation
			enabled Mobile IPv4 MN (Mobile node) depends on the one to one
			mapping of NAI and newly assigned mobile host IP address in DNS name
			server for the connectivity with Correspondent nodes.
			Because it will be the only way the CN (Correspondent Node) can find
			the Mobile Node's newly assigned IP address. An example of
			application is including WWW server, IP push service, Instant
			Messaging, Multi-user Network games, Multi-chat, etc.
	3. NAI RR Type		3. NAI RR Type
	NAI name space is resemble to Domain Name Space, except that it is a		NAI name space is resemble to Domain Name Space, except that it is a
	sequence of one or more labels, made of the user identifier and		sequence of one or more labels, made of the user identifier and
	domain name. The "@" sign before realm, shall be treated as a		domain name. The "@" sign before realm, shall be treated as a
	delimiter to flag user ID part. Every user Identifier		delimiter to flag user ID part. Every user Identifier
	shall end with "@" sign and placed before domain name. NAI records		shall end with "@" sign and placed before domain name. NAI records
	cause no additional section processing		cause no additional section processing
	skipping to change at page 3, line 25 ¶		skipping to change at page 3, line 34 ¶
	number of "?". Note NAI RR requires IANA number assignment.		number of "?". Note NAI RR requires IANA number assignment.
	The class of NAI RR is defined in the IN class only.		The class of NAI RR is defined in the IN class only.
	TTL should be configured to minimize the time of the RR being cached		TTL should be configured to minimize the time of the RR being cached
	The RDATA of NAI is same as A RDATA format, 32 bit Internet Address		The RDATA of NAI is same as A RDATA format, 32 bit Internet Address
	4. Examples		4. Examples
	Resource Record for NAI(junhyuk@samsung.skt.co.kr) is like below:		Resource Record for NAI(junhyuk@xbs.samsung.co.kr) is like below:
	junhyuk@.samsung.skt.co.kr. 86400 IN NAI 165.213.221.4		junhyuk@.xbs.samsung.co.kr. 1440 IN NAI 165.213.221.4
	5. IANA Considerations		5. IANA Considerations
	It requires new RR type number from IANA.		It requires new RR type number from IANA.
	6. Acknowledgements		6. Acknowledgements
	Special thanks to Prof. Murali Venkatesh of Syracuse University, and		Special thanks to Professor Murali Venkatesh of Syracuse University
	Dr. Woo June Kim
	Appendix A. IRS of 3GPP2 wireless IP Network standard		Appendix A. IRS of 3GPP2 wireless IP Network standard
	In this example, we've omitted the detail operation of deleting		In this example, I've omitted the detail operation of deleting
	DNS record in case of user disconnect. In IRS, it is assumed that		DNS record in case of user disconnect. In IRS, it is assumed that
	MS desires to be reached by a fixed identifier such as an NAI-like		MS desires to be reached by a fixed identifier such as an NAI-like
	hostname		hostname
	1. Simple IP operation		1. Simple IP operation
	Upon connecting to new access network MS(Mobile Station) shall		Upon connecting to new access network MS(Mobile Station) shall
	generate CHAP authentication with NAI for user authentication.		generate CHAP authentication with NAI for user authentication.
	After successfully authenticate the user authentication request,		After successfully authenticate the user authentication request,
	AAAH shall send DNS A record update message to name server.		AAAH shall send DNS A record update message to name server.
	skipping to change at line 186 ¶		skipping to change at page 6, line 7 ¶
	Update |		Update |
	v		v
	+--------------+		+--------------+
	| Name Server |		| Name Server |
	+--------------+		+--------------+
	Figure 2: Mobile IPv4 operation		Figure 2: Mobile IPv4 operation
	References		References
	[1] C. Perkins, Editor. "IP Mobility Support". RFC 2002. October		[RFC3220] C. Perkins, Editor. "IP Mobility Support". RFC 3320.
	1996.		January 2002.
	[2] J.H Song, C.Y Chong, DK Lee
	"draft-song-network-user-mobility-00.txt
	[3] Bernard Aboba and Mark A. Beadles "The Network Access		[UM] J.H Song, DK Lee "draft-song-network-user-mobility-00.txt"
	Identifier". RFC 2486. January 1999.		Work in Progress
	[4] 3GPP2 P.S0001-B work in progress.		[RFC2486] Bernard Aboba and Mark A. Beadles "The Network Access
			Identifier". RFC 2486. January 1999.
	[5] J.H Song and C.Y Chong, DK Lee		[P.S0001-B] 3GPP2 P.S0001-B work in progress.
	"draft-song-mobileip-mipv6-user-mobility-00.txt"		ftp://ftp.3gpp2.org/TSGP/Standard/
	Addresses		Addresses
	Questions about this memo can be directed to the authors:		Questions about this memo can be directed to the authors:
	JUNHYUK SONG		JUNHYUK SONG
	CHAEYOUNG CHONG
	SAMSUNG ELECTRONICS.		SAMSUNG ELECTRONICS.
	Mobile Development Team		Packet Technology System Lab.
	Network Systems Division		Mobile Development Team
	Phone: +82-31-279-3639		Phone: +82-31-279-3639
	Email: santajun@lycos.co.kr		Email: junhyuk@telecom.samsung.co.kr
			santajunman@yahoo.com
	DONGKIE LEE		DONGKIE LEE
	SK TELECOM		SK TELECOM
	Core Network Development Team		Core Network Development Team
	Network R&D Center		Network R&D Center
	Phone +82-2-829-4640		Phone +82-2-829-4640
	Email: galahad@netsgo.com		Email: galahad@netsgo.com
	FAX:+82-2-829-4612		FAX:+82-2-829-4612
	Song and Lee Expires July 2002 [Page 6]		Full Copyright Statement
			Copyright (C) The Internet Society (2002). All Rights Reserved.
			This document and translations of it may be copied and furnished to
			others, and derivative works that comment on or otherwise explain it
			or assist in its implementation may be prepared, copied, published
			and distributed, in whole or in part, without restriction of any
			kind, provided that the above copyright notice and this paragraph
			are included on all such copies and derivative works. However, this
			document itself may not be modified in any way, such as by removing
			the copyright notice ore references to the Internet Society or other
			Internet organizations, except as needed for the purpose of
			developing Internet standards in which case the procedures for
			copyrights defined in the Internet Standards process must be
			followed, or as required to translate it into languages other than
			English.
			The limited permissions granted above are perpetual and will not be
			revoked by the Internet Society or its successors or assigns.
			This document and the information contained herein is provided on an
			"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
			TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
			BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
			HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
			MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
End of changes. 20 change blocks.
	49 lines changed or deleted		64 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/