IETF Logo Mail Archive

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

Jouni Korhonen <jouni.nospam@gmail.com> Thu, 17 July 2014 21:22 UTC

Return-Path: <jouni.nospam@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 7FA371B27FF for <dmm@ietfa.amsl.com>; Thu, 17 Jul 2014 14:22:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 nNcruAszXSE7 for <dmm@ietfa.amsl.com>; Thu, 17 Jul 2014 14:22:49 -0700 (PDT)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0DE991B2802 for <dmm@ietf.org>; Thu, 17 Jul 2014 14:22:49 -0700 (PDT)
Received: by mail-pa0-f53.google.com with SMTP id kq14so4100007pab.12 for <dmm@ietf.org>; Thu, 17 Jul 2014 14:22:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=mrA/eUQAMz4vPZ/qf4xcn43tToy63gXYX3MJpw1W51g=; b=iWMLLUF/7FJBwYdFYdZedX8CZQqo48PytvYNpeUBTQPZtWHtCW+uNwfdiuV07EC8x6 NIWbQxW4utOp5ch7H5+BUySTGzjHPa/rzxq1zizUwJ+31xRiccbGkD2duY2Dgvm2OtHw ixo7YIdIfjPqWnDI/QTn5FSwfvFfH0L1HP1O9V1ubhiWhKk/kY0Usf9fwcJ/CNyLKinj a7tPye+n1hD4VLJ1Lwp1BbkBXBlPaYDHJIIn0/Xt5oAQmtuIQXshoSE7ejI1diKINIx/ D2oTSvuV0krbwoeRXaUN6jhfR2yer9WjTPe/k8aAO6DKcdsXlBfJ2un1jLqk2qa8Z0fz Rt6Q==
X-Received: by 10.70.94.100 with SMTP id db4mr33648pdb.122.1405632167800; Thu, 17 Jul 2014 14:22:47 -0700 (PDT)
Received: from [10.100.20.19] ([63.133.199.244]) by mx.google.com with ESMTPSA id mj9sm14490528pab.20.2014.07.17.14.22.46 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Jul 2014 14:22:46 -0700 (PDT)
Message-ID: <53C83EA5.4060402@gmail.com>
Date: Fri, 18 Jul 2014 00:22:45 +0300
From: Jouni Korhonen <jouni.nospam@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Alper Yegin <alper.yegin@yegin.org>, "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
References: <CFED5F60.14EE14%sgundave@cisco.com> <9C78CA64-928B-4B65-BAB2-2D5AB84BBA0C@yegin.org>
In-Reply-To: <9C78CA64-928B-4B65-BAB2-2D5AB84BBA0C@yegin.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/xvQfBYiLFVT-Fyyrp_S79uLt_50
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
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 21:22:50 -0000

The list is still missing draft-korhonen-dmm-local-prefix-01.

- Jouni

7/17/2014 10:45 PM, Alper Yegin kirjoitti:
>
> 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
>> <mailto: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
>>>
>>>
>>
>

v2.23.0 | Report a Bug | By Email