Multiple body-parts in one INFO
Hadriel Kaplan <[email protected]>
| Newsgroups | gmane.ietf.sip |
|---|---|
| Message-ID | <E6C2E8958BA59A4FB960963D475F7AC31374B1F0F0@mail> |
Ignoring the multiple *packages* per INFO for this email - this one is about multiple *body parts* per INFO. Was there consensus/hum on documenting that explicitly in this draft, in Minneapolis? Of course the INFO message has to support multiple body-parts, as does any SIP message. The question is: 1) can we just say in the draft it must support it and point to the relevant RFCs, or... 2) do we have to explicitly describe how it's supported/handled for INFO in particular? Doing 2 implies handling multiple body-parts has some unique issues for INFO. Since the Subscribe/Notify RFC does not have any such text, AFAICT, I fail to see what is unique about INFO package usage from Subscribe/Notify event packages or even just MESSAGE messages, with regards to handling of multiple body-parts. I have tried to glean that answer from the numerous emails about this issue, but they were intertwined with multiple packages per INFO, and I can't seem to find the answer. -hadriel _______________________________________________ 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