pvm@venera.isi.edu (Paul Mockapetris) (03/15/90)
The right policy is: Let people express their preferred capitalization in their own data supplied to the DNS. Thus the NIC gets to decide between EDU and edu for everybody, but Berkeley gets to pick BERKELEY, berkeley, Berkeley, etc. in Berkeley.EDU (or whatever) Match case-insensitively. Preserve the case of data you get. paul
dcrocker@nsl.dec.com (Dave Crocker) (03/15/90)
Paul, I vote in favor of your rule-set.
Makey@Logicon.COM (Jeff Makey) (03/21/90)
In article <9003142059.AA14097@venera.isi.edu> pvm@venera.isi.edu (Paul Mockapetris) writes: >Preserve the case of data you get. BIND 4.8 fails to do this. For example, if I request an A record for "logicon.com" the answer returned has "logicon.com" in it, even though the database has it listed as "Logicon.COM". I actually once found the piece of code responsible for this behavior, but it did not look easy to fix. Followups should probably be directed to the bind@ucbarpa.berkeley.edu mailing list. :: Jeff Makey Department of Tautological Pleonasms and Superfluous Redundancies Department Disclaimer: Logicon doesn't even know we're running news. Internet: Makey@Logicon.COM UUCP: {nosc,ucsd}!logicon.com!Makey