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 19:31 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 D8BD712872C for <ipv6@ietfa.amsl.com>; Sun, 28 Oct 2018 12:31:27 -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 jCfvILRjef7f for <ipv6@ietfa.amsl.com>; Sun, 28 Oct 2018 12:31:26 -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 1BC64127332 for <ipv6@ietf.org>; Sun, 28 Oct 2018 12:31:25 -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 w9SJVM5j009685; Sun, 28 Oct 2018 15:31:22 -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 w9SJVFK5009662 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Sun, 28 Oct 2018 15:31:15 -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.1466.3; Sun, 28 Oct 2018 12:31:14 -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 12:31:14 -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//pPRQgAFwdoCAACj2sIABCHiAgAA1yNA=
Date: Sun, 28 Oct 2018 19:31:14 +0000
Message-ID: <f805c8e5b3dc40a8b8f245f44b7c1c7a@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>
In-Reply-To: <8E339E1C-6AC9-4012-AA63-1A39D64EEDAB@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: A41B927337650C8B0D2B3057F215853D68C6144299FF225FE06740E2008FA4B12000: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/C74dXjsaiTNnaBp21sjrXlyZmI8>
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 19:31:28 -0000

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

>> That should occur when you set up the printer, when you load the printer driver. In my own experience, I have had to enter the actual IP address, EVEN OF enterprise printers, when the DNS for some reason or other didn't contain its name. So that's one way the host can determine to use IPv4, for that printer.
>
> You are still looking at this in a "this is my known network" manner.
>
> You go onto a network you've not been on before, how does your device know whether it should be using IPv4 to look for a printer via mDNS ?

Does the device see IPv4 mDNS, listing A records? That's a hint, in a network you've never been on previously. If no IPv4 DNS, no IPv4 default router configured (or reachable, if an old static default router still set in your device), no DHCPv4, stop attempting IPv4, assuming you have ever attempted IPv4.

What you seem to be missing, all this IPv6 flag means is "no IPv4 packets transit THIS router." That's the extent of it. You seem to be attributing a lot more to the flag than it actually intends.

Here's another example. In a network where all routers have the flag set, can you bring your own IPv4 router, and then use a ROUTE command in your host, to send IPv4 packets to a particular device across that router? Could be a tinynet of peripheral devices, for example. Yes, you can. This would be a case of BYOR, as opposed to BYOS, which should also be perfectly okay.

> If you turn on IPv4 to look for what could be a non-existent printer then you've missed the opportunity to save power, if you don't then you may not know about a printer that should be available to 

You have just violated one of the new heuristics I mentioned. Look at it this way: no matter what, these new hosts will need updated heuristics. Flag or no flag, makes no difference. 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. The flag may perhaps help, as an extra input to the new heuristics, but you are giving it much too much importance!

Bert