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

Behcet Sarikaya <sarikaya2012@gmail.com> Tue, 15 March 2022 21:37 UTC

Return-Path: <sarikaya2012@gmail.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 4947C3A09CC for <int-area@ietfa.amsl.com>; Tue, 15 Mar 2022 14:37:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.857
X-Spam-Level:
X-Spam-Status: No, score=-1.857 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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=gmail.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 ch6FNIzgbu9V for <int-area@ietfa.amsl.com>; Tue, 15 Mar 2022 14:36:57 -0700 (PDT)
Received: from mail-lf1-x132.google.com (mail-lf1-x132.google.com [IPv6:2a00:1450:4864:20::132]) (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 9865E3A09B7 for <int-area@ietf.org>; Tue, 15 Mar 2022 14:36:56 -0700 (PDT)
Received: by mail-lf1-x132.google.com with SMTP id e6so717401lfc.1 for <int-area@ietf.org>; Tue, 15 Mar 2022 14:36:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=1t0cYiAUy8cIeG/q3ElD15JFguxjqO+XbMttp2S/z2I=; b=JeFV/lkB8UOdCdhT0gTxVuxuhhKl46QYykJ6S6Q84P4t4nJ1dzU1o+Uzr64qCHnkSl 2xPCRM0za8LRHPshqyRe/VIHGzwCkXLbjl3v2b95bxj3KiMDmM2Th9VKVYRO7WBlXEYn peDFtZCL9r99X6tlNsALFhQS501cCNuU8NXsWjXhw648Q6l+/2Hq3t+IHVnmGIxU1+Rz oI0Vm+6gFnSf8KTeHJLsUa68cf3zHC9IvXwcLJYp9e9ek5BcQHN8rFRCu+Zfdk8Owgem ch7bvKSBkF5etlXKF/8YJaL5Wf8A5XK+fcB5oYALUFehwoM0wRvue/fSpZUrxINVaLZt cZZg==
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:reply-to :from:date:message-id:subject:to:cc; bh=1t0cYiAUy8cIeG/q3ElD15JFguxjqO+XbMttp2S/z2I=; b=FDuqZy14Vq4Ygp7oFulmNNjHdLw2i/BlfM9dXXoq7x9oVGhTCppLpCFXc68CbG7x31 MKXuNLIrMP5MDpaVS+T7GnIOHrZVyRw794+MY9yd/zGsY6zgTWnPzQkvTAIs7HaBoDdu hEgya7fasmCYXQ/yJgH64ZwGK4YE9aqukLVYIrJLB9JUG7knjge2I85lWSGiX8jX4Hpz QopwIt9aSzUClcg52aTKgAiPN4dhx8aRUfAcEp+mT9Jx99k2zPSWyH/Z8ciPwMaxMgMe 223C+dLICwCw+q7XpzYmHtSniywcYCiyfid+hQioeHslu7DnLMll6vUJ6nJCs1L5Ap4o 3NDQ==
X-Gm-Message-State: AOAM530qy35TPukOAnMgaHBDMHJBAu/cMklDB+chQS8GnEEEdZC+Limi oi52UKaiozcY8E5MtMxjtIBjNS0hE3P5klrCfFoIoWwNPBY=
X-Google-Smtp-Source: ABdhPJwfu/UeQarfnb2YjZhh2JkXTjF3xoscMzUZ0ULRzsZj11rQlRIbj733ITuRoDwYyJJFlXuAzcr+98tAB3PYADc=
X-Received: by 2002:ac2:5082:0:b0:448:35ad:23b7 with SMTP id f2-20020ac25082000000b0044835ad23b7mr17820495lfm.509.1647380214095; Tue, 15 Mar 2022 14:36:54 -0700 (PDT)
MIME-Version: 1.0
References: <20220314204143.GF2515959@frotz.zork.net> <20220315185920.GM918607@frotz.zork.net> <af109588-9319-af86-36a3-917a9475ea55@gmail.com> <53E917DC-58D4-4F72-9B9F-28861F60BC1D@consulintel.es>
In-Reply-To: <53E917DC-58D4-4F72-9B9F-28861F60BC1D@consulintel.es>
Reply-To: sarikaya@ieee.org
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Tue, 15 Mar 2022 16:36:42 -0500
Message-ID: <CAC8QAcf_XhXtysL2ZqLpc=h+G92Gqrjx9EUXxa7XT-FvSE1yiA@mail.gmail.com>
To: JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org>
Cc: IETF intarea WG <int-area@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000078a28405da48982e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/bM6jintzIAW4lcugAtBmqkiMYGU>
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 21:37:02 -0000

+1

Behcet

On Tue, Mar 15, 2022 at 3:32 PM JORDI PALET MARTINEZ <jordi.palet=
40consulintel.es@dmarc.ietf.org> wrote:

> +1
>
>
> El 15/3/22, 21:05, "Int-area en nombre de Brian E Carpenter" <
> int-area-bounces@ietf.org en nombre de brian.e.carpenter@gmail.com>
> escribió:
>
>     Hi,
>
>     > 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.
>
>     Regards
>         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
>     >
>     >
> 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 mailing list
>     > Int-area@ietf.org
>     > https://www.ietf.org/mailman/listinfo/int-area
>     >
>
>     _______________________________________________
>     Int-area mailing list
>     Int-area@ietf.org
>     https://www.ietf.org/mailman/listinfo/int-area
>
>
>
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.theipv6company.com
> 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.
>
>
>
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area
>