1 Session Recording Protocol Requirements and Charter IETF 76, Hiroshima Andy Hutton and Leon Portman on behalf of the team Draft authors: Kenneth Rehor, Rajnish Jain, Leon Portman, Andrew Hutton, Vijay Gurbani, Hadriel Kaplan

2 Some use cases for recording Trading floor compliance Contact Center quality management Customer analytics Financial institution transactions Insurance and healthcare regulations Emergency services regulations In many cases it’s not a legal requirement, it’s a user requirement – users wanting to protect themselves (i.e., non-repudiation)

Goals Managing delivery of media from a communication system to a recording device Replace proprietary and incompatible mechanisms Reduce complexity and cost Accelerate adoption of SIP-based solutions in the enterprises 3

Problem Statement Unique requirements that are not addressed in the current SIP protocol specifications Some examples – Distinction between the session that is being recorded and recording session – Ability to indicate recording session (RAVEN) – Ability to disable recording session (RAVEN) – Recording Metadata Definition and Delivery 4

Recording from Media Server (AS Initiated) 5

Recording from B2BUA (RS Initiated) 6

Recording from UA (Endpoint Initiated) 7

Charter Proposal The scope of the activity includes: – Recorder Control (Session Initiation) – Session metadata content and format – Security mechanisms, including transport and media encryption – Negotiation of recording media streams (E.g. Mixed or Not Mixed). The group will produce: – Updated Requirements, Use Cases, Architecture draft – Specification for a Session Recording Protocol (i.e. SIP extensions) Timeline: – Apr 2010 Requirements, Use Cases, Architecture to IESG as Informational Draft – Nov 2010 Submit protocol draft to IESG as standards track 8

9 Discussion