Re: Send-N draft: draft-bellis-enum-send-n-02 published

[email protected] wrote:

> With overlapped dialling, one would send a DNS query with QTYPE = NAPTR to 
> see if a full ENUM record is available.
> 
> With Send-N, the full record isn't available, but a Send-N NAPTR is 
> returned in its place.  This is the standard DNS behaviour, with no 
> special processing required at either end and it's all done in one DNS 
> request round-trip.
> 
> If a different RRtype is used for Send-N, the DNS client receiving NOHOST 
> for the QTYPE = NAPTR lookup would need to send a second DNS request with 
> QTYPE = SENDN.  That's specifically what we're trying to avoid.

Then go with the additional records suggestion then, since you more than
likely will have to poll 2 separate databases, what exactly is wrong
with returning this information as either a pseudo RR like EDNS0 or
something to that effect?

Actually that would be the smart way to do it, the client sends a EDNS0
requests or something similar asking for send-n too, otherwise only
NAPTR records are returned.

-- 

Best regards,
 Duane