On Jul 15, 2008, at 2:12 PM, Paul Kyzivat wrote:
IMO the registry of existing usages is at least, if not more, important than standardizing future usages. It gets all the proprietary usages out in the light of day. That will provide a way to understand what sort of mess we have.
Possible registry structure:Usage-Name Info-type MIME-Type Content-Disposition Option-Tag Specification ---------- --------- --------------------- ------------------- --------- ------------- ISUP ISUP application/ISUP N/A N/ A RFC 3398 QSIG QSIG application/QSIG N/A N/ A RFC 4497 DTMF DTMF application/dtmf N/A N/ A N/A DTMF Relay DTMFrel application/dtmf-relay N/A N/ A draft-kaplan-sipping-dtmf-package-01 Snapshot snapshot image/jpeg render snapshot draft-ietf-sip-snapshot-00 (std track)
Here's a question: The ISUP docs use an outer multipart MIME type, with the application/whatever inside. What does it mean when you have an INFO containing multiple parts of mismatched types?
-- Dean
_______________________________________________ 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
