[Council] XMPP BOF @ IETF 74
stpeter at stpeter.im
Mon Feb 23 16:58:34 CST 2009
Peter Saint-Andre wrote:
> Plans are coming together for an XMPP BOF @ IETF 74 in San Francisco,
> probably to be held on Monday, March 23. Let's discuss in the next
> Council meeting. I'll post further before then.
See the archives for the xmppwg at xmpp.org list for details. Posting here
so we can talk in the Council meeting.
0. Does it make sense to revive the XMPP WG in order to complete work at
the IETF on some topics of interest? I see the primary topics as:
1. RFC revisions (rfc3920bis/rfc3921bis).
2. Do we need to complete interop reports? (Those might not needed until
we try to advance the core specs from Proposed to Draft, whereas right
now I think we will cycle at Proposed.)
3. Finish mappings between XMPP and SIP/SIMPLE (cf. the series of I-Ds
with names draft-saintandre-sip-xmpp-* -- currently 6 of them).
4. Mobile optimizations. So far these are mainly roster versioning and
stream management (XEP-0198). The "roster filtering" stuff discussed at
the XMPP Summit might also be worth considering. I think that "session
hush" (also discussed in Brussels) is too preliminary.
5. Replace stringprep / IDNA with something more reasonable.
6. End-to-end encryption.
7. BOSH. However, I think this is more properly part of the AppArea
meeting, see here:
So, I think we might need the following participation from the XMPP
community before the BOF:
a. Internet-Draft submissions for stream management (XEP-0198) and e2e
(Jingle-XTLS proposal). In the Council meeting let's discuss whether we
think it's OK to send this work off to the IETF. The same goes for some
of the roster work (versioning and filtering).
b. Commitments from presenters. That would include core (me), SIP-XMPP
(perhaps Salvatore Loreto from Ericsson), mobile (me, or perhaps Justin
Karneges could come up to SF to talk about XEP-0198), stringprep and
IDNA (Kurt Zeilenga or Joe Hildebrand?), e2e (probably me, I don't think
Dirk could be there), and BOSH (Jack?).
We'll talk about this more in the meeting, I just wanted to set the stage.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 6751 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mail.jabber.org/pipermail/council/attachments/20090223/3aaa87c4/attachment.bin
More information about the Council