[DMM] WG adoption (was Re: DMM solution space)

Alper Yegin <alper.yegin@yegin.org> Thu, 17 July 2014 06:19 UTC

Return-Path: <alper.yegin@yegin.org>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22ECF1A0356 for <dmm@ietfa.amsl.com>; Wed, 16 Jul 2014 23:19:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kh9f__PWIrbB for <dmm@ietfa.amsl.com>; Wed, 16 Jul 2014 23:19:56 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.197]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64A121A0345 for <dmm@ietf.org>; Wed, 16 Jul 2014 23:19:56 -0700 (PDT)
Received: from [192.168.2.49] (88.247.135.202.static.ttnet.com.tr [88.247.135.202]) by mrelay.perfora.net (node=mreueus001) with ESMTP (Nemesis) id 0Lebpg-1WmKKn2Vt0-00qVCd; Thu, 17 Jul 2014 08:19:55 +0200
From: Alper Yegin <alper.yegin@yegin.org>
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_B4867854-2FBB-4E29-9E77-8442EA8B0D3C"
Date: Thu, 17 Jul 2014 09:19:49 +0300
In-Reply-To: <EFF03114-39B2-4B5F-846E-4B43171D45B8@yegin.org>
To: dmm@ietf.org
References: <EFF03114-39B2-4B5F-846E-4B43171D45B8@yegin.org>
Message-Id: <0062BE8D-4A23-4DFC-BC71-3AF1D645EA02@yegin.org>
X-Mailer: Apple Mail (2.1283)
X-Provags-ID: V02:K0:WKf75IqFjLFq6ez1/BcY4O53TwOefjCWhyoOSGxtgbj iIRWVDdz61vnDnAJRG3WPP7czX8n3V8b8nPh7TN+Cz+O5E2mr0 mL8YkrnS7KCc2LF+an6p8FUO5E/A7t/KtlTgGgNZ2SYqw/M5Ts WMx5uBqUBF4+8w0GKpAyYlG+9CwBTtTV9ocSq4r+H+/REJKwdS E4doSAMdIq935Ycy7AmXY6scW3NOfal4cPhKTinPJL146jrDDw GkyJy2vCsI8bbT0i23+SrkNMCpAwLtCVDiE7A4uu4fYfWELbpX d8xrvhaLxHs6+tPo/GgfVcJj8toZXwlEtIcTFL/AECaPwgXCza oMPqf/QSma7RVTSs5ZB4Ownkocx5u9rIdqhtJM+V2JPM5h59Lx k0/o9u9sR6IhQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/Z2nIOprjRGmua9t_ym6J9P431fE
Subject: [DMM] WG adoption (was Re: DMM solution space)
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jul 2014 06:19:58 -0000

Folks,

Let's change gears.

We'd like to propose draft-yegin-dmm-ondemand-mobility-02 for WG adoption.

This draft falls under the following deliverable:

        Exposing mobility state to mobile nodes and network nodes:
        define solutions that allow, for example, mobile nodes to select
        either a care-of address or a home address depending on an
        application' mobility needs. In order to enable this
        functionality, the network side control functions and other
        networking nodes must also be able to exchange appropriate
        control information, as well as to the mobile nodes and their
        applications.


Comments welcome.

Alper



Behcet/Fred: I've updated the list with your input.


- Per-flow IP address configuration according to mobility needs

Apps indicating their mobility needs to the IP stack on the MN, and associated IP configuration signaling between the MN and the network.

draft-bhandari-dhc-class-based-prefix-03
draft-korhonen-dmm-prefix-properties-00.txt
draft-yegin-dmm-ondemand-mobility-02

- Mobility solution selection 

MN determining the type of mobility solution(s) it'd apply to a given flow.

draft-yegin-ip-mobility-orchestrator-00

- IP anchor selection

MN selecting the IP anchor node after it decides to use IP anchoring (whether in the access network or the core network).

draft-aliahmad-dmm-anchor-selection-00.txt


- Access network anchoring

Anchoring IP address within the access network using IP-in-IP tunneling.

draft-bernardos-dmm-cmip-01
draft-bernardos-dmm-pmip-03
draft-bernardos-dmm-distributed-anchoring-04
draft-chan-dmm-enhanced-mobility-anchoring-00
draft-sarikaya-dmm-for-wifi-00.txt
draft-seite-dmm-dma-07.txt
draft-xuan-dmm-nemo-dmm-02.txt


- Corresponding node/network anchoring

Anchoring IP address on the Corresponding Node or Corresponding Network.

Mobile IPv6 route optimization
draft-yegin-dmm-cnet-homing-02
draft-xiong-dmm-ip-reachability-01
draft-templin-aerolink-29

- Host-route based intra-domain solutions

Non-tunneling solutions.

draft-chan-dmm-enhanced-mobility-anchoring-00
draft-matsushima-stateless-uplane-vepc-02
draft-mccann-dmm-flatarch-00
draft-sarikaya-dmm-for-wifi-00.txt