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):||8 October 2005|
|PDF File Size:||5.19 Mb|
|ePub File Size:||8.11 Mb|
|Price:||Free* [*Free Regsitration Required]|
On 5 Junat The degree of stability or maturity of the document:. Tuesday, June 05, 8: The degree of stability or maturity of the document: Adam Dave Singer wrote: It is a standards-track document and is currently in the “Proposed Standard” state.
Iftf Description Protocol wich is tested in Q. Committed to connecting the world.
ITU-T work programme
Implementation of the protocol described herein is not recommended. Better that these sorts of issues are documented. I’ve also added some additional text to address your proposal. Hello Colin, Thanks for the extra information.
All RFCs always remain available on-line. Without going into a case-by-case analysis of those changes, I dunno if there would be much value in ietd “-” 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.
Values are typically a UTF-8 encoding. Justification for 23277 specific reference: B tells A that it is ringing. I agree such issues should be documented.
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 dfc. Was this issue known before it became an RFC? Might want rvc ping the authors first to make sure that was their intent.
Information on RFC » RFC Editor
SDP is designed to be extensible to support new media types and formats. It seems like RFC section 10 Summary of changes since RFC should have mentioned this issue, and others where complying with would make you at least in theory not interoperable with RFC In reply to this post by Christian Groves This page was last edited on 7 Octoberat ACK — Used by the initiator to tell the invitee that an out-of-band session has been established.
Other for any supplementary information:. Current information, if any, ietd IPR issues: Note the inclusion of SHIM headers and extended addresses. Recipients of this session description ietd instructed to only receive media. I think it’s too late for such encouragement.
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. For example, to schedule the same event also on Saturday at the same time of the day you would use:.
Current information, if any, about IPR issues: This document does not describe how the media protocols e. Session Description Protocol 2. Colin On 5 Jun gfc, at Such an implementation would also reject: There might be similar.
Other for any supplementary information: Dan Wing dwing ; [hidden email] ; [hidden email] ; [hidden email] Subject: At least one 232 them is. Wednesday, February itf, 3: Comments on RFCs and corresponding changes are accommodated through the existing standardization process.