Re: [v6ops] Some stats on IPv6 fragments and EH filtering on the Internet

Jen Linkova <furry13@gmail.com> Tue, 05 November 2013 03:23 UTC

Return-Path: <furry13@gmail.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 ADCF411E8155 for <v6ops@ietfa.amsl.com>; Mon, 4 Nov 2013 19:23:27 -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=[AWL=0.000, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1ysFvW43AECV for <v6ops@ietfa.amsl.com>; Mon, 4 Nov 2013 19:23:27 -0800 (PST)
Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 2735711E821F for <v6ops@ietf.org>; Mon, 4 Nov 2013 19:23:23 -0800 (PST)
Received: by mail-qc0-f170.google.com with SMTP id n9so4495561qcw.15 for <v6ops@ietf.org>; Mon, 04 Nov 2013 19:23:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=6v2GzwsHG+wc2j5BnfsKC+kxjtufkwjVUkyBcv2dnI8=; b=iSGXNaTxfxVlDpJaAOZpoi5vAvkGJ6Cu3t5YVFNvnM74rFK0ilYL96yxAiOKIKBHgv j92QlsS9AdPixFKM62KD//HO5TRk8jW39eMmM8qh7LeOH7wKpyh24XItSvylIIX+A1Iw sQB0DqKANfZlJOFS5P/wTM9b2yIds15FjUl2Jvx4gDflpuJay1buhJXonej2ZP02k6fD gjKRU3lCYb9AEaPp+uzZpIokQ6thUFZAXAlZJxy099an24Qy/06AnaqnYM1H1Tpc3rHc +YQgaEUOUj3LMMIMjYsJcN4lzfLtUCYnC0FIzgGAmiYp4St5Mhzcs6F0xnlXUTOhZW2a Z7vw==
X-Received: by 10.49.71.207 with SMTP id x15mr26926309qeu.49.1383621802660; Mon, 04 Nov 2013 19:23:22 -0800 (PST)
MIME-Version: 1.0
Received: by 10.224.100.195 with HTTP; Mon, 4 Nov 2013 19:23:02 -0800 (PST)
In-Reply-To: <52785CA4.1060600@si6networks.com>
References: <5278275C.50206@gont.com.ar> <alpine.DEB.2.02.1311050028410.26054@uplift.swm.pp.se> <52783535.9030200@si6networks.com> <20131105001243.53E28985D0D@rock.dv.isc.org> <527839C6.3000805@viagenie.ca> <2134F8430051B64F815C691A62D98318148100@XCH-BLV-504.nw.nos.boeing.com> <001F10BA-F1D4-4AFA-BC0B-E574739782FA@ecs.soton.ac.uk> <F4AB804C-2C8E-40EF-ACE9-0A901E4F5122@employees.org> <EMEW3|143bd43fa5d2a4711db6534159f9ff03pA41VQ03tjc|ecs.soton.ac.uk|001F10BA-F1D4-4AFA-BC0B-E574739782FA@ecs.soton.ac.uk> <CAFU7BASp6fBg4i3P9Ld6PNnuC8N0Syovj3zJebX8hBRZNFVJKQ@mail.gmail.com> <9DC9AFAD-CB63-46BC-B8E1-229F5EA64E6E@ecs.soton.ac.uk> <EMEW3|9997439ba011697baaae10f67ec99f9fpA42Mk03tjc|ecs.soton.ac.uk|9DC9AFAD-CB63-46BC-B8E1-229F5EA64E6E@ecs.soton.ac.uk> <52785CA4.1060600@si6networks.com>
From: Jen Linkova <furry13@gmail.com>
Date: Tue, 05 Nov 2013 04:23:02 +0100
Message-ID: <CAFU7BATbR693eBU0sXQBDkp_-hu_nNW2uxrWtLaO=nJ9KBg07w@mail.gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] Some stats on IPv6 fragments and EH filtering on the Internet
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 05 Nov 2013 03:23:27 -0000

-v6ops@ to minimize the noise

On Tue, Nov 5, 2013 at 3:49 AM, Fernando Gont <fgont@si6networks.com> wrote:
>>> It could be verified by checking the hop limit from the your machine
>>> to the server you are testing and then vary the hop limits of probe
>>> packets - so you can see when you stop receiving 'time exceeded’.
>>
>> Modifying traceroute itself to slip in some extension headers might be useful?  Much as you can check DSCP rewrites, for example.
>
> FWIW, I'm in the process of updating the toolkit to support this sort of
> thing.. Should have something along these lines shortly.

It would be interesting to do such measurements using Atlas but AFAIR
it does not have an option to send packets with extension headers..
Just curious - have you contacted RIPE Atlas guys? I could ask them if
you think it makes sense.


-- 
SY, Jen Linkova aka Furry