Re: wildcards and n-send NAPTRs

On 27 Jun 2008, at 13:33, Clive D.W. Feather wrote:

> No change to the semantics of wildcarding is being proposed.

Sorry Clive, you're wrong. There are. The draft makes wildcard  
processing conditional on the RDATA that's in one of these nsend  
NAPTRs. This *is* a change in semantics and the consequences of that  
have still to be worked through. You even go on to concede the  
semantics are changed by pointing out a corner case where a badly  
structured nsend NAPTR causes an infinite loop.

Now it's one thing having applications playing in this nsend world  
perform loop detection. [How? And where is this documented?] But are  
there scenarios where name servers, espeically full service resolvers,  
could end up having to do loop detection? Some further analysis is  
required. IMO, the proponents of nsend need to do that work and  
convince this WG and dnsop that there is no impact on either the DNS  
protocol or implementations.

It's all very well for the draft to say nsend SHOULD NOT be used with  
wildcards. But it really has to say something about what happens if/ 
when that advice is not followed.