Re: draft-ietf-sip-info-events-00: multiple packages per INFO

In reply to this whole thread, please bear in mind that we had lots of
discussion about whether it would be worthwhile defining this new INFO
mechanism, since existing applications are unlikely to change and the
best we can hope for is that new applications will exploit the new
mechanism. Therefore we want to keep the mechanism as simple as
possible. The complexities of matching body parts to header fields,
dealing with cases where only some of the packages are understood, etc.
are hardly likely to persuade people to implement the mechanism. Please
keep it simple.

John


> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On 
> Behalf Of Christer Holmberg
> Sent: 23 October 2008 08:17
> To: Dean Willis; DRAGE, Keith (Keith)
> Cc: SIP IETF; Eric Burger; Paul Kyzivat
> Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple 
> packages per INFO
> 
> 
> Hi, 
> 
> >>Why does putting two different packages in the same INFO 
> work better 
> >>than two different INFO messages each with their own 
> package usage? Is
> 
> >>there a desirable relationship that can be implemented 
> between the two
> 
> >>that we would otherwise lose?
> >
> >We have one package per NOTIFY. Let's stick with one package 
> per INFO,
> unless we want to go back to using mime-types as the only 
> distinguisher
> of packages.
> 
> I raised that issue in another e-mail.
> 
> But, never the less, I have no strong feelings on the single versus
> multiple package issue.
> 
> Regards,
> 
> Christer
> 
> 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use [email protected] for questions on current sip
> Use [email protected] for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [email protected] for questions on current sip
Use [email protected] for new developments on the application of sip