Hi Erik,
Perhaps I don't understand how state management is separable from the
behavior description of the protocol, but isn't the basic state
management (when/how state is created, maintained, and destroyed)
something which needs to be in the behavioral description of the protocol?
Thus I don't understand how state management can be a piece which can be
done later.
I agree. I think the state management document should be included in the
Architecture and Protocol document. If there needs to be a document
split, I'd suggest having the architecture document seperate, which
would look more like a framework type of document - so informational
in nature. Then there could be a Protocol document.