[Docs] [txt|pdf] [draft-ietf-mmus ] [Tracker] [Diff1] [Diff2] [IPR] [Errata] Obsoleted by : PROPOSED STANDARD Errata Exist Network Working Group H. Canonical URL: terney.info; File formats: icon for text file icon for PDF icon for HTML; Status: PROPOSED STANDARD; Obsoleted. RFC; Real Time Streaming Protocol (RTSP). edit . terney.info rfc 1 reference. stated in terney.info

Language:English, Spanish, French
Published (Last):17.01.2016
Distribution:Free* [*Registration Required]
Uploaded by: VANITA

54713 downloads 126824 Views 39.59MB ePub Size Report

Rfc 2326 Epub Download

RFC , updated in July by RFC RTP: A Transport Protocol for Real- .. RTSP, defined in RFC , is an application-level r protocol that enables. ePub File Size: Mb. ISBN: Downloads: Rfc useful information describing the “Quality” of the document: Indicates the. This memorandum is a revision of RFC , which is currently a Proposed choosing delivery mechanisms based upon RTP (RFC ).

Shalkree Header type support methods Accept R opt. It may also give an indication about the timeline of the movie. For aggregate control, a particular stream may not actually generate a packet for the Range time value rfc or implied. In addition, it also removes state ambiguity when ffc client requires features that the server does not understand. However, if a group of caches is being operated as a unified system with good internal connectivity, such a request MAY be forwarded within that group of rfc That is, the client wants a response that will rfc be fresh for at least the specified number of seconds. RFC Data where there is a timing frc between source and sink; that is, the sink must rfc the timing relationship that existed at the source.

These conferences are created by protocols outside the scope of this specification, e. Instead of the RTSP client explicitly providing transport information, for example, it asks the media server to use the values in the conference description instead. Linear white space must be URL-escaped. See Section The time code has the format hours:minutes:seconds:frames. For the "frames" field in the time value can assume the values 0 through The difference between 30 and If the frame value is zero, it may be omitted.

Subframes are measured in one-hundredth of a frame. The timestamp consists of a decimal fraction. The part left of the decimal may be expressed in either seconds or hours, minutes, and seconds. The part right of the decimal point measures fractions of a second. The beginning of a presentation corresponds to 0. Negative values are not defined. The special constant now is defined as the current instant of a live event.

It may be used only for live events. It is often digitally displayed on a VCR. The npt-sec notation is optimized for automatic generation, the ntp-hhmmss notation for consumption by human readers. The "now" constant allows clients to request to Schulzrinne, et. This is needed since neither absolute time nor zero time are appropriate for this case.

Fractions of a second may be indicated. These tags are used in Require Section The name MUST not contain any spaces, control characters or periods. Text-based protocols make it easier to add optional parameters in a self-describing manner.

Since the number of parameters and the frequency of commands is low, processing efficiency is not a concern. Text-based protocols, if done carefully, also allow easy implementation of research prototypes in scripting languages such as Tcl, Visual Basic and Perl.

This is also the encoding used for RTCP. ISO translates directly into Unicode with a high-order octet of zero. ISO characters with the most-significant bit set are represented as x 10xxxxxx. Requests contain methods, the object the method is operating upon and parameters to further describe the method.

Methods are idempotent, unless otherwise noted.

CLI Book 2: Cisco ASA Series Firewall CLI Configuration Guide, 9.3

Methods are also designed to require little or no state maintenance at the media server. Any response message which MUST NOT include a message body such as the 1xx, , and responses is always terminated by the first empty line after the header fields, regardless of the entity-header fields present in the message.

If a Content-Length header field section If this header field is not present, a value of zero is assumed. By the server closing the connection.

Closing the connection cannot be used to indicate the end of a request body, since that would leave no possibility for the server to send back a response. Given the moderate length of presentation descriptions returned, the server should always be able to determine its length, even if it is generated dynamically, making the chunked transfer encoding unnecessary.

