Re: [apps-discuss] Applicability Statements

[Scott Brim <[e-mail]>]

We have always done the equivalent of applicability statements where
we thought they were necessary.  We are not stupid, and we do produce
what we think people need to be able to use our products effectively.
Sometimes they are in separate documents, sometimes part of "framework
documents", sometimes included in the protocol specs themselves, and
sometimes split across multiple documents with different focus issues.

We have always done applicability "statements", but rarely standalone
application statement documents.  That's okay ... but the problem is
when WGs don't get around to documenting applicability, or do a
haphazard job of it.  Then you get disagreements and incompatibility,
and the IETF hasn't done its job.  So, while we don't usually need
separate applicability documents, we do need to document any
applicability issues for those who weren't in the meeting room.

I believe we should put "deal with applicability questions" on the
shepherding checklist.  The WG decides what the most appropriate way
to document applicability is, but they make an explicit decision about
how to do it.

Scott