Re: [dispatch] Announcing a MUC with RFC4575
Peter Saint-Andre <stpeter@stpeter.im> Tue, 28 May 2013 21:21 UTC
Return-Path: <stpeter@stpeter.im>
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 9657E21F8D90 for <dispatch@ietfa.amsl.com>; Tue, 28 May 2013 14:21:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 Xh+qrUDHv24s for <dispatch@ietfa.amsl.com>; Tue, 28 May 2013 14:21:43 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id CB1DE21F8E3C for <dispatch@ietf.org>; Tue, 28 May 2013 14:21:37 -0700 (PDT)
Received: from ergon.local (unknown [128.107.239.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id D8C2E411C2; Tue, 28 May 2013 15:34:22 -0600 (MDT)
Message-ID: <51A51FDE.7000006@stpeter.im>
Date: Tue, 28 May 2013 15:21:34 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Emil Ivov <emcho@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> <CAHBDyN65C8oxdY3_hX46biFtENYF3dwhyqc_66mG6Wvo0RYQtw@mail.gmail.com> <5176CBA0.6000602@stpeter.im> <51773F1B.3020907@jitsi.org>
In-Reply-To: <51773F1B.3020907@jitsi.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "dispatch@ietf.org" <dispatch@ietf.org>, Jonathan Lennox <jonathan@vidyo.com>
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, 28 May 2013 21:21:49 -0000
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 4/23/13 8:10 PM, Emil Ivov wrote: > There it is then: > > http://tools.ietf.org/html/draft-ivov-grouptextchat-purpose An additional security consideration might be opening another attack vector for the conference (e.g., chatroom flooding). Furthermore, an attack on the auxiliary chatroom might be easier (or harder) than an attack on the main conference depending on the security policies in effect. Emil, regarding such mismatches you might borrow some text from draft-ivov-xmpp-cusax, but I think it would also be helpful to describe the nature of the chatroom attack vector (you might find it helpful to look at Section 13 of XEP-0045, especially 13.6.) Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRpR/eAAoJEOoGpJErxa2pE5gP/1FMP1nWnEZqeHl2ivesPxZY pRriCt94jEbKEVp86tCNBtMmCg5K6VjOIx6gFcMKXGWvg0HBRCT+bbLgNAAPlqIn 6zTbRTmbhpvClA4Y8CIUrqoExHynOoMvfDCbEo9OLRdKpiDYMESWboekgEqAAkL8 nE/ErJxfr3hvrd8gZUBAepQd3qPnbmgQUw9cg0Y+euT5mfURPk04J4rn8kFECDR2 XT6CcNSodFW7QYC7tYIAgseSsfHZV6bLlvrOrIOXE4lIxgoln9JRXJ5CnLPnvX9d 9uE/G3WxcqrlTd7U0XuvtOsQJ9nZowOL2MBDMuECEXlNjPfKqFKHfwyPX50puUB5 anfX1MVysrc7v9gKUJLuBomQXCZovJMC5Yr9SHuxLzmqkCuN/Go00uCKo8fh0oQV tofwS03MIWTtglUI0iXxgDTOc7ZvGgxYgnLt2qxskw2lQqK+6VwYfoMwzV2Q5MEW LD12OA2jnLeaYQKkyxwJJaTssLeXjLYqyUtPT0RZwxZIcjUKJlRk6YIaG9tYKSWW bN5yqsKWIr3cpudofS1fkEnC1MP4AhDZdDcYFVbSONzR0JFnCZwPEV22lmApo9VH Nb7QkJShrzH+QI/eRx/+UtEfjZrEzrXxV5oKYzTsCsbt5hb0ejXNtRJIT74mtW+K GI720Wp5gFkYanUn0Vk5 =JW6y -----END PGP SIGNATURE-----
- [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