Re: [Int-area] New draft: The IETF Will Continue Maintaining IPv4 (draft-schoen-intarea-ietf-maintaining-ipv4)

Ted Lemon <mellon@fugue.com> Tue, 15 March 2022 22:47 UTC

Return-Path: <mellon@fugue.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 95F303A0C87 for <int-area@ietfa.amsl.com>; Tue, 15 Mar 2022 15:47:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.908
X-Spam-Level:
X-Spam-Status: No, score=-6.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20210112.gappssmtp.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 fx3VKNt-RW4K for <int-area@ietfa.amsl.com>; Tue, 15 Mar 2022 15:46:58 -0700 (PDT)
Received: from mail-ot1-x329.google.com (mail-ot1-x329.google.com [IPv6:2607:f8b0:4864:20::329]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B19B13A080B for <int-area@ietf.org>; Tue, 15 Mar 2022 15:46:58 -0700 (PDT)
Received: by mail-ot1-x329.google.com with SMTP id t8-20020a0568301e2800b005b235a56f2dso286067otr.9 for <int-area@ietf.org>; Tue, 15 Mar 2022 15:46:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=obH9ZRn3kL5VJvJI/caJk4Yy0roXiAFfUymccUJrvUk=; b=Viss6YKnNSJKQKREjt9Ra+dSxpbABcagboUrEEx4ly0ZEhpuaMmR7KKryVvIzHwx8y QJlFAvOywtEwNV7lYZeLMp7sjcKyG63D+DKUyUx3WDk7FBbCN3ForHone8pPJrgH4TYc cS3Gzeicsicbir9bHRxmy5TUCD/pcYPuOcDuc3v0wO1RwqpabOfdMBvu4PtH9XzArAuv r/LygVfBv02H1Y0Bl/WMxosRtD5Pjvb+6j7ou0u4vw5XC/5Q8p9Ww4E/nKxuvocJ0HWB v/tHO27QMk/7Q3O2cxpdzLN4lYOdmi+JhwmkO4KlBU1dFuYqmxdaukhOGeWOcDGRp26R aPeg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=obH9ZRn3kL5VJvJI/caJk4Yy0roXiAFfUymccUJrvUk=; b=EfDpn4Du92dtlD4MjQOdhvn3Q8GeR6zsl0txHvzHUZ+tlc6mvi8q5YF8w/nIToWvr4 4Gc4IpOstaNI4UzaZW2V6C3RPLHG46AJQ2Wq2P4uhRYSyJ0FRjUgxh5K3D5bvyDMvITt 9e0BBfFKPqf2Ha7eHpcGgl7A3dMuRqaaaNPI1mbzqfYW00p/q2rGPAMO7S6BjWsI5IDG YLpSRJLntnwfu8tvEMDgSnkIjMIYRw/O/MtBrdVBkjlIEdoDHe0fIK6e6mEvvJzGPfTp 49koBYBbNN4+0lQ1IIQ4Jyev6fY8bCgduUtmFoMy/5id5gh+YiLJeA6tYfslcnNdCkkv rm/g==
X-Gm-Message-State: AOAM5335E/pqMUKZracQnCTJC3JKxfD3Ry4kvSKGhGib+nd7fBOjrhSK tV8GTd/hvHe7PVrBW+RlYMeMrjRqYqcSexi4j+LHhveTChgG1g==
X-Google-Smtp-Source: ABdhPJzmJ3gf2tiWZom0hQOq72gmqZPpKxSFzCeVaCcSB29Qt8COUEBk3wI90PR53CwQAYCsDas77a0y2XN2idD40b0=
X-Received: by 2002:a9d:6292:0:b0:5b2:4693:de5a with SMTP id x18-20020a9d6292000000b005b24693de5amr13313373otk.163.1647384417355; Tue, 15 Mar 2022 15:46:57 -0700 (PDT)
MIME-Version: 1.0
References: <20220314204143.GF2515959@frotz.zork.net> <20220315185920.GM918607@frotz.zork.net>
In-Reply-To: <20220315185920.GM918607@frotz.zork.net>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 15 Mar 2022 18:46:46 -0400
Message-ID: <CAPt1N1=g9BVUX7TEu3Hc3wyZE7HSra575V4tjgioxK+TEa+uXQ@mail.gmail.com>
To: Seth David Schoen <schoen@loyalty.org>
Cc: Dave Taht <dave@taht.net>, IETF intarea WG <int-area@ietf.org>, John Gilmore <gnu@rfc.toad.com>
Content-Type: multipart/alternative; boundary="000000000000015d2e05da499397"
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/YOQdwCskQ-FvlEOynRAmccPIMxc>
Subject: Re: [Int-area] New draft: The IETF Will Continue Maintaining IPv4 (draft-schoen-intarea-ietf-maintaining-ipv4)
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area WG 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, 15 Mar 2022 22:47:04 -0000

On Tue, Mar 15, 2022 at 2:59 PM Seth David Schoen <schoen@loyalty.org>
wrote:

> When we presented our reserved address space drafts at the previous IETF
> meeting, we noticed that the most common concern was not so much about
> the substance of our proposals as about the question of whether intarea
> and the IETF should be working on IPv4 fixes at all


I can't say for sure whether this was the most common concern, but what I
remember as the main concern was that your proposal wouldn't actually do
what you want, but would create a great deal of work for the IETF and for
implementors, with no clear upside.

That’s actually a good test for whether it makes sense to do new IPv4
maintenance work, and I don’t think changing the balance on that is going
to be an improvement.