1 / 9

Session Recording Protocol Requirements and Charter

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. Some use cases for recording. Trading floor compliance

dgrigsby
Télécharger la présentation

Session Recording Protocol Requirements and Charter

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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)

  3. 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

  4. 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

  5. Recording from Media Server (AS Initiated)

  6. Recording from B2BUA (RS Initiated)

  7. Recording from UA (Endpoint Initiated)

  8. 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

  9. Discussion

More Related