On 5/30/2013 9:58 AM, Melinda Shore wrote:
On 5/29/13 11:56 PM, Adrian Farrel wrote:
Yes, I'm sure.
Your turn now.
Are you sure?
No, not at all.
Let me try to help...
A process document is a normative statement of structure and sequence
for a process. It is the organization's means of saying how things must
be done. That 'must' might include degrees of freedom, of course, but
they key point is that whatever it specifies has formal authority within
the organization.
The current draft is quite explicitly not that.
The current draft is a kindly mentor, sitting around the bar, imparting
sage advice for how something can be reasonably done, within the formal
bounds of IETF rules and culture.
It's only 'force' is whatever credibility the individual reader choose
to assign to the text, as is true for any "Informational" RFC...
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net