Even though Content-Length must be present if there is any entity body, the rules ensure reasonable behavior even if the length is not given explicitly. The valid response codes and the methods they can be used with are defined in Table 1. After receiving and interpreting a request message, the recipient responds with an RTSP response message.

These codes are fully defined in Section The Reason-Phrase is intended to give a short textual description of the Status-Code. The Status-Code is intended for use by automata and the Reason-Phrase is intended for the human user.

The client is not required to examine or display the Reason- Phrase. The last two digits do not have any categorization role.

The reason phrases listed here are only recommended - they may be replaced by local equivalents without affecting the protocol. RTSP applications are not required to understand the meaning of all registered status codes, though such understanding is obviously desirable.

However, applications MUST understand the class of any status code, as indicated by the first digit, and treat any unrecognized response as being equivalent to the x00 status code of that class, with the exception that an unrecognized response MUST NOT be cached. For example, if an unrecognized status code of is received by the client, it can safely assume that there was something wrong with its request and treat the response as if it had received a status code. In such cases, user agents SHOULD present to the user the entity returned with the response, since that entity is likely to include human- readable information which will explain the unusual status.

Information on RFC » RFC Editor

These header fields give information about the server and about further access to the resource identified by the Request-URI. However, new or experimental header fields MAY be given the semantics of response- header fields if all parties in the communication recognize them to be response-header fields.

Unrecognized header fields are treated as entity-header fields. An entity consists of entity-header fields and an entity-body, although some responses will only include the entity-headers.

In this section, both sender and recipient refer to either the client or the server, depending on who sends and who receives the entity.

For the scheme "rtsp", a persistent connection is assumed, while the scheme "rtspu" calls for RTSP requests to be sent without setting up a connection. However, this is only supported for persistent connections, as the media server otherwise has no reliable way of reaching the client. Also, this is the only way that requests from media server to client are likely to traverse firewalls.

A server MUST send its responses to those requests in the same order that the requests were received. If there is no acknowledgement, the sender may resend the same message after a timeout of one round-trip time RTT. If both the underlying reliable transport such as TCP and the RTSP application retransmit requests, it is possible that each packet loss results in two retransmissions. The receiver cannot typically take advantage of the application-layer retransmission since the Schulzrinne, et.

Standards Track [Page 28] RFC Real Time Streaming Protocol April transport stack will not deliver the application-layer retransmission before the first attempt has reached the receiver.

If the packet loss is caused by congestion, multiple retransmissions at different layers will exacerbate the congestion.

The Timestamp header Section Each request carries a sequence number in the CSeq header Section If a request is repeated because of lack of acknowledgement, the request MUST carry the original sequence number i. Otherwise, an RTSP packet is terminated with an empty line immediately following the last message header. The method is case-sensitive. New methods may be defined in the future.

Methods are summarized in Table 2. RTSP can also control multiple streams as a single entity. When the must-revalidate directive is present in a SETUP response received by a cache, that cache MUST NOT the entry after it becomes stale to respond to a subsequent request without first revalidating ietv with the origin server. A server MAY refuse to change parameters of an existing stream. The may be applied on a stream URL. It should be silently ignored if sent. The response MUST ieft the actual scale value chosen by the server.

The block size MUST be a positive decimal number, measured in octets. Within RTSP, redirection may be used for load balancing or redirecting stream requests to a server topologically closer to the client.

See Table 1 for a listing of which status codes may be returned by which requests. Indicates the RTP timestamp corresponding to the time value in the Range response header.

CLI Book 2: Cisco ASA Series Firewall CLI Configuration Guide, 9.8

The purpose of this field is to strictly inform the recipient of valid methods associated with the resource. September Learn how and when to remove this template message. By using this site, you agree to the Terms of Use and Privacy Policy. The two major functions of H. Because H. Dynamically allocate the negotiated H. The H. How H. As part of the call setup process, the H.

In environments where H. If the H.

Note The H. Within each H.

You might also like: OPPOSITION LUX EPUB

Additionally, you must permit traffic for the well-known H. When an H. After inspecting the H. All H.

Related articles:

Copyright © 2019 terney.info.
DMCA |Contact Us