[Sipping] Re: [Simple] MESSAGE Exploders draft

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

_______________________________________________
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