This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/mat-wg@ripe.net/
[mat-wg] IPv6 extension headers support on RIPE Atlas
- Previous message (by thread): [mat-wg] IPv6 extension headers support on RIPE Atlas
- Next message (by thread): [mat-wg] IPv6 extension headers support on RIPE Atlas
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ole Troan
otroan at employees.org
Wed Nov 6 23:48:09 CET 2013
>> Do folk see where I'm going with this? > > Where in the standards does it say that a packet with any of these headers should/may/must not be used on the Internet? > > I don't understand the reasoning at all. My opinion is that yes, we perhaps should not create packet generators that send line-rate with small packets with these headers "because we can", but I see little reason not to generally create a test that perhaps does a few pps (or less) of sending these packets (all combinations of headers) to test what happens. > > There is nothing on the Internet today stopping anyone with IPv6 access to generate these packets, so if it breaks the equipment, it's probably better that someone like RIPE, running Atlas probes, discovers this rather than a script kiddie out there then posting it to full-disclosure. wouldn't it be sufficient to support the fragment header initially? hop-by-hop we expect to be severely rate limited anyway, and RH0 is probably blocked. let's be able to test the one that actually matters. cheers, Ole
- Previous message (by thread): [mat-wg] IPv6 extension headers support on RIPE Atlas
- Next message (by thread): [mat-wg] IPv6 extension headers support on RIPE Atlas
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ mat-wg Archives ]