On Jan 20, 2006, at 9:27 AM, Leslie Daigle wrote:
But, the purpose of scoping
techspec was (the usual) one of identifying a problem
we could focus on and solve, without too many distractions.
FWIW, RFC3932 has a taxonomy of documents:
o IETF Working Group (WG) to Standards Track: Includes WG
consensus,
review in the IETF, IETF Last Call, and IESG approval
o IETF WG to Experimental/Informational: Includes WG consensus,
review in the IETF, and IESG approval
o Area Director (AD) sponsored to Standards Track: Includes review
in the IETF, IETF Last Call, and IESG approval
o AD Sponsored Individual to Experimental/Informational: Includes
some form of review in the IETF and IESG approval
o Documents for which special rules exist
o RFC Editor documents to Experimental/Informational
My understanding is that techspec was chartered to address all but
the last.
--aaron
_______________________________________________
Techspec mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/techspec
