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

Author: Taurr Doulmaran
Country: Maldives
Language: English (Spanish)
Genre: Life
Published (Last): 21 August 2005
Pages: 269
PDF File Size: 3.75 Mb
ePub File Size: 4.22 Mb
ISBN: 899-9-93033-455-3
Downloads: 30819
Price: Free* [*Free Regsitration Required]
Uploader: Vull

From Wikipedia, the free encyclopedia. The latest draft can be found ietd Obsoletes RFCs; Errata exist. The set of properties and parameters are often called a session profile. Committed to connecting the world.

XEP-0111: A Transport for Initiating and Negotiating Sessions (TINS)

The ‘from’ addresses will usually be added by rc XMPP server or relevant gateway, but are shown here for the sake of clarity. Regards, Christian Dan Wing wrote: Feedback Contact Us Accessibility.

RTCP ports for the audio and video streams of andrespectively, are implied. Attributes can appear within the Session or Media sections and are scoped accordingly as session-level or media-level. On 5 Junat I guess those who have implemented the drafts wouldn’t be happy though: Obsoletes RFCs A sends an acknowledgement to Rf.


B sends an updated description to A. The degree of stability or maturity of the document:. They don’t expect to support until the end ofif it doesn’t slip The following requirements keywords as used in this document are to be interpreted as described in RFC It is a standards-track document and is currently in the “Proposed standard” state.

Information on RFC ยป RFC Editor

Values are typically a UTF-8 encoding. This session is originated by the user ‘jdoe’, at IPv4 address Was this issue known before it became an RFC? When repeat times are specified, 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 time and the stop time which are still specified in NTP format in an absolute UTC timezone.

BYE — Used by either side of the conversation to terminate the transaction. Any explicit references within that referenced document should also be listed: There is no general-purpose way to ensure that media protocol connections are associated with the in-band TINS conversation. Note also that sessions may be repeated irregularly over a week but scheduled the same way for all weeks in the period, by adding more tuples in the r parameter.

All RFCs always remain available on-line.

Developers desiring similar functionality are advised to implement the protocol that supersedes this one XEP Architecture and Basic Multilingual Plane.


Limitation of Liability In no event and under no legal theory, whether in tort including negligencecontract, or otherwise, unless required by applicable law such as deliberate and grossly negligent acts or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losseseven if the XMPP Standards Foundation or such author has been advised of the possibility of such damages.

This page was last edited on 7 Octoberat I can only expect that was the intent, yes. Retrieved from ” https: Tuesday, June 05, 8: It’s my belief that there are no more compatibility issues between an “RFC implementation” and one based on RFCthan between any two RFC implementations.