Re: [v6ops] 464xlat case study (was reclassify 464XLAT as standard instead of info)

Ca By <cb.list6@gmail.com> Thu, 28 September 2017 12:29 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 C41031346F8 for <v6ops@ietfa.amsl.com>; Thu, 28 Sep 2017 05:29:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 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, URIBL_BLOCKED=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 5_AVSkbrSOPH for <v6ops@ietfa.amsl.com>; Thu, 28 Sep 2017 05:29:46 -0700 (PDT)
Received: from mail-yw0-x234.google.com (mail-yw0-x234.google.com [IPv6:2607:f8b0:4002:c05::234]) (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 758FE132D79 for <v6ops@ietf.org>; Thu, 28 Sep 2017 05:29:46 -0700 (PDT)
Received: by mail-yw0-x234.google.com with SMTP id l4so857379ywa.6 for <v6ops@ietf.org>; Thu, 28 Sep 2017 05:29:46 -0700 (PDT)
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=waojmvryCJAIfi1RVw/MG+EAvUJ+h4D6wSVIXqUijtw=; b=hbz4LW6CGWvhEYxFaB2AXowPQvVZRXRU8Z1QwWgSI5Nbh9+E0P5Qnj145NbNzSOiuq XnRiP3dHeQyfSiOZ9xMNCodnZbeOcnDzl1E6yswz0l3P/hp7R74y248y9UgSikfQJsOo JLUlTBGn3tZ4/oxod28IRVDFb9sPaZx8RjjEry588J9EkHzkZ6+hi9ttNHbkblt05Fq1 8BpEGTDtepF0VY+XrZ5qERJezIYr4RvUzK4NPHSYSwL3MVY/sfuWjhYVlRqkU1d7UMtz kXBklnK0yzGA4kyzL8MmfniAn0FHVqKPtpWk+chuEUAU66u9NpQ9UCdj3UFIidB6LQGD Tzkw==
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=waojmvryCJAIfi1RVw/MG+EAvUJ+h4D6wSVIXqUijtw=; b=rhhmRwtv9/CwigZo08W8PqMQhHoklw0JS2UB+hStKOj/WrwpUxph07gRFQiDVSV/Y8 WOEcvLKKd/gvTtEJHF36h4l/sYzhdnY4J78R5hkjZxr7Al/m7meypCsVbL/cdUla1+LX s39XMppOZUrnT0GSDOzw0NHp5/9v/fjxLc22vugFMHZ25wvUYzu1pvMTMZ1u35luErfU NFSKFhii467bn0CLNaNPFacrNpNDs3zjqN5y4gfe+h8CcdV4toTLZICGYnIxDiDVyMaV n1wzzcMW56TrYY2+9ET/ILA6JBVAKUoomrjNGnDoCRE0FevuKG/q3mAn8iiLD/cO42cS dePQ==
X-Gm-Message-State: AHPjjUg2N6ShOJBnLup5YNiEkqjYk6onrfW9B756xbPQX7XH4gE+A0/G o71/DcBLt95CqIcZJzPTNRRGewL9QwTbHLuhaec=
X-Google-Smtp-Source: AOwi7QAIS/fI51p+F/3dht1oWPVzZ1q7dlIEQiPY4U14pnjoFYSJpT2Bpv5c0+1ZYo43vLBxPQoPzg1NO1Y68Y9IuzM=
X-Received: by 10.13.202.134 with SMTP id m128mr3380038ywd.42.1506601785689; Thu, 28 Sep 2017 05:29:45 -0700 (PDT)
MIME-Version: 1.0
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> <CAAedzxobp6ORODchDGqjbjfKuiZ1vO+q4k5so74MLqdpCzY84A@mail.gmail.com> <F3AFCB39-00D0-4E3C-AC90-E06038AC5230@cisco.com>
In-Reply-To: <F3AFCB39-00D0-4E3C-AC90-E06038AC5230@cisco.com>
From: Ca By <cb.list6@gmail.com>
Date: Thu, 28 Sep 2017 12:29:34 +0000
Message-ID: <CAD6AjGTeQ4RTXmzYKotKFMGO3z8E+5n3FXb9iKL03O3rSATwTQ@mail.gmail.com>
To: Erik Kline <ek@google.com>, "Rajiv Asati (rajiva)" <rajiva@cisco.com>
Cc: IPv6 Ops WG <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="001a114f1c38410bde055a3f1035"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ZPDBsDACqnuT9RmaEGP7lgRT0tE>
Subject: Re: [v6ops] 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: Thu, 28 Sep 2017 12:29:49 -0000

On Thu, Sep 28, 2017 at 2:44 AM Rajiv Asati (rajiva) <rajiva@cisco.com>
wrote:

>
> Do any other mobile operating systems do DHCPv6 on the GTP tunnel? It's
> been
>
>
> I could double check CPE routers such as ISR819 with LTE WAN uplink
> support DHCPv6.
>
> Separately, from PGW point of view, DHCPv6 within an APN seems to be
> supported -
>
>
> https://www.cisco.com/c/en/us/td/docs/wireless/asr_5000/20/P-GW/b_20_PGW_Admin/b_19_PGW_Admin_chapter_010.html#task_309eb986-4510-425a-81ed-833018e70921
>
> //
> The system can be configured to use the Dynamic Host Control Protocol
> (DHCP) for IPv6 to enable the DHCP servers to pass the configuration
> parameters such as IPv6 network addresses to IPv6 nodes. DHCPv6
> configuration is done within an APN.
> //
>
>
I may be wrong here, but these instruction likely do not allow the client
mobile to run dhcpv6

What is likely happening here is the Cisco gateway is running SLAAC to the
mobile but selecting / registering the addresses from an external dhcpv6
server.

Here is the hint from the doc that the gateway is the dhcpv6 client, not
the mobile, and thus no support for dhcpv6 / map to the client ( i may be
wrong)

“

   -

   client identifier command configures the client-identifier, which is
   sent to the external DHCP server. By default, IMSI is sent. Another
   available option is MSISDN.
   -

   “




>
> I have been wondering about asking for an API to the modem to query
> for the 3GPP release number of the network as a hint for expected
> capabilities, but that kinda seems both excessive and like a layering
>
>
> Given all the thing that get queried and fetched by apps, fetching the
> rel# being used (assuming available) would add a drop to the ocean. :)
>
> Cheers,
> Rajiv Asati
> Distinguished Engineer, Cisco Services
>
>
> On Sep 28, 2017, at 11:06 AM, Erik Kline <ek@google.com> wrote:
>
> On 28 September 2017 at 17:53, Mikael Abrahamsson <swmike@swm.pp.se>
> wrote:
>
> 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? It's
> been
>
> too many years since I last looked at GTP packet traces to remember if this
>
> was done or not.
>
>
> I've no idea.  Nor do I know what might happen to various networks if
> DHCPv6 requests were to be made on the mobile interface (even if the O
> bit /were/ observed to be set).  The stories of billing system crashes
> and so on from the early days of v6 on mobile leave me somewhat
> suspicious.
>
> I have been wondering about asking for an API to the modem to query
> for the 3GPP release number of the network as a hint for expected
> capabilities, but that kinda seems both excessive and like a layering
> violation.  ;-)
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>