idnits 2.17.1 draft-ivov-grouptextchat-purpose-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([RFC4575]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 1 instance of lines with non-RFC2606-compliant FQDNs in the document. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 148: '...e possible it is RECOMMENDED that clie...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (April 24, 2013) is 4013 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group E. Ivov 3 Internet-Draft Jitsi 4 Intended status: Standards Track April 24, 2013 5 Expires: October 26, 2013 7 A Group Text Chat Purpose for Conference and Service URIs in the Session 8 Initiation Protocol (SIP) Event Package for Conference State 9 draft-ivov-grouptextchat-purpose-00 11 Abstract 13 This document defines and registers a value of "grouptextchat" 14 ("Group Text Chat") value for the URI element of SIP's 15 Conference Event Package [RFC4575]. 17 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at http://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on October 26, 2013. 34 Copyright Notice 36 Copyright (c) 2013 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 52 2. Security Considerations . . . . . . . . . . . . . . . . . . . 3 53 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 54 4. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 55 4.1. Normative References . . . . . . . . . . . . . . . . . . 4 56 4.2. Informative References . . . . . . . . . . . . . . . . . 4 57 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 4 58 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 60 1. Introduction 62 The Conference Event Package [RFC4575] defines means for a SIP User 63 Agent (UA) to obtain information about the state of the conference, 64 the types of media that are being used, the number and state of 65 current participants, additional sources of information such as a web 66 page, availability of recordings and others. 68 Details describing auxiliary services available for a are included 69 within a child element of the 70 element. Such details are presented as a set of child 71 elements each containing the URI allowing access the corresponding 72 auxiliary service. In addition to the URI, entries can also contain 73 a descriptive element and are expected to also have a 74 element that specifies their nature as illustrated in the 75 following example: 77 78 Agenda: This sprint's goals 79 80 81 http://sharepoint/salesgroup/ 82 web-page 83 84 85 87 In addition to the "web-page" purpose mentioned above, [RFC4575] also 88 defines several other possible values in a "URI purposes" a sub- 89 registry "URI purposes" under the existing registry: http:// 90 www.iana.org/assignments/sip-parameters. 92 This specification adds the "grouptextchat" value in this "URI 93 purposes" sub-registry. The new value allows conference mixers or 94 focus agents to advertise a multi-user chat location (i.e. a chat 95 room) associated with the current conference. 97 The actual URI carried by the entry with the "grouptextchat" purpose 98 can be of any type as long as the content that it points to would 99 allow for instant text communication between participants of the 100 conference. Suitable URI schemes include sip: and sips: [RFC3261] 101 for SIP signalled Message Session Relay Protocol (MSRP) conferences, 102 xmpp: [RFC5122] for XMPP Multi-User Chat (MUC), irc: for Internet 103 Relay Chat, http: or https: for web-based chat, and others. 105 The following example shows one possible use case: 107 108 Agenda: This sprint's goals 109 110 111 xmpp:sprint@conference.example.com 112 grouptextchat 113 114 115 117 It is worth pointing out that, in addition to simply adding text 118 messaging capabilities to an audio/video conference, group chats can 119 also be used for defining roles, giving permissions, muting, kicking 120 and banning participants, etc. A conference mixer or focus agent, 121 can mimic these settings within the conference call, actually muting, 122 kicking, or banning participants in the call as these actions occur 123 in the chat room. Such an approach requires no additional 124 specification and is purely an implementation decision for the 125 conferencing software. 127 It is also worth mentioning that it is possible for the grouptextchat 128 URI to match the URI of the conference. This would typically be the 129 case in scenarios where the conference focus also provides a SIP 130 signalled MSRP chat service at the. 132 2. Security Considerations 134 Advertising group text chats over SIP could provide malicious 135 entities with the following attack vector: if a malicious entity is 136 capable of intercepting and modifying conference package event 137 notifications, it could trick participants in to joining a third 138 party chat room where the attacker could eavesdrop on the 139 conversation and potentially even impersonate some of the 140 participants. 142 Similar attacks are already possible with the "participation" 143 defined in [RFC4575] which is why it recommends "a 144 strong means for authentication and conference information 145 protection" as well as "comprehensive authorization rules". Clients 146 can integrity protect and encrypt notification messages using end-to- 147 end mechanisms such as S/MIME or hop-by-hop mechanisms such as TLS. 148 When none of the above are possible it is RECOMMENDED that clients 149 clearly display the address of the destination chat room (before and 150 after it has been joined). 152 3. IANA Considerations 154 The IANA is requested to add a new predefined value "grouptextchat" 155 in the "URI purposes" sub-registry of the http://www.iana.org/ 156 assignments/sip-parameters registry as follows: 158 Value: grouptextchat 159 Description: The URI can be used to join a multi-user chat directly 160 associated with the conference 161 Document: [this document] 163 4. References 165 4.1. Normative References 167 [RFC4575] Rosenberg, J., Schulzrinne, H., and O. Levin, "A Session 168 Initiation Protocol (SIP) Event Package for Conference 169 State", RFC 4575, August 2006. 171 4.2. Informative References 173 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 174 A., Peterson, J., Sparks, R., Handley, M., and E. 175 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 176 June 2002. 178 [RFC5122] Saint-Andre, P., "Internationalized Resource Identifiers 179 (IRIs) and Uniform Resource Identifiers (URIs) for the 180 Extensible Messaging and Presence Protocol (XMPP)", RFC 181 5122, February 2008. 183 Appendix A. Acknowledgements 184 Thanks to Jonathan Lennox, Mary Barnes, Paul Kyzivat, Peter Saint- 185 Andre, Rifaat Shekh-Yusef, and Saul Ibarra Corretge for their input. 187 Author's Address 189 Emil Ivov 190 Jitsi 191 Strasbourg 67000 192 France 194 Phone: +33-672-811-555 195 Email: emcho@jitsi.org