> -----Original Message----- > From: DNSOP [mailto:dnsop-boun...@ietf.org] On Behalf Of John Levine > > At yesterday's session, Tale confirmed that since BULK adds so much > new special purpose complexity to DNS servers, the plan is that > support for it will be optional. > > An optional RRTYPE with extra semantics introduces some new > compatibility problems. What happens if a server that doesn't > support BULK tries to load a local zone file with a BULK record. >
Hi John, Thanks for your beautiful question. If a server doesn't support BULK the RR will simply sit there like any other unrecognized RR type. > > Does it reject the whole file, ignore the record, or something else? > What if such a server receives BULK by AXFR? By IXFR? What if one > shows up in a cache from a buggy authoritative server? In all of > these cases, the current RFC 3597 behavior will just return the > BULK record which seems wrong. > The BULK RR simply transfers "intent" or a "recipe" for other records. As you indicate, it would be displayed as TYPEXX and "\#" RDATA encoding but would not interfere with transfers. Since this RFC3597 behavior is expected behavior, these zones could even be housed in a nameserver without support and transferred to one with, again with no impact to the transfer. One thing I feel I must point out is no one other than the zone admin really cares about the recipe just the cupcakes. If your nameserver can't (or won't) make cupcakes then the cupcakes just don't exist. Not understanding the recipe is really no different than not using it. > > I continue to think that this kind of feature belongs in special > purpose DNS servers, not in the core DNS. > I wouldn't want to force any customers to use "XYZ" just to be able to send us their recipes. They probably already have tools and people in place for managing their current "ABC" nameservers. I would also just love for a $GENERATE to make it across the wire intact (assuming both ends are on bind). Thanks again, John > > R's, > John > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop > > -- THESE ARE THE DROIDS TO WHOM I REFER: This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
