1 siprec requirements ietf #80 authors: k. rehor, a. hutton, l. portman, r. jain, h. lam
TRANSCRIPT
![Page 1: 1 SIPREC Requirements IETF #80 Authors: K. Rehor, A. Hutton, L. Portman, R. Jain, H. Lam](https://reader036.vdocument.in/reader036/viewer/2022082709/56649d985503460f94a82485/html5/thumbnails/1.jpg)
1
SIPREC Requirements
IETF #80
Authors: K. Rehor, A. Hutton, L. Portman, R. Jain, H. Lam
![Page 2: 1 SIPREC Requirements IETF #80 Authors: K. Rehor, A. Hutton, L. Portman, R. Jain, H. Lam](https://reader036.vdocument.in/reader036/viewer/2022082709/56649d985503460f94a82485/html5/thumbnails/2.jpg)
Status
• Currently submitted -08 draft• Minor updates after AD Comments for -09
2
![Page 3: 1 SIPREC Requirements IETF #80 Authors: K. Rehor, A. Hutton, L. Portman, R. Jain, H. Lam](https://reader036.vdocument.in/reader036/viewer/2022082709/56649d985503460f94a82485/html5/thumbnails/3.jpg)
Changes summary
• Title Change - Added “Use Cases and”• Move Terminology after Introduction section• Minor requirements rewording• Security Section additional text regarding
relationship between CS and RS security• Minor change in Privacy Section• Addition in Acknowledgements
3
![Page 4: 1 SIPREC Requirements IETF #80 Authors: K. Rehor, A. Hutton, L. Portman, R. Jain, H. Lam](https://reader036.vdocument.in/reader036/viewer/2022082709/56649d985503460f94a82485/html5/thumbnails/4.jpg)
Requirements Changes• REQ-012
– “The mechanism MUST include a means for providing the SRS with metadata describing CSs that are being recorded, including the media being used and the identities of parties involved. ”
• REQ-013– “The mechanism MUST include a means for the SRS to be able to correlate RS
media with CS participant media.”• REQ-022
– “The mechanism MUST include a means for the SRS to receive the starting wall clock time for each RS media stream corresponding to the CS participant media. “
• REQ-023– “The mechanism MUST include a means for the SRS to receive the wall clock time
when the Recording Session is paused and resumed.” • REQ-027,028,29
– "The mechanism MUST include a means for ensuring..."
4
![Page 5: 1 SIPREC Requirements IETF #80 Authors: K. Rehor, A. Hutton, L. Portman, R. Jain, H. Lam](https://reader036.vdocument.in/reader036/viewer/2022082709/56649d985503460f94a82485/html5/thumbnails/5.jpg)
Security Section
• Proposed text– “Communication Sessions and Recording Sessions can require different
security levels both for signaling and media, depending on deployment configurations. For some environments, for example, SRS and SRC will be collocated in a secure network region and therefore the RS will not require the same protection level as a CS that extends over a public network, for example. For other environments, the SRS can be located in a public cloud, for example, and the RS will require a higher protection level than the CS. For these reasons, there is not a direct relationship between the security level of Communication Sessions and the security level of Recording Sessions.”
5
![Page 6: 1 SIPREC Requirements IETF #80 Authors: K. Rehor, A. Hutton, L. Portman, R. Jain, H. Lam](https://reader036.vdocument.in/reader036/viewer/2022082709/56649d985503460f94a82485/html5/thumbnails/6.jpg)
Privacy Section
• Original text– “although any user can terminate a CS"
• New text– “although any user can terminate its participation
in a CS."
6
![Page 7: 1 SIPREC Requirements IETF #80 Authors: K. Rehor, A. Hutton, L. Portman, R. Jain, H. Lam](https://reader036.vdocument.in/reader036/viewer/2022082709/56649d985503460f94a82485/html5/thumbnails/7.jpg)
7
Discussion