Yes, or a footnote explaining how to turn them off ?

I would like to strongly advocate publishing this document as-is: o Weighing cost vs. benefit it is better to have some warnings produced by missing $TTL statements than errors introduced by $TTL statements in older BIND versions. Recommendation of the use of the ``latest'' version nonwithstanding. Please remember the working title and that the target audience may not be expected to fetch and compile those ``latest'' versions themselves. o A design criterion was that the document be ``short''. Any further discussion about peculiarities of certain major or minor releases is not helpful. o While there is an issue with $TTL, the document in its current state is not broken. There is always some issue not covered in all detail, but that's by design. o Even RIPE documents are not set in stone. Should the operational experience with that document suggest that the $TTL or any other issue do not work out, we can and should review and maybe revise it. o With regard to working group economics I would prefer a living (i.e. published and hopefully used in real life) document over a draft that circulates forever heading for perfection and never hits a ``real end user''. We need that kind of feedback. -Peter