1. 06.11.06draft-mayrhofer-enum-xmpp1 XMPP Enumservice registration draft-mayrhofer-enum-xmpp-00 Alexander Mayrhofer, enum.at mailto:alexander.mayrhofer@enum.at IETF67, San Diego, CA, USA

2. 06.11.06draft-mayrhofer-enum-xmpp2 What is XMPP?  "Extensible Messaging and Presence Protocol ("Jabber" protocol)  Streaming XML elements between endpoints in close to real time  RFC3920/3921 (core, IM+presence)  Additional standardization through "Jabber Software Foundation" (XEPs – "XMPP Enhancement Proposals, formerly JEPs)

3. 06.11.06draft-mayrhofer-enum-xmpp3 What is it being used for?  Instant Messaging  Presence ("Roster")  VoIP (Jingle/XEP-0166)  Google Talk, Dingaling, chan_jingle, etc..  The IETF jabber rooms  Vast amount of clients available  PC  PDA  Mobile (potential SMS replacement?)

4. 06.11.06draft-mayrhofer-enum-xmpp4 XMPP IRIs/URIs  Defined in RFC4622 (July 2006)  Most simplest example:  xmpp:axelm@jabber.org  But:  Internationalized  xmpp:ji%C5%99i@%C4%8Dechy.example/v%20Praze  Authentication/message component  xmpp://axelm@jabber.org/enum@ietf.org?hi%20there

5. 06.11.06draft-mayrhofer-enum-xmpp5 XMPP Enumservice  Enumservice name: "XMPP"  Enumservice type: "xmpp"  URI/IRI schemes: "xmpp"  No subtypes  Example: @INNAPTR 100 10 "u" "E2U+xmpp" "!^.*$!xmpp:axelm@jabber.org".

6. 06.11.06draft-mayrhofer-enum-xmpp6 XMPP Enumservice  Special considerations:  URI SHOULD NOT contain authentication component:  xmpp://axelm@jabber.org/support@jabber.org  Internationalized Resource Indentifiers – no wording about this yet.  Hence, currently allowed in Enumservice..  Do we care?  More issues?

7. 06.11.06draft-mayrhofer-enum-xmpp7 Draft status  Currently -00, individual draft  Straightforward Enumservice registration  Request adoption of WG item  Work on remaining open issues (IRIs?)  Then last call it?