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

"Charles E. Perkins" <charliep@computer.org> Thu, 04 September 2014 10:32 UTC

Return-Path: <charliep@computer.org>
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 1E1B41A7012 for <dmm@ietfa.amsl.com>; Thu, 4 Sep 2014 03:32:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no
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 OT4DNcB-GAXw for <dmm@ietfa.amsl.com>; Thu, 4 Sep 2014 03:32:05 -0700 (PDT)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) by ietfa.amsl.com (Postfix) with ESMTP id 0463B1A6F27 for <dmm@ietf.org>; Thu, 4 Sep 2014 03:32:05 -0700 (PDT)
Received: from [122.55.93.140] (helo=[172.22.35.120]) by elasmtp-galgo.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charliep@computer.org>) id 1XPUKh-0005si-Ub; Thu, 04 Sep 2014 06:32:04 -0400
Message-ID: <54083F9A.8030507@computer.org>
Date: Thu, 04 Sep 2014 03:31:54 -0700
From: "Charles E. Perkins" <charliep@computer.org>
Organization: Blue Skies
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.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>
In-Reply-To: <54083B6C.5010701@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac71475dce8af98524d0ecc5fdae058dd0b350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 122.55.93.140
Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/3SRL1I_BGhpYHVVfV1w2IpcZQhA
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 10:32:06 -0000

Hello folks,

I have asked this same question many times, in different words...

Namely, if we design a solution that fits the requirements, and bridges
the gaps as analyzed in the gap analysis document, have we succeeded?

Or, is there a requirement for the work to be adopted by 3GPP?

What if we design for IEEE 802 Wireless, which is currently carrying the
preponderance of the world's wireless data, and will almost assuredly
continue to carry a greater proportion?

Regards
Charlie P.



On 9/4/2014 3:14 AM, Alexandru Petrescu wrote:
>
> Hi,
>
> ....
>
> 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
>


-- 
Regards,
Charlie P.