Thierry Ernst (INRIA and WIDE) Hesham Soliman (Ericsson)

Slides:



Advertisements
Similar presentations
MONET Problem Scope and Requirements draft-kniveton-monet-requirements-00 T.J. Kniveton Alper Yegin IETF March 2002.
Advertisements

Mobile IP How Mobile IP Works? Agenda What problems does Mobile IP solve? Mobile IP: protocol overview Scope Requirements Design goals.
51st IETF London - Thierry Ernst - August Network Mobility Support in IPv6 Thierry Ernst - Motorola Labs & INRIA (Planete)
Dynamic Tunnel Management Protocol for IPv4 Traversal of IPv6 Mobile Network Jaehoon Jeong Protocol Engineering Center, ETRI
Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made.
Network Localized Mobility Management using DHCP
1 Route Optimization based on ND-Proxy for Mobile Nodes in IPv6 Mobile Networks Jaehoon Jeong, Kyeongjin Lee, Jungsoo Park, Hyoungjun Kim ETRI
Mobile IP.
1 The Design and Implementation of Mobile Session Controller.
NEtwork MObility By: Kristin Belanger. Contents Introduction Introduction Mobile Devices Mobile Devices Objectives Objectives Security Security Solution.
1 © 2001, Cisco Systems, Inc. All rights reserved. Session Number Presentation_ID Gopal Dommety Mobile IP VPN Design Team Update.
IPv6 & Mobile Residential Network 곽 광훈 ETRI
Req1 - Separability Old: –An RO scheme MUST have the ability to be bypassed by traffic types that desire to use bidirectional tunnels through an HA. New:
NEtwork MObility (NEMO) Houcheng Lee. Main Idea NEMO works by moving the mobility functionality from Mobile IP mobile nodes to a mobile router. The router.
NEMO Requirements and Mailing List Discussions/Conclusions T.J. Kniveton - Nokia Pascal Thubert - Cisco IETF 54 – July 14, 2002 Yokohama, Japan.
1 AutoconfBOF2.PPT / Aug / Singh,Perkins,Clausen IETF Not Confidential Ad hoc network autoconfiguration: definition and problem statement (draft-singh-autoconf-adp-00.txt)
NEtwork MObility (NEMO) Houcheng Lee. Main Idea NEMO works by moving the mobility functionality from Mobile IP mobile nodes to a mobile router. The router.
Prefix Delegation Protocol Selection T.J. Kniveton MEXT Working Group IETF 70 - December ’07 - Vancouver.
Mdnsext BoF Chairs: Tim Chown, Thomas Narten IETF85 Atlanta 6 th November, 2012.
71th IETF, Philadelphia, March 2008 ROLL Working Group Meeting IETF-71, March 2008, Philadelphia Online Agenda and Slides at:
49th IETF - San Diego - 1 Mobile Networks Support in IPv6 - Draft Update draft-ernst-mobileip-v6-01.txt - Thierry Ernst - MOTOROLA Labs Ludovic Bellier.
Dynamic Management of Multiple Mobile Routers Manabu Tsukada, Thierry Ernst, Ryuji Wakikawa and Koshiro Mitsuya Graduate School of Media and Governance,
1 Route Optimization for Large Scale Network Mobility Assisted by BGP Feriel Mimoune, Farid Nait-Abdesselam, Tarik Taleb and Kazuo Hashimoto GLOBECOM 2007.
ALTO BOF Charter Discussion. Charter Iterated (twice) on the list  Several comments on the first version Terminology, caching  No complains on current.
Spring 2004 Network Mobility School of Electronics and Information Kyung Hee University Choong Seon HONG
Mobile IP Outline Intro to mobile IP Operation Problems with mobility.
Thierry Ernst - MOTOROLA Labs / INRIA Ludovic Bellier - INRIA project PLANETE Claude Castelluccia - INRIA project PLANETE Hong-Yon Lach - MOTOROLA Labs.
1 Monami6 Working Group IETF 66 July 2006 Montréal, Canada Thierry Ernst (INRIA) Nicolas Montavont (ENST Bretagne)
1 NetLMM Vidya Narayanan Jonne Soininen
NEMO Re-chartering IETF 67 – November 9, 2006 T.J. Kniveton.
L3VPN WG IETF 78 30/07/ :00-11:30 Chairs: Marshall Eubanks Danny McPherson Ben Niven-Jenkins.
CONEX BoF. Welcome to CONEX! Chairs: –Leslie Daigle –Philip Eardley Scribe Note well.
63rd IETF - NEMO WG1 NEMO Multihoming Issues NEMO Multihoming Issues draft-ietf-nemo-multihoming-issues-03.txt Chan-Wah Ng Paik Eun-Kyoung Thierry Ernst.
Access Node Control Protocol (ANCP) IETF 66, Montreal Wojciech Dec Matthew Bocci
Nemo RO taxonomy P. Thubert, M. Molteni (Cisco) C. Ng (Panasonic) H. Ohnishi (NTT) E. Paik (Seoul Nat. Univ.) 59th IETF, NEMO WG.
Ασύρματες και Κινητές Επικοινωνίες Ενότητα # 10: Mobile Network Layer: Mobile IP Διδάσκων: Βασίλειος Σύρης Τμήμα: Πληροφορικής.
MEXT Deliverable status IETF 71. Deliverables (I) Dec 2007Submit I-D 'Mobile IPv6 Dual-Stack Operation' to IESG –draft-ietf-mip6-nemo-v4traversal-06 –WGLC.
GEONET Brainstorming Document. Content Purpose of the document Brainstorming process / plan Proposed charter Assumptions Use cases Problem description.
Network Mobility (NEMO) Advanced Internet 2004 Fall
2003/3/1856th IETF NEMO WG1 Basic Network Mobility Support draft-wakikawa-nemo-basic-00.txt Ryuji Wakikawa Keisuke Uehara
1 MIP6-IETF63 Mobility for IPv6 [MIP6] Tuesday, August 2, Afternoon Session II & Afternoon Session III IETF63 Chair(s): Basavaraj.
Strawman Recharter Nov 12, Basic Problem “The purpose of this working group is to standardize IP routing protocol functionality suitable for wireless.
GEONET Brainstorming Document. Content Purpose of the document Brainstorming process / plan Proposed charter Assumptions Use cases Problem description.
63rd IETF - Monami6 BoF1 NEMO Multihoming Issues for Monami6 NEMO Multihoming Issues for Monami6 draft-ietf-nemo-multihoming-issues-03.txt Chan-Wah Ng.
IETF-70 in Vancouver1 STANDARDIZATION OF SOLUTIONS Behcet Sarikaya Huawei Research.
NEMO RO Use Case, Issues & Requirements in the MANEMO Scenarios.
th IETF NEMO WG 1 NEMO RO Problem Space Prepared for 55 th IETF By Pascal Thubert (Cisco), Ng Chan Wah & Takeshi Tanaka (Panasonic)
1 IPv6 and Mobile IPv6 For Mobile Networks Hesham Soliman Director, Elevate Technologies Octorber 2012.
Mobile IP THE 12 TH MEETING. Mobile IP  Incorporation of mobile users in the network.  Cellular system (e.g., GSM) started with mobility in mind. 
V4 traversal for IPv6 mobility protocols - Scenarios Mip6trans Design Team MIP6 and NEMO WGs, IETF 63.
1 Charter 2.0 chairs. 2 Description of Working Group The Working Group will focus on enabling IPv6 over the TSCH mode of the.
BANANA BOF Scope & Problem Description
Telematics Protocols and Technologies
Booting up on the Home Link
Route Optimization of Mobile IP over IPv4
MANEMO Applicability of existing mechanism
Support for Flow bindings in MIPv6 and NEMO
Instructor Materials Chapter 9: NAT for IPv4
Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made.
L1VPN Working Group Scope
Routing and Switching Essentials v6.0
IETF67 B. Patil, Gopal D., S. Gundavelli, K. Chowdhury
CONEX BoF.
BANANA BOF Scope & Problem Description
Network Virtualization
Instructor Materials Chapter 9: NAT for IPv4
Summary of the InternetCAR testbeds
Chapter 11: Network Address Translation for IPv4
Mobile IP Outline Homework #4 Solutions Intro to mobile IP Operation
Mobile IP Outline Intro to mobile IP Operation Problems with mobility.
Presentation transcript:

