Standards Track A. Rao Netscap - RFC Editor

RFC 2326 Real Time Streaming Protocol April 1998available via a multicast group), state begins at Ready. In thiscase, there are only two states, Ready and Playing. The client alsochanges state from Playing/Recording to Ready when the end of therequested range is reached.The "next state" column indicates the state assumed after receiving asuccess response (2xx). If a request yields a status code of 3xx, thestate becomes Init, and a status code of 4xx yields no change instate. Messages not listed for each state MUST NOT be issued by theclient in that state, with the exception of messages not affectingstate, as listed above. Receiving a REDIRECT from the server isequivalent to receiving a 3xx redirect status from the server.state message sent next state after responseInit SETUP ReadyTEARDOWNInitReady PLAY PlayingRECORDRecordingTEARDOWNInitSETUPReadyPlaying PAUSE ReadyTEARDOWNInitPLAYPlayingSETUPPlaying (changed transport)Recording PAUSE ReadyTEARDOWNInitRECORDRecordingSETUPRecording (changed transport)A.2 Server State MachineThe server can assume the following states:Init:Ready:The initial state, no valid SETUP has been received yet.Last SETUP received was successful, reply sent or afterplaying, last PAUSE received was successful, reply sent.Playing:Last PLAY received was successful, reply sent. Data is beingsent.Recording:The server is recording media data.Schulzrinne, et. al. Standards Track [Page 77]