Media Control Channel Framework (CFW) Call Flow Examples
RFC 7058

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

(Richard Barnes) Yes

(Spencer Dawkins) Yes

(Jari Arkko) No Objection

(Stewart Bryant) No Objection

Comment (2013-09-12)
No email
send info
I am taking a position of no objection based on a quick look which indicated that this text has no impact on Routing.

(Gonzalo Camarillo) No Objection

(Stephen Farrell) No Objection

Comment (2013-09-12)
No email
send info

- Some of the tools page links seem to be broken by
the formatting used, e.g. [1] doesn't go to the
security considerations. Not sure if that's easy
to fix or worth fixing though.

   [1] http://tools.ietf.org/html/draft-ietf-mediactrl-call-flows-13#section-8

- "variegated bouquet of services": heh, not many RFCs
have those:-)

(Brian Haberman) No Objection

(Martin Stiemerling) No Objection

(Sean Turner) No Objection

Comment (2013-09-12)
No email
send info
s7.2.1: "mess with" could be better phrased ;)

Barry Leiba No Record

Comment (2013-09-12)
No email
send info
I'm intentionally staying with "no position" on this, rather than deferring it, as Richard has assured me that a sufficient number of the right set of eyes have been on it, and as I trust my fellow ADs to have it covered.