INTERNET DRAFT JUNHYUK SONGJanuaryMarch 2002CHAE YOUNG CHONGSAMSUNGELECTRONICS.ELECTRONICS DONGKIE LEE SK TELECOM DNS RR type for NAIdraft-song-dnsext-nai-support-00.txtdraft-song-dnsext-nai-support-01.txt Status of This Memo Distribution of this memo is unlimited. This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at: http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at: http://www.ietf.org/shadow.html. Abstract This document proposes the use of the new DNS RR type "NAI" (Network Access Identifier) [RFC2486] to specifythe most current location of the user(Hostdynamically assigned IPaddress).address. 1. Introduction Thedemand foruse of the wireless mobile networking has been dramatically increased thanks to rapid development of wireless technology andde factocommercial deployment of Mobile IP technology[1]. Therefore, the need for standardized method[RFC3220]. The most recent release ofspecifyingMobile IPv4 supports theuser over different Internet Service Providers (ISPs) was identified.dynamic Home Address assignment mechanism that allow MN (Mobile Node) being identified by NAI (Network Access Identifier) [RFC2486] rather than static Home IP address. NAI has a prominent role on the mobile network environment. This isas defined in RFC-2486not only because NAI significantly reduces the IPv4 address shortage problem and but also it provides the standardized method for identifying users in order to accomplish the interoperability for roamingand tunnelingover multipleInternetISPs (Internet ServiceProviders (ISPs).Providers). TheNAI (Network Access Identifier) ismost of theform user@realm [3].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 IP address with support of many other RRs thorough hierarchically built domain names.Combining above two, NAI and DNS shall enable IP user mobility [2].TheIP user mobilityNAI isthe ability of end user to send and receive IP datagrams regardlessof thelocationform user@realm [RFC2486]. Adding NAI as a DNS RR shall enable tracking of themobile terminal and user location.dynamically changed home IP address. This document specifies a new RR type for NAI, mapping host IP address and user identifier (NAI)[3].[RFC2486]. 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 connection and Mobile IPv4. The basic idea is to let mobile Internet user to constantly update itslocation(IP address),IP address, while moving around multiple access provider network. It can enables correspondent user to always reach the specific user by querying NAI to name server, regardless of the connecting location. It is expected that NAI RR will be used in IRS(Internet Reachability Service) of 3GPP2 wireless IP network standard[4][P.S0001-B] (see AppendixA) and IP user mobility application [5]. Those applicationA). 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 nameserver.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 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 domain name. The "@" sign before realm, shall be treated as a delimiter to flag user ID part. Every user Identifier shall end with "@" sign and placed before domain name. NAI records cause no additional section processing The NAI record has the DNS RR type of "?", hence has the same QTYPE number of "?". Note NAI RR requires IANA number assignment. 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 The RDATA of NAI is same as A RDATA format, 32 bit Internet Address 4. Examples Resource Record forNAI(junhyuk@samsung.skt.co.kr)NAI(junhyuk@xbs.samsung.co.kr) is like below:junhyuk@.samsung.skt.co.kr. 86400junhyuk@.xbs.samsung.co.kr. 1440 IN NAI 165.213.221.4 5. IANA Considerations It requires new RR type number from IANA. 6. Acknowledgements Special thanks toProf.Professor Murali Venkatesh of SyracuseUniversity, and Dr. Woo June KimUniversity Appendix A. IRS of 3GPP2 wireless IP Network standard In this example,we'veI've omitted the detail operation of deleting 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 hostname 1. Simple IP operation Upon connecting to new access network MS(Mobile Station) shall generate CHAP authentication with NAI for user authentication. After successfully authenticate the user authentication request, AAAH shall send DNS A record update message to name server. (See figure 1) +--------------+ PPP CHAP (3) +--------------+ | | Auth Req | AAAH | | AAAF |-------------->| | | |<--------------| | +--------------+ PPP CHAP(5) +--------------+ ^ | Auth Ack | PPP CHAP | | User | Auth Req | | PPP CHAP Location | (2) | | Auth Ack Update(4)| | | (6) v | v +---------------+ +------+ PPP CHAP +-----------+ | Name Server | | | Auth Req (1) | | +---------------+ | |---------------------->| PDSN | ^ | |<----------------------| | User | | MS | PPP CHAP | | Location | | | Auth Ack (7) | | Query | | |<--------------------->| | | | | IP data (8) | | +-------+ +------+ | | <-----------| CH | +-----------+ IP data +-------+ Figure 1: Simple IPv4 operation 2. Mobile IP operation When the HA receives and successfully replies to an initial Mobile IP Registration Request, it performs the DNS update for the MS if it has previously received an indication from the home RADIUS server to do so, or has otherwise been provisioned to do so. The HA shall send a DNS Update message [RFC 2136] to the DNS server to add a Resource Record for the MS, if so required by the home RADIUS server [4]. (See figure 2) +--------------+ +--------------+ | |---------------->| | | AAAF | | AAAH | | |<----------------| | +--------------+ +--------------+ ^ | ^ Access | | Access | Request | v Accept v +------+ Agent +--------------+ +--------------+ | |Advertisement | | | | | | with FAC | PDSN/FA | | Mobile IPv4 | | MS |<------------ | | | Home Agent | | |------------> | |---------------->| | | |Mobile IP RRQ | |Mobile IP RRQ | | | |with MN-AAA | | | | | |<-------------| |<----------------| | +------+Mobile IP RRP +--------------+Mobile IP RRP +--------------+ | User | Location | Update | v +--------------+ | Name Server | +--------------+ Figure 2: Mobile IPv4 operation References[1][RFC3220] C. Perkins, Editor. "IP Mobility Support". RFC 3320. January 2002.October 1996. [2][UM] J.H Song,C.Y Chong,DK Lee"draft-song-network-user-mobility-00.txt [3]"draft-song-network-user-mobility-00.txt" Work in Progress [RFC2486] Bernard Aboba and Mark A. Beadles "The Network Access Identifier". RFC 2486. January 1999.[4][P.S0001-B] 3GPP2 P.S0001-B work in progress.[5] J.H Song and C.Y Chong, DK Lee "draft-song-mobileip-mipv6-user-mobility-00.txt"ftp://ftp.3gpp2.org/TSGP/Standard/ Addresses Questions about this memo can be directed to the authors: JUNHYUK SONGCHAEYOUNG CHONGSAMSUNG ELECTRONICS. Packet Technology System Lab. Mobile Development TeamNetwork Systems DivisionPhone: +82-31-279-3639 Email:santajun@lycos.co.krjunhyuk@telecom.samsung.co.kr santajunman@yahoo.com DONGKIE LEE SK TELECOM Core Network Development Team Network R&D Center Phone +82-2-829-4640 Email: galahad@netsgo.com FAX:+82-2-829-4612SongFull Copyright Statement Copyright (C) The Internet Society (2002). All Rights Reserved. This document andLee Expires July 2002 [Page 6]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.