-
Notifications
You must be signed in to change notification settings - Fork 0
/
rtmp-uris.txt
672 lines (434 loc) · 25.4 KB
/
rtmp-uris.txt
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
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
M. Thornburgh
2 July 2024
RTMP Family URI Schemes
Abstract
Adobe’s Real-Time Messaging Protocol (RTMP) comprises a family of
network protocols for transporting streams of time-oriented video,
audio, and data messages over IP networks. The URI schemes that are
used to identify, locate, and access streaming resources in the RTMP
family follow the URI Generic Syntax of RFC 3986, with constraints.
This memo describes the syntax constraints and the access semantics
for RTMP family URIs.
Copyright Notice
Copyright © 2023 Michael Thornburgh. All rights reserved.
Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:
The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS
BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Authority . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.1. Host and Port . . . . . . . . . . . . . . . . . . . . . . 4
4.2. Userinfo . . . . . . . . . . . . . . . . . . . . . . . . 4
Thornburgh Informational [Page 1]
RTMP URIs July 2024
5. Path and Query . . . . . . . . . . . . . . . . . . . . . . . 5
6. Fragment Identifier . . . . . . . . . . . . . . . . . . . . . 5
7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 6
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
8.1. RTMP Registration . . . . . . . . . . . . . . . . . . . . 6
8.2. RTMPS Registration . . . . . . . . . . . . . . . . . . . 8
8.3. RTMFP Registration . . . . . . . . . . . . . . . . . . . 9
9. Security Considerations . . . . . . . . . . . . . . . . . . . 11
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
10.1. Normative References . . . . . . . . . . . . . . . . . . 11
10.2. Informative References . . . . . . . . . . . . . . . . . 12
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction
Adobe’s Real-Time Messaging Protocol (RTMP) comprises a family of
network protocols for transporting streams of time-oriented video,
audio, and data messages over IP networks.
The URI schemes that are used to identify, locate, and access
streaming resources in the RTMP family follow the URI Generic Syntax
of [RFC3986], with constraints.
RTMP and its TCP-based transport (the RTMP Chunk Stream) are
described in the RTMP Specification of December 2012 [RTMP]. Errors,
omissions, and ambiguities in that specification are addressed in
RTMP Errata and Addenda [RTMP-Errata]. Coordinated interoperable
enhancements to RTMP are described in Enhanced RTMP [E-RTMP].
Transporting RTMP messages over the Secure Real-Time Media Flow
Protocol (RTMFP) [RFC7016] is described in Adobe's RTMFP Profile for
Flash Communication [RFC7425].
This memo describes the syntax constraints and the access semantics
for RTMP family URIs.
This memo does not address private or undocumented extensions to the
RTMP family for which interoperation is not desired by the extending
parties.
The primary operation for dereferencing an RTMP family URI is to
connect to the indicated origin server and its abstract _target
resource_. Neither the connection itself nor the target resource have
a "representation" or a "media type" in the senses described in RFC
3986, nor is a "retrieval" performed by connecting.
Thornburgh Informational [Page 2]
RTMP URIs July 2024
The target resource can have secondary resources, such as streams,
shared objects, and remote procedures, that can be accessed according
their kinds via the connection. For example, streams may be
published or played, shared objects updated or observed, and remote
procedures called.
2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
The terms "client", "server", "origin server", "resource", "secondary
resource", "dereference", "representation", and "media type" in this
document are to be interpreted as used or described in [RFC3986].
3. Syntax
RTMP family URIs follow the Generic Syntax of [RFC3986], with
constraints. Their syntax is described here using the Augmented
Backus-Naur Form (ABNF) [RFC5234] rules from RFC 3986, which are
incorporated by reference as though fully set forth here. The host
rule is also reproduced here for clarity in the following sections.
Note that the rtmp-authority rule defined here is compatible with the
authority rule, and rtmp-userinfo is compatible with the userinfo
rule.
rtmp-URI = "rtmp://" common
rtmps-URI = "rtmps://" common
rtmfp-URI = "rtmfp:" ["//" common]
common = rtmp-authority path-abempty ["?" query] ["#" fragment]
rtmp-authority = [rtmp-userinfo "@"] host [":" port]
rtmp-userinfo = rtmp-connect-arg *(":" rtmp-connect-arg)
rtmp-connect-arg = *(unreserved / pct-encoded / sub-delims)
host = IP-literal / IPv4address / reg-name
Thornburgh Informational [Page 3]
RTMP URIs July 2024
4. Authority
The rtmp-authority component, when present, identifies the location
of an RTMP origin server which governs a namespace of target and
secondary resources.
Note: The bare RTMFP URI form "rtmfp:" does not have an rtmp-
authority component (or any other components). All of the other URI
forms do. The bare "rtmfp:" URI is used in the APIs of some
implementations to indicate instantiation of an RTMFP client
according to [RFC7425], but without connecting to a server. Such an
instantiation might be used for pure peer-to-peer communication.
4.1. Host and Port
The host and optional port components locate the origin server in the
network. The host component of the rtmp-authority MUST NOT be empty.
For an rtmp-URI, the host and optional port identify a potential
origin server listening for TCP [RFC0793] connections, over which
RTMP messages are to be sent using the RTMP Chunk Stream as described
in the RTMP Specification [RTMP]. If the port is empty or not given,
TCP port 1935 is the default.
For an rtmps-URI, the host and optional port identify a potential
origin server listening for TCP connections and capable of
establishing a TLS [RFC8446] connection secured for RTMP Chunk Stream
communication [RTMP]. "Secured" means a connection that is
authenticated, confidential, and integrity-protected in a manner
acceptable to both the client and server. If the port is empty or
not given, TCP port 443 is the default.
For an rtmfp-URI where the rtmp-authority is present, the host and
optional port identify one or more initial candidate addresses with
which to initiate an RTMFP [RFC7016] connection according to
[RFC7425]. The UDP [RFC0768] port for the initial candidate
addresses, if empty or not specified, is 1935. If host is a reg-
name, the initial candidate address set SHOULD comprise all IPv4 and
IPv6 addresses to which reg-name resolves.
4.2. Userinfo
When connecting to an RTMP server, the connect command
(Section 7.2.1.1 of [RTMP]) can accept or expect additional arguments
following the _Command Object_. The number and types of the
additional arguments, their interpretation, and whether they are
expected is implementation-specific and is the prerogative of the
server.
Thornburgh Informational [Page 4]
RTMP URIs July 2024
Often the server expects one or more string arguments to the connect
command following the _Command Object_, for example a developer key,
a user name and password, or implementation-specific connection
properties.
If the rtmp-authority contains an rtmp-userinfo component, and in the
absence of other arrangements between the client and server, the
rtmp-userinfo SHOULD be interpreted as a ":" (COLON) separated
sequence of potentially empty rtmp-connect-arg strings (as
illustrated in the ABNF) to be sent as string arguments to the
connect command following the _Command Object_. Each rtmp-connect-arg
SHOULD be percent-decoded before being sent.
Clients SHOULD remove the rtmp-userinfo component from the URI when
sending it as the tcUrl property of the connect command’s _Command
Object_ or in the Ancillary Data option of an RTMFP Endpoint
Discriminator (Section 4.4.2.2 of [RFC7425]).
5. Path and Query
The path-abempty and query components identify the abstract _target
resource_ within the origin server’s namespace. The meaning of
"target resource" is implementation-specific and is the prerogative
of the origin server.
Interoperability Note: Some client implementations incorrectly
presume the server’s interpretation of the path-abempty component of
the URI, specifically by presuming the number of path segments that
identify the target resource. These clients then incorrectly
interpret the remaining path segments of the original URI as
identifying a secondary resource (such as the name of a stream to
play or publish via the connection to the target resource). This
behavior is not in keeping with the spirit of URIs (particularly that
the authority governs its namespace), is not interoperable, and is
NOT RECOMMENDED. Such secondary resources, when encoded in a URI,
should instead be identified by the fragment identifier as described
in the next section.
6. Fragment Identifier
Section 3.5 of [RFC3986] describes the fragment component of a
generic URI as allowing "indirect identification of a secondary
resource by reference to a primary resource and additional
identifying information".
Since an RTMP connection to a target resource has neither a
"representation" nor a "media type", the semantics of the fragment
component are unconstrained according to that section.
Thornburgh Informational [Page 5]
RTMP URIs July 2024
Often an RTMP client connects to a server to perform a specific
operation on a specific secondary resource, such as to publish to or
play from a named stream. In cases where the kind of secondary
resource and the intended operation are unambiguous, and in the
absence of other arrangements between the client and server, the
secondary resource MAY be identified by the fragment component. The
fragment SHOULD be percent-decoded before being used in secondary
resource APIs (for example in a stream play command).
Clients SHOULD remove the fragment component from the URI when
sending it as the tcUrl property of the connect command’s _Command
Object_ or in the Ancillary Data option of an RTMFP Endpoint
Discriminator (Section 4.4.2.2 of [RFC7425]).
7. Examples
rtmp://server.example/three/segment/path
rtmp://server.example/three/segment/path#BigBuckBunny
rtmp://[2001:db8:1::2]:19350/something?else
rtmps://server.example/something?else#CosmosLaundromat?aFlag
rtmps://arg1:arg2::[email protected]:1943
rtmps://name=Mike;pri=5;exi=3600:[email protected]/path#Caves
rtmfp://:[email protected]/two/segments?key=value&flag
rtmfp://arg%3Aone:[email protected]/something#BigBuck%42unny
rtmfp:
8. IANA Considerations
A future version of this memo will request of the IANA to update the
URI Scheme Registry [SCHEMES] for the following schemes.
8.1. RTMP Registration
This section will request an update to the rtmp provisional scheme
registration.
Scheme Name: rtmp
Status: provisional
URI scheme syntax:
rtmp-URI = "rtmp://" common
common = rtmp-authority path-abempty ["?" query] ["#" fragment]
rtmp-authority = [rtmp-userinfo "@"] host [":" port]
Thornburgh Informational [Page 6]
RTMP URIs July 2024
rtmp-userinfo = rtmp-connect-arg *(":" rtmp-connect-arg)
rtmp-connect-arg = *(unreserved / pct-encoded / sub-delims)
URI scheme semantics: This provides location information for the
RTMP server to which to connect, and identifies a target resource
and an optional secondary resource in the namespace of the server.
The host component of the authority MUST NOT be empty. The host
and optional port components of the authority identify a potential
origin server listening for TCP connections, over which RTMP
messages are to be sent using the RTMP Chunk Stream as described
in the RTMP Specification (as amended). If port is empty or not
given, TCP port 1935 is the default.
See the RTMP Family URI Schemes memo for more specific information
regarding the semantics of this URI scheme.
Encoding considerations: The rtmp-userinfo, path-abempty, query, and
fragment components represent textual data consisting of
characters from the Universal Character Set. These components
SHOULD be encoded according to Section 2.5 of RFC 3986.
Applications/protocols that use this URI scheme name: Computer
program products that use Adobe's Real-Time Messaging Protocol
(RTMP) to transport streams of time-oriented video, audio, and
data messages over IP networks.
Interoperability considerations: This scheme requires use of RTMP
and the RTMP Chunk Stream as defined by the RTMP Specification (as
amended).
Security considerations: See the Security Considerations sections in
RTMP Errata and Addenda and in RTMP Family URI Schemes.
Contact: Michael Thornburgh, <[email protected]>.
Author/Change controller: Michael Thornburgh, <[email protected]>.
References:
Parmar, H., Ed. and M. Thornburgh, Ed., "Adobe's Real Time
Messaging Protocol" ("RTMP Specification"), December 2012,
<https://veovera.org/docs/legacy/rtmp-v1-0-spec.pdf>.
Thornburgh, M., "RTMP Errata and Addenda", July 2024,
<https://zenomt.github.io/rtmp-errata-addenda/>.
Thornburgh, M., "RTMP Family URI Schemes", July 2024,
<https://zenomt.github.io/rtmp-errata-addenda/rtmp-uris/>.
Thornburgh Informational [Page 7]
RTMP URIs July 2024
Lozben, S., "Enhanced RTMP", June 2024, <https://veovera.org/>.
8.2. RTMPS Registration
This section will request provisional registration of the rtmps
scheme.
Scheme Name: rtmps
Status: provisional
URI scheme syntax:
rtmps-URI = "rtmps://" common
common = rtmp-authority path-abempty ["?" query] ["#" fragment]
rtmp-authority = [rtmp-userinfo "@"] host [":" port]
rtmp-userinfo = rtmp-connect-arg *(":" rtmp-connect-arg)
rtmp-connect-arg = *(unreserved / pct-encoded / sub-delims)
URI scheme semantics: This provides location information for the
secure RTMP server to which to connect, and identifies a target
resource and an optional secondary resource in the namespace of
the server. The host component of the authority MUST NOT be
empty. The host and optional port components of the authority
identify a potential origin server listening for TCP connections
and capable of establishing a TLS connection secured for RTMP
Chunk Stream communication, over which RTMP messages are to be
sent using the RTMP Chunk Stream as described in the RTMP
Specification (as amended). If port is empty or not given, TCP
port 443 is the default.
See the RTMP Family URI Schemes memo for more specific information
regarding the semantics of this URI scheme.
Encoding considerations: The rtmp-userinfo, path-abempty, query, and
fragment components represent textual data consisting of
characters from the Universal Character Set. These components
SHOULD be encoded according to Section 2.5 of RFC 3986.
Applications/protocols that use this URI scheme name: Computer
program products that use Adobe's Real-Time Messaging Protocol
(RTMP) to securely transport streams of time-oriented video,
audio, and data messages over IP networks.
Interoperability considerations: This scheme requires use of RTMP
Thornburgh Informational [Page 8]
RTMP URIs July 2024
and the RTMP Chunk Stream as defined by the RTMP Specification (as
amended) over TLS.
Security considerations: See the Security Considerations sections in
RTMP Errata and Addenda and in RTMP Family URI Schemes.
Contact: Michael Thornburgh, <[email protected]>.
Author/Change controller: Michael Thornburgh, <[email protected]>.
References:
Parmar, H., Ed. and M. Thornburgh, Ed., "Adobe's Real Time
Messaging Protocol" ("RTMP Specification"), December 2012,
<https://veovera.org/docs/legacy/rtmp-v1-0-spec.pdf>.
Thornburgh, M., "RTMP Errata and Addenda", July 2024,
<https://zenomt.github.io/rtmp-errata-addenda/>.
Thornburgh, M., "RTMP Family URI Schemes", July 2024,
<https://zenomt.github.io/rtmp-errata-addenda/rtmp-uris/>.
Lozben, S., "Enhanced RTMP", June 2024, <https://veovera.org/>.
8.3. RTMFP Registration
This section will request an update to the rtmfp provisional scheme
registration.
Scheme Name: rtmfp
Status: provisional
URI scheme syntax:
rtmfp-URI = "rtmfp:" ["//" common]
common = rtmp-authority path-abempty ["?" query] ["#" fragment]
rtmp-authority = [rtmp-userinfo "@"] host [":" port]
rtmp-userinfo = rtmp-connect-arg *(":" rtmp-connect-arg)
rtmp-connect-arg = *(unreserved / pct-encoded / sub-delims)
URI scheme semantics: The scheme-only form is used in the APIs of
some implementations to indicate instantiation of an RTMFP client
according to RFC 7425, but without connecting to a server. Such
an instantiation might be used for pure peer-to-peer
communication.
Thornburgh Informational [Page 9]
RTMP URIs July 2024
The full form provides location information for the RTMFP server
to which to connect, and identifies a target resource and an
optional secondary resource in the namespace of the server.
Connections are made using RTMFP (RFC 7016) as described by RFC
7425. The host component of the authority MUST NOT be empty. If
host is a reg-name, the initial candidate address set SHOULD
comprise all IPv4 and IPv6 addresses to which reg-name resolves.
The UDP port for the initial candidate addresses for the server,
if not specified, is 1935.
See the RTMP Family URI Schemes memo for more specific information
regarding the semantics of this URI scheme.
Encoding considerations: The rtmp-userinfo, path-abempty, query, and
fragment components represent textual data consisting of
characters from the Universal Character Set. These components
SHOULD be encoded according to Section 2.5 of RFC 3986.
Applications/protocols that use this URI scheme name: Computer
program products that use Adobe's Secure Real-Time Media Flow
Protocol (RTMFP) according to RFC 7425 to transport streams of
time-oriented video, audio, and data messages over IP networks.
Interoperability considerations: This scheme requires use of RTMFP
as defined by RFC 7016 in the manner described by RFC 7425.
Security considerations: See the Security Considerations sections of
RFC 7016, RFC 7425, and RTMP Errata and Addenda.
Contact: Michael Thornburgh, <[email protected]>.
Author/Change controller: Michael Thornburgh, <[email protected]>.
References:
Thornburgh, M., "Adobe's Secure Real-Time Media Flow Protocol",
RFC 7016, November 2013.
Thornburgh, M., "Adobe's RTMFP Profile for Flash
Communication", RFC 7425, December 2014.
Thornburgh, M., "RTMP Errata and Addenda", July 2024,
<https://zenomt.github.io/rtmp-errata-addenda/>.
Thornburgh, M., "RTMP Family URI Schemes", July 2024,
<https://zenomt.github.io/rtmp-errata-addenda/rtmp-uris/>.
Thornburgh Informational [Page 10]
RTMP URIs July 2024
9. Security Considerations
Several. See the Security Considerations sections of [RFC7016],
[RFC7425], and [RTMP-Errata].
Many of the security considerations of [RFC9110] also apply to RTMP.
10. References
10.1. Normative References
[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
DOI 10.17487/RFC0768, August 1980,
<https://www.rfc-editor.org/info/rfc768>.
[RFC0793] Postel, J., "Transmission Control Protocol", RFC 793,
DOI 10.17487/RFC0793, September 1981,
<https://www.rfc-editor.org/info/rfc793>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, DOI 10.17487/RFC3986, January 2005,
<https://www.rfc-editor.org/info/rfc3986>.
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234,
DOI 10.17487/RFC5234, January 2008,
<https://www.rfc-editor.org/info/rfc5234>.
[RFC7016] Thornburgh, M., "Adobe's Secure Real-Time Media Flow
Protocol", RFC 7016, DOI 10.17487/RFC7016, November 2013,
<https://www.rfc-editor.org/info/rfc7016>.
[RFC7425] Thornburgh, M., "Adobe's RTMFP Profile for Flash
Communication", RFC 7425, DOI 10.17487/RFC7425, December
2014, <https://www.rfc-editor.org/info/rfc7425>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
Thornburgh Informational [Page 11]
RTMP URIs July 2024
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc8446>.
[RTMP] Parmar, H., Ed. and M. Thornburgh, Ed., "Adobe’s Real Time
Messaging Protocol", December 2012,
<https://veovera.org/docs/legacy/rtmp-v1-0-spec.pdf>.
10.2. Informative References
[E-RTMP] Lozben, S., "Enhanced RTMP", June 2024,
<https://veovera.org/>.
[RFC9110] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
Ed., "HTTP Semantics", STD 97, RFC 9110,
DOI 10.17487/RFC9110, June 2022,
<https://www.rfc-editor.org/info/rfc9110>.
[RTMP-Errata]
Thornburgh, M., "RTMP Errata and Addenda", July 2024,
<https://zenomt.github.io/rtmp-errata-addenda/>.
[SCHEMES] Internet Assigned Numbers Authority, "Uniform Resource
Identifier (URI) Schemes",
<https://www.iana.org/assignments/uri-schemes/>.
Author's Address
Michael C. Thornburgh
Santa Cruz, CA 95060-1950
United States of America
Email: [email protected]
URI: https://zenomt.zenomt.com/card#me
Thornburgh Informational [Page 12]