Hi Dave,
At 21:41 21-10-10, Dave CROCKER wrote:
right. I think that clear references and careful use of terminology
should suffice. The specification need not be a tutorial on the
differences between two technologies or RFCs that it cites. Correct?
Yes. A specification is not a tutorial.
I am confused. In a technical specification a normative reference
provides material that is part of the technical detail. It's not
for background or explanation. It is for /use/.
A normative reference provides material which the reader must read to
understand the specification. In this case, it is a way to have a
reference to STD 13 which covers domain name concepts and implementation.
We need to be careful not to let odd formalities get in the way of
basic pragmatics.
I am fine with that as long as there is a good reason.
Regards,
-sm
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html