[DMM] DMM solution space

Alper Yegin <alper.yegin@yegin.org> Sat, 12 July 2014 11:13 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 98DCF1B2A69 for <dmm@ietfa.amsl.com>; Sat, 12 Jul 2014 04:13:35 -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 RTKHxf50i18h for <dmm@ietfa.amsl.com>; Sat, 12 Jul 2014 04:13:33 -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 D57431B2858 for <dmm@ietf.org>; Sat, 12 Jul 2014 04:13:33 -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 0Lz1b4-1WSY4g0a5g-014CQR; Sat, 12 Jul 2014 13:13:32 +0200
From: Alper Yegin <alper.yegin@yegin.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D8BF5195-3300-4FFD-9081-3DA67C3551DD"
Date: Sat, 12 Jul 2014 14:13:29 +0300
Message-Id: <EFF03114-39B2-4B5F-846E-4B43171D45B8@yegin.org>
To: dmm@ietf.org
Mime-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
X-Provags-ID: V02:K0:xMm55/KPyosrjKAMj4hBF1sVFN+qE4pyUtxt7iRk/xC U8UaDV4fIN3KIMLmPa8D4FxCs6D+Q7jUF2/KAHZpqJZqCxZ+dQ MIJm5cydouE3UsnFonX+9Dp2JH8Wsnhfp7xELuK9PsrGYypH3n buYxyQCEL6too0/VphY28TWGfIG2cXHUiqFnPlrUjwhZn3yOj7 eWMWVS9RDSxmu96RfiX7SWV83gwSLdoq1Iv6HEu9c0fb++dDF0 tNbI+ajT0/H2UJtHRZWUT2mdCSitF35ticeEMbNjjUMRSgu+Mv yEQWleP85K+J+U1Zy7xcdV/5+SfRnRztkV4y7S881I1w4Fmv5D 7cizV80dtTaqxaT+6Va6eTEDJZ953VQ2951UhNJqjL9KxPb4EQ NDBHSyOO2BeLQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/f3zFHACxiNZOlHuwweC4Rd01Lkk
Subject: [DMM] 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: Sat, 12 Jul 2014 11:13:35 -0000

Folks,

I went over the solutions and categorized them.

I haven't covered all of the solutions (due to lack of time). For any I-D that is missing, please state the name and where you think it belongs to.

When we agree with the categorization and the candidates for each, then we can proceed to discussing how we can converge. 

Note: Multiple I-Ds under each category may be complementary, competing, or orthogonal (e.g., due to different applicability). It's case by case.


Cheers,



- 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

- 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