Re: [v6ops] draft-xie-v6ops-network-happyeyeballs

<mohamed.boucadair@orange.com> Tue, 27 November 2018 16:05 UTC

Return-Path: <mohamed.boucadair@orange.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 A14B8130ED6 for <v6ops@ietfa.amsl.com>; Tue, 27 Nov 2018 08:05:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham 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 QlBiDGyBwJT8 for <v6ops@ietfa.amsl.com>; Tue, 27 Nov 2018 08:05:23 -0800 (PST)
Received: from orange.com (mta241.mail.business.static.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31D55130EED for <v6ops@ietf.org>; Tue, 27 Nov 2018 08:05:21 -0800 (PST)
Received: from opfedar01.francetelecom.fr (unknown [xx.xx.xx.2]) by opfedar25.francetelecom.fr (ESMTP service) with ESMTP id 4347sq3yr6z8tdp; Tue, 27 Nov 2018 17:05:19 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.18]) by opfedar01.francetelecom.fr (ESMTP service) with ESMTP id 4347sq319TzBrLM; Tue, 27 Nov 2018 17:05:19 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM34.corporate.adroot.infra.ftgroup ([fe80::cba:56d0:a732:ef5a%19]) with mapi id 14.03.0415.000; Tue, 27 Nov 2018 17:05:19 +0100
From: mohamed.boucadair@orange.com
To: JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org>, Nick Hilliard <nick@foobar.org>
CC: "v6ops@ietf.org list" <v6ops@ietf.org>
Thread-Topic: [v6ops] draft-xie-v6ops-network-happyeyeballs
Thread-Index: AQHUhmlcmU7Hfk90lEukLC5aUNdD3KVjx4xQ
Date: Tue, 27 Nov 2018 16:05:18 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302E04E767@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <BYAPR05MB42453683C869E9A5327DA903AED70@BYAPR05MB4245.namprd05.prod.outlook.com> <alpine.DEB.2.20.1811271231060.7766@uplift.swm.pp.se> <30D71C7B-1FBF-49C2-A5C6-40948550CA69@consulintel.es> <alpine.DEB.2.20.1811271424170.7766@uplift.swm.pp.se> <D1B8630E-6CEB-4AF0-BFF5-004E144FC278@consulintel.es> <alpine.DEB.2.20.1811271451450.7766@uplift.swm.pp.se> <C88CEF72-D1FB-435A-B53D-4D940A4445FF@consulintel.es> <2372941b-67e7-a418-d81c-545aa4ab1010@foobar.org> <A7C3A588-6962-419A-B537-B859F0A4E56A@consulintel.es>
In-Reply-To: <A7C3A588-6962-419A-B537-B859F0A4E56A@consulintel.es>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.4]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/mO9ELCVb61ey4afBbsBTmYNOQtg>
Subject: Re: [v6ops] draft-xie-v6ops-network-happyeyeballs
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, 27 Nov 2018 16:05:34 -0000

Jordi, 

It is not unusual that operators deploying IPv6 monitor both IPv4/IPv6 performance metrics to track and detect severe gaps. 

Nevertheless, that probing does not allow to ** deterministically ** conclude that the root of the problem is at the server side (proxy, CDN, etc.). 

Gaps in v4/v6 metrics is used as one of the problem detection triggers among others: the problem may be caused by a misbehaving router/node on IPv6 packets, local forwarding issues, congestionned links with a peer/transit providers, etc. Of course, in some cases the content provider is contacted to solve the problem by tuning, for example, how the traffic is delivered to the network provider. 

So, sending an automatic report to some server may not help solving the problem.

Cheers,
Med

> -----Message d'origine-----
> De : v6ops [mailto:v6ops-bounces@ietf.org] De la part de JORDI PALET MARTINEZ
> Envoyé : mardi 27 novembre 2018 16:53
> À : Nick Hilliard
> Cc : v6ops@ietf.org list
> Objet : Re: [v6ops] draft-xie-v6ops-network-happyeyeballs
> 
> In the previous related work, I was told otherwise: let's the ISPs do it, not
> the O/S vendors ...
> 
> Regards,
> Jordi
> 
> 
> 
> -----Mensaje original-----
> De: v6ops <v6ops-bounces@ietf.org> en nombre de Nick Hilliard
> <nick@foobar.org>
> Fecha: martes, 27 de noviembre de 2018, 16:42
> Para: JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org>
> CC: "v6ops@ietf.org list" <v6ops@ietf.org>
> Asunto: Re: [v6ops] draft-xie-v6ops-network-happyeyeballs
> 
>     JORDI PALET MARTINEZ wrote on 27/11/2018 15:38:
>     > Yes, is within a specific network.
>     >
>     > If they decide later on to tell other ISPs "traffic from our network
>     > to your address xxx" is not working ... that's not handled by this
>     > document.
>     O/S software to do this would be great.  There's no need for IETF
>     involvement.
> 
>     Nick
> 
>     _______________________________________________
>     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.
> 
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops