3 ms·
Interesting point. Blacklisting based on the /64 won't work, due to the potential to deny service to legitimate users, so what will take its place? Also, it's
by alexwestholm 16y ago
Interesting point. Blacklisting based on the /64 won't work, due to the potential to deny service to legitimate users, so what will take its place?
Also, it's already started: http://mailchannels.com/blog/?p=114 http://mailchannels.com/blog/?p=114 (First IPv6 Spam Message Caught in the Wild)
- iwwr 16y agoWhitelisting. Only allow mail from certified domains or servers. Have a sort of certification/cost barrier system in place to prevent spammers from gaining access. That, or a distributed web-of-trust scenario with authoritative entities like google in the chain.
- mike-cardwell 16y agoI don't understand this statement: "Blacklisting based on the /64 won't work, due to the potential to deny service to legitimate users," At the moment, we have multiple users sharing a single IPv4 address, so when that gets listed, there is collateral damage. If we change to having lots of users sharing the same IPv6 /64 and we start listing /64 there is no change to the collateral damange... If every user starts getting their own /64 to send mail from, then this will reduce the collateral damage, but make it harder to list. In which case, larger blocks will get listed, again bringing the collateral damage back up to the same level we already have it at...
- zaphoyd 16y agoIn general, a /64 is being assigned in a similar way to a single IPv4 address is used today. Blacklisting a /64 would be similar to blacklisting a single IPv4 with multiple machines behind a NAT. If anything this gives us more control. You can start by blacklisting individual v6 addresses, and if you notice an above average number are from the same /64 knock off the whole thing.