I'm reading the patent now and the summary of the invention is; > The invention includes a caching server having a segregated cache. The > segregation is configured such that referral information and answer > information are stored in different data structures, each data structure > having advantages with regard to finding data of these particular types. In > some embodiments, answer information is stored in a flat data structure > configured such that these data can be located using efficient look-up > techniques, while referral information is stored in a tree based data > structure reflecting the hierarchical nature of these data. Some embodiments > of the invention include methods of determining DNS information from an > associated domain name, the determination including searching the data > structure including the answer information prior to searching the data > structure including the referral information. In various embodiments of the > invention the determined DNS information includes IP addresses, mail exchange > information (MX records), or other data defined within DNS standards. (See, > for example, Mockapetris, P., "Domain Names--Concepts and Facilities," STD > 13, RFC 1034, November 1987. http://www.ietf.org/rfc/rfc1034.txt, and > Mockapetris, P., "Domain Names--Implementation and Specification," STD 13, > RFC 1035, November 1987. http://www.ietf.org/rfc/rfc1035.txt, incorporated > herein by reference.) > > Various embodiments of the invention include a caching server comprising an > answer cache configured to access answer information through a flat data > structure, a referral cache configured to store referral information, and > computer instructions configured to determine DNS information by examining > the answer cache and, responsive to the results of examining the answer > cache, examining the referral cache. > > Various embodiments of the invention include a computer readable medium > having stored thereupon computer code configured for determining DNS > information associated with a domain name, the computer code comprising a > code segment configured for receiving a request for the DNS information > corresponding to a domain name, a code segment configured for examining a > first cache to find the DNS information, the first cache including a flat > data structure and configured to store the DNS information or a pointer to > the DNS information, and a code segment configured to initiate a search of a > second cache if the DNS information is not found by examining the first > cache, the second cache configured to store data referring to further > locations on a computer network wherein the DNS information may be found. > > Various embodiments of the invention include a computer network comprising > means for receiving a request for DNS information corresponding to a domain > name, means for examining a first cache to find the DNS information, the > first cache configured to store the DNS information or a pointer to the DNS > information, and means for searching a second cache if the DNS information is > not found by examining the first cache, the second cache configured to store > data referring to further locations on the computer network wherein the DNS > information may be found. > > Various embodiments of the invention include a computer network comprising a > computing system configured to access a component of the computer network > using a domain name, and a caching server including a cache configured for > translating the domain name into DNS information defined within the DNS > standards such as an IP address MX record set, or the like, and means for > examining the cache in a time that remains essentially constant regardless of > the number of labels comprising the domain name being translated and the size > of the cache. > > Various embodiments of the invention include a method of determining DNS > information, the method comprising receiving a request for DNS information > corresponding to a domain name, and examining an answer cache for answer > information, the answer cache including a hash table configured to store the > answer information, and preferably not including a tree data structure. > > Various embodiments of the invention include a method of determining DNS > information, the method comprising receiving a request for an DNS information > corresponding to a domain name, examining an answer cache to find answer > information, the answer cache including a flat data structure, and responsive > to the examination of the answer cache, searching a referral cache. > > Various embodiments of the invention include a method of storing data in a > cache, the method comprising requesting DNS information, receiving data in > response to the request, classifying the data received as an answer or a > referral, storing the data received in either a referral cache or an answer > cache, selection between the referral cache and the answer cache being > response to the classification. > > Various embodiments of the invention include a method of caching DNS > information, the method comprising requesting DNS information, receiving data > in response to requesting DNS information, classifying the data received as > an answer or a referral, storing the data received in either a referral cache > or an answer cache based on the classification, the answer cache including a > flat data structure, receiving a request for DNS information corresponding to > a domain name, examining the answer cache to find answer information, and > responsive to the examination of the answer cache, searching the referral > cache. > > In various embodiments of the invention the DNS information includes, an IP > address, MX record set, or other data of a data type defined by DNS standards.
I believe that having a segregated referral and answer cache is not needed for the updated resolver algorithm to work and we can leave the language about it out of the draft. Ondrej -- Ondřej Surý (He/Him) ond...@isc.org My working hours and your working hours may be different. Please do not feel obligated to reply outside your normal working hours. > On 20. 3. 2025, at 9:58, Kazunori Fujiwara <fujiw...@jprs.co.jp> wrote: > >> From: Ondřej Surý <ond...@isc.org> >>> On 19. 3. 2025, at 5:42, Shumon Huque <shu...@gmail.com> wrote: >>> >>> I encourage you to resurrect the competing fujiwara-dnsop-resolver-update >>> and get that published (which I will also support). >> >> Let me see. Perhaps, I can resurrect this draft with Fujiwara-san as we are >> probably going to internally do the separation >> between delegations and answers in development version of BIND 9. >> >> Perhaps the fujiwara-dnsop-resolver-update draft should not update RFC 1034 >> Section 5.3.3, but rather provide >> an alternative solution. I guess that would make it more likely to be >> adopted. > > The draft got IPR Disclosure. > https://datatracker.ietf.org/ipr/2907/ > > After then, I tried to update the draft in local. > I find the markdown source of -00 and editing -01 version. > > I put them in my page. > http://member.wide.ad.jp/~fujiwara/draft-fujiwara-dnsop-resolver-update.html > (note that this URL is http. https requires private certificate.) > > please advice how to update. > > Regards, > > -- > Kazunori Fujiwara, JPRS <fujiw...@jprs.co.jp> >
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
