Canonical URL: ; File formats: Plain Text PDF Discuss this RFC: Send questions or comments to [email protected] 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 . “An Offer/Answer Model with the Session Description Protocol(RFC ). SIP Configuration Guide, Cisco IOS Release 15M&T-Achieving SIP RFC Compliance. (SDP), as defined in the IETF specification, RFC , An Offer/ Answer.
|Published (Last):||28 April 2007|
|PDF File Size:||16.35 Mb|
|ePub File Size:||11.85 Mb|
|Price:||Free* [*Free Regsitration Required]|
Views Read Edit View history. An offer and answer model with SDP.
SDP is designed to be extensible to support new media types and formats. An invite-initiated dialog event package for the SIP. RTCP ports for the audio and video streams of andrespectively, are implied. If the stop time is 0 then the session is “unbounded. Names are only unique within the associated syntactic construct, i.
All these offsets are relative to the start time, they are not cumulative. When repeat times are rfd, the start time of each repetition may need to be adjusted so that it will occur at the same local time in a specific timezone throughout the period between the start rfv and the stop time which are still specified in NTP format in an absolute Rrc timezone.
SDP uses attributes to extend the core protocol.
Private Extensions rgc the SIP for asserted identity within trusted networks. Setting up SIP application composition. A session is described by a series of fields, one per line. Browse all SIP topics.
Information on RFC » RFC Editor
The SIP Refer method. SIP extension for instant messaging. The SDP specification does not incorporate any transport protocol; it is purely a format for session description. Its name is “SDP Seminar” and extended session information “A Seminar on the session description protocol” is included along with a link for additional information and an email address to contact the responsible party, Jane Doe.
Private SIP proxy-to-proxy extensions for supporting the PacketCable distributed call signaling architecture. Below is a sample session description from RFC Thus an hour meeting from 10am UTC on 1 Augustwith a single repeat time a week later at the same time can be represented as:.
Session Description Protocol
Transcoding services invocation in 2364 SIP using third-party call control 3pcc. SIP Extension Header field for registering non-adjacent contacts.
This session is originated by the user ‘jdoe’, at IPv4 address A mechanism for content indirection in SIP messages. This product complies with standards for SIP applications as noted in the following table. Intervals can be represented with Network Time Protocol times or in typed time: Iettf example, if a daylight adjustment will subtract 1 hour on 31 October at 03am UTC i.
Session Initiation Protocol (SIP) industry standards compliance
SIP Extension Header field for service route discovery during registration. This page was last edited on 7 Octoberat The early session disposition type for the SIP.
The second one is used to specify in which language it is written alternate texts in multiple languages may be carried in the protocol, and selected automatically by the user agent according to user preferences. The fields present in their values are considered in the protocol as opaque strings, they are used as identifiers, just like paths ieetf an URL or filenames in a file system: In both cases, each textual field rcc 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 product complies with SIP standards as jetf in the following table.
SIP industry standards compliance
Indicating user agent capabilities in the SIP. Within an SDP message there are three main sections, detailing the sessiontimingand media descriptions. Implementations are allowed to relax this to omit the carriage return and supply only the line feed.
The first one is used in the Session or Media sections to specify 364 character encoding as registered in the IANA registry  than the default one oetf recommended UTF-8 where it is used in standard protocol keys whose values are containing a text intended to be displayed to a user.
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 itef end time falling at or after each daylight adjustment.
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 Reliability of provisional responses in SIP. New attributes are added to the standard occasionally through registration with IANA. Compliance with standards for SIP applications.
Webarchive template wayback links Articles with short description All articles with unsourced statements Articles with unsourced statements from August Pages using RFC magic links.