MEXT Working Group C. Park Internet-Draft N. Choi Expires: April 26, 2009 T. Kwon Y. Choi Seoul National University E. Paik KT Oct 23, 2008 Differentiation Using Virtualization of Mobile Network draft-mext-park-vnemo-00.txt Status of this Memo By submitting this Internet-Draft, each author represents that any 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 aware will be disclosed, in accordance with Section 6 of BCP 79. 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. This Internet-Draft will expire on April 26, 2009. Abstract A mobile router with multiple interfaces can make connection to several access networks. Using virtualization on the mobile network, several virtual mobile network can be exist for a single mobile network. Multiple virtual mobile networks for a single mobile network can be used for service differentiation for mobile network nodes. Park, et al. Expires April 26, 2009 [Page 1] Internet-Draft diff-vnemo Oct 2008 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Virtualization on a mobile network . . . . . . . . . . . . . . 4 4. Differentiation Using Virtual Mobile Network . . . . . . . . . 5 4.1. Single access network case . . . . . . . . . . . . . . . . 5 4.2. Multiple access network case . . . . . . . . . . . . . . . 5 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 Intellectual Property and Copyright Statements . . . . . . . . . . 9 Park, et al. Expires April 26, 2009 [Page 2] Internet-Draft diff-vnemo Oct 2008 1. Introduction Various mobility support mechanism for a mobile terminal have been supposed, including outstanding Mobile IPv6 [RFC3775]. Also to lessen the burden of change in terminal to support mobility, network- based mobility solution for a mobile terminal is specified in Proxy Mobile IPv6 [RFC5213]. On the other hands, NEMO basic support [RFC3963] support mobility for a router or a subnetwork. With NEMO, a subnet node need not be aware of the movement and no change is required to support the mobility, consequently. Multiple care-of address registration [MCoA] describes the way how to register multiple care-of address to the Home Agent in the case that a mobile node has multiple interfaces and uses them to connect several access network simultaneously for matters of cost, bandwidth, delay, etc. With multiple care-of addresses, a mobile node (or router) can exploit the advantage of each access network. [MCoA] does not have description about the way how to make a choice of interface, or access network, to transmit the traffic. Virtualization refers to an abstraction technique to share a single physical resource among several users. For a mobile network, virtualization can be used to form several virtual mobile networks on a single mobile network. A mobile router with multiple interfaces that are connected to multiple access network can support differentiation of service quality to its mobile network nodes, by adopting virtual mobile network concept. 2. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. Terms used in this draft are defined in [RFC5213], [RFC3963], [RFC3775], [MCoA]. In addition or in replacement of these, the following terms are defined or redefined: Mobile Network A mobile network is a network which is composed of a router and its subnet nodes, while the router has mobility. Mobile Network Node Park, et al. Expires April 26, 2009 [Page 3] Internet-Draft diff-vnemo Oct 2008 A mobile network node is a node connected to the mobile router. A mobile network node is provided with Internet connectivity from a mobile router, so even a mobile network moves, a mobile network node that is attached to the mobile router is not aware of the movement. A mobile network node can be mobile itself, or fixed with the mobile router. Virtual Mobile Network A virtual mobile network is a logical network that lies on a single physical mobile network. Several virtual mobile network can be exist on a single physical mobile network. Every virtual mobile network includes the mobile router and all or some of the mobile network nodes. 3. Virtualization on a mobile network Virtualization is a term refers to a technique for abstraction physical resource to provide it to one or more users. One single resource can be seen as several virtual resources to multiple users, or several physical resources can be seen as a single virtual resource to a user. For a network, various type of virtualization can be exist according to the layer that is virtualized. Virtualization at lower layer, PHY or MAC, is implemented using various multiplexing or multiple access mechanisms to support multiple users that shares a single resource, like a link or radio spectrum. But usually lower layer multiplexing technique needs MAC- level or PHY-level modification, and it is hard to implement or manage. A network can be virtualized at a higher layer. An overlay network is example of the network virtualization at a higher layer, like network layer or application layer. In an overlay network, a virtual link which is composed of multi-hop physical link connects two or more overlay nodes. On a single physical network composed of routers and terminals, several virtual networks can be exist. Under IPv6, a virtual mobile network can be implemented in other way, by using several mobile network prefixes in a single NEMO. In this way, a part of mobile network, including mobile router itself and some of the mobile network nodes, forms a virtual mobile network while the mobile router and other mobile network nodes compose another virtual mobile network on the same NEMO. Park, et al. Expires April 26, 2009 [Page 4] Internet-Draft diff-vnemo Oct 2008 +---------------+ | Mobile Router | +-------+-------+ | +-----------------------------------+ | +----------------------------------+ | VMN 1 : 2001:a:e:1::/64 | | | VMN 2 : 2001:a:e:2::/64 | | | | | | | +--------------+----------+---+------------+---------------+ | | | | | | | | | | +---------+ +---------+ | | +---------+ +----+----+ | | | MNN 1 | | MNN 2 | | | | MNN 3 | | MNN 4 | | | +---------+ +---------+ | | +---------+ +---------+ | | | | | +-----------------------------------+ +----------------------------------+ Each virtual mobile network is distinguished by mobile network prefix that the virtual mobile network uses. A mobile router sets up multiple mobile network prefixes for the virtual mobile networks. A mobile network node selects one of the mobile network prefixes advertised by the mobile router. 4. Differentiation Using Virtual Mobile Network Service differentiation for mobile network can be implemented using virtual mobile network concept. 4.1. Single access network case A mobile router generates several prefixes to form multiple virtual mobile networks. Each virtual mobile network corrspondes to a priority class of each mobile network node. The decision of virtual mobile network for a mobile network node is negotiated when the mobile network node attahces to the mobile router. When a mobile network node sends traffic to the Internet, the mobile router regulates the traffic according to the priority of the virtual mobile network in which the mobile network joined. 4.2. Multiple access network case In the case that the mobile router has several interfaces that are connected to multiple access networks, characteristic of each access network can be used for service differentiation of virtual mobile networks. A mobile router generates new mobile network prefix when it attaches to a new access network. Each mobile network prefix forms a new virtual mobile network, while the mobile network prefix Park, et al. Expires April 26, 2009 [Page 5] Internet-Draft diff-vnemo Oct 2008 also connected to a specific access network. The mapping information between the mobile network prefix and the access network is stored in the mobile router. When a mobile network node joins to the mobile network, it notifies the access network requirement to the mobile router. The network requirement can be traffic classification, like BE, Voice, or Video, or the network requirement can be specified by some parameters like bandwidth, packet loss rate, or latency. According to the requirement, the mobile network selects an appropriate virtual mobile network, e.g. the mobile network prefix, that is connected to one of the access networks. The mobile network node then configures the address. Traffic from the mobile network node destined to the Internet is classified at the mobile router and forwarded to the access network connected to the virtual mobile network prefix. 5. Security Considerations We do not consider any security issues in this draft. 6. References [RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in IPv6", RFC 3775, June 2004. [RFC3963] Devarapalli, V., Wakikawa, R., Petrescu, A., and P. Thubert, "Network Mobility (NEMO) Basic Support Protocol", RFC 3963, January 2005. [RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008. [MCoA] Wakikawa, R., Devarapalli, V., Ernst, T., and K. Nagami, "Multiple Care-of Addresses Registration", August 2008. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. Park, et al. Expires April 26, 2009 [Page 6] Internet-Draft diff-vnemo Oct 2008 Authors' Addresses Chulhyun Park Seoul National University Multimedia Communications Lab., Seoul National Univ. Shillim-dong, Kwanak-gu Seoul 151-744 Korea Phone: +82-2-880-9147 Fax: +82-2-876-7170 Email: chpark@mmlab.snu.ac.kr URI: http://mmlab.snu.ac.kr/~chpark/ Nakjung Choi Seoul National University Multimedia Communications Lab., Seoul National Univ. Shillim-dong, Kwanak-gu Seoul 151-744 Korea Phone: +82-2-876-7170 Fax: +82-2-876-7170 Email: fomula@mmlab.snu.ac.kr URI: http://mmlab.snu.ac.kr/~fomula/ Taekyoung Kwon Seoul National University Multimedia Communications Lab., Seoul National Univ. Shillim-dong, Kwanak-gu Seoul 151-744 Korea Phone: +82-2-880-9105 Fax: +82-2-872-2045 Email: tk@mmlab.snu.ac.kr URI: http://mmlab.snu.ac.kr/~tk/ Park, et al. Expires April 26, 2009 [Page 7] Internet-Draft diff-vnemo Oct 2008 Yanghee Choi Seoul National University Multimedia Communications Lab., Seoul National Univ. Shillim-dong, Kwanak-gu Seoul 151-744 Korea Phone: +82-2-880-7303 Fax: +82-2-872-2045 Email: yhchoi@snu.ac.kr URI: http://mmlab.snu.ac.kr/~yhchoi/ Eunkyoung Paik KT Future Technology Lab. KT 17 Woomyeon-dong, Seocho-gu Seoul 137-792 Korea Phone: +82-2-526-5233 Fax: +82-2-526-5759 Email: euna@kt.co.kr URI: http://mmlab.snu.ac.kr/~eun/ Park, et al. Expires April 26, 2009 [Page 8] Internet-Draft diff-vnemo Oct 2008 Full Copyright Statement Copyright (C) The IETF Trust (2008). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Park, et al. Expires April 26, 2009 [Page 9]