Real-Time Streaming Protocol (RTSP) 2.0 Parameters
Created
- 2014-02-21
Last Updated
- 2024-05-20
Available Formats
Feature-tags
Registration Procedure(s)
- First Come First Served
Reference
- RFC 7826: Real-Time Streaming Protocol Version 2.0
Note
Proprietary feature-tags should begin with a vendor "prefix" followed by a "."
Available Formats
| Name | Description | Reference |
|---|---|---|
| play.basic | The implementation for delivery and playback operations according to the core RTSP specification, as defined in this memo. Applies for clients, servers, and proxies. See Section 11.1 of RFC 7826 | RFC 7826 |
| play.scale | Support of scale operations for media playback. Applies only for servers. See Section 18.46 of RFC 7826. | RFC 7826 |
| play.speed | Support of the speed functionality for media delivery. Applies only for servers. See Section 18.50 of RFC 7826. | RFC 7826 |
| setup.rtp.rtcp.mux | Support of the RTP and RTCP multiplexing as discussed in Appendix C.1.6.4 of RFC 7826. Applies for both client and servers and any media caching proxy. | RFC 7826 |
| setup.ice-d-m | A feature tag representing the support of the ICE-based establishment of datagram media transport that is capable of transport establishment through NAT and firewalls. This feature tag applies to clients, servers, and proxies and indicates support of all the mandatory functions of this specification. | RFC 7825 |
RTSP 2.0 Methods
Registration Procedure(s)
- Standards Action
Reference
- RFC 7826: Real-Time Streaming Protocol Version 2.0
Available Formats
RTSP 2.0 Status Codes
Registration Procedure(s)
- IETF Review
Reference
- RFC 7826: Real-Time Streaming Protocol Version 2.0
Note
For every set of 100 values (e.g. 100-199, 200-299, etc.), values x50-x99 should be assigned first, except when adopting an HTTP extension to RTSP.
Available Formats
| Status Code | Description | Reference |
|---|---|---|
| 100 | Continue | RFC 7826 |
| 150 | Server still working on ICE connectivity checks | RFC 7825 |
| 200 | OK | RFC 7826 |
| 301 | Moved Permanently | RFC 7826 |
| 302 | Found | RFC 7826 |
| 303 | See Other | RFC 7826 |
| 304 | Not Modified | RFC 7826 |
| 305 | Use Proxy | RFC 7826 |
| 400 | Bad Request | RFC 7826 |
| 401 | Unauthorized | RFC 7826 |
| 402 | Payment Required | RFC 7826 |
| 403 | Forbidden | RFC 7826 |
| 404 | Not Found | RFC 7826 |
| 405 | Method Not Allowed | RFC 7826 |
| 406 | Not Acceptable | RFC 7826 |
| 407 | Proxy Authentication Required | RFC 7826 |
| 408 | Request Time-Out | RFC 7826 |
| 410 | Gone | RFC 7826 |
| 412 | Precondition Failed | RFC 7826 |
| 413 | Request Message Body Too Large | RFC 7826 |
| 414 | Request-URI Too Large | RFC 7826 |
| 415 | Unsupported Media Type | RFC 7826 |
| 451 | Parameter Not Understood | RFC 7826 |
| 452 | Reserved | RFC 7826 |
| 453 | Not Enough Bandwidth | RFC 7826 |
| 454 | Session Not Found | RFC 7826 |
| 455 | Method Not Valid in This State | RFC 7826 |
| 456 | Header Field Not Valid for Resource | RFC 7826 |
| 457 | Invalid Range | RFC 7826 |
| 458 | Parameter Is Read-Only | RFC 7826 |
| 459 | Aggregate operation not allowed | RFC 7826 |
| 460 | Only aggregate operation allowed | RFC 7826 |
| 461 | Unsupported Transport | RFC 7826 |
| 462 | Destination Unreachable | RFC 7826 |
| 463 | Destination Prohibited | RFC 7826 |
| 464 | Data Transport Not Ready Yet | RFC 7826 |
| 465 | Notification Reason Unknown | RFC 7826 |
| 466 | Key Management Error | RFC 7826 |
| 470 | Connection Authorization Required | RFC 7826 |
| 471 | Connection Credentials not accepted | RFC 7826 |
| 472 | Failure to establish secure connection | RFC 7826 |
| 480 | ICE Connectivity check failure | RFC 7825 |
| 500 | Internal Server Error | RFC 7826 |
| 501 | Not Implemented | RFC 7826 |
| 502 | Bad Gateway | RFC 7826 |
| 503 | Service Unavailable | RFC 7826 |
| 504 | Gateway Time-out | RFC 7826 |
| 505 | RTSP Version not supported | RFC 7826 |
| 551 | Option not supported | RFC 7826 |
| 553 | Proxy Unavailable | RFC 7826 |
RSTP 2.0 Headers
Registration Procedure(s)
- Expert Review
Expert(s)
- Martin Stiemerling
Reference
- RFC 7826: Real-Time Streaming Protocol Version 2.0
Available Formats
| Name | Reference |
|---|---|
| 3GPP-Adaptation | TS-26234; RFC 7826 |
| 3GPP-Link-Char | TS-26234; RFC 7826 |
| 3GPP-QoE-Feedback | TS-26234; RFC 7826 |
| 3GPP-QoE-Metrics | TS-26234; RFC 7826 |
| 3gpp-videopostdecbufsize | TS-26234; RFC 7826 |
| Accept | RFC 7826 |
| Accept-Credentials | RFC 7826 |
| Accept-Encoding | RFC 7826 |
| Accept-Language | RFC 7826 |
| Accept-Ranges | RFC 7826 |
| Allow | RFC 7826 |
| Authentication-Info | RFC 7826 |
| Authorization | RFC 7826 |
| Bandwidth | RFC 7826 |
| Blocksize | RFC 7826 |
| Cache-Control | RFC 7826 |
| Connection | RFC 7826 |
| Connection-Credentials | RFC 7826 |
| Content-Base | RFC 7826 |
| Content-Encoding | RFC 7826 |
| Content-Language | RFC 7826 |
| Content-Length | RFC 7826 |
| Content-Location | RFC 7826 |
| Content-Type | RFC 7826 |
| CSeq | RFC 7826 |
| Date | RFC 7826 |
| Expires | RFC 7826 |
| From | RFC 7826 |
| If-Match | RFC 7826 |
| If-None-Match | RFC 7826 |
| Last-Modified | RFC 7826 |
| Location | RFC 7826 |
| Media-Properties | RFC 7826 |
| Media-Range | RFC 7826 |
| MTag | RFC 7826 |
| Notify-Reason | RFC 7826 |
| Pipelined-Requests | RFC 7826 |
| Proxy-Authenticate | RFC 7826 |
| Proxy-Authorization | RFC 7826 |
| Proxy-Require | RFC 7826 |
| Proxy-Supported | RFC 7826 |
| Public | RFC 7826 |
| Range | RFC 7826 |
| Referrer | RFC 7826 |
| Request-Status | RFC 7826 |
| Require | RFC 7826 |
| Retry-After | RFC 7826 |
| RTP-Info | RFC 7826 |
| Scale | RFC 7826 |
| Seek-Style | RFC 7826 |
| Server | RFC 7826 |
| Session | RFC 7826 |
| Speed | RFC 7826 |
| Supported | RFC 7826 |
| Terminate-Reason | RFC 7826 |
| Timestamp | RFC 7826 |
| Transport | RFC 7826 |
| Unsupported | RFC 7826 |
| User-Agent | RFC 7826 |
| Via | RFC 7826 |
| WWW-Authenticate | RFC 7826 |
| x-initpredecbufperiod | TS-26234; RFC 7826 |
| x-predecbufsize | TS-26234; RFC 7826 |
| x-wap-profile | TS-26234; RFC 7826 |
| x-wap-profile-diff | TS-26234; RFC 7826 |
| x-wap-profile-warning | TS-26234; RFC 7826 |
Accept-Credentials Policies
Registration Procedure(s)
- Standards Action
Reference
- RFC 7826: Real-Time Streaming Protocol Version 2.0
Available Formats
| Name | Description | Reference |
|---|---|---|
| Any | A policy requiring the proxy to accept any received certificate. | RFC 7826 |
| Proxy | A policy where the proxy applies its own policies to determine which certificates are accepted. | RFC 7826 |
| User | A policy where the certificate is required to be forwarded down the proxy chain to the client, thus allowing the user to decided to accept or refuse a certificate. | RFC 7826 |
Accept-Credentials Hash Algorithms
Registration Procedure(s)
- Standards Action
Reference
- RFC 7826: Real-Time Streaming Protocol Version 2.0
Available Formats
| Hash Alg. ID | Reference |
|---|---|
| sha-256 | RFC 7826 |
Cache-Control Cache Directive Extensions
Registration Procedure(s)
- Standards Action or IESG Approval
Reference
- RFC 7826: Real-Time Streaming Protocol Version 2.0
Available Formats
Media Properties
Registration Procedure(s)
- Specification Required
Expert(s)
- Martin Stiemerling
Reference
- RFC 7826: Real-Time Streaming Protocol Version 2.0
Available Formats
Notify-Reason Values
Registration Procedure(s)
- Specification Required
Expert(s)
- Martin Stiemerling
Reference
- RFC 7826: Real-Time Streaming Protocol Version 2.0
Available Formats
| Name | Description | Reference |
|---|---|---|
| end-of-stream | This Notify-Reason value indicates the end of a media stream. | RFC 7826 |
| media-properties-update | This Notify-Reason value allows the server to indicate that the properties of the media have changed during the playout. | RFC 7826 |
| scale-change | This Notify-Reason value allows the server to notify the client about a change in the Scale of the media. | RFC 7826 |
| ice-restart | This Notify-Reason value allows the server to notify the client about the need for an ICE restart. See Section 4.6 of RFC 7825. | RFC 7825 |
Range Header Formats
Registration Procedure(s)
- Specification Required
Expert(s)
- Martin Stiemerling
Reference
- RFC 7826: Real-Time Streaming Protocol Version 2.0
Available Formats
Terminate-Reason Redirect Reasons
Registration Procedure(s)
- Expert Review
Expert(s)
- Martin Stiemerling
Reference
- RFC 7826: Real-Time Streaming Protocol Version 2.0
Available Formats
Terminate-Reason Header Parameters
Registration Procedure(s)
- Specification Required
Expert(s)
- Martin Stiemerling
Reference
- RFC 7826: Real-Time Streaming Protocol Version 2.0
Available Formats
RTP-Info Header Parameters
Registration Procedure(s)
- Specification Required
Expert(s)
- Martin Stiemerling
Reference
- RFC 7826: Real-Time Streaming Protocol Version 2.0
Available Formats
Seek-Style Policies
Registration Procedure(s)
- Specification Required
Expert(s)
- Martin Stiemerling
Reference
- RFC 7826: Real-Time Streaming Protocol Version 2.0
Available Formats
| Name | Description | Reference |
|---|---|---|
| RAP | Using the closest Random Access Point prior to or at the requested start position. | RFC 7826 |
| CoRAP | Conditional Random Access Point is like RAP, but only if the RAP is closer prior to the requested start position than current pause point. | RFC 7826 |
| First-Prior | The first-prior policy will start delivery with the media unit that has a playout time first prior to the requested start position. | RFC 7826 |
| Next | The next media units after the provided start position. | RFC 7826 |
Transport Protocol Identifier
Registration Procedure(s)
- Specification Required
Expert(s)
- Martin Stiemerling
Reference
- RFC 7826: Real-Time Streaming Protocol Version 2.0
Available Formats
| ID String | Reference |
|---|---|
| RTP/AVP | RFC 7826 |
| RTP/AVP/UDP | RFC 7826 |
| RTP/AVPF | RFC 7826 |
| RTP/AVPF/UDP | RFC 7826 |
| RTP/SAVP | RFC 7826 |
| RTP/SAVP/UDP | RFC 7826 |
| RTP/SAVPF | RFC 7826 |
| RTP/SAVPF/UDP | RFC 7826 |
| RTP/AVP/TCP | RFC 7826 |
| RTP/AVPF/TCP | RFC 7826 |
| RTP/SAVP/TCP | RFC 7826 |
| RTP/SAVPF/TCP | RFC 7826 |
| RTP/AVP/D-ICE | RFC 7825 |
| RTP/AVPF/D-ICE | RFC 7825 |
| RTP/SAVP/D-ICE | RFC 7825 |
| RTP/SAVPF/D-ICE | RFC 7825 |
Transport Modes
Registration Procedure(s)
- Standards Action
Reference
- RFC 7826: Real-Time Streaming Protocol Version 2.0
Available Formats
| Value | Reference |
|---|---|
| PLAY | RFC 7826 |
Transport Parameters
Registration Procedure(s)
- Specification Required
Expert(s)
- Martin Stiemerling
Reference
- RFC 7826: Real-Time Streaming Protocol Version 2.0