Centralized Conferencing Manipulation Protocol (CCMP) Call Flow Examples
RFC 6504

Note: This ballot was opened for revision 10 and is now closed.

(Robert Sparks) Yes

(Ron Bonica) No Objection

(Stewart Bryant) No Objection

(Gonzalo Camarillo) No Objection

(Ralph Droms) No Objection

(Wesley Eddy) No Objection

(Adrian Farrel) No Objection

Comment (2011-05-24 for -)
No email
send info
I am ballotting "No Objection" after only a light skim of the document, mainly trusting the RAI ADs to have checked this document. However, I do wonder whether one sentence in the Abstract is open to misinterpretation. It says:

   objective is to provide a base reference for both protocol
   researchers and developers.

That sounds like the flows in this document form part of the normative definition of the protocol. This is presumably not the intention of this Informational I-D. You can resolve this simply by moving that sentence from the Abstract to the Introduction and qualifying it by deferring to I-D.ietf-xcon-ccmp.

(Stephen Farrell) No Objection

(Russ Housley) No Objection

Comment (2011-05-24 for -)
No email
send info
  The Gen-ART Review by Francis Dupont on 5-Mar-2011 suggested several
  editorial changes.  Please consider them.

(Pete Resnick) (was Discuss) No Objection

Comment (2011-05-26)
No email
send info
I'm again worried about text that is common between documents, especially section 4 of this document. In particular, the information in 4.2 looks like it should be in section 9 of draft-ietf-xcon-ccmp.

(Peter Saint-Andre) No Objection

(Sean Turner) (was Discuss) No Objection