Standards Track A. Rao Netscap - RFC Editor

RFC 2326 Real Time Streaming Protocol April 1998CSeq: 421Content-length: 10Content-type: text/parametersbarparamThe "text/parameters" section is only an example type forparameter. This method is intentionally loosely defined with theintention that the reply content and response content will bedefined after further experimentation.10.10 REDIRECTA redirect request informs the client that it must connect to anotherserver location. It contains the mandatory header Location, whichindicates that the client should issue requests for that URL. It maycontain the parameter Range, which indicates when the redirectiontakes effect. If the client wants to continue to send or receivemedia for this URI, the client MUST issue a TEARDOWN request for thecurrent session and a SETUP for the new session at the designatedhost.This example request redirects traffic for this URI to the new serverat the given play time:S->C: REDIRECT rtsp://example.com/fizzle/foo RTSP/1.0CSeq: 732Location: rtsp://bigserver.com:8001Range: clock=19960213T143205Z-10.11 RECORDThis method initiates recording a range of media data according tothe presentation description. The timestamp reflects start and endtime (UTC). If no time range is given, use the start or end timeprovided in the presentation description. If the session has alreadystarted, commence recording immediately.The server decides whether to store the recorded data under therequest-URI or another URI. If the server does not use the request-URI, the response SHOULD be 201 (Created) and contain an entity whichdescribes the status of the request and refers to the new resource,and a Location header.A media server supporting recording of live presentations MUSTsupport the clock range format; the smpte format does not make sense.Schulzrinne, et. al. Standards Track [Page 39]