Presence and IntComm WG

[Neal McBurnett <>]

Now there is an IETF standards-track way to link to jabber users and
conference rooms from the web, etc.  E.g.

 
xmpp:
 
xmpp:

in the new RFC 4622:

 http://potaroo.net/ietf/idref/rfc4622/

These URIs aren't for use within XMPP itself - just for identifying
xmpp entities in other formats and protocols.

More interesting capabilities also exist.  E.g.

 the following XMPP IRI/URI signals the processing application to
 authenticate as its configured default account and to send a message
 to 
"":

      
xmpp:?message

 There are many potential use cases for encapsulating information in
 the query component of an XMPP IRI/URI; examples include but are not
 limited to:

   o  sending an XMPP message stanza (see [XMPP-IM]),
   o  adding a roster item (see [XMPP-IM]),
   o  sending a presence subscription (see [XMPP-IM]),
   o  probing for current presence information (see [XMPP-IM]),
   o  triggering a remote procedure call (see [JEP-0009]),
   o  discovering the identity or capabilities of another entity (see
      [JEP-0030]),
   o  joining an XMPP-based text chat room (see [JEP-0045]),
   o  interacting with publish-subscribe channels (see [JEP-0060]),
   o  providing a SOAP interface (see [JEP-0072]), and
   o  registering with another entity (see [JEP-0077]).

A comparison is drawn to the flexibility of the
"application/x-www-form-urlencoded" MIME type

I noticed some rather liberal language for a standards document,
containing a quote from

 http://potaroo.net/ietf/idref/rfc3986/

 the semantics of the fragment identifier component in XMPP IRIs/URIs
 are to be "considered unknown and, effectively, unconstrained"

I found these security tidbits interesting also:

 Malicious construction of XMPP IRIs/URIs is made less likely by the
 prohibition on port numbers in XMPP IRIs/URIs (since port numbers are
 to be discovered using [DNS-SRV] records, as specified in
 [XMPP-CORE]).

 XMPP servers SHOULD NOT natively parse XMPP IRIs/URIs but instead
 SHOULD accept only the XML wire protocol specified in [XMPP-CORE] and
 any desired extensions thereto.

 To help prevent leaking of sensitive information, passwords and other
 user credentials are forbidden in the authority component of XMPP
 IRIs/URIs; in fact they are not needed, since the fact that
 authentication in XMPP occurs via [SASL] makes it possible to use the
 SASL ANONYMOUS mechanism, if desired.

Beware the complicated conversion issues around the differences
between URIs (where non-ASCII character sets are done in encoded
ASCII) and IRIs which are generally UTF-8.  Or something like that....

Cheers,

Neal McBurnett                 http://mcburnett.org/neal/
Signed and/or sealed mail encouraged.  GPG/PGP Keyid: 2C9EBA60

----- Forwarded message from 

 -----

To: 
,
 

Cc: 

From: 

Subject: RFC 4622 on Internationalized Resource Identifiers (IRIs) and
        Uniform Resource Identifiers (URIs) for the Extensible
        Messaging and Presence Protocol (XMPP)

A new Request for Comments is now available in online RFC libraries.
        
        RFC 4622

        Title:      Internationalized Resource Identifiers (IRIs) and 
                    Uniform Resource Identifiers (URIs) for the 
                    Extensible Messaging and Presence Protocol (XMPP) 
        Author:     P. Saint-Andre
        Status:     Standards Track
        Date:       July 2006
        Mailbox:    

        Pages:      23
        Characters: 49968
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-saintandre-xmpp-iri-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4622.txt

This document defines the use of Internationalized Resource
Identifiers (IRIs) and Uniform Resource Identifiers (URIs) in
identifying or interacting with entities that can communicate via the
Extensible Messaging and Presence Protocol (XMPP).  [STANDARDS TRACK]

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and 
suggestions for improvements.Please refer to the current edition of the 
Internet Official Protocol Standards (STD 1) for the standardization 
state and status of this protocol.  Distribution of this memo is 
unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to 
.
  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to 
.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to 

 with the message body 

help: ways_to_get_rfcs. For example:

        To: 

        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to 
.
  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
.
  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

_______________________________________________
IETF-Announce mailing list

https://www1.ietf.org/mailman/listinfo/ietf-announce

----- End forwarded message -----