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

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Tue, 27 November 2018 13:50 UTC

Return-Path: <prvs=186974acab=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 2E021130E33 for <v6ops@ietfa.amsl.com>; Tue, 27 Nov 2018 05:50:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] 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 HjC5Ez0wkdJY for <v6ops@ietfa.amsl.com>; Tue, 27 Nov 2018 05:50:13 -0800 (PST)
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 D7DD5130DD7 for <v6ops@ietf.org>; Tue, 27 Nov 2018 05:50:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1543326610; x=1543931410; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:CC:Message-ID:Thread-Topic:References: In-Reply-To:Mime-version:Content-type:Content-transfer-encoding; bh=c+9v5LL97jr+kDTgFhSxrfvFwUUG7B6OaPe9kGnTHAo=; b=hM45DD1mfjMLq rZ7btK1C1LJcqQXOUTuxyPTpuKwYFU3hrg12+dPlNwE7EjInrOTOnjo+z5ri8+C9 X/tqVR+Wsh0QCpIQyKGNKXgGNWU/rMnv9BzGsYjOw+VXwC4uJilX1WImyVJ9rzCE /cJiAJEtpayjiBAO5zN4NfJDYKbDn0=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Tue, 27 Nov 2018 14:50:10 +0100
X-Spam-Processed: mail.consulintel.es, Tue, 27 Nov 2018 14:50:09 +0100
Received: from [197.10.32.200] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50006012909.msg for <v6ops@ietf.org>; Tue, 27 Nov 2018 14:50:08 +0100
X-MDRemoteIP: 2001:4350:c:40:11e1:5305:5abd:6037
X-MDHelo: [197.10.32.200]
X-MDArrival-Date: Tue, 27 Nov 2018 14:50:08 +0100
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=186974acab=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/10.10.4.181110
Date: Tue, 27 Nov 2018 14:50:01 +0100
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: Mikael Abrahamsson <swmike@swm.pp.se>
CC: Ron Bonica <rbonica@juniper.net>, "v6ops@ietf.org list" <v6ops@ietf.org>
Message-ID: <D1B8630E-6CEB-4AF0-BFF5-004E144FC278@consulintel.es>
Thread-Topic: [v6ops] draft-xie-v6ops-network-happyeyeballs
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>
In-Reply-To: <alpine.DEB.2.20.1811271424170.7766@uplift.swm.pp.se>
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/pBFswC47-UXohIeZ4OzsjN7T5Bc>
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 13:50:20 -0000

We can make the text clearer, but it mentions NHE (Network Happy Eyeballs). So, the reporting is done "internally" in the ISP network.

We believe that if the operator want to have multiple syslog servers, 4.1 will help to avoid configuring the operator probes, and of course, we are assuming that the operator has an IPv6-enabled network.

Regards,
Jordi
 
 

-----Mensaje original-----
De: Mikael Abrahamsson <swmike@swm.pp.se>
Organización: People's Front Against WWW
Fecha: martes, 27 de noviembre de 2018, 14:28
Para: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
CC: Ron Bonica <rbonica@juniper.net>, "v6ops@ietf.org list" <v6ops@ietf.org>
Asunto: Re: [v6ops] draft-xie-v6ops-network-happyeyeballs

    On Tue, 27 Nov 2018, JORDI PALET MARTINEZ wrote:
    
    > Hi Mikael,
    >
    > I got the impression that when I originally proposed this, syslog was a privacy issue because it is sending data from "customers traffic" from their own devices to the ISP.
    >
    > But in the actual proposal, the data is NOT from any customer, neither identifying the customer at all.
    >
    > So not sure to understand if we have failed to clearly describe the way we are measuring, or you'd in mind the previous document?
    
    https://tools.ietf.org/html/draft-xie-v6ops-network-happyeyeballs-01#section-4
    
    4.  Reporting IPv6 failures using syslog
    
        In order to simplify the reporting of the NHE failures, syslog
        ([RFC5424]) over UDP ([RFC5426]), MUST be used, by means of the
        default port (514) with IPv6-only.
    
    
    
    What is this then? When I re-read it it's not clear if this is for 
    operator-operator communication or between client HE and operator. If it's 
    for operator-operator, how is this address discovered?
    
    The reference to 4.1 about this doesn't make sense to me from a NHE 
    perspective? Why is this conflating things with the NAT64 prefix?
    
    -- 
    Mikael Abrahamsson    email: swmike@swm.pp.se
    



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