Saying, "OK for interworking" does not really say anything. If I come up with a really broken method for interworking, saying that it is for interworking does not make it correct.
The problem is, how do the endpoints know they will be able to communicate? For the ISUP/Q.sig/DPNSS/mumble case, the endpoints know they will be able to interoperate because they know a'priori: they are configured to work. However, this means that the devices must be in the same administrative domain and configured properly. Said in a different manner, INFO works fine for non-inter-network use. It would be hard for the IETF to say, "Here is a non-IETF use. We will not use it. You cannot use it with anyone else. You cannot use it between manufacturers, unless you get them to agree to this use." That is a bit more of what we call the toxic waste warning that accompanies 3GPP specifications... On 8/27/07 8:35 AM, "Peili Xu" <[EMAIL PROTECTED]> wrote: > Hi Eric, > > Several cases I encounter to use INFO is for interworking with PSTN signaling, > or simulate PSTN services at SIP entities such as SIP UA or SIP GW, > which require mid-dialog information change. > > For such SIP entities, It's not always possible or required to support > encapsulation of ISUP or QSIG package. Just some XML body with > application info is enough and light-weight for this purpose. > > > INFO is not an ideal tool for everything, but is an ideal tool for some thing. > > I'd prpose to at lease allow using INFO for interworking or simulation > purpose with legacy system. > > Regards. > Peili > > 2007/8/22, Eric Burger <[EMAIL PROTECTED]>: >> Since list traffic is down, how about something to spice things up? >> >> >> Any thoughts on >> >> http://www.ietf.org/internet-drafts/draft-burger-sip-info-01.txt >> >> ??? >> >> If you like it, say so. If you hate it, say so. >> >> Text welcome. >> >> >> Notice: This email message, together with any attachments, may contain >> information of BEA Systems, Inc., its subsidiaries and affiliated >> entities, that may be confidential, proprietary, copyrighted and/or >> legally privileged, and is intended solely for the use of the individual or >> entity named in this message. If you are not the intended recipient, and have >> received this message in error, please immediately return this by email and >> then delete it. >> >> >> _______________________________________________ >> Sip mailing list https://www1.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 >> > Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________ Sip mailing list https://www1.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
