IETF Logo Mail Archive

Re: Usage of services without IPv6 Support

Keith Moore <moore@network-heretics.com> Thu, 23 April 2020 15:03 UTC

Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60B213A09BA for <ietf@ietfa.amsl.com>; Thu, 23 Apr 2020 08:03:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
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 z75a-xqF-woe for <ietf@ietfa.amsl.com>; Thu, 23 Apr 2020 08:03:27 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DE1E3A09C2 for <ietf@ietf.org>; Thu, 23 Apr 2020 08:03:25 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 53E0C5C0113; Thu, 23 Apr 2020 11:03:24 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Thu, 23 Apr 2020 11:03:24 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=KUcTSB5x2Ewl+cgGzvO04qtLHGH1gnC0VSf8NNcmU hA=; b=OiFtjgnvQT2AiiWOyiy4TmGe3FkouOgj6DgB9mX+p+6PNCBjimWuX+C1S ZqEo4+oDywaG4CkLdjL5p5/ZMGgNqYF4qE/DCRUUMHPBerSDmmvbryTCKRAf8nGl ndjQzspKccUsPVP40tRjnzKLn/ykqGwJOQWj/JCJ33DwHFlQE3rGkL4LhD04VT6G 8My+EnyHJ6o9F9u1XftoN7pFvDTjXH2DCdfO/dRPbdMaJNUFvtaCfHvzWDhwIhQi daCROLZuOWxGy70HtGlYi5IcOycTLqv9FTiJuytg+bLtZa/TVjvaf0PxeF1DMP8Z Fq9yPL2JnsLRTdjLKgsncoSw+EjnA==
X-ME-Sender: <xms:O66hXrJ0br4-0CCAMBEu10cZOw26dADhpXaySqpkpYnofO_zBE_wqQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrgeelgdeilecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesthekre dttdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvghtfiho rhhkqdhhvghrvghtihgtshdrtghomheqnecukfhppedutdekrddvvddurddukedtrdduhe enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmohho rhgvsehnvghtfihorhhkqdhhvghrvghtihgtshdrtghomh
X-ME-Proxy: <xmx:O66hXnzjDFOcsjC6-Jax8OARMSBnaMOr47rRERHD6D6k-Om6tQyqVA> <xmx:O66hXnoAPX9G7y4soMMrBCcE4aE1PuoJWQiGUjAWzc3i9QVPftWgOw> <xmx:O66hXp3LAao1P4zIW23b0OOri7KpeLJd3M-J-9ua24BQTNLIDgT_HA> <xmx:PK6hXkFjG58S9dcNRM9U6yka57OFe0W2qK7mkj9m8ltPoCNmmNgi-w>
Received: from [192.168.1.97] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id ABD24328006A; Thu, 23 Apr 2020 11:03:23 -0400 (EDT)
Subject: Re: Usage of services without IPv6 Support
To: ietf@ietf.org
References: <ba1450e1-4288-7682-3e15-f36909f6a1fa@gmail.com> <DB40315C-D62E-4135-8DB4-7760FFC4DB88@consulintel.es> <D6FF32D1-FABE-4648-AA5B-0F5025D61A5F@iii.ca> <6b370298-ba04-e9a5-8f97-71c54fc6f1e5@gmail.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <69b35af6-eca9-abbf-7ad2-73cfa5a86aaf@network-heretics.com>
Date: Thu, 23 Apr 2020 11:03:22 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <6b370298-ba04-e9a5-8f97-71c54fc6f1e5@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BzJti8rSQD_Yt4uzehzvjQGmCEU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Apr 2020 15:03:28 -0000

On 4/23/20 10:49 AM, Fernando Frediani wrote:

> Well, in order to show example and stick to values we have to get out 
> of our comfort zone and not always do everything as we would wish. 

We're supposed to be an engineering group, and engineering is all about 
pragmatism and compromise.  IMO we should expeditiously gravitate toward 
tools that best support our work, and that includes a lot of 
considerations like supporting IPv6 and avoiding vendor lockin.   But we 
should not let that impede our work. It's a difficult balance to 
maintain because inertia gets in the way.   It's easy to get stuck.

IMO any vendor-provided services that aren't well-defined by open 
standards or maybe open source code are inherently suspect, because we 
won't be able to easily modify such tools to suit our changing needs, or 
migrate to other tools that support our needs better.   Our organization 
is dedicated to producing and promoting open standards, so anything we 
use that isn't entirely or at least mostly specified by open standards 
inherently puts us in a conflicted position and impedes our work sooner 
or later.   Lack of IPv6 support is only one example of an issue that 
results from reliance on nonstandard tools.

Keith

v2.23.0 | Report a Bug | By Email