source: draft-ietf-stox-im.xml

Last change on this file was 73, checked in by stpeter@…, 9 years ago


  • Property svn:mime-type set to text/plain
File size: 36.5 KB
1<?xml version="1.0"?>
2<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
3<?rfc compact="yes"?>
4<?rfc sortrefs="yes"?>
5<?rfc strict="yes"?>
6<?rfc symrefs="yes"?>
7<?rfc toc="yes"?>
8<?rfc tocdepth="1"?>
9<rfc category='std' docName='draft-ietf-stox-im-08' ipr='trust200902'>
11  <front>
12    <title abbrev="SIP-XMPP Interworking: IM">Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Instant Messaging</title>
13    <author initials="P." surname="Saint-Andre" fullname="Peter Saint-Andre">
14      <organization>&amp;yet</organization>
15      <address>
16        <postal>
17          <street>P.O. Box 787</street>
18          <city>Parker</city>
19          <region>CO</region>
20          <code>80134</code>
21          <country>USA</country>
22        </postal>
23        <email></email>
24      </address>
25    </author>
26    <author initials="A." surname="Houri" fullname="Avshalom Houri">
27      <organization>IBM</organization>
28      <address>
29        <postal>
30          <street>Rorberg Building, Pekris 3</street>
31          <city>Rehovot</city>
32          <code>76123</code>
33          <country>Israel</country>
34        </postal>
35        <email></email>
36      </address>
37    </author>
38    <author initials="J." surname="Hildebrand" fullname="Joe Hildebrand">
39      <organization>Cisco Systems, Inc.</organization>
40      <address>
41        <postal>
42          <street>1899 Wynkoop Street, Suite 600</street>
43          <city>Denver</city>
44          <region>CO</region>
45          <code>80202</code>
46          <country>USA</country>
47        </postal>
48        <email></email>
49      </address>
50    </author>
51    <date/>
52    <area>RAI</area>
53    <keyword>XMPP</keyword>
54    <keyword>Jabber</keyword>
55    <keyword>SIP</keyword>
56    <keyword>SIMPLE</keyword>
57    <keyword>IM</keyword>
58    <keyword>Instant Messaging</keyword>
60    <abstract>
61      <t>This document defines a bidirectional protocol mapping for the exchange of single instant messages between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP).</t>
62    </abstract>
63  </front>
65  <middle>
67    <section title="Introduction" anchor="intro">
68      <t>In order to help ensure interworking between instant messaging (IM) systems that conform to the instant messaging / presence requirements <xref target="RFC2779"/>, it is important to clearly define protocol mappings between such systems.  Within the IETF, work has proceeded on two instant messaging technologies:</t>
69      <t>
70        <list style='symbols'>
71          <t>Various extensions to the Session Initiation Protocol (<xref target="RFC3261"/>) for instant messaging, in particular the MESSAGE method extension <xref target='RFC3428'/></t>
72          <t>The Extensible Messaging and Presence Protocol (XMPP), which consists of a formalization of the core XML streaming protocols developed originally by the Jabber open-source community; the relevant specifications are <xref target='RFC6120'/> for the XML streaming layer and <xref target='RFC6121'/> for basic presence and instant messaging extensions</t>
73        </list>
74      </t>
75      <t>One approach to helping ensure interworking between these protocols is to map each protocol to the abstract semantics described in <xref target="RFC3860"/>; that is the approach taken by <xref target="I-D.ietf-simple-cpim-mapping"/> and <xref target="RFC3922"/>.  By contrast, the approach taken in this document is to directly map semantics from one protocol to another (i.e., from SIP/SIMPLE to XMPP and vice-versa).</t>
76      <t>Both XMPP and IM-capable SIP systems enable entities to exchange "instant messages".  The term "instant message" usually refers to a message sent between two entities for delivery in close to real time (rather than a message that is stored and forwarded to the intended recipient upon request).  This document covers single messages only (sometimes called "pager-mode" messaging), since they form the lowest common denominator for IM.  Separate documents cover one-to-one chat sessions <xref target='I-D.ietf-stox-chat'/> and multi-party groupchat <xref target='I-D.ietf-stox-groupchat'/>.</t>
77      <t>The architectural assumptions underlying such direct mappings are provided in <xref target='I-D.ietf-stox-core'/>, including mapping of addresses and error conditions.  The mappings specified in this document cover basic instant messaging functionality, i.e., the exchange of a single instant message between a SIP user and an XMPP user in either direction.  Mapping of more advanced functionality is out of scope for this document, but other documents in this "series" cover such topics.</t>
78    </section>
80    <section title="Intended Audience" anchor="audience">
81      <t>The documents in this series are intended for use by software developers who have an existing system based on one of these technologies (e.g., SIP), and would like to enable communication from that existing system to systems based on the other technology (e.g., XMPP).  We assume that readers are familiar with the core specifications for both SIP <xref target='RFC3261'/> and XMPP <xref target='RFC6120'/>, with the base document for this series <xref target='I-D.ietf-stox-core'/>, and with the following IM-related specifications:</t>
82      <t>
83        <list style='symbols'>
84          <t>Session Initiation Protocol (SIP) Extension for Instant Messaging <xref target='RFC3428'/></t>
85          <t>Extensible Messaging and Presence Protocol: Instant Messaging and Presence <xref target='RFC6121'/></t>
86        </list>
87      </t>
88    </section>
90    <section title="Terminology" anchor="terms">
91      <t>A number of terms used here are explained in <xref target='RFC3261'/>, <xref target='RFC3428'/>, <xref target='RFC6120'/>, and <xref target='RFC6121'/>.</t>
92      <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in <xref target='RFC2119'/>.</t>
93    </section>
95    <section title="XMPP to SIP" anchor="xmpp2sip">
96      <t>As described in <xref target="RFC6121"/>, a single instant message is an XML &lt;message/&gt; stanza of type "normal" sent over an XML stream (since "normal" is the default for the 'type' attribute of the &lt;message/&gt; stanza, the attribute is often omitted).  In this document we will assume that such a message is sent from an XMPP client to an XMPP server over an XML stream negotiated between the client and the server, and that the client is controlled by a human user (this is a simplifying assumption introduced for explanatory purposes only; the XMPP sender could be an automated client, a component such as a workflow application, a server, etc.).</t>
97      <t>When Juliet wants to send an instant message to Romeo, she interacts with her XMPP client, which generates an XMPP &lt;message/&gt; stanza.  The syntax of the &lt;message/&gt; stanza, including required and optional elements and attributes, is defined in <xref target="RFC6121"/> (for single instant messages, the value of the 'to' address SHOULD be a "bare JID" of the form "localpart@domainpart").  The following is an example of such a stanza:</t>
98      <figure>
99        <preamble>Example 1: XMPP user sends message</preamble>
100        <artwork><![CDATA[
101|  <message from=''
102|           to=''>
103|    <body>Art thou not Romeo, and a Montague?</body>
104|  </message>
105        ]]></artwork>
106      </figure>
107      <t>Upon receiving such a message stanza, the XMPP server needs to determine the identity of the domainpart in the 'to' address, which it does by following the procedures explained in Section 5 of <xref target='I-D.ietf-stox-core'/>.  If the domain is a SIP domain, the XMPP server will hand off the message stanza to an XMPP-to-SIP gateway or connection manager that natively communicates with IM-aware SIP servers.</t>
108      <t>The XMPP-SIP gateway is then responsible for translating the XMPP message stanza into a SIP MESSAGE request from the XMPP user to the SIP user:</t>
109      <figure>
110        <preamble>Example 2: XMPP user sends message (SIP transformation)</preamble>
111        <artwork><![CDATA[
112|  MESSAGE SIP/2.0
113|  Via: SIP/2.0/TCP;branch=z9hG4bK776sgdkse
114|  Max-Forwards: 70
115|  To:
116|  From: <;gr=balcony>;tag=12345
117|  Call-ID: D9AA95FD-2BD5-46E2-AF0F-6CFAA96BDDFA
118|  CSeq: 1 MESSAGE
119|  Content-Type: text/plain
120|  Content-Length: 35
122|  Art thou not Romeo, and a Montague?
123        ]]></artwork>
124      </figure>
125      <t>The destination SIP server is responsible for delivering the message to the intended recipient, and the recipient is responsible for generating a response (e.g., 200 OK).</t>
126      <figure>
127        <preamble>Example 3: SIP user agent indicates receipt of message</preamble>
128        <artwork><![CDATA[
129|  SIP/2.0 200 OK
130|  Via: SIP/2.0/TCP;branch=z9hG4bK776sgdkse
131|  From:;tag=vwxyz
132|  To:;tag=12345
133|  Call-ID: D9AA95FD-2BD5-46E2-AF0F-6CFAA96BDDFA
134|  CSeq: 1 MESSAGE
135|  Content-Length: 0
136        ]]></artwork>
137      </figure>
138      <t>As described in <xref target='RFC3428'/>, a downstream proxy could fork a MESSAGE request, but it would return only one 200 OK to the gateway.</t>
139      <t><list style='empty'><t>Informational Note: This document does not specify handling of the 200 OK by the XMPP-SIP gateway (e.g., to enable message acknowledgements).  See <xref target='I-D.ietf-stox-chat'/> for a mapping of message acknowledgements in the context of one-to-one chat sessions.</t></list></t>
140      <t>The mapping of XMPP syntax to SIP syntax SHOULD be as shown in the following table.  (Mappings for several aspects not mentioned here are specified in <xref target='I-D.ietf-stox-chat'/>.)</t>
141      <figure>
142        <preamble>Table 1: Message syntax mapping from XMPP to SIP</preamble>
143        <artwork><![CDATA[
144   +-----------------------------+--------------------------+
145   |  XMPP Element or Attribute  |  SIP Header or Contents  |
146   +-----------------------------+--------------------------+
147   |  <body/>                    |  body of MESSAGE         |
148   |  <subject/>                 |  Subject                 |
149   |  <thread/>                  |  Call-ID                 |
150   |  from                       |  From (1)                |
151   |  id                         |  (no mapping)            |
152   |  to                         |  To or Request-URI       |
153   |  type                       |  (no mapping) (2)        |
154   |  xml:lang                   |  Content-Language        |
155   +-----------------------------+--------------------------+
156        ]]></artwork>
157      </figure>
158      <t>
159        <list style='numbers'>
160          <t>As shown in the foregoing example and described in <xref target='I-D.ietf-stox-core'/>, the XMPP-SIP gateway SHOULD map the full JID (localpart@domainpart/resourcepart) of the XMPP sender to the SIP From header and include the resourcepart as the GRUU portion <xref target='RFC5627'/> of the SIP URI.</t>
161          <t>Because there is no SIP header field that matches the meaning of the XMPP message 'type' values ("normal", "chat", "groupchat", "headline", "error"), no general mapping is possible here.</t>
162        </list>
163      </t>
164    </section>
166    <section title="SIP to XMPP" anchor="sip2xmpp">
167      <t>As described in <xref target="RFC3428"/>, a single instant message is a SIP MESSAGE request sent from a SIP user agent to an intended recipient who is most generally referenced by an Instant Message URI of the form &lt;im:user@domain&gt; but who might be referenced by a SIP or SIPS URI of the form &lt;sip:user@domain&gt; or &lt;sips:user@domain&gt;.  Here again we introduce the simplifying assumption that the user agent is controlled by a human user, whom we shall dub &lt;;.</t>
168      <t>When Romeo wants to send an instant message to Juliet, he interacts with his SIP user agent, which generates a SIP MESSAGE request.  The syntax of the MESSAGE request is defined in <xref target="RFC3428"/>.  The following is an example of such a request:</t>
169      <figure>
170        <preamble>Example 4: SIP user sends message</preamble>
171        <artwork><![CDATA[
172|  MESSAGE SIP/2.0
173|  Via: SIP/2.0/TCP;branch=z9hG4bKeskdgs677
174|  Max-Forwards: 70
175|  To:
176|  From:;tag=vwxyz
177|  Call-ID: 9E97FB43-85F4-4A00-8751-1124FD4C7B2E
178|  CSeq: 1 MESSAGE
179|  Content-Type: text/plain
180|  Content-Length: 44
182|  Neither, fair saint, if either thee dislike.
183        ]]></artwork>
184      </figure>
185      <t>Section 5 of <xref target="RFC3428"/> stipulates that a SIP User Agent presented with an im: URI should resolve it to a sip: or sips: URI.  Therefore we assume that the Request-URI of a request received by an IM-capable SIP-XMPP gateway will contain a sip: or sips: URI.  Upon receiving the MESSAGE, the SIP (MSRP) server needs to determine the identity of the domain portion of the Request-URI or To header, which it does by following the procedures explained in Section 5 of <xref target='I-D.ietf-stox-core'/>.  If the domain is an XMPP domain, the SIP server will hand off the MESSAGE to an associated SIP-XMPP gateway or connection manager that natively communicates with XMPP servers.</t>
186      <t>The SIP-to-XMPP gateway is then responsible for translating the request into an XMPP message stanza from the SIP user to the XMPP user and returning a SIP "200 OK" message to the sender:</t>
187      <figure>
188        <preamble>Example 5: SIP user sends message (XMPP transformation)</preamble>
189        <artwork><![CDATA[
190|  <message from=''
191|           to=''>
192|    <body>Neither, fair saint, if either thee dislike.</body>
193|  </message>
194        ]]></artwork>
195      </figure>
196      <t>Note that the stanza handling rules specified in <xref target='RFC6121'/> allow the receiving XMPP server to deliver a message stanza whose 'to' address is a bare JID ("localpart@domainpart") to multiple connected devices.  This is similar to the "forking" of messages in SIP.</t>
197      <t>The mapping of SIP syntax to XMPP syntax SHOULD be as shown in the following table.  (Mappings for several aspects not mentioned here are specified in <xref target='I-D.ietf-stox-chat'/>.)</t>
198      <figure>
199        <preamble>Table 2: Message syntax mapping from SIP to XMPP</preamble>
200        <artwork><![CDATA[
201   +--------------------------+-----------------------------+
202   |  SIP Header or Contents  |  XMPP Element or Attribute  |
203   +--------------------------+-----------------------------+
204   |  Call-ID                 |  <thread/>                  |
205   |  Content-Language        |  xml:lang                   |
206   |  CSeq                    |  (no mapping)               |
207   |  From                    |  from (1)                   |
208   |  Subject                 |  <subject/>                 |
209   |  Request-URI or To       |  to                         |
210   |  body of MESSAGE         |  <body/>                    |
211   +--------------------------+-----------------------------+
212        ]]></artwork>
213      </figure>
214      <t>
215        <list style='numbers'>
216          <t>As shown in the foregoing example and described in <xref target='I-D.ietf-stox-core'/>, if the IM-capable SIP-XMPP gateway has information about the GRUU <xref target='RFC5627'/> of the particular endpoint that sent the SIP message then it SHOULD map the sender's address to a full JID (localpart@domainpart/resourcepart) in the 'from' attribute of the XMPP stanza and include the GRUU as the resourcepart.</t>
217        </list>
218      </t>
219      <t>When transforming SIP pager-mode messages, an IM-capable SIP-XMPP gateway SHOULD specify no XMPP 'type' attribute or, equivalently, a 'type' attribute whose value is "normal" <xref target='RFC6121'/>.</t>
220      <t>See <xref target='content'/> of this document about the handling of SIP message bodies that contain content types other than plain text.</t>
221    </section>
223    <section title='Content Types' anchor="content">
224      <t>SIP requests of type MESSAGE are allowed to contain essentially any content type.  The recommended procedures for SIP-to-XMPP gateways to use in handling these content types are as follows.</t>
225      <t>An IM-aware SIP-to-XMPP gateway MUST process SIP messages that contain message bodies of type "text/plain" and MUST encapsulate such message bodies as the XML character data of the XMPP &lt;body/&gt; element.</t>
226      <t>An IM-aware SIP-to-XMPP gateway SHOULD process SIP messages that contain message bodies of type "text/html"; if so, a gateway MUST transform the "text/html" content into XHTML content that conforms to the XHTML-IM Integration Set specified in <xref target='XEP-0071'/>.</t>
227      <t>Although an IM-aware SIP-to-XMPP gateway MAY process SIP messages that contain message bodies of types other than "text/plain" and "text/html", the handling of such content types is a matter of implementation.</t>
228    </section>
230    <section title="Internationalization Considerations" anchor="i18n">
231      <t>Both XMPP and SIP support the UTF-8 encoding <xref target='RFC3629'/> of Unicode characters <xref target='UNICODE'/> within messages, and signalling of the language for a particular message (in XMPP via the 'xml:lang' attribute and in SIP via the Content-Language header).  Several examples follow, using the "XML Notation" for Unicode characters outside the ASCII range described in <xref target='RFC3987'/>.</t>
232      <figure>
233        <preamble>Example 6: SIP user sends message</preamble>
234        <artwork><![CDATA[
235|  MESSAGE SIP/2.0
236|  Via: SIP/2.0/TCP;branch=z9hG4bKeskdgs677
237|  Max-Forwards: 70
238|  To:
239|  From:;tag=vwxyz
240|  Call-ID: 9E97FB43-85F4-4A00-8751-1124FD4C7B2E
241|  CSeq: 1 MESSAGE
242|  Content-Type: text/plain
243|  Content-Length: 45
244|  Content-Language: cs
246|  Nic z ob&#xC3A9;ho, m&#xC3A1; d&#xC49B;vo spanil&#xC3A1;,
247|  nenavid&#xC3AD;&#xC5A1;-li jedno nebo druh&#xC3A9;.
248        ]]></artwork>
249      </figure>
250      <figure>
251        <preamble>Example 7: SIP user sends message (XMPP transformation)</preamble>
252        <artwork><![CDATA[
253|  <message from=''
254|           to=''
255|           xml:lang='cs'>
256|    <body>
257|  Nic z ob&#xC3A9;ho, m&#xC3A1; d&#xC49B;vo spanil&#xC3A1;,
258|  nenavid&#xC3AD;&#xC5A1;-li jedno nebo druh&#xC3A9;.
259|    </body>
260|  </message>
261        ]]></artwork>
262      </figure>
263    </section>
265    <section title="IANA Considerations" anchor="iana">
266      <t>This document requests no actions of IANA.</t>
267    </section>
269    <section title='Security Considerations' anchor="sec">
270      <t>Detailed security considerations for instant messaging protocols are given in <xref target='RFC2779'/>, for SIP-based instant messaging in <xref target="RFC3428"/> (see also <xref target="RFC3261"/>), and for XMPP-based instant messaging in <xref target="RFC6121"/> (see also <xref target="RFC6120"/>).  The security considerations provided in <xref target='I-D.ietf-stox-core'/> also apply.</t>
271      <t>This document specifies methods for exchanging instant messages through a gateway that translates between SIP and XMPP.  Such a gateway MUST be compliant with the minimum security requirements of the instant messaging protocols for which it translates (i.e., SIP and XMPP).  The addition of gateways to the security model of instant messaging specified in <xref target="RFC2779"/> introduces some new risks.  In particular, end-to-end security properties (especially confidentiality and integrity) between instant messaging user agents that interface through an IM-capable SIP-XMPP gateway can be provided only if common formats are supported.  Specification of those common formats is out of scope for this document, although it is preferred to use <xref target="RFC3862"/> for instant messages.</t>
272    </section>
274  </middle>
276  <back>
278    <references title="Normative References">
280<reference anchor='I-D.ietf-stox-chat'>
282<title>Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): One-to-One Text Chat Sessions</title>
283<author initials='P' surname='Saint-Andre' fullname='Peter Saint-Andre'>
284    <organization />
286<author initials='S' surname='Loreto' fullname='Salvatore Loreto'>
287    <organization />
289<date month='March' day='11' year='2014' />
290<abstract><t>This document defines a bidirectional protocol mapping for the exchange of instant messages in the context of a one-to-one chat session between a user of the Session Initiation Protocol (SIP) and a user of the Extensible Messaging and Presence Protocol (XMPP). Specifically for SIP text chat, this document specifies a mapping to the Message Session Relay Protocol (MSRP).</t></abstract>
292<seriesInfo name='Internet-Draft' value='draft-ietf-stox-chat-06' />
293<format type='TXT'
294        target='' />
297<reference anchor='I-D.ietf-stox-core'>
299<title>Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Core</title>
300<author initials='P' surname='Saint-Andre' fullname='Peter Saint-Andre'>
301    <organization />
303<author initials='A' surname='Houri' fullname='Avshalom Houri'>
304    <organization />
306<author initials='J' surname='Hildebrand' fullname='Joe Hildebrand'>
307    <organization />
309<date month='February' day='11' year='2014' />
310<abstract><t>As a foundation for the definition of application-specific, bi-directional protocol mappings between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP), this document specifies the architectural assumptions underlying such mappings as well as the mapping of addresses and error conditions.</t></abstract>
312<seriesInfo name='Internet-Draft' value='draft-ietf-stox-core-11' />
313<format type='TXT'
314        target='' />
317<reference anchor='RFC2119'>
318  <front>
319    <title abbrev='RFC Key Words'>Key words for use in RFCs to Indicate Requirement Levels</title>
320    <author initials='S.' surname='Bradner' fullname='Scott Bradner'>
321      <organization>Harvard University</organization>
322      <address>
323        <postal>
324          <street>1350 Mass. Ave.</street>
325          <street>Cambridge</street>
326          <street>MA 02138</street>
327        </postal>
328        <phone>- +1 617 495 3864</phone>
329        <email>-</email>
330      </address>
331    </author>
332    <date month='March' year='1997'></date>
333    <area>General</area>
334    <keyword>keyword</keyword>
335    <abstract>
336      <t>In many standards track documents several words are used to signify the requirements in the specification.  These words are often capitalized.  This document defines these words as they should be interpreted in IETF documents.  Authors who follow these guidelines should incorporate this phrase near the beginning of their document:
337        <list>
338          <t>The key words &quot;MUST&quot;, &quot;MUST NOT&quot;, &quot;REQUIRED&quot;, &quot;SHALL&quot;, &quot;SHALL NOT&quot;, &quot;SHOULD&quot;, &quot;SHOULD NOT&quot;, &quot;RECOMMENDED&quot;,  &quot;MAY&quot;, and &quot;OPTIONAL&quot; in this document are to be interpreted as described in RFC 2119.</t>
339        </list>
340      </t>
341      <t>Note that the force of these words is modified by the requirement level of the document in which they are used.</t>
342    </abstract>
343  </front>
344  <seriesInfo name='BCP' value='14' />
345  <seriesInfo name='RFC' value='2119' />
348<reference anchor='RFC3261'>
350<title>SIP: Session Initiation Protocol</title>
351<author initials='J.' surname='Rosenberg' fullname='J. Rosenberg'>
352<organization /></author>
353<author initials='H.' surname='Schulzrinne' fullname='H. Schulzrinne'>
354<organization /></author>
355<author initials='G.' surname='Camarillo' fullname='G. Camarillo'>
356<organization /></author>
357<author initials='A.' surname='Johnston' fullname='A. Johnston'>
358<organization /></author>
359<author initials='J.' surname='Peterson' fullname='J. Peterson'>
360<organization /></author>
361<author initials='R.' surname='Sparks' fullname='R. Sparks'>
362<organization /></author>
363<author initials='M.' surname='Handley' fullname='M. Handley'>
364<organization /></author>
365<author initials='E.' surname='Schooler' fullname='E. Schooler'>
366<organization /></author>
367<date month='June' year='2002' /></front>
368<seriesInfo name='RFC' value='3261' />
369<format type='TXT' octets='647976' target='' />
372<reference anchor="RFC3428">
374<title>Session Initiation Protocol (SIP) Extension for Instant Messaging</title>
375<author initials='B.' surname='Campbell' fullname='B. Campbell'>
376<organization /></author>
377<author initials='J.' surname='Rosenberg' fullname='J. Rosenberg'>
378<organization /></author>
379<author initials='H.' surname='Schulzrinne' fullname='H. Schulzrinne'>
380<organization /></author>
381<author initials='C.' surname='Huitema' fullname='C. Huitema'>
382<organization /></author>
383<author initials='D.' surname='Gurle' fullname='D. Gurle'>
384<organization /></author>
385<date month='December' year='2002' /></front>
386<seriesInfo name='RFC' value='3428' />
387<format type='TXT' octets='41475' target='' />
390<reference anchor='RFC5627'>
392<title>Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP)</title>
393<author initials='J.' surname='Rosenberg' fullname='J. Rosenberg'>
394<organization /></author>
395<date year='2009' month='October' />
397<t>Several applications of the Session Initiation Protocol (SIP) require a user agent (UA) to construct and distribute a URI that can be used by anyone on the Internet to route a call to that specific UA instance.  A URI that routes to a specific UA instance is called a Globally Routable UA URI (GRUU).  This document describes an extension to SIP for obtaining a GRUU from a registrar and for communicating a GRUU to a peer within a dialog. [STANDARDS-TRACK]</t></abstract></front>
398<seriesInfo name='RFC' value='5627' />
399<format type='TXT' octets='94790' target='' />
402<reference anchor='RFC6120'>
404<title>Extensible Messaging and Presence Protocol (XMPP): Core</title>
405<author initials='P.' surname='Saint-Andre' fullname='P. Saint-Andre'>
406<organization /></author>
407<date year='2011' month='March' />
409<t>The Extensible Messaging and Presence Protocol (XMPP) is an application profile of the Extensible Markup Language (XML) that enables the near-real-time exchange of structured yet extensible data between any two or more network entities.  This document defines XMPP's core protocol methods: setup and teardown of XML streams, channel encryption, authentication, error handling, and communication primitives for messaging, network availability ("presence"), and request-response interactions.  This document obsoletes RFC 3920. [STANDARDS-TRACK]</t></abstract></front>
410<seriesInfo name='RFC' value='6120' />
411<format type='TXT' octets='451942' target='' />
414<reference anchor='RFC6121'>
416<title>Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence</title>
417<author initials='P.' surname='Saint-Andre' fullname='P. Saint-Andre'>
418<organization /></author>
419<date year='2011' month='March' />
421<t>This document defines extensions to core features of the Extensible Messaging and Presence Protocol (XMPP) that provide basic instant messaging (IM) and presence functionality in conformance with the requirements in RFC 2779.  This document obsoletes RFC 3921. [STANDARDS-TRACK]</t></abstract></front>
422<seriesInfo name='RFC' value='6121' />
423<format type='TXT' octets='244800' target='' />
426<reference anchor="XEP-0071">
427  <front>
428    <title>XHTML-IM</title>
429    <author initials="P." surname="Saint-Andre" fullname="Peter Saint-Andre">
430      <organization/>
431      <address>
432        <email></email>
433      </address>
434    </author>
435    <date day="28" month="November" year="2012"/>
436  </front>
437  <seriesInfo name="XSF XEP" value="0071"/>
438  <format type="HTML" target=""/>
441    </references>
443    <references title="Informative References">
445<reference anchor="I-D.ietf-simple-cpim-mapping">
447<title>CPIM Mapping of SIMPLE Presence and Instant Messaging</title>
448<author initials="J" surname="Rosenberg" fullname="Jonathan  Rosenberg">
449    <organization />
451<author initials="B" surname="Campbell" fullname="Ben Campbell">
452    <organization />
454<date month="June" day="28" year="2002" />
456<seriesInfo name="Internet-Draft" value="draft-ietf-simple-cpim-mapping-01" />
457<format type="TXT"
458        target="" />
461<reference anchor='I-D.ietf-stox-groupchat'>
463<title>Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Groupchat</title>
464<author initials='P' surname='Saint-Andre' fullname='Peter Saint-Andre'>
465    <organization />
467<author initials='S' surname='Corretge' fullname='Saul Corretge'>
468    <organization />
470<author initials='S' surname='Loreto' fullname='Salvatore Loreto'>
471    <organization />
473<date month='December' day='12' year='2013' />
474<abstract><t>This document defines a bidirectional protocol mapping for the exchange of instant messages in the context of a multiparty chat session among users of the Session Initiation Protocol (SIP) and users of the Extensible Messaging and Presence Protocol (XMPP). Specifically, this document defines a mapping between the SIP-based Message Session Relay Protocol (MSRP) and the XMPP Multi-User Chat (MUC) extension.</t></abstract>
476<seriesInfo name='Internet-Draft' value='draft-ietf-stox-groupchat-02' />
477<format type='TXT'
478        target='' />
481<reference anchor="RFC2779">
483<title abbrev='Instant Messaging/Presence Protocol'>Instant Messaging / Presence Protocol Requirements</title>
484<author initials='M.' surname='Day' fullname='Mark Day'>
485<organization>SightPath, Inc.</organization>
488<street>135 Beaver Street</street>
494<author initials='S.' surname='Aggarwal' fullname='Sonu Aggarwal'>
495<organization>Microsoft Corporation</organization>
498<street>One Microsoft Way</street>
504<author initials='J.' surname='Vincent' fullname='Jesse Vincent'>
505<organization>Into Networks, Inc.</organization>
508<street>150 Cambridgepark Drive</street>
514<date month='February' year='2000' />
516<t>Presence and Instant Messaging have recently emerged as a new medium of communications over the Internet.  Presence is a means for finding, retrieving, and subscribing to changes in the presence information (e.g.  "online" or "offline") of other users.  Instant messaging is a means for sending small, simple messages that are delivered immediately to online users.</t>
517<t>Applications of presence and instant messaging currently use independent, non-standard and non-interoperable protocols developed by various vendors.  The goal of the Instant Messaging and Presence Protocol (IMPP) Working Group is to define a standard protocol so that independently developed applications of instant messaging and/or   presence can interoperate across the Internet.  This document defines a minimal set of requirements that IMPP must meet.</t></abstract></front>
518<seriesInfo name='RFC' value='2779' />
519<format type='TXT' octets='47420' target='' />
522<reference anchor='RFC3629'>
524<title>UTF-8, a transformation format of ISO 10646</title>
525<author initials='F.' surname='Yergeau' fullname='F. Yergeau'>
526<organization /></author>
527<date year='2003' month='November' />
529<t>ISO/IEC 10646-1 defines a large character set called the Universal Character Set (UCS) which encompasses most of the world's writing systems.  The originally proposed encodings of the UCS, however, were not compatible with many current applications and protocols, and this has led to the development of UTF-8, the object of this memo.  UTF-8 has the characteristic of preserving the full US-ASCII range, providing compatibility with file systems, parsers and other software that rely on US-ASCII values but are transparent to other values.  This memo obsoletes and replaces RFC 2279.</t></abstract></front>
530<seriesInfo name='STD' value='63' />
531<seriesInfo name='RFC' value='3629' />
532<format type='TXT' octets='33856' target='' />
535<reference anchor="RFC3860">
537<title>Common Profile for Instant Messaging (CPIM)</title>
538<author initials='J.' surname='Peterson' fullname='J. Peterson'>
539<organization /></author>
540<date year='2004' month='August' /></front>
541<seriesInfo name='RFC' value='3860' />
542<format type='TXT' octets='26486' target='' />
545<reference anchor="RFC3862">
547<title>Common Presence and Instant Messaging (CPIM): Message Format</title>
548<author initials='G.' surname='Klyne' fullname='G. Klyne'>
549<organization /></author>
550<author initials='D.' surname='Atkins' fullname='D. Atkins'>
551<organization /></author>
552<date year='2004' month='August' /></front>
553<seriesInfo name='RFC' value='3862' />
554<format type='TXT' octets='56133' target='' />
557<reference anchor="RFC3922">
558  <front>
559    <title>Mapping the Extensible Messaging and Presence Protocol (XMPP) to Common Presence and Instant Messaging (CPIM)</title>
560    <author initials='P.' surname='Saint-Andre' fullname='P. Saint-Andre'>
561      <organization>Jabber Software Foundation</organization>
562    </author>
563    <date year='2004' month='October' />
564  </front>
565  <seriesInfo name='RFC' value='3922' />
566  <format type='TXT' octets='70790' target='' />
569<reference anchor='RFC3987'>
571<title>Internationalized Resource Identifiers (IRIs)</title>
572<author initials='M.' surname='Duerst' fullname='M. Duerst'>
573<organization /></author>
574<author initials='M.' surname='Suignard' fullname='M. Suignard'>
575<organization /></author>
576<date year='2005' month='January' />
578<t>This document defines a new protocol element, the Internationalized Resource Identifier (IRI), as a complement of the Uniform Resource Identifier (URI). An IRI is a sequence of characters from the Universal Character Set (Unicode/ISO 10646). A mapping from IRIs to URIs is defined, which means that IRIs can be used instead of URIs, where appropriate, to identify resources.&lt;/t>&lt;t> The approach of defining a new protocol element was chosen instead of extending or changing the definition of URIs. This was done in order to allow a clear distinction and to avoid incompatibilities with existing software. Guidelines are provided for the use and deployment of IRIs in various protocols, formats, and software components that currently deal with URIs.</t></abstract></front>
579<seriesInfo name='RFC' value='3987' />
580<format type='TXT' octets='111190' target='' />
583<reference anchor="UNICODE" target="">
584  <front>
585    <title>The Unicode Standard, Version 6.3</title>
586    <author>
587      <organization>The Unicode Consortium</organization>
588    </author>
589    <date year="2013" />
590  </front>
593    </references>
595    <section title="Acknowledgements" anchor="ack">
596      <t>The authors wish to thank the following individuals for their feedback: Mary Barnes, Dave Cridland, Dave Crocker, Adrian Georgescu, Christer Holmberg, Saul Ibarra Corretge, Olle Johansson, Paul Kyzivat, Salvatore Loreto, Daniel-Constantin Mierla, and Tory Patnoe.</t>
597      <t>The authors gratefully acknowledge the assistance of Markus Isomaki and Yana Stamcheva as the working group chairs and Gonzalo Camarillo and Alissa Cooper as the sponsoring Area Directors.</t>
598      <t>Peter Saint-Andre wishes to acknowledge Cisco Systems, Inc., for employing him during his work on earlier versions of this document.</t>
599    </section>
601  </back>
Note: See TracBrowser for help on using the repository browser.