[Council] meeting agenda, 2006-03-23
Matthew A. Miller
linuxwolf at outer-planes.net
Thu Mar 23 07:41:01 CST 2006
For some reason, I thought our meeting this week was to be tomorrow, and
not today (-:
I have a previous engagement, and can't make today's meeting, so here's
1) JEP-0145 (Annotations): +1
2) JEP-0146 (Remote Controlling Clients): +1
3) JEP-0147 (XMPP URI Scheme Query Components): +1
4) JEP-0130 (Waiting Lists): +1
5) JEP-0124 (HTTP Binding): I'm -1 until I can fully digest (more
6,7) Proto-JEPs on Forwarding: +1
8) JEP-0033 (Extended Stanza Addressing): +1, and about time (-:
9) JEP-0133 (Service Administration): Need to read through it again
before I weigh in
10) JEP-0078 (Non-SASL Authentication): +1
11) Proto-JEP (Server-Side Message Archiving): +1
12-14) Proto-JEPs on Jingle: +1
15) Proto-JEP (Zoep): -0 (We've tried the "SIP in XMPP" approach
before, and it didn't work. But I'm not stopping this one yet)
Now back to JEP-0124:
I'm generally opposed to such large changes to Draft JEPs (which this
appears to me to be the case), unless the changes fix deficienies (e.g.
JEP-0045 and JEP-0060). The biggest reason is that it makes it hard for
multiple implementors to properly interoperate, because they need to
somehow determine what version of a JEP the other parties have
implemented (unless the changes can be 100% ignored).
I'm wondering if the multi-stream stuff could not have been done as an
add-on (and therefore a different JEP), but I'll read through it and
weigh in later.
Peter Saint-Andre wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Here is a proposed agenda for tomorrow's meeting:
> The agenda is long. In the interests of a short meeting, here are my
> thoughts on the items:
> 1. JEP-0145: Annotations. A few developers said they are or will be
> using this. IMHO it can be modified if/when PEP storage is ready to go
> (same as for all the other formats we stick into private data storage
> today). Therefore I'd vote +1.
> 2. JEP-0146: Remote Controlling Clients. There is at least one
> implementation, with perhaps more on the way. Seems potentially helpful,
> a nice use of ad-hoc commands, I'm +1.
> 3. JEP-0147: XMPP URI Scheme Query Components. +1 here. :-) Let's create
> the registry so the IESG can move forward.
> 4. JEP-0130: Waiting Lists. Another minor modification agreed upon among
> the implementors. In fact it's a deletion, the remote-server-not-found
> error was never used AFAIK, people just returned item-not-found instead.
> So +1 here.
> 5. JEP-0124: HTTP Binding. Ian, do you think this is ready to go? It
> seems that we still need to add the text about certificate consistency.
> IMHO it might be better to finish the discussion on the Standards-JIG
> list (or off-list) before approving the next version. So I'd say let's
> punt on this for now, clean it up, then approve 1.5 so that I can seek
> an expert security review at that time (once we've cleaned up everything
> we can see).
> 6-9. These all relate to forwarding. I've modified forwarding-delivery
> so that the from address is the forwarding address, not the forwarding
> server, not sure if that meets Ralph's objections. But I'm +1 on getting
> these out there.
> 10. JEP-0078: Non-SASL Authentication. Oops, this expired again back in
> October. I'm +1 on extending its lease on life for another 6 months but
> I think the time is coming when this can be changed to Deprecated (maybe
> in 6 or 12 months, e.g. when we are close to publishing rfc3920bis). For
> the logic behind expiration dates, see
> 11. Proto-JEP: Server-Side Message Archiving. I'm +1 obviously.
> 12. Proto-JEP: Jingle Video Media Description Format. +1.
> 13. Proto-JEP: Jingle DTMF. +1.
> 14. Proto-JEP: Application-Specific Error Conditions. +1
> 15. Proto-JEP: Zoep. I may recuse myself from this discussion. But in
> general I am always +1 on publishing JEPs, let them sink or swim on
> their own merits.
> - --
> Peter Saint-Andre
> Jabber Software Foundation
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> -----END PGP SIGNATURE-----
"Got JABBER(R)?" <http://www.jabber.org/>
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3543 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mail.jabber.org/pipermail/council/attachments/20060323/083c253b/smime.bin
More information about the Council