Hmmm ... I went back and look at section 111.2 of the bill. I'm not
sure I read it as requiring any action by the IETF. Section 111.2
merely says that any solution should conform to IETF standards,
e.g., RFCs 2822, 2821.
In the light of this point and the points made by Yakov I suggest we proceed
as follows:
1) Send a note to the IAB telling them that we think that this is their tar
baby and that they should deal with it.
2) Attach to the note a >short< summary of the discusion on ASRG, viz
* Concerns were raised about the practical value of labelling which the
FTC can evaluate for itself in the light of their mandate from Congress.
* Responsibility for defining label terms and their use is properly the
domain of the FTC, the role of the IETF would appear to be limited to
defining the mechanism by which the labels are expressed.
* Various mechanisms for expressing labelling were discussed, these
include overloading the subject line, use of the keywords field, defining a
new header. The advantages of and objections to overloading the subject line
and defining a new header are largely self evident.
* The principal difficulty with use of keyword terms is the risk of
collision. This risk may be mitigated by defining some form of prefix scheme
analogous to the namespace scheme employed in XML. Keyword labels might be
encoded as USFTC:Spam or possibly IETF:Spam. It is likely that IANA
registration will be sufficient to avoid prefix collisions.
Given that we are not the IETF and given that we report through the IAB and
given that political philosophy is out of scope that would appear to be the
sum total of the discussion of the topic here that has relevance.
Phill
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg