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):||19 March 2008|
|PDF File Size:||4.20 Mb|
|ePub File Size:||16.6 Mb|
|Price:||Free* [*Free Regsitration Required]|
On 5 Junat Current standards status of this document can be found at ftp: SDP does not deliver any media by itself but is used between endpoints iett negotiation of media type, format, and all associated properties.
Session Description Protocol – Wikipedia
Comments on RFCs and corresponding changes are accommodated through the existing standardization process. 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.
It is the responsibility of the XMPP recipient or translating gateway to unescape these restricted characters for processing. Hello Dan, Are you referring to additional differences between the grammar of attribute names or differences between the RFC and RFC syntax in general?
Other for any supplementary information: At least one of them is. Other for any supplementary information:. Feedback Contact Us Accessibility. For example, to schedule the same event also on Saturday at the same time of the day you would use:. Any protocol defined in this document has been developed outside the Internet Standards Process and is to be understood as an extension to XMPP rather than as an evolution, development, or modification of XMPP itself.
There might be similar. Each message may contain multiple timing and media descriptions. Justification for the specific reference: 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 Iftf.
If the stop time is 0 then the session is “unbounded.
Any explicit references within that referenced document should also be listed: Other useful information describing the “Quality” of the document: SDP uses attributes to extend the core protocol. Attributes can appear within the Session or Media sections and are scoped accordingly as session-level or media-level.
Session Description Protocol
RTCP ports for the audio and video streams of andrespectively, are implied. For example, if a daylight adjustment will subtract 1 hour on 31 October at 03am UTC i. If a iietf is already established for this transaction, the new INVITE serves as a renegotiation of session parameters. Joe Original Message From: Other useful information describing the “Quality” of the document:. Permissions Permission is hereby granted, free of charge, to any person obtaining a iettf of this specification the “Specification” itef, to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification.
Feedback Contact Us Accessibility.
Other for any supplementary information:. Five amendments and a technical corrigendum have been published up to now. 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 ietd the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation.
ITU-T A.5 reference justification
Untenable, as this isn’t the only attribute name affected by a strict parser. RFC is a basic component of the basic suite of internet protocols and standards and is widely used by the internet community. The following XMPP stanzas could be used to initiate a voice call. Clear description of the referenced document: Implementation of the protocol described 237 is not recommended. Would the following text capture your clarification?
Add a caveat like: