Re: New I-D:draft-kaplan-enum-source-uri-00.txt

On 2007/12/11 23:12, Hadriel Kaplan <[email protected]> wrote:
> Howdy,
>
> We just submitted an I-D for a mechanism to include the source URI
> information in ENUM queries, primarily targeted at including the
> From/PAI SIP/Tel URI of the SIP Request which triggered the ENUM
> lookup, so the ENUM server can provide a response based on that. This
> is useful for performing source-based ENUM routing and filtering.

I can see the motivation. As others have stated, this is not appropriate
for the public e164.arpa tree.

The DNS protocol makes some assumptions about the environment it
operates in. Caching, idempotent queries, public queries, ...
We have already layered a few additions on the base protocol, from DNS views 
(different answers for different clients), TSIG (authentication of clients)
to private roots.

With this proposal, the basic premise of DNS lookups (FQDN + RRTYPE => RRSET)
is extended once more. DNS is thus used as an almost generic lookup protocol.

Yes, the incremental change ist not that big. The question remains: 

Have we now reached the point where we should stop fiddling with the
DNS protocol and should instead look for a directory lookup protocol
which was designed from the beginning to support authenticated and
complex queries returning structured data?

As this is not for e164.arpa, but private trees instead, do you actually
need the sub-tree delegation feature of DNS/ENUM? Or is ENUM just used
as a simple query protocol into a single database?

/ol
-- 
// Otmar Lendl <[email protected]>, T: +43 1 5056416 - 33, F: - 933
// nic.at Internet Verwaltungs- und Betriebsgesellschaft m.b.H
// http://www.nic.at/  LG Salzburg, FN 172568b, Sitz: Salzburg