From: Paul Kyzivat <[email protected]>
> Section 12.1 makes it clear that for multipart/alternative, only the
> handling property for the selected alternative matters.
So you are saying that a multipart/alternative may have several parts
with handling=required, and that I only have to be capable of handling
the part I choose?
RFC 3459 uses multiparts in a somewhat different way that SIP does.
In SIP, the I-D suggests that components of a multipart/alternative
should have handling=optional and that the processor should ignore the
handling parameter:
The UA SHOULD also set the 'handling' parameter of all the
body part within the 'multipart/alternative' to 'optional'
(the receiver will process the body parts based on the
handling parameter of the 'multipart/alternative' body; the
receiver will ignore the handling parameters of the body
parts).
The receiver SHOULD ignore the handling parameters of the body
parts within the 'multipart/ alternative'.
Dale
_______________________________________________
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.