Hi Barry,
Let me ask a very basic question to everybody, including the other IESG
members: what is the goal of an Applicability Statement?
1. Explain how the technical specifications are used "in the wild", as you
mentioned. So a deployment experience document
2. Or explain how the technical specifications should be used for the
different use cases (generally specified in a requirement document)
When I read RFC 2026 section 3.2, I conclude for 2.
Yes, 2. But an AS doesn't necessarily (perhaps usually doesn't) cover
every use case. Consider the greylisting document that's also on this
week's telechat: it's describing how to use SMTP for a specific use
case, to do a specific thing. Many AS documents will be of that
nature, talking about certain use cases, but not every possible one.
https://datatracker.ietf.org/doc/draft-ietf-appsawg-greylisting/ is
different, as its scope is well defined, starting with the title: "Email
Greylisting: An Applicability Statement for SMTP"
On the other hand, "Creation and Use of Email Feedback Reports: An
Applicability Statement for the Abuse Reporting Format (ARF)" points to
a generic ARF application statement... which is not.
Regards, Benoit.
Therefore, I'm in favor to mention how fraud, not-spam, virus should be
used.
The working group chose to center the marf-as document on the cases
that are actually in use today. I think that's a fine choice. It
might be reasonable to have one or more AS documents about the
less-common use cases, and that/those could be written later. This
isn't that document.
Barry
_______________________________________________
marf mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/marf
