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

JORDI PALET MARTINEZ <> Tue, 15 March 2022 20:32 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 10EA33A0045 for <>; Tue, 15 Mar 2022 13:32:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.008
X-Spam-Status: No, score=-7.008 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_HI=-5, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id WkgAoEKdMz0O for <>; Tue, 15 Mar 2022 13:32:06 -0700 (PDT)
Received: from ( [IPv6:2001:470:1f09:495::5]) by (Postfix) with ESMTP id 9DF693A005F for <>; Tue, 15 Mar 2022 13:32:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple;; s=MDaemon; t=1647376320; x=1647981120;; q=dns/txt; h=User-Agent:Date: Subject:From:To:Message-ID:Thread-Topic:References:In-Reply-To: Mime-version:Content-type:Content-transfer-encoding; bh=6rdsXP+8 5UPrX5HEn6BrZdGEgpE3My9Z5JXehH+4km4=; b=obQZIzVyskpK7fZ2nPI0fGn7 ibu+sy9ScbKJFg2QGJCqsvZ1mfE9QXZtPpbDN6GOy4jvVUi6SbNOCQ6u/Y1UqSaD gSPksrN5h4h8iL8B12q3vrDnr+KtBsjeOMmuQx+Ow1hd0RzvhsK8Nw6EjubT3/i6 Tez1OLkc2uKMu9NGQmc=
X-MDAV-Result: clean
X-MDAV-Processed:, Tue, 15 Mar 2022 21:32:00 +0100
X-Spam-Processed:, Tue, 15 Mar 2022 21:32:00 +0100
Received: from [] by (MDaemon PRO v16.5.2) with ESMTPA id md50000824125.msg for <>; Tue, 15 Mar 2022 21:32:00 +0100
X-MDRemoteIP: 2001:470:1f09:495:ad15:e5e0:e46e:a498
X-MDHelo: []
X-MDArrival-Date: Tue, 15 Mar 2022 21:32:00 +0100
User-Agent: Microsoft-MacOutlook/16.60.22022702
Date: Tue, 15 Mar 2022 21:31:55 +0100
To: IETF intarea WG <>
Message-ID: <>
Thread-Topic: [Int-area] New draft: The IETF Will Continue Maintaining IPv4 (draft-schoen-intarea-ietf-maintaining-ipv4)
References: <> <> <>
In-Reply-To: <>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <>
Subject: Re: [Int-area] New draft: The IETF Will Continue Maintaining IPv4 (draft-schoen-intarea-ietf-maintaining-ipv4)
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area WG Mailing List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 15 Mar 2022 20:32:16 -0000


El 15/3/22, 21:05, "Int-area en nombre de Brian E Carpenter" < en nombre de> escribió:


    > Please let us know if you have any questions after reading the
    > draft.

    I have no questions.

    IMHO the draft is unnecessary and potentially harmful. It's a
    matter of common sense that the IETF will fix things that *need*
    fixing, even if they are specific to IPv4. It's a matter of fact
    that IPv4 will continue to coexist with IPv6 until nobody uses
    IPv4 any more. But it would be a mistake to apply scarce IETF
    resources for anything but serious fixes, and this draft opens
    the door to that. Consider for example the phrase "ongoing
    standardization" near the end of section 7. That is exactly
    what we do not need.

    FWIW I do not consider the minor wastage of IPv4 addresses that
    the same authors are concerned about to be serious enough to need
    fixing. We shouldn't be fixing problems that IPv6 already fixes,
    and shortage of addresses is certainly in that category.

    When there is an issue that is serious enough to justify IETF
    effort, and specific to IPv4, the intarea WG charter already
    allows for it. That's why this draft seems unnecessary to me.

        Brian Carpenter

    On 16-Mar-22 07:59, Seth David Schoen wrote:
    > 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
    > 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 mailing list

    Int-area mailing list

IPv4 is over
Are you ready for the new Internet ?
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.