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

Ross Chandler <ross@eircom.net> Sat, 14 February 2015 12:25 UTC

Return-Path: <ross@eircom.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 9ABD81A1C04 for <v6ops@ietfa.amsl.com>; Sat, 14 Feb 2015 04:25:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 fxYK_Mt2kpIK for <v6ops@ietfa.amsl.com>; Sat, 14 Feb 2015 04:25:21 -0800 (PST)
Received: from mail11.svc.cra.dublin.eircom.net (mail11.svc.cra.dublin.eircom.net [159.134.118.27]) by ietfa.amsl.com (Postfix) with SMTP id BA0D21A1C00 for <v6ops@ietf.org>; Sat, 14 Feb 2015 04:25:20 -0800 (PST)
Received: (qmail 61925 messnum 6674032 invoked from network[213.94.190.11/avas00.vendorsvc.cra.dublin.eircom.net]); 14 Feb 2015 12:25:18 -0000
Received: from avas00.vendorsvc.cra.dublin.eircom.net (213.94.190.11) by mail11.svc.cra.dublin.eircom.net (qp 61925) with SMTP; 14 Feb 2015 12:25:18 -0000
Received: from [192.168.1.1] ([86.43.35.194]) by avas00.vendorsvc.cra.dublin.eircom.net with Cloudmark Gateway id sCRE1p00b4BK5ly01CRJ0W; Sat, 14 Feb 2015 12:25:18 +0000
Content-Type: multipart/alternative; boundary="Apple-Mail=_88B85873-9475-46DF-91F4-A02CED3DAD37"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Ross Chandler <ross@eircom.net>
In-Reply-To: <CAKD1Yr0j23E-UMdL2Ujv5nrpbbUa9rgPE_6AhbHLn0JeOZ9Edg@mail.gmail.com>
Date: Sat, 14 Feb 2015 12:25:14 +0000
Message-Id: <355A1FFC-9F92-4D61-985D-4C5FC6EC69EC@eircom.net>
References: <787AE7BB302AE849A7480A190F8B9330049091C2@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CAKD1Yr2yDnwPDHgsq3Wi3UOzKY7KrqSpBMbBttJ5qAAu6ijOAw@mail.gmail.com> <54DDF02C.8020903@gmail.com> <2D09D61DDFA73D4C884805CC7865E61130F231B4@GAALPA1MSGUSRBF.ITServices.sbc.com> <6536E263028723489CCD5B6821D4B21303DEA706@UK30S005EXS06.EEAD.EEINT.CO.UK> <CAKD1Yr0j23E-UMdL2Ujv5nrpbbUa9rgPE_6AhbHLn0JeOZ9Edg@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/hmj5OUN_ksqto-pje4ovuQzGCos>
Cc: "IPv6 Ops WG \(v6ops@ietf.org\)" <v6ops@ietf.org>
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: Sat, 14 Feb 2015 12:25:23 -0000

> On 14 Feb 2015, at 01:31, Lorenzo Colitti <lorenzo@google.com> wrote:
> 
> On Fri, Feb 13, 2015 at 7:29 AM, Heatley, Nick <nick.heatley@ee.co.uk <mailto:nick.heatley@ee.co.uk>> wrote:
> Lorenzo, I feel you are like the specialist surgeon berating the GPs for not knowing every RFC in its pure form.
> 
> No, I am berating the authors of this draft for writing a document that makes GPs (=device manufacturers, other network operators) believe that they have to prepare loads of unnecessary medical machinery (=the many recommendations that this draft makes) before they can open a small GP surgery (=deploy IPv6), without bothering to tell them why they need all that machinery and what they’re supposed to do with it.

In this particular analogy I classify the device manufacturers as members of Big Pharma, not as GPs.  The small country GPs are faced with buying equipment/features (dual-stack vaccination) to compensate for deficiencies between network+devices they get from their vendors. Until some paying customer demand arises that gets the GP’s Bank Manager interested in helping to push through the development to production services the GP has little incentive to try to move forward (got a works order for that? no didn’t think so) unless he also happens to be an  IPv6 “ultra-geek”.  

A lot of specific input has been taken on board. The list of recommendations has been paired right back and they are in order of priority and there are explanations in the document. 


Ross