[Standards] [Fwd: [Council] meeting minutes, 2007-02-26]

Mridul mridul at sun.com
Wed Feb 28 20:35:09 UTC 2007


I was searching for the muc log of the meeting .. was esp interested in 
124 and file transfer related discussion.
When finally I noticed the 'IRL' :-)

- Mridul

Peter Saint-Andre wrote:
> FYI.
> 
> -------- Original Message --------
> Date: Tue, 27 Feb 2007 15:24:01 -0500
> From: Peter Saint-Andre <stpeter at jabber.org>
> To: council at xmpp.org
> Subject: [Council] meeting minutes, 2007-02-26
> 
> Results of the XMPP Council meeting held 2007-02-26...
> 
> Agenda:
> 
> http://www.jabber.org/council/meetings/agendas/2007-02-26.html
> 
> Log:
> 
> No log (meeting held IRL at "XMPP Summit" in Brussels, Belgium)
> 
> 0. Roll Call
> 
> Chris Mullins was not in Brussels. All other Council members (Ralph
> Meijer, Ian Paterson, Peter Saint-Andre, Kevin Smith) in attendance.
> Quorum achieved.
> 
> 1. XEP-0124: HTTP Binding
> 
> Approve version 1.6 and spin off XMPP-specific extensions as XEP-0206?
> 
> No objections. The Editor shall update and publish.
> 
> 2. XEP-0189: Public Key Publishing
> 
> Issue Last Call?
> 
> No objections. The Editor shall issue a Last Call.
> 
> 3. XEP-0136: Message Archiving
> 
> Issue second Last Call?
> 
> No objections. The Editor shall issue a Last Call.
> 
> 4. XEP-0174: Link-Local Messaging
> 
> Issue Last Call?
> 
> No objections. The Editor shall issue a Last Call.
> 
> 5. ProtoXEP: File Repository and Sharing
> 
> Accept as a XEP?
> 
> Direct proposal author to investigate and compare his approach to
> XEP-0137 and explore how to integrate Jingle as the transfer method (the
> Council found it somewhat unhelpful to point clients at such a large
> number of mirroring technologies). Publication may depend on settling
> preferred XMPP file transfer methods (discussed but not settled at XMPP
> Summit).
> 
> 6. ProtoXEP: Jingle RTMP Transport
> 
> Accept as a XEP?
> 
> Council consensus that it is inappropriate to publish this proposal
> given the proprietary nature of the RTMP technology on which this
> specification depends. Peter Saint-Andre to pursue contact with
> representatives of Adobe regarding their plans for RTMP.
> 
> 7. ProtoXEP: Jingle Bytestreams Transport
> 
> Accept as a XEP?
> 
> Based on discussion at the XMPP Summit, the author retracted the
> proposal in favor of a simple "hello world" style approach using the
> Echo Protocol (RFC 862).
> 
> 8. ProtoXEP: Jingle HTTP File Transfer
> 
> Accept as a XEP?
> 
> Council consensus that it is inappropriate to publish this proposal now,
> pending further discussion of preferred file transfer methods and NAT
> traversal technologies.
> 
> 9. Next meeting.
> 
> Scheduled for March 14.
> 
> /psa
> 
> 




More information about the Standards mailing list