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> Tue, 30 October 2018 21:46 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 CD43812D4F0 for <ipv6@ietfa.amsl.com>; Tue, 30 Oct 2018 14:46:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 kTbPRwuGWuBA for <ipv6@ietfa.amsl.com>; Tue, 30 Oct 2018 14:46:01 -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 BAC9E124408 for <ipv6@ietf.org>; Tue, 30 Oct 2018 14:46:00 -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 w9ULjwTi001760; Tue, 30 Oct 2018 17:45:59 -0400
Received: from XCH16-01-09.nos.boeing.com (xch16-01-09.nos.boeing.com [144.115.65.234]) by clt-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id w9ULjuJ0001473 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Tue, 30 Oct 2018 17:45:56 -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; Tue, 30 Oct 2018 14:45:55 -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; Tue, 30 Oct 2018 14:45:55 -0700
From: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>
To: Toerless Eckert <tte@cs.fau.de>
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: AQHUcFcpYquacc8opU6a6i/ZWJF0uqU4EEbQgACCtwD//41FEIAAm4oA//+Rq/A=
Date: Tue, 30 Oct 2018 21:45:55 +0000
Message-ID: <87651dfca4694f599e67abbc593f1787@boeing.com>
References: <8C587906-F0EE-4A61-9046-2BFAC52588C0@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> <m1gHUMI-0000I6C@stereo.hq.phicoh.net> <acb0984ec73b40c9a350a0d144b23835@boeing.com> <20181030183416.wfv47m63w5xk3cqe@faui48f.informatik.uni-erlangen.de> <143d790e624d498c91fbf69b070da007@boeing.com> <20181030210020.66dppz77jeowp722@faui48f.informatik.uni-erlangen.de>
In-Reply-To: <20181030210020.66dppz77jeowp722@faui48f.informatik.uni-erlangen.de>
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: 922AAB6F436DE070E92331F53705DFCC72DBD3198D617A47423F78FC848F30632000: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/MhrMJQeNATxRrIlldH_eh9L0VhA>
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: Tue, 30 Oct 2018 21:46:03 -0000

-----Original Message-----
From: Toerless Eckert <tte@cs.fau.de> 

> If you don't have IPv4 only hosts on the subnet and no routers routing
IPv4, then IMHO IPv4 is unnecessary and should be completely disabled.
>
> What would be the argument agains this conclusion ?

No argument, Toerless. And, just as you have to have an updated host to read the IPv6-only flag, to make the decision to shut off IPv4 entirely, that same updated host could simply be running the better heuristic. Which says, I have no peripherals configured which require IPv4, I have no old IPv4 PCs with which I'm sharing drives, I have access to one or more IPv6 default routers, so I don't need to use IPv4 for anything.

Your point about assisting in troubleshooting might have merit. A possible counterargument being, possibly, the flag creates errors, that would require troubleshooting.

True story. Years ago, when I was still watching and/or recording TV programs the old-fashioned way, my Philips recording device would sometimes fail to record the program I had set up. I tried updating its software, I was super careful to set it up recording sessions correctly, and yet, sporadically, no recording when I went to watch. Irritation!

So I had to do some research. Come to find out, even though the US Supreme Court had decided that time-shift recording is perfectly legal, a "do not copy" flag was still configured, in these recording devices. So, I called the engineer from the one station giving me this problem, and the nice guy on the other end had no idea they were transmitting this blasted flag. But, the problem did go away after that.

Lesson learned (for me, anyway): best to avoid flags that aren't really essential.

Bert

v2.23.0 | Report a Bug | By Email