Use Cases and Requirements for SIP-Based Media Recording (SIPREC)
RFC 6341

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

(Gonzalo Camarillo; former steering group member) Yes

Yes ( for -)
No email
send info

(Adrian Farrel; former steering group member) No Objection

No Objection ( for -)
No email
send info

(Jari Arkko; former steering group member) No Objection

No Objection ( for -)
No email
send info

(Pete Resnick; former steering group member) No Objection

No Objection ( for -)
No email
send info

(Peter Saint-Andre; former steering group member) No Objection

No Objection (2011-05-23 for -)
No email
send info
REQ-012 refers to "the identities of parties involved". The term "identity" is vague. I suggest changing "identities" to "identifiers" or, even better, "SIP identifiers" or "SIP addresses".

In REQ-024, what is "wall clock time"?

Regarding terms such as "authentication", "confidentiality", "encryption", and "integrity" in REQ-025 through REQ-032, an informational reference to RFC 4949 seems appropriate.

(Ralph Droms; former steering group member) No Objection

No Objection ( for -)
No email
send info

(Robert Sparks; former steering group member) No Objection

No Objection ( for -)
No email
send info

(Ron Bonica; former steering group member) No Objection

No Objection ( for -)
No email
send info

(Russ Housley; former steering group member) No Objection

No Objection ( for -)
No email
send info

(Sean Turner; former steering group member) No Objection

No Objection (2011-05-26 for -)
No email
send info
I support Stephen's discusses.

(Stephen Farrell; former steering group member) (was Discuss) No Objection

No Objection (2011-06-01)
No email
send info

(Stewart Bryant; former steering group member) No Objection

No Objection ( for -)
No email
send info

(Wesley Eddy; former steering group member) No Objection

No Objection ( for -)
No email
send info