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

Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 19 February 2015 13:59 UTC

Return-Path: <alexandru.petrescu@gmail.com>
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 6332D1A906A for <v6ops@ietfa.amsl.com>; Thu, 19 Feb 2015 05:59:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level:
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 zi95rGIJDibU for <v6ops@ietfa.amsl.com>; Thu, 19 Feb 2015 05:59:06 -0800 (PST)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B29001A8A96 for <v6ops@ietf.org>; Thu, 19 Feb 2015 05:59:05 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t1JDx3dW009226 for <v6ops@ietf.org>; Thu, 19 Feb 2015 14:59:03 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id AC8BA2022EB for <v6ops@ietf.org>; Thu, 19 Feb 2015 15:00:08 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id A4D4420225D for <v6ops@ietf.org>; Thu, 19 Feb 2015 15:00:08 +0100 (CET)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t1JDwfmc019721 for <v6ops@ietf.org>; Thu, 19 Feb 2015 14:59:03 +0100
Message-ID: <54E5EC11.4070002@gmail.com>
Date: Thu, 19 Feb 2015 14:58:41 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: v6ops@ietf.org
References: <787AE7BB302AE849A7480A190F8B9330049091C2@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CAKD1Yr2PX81czTwUZzaMtgPc9vhvP=oL++UZByGzxmkq_B=DMA@mail.gmail.com> <6536E263028723489CCD5B6821D4B21303E07EE2@UK30S005EXS06.EEAD.EEINT.CO.UK> <CAKD1Yr0Zkic6-ydV-u==xjDGdY9GYWb8KwciBPnfk8zO=6FFqQ@mail.gmail.com> <CAKD1Yr0qS-Vg-XB7mNWwephkkL5rCG+NJO7uDJg_4W3LT+Q9Ew@mail.gmail.com> <6536E263028723489CCD5B6821D4B21303E088AE@UK30S005EXS06.EEAD.EEINT.CO.UK> <CAKD1Yr00Ri8hQMsJcSqMAw+g_T-mU8GxG1G8rTHgo=McaKdW8Q@mail.gmail.com> <26150_1424277597_54E4C05D_26150_800_1_A729C0B3952BEE45A1AA136ADD556BE80493F147@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CAKD1Yr2+BMSifTS3x0WD5LqKYe-Yse8CGf4Egaijp=8DVSf5UA@mail.gmail.com> <fdc7ab8c-4f63-43eb-a77b-4764f24d9486@OPEXCLILH01.corporate.adroot.infra.ftgroup> <D10B3F46.1A731%dave.michaud@rci.rogers.com> <CAKD1Yr0zig7DY6npfe6JiKjmhojxTohV2==+C26zLVAU5CMo3w@mail.gmail.com> <D10B47D6.1A74E%dave.michaud@rci.rogers.com>
In-Reply-To: <D10B47D6.1A74E%dave.michaud@rci.rogers.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/iSKpIFIvpEqKDVhNYzGJrU5Fc8k>
Subject: Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call- "harmfully broad"?
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: Thu, 19 Feb 2015 13:59:11 -0000

Le 19/02/2015 14:10, Dave Michaud a écrit :
[...]
> Transitionning to IPv6-only requires further support from the host
> side to form a complete solution.

In this particular respect: no, I think it's very possible to have
transition to an IPv6-only access yet the host acts as a pure IPv4 host
(no CLAT translation on the Host).

I think what you mean is that the cellular operators have a particular
solution for migrating to IPv6-only.  The method 464xlat/clat is good
but not necessarily the best for every context (an IPv4 Host-to-Host app
like Push-to-Talk, to mention something new).

Among those two (IPv6 and CLAT) one would certainly suggest IPv6
implementation in the terminal, but CLAT should be a "MAY".  One
wouldn't want others to think that IPv6 is possible only if CLAT is there.

Alex

>
> The documents published under v6ops should "serve as useful guides
> to network operators and users on possible ways how to deploy IPv6
> within their existing IPv4 networks, as well as in new network
> installations.”
>
> This is exactly what this is. As a LAN administrator, it wouldn’t
> cross my mind to look for an RFC for host requirements because I
> would have little control anyway. As a cellular operator, the hosts
> are part of my network and I do have a say on how they operate and
> it forms part of the overall solution (bullet 4 of the charter).
> Same would apply from a Cable MSO where the CPEs are integral part of
> the network.
>
>
>
> *Dave Michaud* Sr. Architect Mobility – Access Networks & IP Network
> Services Network Technology | Rogers Communications
> dave.michaud@rci.rogers.com <mailto:dave.michaud@rci.rogers.com> |
> tel: +1 647.747.9442 | mobile: +1 416.219.5531
>
>
> From: Lorenzo Colitti <lorenzo@google.com
> <mailto:lorenzo@google.com>> Date: Thursday, February 19, 2015 at
> 07:45 To: Dave Michaud <dave.michaud@rci.rogers.com
> <mailto:dave.michaud@rci.rogers.com>> Cc:
> "mohamed.boucadair@orange.com <mailto:mohamed.boucadair@orange.com>"
> <mohamed.boucadair@orange.com <mailto:mohamed.boucadair@orange.com>>,
> BINET IMT/OLN <david.binet@orange.com
> <mailto:david.binet@orange.com>>, IPv6 WG <v6ops@ietf.org
> <mailto:v6ops@ietf.org>> Subject: Re: [v6ops]
> draft-ietf-v6ops-mobile-device-profile last call- "harmfully broad"?
>
> On Thu, Feb 19, 2015 at 9:31 PM, Dave Michaud
> <Dave.Michaud@rci.rogers.com <mailto:Dave.Michaud@rci.rogers.com>>
> wrote:
>
> This is directly in line with the v6ops charter:
>
> The IPv6 Operations Working Group (v6ops) develops guidelines for the
> operation of a shared IPv4/IPv6 Internet and provides operational
> guidance on how to deploy IPv6 into existing IPv4-only networks, as
> well as into new network installations.
>
> The main focus of the v6ops WG is to look at the immediate
> deployment issues; more advanced stages of deployment and transition
> are a lower priority.
>
>
> Actually, it isn't, really. The charter is operational guidance for
> the IPv4/IPv6 Internet. Not host requirements.
>
> In fact, if you look at the numbered list in the charter, the items
> are "identify operational issues and determine solutions", "identify
> potential security risks", "identify portions of the specs that can
> cause operational concerns", and "analyze solutions for deploying
> IPv6 within network environments". None of those cover this
> document.
>
>
>
>
> ------------------------------------------------------------------------
>
>
>
>
>
>
>
This communication is confidential. We only send and receive email on
> the basis of the terms set out at
> www.rogers.com/web/content/emailnotice
> <http://www.rogers.com/web/content/emailnotice>
>
>
>
> Ce message est confidentiel. Notre transmission et réception de
> courriels se fait strictement suivant les modalités énoncées dans
> l’avis publié à www.rogers.com/aviscourriel
> <http://www.rogers.com/aviscourriel >
> ------------------------------------------------------------------------
>
>
>
>
>
>
>
>
> _______________________________________________ v6ops mailing list
> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>