[Standards] Editor Team

[Peter Saint-Andre]

Folks, we now have a team of people who are responsible for the 
functions of the XMPP Extensions Editor:


http://xmpp.org/participate/become-a-member/editor-team/

To communicate with the team, simply send email to edi...@xmpp.org and 
make sure that you include the string xep (e.g., ProtoXEP: foo) 
somewhere in the subject line for faster processing.


Thanks!

Peter

[Standards] Proposed XMPP Extension: Recipient Server Side Notifications Filtering

[XMPP Extensions Editor]

The XMPP Extensions Editor has received a proposal for a new XEP.

Title: Recipient Server Side Notifications Filtering

Abstract: This specification defines a modern efficient way to deliver PubSub 
notifications.

URL: http://xmpp.org/extensions/inbox/rsf.html

The XMPP Council will decide in the next two weeks whether to accept this 
proposal as an official XEP.

[Standards] XEP-0340: COLIBRI feedback

[Peter Saint-Andre]

I'm working on an implementation of COLIBRI (XEP-0340) and have some 
questions and comments...


The relationship (if any) to Jingle isn't explained at all. As a small 
example, is the 'name' attribute of the content/ element supposed to 
match the same construction in Jingle? As a larger example, is the 
content/ element supposed to (potentially) contain description/ and 
transport/ elements from the Jingle specs, as is hinted by examples 2 
and 3? (Note that example 3 has payload-type/ elements without the 
description/ wrapper - this seems like a plain error.) Another 
example: are the values of the 'direction' attribute (e.g., recvonly) 
supposed to match the values of the 'senders' attribute in Jingle?


The text says that creation of a conference enables the organizers to 
specify the participants. But I don't see any connection between the 
channels that are created and any given JID. Should the channel/ 
element include a JID for the participant? (Nit: the 'initiator' 
attribute here might be confused with the meaning of initiator in Jingle.)


What are the allowable values for the 'rtp-level-relay-type' attribute, 
and why?


Example 7 strikes me as odd (for adding a new channel). Is this really 
done by sending an IQ-get or is that a typo? More importantly, how does 
the media bridge know that this stanza is intended to update an existing 
conference, rather than to create a new one? I think we might want an 
explicit 'action' attribute, so that we can differentiate between 
conference creation and conference modification.


There's no reference to XEP-0320 for the fingerprint/ element or to 
XEP-0339 for the source/ element.


I might have more questions once I make more progress on the code I'm 
writing...


Peter