Re: [DMM] MIP and GTP (was Re: regarding the re-chartering..)

Jouni <jouni.nospam@gmail.com> Sat, 06 September 2014 10:15 UTC

Return-Path: <jouni.nospam@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 C5E741A0205 for <dmm@ietfa.amsl.com>; Sat, 6 Sep 2014 03:15:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_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 fnuVEA3P7kf4 for <dmm@ietfa.amsl.com>; Sat, 6 Sep 2014 03:15:57 -0700 (PDT)
Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A40721A004E for <dmm@ietf.org>; Sat, 6 Sep 2014 03:15:56 -0700 (PDT)
Received: by mail-lb0-f180.google.com with SMTP id s7so394862lbd.25 for <dmm@ietf.org>; Sat, 06 Sep 2014 03:15:54 -0700 (PDT)
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; bh=6WYQujFvEzEm8tAMlTaFOtEtJV42wa+ulKShC2X2Fu0=; b=mm4KJK5dzVsqyI6XG6yfhbbzbmcUqoIbl7vedzHFfR3dfBSH7ve64GBGVAtouC/VeE Vl7FngUPoT0t9ud5IIMrPTnFh4pWH0ECDTmZY2gucXsmOqtDSHrjmKTQrGwzrH5J827c vy+TOag3mx6odaq6uNDqkx1tWtCbHKuTg42j4W16NhrBrkfdVtUHKEyPKEL0t+tV7fSm ZRP/W/2w0mI2wU3WJQHl1lPsevCNsIFbRiOqwzbM3qkwP/l4vD3ELtQ+5r3qNkPzZPd5 9N6+G/dd3FMQE7kn5NwFZhfhJxUVj+Zo5SBsKL+0WWwgEXMvqgj829VowqsPsTrL1wCH Vdcg==
X-Received: by 10.112.210.138 with SMTP id mu10mr1655480lbc.81.1409998554882; Sat, 06 Sep 2014 03:15:54 -0700 (PDT)
Received: from [188.117.15.109] ([188.117.15.109]) by mx.google.com with ESMTPSA id y9sm1491118lad.32.2014.09.06.03.15.53 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 06 Sep 2014 03:15:54 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset="windows-1252"
From: Jouni <jouni.nospam@gmail.com>
In-Reply-To: <25086374-11E8-45F6-B20F-428897C50DA7@yegin.org>
Date: Sat, 06 Sep 2014 13:15:52 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <3DCB6C08-05A8-452A-BC24-597011099AA3@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> <F51A5BB8-0B0D-4F77-B354-A22B3171D8B9@yegin.org> <5409EE9A.1020700@earthlink.net> <25086374-11E8-45F6-B20F-428897C50DA7@yegin.org>
To: Alper Yegin <alper.yegin@yegin.org>
X-Mailer: Apple Mail (2.1283)
Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/pDBouLtF3FGbsoIb1fFa0ld0B2U
Cc: Charlie Perkins <charles.perkins@earthlink.net>, dmm@ietf.org
Subject: Re: [DMM] MIP and GTP (was Re: 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: Sat, 06 Sep 2014 10:15:59 -0000

Just to point out that GTP-U also carries control information, which none of the existing *MIP user plane tunnels do not do today.

Regarding GTP-C part, 3GPP TS29.275 has done pretty thorough job already mapping GTPv2-C to PMIP signaling, so using GTP-U instead of GRE or IPIP should be rather straightforward if someone were to do it.

- Jouni

On Sep 6, 2014, at 1:06 PM, Alper Yegin wrote:

> Hi Charlie,
> 
> GTP has its data-plane (GTP-U) and control-plane (GTP-C).
> I think you are talking about using Mobile IP signaling in-place of GTP-C to enable GTP-U.
> If so, I think it'd technically work. But, for adoption by 3GPP standards and deployments, we'd need to make a case for using Mobile IP instead of GTP-C. 
> 
> Alper
> 
> 
> On Sep 5, 2014, at 8:10 PM, 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?
>> 
>> 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