So, I propose we modify the current process to work something like this:
1. Tell users that their delegations are lame. 2. Wait, then tell them again if not fixed. 3. Wait, then PULL THE DELEGATION if not fixed.
One interpretation could be "pull the delegation to the lame name server, but leave the working ones in place". Do note, though, that if the zone itself still lists the lame server in its NS RRset, that RRset will override the NS RRset received from the delegating zone, since the latter is non- authoritative information, and recursive name servers may think it's a good idea to validate the NS RRset from one of the authoritative name servers. So... It's not a given that removing the delegation record for the lame name server will actually make much of a difference. Or perhaps you meant "remove the entire delegation"? It sounds kind of drastic... Regards, - Håvard