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/[email protected]/
[cooperation-wg] DNS-based filtering
- Previous message (by thread): [cooperation-wg] DNS-based filtering
- Next message (by thread): [cooperation-wg] DNS-based filtering
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Tue Jan 28 14:02:34 CET 2014
On 26 Jan 2014, at 15:08, Michele Neylon - Blacknight <michele at blacknight.com> wrote: > And I thought this paper was about domains more than domain registries? Indeed it is. However the point I made remains. So I repeat it: DNS service for some domain does not necessarily rest with a single entity. ie all the authoritative name servers for a domain might not be under the same administrative and operational control: SLAs, reporting and incident response procedures, legal jurisdictions, contracts, T&Cs, etc. Even if all the names you manage for your customers are on Blacknight's DNS servers Michele, it doesn't follow that every domain name registration with every other registrar follows that model. A government or regulator who is thinking about deploying DNS filtering/blocking or whatever needs to bear that in mind.
- Previous message (by thread): [cooperation-wg] DNS-based filtering
- Next message (by thread): [cooperation-wg] DNS-based filtering
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]