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

"Templin, Fred L" <Fred.L.Templin@boeing.com> Mon, 08 September 2014 14:28 UTC

Return-Path: <Fred.L.Templin@boeing.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 BEF551A883F for <dmm@ietfa.amsl.com>; Mon, 8 Sep 2014 07:28:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.853
X-Spam-Level:
X-Spam-Status: No, score=-5.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.652, 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 k9QnMtDoazhe for <dmm@ietfa.amsl.com>; Mon, 8 Sep 2014 07:28:57 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D3C11A8837 for <dmm@ietf.org>; Mon, 8 Sep 2014 07:28:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s88ESu5s032315; Mon, 8 Sep 2014 09:28:56 -0500
Received: from XCH-BLV-306.nw.nos.boeing.com (xch-blv-306.nw.nos.boeing.com [130.247.25.218]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s88ESkSw032199 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Mon, 8 Sep 2014 09:28:47 -0500
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.62]) by XCH-BLV-306.nw.nos.boeing.com ([169.254.6.59]) with mapi id 14.03.0181.006; Mon, 8 Sep 2014 07:28:45 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Alper Yegin <alper.yegin@yegin.org>, Charlie Perkins <charles.perkins@earthlink.net>
Thread-Topic: [DMM] MIP and GTP (was Re: regarding the re-chartering..)
Thread-Index: AQHPybpWBou3up9he0+Sft4fJwV685v3TmPg
Date: Mon, 08 Sep 2014 14:28:44 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832D11CEC@XCH-BLV-504.nw.nos.boeing.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>
In-Reply-To: <25086374-11E8-45F6-B20F-428897C50DA7@yegin.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/Hoi6wBGROruXU6O54QBKMMdZCm0
Cc: "dmm@ietf.org" <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: Mon, 08 Sep 2014 14:28:58 -0000

Hi Alper, Charlie,

> -----Original Message-----
> From: dmm [mailto:dmm-bounces@ietf.org] On Behalf Of Alper Yegin
> Sent: Saturday, September 06, 2014 3:06 AM
> To: Charlie Perkins
> Cc: dmm@ietf.org
> Subject: [DMM] MIP and GTP (was Re: regarding the re-chartering..)
> 
> 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.

At the risk of saying "me too", AERO would work fine with GTP as
well, using AERO control plane signaling. AERO works over any
tunnel type that supports IP-in-*-in-IP encapsulation.

Thanks - Fred
fred.l.templin@boeing.com
 
> 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