Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call

Gert Doering <gert@space.net> Fri, 30 January 2015 18:05 UTC

Return-Path: <gert@Space.Net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE58F1A8788 for <v6ops@ietfa.amsl.com>; Fri, 30 Jan 2015 10:05:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level:
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 PJbZKrAeTxhR for <v6ops@ietfa.amsl.com>; Fri, 30 Jan 2015 10:05:24 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (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 597A21A00BE for <v6ops@ietf.org>; Fri, 30 Jan 2015 10:04:59 -0800 (PST)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 0136A62D24 for <v6ops@ietf.org>; Fri, 30 Jan 2015 19:04:56 +0100 (CET)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 9A7AB60B4E for <v6ops@ietf.org>; Fri, 30 Jan 2015 19:04:56 +0100 (CET)
Received: (qmail 51723 invoked by uid 1007); 30 Jan 2015 19:04:56 +0100
Date: Fri, 30 Jan 2015 19:04:56 +0100
From: Gert Doering <gert@space.net>
To: david.binet@orange.com
Message-ID: <20150130180456.GP34798@Space.Net>
References: <B7D61F30-BAC4-4BE0-A5FD-1D4BD4652E55@employees.org> <20150129201251.GD34798@Space.Net> <787AE7BB302AE849A7480A190F8B933004902668@OPEXCLILM23.corporate.adroot.infra.ftgroup> <20150130103924.GG34798@Space.Net> <787AE7BB302AE849A7480A190F8B933004902889@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CAKD1Yr2WQfbDstchk4J0hcCz2_X23nijd71QytU5RpuV=Q3Wjg@mail.gmail.com> <FFD91DE61362694C94B174BB03CFDCDD0102408FA8AC@HE113605.emea1.cds.t-internal.com> <54CBB2BB.9010608@foobar.org> <20150130164126.GO34798@Space.Net> <8909_1422637053_54CBB7FD_8909_6553_1_5adce3e7-c0d1-4493-b88f-a20a0d4e3c9b@OPEXCLILH03.corporate.adroot.infra.ftgroup>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mNGKFxWlKa8RVqLf"
Content-Disposition: inline
In-Reply-To: <8909_1422637053_54CBB7FD_8909_6553_1_5adce3e7-c0d1-4493-b88f-a20a0d4e3c9b@OPEXCLILH03.corporate.adroot.infra.ftgroup>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/fUB0q9k7BLDBNECy3jQZA9N21iY>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, "draft-ietf-v6ops-mobile-device-profile.all@tools.ietf.org" <draft-ietf-v6ops-mobile-device-profile.all@tools.ietf.org>
Subject: Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 30 Jan 2015 18:05:32 -0000

Hi,

On Fri, Jan 30, 2015 at 04:57:28PM +0000, david.binet@orange.com wrote:
> > > the WG position hasn't materially changed; the document has.
> > 
> > To some extent, reality has changed.  There are a number of large scale production
> > wireless 3G/4G deployments out there, so the claim "it cannot be done because
> > handsets sucks" is most definitely no longer true.
> [DB] Whatever the IPv6 deployment status in a given country, we can't say that IPv6 deployment is ready everywhere. In some countries lack of IPv6 support in some mobile devices is still an issue. 

This is a global world, and (maybe except for the chinese market), handset
vendors ship globally - so I bet that an Android handset that works well
in T-Mobile USA's and Verizon Wireless' network has enough IPv6 support
to work on your network as well...

OTOH, I have a number of Telco-branded devices here that can *not* do
IPv6, even if the original vendor firmware *does* IPv6.  So this is really
a matter of the Telcos telling their handset / USB / router vendors to
enable IPv6 in the build shipped to them.  So that wishlist makes sense
to have as a Telco, but I'm not convinced it's a useful IETF document
(I don't see Telcos following IETF or 3GPP recommendations in other 
fields either if they don't want to.  Like, implementing IPv6, which is
mandatory in the 3GPP specs since ever...).

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279