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] DNS Abuse, Abuse of Privacy & Legitimizing Criminal Activity
- Previous message (by thread): [anti-abuse-wg] DNS Abuse, Abuse of Privacy & Legitimizing Criminal Activity
- Next message (by thread): [anti-abuse-wg] DNS Abuse, Abuse of Privacy & Legitimizing Criminal Activity
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Rob Evans
rhe at nosc.ja.net
Wed Jan 4 10:31:37 CET 2017
Hi, >> The presumed draft you're unhappy about >> (https://datatracker.ietf.org/doc/draft-vixie-dns-rpz/) is >> informational. It is not a standard. >> > not yet a standard. operational word, I guess, is yet. so there is > still time to create awareness and to speak out. More than that, it hasn't yet been adopted by the dnsop working group in the IETF, where a similar discussion is happening, and I don't believe the authors have stated an aim for an individual submission RFC. Raising awareness of RPZ is good, however it's an operational tool that many service providers and enterprises might want in their arsenal (even if as an opt-in). The best place to discuss furthering (or otherwise) RPZ is likely to be on the IETF's dnsop list. Cheers, Rob
- Previous message (by thread): [anti-abuse-wg] DNS Abuse, Abuse of Privacy & Legitimizing Criminal Activity
- Next message (by thread): [anti-abuse-wg] DNS Abuse, Abuse of Privacy & Legitimizing Criminal Activity
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]