Re: wildcard NAPTR ( was [sitefinder-tech-discuss] followup from 15oct secsac )

[Andrew Newton <anewton@verisignlabs.com>]

Kee Hinckley wrote:

> At 7:35 PM -0400 10/21/03, Andrew Newton wrote:
>
> > bmanning@karoshi.com wrote:
> >
> > >     in any case... how would folks feel about something like this:
> > >
> > >     com.  in soa (bits'o'rr)
> > >           in ns  lumpy.
> > >           in ns  gravy.
> > >     *     in naptr (naptr-bits)
> > >
> > >     whango z tango --- no pesky A rr... :)
>
>
> Could we have this in English?

Use a wildcard NAPTR record to target specific application services (not 
just application protocols) such as web browsing using HTTP (i.e. not 
SOAP using HTTP).

> > Well, I'm not sure what the competitors are.  A change to the DNS 
> > protocol would require adoption by both infrastructe and applications. 
> > This is just change to the applications.
>
>
> And I'm not sure if that's serious or a joke.  The A record is requiring 
> a change to applications as well.  I haven't heard anyone using the word 
> "just" in that regards though.

Suggestions about modifying the DNS protocol may require changes to 
authoritative servers, caches, resolvers and will require changes to 
applications.  On top of that, they may still not make the necessary 
distinction between applicaton services, application protocols, and hosts.

-andy



----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.elistx.com/unsubscribe>