Thierry Ernst (INRIA and WIDE) Hesham Soliman (Ericsson) NEMO WG Charter Thierry Ernst (INRIA and WIDE) Hesham Soliman (Ericsson)

Mailing List and Web Page Mailing Lists: nemo@nal.motlabs.com How to Subscribe: http://www.nal.motlabs.com/mailman/listinfo/nemo Archives: Discussion prior to WG formation also available (see tar file) Additional Web Page http://www.nal.motlabs.com/nemo/

Description of WG 1/3 The NEMO Working Group is concerned with managing the mobility of an entire network, viewed as a single unit, which changes its point of attachment to the Internet and thus its reachability in the topology. The mobile network is moving as a unit, and includes one or more mobile routers (MRs) which connect it to the global Internet. A mobile network is assumed to be a leaf network, i.e. it will not carry transit traffic. However,it could be multihomed, either with a single MR that has multiple attachments to the internet, or by using multiple MRs that attach the Nemo to the Internet. Initially, the WG will assume that none of the nodes behind the MR will be aware of the network's mobility, thus the network's movement needs to be completely transparent to the nodes inside the mobile network. This assumption will be made to accomodate nodes inside the network that are not generally aware of mobility. A basic approach for Nemo is for each Mobile Router to have a Home Agent, and use bidirectional tunneling between the MR and HA to preserve session continuity while the MR moves. The MR will acquire a Care-of-address from its attachment point much like what is done for Mobile Nodes using Mobile IP. This approach allows nesting of Nemos, since each MR will appear to its attachment point as a single node. The WG will take a stepwise approach by standardizing some basic support based on the bidirectional tunneling approach, and at the same time study the possible approaches and issues with providing more optimal routing than can be had with (potentially nested) tunneling. However, the WG is not chartered to actually standardize a solution to such route optimization for mobile networks at this point in time.

