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/anti-abuse-wg@ripe.net/
[anti-abuse-wg] RIPE policy
- Previous message (by thread): [anti-abuse-wg] RIPE policy
- Next message (by thread): [anti-abuse-wg] RIPE policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marco Hogewoning
marcoh at marcoh.net
Wed Mar 9 14:48:31 CET 2011
> OTOH, IPv4 extensively uses NAT, so that blocking the wrong IP may > affect an entire network behind it. Traditional DNSBLs would be safer > without such widespread use of NAT, which can be taken down using IPv6. While on this topic, be aware the same could happen with IPv6 very easily. As people will no longer get a single address but a whole range, there will probably be some need to aggregate. As assignments per end site can vary between /64 and /48 you run the risk of blocking 65.000 customers while you intended to block one. To partially solve these issues there is now a attribute in de RIPE Database called assignment size, indicating the size of assignment to a single end site. If you are working on black- or grey listings you might want to have a look at RIPE-513 which describes the use of this new attribute. For your information, MarcoH (co-author of the document)
- Previous message (by thread): [anti-abuse-wg] RIPE policy
- Next message (by thread): [anti-abuse-wg] RIPE policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]