Re: [dispatch] Announcing a MUC with RFC4575
Mary Barnes <mary.ietf.barnes@gmail.com> Tue, 23 April 2013 15:36 UTC
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA4A721F969D for <dispatch@ietfa.amsl.com>; Tue, 23 Apr 2013 08:36:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level:
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zAWTC+I7qhBF for <dispatch@ietfa.amsl.com>; Tue, 23 Apr 2013 08:36:09 -0700 (PDT)
Received: from mail-qe0-f51.google.com (mail-qe0-f51.google.com [209.85.128.51]) by ietfa.amsl.com (Postfix) with ESMTP id 16D9421F969C for <dispatch@ietf.org>; Tue, 23 Apr 2013 08:36:09 -0700 (PDT)
Received: by mail-qe0-f51.google.com with SMTP id 1so472295qec.38 for <dispatch@ietf.org>; Tue, 23 Apr 2013 08:36:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=yiGkhx4OzFcVkzS1rS1r++VL61OGpsapxO5RFQ18MxA=; b=ftCsatz3XYJr7RddPiIUQd2zz4S4Lx7NBeR116CZuIn4rLk7W3XyxLiqoXrLF/QyZA PgXD6AksdaiHF+WPAFfptEjkWGrjo4QV1DBvn02xALrQyt6Ni0aXO8lkf0lA+B8PaeJW pcBERja4mSaku3jlTOiTvG34DiDGAptqs9QZBi4frDO1Xn7FIRVQNnDCdZwxABfwbVXM kJsKXJEIXOUJU87Mx0CWaozbrOrb7IFNzkVjeXNmyL+l+wGBIT/rGicZ/TPjoLma8Ufb /I/875dOQj622u5CgYD0icy8qzWSQBVmu/VJjaZLfboQ0OipD6QgDsG6FygStUoDZhin mqHw==
MIME-Version: 1.0
X-Received: by 10.224.190.6 with SMTP id dg6mr26396594qab.85.1366731368624; Tue, 23 Apr 2013 08:36:08 -0700 (PDT)
Received: by 10.49.117.163 with HTTP; Tue, 23 Apr 2013 08:36:08 -0700 (PDT)
In-Reply-To: <5176A9B9.3050105@jitsi.org>
References: <51744F5B.8010506@jitsi.org> <5175A133.5040309@stpeter.im> <5175A9C6.9010707@alum.mit.edu> <8393F7ED-51FD-4CE1-B8A3-FD95EA185016@vidyo.com> <CAHBDyN7r8kuOyfUmzCeYa3dYM7ZqtdvfTvkF4QSkiDTSTfN02w@mail.gmail.com> <5176A9B9.3050105@jitsi.org>
Date: Tue, 23 Apr 2013 10:36:08 -0500
Message-ID: <CAHBDyN65C8oxdY3_hX46biFtENYF3dwhyqc_66mG6Wvo0RYQtw@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Emil Ivov <emcho@jitsi.org>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: Jonathan Lennox <jonathan@vidyo.com>, "dispatch@ietf.org" <dispatch@ietf.org>
Subject: Re: [dispatch] Announcing a MUC with RFC4575
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2013 15:36:10 -0000
On Tue, Apr 23, 2013 at 10:33 AM, Emil Ivov <emcho@jitsi.org> wrote: > Hey Mary, > > On 23.04.13, 16:50, Mary Barnes wrote: >> This would also be something useful for the XCON chat, which is >> defined in draft-boulton-xcon-session-chat (we will shortly be >> updating this and posting for discussion on this mailing list). I >> think "grouptextchat" would work, although I don't find it >> particularly readable, but I don't think abbreviating is useful, so I >> don't have another suggestion. > > I suppose I am once again missing something so I'd better ask :) > > Are you saying that you would find a draft that defines the value > helpful for draft-boulton-xcon-session-chat or are you planning on > adding the definition in the draft itself? > > The former could be quicker I suppose and I'd be happy to write the > document, but the latter also works for me. [MB] I agree with you. I think we can write a simple doc to define this and it can be referenced by these other docs as necessary (since it isn't unique to any of these chat applications). [/MB] > > Cheers, > Emil > >> >> Mary. >> >> On Tue, Apr 23, 2013 at 9:41 AM, Jonathan Lennox <jonathan@vidyo.com> wrote: >>> >>> On Apr 22, 2013, at 5:21 PM, Paul Kyzivat wrote: >>> >>>> On 4/22/13 4:44 PM, Peter Saint-Andre wrote: >>>>> >>>>> Somehow "impp-participation" doesn't sound right to me. What you're >>>>> talking about is a multiparty text conference that is associated with or >>>>> auxiliary to the main conference. It seems to me that the text >>>>> conference could be an XMPP MUC room, an IRC channel, an MSRP multiparty >>>>> chat session, etc. So I would suggest something like "groupchat" (since >>>>> the primary purpose here is multiparty text chat, not one-to-one IM and >>>>> presence as they are traditionally understood). >>>> >>>> Yes, any of these could be possible, though probably if it was MSRP it >>>> wouldn't be a separate URI from the main conference URL. >>>> >>>> So the mechanism should be work for any of those. >>>> <purpose>groupchat</purpose> together with the URI scheme to distinguish >>>> among them should work. (As long as we believe everyone knows that >>>> "chat" means "type" rather than "talk informally".) >>> >>> Maybe something with "text" in the name would be clearer -- "grouptextchat"? >>> >>> (Also, I think the bike shed should be orange.) >>> >>> -- >>> Jonathan Lennox >>> jonathan@vidyo.com >>> >>> >>> _______________________________________________ >>> dispatch mailing list >>> dispatch@ietf.org >>> https://www.ietf.org/mailman/listinfo/dispatch >> _______________________________________________ >> dispatch mailing list >> dispatch@ietf.org >> https://www.ietf.org/mailman/listinfo/dispatch >> > > -- > https://jitsi.org
- [dispatch] Announcing a MUC with RFC4575 Emil Ivov
- Re: [dispatch] Announcing a MUC with RFC4575 Saúl Ibarra Corretgé
- Re: [dispatch] Announcing a MUC with RFC4575 Shekh-Yusef, Rifaat (Rifaat)
- Re: [dispatch] Announcing a MUC with RFC4575 Emil Ivov
- Re: [dispatch] Announcing a MUC with RFC4575 Shekh-Yusef, Rifaat (Rifaat)
- Re: [dispatch] Announcing a MUC with RFC4575 Peter Saint-Andre
- Re: [dispatch] Announcing a MUC with RFC4575 Peter Saint-Andre
- Re: [dispatch] Announcing a MUC with RFC4575 Emil Ivov
- Re: [dispatch] Announcing a MUC with RFC4575 Peter Saint-Andre
- Re: [dispatch] Announcing a MUC with RFC4575 Emil Ivov
- Re: [dispatch] Announcing a MUC with RFC4575 Paul Kyzivat
- Re: [dispatch] Announcing a MUC with RFC4575 Jonathan Lennox
- Re: [dispatch] Announcing a MUC with RFC4575 Mary Barnes
- Re: [dispatch] Announcing a MUC with RFC4575 Emil Ivov
- Re: [dispatch] Announcing a MUC with RFC4575 Mary Barnes
- Re: [dispatch] Announcing a MUC with RFC4575 Peter Saint-Andre
- Re: [dispatch] Announcing a MUC with RFC4575 Emil Ivov
- Re: [dispatch] Announcing a MUC with RFC4575 Saúl Ibarra Corretgé
- Re: [dispatch] Announcing a MUC with RFC4575 Salvatore Loreto
- Re: [dispatch] Announcing a MUC with RFC4575 Cullen Jennings (fluffy)
- Re: [dispatch] Announcing a MUC with RFC4575 Mary Barnes
- Re: [dispatch] Announcing a MUC with RFC4575 Richard Barnes
- Re: [dispatch] Announcing a MUC with RFC4575 Peter Saint-Andre
- Re: [dispatch] Announcing a MUC with RFC4575 Emil Ivov
- Re: [dispatch] Announcing a MUC with RFC4575 Peter Saint-Andre