I believe that the next step, according to XEP-001, is submission to the council for a vote on the advancement to Draft. Is this the next council meeting, or further in the future? Do any council members have concerns that I might address further to the discussion in this thread so far?
Cheers, Ben On 17 April 2015 at 15:48, Ben Langfeld <[email protected]> wrote: > Changes suggested to this specification in this thread, with the exception > of those deferred to v2, are available at > https://github.com/rayo/xmpp/compare/1b4ee7f...feature/rayo.patch > > On 6 April 2015 at 11:26, XMPP Extensions Editor <[email protected]> wrote: > >> This message constitutes notice of a Last Call for comments on XEP-0327 >> (Rayo). >> >> Abstract: This specification defines an XMPP protocol extension for the >> third-party control of telephone calls and other similar media sessions. >> The protocol includes support for session management/signaling, as well as >> advanced media resources such as speech recognizers, speech synthesizers >> and audio/video recorders. The protocol serves a different purpose from >> that of first-party protocols such as Jingle or SIP, and is compatible with >> those protocols. >> >> URL: http://xmpp.org/extensions/xep-0327.html >> >> This Last Call begins today and shall end at the close of business on >> 2015-04-17. >> >> Please consider the following questions during this Last Call and send >> your feedback to the [email protected] discussion list: >> >> 1. Is this specification needed to fill gaps in the XMPP protocol stack >> or to clarify an existing protocol? >> 2. Does the specification solve the problem stated in the introduction >> and requirements? >> 3. Do you plan to implement this specification in your code? If not, why >> not? >> 4. Do you have any security concerns related to this specification? >> 5. Is the specification accurate and clearly written? >> >> Your feedback is appreciated! >> > >
