Re: [Fwd: Re: ID Tracker State Update Notice: draft-ietf-opes-ocp-core]

   OCP extensions are allowed to change normative OCP Core requirements
   for OPES processors and callout servers. However, OCP extensions
   SHOULD NOT make such changes and MUST require on a "MUST"-level that
   such changes are negotiated prior to taking effect. Informally, this
   specification defines compliant OCP agent behavior until changes to
   this specifications (if any) are successfully negotiated.

Is "negotiated" used to mean a protocol operation in the second sentence,
and as a action within a standards body in the third sentence.

I think that the IESG concern about negotiation is that if the state
machine for the core negotiaion changes as a result of negotiation (in
the protocol sense), you can easily get a resulting state machine that
is unmanageable.  Infinite loops, deadlocks, etc.  Can you add verbiage
that indicates why those bad things are not possibilities?

Hilarie