On Wed 25/Apr/2012 19:40:50 +0200 Barry Leiba wrote: >> 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.
This is not the first time I see exchanges of clarifications on this topic among people whom I consider IETF experts. So, I'm worried what will average readers of this document be able to conclude if they happen to wonder about the status of the recommendations made or referred to therein. I doubt that citing [RFC2026] suffices. That was the sense of my previous post, http://www.ietf.org/mail-archive/web/marf/current/msg02329.html in case it wasn't clear. _______________________________________________ marf mailing list [email protected] https://www.ietf.org/mailman/listinfo/marf
