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> Sun, 28 October 2018 21:47 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 D362D1277CC for <ipv6@ietfa.amsl.com>; Sun, 28 Oct 2018 14:47:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 JV2tbUF35ftD for <ipv6@ietfa.amsl.com>; Sun, 28 Oct 2018 14:47:49 -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 D7C63127332 for <ipv6@ietf.org>; Sun, 28 Oct 2018 14:47:48 -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 w9SLlko5030963; Sun, 28 Oct 2018 17:47:46 -0400
Received: from XCH16-01-12.nos.boeing.com (xch16-01-12.nos.boeing.com [144.115.66.70]) by clt-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id w9SLlcW4030925 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Sun, 28 Oct 2018 17:47:38 -0400
Received: from XCH16-01-11.nos.boeing.com (144.115.66.39) by XCH16-01-12.nos.boeing.com (144.115.66.70) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.1466.3; Sun, 28 Oct 2018 14:47:37 -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; Sun, 28 Oct 2018 14:47:37 -0700
From: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>
To: Simon Hobson <linux@thehobsons.co.uk>, "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: AQHUbJuG2Zjjso5+/km4+87SaUMNqaUwfHjwgAE2LoCAACLHMIAAg2aA//+OfUCAAKaPAP//pPRQgAFwdoCAACj2sIABCHiAgAA1yNCAAJXiAP//k39Q
Date: Sun, 28 Oct 2018 21:47:37 +0000
Message-ID: <74048c37559d451ea0e01a45993cd707@boeing.com>
References: <CAFU7BASO_ByzbanhLKnWV280O_fASd-8W+ujpj3sN6d2-whw2w@mail.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-2BF AC52588C0@isc.org> <E8DE18B5-94FC-411C-A310-E49A382E0079@thehobsons.co.uk> <e0fa8fad1b4249c9af79788323b0a922@boeing.com> <3A03A073-72E2-43A8-90A4-5C29DF445361@thehobsons.co.uk> <27fdbd71125842d888c5136684bf6e7b@boeing.com> <9A4368D6-E4B1-474C-9838-B584AF6D70C8@thehobsons.co.uk> <a3a2d823c38f44d48b301e2ca657e352@boeing.com> <6EE067A5-3536-4EDD-80D9-D98783DE57CE@thehobsons.co.uk> <0be69133e9a34199b5796410684ab226@boeing.com> <d84bab3c-3ad8-2338-1af1-3fe2b277db6c@innovat ionslab.net> <308494108c0b466f91a9314f7d9367bc@boeing.com> <8E339E1C-6AC9-4012-AA63-1A39D64EEDAB@thehobsons.co.uk> <f805c8e5b3dc40a8b8f245f44b7c1c7a@boeing.com> <63345723-EF9D-45E2-9848-9BFC818D78E0@thehobsons.co.uk>
In-Reply-To: <63345723-EF9D-45E2-9848-9BFC818D78E0@thehobsons.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [137.137.12.6]
x-tm-snts-smtp: FB682C9C911AA4E5BFDF395447560A6534ABABC60B7EEB5B2C8AFEB327A348AE2000: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/Vqjt8P9Kh5YDqah6dHFNZkCgYIw>
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: Sun, 28 Oct 2018 21:47:51 -0000

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

>> With the heuristics I have already described, if you are not bringing along IPv4 peripherals with you, and IPv6 seems to be available (DNS, RAs, etc.), then your device will have *no reason* to attempt IPv4. Same goal is achieved.
>
> Err no, you've explicitly broken some networks - specifically just about every dual stack network !

Not hardly.

Again, an equipment designer, intent on saving battery power, would not need to use IPv4 ever, if IPv6 provides all the needed services. In a dual-stack network, SAME THING. That's why an equipment vendor who wants to do what's best will still need updated heuristics, with or without a flag. The interests of the network are not necessarily aligned with the interests of the host.

> The MOST IMPORTANT think is for whatever is done to NOT BREAK EXISTING NETWORKS. This flag does that - it only has an effect when manually set by the administrator who we have to assume has got some sort of clue. Thus the default is to not break anything - ie the flag not set.

Not even close. The heuristics I described break nothing. A dual-stack host on a dual-stack network, where the host can do everything the user asks with IPv6 only, breaks absolutely nothing, and saves power. Plus, I repeat, the host will see IPv4 services are available, from the DNS and the presence of an IPv4 default router. So that, should there be something IPv6 is unable to do, or reach, the host can try IPv4.

The flag adds very little indeed.

Bert

v2.23.0 | Report a Bug | By Email