Note to RFC Editor
Please add the RFC3932 Section 4 #1 disclaimer:
The content of this RFC was at one time considered by the IETF,
and therefore it may resemble a current IETF work in progress or a
published IETF work. This RFC is not a candidate for any level of
Internet Standard. The IETF disclaims any knowledge of the
fitness of this RFC for any purpose and in particular notes that
the decision to publish is not based on IETF review for such
things as security, congestion control, or inappropriate
interaction with deployed protocols. The RFC Editor has chosen to
publish this document at its discretion. Readers of this RFC
should exercise caution in evaluating its value for implementation
and deployment. See RFC 3932 for more information.
Chris Newman noted that there may be additional security considerations
worth noting, in enabling spam.