1 / 12

SIPREC Protocol (draft-portman-siprec-protocol-05)

SIPREC Protocol (draft-portman-siprec-protocol-05). June 28, 2011 IETF 81. Authors: L. Portman, H. Lum, A. Johnston, A. Hutton. Status. Currently - 05 draft Changes since last revision Issues. Changes since last revision (1). Section 6.1

hasana
Download Presentation

SIPREC Protocol (draft-portman-siprec-protocol-05)

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-portman-siprec-protocol-05) June 28, 2011 IETF 81 Authors: L. Portman, H. Lum, A. Johnston, A. Hutton

  2. Status • Currently -05 draft • Changes since last revision • Issues

  3. Changes since last revision (1) • Section 6.1 • Clarified recording indicator usage with call flow • Recording indicator is used a declaration when recording is enabled by one endpoint • Does not indicate which SRC is recording when there are multiple SRCs in the call path

  4. Changes since last revision (2) • Section 6.2 • Recording-aware UA is obliged to render recording indication to the user • Recording-aware automatons (ie. Mixer, IVR, PSTN gateway) needs to render indication through other means

  5. Changes since last revision (3) • Added a=recordpref:nopreference as a value to explicitly state no recording preference

  6. Changes since last revision (4) • Metadata snapshot request • Simple text content • No requirement for SRC to process content other than the format type

  7. Issues (1) • Metadata snapshot request • How simple do we want the request to be? • Numeric reason code? • Plain text, but need to address internationalization? • What does a snapshot consist of? • Metadata XML only? • Metadata + SDP?

  8. Issues (2) • Metadata format needs to be transport agnostic (REQ-014) • Is the current mechanism (using a=label) on the protocol side considered transport agnostic for the metadata format?

  9. Issues (3) • Need for options tag for recording session in addition to feature tag (src/srs)?

  10. Issues (4) • SRS-initiated recording session • SRS-initiated recording is out-of-scope • Should we allow SRS to initiate a recording session? What use case does this address?

  11. Other changes pending • Editorial changes requested from reviewers • SRS initiated recording session • Add text to explain usage • SRS may initiate recording session, but only SRC can initiate recording a CS or part of a CS

  12. Next Steps • Are we ready to merge recommendations from draft-eckel-siprec-rtp-rec into a single draft • Adopt as working group item?

More Related