[mat-wg] IPv6 extension headers support on RIPE Atlas

Dear RIPE Atlas users, Jen,

we have followed the discussion about IPv6 extension headers,
and this is our understanding of what you would want us to implement -- 
please send any comments or suggestions to the list!


On 06-nov.-13 01:59, Jen Linkova wrote:
 > There are some ongoing efforts to measure IPv6 extension headers
 > filtering in the Internet
[...]
 > Therefore it would be great if Atlas supports:
 > - inserting Ipv6 extension headers into probe packets. Ideally user
 > should be allowed to define a chain of extension headers as specified
 > in RFC2460. In particular, it would be nice to insert the following
 > headers:
 >   -- Fragment

This is already possible to do:
- specify "ping6" measurement with the packet larger then 1500
- specify "traceroute6", with the desirable packet size, and with an 
optional "do not fragment" flag that sets "no fragmentation"
(which you should skip if you want fragmentation)

I am curious if you would require more capabilities, and which ones?
Or more documentation?

(Emile did some research about it:
https://labs.ripe.net/Members/emileaben/ripe-atlas-packet-size-matters )

 >   -- Destination Options

The way we want to implement this is: user can specify the size of the 
extension header, but we will fill it with padding, as specified in the 
RFC.

We judge this option to be "safe", and we will start implementing this, 
in the new version of the probe firmware.

 >   -- Hop-by-Hop Options

Althou there were some concerns that this option can have impact on the
routers on the path of the packets with such headers, we consider it
"safe" enough to be added to the measurements, and we will work on
implementing it, the same way as with "Destination Options".


Since these features need to be added in the firmware, it will take a 
bit longer till the new FW is released & propagated, and added to the 
API & user interface. Due to upcoming holiday seasons, please allow even 
longer time till you actually see it in production.

 > - HTTP measurements (Tim, please add particular requirements if you 
have any).

(This is a totally different topic, that requires its own thread,
and I will come back to this one at the later date. )

Please let us know if you still have any concerns about our plans to
deploy these IPv6 related features.

Regards,
Vesna