--- 1/draft-ietf-dmm-requirements-13.txt 2014-02-03 15:14:34.413238865 -0800 +++ 2/draft-ietf-dmm-requirements-14.txt 2014-02-03 15:14:34.453239840 -0800 @@ -1,26 +1,25 @@ Network Working Group H. Chan (Ed.) -Internet-Draft Huawei Technologies (more -Intended status: Informational co-authors on P. 17) -Expires: August 4, 2014 D. Liu - China Mobile +Internet-Draft Huawei Technologies +Intended status: Informational D. Liu +Expires: August 7, 2014 China Mobile P. Seite Orange H. Yokota KDDI Lab J. Korhonen Broadcom Communications - January 31, 2014 + February 3, 2014 Requirements for Distributed Mobility Management - draft-ietf-dmm-requirements-13 + draft-ietf-dmm-requirements-14 Abstract This document defines the requirements for Distributed Mobility Management (DMM) at the network layer. The hierarchical structure in traditional wireless networks has led primarily to centralized deployment models. As some wireless networks are evolving away from the hierarchical structure, a distributed model for mobility management can be useful to them. @@ -38,54 +37,55 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. 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." - This Internet-Draft will expire on August 4, 2014. + + This Internet-Draft will expire on August 7, 2014. Copyright Notice Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents - 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 - 2. Conventions used in this document . . . . . . . . . . . . . . 5 - 2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5 - 3. Centralized versus distributed mobility management . . . . . . 6 - 3.1. Centralized mobility management . . . . . . . . . . . . . 7 - 3.2. Distributed mobility management . . . . . . . . . . . . . 8 - 4. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 9 - 5. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 11 - 6. Security Considerations . . . . . . . . . . . . . . . . . . . 14 - 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 - 8. Co-authors and Contributors . . . . . . . . . . . . . . . . . 14 - 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 - 9.1. Normative References . . . . . . . . . . . . . . . . . . . 14 - 9.2. Informative References . . . . . . . . . . . . . . . . . . 14 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17 + 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 + 2. Conventions used in this document . . . . . . . . . . . . . . 4 + 2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 + 3. Centralized versus distributed mobility management . . . . . . 5 + 3.1. Centralized mobility management . . . . . . . . . . . . . 6 + 3.2. Distributed mobility management . . . . . . . . . . . . . 7 + 4. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 8 + 5. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 10 + 6. Security Considerations . . . . . . . . . . . . . . . . . . . 13 + 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 + 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 13 + 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 + 9.1. Normative References . . . . . . . . . . . . . . . . . . . 15 + 9.2. Informative References . . . . . . . . . . . . . . . . . . 15 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18 1. Introduction In the past decade a fair number of network-layer mobility protocols have been standardized [RFC6275] [RFC5944] [RFC5380] [RFC6301] [RFC5213]. Although the protocols differ in terms of functions and associated message formats, they all employ a mobility anchor to allow a mobile node to remain reachable after it has moved to a different network. The anchor point, among other tasks, ensures connectivity by forwarding packets destined to, or sent from, the @@ -139,27 +139,26 @@ for the service provider. Infrequent node mobility coupled with application intelligence suggest that mobility support could be provided selectively such as in [I-D.bhandari-dhc-class-based- prefix] and [I-D.korhonen-6man-prefix-properties], thus reducing the amount of context maintained in the network. DMM may distribute the mobility anchors in the data-plane towards a more flat network such that the mobility anchors are positioned closer to the user; ideally, mobility agents could be collocated with the first-hop router. Facilitated by the distribution of mobility - anchors, DMM may also selectively activate/deactivate mobility - protocol support. There is need to identify when mobility support - must be activated and when sessions do not require mobility - management support. It can thus reduce the amount of state - information that must be maintained in various mobility agents of the - mobile network. It can then avoid the unnecessary establishment of - mechanisms to forward traffic from an old to a new mobility anchor. + anchors, it may be possible to selectively use or not use mobility + protocol support depending on whether such support is needed or not. + It can thus reduce the amount of state information that must be + maintained in various mobility agents of the mobile network. It can + then avoid the unnecessary establishment of mechanisms to forward + traffic from an old to a new mobility anchor. This document compares distributed mobility management with centralized mobility management in Section 3. The problems that can be addressed with DMM are summarized in Section 4. The mandatory requirements as well as the optional requirements for network-layer distributed mobility management are given in Section 5. Finally, security considerations are discussed in Section 6. The problem statement and the use cases [I-D.yokota-dmm-scenario] can be found in [Paper-Distributed.Mobility.Review]. @@ -545,25 +544,133 @@ 6. Security Considerations Please refer to the discussion under Security requirement in Section 5.6. 7. IANA Considerations None -8. Co-authors and Contributors +8. Contributors - This problem statement document is a joint effort among the numerous - participants. Each individual has made significant contributions to - this work and have been listed as co-authors. + This requirements document is a joint effort among numerous + participants working in a team. In addition to the authors, each of + the following has made very significant and important contributions + to this work: + + Charles E. Perkins + Huawei Technologies + Email: charliep@computer.org + + Melia Telemaco + Alcatel-Lucent Bell Labs + Email: telemaco.melia@googlemail.com + + Elena Demaria + Telecom Italia + via G. Reiss Romoli, 274, TORINO, 10148, Italy + Email: elena.demaria@telecomitalia.it + + Jong-Hyouk Lee + Sangmyung University, Korea + Email: jonghyouk@smu.ac.kr + + Kostas Pentikousis + EICT GmbH + Email: k.pentikousis@eict.de + + Tricci So + ZTE + Email: tso@zteusa.com + Carlos J. Bernardos + Universidad Carlos III de Madrid + Av. Universidad, 30, Leganes, Madrid 28911, Spain + Email: cjbc@it.uc3m.es + + Peter McCann + Huawei Technologies + Email: Peter.McCann@huawei.com + + Seok Joo Koh + Kyungpook National University, Korea + Email: sjkoh@knu.ac.kr + + Wen Luo + ZTE + No.68, Zijinhua RD,Yuhuatai District, Nanjing, Jiangsu 210012, China + Email: luo.wen@zte.com.cn + + Sri Gundavelli + Cisco + sgundave@cisco.com + + Marco Liebsch + NEC Laboratories Europe + Email: liebsch@neclab.eu + + Carl Williams + MCSR Labs + Email: carlw@mcsr-labs.org + + Seil Jeon + Instituto de Telecomunicacoes, Aveiro + Email: seiljeon@av.it.pt + + Sergio Figueiredo + Universidade de Aveiro + Email: sfigueiredo@av.it.pt + + Stig Venaas + Email: stig@venaas.com + + Luis Miguel Contreras Murillo + Telefonica I+D + Email: lmcm@tid.es + + Juan Carlos Zuniga + InterDigital + Email: JuanCarlos.Zuniga@InterDigital.com + Alexandru Petrescu + Email: alexandru.petrescu@gmail.com + + Georgios Karagiannis + University of Twente + Email: g.karagiannis@utwente.nl + + Julien Laganier + Juniper + Email: julien.ietf@gmail.com + + Wassim Michel Haddad + Ericsson + Email: Wassim.Haddad@ericsson.com + + Dirk von Hugo + Deutsche Telekom Laboratories + Email: Dirk.von-Hugo@telekom.de + + Ahmad Muhanna + Award Solutions + Email: asmuhanna@yahoo.com + + Byoung-Jo Kim + ATT Labs + Email: macsbug@research.att.com + + Hassan Ali-Ahmad + Orange + Email: hassan.aliahmad@orange.com + + Alper Yegin + Samsung + Email: alper.yegin@partner.samsung.com 9. References 9.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. 9.2. Informative References @@ -678,21 +786,21 @@ for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access", 3GPP TR 23.401 10.10.0, March 2013. [TS.29303] 3GPP, "Domain Name System Procedures; Stage 3", 3GPP TR 23.303 11.2.0, September 2012. Authors' Addresses H Anthony Chan (editor) - Huawei Technologies (more co-authors on P. 17) + Huawei Technologies 5340 Legacy Dr. Building 3, Plano, TX 75024, USA Email: h.a.chan@ieee.org Dapeng Liu China Mobile Unit2, 28 Xuanwumenxi Ave, Xuanwu District, Beijing 100053, China Email: liudapeng@chinamobile.com Pierrick Seite Orange @@ -696,125 +804,14 @@ Pierrick Seite Orange 4, rue du Clos Courtel, BP 91226, Cesson-Sevigne 35512, France Email: pierrick.seite@orange.com Hidetoshi Yokota KDDI Lab 2-1-15 Ohara, Fujimino, Saitama, 356-8502 Japan Email: yokota@kddilabs.jp - Jouni Korhonen Broadcom Communications Porkkalankatu 24, FIN-00180 Helsinki, Finland Email: jouni.nospam@gmail.com - - - Charles E. Perkins - Huawei Technologies - Email: charliep@computer.org - - - Melia Telemaco - Alcatel-Lucent Bell Labs - Email: telemaco.melia@googlemail.com - - - Elena Demaria - Telecom Italia - via G. Reiss Romoli, 274, TORINO, 10148, Italy - Email: elena.demaria@telecomitalia.it - - - Jong-Hyouk Lee - Sangmyung University, Korea - Email: jonghyouk@smu.ac.kr - - - Kostas Pentikousis - EICT GmbH - Email: k.pentikousis@eict.de - - - Tricci So - ZTE - Email: tso@zteusa.com - - - Carlos J. Bernardos - Universidad Carlos III de Madrid - Av. Universidad, 30, Leganes, Madrid 28911, Spain - Email: cjbc@it.uc3m.es - - - Peter McCann - Huawei Technologies - Email: Peter.McCann@huawei.com - - - Seok Joo Koh - Kyungpook National University, Korea - Email: sjkoh@knu.ac.kr - - - Wen Luo - ZTE - No.68, Zijinhua RD,Yuhuatai District, Nanjing, Jiangsu 210012, China - Email: luo.wen@zte.com.cn - - - Sri Gundavelli - Cisco - sgundave@cisco.com - - - Marco Liebsch - NEC Laboratories Europe - Email: liebsch@neclab.eu - - - Carl Williams - MCSR Labs - Email: carlw@mcsr-labs.org - - - Seil Jeon - Instituto de Telecomunicacoes, Aveiro - Email: seiljeon@av.it.pt - - - Sergio Figueiredo - Universidade de Aveiro - Email: sfigueiredo@av.it.pt - - - Stig Venaas - Email: stig@venaas.com - - - Luis Miguel Contreras Murillo - Telefonica I+D - Email: lmcm@tid.es - - - Juan Carlos Zuniga - InterDigital - Email: JuanCarlos.Zuniga@InterDigital.com - - - Alexandru Petrescu - Email: alexandru.petrescu@gmail.com - - - Georgios Karagiannis - University of Twente - Email: g.karagiannis@utwente.nl - - - Julien Laganier - Juniper - julien.ietf@gmail.com - - - Wassim Michel Haddad - Ericsson - Wassim.Haddad@ericsson.com - - - Dirk von Hugo - Deutsche Telekom Laboratories - Dirk.von-Hugo@telekom.de - - - Ahmad Muhanna - Award Solutions - asmuhanna@yahoo.com - - - Byoung-Jo Kim - ATT Labs - macsbug@research.att.com - - - Hassan Ali-Ahmad - Orange - hassan.aliahmad@orange.com - - - Alper Yegin - Samsung - alper.yegin@partner.samsung.com - -