Re: [v6ops] DHCPv6-PD presence on OSs, and GTP question (was: 464xlat case study (was reclassify 464XLAT as standard instead of info))

Alexandre Petrescu <alexandre.petrescu@gmail.com> Fri, 29 September 2017 07:54 UTC

Return-Path: <alexandre.petrescu@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 9708A1344ED for <v6ops@ietfa.amsl.com>; Fri, 29 Sep 2017 00:54:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level:
X-Spam-Status: No, score=-2.633 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=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 Wqs8IJKhqWfk for <v6ops@ietfa.amsl.com>; Fri, 29 Sep 2017 00:54:09 -0700 (PDT)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89063134481 for <v6ops@ietf.org>; Fri, 29 Sep 2017 00:54:09 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id v8T7s7fj014837 for <v6ops@ietf.org>; Fri, 29 Sep 2017 09:54:07 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id E60BF202260 for <v6ops@ietf.org>; Fri, 29 Sep 2017 09:54:07 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id DC5EA20080A for <v6ops@ietf.org>; Fri, 29 Sep 2017 09:54:07 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id v8T7s7pG029546 for <v6ops@ietf.org>; Fri, 29 Sep 2017 09:54:07 +0200
To: v6ops@ietf.org
References: <LO1P123MB01168388285206BB7C26F029EA7A0@LO1P123MB0116.GBRP123.PROD.OUTLOOK.COM> <46045DAA-9096-43BA-A5FD-571232767726@google.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>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <ef940338-4167-dbae-0895-069602f76013@gmail.com>
Date: Fri, 29 Sep 2017 09:54:07 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.20.1709281052430.18564@uplift.swm.pp.se>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/4128zI_q_uG8DNcdj_RV8P10q2g>
Subject: Re: [v6ops] DHCPv6-PD presence on OSs, and GTP question (was: 464xlat case study (was reclassify 464XLAT as standard instead of info))
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: Fri, 29 Sep 2017 07:54:11 -0000

Mikael,

I would like to reply, and also ask a few GTP questions publicly.

Le 28/09/2017 à 10:53, Mikael Abrahamsson a écrit :
> On Thu, 28 Sep 2017, Erik Kline wrote:
> 
>> I can just feel all the "android and dhcpv6" screeds being written 
>> right now...
> 
> Do any other mobile operating systems do DHCPv6 on the GTP tunnel?

I have seen DHCPv6-PD Solicits on Android and on Sierra Legato OS.

> It's been too many years since I last looked at GTP packet traces to 
> remember if this was done or not.

Having loooked at GTP packet traces, I suppose one looked at 3GPP specs
as well.

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.

This is the example packet capture I am talking about:

Friday August 11 2017
INBOUND>>>>>  15:45:22:470 Eventid:142004(3)
GTPU Rx PDU, from [IPv4-address]:2152 to [IPv4-address2]:2152 (129)
TEID: 0x80072183, Message type: GTP_TPDU_MSG (0xFF)
Sequence Number:: NA
GTP HEADER FOLLOWS:
              Version number: 1
               Protocol type: 1 (GTP C/U)
[snip]
GTP HEADER ENDS.
            Payload protocol: IPv6
PROTOCOL PAYLOAD FOLLOWS:
fe80::b9d9:c10a:2c2d:3c3b.546 > ff02::2.546:  [udp sum ok]
IPv6 Header Follows:
[snip]
IA_PD Option Follows:
                 Option Type: 0x0019 (OPTION_IA_PD)
                Option Length: 0x0029
                        IA ID: 0x00000000 (0)
                           T1: 0x00000e10 (3600)
                           T2: 0x00001518 (5400)
IA_PD Prefix Option Follows:
                  Option Type: 0x001a (OPTION_IA_PD_PREFIX)
                Option Length: 0x0019 (25)
               IA Prefix Addr: ::/56
                      PL Time: 0x00000e10 (3600)
                      VL Time: 0x00001518 (5400)
[hlim 1] (len 81)
PROTOCOL PAYLOAD ENDS.