[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
--On Wednesday, October 08, 2003 18:27 -0400 "Hollenbeck, Scott" <shollenbeck@verisign.com> wrote:
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.
I think that the problem is in the presence of a wildcard, there is NO way to tell if something really exists or of you just received a synthesized answer based on the wildcard. Having an indication of that in the data returned to the client would be nice, but would require API as well as Protocol changes. The protocol would be the place to start, but the APIs that need adding/changing/modifying are in massively large deployment, change could take years.
--GPG/PGP --> 0xE736BD7E 5144 6A2D 977A 6651 DFBE 1462 E351 88B9 E736 BD7E
---------------------------------------------------------------- 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