IETF Logo Mail Archive

Re: [v6ops] draft-vf-v6ops-ipv6-deployment

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Sun, 04 April 2021 08:42 UTC

Return-Path: <prvs=1728987ea5=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 05C8C3A1D58 for <v6ops@ietfa.amsl.com>; Sun, 4 Apr 2021 01:42:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 NFqU5A1w0EKX for <v6ops@ietfa.amsl.com>; Sun, 4 Apr 2021 01:42:38 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) by ietfa.amsl.com (Postfix) with ESMTP id 136103A1D52 for <v6ops@ietf.org>; Sun, 4 Apr 2021 01:42:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1617525756; x=1618130556; 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=gPrILvrP MN+MCJjsCt9xa+CFfw1KbJSrixgC/q+WaaE=; b=Y3p53TdpNDwfGRfSDHm7ZJmU 74zDGFdrbkvCQQ3vQpRsP3lBoycLBEdXVr/Hkd9zb0SVZA/Hj7Z9G/H++zUcbhVD 7IUFhPqUcxHdFFejnH0LMBFp80AK5zzulqfpEJxU4qFSsEeGzc8O3qbJhiolw9o7 v70pW3N6ssLjA+O3wEI=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Sun, 04 Apr 2021 10:42:36 +0200
X-Spam-Processed: mail.consulintel.es, Sun, 04 Apr 2021 10:42:35 +0200
Received: from [10.10.10.144] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000563928.msg for <v6ops@ietf.org>; Sun, 04 Apr 2021 10:42:34 +0200
X-MDRemoteIP: 2001:470:1f09:495:d5f4:8f2d:9c4b:4e5
X-MDHelo: [10.10.10.144]
X-MDArrival-Date: Sun, 04 Apr 2021 10:42:34 +0200
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1728987ea5=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/16.47.21031401
Date: Sun, 04 Apr 2021 10:42:32 +0200
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "v6ops@ietf.org" <v6ops@ietf.org>
Message-ID: <8B6364D5-BB08-4C3A-84C6-3975B687D4D4@consulintel.es>
Thread-Topic: [v6ops] draft-vf-v6ops-ipv6-deployment
References: <43c05777-01c3-df81-9da1-64abd6dc8c91@gmail.com> <0f404c54-c4df-bcf4-bd8b-3aa5e28136fd@otenet.gr> <CABNhwV0OQqAuzo4fpUqCamX8SYuWzYLDDrgjHTQikQP+N28nfg@mail.gmail.com> <6061207C-5226-45D0-AA29-AA133E76F557@consulintel.es> <CABNhwV3HH23NAxNpOGQggviQgEecbVVDiOOCQLR-9kab=MnTVg@mail.gmail.com> <48ebd4f5151040729b39298b4c2d95f9@huawei.com> <2E04A25E-8075-4D94-BFF6-F72B69561BEC@consulintel.es> <282df8e7ea774ef3ae4d7a33fd016b3d@huawei.com> <062AF533-4FE8-4692-87BE-D496A5A58280@consulintel.es> <1883c281565a43f2ae58ceb798943d8d@huawei.com> <YGcSHSFE8mB74XBF@Space.Net> <fdd57a6d-3b21-ce36-d536-15c6a3b4e743@gmail.com>
In-Reply-To: <fdd57a6d-3b21-ce36-d536-15c6a3b4e743@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/t9ZjwryiThAuIXhuS-K_--BMxME>
Subject: Re: [v6ops] draft-vf-v6ops-ipv6-deployment
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: Sun, 04 Apr 2021 08:42:44 -0000

Hi Brian,

The point is that a few of the CDNs, by default, turn on dual-stack even if the original content is only available with IPv4.
 
Regards,
Jordi
@jordipalet
 
 

El 2/4/21 22:23, "v6ops en nombre de Brian E Carpenter" <v6ops-bounces@ietf.org en nombre de brian.e.carpenter@gmail.com> escribió:

    On 03-Apr-21 01:46, Gert Doering wrote:
    > Hi,
    > 
    > On Wed, Mar 31, 2021 at 11:10:29AM +0000, Vasilenko Eduard wrote:
    >> Hi Jordi,
    >> The fact that something is going to CDN would not help you. Because every CDN accelerates many Web sites.
    >> If the original Web site does not support it ??? then CDN could not help here. It would continue to stream IPv4 for this request.
    > 
    > Uh, no?  CDNs typically decouple frontend protocol from backend protocol.

    Sure, but the site can *request* dual stack or IPv4-only.
    > 
    > Especially if the content is cached anyway, why should it be relevant
    > where it came from?

    Doesn't streaming often bypass the CDN?

       Brian

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

v2.23.0 | Report a Bug | By Email