forked from w3c/webrtc-rtptransport
-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.bs
443 lines (412 loc) · 13.2 KB
/
index.bs
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
<pre class="metadata">
Title: WebRTC RTP Transport
Shortname: webrtc-rtptransport
Level: None
Status: UD
Group: webrtc
ED: https://w3c.github.io/webrtc-rtptransport/
TR: https://www.w3.org/TR/webrtc-rtptransport/
Repository: w3c/webrtc-rtptransport
URL: https://github.com/w3c/webrtc-rtptransport
Editor: Peter Thatcher, w3cid 68236, Microsoft Corporation https://www.microsoft.com, [email protected]
Editor: Bernard Aboba, w3cid 65611, Microsoft Corporation https://www.microsoft.com, [email protected]
Abstract:
The WebRTC-RtpTransport API allows web applications to send and receive RTP/RTCP packets
using the protocol defined in [[!RFC3550]].
Boilerplate: omit conformance
Complain About:accidental-2119 yes
Markup Shorthands: css no, markdown yes, dfn yes
!Participate: <a href="https://github.com/w3c/webrtc-rtptransport">Git Repository.</a>
!Participate: <a href="https://github.com/w3c/webrtc-rtptransport/issues/new">File an issue.</a>
!Version History: <a href="https://github.com/w3c/webrtc-rtptransport/commits">https://github.com/w3c/webrtc-rtptransport/commits</a>
</pre>
<pre class=link-defaults>
spec:webidl; type:dfn; text:resolve
</pre>
<pre class=biblio>
{
"WEBCODECS": {
"title": "WebCodecs",
"href": "https://www.w3.org/TR/webcodecs/",
"status": "None",
"publisher": "IETF"
},
"RFC3550": {
"title": "RTP: A Transport Protocol for Real-Time Applications",
"href": "https://datatracker.ietf.org/doc/html/rfc3550",
"authors": [
"H. Schulzrinne",
"S. Casner",
"R. Frederick",
"V. Jacobson"
],
"status": "July 2003. RFC",
"publisher": "IETF"
},
"RFC3551": {
"title": "RTP Profile for Audio and Video Conferences with Minimal Control",
"href": "https://datatracker.ietf.org/doc/html/rfc3551",
"authors": [
"H. Schulzrinne",
"S. Casner"
],
"status": "July 2003. RFC",
"publisher": "IETF"
},
"RFC3711": {
"title": "The Secure Real-time Transport Protocol (SRTP)",
"href": "https://datatracker.ietf.org/doc/html/rfc3711",
"authors": [
"M. Baugher",
"D. McGrew",
"M. Naslund",
"E. Carrara",
"K. Norrman"
],
"status": "March 2004. RFC",
"publisher": "IETF"
},
"RFC3890": {
"title": "A Transport Independent Bandwidth Modifier for the Session Description Protocol (SDP)",
"href": "https://datatracker.ietf.org/doc/html/rfc3890",
"authors": [
"M. Westerlund"
],
"status": "September 2004. RFC",
"publisher": "IETF"
},
"RFC4103": {
"title": "RTP Payload for Text Conversation",
"href": "https://datatracker.ietf.org/doc/html/rfc4103",
"authors": [
"G. Hellstrom",
"P. Jones"
],
"status": "June 2005. RFC",
"publisher": "IETF"
},
"RFC4585": {
"title": "Extended RTP Profile for RTCP-Based Feedback (RTP/AVPF)",
"href": "https://datatracker.ietf.org/doc/html/rfc4585",
"authors": [
"J. Ott",
"S. Wenger",
"N. Sato",
"C. Burmeister",
"J. Rey"
],
"status": "July 2006. RFC",
"publisher": "IETF"
},
"RFC4961": {
"title": "Symmetric RTP/RTC Control Protocol (RTCP)",
"href": "https://datatracker.ietf.org/doc/html/rfc4961",
"authors": [
"D. Wing"
],
"status": "July 2007. RFC",
"publisher": "IETF"
},
"RFC5104": {
"title": "Codec Control Messages in the RTP Audio-Visual Profile with Feedback (AVPF)",
"href": "https://datatracker.ietf.org/doc/html/rfc5104",
"authors": [
"S. Wenger",
"U. Chandra",
"M. Westerlund",
"B. Burman"
],
"status": "February 2008. RFC",
"publisher": "IETF"
},
"RFC5124": {
"title": "Extended Secure RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/SAVPF)",
"href": "https://datatracker.ietf.org/doc/html/rfc5124",
"authors": [
"J. Ott",
"E. Carrara"
],
"status": "February 2008. RFC",
"publisher": "IETF"
},
"RFC5450": {
"title": "Transmission Time Offsets in RTP Streams",
"href": "https://datatracker.ietf.org/doc/html/rfc5450",
"authors": [
"D. Singer",
"H. Desineni"
],
"status": "March 2009. RFC",
"publisher": "IETF"
},
"RFC5506": {
"title": "Support for Reduced-Size Real-Time Transport Control Protocol (RTCP): Opportunities and Consequences",
"href": "https://datatracker.ietf.org/doc/html/rfc5506",
"authors": [
"I. Johansson",
"M. Westerlund"
],
"status": "April 2009. RFC",
"publisher": "IETF"
},
"RFC5761": {
"title": "Multiplexing RTP Data and Control Packets on a Single Port",
"href": "https://datatracker.ietf.org/doc/html/rfc5761",
"authors": [
"C. Perkins",
"M. Westerlund"
],
"status": "April 2010. RFC",
"publisher": "IETF"
},
"RFC6051": {
"title": "Rapid Synchronisation of RTP Flows",
"href": "https://datatracker.ietf.org/doc/html/rfc6051",
"authors": [
"C. Perkins",
"T. Schierl"
],
"status": "November 2010. RFC",
"publisher": "IETF"
},
"RFC6263": {
"title": "Application Mechanism for Keeping Alive the NAT Mappings Associated with RTP / RTP Control Protocol (RTCP) Flows",
"href": "https://datatracker.ietf.org/doc/html/rfc6263",
"authors": [
"X. Marjou",
"A. Sollaud"
],
"status": "June 2011. RFC",
"publisher": "IETF"
},
"RFC6464": {
"title": "A Real-time Transport Protocol (RTP) Header Extension for Client-to-Mixer Audio Level Indication",
"href": "https://datatracker.ietf.org/doc/html/rfc6464",
"authors": [
"J. Lennox, Ed.",
"E. Ivov",
"E. Marocco"
],
"status": "December 2011. RFC",
"publisher": "IETF"
},
"RFC6465": {
"title": "A Real-time Protocol (RTP) Header Extension for Mixer-to-Client Audio Level Indication",
"href": "https://datatracker.ietf.org/doc/html/rfc6465",
"authors": [
"E. Ivov",
"E. Marocco",
"J. Lennox"
],
"status": "December 2011. RFC",
"publisher": "IETF"
},
"RFC6904": {
"title": "Encryption of Header Extensions in the SRTP",
"href": "https://datatracker.ietf.org/doc/html/rfc6904",
"authors": [
"J. Lennox"
],
"status": "April 2013. RFC",
"publisher": "IETF"
},
"RFC7022": {
"title": "Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)",
"href": "https://datatracker.ietf.org/doc/html/rfc7022",
"authors": [
"A. Begen",
"C. Perkins",
"D. Wing",
"E. Rescorla"
],
"status": "September 2013. RFC",
"publisher": "IETF"
},
"RFC7160": {
"title": "Support for Multiple Clock Rates in an RTP Session",
"href": "https://datatracker.ietf.org/doc/html/rfc7160",
"authors": [
"M. Petit-Huguenin",
"G. Zorn"
],
"status": "April 2014. RFC",
"publisher": "IETF"
},
"RFC7656": {
"title": "A Taxonomy of Semantics and Mechanisms for Real-Time Transport Protocol (RTP) Sources",
"href": "https://datatracker.ietf.org/doc/html/rfc7656",
"authors": [
"J. Lennox",
"K. Gross",
"S. Nandakumar",
"G. Salgueiro",
"B. Burman"
],
"status": "November 2015. RFC",
"publisher": "IETF"
},
"RFC8082": {
"title": "Using Codec Control Messages in the RTP Audio-Visual Profile with Feedback with Layered Codecs",
"href": "https://datatracker.ietf.org/doc/html/rfc8082",
"authors": [
"S. Wenger",
"J. Lennox",
"B. Burman"
],
"status": "March 2017. RFC",
"publisher": "IETF"
},
"RFC8108": {
"title": "Sending Multiple RTP Streams in a Single RTP Session",
"href": "https://datatracker.ietf.org/doc/html/rfc8108",
"authors": [
"J. Lennox",
"M. Westerlund",
"Q. Wu",
"C. Perkins"
],
"status": "March 2017. RFC",
"publisher": "IETF"
},
"RFC8285": {
"title": "A General Mechanism for RTP Header Extensions",
"href": "https://datatracker.ietf.org/doc/html/rfc8285",
"authors": [
"D. Singer",
"H. Desineni",
"R. Even"
],
"status": "October 2017. RFC",
"publisher": "IETF"
},
"RFC8627": {
"title": "RTP Payload Format for Flexible Forward Error Correction (FEC)",
"href": "https://datatracker.ietf.org/doc/html/rfc8627",
"authors": [
"M. Zanaty",
"V. Singh",
"A. Begen",
"G. Mandyam"
],
"status": "July 2019. RFC",
"publisher": "IETF"
},
"RFC8834": {
"title": "Media Transport and Use of RTP in WebRTC",
"href": "https://datatracker.ietf.org/doc/html/rfc8834",
"authors": [
"C. Perkins",
"M. Westerlund",
"J. Ott"
],
"status": "January 2021. RFC",
"publisher": "IETF"
},
"RFC8852": {
"title": "RTP Stream Identifier Source Description (SDES)",
"href": "https://datatracker.ietf.org/doc/html/rfc8852",
"authors": [
"A. Roach",
"S. Nandakumar",
"P. Thatcher"
],
"status": "January 2021. RFC",
"publisher": "IETF"
},
"RFC8861": {
"title": "Sending Multiple RTP Streams in a Single RTP Session: Grouping RTP Control Protocol (RTCP) Reception Statistics and Other Feedback",
"href": "https://datatracker.ietf.org/doc/html/rfc8861",
"authors": [
"J. Lennox",
"M. Westerlund",
"Q. Wu",
"C. Perkins"
],
"status": "January 2021. RFC",
"publisher": "IETF"
},
"RFC9335": {
"title": "Completely Encrypting RTP Header Extensions and Contributing Sources",
"href": "https://datatracker.ietf.org/doc/html/rfc9335",
"authors": [
"J. Uberti",
"C. Jennings",
"G. Murillo"
],
"status": "January 2023. RFC",
"publisher": "IETF"
},
"RFC9443": {
"title": "Multiplexing Scheme Updates for QUIC",
"href": "https://datatracker.ietf.org/doc/html/rfc9443",
"authors": [
"B. Aboba",
"G. Salgueiro",
"C. Perkins"
],
"status": "July 2023. RFC",
"publisher": "IETF"
}
}
</pre>
<style>
main > dl > dd {
margin-bottom: 1em;
}
table {
width: 100%;
}
table#sample-types td, table#sample-types th {
text-align: center;
}
table#sample-types .even {
background-color: lightgrey;
}
.rfc2119 {
text-transform: lowercase;
font-variant: small-caps;
font-style: normal;
}
</style>
<pre class=link-defaults>
spec:streams; type:interface; text:ReadableStream
</pre>
# Introduction # {#introduction}
*This section is non-normative.*
This specification uses [[!RFC3550]] to send and receive RTP and RTCP packets.
Note: The API presented in this specification represents a preliminary proposal
based on work-in-progress within the W3C WEBRTC WG. As a result, the API is likely
to change significantly going forward.
# Conformance # {#conformance}
As well as sections marked as non-normative, all authoring guidelines,
diagrams, examples, and notes in this specification are non-normative.
Everything else in this specification is normative.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
"SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as described in
[[!RFC2119]] and [[!RFC8174]] when, and only when, they appear in all capitals, as shown here.
This specification defines conformance criteria that apply to a single product:
the user agent that implements the interfaces that it contains.
Conformance requirements phrased as algorithms or specific steps may be
implemented in any manner, so long as the end result is equivalent. (In
particular, the algorithms defined in this specification are intended to be
easy to follow, and not intended to be performant.)
Implementations that use ECMAScript to implement the APIs defined in this
specification MUST implement them in a manner consistent with the ECMAScript
Bindings defined in the Web IDL specification [[!WEBIDL]], as this
specification uses that specification and terminology.
# Terminology # {#terminology}
Terminology definitions go here.
# RTCRtpTransport Interface # {#rtptransport}
## Internal slots ## {#internal-slots}
## Constructor ## {#constructor}
## Attributes ## {#attributes}
## Methods ## {#methods}
# Privacy and security considerations # {#privacy}
## Confidentiality of Communications ## {#confidentiality}
## State Persistence ## {#state-persistence}
## Protocol Security ## {#protocol-security}
## Fingerprinting and Tracking ## {#fingerprinting}
# Examples # {#examples}
See the [explainer document](https://github.com/w3c/webrtc-rtptransport/blob/main/explainer.md#code-examples).
# Acknowledgements # {#acknowledgements}
The editors wish to thank the WEBRTC Working Group chairs and Team Contact for their support.