Hi, Please take a look at the "read this first" mail I sent. At least I am ok with one package per INFO, assuming we remove all the CID stuff from the draft, and that a single package can have multiple body-parts.
Regards, Christer -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hadriel Kaplan Sent: Sunday, December 07, 2008 6:45 PM To: Mary Barnes; Eric Burger Cc: SIP List Subject: Re: [Sip] INFO Framework - one pakage per INFO > -----Original Message----- > From: Mary Barnes [mailto:[EMAIL PROTECTED] > Sent: Sunday, December 07, 2008 11:34 AM > > ... That all said, if there is some correlation/coupling of the two > packages by the application, then perhaps you should define a single > new package that combines the information - it seems then that the > implementation would be significantly simpler. Right, that's what we said when people asked how to do two things that really have co-dependence and cannot be separated because they're not atomic actions. Just define a package that has both of those things in it. A "molecule" so to speak. :) There's no reason a single package can't have multiple body-parts, for example. Just like SUB/NOT/PUB packages can. -hadriel _______________________________________________ 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
