Standards Track A. Rao Netscap - RFC Editor

More documents

Recommendations

Info

RFC 2326 Real Time Streaming Protocol April 1998layers:The number of multicast layers to be used for this mediastream. The layers are sent to consecutive addresses startingat the destination address.mode:The mode parameter indicates the methods to be supported forthis session. Valid values are PLAY and RECORD. If notprovided, the default is PLAY.append:If the mode parameter includes RECORD, the append parameterindicates that the media data should append to the existingresource rather than overwrite it. If appending is requestedand the server does not support this, it MUST refuse therequest rather than overwrite the resource identified by theURI. The append parameter is ignored if the mode parameterdoes not contain RECORD.interleaved:The interleaved parameter implies mixing the media stream withthe control stream in whatever protocol is being used by thecontrol stream, using the mechanism defined in Section 10.12.The argument provides the channel number to be used in the $statement. This parameter may be specified as a range, e.g.,interleaved=4-5 in cases where the transport choice for themedia stream requires it.This allows RTP/RTCP to be handled similarly to the way that it isdone with UDP, i.e., one channel for RTP and the other for RTCP.Multicast specific:ttl:multicast time-to-liveRTP Specific:port:This parameter provides the RTP/RTCP port pair for a multicastsession. It is specified as a range, e.g., port=3456-3457.client_port:This parameter provides the unicast RTP/RTCP port pair onwhich the client has chosen to receive media data and controlinformation. It is specified as a range, e.g.,client_port=3456-3457.Schulzrinne, et. al. Standards Track [Page 60]
RFC 2326 Real Time Streaming Protocol April 1998server_port:This parameter provides the unicast RTP/RTCP port pair onwhich the server has chosen to receive media data and controlinformation. It is specified as a range, e.g.,server_port=3456-3457.ssrc:The ssrc parameter indicates the RTP SSRC [24, Sec. 3] valuethat should be (request) or will be (response) used by themedia server. This parameter is only valid for unicasttransmission. It identifies the synchronization source to beassociated with the media stream.Transport = "Transport" ":"1\#transport-spectransport-spec = transport-protocol/profile[/lower-transport]*parametertransport-protocol = "RTP"profile = "AVP"lower-transport = "TCP" | "UDP"parameter = ( "unicast" | "multicast" )| ";" "destination" [ "=" address ]| ";" "interleaved" "=" channel [ "-" channel ]| ";" "append"| ";" "ttl" "=" ttl| ";" "layers" "=" 1*DIGIT| ";" "port" "=" port [ "-" port ]| ";" "client_port" "=" port [ "-" port ]| ";" "server_port" "=" port [ "-" port ]| ";" "ssrc" "=" ssrc| ";" "mode" = ttl = 1*3(DIGIT)port = 1*5(DIGIT)ssrc = 8*8(HEX)channel = 1*3(DIGIT)address = hostmode = | MethodExample:Transport: RTP/AVP;multicast;ttl=127;mode="PLAY",RTP/AVP;unicast;client_port=3456-3457;mode="PLAY"The Transport header is restricted to describing a single RTPstream. (RTSP can also control multiple streams as a singleentity.) Making it part of RTSP rather than relying on a multitudeof session description formats greatly simplifies designs offirewalls.Schulzrinne, et. al. Standards Track [Page 61]
Page 2 and 3:
RFC 2326 Real Time Streaming Protoc
Page 4 and 5:
Page 7:
Page 10 and 11: RFC 2326 Real Time Streaming Protoc
Page 92: RFC 2326 Real Time Streaming Protoc
show all

Standards Track A. Rao Netscap - RFC Editor

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?