Re: [DMM] regarding the re-chartering..

"MONGAZON-CAZAVET, BRUNO (BRUNO)" <bruno.mongazon-cazavet@alcatel-lucent.com> Mon, 08 September 2014 06:57 UTC

Return-Path: <bruno.mongazon-cazavet@alcatel-lucent.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 5E79D1A6F2B for <dmm@ietfa.amsl.com>; Sun, 7 Sep 2014 23:57:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.653
X-Spam-Level:
X-Spam-Status: No, score=-1.653 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RP_MATCHES_RCVD=-1.652] 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 LdJ9cnilhfTd for <dmm@ietfa.amsl.com>; Sun, 7 Sep 2014 23:57:47 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpgre-esg-02.alcatel-lucent.com [135.245.210.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A29681A6F2A for <dmm@ietf.org>; Sun, 7 Sep 2014 23:57:47 -0700 (PDT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (unknown [135.239.2.122]) by Websense Email Security Gateway with ESMTPS id 9568B89B231BD for <dmm@ietf.org>; Mon, 8 Sep 2014 06:57:43 +0000 (GMT)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id s886viWo019922 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dmm@ietf.org>; Mon, 8 Sep 2014 08:57:45 +0200
Received: from [172.27.204.72] (135.239.27.39) by FR711WXCHHUB01.zeu.alcatel-lucent.com (135.239.2.111) with Microsoft SMTP Server (TLS) id 14.2.247.3; Mon, 8 Sep 2014 08:57:44 +0200
Message-ID: <540D5367.2000403@alcatel-lucent.com>
Date: Mon, 08 Sep 2014 08:57:43 +0200
From: "MONGAZON-CAZAVET, BRUNO (BRUNO)" <bruno.mongazon-cazavet@alcatel-lucent.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:26.0) Gecko/20100101 Thunderbird/26.0
MIME-Version: 1.0
To: dmm@ietf.org
References: <53D17F75.3030207@gmail.com> <53D7A012.2050700@gmail.com> <53D8AAE0.4040301@gmail.com> <2E9AF0DF-8B1A-475B-B5FB-ED5E419F0085@yegin.org> <53EB4F10.1040502@gmail.com> <A02C6954-3EC9-443F-ACC3-4A635EC79EFC@yegin.org> <53F35B44.1090808@gmail.com> <1E1DFA1F-8BC5-474B-A792-A8681A99D094@yegin.org> <72DAF3D2-05D9-4A1E-9185-7265AA915075@gmail.com> <CAC8QAcegx1QPATsrPS-v-dkoLbaSTNqE3M+BbrYJPHrCFKMyXA@mail.gmail.com> <5404BC3D.1000406@gmail.com> <CAC8QAccqjXHogC44iOBO5bDccFBRixgcgrQU=hst8ZYGM3Y5xA@mail.gmail.com> <5406A20F.60604@gmail.com> <CAC8QAccBSXSsydagekNHnBbaYvmtTdm=xv5aEE64c+=9X2Fp9w@mail.gmail.com> <5407422F.2010700@innovationslab.net> <CAC8QAcdvdY1Kbys4a=dw9aQ4cUs8cnRcnfaujxm1Fjn6_EAvkg@mail.gmail.com> <54074DAB.9020801@innovationslab.net> <CAC8QAcfVBeToUYYMp1uKTDwx8dGHw5TP2MTTSw8wziepcEZCsw@mail.gmail.com> <540763A0.7080509@innovationslab.net> <54083B6C.5010701@gmail.com> <F51A5BB8-0B0D-4F77-B354-A22B3171D8B9@yegin.org> <5409EE9A.1020700@earthlink.net>
In-Reply-To: <5409EE9A.1020700@earthlink.net>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Originating-IP: [135.239.27.39]
Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/0iX0OWq57wLRd4B6gobN_pAJNFc
Subject: Re: [DMM] regarding the re-chartering..
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, 08 Sep 2014 06:57:49 -0000

On 05/09/2014 19:10, Charlie Perkins wrote:
>
> Hello folks,
>
> I have made various presentations at IETF, some from many years
> ago, proposing that Mobile IP enable use of GTP as a tunneling
> option.  I still think that would be a good idea.  Should I re-re-revive
> a draft stating this in more detail?

I would be interested to look at this draft.
Thanks.
Bruno

>
>
> Regards,
> Charlie P.
>
>
> On 9/5/2014 1:48 AM, Alper Yegin wrote:
>> Alex,
>>
>> DMM is not meant to be only about a bunch of MIP-based solutions.
>> There are various components in DMM solution space that'd also work 
>> with GTP-based architectures.
>> For example, identifying the mobility needs of flows.
>> Or, conveying the mobility characteristic of a prefix to the UE.
>>
>> Alper
>>
>>
>>
>>
>> On Sep 4, 2014, at 1:14 PM, Alexandru Petrescu wrote:
>>
>>> Le 03/09/2014 20:53, Brian Haberman a écrit :
>>>> Behcet,
>>>>
>>>> On 9/3/14 2:33 PM, Behcet Sarikaya wrote:
>>>>> You don't seem to understand my points.
>>>> That is quite possible.  Your comment on the list was "I am against 
>>>> any
>>>> deployment work before we decide on a solution..."
>>>>
>>>> I read that as an objection to having the deployment models work 
>>>> item on
>>>> the agenda.  Please do tell me what I am missing.
>>>>
>>>> Regards,
>>>> Brian
>>> Hi,
>>>
>>> I am following the discussion and me too I do not quite understand 
>>> what is the complain.
>>>
>>> I am happy to learn that a if a WG is to be formed then it would be 
>>> around a solution rather than just requirements or architecture.
>>>
>>> That said, I would like to express a worry along similar lines.
>>>
>>> In DMM, precedents and the keen NETEXT, there seems to be a 
>>> hard-rooted disconnect between the product developped - (P)Mobile IP 
>>> - and the deployments.  We know for a fact that 3GPP deployments 
>>> (2G/3G/4G) do not use (P)Mobile IP.  We also know that 3GPP specs do 
>>> mention Mobile IP. To such a point that I wonder whether 3GPP has 
>>> not the same disconnect as here.
>>>
>>> On another hand, we do have indications of where (P)Mobile IP is 
>>> used - the trials, the projects, the kernel code, and not least the 
>>> slideware attracting real customers.
>>>
>>> The worry: develop DMM protocol while continuing the disconnect.
>>>
>>> Alex
>>>
>>>
>>>
>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>> _______________________________________________
>> 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
>
>