Re: [v6ops] GTP questions

Ca By <cb.list6@gmail.com> Sun, 12 November 2017 15:05 UTC

Return-Path: <cb.list6@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89A8B129458 for <v6ops@ietfa.amsl.com>; Sun, 12 Nov 2017 07:05:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 pFCJuVyEmbBo for <v6ops@ietfa.amsl.com>; Sun, 12 Nov 2017 07:04:55 -0800 (PST)
Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB1561200E5 for <v6ops@ietf.org>; Sun, 12 Nov 2017 07:04:53 -0800 (PST)
Received: by mail-yw0-x235.google.com with SMTP id k191so3162093ywe.1 for <v6ops@ietf.org>; Sun, 12 Nov 2017 07:04:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=viN7NhWFZD/x0VYhyw/Yj7uH45xdyqkjadloaFWvEu0=; b=OqLdMYsHYUupZbwnz2gJ5ZaYWzSSR6YttXZ7bZP1rbgYJY8anDQ0cJRcjgBbQAO7AP Jru1nLeP3arZ0iLOG+c+tzUgWF7twvUQWTtbfSYLTvLvWgbOxAymxdrulLWtbHXvirS0 ruIugTOXgwarj9mA0188mjVGTjFE4+0YvOX8xxe3OzPhL1MCkpOYkQmnyeGiLjS7MFvG IwFQj4LacmKpi+eq3Chmtu8iz2wZ7WwMIz0XXh2yadrQuZNklBNt8L1DtP4NPvdxxhaA UdmIvrrnbBKSpfvh50VbB7DTZZLkseJkWzbzgjdqysrad/ggbaCAFG7YixzgMbttzzXn Ym5w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=viN7NhWFZD/x0VYhyw/Yj7uH45xdyqkjadloaFWvEu0=; b=ZdiS1h1f4F4SokjjAU6YX3+0Zi2fxseaKq6KNFN0fcnDIOPFIFP3Iv9xyhbXkYWue2 Vk8hPAmkD9ErF9Tj/LkbtaSYpY1FCoXLYrwy5rw/e0mytDUPEi1b67LY3UNaXYqDkJpl J+Wnah1/6+u9fHWY5aeq7VUmluHnBHarGjr5zFhskdf9Jm6yOqKg6ONh7aJj393o4HNj jnh193cuf4oJO/bbcA0Kk6RkJoz9YfMZJCtjD1Hfpi3XfQFvXiMNfBpalcjWtNIwHS+g zwnp6+B36/QWeHjyxtIBp8Zk0kWbB/W2egsffrYer4JIncM6g2QNirxQykN7ZtwgBBZD Wb4A==
X-Gm-Message-State: AJaThX6Rn20HpbOGZIQ7lnaSCk3pDhnVYlu0koPZjQUpCOVI0cxJxGEg Bn2sYO6cu3lnmgURvlm0nkFlCkJPUFSSe2Je9FI=
X-Google-Smtp-Source: AGs4zMZey2+XoH2c9dD1O7jeBTXnzMo3m8xDa1/X5hhy6QtEEwpoxT1tpm/k9jJGYX09XnEqBYuEhN/spJff+6/ZByQ=
X-Received: by 10.129.65.69 with SMTP id f5mr4399360ywk.470.1510499092919; Sun, 12 Nov 2017 07:04:52 -0800 (PST)
MIME-Version: 1.0
References: <LO1P123MB01168388285206BB7C26F029EA7A0@LO1P123MB0116.GBRP123.PROD.OUTLOOK.COM> <CAKD1Yr3vziaHfkR+hQ7QHXaz7QraKH2HLUVXUW63GpnOAj4JoQ@mail.gmail.com> <E72C3FBE-57A4-4058-B9E5-F7392C9E9101@google.com> <LO1P123MB0116805F9A18932E2D0694FEEA780@LO1P123MB0116.GBRP123.PROD.OUTLOOK.COM> <1496304E-54BE-47FA-A7F1-1AA6E163DAB1@employees.org> <CAD6AjGQdMFgv4727wHm41HmEyo2Z-PCabPHPSRSVwOi_rey7OQ@mail.gmail.com> <CAKD1Yr03zsuSBqPegs6RNbBqnJizUOLZwH+rNDi1Ocg4k+mARQ@mail.gmail.com> <20170928030630.DD2D08867238@rock.dv.isc.org> <alpine.DEB.2.20.1709280753080.18564@uplift.swm.pp.se> <20170928074105.BCB99886E538@rock.dv.isc.org> <alpine.DEB.2.20.1709280955490.18564@uplift.swm.pp.se> <20170928081527.21D9F886EF0C@rock.dv.isc.org> <CAAedzxqRar=X6c6WJNOWtKA3S6Dx8nXcuwYYh8OyK3oncJYnsQ@mail.gmail.com> <alpine.DEB.2.20.1709281052430.18564@uplift.swm.pp.se> <ef940338-4167-dbae-0895-069602f76013@gmail.com> <alpine.DEB.2.20.1709291034390.18564@uplift.swm.pp.se> <40ec0857-30b1-8e7e-ec41-545d8f604d01@gmail.com>
In-Reply-To: <40ec0857-30b1-8e7e-ec41-545d8f604d01@gmail.com>
From: Ca By <cb.list6@gmail.com>
Date: Sun, 12 Nov 2017 15:04:42 +0000
Message-ID: <CAD6AjGSfBH3GGLp2H07GrJ4KDwtFnD8aYkY5HDT9BCDJWGkeVg@mail.gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: Mikael Abrahamsson <swmike@swm.pp.se>, v6ops@ietf.org
Content-Type: multipart/alternative; boundary="f403045e7670ddfb6e055dca79e7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/tmSsOko4lkOFJem8weAi4UDd0LA>
Subject: Re: [v6ops] GTP questions
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Nov 2017 15:05:07 -0000

