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

Andrew Sullivan <ajs@anvilwalrusden.com> Tue, 03 August 2021 19:11 UTC

Return-Path: <ajs@anvilwalrusden.com>
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 A38303A1552 for <int-area@ietfa.amsl.com>; Tue, 3 Aug 2021 12:11:31 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=yitter.info header.b=PO0E0+lP; dkim=pass (1024-bit key) header.d=yitter.info header.b=nFyMTi1q
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 PIb3lhCCTdDC for <int-area@ietfa.amsl.com>; Tue, 3 Aug 2021 12:11:27 -0700 (PDT)
Received: from mx5.yitter.info (mx5.yitter.info [159.203.31.152]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DEC563A2E26 for <int-area@ietf.org>; Tue, 3 Aug 2021 12:11:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx5.yitter.info (Postfix) with ESMTP id 0C116BD5C5 for <int-area@ietf.org>; Tue, 3 Aug 2021 19:11:26 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1628017886; bh=96v/mKPYYLH5kh/UGknIpeqG3nBPBBbgIltwLlm51Iw=; h=Date:From:To:Subject:References:In-Reply-To:From; b=PO0E0+lPeHyuIDm4VVvSyjEHq/ZWeSG0E6J1jVvZDMbEdSLosqrUXTuHLnav7Kfpx 6tXQ3/ZVYPEpXroP7ps03LCOEP+xkRucLKJcjF2yAs0nCWpb/qXRUzeANbMKCUA5lB FkevnTRR7S69sO1yVoRqAhhExW5cQ9bEH3hecP2Q=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx5.yitter.info ([127.0.0.1]) by localhost (mx5.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7B0oxCK3Ijqw for <int-area@ietf.org>; Tue, 3 Aug 2021 19:11:24 +0000 (UTC)
Date: Tue, 03 Aug 2021 15:11:21 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1628017884; bh=96v/mKPYYLH5kh/UGknIpeqG3nBPBBbgIltwLlm51Iw=; h=Date:From:To:Subject:References:In-Reply-To:From; b=nFyMTi1qm3O0LaeH3bRQBVuWeo6TpwoBHy6iXcxbrV7jABM4ElINUTUhBpc/9np0d cNDgYsfLKdyMOEyxHuT0RmU4iNbCp8bTFf2CvsOTPSUx84KVhy9oP3IYtlrN79XdSc iTD9cjuTh1uVQbhI3LAMSHJJN5V6ZJDkqZ4cr5co=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: int-area@ietf.org
Message-ID: <20210803191121.pesmxzdbf2exllwn@crankycanuck.ca>
Mail-Followup-To: int-area@ietf.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"; format="flowed"
Content-Disposition: inline
In-Reply-To: <5734.1627983790@hop.toad.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/thZG0p1Hk-8irSs8Hx7axsdd7js>
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 19:11:32 -0000

Dear colleagues,

I work at the Internet Society but am not speaking for them.

On Tue, Aug 03, 2021 at 02:43:10AM -0700, John Gilmore wrote:

>lowest-address draft is the first of a set of upcoming drafts that
>propose small, easy improvements in IPv4.

I think I recalled an (int area?) meeting something like a decade ago where there was a pretty strong sense of consensus that the right thing for the IETF to do is to stop fiddling with IPv4 and to make the path to v6 easier.  How would this set of work contribute to that direction?

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com