IETF Logo Mail Archive

Re: [DMM] DMM solution space

"Templin, Fred L" <Fred.L.Templin@boeing.com> Mon, 14 July 2014 15:59 UTC

Return-Path: <Fred.L.Templin@boeing.com>
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 B7C221A0AB1 for <dmm@ietfa.amsl.com>; Mon, 14 Jul 2014 08:59:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.851
X-Spam-Level:
X-Spam-Status: No, score=-4.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_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 q9rOoCIfzWw3 for <dmm@ietfa.amsl.com>; Mon, 14 Jul 2014 08:59:30 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 923601A0AAE for <dmm@ietf.org>; Mon, 14 Jul 2014 08:59:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s6EFxTQA023014; Mon, 14 Jul 2014 10:59:29 -0500
Received: from XCH-PHX-109.sw.nos.boeing.com (xch-phx-109.sw.nos.boeing.com [130.247.25.36]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s6EFxLek022374 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Mon, 14 Jul 2014 10:59:21 -0500
Received: from XCH-BLV-302.nw.nos.boeing.com (2002:82f7:19d6::82f7:19d6) by XCH-PHX-109.sw.nos.boeing.com (2002:82f7:1924::82f7:1924) with Microsoft SMTP Server (TLS) id 14.3.181.6; Mon, 14 Jul 2014 08:59:20 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.173]) by XCH-BLV-302.nw.nos.boeing.com ([169.254.2.128]) with mapi id 14.03.0181.006; Mon, 14 Jul 2014 08:59:20 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Alper Yegin <alper.yegin@yegin.org>, "dmm@ietf.org" <dmm@ietf.org>
Thread-Topic: [DMM] DMM solution space
Thread-Index: AQHPncJo17mvT/6IhEC+2tyYNXVsV5ufvKUg
Date: Mon, 14 Jul 2014 15:59:20 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832CC7B33@XCH-BLV-504.nw.nos.boeing.com>
References: <EFF03114-39B2-4B5F-846E-4B43171D45B8@yegin.org>
In-Reply-To: <EFF03114-39B2-4B5F-846E-4B43171D45B8@yegin.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.247.104.6]
Content-Type: multipart/alternative; boundary="_000_2134F8430051B64F815C691A62D9831832CC7B33XCHBLV504nwnosb_"
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/E8bZGqSxYuf23jqd7ZL5Q_35OAE
Subject: Re: [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: Mon, 14 Jul 2014 15:59:34 -0000

Hi Alper,

Please add AERO to your list:

draft-templin-aerolink-29

To categorize, I would say the best fit is "Corresponding node/network anchoring",
but AERO also handles mobile networks and not just mobile hosts.

Thanks - Fred

From: dmm [mailto:dmm-bounces@ietf.org] On Behalf Of Alper Yegin
Sent: Saturday, July 12, 2014 4:13 AM
To: dmm@ietf.org
Subject: [DMM] DMM solution space

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

v2.23.0 | Report a Bug | By Email