Re: [DMM] Requirements on cmm

Brian Haberman <brian@innovationslab.net> Mon, 19 November 2012 19:53 UTC

Return-Path: <brian@innovationslab.net>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD6AC21F85E6 for <dmm@ietfa.amsl.com>; Mon, 19 Nov 2012 11:53:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hNWDUhfjtcz2 for <dmm@ietfa.amsl.com>; Mon, 19 Nov 2012 11:53:23 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 2063821F8564 for <dmm@ietf.org>; Mon, 19 Nov 2012 11:53:23 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id BD18C88099 for <dmm@ietf.org>; Mon, 19 Nov 2012 11:53:22 -0800 (PST)
Received: from clemson.local (nat-gwifi.jhuapl.edu [128.244.87.132]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 7917F13001B for <dmm@ietf.org>; Mon, 19 Nov 2012 11:53:22 -0800 (PST)
Message-ID: <50AA8E30.1050408@innovationslab.net>
Date: Mon, 19 Nov 2012 14:53:20 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: dmm@ietf.org
References: <CAC8QAce3FmR=G13FOMg6Notgu-d0VreoW5cDcK8Dtmh5rTeX=A@mail.gmail.com> <BC258C85-60C4-498C-8ECC-B979F0F6CB24@mimectl> <CAC8QAceHk3h7MDrvOdK+9bLjPqSZdq8BDP0znOXrFqzfos0H+w@mail.gmail.com>
In-Reply-To: <CAC8QAceHk3h7MDrvOdK+9bLjPqSZdq8BDP0znOXrFqzfos0H+w@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [DMM] Requirements on cmm
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.12
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, 19 Nov 2012 19:53:23 -0000

Behcet,

On 11/19/12 12:25 PM, Behcet Sarikaya wrote:
> Hi all,
>
> Here is the requirement I have in mind:
>
> The DMM solution SHOULD support more than one cloud network belonging
> to the same DMM domain.
>
> Two points:
>
> The above requirement does have protocol impact.

Could you elaborate on what that impact would be?

It is unclear to me what the impact of using a cloud service would be. 
The IETF has not had to change other protocols in order to have them 
work within "the cloud".

Regards,
Brian

>
> Second point: I also support Georgios' requirement as a base. We can
> work on both and make it better.
>
> Regards,
>
> Behcet
>
> On Sat, Nov 17, 2012 at 6:28 AM,  <karagian@cs.utwente.nl> wrote:
>> Hi Behcet, Hi all,
>>
>>
>>
>> Regarding the cloud like architecture use case, the requirement that could
>> be used for this purpose can be the following one:
>>
>>
>>
>> "The DMM solution MAY have the ability to be applied in virtualized and/or
>> cloud like archietctures."
>>
>>
>>
>> Motivation:
>>
>>
>>
>> Currently, there is a trend to implement more and more functions of a mobile
>> communication network in software, e.g., for signal and protocol processing.
>> This enables the use of cloud computing infrastructures as processing
>> platforms for signal and protocol processing of mobile communication
>> networks, in particular for current (4G) and future (5G) generation cellular
>> networks. This can only be realized if, among others, efficient DMM
>> solutions are supported by the cloud computing architectures.
>>
>>
>>
>> Best regards,
>>
>> Georgios
>>
>> ________________________________
>> Van: Behcet Sarikaya [sarikaya2012@gmail.com]
>> Verzonden: vrijdag 16 november 2012 22:20
>> To: Karagiannis, G. (EWI)
>> Cc: dmm@ietf.org
>> Onderwerp: Requirements on cmm
>>
>> Hi Georgios,
>>
>> Can you please suggest some requirements on cmm in DMM?
>>
>> I think that it would be relevant and useful to DMM while requirements
>> are still being discussed.
>>
>> Regards,
>>
>> Behcet
>> On Sun, Nov 4, 2012 at 1:52 PM,  <karagian@cs.utwente.nl> wrote:
>>> Hi Behcet,
>>>
>>> I would like to mention that I find this draft useful due to the following
>>> reasons.
>>>
>>> Currently, there is a trend to implement more and more functions of a
>>> mobile communication network in software, e.g., for signal and protocol
>>> processing. This enables the use of cloud computing infrastructures as
>>> processing platforms for signal and protocol processing of mobile
>>> communication networks, in particular for current (4G) and future (5G)
>>> generation cellular networks.
>>> This can of course only be realized if, among others, efficient mobility
>>> management solutions are supported like the ones that are in line with what
>>> DMM would like to specify.
>>> I think therefore, that the DMM WG could also consider the distributed
>>> mobility management support in cloud computing like architectures as a
>>> possible use case.
>>>
>>> Regarding your draft I have some comments:
>>> The draft mentions some limitation of the existing mobility management
>>> solutions in cloud-like architectures. However, these limitations are not
>>> clearly focussing on the requirements specified in
>>> http://www.ietf.org/id/draft-ietf-dmm-requirements-02.txt.
>>> I think that this will make the desciption of the limitations clearer!
>>> Moreover, it might also be useful to show describe these limitations by
>>> using as use as context a generic framework, like the one introduced in
>>> http://www.ietf.org/id/draft-chan-dmm-framework-gap-analysis-05.txt and/or
>>> http://www.ietf.org/id/draft-liebsch-dmm-framework-analysis-00.txt.
>>>
>>> Best regards,
>>> Georgios
>>>
>>>
>>>
>>>
>>> ________________________________________
>>> Van: dmm-bounces@ietf.org [dmm-bounces@ietf.org] namens Behcet Sarikaya
>>> [sarikaya2012@gmail.com]
>>> Verzonden: dinsdag 23 oktober 2012 21:51
>>> To: dmm@ietf.org
>>> Onderwerp: [DMM] New Version Notification for
>>> draft-sarikaya-dmm-cloud-mm-00.txt
>>>
>>> Hi all,
>>>
>>> I have submitted a new draft on Mobility Management Protocols for
>>> Cloud-Like Architectures, for details see below.
>>>
>>> Chairs: please reserve a slot in IETF 85 session if possible.
>>>
>>> Regards,
>>>
>>> Behcet
>>>
>>> A new version of I-D, draft-sarikaya-dmm-cloud-mm-00.txt
>>> has been successfully submitted by Behcet Sarikaya and posted to the
>>> IETF repository.
>>>
>>> Filename:        draft-sarikaya-dmm-cloud-mm
>>> Revision:        00
>>> Title:           Mobility Management Protocols for Cloud-Like
>>> Architectures
>>> Creation date:   2012-10-15
>>> WG ID:           Individual Submission
>>> Number of pages: 11
>>> URL:
>>> http://www.ietf.org/internet-drafts/draft-sarikaya-dmm-cloud-mm-00.txt
>>> Status:
>>> http://datatracker.ietf.org/doc/draft-sarikaya-dmm-cloud-mm
>>> Htmlized:        http://tools.ietf.org/html/draft-sarikaya-dmm-cloud-mm-00
>>>
>>>
>>> Abstract:
>>>     Telecommunication networks are being virtualized and are moving into
>>>     the cloud networks.  This brings the need to redesign the mobility
>>>     protocols of Mobile and Proxy Mobile IPv6.  This document defines
>>>     mobility management protocols for virtualized networks.  Control and
>>>     data plane separation is achieved by separating Home Agent and Mobile
>>>     Access Gateway functionalities into the control and data planes.
>>>
>>>
>>>
>>>
>>> The IETF Secretariat
>>> _______________________________________________
>>> dmm mailing list
>>> dmm@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dmm
> _______________________________________________
> dmm mailing list
> dmm@ietf.org
> https://www.ietf.org/mailman/listinfo/dmm
>