81
edits
Difference between revisions of "Radar"
Jump to navigation
Jump to search
no edit summary
| Line 21: | Line 21: | ||
Version: [http://xmpp.org/extensions/tmp/xep-0166-1.1.html 1.1rc1] | Version: [http://xmpp.org/extensions/tmp/xep-0166-1.1.html 1.1rc1] | ||
Status: Revisions complete. | Status: Revisions complete, Council vote in progress. | ||
Changelog: Specified handling of duplicate name attributes on content element; clarified recommended usage of Jingle when exchanging multiple content-types; declared the principle that application types ought not to be mixed beyond necessity within a single session; clarified use of the reason element in cases other than termination. | Changelog: Specified handling of duplicate name attributes on content element; clarified recommended usage of Jingle when exchanging multiple content-types; declared the principle that application types ought not to be mixed beyond necessity within a single session; clarified use of the reason element in cases other than termination. | ||
| Line 29: | Line 29: | ||
Version: [http://xmpp.org/extensions/tmp/xep-0167-1.1.html 1.1rc4] | Version: [http://xmpp.org/extensions/tmp/xep-0167-1.1.html 1.1rc4] | ||
Status: Revisions complete. | Status: Revisions complete, Council vote in progress. | ||
Changelog: Added creator attribute to mute and unmute elements so that these events can be correlated with a particular content type; clarified use of the reason element in cases other than termination; defined handling of content-add when none of the offered payload-types are supported, where the signalling uses a content-reject message with a Jingle reason of <failed-application/> and a list of the supported codecs; clarified that the RTP profile is RTP/AVP by default, that the profile is RTP/SAVP if security preconditions are present, and that additional profiles such as RTP/AVPF and RTP/SAVPF might be supported in a future version of this specification. | Changelog: Added creator attribute to mute and unmute elements so that these events can be correlated with a particular content type; clarified use of the reason element in cases other than termination; defined handling of content-add when none of the offered payload-types are supported, where the signalling uses a content-reject message with a Jingle reason of <failed-application/> and a list of the supported codecs; clarified that the RTP profile is RTP/AVP by default, that the profile is RTP/SAVP if security preconditions are present, and that additional profiles such as RTP/AVPF and RTP/SAVPF might be supported in a future version of this specification. | ||
| Line 37: | Line 37: | ||
Version: [http://xmpp.org/extensions/tmp/xep-0177-1.1.html 1.1rc1] | Version: [http://xmpp.org/extensions/tmp/xep-0177-1.1.html 1.1rc1] | ||
Status: Revisions complete. | Status: Revisions complete, Council vote in progress. | ||
Changelog: Added type attribute to candidate element for consistency with XEP-0176. | Changelog: Added type attribute to candidate element for consistency with XEP-0176. | ||
= Calls for Experience = | = Calls for Experience = | ||