Re: I-D Action: draft-ietf-6man-ipv6only-flag-03.txt

Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com> Mon, 22 October 2018 14:52 UTC

Return-Path: <pch-bCE2691D2@u-1.phicoh.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BE5012896A for <ipv6@ietfa.amsl.com>; Mon, 22 Oct 2018 07:52:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] autolearn=ham autolearn_force=no
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 WleKhbVFXf63 for <ipv6@ietfa.amsl.com>; Mon, 22 Oct 2018 07:52:32 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (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 528C81276D0 for <ipv6@ietf.org>; Mon, 22 Oct 2018 07:52:20 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384) (Smail #157) id m1gEbZ3-0000IBC; Mon, 22 Oct 2018 16:52:17 +0200
Message-Id: <m1gEbZ3-0000IBC@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Subject: Re: I-D Action: draft-ietf-6man-ipv6only-flag-03.txt
From: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>
Sender: pch-bCE2691D2@u-1.phicoh.com
References: <153973137181.9473.10666616544238076833@ietfa.amsl.com> <092346e1-6350-e54e-e711-9c5ee6dc4e6b@gmail.com> <4a883ed6-c0d7-5d3f-9657-3ba0476919e0@foobar.org> <6952EE88-B3D6-48BC-ACFF-C5248965EDC9@employees.org> <61706f85-cf3a-1a03-0371-30fe3eaaec6f@foobar.org> <2afa8333-fad3-3a26-0466-2ed3bd1e0c9c@gmail.com> <3F8BCD30-DEE4-44B8-BF45-CAB75F21B11A@jisc.ac.uk>
In-reply-to: Your message of "Mon, 22 Oct 2018 10:04:16 +0000 ." <3F8BCD30-DEE4-44B8-BF45-CAB75F21B11A@jisc.ac.uk>
Date: Mon, 22 Oct 2018 16:52:16 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/a1zb3SxBjm8Sah5FjVcJj8_4Oj4>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2018 14:52:36 -0000

>There is currently no evidence of any vendor interest in implementing support 
>for the flag.

I wondered about that myself. I don't like this draft at all, but the
bigger question is who is actually going to implement this?

There is benefit for battery powered devices, but I haven't seen any vendor
of mobile devices stand up and say that they will implement it. And my guess
is that any dev team will find more robust ways of saving battery power than
relying on this option.

At the same time, if room full of operators at a RIPE meeting say they have no
need for this option, then who is going to set it on routers?

>From a technical point of view, if nobody implements the flag, it doesn't do 
any harm.

Beyond a narrow technical view, it does harm. It makes the total IPv6 protocol
bigger, so harder to analyse, harder for people to learn about IPv6 or to
teach others.