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):||28 December 2008|
|PDF File Size:||17.45 Mb|
|ePub File Size:||13.3 Mb|
|Price:||Free* [*Free Regsitration Required]|
And how will this be handled for the next attribute named? Implementation of the protocol described herein is not recommended. The revision of H.
IETF – mmusic – Comparison of SDP variants between RFC and RFC
Committed to connecting the world. 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 23227 email address to contact the responsible party, Jane Doe.
The fields present in their values are considered in the protocol as opaque strings, they are used as identifiers, just like paths in an URL or filenames in a file system: Obsoletes RFCs The text also says to ignore unknown atributes, but that assumes you’ve been able to parse the attribute name. I guess those who have implemented the drafts wouldn’t be happy though: For example, if a daylight adjustment will subtract 1 hour on 31 October at 03am UTC i. Other for any supplementary information: RFC was published in July, Justification for the specific reference:.
There 237 no general-purpose way to ensure that media protocol connections are associated with the in-band TINS conversation. In reply to this post by Christian Groves-2 On 5 Junat Architecture and Basic Multilingual Plane.
If the stop time is 0 then the session is “unbounded.
XEP-0111: A Transport for Initiating and Negotiating Sessions (TINS)
Justification for the specific reference:. At least one of them is. Current information, if any, about IPR issues: And why was a name chosen that might break backwards compatibility? The latest draft can be found at: There’s no discussion of the compatibility impact of this. From Wikipedia, the free encyclopedia. Without going into a case-by-case analysis of those changes, I dunno if there would be much value in highlighting “-” in attribute names; highlighting it might cause some readers of the errata to assume that was the only change, which could make RFC ‘compliance’ worse if that was thought by some implementor to be the only substantive change to the grammar.
I agree such issues should be documented.
Was this issue known before it became an RFC? If I have one stream which carries optional ‘repair’ data for another stream, and I want to send them on two separate 232 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? This proposal has been retracted by the authors in favor of Jingle XEP [ 1 ].
HTML This document in other formats: This document does not describe how the media protocols e. For scalable video coding these indications are still under discussion. Justification for the specific reference: Wednesday, February 28, 3: Iwtf explicit references within that referenced document should also be listed: It IS used in H.
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. Older versions of this specification might be available at http: RFCwhile not perfect, greatly clarifies the text to fix those problems, and to reflect existing practice.
Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation. Retrieved from ” https: Current standards status of this document can be found at ftp: In reality, RFC is self-contradictory and unclear in a number of places, and useful implementations rely on a large number of extensions and interpretations of the standard.
ACK — Used by the initiator to tell the invitee that an out-of-band session has been established. Names are only unique within the associated syntactic construct, i. It is a standards-track document and is currently in the “Proposed Standard” state.
Hello Rtc, Are you referring to additional differences between the grammar of attribute names or differences between the RFC and RFC syntax in general? Current information, dfc any, about IPR issues:.
RFC – SDP: Session Description Protocol
SDP is designed to be extensible to support new media types and formats. 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:.
RFC allows ‘-‘ and a lot of other characters in attribute names. Other for any supplementary information:.