idnits 2.17.1 draft-ietf-avt-rapid-acquisition-for-rtp-16.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 : ---------------------------------------------------------------------------- -- The document has examples using IPv4 documentation addresses according to RFC6890, but does not use any IPv6 documentation addresses. Maybe there should be IPv6 examples, too? Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 607 has weird spacing: '...| Burst and |...' == The document seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 16, 2010) is 4940 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) == Missing Reference: 'RFCXXXX' is mentioned on line 2342, but not defined ** Obsolete normative reference: RFC 4566 (Obsoleted by RFC 8866) ** Obsolete normative reference: RFC 5285 (Obsoleted by RFC 8285) == Outdated reference: A later version (-13) exists of draft-ietf-avt-rapid-rtp-sync-12 == Outdated reference: A later version (-04) exists of draft-ietf-avt-rtcp-port-for-ssm-02 == Outdated reference: A later version (-11) exists of draft-ietf-avt-ports-for-ucast-mcast-rtp-02 ** Obsolete normative reference: RFC 5077 (Obsoleted by RFC 8446) == Outdated reference: A later version (-01) exists of draft-begen-avt-rams-scenarios-00 == Outdated reference: A later version (-05) exists of draft-ietf-avt-rtp-cnames-01 == Outdated reference: A later version (-03) exists of draft-ietf-avt-ecn-for-rtp-02 == Outdated reference: A later version (-03) exists of draft-ietf-avt-srtp-ekt-01 -- Obsolete informational reference (is this intentional?): RFC 5226 (Obsoleted by RFC 8126) Summary: 3 errors (**), 0 flaws (~~), 11 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 AVT B. VerSteeg 3 Internet-Draft A. Begen 4 Intended status: Standards Track Cisco 5 Expires: April 19, 2011 T. VanCaenegem 6 Alcatel-Lucent 7 Z. Vax 8 Microsoft Corporation 9 October 16, 2010 11 Unicast-Based Rapid Acquisition of Multicast RTP Sessions 12 draft-ietf-avt-rapid-acquisition-for-rtp-16 14 Abstract 16 When an RTP receiver joins a multicast session, it may need to 17 acquire and parse certain Reference Information before it can process 18 any data sent in the multicast session. Depending on the join time, 19 length of the Reference Information repetition (or appearance) 20 interval, size of the Reference Information as well as the 21 application and transport properties, the time lag before an RTP 22 receiver can usefully consume the multicast data, which we refer to 23 as the Acquisition Delay, varies and can be large. This is an 24 undesirable phenomenon for receivers that frequently switch among 25 different multicast sessions, such as video broadcasts. 27 In this document, we describe a method using the existing RTP and RTP 28 Control Protocol (RTCP) machinery that reduces the acquisition delay. 29 In this method, an auxiliary unicast RTP session carrying the 30 Reference Information to the receiver precedes/accompanies the 31 multicast stream. This unicast RTP flow can be transmitted at a 32 faster than natural bitrate to further accelerate the acquisition. 33 The motivating use case for this capability is multicast applications 34 that carry real-time compressed audio and video. However, the 35 proposed method can also be used in other types of multicast 36 applications where the acquisition delay is long enough to be a 37 problem. 39 Status of this Memo 41 This Internet-Draft is submitted in full conformance with the 42 provisions of BCP 78 and BCP 79. 44 Internet-Drafts are working documents of the Internet Engineering 45 Task Force (IETF). Note that other groups may also distribute 46 working documents as Internet-Drafts. The list of current Internet- 47 Drafts is at http://datatracker.ietf.org/drafts/current/. 49 Internet-Drafts are draft documents valid for a maximum of six months 50 and may be updated, replaced, or obsoleted by other documents at any 51 time. It is inappropriate to use Internet-Drafts as reference 52 material or to cite them other than as "work in progress." 54 This Internet-Draft will expire on April 19, 2011. 56 Copyright Notice 58 Copyright (c) 2010 IETF Trust and the persons identified as the 59 document authors. All rights reserved. 61 This document is subject to BCP 78 and the IETF Trust's Legal 62 Provisions Relating to IETF Documents 63 (http://trustee.ietf.org/license-info) in effect on the date of 64 publication of this document. Please review these documents 65 carefully, as they describe your rights and restrictions with respect 66 to this document. Code Components extracted from this document must 67 include Simplified BSD License text as described in Section 4.e of 68 the Trust Legal Provisions and are provided without warranty as 69 described in the Simplified BSD License. 71 This document may contain material from IETF Documents or IETF 72 Contributions published or made publicly available before November 73 10, 2008. The person(s) controlling the copyright in some of this 74 material may not have granted the IETF Trust the right to allow 75 modifications of such material outside the IETF Standards Process. 76 Without obtaining an adequate license from the person(s) controlling 77 the copyright in such materials, this document may not be modified 78 outside the IETF Standards Process, and derivative works of it may 79 not be created outside the IETF Standards Process, except to format 80 it for publication as an RFC or to translate it into languages other 81 than English. 83 Table of Contents 85 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 86 1.1. Acquisition of RTP Streams vs. RTP Sessions . . . . . . . 6 87 1.2. Outline . . . . . . . . . . . . . . . . . . . . . . . . . 7 88 2. Requirements Notation . . . . . . . . . . . . . . . . . . . . 7 89 3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 7 90 4. Elements of Delay in Multicast Applications . . . . . . . . . 9 91 5. Protocol Design Considerations and Their Effect on 92 Resource Management for Rapid Acquisition . . . . . . . . . . 10 93 6. Rapid Acquisition of Multicast RTP Sessions (RAMS) . . . . . . 12 94 6.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 13 95 6.2. Message Flows . . . . . . . . . . . . . . . . . . . . . . 13 96 6.3. Synchronization of Primary Multicast Streams . . . . . . . 24 97 6.4. Burst Shaping and Congestion Control in RAMS . . . . . . . 24 98 6.5. Failure Cases . . . . . . . . . . . . . . . . . . . . . . 27 99 7. Encoding of the Signaling Protocol in RTCP . . . . . . . . . . 28 100 7.1. Extensions . . . . . . . . . . . . . . . . . . . . . . . . 29 101 7.1.1. Vendor-Neutral Extensions . . . . . . . . . . . . . . 30 102 7.1.2. Private Extensions . . . . . . . . . . . . . . . . . . 30 103 7.2. RAMS Request . . . . . . . . . . . . . . . . . . . . . . . 31 104 7.3. RAMS Information . . . . . . . . . . . . . . . . . . . . . 34 105 7.3.1. Response Code Definitions . . . . . . . . . . . . . . 37 106 7.4. RAMS Termination . . . . . . . . . . . . . . . . . . . . . 39 107 8. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 40 108 8.1. Definitions . . . . . . . . . . . . . . . . . . . . . . . 40 109 8.2. Requirements . . . . . . . . . . . . . . . . . . . . . . . 41 110 8.3. Example and Discussion . . . . . . . . . . . . . . . . . . 41 111 9. NAT Considerations . . . . . . . . . . . . . . . . . . . . . . 44 112 10. Security Considerations . . . . . . . . . . . . . . . . . . . 45 113 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 47 114 11.1. Registration of SDP Attributes . . . . . . . . . . . . . . 48 115 11.2. Registration of SDP Attribute Values . . . . . . . . . . . 48 116 11.3. Registration of FMT Values . . . . . . . . . . . . . . . . 48 117 11.4. SFMT Values for RAMS Messages Registry . . . . . . . . . . 49 118 11.5. RAMS TLV Space Registry . . . . . . . . . . . . . . . . . 49 119 11.6. RAMS Response Code Space Registry . . . . . . . . . . . . 50 120 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 52 121 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 52 122 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 52 123 14.1. Normative References . . . . . . . . . . . . . . . . . . . 52 124 14.2. Informative References . . . . . . . . . . . . . . . . . . 54 125 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 55 127 1. Introduction 129 Most multicast flows carry a stream of inter-related data. Receivers 130 need to acquire certain information to start processing any data sent 131 in the multicast session. This document refers to this information 132 as Reference Information. The Reference Information is 133 conventionally sent periodically in the multicast session (although 134 its content can change over time) and usually consists of items such 135 as a description of the schema for the rest of the data, references 136 to which data to process, encryption information including keys, as 137 well as any other information required to process the data in the 138 multicast stream [IC2009]. 140 Real-time multicast applications require receivers to buffer data. 141 Receivers may have to buffer data to smooth out the network jitter, 142 to allow loss-repair methods such as Forward Error Correction and 143 retransmission to recover the missing packets, and to satisfy the 144 data processing requirements of the application layer. 146 When a receiver joins a multicast session, it has no control over 147 what point in the flow is currently being transmitted. Sometimes the 148 receiver might join the session right before the Reference 149 Information is sent in the session. In this case, the required 150 waiting time is usually minimal. Other times, the receiver might 151 join the session right after the Reference Information has been 152 transmitted. In this case, the receiver has to wait for the 153 Reference Information to appear again in the flow before it can start 154 processing any multicast data. In some other cases, the Reference 155 Information is not contiguous in the flow but dispersed over a large 156 period, which forces the receiver to wait for the whole Reference 157 Information to arrive before starting to process the rest of the 158 data. 160 The net effect of waiting for the Reference Information and waiting 161 for various buffers to fill up is that receivers can experience 162 significantly large delays in data processing. In this document, we 163 refer to the difference between the time an RTP receiver joins the 164 multicast session and the time the RTP receiver acquires all the 165 necessary Reference Information as the Acquisition Delay. The 166 acquisition delay might not be the same for different receivers; it 167 usually varies depending on the join time, length of the Reference 168 Information repetition (or appearance) interval, size of the 169 Reference Information as well as the application and transport 170 properties. 172 The varying nature of the acquisition delay adversely affects the 173 receivers that frequently switch among multicast sessions. While 174 this problem equally applies to both any-source (ASM) and source- 175 specific (SSM) multicast applications, in this specification we 176 address it for the SSM-based multicast applications by describing a 177 method that uses the fundamental tools offered by the existing RTP 178 and RTCP protocols [RFC3550]. In this method, either the multicast 179 source (or the distribution source in an SSM session) retains the 180 Reference Information for a period after its transmission, or an 181 intermediary network element (that we refer to as Retransmission 182 Server) joins the multicast session and continuously caches the 183 Reference Information as it is sent in the session and acts as a 184 feedback target (See [RFC5760]) for the session. When an RTP 185 receiver wishes to join the same multicast session, instead of simply 186 issuing a Source Filtering Group Management Protocol (SFGMP) Join 187 message, it sends a request to the feedback target for the session 188 and asks for the Reference Information. The retransmission server 189 starts a new unicast RTP (retransmission) session and sends the 190 Reference Information to the RTP receiver over that session. If 191 there is spare bandwidth, the retransmission server might burst the 192 Reference Information faster than its natural rate. As soon as the 193 receiver acquires the Reference Information, it can join the 194 multicast session and start processing the multicast data. A 195 simplified network diagram showing this method through an 196 intermediary network element is depicted in Figure 1. 198 This method potentially reduces the acquisition delay. We refer to 199 this method as Unicast-based Rapid Acquisition of Multicast RTP 200 Sessions. A primary use case for this method is to reduce the 201 channel-change times in IPTV networks where compressed video streams 202 are multicast in different SSM sessions and viewers randomly join 203 these sessions. 205 ----------------------- 206 +--->| Intermediary | 207 | | Network Element | 208 | ...|(Retransmission Server)| 209 | : ----------------------- 210 | : 211 | v 212 ----------- ---------- ---------- 213 | Multicast | | |---------->| Joining | 214 | Source |------->| Router |..........>| RTP | 215 | | | | | Receiver | 216 ----------- ---------- ---------- 217 | 218 | ---------- 219 +---------------->| Existing | 220 | RTP | 221 | Receiver | 222 ---------- 224 -------> Multicast RTP Flow 225 .......> Unicast RTP Flow 227 Figure 1: Rapid acquisition through an intermediary network element 229 A principle design goal in this solution is to use the existing tools 230 in the RTP/RTCP protocol family. This improves the versatility of 231 the existing implementations, and promotes faster deployment and 232 better interoperability. To this effect, we use the unicast 233 retransmission support of RTP [RFC4588] and the capabilities of RTCP 234 to handle the signaling needed to accomplish the acquisition. 236 A reasonable effort has been made in this specification to design a 237 solution that reliably works in both engineered and best-effort 238 networks. However, a proper congestion control combined with the 239 desired behavior of this solution is difficult to achieve. Rather, 240 this solution has been designed based on an assumption that the 241 retransmission server and the RTP receivers have some knowledge about 242 where the bottleneck between them is. This assumption may not hold 243 unless both the retransmission server and the RTP receiver are in the 244 same edge network. This solution is not designed to be used across 245 any best-effort path of the Internet. Thus, a careful consideration 246 should be given when deploying this solution in best-effort networks. 248 1.1. Acquisition of RTP Streams vs. RTP Sessions 250 In this memo we describe a protocol that handles the rapid 251 acquisition of a single multicast RTP session (called primary 252 multicast RTP session) carrying one or more RTP streams (called 253 primary multicast streams). If desired, multiple instances of this 254 protocol may be run in parallel to acquire multiple RTP sessions 255 simultaneously. 257 When an RTP receiver requests the Reference Information from the 258 retransmission server, it can opt to rapidly acquire a specific 259 subset of the available RTP streams in the primary multicast RTP 260 session. Alternatively, the RTP receiver can request the rapid 261 acquisition of all of the RTP streams in that RTP session. 262 Regardless of how many RTP streams are requested by the RTP receiver 263 or how many will be actually sent by the retransmission server, only 264 one unicast RTP session will be established by the retransmission 265 server. This unicast RTP session is separate from the associated 266 primary multicast RTP session. As a result, there are always two 267 different RTP sessions in a single instance of the rapid acquisition 268 protocol: (i) the primary multicast RTP session with its associated 269 unicast feedback and (ii) the unicast RTP session. 271 If the RTP receiver wants to rapidly acquire multiple RTP sessions 272 simultaneously, separate unicast RTP sessions will be established for 273 each of them. 275 1.2. Outline 277 In the rest of this specification, we have the following outline: In 278 Section 4, we describe the delay components in generic multicast 279 applications. Section 5 presents an overview of the protocol design 280 considerations for rapid acquisition. We provide the protocol 281 details of the rapid acquisition method in Section 6 and Section 7. 282 Section 8 and Section 9 discuss the SDP signaling issues with 283 examples and NAT-related issues, respectively. Finally, Section 10 284 discusses the security considerations. 286 Section 3 provides a list of the definitions frequently used in this 287 document. 289 2. Requirements Notation 291 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 292 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 293 document are to be interpreted as described in [RFC2119]. 295 3. Definitions 297 This document uses the following acronyms and definitions frequently: 299 (Primary) SSM (or Multicast) Session: The multicast session to which 300 RTP receivers can join at a random point in time. A primary SSM 301 session can carry multiple RTP streams. 303 Primary Multicast RTP Session: The multicast RTP session an RTP 304 receiver is interested in acquiring rapidly. From the RTP receiver's 305 viewpoint, the primary multicast RTP session has one associated 306 unicast RTCP feedback stream to a Feedback Target, in addition to the 307 primary multicast RTP stream(s). 309 Primary Multicast (RTP) Streams: The RTP stream(s) carried in the 310 primary multicast RTP session. 312 Source Filtering Group Management Protocol (SFGMP): Following the 313 definition in [RFC4604], SFGMP refers to the Internet Group 314 Management Protocol (IGMP) version 3 [RFC3376] and the Multicast 315 Listener Discovery Protocol (MLD) version 2 [RFC3810] in the IPv4 and 316 IPv6 networks, respectively. However, the rapid acquisition method 317 introduced in this document does not depend on a specific version of 318 either of these group management protocols. In the remainder of this 319 document, SFGMP will refer to any group management protocol that has 320 Join and Leave functionalities. 322 Feedback Target (FT): Unicast RTCP feedback target as defined in 323 [RFC5760]. FT_Ap denotes a specific feedback target running on a 324 particular address and port. 326 Retransmission (or Burst) Packet: An RTP packet that is formatted as 327 defined in Section 4 of [RFC4588]. The payload of a retransmission 328 or burst packet comprises the retransmission payload header followed 329 by the payload of the original RTP packet. 331 Reference Information: The set of certain media content and metadata 332 information that is sufficient for an RTP receiver to start usefully 333 consuming a media stream. The meaning, format and size of this 334 information are specific to the application and are out of scope of 335 this document. 337 Preamble Information: A more compact form of the whole or a subset 338 of the Reference Information transmitted out-of-band. 340 (Unicast) Burst (or Retransmission) RTP Session: The unicast RTP 341 session used to send one or more unicast burst RTP streams and their 342 associated RTCP messages. The terms "burst RTP session" and 343 "retransmission RTP session" can be used interchangeably. 345 (Unicast) Burst (Stream): A unicast stream of RTP retransmission 346 packets that enable an RTP receiver to rapidly acquire the Reference 347 Information associated with a primary multicast stream. Each burst 348 stream is identified by its Synchronization Source (SSRC) identifier 349 that is unique in the primary multicast RTP session. Following the 350 session-multiplexing guidelines in [RFC4588], each unicast burst 351 stream will use the same SSRC and Canonical Name (CNAME) as its 352 primary multicast RTP stream. 354 Retransmission Server (RS): The RTP/RTCP endpoint that can generate 355 the retransmission packets and the burst streams. The RS may also 356 generate other non-retransmission packets to aid rapid acquisition. 358 4. Elements of Delay in Multicast Applications 360 In a source-specific (SSM) multicast delivery system, there are three 361 major elements that contribute to the overall acquisition delay when 362 an RTP receiver switches from one multicast session to another one. 363 These are: 365 o Multicast switching delay 367 o Reference Information latency 369 o Buffering delays 371 Multicast switching delay is the delay that is experienced to leave 372 the current multicast session (if any) and join the new multicast 373 session. In typical systems, the multicast join and leave operations 374 are handled by a group management protocol. For example, the 375 receivers and routers participating in a multicast session can use 376 the Internet Group Management Protocol (IGMP) version 3 [RFC3376] or 377 the Multicast Listener Discovery Protocol (MLD) version 2 [RFC3810]. 378 In either of these protocols, when a receiver wants to join a 379 multicast session, it sends a message to its upstream router and the 380 routing infrastructure sets up the multicast forwarding state to 381 deliver the packets of the multicast session to the new receiver. 382 Depending on the proximity of the upstream router, the current state 383 of the multicast tree, the load on the system and the protocol 384 implementation, the join times vary. Current systems provide join 385 latencies usually less than 200 milliseconds (ms). If the receiver 386 had been participating in another multicast session before joining 387 the new session, it needs to send a Leave message to its upstream 388 router to leave the session. In common multicast routing protocols, 389 the leave times are usually smaller than the join times, however, it 390 is possible that the Leave and Join messages might get lost, in which 391 case the multicast switching delay inevitably increases. 393 Reference Information latency is the time it takes the receiver to 394 acquire the Reference Information. It is highly dependent on the 395 proximity of the actual time the receiver joined the session to the 396 next time the Reference Information will be sent to the receivers in 397 the session, whether the Reference Information is sent contiguously 398 or not, and the size of the Reference Information. For some 399 multicast flows, there is a little or no interdependency in the data, 400 in which case the Reference Information latency will be nil or 401 negligible. For other multicast flows, there is a high degree of 402 interdependency. One example of interest is the multicast flows that 403 carry compressed audio/video. For these flows, the Reference 404 Information latency can become quite large and be a major contributor 405 to the overall delay. 407 The buffering component of the overall acquisition delay is driven by 408 the way the application layer processes the payload. In many 409 multicast applications, an unreliable transport protocol such as UDP 410 [RFC0768] is often used to transmit the data packets, and the 411 reliability, if needed, is usually addressed through other means such 412 as Forward Error Correction (e.g., 413 [I-D.ietf-fecframe-interleaved-fec-scheme]) and retransmission. 414 These loss-repair methods require buffering at the receiver side to 415 function properly. In many applications, it is also often necessary 416 to de-jitter the incoming data packets before feeding them to the 417 application. The de-jittering process also increases the buffering 418 delays. Besides these network-related buffering delays, there are 419 also specific buffering needs that are required by the individual 420 applications. For example, standard video decoders typically require 421 an amount, sometimes up to a few seconds, of coded video data to be 422 available in the pre-decoding buffers prior to starting to decode the 423 video bitstream. 425 5. Protocol Design Considerations and Their Effect on Resource 426 Management for Rapid Acquisition 428 This section is for informational purposes and does not contain 429 requirements for implementations. 431 Rapid acquisition is an optimization of a system that is expected to 432 continue to work correctly and properly whether or not the 433 optimization is effective, or even fails due to lost control and 434 feedback messages, congestion, or other problems. This is 435 fundamental to the overall design requirements surrounding the 436 protocol definition and to the resource management schemes to be 437 employed together with the protocol (e.g., QoS machinery, server load 438 management, etc). In particular, the system needs to operate within 439 a number of constraints: 441 o First, a rapid acquisition operation must fail gracefully. The 442 user experience must be not significantly worse for trying and 443 failing to complete rapid acquisition compared to simply joining 444 the multicast session. 446 o Second, providing the rapid acquisition optimizations must not 447 cause collateral damage to either the multicast session being 448 joined, or other multicast sessions sharing resources with the 449 rapid acquisition operation. In particular, the rapid acquisition 450 operation must avoid interference with the multicast session that 451 might be simultaneously being received by other hosts. In 452 addition, it must also avoid interference with other multicast 453 sessions sharing the same network resources. These properties are 454 possible, but are usually difficult to achieve. 456 One challenge is the existence of multiple bandwidth bottlenecks 457 between the receiver and the server(s) in the network providing the 458 rapid acquisition service. In commercial IPTV deployments, for 459 example, bottlenecks are often present in the aggregation network 460 connecting the IPTV servers to the network edge, the access links 461 (e.g., DSL, DOCSIS) and in the home network of the subscribers. Some 462 of these links might serve only a single subscriber, limiting 463 congestion impact to the traffic of only that subscriber, but others 464 can be shared links carrying multicast sessions of many subscribers. 465 Also note that the state of these links can vary over time. The 466 receiver might have knowledge of a portion of this network, or might 467 have partial knowledge of the entire network. The methods employed 468 by the devices to acquire this network state information is out of 469 scope for this document. The receiver should be able to signal the 470 server with the bandwidth that it believes it can handle. The server 471 also needs to be able to rate limit the flow in order to stay within 472 the performance envelope that it knows about. Both the server and 473 receiver need to be able to inform the other of changes in the 474 requested and delivered rates. However, the protocol must be robust 475 in the presence of packet loss, so this signaling must include the 476 appropriate default behaviors. 478 A second challenge is that for some uses (e.g., high-bitrate video) 479 the unicast burst bitrate is high while the flow duration of the 480 unicast burst is short. This is because the purpose of the unicast 481 burst is to allow the RTP receiver to join the multicast quickly and 482 thereby limit the overall resources consumed by the burst. Such 483 high-bitrate, short-duration flows are not amenable to conventional 484 admission control techniques. For example, end-to-end per-flow 485 signaled admission control techniques such as RSVP have too much 486 latency and control channel overhead to be a good fit for rapid 487 acquisition. Similarly, using a TCP (or TCP-like) approach with a 488 3-way handshake and slow-start to avoid inducing congestion would 489 defeat the purpose of attempting rapid acquisition in the first place 490 by introducing many round-trip times (RTT) of delay. 492 These observations lead to certain unavoidable requirements and goals 493 for a rapid acquisition protocol. These are: 495 o The protocol must be designed to allow a deterministic upper bound 496 on the extra bandwidth used (compared to just joining the 497 multicast session). A reasonable size bound is e*B, where B is 498 the nominal bandwidth of the primary multicast streams, and e is 499 an excess-bandwidth coefficient. The total duration of the 500 unicast burst must have a reasonable bound; long unicast bursts 501 devolve to the bandwidth profile of multi-unicast for the whole 502 system. 504 o The scheme should minimize (or better eliminate) the overlap of 505 the unicast burst and the primary multicast stream. This 506 minimizes the window during which congestion could be induced on a 507 bottleneck link compared to just carrying the multicast or unicast 508 packets alone. 510 o The scheme must minimize (or better eliminate) any gap between the 511 unicast burst and the primary multicast stream, which has to be 512 repaired later, or in the absence of repair, will result in loss 513 being experienced by the application. 515 In addition to the above, there are some other protocol design issues 516 to be considered. First, there is at least one RTT of "slop" in the 517 control loop. In starting a rapid acquisition burst, this manifests 518 as the time between the client requesting the unicast burst and the 519 burst description and/or the first unicast burst packets arriving at 520 the receiver. For managing and terminating the unicast burst, there 521 are two possible approaches for the control loop: The receiver can 522 adapt to the unicast burst as received, converge based on observation 523 and explicitly terminate the unicast burst with a second control loop 524 exchange (which takes a minimum of one RTT, just as starting the 525 unicast burst does). Alternatively, the server generating the 526 unicast burst can pre-compute the burst parameters based on the 527 information in the initial request and tell the receiver the burst 528 duration. 530 The protocol described in the next section allows either method of 531 controlling the rapid acquisition unicast burst. 533 6. Rapid Acquisition of Multicast RTP Sessions (RAMS) 535 We start this section with an overview of the rapid acquisition of 536 multicast sessions (RAMS) method. 538 6.1. Overview 540 [RFC5760] specifies an extension to the RTP Control Protocol (RTCP) 541 to use unicast feedback in an SSM session. It defines an 542 architecture that introduces the concept of Distribution Source, 543 which - in an SSM context - distributes the RTP data and 544 redistributes RTCP information to all RTP receivers. This RTCP 545 information is retrieved from the Feedback Target, to which RTCP 546 unicast feedback traffic is sent. One or more entities different 547 from the Distribution Source MAY implement the feedback target 548 functionality, and different RTP receivers MAY use different feedback 549 targets. 551 This document builds further on these concepts to reduce the 552 acquisition delay when an RTP receiver joins a multicast session at a 553 random point in time by introducing the concept of the Burst Source 554 and new RTCP feedback messages. The Burst Source has a cache where 555 the most recent packets from the primary multicast RTP session are 556 continuously stored. When an RTP receiver wants to receive a primary 557 multicast stream, it can first request a unicast burst from the Burst 558 Source before it joins the SSM session. In this burst, the packets 559 are formatted as RTP retransmission packets [RFC4588] and carry 560 Reference Information. This information allows the RTP receiver to 561 start usefully consuming the RTP packets sent in the primary 562 multicast RTP session. 564 Using an accelerated bitrate (as compared to the nominal bitrate of 565 the primary multicast stream) for the unicast burst implies that at a 566 certain point in time, the payload transmitted in the unicast burst 567 is going to be the same as the payload in the associated multicast 568 stream, i.e., the unicast burst will catch up with the primary 569 multicast stream. At this point, the RTP receiver no longer needs to 570 receive the unicast burst and can join the SSM session. This method 571 is referred to as the Rapid Acquisition of Multicast Sessions (RAMS). 573 This document defines extensions to [RFC4585] for an RTP receiver to 574 request a unicast burst as well as for additional control messaging 575 that can be leveraged during the acquisition process. 577 6.2. Message Flows 579 Figure 2 shows the main entities involved in rapid acquisition and 580 the message flows. They are 581 o Multicast Source 583 o Feedback Target (FT) 585 o Burst/Retransmission Source (BRS) 587 o RTP Receiver (RTP_Rx) 589 ----------- -------------- 590 | |------------------------------------>| | 591 | |.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.->| | 592 | | | | 593 | Multicast | ---------------- | | 594 | Source | | Retransmission | | | 595 | |-------->| Server (RS) | | | 596 | |.-.-.-.->| | | | 597 | | | ------------ | | | 598 ----------- | | Feedback | |<.=.=.=.=.| | 599 | | Target (FT)| |<~~~~~~~~~| RTP Receiver | 600 PRIMARY MULTICAST | ------------ | | (RTP_Rx) | 601 RTP SESSION with | | | | 602 UNICAST FEEDBACK | | | | 603 | | | | 604 - - - - - - - - - - - |- - - - - - - - |- - - - - |- - - - - - - |- - 605 | | | | 606 UNICAST BURST | ------------ | | | 607 (or RETRANSMISSION) | | Burst and | |<~~~~~~~~>| | 608 RTP SESSION | | Retrans. | |.........>| | 609 | |Source (BRS)| |<.=.=.=.=>| | 610 | ------------ | | | 611 | | | | 612 ---------------- -------------- 614 -------> Multicast RTP Flow 615 .-.-.-.> Multicast RTCP Flow 616 .=.=.=.> Unicast RTCP Reports 617 ~~~~~~~> Unicast RTCP Feedback Messages 618 .......> Unicast RTP Flow 620 Figure 2: Flow diagram for unicast-based rapid acquisition 622 The feedback target (FT) is the entity as defined in [RFC5760], to 623 which the RTP_Rx sends its RTCP feedback messages indicating packet 624 loss by means of an RTCP NACK message or indicating RTP_Rx's desire 625 to rapidly acquire the primary multicast RTP session by means of an 626 RTCP feedback message defined in this document. While the Burst/ 627 Retransmission Source (BRS) is responsible for responding to these 628 messages and for further RTCP interaction with the RTP_Rx in the case 629 of a rapid acquisition process, it is assumed in the remainder of the 630 document that these two logical entities (FT and BRS) are combined in 631 a single physical entity and they share state. In the remainder of 632 the text, the term Retransmission Server (RS) is used whenever 633 appropriate, to refer to this single physical entity. 635 The FT is involved in the primary multicast RTP session and receives 636 unicast feedback for that session as in [RFC5760]. The BRS is 637 involved in the unicast burst (or retransmission) RTP session and 638 transmits the unicast burst and retransmission packets formatted as 639 RTP retransmission packets [RFC4588] in a single separate unicast RTP 640 session to each RTP_Rx. In the unicast burst RTP session, as in any 641 other RTP session, the BRS and RTP_Rx regularly send the periodic 642 sender and receiver reports, respectively. 644 The unicast burst is started by an RTCP feedback message that is 645 defined in this document based on the common packet format provided 646 in [RFC4585]. An RTP retransmission is triggered by an RTCP NACK 647 message defined in [RFC4585]. Both of these messages are sent to the 648 FT of the primary multicast RTP session, and can start the unicast 649 burst/retransmission RTP session. 651 In the extended RTP profile for RTCP-based feedback (RTP/AVPF), there 652 are certain rules that apply to scheduling of both of these messages 653 sent to the FT in the primary multicast RTP session, and these are 654 detailed in Section 3.5 of [RFC4585]. One of the rules states that 655 in a multi-party session such as the SSM sessions we are considering 656 in this specification, an RTP_Rx cannot send an RTCP feedback message 657 for a minimum of one second period after joining the session (i.e., 658 Tmin=1.0 second). While this rule has the goal of avoiding problems 659 associated with flash crowds in typical multi-party sessions, it 660 defeats the purpose of rapid acquisition. Furthermore, when RTP 661 receivers delay their messages requesting a burst by a deterministic 662 or even a random amount, it still does not make a difference since 663 such messages are not related and their timings are independent from 664 each other. Thus, in this specification we initialize Tmin to zero 665 and allow the RTP receivers to send a burst request message right at 666 the beginning. For the subsequent messages (e.g., updated requests) 667 during rapid acquisition, the timing rules of [RFC4585] still apply. 669 Figure 3 depicts an example of messaging flow for rapid acquisition. 670 The RTCP feedback messages are explained below. The optional 671 messages are indicated in parentheses and they might or might not be 672 present during rapid acquisition. In a scenario where rapid 673 acquisition is performed by a feedback target co-located with the 674 media sender, the same method (with the identical message flows) 675 still applies. 677 ------------------------- 678 | Retransmission Server | 679 ----------- | ------ ------------ | -------- ------------ 680 | Multicast | | | FT | | Burst/Ret. | | | | | RTP | 681 | Source | | | | | Source | | | Router | | Receiver | 682 | | | ------ ------------ | | | | (RTP_Rx) | 683 ----------- | | | | -------- ------------ 684 | ------------------------- | | 685 | | | | | 686 |-- RTP Multicast ---------->--------------->| | 687 |-. RTCP Multicast -.-.-.-.->-.-.-.-.-.-.-.->| | 688 | | | | | 689 | | |********************************| 690 | | |* PORT MAPPING SETUP *| 691 | | |********************************| 692 | | | | | 693 | |<~~~~~~~~~~~~~~~~~~~~~~~~~ RTCP RAMS-R ~~~| 694 | | | | | 695 | | |********************************| 696 | | |* UNICAST SESSION ESTABLISHED *| 697 | | |********************************| 698 | | | | | 699 | | |~~~ RTCP RAMS-I ~~~~~~~~~~~~~~~>| 700 | | | | | 701 | | |... Unicast RTP Burst .........>| 702 | | | | | 703 | |<~~~~~~~~~~~~~~~~~~~~~~~~ (RTCP RAMS-R) ~~| 704 | | | | | 705 | | |~~ (RTCP RAMS-I) ~~~~~~~~~~~~~~>| 706 | | | | | 707 | | | | | 708 | | | |<= SFGMP Join ==| 709 | | | | | 710 |-- RTP Multicast ------------------------------------------->| 711 |-. RTCP Multicast -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.>| 712 | | | | | 713 | | | | | 714 | | |<~~~~~~~~~~~~~~~ RTCP RAMS-T ~~~| 715 | | | | | 716 : : : : : 717 | | |<.=.= Unicast RTCP Reports .=.=>| 718 : : : (for the unicast session) : 719 | | | | | 721 -------> Multicast RTP Flow 722 .-.-.-.> Multicast RTCP Flow 723 .=.=.=.> Unicast RTCP Reports 724 ~~~~~~~> Unicast RTCP Feedback Messages 725 =======> SFGMP Messages 726 .......> Unicast RTP Flow 728 Figure 3: Message flows for unicast-based rapid acquisition 730 This document defines the expected behaviors of the RS and RTP_Rx. 731 It is instructive to consider independently operating implementations 732 on the RS and RTP_Rx that request the burst, describe the burst, 733 start the burst, join the multicast session and stop the burst. 734 These implementations send messages to each other, but provisions are 735 needed for the cases where the control messages get lost, or re- 736 ordered, or are not being delivered to their destinations. 738 The following steps describe rapid acquisition in detail: 740 1. Port Mapping Setup: For the primary multicast RTP session, the 741 RTP and RTCP destination ports are declaratively specified 742 (Refer to Section 8 for examples in SDP). However, the RTP_Rx 743 needs to choose its RTP and RTCP receive ports for the unicast 744 burst RTP session. Since this unicast session is established 745 after the RTP_Rx has sent a RAMS-Request (RAMS-R) message as 746 unicast feedback in the primary multicast RTP session, the 747 RTP_Rx MUST first setup the port mappings between the unicast 748 and multicast sessions and send this mapping information to the 749 FT along with the RAMS-R message so that the BRS knows how to 750 communicate with the RTP_Rx. 752 The details of this setup procedure are explained in 753 [I-D.ietf-avt-ports-for-ucast-mcast-rtp]. Other NAT-related 754 issues are left to Section 9 to keep the present discussion 755 focused on the RAMS message flows. 757 2. Request: the RTP_Rx sends a rapid acquisition request (RAMS-R) 758 for the primary multicast RTP session to the unicast feedback 759 target of that session. The request contains the SSRC 760 identifier of the RTP_Rx (aka SSRC of packet sender) and can 761 contain the media sender SSRC identifier(s) of the primary 762 multicast stream(s) of interest (aka SSRC of media source). The 763 RAMS-R message can contain parameters that constrain the burst, 764 such as the buffer and bandwidth limits. 766 Before joining the SSM session, the RTP_Rx learns the addresses 767 for the multicast source, group and RS by out-of-band means. If 768 the RTP_Rx desires to rapidly acquire only a subset of the 769 primary multicast streams available in the primary multicast RTP 770 session, the RTP_Rx MUST also acquire the SSRC identifiers for 771 the desired RTP streams out-of-band. Based on this information, 772 the RTP_Rx populates the desired SSRC(s) in the RAMS-R message. 774 When the FT successfully receives the RAMS-R message, the BRS 775 responds to it by accepting or rejecting the request. 776 Immediately before the BRS sends any RTP or RTCP packet(s) 777 described below, it establishes the unicast burst RTP session. 779 3. Response: The BRS sends RAMS-Information (RAMS-I) message(s) to 780 the RTP_Rx to convey the status for the burst(s) requested by 781 the RTP_Rx. 783 If the primary multicast RTP session associated with the FT_Ap 784 (a specific feedback target running on a particular address and 785 port) on which the RAMS-R message was received contains only a 786 single primary multicast stream, the BRS SHALL always use the 787 SSRC of the RTP stream associated with the FT_Ap in the RAMS-I 788 message(s) regardless of the media sender SSRC requested in the 789 RAMS-R message. In such cases the 'ssrc' attribute MAY be 790 omitted from the media description. If the requested SSRC and 791 the actual media sender SSRC do not match, the BRS MUST 792 explicitly populate the correct media sender SSRC in the initial 793 RAMS-I message (See Section 7.3). 795 The FT_Ap could also be associated with an RTP session that 796 carries two or more primary multicast streams. If the RTP_Rx 797 wants to issue a collective request to receive the whole primary 798 multicast RTP session, it does not need the 'ssrc' attributes to 799 be described in the media description. 801 If the FT_Ap is associated with two or more RTP sessions, 802 RTP_Rx's request will be ambiguous. To avoid any ambiguity, 803 each FT_Ap MUST be only associated with a single RTP session. 805 If the RTP_Rx is willing to rapidly acquire only a subset of the 806 primary multicast streams, the RTP_Rx MUST list all the media 807 sender SSRC(s) denoting the stream(s) it wishes to acquire in 808 the RAMS-R message. Upon receiving such a message, the BRS MAY 809 accept the request for all or a subset of the media sender 810 SSRC(s) that matched the RTP stream(s) it serves. The BRS MUST 811 reject all other requests with an appropriate response code. 813 * Reject Responses: The BRS MUST take into account any 814 limitations that may have been specified by the RTP_Rx in the 815 RAMS-R message when making a decision regarding the request. 816 If the RTP_Rx has requested to acquire the whole primary 817 multicast RTP session but the BRS cannot provide a rapid 818 acquisition service for any of the primary multicast streams, 819 the BRS MUST reject the request via a single RAMS-I message 820 with a collective reject response code, which is defined as 821 510 in Section 11.6, and whose media sender SSRC field is set 822 to one of SSRCs served by this FT_Ap. Upon receiving this 823 RAMS-I message, the RTP_Rx abandons the rapid acquisition 824 attempt and can immediately join the multicast session by 825 sending an SFGMP Join message towards its upstream multicast 826 router. 828 In all other cases, the BRS MUST send a separate RAMS-I 829 message with the appropriate 5xx-level response code (as 830 defined in Section 11.6) for each primary multicast stream 831 that has been requested by the RTP_Rx but cannot be served by 832 the BRS. There could be multiple reasons why the BRS has 833 rejected the request, however, the BRS chooses the most 834 appropriate response code to inform the RTP_Rx. 836 Upon receiving a reject response indicating a transient 837 problem such as insufficient BRS or network resources, if the 838 RTP_Rx wants to retry sending the same request, the RTP_Rx 839 MUST follow the RTCP timer rules of [RFC4585] to allow the 840 transient problems go away. However, if the reject response 841 indicates a non-transient problem (such as the ones reported 842 by response codes 504, 505 and 506), the RTP_Rx MUST NOT 843 attempt a retry. Different response codes have different 844 scopes. Refer to Section 7.3.1 for details. 846 The BRS can employ a policing mechanism against the broken 847 RTP_Rx implementations that are not following these rules. 848 See Section 10 for details. 850 * Accept Responses: The BRS MUST send at least one separate 851 RAMS-I message with the appropriate response code (either 852 zero indicating a private response or response code 200 853 indicating success as listed in Section 11.6) for each 854 primary multicast stream that has been requested by the 855 RTP_Rx and will be served by the BRS. Such RAMS-I messages 856 comprise fields that can be used to describe the individual 857 unicast burst streams. When there is a RAMS-R request for 858 multiple primary multicast streams, the BRS MUST include all 859 the individual RAMS-I messages corresponding to that RAMS-R 860 request in the same compound RTCP packet if these messages 861 fit in the same packet. Note that if the BRS is sending only 862 the preamble information but not the whole unicast burst 863 stream, it will not accept the request, but will send a 864 response code 511 instead as defined in Section 11.6. 866 The RAMS-I message carries the RTP sequence number of the 867 first packet transmitted in the respective RTP stream to 868 allow the RTP_Rx to detect any missing initial packet(s). 869 When the BRS accepts a request for a primary multicast 870 stream, this field MUST always be populated in the RAMS-I 871 message(s) sent for this particular primary multicast stream. 872 It is RECOMMENDED that the BRS sends a RAMS-I message at the 873 start of the burst so that the RTP_Rx can quickly detect any 874 missing initial packet(s). 876 It is possible that the RAMS-I message for a primary multicast 877 stream can get delayed or lost, and the RTP_Rx can start 878 receiving RTP packets before receiving a RAMS-I message. An 879 RTP_Rx implementation MUST NOT assume it will quickly receive 880 the initial RAMS-I message. For redundancy purposes, it is 881 RECOMMENDED that the BRS repeats the RAMS-I messages multiple 882 times as long as it follows the RTCP timer rules defined in 883 [RFC4585]. 885 4. Unicast Burst: For the primary multicast stream(s) for which 886 the request is accepted, the BRS starts sending the unicast 887 burst(s) that comprises one or more RTP retransmission packets 888 sent in the unicast burst RTP session. In addition, in some 889 applications the BRS can send preamble information data to the 890 RTP_Rx in addition to the requested burst to prime the media 891 decoder(s). However, for the BRS to send the preamble 892 information in a particular format, explicit signaling from the 893 RTP_Rx is required. In other words, the BRS MUST NOT send 894 preamble information in a particular format unless the RTP_Rx 895 has signaled support for that format in the RAMS-R message 896 through a public or private extension as defined in Section 7.1. 898 The format of this preamble data is RTP-payload specific and not 899 specified here. 901 5. Updated Request: The RTP_Rx MAY send an updated RAMS-R message 902 (as unicast feedback in the primary multicast RTP session) with 903 a different value for one or more fields of an earlier RAMS-R 904 message. The BRS MUST be able to detect whether a burst is 905 already planned for or being transmitted to this particular 906 RTP_Rx for this particular media sender SSRC. If there is an 907 existing burst planned for or being transmitted, the newly 908 arriving RAMS-R is an updated request; otherwise it is a new 909 request. It is also possible that the RTP_Rx has sent an 910 improperly formatted RAMS-R message or used an invalid value in 911 the RAMS-R message. If notified by the BRS using a 4xx-level 912 response code (as defined in Section 11.6) and only after 913 following the timing rules of [RFC4585], the RTP_Rx MAY re-send 914 its corrected request. 916 The BRS determines the identity of the requesting RTP_Rx by 917 looking at its canonical name identifier (CNAME item in the SDES 918 source description). Thus, the RTP_Rx MUST choose a method that 919 ensures it uses a unique CNAME identifier. Different such ways 920 are provided in [I-D.ietf-avt-rtp-cnames]. In addition to one 921 or more fields with updated values, an updated RAMS-R message 922 may also include the fields whose values did not change. 924 Upon receiving an updated request, the BRS can use the updated 925 values for sending/shaping the burst, or refine the values and 926 use the refined values for sending/shaping the burst. 927 Subsequently, the BRS MAY send an updated RAMS-I message in the 928 unicast burst RTP session to indicate the changes it made. 930 It is an implementation-dependent decision for an RTP_RX whether 931 and when to send an updated request. However, note that the 932 updated request messages can get delayed and arrive at the BRS 933 after the initial unicast burst was completed. In this case, 934 the updated request message can trigger a new unicast burst and 935 by then if the RTP_Rx has already started receiving multicast 936 data, a congestion is likely to occur. In this case, the RTP_Rx 937 can detect this only after a delay and then it can try to 938 terminate the new burst. However, in the mean time, the RTP_Rx 939 can experience packet loss or other problems. This and other 940 similar corner cases SHOULD be carefully examined if updated 941 requests are to be used. 943 6. Updated Response: The BRS can send more than one RAMS-I 944 messages in the unicast burst RTP session, e.g., to update the 945 value of one or more fields in an earlier RAMS-I message. The 946 updated RAMS-I messages might or might not be a direct response 947 to a RAMS-R message. The BRS can also send updated RAMS-I 948 messages to signal the RTP_Rx in real time to join the SSM 949 session, when the BRS had already sent an initial RAMS-I 950 message, e.g., at the start of the burst. The RTP_Rx depends on 951 the BRS to learn the join time, which can be conveyed by the 952 first RAMS-I message, or can be sent/revised in a later RAMS-I 953 message. If the BRS is not capable of determining the join time 954 in the initial RAMS-I message, the BRS MUST send another RAMS-I 955 message (with the join time information) later. 957 7. Multicast Join Signaling: The RAMS-I message allows the BRS to 958 signal explicitly when the RTP_Rx needs to send the SFGMP Join 959 message. The RTP_Rx SHOULD use this information from the most 960 recent RAMS-I message unless it has more accurate information. 962 If the request is accepted, this information MUST be conveyed in 963 at least one RAMS-I message and its value MAY be updated by 964 subsequent RAMS-I messages. 966 There can be missing packets if the RTP_Rx joins the multicast 967 session too early or too late. For example, if the RTP_Rx 968 starts receiving the primary multicast stream while it is still 969 receiving the unicast burst at a high excess bitrate, this can 970 result in an increased risk of packet loss. Or, if the RTP_Rx 971 joins the multicast session some time after the unicast burst is 972 finished, there can be a gap between the burst and multicast 973 data (a number of RTP packets might be missing). In both cases, 974 the RTP_Rx can issue retransmission requests (via RTCP NACK 975 messages sent as unicast feedback in the primary multicast RTP 976 session) [RFC4585] to the FT entity of the RS to fill the gap. 977 The BRS might or might not respond to such requests. When it 978 responds and the response causes significant changes in one or 979 more values reported earlier to the RTP_Rx, an updated RAMS-I 980 SHOULD be sent to the RTP_Rx. 982 8. Multicast Receive: After the join, the RTP_Rx starts receiving 983 the primary multicast stream(s). 985 9. Terminate: The BRS can know when it needs to ultimately stop 986 the unicast burst based on its parameters. However, the RTP_Rx 987 may need to ask the BRS to terminate the burst prematurely or at 988 a specific sequence number. For this purpose, the RTP_Rx uses 989 the RAMS-Termination (RAMS-T) message sent as RTCP feedback in 990 the unicast burst RTP session. A separate RAMS-T message is 991 sent for each primary multicast stream served by the BRS unless 992 an RTCP BYE message has been sent in the unicast burst RTP 993 session as described in Step 10. For the burst requests that 994 were rejected by the BRS, there is no need to send a RAMS-T 995 message. 997 If the RTP_Rx wants to terminate a burst prematurely, it MUST 998 send a RAMS-T message for the SSRC of the primary multicast 999 stream it wishes to terminate. This message is sent in the 1000 unicast burst RTP session. Upon receiving this message, the BRS 1001 MUST terminate the unicast burst. If the RTP_Rx requested to 1002 acquire the entire primary multicast RTP session but wants to 1003 terminate this request before it learns the individual media 1004 sender SSRC(s) via RAMS-I message(s) or RTP packets, the RTP_Rx 1005 cannot use RAMS-T message(s) and thus MUST send an RTCP BYE 1006 message in the unicast burst RTP session to terminate the 1007 request. 1009 Otherwise, the default behavior for the RTP_Rx is to send a 1010 RAMS-T message in the unicast burst RTP session immediately 1011 after it joins the multicast session and has started receiving 1012 multicast packets. In that case, the RTP_Rx MUST send a RAMS-T 1013 message with the sequence number of the first RTP packet 1014 received in the primary multicast stream. Then, the BRS MUST 1015 terminate the respective burst after it sends the unicast burst 1016 packet whose Original Sequence Number (OSN) field in the RTP 1017 retransmission payload header matches this number minus one. If 1018 the BRS has already sent that unicast burst packet when the 1019 RAMS-T message arrives, the BRS MUST terminate the respective 1020 burst immediately. 1022 If an RTCP BYE message has not been issued yet as described in 1023 Step 10, the RTP_Rx MUST send at least one RAMS-T message for 1024 each primary multicast stream served by the BRS. The RAMS-T 1025 message(s) MUST be sent to the BRS in the unicast burst RTP 1026 session. Against the possibility of a message loss, it is 1027 RECOMMENDED that the RTP_Rx repeats the RAMS-T messages multiple 1028 times as long as it follows the RTCP timer rules defined in 1029 [RFC4585]. 1031 The binding between RAMS-T and ongoing bursts is achieved 1032 through RTP_Rx's CNAME identifier, and packet sender and media 1033 sender SSRCs. Choosing a globally unique CNAME makes sure that 1034 the RAMS-T messages are processed correctly. 1036 10. Terminate with RTCP BYE: When the RTP_Rx is receiving one or 1037 more burst streams, if the RTP_Rx becomes no longer interested 1038 in acquiring any of the primary multicast streams, the RTP_Rx 1039 SHALL issue an RTCP BYE message for the unicast burst RTP 1040 session and another RTCP BYE message for the primary multicast 1041 RTP session. These RTCP BYE messages are sent to the BRS and FT 1042 logical entities, respectively. 1044 Upon receiving an RTCP BYE message, the BRS MUST terminate the 1045 rapid acquisition operation, and cease transmitting any further 1046 burst packets and retransmission packets. If support for 1047 [RFC5506] has been signaled, the RTCP BYE message MAY be sent in 1048 a reduced-size RTCP packet. Otherwise, Section 6.1 of [RFC3550] 1049 mandates the RTCP BYE message always to be sent with a sender or 1050 receiver report in a compound RTCP packet. If no data has been 1051 received, an empty receiver report MUST be still included. With 1052 the information contained in the receiver report, the RS can 1053 figure out how many duplicate RTP packets have been delivered to 1054 the RTP_Rx (Note that this will be an upper-bound estimate as 1055 one or more packets might have been lost during the burst 1056 transmission). The impact of duplicate packets and measures 1057 that can be taken to minimize the impact of receiving duplicate 1058 packets will be addressed in Section 6.4. 1060 Since an RTCP BYE message issued for the unicast burst RTP 1061 session terminates that session and ceases transmitting any 1062 further packets in that session, there is no need for sending 1063 explicit RAMS-T messages, which would only terminate their 1064 respective bursts. 1066 For the purpose of gathering detailed information about RTP_Rx's 1067 rapid acquisition experience, [I-D.ietf-avt-multicast-acq-rtcp-xr] 1068 defines an RTCP Extended Report (XR) Block. This report is designed 1069 to be payload-independent, thus, it can be used by any multicast 1070 application that supports rapid acquisition. Support for this XR 1071 report is, however, OPTIONAL. 1073 6.3. Synchronization of Primary Multicast Streams 1075 When an RTP_RX acquires multiple primary multicast streams, it might 1076 need to synchronize them for playout. This synchronization is 1077 achieved by the help of the RTCP sender reports [RFC3550]. If the 1078 playout will start before the RTP_Rx has joined the multicast 1079 session, the RTP_Rx needs to receive the information reflecting the 1080 synchronization among the primary multicast streams early enough so 1081 that it can play out the media in a synchronized fashion. 1083 The suggested approach is to use the RTP header extension mechanism 1084 [RFC5285] and convey the synchronization information in a header 1085 extension as defined in [I-D.ietf-avt-rapid-rtp-sync]. Per [RFC4588] 1086 "if the original RTP header carried an RTP header extension, the 1087 retransmission packet SHOULD carry the same header extension." Thus, 1088 as long as the multicast source emits a header extension with the 1089 synchronization information frequently enough, there is no additional 1090 task that needs to be carried out by the BRS. The synchronization 1091 information will be sent to the RTP_Rx along with the burst packets. 1092 The frequent header extensions sent in the primary multicast RTP 1093 sessions also allow rapid synchronization of the RTP streams for the 1094 RTP receivers that do not support RAMS or that directly join the 1095 multicast session without running RAMS. Thus, in RAMS applications, 1096 it is RECOMMENDED that the multicast sources frequently send 1097 synchronization information by using header extensions following the 1098 rules presented in [I-D.ietf-avt-rapid-rtp-sync]. The regular sender 1099 reports are still sent in the unicast session by following the rules 1100 of [RFC3550]. 1102 6.4. Burst Shaping and Congestion Control in RAMS 1104 This section provides informative guidelines about how the BRS can 1105 shape the transmission of the unicast burst and how congestion can be 1106 dealt within the RAMS process. When the RTP_Rx detects that the 1107 unicast burst is causing severe congestion, it can prefer to send a 1108 RAMS-T message immediately to stop the unicast burst. 1110 A higher bitrate for the unicast burst naturally conveys the 1111 Reference Information and media content to the RTP_Rx faster. This 1112 way, the RTP_Rx can start consuming the data sooner, which results in 1113 a faster acquisition. A higher bitrate also represents a better 1114 utilization of the BRS resources. As the burst may continue until it 1115 catches up with the primary multicast stream, the higher the bursting 1116 bitrate, the less data the BRS needs to transmit. However, a higher 1117 bitrate for the burst also increases the chances for congestion- 1118 caused packet loss. Thus, as discussed in Section 5, there has to be 1119 an upper bound on the bandwidth used by the burst. 1121 When the BRS transmits the unicast burst, it is expected to take into 1122 account all available information to prevent any packet loss that 1123 might take place during the bursting as a result of buffer overflow 1124 on the path between the RS and RTP_Rx and at the RTP_Rx itself. The 1125 bursting bitrate can be determined by taking into account the 1126 following information, when available: 1128 a. Information obtained via the RAMS-R message, such as Max RAMS 1129 Buffer Fill Requirement and/or Max Receive Bitrate (See 1130 Section 7.2). 1132 b. Information obtained via RTCP receiver reports provided by the 1133 RTP_Rx in the retransmission session, allowing in-session bitrate 1134 adaptations for the burst. When these receiver reports indicate 1135 packet loss, this can indicate a certain congestion state in the 1136 path from the RS to the RTP_Rx. 1138 c. Information obtained via RTCP NACKs provided by the RTP_Rx in the 1139 primary multicast RTP session, allowing in-session bitrate 1140 adaptations for the burst. Such RTCP NACKs are transmitted by 1141 the RTP_Rx in response to packet loss detection in the burst. 1142 NACKs can indicate a certain congestion state on the path from 1143 the RS to RTP_Rx. 1145 d. There can be other feedback received from the RTP_Rx, e.g., in 1146 the form of ECN-CE markings [I-D.ietf-avt-ecn-for-rtp] that can 1147 influence in-session bitrate adaptation. 1149 e. Information obtained via updated RAMS-R messages, allowing in- 1150 session bitrate adaptations, if supported by the BRS. 1152 f. Transport protocol-specific information. For example, when DCCP 1153 is used to transport the RTP burst, the ACKs from the DCCP client 1154 can be leveraged by the BRS / DCCP server for burst shaping and 1155 congestion control. 1157 g. Pre-configured settings for each RTP_Rx or a set of RTP_Rxs that 1158 indicate the upper-bound bursting bitrates for which no packet 1159 loss will occur as a result of congestion along the path of the 1160 RS to RTP_Rx. For example, in managed IPTV networks, where the 1161 bottleneck bandwidth along the end-to-end path is known and where 1162 the network between the RS and this link is provisioned and 1163 dimensioned to carry the burst streams, the bursting bitrate does 1164 not exceed the provisioned value. These settings can also be 1165 dynamically adapted using application-aware knowledge. 1167 The BRS chooses the initial burst bitrate as follows: 1169 o When using RAMS in environments as described in (g), the BRS MUST 1170 transmit the burst packets at an initial bitrate higher than the 1171 nominal bitrate, but within the engineered or reserved bandwidth 1172 limit. 1174 o When the BRS cannot determine a reliable bitrate value for the 1175 unicast burst (using a through g), it is desirable that the BRS 1176 chooses an appropriate initial bitrate not above the nominal 1177 bitrate and increases it gradually unless a congestion is 1178 detected. 1180 In both cases, during the burst transmission the BRS MUST 1181 continuously monitor for packet losses as a result of congestion by 1182 means of one or more of the mechanisms described in (b,c,d,e,f). 1183 When the BRS relies on RTCP receiver reports, sufficient bandwidth 1184 needs to be provided to RTP Rx for RTCP transmission in the unicast 1185 burst RTP session. To achieve a reasonable fast adaptation against 1186 congestion, it is recommended that the RTP_Rx sends a receiver report 1187 at least once every two RTTs between the RS and RTP_Rx. Although the 1188 specific heuristics and algorithms that deduce a congestion state and 1189 how subsequently the BRS acts are outside the scope of this 1190 specification, the following two methods are the best practices: 1192 o Upon detection of a significant amount of packet loss, which the 1193 BRS attributes to congestion, the BRS decreases the burst bitrate. 1194 The rate by which the BRS increases and decreases the bitrate for 1195 the burst can be determined by a TCP-friendly bitrate adaptation 1196 algorithm for RTP over UDP , or in the case of (f) by the 1197 congestion control algorithms defined in DCCP [RFC5762]. 1199 o If the congestion is persistent and the BRS has to reduce the 1200 burst bitrate to a point where the RTP Rx buffer might underrun or 1201 the burst will consume too many resources, the BRS terminates the 1202 burst and transmits a RAMS-I message to RTP Rx with the 1203 appropriate response code. It is then up to RTP Rx to decide when 1204 to join the multicast session. 1206 Even though there is no congestion experienced during the burst, 1207 congestion may anyway arise near the end of the burst as the RTP_Rx 1208 eventually needs to join the multicast session. During this brief 1209 period both the burst packets and the multicast packets can be 1210 simultaneously received by the RTP_Rx, thus enhancing the risk of 1211 congestion. 1213 Since the BRS signals the RTP_Rx when the BRS expects the RTP_Rx to 1214 send the SFGMP Join message, the BRS can have a rough estimate of 1215 when the RTP_Rx will start receiving multicast packets in the SSM 1216 session. The BRS can keep on sending burst packets but reduces the 1217 bitrate accordingly at the appropriate instant by taking the bitrate 1218 of the whole SSM session into account. If the BRS ceases 1219 transmitting the burst packets before the burst catches up, any gap 1220 resulting from this imperfect switch-over by the RTP_Rx can be later 1221 repaired by requesting retransmissions for the missing packets from 1222 the RS. The retransmissions can be shaped by the BRS to make sure 1223 that they do not cause collateral loss in the primary multicast RTP 1224 session and the unicast burst RTP session. 1226 6.5. Failure Cases 1228 In the following, we examine the implications of losing the RAMS-R, 1229 RAMS-I or RAMS-T messages and other failure cases. 1231 When the RTP_Rx sends a RAMS-R message to initiate a rapid 1232 acquisition but the message gets lost and the FT does not receive it, 1233 the RTP_Rx will get neither a RAMS-I message, nor a unicast burst. 1234 In this case, the RTP_Rx MAY resend the request when it is eligible 1235 to do so based on the RTCP timer rules defined in [RFC4585]. Or, 1236 after a reasonable amount of time, the RTP_Rx can time out (based on 1237 the previous observed response times) and immediately join the SSM 1238 session. 1240 In the case the RTP_Rx starts receiving a unicast burst but it does 1241 not receive a corresponding RAMS-I message within a reasonable amount 1242 of time, the RTP_Rx can either discard the burst data or decide not 1243 to interrupt the unicast burst, and be prepared to join the SSM 1244 session at an appropriate time it determines or as indicated in a 1245 subsequent RAMS-I message (if available). If the network is subject 1246 to packet loss, it is RECOMMENDED that the BRS repeats the RAMS-I 1247 messages multiple times based on the RTCP timer rules defined in 1248 [RFC4585]. 1250 In the failure cases where the RAMS-R message is lost and the RTP_Rx 1251 gives up, or the RAMS-I message is lost, the RTP_Rx MUST still 1252 terminate the burst(s) it requested by following the rules described 1253 in Section 6.2. 1255 In the case a RAMS-T message sent by the RTP_Rx does not reach its 1256 destination, the BRS can continue sending burst packets even though 1257 the RTP_Rx no longer needs them. If an RTP_Rx is receiving burst 1258 packets it no longer needs after sending a RAMS-T message, it is 1259 RECOMMENDED that the RTP_Rx repeats the RAMS-T message multiple times 1260 based on the RTCP timer rules defined in [RFC4585]. The BRS MUST be 1261 provisioned to terminate the burst when it can no longer send the 1262 burst packets faster than it receives the primary multicast stream 1263 packets. 1265 Section 6.3.5 of [RFC3550] explains the rules pertaining to timing 1266 out an SSRC. When the BRS accepts to serve the requested burst(s) 1267 and establishes the retransmission session, the BRS needs to check 1268 the liveness of the RTP_Rx via the RTCP messages and reports the 1269 RTP_Rx sends. The default rules explained in [RFC3550] apply in RAMS 1270 as well. 1272 7. Encoding of the Signaling Protocol in RTCP 1274 This section defines the formats of the RTCP transport-layer feedback 1275 messages that are exchanged between the retransmission server (RS) 1276 and RTP receiver (RTP_Rx) during rapid acquisition. These messages 1277 are referred to as the RAMS Messages. They are payload-independent 1278 and MUST be used by all RTP-based multicast applications that support 1279 rapid acquisition regardless of the payload they carry. 1281 Payload-specific feedback messages are not defined in this document. 1282 However, further optional payload-independent and payload-specific 1283 information can be included in the exchange. 1285 The common packet format for the RTCP feedback messages is defined in 1286 Section 6.1 of [RFC4585] and is also sketched in Figure 4. 1288 0 1 2 3 1289 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1290 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1291 |V=2|P| FMT | PT | length | 1292 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1293 | SSRC of packet sender | 1294 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1295 | SSRC of media source | 1296 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1297 : Feedback Control Information (FCI) : 1298 : : 1300 Figure 4: The common packet format for the RTCP feedback messages 1302 Each feedback message has a fixed-length field for version, padding, 1303 feedback message type (FMT), packet type (PT), length, SSRC of packet 1304 sender, SSRC of media source as well as a variable-length field for 1305 feedback control information (FCI). 1307 In the RAMS messages, the PT field is set to RTPFB (205) and the FMT 1308 field is set to RAMS (6). Individual RAMS messages are identified by 1309 a sub-field called Sub Feedback Message Type (SFMT). Any Reserved 1310 field SHALL be set to zero and ignored. 1312 Depending on the specific scenario and timeliness/importance of a 1313 RAMS message, it can be desirable to send it in a reduced-size RTCP 1314 packet [RFC5506]. However, unless support for [RFC5506] has been 1315 signaled, compound RTCP packets MUST be used by following [RFC3550] 1316 rules. 1318 Following the rules specified in [RFC3550], all integer fields in the 1319 messages defined below are carried in network-byte order, that is, 1320 most significant byte (octet) first, also known as big-endian. 1321 Unless otherwise stated, numeric constants are in decimal (base 10). 1323 7.1. Extensions 1325 To improve the functionality of the RAMS method in certain 1326 applications, it can be desirable to define new fields in the RAMS 1327 Request, Information and Termination messages. Such fields MUST be 1328 encoded as Type-Length-Value (TLV) elements as described below and 1329 sketched in Figure 5: 1331 o Type: A single-octet identifier that defines the type of the 1332 parameter represented in this TLV element. 1334 o Length: A two-octet field that indicates the length (in octets) 1335 of the TLV element excluding the Type and Length fields, and the 1336 8-bit Reserved field between them. This length does not include 1337 any padding that is required for alignment. 1339 o Value: Variable-size set of octets that contains the specific 1340 value for the parameter. 1342 In the extensions, the Reserved field SHALL be set to zero and 1343 ignored. If a TLV element does not fall on a 32-bit boundary, the 1344 last word MUST be padded to the boundary using further bits set to 1345 zero. 1347 An RTP_Rx or BRS MAY include vendor-neutral and private extensions in 1348 any RAMS message. The RTP_Rx or BRS MUST place such extensions after 1349 the mandatory fields and mandatory TLV elements (if any), and MAY 1350 place such extensions in any order. The RTP_Rx or BRS MUST NOT 1351 include multiple TLV elements with the same Type value in a RAMS 1352 message. 1354 The support for extensions (unless specified otherwise) is OPTIONAL. 1355 An RTP_Rx or BRS receiving a vendor-neutral or private extension that 1356 it does not understand MUST ignore that extension. 1358 0 1 2 3 1359 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1360 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1361 | Type | Reserved | Length | 1362 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1363 : Value : 1364 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1366 Figure 5: Structure of a TLV element 1368 7.1.1. Vendor-Neutral Extensions 1370 If the goal in defining new TLV elements is to extend the 1371 functionality in a vendor-neutral manner, they MUST be registered 1372 with IANA through the guidelines provided in Section 11.5. 1374 The current document defines several vendor-neutral extensions in the 1375 subsequent sections. 1377 7.1.2. Private Extensions 1379 It is desirable to allow vendors to use private extensions in a TLV 1380 format. For interoperability, such extensions must not collide with 1381 each other. 1383 A certain range of TLV Types (between - and including - 128 and 254 ) 1384 is reserved for private extensions (Refer to Section 11.5). IANA 1385 management for these extensions is unnecessary and they are the 1386 responsibility of individual vendors. 1388 The structure that MUST be used for the private extensions is 1389 depicted in Figure 6. Here, the enterprise numbers are used from 1390 http://www.iana.org/assignments/enterprise-numbers. This will ensure 1391 the uniqueness of the private extensions and avoid any collision. 1393 0 1 2 3 1394 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1395 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1396 | Type | Reserved | Length | 1397 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1398 | Enterprise Number | 1399 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1400 : Value : 1401 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1403 Figure 6: Structure of a private extension 1405 7.2. RAMS Request 1407 The RAMS Request (RAMS-R) message is identified by SFMT=1. This 1408 message is sent as unicast feedback in the primary multicast RTP 1409 session by the RTP_Rx to request rapid acquisition of a primary 1410 multicast RTP session, or one or more primary multicast streams 1411 belonging to the same primary multicast RTP session. In the RAMS-R 1412 message, the RTP_Rx MUST set both the packet sender SSRC and media 1413 sender SSRC fields to its own SSRC since the media sender SSRC may 1414 not be known. The RTP_Rx MUST provide explicit signaling as 1415 described below to request stream(s). This minimizes the chances of 1416 accidentally requesting a wrong primary multicast stream. 1418 The FCI field MUST contain only one RAMS Request. The FCI field has 1419 the structure depicted in Figure 7. 1421 The semantics of the RAMS-R message is independent of the payload 1422 type carried in the primary multicast RTP session. 1424 0 1 2 3 1425 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1426 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1427 | SFMT=1 | Reserved | 1428 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1429 : Requested Media Sender SSRC(s) : 1430 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1431 : Optional TLV-encoded Fields (and Padding, if needed) : 1432 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1434 Figure 7: FCI field syntax for the RAMS Request message 1436 o Requested Media Sender SSRC(s): Mandatory TLV element that lists 1437 the media sender SSRC(s) requested by the RTP_Rx. The BRS MUST 1438 ignore the media sender SSRC specified in the header of the RAMS-R 1439 message. 1441 If the Length field is set to zero (i.e., no media sender SSRC is 1442 listed), it means that the RTP_Rx is requesting to rapidly acquire 1443 the entire primary multicast RTP session. Otherwise, the RTP_Rx 1444 lists the individual media sender SSRCs in this TLV element and 1445 sets the Length field of the TLV element to 4*n, where n is the 1446 number of SSRC entries. 1448 Type: 1 1450 o Min RAMS Buffer Fill Requirement (32 bits): Optional TLV element 1451 that denotes the minimum milliseconds of data that the RTP_Rx 1452 desires to have in its buffer before allowing the data to be 1453 consumed by the application. 1455 The RTP_Rx can have knowledge of its buffering requirements. 1456 These requirements can be application and/or device specific. For 1457 instance, the RTP_Rx might need to have a certain amount of data 1458 in its application buffer to handle transmission jitter and/or to 1459 be able to support error-control methods. If the BRS is told the 1460 minimum buffering requirement of the receiver, the BRS can tailor 1461 the burst(s) more precisely, e.g., by choosing an appropriate 1462 starting point. The methods used by the RTP_Rx to determine this 1463 value are application specific, and thus, out of the scope of this 1464 document. 1466 If specified, the amount of backfill that will be provided by the 1467 unicast bursts and any payload-specific information MUST NOT be 1468 smaller than the specified value. Otherwise, the backfill will 1469 not be able to build up the desired level of buffer at the RTP_Rx 1470 and can cause buffer underruns. 1472 Type: 2 1474 o Max RAMS Buffer Fill Requirement (32 bits): Optional TLV element 1475 that denotes the maximum milliseconds of data that the RTP_Rx can 1476 buffer without losing the data due to buffer overflow. 1478 The RTP_Rx can have knowledge of its buffering requirements. 1479 These requirements can be application or device specific. For 1480 instance, one particular RTP_Rx might have more physical memory 1481 than another RTP_Rx, and thus, can buffer more data. If the BRS 1482 knows the buffering ability of the receiver, the BRS can tailor 1483 the burst(s) more precisely. The methods used by the receiver to 1484 determine this value are application specific, and thus, out of 1485 scope. 1487 If specified, the amount of backfill that will be provided by the 1488 unicast bursts and any payload-specific information MUST NOT be 1489 larger than this value. Otherwise, the backfill may cause buffer 1490 overflows at the RTP_Rx. 1492 Type: 3 1494 o Max Receive Bitrate (64 bits): Optional TLV element that denotes 1495 the maximum bitrate (in bits per second) at which the RTP_Rx can 1496 process the aggregation of the unicast burst(s) and any payload- 1497 specific information that will be provided by the BRS. The limits 1498 can include local receiver limits as well as network limits that 1499 are known to the receiver. 1501 If specified, the total bitrate of the unicast burst(s) plus any 1502 payload-specific information MUST NOT be larger than this value. 1503 Otherwise, congestion and packet loss are more likely to occur. 1505 Type: 4 1507 o Preamble-only Allowed (0 bits): Optional TLV element that 1508 indicates that the RTP_Rx is willing to receive only the preamble 1509 information for the desired primary multicast stream(s) in case 1510 the BRS cannot send the unicast burst stream(s) (In such cases, 1511 the BRS will not accept the request, but will send a response code 1512 511 in the RAMS-I message as defined in Section 11.6). Note that 1513 the RTP_Rx signals the particular preamble format(s) it supports 1514 through a public or a private extension in the same RAMS-R 1515 message. 1517 If this TLV element does not exist in the RAMS-R message, the BRS 1518 MUST NOT respond to the RAMS-R message by sending the preamble 1519 information only. Since this TLV element does not carry a Value 1520 field, the Length field MUST be set to zero. 1522 Type: 5 1524 o Supported Enterprise Number(s): Optional TLV element that 1525 indicates the enterprise number(s) that the RTP_Rx implementation 1526 supports. Similar to the private extensions, the enterprise 1527 numbers here are used from 1528 http://www.iana.org/assignments/enterprise-numbers. This TLV 1529 element, if exists, provides a hint information to the BRS about 1530 which private extensions the RTP_Rx can potentially support. Note 1531 that an RTP_Rx does not necessarily support all the private 1532 extensions under a particular enterprise number. Unless the BRS 1533 explicitly knows which private extensions an RTP_Rx supports 1534 (through this or some out-of-band means), the BRS SHOULD NOT use 1535 private extensions in the RAMS-I messages. The BRS SHOULD rather 1536 use only vendor-neutral extensions. The Length field of this TLV 1537 element is set to 4*n, where n is the number of enterprise number 1538 entries. 1540 Type: 6 1542 7.3. RAMS Information 1544 The RAMS Information (RAMS-I) message is identified by SFMT=2. This 1545 message is used to describe the unicast burst that will be sent for 1546 rapid acquisition. It also includes other useful information for the 1547 RTP_Rx as described below. 1549 A separate RAMS-I message with the appropriate response code is sent 1550 in the unicast burst RTP session by the BRS for each primary 1551 multicast stream that has been requested by the RTP_Rx. In each of 1552 these RAMS-I messages, the media sender SSRC and packet sender SSRC 1553 fields are both set to the SSRC of the BRS, which equals the SSRC of 1554 the respective primary multicast stream. 1556 The FCI field MUST contain only one RAMS Information message. The 1557 FCI field has the structure depicted in Figure 8. 1559 The semantics of the RAMS-I message is independent of the payload 1560 type carried in the primary multicast RTP session. 1562 0 1 2 3 1563 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1564 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1565 | SFMT=2 | MSN | Response | 1566 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1567 : Optional TLV-encoded Fields (and Padding, if needed) : 1568 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1570 Figure 8: FCI field syntax for the RAMS Information message 1572 A RAMS-I message has the following fields: 1574 o Message Sequence Number (8 bits) : Mandatory field that denotes 1575 the sequence number of the RAMS-I message for the particular media 1576 sender SSRC specified in the message header. The MSN value SHALL 1577 be set to zero only when a new RAMS request is received. During 1578 rapid acquisition, the same RAMS-I message MAY be repeated for 1579 redundancy purposes without incrementing the MSN value. If an 1580 updated RAMS-I message will be sent (either with a new information 1581 or an updated information), the MSN value SHALL be incremented by 1582 one. In the MSN field, the regular wrapping rules apply. Note 1583 that if the RTP_Rx has sent an updated request, it MUST check 1584 every RAMS-I message entirely regardless of whether the MSN value 1585 has changed or not. 1587 o Response (16 bits): Mandatory field that denotes the response 1588 code for this RAMS-I message. This document defines several 1589 initial response codes in Section 7.3.1 and registers them with 1590 IANA in Section 11.6. If a new vendor-neutral response code will 1591 be defined, it MUST be registered with IANA through the guidelines 1592 specified in Section 11.6. If the new response code is intended 1593 to be used privately by a vendor, there is no need for IANA 1594 management. Instead, the vendor MUST use the private extension 1595 mechanism (Section 7.1.2) to convey its message and MUST indicate 1596 this by putting zero in the Response field. 1598 When the RTP_Rx receives a RAMS-I message with a response code 1599 that it does not understand, the RTP_Rx MUST send a RAMS-T message 1600 immediately to the BRS. 1602 The following TLV elements have been defined for the RAMS-I messages: 1604 o Media Sender SSRC (32 bits): Optional TLV element that specifies 1605 the media sender SSRC of the unicast burst stream. If the FT_Ap 1606 that received the RAMS-R message is associated with a single 1607 primary multicast stream but the requested media sender SSRC does 1608 not match the SSRC of the RTP stream associated with this FT_Ap, 1609 the BRS includes this TLV element in the initial RAMS-I message to 1610 let the RTP_Rx know that the media sender SSRC has changed. If 1611 the two SSRCs match, there is no need to include this TLV element. 1613 Type: 31 1615 o RTP Seqnum of the First Packet (16 bits): TLV element that 1616 specifies the RTP sequence number of the first packet that will be 1617 sent in the respective unicast RTP stream. This allows the RTP_Rx 1618 to know whether one or more packets sent by the BRS have been 1619 dropped at the beginning of the stream. If the BRS accepts the 1620 RAMS request, this element exists. If the BRS rejects the RAMS 1621 request, this element SHALL NOT exist. 1623 Type: 32 1625 o Earliest Multicast Join Time (32 bits): TLV element that 1626 specifies the delta time (in ms) between the arrival of the first 1627 RTP packet in the unicast RTP stream (which could be a burst 1628 packet or a payload-specific packet) and the earliest time instant 1629 when an RTP_Rx MAY send an SFGMP Join message to join the 1630 multicast session. A zero value in this field means that the 1631 RTP_Rx MAY send the SFGMP Join message right away. If the RTP_Rx 1632 does not want to wait until the earliest multicast join time, it 1633 MAY send a RAMS-T message and only after a reasonable amount of 1634 time, it MAY join the SSM session. 1636 If the RAMS request has been accepted, the BRS sends this field at 1637 least once, so that the RTP_Rx knows when to join the multicast 1638 session. If the burst request has been rejected as indicated in 1639 the Response field, this field MUST be set to zero. In that case, 1640 it is up to the RTP_Rx when or whether to join the multicast 1641 session. 1643 When the BRS serves two or more bursts and sends a separate RAMS-I 1644 message for each burst, the join times specified in these RAMS-I 1645 messages SHOULD correspond to more or less the same time instant, 1646 and the RTP_Rx sends the SFGMP Join message based on the earliest 1647 join time. 1649 Type: 33 1651 o Burst Duration (32 bits): Optional TLV element that denotes the 1652 time the burst will last (in ms), i.e., the difference between the 1653 expected transmission times of the first and the last burst 1654 packets that the BRS is planning to send in the respective unicast 1655 RTP stream. In the absence of additional stimulus, the BRS will 1656 send a burst of this duration. However, the burst duration can be 1657 modified by subsequent events, including changes in the primary 1658 multicast stream and reception of RAMS-T messages. 1660 The BRS MUST terminate the flow in the timeframe indicated by this 1661 burst duration or the duration established by those subsequent 1662 events, even if it does not get a RAMS-T or a BYE message from the 1663 RTP_Rx. It is OPTIONAL to send this field in a RAMS-I message 1664 when the burst request is accepted. If the burst request has been 1665 rejected as indicated in the Response field, this field MAY be 1666 omitted or set to zero. 1668 Type: 34 1670 o Max Transmit Bitrate (64 bits): Optional TLV element that denotes 1671 the maximum bitrate (in bits per second) that will be used by the 1672 BRS for the RTP stream associated with this RAMS-I message. 1674 Type: 35 1676 7.3.1. Response Code Definitions 1678 1xx-Level Response Codes: These response codes are sent for 1679 informational purposes. 1681 o 100: This is used when the BRS wants to update a value that was 1682 sent earlier to the RTP_Rx. 1684 2xx-Level Response Codes: These response codes are sent to indicate 1685 success. 1687 o 200: This is used when the server accepts the RAMS request. 1689 o 201: This is used when the unicast burst has been completed and 1690 the BRS wants to notify the RTP_Rx. 1692 4xx-Level Response Codes: These response codes are sent to indicate 1693 that the message sent by the RTP_Rx is either improperly formatted or 1694 contains an invalid value. The rules the RTP_Rx needs to follow upon 1695 receiving one of these response codes are outlined in Step 5 in 1696 Section 6.2. The 4xx-level response codes are also used as status 1697 codes in the Multicast Acquisition Report Block 1698 [I-D.ietf-avt-multicast-acq-rtcp-xr] in order to collect RTP_Rx-based 1699 error conditions. 1701 o 400: This is used when the RAMS-R message is improperly 1702 formatted. 1704 o 401: This is used when the minimum RAMS buffer fill requirement 1705 value indicated in the RAMS-R message is invalid. 1707 o 402: This is used when the maximum RAMS buffer fill requirement 1708 value indicated in the RAMS-R message is invalid. 1710 o 403: This is used when the maximum receive bitrate value 1711 indicated in the RAMS-R message is insufficient. 1713 o 404: This is used when the RAMS-T message is improperly 1714 formatted. 1716 5xx-Level Response Codes: These response codes are sent to indicate 1717 an error on the BRS side. The rules the RTP_Rx needs to follow upon 1718 receiving one of these response codes are outlined in Step 3 in 1719 Section 6.2 and Section 7.2. The 5xx-level response codes are also 1720 used as status codes in the Multicast Acquisition Report Block 1721 [I-D.ietf-avt-multicast-acq-rtcp-xr] in order to collect BRS-based 1722 error conditions. 1724 o 500: This is used when the BRS has experienced an internal error 1725 and cannot accept the RAMS request. 1727 o 501: This is used when the BRS does not have enough bandwidth to 1728 send the unicast burst stream. 1730 o 502: This is used when the BRS terminates the unicast burst 1731 stream due to network congestion. 1733 o 503: This is used when the BRS does not have enough CPU resources 1734 to send the unicast burst stream. 1736 o 504: This is used when the BRS does not support sending a unicast 1737 burst stream. 1739 o 505: This is used when the requesting RTP_Rx is not eligible to 1740 receive a unicast burst stream. 1742 o 506: This is used when RAMS functionality is not enabled for the 1743 requested multicast stream. 1745 o 507: This is used when the BRS cannot find a valid starting point 1746 for the unicast burst stream satisfying the RTP_Rx's requirements. 1748 o 508: This is used when the BRS cannot find the essential 1749 reference information for the requested multicast stream. 1751 o 509: This is used when the BRS cannot match the requested SSRC to 1752 any of the streams it is serving. 1754 o 510: This is used when the BRS cannot serve the requested entire 1755 session. 1757 o 511: This is used when the BRS sends only the preamble 1758 information but not the whole unicast burst stream. 1760 o 512: This is used when the RAMS request is denied due to a policy 1761 specified for the requested multicast stream, requesting RTP_Rx or 1762 this particular BRS. 1764 7.4. RAMS Termination 1766 The RAMS Termination (RAMS-T) message is identified by SFMT=3. 1768 The RAMS Termination is used to assist the BRS in determining when to 1769 stop the burst. A separate RAMS-T message is sent in the unicast 1770 burst RTP session by the RTP_Rx for each primary multicast stream 1771 that has been served by the BRS. Each of these RAMS-T message's 1772 media sender SSRC field SHALL BE populated with the SSRC of the media 1773 stream to be terminated. If the media sender SSRC populated in the 1774 RAMS-T message does not match the SSRC of the burst served by the 1775 BRS, BRS SHALL ignore the RAMS-T message. 1777 If the RTP_Rx wants the BRS to stop a burst prematurely, it sends a 1778 RAMS-T message as described below. Upon receiving this message, the 1779 BRS stops the respective burst immediately. If the RTP_Rx wants the 1780 BRS to terminate all of the bursts, it needs to send all of the 1781 respective RAMS-T messages in a single compound RTCP packet. 1783 The default behavior for the RTP_Rx is to send a RAMS-T message 1784 immediately after it joined the multicast session and started 1785 receiving multicast packets. In that case, the RTP_Rx includes the 1786 sequence number of the first RTP packet received in the primary 1787 multicast stream in the RAMS-T message. With this information, the 1788 BRS can decide when to terminate the unicast burst. 1790 The FCI field MUST contain only one RAMS Termination. The FCI field 1791 has the structure depicted in Figure 9. 1793 The semantics of the RAMS-T message is independent of the payload 1794 type carried in the primary multicast RTP session. 1796 0 1 2 3 1797 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1798 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1799 | SFMT=3 | Reserved | 1800 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1801 : Optional TLV-encoded Fields (and Padding, if needed) : 1802 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1804 Figure 9: FCI field syntax for the RAMS Termination message 1806 o Extended RTP Seqnum of First Multicast Packet (32 bits): Optional 1807 TLV element that specifies the extended RTP sequence number of the 1808 first packet received from the SSM session for a particular 1809 primary multicast stream. The low 16 bits contain the sequence 1810 number of the first packet received from the SSM session, and the 1811 most significant 16 bits extend that sequence number with the 1812 corresponding count of sequence number cycles, which can be 1813 maintained according to the algorithm in Appendix A.1 of 1814 [RFC3550]. 1816 Type: 61 1818 8. SDP Signaling 1820 8.1. Definitions 1822 The syntax of the 'rtcp-fb' attribute has been defined in [RFC4585]. 1823 Here we add the following syntax to the 'rtcp-fb' attribute (the 1824 feedback type and optional parameters are all case sensitive): 1826 (In the following ABNF [RFC5234], rtcp-fb-nack-param is used as 1827 defined in [RFC4566].) 1829 rtcp-fb-nack-param =/ SP "rai" 1831 The following parameter is defined in this document for use with 1832 'nack': 1834 o 'rai' stands for Rapid Acquisition Indication and indicates the 1835 use of RAMS messages as defined in Section 7. 1837 This document also defines a new media-level SDP attribute ('rams- 1838 updates') that indicates whether the BRS supports updated request 1839 messages or not. This attribute is used in a declarative manner and 1840 no Offer/Answer Model behavior is specified. If the BRS supports 1841 updated request messages and this attribute is included in the SDP 1842 description, the RTP_Rx can send updated requests. The BRS might or 1843 might not be able to accept value changes in every field in an 1844 updated RAMS-R message. However, if the 'rams-updates' attribute is 1845 not included in the SDP description, the RTP_Rx SHALL NOT send 1846 updated requests. The RTP_Rx MAY still repeat its initial request 1847 without changes, though. 1849 8.2. Requirements 1851 The use of SDP to describe the RAMS entities normatively requires the 1852 support for: 1854 o The SDP grouping framework and flow identification (FID) semantics 1855 [RFC5888] 1857 o The RTP/AVPF profile [RFC4585] 1859 o The RTP retransmission payload format [RFC4588] 1861 o The RTCP extensions for SSM sessions with unicast feedback 1862 [RFC5760] 1864 o The multicast RTCP port attribute [I-D.ietf-avt-rtcp-port-for-ssm] 1866 o Multiplexing RTP and RTCP on a single port on both endpoints in 1867 the unicast session[RFC5761] 1869 The support for the source-specific media attributes [RFC5576] can 1870 also be needed when the 'ssrc' attribute is to be used for the media 1871 descriptions. 1873 8.3. Example and Discussion 1875 This section provides a declarative SDP [RFC4566] example (for the 1876 RTP_Rx side) for enabling rapid acquisition of multicast RTP 1877 sessions. 1879 v=0 1880 o=ali 1122334455 1122334466 IN IP4 rams.example.com 1881 s=Rapid Acquisition Example 1882 t=0 0 1883 a=group:FID 1 2 1884 a=rtcp-unicast:rsi 1885 m=video 41000 RTP/AVPF 98 1886 i=Primary Multicast Stream 1887 c=IN IP4 233.252.0.2/255 1888 a=source-filter:incl IN IP4 233.252.0.2 198.51.100.1 1889 a=rtpmap:98 MP2T/90000 1890 a=multicast-rtcp:42000 1891 a=rtcp:43000 IN IP4 192.0.2.1 1892 a=rtcp-fb:98 nack 1893 a=rtcp-fb:98 nack rai 1894 a=ssrc:123321 cname:iptv-ch32@rams.example.com 1895 a=rams-updates 1896 a=mid:1 1897 m=video 51000 RTP/AVPF 99 1898 i=Unicast Retransmission Stream (Ret. and Rapid Acq. Support) 1899 c=IN IP4 192.0.2.1 1900 a=sendonly 1901 a=rtpmap:99 rtx/90000 1902 a=rtcp-mux 1903 a=fmtp:99 apt=98;rtx-time=5000 1904 a=mid:2 1906 Figure 10: Example SDP for a single-channel RAMS scenario 1908 In this example SDP description, we have a primary multicast (source) 1909 stream and a unicast retransmission stream. The source stream is 1910 multicast from a distribution source (with a source IP address of 1911 198.51.100.1) to the multicast destination address of 233.252.0.2 and 1912 port 41000. The corresponding RTCP traffic is multicast to the same 1913 multicast destination address at port 42000. Here, we are assuming 1914 that the multicast RTP and RTCP ports are carefully chosen so that 1915 different RTP and RTCP streams do not collide with each other. 1917 The feedback target (FT_Ap) residing on the RS (with an address of 1918 192.0.2.1) at port 43000 is declared with the "a=rtcp" line 1919 [RFC3605]. The support for the conventional retransmission is 1920 indicated through the "a=rtcp-fb:98 nack" line. The RTP receiver(s) 1921 can report missing packets on the source stream to the feedback 1922 target and request retransmissions. The SDP above includes the 1923 "a=sendonly" line for the media description of the retransmission 1924 stream since the retransmissions are sent in only one direction. 1926 The support for rapid acquisition is indicated through the "a=rtcp- 1927 fb:98 nack rai" line. The parameter 'rtx-time' applies to both the 1928 conventional retransmissions and rapid acquisition. However, when 1929 rapid acquisition is enabled, the standard definition for the 1930 parameter 'rtx-time' given in [RFC4588] is not followed. Instead, 1931 when rapid acquisition support is enabled, 'rtx-time' specifies the 1932 time in milliseconds that the BRS keeps an RTP packet in its cache 1933 available for retransmission (measured from the time the packet was 1934 received by the BRS, not from the time indicated in the packet 1935 timestamp). 1937 Once an RTP_Rx has acquired an SDP description, it can ask for rapid 1938 acquisition before it joins a primary multicast RTP session. To do 1939 so, it sends a RAMS-R message to the feedback target of that primary 1940 multicast RTP session. If the FT_Ap is associated with only one RTP 1941 stream, the RTP_Rx does not need to learn the SSRC of that stream via 1942 an out-of-band method. If the BRS accepts the rapid acquisition 1943 request, it will send a RAMS-I message with the correct SSRC 1944 identifier. If the FT_Ap is associated with a multi-stream RTP 1945 session and the RTP_Rx is willing to request rapid acquisition for 1946 the entire session, the RTP_Rx again does not need to learn the SSRCs 1947 via an out-of-band method. However, if the RTP_Rx intends to request 1948 a particular subset of the primary multicast streams, it must learn 1949 their SSRC identifiers and list them in the RAMS-R message. Since 1950 this RTP_Rx has not yet received any RTP packets for the primary 1951 multicast stream(s), the RTP_Rx must in this case learn the SSRC 1952 value(s) from the 'ssrc' attribute of the media description 1953 [RFC5576]. In addition to the SSRC value, the 'cname' source 1954 attribute must also be present in the SDP description [RFC5576]. 1956 Listing the SSRC values for the primary multicast streams in the SDP 1957 file does not create a problem in SSM sessions when an SSRC collision 1958 occurs. This is because in SSM sessions, an RTP_Rx that observed an 1959 SSRC collision with a media sender must change its own SSRC [RFC5760] 1960 by following the rules defined in [RFC3550]. 1962 A feedback target that receives a RAMS-R message becomes aware that 1963 the RTP_Rx wants to rapidly catch up with a primary multicast RTP 1964 session. If the necessary conditions are satisfied (as outlined in 1965 Section 7 of [RFC4585]) and available resources exist, the BRS can 1966 react to the RAMS-R message by sending any transport-layer (and 1967 optional payload-specific, when allowed) feedback message(s) and 1968 starting the unicast burst. 1970 In this section, we considered the simplest scenario where the 1971 primary multicast RTP session carried only one stream and the RTP_Rx 1972 wanted to rapidly acquire this stream only. Best practices for 1973 scenarios where the primary multicast RTP session carries two or more 1974 streams or the RTP_Rx wants to acquire one or more streams from 1975 multiple primary multicast RTP sessions at the same time are 1976 presented in [I-D.begen-avt-rams-scenarios]. 1978 9. NAT Considerations 1980 For a variety of reasons, one or more Network Address Port 1981 Translators (NAPT - hereafter simply called NAT) can exist between 1982 the RTP_Rx and RS. NATs have a variety of operating characteristics 1983 for UDP traffic [RFC4787]. For a NAT to permit traffic from the BRS 1984 to arrive at the RTP_Rx, the NAT(s) must first either: 1986 a. See UDP (or DCCP) traffic sent from the RTP_Rx (which is on the 1987 'inside' of the NAT) to the BRS (which is on the 'outside' of the 1988 NAT). This traffic has the same transport address as the 1989 subsequent response traffic, or; 1991 b. Be configured to forward certain ports (e.g., using HTML 1992 configuration or UPnP IGD [UPnP-IGD]). Details of this are out 1993 of scope of this document. 1995 For both (a) and (b), the RTP_Rx is responsible for maintaining the 1996 NAT's state if it wants to receive traffic from the BRS on that port. 1997 For (a), the RTP_Rx MUST send UDP traffic to keep the NAT binding 1998 alive, at least every 30 seconds [RFC4787]. While (a) is more like 1999 an automatic/dynamic configuration, (b) is more like a manual/static 2000 configuration. 2002 When the RTP_Rx sends a request (RAMS-R) message to the FT as unicast 2003 feedback in the primary multicast RTP session, and the request is 2004 received by the FT, a new unicast burst RTP session will be 2005 established between the BRS and RTP_Rx. 2007 While the FT and BRS ports on the RS are already signaled via out-of- 2008 band means (e.g., SDP), the RTP_Rx needs to convey the RTP and RTCP 2009 ports it wants to use on its side for the new session. Since there 2010 are two RTP sessions (one multicast and one unicast) involved during 2011 this process and one of them is established upon a feedback message 2012 sent in the other one, this requires an explicit port mapping method. 2014 Applications using RAMS MUST support the solution presented in 2015 [I-D.ietf-avt-ports-for-ucast-mcast-rtp] both on the RS and RTP_Rx 2016 side to allow RTP receivers to use their desired ports and to support 2017 RAMS behind NAT devices. The port mapping message exchange needs to 2018 take place whenever the RTP_Rx intends to make use of the RAMS 2019 protocol for rapidly acquiring a specific multicast RTP session, 2020 prior to joining the associated SSM session. 2022 10. Security Considerations 2024 Applications that are using RAMS make heavy use of the unicast 2025 feedback mechanism described in [RFC5760], the payload format defined 2026 in [RFC4588] and the port mapping solution specified in 2027 [I-D.ietf-avt-ports-for-ucast-mcast-rtp]. Thus, these applications 2028 are subject to the general security considerations discussed in those 2029 documents. In particular, the threats and risks discussed in 2030 [RFC5760] need to be considered carefully. In this section, we give 2031 an overview of the guidelines and suggestions described in these 2032 specifications from a RAMS perspective. We also discuss the security 2033 considerations that explicitly apply to applications using RAMS. 2035 First of all, much of the session description information is 2036 available in the SDP descriptions that are distributed to the media 2037 senders, retransmission servers and RTP receivers. Adequate security 2038 measures are RECOMMENDED to ensure the integrity and authenticity of 2039 the SDP descriptions so that transport addresses of the media 2040 senders, distribution sources, feedback targets as well as other 2041 session-specific information can be protected. See [RFC4566] for 2042 details. 2044 Compared to an RTCP NACK message that triggers one or more 2045 retransmissions, a RAMS Request (RAMS-R) message can trigger a new 2046 burst stream to be sent by the retransmission server. Depending on 2047 the application-specific requirements and conditions existing at the 2048 time of the RAMS-R reception by the retransmission server, the 2049 resulting burst stream can potentially contain a large number of 2050 retransmission packets. Since these packets are sent faster than the 2051 nominal rate, RAMS consumes more resources on the retransmission 2052 servers, RTP receivers and the network. In particular, this can make 2053 denial-of-service (DoS) attacks more intense, and hence, more harmful 2054 than attacks that target ordinary retransmission sessions. 2056 As RAMS messages are sent as RTCP messages, following the suggestions 2057 given in [RFC4588], counter-measures SHOULD be taken to prevent 2058 tampered or spoofed RTCP packets. Tampered RAMS-R messages can 2059 trigger inappropriate burst streams or alter the existing burst 2060 streams in an inappropriate way. For example, if the Max Receive 2061 Bitrate field is altered by a tampered RAMS-R message, the updated 2062 burst can overflow the buffer at the receiver side, or oppositely, 2063 can slow down the burst to the point that it becomes useless. 2064 Tampered RAMS Termination (RAMS-T) messages can terminate valid burst 2065 streams prematurely resulting in gaps in the received RTP packets. 2066 RAMS Information (RAMS-I) messages contain fields that are critical 2067 for a successful rapid acquisition. Any tampered information in the 2068 RAMS-I message can easily cause an RTP receiver to make wrong 2069 decisions. Consequently, the RAMS operation can fail. 2071 RTCP BYE messages are similar to RAMS-T messages in the sense that 2072 they can be used to stop an existing burst. The CNAME of an RTP 2073 receiver is used to bind the RTCP BYE message to an existing burst. 2074 Thus, one should be careful if the CNAMEs are reasonably easy to 2075 guess and off-path attacks can be performed. Also note that the 2076 CNAMEs might be redistributed to all participants in the multicast 2077 group (as in ASM or the simple feedback model of [RFC5760]). 2079 The retransmission server has to consider if values indicated in a 2080 RAMS-R message are reasonable. For example, a request demanding a 2081 large value of many seconds in the Min RAMS Buffer Fill Requirement 2082 element should, unless special uses cases exist, likely be rejected 2083 since it is likely to be an attempt to prolong a DoS attack on the 2084 retransmission server, RTP receiver and/or the network. The Max 2085 Receive Bitrate could also be set to a very large value to try to get 2086 the retransmission server to cause massive congestion by bursting at 2087 a bitrate that will not be supported by the network. An RTP_Rx 2088 should also consider if the values for the Earliest Multicast Join 2089 Time and Burst Duration indicated by the retransmission server in a 2090 RAMS-I message are reasonable. For example, if the burst packets 2091 stop arriving and the join time is still significantly far into the 2092 future, this could be a sign of a man-in-the-middle attack where the 2093 RAMS-I message has been manipulated by an attacker. 2095 A basic mitigation against DoS attacks introduced by an attacker 2096 injecting tampered RAMS messages is source address validation 2097 [RFC2827]. Also, most of the DoS attacks can be prevented by the 2098 integrity and authenticity checks enabled by Secure RTP (SRTP) 2099 [RFC3711]. However, an attack can still be started by legitimate 2100 endpoints that send several valid RAMS-R messages to a particular 2101 feedback target in a synchronized fashion and in a very short amount 2102 of time. Since a RAMS operation can temporarily consume a large 2103 amount of resources, a series of the RAMS-R messages can temporarily 2104 overload the retransmission server. In these circumstances, the 2105 retransmission server can, for example, reject incoming RAMS requests 2106 until its resources become available again. One means to ameliorate 2107 this threat is to apply a per-endpoint policing mechanism on the 2108 incoming RAMS requests. A reasonable policing mechanism should 2109 consider application-specific requirements and minimize false 2110 negatives. 2112 In addition to the DoS attacks, man-in-the-middle and replay attacks 2113 will also be harmful. RAMS-R messages do not carry any information 2114 that allows the retransmission server to detect duplication or replay 2115 attacks. Thus, the possibility of a replay attack using a captured 2116 valid RAMS-R message exists unless a mitigation method such as Secure 2117 RTCP (SRTCP) is used. Similarly, RAMS-T messages can be replayed. 2118 The RAMS-I has sequence number that makes replay attacks less likely 2119 but not impossible. Man-in-the-middle attacks that are capable of 2120 capturing, injecting or modifying the RAMS messages can easily 2121 accomplish the attacks described above. Thus, cryptographic 2122 integrity and authentication is the only reliable protection. To 2123 protect the RTCP messages from man-in-the-middle and replay attacks, 2124 the RTP receivers and retransmission server SHOULD perform a DTLS- 2125 SRTP handshake [RFC5764] over the RTCP channel. Because there is no 2126 integrity-protected signaling channel between an RTP receiver and the 2127 retransmission server, the retransmission server MUST maintain a list 2128 of certificates owned by legitimate RTP receivers, or their 2129 certificates MUST be signed by a trusted Certificate Authority. Once 2130 the DTLS-SRTP security is established, non-SRTCP-protected messages 2131 received from a particular RTP receiver are ignored by the 2132 retransmission server. To reduce the impact of DTLS-SRTP overhead 2133 when communicating with different feedback targets on the same 2134 retransmission server, it is RECOMMENDED that RTP receivers and the 2135 retransmission server both support TLS Session Resumption without 2136 Server-side State [RFC5077]. To help scale SRTP to handle many RTP 2137 receivers asking for retransmissions of identical data, implementors 2138 may consider using the same SRTP key for SRTP data sent to the 2139 receivers [I-D.ietf-avt-srtp-ekt] and be aware that such key sharing 2140 allows those receivers to impersonate the sender, so source address 2141 validation remains important. 2143 [RFC4588] RECOMMENDS that the cryptography mechanisms are used for 2144 the retransmission payload format to provide protection against known 2145 plain-text attacks. As discussed in [RFC4588], the retransmission 2146 payload format sets the timestamp field in the RTP header to the 2147 media timestamp of the original packet and this does not compromise 2148 the confidentiality. Furthermore, if cryptography is used to provide 2149 security services on the original stream, then the same services, 2150 with equivalent cryptographic strength, MUST be provided on the 2151 retransmission stream per [RFC4588]. 2153 Finally, a retransmission server that has become subverted by an 2154 attacker is almost impossible to protect against as such a server can 2155 perform a large number of different actions to deny service to 2156 receivers. 2158 11. IANA Considerations 2160 The following contact information shall be used for all registrations 2161 in this document: 2163 Ali Begen 2164 abegen@cisco.com 2166 Note to the RFC Editor: In the following, please replace "XXXX" with 2167 the number of this document prior to publication as an RFC. 2169 11.1. Registration of SDP Attributes 2171 This document registers a new attribute name in SDP. 2173 SDP Attribute ("att-field"): 2174 Attribute name: rams-updates 2175 Long form: Support for Updated RAMS Request Messages 2176 Type of name: att-field 2177 Type of attribute: Media level 2178 Subject to charset: No 2179 Purpose: See this document 2180 Reference: [RFCXXXX] 2181 Values: None 2183 11.2. Registration of SDP Attribute Values 2185 This document registers a new value for the 'nack' attribute to be 2186 used with the 'rtcp-fb' attribute in SDP. For more information about 2187 the 'rtcp-fb' attribute, refer to Sections 4.2 and 6.2 of [RFC4585]. 2189 Value name: rai 2190 Long name: Rapid Acquisition Indication 2191 Usable with: nack 2192 Reference: [RFCXXXX] 2194 11.3. Registration of FMT Values 2196 Within the RTPFB range, the following format (FMT) value is 2197 registered: 2199 Name: RAMS 2200 Long name: Rapid Acquisition of Multicast Sessions 2201 Value: 6 2202 Reference: [RFCXXXX] 2204 11.4. SFMT Values for RAMS Messages Registry 2206 This document creates a new sub-registry for the sub-feedback message 2207 type (SFMT) values to be used with the FMT value registered for RAMS 2208 messages. The registry is called the SFMT Values for RAMS Messages 2209 Registry. This registry is to be managed by the IANA according to 2210 the Specification Required policy of [RFC5226]. 2212 The length of the SFMT field in the RAMS messages is a single octet, 2213 allowing 256 values. The registry is initialized with the following 2214 entries: 2216 Value Name Reference 2217 ----- -------------------------------------------------- ------------- 2218 0 Reserved [RFCXXXX] 2219 1 RAMS Request [RFCXXXX] 2220 2 RAMS Information [RFCXXXX] 2221 3 RAMS Termination [RFCXXXX] 2222 4-254 Assignable - Specification Required 2223 255 Reserved [RFCXXXX] 2225 The SFMT values 0 and 255 are reserved for future use. 2227 Any registration for an unassigned SFMT value needs to contain the 2228 following information: 2230 o Contact information of the one doing the registration, including 2231 at least name, address, and email. 2233 o A detailed description of what the new SFMT represents and how it 2234 shall be interpreted. 2236 New RAMS functionality is intended to be introduced by using the 2237 extension mechanism within the existing RAMS message types not by 2238 introducing new message types unless it is absolutely necessary. 2240 11.5. RAMS TLV Space Registry 2242 This document creates a new IANA TLV space registry for the RAMS 2243 extensions. The registry is called the RAMS TLV Space Registry. 2244 This registry is to be managed by the IANA according to the 2245 Specification Required policy of [RFC5226]. 2247 The length of the Type field in the TLV elements is a single octet, 2248 allowing 256 values. The Type values 0 and 255 are reserved for 2249 future use. The Type values between (and including) 128 and 254 are 2250 reserved for private extensions. 2252 The registry is initialized with the following entries: 2254 Type Description Reference 2255 ---- -------------------------------------------------- ------------- 2256 0 Reserved [RFCXXXX] 2257 1 Requested Media Sender SSRC(s) [RFCXXXX] 2258 2 Min RAMS Buffer Fill Requirement [RFCXXXX] 2259 3 Max RAMS Buffer Fill Requirement [RFCXXXX] 2260 4 Max Receive Bitrate [RFCXXXX] 2261 5 Request for Preamble Only [RFCXXXX] 2262 6 Supported Enterprise Number(s) [RFCXXXX] 2263 7-30 Assignable - Specification Required 2264 31 Media Sender SSRC [RFCXXXX] 2265 32 RTP Seqnum of the First Packet [RFCXXXX] 2266 33 Earliest Multicast Join Time [RFCXXXX] 2267 34 Burst Duration [RFCXXXX] 2268 35 Max Transmit Bitrate [RFCXXXX] 2269 36-60 Assignable - Specification Required 2270 61 Extended RTP Seqnum of First Multicast Packet [RFCXXXX] 2271 62-127 Assignable - Specification Required 2272 128-254 No IANA Maintenance 2273 255 Reserved [RFCXXXX] 2275 Any registration for an unassigned Type value needs to contain the 2276 following information: 2278 o Contact information of the one doing the registration, including 2279 at least name, address, and email. 2281 o A detailed description of what the new TLV element represents and 2282 how it shall be interpreted. 2284 11.6. RAMS Response Code Space Registry 2286 This document creates a new IANA TLV space registry for the RAMS 2287 response codes. The registry is called the RAMS Response Code Space 2288 Registry. This registry is to be managed by the IANA according to 2289 the Specification Required policy of [RFC5226]. 2291 The length of the Response field is two octets, allowing 65536 codes. 2292 However, the response codes have been classified and registered 2293 following an HTTP-style code numbering in this document. New 2294 response codes should be classified following the guidelines below: 2296 Code Level Purpose 2297 ---------- --------------- 2298 1xx Informational 2299 2xx Success 2300 3xx Redirection 2301 4xx RTP Receiver (RTP_Rx) Error 2302 5xx Burst/Retransmission Source (BRS) Error 2304 The Response code 65535 is reserved for future use. 2306 The registry is initialized with the following entries: 2308 Code Description Reference 2309 ----- -------------------------------------------------- ------------- 2310 0 A private response code is included in the message [RFCXXXX] 2312 100 Parameter update for RAMS session [RFCXXXX] 2314 200 RAMS request has been accepted [RFCXXXX] 2315 201 Unicast burst has been completed [RFCXXXX] 2317 400 Invalid RAMS-R message syntax [RFCXXXX] 2318 401 Invalid min buffer requirement in RAMS-R message [RFCXXXX] 2319 402 Invalid max buffer requirement in RAMS-R message [RFCXXXX] 2320 403 Insufficient max bitrate requirement in RAMS-R 2321 message [RFCXXXX] 2322 404 Invalid RAMS-T message syntax [RFCXXXX] 2324 500 An unspecified BRS internal error has occurred [RFCXXXX] 2325 501 BRS has insufficient bandwidth to start RAMS 2326 session [RFCXXXX] 2327 502 Burst is terminated due to network congestion [RFCXXXX] 2328 503 BRS has insufficient CPU cycles to start RAMS 2329 session [RFCXXXX] 2330 504 RAMS functionality is not available on BRS [RFCXXXX] 2331 505 RAMS functionality is not available for RTP_Rx [RFCXXXX] 2332 506 RAMS functionality is not available for 2333 the requested multicast stream [RFCXXXX] 2334 507 BRS has no valid starting point available for 2335 the requested multicast stream [RFCXXXX] 2336 508 BRS has no reference information available for 2337 the requested multicast stream [RFCXXXX] 2338 509 BRS has no RTP stream matching the requested SSRC [RFCXXXX] 2339 510 RAMS request to acquire the entire session 2340 has been denied [RFCXXXX] 2341 511 Only the preamble information is sent [RFCXXXX] 2342 512 RAMS request has been denied due to a policy [RFCXXXX] 2344 Any registration for an unassigned Response code needs to contain the 2345 following information: 2347 o Contact information of the one doing the registration, including 2348 at least name, address, and email. 2350 o A detailed description of what the new Response code describes and 2351 how it shall be interpreted. 2353 12. Contributors 2355 Dave Oran, Magnus Westerlund and Colin Perkins have contributed 2356 significantly to this specification by providing text and solutions 2357 to some of the issues raised during the development of this 2358 specification. 2360 13. Acknowledgments 2362 The following individuals have reviewed the earlier versions of this 2363 specification and provided helpful comments: Joerg Ott, Roni Even, 2364 Dan Wing, Tony Faustini, Peilin Yang, Jeff Goldberg, Muriel 2365 Deschanel, Orit Levin, Guy Hirson, Tom Taylor, Xavier Marjou, Ye-Kui 2366 Wang, Zixuan Zou, Ingemar Johansson, Haibin Song, Ning Zong, Jonathan 2367 Lennox, Jose Rey, Sean Sheedy and Keith Drage. 2369 14. References 2371 14.1. Normative References 2373 [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. 2374 Jacobson, "RTP: A Transport Protocol for Real-Time 2375 Applications", STD 64, RFC 3550, July 2003. 2377 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2378 Requirement Levels", BCP 14, RFC 2119, March 1997. 2380 [RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. 2381 Thyagarajan, "Internet Group Management Protocol, Version 2382 3", RFC 3376, October 2002. 2384 [RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery 2385 Version 2 (MLDv2) for IPv6", RFC 3810, June 2004. 2387 [RFC4604] Holbrook, H., Cain, B., and B. Haberman, "Using Internet 2388 Group Management Protocol Version 3 (IGMPv3) and Multicast 2389 Listener Discovery Protocol Version 2 (MLDv2) for Source- 2390 Specific Multicast", RFC 4604, August 2006. 2392 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 2393 Description Protocol", RFC 4566, July 2006. 2395 [RFC5888] Camarillo, G. and H. Schulzrinne, "The Session Description 2396 Protocol (SDP) Grouping Framework", RFC 5888, June 2010. 2398 [RFC4585] Ott, J., Wenger, S., Sato, N., Burmeister, C., and J. Rey, 2399 "Extended RTP Profile for Real-time Transport Control 2400 Protocol (RTCP)-Based Feedback (RTP/AVPF)", RFC 4585, 2401 July 2006. 2403 [RFC4588] Rey, J., Leon, D., Miyazaki, A., Varsa, V., and R. 2404 Hakenberg, "RTP Retransmission Payload Format", RFC 4588, 2405 July 2006. 2407 [RFC5760] Ott, J., Chesterfield, J., and E. Schooler, "RTP Control 2408 Protocol (RTCP) Extensions for Single-Source Multicast 2409 Sessions with Unicast Feedback", RFC 5760, February 2010. 2411 [RFC5576] Lennox, J., Ott, J., and T. Schierl, "Source-Specific 2412 Media Attributes in the Session Description Protocol 2413 (SDP)", RFC 5576, June 2009. 2415 [RFC3605] Huitema, C., "Real Time Control Protocol (RTCP) attribute 2416 in Session Description Protocol (SDP)", RFC 3605, 2417 October 2003. 2419 [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 2420 Specifications: ABNF", STD 68, RFC 5234, January 2008. 2422 [RFC5506] Johansson, I. and M. Westerlund, "Support for Reduced-Size 2423 Real-Time Transport Control Protocol (RTCP): Opportunities 2424 and Consequences", RFC 5506, April 2009. 2426 [RFC5285] Singer, D. and H. Desineni, "A General Mechanism for RTP 2427 Header Extensions", RFC 5285, July 2008. 2429 [I-D.ietf-avt-rapid-rtp-sync] 2430 Perkins, C. and T. Schierl, "Rapid Synchronisation of RTP 2431 Flows", draft-ietf-avt-rapid-rtp-sync-12 (work in 2432 progress), July 2010. 2434 [RFC5761] Perkins, C. and M. Westerlund, "Multiplexing RTP Data and 2435 Control Packets on a Single Port", RFC 5761, April 2010. 2437 [I-D.ietf-avt-rtcp-port-for-ssm] 2438 Begen, A., "RTP Control Protocol (RTCP) Port for Source- 2439 Specific Multicast (SSM) Sessions", 2440 draft-ietf-avt-rtcp-port-for-ssm-02 (work in progress), 2441 August 2010. 2443 [I-D.ietf-avt-ports-for-ucast-mcast-rtp] 2444 Begen, A. and B. Steeg, "Port Mapping Between Unicast and 2445 Multicast RTP Sessions", 2446 draft-ietf-avt-ports-for-ucast-mcast-rtp-02 (work in 2447 progress), May 2010. 2449 [RFC2827] Ferguson, P. and D. Senie, "Network Ingress Filtering: 2450 Defeating Denial of Service Attacks which employ IP Source 2451 Address Spoofing", BCP 38, RFC 2827, May 2000. 2453 [RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. 2454 Norrman, "The Secure Real-time Transport Protocol (SRTP)", 2455 RFC 3711, March 2004. 2457 [RFC5764] McGrew, D. and E. Rescorla, "Datagram Transport Layer 2458 Security (DTLS) Extension to Establish Keys for the Secure 2459 Real-time Transport Protocol (SRTP)", RFC 5764, May 2010. 2461 [RFC5077] Salowey, J., Zhou, H., Eronen, P., and H. Tschofenig, 2462 "Transport Layer Security (TLS) Session Resumption without 2463 Server-Side State", RFC 5077, January 2008. 2465 14.2. Informative References 2467 [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, 2468 August 1980. 2470 [I-D.begen-avt-rams-scenarios] 2471 Begen, A., "Considerations for RAMS Scenarios", 2472 draft-begen-avt-rams-scenarios-00 (work in progress), 2473 October 2009. 2475 [I-D.ietf-avt-rtp-cnames] 2476 Begen, A., Perkins, C., and D. Wing, "Guidelines for 2477 Choosing RTP Control Protocol (RTCP) Canonical Names 2478 (CNAMEs)", draft-ietf-avt-rtp-cnames-01 (work in 2479 progress), August 2010. 2481 [I-D.ietf-avt-multicast-acq-rtcp-xr] 2482 Begen, A. and E. Friedrich, "Multicast Acquisition Report 2483 Block Type for RTP Control Protocol (RTCP) Extended 2484 Reports (XRs)", draft-ietf-avt-multicast-acq-rtcp-xr-01 2485 (work in progress), May 2010. 2487 [I-D.ietf-avt-ecn-for-rtp] 2488 Westerlund, M., Johansson, I., Perkins, C., and K. 2489 Carlberg, "Explicit Congestion Notification (ECN) for RTP 2490 over UDP", draft-ietf-avt-ecn-for-rtp-02 (work in 2491 progress), July 2010. 2493 [I-D.ietf-fecframe-interleaved-fec-scheme] 2494 Begen, A., "RTP Payload Format for 1-D Interleaved Parity 2495 FEC", draft-ietf-fecframe-interleaved-fec-scheme-09 (work 2496 in progress), January 2010. 2498 [RFC4787] Audet, F. and C. Jennings, "Network Address Translation 2499 (NAT) Behavioral Requirements for Unicast UDP", BCP 127, 2500 RFC 4787, January 2007. 2502 [RFC5762] Perkins, C., "RTP and the Datagram Congestion Control 2503 Protocol (DCCP)", RFC 5762, April 2010. 2505 [I-D.ietf-avt-srtp-ekt] 2506 McGrew, D., Andreasen, F., Wing, D., and K. Fischer, 2507 "Encrypted Key Transport for Secure RTP", 2508 draft-ietf-avt-srtp-ekt-01 (work in progress), July 2010. 2510 [UPnP-IGD] 2511 Forum, UPnP., "Universal Plug and Play (UPnP) Internet 2512 Gateway Device (IGD)", November 2001. 2514 [IC2009] Begen, A., Glazebrook, N., and W. VerSteeg, "Reducing 2515 Channel Change Times in IPTV with Real-Time Transport 2516 Protocol (IEEE Internet Computing)", May 2009. 2518 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 2519 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 2520 May 2008. 2522 Authors' Addresses 2524 Bill VerSteeg 2525 Cisco 2526 5030 Sugarloaf Parkway 2527 Lawrenceville, GA 30044 2528 USA 2530 Email: billvs@cisco.com 2532 Ali Begen 2533 Cisco 2534 181 Bay Street 2535 Toronto, ON M5J 2T3 2536 Canada 2538 Email: abegen@cisco.com 2540 Tom VanCaenegem 2541 Alcatel-Lucent 2542 Copernicuslaan 50 2543 Antwerpen, 2018 2544 Belgium 2546 Email: Tom.Van_Caenegem@alcatel-lucent.be 2548 Zeev Vax 2549 Microsoft Corporation 2550 1065 La Avenida 2551 Mountain View, CA 94043 2552 USA 2554 Email: zeevvax@microsoft.com