[hops] Middlebox on your device

Szilveszter Nadas <Szilveszter.Nadas@ericsson.com> Mon, 23 March 2015 23:03 UTC

Return-Path: <Szilveszter.Nadas@ericsson.com>
X-Original-To: hops@ietfa.amsl.com
Delivered-To: hops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 144DD1A0111 for <hops@ietfa.amsl.com>; Mon, 23 Mar 2015 16:03:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 FEysSPlN7mHt for <hops@ietfa.amsl.com>; Mon, 23 Mar 2015 16:03:01 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 093F11A00FE for <hops@ietf.org>; Mon, 23 Mar 2015 16:03:00 -0700 (PDT)
X-AuditID: c1b4fb2d-f79a46d0000006b4-bb-55109ba3c560
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id C1.37.01716.3AB90155; Tue, 24 Mar 2015 00:02:59 +0100 (CET)
Received: from ESESSMB303.ericsson.se ([169.254.3.196]) by ESESSHC002.ericsson.se ([153.88.183.24]) with mapi id 14.03.0210.002; Tue, 24 Mar 2015 00:02:58 +0100
From: Szilveszter Nadas <Szilveszter.Nadas@ericsson.com>
To: "hops@ietf.org" <hops@ietf.org>
Thread-Topic: Middlebox on your device
Thread-Index: AdBlu73as0T2GeDBSbGOaK8PQbtMig==
Date: Mon, 23 Mar 2015 23:02:58 +0000
Message-ID: <EA4C43BE752A194597B002779DF69BAE23CC03D3@ESESSMB303.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.149]
Content-Type: multipart/alternative; boundary="_000_EA4C43BE752A194597B002779DF69BAE23CC03D3ESESSMB303erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrGLMWRmVeSWpSXmKPExsUyM+Jvje7i2QKhBv2bxCy+H9zD7MDosWTJ T6YAxigum5TUnMyy1CJ9uwSujN71xQUzpSv6Xt1jbGD8Id7FyMkhIWAisev5DjYIW0ziwr31 QDYXh5DAEUaJ31fXM0I4SxglFj24ywRSxSZgIdGwcjNYh4iAssT7HRtYQGxhAUWJ46vXMELE 1SQWP/vNBGHrSby5tgIsziKgKvHn1R2gOAcHr4CvxPX70iBhRqDF30+tAStnFhCXuPVkPhPE QQISS/acZ4awRSVePv7HCmErSaw9vJ0Foj5fou3ud7BzeAUEJU7OfMIygVFoFpJRs5CUzUJS BhHXkViw+xMbhK0tsWzha2YY+8yBx0zI4gsY2VcxihanFhfnphsZ66UWZSYXF+fn6eWllmxi BEbEwS2/dXcwrn7teIhRgINRiYd3QyN/qBBrYllxZe4hRmkOFiVxXjvjQyFCAumJJanZqakF qUXxRaU5qcWHGJk4OKUaGD0W3Sp7v/66ucziOWvurJpnzpBi11uwS/6X8NfQicJye1bpLZNw 0331S//yvw1T1107u7ZANfHvc3bxVWzzSz7/Ec2bJBCiuyvh4MNjXBd533K9OOqziWHX2v6I XOOTvEfnqOnfzdTbHutxWk1tzimf6MWnGabsyZohPiVMKO/mmUPlP6rYOoKVWIozEg21mIuK EwFWQw3oaQIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/hops/1g_EJOSSJpZL1yTBMFXRpmdUjb4>
Subject: [hops] Middlebox on your device
X-BeenThere: hops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Measuring deployability of new transport protocols <hops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hops>, <mailto:hops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hops/>
List-Post: <mailto:hops@ietf.org>
List-Help: <mailto:hops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hops>, <mailto:hops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2015 23:03:03 -0000

Hi,

What if the "middlebox" blocking some transport feature/field is on the end-user device, e.g. a firewall software? Maybe saying the obvious here, just wanted to mention that sometimes it might not be the ISP the one to blame. Maybe it is not even important who to blame. Probably/hopefully firewall software is easier to update though, but it can have quite an effect on the measurement results.

(slightly related to this thread: http://www.ietf.org/mail-archive/web/spud/current/msg00028.html)

Cheers,
Sz.