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

Tim Chown <> Tue, 05 November 2013 03:39 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4674921E8102 for <>; Mon, 4 Nov 2013 19:39:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Mo-anGPaaLUx for <>; Mon, 4 Nov 2013 19:39:53 -0800 (PST)
Received: from ( [IPv6:2001:630:d0:f102::25e]) by (Postfix) with ESMTP id CCCBD21E80E0 for <>; Mon, 4 Nov 2013 19:39:52 -0800 (PST)
Received: from (localhost []) by (8.13.8/8.13.8) with ESMTP id rA53dl1T004254 for <>; Tue, 5 Nov 2013 03:39:47 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 rA53dl1T004254
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple;; s=201304; t=1383622787; bh=bu76HeCQjRjxM0WEOtPz/B9gBkw=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=E8+6vW4H1N9s3G75fWMI1EvOlD8rcjDNO4CLPK4HiLXyi65tM9YZuPFGoC2GFMvyr OuAX8+8zv2cYAfNY0TgPWhhF9iQm5u/+vj1uoyWUU9nJ3Ml5fZPqUVVU1HQi9PQUei oxknww+upX629KHVU0+FvP+Pqh6a5DekpZxRakA4=
Received: from ([2001:630:d0:f102:250:56ff:fea0:401]) by ( [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <> with ESMTP (valid=N/A) id pA43dl09596353831P ret-id none; Tue, 05 Nov 2013 03:39:47 +0000
Received: from ( [IPv6:2001:67c:370:160:6865:dd3f:9c57:76dd] (may be forged)) (authenticated bits=0) by (8.13.8/8.13.8) with ESMTP id rA53cQat012974 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <>; Tue, 5 Nov 2013 03:38:28 GMT
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
From: Tim Chown <>
In-Reply-To: <>
Date: Tue, 5 Nov 2013 03:38:26 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|32a5fe2bc02b433f835f9959f328942fpA43dl03tjc||>
References: <> <> <> <> <> <> <> <> <EMEW3|143bd43fa5d2a4711db6534159f9ff03pA41VQ03tjc||> <> <> <EMEW3|9997439ba011697baaae10f67ec99f9fpA42Mk03tjc||> <> <> <>
To: "" <>
X-Mailer: Apple Mail (2.1816)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=pA43dl095963538300; tid=pA43dl09596353831P; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: rA53dl1T004254
Subject: Re: [v6ops] Some stats on IPv6 fragments and EH filtering on the Internet
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 05 Nov 2013 03:39:54 -0000

On 5 Nov 2013, at 03:23, Jen Linkova <> wrote:

> -v6ops@ to minimize the noise
> On Tue, Nov 5, 2013 at 3:49 AM, Fernando Gont <> 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.

While I love the idea of the Atlas project, and have a probe myself, I tried asking them whether I could do just basic HTTP monitoring with my probe, and that wasn’t possible, so I’m not optimistic that a general probe user could just add such tests. 

I suspect it would need some significant code updates from the developers. But measuring probe to probe would certainly be useful, so it would be nice to see at some point… some of the Atlas people are here, so we might get some idea of a timeline if it is possible… :)