Re: [DMM] Requirements on cmm

jouni korhonen <jouni.nospam@gmail.com> Sat, 17 November 2012 23:05 UTC

Return-Path: <jouni.nospam@gmail.com>
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 467F221F84F3 for <dmm@ietfa.amsl.com>; Sat, 17 Nov 2012 15:05:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 jDDNtC3lR7CO for <dmm@ietfa.amsl.com>; Sat, 17 Nov 2012 15:04:59 -0800 (PST)
Received: from mail-ea0-f172.google.com (mail-ea0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1952E21F84F2 for <dmm@ietf.org>; Sat, 17 Nov 2012 15:04:58 -0800 (PST)
Received: by mail-ea0-f172.google.com with SMTP id a1so813819eaa.31 for <dmm@ietf.org>; Sat, 17 Nov 2012 15:04:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=pKOKpT1nzjAkLpO7OWlhACUXb2nbbnNIM4HCjfKllyc=; b=COz0XlYc8sF2qxNeQoyOG/XD7KvhooFBdpkJXI474/NeepCr8ap90YJCyn0wh6e/4u YQcfnsYfnTL6FvcJQ3frgSSg1UGlKBs9mtTnQs57AJdw1Ch0+2n1j6olc1dUPl71wDCw l4df6Ei1aQQJORUAT+XiHV0Ne4F6KvmLNjkcMRrAAqXywK4TVVuiX9EutE7ze5PMLtWH vG31NqsbmGSUAsj/38x8Yglcnpe6tVttW1gYVxfJWbM/zfc4cikCGnTZ44/L2qTY6ckP IIIHGiahhw6dmCwSk1q3BS60yLt3wa3v66s/r487XX2QP7OuVayNXpuW6piiAxu+QYpW GK2Q==
Received: by 10.14.213.7 with SMTP id z7mr9606396eeo.39.1353193498297; Sat, 17 Nov 2012 15:04:58 -0800 (PST)
Received: from ?IPv6:2001:1bc8:101:f101:226:bbff:fe18:6e9c? ([2001:1bc8:101:f101:226:bbff:fe18:6e9c]) by mx.google.com with ESMTPS id 46sm3801156eeg.4.2012.11.17.15.04.53 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 17 Nov 2012 15:04:56 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset="us-ascii"
From: jouni korhonen <jouni.nospam@gmail.com>
In-Reply-To: <BC258C85-60C4-498C-8ECC-B979F0F6CB24@mimectl>
Date: Sun, 18 Nov 2012 01:04:52 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <D0CAD6CF-1748-42F2-BFA0-E94ED4E183E2@gmail.com>
References: <CAC8QAce3FmR=G13FOMg6Notgu-d0VreoW5cDcK8Dtmh5rTeX=A@mail.gmail.com> <BC258C85-60C4-498C-8ECC-B979F0F6CB24@mimectl>
To: karagian@cs.utwente.nl
X-Mailer: Apple Mail (2.1085)
Cc: dmm@ietf.org
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: Sat, 17 Nov 2012 23:05:00 -0000

Hi,

I do not see a reason for this requirement. Give me an example how node/function virtualization would be visible e.g. at the IP mobility protocol level. Many vendors already today virtualize their elements (and call it cloud or something semantically equivalently foggy stuff) and that has not had any impact on the signaling protocols they use on the level of the infrastructure they virtualize.

- Jouni


On Nov 17, 2012, at 2:28 PM, <karagian@cs.utwente.nl> <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