IETF Logo Mail Archive

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

"Manfredi (US), Albert E" <albert.e.manfredi@boeing.com> Fri, 10 May 2019 00:06 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 56868120126 for <ipv6@ietfa.amsl.com>; Thu, 9 May 2019 17:06:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 2AORt6hyUp_O for <ipv6@ietfa.amsl.com>; Thu, 9 May 2019 17:06:42 -0700 (PDT)
Received: from clt-mbsout-02.mbs.boeing.net (clt-mbsout-02.mbs.boeing.net [130.76.144.163]) (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 5599D12012C for <ipv6@ietf.org>; Thu, 9 May 2019 17:06:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id x4A06da6008304; Thu, 9 May 2019 20:06:40 -0400
Received: from XCH16-01-10.nos.boeing.com (xch16-01-10.nos.boeing.com [144.115.66.5]) by clt-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id x4A06TGQ006568 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Thu, 9 May 2019 20:06:29 -0400
Received: from XCH16-01-11.nos.boeing.com (144.115.66.39) by XCH16-01-10.nos.boeing.com (144.115.66.5) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.1713.5; Thu, 9 May 2019 17:06:28 -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; Thu, 9 May 2019 17:06:28 -0700
From: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, IPv6 List <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: AQHVAnkVjGkJVv2nbEmbUUu428c9f6ZiQc0AgACKPQCAALmigIAAZZKA//+SMUA=
Date: Fri, 10 May 2019 00:06:27 +0000
Message-ID: <17339b6d51be4e8ebb2918d735936ad1@boeing.com>
References: <F8BFFCAD-E58E-4736-8A1C-56579B6F6032@employees.org> <CAO42Z2zEWvt9NyemMb8H0AEvPvmNSDGa4wcXiS6n5yRxNFCHQg@mail.gmail.com> <c7e18765-be04-6494-8193-984dbccb520b@foobar.org> <CANMZLAYh+V57yrWOzmUyjSMK0g95u1D5_GZmyZBMOMKAZnrnCg@mail.gmail.com> <3F474511-6FE3-4A0A-9B84-7C37F08FBB5D@steffann.nl> <E352C226-C708-4418-BCDE-10525CAB109A@jisc.ac.uk> <652fb10e-b8ce-0151-a9a0-62d2378caed2@gmail.com> <0079c716-d56c-7199-f493-f5e56e1307ae@foobar.org> <b33de303-eaca-f7f6-804e-2c9343eb92a1@gmail.com> <6C4ABEF1-2565-4BA9-9FC5-5B3C45A719AD@gmail.com> <c2222416-6491-1906-a403-d012777a4b38@gmail.com> <CABNhwV0-SdKZqQa4z9jhpc8h1Eq=8UxRhtvHt1==BYEMTVRjug@mail.gmail.com> <96790121-7D50-4C6F-924F-87065B989E44@gmail.com> <ccab3694-54f2-bdd1-f8ac-cb159dbc0a81@gont.com.ar> <CAN-Dau0_w0n9C6grqi1bXAL-k239K7RMiQyhx5=c-Y_wqrV2OQ@mail.gmail.com> <CAO42Z2wwftO6wtF7PAJ9CCK2iBvtOj0BQP7O0UREr-pMmPegvQ@mail.gmail.com> <A116C7B4-9ED0-4268-9086-5768CB53898D@conjury.org> <e77514fa-cb76-88a8-894e-764b374f363d@gmail.com>
In-Reply-To: <e77514fa-cb76-88a8-894e-764b374f363d@gmail.com>
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: 559827C356A8C88738504703CCB75A95E988E1581B1280C54C150CCFB004B3EB2000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/4gtPvJLA--ZRx6J5E6qQvO3RPO4>
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: Fri, 10 May 2019 00:06:46 -0000

-----Original Message-----
From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Brian E Carpenter

> (Explicitly: discovered on an IPv6-only network several IETFs ago, if you want chapter and verse. The limitation being the absence of a mechanism to signal "IPv6-only" to dual stack hosts.)

Very well and succinctly put, Brian. And that is precisely why I don’t think this draft needs to go further.

Paraphrased, in a "lab experiment" at one IETF, people wondered what would happen if one could just shut off IPv4 entirely. A first, almost knee-jerk reaction was, this lab experiment would be so simple if we only had an explicit bit, transmitted by the network, to say "no IPv4 here."

And yet, upon further reflection, aside from just the momentary curiosity of this "what if no IPv4" experiment, a couple of things became clear: the actual advantage of such a drastic measure was, credibly, only to save some power in battery-powered devices. And there are several other heuristics that hosts can use, to achieve almost completely the same result, in a *decentralized* way, changing no network protocol whatsoever. Furthermore, there are also other ways for the net admin of a managed network, to kill off IPv4 (L2 filtering).

And yet still, in spite of these potential mechanisms which already exist to kill off IPv4, and even in spite of this potential new flag, doggone if people can’t STILL bring their own switch, bring their own peripherals, and run IPv4 in that network anyway!

Not necessary, not sufficient, therefore, IMO, not needed.

Bert

v2.23.0 | Report a Bug | By Email