| 1 |
<pre>Internet Engineering Task Force (IETF) E. Ivov |
| 2 |
Request for Comments: 7106 Jitsi |
| 3 |
Category: Informational January 2014 |
| 4 |
ISSN: 2070-1721 |
| 5 |
|
| 6 |
|
| 7 |
<span class="h1">A Group Text Chat Purpose for Conference and Service URIs in the</span> |
| 8 |
<span class="h1">SIP Event Package for Conference State</span> |
| 9 |
|
| 10 |
Abstract |
| 11 |
|
| 12 |
This document defines and registers a value of "grouptextchat" |
| 13 |
("Group Text Chat") for the URI <purpose> element of SIP's Conference |
| 14 |
Event Package. |
| 15 |
|
| 16 |
Status of This Memo |
| 17 |
|
| 18 |
This document is not an Internet Standards Track specification; it is |
| 19 |
published for informational purposes. |
| 20 |
|
| 21 |
This document is a product of the Internet Engineering Task Force |
| 22 |
(IETF). It represents the consensus of the IETF community. It has |
| 23 |
received public review and has been approved for publication by the |
| 24 |
Internet Engineering Steering Group (IESG). Not all documents |
| 25 |
approved by the IESG are a candidate for any level of Internet |
| 26 |
Standard; see <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>. |
| 27 |
|
| 28 |
Information about the current status of this document, any errata, |
| 29 |
and how to provide feedback on it may be obtained at |
| 30 |
<a href="http://www.rfc-editor.org/info/rfc7106">http://www.rfc-editor.org/info/rfc7106</a>. |
| 31 |
|
| 32 |
Copyright Notice |
| 33 |
|
| 34 |
Copyright (c) 2014 IETF Trust and the persons identified as the |
| 35 |
document authors. All rights reserved. |
| 36 |
|
| 37 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 38 |
Provisions Relating to IETF Documents |
| 39 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 40 |
publication of this document. Please review these documents |
| 41 |
carefully, as they describe your rights and restrictions with respect |
| 42 |
to this document. Code Components extracted from this document must |
| 43 |
include Simplified BSD License text as described in Section 4.e of |
| 44 |
the Trust Legal Provisions and are provided without warranty as |
| 45 |
described in the Simplified BSD License. |
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Ivov Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc7106">RFC 7106</a> Entry Purpose: GroupTextChat January 2014</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>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a> |
| 61 |
<a href="#section-3">3</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a> |
| 62 |
<a href="#section-4">4</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a> |
| 63 |
<a href="#section-4.1">4.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a> |
| 64 |
<a href="#section-4.2">4.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-5">5</a> |
| 65 |
<a href="#appendix-A">Appendix A</a>. Acknowledgements . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a> |
| 66 |
|
| 67 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 68 |
|
| 69 |
The Conference Event Package [<a href="./rfc4575" title=""A Session Initiation Protocol (SIP) Event Package for Conference State"">RFC4575</a>] defines means for a SIP User |
| 70 |
Agent (UA) to obtain information about the state of the conference, |
| 71 |
the types of media that are being used, the number and state of |
| 72 |
current participants, additional sources of information (e.g., web |
| 73 |
page), availability of recordings, and more. |
| 74 |
|
| 75 |
Details describing auxiliary services available for a conference are |
| 76 |
included within a <service-uris> child element of the |
| 77 |
<conference-description> element. Such details are presented as a |
| 78 |
set of <entry> child elements, each containing the URI allowing |
| 79 |
access the corresponding auxiliary service. In addition to the URI, |
| 80 |
entries can also contain a descriptive <display-text> element and are |
| 81 |
expected to have a <purpose> element that specifies their nature as |
| 82 |
illustrated in the following example: |
| 83 |
|
| 84 |
<conference-description> |
| 85 |
<subject>Agenda: This sprint's goals</subject> |
| 86 |
<service-uris> |
| 87 |
<entry> |
| 88 |
<uri>http://conference.example.com/dev-group/</uri> |
| 89 |
<purpose>web-page</purpose> |
| 90 |
</entry> |
| 91 |
</service-uris> |
| 92 |
</conference-description> |
| 93 |
|
| 94 |
In addition to the "web-page" purpose mentioned above, [<a href="./rfc4575" title=""A Session Initiation Protocol (SIP) Event Package for Conference State"">RFC4575</a>] also |
| 95 |
defines several other possible values in the "URI Purposes" sub- |
| 96 |
registry under the existing "Session Initiation Protocol (SIP) |
| 97 |
Parameters" registry. |
| 98 |
|
| 99 |
This specification adds the "grouptextchat" value to this "URI |
| 100 |
Purposes" sub-registry. The new value allows conference mixers or |
| 101 |
focus agents to advertise a multi-user chat location (i.e., a chat |
| 102 |
room) associated with the current conference. |
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Ivov Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc7106">RFC 7106</a> Entry Purpose: GroupTextChat January 2014</span> |
| 111 |
|
| 112 |
|
| 113 |
The actual URI carried by the entry with the "grouptextchat" purpose |
| 114 |
can be of any type as long as the content that it points to allows |
| 115 |
for instant text communication between participants of the |
| 116 |
conference. Suitable URI schemes include sip: and sips: [<a href="./rfc3261" title=""SIP: Session Initiation Protocol"">RFC3261</a>] |
| 117 |
for SIP-signaled Message Session Relay Protocol (MSRP) conferences, |
| 118 |
xmpp: [<a href="./rfc5122" title=""Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) for the Extensible Messaging and Presence Protocol (XMPP)"">RFC5122</a>] for XMPP Multi-User Chat (MUC), irc: for Internet |
| 119 |
Relay Chat, http: or https: for web-based chat, and others. |
| 120 |
|
| 121 |
The following example shows one possible use case: |
| 122 |
|
| 123 |
<conference-description> |
| 124 |
<subject>Agenda: The goals for this development sprint.</subject> |
| 125 |
<service-uris> |
| 126 |
<entry> |
| 127 |
<uri>xmpp:[email protected]</uri> |
| 128 |
<purpose>grouptextchat</purpose> |
| 129 |
</entry> |
| 130 |
</service-uris> |
| 131 |
</conference-description> |
| 132 |
|
| 133 |
It is worth pointing out that, in addition to simply adding text |
| 134 |
messaging capabilities to an audio/video conference, group chats can |
| 135 |
also be used for defining roles, giving permissions, muting, kicking |
| 136 |
out and banning participants, etc. A conference mixer or focus agent |
| 137 |
can mimic these settings within the conference call, actually muting, |
| 138 |
kicking out, or banning participants on the call as these actions |
| 139 |
occur in the chat room. Such an approach requires no additional |
| 140 |
specification and is purely an implementation decision for the |
| 141 |
conferencing software. |
| 142 |
|
| 143 |
It is also worth mentioning that it is possible for the grouptextchat |
| 144 |
URI to match the URI of the conference. This would typically be the |
| 145 |
case in scenarios where the conference focus agent also provides a |
| 146 |
SIP-signaled MSRP chat service at the same URI. |
| 147 |
|
| 148 |
Also, in some cases, servers could potentially advertise more than a |
| 149 |
single chat room for a specific conference. When this happens, |
| 150 |
clients supporting the "grouptextchat" purpose could either present |
| 151 |
the user with a choice of joining individual chats or simply opening |
| 152 |
all of them simultaneously. Either way, there is to be no |
| 153 |
expectation about any content synchronization between chat rooms. If |
| 154 |
synchronization exists, such behavior would be entirely |
| 155 |
implementation specific. |
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Ivov Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc7106">RFC 7106</a> Entry Purpose: GroupTextChat January 2014</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Security Considerations</span> |
| 170 |
|
| 171 |
Advertising group text chats over SIP could provide malicious |
| 172 |
entities with the following attack vector: if a malicious entity is |
| 173 |
capable of intercepting and modifying conference package event |
| 174 |
notifications, it could trick participants into joining a third-party |
| 175 |
chat room where the attacker could eavesdrop on the conversation and |
| 176 |
potentially even impersonate some of the participants. |
| 177 |
|
| 178 |
Similar attacks are already possible with the "participation" |
| 179 |
<conference-uris> defined in [<a href="./rfc4575" title=""A Session Initiation Protocol (SIP) Event Package for Conference State"">RFC4575</a>], which is why it recommends "a |
| 180 |
strong means for authentication and conference information |
| 181 |
protection" as well as "comprehensive authorization rules". Clients |
| 182 |
can integrity protect and encrypt notification messages using end-to- |
| 183 |
end mechanisms such as S/MIME or hop-by-hop mechanisms such as TLS. |
| 184 |
When none of these are possible, clients need to clearly display the |
| 185 |
address of the destination chat room (before and after it has been |
| 186 |
joined) so that users can notice possible discrepancies. |
| 187 |
|
| 188 |
As an example, let's consider a situation in which an attacker tricks |
| 189 |
participants into joining a conference chat at |
| 190 |
xmpp:[email protected] rather than the chat at |
| 191 |
xmpp:[email protected], which was originally |
| 192 |
advertised for this conference. In the absence of any SIP-layer |
| 193 |
security, displaying the full URI of the target chat room to the user |
| 194 |
would be the only way of actually detecting the problem. |
| 195 |
|
| 196 |
Obviously, relying on human-performed string comparison is a rather |
| 197 |
meek form of protection. Therefore, client developers are encouraged |
| 198 |
to implement additional checks that would allow users to request via |
| 199 |
configuration that a target chat room satisfy some basic criteria, |
| 200 |
such as: |
| 201 |
|
| 202 |
o target chat rooms belong to the same domain as the conference |
| 203 |
service that is advertising them. |
| 204 |
|
| 205 |
o chat room names (user part of the chat room URI) match the name of |
| 206 |
the conference. |
| 207 |
|
| 208 |
Once again, these conditions are only satisfied if the corresponding |
| 209 |
deployment conventions have been followed and they cannot be |
| 210 |
universally required by clients. Therefore, they are suggested |
| 211 |
configuration options. |
| 212 |
|
| 213 |
An additional security consideration might be the possibility for |
| 214 |
using a large-scale conference as leverage to perform a flooding |
| 215 |
attack on a chat room. To help prevent this, clients could to |
| 216 |
require an explicit user action before joining chat rooms on behalf |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Ivov Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc7106">RFC 7106</a> Entry Purpose: GroupTextChat January 2014</span> |
| 223 |
|
| 224 |
|
| 225 |
of users. In cases where such a constraint could be considered to |
| 226 |
have a negative impact on usability and where automatic joins are |
| 227 |
seen as important, clients may still perform the joins but only when |
| 228 |
they can confirm a relationship between the room and the conference |
| 229 |
(e.g., they both belong to the same administrative domain, or domains |
| 230 |
that the client is provisioned to consider as related). |
| 231 |
|
| 232 |
Furthermore, an attack on an auxiliary chat room might be easier (or |
| 233 |
harder) than an attack on the main conference chat room depending on |
| 234 |
the security policies in effect. Once again, clients would have to |
| 235 |
make sure that users are appropriately notified about the security |
| 236 |
levels of each component of the conference and that user-specified |
| 237 |
privacy restrictions are applied to all of them. |
| 238 |
|
| 239 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. IANA Considerations</span> |
| 240 |
|
| 241 |
IANA has added the value "grouptextchat" to the "URI Purposes" sub- |
| 242 |
registry of the "Session Initiation Protocol (SIP) Parameters" |
| 243 |
registry <<a href="http://www.iana.org/assignments/sip-parameters">http://www.iana.org/assignments/sip-parameters</a>> as follows: |
| 244 |
|
| 245 |
Value: grouptextchat |
| 246 |
Description: The URI can be used to join a multi-user chat directly |
| 247 |
associated with the conference |
| 248 |
Document: [this document] |
| 249 |
|
| 250 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. References</span> |
| 251 |
|
| 252 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Normative References</span> |
| 253 |
|
| 254 |
[<a id="ref-RFC4575">RFC4575</a>] Rosenberg, J., Schulzrinne, H., and O. Levin, "A Session |
| 255 |
Initiation Protocol (SIP) Event Package for Conference |
| 256 |
State", <a href="./rfc4575">RFC 4575</a>, August 2006. |
| 257 |
|
| 258 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Informative References</span> |
| 259 |
|
| 260 |
[<a id="ref-RFC3261">RFC3261</a>] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, |
| 261 |
A., Peterson, J., Sparks, R., Handley, M., and E. |
| 262 |
Schooler, "SIP: Session Initiation Protocol", <a href="./rfc3261">RFC 3261</a>, |
| 263 |
June 2002. |
| 264 |
|
| 265 |
[<a id="ref-RFC5122">RFC5122</a>] Saint-Andre, P., "Internationalized Resource Identifiers |
| 266 |
(IRIs) and Uniform Resource Identifiers (URIs) for the |
| 267 |
Extensible Messaging and Presence Protocol (XMPP)", <a href="./rfc5122">RFC</a> |
| 268 |
<a href="./rfc5122">5122</a>, February 2008. |
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Ivov Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc7106">RFC 7106</a> Entry Purpose: GroupTextChat January 2014</span> |
| 279 |
|
| 280 |
|
| 281 |
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Acknowledgements</span> |
| 282 |
|
| 283 |
Thanks to Jonathan Lennox, Mary Barnes, Paul Kyzivat, Peter Saint- |
| 284 |
Andre, Rifaat Shekh-Yusef, and Saul Ibarra Corretge for their input. |
| 285 |
|
| 286 |
Author's Address |
| 287 |
|
| 288 |
Emil Ivov |
| 289 |
Jitsi |
| 290 |
Strasbourg 67000 |
| 291 |
France |
| 292 |
|
| 293 |
Phone: +33-177-624-330 |
| 294 |
EMail: [email protected] |
| 295 |
|
| 296 |
|
| 297 |
|
| 298 |
|
| 299 |
|
| 300 |
|
| 301 |
|
| 302 |
|
| 303 |
|
| 304 |
|
| 305 |
|
| 306 |
|
| 307 |
|
| 308 |
|
| 309 |
|
| 310 |
|
| 311 |
|
| 312 |
|
| 313 |
|
| 314 |
|
| 315 |
|
| 316 |
|
| 317 |
|
| 318 |
|
| 319 |
|
| 320 |
|
| 321 |
|
| 322 |
|
| 323 |
|
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
Ivov Informational [Page 6] |
| 333 |
</pre> |