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

> Send-n is not implemented in the enum client.

Not in an end-user client, no.
 
> Implement something else (i.e. a client to another database which has 
length
> information) in the same server.

When devising this at NICC we did consider several alternatives.

Using NAPTR records in DNS was ultimately chosen for several reasons, the 
most compelling of which is because it's simply optimally efficient if 
you're already doing a DNS lookup for NAPTR records in an ENUM-like tree 
to get back a Send-N record immediately rather than have to issue a second 
lookup request (whether that request be another protocol or a DNS query 
with a different QTYPE).

Granted this isn't faithful to the public ENUM dogma that says that 
lookups should only be done on full numbers.  However this isn't intended 
for public ENUM.

Ray