Re: [Simple] MESSAGE Exploders draft
Ben Campbell <bcampbell@dynamicsoft.com> Fri, 02 April 2004 22:25 UTC
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09155 for <simple-archive@ietf.org>; Fri, 2 Apr 2004 17:25:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B9X6L-0000kD-00 for simple-archive@ietf.org; Fri, 02 Apr 2004 17:25:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B9X26-0007f2-00 for simple-archive@ietf.org; Fri, 02 Apr 2004 17:21:03 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1B9WyE-0006bI-02; Fri, 02 Apr 2004 17:17:02 -0500
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1B9Wnq-0000Il-DT; Fri, 02 Apr 2004 17:06:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B9Wnc-0003s0-Im; Fri, 02 Apr 2004 17:06:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B9Wn5-0003W7-C6 for simple@optimus.ietf.org; Fri, 02 Apr 2004 17:05:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06010 for <simple@ietf.org>; Fri, 2 Apr 2004 17:05:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B9Wn3-0004Am-00 for simple@ietf.org; Fri, 02 Apr 2004 17:05:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B9WjT-0003Uy-00 for simple@ietf.org; Fri, 02 Apr 2004 17:01:48 -0500
Received: from [63.110.3.64] (helo=dyn-tx-arch-crash.dfw.dynamicsoft.com) by ietf-mx with esmtp (Exim 4.12) id 1B9Wfz-0002Zt-00; Fri, 02 Apr 2004 16:58:11 -0500
Received: from dynamicsoft.com (localhost.localdomain [127.0.0.1]) by dyn-tx-arch-crash.dfw.dynamicsoft.com (8.11.6/8.11.6) with ESMTP id i32LvVh07784; Fri, 2 Apr 2004 15:57:31 -0600
Message-ID: <406DE1C8.3040309@dynamicsoft.com>
From: Ben Campbell <bcampbell@dynamicsoft.com>
User-Agent: Mozilla Thunderbird 0.5 (X11/20040208)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Miguel Garcia <Miguel.An.Garcia@nokia.com>
CC: SIMPLE mailing list <simple@ietf.org>, SIPPING mailing list <sipping@ietf.org>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
Subject: Re: [Simple] MESSAGE Exploders draft
References: <406BC5A8.4080003@nokia.com>
In-Reply-To: <406BC5A8.4080003@nokia.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: simple-admin@ietf.org
Errors-To: simple-admin@ietf.org
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/mail-archive/working-groups/simple/>
Date: Fri, 02 Apr 2004 15:57:28 -0600
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
I like this approach overall. A couple of comments and questions. Apologies if these have already been discussed. Is it legal for the list parameter to point to something other than a body part? That is, can I have external lists? Saying the exploder MUST NOT include the URI list in the outbound messages seems a little severe. I can imagine applications where I want the recipients to know the list. This could be useful for "reply to all" sort of functions. But if we do allow this, we would need to give the sender a way to choose, possibly on a per-URI basis. (Sort of a "cc" vs. "bcc" thing.) Instead of saying that message exploders must always send message requests, we might consider saying the outbound request method must match the outbound method. This would allow for exploders that know how to explode more than one method. When condidering DoS issues, it might be worth suggesting behavior if the exploder finds duplicate URIs on the list. For example, I could put the same URI in a bunch of times, and have a nice DoS amplifier. Miguel Garcia wrote: > Hi: > > I have just submitted a draft that discusses a exploder of MESSAGEs. > > While it appears in the repository, you can download them from: > > http://people.nokia.net/~miguel/drafts/draft-garcia-simple-message-exploder-00.txt > > http://people.nokia.net/~miguel/drafts/draft-garcia-simple-message-exploder-00.html > > > Since this is an area covered by SIMPLE (Instant Messaging) and SIPPING > (exploders), I am copying both mailing lists. > > Regards, > > Miguel _______________________________________________ Simple mailing list Simple@ietf.org https://www1.ietf.org/mailman/listinfo/simple
- [Simple] MESSAGE Exploders draft Miguel Garcia
- Re: [Simple] MESSAGE Exploders draft Ben Campbell
- Re: [Simple] MESSAGE Exploders draft Ben Campbell
- [Simple] Re: [Sipping] MESSAGE Exploders draft Paul Kyzivat
- Re: [Simple] MESSAGE Exploders draft Miguel Garcia
- Re: [Simple] MESSAGE Exploders draft Ben Campbell
- [Simple] Re: [Sipping] MESSAGE Exploders draft Miguel Garcia
- Re: [Simple] MESSAGE Exploders draft Miguel Garcia
- [Simple] Managing multiple body parts Paul Kyzivat
- [Simple] Re: Managing multiple body parts Gonzalo Camarillo
- [Simple] Re: Managing multiple body parts Paul Kyzivat