Hi Benoit,
At 03:03 25-04-2012, Benoit Claise wrote:
Let me ask a very basic question to everybody, including the other
IESG members: what is the goal of an Applicability Statement?
That was the question which comes to mind on reading the DISCUSS-DISCUSS.
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.
That section mentions Technical Specification. The Applicability
Statement was about restricted "domain of applicability" when using
the Technical Specification.
One little quirk is:
"An AS may not have a higher maturity level in the standards track
than any standards-track TS on which the AS relies (see section 4.1).
For example, a TS at Draft Standard level may be referenced by an AS
at the Proposed Standard or Draft Standard level, but not by an AS at
the Standard level."
There are a few other quirks. Whether they are relevant or not
depends on whether one wants to cherry-pick what's in RFC 2606.
Regards,
-sm
_______________________________________________
marf mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/marf
