protocol failures

Upload: naivedya-mishra

Post on 29-May-2018

221 views

Category:

Documents


0 download

TRANSCRIPT

  • 8/8/2019 Protocol Failures

    1/2

    Protocol:Protocol is Predefined Set Of Rules. Protocol is used to transferthe data from one computer to another computer.

    Protocol Failures:It means that Changing the Set of Rules/Functionality of Layers.Going to the lower level programming & changing the Set ofRules/Functionality of Layers so it might leak the Information or

    Corrupt the data.

    Different Forms:

    HTTP :The latest version of HTTP. The goal of HTTP/1.1 is to support thewide diversity of configurations already deployed while introducingprotocol constructs that meet the needs of those who build webapplications that require high reliability and, failing that, at leastreliable indications of failure.

    TCP/IP :Transfer Control Protocol/Internet Protocol is used to transfer thedata from one computer to another computer. It takes cares oferrors as well as information leakage during the transformation.

    RTP :RTP (Real-Time Transport Protocol) is an Internet protocol fortransmitting real-time data such as audio and video. RTP itself doesnot guarantee real-time delivery of data, but it does providemechanisms for the sending and receiving applications to supportstreaming data. Typically, RTP runs on top of the UDP protocol,although the specification is general enough to support othertransport protocols.

    RTSP State :RTSP controls a stream which may be sent via a separate protocol,independent of the control channel. For example, RTSP control mayoccur on a TCP connection while the data flows via UDP. Thus, datadelivery continues even if no RTSP requests are received by themedia server. Also, during its lifetime, a single media stream maybe controlled by RTSP requests issued sequentially on different TCP

    connections. Therefore, the server needs to maintain "sessionstate" to be able to correlate RTSP requests with a stream definingthe allocation and usage of stream resources on the server:SETUP, PLAY, RECORD, PAUSE, and TEARDOWN.

    Example:Example 1: Media on Demand (Unicast)Client C requests a movie from media servers A(audio.example.com) and V (video.example.com). The mediadescription is stored on a web server W. The mediadescription contains descriptions of the presentation and all its

    streams, including the codecs that are available, dynamic RTPpayload types, the protocol stack, and content information such as

    1 | P a g e

  • 8/8/2019 Protocol Failures

    2/2

    language or copyright restrictions. It may also give an indicationabout the timeline of the movie. In this example, the client is only

    interested in the last part of the movie. In the first instance offailure, the client tries to pause one stream (in this case video) ofthe presentation. This is disallowed for that presentation by theserver.

    Example 2: Streaming of a Container fileFor purposes of this example, a container file is a storage entity inwhich multiple continuous media types pertaining to the same end-user presentation are present. In effect, the container filerepresents a RTSP presentation, with each of its components beingRTSP streams. Container files are a widely used means to storesuch presentations. While the components are transported asindependent streams, it is desirable to maintain a common contextfor those streams at the server end. This enables the server to keep

    a single storage handle open easily. It also allows treating all thestreams equally in case of any prioritization of streams by theserver. It is also possible that the presentation author may wish toprevent selective retrieval of the streams by the client in order topreserve the artistic effect of the combined media presentation. Inthe second instance, the aggregate URL may not be used for SETUPand one control message is required per stream to set up transportparameters. This keeps the syntax of the Transport header simpleand allows easy parsing of transport information by firewalls.