On Sun, Nov 12, 2017 at 4:11 AM Alexandre Petrescu <
alexandre.petrescu@gmail.com> wrote:

> Hi Mikael,
>
> Sorry for late reply.
>
> Le 29/09/2017 à 10:44, Mikael Abrahamsson a écrit :
> > On Fri, 29 Sep 2017, Alexandre Petrescu wrote:
> >
> >> I would like to ask whether by 3GPP specs the GTP packets can
> >> optionally be transported in IPv6 messages?
> >>
> >> 3GPP spec "GTP" Rel 15 of September 2017 says this:
> >>> UDP/IP is the only path protocol defined to transfer GTP
> >>> messages in the version 1 of GTP. A User Datagram Protocol (UDP)
> >>> compliant with IETF RFC 768 [13] shall be used.
> >>
> >> In practice, a packet capture on PGW shows an IPv6 DHCPv6-PD
> >> Solicit message, preceded by a GTP-U Header, which is itself
> >> preceded by a "GTPU Rx PDU" which is an IPv4 UDP packet.
> >>
> >> The UDPv4 port number that transports GTP packets is 2152,
> >> reserved at IANA and at that 3GPP spec.
> >
> > It's an implementation detail whether this is carried over IPv4 or
> > IPv6. UDP can be carried by both. If you read 29.060 it talks about
> > GTP over both IPv4 and IPv6:
> >
> > "If an IPv4/IPv6 capable SGSN received IPv4 GGSN addresses from the
> > old SGSN, it shall include IPv4 addresses in the fields SGSN Address
> > for Control Plane and SGSN Address for User Traffic and IPv6
> > addresses in the fields Alternative SGSN Address for Control Plane
> > and Alternative SGSN Address for User Traffic. Otherwise, an
> > IPv4/IPv6 capable SGSN shall use only SGSN IPv6 addresses if it has
> > GGSN IPv6 addresses available. If the GGSN supports IPv6 below GTP,
> > it shall store and use the IPv6 SGSN addresses for communication
> > with the SGSN and ignore the IPv4 SGSN addresses. If the GGSN
> > supports only IPv4 below GTP, it shall store and use the IPv4  SGSN
> > addresses for communication with the  SGSN and ignore the IPv6 SGSN
> > addresses. When active contexts are being redistributed due to load
> > sharing, G-PDUs that are in transit across the Gn-interface are in
> > an undetermined state and may be lost."
> >
> > "below GTP" seems to indicate what protocol GTP is run over.
>
> YEs, I can agree to read it that way, but it can be a little bit of a
> stretch.  GTP Rel15 Sept. 2017 clearly says only RFC768.  If it wanted
> to mean GTP/UDP/IPv6 it could have cited e.g. RFC6936.  Hence the doubt.
>
> But yes, I agree with you that in largest part UDP works over IPv6 as
> over IPv4.
>
> > There is a lot more text in TS 29.060 regarding this, but interested
> > parties can read it and form their own opinion.
>
> I agree.
>
> > To me it's clear that 3GPP has done the work to try to achieve so you
> > can standards-based build a network with no IPv4 addresses used for
> > infrastructure. If this works in real life in shipping products,
> > that's a whole other question.
>
> I agree that real life in shipping products is a whole other question.
>
> I had some discussion with some people, and here are some of my
> deductions.  If I am wrong, I carry the responsibility.
>
> Operator1 in hexagon country: the IPv6 is carried in GTP/UDP/IPv4
> Operator2 in country voted out of EU: the IPv6 is carred in GTP/UDP/IPv4.
>
> Among other cellular operators that offer IPv6 to smartphones, I wonder
> about the following:
>
> Is T-Mobile USA carrying the smartphone's IPv6 inside GTP/UDP/IPv4?  Or
> inside GTP/UDP/IPv6?
>
> Is Reliance JIO in India carrying the smartphone's IPv6 inside
> GTP/UDP/IPv4?  Or inside GTP/UDP/IPv6?
>
> My gut feeling is that all do GTP/UDP/IPv4.
>

Your gut is correct, i do not know of any carrier using GTP with ipv6
transport.

That said, i believe the GTP transport network operations is orthogonal to
the network that the UE / customer traffic experiences.



> My intention with this discussion is twofold: find an operator that does
> GTP/UDP/IPv6 and second to deduce something for the IPv6-only
> terminology draft.
>
> Alex
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>