Re: [Rift] IPv4 vs IPv6

Mikael Abrahamsson <swmike@swm.pp.se> Thu, 18 July 2019 18:22 UTC

Return-Path: <swmike@swm.pp.se>
X-Original-To: rift@ietfa.amsl.com
Delivered-To: rift@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DD4012006B for <rift@ietfa.amsl.com>; Thu, 18 Jul 2019 11:22:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level:
X-Spam-Status: No, score=-4.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 SRILORbe1yqr for <rift@ietfa.amsl.com>; Thu, 18 Jul 2019 11:22:28 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (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 0899D120B3E for <rift@ietf.org>; Thu, 18 Jul 2019 11:22:28 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id C95E4B2; Thu, 18 Jul 2019 20:22:25 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1563474145; bh=r6j33bjq23zxpzhYqKzfp+ep96CdPuulBD/ZHvmHWP8=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=aT7ONpdsK2oYNia4DlUQu+7LZ/jlkjMGUAob2IMHmRb/3KIivMftWZNUUx3BWLRQP UoBptb694qOYpUbilFQyzjuUT/6djU23VNnJRrLI+pUgjvXSpdb+eBhXH2KoV+j7dC eaJzagAl+mZYRxuxycHzdmI/Mgp6nwqQRBeL8zEc=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id C7491B0; Thu, 18 Jul 2019 20:22:25 +0200 (CEST)
Date: Thu, 18 Jul 2019 20:22:25 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Tony Przygienda <tonysietf@gmail.com>
cc: rift@ietf.org
In-Reply-To: <CA+wi2hP6K3Or7ynOUzKovxkx8ZtvnTUdKVDvjRcB8=4yjFD6aQ@mail.gmail.com>
Message-ID: <alpine.DEB.2.20.1907182001590.19225@uplift.swm.pp.se>
References: <alpine.DEB.2.20.1907180636330.19225@uplift.swm.pp.se> <CA+wi2hP6K3Or7ynOUzKovxkx8ZtvnTUdKVDvjRcB8=4yjFD6aQ@mail.gmail.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rift/MFikT8ZVIFzlHrF6O7G60hHVp5M>
Subject: Re: [Rift] IPv4 vs IPv6
X-BeenThere: rift@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of Routing in Fat Trees <rift.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rift>, <mailto:rift-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rift/>
List-Post: <mailto:rift@ietf.org>
List-Help: <mailto:rift-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rift>, <mailto:rift-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jul 2019 18:22:30 -0000

On Thu, 18 Jul 2019, Tony Przygienda wrote:

> Please dig out the archive where that discussion was brought up by Alvaro
> and follow up there if you still have doubts.

Since I cannot reply to that thread (I just subscribed to the list so I 
don't have an original email to reply to), that's hard.

Anyhow, I think the IPv4 MUST should be removed. It's 2019 now, we should 
not mandate IPv4 support in anything.

> not to the requirements _of devices runing RIFT_:  we cannot mandate 
> that everyone in reality will run IPv6 forwarding on the fabric so the 
> reality is that every silicon does IPv4 today and some does IPv6. And

This fact doesn't warrant making IPv4 a MUST. Think 5-10 years down the 
line, there might be IPv6 only silicon and control plane. Why should 
future implementors be required to implement IPv4 if they do not want to?

> then IPv4 over IPv6 is reality while IPv6 over IPv4 is not (since IPv6 
> does ND anyway so why would you).  So it is very good for v6 here to 
> basically make it an implicit transport for v4 (by saying running v6 
> does _automatically_ give you v4 forwarding) while making sure that v4 
> being-de-facto-what-e'one-can-do is the lowest common denominator of the 
> router's running RIFT. RIFT being only usable if a router/switch can do 
> IPv6 is simply not a practical proposition AFAIS.  We could arguably 
> split it into a "RIFT router/switch requirements document" but that 
> seems just paper bloat ...

I am not proposing making IPv6 a MUST, but I am against making IPv4 a 
MUST. Better to be silent on the matter in that case so future 
implementors can decide for themselves.

I just made me cringe when I read the IPv4 MUST in the document.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se