Re: [Int-area] Introducing IPv4 Unicast Extensions with new draft-schoen-intarea-lowest-address

Derek Fawcus <dfawcus+lists-int-area@employees.org> Tue, 03 August 2021 11:24 UTC

Return-Path: <dfawcus@employees.org>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDE523A1F81 for <int-area@ietfa.amsl.com>; Tue, 3 Aug 2021 04:24:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, 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 KN-Hzvp3pg2a for <int-area@ietfa.amsl.com>; Tue, 3 Aug 2021 04:24:16 -0700 (PDT)
Received: from clarinet.employees.org (clarinet.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B93FB3A1F80 for <int-area@ietf.org>; Tue, 3 Aug 2021 04:24:16 -0700 (PDT)
Received: by clarinet.employees.org (Postfix, from userid 1736) id 6B0484E11BB7; Tue, 3 Aug 2021 11:24:15 +0000 (UTC)
Date: Tue, 03 Aug 2021 12:24:15 +0100
From: Derek Fawcus <dfawcus+lists-int-area@employees.org>
To: int-area@ietf.org
Message-ID: <YQknXznhNxP2VQel@clarinet.employees.org>
References: <20210802055916.GL550425@frotz.zork.net> <4C839DB1-AD99-4DF0-A7C6-D6F99B4BC335@gmail.com> <5734.1627983790@hop.toad.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <5734.1627983790@hop.toad.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/usRfCg0sPBaX7XQpcM5bDiyd2jA>
Subject: Re: [Int-area] Introducing IPv4 Unicast Extensions with new draft-schoen-intarea-lowest-address
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Aug 2021 11:24:18 -0000

On Tue, Aug 03, 2021 at 02:43:10AM -0700, John Gilmore wrote:
> Our team successfully patched both Linux and BSD over a few weeks, and
> interoperated them successfully.

Linux doesn't need a patch, just a configuration change
(use the 'ip' command to delete the 0-host address/prefix).

I know because a number of years ago I did this with my home set up
where my ISP proveded a /29, and I used all 8 addresses without NAT.

As I recall, I did something like using a RFC 1918 prefix as the
attached net to an interface, and installed a static /28 route for
the public prefix to the same interface on the router (so it would ARP).

Then it was simply a question of how to get the various hosts to
initiate outgoing connections using that public address.  Linux was
easy, as one can specify the source address for the default route.

One one box I used a tunnel to the edge router to achieve a similar effect.

I imagine there are a few ways to achieve these w/o forcing use of NAT.

So operationally one can reclaim both the all-0 and all-1 host
addresses _now_, if one knows what one is doing.  So while I don't
object to the change, I don't view it as freeing up addresses which
can't already be used.

DF