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.
/a
_______________________________________________
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
