RE: [Simple] RE: Advanced IM requirements

[Markus.Isomaki at nokia.com]

Hi,

I agree that it should be enough if we do this for SIP MESSAGE only, not for CPIM in general.

Also I think this work should borrow as much as possible from the current e-mail mechanims, so we would not need to re-invent stuff that already works there.

Markus

> -----Original Message-----
> From: simple-admin@ietf.org [mailto:simple-admin@ietf.org]On Behalf Of
> ext Aki Niemi
> Sent: 26 February, 2004 14:44
> To: ext Jonathan Rosenberg
> Cc: Chris Boulton; Garcia Miguel.An (Nokia-NRC/Helsinki);
> simple@ietf.org; Eric Burger
> Subject: Re: [Simple] RE: Advanced IM requirements
> 
> 
> 
> 
> ext Jonathan Rosenberg wrote:
> > 
> > 
> > 
> > Chris Boulton wrote:
> > 
> >> 1. it placed the URI for sending the delivery notification 
> as a CPIM
> >> header, not a SIP header
> >>
> >> <<CJB>> Out of interest, what was the driving force for 
> this design 
> >> choice?
> > 
> > 
> > I believe the document talks a bit about this. It would make the 
> > mechanism applicable to any system that uses cpim, which 
> would include 
> > IM sessions and in theory any other IMPP compliant IM 
> protocol, though 
> > since XMPP is not using it there are practically none others.
> 
> Perhaps that's a good sign that we should up a notch the place where 
> MDNs are defined. In other words perhaps we should define the 
> MDNs for 
> SIP MESSAGE instead of message/cpim.
> 
> This would enable us to request/receive delivery reports 
> without having 
> to wrap content in message/cpim.
> 
> Cheers,
> AKi
> 
> > Of course, Eric is the author of this and is better suited 
> to answer the 
> > question.
> > 
> > -Jonathan R.
> 
> _______________________________________________
> Simple mailing list
> Simple@ietf.org
> https://www1.ietf.org/mailman/listinfo/simple
> 

_______________________________________________
Simple mailing list
Simple@ietf.org
https://www1.ietf.org/mailman/listinfo/simple