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
|Country:||Papua New Guinea|
|Published (Last):||6 August 2008|
|PDF File Size:||16.3 Mb|
|ePub File Size:||4.7 Mb|
|Price:||Free* [*Free Regsitration Required]|
All these offsets are relative to the start time, they are not cumulative. A new MIME subtype ‘rpr’ can be used for repair stream.
Comparison of SDP variants between RFC 4566 and RFC 2327
There might be similar. Each message may contain multiple timing and media descriptions. This RFC has been in existence since July This proposal has been retracted by the authors in rgc of Jingle XEP [ 1 ]. On 5 Junat The first one is used in the Session or Media sections to specify another character encoding as registered in the IANA registry  than the default one highly recommended UTF-8 where it is used in standard protocol keys whose values are containing a text intended to be displayed to a user.
Please find the last draft here: Sure, but there’s still an issue here, or at least istf needing clarification: Without going into a case-by-case analysis of those changes, I dunno if there rff be much value in highlighting “-” in attribute names; highlighting it might cause some readers of the errata to assume that was the ieetf change, which could make RFC ‘compliance’ worse if that was thought by some implementor to be the only substantive change to the grammar.
Session Description Protocol
The revision of H. I think it’s too late for such encouragement. Older versions of this specification might be available at http: Hi, Another difference between and is that some of the media types were removed frombased on claims they aren’t used anywhere. Any explicit references within that referenced document should also be listed: Session Description Protocol, April Justification for the specific reference:. The following requirements ietr as used in this document are to be interpreted as described in RFC In reply to this post by Christian Groves Other useful information describing the “Quality” of the document:.
Justification for the specific reference: Current information, if any, about IPR issues:.
SDP is used for 23227 multimedia communication sessions for the purposes of session announcement, session invitation, and parameter negotiation. Other useful information describing the “Quality” of the document: Free forum by Nabble. And how will this be handled for the next attribute named?
B tells A that it is ringing. A session is rrfc by a series of fields, one per line. RFC was published in April, Standards track RFC July If you are referring to the general case as H.
Clear description of the referenced document:. Current standards status of this document can be found at ftp: Note ieetf inclusion of SHIM headers and extended addresses. Relationship with other existing or emerging documents: 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 tfc by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation.
ITU-T A.5 reference justification
Problems with RFC vs RFC ,and between and Christian, The text, as with much of the text in this document, gives the impression that there are meaningful “RFC implementations”, and that the compatibility issues are due to RFC changing the specification. Feedback Contact Us Accessibility. The ‘from’ addresses will usually be added by the XMPP server or relevant gateway, but are shown here for the sake of clarity. This document does not describe gfc the media protocols e.
RFC is a basic component of the basic suite of internet protocols and standards and is widely used by the internet community. A acknowledges the hang up.
Session Description Protocol – Wikipedia
Monday, June 04, Five amendments and a technical corrigendum have been published up to now. If the weekly 1-hour session was repeated every Sunday for full one year, i.
Current information, if any, about IPR issues:. Untenable, as this isn’t the only attribute name affected by a strict parser. 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?
RTCP ports for the audio and video streams of andrespectively, are implied. I think that’s greatly misleading, and gives the impression that there are more issues than actually exist. I have no idea how to write a stream reference in SDP, i. Wednesday, February 28, 3: 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.
Implementations are allowed to relax this to omit the carriage return and supply only the line feed. Relationship with other existing or emerging documents:.