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

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Mon, 16 March 2020 22:15 UTC

Return-Path: <prvs=134411b52a=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 40D1B3A1262 for <v6ops@ietfa.amsl.com>; Mon, 16 Mar 2020 15:15:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level:
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, 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 QRL4IvH2eric for <v6ops@ietfa.amsl.com>; Mon, 16 Mar 2020 15:15:28 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D74563A1261 for <v6ops@ietf.org>; Mon, 16 Mar 2020 15:15:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1584396925; x=1585001725; 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; bh=yAqRh8o+qmHhY4F1o27Flz17hP1rqwp+GI MSTcY8cC0=; b=t4LlMKEpeboJMTYlRAO6la5BCEIcpnBFTkqlVrWqcA9ApTumaH moJKznyQI0uNEN9DrC+OAtvGJQgC/8QyuFlRp+en8cYi6EVv7aUbUgw+6fqy9mjz ZGnJHeBHyzaKptIAf/kHLOHnO5dVX1Q5vQucGHP5CDstLfXT04gtSr390=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Mon, 16 Mar 2020 23:15:25 +0100
X-Spam-Processed: mail.consulintel.es, Mon, 16 Mar 2020 23:15:25 +0100
Received: from [10.10.10.100] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000093691.msg for <v6ops@ietf.org>; Mon, 16 Mar 2020 23:15:24 +0100
X-MDRemoteIP: 2001:470:1f09:495:a83b:e378:3a37:3744
X-MDHelo: [10.10.10.100]
X-MDArrival-Date: Mon, 16 Mar 2020 23:15:24 +0100
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=134411b52a=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/16.35.20030802
Date: Mon, 16 Mar 2020 23:15:23 +0100
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: v6ops@ietf.org
Message-ID: <F7DE2BAF-349E-4C19-9B65-207CB6B479C8@consulintel.es>
Thread-Topic: [v6ops] About Req for Comments - "Transition to IPv6"
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> <1108969B-48D5-4A81-9E51-887F37B4111C@delong.com> <76c81ccb-0cde-26bb-4650-a7053311bbe8@gmail.com>
In-Reply-To: <76c81ccb-0cde-26bb-4650-a7053311bbe8@gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3667245323_1256320026"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/VfZutMj4qc641YLdOdAtHrIBoxY>
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 22:15:33 -0000

That’s why the *only* objective way to define it is to clearly state what part of the network you’re referring to.

 

Regards,

Jordi

@jordipalet

 

 

 

El 16/3/20 22:58, "v6ops en nombre de Alexandre Petrescu" <v6ops-bounces@ietf.org en nombre de alexandre.petrescu@gmail.com> escribió:

 

 

Le 16/03/2020 à 22:20, Owen DeLong a écrit :

 



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> wrote:

 

 

Le 16/03/2020 à 08:05, Owen DeLong a écrit :

 



On Mar 15, 2020, at 16:32 , Matthew Petach <mpetach@netflight.com> wrote:

 

 

 

On Fri, Mar 6, 2020 at 11:54 AM Owen DeLong <owen@delong.com> wrote:

> On Mar 5, 2020, at 8:51 AM, Alexandre Petrescu <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

 

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.

 

Here' s where we differ in the definition of 'IPv6-only'.  I disagree with the above statement.  An IPv6-only network has no translatio gateways.  But it's just a definition, no problem :-)

Alex

 

Owen

 

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