A Group Text Chat Purpose for Conference and Service URIs in the SIP Event Package for Conference State
draft-ivov-grouptextchat-purpose-04

[Ballot comment]
I would need someone more clueful than I to pronounce on this, but don't we have better things to include in an example than:
http://sharepoint/salesgroup/

[Ballot comment]
Did the *content* of this document get any review at all in the IETF? I know that DISPATCH looked at it, but that's a "where should this be handled" review rather than a content review. I see no discussion of it on the IETF list. Is this actually an IETF consensus document? (The general subject is a current topic of conversation between the IAB and IESG, so shedding some light on this case might prove useful. It should not stop publication of this document.)

[Ballot comment]
I did have one question, which you might consider along with any other comments you receive during the evaluation process.

I'm reading (quickly) this specification plus RFC 4575 taken together as saying that a conference description with two grouptextchat purposes would be valid, so that a conference can advertise both an XMPP URI and an SIP URI with grouptextchat purpose, for instance.

If that's valid, is there any expectation that if I type something into one of these group chats, it would show up for people in another chat advertised in the same conference description?

You could also tell me that everyone uses XMPP for group chats, so this isn't an interesting question, of course :-)

[Ballot discuss]
s2: On the display the chatroom mitigation if there's no network security:

a) exactly what gets displayed: host or host:port is?  I guess I'm asking from where is the data to be displayed pulled?

b) Is there anything the client should be checking for the user because leaving it up to the user is likely not a good idea - i.e., can the client do some normal matching to see if the fields in the request to join the conference match the ones in the response that said yeah you can join?

[Ballot comment]
s2: I think here you meant to say 4575 recommends this things and so do we:

OLD:

  Similar attacks are already possible with the "participation"
  defined in [RFC4575] which is why it recommends "a
  strong means for authentication and conference information
  protection" as well as "comprehensive authorization rules".

NEW:

  Similar attacks are already possible with the "participation"
  defined in [RFC4575] which is why it and this
  document recommend "a
  strong means for authentication and conference information
  protection" as well as "comprehensive authorization rules".

[Ballot comment]
I notice the following fragment in a couple of places:

Agenda: This sprint's goals

Given that Sprint is a service provider in this sector, it would be better to pick a neutral name.

IESG/Authors/WG Chairs:

IANA has reviewed draft-ivov-grouptextchat-purpose-03.  Authors should review the comments and/or questions below.  Please report any inaccuracies and respond to any questions as soon as possible.

We received the following comments/questions from the IANA's reviewer:

We understand that, upon approval of this document, there is a single IANA action which needs to be completed.

In the URI Purposes subregistry of the Session Initiation Protocol (SIP) Parameters located at:

http://www.iana.org/assignments/sip-parameters/sip-parameters.xhtml

a single new URI Purpose will be registered as follows:

Value: grouptextchat
Description: The URI can be used to join a multi-user chat directly associated with the conference
Reference: [ RFC-to-be ]

We understand that this is the only action required to be completed
upon approval of this document.

Note:  The actions requested in this document will not be completed
until the document has been approved for publication as an RFC.
This message is only to confirm what actions will be performed.

The following Last Call announcement was sent out:

From: The IESG
To: IETF-Announce
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (A Group Text Chat Purpose for Conference and Service URIs in the Session Initiation Protocol (SIP) Event Package for Conference State) to Informational RFC


The IESG has received a request from an individual submitter to consider
the following document:
- 'A Group Text Chat Purpose for Conference and Service URIs in the
  Session Initiation Protocol (SIP) Event Package for Conference
  State'
  as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2013-07-22. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


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




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ivov-grouptextchat-purpose/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ivov-grouptextchat-purpose/ballot/


No IPR declarations have been submitted directly on this I-D.