IETF Logo Mail Archive

Re: Usage of services without IPv6 Support

Keith Moore <moore@network-heretics.com> Wed, 22 April 2020 14:59 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 72C433A0E27 for <ietf@ietfa.amsl.com>; Wed, 22 Apr 2020 07:59:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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 jRF6yo8BLR-0 for <ietf@ietfa.amsl.com>; Wed, 22 Apr 2020 07:59:30 -0700 (PDT)
Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00E7D3A0E1D for <ietf@ietf.org>; Wed, 22 Apr 2020 07:59:29 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 1F37B6A3; Wed, 22 Apr 2020 10:59:29 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Wed, 22 Apr 2020 10:59:29 -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=Rfc/b4wG1bZSK4X4GtRzyiYdcasK/IvbmqDpS7wQk Nk=; b=lNpTXOh4VcPx7BQVVUx8sVNl2rCKSqcyR+jU84la3O2tbjhd+23JfrwAJ qbwgbX2EafbE4bgWkSGfJkZJH00nYlgBdkSvBdE9VN4Vx94I4ghWPX6Ic5TCr2pK ZwNzQHJn1573WcvVYVXANEMLjZta2/B0iBVGrglX7GZF7HWZYh6q/slyIzd9ZL0J uz5rGHsvw8z5C2jIfckLyHm/PYeGzD63ccJOkn6nDub8ImHQ5Bb71swyGlunli6C YmcFcTc9fSKiXeuSsBE8htkomfFQ797obPzFD7FYhhocH83JtevxTGNyrgVOOKvN WuGSe7ZFcGe8ITHH8GHDB+/Keq3iQ==
X-ME-Sender: <xms:0FugXu1MAsV0wI99sPEzVik3849ECD8mcCVr5kA_2sdCJMHa414mJg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrgeejgdejjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesthekre dttdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvghtfiho rhhkqdhhvghrvghtihgtshdrtghomheqnecukfhppedutdekrddvvddurddukedtrdduhe enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmohho rhgvsehnvghtfihorhhkqdhhvghrvghtihgtshdrtghomh
X-ME-Proxy: <xmx:0FugXn4UtAcNcTVcyMG9c4N9EuaIiJpoMNi6x0dZ70_5kaF5nXf9Tg> <xmx:0FugXv2DyxcmmAxnlZIV_SLu1q5HovOux5qaxyUGlA5X_Fdg12RzWg> <xmx:0FugXipMeiVZbhNhwmB2MTxy7gkBaSZ0Ry4nvvaXM0hityudTO30og> <xmx:0FugXm3hThPDdiuvMKocSqPKr0QSqym_7GjxjyapFSeCCLtlEGrugQ>
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 BB6EC3280064; Wed, 22 Apr 2020 10:59:26 -0400 (EDT)
Subject: Re: Usage of services without IPv6 Support
To: ietf@ietf.org
References: <ba1450e1-4288-7682-3e15-f36909f6a1fa@gmail.com> <1c4a6ad2-fc65-207a-6a89-558f6b86b0a1@gmail.com> <20200422013643.GU27494@kduck.mit.edu> <d1b18b6b-4e52-6975-0ac9-480ef67142d0@gmail.com> <r7pitm$2250$1@gal.iecc.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <0a9af564-695c-9c84-82ce-b5757514ec18@network-heretics.com>
Date: Wed, 22 Apr 2020 10:59:26 -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: <r7pitm$2250$1@gal.iecc.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/PaSBWbbyzwtezXUqhe4isVLcstM>
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: Wed, 22 Apr 2020 14:59:32 -0000

On 4/22/20 10:04 AM, John Levine wrote:

> In article <d1b18b6b-4e52-6975-0ac9-480ef67142d0@gmail.com>,
> Fernando Frediani  <fhfrediani@gmail.com> wrote:
>> Hello Ben
>> You actually have a very point.
>>
>> However I don't think it applies the very same way as IPv6. NFSv4 for
>> example is not an relevant protocol for Internet, is not something that
>> is exposed publicly, ...
> Sure it is.  Lots of us do remote NFS mounts over the net to retrieve
> a few files.
>
> To be blunt, refusing to use a service solely because it doesn't
> handle IPv6 would be self-defeating virtue signalling.

That would only be true if there were no actual need to support 
IPv6.     And eating our own dogfood is not virtue signaling, it's 
making sure that we understand firsthand the advantages and limitations 
of our recommendations.

Again, this isn't an emergency, and there's no firm deadline (yet).   
Making sure everything works with IPv6 is just being proactive.

I also suspect that there are multiple paths to address this problem 
with a minimum of disruption.

Keith

v2.23.0 | Report a Bug | By Email