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/ripe-atlas@ripe.net/
[atlas] Spoofing measurenments
- Previous message (by thread): [atlas] Spoofing measurenments
- Next message (by thread): [atlas] Spoofing measurenments
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at inex.ie
Mon Nov 23 17:02:06 CET 2015
On 23/11/2015 13:01, Daniel Karrenberg wrote: > On 23.11.15 13:11 , Nick Hilliard wrote: >> On 23/11/2015 12:03, Daniel Karrenberg wrote: >>> Why exactly do we need to know the exact amount of this problem? >> >> it would be useful to know the sources of the problem. >> > > Those would be the ones not reporting to implement BCP-38. I know of a bunch of organisations that quietly implement bcp38 but don't talk about it. Also, add to the problem that just because a provider supports bcp38, that doesn't mean they support bcp38 everywhere on their network. Like any fence, you can end up with holes appearing due to poor installation or lack of maintenance. Overall it's a problem which would benefit from good quality characterisation. This isn't a request for Atlas to be the mechanism to do this, btw, but there would be value in having an opt-in mechanism with informed consent. This should be sufficient to deal with ethical issues associated with spoof testing. Nick
- Previous message (by thread): [atlas] Spoofing measurenments
- Next message (by thread): [atlas] Spoofing measurenments
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]