On Oct 17, 2007, at 12:50 PM, Brian Stucker wrote:
Let's say we have something (not DTMF) that needs to
transport jpg images that are used as soft-key overlays. To
do what you're suggesting, we'd need a new MIME-type
registration that says "This is just like jpeg, except that
it is only useful for keypad overlays".
The MIME folks would birth kittens.
I think you may have misunderstood my example here. I'm postulating
that
you don't change the MIME type (jpeg) you change the supported/
required
header value.
I think that conflicts with the way Supported and Require work. They
both purely say "Can support these options at any time", not "I
expect you to use this particular option's handling for this
particular message"
Let's say you support jpeg for image-mapped touch screen and jpeg for
storing in my pone book and displaying with caller ID. You'd indicate
support for both in "Supported" and would not reject a request with
Require for both.
I send you a jpeg. How do I tell you whether to put it on your screen
as an image map or store it in your phone book?
--
Dean
_______________________________________________
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
