RE: Confirmation to advance: draft-ietf-6man-ipv6only-flag-05

"Manfredi (US), Albert E" <albert.e.manfredi@boeing.com> Tue, 07 May 2019 21:26 UTC

Return-Path: <albert.e.manfredi@boeing.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 2F77712023E for <ipv6@ietfa.amsl.com>; Tue, 7 May 2019 14:26:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 h0NmTRGC1HcZ for <ipv6@ietfa.amsl.com>; Tue, 7 May 2019 14:26:08 -0700 (PDT)
Received: from clt-mbsout-01.mbs.boeing.net (clt-mbsout-01.mbs.boeing.net [130.76.144.162]) (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 1651C12017F for <ipv6@ietf.org>; Tue, 7 May 2019 14:26:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id x47LQ47F027599; Tue, 7 May 2019 17:26:05 -0400
Received: from XCH16-01-09.nos.boeing.com (xch16-01-09.nos.boeing.com [144.115.65.234]) by clt-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id x47LQ3Qc027576 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Tue, 7 May 2019 17:26:04 -0400
Received: from XCH16-01-11.nos.boeing.com (144.115.66.39) by XCH16-01-09.nos.boeing.com (144.115.65.234) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.1713.5; Tue, 7 May 2019 14:26:02 -0700
Received: from XCH16-01-11.nos.boeing.com ([fe80::c57c:39bc:4c0a:384b]) by XCH16-01-11.nos.boeing.com ([fe80::c57c:39bc:4c0a:384b%4]) with mapi id 15.01.1713.004; Tue, 7 May 2019 14:26:02 -0700
From: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>
To: Ole Troan <otroan@employees.org>
CC: 6man WG <ipv6@ietf.org>
Subject: RE: Confirmation to advance: draft-ietf-6man-ipv6only-flag-05
Thread-Topic: Confirmation to advance: draft-ietf-6man-ipv6only-flag-05
Thread-Index: AQHVBKChjGkJVv2nbEmbUUu428c9f6ZgK7EA
Date: Tue, 07 May 2019 21:26:02 +0000
Message-ID: <5bf11ff3fb3b4ba88c33c23521d931e8@boeing.com>
References: <F8BFFCAD-E58E-4736-8A1C-56579B6F6032@employees.org> <alpine.DEB.2.20.1905070846120.1824@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.20.1905070846120.1824@uplift.swm.pp.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [144.115.204.6]
x-tm-snts-smtp: 0191019F3D8035E1056B980CDC5E159FA2B41D983A2292955EC1DDD3B90FC4BF2000:8
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/tfW-T2aZD3OvTZ1eN5mpEjIyHIw>
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: Tue, 07 May 2019 21:26:11 -0000

On Mon, 29 Apr 2019, Ole Troan wrote:

> At the 6man meeting at IETF 104 in Prague there was support to close the working group last call and advance
> draft-ietf-6man-ipv6only-flag-05 to the IESG.
>
> This call is to confirm that decision on the mailing list.
>
> Please give objections and comments to this decision to the mailing list, by 2019-05-13.

I've not changed my mind on this. The flag seems unnecessary, and if anything, can cause confusion and problems. It seems to have been motivated by people wanting to see what it would be like to get all IPv4 users off the network, at an IETF meeting, and then people have been trying to make the case that it would be generically useful.

There are other ways of sunsetting IPv4 if a network wants to, exactly the same as any number of older network protocols have been obsoleted, never needing any new explicit flag for the purpose. And I would way prefer for equipment vendors themselves, such as smartphone vendors, to create their own heuristics, if they feel that IPv4 is so wasteful of battery power. The onus should be on them, IMO, not on the IETF, and certainly not on other users of the network who might not know or pay attention to that flag.

The KISS principle holds. Only add complications if it's essential.

Bert