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: | Gogore Mauramar |
| Country: | Cameroon |
| Language: | English (Spanish) |
| Genre: | Art |
| Published (Last): | 13 February 2005 |
| Pages: | 426 |
| PDF File Size: | 19.6 Mb |
| ePub File Size: | 13.35 Mb |
| ISBN: | 690-9-17702-578-5 |
| Downloads: | 58129 |
| Price: | Free* [*Free Regsitration Required] |
| Uploader: | Zulukinos |
Thus an hour meeting from 10am UTC on 1 232with a single repeat time a week later at the same time can be represented as:.
Other useful information describing the “Quality” of the document:. SDP does not deliver any media by itself but is used between endpoints for negotiation of media type, format, and all associated properties.
Negotiating a Voice Call 6. Relationship with other existing or emerging documents: Note the inclusion of SHIM headers and extended addresses.
All RFCs always remain available on-line. Adam Dave Rdc wrote: Justification for the specific reference:. This session is specified to last for two hours using NTP efc, 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 Implementations are allowed to relax this to omit the carriage return and supply only the line feed.
It seems like RFC section 10 Summary of changes since RFC should have mentioned this issue, and ketf where complying with would make you at least in theory not interoperable with RFC The revision of H.
Views Read Edit View history. Obsoletes RFCs Please find the last draft here: All these offsets are relative to the start time, they are not cumulative. Regards, Christian Dan Wing wrote: BYE — Used by either side of the conversation to terminate the transaction.
Tuesday, June 05, 8: Values are typically a UTF-8 encoding.
ITU-T A.5 reference justification
The second one is used to specify in which language it iwtf written alternate texts in multiple languages may be carried in the protocol, and selected automatically by the user agent according to user preferences. Session Description Protocol wich is tested in Q. Any explicit references within that referenced document should also be listed: Relationship with other existing or emerging documents:.
If a session is already established for this transaction, the new INVITE serves as a renegotiation of session parameters.
Any explicit references within that referenced document should also be listed: This RFC has been in existence since April There might be similar. New attributes are added to the standard occasionally through registration with IANA. Feedback Contact Us Accessibility. Within an SDP message there are three main sections, detailing the sessiontimingand media descriptions.
Might want to ping the authors first iet make sure that was their intent.
Comparison of SDP variants between RFC 4566 and RFC 2327
RFCwhile not iietf, greatly clarifies the text to fix those problems, and to reflect existing practice. Below is a sample session description from RFC Clear description of the referenced document: Limitation of Liability In no event and under no legal theory, 23327 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 rcf, 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.
They don’t expect to support until the end ofif it doesn’t slip And why was a name chosen that might break backwards compatibility? Clear description of the referenced document: This page was last edited on 7 Octoberat Free forum by Rfx. From Wikipedia, the free encyclopedia.
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.