IETF Logo Mail Archive

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

Behcet Sarikaya <sarikaya2012@gmail.com> Thu, 17 July 2014 20:19 UTC

Return-Path: <sarikaya2012@gmail.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 E1C491A017C for <dmm@ietfa.amsl.com>; Thu, 17 Jul 2014 13:19:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
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 EdrA8LUjxKDM for <dmm@ietfa.amsl.com>; Thu, 17 Jul 2014 13:19:52 -0700 (PDT)
Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5F751A00AA for <dmm@ietf.org>; Thu, 17 Jul 2014 13:19:51 -0700 (PDT)
Received: by mail-la0-f42.google.com with SMTP id pv20so1660106lab.1 for <dmm@ietf.org>; Thu, 17 Jul 2014 13:19:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=dC+dFxcCJUAm4poG1JfGbJFKoJSZUPrUCC8UYuQLpX8=; b=rdCNnMuHI3FwapOJv4veJ8AXzGW++DjQgmLLV7tpQa1yYcRy6n+dpXF3Wn9CcSWPHe iE6cXDZYT35QHBwPLN6y+ai8cj+/gqoSK1ydbuW0Yz6DXLLfxNGr363gyYeQ8SFIPJBy 7HskHmGduwx9O1AWRT9ImEzQbOKgTeTsXrryO1Yfgv46U7kWVLduCklLnCCLNpFclEsV ddnIoappdmIuWYuRRgNHiubhB4nKLossivnqMgJzCOKvptlIo+0qSj4qnJuu/ktZX9QW ttoNaf/2FsyS1ObTYC5zVuEc+HJFi+kGnBfuYdV8Mi7k2QYRJdXBd76LZAim2ufJPFEy xzMw==
MIME-Version: 1.0
X-Received: by 10.152.8.165 with SMTP id s5mr6661373laa.80.1405628389990; Thu, 17 Jul 2014 13:19:49 -0700 (PDT)
Received: by 10.114.27.106 with HTTP; Thu, 17 Jul 2014 13:19:49 -0700 (PDT)
In-Reply-To: <9C78CA64-928B-4B65-BAB2-2D5AB84BBA0C@yegin.org>
References: <CFED5F60.14EE14%sgundave@cisco.com> <9C78CA64-928B-4B65-BAB2-2D5AB84BBA0C@yegin.org>
Date: Thu, 17 Jul 2014 15:19:49 -0500
Message-ID: <CAC8QAccPCF2BFQ_YhkVDiUaY9xBEs2WZGLyHMT8vWQy5NOA-pA@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Alper Yegin <alper.yegin@yegin.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/MJDoyn1LyCsVDTZlAd9qfCGZkA0
Cc: "dmm@ietf.org" <dmm@ietf.org>
Subject: Re: [DMM] WG adoption (was Re: DMM solution space)
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
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 20:19:53 -0000

Hi Alper,

draft-sarikaya-dmm-for-wifi-
00.txt does not use anchoring, I don't know how many times I should tell?

It simply extends vEPC, so it should be classified wherever vEPC is
classified, and I don't care where.

Regards,

Behcet

On Thu, Jul 17, 2014 at 2:45 PM, Alper Yegin <alper.yegin@yegin.org> wrote:
>
> On Jul 17, 2014, at 9:11 PM, Sri Gundavelli (sgundave) wrote:
>
> I'm in favor of this approach. This was my suggestion as well in the past
> (when we presented prefix coloring spec) to move forward some documents.
> But, those should be documents which are considered common across multiple
> solution approaches.
>
>
> Obviously. And that's the case in this particular instance.
>
> Recapping the DMM solution space analysis below.
>
>
> 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
>
>
>
>
> Alper
>
>
>
> The issue seems to be charter approval.
>
>
>
>
> Sri
>
>
> On 7/17/14 11:04 AM, "Alper Yegin" <alper.yegin@yegin.org> wrote:
>
>
> Why? Why not make technical progress at every opportunity?
>
> This extreme serialization and every step overly stretchingŠ. am I the
>
> only one having issue with the slow progress?
>
>
> Alper
>
>
>
>
>
>
> _______________________________________________
> dmm mailing list
> dmm@ietf.org
> https://www.ietf.org/mailman/listinfo/dmm
>

v2.23.0 | Report a Bug | By Email