> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dean > Willis > > Because an SIP request can carry AIB or e2m (or other such extension, > like SAML assertions)) body parts, there is the possibility that an > INFO might also get such attachments. We can't stop this without > deprecating the behavior of those specifications. We must therefore be > prepared to determine which body part(s) is(are) associated with the > INFO package, and which are something else.
Right now INFO works, and no such problem exists. What does Subscribe/Notify do to cover this problem? > Can we do this based only on the MIME body type? Yes, in the cases we > know about so far. Do we have a way to assure this given the > probability of future specs Future specs can fix themselves by specifying what to do, if they support mime content types which could be that ambiguous. The base INFO spec doesn't need to fix it for all, if it's only a problem for some possible future use no one actually has. -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
