I did an OPS-DIR review of draft-ietf-siprec-protocol-16. This document describes a mechanism for recording SIP sessions, ostensibly, only with the knowledge of the SIP endpoints. The document is clear and mature (which I would hope was the case for a -16 working group ID). In particular, the security considerations section seems quite well written to me. I find no additional operational concerns beyond those present in running any secure SIP infrastructure. I do observe that the stage upon which this standards track ID is dancing on is rather close to the forbidden zone as described by RFC 2804. But the stage was selected when the working group was formed and it is too late to revisit if that was a stage that an IETF working group should be dancing on. Scott