> -----Original Message----- > From: Adam Roach [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 27, 2007 8:17 AM > To: Stucker, Brian (RICH1:AR00) > Cc: Hadriel Kaplan; [email protected] > Subject: Re: [Sip] INFO > > Brian Stucker wrote: > >> Eric's document basically takes the second approach, > grandfathering > >> all uses of INFO that are currently published in an RFC or > an active > >> internet-draft, and forbidding any others. The list is not > long; I'll > >> replicate it here: > >> > >> 1. RFC 3372 > >> > >> You want more than that, you really need packages. > >> > > > > Expand that list to include application/dtmf and I think you'll > > largely end the debate. > > > > It wouldn't be fair to ask you to show me the IANA > registration for that MIME type, so I won't -- but the > practical problem here is that no one has even *tried* > formalizing this mechanism. > > To be clear, I would argue against standardizing such an > approach (but that discussion is tangential to this one, and > would only distract). My point is: even if someone wants to > support your position, there's nothing for them to support; > there's not even an individual draft -- not even an *expired* > one -- documenting the INFO usage you're promoting.
I'm not promoting anything, I think the issue is fairly moot as many devices support 2833/4733. I'm trying to be practical here. I wasn't aware that nobody had even bothered to register for the MIME type, that's pretty sad. I just don't buy the argument that you can't figure out what to do with this usage based on the information sent. Getting an INFO you don't understand is no worse than getting any other message or content type you don't understand. Plus, if you don't understand it, the guy sending it (in this case) is clearly going to get the angry call from the customer because they can't get their DTMF buttons to work on their device. Not having any documentation for it, in a very twisted (and not recommended) way, even further proves this point because folks are using it without having to be told much about how it works! Not the way we want to operate though. Regards, Brian _______________________________________________ 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
