On Thu, Sep 13, 2018 at 09:38:54AM +1100, Ólafur Guðmundsson wrote: > On Thu, Sep 13, 2018 at 9:13 AM, Benjamin Kaduk <ka...@mit.edu> wrote: > > > Hi Ólafur, > > > > Before I get into the inline comments, I should note something that I only > > noticed after I posted my ballot position: although everyone I know always > > refers to this query as "ANY", that's the command-line interface in dig(1), > > etc., it seems that the specified string to refer to this query is > > officially "*". That's what 1035 uses and that's what's in the IANA > > registry; RFC 6895 has a clarification in a parenthetical "* (ALL/ANY)", > > but I didn't see much precedent for only using "ANY" in an RFC to refer to > > this query. To be clear, I don't object to using that as the primary term > > -- it is, after all, the common usage! But perhaps it's worth a short > > mention at the start that we use "ANY" to refer to QTYPE 255, registered as > > "*". The reader can perhaps infer this fact from the IANA considerations > > that update that entry in the registry to also refer to this document, but > > it would be nice for the relationship to be more explicit. > > > That is a great point something like: > RFC1035 defined "*" as type 255 but DNS applications have used the "ANY" > word to refer to that type code"
That works to get the point across, sure. Thanks, Benjamin _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
