A Group Text Chat Purpose for Conference and Service URIs in the SIP Event Package for Conference State
RFC 7106

 
Document Type RFC - Informational (January 2014; No errata)
Was draft-ivov-grouptextchat-purpose (individual in rai area)
Last updated 2014-01-21
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd Saul Corretge
Shepherd write-up Show (last changed 2013-06-24)
IESG IESG state RFC 7106 (Informational)
Telechat date
Responsible AD Gonzalo Camarillo
Send notices to emcho@jitsi.org, draft-ivov-grouptextchat-purpose@ietf.org, saul@ag-projects.com
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack

Email authors IPR References Referenced by Nits Search lists

Internet Engineering Task Force (IETF)                           E. Ivov
Request for Comments: 7106                                         Jitsi
Category: Informational                                     January 2014
ISSN: 2070-1721

    A Group Text Chat Purpose for Conference and Service URIs in the
                 SIP Event Package for Conference State

Abstract

   This document defines and registers a value of "grouptextchat"
   ("Group Text Chat") for the URI <purpose> element of SIP's Conference
   Event Package.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are a candidate for any level of Internet
   Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc7106.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Ivov                          Informational                     [Page 1]
RFC 7106              Entry Purpose: GroupTextChat          January 2014

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   4.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     4.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The Conference Event Package [RFC4575] defines means for a SIP User
   Agent (UA) to obtain information about the state of the conference,
   the types of media that are being used, the number and state of
   current participants, additional sources of information (e.g., web
   page), availability of recordings, and more.

   Details describing auxiliary services available for a conference are
   included within a <service-uris> child element of the
   <conference-description> element.  Such details are presented as a
   set of <entry> child elements, each containing the URI allowing
   access the corresponding auxiliary service.  In addition to the URI,
   entries can also contain a descriptive <display-text> element and are
   expected to have a <purpose> element that specifies their nature as
   illustrated in the following example:

   <conference-description>
   <subject>Agenda: This sprint's goals</subject>
     <service-uris>
       <entry>
         <uri>http://conference.example.com/dev-group/</uri>
         <purpose>web-page</purpose>
       </entry>
     </service-uris>
   </conference-description>

   In addition to the "web-page" purpose mentioned above, [RFC4575] also
   defines several other possible values in the "URI Purposes" sub-
   registry under the existing "Session Initiation Protocol (SIP)
   Parameters" registry.

   This specification adds the "grouptextchat" value to this "URI
   Purposes" sub-registry.  The new value allows conference mixers or
   focus agents to advertise a multi-user chat location (i.e., a chat
   room) associated with the current conference.

Ivov                          Informational                     [Page 2]
RFC 7106              Entry Purpose: GroupTextChat          January 2014

   The actual URI carried by the entry with the "grouptextchat" purpose
   can be of any type as long as the content that it points to allows
   for instant text communication between participants of the
Show full document text