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

<> Fri, 30 January 2015 16:57 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 349EF1A6EFE for <>; Fri, 30 Jan 2015 08:57:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id qH6ZMjzMY9hW for <>; Fri, 30 Jan 2015 08:57:35 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 497991A19F4 for <>; Fri, 30 Jan 2015 08:57:35 -0800 (PST)
Received: from (unknown [xx.xx.xx.201]) by (ESMTP service) with ESMTP id 64D921B8116; Fri, 30 Jan 2015 17:57:33 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown []) by (ESMTP service) with ESMTP id 4406F38404A; Fri, 30 Jan 2015 17:57:33 +0100 (CET)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([]) by OPEXCLILH03.corporate.adroot.infra.ftgroup ([]) with mapi id 14.03.0224.002; Fri, 30 Jan 2015 17:57:29 +0100
From: <>
To: Gert Doering <>, Nick Hilliard <>
Thread-Topic: [v6ops] draft-ietf-v6ops-mobile-device-profile last call
Date: Fri, 30 Jan 2015 16:57:28 +0000
Message-ID: <8909_1422637053_54CBB7FD_8909_6553_1_5adce3e7-c0d1-4493-b88f-a20a0d4e3c9b@OPEXCLILH03.corporate.adroot.infra.ftgroup>
References: <> <> <20150129201251.GD34798@Space.Net> <787AE7BB302AE849A7480A190F8B933004902668@OPEXCLILM23.corporate.adroot.infra.ftgroup> <20150130103924.GG34798@Space.Net> <787AE7BB302AE849A7480A190F8B933004902889@OPEXCLILM23.corporate.adroot.infra.ftgroup> <> <> <> <20150130164126.GO34798@Space.Net>
In-Reply-To: <20150130164126.GO34798@Space.Net>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version:, Antispam-Engine:, Antispam-Data: 2015.1.30.122720
Archived-At: <>
Cc: "" <>, "" <>
Subject: Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call
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: Fri, 30 Jan 2015 16:57:37 -0000


> Hi,
> On Fri, Jan 30, 2015 at 04:35:07PM +0000, Nick Hilliard 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. 
> And, as Lorenzo stated, none of these handsets (that work well in
> practice!) fulfills the shopping list in this draft...  which gives that the requirements
> are not needed for successful deployment, and *that* makes the whole document
> slightly... superfluous.
[DB] The document does not mandate some support of every feature present in the document as it is the case for RFC 7084 (CPE can be connected to IPv6 networks without any 6rd or DS-Lite features).
The document does not mandate CLAT feature but in some situations, mobile devices should implement this feature. 

> 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


Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.