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

Lorenzo Colitti <> Mon, 16 February 2015 06:11 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id BB2221A873D for <>; Sun, 15 Feb 2015 22:11:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 4.062
X-Spam-Level: ****
X-Spam-Status: No, score=4.062 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FB_GET_MEDS=2.75, 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 iJYoFuU09747 for <>; Sun, 15 Feb 2015 22:11:29 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4001:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D4E3B1A8739 for <>; Sun, 15 Feb 2015 22:11:28 -0800 (PST)
Received: by with SMTP id a13so21755708igq.0 for <>; Sun, 15 Feb 2015 22:11:28 -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=XYHCmoFpkPfkQkXqvhyAelfDGN+NcW32qTzexLA6bAE=; b=hegbvihSxFiUJSyj8lvffhB2Zki3v+cP/q3IrLRQpif/AzNp/WmgmAuGHg3JhOZ0K9 ZfNcZX3E0F7XluS12ImLuOQivATXh9CIzbuHHT7cw0qCAlAxSOUeB4/at10B0nH3wEXG dbLERYKa8sg0DRCPt0EvVy20SuXevpOInlsLMNpGmH0TCZoyIUgJgVGDQ/LYjXxCmaka YJTpDX2wd+VxZAXlFtQAiMF81A/k9jbbK/6Q9XMCSuIpZQ1lR8mS7a7UcRQw06s3HtpX zORzVPWOlBn6UKX8XJJaFjcpTiE9sGZ+RNw9T+SDuPAlkibe/vlpDqN4nAZ0z0dLPs/p DaTw==
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=XYHCmoFpkPfkQkXqvhyAelfDGN+NcW32qTzexLA6bAE=; b=gjuIxdTKCxHVDuoxjn20X8iSNUNgZeCYd7e+AoSkDfdcmXKTOc1RuR3TE1Cz7sgpbp /CxDW99UvO7da4BDwmcodRUhqn95NZ7r4NifLIgne7NicldiXwlCt+N5MLkAk9732c1g BjgBWcgbHzQ4NkKGD4dkLeUBzKTXUKJA111cbPRKsgeWOR74S29Q8WFiHTO3WbdWNUIP uKf+82aQyLYnOt+HsrLhnEyOJ+YLqcpGZRVJ0LnofzXW8kGihlUd3yu+spTASGYuJM3f FOGhToQq95UUiF4eyG2okArhQIUsSpWVWNf1SsKBRX/Iw3kEBI7zJObTaE0kDgSlg3Gr Y7fA==
X-Gm-Message-State: ALoCoQnV5z6IhbbzJZ1vxVMQDCti9aYSdY+0AWYFtV8nCC9XmyZETDgfjuZ50SB2kqWq2izwFegs
X-Received: by with SMTP id 16mr19779413igj.45.1424067087999; Sun, 15 Feb 2015 22:11:27 -0800 (PST)
MIME-Version: 1.0
Received: by with HTTP; Sun, 15 Feb 2015 22:11:07 -0800 (PST)
In-Reply-To: <>
References: <787AE7BB302AE849A7480A190F8B9330049091C2@OPEXCLILM23.corporate.adroot.infra.ftgroup> <> <> <> <6536E263028723489CCD5B6821D4B21303DEA706@UK30S005EXS06.EEAD.EEINT.CO.UK> <> <>
From: Lorenzo Colitti <>
Date: Sun, 15 Feb 2015 22:11:07 -0800
Message-ID: <>
To: Ross Chandler <>
Content-Type: multipart/alternative; boundary=047d7bdc12b0eac269050f2e74f0
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: Mon, 16 Feb 2015 06:11:31 -0000

Ok, and to continue the analogy, the proposed solution to convince Big
Pharma to do what the GPs need is to get a medical standards organization
(not even a GP consortium!) to publish an informational document says "this
document is not a standard, and compliance with this document is not
required, but if you haven't yet stopped reading, here's a profile 30
features long that you might want to implement if you feel like it". I
don't see how that will help at all.

The way I see it, the only important issues here are a) absent strong
operator requirements, device manufacturers do not always implement IPv6 in
all products on all regions, and b) iOS does not implement 464xlat.

If you want to effect meaningful change, I'd suggest focusing on those
issues instead.

On Sat, Feb 14, 2015 at 4:25 AM, Ross Chandler <> wrote:

> On 14 Feb 2015, at 01:31, Lorenzo Colitti <> wrote:
> On Fri, Feb 13, 2015 at 7:29 AM, Heatley, Nick <>
> 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