Re: [v6ops] Thoughts about wider operational input

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Tue, 22 March 2022 09:05 UTC

Return-Path: <prvs=10806be5d8=jordi.palet@consulintel.es>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D9FD3A0D05 for <v6ops@ietfa.amsl.com>; Tue, 22 Mar 2022 02:05:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.007
X-Spam-Level:
X-Spam-Status: No, score=-2.007 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_BLOCKED=0.001, SPF_HELO_NONE=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 (1024-bit key) header.d=consulintel.es
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 wr_6Et1E_4EY for <v6ops@ietfa.amsl.com>; Tue, 22 Mar 2022 02:05:41 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) by ietfa.amsl.com (Postfix) with ESMTP id CF5373A0C9A for <v6ops@ietf.org>; Tue, 22 Mar 2022 02:05:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1647939938; x=1648544738; i=jordi.palet@consulintel.es; 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=/oKIylQu zeBgj0gYYAdJOAQCIlEnpvoC2RHfhBAm5+4=; b=LDCrBunoJkrOhSrKtyWEHhCx kuBSQWfxy9fWn23+G67ua94IC5eHuxSeuT5xnOJM2pvivVyeRoxNyJ9i9HcnEMKZ GJIrEVE7x/bwdiMhEv3E4ZcP2bSDLbL6sZkwozrFHAqocPtuJabt7qEoTDyMcAhQ CnegwetdNhWJoWP5EaQ=
X-Spam-Processed: mail.consulintel.es, Tue, 22 Mar 2022 10:05:37 +0100
Received: from [10.10.10.148] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000828111.msg for <v6ops@ietf.org>; Tue, 22 Mar 2022 10:05:37 +0100
X-MDRemoteIP: 2001:470:1f09:495:3cb6:32dd:69d5:fb2f
X-MDHelo: [10.10.10.148]
X-MDArrival-Date: Tue, 22 Mar 2022 10:05:37 +0100
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=10806be5d8=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/16.60.22022702
Date: Tue, 22 Mar 2022 10:05:34 +0100
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: v6ops@ietf.org
Message-ID: <FE2FC674-DBAA-43D3-A286-94B9D5844E85@consulintel.es>
Thread-Topic: [v6ops] Thoughts about wider operational input
References: <52661a3d-75dc-111a-3f23-09b10d7cb8d4@gmail.com> <A72CDDDB-CDCE-4EAF-B95E-997C764DB2C4@gmail.com> <9175dc32-45c1-e948-c20a-3bcc958b77b9@gmail.com> <26C8710D-BB40-4DBD-98A2-20BC3767D732@gmail.com>
In-Reply-To: <26C8710D-BB40-4DBD-98A2-20BC3767D732@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/mqT_36BljBF6DIe7tzJn1icA088>
Subject: Re: [v6ops] Thoughts about wider operational input
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Mar 2022 09:05:51 -0000

Yes, Brian said it, it is a much broader scalability problem.

Actually I think it will not make sense to think only in the "bigger" enterprises only, if we realize that it is very possible that even the "smaller" SMEs will wish be multihommed in the near future. Everybody becoming more dependant on Internet connectivity means you really want to pay links with two different providers, even for residential users.

May be not "active/active" connections for the SMEs, but something like main link being FTTH and secondary backup being 5G. So what I call "hybrid" CPEs and then we have the problem of resolving how to router their own PI.
 
Saludos,
Jordi
@jordipalet
 
 

El 22/3/22, 2:02, "v6ops en nombre de Bob Hinden" <v6ops-bounces@ietf.org en nombre de bob.hinden@gmail.com> escribió:

    Brian,

    I should probably know better to respond to this thread, but apparently not :-)

    > On Mar 21, 2022, at 3:42 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    > 
    > On 22-Mar-22 10:50, Fred Baker wrote:
    >> Sent using a machine that autocorrects in interesting ways...
    >>> On Mar 21, 2022, at 2:05 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    >>> 
    >>> "Why didn't those idiots make IPv6 backward-compatible with IPv4?"
    >> To which the obvious answer is “IPv4 isn’t forward compatible with anything. It was designed to be replaced.”

    To add to what Fred said, IPv6 uses the transition mechanism that the Internet Protocol provided, that is the version number.

    > 
    > As has been said, in different words, many times on The Register forums. I think there are several IPv6ists who respond there, under various pseudonyms. (The Register is not a place where many people care to use real names.)
    > 
    > But unfortunately the usual reply is to repeat that we were idiots not to make IPv6 backwards-compatible (often accompanied by one of the many ideas proposed but found impossible in the early 1990s). Either that, or a plaintive "too hard" argument.
    > 
    > I agree with Jordi that multihoming is a genuine impediment. What isn't generally realised is that it's a problem of scale when considering at least 10,000,000 enterprises, much more than it's a problem of IPv6 itself.

    In my view, and I think I am agreeing with Nick said, it’s not a technical problem that would be fixed by a technical feature.   IPv4 works for most enterprises today and they don’t see a need (aka business case) to do anything different.   The Enterprises who are thinking about moving to IPv6 are very large enterprises who can’t live within the limits of private IPv4 space.

    I suspect these are the ones we should be talking to.

    Bob



    > 
    > _______________________________________________
    > v6ops mailing list
    > v6ops@ietf.org
    > https://www.ietf.org/mailman/listinfo/v6ops

    _______________________________________________
    v6ops mailing list
    v6ops@ietf.org
    https://www.ietf.org/mailman/listinfo/v6ops



**********************************************
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.