Re: [v6ops] About Req for Comments - "Transition to IPv6"

Owen DeLong <owen@delong.com> Mon, 16 March 2020 21:20 UTC

Return-Path: <owen@delong.com>
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 2FA993A1184 for <v6ops@ietfa.amsl.com>; Mon, 16 Mar 2020 14:20:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.098
X-Spam-Level:
X-Spam-Status: No, score=-1.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 Q1L85Js64GRX for <v6ops@ietfa.amsl.com>; Mon, 16 Mar 2020 14:20:47 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id A1A893A1183 for <v6ops@ietf.org>; Mon, 16 Mar 2020 14:20:47 -0700 (PDT)
Received: from kiev.delong.com (kiev.delong.com [IPv6:2620:0:930:0:0:0:200:5]) (authenticated bits=0) by owen.delong.com (8.15.2/8.15.2) with ESMTPSA id 02GLJk8Q227516 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 16 Mar 2020 14:20:45 -0700
From: Owen DeLong <owen@delong.com>
Message-Id: <1108969B-48D5-4A81-9E51-887F37B4111C@delong.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F84DF116-7EBA-48F7-974C-35F46CD9E863"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Mon, 16 Mar 2020 14:20:45 -0700
In-Reply-To: <3a33c3ce-d2ce-b4b2-091b-d4aff3162461@gmail.com>
Cc: Matthew Petach <mpetach@netflight.com>, v6ops@ietf.org
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
References: <e8a25961-5ac9-d35e-77dd-bf86f45cd077@gmail.com> <7eb4dc25-28a6-4927-2356-846e200681d2@gmail.com> <0791D4B0-8390-48D7-AF0A-CE004EC3224C@consulintel.es> <ccc75efb-8c00-ee97-5cc7-2e061e6e5a54@gmail.com> <52b6b9a4f46a49598eccee1b35e5efc5@irs.gov> <89127c25-9c51-c4bb-97ae-3567e80a4c52@gmail.com> <43D0E5A1-E5C5-4ACA-A44D-BC2F67129174@delong.com> <a7269431-c8a3-4182-072d-4bc1a39fcd57@gmail.com> <AC76A63B-3C93-4721-BE73-1851EBA25878@delong.com> <CAEmG1=pekqP8X1+-vqPEJpdLptiqbEvOGQmdin2EmBKGPfiFSA@mail.gmail.com> <8630BF2A-9831-44EE-8CA3-0C3647E86EDE@delong.com> <7d173149-8fc1-b0db-26af-fe5db1954386@gmail.com> <7C4711FE-5C90-4065-950B-FD61B802AE70@delong.com> <3a33c3ce-d2ce-b4b2-091b-d4aff3162461@gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (owen.delong.com [IPv6:2620:0:930:0:0:0:200:2]); Mon, 16 Mar 2020 14:20:46 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/iZ7PC0N6kw6myFfxJCYYjviRFAY>
Subject: Re: [v6ops] About Req for Comments - "Transition to IPv6"
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: Mon, 16 Mar 2020 21:20:49 -0000


> On Mar 16, 2020, at 13:40 , Alexandre Petrescu <alexandre.petrescu@gmail.com> wrote:
> 
> 
> 
> Le 16/03/2020 à 20:42, Owen DeLong a écrit :
>> 
>> 
>>> On Mar 16, 2020, at 04:03 , Alexandre Petrescu <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com>> wrote:
>>> 
>>> 
>>> 
>>> Le 16/03/2020 à 08:05, Owen DeLong a écrit :
>>>> 
>>>> 
>>>>> On Mar 15, 2020, at 16:32 , Matthew Petach <mpetach@netflight.com <mailto:mpetach@netflight.com>> wrote:
>>>>> 
>>>>> 
>>>>> 
>>>>> On Fri, Mar 6, 2020 at 11:54 AM Owen DeLong <owen@delong.com <mailto:owen@delong.com>> wrote:
>>>>> > On Mar 5, 2020, at 8:51 AM, Alexandre Petrescu <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com>> wrote:
>>>>> > Is facebook a network?  I thought of it like a server farm.
>>>>> 
>>>>> How does one run a distributed server farm throughout the world without connecting it with a network? Am I missing something?
>>>>> 
>>>>> I believe for a very long time, that would have accurately described Akamai.
>>>> 
>>>> Akamai didn’t run a backbone. I’d argue that they did run many rather sizable networks.
>>>> 
>>>>> Until their announcement, long after they had established themselves in the marketplace, that they were going to deploy a network: https://pc.nanog.org/static/published/meetings/NANOG71/1532/20171003_Kaufmann_Lightning_Talk_Akamai_v1.pdf <https://pc.nanog.org/static/published/meetings/NANOG71/1532/20171003_Kaufmann_Lightning_Talk_Akamai_v1.pdf>
>>>> Oh, I’m very familiar with that particular project… It was in it’s startup hey day during my tenure in Mr. Kaufmann’s group. That was Akamai building a backbone to connect many (not nearly all) of their networks together.
>>>> 
>>>> I stand by my original statement. One cannot (usefully) run a server farm without a network. Network != backbone.
>>> 
>>> I agree a server farm needs a network.  But that network might be a switched Ethernet with VLANs in a large building, or it might be made of long haul links (ATM, FDDI, multi-Gigabit Ethernet fiber).
>>> 
>>> In the first case (call it VLAN) it is highly possible that VLAN in a building, or a set of close by buildings, are IPv6 only, and no IPv4.
>>> 
>> 
>> This is just silly… For the server farm to be useful, that “VLAN” still needs a larger network in front of it that eventually makes contact (ideally in multiple diverse ways) with a larger internet.
>>> 
>>> But if the facebook system is a geographically distributed server farm with a large network, it might be that at some point the data is carried on IPv4 even though it is IPv6 over IPv4.
>>> 
>> In talking to Facebook’s engineers, they claim to do v4<->6 translation at the edge where necessary to talk to IPv4-only clients and are IPv6-only throughout their datacenters and other networks.
> 
> that v4<->v6 means facebook network is not IPv6-only
> 

No, it doesn’t. A few translation gateways at the very edge of the network are precisely what allows the network itself to be IPv6-only.

Owen