> -----Original Message----- > From: Dean Willis [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 03, 2008 7:15 PM > > How exactly does INFO work in conjunction with other extensions (e2m, > AIB, SAML) that add bodies?
I don't know - it's like asking me how I know my chimney is big enough for Santa Claus. The odds are not high I'll ever find out; but I'm not rebuilding the chimney to fit him - he has to fit in the chimney, because it's already built, and it's the same size as everyone else's chimney. > How do you KNOW it works with deployed phones? I haven't seen any > implementations with those extensions applied to deployed phones, yet. Right but there's the rub - the phones are DEPLOYED. It's not them that need a'changin', nor *could* they be changed. It's AIB/e2m/saml/foobar that need to be changed. > if we can see that INFO packages (and other SIP requests, perhaps) are > going to have problems with other extensions that add bodies, then we > have to fix it. No, actually we don't. We have to change the extensions to not have a problem with INFO - or any other SIP message type, for that matter. Otherwise, what you're really saying is that every single message type in SIP needs to be changed - requests and responses - because this is NOT specific to INFO. Good luck with that. I'm sure people will love to change their implementations and upgrade all systems just in case unicorns show up someday. -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
