IETF Logo Mail Archive

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

Erik Kline <ek@google.com> Thu, 28 September 2017 09:06 UTC

Return-Path: <ek@google.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 436F5134566 for <v6ops@ietfa.amsl.com>; Thu, 28 Sep 2017 02:06:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=google.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 vKULu3lyVlni for <v6ops@ietfa.amsl.com>; Thu, 28 Sep 2017 02:06:27 -0700 (PDT)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (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 0B97A13453C for <v6ops@ietf.org>; Thu, 28 Sep 2017 02:06:27 -0700 (PDT)
Received: by mail-wm0-x236.google.com with SMTP id m72so838270wmc.1 for <v6ops@ietf.org>; Thu, 28 Sep 2017 02:06:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=tCXNSHfzgK11mDTOZjHmUv8tmqJoPFLh59JQCTHxvmU=; b=tF8xu6JtMrQWCPt1a6izczUzjRcGCdNozuFr8RwLgS/T2l8XPN7gXh3gaE3QsZKVpU iO+KcwiwMp6VkTUwgOmGYvlkq4LCDJVZYHfK+jjpnYD1w2pRR54KVYVC5QN0PXwwo/ki wMEVrT9xAkzt7PG8K5u7OLhjQgZ0t4e6kEct0GS/JkiytwjAEKVtOEAHy7Zyhdm63k0w QrR7Kclv60SbCQayHs+AL6cNSFgER3sJ1VHriMyRQ6W6DJDfRVz+37vTluUPfU8Q+3UY clKAKFHyn5JxpDHrgQqfNi/Na/UAp/lRJ8okYwlaBXlbgOwD80mMPoSmYex7NfsZ+d2A SCIg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=tCXNSHfzgK11mDTOZjHmUv8tmqJoPFLh59JQCTHxvmU=; b=qTLqsREb4XvwdjqEf4Npru9q+D+VwiHLWQDQuxz5Ewsh2OvzvTlIOlvgqgdtGo4rOB 1wyH6lb7JTjB2mXuuipIZfoPTf/c+gS0PRoqXr/U55nc3HO8MRgKwg5fkoKhu1A2Tj2D d7ZzGzt7lA88kS0X23isYjjklN5DsaarjVJgut/VwWlb+CmkG3GglMh4ePSl40xHzigU /8zOV2m46IlgzM8SpBj3pWLsyxofDFO3LH0K3i3Pv5gkCXWJ0NsYn5Xw3bq9W4aqefrQ bzfjUj87y78MTF78Sp8cBc38aYz2TTZtxTQ8Zw0dUWxcDvs2ZkFdhDbdxCqtl3Rggw5R filQ==
X-Gm-Message-State: AHPjjUhQUwG8MZ254GXu+qSQ/yVnKr6fUpIj8IKVRLNzk4fn7utm6hU/ vdOQDcHE4BirI2004YkNoi97bEzVhTNd7YZIdwogxQ==
X-Google-Smtp-Source: AOwi7QC9KUa1dL6Y0Cqu5SDDFjH7n4KcIllrXEJw097wB2CJZQO1g7gQhNQLx4VBrPyIEfAMke3U+RPiVDypsetueb0=
X-Received: by 10.28.64.6 with SMTP id n6mr423150wma.61.1506589585176; Thu, 28 Sep 2017 02:06:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.213.9 with HTTP; Thu, 28 Sep 2017 02:06:04 -0700 (PDT)
In-Reply-To: <alpine.DEB.2.20.1709281052430.18564@uplift.swm.pp.se>
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: Erik Kline <ek@google.com>
Date: Thu, 28 Sep 2017 18:06:04 +0900
Message-ID: <CAAedzxobp6ORODchDGqjbjfKuiZ1vO+q4k5so74MLqdpCzY84A@mail.gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: IPv6 Ops WG <v6ops@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="001a114b32ec147d2b055a3c392f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/YVtpe_a6nBWgt-RZYlR04hq6uOA>
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 09:06:33 -0000

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.  ;-)

v2.23.0 | Report a Bug | By Email