The Session Description Protocol (SDP) is a format for describing streaming media communications parameters. The IETF published the original specification as an IETF Proposed Standard in April , and subsequently published a revised specification as an IETF Proposed Standard as RFC in July . ” SDP: Session Description Protocol (RFC )”. ITU-T A.5 justification information for referenced document IETF RFC ( ) in draft H. It was not available in the previous SDP defined by RFC 4. Status of approval: Normative. 3. Justification for the specific reference: IETF RFC specifies SDP: Session Description Protocol wich is tested in Q
|Published (Last):||12 February 2016|
|PDF File Size:||6.64 Mb|
|ePub File Size:||11.42 Mb|
|Price:||Free* [*Free Regsitration Required]|
Any explicit references within that referenced document should also be listed: Below is a sample session description from RFC If a session is already established for this transaction, the new INVITE serves as ietv renegotiation of session parameters. In reply to this post by Colin Perkins.
In both cases, each textual field in the protocol which are not interpreted symbolically by the protocol itself, will be interpreted as opaque strings, but rendered to the user or application with the values indicated in the last occurrence of the charset and sdplang in the current Media section, or otherwise their last value in the Session section.
This session is specified to last for two hours using NTP timestamps, with a connection address which indicates the address clients must connect to or — when a multicast address is provided, as it is here — subscribe to specified as IPv4 RFC was published in April, Session Description Protocol, April 2. For example, to schedule the same event also on Saturday at the same time of the day you would use:.
This message SHOULD cause all resources associated with this transaction to be freed, and any associated network connections to be terminated. Other for any supplementary information:. Clear description of the referenced document: I guess this is somewhat like scalable coding, in which I would need to say ‘this stream’ is an enhancement, and builds on ‘that stream’.
Session Description Protocol
This session is originated by the user ‘jdoe’, at IPv4 address HTML This document in other formats: Standards track RFC July Relationship with other existing or emerging documents: The approach taken herein is to send pure SDP. On 5 Junat Such an implementation would also reject: The following Iettf stanzas could be used to initiate a voice call.
The degree rffc stability or maturity of the document: Current information, if any, about IPR issues:.
The set of properties and parameters are often called a session profile. Five amendments and a technical corrigendum have been published up to now.
RFC – SDP: Session Description Protocol
Other for any supplementary information: All RFCs always remain available on-line. This RFC has been in existence since April For example, if a daylight adjustment will subtract 1 hour on 31 October at 03am UTC i.
The techniques for scalable coding seem to be confined.
If I have one stream which carries optional ‘repair’ data for another stream, and I want to send them on two separate multicast groups, or two separate streams to an RTSP client, how would I indicate that ‘this media stream’ is the repair data for ‘that media stream’ in SDP? Session Description Protocol wich is tested in Q.
Instead of specifying this timezone and having to support a database of timezones for knowing when and where daylight adjustments will be needed, the repeat times are assumed to be all defined within the same timezone, and SDP supports the indication of NTP absolute times when a daylight offset expressed in seconds or using a type time will need to be applied to the repeated start time or end time falling at or after each daylight adjustment.
Discussion on other xmpp. I guess those who have implemented 22327 drafts wouldn’t be happy though: Retrieved from ” https: