Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call- "harmfully broad"?

Lorenzo Colitti <> Tue, 17 February 2015 02:41 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 6ACDA1A8983 for <>; Mon, 16 Feb 2015 18:41:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id uIctOsnv58XI for <>; Mon, 16 Feb 2015 18:41:56 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4001:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id EF3B61A86EE for <>; Mon, 16 Feb 2015 18:41:40 -0800 (PST)
Received: by with SMTP id z20so27079727igj.4 for <>; Mon, 16 Feb 2015 18:41:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=t6IMLzuGOjpKWOSd/1UdvNYeX4KZlbebN9lq84cmJOY=; b=pcIveRK702W0f6JVo6bquwrRgcaodrRUrSLoM3WHyGrjVKUem2Uus7JkhnpAKJzPaO YNdel2Qul5s1AlOcRzz7NJ9PJC2RfEmdwezlNVV2OkYjPaRc2/llSR3gHiQ1YgAtGVbE O7NYbb/jmVV7ubOi8swVlrhuJHG+8WanE43OqcCGNJgHBu+FCwBka6RGj/f47a4Ipbt1 Cwrx8uofcMAM70bkdxMxLA8W3Pmpw6XgEWAnR9VFFAI3ouf+FrvNHPLi5hv4lb4etFiZ bbA4DOloPaahmtD43czFHiO2B8j191KhEbazR9t5jjMBjxkgf9kyfGH48o94cEhzCkTJ TJNw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=t6IMLzuGOjpKWOSd/1UdvNYeX4KZlbebN9lq84cmJOY=; b=G1GT2O6A6Ag+Vs6zCSMTuWHJPrVUOFMiMPnXPW6UsL9jHgGrVZjKJRK7L+qeSUc0zM qmvywL312LXCIx3Cc6DBSGTdzO6I7xFuPoG7EFA3l9I+t7qwdtHQwwqE+yXjjkXgWOHs qmSMckW2FmhOcsrwGtcbvgNxdThfFOcHSQ9taim9kF/dnP1Hm7ARvrcdFIroMO+Dj0cn HRYnW8mueQVBtCWkKiI7+shO5Mw8078skbnD0eS8pXF38Tsfo88yav9v/stELHux7g3C gAsH2g1wLFVcE1AP9vbL0L/50O4oZpE42Mtl+CQ+1vybhh91Kk1AAGY2q3N9CVv/mYbi KiOw==
X-Gm-Message-State: ALoCoQmfrE/ZufkLC6zdttt5NrmNaiM7LWXtGpj+yOFWXv0C2jPsEHCvc7GzhBSQS1xoMv+u0Osy
X-Received: by with SMTP id g89mr32808593ioj.31.1424140900200; Mon, 16 Feb 2015 18:41:40 -0800 (PST)
MIME-Version: 1.0
Received: by with HTTP; Mon, 16 Feb 2015 18:41:19 -0800 (PST)
In-Reply-To: <>
References: <787AE7BB302AE849A7480A190F8B9330049091C2@OPEXCLILM23.corporate.adroot.infra.ftgroup> <> <> <> <6536E263028723489CCD5B6821D4B21303DEA706@UK30S005EXS06.EEAD.EEINT.CO.UK> <> <> <> <6536E263028723489CCD5B6821D4B21303E07EE2@UK30S005EXS06.EEAD.EEINT.CO.UK> <>
From: Lorenzo Colitti <>
Date: Tue, 17 Feb 2015 11:41:19 +0900
Message-ID: <>
To: "Heatley, Nick" <>
Content-Type: multipart/alternative; boundary=001a114159b87794e6050f3fa46d
Archived-At: <>
Cc: "IPv6 Ops WG \(\)" <>
Subject: Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call- "harmfully broad"?
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 17 Feb 2015 02:41:57 -0000

On Tue, Feb 17, 2015 at 10:57 AM, Lorenzo Colitti <>

> Yes. Make IPv6* (see below) a requirement for carrier-branded devices, and
> give the OEMs a credible signal that from date X onwards, you *will* fail
> TA on every device that doesn't implement IPv6, and you *will not* waive
> the requirement. That's what Verizon and T-Mobile did, and it worked for
> them.

Also: if you think that this strategy is not feasible because you do not
have an IPv6 network yet, then yes, that's true - you can't make IPv6 a
device requirement until you have an IPv6 network.

But I think the key point here is that apart from the lack of 464xlat on
iOS, the mobile operating systems are a lot more ready for IPv6 than you
might think they are. Once the network is complete, I think turning on IPv6
in the devices does work. Orange Poland, Telenor, and SK Telecom should be
able to confirm.