Debian Codegraph @

rfc3994.html

raw
1 <pre>Network Working Group H. Schulzrinne
2 Request for Comments: 3994 Columbia U.
3 Category: Standards Track January 2005
4
5
6 <span class="h1">Indication of Message Composition for Instant Messaging</span>
7
8 Status of This Memo
9
10 This document specifies an Internet standards track protocol for the
11 Internet community, and requests discussion and suggestions for
12 improvements. Please refer to the current edition of the "Internet
13 Official Protocol Standards" (STD 1) for the standardization state
14 and status of this protocol. Distribution of this memo is unlimited.
15
16 Copyright Notice
17
18 Copyright (C) The Internet Society (2005).
19
20 Abstract
21
22 In instant messaging (IM) systems, it is useful to know during an IM
23 conversation whether the other party is composing a message; e.g.,
24 typing or recording an audio message. This document defines a new
25 status message content type and XML namespace that conveys
26 information about a message being composed. The status message can
27 indicate the composition of a message of any type, including text,
28 voice, or video. The status messages are delivered to the instant
29 messaging recipient in the same manner as the instant messages
30 themselves.
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Schulzrinne Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc3994">RFC 3994</a> isComposing January 2005</span>
55
56
57 Table of Contents
58
59 <a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
60 <a href="#section-2">2</a>. Terminology and Conventions . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
61 <a href="#section-3">3</a>. Description . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
62 <a href="#section-3.1">3.1</a>. Overview . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
63 <a href="#section-3.2">3.2</a>. Message Composer Behavior . . . . . . . . . . . . . . . <a href="#page-4">4</a>
64 <a href="#section-3.3">3.3</a>. Status Message Receiver Behavior . . . . . . . . . . . . <a href="#page-5">5</a>
65 <a href="#section-3.4">3.4</a>. Message Content . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
66 <a href="#section-3.5">3.5</a>. Additional Status Information . . . . . . . . . . . . . <a href="#page-6">6</a>
67 <a href="#section-4">4</a>. Using the Status Message . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
68 <a href="#section-5">5</a>. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
69 <a href="#section-6">6</a>. XML Document Format . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
70 <a href="#section-6.1">6.1</a>. XML Schema . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
71 <a href="#section-7">7</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
72 <a href="#section-8">8</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
73 8.1. Content-Type Registration for
74 'application/im-iscomposing+xml' . . . . . . . . . . . . <a href="#page-10">10</a>
75 8.2. URN Sub-Namespace Registration for
76 'urn:ietf:params:xml:ns:im-iscomposing' . . . . . . . . <a href="#page-11">11</a>
77 <a href="#section-8.3">8.3</a>. Schema Registration . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
78 <a href="#section-9">9</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
79 <a href="#section-10">10</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
80 <a href="#section-10.1">10.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
81 <a href="#section-10.2">10.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
82 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
83 Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
84
85 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
86
87 By definition, instant messaging (IM) is message based: A user
88 composes a message by, for example, typing, speaking, or recording a
89 video clip. This message is then sent to one or more recipients.
90 Unlike email, instant messaging is often conversational, so the other
91 party is waiting for a response. If no response is forthcoming, a
92 participant in an instant messaging conversation may erroneously
93 assume either that the communication partner has left or that it is
94 her turn to type again, leading to two messages "crossing on the
95 wire".
96
97 To avoid this uncertainty, a number of commercial instant messaging
98 systems feature an "is-typing" indication sent as soon as one party
99 starts typing a message. In this document, we describe a generalized
100 version of this indication, called the isComposing status message.
101 As described in <a href="#section-3">Section 3</a> in more detail, a status message is
102 delivered to the instant message recipient in the same manner as are
103 the messages themselves. The isComposing status messages can
104 announce the composition of any media type, not just text. For
105
106
107
108 <span class="grey">Schulzrinne Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc3994">RFC 3994</a> isComposing January 2005</span>
111
112
113 example, it might be used if somebody is recording an audio or video
114 clip. In addition, it can be extended to convey other instant
115 messaging user states in the future. Below, we will call these
116 messages "status messages" for brevity.
117
118 The status messages are carried as XML, as instances of the XML
119 schema defined in <a href="#section-6">Section 6</a>, and labeled as an
120 application/im-iscomposing+xml content type.
121
122 These status messages can be considered somewhat analogous to the
123 comfort noise packets that are transmitted in silence-suppressed
124 interactive voice conversations.
125
126 Events and extensions to presence, such as PIDF [<a href="#ref-6" title="&quot;Presence Information Data Format (PIDF)&quot;">6</a>], were also
127 considered but have a number of disadvantages. They add more
128 overhead, as an explicit and periodic subscription is required.
129 For page-mode delivery, subscribing to the right user agent and
130 set of messages may not be easy. An in-band, message-based
131 mechanism is also easier to translate across heterogeneous instant
132 messaging systems.
133
134 The mechanism described here aims to satisfy the requirements in [<a href="#ref-7" title="&quot;Advanced Instant Messaging Requirements for the Session Initiation Protocol (SIP)&quot;">7</a>].
135
136 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology and Conventions</span>
137
138 This memo makes use of the vocabulary defined in the IMPP Model
139 document [<a href="#ref-1" title="&quot;A Model for Presence and Instant Messaging&quot;">1</a>]. In this memo, terms such as CLOSED, INSTANT MESSAGE,
140 OPEN, PRESENCE SERVICE, PRESENTITY, WATCHER, and WATCHER USER AGENT
141 are used with the same meaning defined therein. The key words MUST,
142 MUST NOT, REQUIRED, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and
143 OPTIONAL in this document are to be interpreted as described in <a href="https://www.rfc-editor.org/bcp/bcp14">BCP</a>
144 <a href="https://www.rfc-editor.org/bcp/bcp14">14</a>, <a href="./rfc2119">RFC 2119</a> [<a href="#ref-2" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">2</a>].
145
146 This document discusses two kinds of messages; namely, the instant
147 message (IM) conveying actual content between two or more users
148 engaged in an instant messaging conversation, and the status message,
149 described in this document, which indicates the current composing
150 status to the other participants in a conversation. We use the terms
151 "content message" and "status message" for these two message types.
152
153 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Description</span>
154
155 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Overview</span>
156
157 We model the user of an instant messaging system as being in one of
158 several states, in this document limited to "idle" and "active". By
159 default, the user is in "idle" state, both before starting to compose
160 a message and after sending it.
161
162
163
164 <span class="grey">Schulzrinne Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc3994">RFC 3994</a> isComposing January 2005</span>
167
168
169 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Message Composer Behavior</span>
170
171 Only the instant messaging user agent actively composing a content
172 message generates status messages indicating the current state. When
173 the user starts composing a content message (the actual instant
174 message), the state becomes "active", and an isComposing status
175 message containing a &lt;state&gt; element indicating "active" is sent to
176 the recipient of the content message being composed. As long as the
177 user continues to produce instant message content, the user remains
178 in state "active".
179
180 There are two sender timers: the active-state refresh interval, and
181 the idle time-out interval.
182
183 The active-state refresh interval determines how often "active" state
184 messages are sent while the composer remains in "active" state. The
185 interval is chosen by the composing user and indicated in the
186 &lt;refresh&gt; element in the status message, expressed in integer
187 seconds. Each transmission of the isComposing message resets the
188 timer. The interval SHOULD be no shorter than 60 seconds. A message
189 composer MAY decide not to send active-state refresh messages at all.
190 This is indicated by omitting the refresh interval; this will cause
191 the receiver to assume that it has gone idle after 120 seconds. (In
192 most cases, the content message will have been sent by then.) No
193 refresh messages are sent in "idle" state.
194
195 The active-state refresh mechanism deals with the case in which
196 the user logs off or the application crashes before the content
197 message is completed.
198
199 If the user stops composing for more than a configured time interval,
200 the idle timeout, the state transitions to "idle", and an "idle"
201 status message is sent. If the user starts composing again while in
202 "idle" state, the state transitions to "active", and the
203 corresponding status message is sent. Unless otherwise configured by
204 the user, the idle timeout SHOULD have a default value of 15 seconds.
205
206 If a content message is sent before the idle threshold expires, no
207 "idle" state indication is needed. Thus, in most cases, only one
208 status message is generated for each content message. In any event,
209 the message rate is limited to one status message per refresh
210 threshold interval.
211
212
213
214
215
216
217
218
219
220 <span class="grey">Schulzrinne Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc3994">RFC 3994</a> isComposing January 2005</span>
223
224
225 The state transitions are shown in Figure 1.
226
227 +-------------+
228 |+-----------+|
229 || ||
230 +------&gt;| idle |&lt;--------+
231 | || || |
232 | |+-----------+| |
233 | +------+------+ |
234 content | | | idle timeout
235 msg. sent | | composing | w/o activity
236 ----------- | | ------------- | ------------------
237 -- | | "active" msg. | "idle" status msg.
238 | | |
239 | +------V------+ |
240 | | | |
241 | | | |
242 | | | |
243 +------+ active +--------+
244 | |
245 | |------+
246 +------^------+ | refresh timeout
247 | | --------------------
248 | | "active" status msg.
249 +-------------+
250
251 Figure 1. Sender State Diagram
252
253 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Status Message Receiver Behavior</span>
254
255 The status message receiver uses the status messages to determine the
256 state of the content message sender. If the most recent "active"
257 status message contained a &lt;refresh&gt; value, the refresh time-out is
258 set to that value; otherwise, it is 120 seconds. The state at the
259 receiver transitions from "active" to "idle" under three conditions:
260
261 1. A status message with status "idle" is received.
262 2. A content message is received.
263 3. The refresh interval expires.
264
265 Receivers MUST be able to handle multiple consecutive isComposing
266 messages with "active" state, regardless of the refresh interval.
267
268
269
270
271
272
273
274
275
276 <span class="grey">Schulzrinne Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc3994">RFC 3994</a> isComposing January 2005</span>
279
280
281 The state transitions are shown in Figure 2.
282
283 +-------------+
284 |+-----------+|
285 || ||
286 +------&gt;| idle |&lt;------+
287 | || || |
288 | |+-----------+| |
289 | +------+------+ |
290 | | |
291 "idle" recd. | |"active" msg.| refresh timeout
292 or content recd. | | | or 120s
293 | | |
294 | +------V------+ |
295 | | | |
296 | | | |
297 | | | |
298 +------+ active +------+
299 | |
300 | |
301 +-------------+
302
303 Figure 2. Receiver State Diagram
304
305 <span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Message Content</span>
306
307 We briefly describe the message content to summarize the discussion
308 above. This description is non-normative. The schema (<a href="#section-6">Section 6</a>)
309 should be consulted for the normative message format.
310
311 The message consists of an &lt;isComposing&gt; element, with a mandatory
312 &lt;state&gt; element indicating the composer state; i.e., idle or active.
313 In addition, there are three optional elements: &lt;lastactive&gt;,
314 indicating the time of last activity; &lt;contenttype&gt;, the type of
315 message being created; and &lt;refresh&gt;, the time interval after which
316 the receiver can expect an update from the composer. Details are
317 given in the following section.
318
319 <span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. Additional Status Information</span>
320
321 The status message contains additional optional elements to provide
322 further details on the composition activity. Any of these can appear
323 in both "active" and "idle" state messages.
324
325
326
327
328
329
330
331
332 <span class="grey">Schulzrinne Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc3994">RFC 3994</a> isComposing January 2005</span>
335
336
337 The optional &lt;lastactive&gt; element describes the absolute time when
338 the user last added or edited content.
339
340 The optional &lt;contenttype&gt; element indicates the type of medium in
341 which the messaging terminal is currently composing. It can contain
342 either just a MIME media type, such as "audio" or "text", or a media
343 type and subtype, such as "text/html". It is best understood as a
344 hint to the user, not a guarantee, that the actual content message
345 will indeed contain only the content indicated. It allows the human
346 recipient to be prepared for the likely message format.
347
348 To further describe message composition, the XML schema or the set of
349 allowable state names can be extended in future documents.
350 Recipients of status messages implementing this specification without
351 extensions MUST treat state tokens other than "idle" and "active" as
352 "idle". Additional elements MUST use their own namespaces and MUST
353 be designed so that receivers can safely ignore such extensions.
354 Adding elements to the namespace defined in this document is not
355 permitted.
356
357 The isComposing status message MAY be carried in CPIM messages [<a href="#ref-3" title="&quot;Common Presence and Instant Messaging (CPIM): Message Format&quot;">3</a>].
358
359 Such a wrapper is particularly useful if messages are relayed by a
360 conference server since the CPIM message maintains the identity of
361 the original composer.
362
363 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Using the Status Message</span>
364
365 The isComposing status message can be used with either page mode or
366 session mode, although session mode is a more natural fit. In
367 session mode, the status message is sent as part of the messaging
368 stream. Its usage is negotiated just like any other media type in
369 that stream, with details depending on the session mode protocol.
370
371 Sending the status messages within the session-mode messaging stream
372 has at least three benefits. First, it ensures proper ordering and
373 synchronization with the actual content messages being composed. In
374 messaging systems that guarantee in-order delivery of messages, this
375 approach avoids having an active indication appear at the receiver
376 after the actual message has been delivered, due to message
377 reordering across two delivery mechanisms.
378
379 Secondly, end-to-end security can be applied to the messages.
380 Thirdly, session negotiation mechanisms can be used to turn it on and
381 off at any time, and even to negotiate its use in a single direction
382 at a time.
383
384
385
386
387
388 <span class="grey">Schulzrinne Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc3994">RFC 3994</a> isComposing January 2005</span>
391
392
393 Usage with page mode is also straightforward: The status message is
394 carried as the body of a page mode message. In SIP-based IM, The
395 composer MUST cease transmitting status messages if the receiver
396 returned a 415 status code (Unsupported Media Type) in response to a
397 MESSAGE request containing the status indication.
398
399 The sender cannot be assured that the status message is delivered
400 before the actual content being composed arrives. However, SIP page
401 mode is limited to one unacknowledged message, so out-of-order
402 delivery is unlikely, albeit still possible if proxies are involved.
403
404 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Examples</span>
405
406 &lt;?xml version="1.0" encoding="UTF-8"?&gt;
407 &lt;isComposing xmlns="urn:ietf:params:xml:ns:im-iscomposing"
408 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
409 xsi:schemaLocation="urn:ietf:params:xml:ns:im-composing
410 iscomposing.xsd"&gt;
411 &lt;state&gt;active&lt;/state&gt;
412 &lt;contenttype&gt;text/plain&lt;/contenttype&gt;
413 &lt;refresh&gt;90&lt;/refresh&gt;
414 &lt;/isComposing&gt;
415
416 &lt;?xml version="1.0" encoding="UTF-8"?&gt;
417 &lt;isComposing xmlns="urn:ietf:params:xml:ns:im-iscomposing"
418 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
419 xsi:schemaLocation="urn:ietf:params:xml:ns:im-composing
420 iscomposing.xsd"&gt;
421 &lt;state&gt;idle&lt;/state&gt;
422 &lt;lastactive&gt;2003-01-27T10:43:00Z&lt;/lastactive&gt;
423 &lt;contenttype&gt;audio&lt;/contenttype&gt;
424 &lt;/isComposing&gt;
425
426 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. XML Document Format</span>
427
428 An isComposing document is an XML document that MUST be well formed
429 and SHOULD be valid. isComposing documents MUST be based on XML 1.0
430 and MUST be encoded by using UTF-8. This specification makes use of
431 XML namespaces for identifying isComposing documents. The namespace
432 URI for elements defined for this purpose is a URN using the
433 namespace identifier 'ietf'. This URN is:
434
435 urn:ietf:params:xml:ns:im-iscomposing
436
437
438
439
440
441
442
443
444 <span class="grey">Schulzrinne Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc3994">RFC 3994</a> isComposing January 2005</span>
447
448
449 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. XML Schema</span>
450
451 &lt;?xml version="1.0" encoding="UTF-8"?&gt;
452 &lt;xs:schema targetNamespace="urn:ietf:params:xml:ns:im-iscomposing"
453 elementFormDefault="qualified"
454 attributeFormDefault="unqualified"
455 xmlns:xs="http://www.w3.org/2001/XMLSchema"
456 xmlns:tns="urn:ietf:params:xml:ns:im-iscomposing"&gt;
457 &lt;xs:element name="isComposing"&gt;
458 &lt;xs:complexType&gt;
459 &lt;xs:sequence&gt;
460 &lt;xs:element name="state" type="xs:string"/&gt;
461 &lt;xs:element name="lastactive" type="xs:dateTime"
462 minOccurs="0"/&gt;
463 &lt;xs:element name="contenttype" type="xs:string"
464 minOccurs="0"/&gt;
465 &lt;xs:element name="refresh" type="xs:positiveInteger"
466 minOccurs="0"/&gt;
467 &lt;xs:any namespace="##other" processContents="lax"
468 minOccurs="0" maxOccurs="unbounded"/&gt;
469 &lt;/xs:sequence&gt;
470 &lt;/xs:complexType&gt;
471 &lt;/xs:element&gt;
472 &lt;/xs:schema&gt;
473
474 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
475
476 The isComposing indication provides a fine-grained view of the
477 activity of the entity composing and thus deserves particularly
478 careful confidentiality protection so that only the intended
479 recipient of the message will receive the isComposing indication.
480
481 Since the status messages are carried by using the IM protocol
482 itself, all security considerations of the underlying IM protocol
483 also apply to the isComposing status messages.
484
485 There are potential privacy issues in sending isComposing status
486 messages before an actual conversation has been established between
487 the communicating users. A status message may be sent even if the
488 user later abandons the message. It is RECOMMENDED that isComposing
489 indications in page mode are only sent when a message is being
490 composed as a reply to an earlier message. This document does not
491 prescribe how an implementation detects whether a message is in
492 response to an earlier one in page mode, but elapsed time or user
493 interface behavior might be used as hints.
494
495
496
497
498
499
500 <span class="grey">Schulzrinne Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc3994">RFC 3994</a> isComposing January 2005</span>
503
504
505 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. IANA Considerations</span>
506
507 <span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Content-Type Registration for 'application/im-iscomposing+xml'</span>
508
509 To: [email protected]
510 Subject: Registration of MIME media type application/
511 im-iscomposing+xml
512 MIME media type name: application
513 MIME subtype name: im-iscomposing+xml
514 Required parameters: (none)
515 Optional parameters: charset; Indicates the character encoding of
516 enclosed XML. Default is UTF-8.
517 Encoding considerations: Uses XML, which can employ 8-bit characters,
518 depending on the character encoding used. See <a href="./rfc3023">RFC 3023</a> [<a href="#ref-4" title="&quot;XML Media Types&quot;">4</a>],
519 section 3.2.
520 Security considerations: This content type is designed to carry
521 information about current user activity, which may be considered
522 private information. Appropriate precautions should be adopted to
523 limit disclosure of this information.
524 Interoperability considerations: This content type provides a common
525 format for exchange of composition activity information.
526 Published specification: <a href="./rfc3994">RFC 3994</a>
527 Applications which use this media type: Instant messaging systems.
528 Additional information: none
529 Person &amp; email address to contact for further information: Henning
530 Schulzrinne, [email protected]
531 Intended usage: LIMITED USE
532 Author/Change controller: This specification is a work item of the
533 IETF SIMPLE working group, with the mailing list address
534 [email protected].
535 Other information: This media type is a specialization of
536 application/xml <a href="./rfc3023">RFC 3023</a> [<a href="#ref-4" title="&quot;XML Media Types&quot;">4</a>], and many of the considerations
537 described there also apply to application/im-iscomposing+xml.
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556 <span class="grey">Schulzrinne Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc3994">RFC 3994</a> isComposing January 2005</span>
559
560
561 <span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. URN Sub-Namespace Registration for</span>
562 'urn:ietf:params:xml:ns:im-iscomposing'
563
564 URI: urn:ietf:params:xml:ns:im-iscomposing
565 Description: This is the XML namespace for XML elements defined by
566 <a href="./rfc3994">RFC 3994</a> to describe composition activity by an instant messaging
567 client using the application/im-iscomposing+xml content type.
568 Registrant Contact: IETF, SIMPLE working group, [email protected],
569 Henning Schulzrinne, [email protected]
570 XML:
571
572 BEGIN
573 &lt;?xml version="1.0"?&gt;
574 &lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
575 "<a href="http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd</a>"&gt;
576 &lt;html xmlns="http://www.w3.org/1999/xhtml"&gt;
577 &lt;head&gt;
578 &lt;meta http-equiv="content-type"
579 content="text/html;charset=iso-8859-1"/&gt;
580 &lt;title&gt;Is-composing Indication for Instant Messaging&lt;/title&gt;
581 &lt;/head&gt;
582 &lt;body&gt;
583 &lt;h1&gt;Namespace for SIMPLE iscomposing extension&lt;/h1&gt;
584 &lt;h2&gt;urn:ietf:params:xml:ns:im-composing&lt;/h2&gt;
585 &lt;p&gt;See &lt;a href="[URL of published RFC]"&gt;<a href="./rfc3994">RFC3994</a>&lt;/a&gt;.&lt;/p&gt;
586 &lt;/body&gt;
587 &lt;/html&gt;
588 END
589
590 <span class="h3"><a class="selflink" id="section-8.3" href="#section-8.3">8.3</a>. Schema Registration</span>
591
592 This section registers a new XML schema per the procedures in [<a href="#ref-5" title="&quot;The IETF XML Registry&quot;">5</a>].
593
594 URI: urn:ietf:params:xml:schema:im-composing
595 Registrant Contact: IETF, SIMPLE working group, ([email protected]),
596 Henning Schulzrinne ([email protected]).
597
598 The XML for this schema can be found as the sole content of <a href="#section-6.1">Section</a>
599 <a href="#section-6.1">6.1</a>.
600
601 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Acknowledgements</span>
602
603 Ben Campbell, Miguel Garcia, Scott Hollenbeck, Christian Jansson,
604 Cullen Jennings, Hisham Khartabil, Allison Mankin, Aki Niemi,
605 Jonathan Rosenberg, and Xiaotao Wu provided helpful comments.
606
607
608
609
610
611
612 <span class="grey">Schulzrinne Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc3994">RFC 3994</a> isComposing January 2005</span>
615
616
617 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. References</span>
618
619 <span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Normative References</span>
620
621 [<a id="ref-1">1</a>] Day, M., Rosenberg, J., and H. Sugano, "A Model for Presence and
622 Instant Messaging", <a href="./rfc2778">RFC 2778</a>, February 2000.
623
624 [<a id="ref-2">2</a>] Bradner, S., "Key words for use in RFCs to Indicate Requirement
625 Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
626
627 [<a id="ref-3">3</a>] Klyne, G. and D. Atkins, "Common Presence and Instant Messaging
628 (CPIM): Message Format", <a href="./rfc3862">RFC 3862</a>, August 2004.
629
630 [<a id="ref-4">4</a>] Murata, M., St. Laurent, S., and D. Kohn, "XML Media Types", <a href="./rfc3023">RFC</a>
631 <a href="./rfc3023">3023</a>, January 2001.
632
633 [<a id="ref-5">5</a>] Mealling, M., "The IETF XML Registry", <a href="https://www.rfc-editor.org/bcp/bcp81">BCP 81</a>, <a href="./rfc3688">RFC 3688</a>, January
634 2004.
635
636 <span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. Informative References</span>
637
638 [<a id="ref-6">6</a>] Sugano, H., Fujimoto, S., Klyne, G., Bateman, A., Carr, W., and
639 J. Peterson, "Presence Information Data Format (PIDF)", <a href="./rfc3863">RFC</a>
640 <a href="./rfc3863">3863</a>, August 2004.
641
642 [<a id="ref-7">7</a>] Rosenberg, J., "Advanced Instant Messaging Requirements for the
643 Session Initiation Protocol (SIP)", Work in Progress, February
644 2004.
645
646 Author's Address
647
648 Henning Schulzrinne
649 Columbia University
650 Department of Computer Science
651 450 Computer Science Building
652 New York, NY 10027
653 US
654
655 Phone: +1 212 939 7004
656 EMail: [email protected]
657 URI: <a href="http://www.cs.columbia.edu/~hgs">http://www.cs.columbia.edu/~hgs</a>
658
659
660
661
662
663
664
665
666
667
668 <span class="grey">Schulzrinne Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc3994">RFC 3994</a> isComposing January 2005</span>
671
672
673 Full Copyright Statement
674
675 Copyright (C) The Internet Society (2005).
676
677 This document is subject to the rights, licenses and restrictions
678 contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
679 retain all their rights.
680
681 This document and the information contained herein are provided on an
682 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
683 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
684 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
685 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
686 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
687 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
688
689 Intellectual Property
690
691 The IETF takes no position regarding the validity or scope of any
692 Intellectual Property Rights or other rights that might be claimed to
693 pertain to the implementation or use of the technology described in
694 this document or the extent to which any license under such rights
695 might or might not be available; nor does it represent that it has
696 made any independent effort to identify any such rights. Information
697 on the IETF's procedures with respect to rights in IETF Documents can
698 be found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
699
700 Copies of IPR disclosures made to the IETF Secretariat and any
701 assurances of licenses to be made available, or the result of an
702 attempt made to obtain a general license or permission for the use of
703 such proprietary rights by implementers or users of this
704 specification can be obtained from the IETF on-line IPR repository at
705 <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
706
707 The IETF invites any interested party to bring to its attention any
708 copyrights, patents or patent applications, or other proprietary
709 rights that may cover technology that may be required to implement
710 this standard. Please address the information to the IETF at ietf-
711 [email protected].
712
713 Acknowledgement
714
715 Funding for the RFC Editor function is currently provided by the
716 Internet Society.
717
718
719
720
721
722
723
724 Schulzrinne Standards Track [Page 13]
725 </pre>