Re: wildcard NAPTR ( was [sitefinder-tech-discuss] followup from

[bmanning@karoshi.com]

> >>	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?

	SoCal low-tech dialect is sometimes hard to parse.
	Perhaps this will make more sense:

	the propoal outlined above recommends that -IF- wildcards
	are to be used in the context of sitefinder, that it would 
	be more advantagious to select the NAPTR rr-type than the 
	A rr-type.  Selection of the A rr-type raises the issue
	of which ports/services are to be enabled and the attendent
	public notification concerns.  Use of NAPTR has fewer
	"side effects" on the expectations of application developers
	and end users and also has the advantage that it meets
	the (now) stated objectives of being an inovative technique.

	better?

> Kee Hinckley

--bill

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