IETF Logo Mail Archive

RE: Running code (Was: I-D Action: draft-ietf-6man-ipv6only-flag-03.txt)

"Manfredi (US), Albert E" <albert.e.manfredi@boeing.com> Thu, 25 October 2018 03:04 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 BB8F512F1A6 for <ipv6@ietfa.amsl.com>; Wed, 24 Oct 2018 20:04:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 9i7Hj1PeDM8q for <ipv6@ietfa.amsl.com>; Wed, 24 Oct 2018 20:04:54 -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 8F43F130DDF for <ipv6@ietf.org>; Wed, 24 Oct 2018 20:04:53 -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 w9P34poA006251; Wed, 24 Oct 2018 23:04:51 -0400
Received: from XCH16-01-10.nos.boeing.com (xch16-01-10.nos.boeing.com [144.115.66.5]) by clt-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id w9P34jV5006113 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Wed, 24 Oct 2018 23:04:45 -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.1466.3; Wed, 24 Oct 2018 20:04:44 -0700
Received: from XCH16-01-11.nos.boeing.com ([fe80::a96c:5d85:1337:4323]) by XCH16-01-11.nos.boeing.com ([fe80::a96c:5d85:1337:4323%4]) with mapi id 15.01.1466.003; Wed, 24 Oct 2018 20:04:44 -0700
From: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>
To: Mark Andrews <marka@isc.org>, Fernando Gont <fgont@si6networks.com>
CC: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: Running code (Was: I-D Action: draft-ietf-6man-ipv6only-flag-03.txt)
Thread-Topic: Running code (Was: I-D Action: draft-ietf-6man-ipv6only-flag-03.txt)
Thread-Index: AQHUavsT2Zjjso5+/km4+87SaUMNqaUtmzUAgAAB1YCAAAa2AIAADw8AgAAn6ACAAE6FAIAABzoAgAEVqgCAABz7gIAAK+mA//+2oeA=
Date: Thu, 25 Oct 2018 03:04:44 +0000
Message-ID: <328f8654eca44e3fa532bfb61217ab6c@boeing.com>
References: <CAFU7BASO_ByzbanhLKnWV280O_fASd-8W+ujpj3sN6d2-whw2w@mail.gmail.com> <CACWOCC-u7aAPwAOcixYvt2On=-o_8X25GhqdXTfA+tWRC1o2XA@mail.gmail.com> <3beca72e-19c5-10af-02e5-c21a90d77100@gmail.com> <20181019.223739.271916573.sthaug@nethelp.no> <4f58643c-272e-507e-3282-c87befd42395@gmail.com> <0927741c-4e8e-fcf7-ddd6-3ba500ba4c3d@si6networks.com> <7B48A11D-31DE-443C-B73A-14642EA0A397@jisc.ac.uk> <7526af75-4359-6fc6-e39b-eb94024a04de@si6networks.com> <E1BB1232-C1A2-496A-8157-0682D91EED42@steffann.nl> <5E75F3CA-F1D2-4F4F-9CF7-EEEE59634C1E@gmail.com> <C46C990E-0A4F-4731-8CB1-FD204858935E@consulintel.es> <9B53019C-3506-4C9E-AFCF-D6125FA1A65B@gmail.com> <1157b739-3a66-8d45-e3e1-e5f904dfb9bc@asgard.org> <a00607f9-7ced-f889-b5cb-c2fe16367d73@si6networks.com> <66759b73-0a22-e1a9-49db-21154e8e1267@gmail.com> <37ba23b3-df19-9c2a-bdbe-ba7a99d72d05@si6networks.com> <0d6008a4-337b-2ccb-2d9f-837f786eca65@gmail.com> <bfa4397a-aa7a-1184-4147-4cbfbfd13603@si6networks.com> <8C587906-F0EE-4A61-9046-2BFAC52588C0@isc.org>
In-Reply-To: <8C587906-F0EE-4A61-9046-2BFAC52588C0@isc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [137.136.248.6]
x-tm-snts-smtp: 2C8CB20E616EE3A19076EAD6B0594386B0C21D889F34D2C371C8BC2CACE1B04C2000: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/N1pBQh0FQyVBk8ItxjcADHbAPxg>
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: Thu, 25 Oct 2018 03:04:57 -0000

-----Original Message-----
From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Mark Andrews

> Yes.  The assumption when the flag is set is that all the boxes are IPv6
capable.

Okay, you are speaking as the network admin.

> If I was implementing it the interface would become un-numbered for IPv4,
the DHCP client would be disabled, mDNS would not be attempted over IPv4.

And, as a network admin, wanting to stop all IPv4 traffic for whatever network admin reason, it is feasible tout de suite, today, to simply filter Ethertypes 0x0806 and 0x0800, in your switches and router Ethernet interfaces. No need to wait for the IETF.

And similarly, from an equipment vendor's perspective, say your goal as smartphone maker is to extend battery life, make it your own responsibility to do what's best for your user. Don’t expect the network admin to care. Probe the network, see if IPv6 is sufficient for your user's needs, and if yes, then no op the IPv4 stack. The network admin couldn't care less, potentially. Why count on him/her?

So in short, why do we actually need any flag in the IP header?

Bert

v2.23.0 | Report a Bug | By Email