[Int-area] New draft: The IETF Will Continue Maintaining IPv4 (draft-schoen-intarea-ietf-maintaining-ipv4)
Seth David Schoen <schoen@loyalty.org> Tue, 15 March 2022 18:59 UTC
Return-Path: <schoen@frotz.zork.net>
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 ECD653A15FD for <int-area@ietfa.amsl.com>; Tue, 15 Mar 2022 11:59:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.658
X-Spam-Level:
X-Spam-Status: No, score=-1.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 YN6VbEYyebIU for <int-area@ietfa.amsl.com>; Tue, 15 Mar 2022 11:59:24 -0700 (PDT)
Received: from frotz.zork.net (frotz.zork.net [IPv6:2600:3c00:e000:35f::1]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE8CD3A156B for <int-area@ietf.org>; Tue, 15 Mar 2022 11:59:22 -0700 (PDT)
Received: by frotz.zork.net (Postfix, from userid 1008) id C9E5411529; Tue, 15 Mar 2022 18:59:20 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 frotz.zork.net C9E5411529
Date: Tue, 15 Mar 2022 11:59:20 -0700
From: Seth David Schoen <schoen@loyalty.org>
To: IETF intarea WG <int-area@ietf.org>
Cc: John Gilmore <gnu@rfc.toad.com>, Dave Taht <dave@taht.net>
Message-ID: <20220315185920.GM918607@frotz.zork.net>
References: <20220314204143.GF2515959@frotz.zork.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20220314204143.GF2515959@frotz.zork.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/iZnR1Dkomu4D8AfHTI2xR_npJ8Y>
Subject: [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 18:59:27 -0000
Hi intarea, 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. This question has been discussed on and off over the past few years. It was, in a way, the subject of an entire now-concluded working group in its own right (sunset4). We thought we should go to the heart of the matter and propose to confirm that the IETF intends to keep maintaining IPv4. As our draft notes, this is the opposite of a proposed consensus item from sunset4 which stated that the IETF would stop working on IPv4. That notion raised many concerns for community members, and we now hope to see whether a consensus to continue maintaining IPv4 can be found. Our draft emphasizes that IPv4 is the most-used network layer protocol in the world, that it's expected to be widely used for the foreseeable future, that the IETF is the historic home of IPv4 standardization, and that there continue to be coordination tasks for IPv4 implementations which the IETF is best-suited to host. Those include not only our own proposals about address space, but also numerous work items on various IPv4 topics that have arisen and become RFCs over the past decade. Our draft does not question or alter the community's consensus in favor of IPv6 adoption, but states that neglecting IPv4 is not a part of the IETF's transition plan. You can find it at https://datatracker.ietf.org/doc/draft-schoen-intarea-ietf-maintaining-ipv4/ We invite discussion leading up to our presentation and Q&A at the intarea session (13:30 UTC) on Tuesday, March 22, during IETF113 in Vienna. Please let us know if you have any questions after reading the draft.
- [Int-area] New draft: The IETF Will Continue Main… Seth David Schoen
- Re: [Int-area] New draft: The IETF Will Continue … Brian E Carpenter
- Re: [Int-area] New draft: The IETF Will Continue … mrcullen42
- Re: [Int-area] New draft: The IETF Will Continue … JORDI PALET MARTINEZ
- Re: [Int-area] New draft: The IETF Will Continue … Behcet Sarikaya
- [Int-area] draft-schoen-intarea-ietf-maintaining-… Jim Reid
- Re: [Int-area] New draft: The IETF Will Continue … touch@strayalpha.com
- Re: [Int-area] New draft: The IETF Will Continue … Ted Lemon
- Re: [Int-area] New draft: The IETF Will Continue … Bob Hinden