meeting agenda, 2006-04-24

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Just now in councilconference.jabber.org we decided to
postpone this to
Friday, April 28. Ian and I are going to meet tomorrow
(IRL!) to gain
consensus on JEP-0124, so the hope is we can have final text
for version
1.5 in time for Friday.

I'll post further about some of the other items today.

/psa

Peter Saint-Andre wrote:
> A proposed agenda for tomorrow's meeting of the Jabber
Council is here:
> 
> http://www.jabber.org/council/meetings/agendas/200
6-04-25.html
> 
> Agenda bashing is welcome as always.
> 
> Peter
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


iD8DBQFETjd/NF1RSzyt3NURAmllAKDhoMXqZyc7BAyJDYBjwri5jYhEtwCg
nIHw
SVyCvSyvlRAV9dr/X2KBvyA=
=0n6G
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Peter Saint-Andre wrote:
> Just now in councilconference.jabber.org we
decided to postpone this to
> Friday, April 28. Ian and I are going to meet tomorrow
(IRL!) to gain
> consensus on JEP-0124, so the hope is we can have final
text for version
> 1.5 in time for Friday.
> 
> I'll post further about some of the other items today.

As promised...

1. JEP-0124: HTTP Binding. See above, will post more about
it after Ian
and I talk tomorrow.

2. JEP-0172: User Nickname. A very simple extension. It's
possible we
would add a use case for Jingle if and when JEP-0166
discusses forking
(i.e., sending a Jingle request to a bare JID), but that
would not
result in any changes to the format, only a few more
examples.

3. JEP-0182: Application-Specific Error Conditions. This one
is strictly
procedural so that we can create the relevant registry.

4. JEP-0060: Publish-Subscribe. It would be good to get
closure on the
revisions sometime before the end of the Council term. 

5. JEP-0030: Service Discovery. It's always bothered me
that item
publication is part of JEP-0030. Even though this
functionality was
added in version 0.12, it seems more appropriate to define
it in a
separate spec, especially since people are interested in
adding info
publication as well and it seems quite late in the process
to add that
to JEP-0030. So I think that putting both disco#items and
disco#info
publication in a separate spec makes sense. One further
consideration:
it is *possible* that we would want to publish service
discovery as an
RFC (e.g., to use it as a prerequisite for a cleaned-up
version of RFC
3923) and if so I'd like the spec to be as stripped-down as
we can make
it (but we can discuss that possibility in the meeting on
Friday).

6. Proto-JEP: User Fingerprint. This proposal mirrors
JEP-0172 (User
Nickname) and enables users to include a fingerprint derived
from a key
or certificate in presence subscription requests (etc.).

Peter



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


iD8DBQFETkhHNF1RSzyt3NURAo/HAKCn69wEUAuTVVD9P5sCm6Az9riEOgCg
i4yW
insIsXj3dUFIWSxrQGbBTYY=
=46/v
-----END PGP SIGNATURE-----