IETF Logo Mail Archive

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

Alper Yegin <alper.yegin@yegin.org> Fri, 05 September 2014 08:49 UTC

Return-Path: <alper.yegin@yegin.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 9A26F1A04A4 for <dmm@ietfa.amsl.com>; Fri, 5 Sep 2014 01:49:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] 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 ViBPHAfcyWnT for <dmm@ietfa.amsl.com>; Fri, 5 Sep 2014 01:49:00 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B4121A007F for <dmm@ietf.org>; Fri, 5 Sep 2014 01:49:00 -0700 (PDT)
Received: from [192.168.2.49] (88.247.135.202.static.ttnet.com.tr [88.247.135.202]) by mrelay.perfora.net (node=mreueus003) with ESMTP (Nemesis) id 0Mbzhw-1Xj0k52HTC-00JI4j; Fri, 05 Sep 2014 10:48:59 +0200
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset="windows-1252"
From: Alper Yegin <alper.yegin@yegin.org>
In-Reply-To: <54083B6C.5010701@gmail.com>
Date: Fri, 05 Sep 2014 11:48:53 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <F51A5BB8-0B0D-4F77-B354-A22B3171D8B9@yegin.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>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.1283)
X-Provags-ID: V02:K0:hUZUiXgRVde6IpS0jImBZVJDAYRNfXTZoaX5gDRQlqb 0/3dXaX0qukNJctpmHykh0hHULe2cLwgaTHsEkP4UjGlVJ8ejD XDiQsgp877aEuGDJhppz3ymg99OUAUQ5WyyA4jPX+BOICD8UYQ gXVY+xFUNYXHLWIvmt5AvmRrA+e87C7fvpwTwGJ8CI2DawunJ7 QRnRy+UrbnOiZRO1AlSkTGLzgm6UuXfdzaxJazDH/2OiD+dPfQ U3Z/Gy1n2v6Z/iHlgdEAIh5m4lxys2Q+R8e46HWjkzW/NGPpCp PpiQ5slqQpkBXBphyoq2VnBurwHm2nUE8L6QpsT072KKOakKS2 bdX21HN1VM7zc2bsQV+Tk0u90ur5jdZFnA0Sll0kAuLCbsvmvt uCqP3fEVcWRXw==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/6X6dphxmjcpiQHW7PT-PbDVRpGQ
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: Fri, 05 Sep 2014 08:49:02 -0000

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

v2.23.0 | Report a Bug | By Email