idnits 2.17.1 draft-ietf-siprec-protocol-10.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (May 17, 2013) is 3996 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-22) exists of draft-ietf-siprec-metadata-11 == Outdated reference: A later version (-12) exists of draft-ietf-siprec-architecture-07 -- Obsolete informational reference (is this intentional?): RFC 6222 (Obsoleted by RFC 7022) Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 SIPREC L.P. Portman 3 Internet-Draft NICE Systems 4 Intended status: Standards Track H. Lum, Ed. 5 Expires: November 18, 2013 Genesys 6 C. Eckel 7 Cisco 8 A. Johnston 9 Avaya 10 A. Hutton 11 Siemens Enterprise Communications 12 May 17, 2013 14 Session Recording Protocol 15 draft-ietf-siprec-protocol-10 17 Abstract 19 This document specifies the use of the Session Initiation Protocol 20 (SIP), the Session Description Protocol (SDP), and the Real Time 21 Protocol (RTP) for delivering real-time media and metadata from a 22 Communication Session (CS) to a recording device. The Session 23 Recording Protocol specifies the use of SIP, SDP, and RTP to 24 establish a Recording Session (RS) between the Session Recording 25 Client (SRC), which is on the path of the CS, and a Session Recording 26 Server (SRS) at the recording device. 28 Status of This Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF). Note that other groups may also distribute 35 working documents as Internet-Drafts. The list of current Internet- 36 Drafts is at http://datatracker.ietf.org/drafts/current/. 38 Internet-Drafts are draft documents valid for a maximum of six months 39 and may be updated, replaced, or obsoleted by other documents at any 40 time. It is inappropriate to use Internet-Drafts as reference 41 material or to cite them other than as "work in progress." 43 This Internet-Draft will expire on November 18, 2013. 45 Copyright Notice 47 Copyright (c) 2013 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (http://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with respect 55 to this document. Code Components extracted from this document must 56 include Simplified BSD License text as described in Section 4.e of 57 the Trust Legal Provisions and are provided without warranty as 58 described in the Simplified BSD License. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 63 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 64 3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4 65 4. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 66 5. Overview of operations . . . . . . . . . . . . . . . . . . . 5 67 5.1. Delivering recorded media . . . . . . . . . . . . . . . . 5 68 5.2. Delivering recording metadata . . . . . . . . . . . . . . 7 69 5.3. Receiving recording indications and providing recording 70 preferences . . . . . . . . . . . . . . . . . . . . . . . 8 71 6. SIP Handling . . . . . . . . . . . . . . . . . . . . . . . . 9 72 6.1. Procedures at the SRC . . . . . . . . . . . . . . . . . . 9 73 6.1.1. Initiating a Recording Session . . . . . . . . . . . 9 74 6.1.2. SIP extensions for recording indication and 75 preference . . . . . . . . . . . . . . . . . . . . . 10 76 6.2. Procedures at the SRS . . . . . . . . . . . . . . . . . . 10 77 6.3. Procedures for Recording-aware User Agents . . . . . . . 11 78 7. SDP Handling . . . . . . . . . . . . . . . . . . . . . . . . 11 79 7.1. Procedures at the SRC . . . . . . . . . . . . . . . . . . 12 80 7.1.1. SDP handling in RS . . . . . . . . . . . . . . . . . 12 81 7.1.1.1. Handling media stream updates . . . . . . . . . . 13 82 7.1.2. Recording indication in CS . . . . . . . . . . . . . 13 83 7.1.3. Recording preference in CS . . . . . . . . . . . . . 14 84 7.2. Procedures at the SRS . . . . . . . . . . . . . . . . . . 14 85 7.3. Procedures for Recording-aware User Agents . . . . . . . 16 86 7.3.1. Recording indication . . . . . . . . . . . . . . . . 16 87 7.3.2. Recording preference . . . . . . . . . . . . . . . . 17 88 8. RTP Handling . . . . . . . . . . . . . . . . . . . . . . . . 18 89 8.1. RTP Mechanisms . . . . . . . . . . . . . . . . . . . . . 18 90 8.1.1. RTCP . . . . . . . . . . . . . . . . . . . . . . . . 18 91 8.1.2. RTP Profile . . . . . . . . . . . . . . . . . . . . . 19 92 8.1.3. SSRC . . . . . . . . . . . . . . . . . . . . . . . . 19 93 8.1.4. CSRC . . . . . . . . . . . . . . . . . . . . . . . . 20 94 8.1.5. SDES . . . . . . . . . . . . . . . . . . . . . . . . 20 95 8.1.5.1. CNAME . . . . . . . . . . . . . . . . . . . . . . 20 96 8.1.6. Keepalive . . . . . . . . . . . . . . . . . . . . . . 20 97 8.1.7. RTCP Feedback Messages . . . . . . . . . . . . . . . 20 98 8.1.7.1. Full Intra Request . . . . . . . . . . . . . . . 21 99 8.1.7.2. Picture Loss Indicator . . . . . . . . . . . . . 21 100 8.1.7.3. Temporary Maximum Media Stream Bit Rate Request . 22 101 8.1.8. Symmetric RTP/RTCP for Sending and Receiving . . . . 22 102 8.2. Roles . . . . . . . . . . . . . . . . . . . . . . . . . . 22 103 8.2.1. SRC acting as an RTP Translator . . . . . . . . . . . 23 104 8.2.1.1. Forwarding Translator . . . . . . . . . . . . . . 23 105 8.2.1.2. Transcoding Translator . . . . . . . . . . . . . 24 106 8.2.2. SRC acting as an RTP Mixer . . . . . . . . . . . . . 25 107 8.2.3. SRC acting as an RTP Endpoint . . . . . . . . . . . . 25 108 8.3. RTP Session Usage by SRC . . . . . . . . . . . . . . . . 26 109 8.3.1. SRC Using Multiple m-lines . . . . . . . . . . . . . 26 110 8.3.2. SRC Using Mixing . . . . . . . . . . . . . . . . . . 27 111 8.4. RTP Session Usage by SRS . . . . . . . . . . . . . . . . 28 112 9. Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . 29 113 9.1. Procedures at the SRC . . . . . . . . . . . . . . . . . . 29 114 9.2. Procedures at the SRS . . . . . . . . . . . . . . . . . . 30 115 9.2.1. Formal Syntax . . . . . . . . . . . . . . . . . . . . 32 116 10. Persistent Recording . . . . . . . . . . . . . . . . . . . . 32 117 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32 118 11.1. Registration of Option Tags . . . . . . . . . . . . . . 32 119 11.1.1. siprec Option Tag . . . . . . . . . . . . . . . . . 32 120 11.1.2. record-aware Option Tag . . . . . . . . . . . . . . 33 121 11.2. Registration of media feature tags . . . . . . . . . . . 33 122 11.2.1. src feature tag . . . . . . . . . . . . . . . . . . 33 123 11.2.2. srs feature tag . . . . . . . . . . . . . . . . . . 33 124 11.3. New Content-Disposition Parameter Registrations . . . . 34 125 11.4. Media Type Registration . . . . . . . . . . . . . . . . 34 126 11.4.1. Registration of MIME Type application/rs-metadata . 34 127 11.4.2. Registration of MIME Type application/rs-metadata- 128 request . . . . . . . . . . . . . . . . . . . . . . 34 129 11.5. SDP Attributes . . . . . . . . . . . . . . . . . . . . . 35 130 11.5.1. 'record' SDP Attribute . . . . . . . . . . . . . . . 35 131 11.5.2. 'recordpref' SDP Attribute . . . . . . . . . . . . . 35 132 12. Security Considerations . . . . . . . . . . . . . . . . . . . 36 133 12.1. Authentication and Authorization . . . . . . . . . . . . 36 134 12.2. RTP handling . . . . . . . . . . . . . . . . . . . . . . 37 135 12.3. Metadata . . . . . . . . . . . . . . . . . . . . . . . . 37 136 12.4. Storage and playback . . . . . . . . . . . . . . . . . . 38 137 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 38 138 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 38 139 14.1. Normative References . . . . . . . . . . . . . . . . . . 38 140 14.2. Informative References . . . . . . . . . . . . . . . . . 39 141 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40 143 1. Introduction 144 This document specifies the mechanism to record a Communication 145 Session (CS) by delivering real-time media and metadata from the CS 146 to a recording device. In accordance to the architecture 147 [I-D.ietf-siprec-architecture], the Session Recording Protocol 148 specifies the use of SIP, SDP, and RTP to establish a Recording 149 Session (RS) between the Session Recording Client (SRC), which is on 150 the path of the CS, and a Session Recording Server (SRS) at the 151 recording device. 153 SIP is also used to deliver metadata to the recording device, as 154 specified in [I-D.ietf-siprec-metadata]. Metadata is information 155 that describes recorded media and the CS to which they relate. 157 The Session Recording Protocol intends to satisfy the SIP-based Media 158 Recording requirements listed in [RFC6341]. 160 In addition to the Session Recording Protocol, this document 161 specifies extensions for user agents that are participants in a CS to 162 receive recording indications and to provide preferences for 163 recording. 165 2. Terminology 167 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 168 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 169 document are to be interpreted as described in [RFC2119]. 171 3. Definitions 173 This document refers to the core definitions provided in the 174 architecture document [I-D.ietf-siprec-architecture]. 176 The RTP Handling section uses the definitions provided in "RTP: A 177 Transport Protocol for Real-Time Application" [RFC3550]. 179 4. Scope 181 The scope of the Session Recording Protocol includes the 182 establishment of the recording sessions and the reporting of the 183 metadata. The scope also includes extensions supported by User 184 Agents participating in the CS such as indication of recording. The 185 user agents need not be recording-aware in order to participate in a 186 CS being recorded. 188 The following items, which are not an exhaustive list, do not 189 represent the protocol itself and are considered out of the scope of 190 the Session Recording Protocol: 192 o Delivering recorded media in real-time as the CS media 194 o Specifications of criteria to select a specific CS to be recorded 195 or triggers to record a certain CS in the future 197 o Recording policies that determine whether the CS should be 198 recorded and whether parts of the CS are to be recorded 200 o Retention policies that determine how long a recording is stored 202 o Searching and accessing the recorded media and metadata 204 o Policies governing how CS users are made aware of recording 206 o Delivering additional recording session metadata through non-SIP 207 mechanism 209 5. Overview of operations 211 This section is informative and provides a description of recording 212 operations. 214 Section 6 describes SIP the handling in a recording session between a 215 SRC and a SRS, and the procedures for recording-aware user agents 216 participating in a CS. Section 7 describes the SDP in a recording 217 session, and the procedures for recording indications and recording 218 preferences. Section 8 describes the RTP handling in a recording 219 session. Section 9 describes the mechanism to deliver recording 220 metadata from the SRC to the SRS. 222 As mentioned in the architecture document 223 [I-D.ietf-siprec-architecture], there are a number of types of call 224 flows based on the location of the Session Recording Client. The 225 following sample call flows provide a quick overview of the 226 operations between the SRC and the SRS. 228 5.1. Delivering recorded media 230 When a SIP Back-to-back User Agent (B2BUA) with SRC functionality 231 routes a call from UA(A) to UA(B), the SRC has access to the media 232 path between the user agents. When the SRC is aware that it should 233 be recording the conversation, the SRC can cause the B2BUA to bridge 234 the media between UA(A) and UA(B). The SRC then establishes the 235 Recording Session with the SRS and sends replicated media towards the 236 SRS. 238 An endpoint may also have SRC functionality, where the endpoint 239 itself establishes the Recording Session to the SRS. Since the 240 endpoint has access to the media in the Communication Session, the 241 endpoint can send replicated media towards the SRS. 243 The following is a sample call flow that shows the SRC establishing a 244 recording session towards the SRS. The call flow is essentially 245 identical when the SRC is a B2BUA or as the endpoint itself. Note 246 that the SRC can choose when to establish the Recording Session 247 independent of the Communication Session, even though the following 248 call flow suggests that the SRC is establishing the Recording Session 249 (message #5) after the Communication Session is established. 251 UA A SRC UA B SRS 252 |(1)CS INVITE | | | 253 |------------->| | | 254 | |(2)CS INVITE | | 255 | |---------------------->| | 256 | | (3) 200 OK | | 257 | |<----------------------| | 258 | (4) 200 OK | | | 259 |<-------------| | | 260 | |(5)RS INVITE with SDP | | 261 | |--------------------------------------------->| 262 | | | (6) 200 OK with SDP | 263 | |<---------------------------------------------| 264 |(7)CS RTP | | | 265 |=============>|======================>| | 266 |<=============|<======================| | 267 | |(8)RS RTP | | 268 | |=============================================>| 269 | |=============================================>| 270 |(9)CS BYE | | | 271 |------------->| | | 272 | |(10)CS BYE | | 273 | |---------------------->| | 274 | |(11)RS BYE | | 275 | |--------------------------------------------->| 276 | | | | 278 Figure 1: Basic recording call flow 280 The above call flow can also apply to the case of a centralized 281 conference with a mixer. For clarity, ACKs to INVITEs and 200 OKs to 282 BYEs are not shown. The conference focus can provide the SRC 283 functionality since the conference focus has access to all the media 284 from each conference participant. When a recording is requested, the 285 SRC delivers the metadata and the media streams to the SRS. Since 286 the conference focus has access to a mixer, the SRC may choose to mix 287 the media streams from all participants as a single mixed media 288 stream towards the SRS. 290 An SRC can use a single recording session to record multiple 291 communication sessions. Every time the SRC wants to record a new 292 call, the SRC updates the recording session with a new SDP offer to 293 add new recorded streams to the recording session, and 294 correspondingly also update the metadata for the new call. 296 An SRS can also establish a recording session to an SRC, although it 297 is beyond the scope of this document to define how an SRS would 298 specify which calls to record. 300 5.2. Delivering recording metadata 302 The SRC is responsible for the delivery of metadata to the SRS. The 303 SRC may provide an initial metadata snapshot about recorded media 304 streams in the initial INVITE content in the recording session. 305 Subsequent metadata updates can be represented as a stream of events 306 in UPDATE or reINVITE requests sent by the SRC. These metadata 307 updates are normally incremental updates to the initial metadata 308 snapshot to optimize on the size of updates, however, the SRC may 309 also decide to send a new metadata snapshot anytime. 311 Metadata is transported in the body of INVITE or UPDATE messages. 312 Certain metadata, such as the attributes of the recorded media stream 313 are located in the SDP of the recording session. 315 The SRS has the ability to send a request to the SRC to request for a 316 new metadata snapshot update from the SRC. This can happen when the 317 SRS fails to understand the current stream of incremental updates for 318 whatever reason, for example, when SRS loses the current state due to 319 internal failure. The SRS may optionally attach a reason along with 320 the snapshot request. This request allows both SRC and SRS to 321 synchronize the states with a new metadata snapshot so that further 322 metadata incremental updates will be based on the latest metadata 323 snapshot. Similar to the metadata content, the metadata snapshot 324 request is transported as content in UPDATE or INVITE sent by the SRS 325 in the recording session. 327 SRC SRS 328 | | 329 |(1) INVITE (metadata snapshot) | 330 |---------------------------------------------------->| 331 | (2)200 OK | 332 |<----------------------------------------------------| 333 |(3) ACK | 334 |---------------------------------------------------->| 335 |(4) RTP | 336 |====================================================>| 337 |====================================================>| 338 |(5) UPDATE (metadata update 1) | 339 |---------------------------------------------------->| 340 | (6) 200 OK | 341 |<----------------------------------------------------| 342 |(7) UPDATE (metadata update 2) | 343 |---------------------------------------------------->| 344 | (8) 200 OK | 345 |<----------------------------------------------------| 346 | (9) UPDATE (metadata snapshot request) | 347 |<----------------------------------------------------| 348 | (10) 200 OK | 349 |---------------------------------------------------->| 350 | (11) INVITE (metadata snapshot 2 + SDP offer) | 351 |---------------------------------------------------->| 352 | (12) 200 OK (SDP answer) | 353 |<----------------------------------------------------| 354 | (13) UPDATE (metadata update 1 based on snapshot 2) | 355 |---------------------------------------------------->| 356 | (14) 200 OK | 357 |<----------------------------------------------------| 359 Figure 2: Delivering metadata via SIP UPDATE 361 5.3. Receiving recording indications and providing recording 362 preferences 364 The SRC is responsible to provide recording indications to the 365 participants in the CS. A recording-aware UA supports receiving 366 recording indications via the SDP attribute a=record, and it can 367 specify a recording preference in the CS by including the SDP 368 attribute a=recordpref. The recording attribute is a declaration by 369 the SRC in the CS to indicate whether recording is taking place. The 370 recording preference attribute is a declaration by the recording- 371 aware UA in the CS to indicate the recording preference. 373 To illustrate how the attributes are used, if a UA (A) is initiating 374 a call to UA (B) and UA (A) is also an SRC that is performing the 375 recording, then UA (A) provides the recording indication in the SDP 376 offer with a=record:on. Since UA (A) is the SRC, UA (A) receives the 377 recording indication from the SRC directly. When UA (B) receives the 378 SDP offer, UA (B) will see that recording is happening on the other 379 endpoint of this session. Since UA (B) is not an SRC and does not 380 provide any recording preference, the SDP answer does not contain 381 a=record nor a=recordpref. 383 UA A UA B 384 (SRC) | 385 | | 386 | [SRC recording starts] | 387 |(1) INVITE (SDP offer + a=record:on) | 388 |---------------------------------------------------->| 389 | (2) 200 OK (SDP answer) | 390 |<----------------------------------------------------| 391 |(3) ACK | 392 |---------------------------------------------------->| 393 |(4) RTP | 394 |<===================================================>| 395 | | 396 | [UA B wants to set preference to no recording] | 397 | (5) INVITE (SDP offer + a=recordpref:off) | 398 |<----------------------------------------------------| 399 | [SRC honors the preference and stops recording] | 400 |(6) 200 OK (SDP answer + a=record:off) | 401 |---------------------------------------------------->| 402 | (7) ACK | 403 |<----------------------------------------------------| 405 Figure 3: Recording indication and recording preference 407 After the call is established and recording is in progress, UA (B) 408 later decides to change the recording preference to no recording and 409 sends a reINVITE with the a=recordpref attribute. It is up to the 410 SRC to honor the preference, and in this case SRC decides to stop the 411 recording and updates the recording indication in the SDP answer. 413 6. SIP Handling 415 6.1. Procedures at the SRC 417 6.1.1. Initiating a Recording Session 419 A recording session is a SIP session with specific extensions 420 applied, and these extensions are listed in the procedures for SRC 421 and SRS below. When an SRC or an SRS receives a SIP session that is 422 not a recording session, it is up to the SRC or the SRS to determine 423 what to do with the SIP session. 425 The SRC can initiate a recording session by sending a SIP INVITE 426 request to the SRS. The SRC and the SRS are identified in the From 427 and To headers, respectively. 429 The SRC MUST include the '+sip.src' feature tag in the Contact URI, 430 defined in this specification as an extension to [RFC3840], for all 431 recording sessions. An SRS uses the presence of the '+sip.src' 432 feature tag in dialog creating and modifying requests and responses 433 to confirm that the dialog being created is for the purpose of a 434 Recording Session. In addition, when an SRC sends a REGISTER request 435 to a registrar, the SRC MUST include the '+sip.src' feature tag to 436 indicate the that it is a SRC. 438 Since SIP Caller Preferences extensions are optional to implement for 439 routing proxies, there is no guarantee that a recording session will 440 be routed to an SRC or SRS. A new options tag is introduced: 441 "siprec". As per [RFC3261], only an SRC or an SRS can accept this 442 option tag in a recording session. An SRC MUST include the "siprec" 443 option tag in the Require header when initiating a Recording Session 444 so that UA's which do not support the session recording protocol 445 extensions will simply reject the INVITE request with a 420 Bad 446 Extension. 448 When an SRC receives a new INVITE, the SRC MUST only consider the SIP 449 session as a recording session when both the '+sip.srs' feature tag 450 and 'siprec' option tag are included in the INVITE request. 452 6.1.2. SIP extensions for recording indication and preference 454 For the communication session, the SRC MUST provide recording 455 indication to all participants in the CS. A participant UA in a CS 456 can indicate that it is recording-aware by providing the "record- 457 aware" option tag, and the SRC MUST provide recording indications in 458 the new SDP a=record attribute described in the SDP Handling section. 459 In the absence of the "record-aware" option tag, meaning that the 460 participant UA is not recording-aware, an SRC MUST provide recording 461 indications through other means such as playing a tone inband, if the 462 SRC is required to do so (e.g. based on policies). 464 An SRC in the CS may also indicate itself as a session recording 465 client by including the '+sip.src' feature tag. A recording-aware 466 participant can learn that a SRC is in the CS, and can set the 467 recording preference for the CS with the new SDP a=recordpref 468 attribute described in the SDP Handling section below. 470 6.2. Procedures at the SRS 471 When an SRS receives a new INVITE, the SRS MUST only consider the SIP 472 session as a recording session when both the '+sip.src' feature tag 473 and 'siprec' option tag are included in the INVITE request. 475 The SRS can initiate a recording session by sending a SIP INVITE 476 request to the SRC. The SRS and the SRC are identified in the From 477 and To headers, respectively. 479 The SRS MUST include the '+sip.srs' feature tag in the Contact URI, 480 as per [RFC3840], for all recording sessions. An SRC uses the 481 presence of this feature tag in dialog creating and modifying 482 requests and responses to confirm that the dialog being created is 483 for the purpose of a Recording Session (REQ-30). In addition, when 484 an SRS sends a REGISTER request to a registrar, the SRS MUST include 485 the '+sip.srs' feature tag to indicate that it is a SRS. 487 An SRS MUST include the "siprec" option tag in the Require header as 488 per [RFC3261] when initiating a Recording Session so that UA's which 489 do not support the session recording protocol extensions will simply 490 reject the INVITE request with a 420 Bad Extension. 492 6.3. Procedures for Recording-aware User Agents 494 A recording-aware user agent is a participant in the CS that supports 495 the SIP and SDP extensions for receiving recording indication and for 496 requesting recording preferences for the call. A recording-aware UA 497 MUST indicate that it can accept reporting of recording indication 498 provided by the SRC with a new option tag "record-aware" when 499 initiating or establishing a CS, meaning including the "record-aware" 500 tag in the Supported header in the initial INVITE request or 501 response. 503 A recording-aware UA MUST be prepared to provide recording indication 504 to the end user through an appropriate user interface an indication 505 whether recording is on, off, or paused for each medium. Some user 506 agents that are automatons (e.g. IVR, media server, PSTN gateway) 507 may not have a user interface to render recording indication. When 508 such user agent indicates recording awareness, the UA SHOULD render 509 recording indication through other means, such as passing an inband 510 tone on the PSTN gateway, putting the recording indication in a log 511 file, or raising an application event in a VoiceXML dialog. These 512 user agents MAY also choose not to indicate recording awareness, 513 thereby relying on whatever mechanism an SRC chooses to indicate 514 recording, such as playing a tone inband. 516 7. SDP Handling 517 7.1. Procedures at the SRC 519 The SRC and SRS follows the SDP offer/answer model in [RFC3264]. The 520 procedures for SRC and SRS describe the conventions used in a 521 recording session. 523 7.1.1. SDP handling in RS 525 Since the SRC does not expect to receive media from the SRS, the SRC 526 typically sets each media stream of the SDP offer to only send media, 527 by qualifying them with the a=sendonly attribute, according to the 528 procedures in [RFC3264]. 530 The SRC sends recorded streams of participants to the SRS, and the 531 SRC MUST provide a label attribute (a=label), as per [RFC4574], on 532 each media stream in order to identify the recorded stream with the 533 rest of the metadata. The a=label attribute identifies each recorded 534 media stream, and the label name is mapped to the Media Stream 535 Reference in the metadata as per [I-D.ietf-siprec-metadata]. The 536 scope of the a=label attribute only applies to the SDP and Metadata 537 conveyed in the bodies of the SIP request or response that the label 538 appeared in. Note that a recorded stream is distinct from a CS 539 stream; the metadata provides a list of participants that contributes 540 to each recorded stream. 542 The following is an example SDP offer from SRC with both audio and 543 video recorded streams. Note that the following example contains 544 unfolded lines longer than 72 characters. These are captured between 545 tags. 547 v=0 548 o=SRC 2890844526 2890844526 IN IP4 198.51.100.1 549 s=- 550 c=IN IP4 198.51.100.1 551 t=0 0 552 m=audio 12240 RTP/AVP 0 4 8 553 a=sendonly 554 a=label:1 555 m=video 22456 RTP/AVP 98 556 a=rtpmap:98 H264/90000 557 558 a=fmtp:98 profile-level-id=42A01E; 559 sprop-parameter-sets=Z0IACpZTBYmI,aMljiA== 560 561 a=sendonly 562 a=label:2 563 m=audio 12242 RTP/AVP 0 4 8 564 a=sendonly 565 a=label:3 566 m=video 22458 RTP/AVP 98 567 a=rtpmap:98 H264/90000 568 569 a=fmtp:98 profile-level-id=42A01E; 570 sprop-parameter-sets=Z0IACpZTBYmI,aMljiA== 571 572 a=sendonly 573 a=label:4 575 Figure 4: Sample SDP offer from SRC with audio and video streams 577 7.1.1.1. Handling media stream updates 579 Over the lifetime of a recording session, the SRC can add and remove 580 recorded streams from the recording session for various reasons. For 581 example, when a CS stream is added or removed from the CS, or when a 582 CS is created or terminated if a recording session handles multiple 583 CSes. To remove a recorded stream from the recording session, the 584 SRC sends a new SDP offer where the port of the media stream to be 585 removed is set to zero, according to the procedures in [RFC3264]. To 586 add a recorded stream to the recording session, the SRC sends a new 587 SDP offer by adding a new media stream description or by reusing an 588 old media stream which had been previously disabled, according to the 589 procedures in [RFC3264]. 591 The SRC can temporarily discontinue streaming and collection of 592 recorded media from the SRC to the SRS for reasons such as masking 593 the recording. In this case, the SRC sends a new SDP offer and sets 594 the media stream to inactive (a=inactive) for each recorded stream to 595 be paused, as per the procedures in [RFC3264]. To resume streaming 596 and collection of recorded media, the SRC sends a new SDP offer and 597 sets the media stream to sendonly (a=sendonly). Note that a CS 598 itself may change the media stream direction by updating the SDP, for 599 example, by setting a=inactive for SDP hold. Media stream direction 600 changes in CS are conveyed in the metadata by the SRC. The SRC MUST 601 NOT modify the media stream with a=inactive for SDP hold on the CS 602 since this operation is reserved for pausing the RS media, however, 603 an SRC can have a local policy to pause the RS media when the CS is 604 placed on hold. 606 7.1.2. Recording indication in CS 608 While there are existing mechanisms for providing an indication that 609 a CS is being recorded, these mechanisms are usually delivered on the 610 CS media streams such as playing an in-band tone or an announcement 611 to the participants. A new 'record' SDP attribute is introduced to 612 allow the SRC to indicate recording state to a recording-aware UA in 613 CS. 615 The 'record' SDP attribute appears at the media level or session 616 level in either SDP offer or answer. When the attribute is applied 617 at the session level, the indication applies to all media streams in 618 the SDP. When the attribute is applied at the media level, the 619 indication applies to the media stream only, and that overrides the 620 indication if also set at the session level. Whenever the recording 621 indication needs to change, such as termination of recording, then 622 the SRC MUST initiate a reINVITE or UPDATE to update the SDP a=record 623 attribute. 625 The following is the ABNF of the 'record' attribute: 627 attribute /= record-attr 629 ; attribute defined in RFC 4566 631 record-attr = "record:" indication 633 indication = "on" / "off" / "paused" 635 on Recording is in progress. 637 off No recording is in progress. 639 paused Recording is in progress but media is paused. 641 7.1.3. Recording preference in CS 643 When the SRC receives the a=recordpref SDP in an SDP offer or answer, 644 the SRC chooses to honor the preference to record based on local 645 policy at the SRC. Whether or not the SRC honors the recording 646 preference, the SRC MUST update the a=record attribute to indicate 647 the current state of the recording (on/off/paused). 649 7.2. Procedures at the SRS 651 Typically the SRS only receives RTP streams from the SRC; therefore, 652 the SDP offer/answer from the SRS normally sets each media stream to 653 receive media, by setting them with the a=recvonly attribute, 654 according to the procedures of [RFC3264]. When the SRS is not ready 655 to receive a recorded stream, the SRS sets the media stream as 656 inactive in the SDP offer or answer by setting it with a=inactive 657 attribute, according to the procedures of [RFC3264]. When the SRS is 658 ready to receive recorded streams, the SRS sends a new SDP offer and 659 sets the media streams with a=recvonly attribute. 661 The following is an example of SDP answer from SRS for the SDP offer 662 from the above sample. Note that the following example contain 663 unfolded lines longer than 72 characters. These are captured between 664 tags. 666 v=0 667 o=SRS 0 0 IN IP4 198.51.100.20 668 s=- 669 c=IN IP4 198.51.100.20 670 t=0 0 671 m=audio 10000 RTP/AVP 0 672 a=recvonly 673 a=label:1 674 m=video 10002 RTP/AVP 98 675 a=rtpmap:98 H264/90000 676 677 a=fmtp:98 profile-level-id=42A01E; 678 sprop-parameter-sets=Z0IACpZTBYmI,aMljiA== 679 680 a=recvonly 681 a=label:2 682 m=audio 10004 RTP/AVP 0 683 a=recvonly 684 a=label:3 685 m=video 10006 RTP/AVP 98 686 a=rtpmap:98 H264/90000 687 688 a=fmtp:98 profile-level-id=42A01E; 689 sprop-parameter-sets=Z0IACpZTBYmI,aMljiA== 690 691 a=recvonly 692 a=label:4 694 Figure 5: Sample SDP answer from SRS with audio and video streams 696 Over the lifetime of a recording session, the SRS can remove recorded 697 streams from the recording session for various reasons. To remove a 698 recorded stream from the recording session, the SRS sends a new SDP 699 offer where the port of the media stream to be removed is set to 700 zero, according to the procedures in [RFC3264]. 702 The SRS SHOULD NOT add recorded streams in the recording session when 703 SRS sends a new SDP offer. Similarly, when the SRS starts a 704 recording session, the SRS SHOULD initiate the INVITE without an SDP 705 offer to let the SRC generate the SDP offer with recorded streams. 707 The following sequence diagram shows an example where the SRS is 708 initially not ready to receive recorded streams, and later updates 709 the recording session when the SRS is ready to record. 711 SRC SRS 712 | | 713 |(1) INVITE (SDP offer) | 714 |---------------------------------------------------->| 715 | [not ready to record] 716 | (2)200 OK with SDP inactive | 717 |<----------------------------------------------------| 718 |(3) ACK | 719 |---------------------------------------------------->| 720 | ... | 721 | [ready to record] 722 | (4) re-INVITE with SDP recvonly | 723 |<----------------------------------------------------| 724 |(5)200 OK with SDP sendonly | 725 |---------------------------------------------------->| 726 | (6) ACK | 727 |<----------------------------------------------------| 728 |(7) RTP | 729 |====================================================>| 730 | ... | 731 |(8) BYE | 732 |---------------------------------------------------->| 733 | (9) OK | 734 |<----------------------------------------------------| 736 Figure 6: SRS responding to offer with a=inactive 738 7.3. Procedures for Recording-aware User Agents 740 7.3.1. Recording indication 742 When a recording-aware UA receives an SDP offer or answer that 743 includes the a=record attribute, the UA MUST provide the recording 744 indication to the end user whether the recording is on, off, or 745 paused for each medium based on the most recently received a=record 746 SDP attribute for that medium. 748 If a call is traversed through one or more SIP B2BUA, and it happens 749 that there are more than one SRC in the call path, the recording 750 indication attribute does not provide any hint as to which SRC is 751 performing the recording, meaning the endpoint only knows that the 752 call is being recorded. This attribute is also not used as an 753 indication to negotiate which SRC in the call path will perform 754 recording and is not used as a request to start/stop recording if 755 there are multiple SRCs in the call path. 757 7.3.2. Recording preference 759 A participant in a CS MAY set the recording preference in the CS to 760 be recorded or not recorded at session establishment or during the 761 session. A new 'recordpref' SDP attribute is introduced, and the 762 participant in CS may set this recording preference attribute in any 763 SDP offer/answer at session establishment time or during the session. 764 The SRC is not required to honor the recording preference from a 765 participant based on local policies at the SRC, and the participant 766 can learn the recording indication through the a=record SDP attribute 767 as described in the above section. 769 The SDP a=recordpref attribute can appear at the media level or 770 session level and can appear in an SDP offer or answer. When the 771 attribute is applied at the session level, the recording preference 772 applies to all media stream in the SDP. When the attribute is 773 applied at the media level, the recording preference applies to the 774 media stream only, and that overrides the recording preference if 775 also set at the session level. The user agent can change the 776 recording preference by changing the a=recordpref attribute in 777 subsequent SDP offer or answer. The absence of the a=recordpref 778 attribute in the SDP indicates that the UA has no recording 779 preference. 781 The following is the ABNF of the recordpref attribute: 783 attribute /= recordpref-attr 785 ; attribute defined in RFC 4566 787 recordpref-attr = "a=recordpref:" pref 789 pref = "on" / "off" / "pause" / "nopreference" 791 on Sets the preference to record if it has not already been started. 792 If the recording is currently paused, the preference is to resume 793 recording. 795 off Sets the preference for no recording. If recording has already 796 been started, then the preference is to stop the recording. 798 pause If the recording is currently in progress, sets the preference 799 to pause the recording. 801 nopreference To indicate that the UA has no preference on recording. 803 8. RTP Handling 805 This section provides recommendations and guidelines for RTP and RTCP 806 in the context of SIPREC. In order to communicate most effectively, 807 the Session Recording Client (SRC), the Session Recording Server 808 (SRS), and any Recording aware User Agents (UAs) SHOULD utilize the 809 mechanisms provided by RTP in a well-defined and predicable manner. 810 It is the goal of this document to make the reader aware of these 811 mechanisms and provide recommendations and guidelines. 813 8.1. RTP Mechanisms 815 This section briefly describes important RTP/RTCP constructs and 816 mechanisms that are particularly useful within the content of SIPREC. 818 8.1.1. RTCP 820 The RTP data transport is augmented by a control protocol (RTCP) to 821 allow monitoring of the data delivery. RTCP, as defined in 822 [RFC3550], is based on the periodic transmission of control packets 823 to all participants in the RTP session, using the same distribution 824 mechanism as the data packets. Support for RTCP is REQUIRED, per 825 [RFC3550], and it provides, among other things, the following 826 important functionality in relation to SIPREC: 828 1) Feedback on the quality of the data distribution 830 This feedback from the receivers may be used to diagnose faults in 831 the distribution. As such, RTCP is a well-defined and efficient 832 mechanism for the SRS to inform the SRC, and for the SRC to inform 833 Recording aware UAs, of issues that arise with respect to the 834 reception of media that is to be recorded. 836 2) Carries a persistent transport-level identifier for an RTP source 837 called the canonical name or CNAME 839 The SSRC identifier may change if a conflict is discovered or a 840 program is restarted; in which case receivers can use the CNAME to 841 keep track of each participant. Receivers may also use the CNAME to 842 associate multiple data streams from a given participant in a set of 843 related RTP sessions, for example to synchronize audio and video. 844 Synchronization of media streams is also facilitated by the NTP and 845 RTP timestamps included in RTCP packets by data senders. 847 8.1.2. RTP Profile 849 The RECOMMENDED RTP profiles for the SRC, SRS, and Recording aware 850 UAs are "Extended Secure RTP Profile for Real-time Transport Control 851 Protocol (RTCP)-Based Feedback (RTP/SAVPF)", [RFC5124] when using 852 encrypted RTP streams, and "Extended RTP Profile for Real-time 853 Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)", 854 [RFC4585] when using non encrypted media streams. However, as this 855 is not a requirement, some implementations may use "The Secure Real- 856 time Transport Protocol (SRTP)", [RFC3711] and "RTP Profile for Audio 857 and Video Conferences with Minimal Control", AVP [RFC3551]. 858 Therefore, it is RECOMMENDED that the SRC, SRS, and Recording aware 859 UAs not rely entirely on SAVPF or AVPF for core functionality that 860 may be at least partially achievable using SAVP and AVP. 862 AVPF and SAVPF provide an improved RTCP timer model that allows more 863 flexible transmission of RTCP packets in response to events, rather 864 than strictly according to bandwidth. AVPF based codec control 865 messages provide efficient mechanisms for an SRC, SRS, and Recording 866 aware UAs to handle events such as scene changes, error recovery, and 867 dynamic bandwidth adjustments. These messages are discussed in more 868 detail later in this document. 870 SAVP and SAVPF provide media encryption, integrity protection, replay 871 protection, and a limited form of source authentication. They do not 872 contain or require a specific keying mechanism. 874 8.1.3. SSRC 876 The synchronization source (SSRC), as defined in [RFC3550] is carried 877 in the RTP header and in various fields of RTCP packets. It is a 878 random 32-bit number that is required to be globally unique within an 879 RTP session. It is crucial that the number be chosen with care in 880 order that participants on the same network or starting at the same 881 time are not likely to choose the same number. Guidelines regarding 882 SSRC value selection and conflict resolution are provided in 883 [RFC3550]. 885 The SSRC may also be used to separate different sources of media 886 within a single RTP session. For this reason as well as for conflict 887 resolution, it is important that the SRC, SRS, and Recording aware 888 UAs handle changes in SSRC values and properly identify the reason of 889 the change. The CNAME values carried in RTCP facilitate this 890 identification. 892 8.1.4. CSRC 894 The contributing source (CSRC), as defined in [RFC3550], identifies 895 the source of a stream of RTP packets that has contributed to the 896 combined stream produced by an RTP mixer. The mixer inserts a list 897 of the SSRC identifiers of the sources that contributed to the 898 generation of a particular packet into the RTP header of that packet. 899 This list is called the CSRC list. It is RECOMMENDED that a SRC or 900 Recording aware UA, when acting a mixer, sets the CSRC list 901 accordingly, and that the SRC and SRS interpret the CSRC list 902 appropriately when received. 904 8.1.5. SDES 906 The Source Description (SDES), as defined in [RFC3550], contains an 907 SSRC/CSRC identifier followed by a list of zero or more items, which 908 carry information about the SSRC/CSRC. End systems send one SDES 909 packet containing their own source identifier (the same as the SSRC 910 in the fixed RTP header). A mixer sends one SDES packet containing a 911 chunk for each contributing source from which it is receiving SDES 912 information, or multiple complete SDES packets if there are more than 913 31 such sources. 915 8.1.5.1. CNAME 917 The Canonical End-Point Identifier (CNAME), as defined in [RFC3550], 918 provides the binding from the SSRC identifier to an identifier for 919 the source (sender or receiver) that remains constant. It is 920 important the SRC and Recording aware UAs generate CNAMEs 921 appropriately and that the SRC and SRS interpret and use them for 922 this purpose. Guidelines for generating CNAME values are provided in 923 "Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names 924 (CNAMEs)" [RFC6222]. 926 8.1.6. Keepalive 928 It is anticipated that media streams in SIPREC may exist in an 929 inactive state for extended periods of times for any of a number of 930 valid reasons. In order for the bindings and any pinholes in NATs/ 931 firewalls to remain active during such intervals, it is RECOMMENDED 932 that the SRC, SRS, and Recording aware UAs follow the keep-alive 933 procedure recommended in "Application Mechanism for Keeping Alive the 934 NAT Mappings Associated to RTP/RTP Control Protocol (RTCP) Flows" 935 [RFC6263] for all RTP media streams. 937 8.1.7. RTCP Feedback Messages 938 "Codec Control Messages in the RTP Audio-Visual Profile with Feedback 939 (AVPF)" [RFC5104] specifies extensions to the messages defined in 940 AVPF [RFC4585]. Support for and proper usage of these messages is 941 important to SRC, SRS, and Recording aware UA implementations. Note 942 that these messages are applicable only when using the AVFP or SAVPF 943 RTP profiles 945 8.1.7.1. Full Intra Request 947 A Full Intra Request (FIR) Command, when received by the designated 948 media sender, requires that the media sender sends a Decoder Refresh 949 Point at the earliest opportunity. Using a decoder refresh point 950 implies refraining from using any picture sent prior to that point as 951 a reference for the encoding process of any subsequent picture sent 952 in the stream. 954 Decoder refresh points, especially Intra or IDR pictures for H.264 955 video codecs, are in general several times larger in size than 956 predicted pictures. Thus, in scenarios in which the available bit 957 rate is small, the use of a decoder refresh point implies a delay 958 that is significantly longer than the typical picture duration. 960 8.1.7.1.1. SIP INFO for FIR 962 "XML Schema for Media Control" [RFC5168] defines an Extensible Markup 963 Language (XML) Schema for video fast update. Implementations are 964 discouraged from using the method described except for backward 965 compatibility purposes. Implementations SHOULD use FIR messages 966 instead. 968 8.1.7.2. Picture Loss Indicator 970 Picture Loss Indication (PLI), as defined in [RFC4585], informs the 971 encoder of the loss of an undefined amount of coded video data 972 belonging to one or more pictures. Using the FIR command to recover 973 from errors is explicitly disallowed, and instead the PLI message 974 SHOULD be used. FIR SHOULD be used only in situations where not 975 sending a decoder refresh point would render the video unusable for 976 the users. Examples where sending FIR is appropriate include a 977 multipoint conference when a new user joins the conference and no 978 regular decoder refresh point interval is established, and a video 979 switching MCU that changes streams. 981 8.1.7.3. Temporary Maximum Media Stream Bit Rate Request 983 A receiver, translator, or mixer uses the Temporary Maximum Media 984 Stream Bit Rate Request (TMMBR) to request a sender to limit the 985 maximum bit rate for a media stream to the provided value. 986 Appropriate use of TMMBR facilitates rapid adaptation to changes in 987 available bandwidth. 989 8.1.7.3.1. Renegotiation of SDP bandwidth attribute 991 If it is likely that the new value indicated by TMMBR will be valid 992 for the remainder of the session, the TMMBR sender is expected to 993 perform a renegotiation of the session upper limit using the session 994 signaling protocol. Therefore for SIPREC, implementations are 995 RECOMMENDED to use TMMBR for temporary changes, and renegotiation of 996 bandwidth via SDP offer/answer for more permanent changes. 998 8.1.8. Symmetric RTP/RTCP for Sending and Receiving 1000 Within an SDP offer/answer exchange, RTP entities choose the RTP and 1001 RTCP transport addresses (i.e., IP addresses and port numbers) on 1002 which to receive packets. When sending packets, the RTP entities may 1003 use the same source port or a different source port as those signaled 1004 for receiving packets. When the transport address used to send and 1005 receive RTP is the same, it is termed "symmetric RTP" [RFC4961]. 1006 Likewise, when the transport address used to send and receive RTCP is 1007 the same, it is termed "symmetric RTCP" [RFC4961]. 1009 When sending RTP, it is REQUIRED to use symmetric RTP. When sending 1010 RTCP, it is REQUIRED to use symmetric RTCP. Although an SRS will not 1011 normally send RTP, it will send RTCP as well as receive RTP and RTCP. 1012 Likewise, although an SRC will not normally receive RTP from the SRS, 1013 it will receive RTCP as well as send RTP and RTCP. 1015 Note: Symmetric RTP and symmetric RTCP are different from RTP/RTCP 1016 multiplexing [RFC5761]. 1018 8.2. Roles 1020 An SRC has the task of gathering media from the various UAs in one or 1021 more Communication Sessions (CSs) and forwarding the information to 1022 the SRS within the context of a corresponding Recording Session (RS). 1023 There are numerous ways in which an SRC may do this is, including but 1024 not limited to, appearing as a UA within a CS, or as a B2BUA between 1025 UAs within a CS. 1027 (Recording Session) +---------+ 1028 +------------SIP------->| | 1029 | +------RTP/RTCP----->| SRS | 1030 | | +-- Metadata -->| | 1031 | | | +---------+ 1032 v v | 1033 +---------+ 1034 | SRC | 1035 |---------| (Communication Session) +---------+ 1036 | |<----------SIP---------->| | 1037 | UA-A | | UA-B | 1038 | |<-------RTP/RTCP-------->| | 1039 +---------+ +---------+ 1041 Figure 7: UA as SRC 1043 (Recording Session) +---------+ 1044 +------------SIP------->| | 1045 | +------RTP/RTCP----->| SRS | 1046 | | +-- Metadata -->| | 1047 | | | +---------+ 1048 v v | 1049 +---------+ 1050 | SRC | 1051 +---------+ |---------| +---------+ 1052 | |<----SIP----->| |<----SIP----->| | 1053 | UA-A | | B2BUA | | UA-B | 1054 | |<--RTP/RTCP-->| |<--RTP/RTCP-->| | 1055 +---------+ +---------+ +---------+ 1056 |_______________________________________________| 1057 (Communication Session) 1059 Figure 8: B2BUA as SRC 1061 The following subsections define a set of roles an SRC may choose to 1062 play based on its position with respect to a UA within a CS, and an 1063 SRS within an RS. A CS and a corresponding RS are independent 1064 sessions; therefore, an SRC may play a different role within a CS 1065 than it does within the corresponding RS. 1067 8.2.1. SRC acting as an RTP Translator 1069 The SRC may act as a translator, as defined in [RFC3550]. A defining 1070 characteristic of a translator is that it forwards RTP packets with 1071 their SSRC identifier intact. There are two types of translators, 1072 one that simply forwards, and another that performs transcoding 1073 (e.g., from one codec to another) in addition to forwarding. 1075 8.2.1.1. Forwarding Translator 1076 When acting as a forwarding translator, RTP received as separate 1077 streams from different sources (e.g., from different UAs with 1078 different SSRCs) cannot be mixed by the SRC and MUST be sent 1079 separately to the SRS. All RTCP reports MUST be passed by the SRC 1080 between the UAs and the SRS, such that the UAs and SRS are able to 1081 detect any SSRC collisions. 1083 RTCP Sender Reports generated by a UA sending a stream MUST be 1084 forwarded to the SRS. RTCP Receiver Reports generated by the SRS 1085 MUST be forwarded to the relevant UA. 1087 UAs may receive multiple sets of RTCP Receiver Reports, one or more 1088 from other UAs participating in the CS, and one from the SRS 1089 participating in the RS. A Recording aware UA SHOULD be prepared to 1090 process the RTCP Receiver Reports from the SRS, whereas a recording 1091 unaware UA may discard such RTCP packets as not of relevance. 1093 If SRTP is used on both the CS and the RS, decryption and/or re- 1094 encryption may occur. For example, if different keys are used, it 1095 will occur. If the same keys are used, it need not occur. 1096 Section 12 provides additional information on SRTP and keying 1097 mechanisms. 1099 If packet loss occurs, either from the UA to the SRC or from the SRC 1100 to the SRS, the SRS SHOULD detect and attempt to recover from the 1101 loss. The SRC does not play a role in this other than forwarding the 1102 associated RTP and RTCP packets. 1104 8.2.1.2. Transcoding Translator 1106 When acting as a transcoding translator, an SRC MAY perform 1107 transcoding (e.g., from one codec to another), and this may result in 1108 a different rate of packets between what the SRC receives and what 1109 the SRC sends. As when acting as a forwarding translator, RTP 1110 received as separate streams from different sources (e.g., from 1111 different UAs with different SSRCs) cannot be mixed by the SRC and 1112 MUST be sent separately to the SRS. All RTCP reports MUST be passed 1113 by the SRC between the UAs and the SRS, such that the UAs and SRS are 1114 able to detect any SSRC collisions. 1116 RTCP Sender Reports generated by a UA sending a stream MUST be 1117 forwarded to the SRS. RTCP Receiver Reports generated by the SRS 1118 MUST be forwarded to the relevant UA. The SRC may need to manipulate 1119 the RTCP Receiver Reports to take account of any transcoding that has 1120 taken place. 1122 UAs may receive multiple sets of RTCP Receiver Reports, one or more 1123 from other UAs participating in the CS, and one from the SRS 1124 participating in the RS. A Recording aware UA SHOULD be prepared to 1125 process the RTCP Receiver Reports from the SRS, whereas a recording 1126 unaware UA may discard such RTCP packets as not of relevance. 1128 If SRTP is used on both the CS and the RS, decryption and/or re- 1129 encryption may occur. For example, if different keys are used, it 1130 will occur. If the same keys are used, it need not occur. 1131 Section 12 provides additional information on SRTP and keying 1132 mechanisms. 1134 If packet loss occurs, either from the UA to the SRC or from the SRC 1135 to the SRS, the SRS SHOULD detect and attempt to recover from the 1136 loss. The SRC does not play a role in this other than forwarding the 1137 associated RTP and RTCP packets. 1139 8.2.2. SRC acting as an RTP Mixer 1141 In the case of the SRC acting as a RTP mixer, as defined in 1142 [RFC3550], the SRC combines RTP streams from different UA and sends 1143 them towards the SRS using its own SSRC. The SSRCs from the 1144 contributing UA SHOULD be conveyed as CSRCs identifiers within this 1145 stream. The SRC may make timing adjustments among the received 1146 streams and generate its own timing on the stream sent to the SRS. 1147 Optionally an SRC acting as a mixer can perform transcoding, and can 1148 even cope with different codings received from different UAs. RTCP 1149 Sender Reports and Receiver Reports are not forwarded by an SRC 1150 acting as mixer, but there are requirements for forwarding RTCP 1151 Source Description (SDES) packets. The SRC generates its own RTCP 1152 Sender and Receiver reports toward the associated UAs and SRS. 1154 The use of SRTP between the SRC and the SRS for the RS is independent 1155 of the use of SRTP between the UAs and SRC for the CS. Section 12 1156 provides additional information on SRTP and keying mechanisms. 1158 If packet loss occurs from the UA to the SRC, the SRC SHOULD detect 1159 and attempt to recover from the loss. If packet loss occurs from the 1160 SRC to the SRS, the SRS SHOULD detect and attempt to recover from the 1161 loss. 1163 8.2.3. SRC acting as an RTP Endpoint 1165 The case of the SRC acting as an RTP endpoint, as defined in 1166 [RFC3550], is similar to the mixer case, except that the RTP session 1167 between the SRC and the SRS is considered completely independent from 1168 the RTP session that is part of the CS. The SRC can, but need not, 1169 mix RTP streams from different participants prior to sending to the 1170 SRS. RTCP between the SRC and the SRS is completely independent of 1171 RTCP on the CS. 1173 The use of SRTP between the SRC and the SRS for the RS is independent 1174 of the use of SRTP between the UAs and SRC for the CS. Section 12 1175 provides additional information on SRTP and keying mechanisms. 1177 If packet loss occurs from the UA to the SRC, the SRC SHOULD detect 1178 and attempt to recover from the loss. If packet loss occurs from the 1179 SRC to the SRS, the SRS SHOULD detect and attempt to recover from the 1180 loss. 1182 8.3. RTP Session Usage by SRC 1184 There are multiple ways that an SRC may choose to deliver recorded 1185 media to an SRS. In some cases, it may use a single RTP session for 1186 all media within the RS, whereas in others it may use multiple RTP 1187 sessions. The following subsections provide examples of basic RTP 1188 session usage by the SRC, including a discussion of how the RTP 1189 constructs and mechanisms covered previously are used. An SRC may 1190 choose to use one or more of the RTP session usages within a single 1191 RS. For the purpose of base interoperability between SRC and SRS, an 1192 SRC MUST support separate m-lines in SDP, one per CS media direction. 1193 The set of RTP session usages described is not meant to be 1194 exhaustive. 1196 8.3.1. SRC Using Multiple m-lines 1198 When using multiple m-lines, an SRC includes each m-line in an SDP 1199 offer to the SRS. The SDP answer from the SRS MUST include all 1200 m-lines, with any rejected m-lines indicated with a zero port, per 1201 [RFC3264]. Having received the answer, the SRC starts sending media 1202 to the SRS as indicated in the answer. Alternatively, if the SRC 1203 deems the level of support indicated in the answer to be 1204 unacceptable, it may initiate another SDP offer/answer exchange in 1205 which an alternative RTP session usage is negotiated. 1207 In order to preserve the mapping of media to participant within the 1208 CSs in the RS, the SRC SHOULD map each unique CNAME within the CSs to 1209 a unique CNAME within the RS. Additionally, the SRC SHOULD map each 1210 unique combination of CNAME/SSRC within the CSs to a unique CNAME/ 1211 SSRC within the RS. In doing to, the SRC may act as an RTP 1212 translator or as an RTP endpoint. 1214 The following figure illustrates a case in which each UA represents a 1215 participant contributing two RTP sessions (e.g. one for audio and 1216 one for video), each with a single SSRC. The SRC acts as an RTP 1217 translator and delivers the media to the SRS using four RTP sessions, 1218 each with a single SSRC. The CNAME and SSRC values used by the UAs 1219 within their media streams are preserved in the media streams from 1220 the SRC to the SRS. 1222 +---------+ 1223 +------------SSRC Aa--->| | 1224 | + --------SSRC Av--->| | 1225 | | +------SSRC Ba--->| SRS | 1226 | | | +---SSRC Bv--->| | 1227 | | | | +---------+ 1228 | | | | 1229 | | | | 1230 +---------+ +----------+ +---------+ 1231 | |---SSRC Aa-->| SRC |<--SSRC Ba---| | 1232 | UA-A | |(CNAME-A, | | UA-B | 1233 |(CNAME-A)|---SSRC Av-->| CNAME-B) |<--SSRC Bv---|(CNAME-B)| 1234 +---------+ +----------+ +---------+ 1236 Figure 9: SRC Using Multiple m-lines 1238 8.3.2. SRC Using Mixing 1240 When using mixing, the SRC combines RTP streams from different 1241 participants and sends them towards the SRS using its own SSRC. The 1242 SSRCs from the contributing participants SHOULD be conveyed as CSRCs 1243 identifiers. The SRC includes one m-line for each RTP session in an 1244 SDP offer to the SRS. The SDP answer from the SRS MUST include all 1245 m-lines, with any rejected m-lines indicated with the zero port, per 1246 [RFC3264]. Having received the answer, the SRC starts sending media 1247 to the SRS as indicated in the answer. 1249 In order to preserve the mapping of media to participant within the 1250 CSs in the RS, the SRC SHOULD map each unique CNAME within the CSs to 1251 a unique CNAME within the RS. Additionally, the SRC SHOULD map each 1252 unique combination of CNAME/SSRC within the CSs to a unique CNAME/ 1253 SSRC within the RS. The SRC MUST avoid SSRC collisions, rewriting 1254 SSRCs if necessary when used as CSRCs in the RS. In doing to, the 1255 SRC acts as an RTP mixer. 1257 In the event the SRS does not support this usage of CSRC values, it 1258 relies entirely on the SIPREC metadata to determine the participants 1259 included within each mixed stream. 1261 The following figure illustrates a case in which each UA represents a 1262 participant contributing two RTP sessions (e.g. one for audio and 1263 one for video), each with a single SSRC. The SRC acts as an RTP 1264 mixer and delivers the media to the SRS using two RTP sessions, 1265 mixing media from each participant into a single RTP session 1266 containing a single SSRC and two CSRCs. 1268 SSRC Sa +---------+ 1269 +-------CSRC Aa,Ba--->| | 1270 | | | 1271 | SSRC Sa | SRS | 1272 | +---CSRC Av,Bv--->| | 1273 | | +---------+ 1274 | | 1275 +----------+ 1276 +---------+ | SRC | +---------+ 1277 | |---SSRC Aa-->|(CNAME-S, |<--SSRC Ba---| | 1278 | UA-A | | CNAME-A, | | UA-B | 1279 |(CNAME-A)|---SSRC Aa-->| CNAME-B) |<--SSRC Bv---|(CNAME-B)| 1280 +---------+ +----------+ +---------+ 1282 Figure 10: SRC Using Mixing 1284 8.4. RTP Session Usage by SRS 1286 An SRS that supports recording an audio CS MUST support SRC usage of 1287 separate audio m-lines in SDP, one per CS media direction. An SRS 1288 that supports recording an video CS MUST support SRC usage of 1289 separate video m-lines in SDP, one per CS media direction. 1290 Therefore, for an SRS supporting a typical audio call, the SRS has to 1291 support receiving at least two audio m-lines. For an SRS supporting 1292 a typical audio and video call, the SRS has to support receiving at 1293 least four total m-lines in the SDP, two audio m-lines and two video 1294 m-lines. 1296 Note that these requirements allow an SRS to be implemented that 1297 supports video only, without requiring support for audio recording. 1298 They also allow an SRS to be implemented that supports recording only 1299 one direction of one stream in a CS; for example, an SRS designed to 1300 record security monitoring cameras that only send (not receive) video 1301 without any audio. These requirements were not written to prevent 1302 other modes being implemented and used, such as using a single m-line 1303 and mixing the separate audio streams together. Rather, the 1304 requirements were written to provide a common base mode to implement 1305 for the sake of interoperability. It is important to note that an 1306 SRS implementation supporting the common base may not record all 1307 media streams in a CS if a participant supports more than one m-line 1308 in a video call, such as one for camera and one for presentation. 1309 SRS implementations may support other modes as well, but have to at 1310 least support the ones above such that they interoperate in the 1311 common base mode for basic interoperability. 1313 9. Metadata 1315 9.1. Procedures at the SRC 1317 The SRC MUST deliver metadata to the SRS in a recording session; the 1318 timing of which SRC sends the metadata depends on when the metadata 1319 becomes available. Metadata SHOULD be provided by the SRC in the 1320 initial INVITE request when establishing the recording session, and 1321 subsequent metadata updates can be provided by the SRC in reINVITE 1322 and UPDATE requests ([RFC3311]) and responses in the recording 1323 session. There are cases that metadata is not available in the 1324 initial INVITE request sent by the SRC, for example, when a recording 1325 session is established in the absence of a communication session, and 1326 the SRC would update the recording session with metadata whenever 1327 metadata becomes available. 1329 Certain metadata attributes are contained in the SDP, and others are 1330 contained in a new content type "application/rs-metadata". The 1331 format of the metadata is described as part of the mechanism in 1332 [I-D.ietf-siprec-metadata]. A new "disposition-type" of Content- 1333 Disposition is defined for the purpose of carrying metadata and the 1334 value is "recording-session". The "recording-session" value 1335 indicates that the "application/rs-metadata" content contains 1336 metadata to be handled by the SRS, and the disposition can be carried 1337 in either INVITE or UPDATE requests or responses sent by the SRC. 1339 Metadata sent by the SRC can be categorized as either a full metadata 1340 snapshot or partial update. A full metadata snapshot describes all 1341 the recorded streams and all metadata associated with the recording 1342 session. When the SRC sends a full metadata snapshot, the SRC MUST 1343 send an INVITE or an UPDATE request ([RFC3311]) with an SDP offer and 1344 the "recording-session" disposition. A partial update represents an 1345 incremental update since the last metadata update sent by the SRC. A 1346 partial update sent by the SRC can be an INVITE request or response 1347 with an SDP offer, or an INVITE/UPDATE request or response containing 1348 a "recording-session" disposition, or an INVITE request containing 1349 both an SDP offer and the "recording-session" disposition. 1351 The following is an example of a full metadata snapshot sent by the 1352 SRC in the initial INVITE request: 1354 INVITE sip:recorder@example.com SIP/2.0 1355 Via: SIP/2.0/TCP src.example.com;branch=z9hG4bKdf6b622b648d9 1356 From: ;tag=35e195d2-947d-4585-946f-09839247 1357 To: 1358 Call-ID: d253c800-b0d1ea39-4a7dd-3f0e20a 1359 CSeq: 101 INVITE 1360 Max-Forwards: 70 1361 Require: siprec 1362 Accept: application/sdp, application/rs-metadata, 1363 application/rs-metadata-request 1364 Contact: ;+sip.src 1365 Content-Type: multipart/mixed;boundary=foobar 1366 Content-Length: [length] 1368 --foobar 1369 Content-Type: application/sdp 1371 v=0 1372 o=SRS 2890844526 2890844526 IN IP4 198.51.100.1 1373 s=- 1374 c=IN IP4 198.51.100.1 1375 t=0 0 1376 m=audio 12240 RTP/AVP 0 4 8 1377 a=sendonly 1378 a=label:1 1380 --foobar 1381 Content-Type: application/rs-metadata 1382 Content-Disposition: recording-session 1384 [metadata content] 1386 Figure 11: Sample INVITE request for the recording session 1388 9.2. Procedures at the SRS 1390 The SRS receives metadata updates from the SRC in INVITE and UPDATE 1391 requests. Since the SRC can send partial updates based on the 1392 previous update, the SRS needs to keep track of the sequence of 1393 updates from the SRC. 1395 In the case of an internal failure at the SRS, the SRS may fail to 1396 recognize a partial update from the SRC. The SRS may be able to 1397 recover from the internal failure by requesting for a full metadata 1398 snapshot from the SRC. Certain errors, such as syntax errors or 1399 semantic errors in the metadata information, are likely caused by an 1400 error on the SRC side, and it is likely the same error will occur 1401 again even when a full metadata snapshot is requested. In order to 1402 avoid repeating the same error, the SRS can simply terminate the 1403 recording session when a syntax error or semantic error is detected 1404 in the metadata. 1406 When the SRS explicitly requests for a full metadata snapshot, the 1407 SRS MUST send an UPDATE request without an SDP offer. A metadata 1408 snapshot request contains a content with the content disposition type 1409 "recording-session". Note that the SRS MAY generate an INVITE 1410 request without an SDP offer but this MUST NOT include a metadata 1411 snapshot request. The format of the content is "application/rs- 1412 metadata-request", and the body format is chosen to be a simple text- 1413 based format. The following shows an example: 1415 UPDATE sip:2000@src.exmaple.com SIP/2.0 1416 Via: SIP/2.0/UDP srs.example.com;branch=z9hG4bKdf6b622b648d9 1417 To: ;tag=35e195d2-947d-4585-946f-098392474 1418 From: ;tag=1234567890 1419 Call-ID: d253c800-b0d1ea39-4a7dd-3f0e20a 1420 CSeq: 1 UPDATE 1421 Max-Forwards: 70 1422 Require: siprec 1423 Contact: ;+sip.srs 1424 Accept: application/sdp, application/rs-metadata 1425 Content-Disposition: recording-session 1426 Content-Type: application/rs-metadata-request 1427 Content-Length: [length] 1429 SRS internal error 1431 Figure 12: Metadata Request 1433 The SRS MAY include the reason why a metadata snapshot request is 1434 being made to the SRC in the reason line. This reason line is free 1435 form text, mainly designed for logging purposes on the SRC side. The 1436 processing of the content by the SRC is entirely optional since the 1437 content is for logging only, and the snapshot request itself is 1438 indicated by the use of the application/rs-metadata-request content 1439 type. 1441 When the SRC receives the request for a metadata snapshot, the SRC 1442 MUST provide a full metadata snapshot in a separate INVITE or UPDATE 1443 transaction, along with an SDP offer. All subsequent metadata 1444 updates sent by the SRC MUST be based on the new metadata snapshot. 1446 The metadata received by the SRS can contain ID elements used to 1447 cross reference one element to another. An element containing the 1448 definition of an ID, and an element containing a reference to that ID 1449 will often be received from the same SRC. It is also valid for those 1450 elements to be received from different SRCs, for example, when each 1451 endpoint in the same CS act as an SRC to record the call and a common 1452 ID refers to the same CS. The SRS MUST NOT consider this an error. 1454 9.2.1. Formal Syntax 1456 The formal syntax for the application/rs-metadata-request MIME is 1457 described below using the augmented Backus-Naur Form (BNF) as 1458 described in [RFC5234]. 1460 snapshot-request = srs-reason-line CRLF 1462 srs-reason-line = [TEXT-UTF8-TRIM] 1464 10. Persistent Recording 1466 Persistent recording is a specific use case outlined in REQ-005 or 1467 Use Case 4 in [RFC6341], where a recording session can be established 1468 in the absence of a communication session. The SRC continuously 1469 records media in a recording session to the SRS even in the absence 1470 of a CS for all user agents that are part of persistent recording. 1471 By allocating recorded streams and continuously sending recorded 1472 media to the SRS, the SRC does not have to prepare new recorded 1473 streams with new SDP offer when a new communication session is 1474 created and also does not impact the timing of the CS. The SRC only 1475 needs to update the metadata when new communication sessions are 1476 created. 1478 When there is no communication sessions running on the devices with 1479 persistent recording, there is no recorded media to stream from the 1480 SRC to the SRS. In certain environments where Network Address 1481 Translator (NAT) is used, typically a minimum of flow activity is 1482 required to maintain the NAT binding for each port opened. Agents 1483 that support Interactive Connectivity Establishment (ICE) solves this 1484 problem. For non-ICE agents, in order not to lose the NAT bindings 1485 for the RTP/RTCP ports opened for the recorded streams, the SRC and 1486 SRS SHOULD follow the recommendations provided in [RFC6263] to 1487 maintain the NAT bindings. 1489 11. IANA Considerations 1491 11.1. Registration of Option Tags 1493 This specification registers two option tags. The required 1494 information for this registration, as specified in [RFC3261], is as 1495 follows. 1497 11.1.1. siprec Option Tag 1498 Name: siprec 1500 Description: This option tag is for identifying the SIP session 1501 for the purpose of recording session only. This is typically not 1502 used in a Supported header. When present in a Require header in a 1503 request, it indicates that the UAS MUST be either a SRC or SRS 1504 capable of handling the contexts of a recording session. 1506 11.1.2. record-aware Option Tag 1508 Name: record-aware 1510 Description: This option tag is to indicate the ability for the 1511 user agent to receive recording indicators in media level or 1512 session level SDP. When present in a Supported header, it 1513 indicates that the UA can receive recording indicators in media 1514 level or session level SDP. 1516 11.2. Registration of media feature tags 1518 This document registers two new media feature tags in the SIP tree 1519 per the process defined in [RFC2506] and [RFC3840] 1521 11.2.1. src feature tag 1523 Media feature tag name: sip.src 1525 ASN.1 Identifier: 25 1527 Summary of the media feature indicated by this tag: This feature 1528 tag indicates that the user agent is a Session Recording Client 1529 for the purpose for Recording Session. 1531 Values appropriate for use with this feature tag: boolean 1533 The feature tag is intended primarily for use in the following 1534 applications, protocols, services, or negotiation mechanisms: This 1535 feature tag is only useful for a Recording Session. 1537 Examples of typical use: Routing the request to a Session 1538 Recording Server. 1540 Security Considerations: Security considerations for this media 1541 feature tag are discussed in Section 11.1 of RFC 3840. 1543 11.2.2. srs feature tag 1545 Media feature tag name: sip.srs 1546 ASN.1 Identifier: 26 1548 Summary of the media feature indicated by this tag: This feature 1549 tag indicates that the user agent is a Session Recording Server 1550 for the purpose for Recording Session. 1552 Values appropriate for use with this feature tag: boolean 1554 The feature tag is intended primarily for use in the following 1555 applications, protocols, services, or negotiation mechanisms: This 1556 feature tag is only useful for a Recording Session. 1558 Examples of typical use: Routing the request to a Session 1559 Recording Client. 1561 Security Considerations: Security considerations for this media 1562 feature tag are discussed in Section 11.1 of RFC 3840. 1564 11.3. New Content-Disposition Parameter Registrations 1566 This document registers a new "disposition-type" value in Content- 1567 Disposition header: recording-session. 1569 recording-session the body describes the metadata information about 1570 the recording session 1572 11.4. Media Type Registration 1574 11.4.1. Registration of MIME Type application/rs-metadata 1576 This document registers the application/rs-metadata MIME media type 1577 in order to describe the recording session metadata. This media type 1578 is defined by the following information: 1580 Media type name: application 1582 Media subtype name: rs-metadata 1584 Required parameters: none 1586 Options parameters: none 1588 11.4.2. Registration of MIME Type application/rs-metadata-request 1590 This document registers the application/rs-metadata-request MIME 1591 media type in order to describe a recording session metadata snapshot 1592 request. This media type is defined by the following information: 1594 Media type name: application 1596 Media subtype name: rs-metadata-request 1598 Required parameters: none 1600 Options parameters: none 1602 11.5. SDP Attributes 1604 This document registers the following new SDP attributes. 1606 11.5.1. 'record' SDP Attribute 1608 Contact names: Leon Portman leon.portman@nice.com, Henry Lum 1609 henry.lum@genesyslab.com 1611 Attribute name: record 1613 Long form attribute name: Recording Indication 1615 Type of attribute: session or media level 1617 Subject to charset: no 1619 This attribute provides the recording indication for the session or 1620 media stream. 1622 Allowed attribute values: on, off, paused 1624 11.5.2. 'recordpref' SDP Attribute 1626 Contact names: Leon Portman leon.portman@nice.com, Henry Lum 1627 henry.lum@genesyslab.com 1629 Attribute name: recordpref 1631 Long form attribute name: Recording Preference 1633 Type of attribute: session or media level 1635 Subject to charset: no 1637 This attribute provides the recording preference for the session or 1638 media stream. 1640 Allowed attribute values: on, off, pause, nopreference 1642 12. Security Considerations 1644 The recording session is fundamentally a standard SIP dialog 1645 [RFC3261], therefore, the recording session can reuse any of the 1646 existing SIP security mechanisms available for securing the session 1647 signaling, the recorded media, and the metadata. The use cases and 1648 requirements document [RFC6341] outlines the general security 1649 considerations, and this document describes specific security 1650 recommendations. 1652 The SRC and SRS MUST support SIP with TLS and MAY support SIPS with 1653 TLS as per [RFC5630]. The Recording Session SHOULD be at least as 1654 secure as the Communication Session, meaning using at least the same 1655 strength of cipher suite as the CS if the CS is secured. For 1656 example, if the CS uses SIPS for signaling and RTP/SAVP for media, 1657 then the RS should not downgrade the level of security in the RS to 1658 SIP or plain RTP since doing so will mean an automatic security 1659 downgrade for the CS. In deployments where the SRC and the SRS are 1660 in the same administrative domain and the same physical switch that 1661 prevents outside user access, some SRCs may choose to lower the level 1662 of security when establishing a recording session. While physically 1663 securing the SRC and SRS may prevent an outside attacker from 1664 accessing important call recordings, this still does not prevent an 1665 inside attacker from accessing the internal network to gain access to 1666 the call recordings. 1668 12.1. Authentication and Authorization 1670 At the transport level, the recording session uses TLS authentication 1671 to validate the authenticity of the SRC and SRS. The SRC and SRS 1672 MUST implement TLS mutual authentication for establishing the 1673 recording session. Whether the SRC/SRS chooses to use TLS mutual 1674 authentication is a deployment decision. In deployments where the 1675 SRC and the SRS are in the same administrative domain, the SRC and 1676 SRS may choose not to authenticate each other, or to have the SRC 1677 authenticate the SRS only, as there is an inherent trust relation 1678 between the SRC and the SRS when they are hosted in the same 1679 administrative domain. In deployments where the SRS can be hosted on 1680 a different administrative domain, it is important to perform mutual 1681 authentication to ensure the authenticity of both the SRC and the SRS 1682 before transmitting any recorded media. The risk of not 1683 authenticating the SRS is that the recording may be sent to a 1684 compromised SRS and that a sensitive call recording will be obtained 1685 by an attacker. On the other hand, the risk of not authenticating 1686 the SRC is that an SRS will accept calls from an unknown SRC and 1687 allow potential forgery of call recordings. 1689 There may be scenarios in which the signaling between the SRC and SRS 1690 is not direct, e.g. a SIP proxy exists between the SRC and the SRS. 1691 In such scenarios, each hop is subject to the TLS mutual 1692 authentication constraint and transitive trust at each hop is 1693 utilized. Additionally, an SRC or SRS may use other existing SIP 1694 mechanisms available, including but not limited to, Digest 1695 Authentication [RFC3261], Asserted Identity [RFC3325], and Connected 1696 Identity [RFC4916]. 1698 The SRS may have its own set of recording policies to authorize 1699 recording requests from the SRC. The use of recording policies is 1700 outside the scope of the Session Recording Protocol. 1702 12.2. RTP handling 1704 In many scenarios it will be critical for the media transported 1705 between the SRC and the SRS to be protected. Media encryption is an 1706 important element in the overall SIPREC solution; therefore the SRC 1707 and the SRS MUST support RTP/SAVP [RFC3711] and RTP/SAVPF [RFC5124]. 1708 RTP/SAVP and RTP/SAVPF provide media encryption, integrity 1709 protection, replay protection, and a limited form of source 1710 authentication. They do not contain or require a specific keying 1711 mechanism. At a minimum, the SRC and SRS MUST support the SDP 1712 Security Descriptions (SDES) key negotiation mechanism [RFC4568]. 1713 For cases in which DTLS-SRTP is used to encrypt a CS media stream, an 1714 SRC may use SRTP Encrypted Key Transport (EKT) 1715 [I-D.ietf-avt-srtp-ekt] in order to use SRTP-SDES in the RS without 1716 needing to re-encrypt the media. 1718 When RTP/SAVP or RTP/SAVPF is used, an SRC can choose to use the same 1719 or different keys in the RS than the ones used in the CS. Some SRCs 1720 are designed to simply replicate RTP packets from a CS media stream 1721 to the SRS, in which case the SRC will use the same key in the RS as 1722 used in the CS. In this case, the SRC MUST secure the SDP containing 1723 the keying material in the RS with at least the same level of 1724 security as in the CS. The risk of lowering the level of security in 1725 the RS is that it will effectively become a downgrade attack on the 1726 CS since the same key is used for both CS and RS. 1728 SRCs that decrypt an encrypted CS media stream and re-encrypt it when 1729 sending it to the SRS MUST use a different key for the RS media 1730 stream than what is used for the CS media stream, to ensure that it 1731 is not possible for someone who has the key for the CS media stream 1732 to access recorded data they are not authorized to access. 1734 12.3. Metadata 1735 Metadata contains sensitive information such as the address of record 1736 of the participants and other extension data placed by the SRC. It 1737 is essential to protect the content of the metadata in the RS. Since 1738 metadata is a content type transmitted in SIP signaling, metadata 1739 SHOULD be protected at the transport level by SIPS/TLS. 1741 12.4. Storage and playback 1743 While storage and playback of the call recording is beyond the scope 1744 of this document, it is worthwhile to mention here that it is also 1745 important for the recording storage and playback to provide a level 1746 of security that is comparable to the communication session. It 1747 would defeat the purpose of securing both the communication session 1748 and the recording session mentioned in the previous sections if the 1749 recording can be easily played back with a simple unsecured HTTP 1750 interface without any form of authentication or authorization. 1752 13. Acknowledgements 1754 We want to thank John Elwell, Paul Kyzivat, Partharsarathi R, Ram 1755 Mohan R, Hadriel Kaplan, Adam Roach, Miguel Garcia, Thomas Stach, 1756 Muthu Perumal, Dan Wing, and Magnus Westerlund for their valuable 1757 comments and inputs to this document. 1759 14. References 1761 14.1. Normative References 1763 [I-D.ietf-siprec-metadata] 1764 R, R., Ravindran, P., and P. Kyzivat, "Session Initiation 1765 Protocol (SIP) Recording Metadata", draft-ietf-siprec- 1766 metadata-11 (work in progress), January 2013. 1768 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1769 Requirement Levels", BCP 14, RFC 2119, March 1997. 1771 [RFC2506] Holtman, K., Mutz, A., and T. Hardie, "Media Feature Tag 1772 Registration Procedure", BCP 31, RFC 2506, March 1999. 1774 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 1775 A., Peterson, J., Sparks, R., Handley, M., and E. 1776 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 1777 June 2002. 1779 [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model 1780 with Session Description Protocol (SDP)", RFC 3264, June 1781 2002. 1783 [RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, 1784 "Indicating User Agent Capabilities in the Session 1785 Initiation Protocol (SIP)", RFC 3840, August 2004. 1787 [RFC4574] Levin, O. and G. Camarillo, "The Session Description 1788 Protocol (SDP) Label Attribute", RFC 4574, August 2006. 1790 [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 1791 Specifications: ABNF", STD 68, RFC 5234, January 2008. 1793 14.2. Informative References 1795 [I-D.ietf-avt-srtp-ekt] 1796 Wing, D., McGrew, D., and K. Fischer, "Encrypted Key 1797 Transport for Secure RTP", draft-ietf-avt-srtp-ekt-03 1798 (work in progress), October 2011. 1800 [I-D.ietf-siprec-architecture] 1801 Hutton, A., Portman, L., Jain, R., and K. Rehor, "An 1802 Architecture for Media Recording using the Session 1803 Initiation Protocol", draft-ietf-siprec-architecture-07 1804 (work in progress), November 2012. 1806 [RFC3311] Rosenberg, J., "The Session Initiation Protocol (SIP) 1807 UPDATE Method", RFC 3311, October 2002. 1809 [RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private 1810 Extensions to the Session Initiation Protocol (SIP) for 1811 Asserted Identity within Trusted Networks", RFC 3325, 1812 November 2002. 1814 [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. 1815 Jacobson, "RTP: A Transport Protocol for Real-Time 1816 Applications", STD 64, RFC 3550, July 2003. 1818 [RFC3551] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and 1819 Video Conferences with Minimal Control", STD 65, RFC 3551, 1820 July 2003. 1822 [RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. 1823 Norrman, "The Secure Real-time Transport Protocol (SRTP)", 1824 RFC 3711, March 2004. 1826 [RFC4568] Andreasen, F., Baugher, M., and D. Wing, "Session 1827 Description Protocol (SDP) Security Descriptions for Media 1828 Streams", RFC 4568, July 2006. 1830 [RFC4585] Ott, J., Wenger, S., Sato, N., Burmeister, C., and J. Rey, 1831 "Extended RTP Profile for Real-time Transport Control 1832 Protocol (RTCP)-Based Feedback (RTP/AVPF)", RFC 4585, July 1833 2006. 1835 [RFC4916] Elwell, J., "Connected Identity in the Session Initiation 1836 Protocol (SIP)", RFC 4916, June 2007. 1838 [RFC4961] Wing, D., "Symmetric RTP / RTP Control Protocol (RTCP)", 1839 BCP 131, RFC 4961, July 2007. 1841 [RFC5104] Wenger, S., Chandra, U., Westerlund, M., and B. Burman, 1842 "Codec Control Messages in the RTP Audio-Visual Profile 1843 with Feedback (AVPF)", RFC 5104, February 2008. 1845 [RFC5124] Ott, J. and E. Carrara, "Extended Secure RTP Profile for 1846 Real-time Transport Control Protocol (RTCP)-Based Feedback 1847 (RTP/SAVPF)", RFC 5124, February 2008. 1849 [RFC5168] Levin, O., Even, R., and P. Hagendorf, "XML Schema for 1850 Media Control", RFC 5168, March 2008. 1852 [RFC5630] Audet, F., "The Use of the SIPS URI Scheme in the Session 1853 Initiation Protocol (SIP)", RFC 5630, October 2009. 1855 [RFC5761] Perkins, C. and M. Westerlund, "Multiplexing RTP Data and 1856 Control Packets on a Single Port", RFC 5761, April 2010. 1858 [RFC6222] Begen, A., Perkins, C., and D. Wing, "Guidelines for 1859 Choosing RTP Control Protocol (RTCP) Canonical Names 1860 (CNAMEs)", RFC 6222, April 2011. 1862 [RFC6263] Marjou, X. and A. Sollaud, "Application Mechanism for 1863 Keeping Alive the NAT Mappings Associated with RTP / RTP 1864 Control Protocol (RTCP) Flows", RFC 6263, June 2011. 1866 [RFC6341] Rehor, K., Portman, L., Hutton, A., and R. Jain, "Use 1867 Cases and Requirements for SIP-Based Media Recording 1868 (SIPREC)", RFC 6341, August 2011. 1870 Authors' Addresses 1871 Leon Portman 1872 NICE Systems 1873 8 Hapnina 1874 Ra'anana 43017 1875 Israel 1877 Email: leon.portman@nice.com 1879 Henry Lum (editor) 1880 Genesys 1881 1380 Rodick Road, Suite 201 1882 Markham, Ontario L3R4G5 1883 Canada 1885 Email: henry.lum@genesyslab.com 1887 Charles Eckel 1888 Cisco 1889 170 West Tasman Drive 1890 San Jose, CA 95134 1891 United States 1893 Email: eckelcu@cisco.com 1895 Alan Johnston 1896 Avaya 1897 St. Louis, MO 63124 1899 Email: alan.b.johnston@gmail.com 1901 Andrew Hutton 1902 Siemens Enterprise Communications 1903 Brickhill Street 1904 Milton Keynes MK15 0DJ 1905 United Kingdom 1907 Email: andrew.hutton@siemens-enterprise.com