[Standards] DEFERRED: XEP-0294 (Jingle RTP Header Extensions Negotiation)

2012-04-17 Thread XMPP Extensions Editor
XEP-0294 (Jingle RTP Header Extensions Negotiation) has been Deferred because of inactivity. Abstract: This specification defines an XMPP extension to negotiate the use of the use of RTP Header Extension as defined by RFC 5285 with Jingle RTP sessions URL: http://xmpp.org/extensions/xep-0294

[Standards] DEFERRED: XEP-0293 (Jingle RTP Feedback Negotiation)

2012-04-17 Thread XMPP Extensions Editor
XEP-0293 (Jingle RTP Feedback Negotiation) has been Deferred because of inactivity. Abstract: This specification defines an XMPP extension to negotiate the use of the Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF) with Jingle RTP sessions URL

Re: [Standards] UPDATED: XEP-0268 (Incident Handling)

2012-04-17 Thread Peter Saint-Andre
This is a major rewrite, now using IODEF (RFC 5070) instead of a custom schema. There's still much work to do on the various communication flows, but feedback would be welcome on the general approach. For comparison purposes, the previous version is at [1]. /psa On 4/17/12 10:00 AM, XMPP Extensio

[Standards] UPDATED: XEP-0268 (Incident Handling)

2012-04-17 Thread XMPP Extensions Editor
Version 0.4 of XEP-0268 (Incident Handling) has been released. Abstract: This specification defines methods for incident reporting among XMPP server deployments using the IODEF format produced by the IETF's INCH Working Group. Changelog: Changed the XML format from a custom schema to IODEF (RFC

Re: [Standards] MAM

2012-04-17 Thread Dave Cridland
On Fri Feb 10 23:06:48 2012, Peter Saint-Andre wrote: On 2/10/12 2:59 PM, Matthew Wild wrote: > That said, you can consider even what is there a contribution to the > community, and if people really think it's worthy of submission in its > current state then I won't hold it back. I suggest gi

Re: [Standards] NEW: XEP-0308 (Last Message Correction)- Interop with XEP 0301 RTT

2012-04-17 Thread Mark Rejhon
Hello, On Tue, Apr 17, 2012 at 5:35 AM, Kevin Smith wrote: > I think that you can just start rtt-ing on the previous message > without retransmitting it in advance, unless you care about the edge > case where a user has switched clients very quickly and so doesn't > have that message. I would th

Re: [Standards] NEW: XEP-0308 (Last Message Correction)- Interop with XEP 0301 RTT

2012-04-17 Thread Kevin Smith
Mild thread necromancy: 2011/11/11 Gunnar Hellström : > Mark says: "2. Allow real time text (RTT) to occur with previous messages. >  I would add an optional 'id' attribute to elements.  " > > I can imagine that the action will be something like this: > 1.The transmitting user positions the curso