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 00:41 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 CD71E130E05 for <ipv6@ietfa.amsl.com>; Sat, 27 Oct 2018 17:41:51 -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 E4RJsKNn_qUq for <ipv6@ietfa.amsl.com>; Sat, 27 Oct 2018 17:41:50 -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 0D4DF130E02 for <ipv6@ietf.org>; Sat, 27 Oct 2018 17:41:49 -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 w9S0flp0019619; Sat, 27 Oct 2018 20:41:47 -0400
Received: from XCH16-01-08.nos.boeing.com (xch16-01-08.nos.boeing.com [144.115.65.218]) by clt-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id w9S0fgEf019604 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Sat, 27 Oct 2018 20:41:42 -0400
Received: from XCH16-01-11.nos.boeing.com (144.115.66.39) by XCH16-01-08.nos.boeing.com (144.115.65.218) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.1466.3; Sat, 27 Oct 2018 17:41:40 -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; Sat, 27 Oct 2018 17:41:40 -0700
From: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>
To: Brian Haberman <brian@innovationslab.net>, "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//pPRQgAFwdoCAACj2sA==
Date: Sun, 28 Oct 2018 00:41:40 +0000
Message-ID: <308494108c0b466f91a9314f7d9367bc@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@innovationslab.net>
In-Reply-To: <d84bab3c-3ad8-2338-1af1-3fe2b277db6c@innovationslab.net>
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: FC1B85887083AF93BAEFBE02C87ACF28969BA86ECD674229A9638074B10771F62000: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/QX_CGOixm-mpLqIBwiU8rjAAWsY>
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 00:41:52 -0000

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

> I think your observation is key for everyone. The flag only indicates
that the router(s) will not route IPv4 off the link. There is nothing
stopping devices from using IPv4 locally on the link to communicate with
other such devices.
>
> The same thing occurs today with devices using IPv6 link-locals on
IPv4-only links.

Agreed.

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

> OK, explain how the device is to know whether or not it should be turning on IPv4 to see if there's an IPv4 printer it needs to talk to ?

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.

And too, even in an enterprise net, one can potentially have a printer or other specialty device, like a CD-ROM label maker, in an office, or in a suite, where that specialty device is not under the control of the IT people, and access to it has to be IPv4. A flag, or heuristics, c'est la même chose.

> IFF there is an old IPv4 only printer that the user needs to access, then the admin would not set this flag.

What Brian said. Sorry, that's wrong. If any host uses the flag that way, that host is broken. Which is part of the risk of the IETF creating such a flag, without very explicit instructions on its use by hosts. Instructions which the equipment designer might simply want to ignore, along with the flag itself.
 
Mikael says it would be used as an extra input to the heuristics, which is IMO the actual way it would ever get used.

> Again, you've missed the point - it's not about hosts hollerin, it's about allowing hosts to operate more efficiently.

I missed no such point. There are two interests here: a network admin wanting to shut off IPv4, for whatever reason, and a host wanting to conserve energy. I'm simply saying, if the network wants to shut off IPv4, chances are, flag or no flag, someone's going to holler. Flag makes zero difference. Anyone with an older device will be unhappy.

Bert