Hi Paul, On 11/01/16 16:48, Paul Hoffman wrote: > - It feels like combining both class and type into ClassType might be > over-optimization. Since Class will almost always be IN, why not just > have this as its own object member?
I was also looking at this and there are some values which are very common so you could add to the specification "if not specified then X is Y" assumptions. Cheers, Jerry _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop