[Standards] Proposed XMPP Extension: Publishing Available Jingle Sessions

Dave Cridland dave at cridland.net
Mon Jun 29 16:35:08 UTC 2015


I was looking at that earlier. I'm not wholly convinced that this replaces
the use case lost from jingle file transfer.

I'll go into this more when I'm not on my mobile, but I think the "hey,
that didn't work" case is the one missing.
On 29 Jun 2015 17:30, "Peter Saint-Andre - &yet" <peter at andyet.net> wrote:

> Old thread alert!
>
> This document was considered by the Council in its meeting on August 13,
> 2014:
>
> http://logs.xmpp.org/council/2014-08-13/
>
> Several Council members (Kev and Tobias) said they would vote on the list,
> and according to the minutes Kev was subsequently +1 but Tobias never
> voted. In any case, this document should have been published last August
> but apparently the Editor Team lost track of it (for which I take
> responsibility).
>
> IMHO since it was approved for publication, it can be published now. I'll
> poke the Editor Team about that. :-)
>
> Peter
>
> On 8/12/14 12:07 PM, XMPP Extensions Editor wrote:
>
>> The XMPP Extensions Editor has received a proposal for a new XEP.
>>
>> Title: Publishing Available Jingle Sessions
>>
>> Abstract: This specification defines an XMPP protocol extension that
>> enables an XMPP entity to advertise the fact that it is willing accept a
>> particular Jingle session request. The protocol is used mainly to inform
>> other entities that a particular file is available for transfer via the
>> Jingle File Transfer protocol defined in XEP-0234.
>>
>> URL: http://xmpp.org/extensions/inbox/jingle-pub.html
>>
>> The XMPP Council will decide in the next two weeks whether to accept this
>> proposal as an official XEP.
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20150629/20e41096/attachment.html>


More information about the Standards mailing list