Description of WG 2/3 The WG will work on: A threat analysis and security solution for the basic problem (tunneling between HA and MR) A solution to the basic problem for both IPv4 and IPv6. The solution will allow all nodes in the mobile network to be reachable via permanent IP addresses, as well as maintain ongoing sessions as the MR changes its point of attachment within the topology. This will be done by maintaining a bidirectional tunnel between the MR and its Home Agent. The WG will investigate reusing the existing Mobile IPv6 mechanisms for the tunnel management, or extend it if deemed necessary. An informational document which specifies a detailed problem statement for route optimization and looks at various approaches to solving this problem. This document will look into the issues and tradeoffs involved in making the network's movement visible to some nodes, by optionally making them "NEMO aware". The interaction between route optimization and IP routing will also be described in this document. Furthermore, security considerations for the various approaches will also be considered.

Description of WG 3/3 The WG WILL: Ensure that solutions will scale and function for the different mobile network configurations, without requiring changes to Correspondent Nodes in the Internet. All solutions will aim at preserving route aggregation within the Internet and will satisfy an acceptable level of security (a thorough survey of new threats and an analysis of their severity will be conducted) Ensure that various mechanisms defined within other IETF WGs will be useful for mobile networks. To achieve this, the NEMO WG will interact with other WGs when needed, and may place requirements on the protocols developed by those WGs. The WG WILL NOT: Consider routing issues inside the mobile network. Existing routing protocols (including MANET protocols) can be used to solve these problems.

NEMO Charter: Summary Stepwise Approach Basic Support Extended Support Maintain session continuity to all MNNs Bidirectional tunnel between MR and HA Extended Support Optimal routing between arbitrary CNs and MNNs Requires more investigation in the solution space

Charter: Changes since BOF at Yokohama The WG will first define an informal document describing the terminology and the requirements Then, will propose a solution for Basic Support The group is not chartered to actually produce a solution for the routing optimization problem The WG will investigate the problem scope and potential solutions Not only MIP-like, but also routing protocols, etc Output: an informational document Then, we will decide what to do next based on this document

NEMO Charter: Basic Support Objective: Maintain session continuity to all MNNs Tradeoff Not optimal solution, but guarantee mobile networks are supported quickly with minimal work, and transparently to MNNs. Solution: Mobile-IP like Bidirectional tunnel between HA and MR HA Internet MR AR MR

Goals and Milestones DEC 02 FEB 03 APR 03 JUL 03 DEC 03 FEB 04 Submit terminology and requirements documents (for Basic support). FEB 03   Submit Threat analysis and security requirements for NEMO. APR 03   Submit solution for basic support to IESG. JUL 03   Submit MIB for Basic support to the IESG. DEC 03   Submit the analysis of the solution space for route optimization. FEB 04   Shut down or recharter the WG to solve the route optimization.