sitefinder-tech-discuss message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [sitefinder-tech-discuss Home]


Subject: RE: [sitefinder-tech-discuss] Technical issues encountered by a k 12 site


> The issue is *not* that that there are implementations that 
> don't handle
> every possible option and every variation of every protocol.
> 
> The issue *is* that sitefinder changes the practical meaning of DNS
> responses in a way that leads adequately written applications astray.

No, I was asking about a larger issue that's related to the issue you
described.  The message I responded to mentioned home-grown code that had a
problem.  I asked about the thought process that went into writing that code
because it was reported to have experienced a problem with a long-standing
feature of the DNS protocol.  Given that there's an effort underway in the
IETF to clarify RFC 1034's description of wildcard processing, I want to
understand if there's something here that needs to be clarified or changed
to help application developers.

-Scott-

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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [sitefinder-tech-discuss Home]


Powered by eList eXpress LLC