<html><head><style type="text/css">body {word-wrap: break-word; background-color:#ffffff;}</style></head><body><div style="font-family: sans-serif; font-size: 16px">UNSUBSCRIBE<br><br>REMOVE</div><br><br>-----Original message-----<br><blockquote style="; border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><div style="font-family: sans-serif; font-size: 14px"><b>From: </b>Mikael Abrahamsson <swmike@swm.pp.se><b><br>To: </b>Mike Hughes <mike@smashing.net><b><br>Cc: </b>mat-wg@ripe.net<b><br>Sent: </b>Wed, Nov 6, 2013 11:54:13 CST<b><br>Subject: </b>Re: [mat-wg] IPv6 extension headers support on RIPE Atlas<br><br></div>On Wed, 6 Nov 2013, Mike Hughes wrote:<br><br>> Do folk see where I'm going with this?<br><br>Where in the standards does it say that a packet with any of these headers <br>should/may/must not be used on the Internet?<br><br>I don't understand the reasoning at all. My opinion is that yes, we <br>perhaps should not create packet generators that send line-rate with small <br>packets with these headers "because we can", but I see little reason not <br>to generally create a test that perhaps does a few pps (or less) of <br>sending these packets (all combinations of headers) to test what happens.<br><br>There is nothing on the Internet today stopping anyone with IPv6 access to <br>generate these packets, so if it breaks the equipment, it's probably <br>better that someone like RIPE, running Atlas probes, discovers this rather <br>than a script kiddie out there then posting it to full-disclosure.<br><br>-- <br>Mikael Abrahamsson email: swmike@swm.pp.se<br><br></blockquote></body></html>