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

Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 04 September 2014 11:07 UTC

Return-Path: <alexandru.petrescu@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 6E5981A6F8A for <dmm@ietfa.amsl.com>; Thu, 4 Sep 2014 04:07:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level:
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 bfIcWDLPW2XZ for <dmm@ietfa.amsl.com>; Thu, 4 Sep 2014 04:07:36 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6F1A1A6F29 for <dmm@ietf.org>; Thu, 4 Sep 2014 04:07:34 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id s84B7Wit023531; Thu, 4 Sep 2014 13:07:32 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id AC10B2026E3; Thu, 4 Sep 2014 13:07:46 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id A0971200F5A; Thu, 4 Sep 2014 13:07:46 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id s84B7V40019531; Thu, 4 Sep 2014 13:07:31 +0200
Message-ID: <540847F3.2000202@gmail.com>
Date: Thu, 04 Sep 2014 13:07:31 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.1.0
MIME-Version: 1.0
To: Jouni <jouni.nospam@gmail.com>
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> <9E4649D6-84B1-40C3-B659-15C28B9F01C8@gmail.com>
In-Reply-To: <9E4649D6-84B1-40C3-B659-15C28B9F01C8@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/OcCd4pUAX9AD0U--GcAuV-AZn28
Cc: dmm@ietf.org
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: Thu, 04 Sep 2014 11:07:46 -0000

Le 04/09/2014 12:31, Jouni a écrit :
[...]
>> 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.
>
> There are LTE deployments using PMIP. Nation wide even. While not
> hugely popular, there are still serious commercial deployments.

Jouni, I would truly appreciate to stand corrected because it would be a 
good example to tell other customers about the technology.

But I am afraid that what you are saying is part of: the trials, the 
projects, the kernel code and not least the slideware attracting real 
customers.

The nation-wide LTE IPv6 trial I am familiar with does not use PMIPv6.

Alex

>
>> 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.
>
> DMM solutions are not predefined to be a (P)MIP extensions.
>
> - Jouni
>
>>
>> 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
>
>
>