It is well-known that IETF documents have to address security issues. RFC 3552 provides guidelines how to write them. RFC 4101 illustrates how to write about protocol models; this documents reminds document authors to give reviewers (including reviewers from the security community) a chance to quickly determine the answers for the following three questions:
1. What problem is the protocol trying to achieve?
2. What messages are being transmitted and what do they mean?
3. What are the important, but unobvious, features of the protocol?
There is, however, also a document that outlines some operations & management aspects that should be considered in IETF documents as well. Here is the document that provides more background material:http://www.ietf.org/internet-drafts/draft-harrington-operations-and-management-00.txt
Here is the abstract:
New protocols or protocol extensions are best designed with dueconsideration of operations and management issues related to the protocol. Retrofitting operations and management recommendations to protocols is sub-optimal. The purpose of this document is to provide guidance to authors of protocol documents about aspects to consider related to the operations and management that should be considered for inclusion in documents defining requirements or functionality of new protocols or protocol extensions.