catalog zone VERSION number in Bv9ARM doesn't match draft's version number
I note that the VERSION.$CATZ number in the Bv9ARM section on catalog zones insinuates we should use
version.catalog.example. IN TXT "1"
However, the draft specifies
For this memo, the value of one of the RRs in the "version.$CATZ" TXT RRset MUST be setto "2", i.e.
version.$CATZ 0 IN TXT "2"
Our friends over at Knot DNS say
required to include version record
version 0 IN TXT "2"
So, my question actually is: does BIND now support version 2 and the documentation could be adjusted, or does BIND effectively (in current versions) support version 1?