RFC 7866 on Session Recording Protocol

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



A new Request for Comments is now available in online RFC libraries.

        
        RFC 7866

        Title:      Session Recording Protocol 
        Author:     L. Portman, H. Lum, Ed.,
                    C. Eckel, A. Johnston, A. Hutton
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2016
        Mailbox:    leon.portman@gmail.com, 
                    henry.lum@genesyslab.com, 
                    eckelcu@cisco.com, 
                    alan.b.johnston@gmail.com, 
                    andrew.hutton@unify.com
        Pages:      45
        Characters: 104535
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-siprec-protocol-18.txt

        URL:        https://www.rfc-editor.org/info/rfc7866

        DOI:        http://dx.doi.org/10.17487/RFC7866

This document specifies the use of the Session Initiation Protocol
(SIP), the Session Description Protocol (SDP), and the Real-time
Transport Protocol (RTP) for delivering real-time media and metadata
from a Communication Session (CS) to a recording device.  The Session
Recording Protocol specifies the use of SIP, SDP, and RTP to
establish a Recording Session (RS) between the Session Recording
Client (SRC), which is on the path of the CS, and a Session Recording
Server (SRS) at the recording device.  This document considers only
active recording, where the SRC purposefully streams media to an SRS
and all participating user agents (UAs) are notified of the
recording.  Passive recording, where a recording device detects media
directly from the network (e.g., using port-mirroring techniques), is
outside the scope of this document.  In addition, lawful intercept is
outside the scope of this document.

This document is a product of the SIP Recording Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC





[Index of Archives]     [IETF]     [IETF Discussion]     [Linux Kernel]

  Powered by Linux