1 / 7

SIPREC Protocol (draft-ietf-siprec-protocol-03)

SIPREC Protocol (draft-ietf-siprec-protocol-03). March 30, 2012 IETF 83. Authors: L. Portman, H. Lum, A. Johnston, A. Hutton. Changes since last revision (1). Metadata snapshot request Section 8.2 SRS “the SRS MUST send an UPDATE request without an SDP offer”

csilla
Télécharger la présentation

SIPREC Protocol (draft-ietf-siprec-protocol-03)

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. SIPRECProtocol(draft-ietf-siprec-protocol-03) March 30, 2012 IETF 83 Authors: L. Portman, H. Lum, A. Johnston, A. Hutton

  2. Changes since last revision (1) • Metadata snapshot request • Section 8.2 SRS • “the SRS MUST send an UPDATE request without an SDP offer” • “SRS MAY generate an INVITE request without an SDP offer but this MUST not include a metadata snapshot request” • Section 8.1 SRC • “When the SRC sends a full metadata snapshot, the SRC MUST send an INVITE or an UPDATE request with an SDP offer and the "recording-session" disposition

  3. Changes since last revision (2) • Is siprecmetadata mandatory to implement? • Reworded section 5.1 and 5.2 to mandate SRC and SRS to include siprec option tag in Require header

  4. Changes since last revision (3) • Media stream labels can be reused • "The scope of the label name only applies to the same SIP message as the SDP, meaning that the label name can be reused by another media stream within the same recording session.”

  5. Changes since last revision (4) • Allow SRS to remove media streams in the recording session • Extend record and recordpref SDP attributes to session level in addition to media level • Remove mentions to RTP/RTCP multiplexing (RFC5761) to avoid confusions as a feature mandatory to implement

  6. Changes since last revision (5) • Rename feature tags from “src” to “+sip.src” and “srs” to “+sip.srs” • When a SRC or SRS registers, they must include the “+sip.src” or “+sip.srs” feature tags in the REGISTER request to indicate that it is a SRC or SRS

  7. Issues • Does the draft need to mention the difference in recording a CS that useSDES and DTLS-SRTP for security?

More Related