[Sipping] Re: [Simple] MESSAGE Exploders draft

Miguel Garcia <Miguel.An.Garcia@nokia.com> Tue, 20 April 2004 15:03 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23871 for <sipping-archive@odin.ietf.org>; Tue, 20 Apr 2004 11:03:18 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BFwke-000220-4v for sipping-archive@odin.ietf.org; Tue, 20 Apr 2004 11:01:32 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3KF1WpN007804 for sipping-archive@odin.ietf.org; Tue, 20 Apr 2004 11:01:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BFwaf-0006rq-CY for sipping-web-archive@optimus.ietf.org; Tue, 20 Apr 2004 10:51:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23016 for <sipping-web-archive@ietf.org>; Tue, 20 Apr 2004 10:51:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BFwac-0007Yo-UF for sipping-web-archive@ietf.org; Tue, 20 Apr 2004 10:51:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BFwZj-0007Ih-00 for sipping-web-archive@ietf.org; Tue, 20 Apr 2004 10:50:16 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BFwYz-00072i-00 for sipping-web-archive@ietf.org; Tue, 20 Apr 2004 10:49:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BFwPs-0003mk-Va; Tue, 20 Apr 2004 10:40:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BFwJC-0001Bb-6z for sipping@optimus.ietf.org; Tue, 20 Apr 2004 10:33:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21846 for <sipping@ietf.org>; Tue, 20 Apr 2004 10:33:06 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BFwJ9-0002UX-LC for sipping@ietf.org; Tue, 20 Apr 2004 10:33:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BFwIC-0002AA-00 for sipping@ietf.org; Tue, 20 Apr 2004 10:32:08 -0400
Received: from mgw-x2.nokia.com ([131.228.20.22]) by ietf-mx with esmtp (Exim 4.12) id 1BFwHD-0001sj-00; Tue, 20 Apr 2004 10:31:07 -0400
Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159]) by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i3KEV3O08090; Tue, 20 Apr 2004 17:31:03 +0300 (EET DST)
X-Scanned: Tue, 20 Apr 2004 17:30:56 +0300 Nokia Message Protector V1.3.21 2004031416 - RELEASE
Received: (from root@localhost) by esdks004.ntc.nokia.com (8.12.9/8.12.9) id i3KEUuQo005960; Tue, 20 Apr 2004 17:30:56 +0300
Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks004.ntc.nokia.com 00gQUF5i; Tue, 20 Apr 2004 17:30:55 EEST
Received: from esebh001.NOE.Nokia.com (esebh001.ntc.nokia.com [172.21.138.28]) by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i3KEUUs06672; Tue, 20 Apr 2004 17:30:30 +0300 (EET DST)
Received: from nokia.com ([172.21.40.155]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Tue, 20 Apr 2004 17:30:33 +0300
Message-ID: <40853408.1020804@nokia.com>
Date: Tue, 20 Apr 2004 17:30:32 +0300
From: Miguel Garcia <Miguel.An.Garcia@nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en, es-es
MIME-Version: 1.0
To: ext Ben Campbell <bcampbell@dynamicsoft.com>
CC: SIMPLE mailing list <simple@ietf.org>, SIPPING mailing list <sipping@ietf.org>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
References: <406DE1C8.3040309@dynamicsoft.com>
In-Reply-To: <406DE1C8.3040309@dynamicsoft.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Apr 2004 14:30:33.0100 (UTC) FILETIME=[09BD0CC0:01C426E4]
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Re: [Simple] MESSAGE Exploders draft
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Ben:

Thanks for your comments. Sorry for my late answer. See my inline comments

ext Ben Campbell wrote:

> 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?

I believe this question lies in the field of the URI list draft 
(draft-camarillo-sipping-uri-list-02.txt). Section 8 of that draft has a 
discussion.


> 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.)

It seems reasonable to me. I think what we wanted to say is that the 
Request-URI of the outboud message SHOULD NOT contain a list parameter. 
The body need not carry the list, but may carry it for other purposes 
(such as the one you mentioned).


> 
> 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.

No, I don't agree. In the past we got an agreement that we will create 
a message-specific exploder draft. There is a draft that says how to 
deal with INVITE, other for SUBSCRIBE, other for REFER, and this draft 
is about MESSAGE.  We don't want to go back and make the draft generic, 
to be applicable to any method. So I believe the wording is correct as 
it is now.

> 
> 
> 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.'

Good point. We will add a discussion on the subject.

Miguel.
> 
> 
> 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
> 
> 
> 
> 

-- 
Miguel A. Garcia           tel:+358-50-4804586
Nokia Research Center      Helsinki, Finland


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP